Pkg xen devel - Jan 2012 - Bug#657014: Wheezy, Squeeze and Ubuntu server 11.10 has missing boot option to Xen

Package: xen-hypervisor-4.1-amd64
Version: 4.1.2-2

When installing xen-linux-system on a new Dell R810 server, Wheezy, 
Squeeze and Ubuntu server 11.10 all boot fine when booted directly into 
the standard kernel, but when booting through Xen (after installing the 
package xen-linux-system) the boot process hangs as soon as Xen passes 
control to the Dom0 kernel:

"Gave up waiting for root device" etc

and it gives me Busybox, but it is also frozen, so there's no other 
option that reboot.

After several days of troubleshooting it turns out that adding dom0_mem 
option (e.g. dom0_mem=8192M) to the multiboot line of 
/etc/grub.d/20_linux_xen FIXES THE PROBLEM !

maybe this has to be fixed in the package?

(I havent tried this out on other hardware, only on the Dell R810 with 
256GB RAM and four eight-core processors)

kind regards,

/Erik

Hi Erik,

Thank you for your bug report.

On Mon, 2012-01-23 at 13:36 +0100, Erik Hjelm?s wrote:
> Package: xen-hypervisor-4.1-amd64
> Version: 4.1.2-2
> 
> When installing xen-linux-system on a new Dell R810 server, Wheezy, 
> Squeeze and Ubuntu server 11.10 all boot fine when booted directly into 
> the standard kernel, but when booting through Xen (after installing the 
> package xen-linux-system) the boot process hangs as soon as Xen passes 
> control to the Dom0 kernel:
> 
> "Gave up waiting for root device" etc
> 
> and it gives me Busybox, but it is also frozen, so there's no other 
> option that reboot.
This might be the same issue as #649923. But please could you provide
full console logs so we can verify. If you are able to try the patch in
that bug or perhaps a backported 4.1 hypervisor that would also be
potentially interesting.
> After several days of troubleshooting it turns out that adding dom0_mem 
> option (e.g. dom0_mem=8192M) to the multiboot line of 
> /etc/grub.d/20_linux_xen FIXES THE PROBLEM !
> 
> maybe this has to be fixed in the package?
That file is provided by grub, not the hypervisor but I don't think that
fix will work since a) really it is a workaround not a fix and b) it is
not really possible to determine what is the right number to use for any
given system.

Ian.
> (I havent tried this out on other hardware, only on the Dell R810 with 
> 256GB RAM and four eight-core processors)
> 
> kind regards,
> 
> /Erik
> 
> 
> 
> _______________________________________________
> Pkg-xen-devel mailing list
> Pkg-xen-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-xen-devel
> 
-- 
Ian Campbell

You are number 6!  Who is number one?

Processing control commands:
> reassign -1 src:linux 3.2.21-3
Bug #657014 [xen-hypervisor-4.1-amd64] Wheezy, Squeeze and Ubuntu server 11.10
has missing boot option to Xen
Bug reassigned from package 'xen-hypervisor-4.1-amd64' to
'src:linux'.
No longer marked as found in versions xen/4.1.2-2.
Ignoring request to alter fixed versions of bug #657014 to the same values
previously set
Bug #657014 [src:linux] Wheezy, Squeeze and Ubuntu server 11.10 has missing boot
option to Xen
Marked as found in versions linux/3.2.21-3.
> tag -1 +upstream
Bug #657014 [src:linux] Wheezy, Squeeze and Ubuntu server 11.10 has missing boot
option to Xen
Added tag(s) upstream.

-- 
657014: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657014
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems