tags 591093 fixed-upstream thanks On Sat, Jul 31, 2010 at 01:44:17PM -0700, Stuart Chalmers wrote: > (dom0) System is set up with a single disk with both /boot and / (root) > contained within an LVM2 physical volume. > > When Xen (xen-hypervisor-4.0-amd64 4.0.1~rc3-1 and linux-image-2.6.32-5-amd64 > 2.6.32-15) and Grub are installed > the following is automatically placed in/boot/grub/grub.cfg for the Xen menu > entries: > > -- > echo 'Loading Linux 2.6.32-5-xen-amd64 ...' > multiboot /boot/xen-4.0-amd64.gz placeholder > module /boot/vmlinuz-2.6.32-5-xen-amd64 placeholder root=UUID=<UUID of > what seems to be the root device - (/dev/disk/by-uuid/<UUID> -> /dev/dm-0 > (root))> ro quiet > -- > > Note that this contrasts with the non-Xen entries: > > -- > echo 'Loading Linux 2.6.32-5-xen-amd64 ...' > linux /boot/vmlinuz-2.6.32-5-xen-amd64 root=/dev/mapper/<LVM2 volume > group>-<LVM2 logical volume for root> ro quiet > --
I've fixed this upstream. 2010-08-01 Colin Watson <cjwat...@ubuntu.com> * util/grub.d/20_linux_xen.in: Don't use UUID for LVM root (matching util/grub.d/10_linux.in). Fixes Debian bug #591093. > Furthermore, the system has an ATI Radeon graphics card installed > which seems to use Kernel Mode Setting (KMS) by default and this > causes further issues when starting the X server in the system with > Xen (in fact, firmware-linux-nonfree-0.26 had to be installed in order > to get an X session regardless of Xen being started or not). I don't plan to do anything about this in GRUB; it's a kernel problem, and it should be handled there. Of course, you can set GRUB_CMDLINE_XEN=nomodeset in /etc/default/grub on your system if you wish. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org