-----Original Message-----
From: Tom Horsley tomhorsley@adelphia.net Sent: Nov 7, 2006 9:41 AM To: fedora-list@redhat.com Cc: For users of Fedora fedora-list@redhat.com Subject: Re: why did FC6 install a XEN kernel on my inspiron?
My system can support Xen, but I was also surprised to find nothing except a Xen kernel installed when I did a clean install. I had to install the non-Xen kernel via yum.
I don't know if you can run yum install from rescue mode, but that might be an option to get the non-Xen kernel if you can't boot at all with the Xen kernel.
i believe my error was that i've never played with XEN before and, during the install, i selected "virtualization" thinking, "hey, maybe i'll get around to playing with that some day."
as i read it now, selecting that was what gave me the XEN kernel to begin with, is that right?
rday
On Tuesday 07 November 2006 14:51, Robert P. J. Day wrote:
-----Original Message-----
From: Tom Horsley tomhorsley@adelphia.net Sent: Nov 7, 2006 9:41 AM To: fedora-list@redhat.com Cc: For users of Fedora fedora-list@redhat.com Subject: Re: why did FC6 install a XEN kernel on my inspiron?
My system can support Xen, but I was also surprised to find nothing except a Xen kernel installed when I did a clean install. I had to install the non-Xen kernel via yum.
I don't know if you can run yum install from rescue mode, but that might be an option to get the non-Xen kernel if you can't boot at all with the Xen kernel.
i believe my error was that i've never played with XEN before and, during the install, i selected "virtualization" thinking, "hey, maybe i'll get around to playing with that some day."
as i read it now, selecting that was what gave me the XEN kernel to begin with, is that right?
rday
That's what I found. If you select virtulization during the install it only seems to installl the Xen kernel. Don't know if that's a bug or a feature ;-)
Tony
On Tue, 7 Nov 2006, Tony Molloy wrote:
That's what I found. If you select virtulization during the install it only seems to installl the Xen kernel. Don't know if that's a bug or a feature ;-)
It is probably a feature. If you are going to run xen subsystems, the base domain needs to be running xen as well (or more precisely a 0-domain on top of a xen hypervisor).
Michael Young