Re: [Xen-devel] Xen4.1.0 and Fedora15 Block device bug?
On Fri, Jul 8, 2011 at 3:58 AM, Konrad Rzeszutek Wilk
> On Wed, Jul 06, 2011 at 09:32:50AM -0400, Konrad Rzeszutek Wilk wrote:
>> > > > https://bugzilla.redhat.com/show_bug.cgi?id=718382
>> > >
>> > > Anybody have some patches for it? They can be posted on the dracut
>> > > mailing
>> > list?
>> > > Did loading those two modules in the install initrd fix the installation?
>> > The aforementioned 'xen_emul_unplug=never' kernel arg has worked well
>> > enough
>> > for me. I've pasted it into my kickstart files and my vms have been
>> > installing and running fine.
>> Ok, but with HVM drivers instead of the PV - at least during installation.
>> Is the 'xen_emul_unplug=never' option also present in your VM when it is
> So I didn't even attempt to install it under HVM. I put this in my config
> kernel = "/mnt/tftpboot/f15-x86_64/images/pxeboot/vmlinuz"
That's PV isn't it? It shouldn't be a problem since PV guests don't
> extra="console=hvc0 debug earlyprintk=xenboot askmethod vnc"
> memory = 1024
> name = "Fedora"
> vif = [ 'mac=00:0F:4B:00:00:63,bridge=switch' ]
> disk = [ 'phy:/dev/vg_guest_1/FC15,xvda,w' ]
> boot = "dnc"
> And was able to install it.
So after some test on HVM domU (read: adding xen-platform-pci.ko to
initrd.img, and running "insmod ./xen-platform-pci.ko" just before
anaconda detects disk), I was able to get the installer to proceed.
One thing that puzzles me though, when booting using installer's
kernel, the module xen-platform-pci and xen-blkfront was not loaded
(not until I ran "insmod". However the kernel prints
[ 0.000000] Hypervisor detected: Xen HVM
[ 0.000000] Xen version 4.1.
[ 0.000000] Netfront and the Xen platform PCI driver have been
compiled for this kernel: unplug emulated NICs.
[ 0.000000] Blkfront and the Xen platform PCI driver have been
compiled for this kernel: unplug emulated disks.
[ 0.000000] You might have to change the root device
[ 0.000000] from /dev/hd[a-d] to /dev/xvd[a-d]
[ 0.000000] in your root= kernel command line option
shouldn't the unplug only happen if the drivers are actually loaded?
Xen-devel mailing list