This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Xen4.1.0 and Fedora15 Block device bug?

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] Xen4.1.0 and Fedora15 Block device bug?
From: "Fajar A. Nugraha" <list@xxxxxxxxx>
Date: Fri, 8 Jul 2011 15:25:57 +0700
Cc: "xen@xxxxxxxxxxxxxxxxxxxxxxx" <xen@xxxxxxxxxxxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Travis <corasian@xxxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Delivery-date: Fri, 08 Jul 2011 01:26:28 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110707205833.GA1382@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <BANLkTi=j8Oimr1NzwPXzwL_a29fGSc3GZA@xxxxxxxxxxxxxx> <BANLkTikDN7kWjCzvJeaDQW56WF7Weojubw@xxxxxxxxxxxxxx> <BANLkTikp0Lv_mEeDz+E6rBw9Du=D=FUZCg@xxxxxxxxxxxxxx> <BANLkTimGOj5o1VDd+FnQ2Z_fr+8mm-QkDQ@xxxxxxxxxxxxxx> <1309586555.6460.16.camel@xxxxxxxxxxxxxxxxxxxx> <BANLkTikaHZCFg2RpgUzwFaztpVQz=ycijw@xxxxxxxxxxxxxx> <BANLkTi=S=UHGzMjEjGB8xMxRv8BMKngXOw@xxxxxxxxxxxxxx> <20110705135259.GE2972@xxxxxxxxxxxx> <CAKbLq_+6LxK51rhiq=zu+qMxkMtb=S+DZ37kuPQAM3672+=6bw@xxxxxxxxxxxxxx> <20110706133250.GA4138@xxxxxxxxxxxx> <20110707205833.GA1382@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Fri, Jul 8, 2011 at 3:58 AM, Konrad Rzeszutek Wilk
<konrad.wilk@xxxxxxxxxx> wrote:
> 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 
>> running?
> So I didn't even attempt to install it under HVM. I put this in my config 
> file:
> kernel = "/mnt/tftpboot/f15-x86_64/images/pxeboot/vmlinuz"
> ramdisk="//mnt/tftpboot/f15-x86_64/images/pxeboot/initrd.img"

That's PV isn't it? It shouldn't be a problem since PV guests don't
need xen-platform-pci

> extra="console=hvc0 debug earlyprintk=xenboot askmethod vnc"
> memory = 1024
> name = "Fedora"
> vcpus=2
> vif = [ 'mac=00:0F:4B:00:00:63,bridge=switch' ]
> disk = [ 'phy:/dev/vg_guest_1/FC15,xvda,w' ]
> boot = "dnc"
> vnc=1
> videoram=8
> vnclisten=""
> vncpasswd=''
> stdvga=0
> serial='pty'
> 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