From: George Dunlap <dunlapg@umich.edu>
To: Fabio Fantoni <fabio.fantoni@heliman.it>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: Qemu upstream bugs with xen
Date: Mon, 21 Jan 2013 12:16:12 +0000 [thread overview]
Message-ID: <CAFLBxZaV9VbVvMUwp_QWEfvJUA78qtbceKiD-ayES78j5tmivA@mail.gmail.com> (raw)
In-Reply-To: <50F95FE9.2030104@heliman.it>
[-- Attachment #1.1: Type: text/plain, Size: 3130 bytes --]
On Fri, Jan 18, 2013 at 2:44 PM, Fabio Fantoni <fabio.fantoni@heliman.it>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?
I'll put this on the release tracking list.
-George
[-- Attachment #1.2: Type: text/html, Size: 4233 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-01-21 12:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 9:47 Qemu upstream bugs with xen Fabio Fantoni
2013-01-18 13:00 ` Stefano Stabellini
2013-01-18 14:44 ` Fabio Fantoni
2013-01-18 15:51 ` Stefano Stabellini
2013-02-04 13:14 ` Fabio Fantoni
2013-02-04 13:20 ` Ian Campbell
2013-02-04 13:48 ` Fabio Fantoni
2013-02-04 13:56 ` Ian Campbell
2013-01-21 12:16 ` George Dunlap [this message]
2013-01-30 11:28 ` Fabio Fantoni
2013-02-08 16:21 ` Stefano Stabellini
2013-03-11 11:55 ` Frediano Ziglio
2013-03-11 13:32 ` Fabio Fantoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFLBxZaV9VbVvMUwp_QWEfvJUA78qtbceKiD-ayES78j5tmivA@mail.gmail.com \
--to=dunlapg@umich.edu \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=fabio.fantoni@heliman.it \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).