From: Keith Busch <keith.busch@intel.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Bug 1576347 <1576347@bugs.launchpad.net>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1576347] [NEW] Only one NVMe device is usable in Windows (10) guest
Date: Wed, 4 May 2016 18:42:00 -0400 [thread overview]
Message-ID: <20160504224200.GB2108@localhost.localdomain> (raw)
In-Reply-To: <20160429091039.GC20753@stefanha-x1.localdomain>
> > C:\Windows\system32>sg_vpd -p sn PD1
> > Unit serial number VPD page:
> > Unit serial number: 0000_0000_0000_0000."
I checked your serial number against the SNT refernce on nvmexpress.org and
it's definitely the wrong translation, so that has to be a guest OS driver bug
(Linux has the right translation if interested, but it's use is deprecated).
I pinged some Windows comrades to see if a potential serial conflict prevents
both disks from surfacing.
I'm surprised to see this bad translation as I know of folks successfully
testing multiple nvme drives in various versions of Windows with both the OFA
and Microsoft drivers. An emulated NVMe is no different than real h/w for
namespace identification from the host's perspective.
next prev parent reply other threads:[~2016-05-04 22:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 17:44 [Qemu-devel] [Bug 1576347] [NEW] Only one NVMe device is usable in Windows (10) guest Tom Yan
2016-04-28 17:45 ` [Qemu-devel] [Bug 1576347] " Tom Yan
2016-04-28 17:49 ` Tom Yan
2016-04-28 17:49 ` Tom Yan
2016-04-29 2:32 ` Tom Yan
2016-04-29 3:08 ` Tom Yan
2016-04-29 3:29 ` Tom Yan
2016-04-29 9:10 ` [Qemu-devel] [Bug 1576347] [NEW] " Stefan Hajnoczi
2016-05-04 22:20 ` Keith Busch
2016-05-04 22:42 ` Keith Busch [this message]
2016-12-12 9:26 ` [Qemu-devel] [Bug 1576347] " Tom Yan
2017-08-16 21:18 ` Sergey Blagodurov
2018-02-01 8:53 ` Marshall Porter
2020-11-19 20:54 ` Thomas Huth
2021-01-19 4:17 ` Launchpad Bug Tracker
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=20160504224200.GB2108@localhost.localdomain \
--to=keith.busch@intel.com \
--cc=1576347@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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).