Re: Qemu upstream bugs with xen

[Fabio Fantoni <fabio.fantoni@heliman.it>]

Il 11/03/2013 12:55, Frediano Ziglio ha scritto:
> On Fri, 2013-01-18 at 15:44 +0100, Fabio Fantoni wrote:
>> Il 18/01/2013 14:00, Stefano Stabellini ha scritto:
>>> On Fri, 18 Jan 2013, Fabio Fantoni wrote:
>>>> 1) Both linux and windows domU with qemu upstream have an additional
>>>> empty floppy and cdrom.
>>>> Is there a way to remove these additionals block devices?
>>> the best way would be to pass a device or a global command line option
>>> to QEMU to change the default for isa-fdc
>>>
>>>
>>>> 2) xl cd-eject and cd-insert are not working:
>>>>
>>>> xl -vvv cd-eject W7 hdb
>>>> libxl: debug: libxl.c:2389:libxl_cdrom_insert: ao 0x1b95990: create:
>>>> how=(nil) callback=(nil) poller=0x1b95930
>>>> libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk
>>>> vdev=hdb spec.backend=phy
>>>> libxl: debug: libxl_device.c:175:disk_try_backend: Disk vdev=hdb,
>>>> backend phy unsuitable as phys path not a block device
>>>> libxl: error: libxl_device.c:269:libxl__device_disk_set_backend: no
>>>> suitable backend for disk hdb
>>> cd-eject should work by trying to insert an empty cdrom.
>>> In particular the disk format should be LIBXL_DISK_FORMAT_EMPTY, but I
>>> think this is not the case here.
>>> I guess it is a bug in parse_disk_config.
>>>
>>>
>>>> libxl: debug: libxl_event.c:1482:libxl__ao_abort: ao 0x1b95990: abort
>>>> libxl: debug: libxl_event.c:1472:libxl__ao__destroy: ao 0x1b95990: destroy
>>>> xc: debug: hypercall buffer: total allocations:4 total releases:4
>>>> xc: debug: hypercall buffer: current allocations:0 maximum allocations:2
>>>> xc: debug: hypercall buffer: cache current size:2
>>>> xc: debug: hypercall buffer: cache hits:1 misses:2 toobig:1
>>>>
>>>> xl -vvv cd-insert W7 hdb raw:/mnt/vm/iso/QUANTAL.iso
>>>> libxl: debug: libxl.c:2389:libxl_cdrom_insert: ao 0x1d07990: create:
>>>> how=(nil) callback=(nil) poller=0x1d079f0
>>>> libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk
>>>> vdev=hdb spec.backend=phy
>>>> libxl: error: libxl_device.c:243:libxl__device_disk_set_backend: Disk
>>>> vdev=hdb failed to stat: raw:/mnt/vm/iso/QUANTAL.iso: No such file or
>>>> directory
>>> It looks like it is trying to stat "raw:/mnt/vm/iso/QUANTAL.iso" instead
>>> of "/mnt/vm/iso/QUANTAL.iso".  The format parsing must be wrong.
>>>
>>>
>>>> libxl: debug: libxl_event.c:1482:libxl__ao_abort: ao 0x1d07990: abort
>>>> libxl: debug: libxl_event.c:1472:libxl__ao__destroy: ao 0x1d07990: destroy
>>>> xc: debug: hypercall buffer: total allocations:4 total releases:4
>>>> xc: debug: hypercall buffer: current allocations:0 maximum allocations:2
>>>> xc: debug: hypercall buffer: cache current size:2
>>>> xc: debug: hypercall buffer: cache hits:1 misses:2 toobig:1
>>>>
>>>> Seem there is parsing error about backend and device/iso path, for now I
>>>> not found solution for fix it on code.
>> I've added -nodefaults option to qemu upstream to remove empty floppy
>> and cdrom with success. Please could this be added by default on libxl
>> on qemu upstream starting?
>>
>> About cd-eject cd-insert parsing bug can you solve please?
>>
> Just sent a patch upstream to fix the issue.
>
> Frediano
>
Thanks, is that one?
http://lists.xen.org/archives/html/xen-devel/2013-03/msg00806.html

Tried but not solve the problem :(

xl cd-eject W7 hdb
libxl: error: libxl_device.c:269:libxl__device_disk_set_backend: no 
suitable backend for disk hdb

xl -vvv cd-insert W7 hdb raw:/mnt/vm/iso/XPSP3PRO.iso
libxl: debug: libxl.c:2389:libxl_cdrom_insert: ao 0x22709a0: create: 
how=(nil) callback=(nil) poller=0x2270a00
libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk 
vdev=hdb spec.backend=phy
libxl: debug: libxl_device.c:175:disk_try_backend: Disk vdev=hdb, 
backend phy unsuitable as phys path not a block device
libxl: error: libxl_device.c:269:libxl__device_disk_set_backend: no 
suitable backend for disk hdb
libxl: debug: libxl_event.c:1551:libxl__ao_abort: ao 0x22709a0: abort
libxl: debug: libxl_event.c:1541:libxl__ao__destroy: ao 0x22709a0: destroy
xc: debug: hypercall buffer: total allocations:4 total releases:4
xc: debug: hypercall buffer: current allocations:0 maximum allocations:2
xc: debug: hypercall buffer: cache current size:2
xc: debug: hypercall buffer: cache hits:1 misses:2 toobig:1

Is there a way to reply on posts where I'm not in cc?