[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Can't boot PV from qcow image

  • To: "xen-users@xxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxx>
  • From: Matthias Blankenhaus <matthiasblankenhaus@xxxxxxxxx>
  • Date: Tue, 18 Sep 2012 19:39:22 -0700 (PDT)
  • Delivery-date: Wed, 19 Sep 2012 02:41:32 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=SKTX/OA3K5YmtXZs9r6uSCPe0I+kWeGaqZ4VkaI7sFe/isA5nMFpHV0oapL8d54XE3iBYMZPUsiAtmrxn++hjDIm00sjjiPJd6aqBXuLWvYUHjVvmqbW+YUTVrnvN2ph0YstKo7+wnWdgJ91No8LEaDpPX2R4QsGhdOOC/7nyiQ=;
  • List-id: Xen user discussion <xen-users.lists.xen.org>

Howdy !

I have been trying for more than 2 days to work this out without success. While I am able to identify a qcow image as a block device within the
guest, so far I can not use a qcow or qcow2 images as a block device due to IO errors.  As a reference, I am able to mount raw images via loopback device through DOM0.

Here is my setting:
- Xen 4.2.0
- Debian wheezy with 3.1.0-rc8 / 64bit [without blktap2 patch]
- nfs mounted guest images

- PV
- CentOS 6.2 with /, no initrd
- no grub
- Xen guest disk config:
disk = ['format=raw,vdev=xvda,target=/dev/loop0','tap:qcow:/var/lib/xen-images/21339039-df03-43e2-b94f-2b600e2492b2/rootfs.qcow,xvdb,w'

When attempting to access the qcow backed device (xvdb) I get these errors:

# less /var/log/messages
Sep 19 01:26:15 kernel: [  189.596610] Buffer I/O error on device xvdb, logical block 163967
Sep 19 01:26:15 kernel: [  189.936239] end_request: I/O error, dev xvdb, sector 1311744
Sep 19 01:26:15 kernel: [  189.940237] Buffer I/O error on device xvdb, logical block 163968
Sep 19 01:26:16 kernel: [  190.276228] end_request: I/O error, dev xvdb, sector 1572864

Meanwhile, on DOM0 I see the following output in the process tree:
root       911     2  0 01:49 ?        00:00:00 [blkback.59.xvda]
root       848     1  0 01:49 ?        00:00:10 /usr/lib/xen/bin/qemu-system-i386 -xen-domid 59 -chardev socket,id=lib

The block back-end kernel thread is backing my rootfs which is mapped to a loopback device on DOM0.  I think qemu was launched to
back the qcow device.  Thus, this matches my conceptional understanding of how things should work.

Ultimately, I am looking for a way to boot PVs from disk image using Xen 4.2.  I was able to do this under Xen 4.1.x using a raw disk image in conjunction with the tap:aio option for the guests' disk spec and without using a loopback mount on DOM0.

Your help is much appreciated,

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.