[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Hypervisor error messages after xl block-detach with linux 3.18-rc5
On 11/24/2014 11:02 AM, Ian Campbell wrote: On Mon, 2014-11-24 at 10:55 +0100, Juergen Gross wrote:On 11/21/2014 02:57 PM, Konrad Rzeszutek Wilk wrote:On Fri, Nov 21, 2014 at 09:42:11AM +0100, Juergen Gross wrote:Hi, while testing my "linear p2m list" patches I saw the following problem (even without my patches in place): In dom0 running linux 3.18-rc5 on top of Xen 4.4.1 I modified the disk image of a guest by attaching it to dom0: xl block-attach 0 file:/var/lib/libvirt/images/opensuse13-1/xvda,xvda,w mount /dev/xvda2 /mnt ... umount /mnt xl block-detach 0 xvdaDid some more testing: - Seems to occur only when attaching a block device to dom0That means a qdisk backed situation then, I think. Is your qemu up to date? http://xenbits.xen.org/gitweb/?p=qemu-upstream-unstable.git;a=commit;h=abbbc2f09a53f8f9ee565356ab11a78af006e45e resulted in slightly different messages, but could be related? Tried it with xen-unstable and newest qemu. Now I have another problem: xl -vvv block-attach 0 file:/var/lib/libvirt/images/opensuse13-1/xvda,xvda,wlibxl: debug: libxl.c:4178:libxl_device_disk_add: ao 0xbac0f0: create: how=(nil) callback=(nil) poller=0xbac1d0 libxl: error: libxl.c:1897:device_addrm_aocomplete: unable to add devicelibxl: debug: libxl_event.c:1739:libxl__ao_complete: ao 0xbac0f0: complete, rc=-16 libxl: debug: libxl.c:4178:libxl_device_disk_add: ao 0xbac0f0: inprogress: poller=0xbac1d0, flags=ic libxl: debug: libxl_event.c:1711:libxl__ao__destroy: ao 0xbac0f0: destroy libxl_device_disk_add failed. rc=-16 means ERROR_JSON_CONFIG_EMPTY. Could it be that newest tools won't let me attach a block device to dom0? IMHO that's a severe regression! Juergen _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |