From: "Jungnam Lee" <jungnam.lee@kaist.ac.kr>
To: xen-devel@lists.xen.org
Subject: xl cannot cd-eject an initialy inserted iso in staging-4.2
Date: Fri, 7 Mar 2014 11:47:24 +0900 (KST) [thread overview]
Message-ID: <531934193fe9_@_imoxion.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 865 bytes --]
Hi all.
I created VM with a cdrom device with an iso file, and ejecting works fine in the master branch.
But if I do this with staging-4.2, I got an error below.
libxl: debug: libxl.c:2137:libxl_cdrom_insert: ao 0x1425990: create: how=(nil) callback=(nil) poller=0x14259f0
libxl: debug: libxl_device.c:245:libxl__device_disk_set_backend: Disk vdev=hdc spec.backend=phy
libxl: debug: libxl_device.c:191:disk_try_backend: Disk vdev=hdc, backend phy unsuitable as phys path not a block device
libxl: error: libxl_device.c:285:libxl__device_disk_set_backend: no suitable backend for disk hdc.
cd-insert and cd-eject works fine when it is created with an empty cdrom device, and xl says its backend is qdisk.
But when it is created with an iso inserted cdrom device, it says backend is unknown.
I dont know whether I report this as a bug, so I just mail this.
[-- Attachment #1.2: Type: text/html, Size: 1286 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 reply other threads:[~2014-03-07 2:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 2:47 Jungnam Lee [this message]
2014-03-11 12:26 ` xl cannot cd-eject an initialy inserted iso in staging-4.2 George Dunlap
2014-03-11 13:59 ` Ian Campbell
2014-03-11 14:07 ` George Dunlap
2014-03-11 14:13 ` Jan Beulich
2014-03-11 14:48 ` George Dunlap
2014-03-13 7:20 ` Jungnam Lee
2014-03-13 11:51 ` George Dunlap
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=531934193fe9_@_imoxion.com \
--to=jungnam.lee@kaist.ac.kr \
--cc=xen-devel@lists.xen.org \
/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).