xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Jungnam Lee <jungnam.lee@kaist.ac.kr>
To: George Dunlap <george.dunlap@eu.citrix.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	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: Thu, 13 Mar 2014 16:20:34 +0900	[thread overview]
Message-ID: <1394695234.15705.7.camel@localhost> (raw)
In-Reply-To: <531F222A.8070709@eu.citrix.com>

2014-03-11, 14:48 +0000, George Dunlap:
> On 03/11/2014 02:13 PM, Jan Beulich wrote:
> >>>> On 11.03.14 at 13:26, George Dunlap <George.Dunlap@eu.citrix.com> wrote:
> >> 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.
> >
> > And you really would have needed to Cc IanJ, as he's who takes
> > care of tools side backports.
> 
> Ah, right -- well I did CC IanJ; not in the original message, but when I 
> replied saying "This should probably be backported".
> 
> (I'm not 100% sure it wasn't backported: a quick search through the git 
> history didn't turn up anything, but I may have missed it.)
> 

it seems cherry-picking 0166217103e18368424fbd5ffff01c1ea50d0b17 fixes
this issue. Is this right?

  reply	other threads:[~2014-03-13  7:20 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
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 [this message]
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=1394695234.15705.7.camel@localhost \
    --to=jungnam.lee@kaist.ac.kr \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=george.dunlap@eu.citrix.com \
    --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).