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

Re: [Xen-users] Can not attach vhd image and start vhd-based domU



On Fri, 2015-05-15 at 21:55 +0300, Andrey wrote:
> > For debugging it can be useful to do "xl -N block-attach 0 <diskspec>",
> > this is just a dry-run block attach to dom0, which will print the parsed
> > version of the spec
> 
> Big thanks for the hints. Strange but I get the error while trying to 
> run xl block-attach 0 
> format=vhd,vdev=xvda,access=w,backendtype=tap,target=/home/data/centos-6.vhd 
> :
> 
> libxl: error: libxl_device.c:289:libxl__device_disk_set_backend: no 
> suitable backend for disk xvda
> libxl: error: libxl.c:1727:device_addrm_aocomplete: unable to (null) device
> libxl_device_disk_add failed.

You've trimmed the logs which would confirm, but I expect that libxl has
determined somehow that your systems doesn't have blktap support
enabled.

It might be missing at compile time from the toolstack or the kernel
module might be missing at runtime, or something else...


> 
> xl -N produces correct parsing:
> 
> disk: {
>      "backend_domid": 0,
>      "backend_domname": null,
>      "pdev_path": "/home/data/centos-6.vhd",
>      "vdev": "xvda",
>      "backend": "tap",
>      "format": "vhd",
>      "script": null,
>      "removable": 0,
>      "readwrite": 1,
>      "is_cdrom": 0
> }
> 
> >
> > Ian.
> >
> >



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users


 


Rackspace

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