[Bug 493293] New: pygrub fails to load domU (Boot loader didn't return any data)
http://bugzilla.novell.com/show_bug.cgi?id=493293 Summary: pygrub fails to load domU (Boot loader didn't return any data) Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: All OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Xen AssignedTo: cgriffin@novell.com ReportedBy: nice@titanic.nyme.hu QAContact: qa@suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.8) Gecko/2009032600 SUSE/3.0.8-1.1.1 Firefox/3.0.8 I've created the following domU: carrier4:/var/log/xen # cat /etc/xen/vm/openSUSE111-64 name="openSUSE111-64" uuid="abb18405-b7fa-2caa-fcef-03adb7be0001" memory=1024 vcpus=1 on_poweroff="destroy" on_reboot="restart" on_crash="destroy" on_xend_start = "ignore" on_xend_stop = "shutdown" localtime=0 keymap="en-us" builder="linux" bootloader="/usr/bin/pygrub" disk=[ 'phy:/dev/mapper/openSUSE111-64,xvda,w' ] vif=[ 'mac=00:16:3e:00:00:01,bridge=br0' ] vfb=['type=vnc,vncdisplay=11'] /dev/mapper/openSUSE111-64 is a multipath volume and looks like this: carrier4:/var/log/xen # fdisk -l /dev/mapper/openSUSE111-64 Disk /dev/mapper/openSUSE111-64: 21.4 GB, 21474836480 bytes 255 heads, 63 sectors/track, 2610 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x0003aa0a Device Boot Start End Blocks Id System /dev/mapper/openSUSE111-64p1 * 2 653 5237190 83 Linux /dev/mapper/openSUSE111-64p2 654 914 2096482+ 83 Linux /dev/mapper/openSUSE111-64p3 915 2610 13623120 f W95 Ext'd (LBA) /dev/mapper/openSUSE111-64p5 915 1827 7333641 83 Linux /dev/mapper/openSUSE111-64p6 1828 1957 1044193+ 83 Linux /dev/mapper/openSUSE111-64p7 1958 2348 3140676 83 Linux /dev/mapper/openSUSE111-64p8 2349 2610 2104483+ 83 Linux carrier4:/var/log/xen # ls -al /dev/mapper/openSUSE111-64* brw-r----- 1 root disk 253, 105 Apr 8 18:19 /dev/mapper/openSUSE111-64 brw-r----- 1 root disk 253, 145 Apr 8 18:20 /dev/mapper/openSUSE111-64_part1 brw-r----- 1 root disk 253, 146 Apr 8 18:20 /dev/mapper/openSUSE111-64_part2 brw-r----- 1 root disk 253, 147 Apr 8 18:20 /dev/mapper/openSUSE111-64_part3 brw-r----- 1 root disk 253, 148 Apr 8 18:20 /dev/mapper/openSUSE111-64_part5 brw-r----- 1 root disk 253, 149 Apr 8 18:20 /dev/mapper/openSUSE111-64_part6 brw-r----- 1 root disk 253, 150 Apr 8 18:20 /dev/mapper/openSUSE111-64_part7 brw-r----- 1 root disk 253, 153 Apr 8 18:20 /dev/mapper/openSUSE111-64_part8 carrier4:/var/log/xen # mount -t ext3 /dev/mapper/openSUSE111-64_part1 /mnt carrier4:/var/log/xen # cat /mnt/boot/grub/menu.lst # Modified by YaST2. Last modification on Wed Mar 4 20:26:51 CET 2009 default 0 timeout 8 ##YaST - generic_mbr gfxmenu (hd0,0)/boot/message ##YaST - activate ###Don't change this comment - YaST2 identifier: Original name: xen### title Xen -- openSUSE 11.1 - 2.6.27.19-3.2 root (hd0,0) kernel /boot/xen.gz module /boot/vmlinuz-2.6.27.19-3.2-xen root=/dev/xvda1 splash=silent showopts module /boot/initrd-2.6.27.19-3.2-xen ###Don't change this comment - YaST2 identifier: Original name: linux### title Xen -- openSUSE 11.1 - 2.6.27.7-9 root (hd0,0) kernel /boot/vmlinuz-2.6.27.7-9-xen root=/dev/xvda1 splash=silent showopts initrd /boot/initrd-2.6.27.7-9-xen carrier4:/var/log/xen # ls -al /mnt/boot/vmlinuz-2.6.27.19-3.2-xen -rw-r--r-- 1 root root 2232171 Feb 25 17:49 /mnt/boot/vmlinuz-2.6.27.19-3.2-xen carrier4:/var/log/xen # ls -al /mnt/boot/initrd-2.6.27.19-3.2-xen -rw-r--r-- 1 root root 5374166 Mar 4 20:28 /mnt/boot/initrd-2.6.27.19-3.2-xen BUT: carrier4:/var/log/xen # ls -al /mnt/boot/xen.gz ls: cannot access /mnt/boot/xen.gz: No such file or directory carrier4:/var/log/xen # ls -al /mnt/boot/vmlinuz-2.6.27.7-9-xen ls: cannot access /mnt/boot/vmlinuz-2.6.27.7-9-xen: No such file or directory carrier4:/var/log/xen # ls -al /mnt/boot/initrd-2.6.27.7-9-xen ls: cannot access /mnt/boot/initrd-2.6.27.7-9-xen: No such file or directory Reproducible: Always Steps to Reproduce: 1. Create a domU based on pygrub 2. xm create <configfile> Actual Results: Doesn't start. Expected Results: It should start just like a few months and updates before, when it was working (except https://bugzilla.novell.com/show_bug.cgi?id=469936) and I didn't do anything else since then, but applied the updates. -- 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=493293
User nice@titanic.nyme.hu added comment
http://bugzilla.novell.com/show_bug.cgi?id=493293#c1
--- Comment #1 from Tamás Németh
http://bugzilla.novell.com/show_bug.cgi?id=493293
User nice@titanic.nyme.hu added comment
http://bugzilla.novell.com/show_bug.cgi?id=493293#c2
--- Comment #2 from Tamás Németh
http://bugzilla.novell.com/show_bug.cgi?id=493293
User nice@titanic.nyme.hu added comment
http://bugzilla.novell.com/show_bug.cgi?id=493293#c3
--- Comment #3 from Tamás Németh
http://bugzilla.novell.com/show_bug.cgi?id=493293
User nice@titanic.nyme.hu added comment
http://bugzilla.novell.com/show_bug.cgi?id=493293#c4
--- Comment #4 from Tamás Németh
http://bugzilla.novell.com/show_bug.cgi?id=493293
User nice@titanic.nyme.hu added comment
http://bugzilla.novell.com/show_bug.cgi?id=493293#c5
--- Comment #5 from Tamás Németh
http://bugzilla.novell.com/show_bug.cgi?id=493293
James Fehlig
http://bugzilla.novell.com/show_bug.cgi?id=493293
User jfehlig@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=493293#c7
James Fehlig
I don't know what happened, but both my 32bit and my 64bit openSUSE11.1 dom0 behaves correctly today! Pygrub works on both machines, in spite of the fact that nothing changed since yesterday, AFAIK.
Are you still having problems? Sounds like the issue doesn't exist anymore. Well, there's still the problem with a domU kernel update generating an invalid menu.lst - but that is not a Xen problem and certainly not a pygrub issue. -- 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=493293
User nice@titanic.nyme.hu added comment
http://bugzilla.novell.com/show_bug.cgi?id=493293#c8
Tamás Németh
http://bugzilla.novell.com/show_bug.cgi?id=493293
User jfehlig@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=493293#c9
James Fehlig
Anyway, just like initially I was unable to use pygrub at all (more exactly initially pygrub worked, then it suddenly went wrong), now I am unable to reproduce the problem.
Sorry. These types of problems are always unsettling since you fear they will return.
You might close this report. If you do so, but the I can reproduce it in the future, do you mind if I reopen it?
Not at all. That's what REOPENED is for :-). 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.
participants (1)
-
bugzilla_noreply@novell.com