From: George Dunlap <George.Dunlap@eu.citrix.com>
To: Jungnam Lee <jungnam.lee@kaist.ac.kr>
Cc: Jan Beulich <JBeulich@suse.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: xl cannot cd-eject an initialy inserted iso in staging-4.2
Date: Tue, 11 Mar 2014 12:26:15 +0000 [thread overview]
Message-ID: <CAFLBxZY70bH+u1--O1HziBK7BEwh_vJaq16eO6SFSSm_hLtEjg@mail.gmail.com> (raw)
In-Reply-To: <531934193fe9_@_imoxion.com>
[-- Attachment #1.1: Type: text/plain, Size: 842 bytes --]
On Fri, Mar 7, 2014 at 2:47 AM, Jungnam Lee <jungnam.lee@kaist.ac.kr> wrote:
> 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.
>
Does the patch from this mail help?
I had tried to flag it as a candidate for backport at the time, but I
failed to CC Jan.
-George
[-- Attachment #1.2: Type: text/html, Size: 1322 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:[~2014-03-11 12:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 2:47 xl cannot cd-eject an initialy inserted iso in staging-4.2 Jungnam Lee
2014-03-11 12:26 ` George Dunlap [this message]
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=CAFLBxZY70bH+u1--O1HziBK7BEwh_vJaq16eO6SFSSm_hLtEjg@mail.gmail.com \
--to=george.dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=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).