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

[Xen-users] Questions about mounting tap:qcow images in Xen 4.1.1/Ubuntu 11.10 dom0

  • To: "xen-users@xxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxx>
  • From: Antony Saba <Antony.Saba@xxxxxxxxxxxx>
  • Date: Wed, 11 Jan 2012 00:48:35 +0000
  • Accept-language: en-US
  • Acceptlanguage: en-US
  • Delivery-date: Wed, 11 Jan 2012 00:50:46 +0000
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AczP+sGu555VYmj7QrOm2LL04epwTA==
  • Thread-topic: Questions about mounting tap:qcow images in Xen 4.1.1/Ubuntu 11.10 dom0

Hello xen-users,

I am trying to access a guest disk that was created using qcow-create from dom0 using xl block-attach/block-detach, which appears to be the current "Xen way" of doing it.  However, after the following command, no /dev/xvdb is appearing:

$ xl block-attach 0 tap:qcow2:/home/root/images/test.img xvdb

I am using Xen 4.1.2 (installed from source tarball) with an Ubuntu 11.10 dom0, using the supplied kernel-server-3.0.0-14 image.  I have the xen_blkfront module loaded, and see the following message which makes me think I am almost there:

[ 8494.188638] blkfront device/vbd/51728 num-ring-pages 1 nr_ents 32.

Also, if I attempt xl block-detach for that device, takes up to 30 seconds to return, and following that, xl block-list 0 segfaults.

I saw this thread on xen-devel, but it wasn't clear to me if there has been any resolution of this issue:

I also saw some posts which mentioned that udev should actually be responsible for creating the devices, but haven't found any good references for what the rules should look like for that, so any help for that would be appreciated as well.



Xen-users mailing list



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