http://bugzilla.novell.com/show_bug.cgi?id=516677 User pgnet.dev@gmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=516677#c2 pgnet Dev changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|CLOSED |REOPENED Component|Bootloader |Xen Resolution|FEATURE | AssignedTo|jsrain@novell.com |jdouglas@novell.com QAContact|jsrain@novell.com |qa@suse.de Severity|Normal |Major --- Comment #2 from pgnet Dev 2009-07-03 09:48:12 MDT --- it's not a feature, it's grub needing to work correctly in a legitimate Xen config. moving to 'Xen'. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=516677 User pgnet.dev@gmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=516677#c3 --- Comment #3 from pgnet Dev 2009-07-06 09:05:46 MDT --- hi,

James Fehlig changed: Severity|Major |Normal

grub not working, unable to recognize filesystems in a completely legitimate, supported Xen scenario is not considered "major"? well, i'll disagree -- but defer, as i'm not sure it'll matter much :-/ thanks. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=516677 wei kong changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |ASSIGNED AssignedTo|jfehlig@novell.com |wkong@novell.com -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=516677 User pgnet.dev@gmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=516677#c6 --- Comment #6 from pgnet Dev 2009-07-09 08:41:56 MDT --- hi, (In reply to comment #5)

1: This is may a feature. Due to current sles11/opensuse/sled are not support pv-grub, We are not build/put any pv-grub and stubdom in our product ISO. But user could build it themselves from our source.

iiuc, openSUSE as a *guest* DomU does not require either pv-grub or stubdom to be present in order to boot/run ON a pv-grub Dom0. again, i am NOT using pv-grub in/on *SUSE. does opensuse/sles need to be modified to run as a pv-grub Dom*U*? or, are you suggesting that _policy_ is not to support openSUSE/SLES running as a DomU if launched from "someone else's" pv-grub DomO?

2: I have tried the pv-grub on opensuse11.2-milestone3. It works, messages as below. ------------------pv guest-------------------- Using config file "./xmexample.pv-grub". Started domain ExampleDomain Xen Minimal OS! start_info: 0x986000(VA) Booting 'XEN'

root (hd0,1) Filesystem type is ext2fs, partition type 0x83 kernel /boot/vmlinuz-2.6.27.19-5-xen root=/dev/xvda2 resume=/dev/xvda1 splash=s ilent showopts initrd /boot/initrd-2.6.27.19-5-xen ----------------------------------------------

that looks like console output. and that's generated by the pv-grub Dom0. (a) if you're using the patched Xen sources, then pv-grub's grub will correctly read the filesystem (b) but your root is (hd0,1). i.e. it seems you're booting from a partitioned drive. NOT the case i'm describing, which is booting from a partitionless drieve, e.g., (hd0). here's the console output you'll see in that case: Booting 'PVGRUB' root (hd0) <----------------- NOTE! Filesystem type is ext2fs, using whole disk in THAT case, the grub failure is IN the Guest. so the test case is, once you've booted the release-version *DomU*, @ DomU shell, do: /root > grub GNU GRUB version 0.97 (640K lower / 3072K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename. ] grub> root (hd0) root (hd0) Filesystem type unknown, using whole disk grub> what's _that_ output for your test case?

3: the patch metioned in commnet#1 has been in sles11 and opensuse11.

it has? applied to grub 0.97 source? if that's true, then why does the release's grub fail with "Filesystem type unknown", but the patched, pv-grub DomO's grub work just fine? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=516677 User jsong@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=516677#c8 --- Comment #8 from song james 2009-07-09 20:45:41 MDT --- hi pgnet, Could you give me some information about you testing environment? I want to get some messages that what's the type of your filesystem both in Guest OS and Host, moreover, what's the changeset of the xen source you used and the type of your host OS? thx, -James. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=516677 User pgnet.dev@gmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=516677#c10 --- Comment #10 from pgnet Dev 2009-07-09 21:40:14 MDT --- Created an attachment (id=304281) --> (http://bugzilla.novell.com/attachment.cgi?id=304281) DomU's console output hi, (In reply to comment #8)

Could you give me some information about you testing environment? I want to get some messages that what's the type of your filesystem both in Guest OS and Host, moreover, what's the changeset of the xen source you used and the type of your host OS?

it's an openSUSE 11.1 DomU @ a commercial Xen host, linode.com, http://www.linode.com/wiki/index.php/PV-GRUB booting from their pv-grub-x86_32, Xen/MiniOS Dom0. that's about all the info i can get abt Dom0. i've attached here the console output of my Guest's bootup. here's cat /etc/fstab /dev/xvda /boot ext2 acl,user_xattr 1 2 /dev/xvdb swap swap defaults 0 0 /dev/xvdc / ext3 acl,user_xattr 1 1 /dev/VG_DATA/LV_DATA /data ext3 defaults 1 2 /dev/VG_DATA/LV_CACHE /var/cache ext3 defaults,noatime,nodiratime,data=writeback 1 2 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 and here's @ Guest, default 0 timeout 8 gfxmenu (hd0)/boot/message title PVGRUB root (hd0) kernel /boot/vmlinuz-xen root=/dev/xvdc resume=/dev/xvdb xencons=hvc0 kbdtype=us text nofb selinux=0 edd=off splash=silent noshell showopts initrd /boot/initrd-xen if you'd like add'l info, happy to -- please specify what. again, the system IS booted. it runs. there are NO errors during the boot process, as pv-grub's grub is properly patched. the problem is IN the openSUSE DomU. openSUSE's bundled grub simply doesn't seem to handle the assigned "(hd,0)". iiuc (?), that has nothing to do with pv-grub, but rather that grub remains unpatched to handle an unpartitioned disk. which is a situation that simply manifests in the pv-grub scenario ... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.