From: Paul Durrant <Paul.Durrant@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Wei Liu <wei.liu2@citrix.com>,
Ian Jackson <Ian.Jackson@citrix.com>
Subject: Re: [PATCH RESEND] tools/libxl: add support for emulated NVMe drives
Date: Wed, 18 Jan 2017 12:15:22 +0000 [thread overview]
Message-ID: <e825a93b3d4b4a8ba41f79e88cac5d17@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <20170118120222.GT5089@citrix.com>
> -----Original Message-----
> From: Wei Liu [mailto:wei.liu2@citrix.com]
> Sent: 18 January 2017 12:02
> To: Paul Durrant <Paul.Durrant@citrix.com>
> Cc: Wei Liu <wei.liu2@citrix.com>; xen-devel@lists.xenproject.org; Ian
> Jackson <Ian.Jackson@citrix.com>
> Subject: Re: [PATCH RESEND] tools/libxl: add support for emulated NVMe
> drives
>
[snip]
> > > >
> > > > - For HVM guests, each whole-disk hd* and and sd* device is made
> > > > - available _both_ via emulated IDE resp. SCSI controller, _and_ as a
> > > > - Xen VBD. The HVM guest is entitled to assume that the IDE or SCSI
> > > > - disks available via the emulated IDE controller target the same
> > > > + For HVM guests, each whole-disk hd*, sd* or nvme* device is made
> > > > + available _both_ via emulated IDE, SCSI controller or NVMe drive
> > > > + respectively _and_ as a Xen VBD. The HVM guest is entitled to
> > > > + assume that the disks available via the emulation target the same
> > >
> > > How do you expect the guest to deal with multipath NVMe devices?
> Maybe
> > > we need to add unplug support for NVMe devices in QEMU?
> >
> > That's true. For convenience, there would need to a QEMU patch for
> unplug to allow displacement of the emulated device with PV. I can
> document this as a shortcoming at the moment, if that's ok?
> >
>
> The unplug functionality, as I understand, is crucial to data integrity.
> Documenting this as shortcoming doesn't seem to be good enough. Do we
> need to wait until QEMU is ready before we can apply this patch?
It will take time to get a patch into QEMU and if you're going to use PV drivers then you have little interest in the emulation model. I think just documenting it would be ok. For safety I guess I could explore the possibility of having libxl not create a PV backend for this vdev type.
Paul
>
> Wei.
>
>
> > Paul
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-01-18 12:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 14:00 [PATCH RESEND] tools/libxl: add support for emulated NVMe drives Paul Durrant
2017-01-18 10:28 ` Wei Liu
2017-01-18 10:51 ` Paul Durrant
2017-01-18 12:02 ` Wei Liu
2017-01-18 12:15 ` Paul Durrant [this message]
2017-01-18 12:20 ` Wei Liu
2017-01-18 15:07 ` Wei Liu
2017-01-19 8:58 ` Paul Durrant
2017-01-19 11:18 ` Wei Liu
-- strict thread matches above, loose matches on Subject: below --
2017-03-22 13:09 Paul Durrant
2017-03-22 14:16 ` Ian Jackson
2017-03-22 14:22 ` Paul Durrant
2017-03-22 15:01 ` Ian Jackson
2017-03-22 15:21 ` Paul Durrant
2017-03-22 16:03 ` Ian Jackson
2017-03-22 16:31 ` Paul Durrant
2017-03-22 16:45 ` Paul Durrant
2017-03-22 17:02 ` Ian Jackson
2017-03-22 17:16 ` Paul Durrant
2017-03-22 17:31 ` Ian Jackson
2017-03-22 17:41 ` Paul Durrant
2017-03-22 17:48 ` Ian Jackson
2017-03-23 8:55 ` Paul Durrant
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=e825a93b3d4b4a8ba41f79e88cac5d17@AMSPEX02CL03.citrite.net \
--to=paul.durrant@citrix.com \
--cc=Ian.Jackson@citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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).