xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Paul Durrant <Paul.Durrant@citrix.com>
To: Ian Jackson <Ian.Jackson@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	Wei Liu <wei.liu2@citrix.com>
Subject: Re: [PATCH RESEND] tools/libxl: add support for emulated NVMe drives
Date: Wed, 22 Mar 2017 17:16:14 +0000	[thread overview]
Message-ID: <f34bf5d6705e4e00a1f7dd1219fe6ec9@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <22738.44582.349289.852057@mariner.uk.xensource.com>

> -----Original Message-----
> From: Ian Jackson [mailto:ian.jackson@eu.citrix.com]
> Sent: 22 March 2017 17:03
> To: Paul Durrant <Paul.Durrant@citrix.com>
> Cc: xen-devel@lists.xenproject.org; Wei Liu <wei.liu2@citrix.com>
> Subject: RE: [PATCH RESEND] tools/libxl: add support for emulated NVMe
> drives
> 
> Paul Durrant writes ("RE: [PATCH RESEND] tools/libxl: add support for
> emulated NVMe drives"):
> > > From: Ian Jackson [mailto:ian.jackson@eu.citrix.com]
> > > That's not my point.  The purpose of this table is to advise guests
> > > what the conventional in-guest device name ought to be for a certain
> > > vbd.
> >
> > Yes, and xvd<something> is a perfectly fine name for a PV device in pretty
> much every case. It's already the case that emulated IDE disks are exposed to
> guests using xvd* numbering.
> 
> No, I don't think so:
> 
> /libxl/5/device/vbd/5632/params = "aio:/root/68254.test-amd64-amd64-xl-
> qemuu-debianhvm-amd64.debianhvm-em\..."
> (n0)
> 
> 5632 = 22 << 8 | 0 ie "hd, disk 2, partition 0"
> 

This is my VM:

root@brixham:~# xenstore-ls "/libxl/3"
device = ""
 vbd = ""
  51712 = ""
   frontend = "/local/domain/3/device/vbd/51712"
   backend = "/local/domain/0/backend/qdisk/3/51712"
   params = "qcow2:/root/winrs2-pv1.qcow2"
   frontend-id = "3"
   online = "1"
   removable = "0"
   bootable = "1"
   state = "1"
   dev = "xvda"
   type = "qdisk"
   mode = "w"
   device-type = "disk"
   discard-enable = "1"

No problem using xvda... still ends up as IDE primary master.

> Some operating systems (including many recent Linux kernels) present
> all vbds as xvd*.
> 
> > > Presumably these NVME devices should be subject to the same vbd and
> > > unplug approach as scsi and ide disks.
> >
> > Yes, that's what the QEMU patch does.
> 
> So maybe they should reuse the hd* numbering ?
> 

That might be too limiting. The hd* numbering scheme doesn't stretch very far.

> > That means modifications to PV frontends would be needed, which is
> > going to make things more difficult. Most OS find disks by UUID
> > these days anyway so I'm still not sure that just using xvd*
> > numbering would really be a problem.
> 
> In terms of the "nominal disk type" discussed in
> xen-vbd-interface.markdown.7, I don't think these emulated devices,
> which get unplugged, should be have a "nomainl disk type" of "Xen
> virtual disk".
> 

Ok. I'll submit another patch to QEMU to distinguish between IDE/SCSI disks and NVMe disks in the unplug protocol, come up with a new PV numbering schemed and modify the Windows frontend to understand it.

  Paul

> Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-03-22 17:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-22 13:09 [PATCH RESEND] tools/libxl: add support for emulated NVMe drives 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2017-01-13 14:00 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
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

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=f34bf5d6705e4e00a1f7dd1219fe6ec9@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).