xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Fabio Fantoni <fabio.fantoni@heliman.it>
To: xen-devel <xen-devel@lists.xensource.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Ian Campbell <Ian.Campbell@citrix.com>
Subject: Qemu upstream bugs with xen
Date: Fri, 18 Jan 2013 10:47:17 +0100	[thread overview]
Message-ID: <50F91A25.5080408@heliman.it> (raw)

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?

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
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
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.

3) There is still big problem of network not working after restore on 
windows domU, but for now I not found exactly cause.

             reply	other threads:[~2013-01-18  9:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-18  9:47 Fabio Fantoni [this message]
2013-01-18 13:00 ` Qemu upstream bugs with xen 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
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=50F91A25.5080408@heliman.it \
    --to=fabio.fantoni@heliman.it \
    --cc=Ian.Campbell@citrix.com \
    --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).