On Fri, Feb 11, 2011 at 10:49:29AM +0100, Heikki Levanto wrote:
The problem seems to be that grub2 wants to boot the machine into a regular
linux kernel, and not the xen hypervisor.
There is a workaround at
http://wiki.debian.org/Xen#XenonTesting.2BAC8-SqueezeandonUnstable.2BAC8-SidasDom0.2CtocreateamultitudeofDomU.27s
In short it is
mv -i /etc/grub.d/10_linux /etc/grub.d/50_linux
update-grub2
This makes it prefer the hypervisor.
Actually, that will give problems next time you upgrade grub. If nothing else,
do a
echo #moved to 50_linux /etc/grub.d/10_linux
so that apt will warn you before (re)establishing 10_linux.
It would be more correct to edit the default line in /etc/alternatives/grub to
point to the hypervisor you want to start. That is also the place to set up
boot parameters for the hypervisor and for the kernel it boots dom0 in.
--
Heikki Levantoheikki at indexdata dot dk In Murphy We Turst
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
