[Bug 635380] New: pygrub boot of Ubuntu 10.04.1 LTS DomU Guest fails @ Grub2 config; Redhat 5 patch referenced
https://bugzilla.novell.com/show_bug.cgi?id=635380 https://bugzilla.novell.com/show_bug.cgi?id=635380#c0 Summary: pygrub boot of Ubuntu 10.04.1 LTS DomU Guest fails @ Grub2 config; Redhat 5 patch referenced Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Xen AssignedTo: jdouglas@novell.com ReportedBy: pgngw+dev001+novell.com@f-m.fm QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.8) Gecko/20100723 SUSE/3.6.8-1.3 Firefox/3.6.8 running opensuse 11.3 + xen 4 rpm -qa | egrep -i "xen-4|kernel-xen" xen-4.0.0_21091_05-6.6.x86_64 kernel-xen-2.6.34-12.3.x86_64 installing a Ubuntu Lucid 10.04.1 LTS server instance as a DomU Guest, initial install is OK, using DomU guest .cfg, builder = 'linux' kernel = '/boot/xenguests/ubuntu/installer/vmlinuz' ramdisk ='/boot/xenguests/ubuntu/installer/initrd.gz' sourced from, http://ubuntu.mirrors.tds.net/pub/ubuntu/dists/lucid/main/installer-amd64/cu... works perfectly. at Guest reboot, using runtime .cfg with pygrub, builder = 'linux' #kernel = '/boot/xenguests/ubuntu/installer/vmlinuz' #ramdisk ='/boot/xenguests/ubuntu/installer/initrd.gz' bootloader = '/usr/bin/pygrub' ... fails with, "VmError: Boot loader didn't return any data!" speaking with #ubuntu-server, told this is likely an incompatibility of Opensuse's pygrub with Ubuntu's Grub2 config. the issue has been addressed, and patched for Redhat5, Grub2 guest support for RHEL5 Xen pygrub https://bugzilla.redhat.com/show_bug.cgi?id=577511#c15 pygrub launch of non-Grub2 guests works OK. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=635380
https://bugzilla.novell.com/show_bug.cgi?id=635380#c1
--- Comment #1 from dev001x _
https://bugzilla.novell.com/show_bug.cgi?id=635380
https://bugzilla.novell.com/show_bug.cgi?id=635380#c
dev001x _
https://bugzilla.novell.com/show_bug.cgi?id=635380
https://bugzilla.novell.com/show_bug.cgi?id=635380#c
Charles Arnold
https://bugzilla.novell.com/show_bug.cgi?id=635380
https://bugzilla.novell.com/show_bug.cgi?id=635380#c2
--- Comment #2 from dev001x _
https://bugzilla.novell.com/show_bug.cgi?id=635380
https://bugzilla.novell.com/show_bug.cgi?id=635380#c3
--- Comment #3 from dev001x _
https://bugzilla.novell.com/show_bug.cgi?id=635380
https://bugzilla.novell.com/show_bug.cgi?id=635380#c4
James Fehlig
have these patches been applied to SLES 11? i.e., is SLES' pygrub already Grub2-aware?
None of them have been applied to SLES11. But like 11.3, most are in SLES11 SP1, with exception of 21188 and 21461. I don't think the latter is affecting you though, so 21188 is probably the fix you need. Have you tried that patch as described in your comment #1? (The steps are a bit overkill though. I think you could apply the patch directly to /usr/lib64/python2.6/site-packages/grub/GrubConf.py and remove the corresponding .pyc.) Preston, do you have a Ubuntu pv domU handy? Can you try to reproduce this so we can verify if upstream c/s 21188 resolves the issue? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=635380
https://bugzilla.novell.com/show_bug.cgi?id=635380#c5
--- Comment #5 from dev001x _
None of them have been applied to SLES11. But like 11.3, most are in SLES11 SP1, with exception of 21188 and 21461. I don't think the latter is affecting you though, so 21188 is probably the fix you need. Have you tried that patch as described in your comment #1? (The steps are a bit overkill though. I think you could apply the patch directly to /usr/lib64/python2.6/site-packages/grub/GrubConf.py and remove the corresponding .pyc.)
cd /usr/lib64/python2.6/site-packages/grub/ cp GrubConf.py GrubConf.py.ORIG mv GrubConf.pyc GrubConf.pyc.ORIG wget -k -O grub2A.patch "https://bugzilla.redhat.com/attachment.cgi?id=407518&action=diff&context=patch&collapsed=&headers=1&format=raw" wget -k -O grup2B.patch "https://bugzilla.redhat.com/attachment.cgi?id=416763&action=diff&context=patch&collapsed=&headers=1&format=raw" patch -p4 < grub2A.patch patching file GrubConf.py Reversed (or previously applied) patch detected! Assume -R? [n] patch -p4 < grub2B.patch patching file GrubConf.py Reversed (or previously applied) patch detected! Assume -R? [n] hm. in a bit, i'll look at what part's not yet been applied, and try a manual application ... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=635380
https://bugzilla.novell.com/show_bug.cgi?id=635380#c6
James Fehlig
https://bugzilla.novell.com/show_bug.cgi?id=635380
https://bugzilla.novell.com/show_bug.cgi?id=635380#c7
--- Comment #7 from James Fehlig
https://bugzilla.novell.com/show_bug.cgi?id=635380
https://bugzilla.novell.com/show_bug.cgi?id=635380#c8
--- Comment #8 from dev001x _
https://bugzilla.novell.com/show_bug.cgi?id=635380
https://bugzilla.novell.com/show_bug.cgi?id=635380#c9
dev001x _
https://bugzilla.novell.com/show_bug.cgi?id=635380
https://bugzilla.novell.com/show_bug.cgi?id=635380#c10
--- Comment #10 from James Fehlig
https://bugzilla.novell.com/show_bug.cgi?id=635380
https://bugzilla.novell.com/show_bug.cgi?id=635380#c11
James Fehlig
https://bugzilla.novell.com/show_bug.cgi?id=635380
https://bugzilla.novell.com/show_bug.cgi?id=635380#c12
dev001x _
I think you too will find the bug is fixed once you get past the gntdev issue - which is certainly a different and separate bug.
after the reinstall from d.o.o/repositories/Virtualization:/openSUSE11.3/openSUSE_11.3/ i noted cd /dev/xen ls -al total 0 drwxr-xr-x 2 root root 120 2010-09-10 10:39 ./ drwxr-xr-x 19 root root 4920 2010-09-10 11:01 ../ crw------- 1 root root 252, 0 2010-09-10 10:39 blktap0 crw------- 1 root root 10, 57 2010-09-10 10:39 evtchn crw------- 1 root root 251, 0 2010-09-10 10:39 gntdev crw------- 1 root root 10, 59 2010-09-10 10:38 pci_iomul that gntdev already exists ... but not as a link. checking, ls -al /dev/gntdev crw------- 1 root root 251, 0 2010-09-10 10:39 /dev/gntdev gntdev is 'new' to me. digging around, i find this, [Xen-devel] [PATCH] xc: deal with xen/evtchn and xen/gntdev device names http://lists.xensource.com/archives/html/xen-devel/2010-05/msg01556.html which I suspect is (?) relevant ... sanity check for kernel mods, lsmod | egrep -i "gnt|evt" gntdev 8579 0 evtchn 38482 1 looks ok. with this verified, I tried the guest boot -- same failure as before. i mv'd the gntdev, replaing it with the symlink. smae problem. on a hunch, i did a complete de-install, then re-install of Xen -- i.e., not just an upgrade -- from the updated repos ... now, @ launch of the Ubuntu DomU, via pygrub: pyGRUB version 0.6 ┌────────────────────────────────────────────────────────────────────────┐ │ Ubuntu, with Linux 2.6.32-24-generic │ │ Ubuntu, with Linux 2.6.32-24-generic (recovery mode) │ │ Memory test (memtest86+) │ │ Memory test (memtest86+, serial console 115200) │ Started domain ubu (id=2) .. Ubuntu 10.04.1 LTS ubu hvc0 ubu login: Password: Linux ubu 2.6.32-24-generic #42-Ubuntu SMP Fri Aug 20 14:21:58 UTC 2010 x86_64 GNU/Linux Ubuntu 10.04.1 LTS which looks like success! i assume 4.0.1 will soon enough get promoted to distro update repos. any sense for rough timeframe? I'll keep the updated repo around 'til then, but prefer to stick with the standard repos if/when possible. thanks for the help. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=635380
https://bugzilla.novell.com/show_bug.cgi?id=635380#c13
James Fehlig
which looks like success!
Great!
i assume 4.0.1 will soon enough get promoted to distro update repos. any sense for rough timeframe?
Unfortunately it will be quite some time - probably a few months. We started an update process for SLE11 SP1 and 11.3 not long ago and that is in QA now. These patches missed that update and will have to wait for the next round, which is on a 2-3 month cycle. Sorry. It sounds like we can really close this bug now :-). Thanks for reporting and testing the fix. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=635380
https://bugzilla.novell.com/show_bug.cgi?id=635380#c14
--- Comment #14 from dev001x _
https://bugzilla.novell.com/show_bug.cgi?id=635380
https://bugzilla.novell.com/show_bug.cgi?id=635380#c15
--- Comment #15 from James Fehlig
https://bugzilla.novell.com/show_bug.cgi?id=635380
https://bugzilla.novell.com/show_bug.cgi?id=635380#c16
--- Comment #16 from dev001x _
I don't see any problems with openSUSE 11.3 domUs on my system. But yes, please do open a new bug if you can reproduce with the xen packages in Virtualization:openSUSE11.3. Thanks.
still a problem :-/ new bug opened at https://bugzilla.novell.com/show_bug.cgi?id=645251 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=635380
https://bugzilla.novell.com/show_bug.cgi?id=635380#c17
Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=635380
https://bugzilla.novell.com/show_bug.cgi?id=635380#c18
Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=635380
https://bugzilla.novell.com/show_bug.cgi?id=635380#c19
Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=635380
https://bugzilla.novell.com/show_bug.cgi?id=635380#c
Swamp Workflow Management
participants (1)
-
bugzilla_noreply@novell.com