From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54426) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cGN5E-0006I8-4P for qemu-devel@nongnu.org; Mon, 12 Dec 2016 04:39:45 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cGN5B-000299-1B for qemu-devel@nongnu.org; Mon, 12 Dec 2016 04:39:44 -0500 Received: from indium.canonical.com ([91.189.90.7]:45944) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cGN5A-00028d-Sf for qemu-devel@nongnu.org; Mon, 12 Dec 2016 04:39:40 -0500 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.76 #1 (Debian)) id 1cGN58-0006Ss-Em for ; Mon, 12 Dec 2016 09:39:38 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 60AB42E80C3 for ; Mon, 12 Dec 2016 09:39:38 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Mon, 12 Dec 2016 09:26:03 -0000 From: Tom Yan Reply-To: Bug 1576347 <1576347@bugs.launchpad.net> Sender: bounces@canonical.com References: <20160428174421.24544.77308.malonedeb@gac.canonical.com> Message-Id: <20161212092603.12226.55761.malone@wampee.canonical.com> Errors-To: bounces@canonical.com Subject: [Qemu-devel] [Bug 1576347] Re: Only one NVMe device is usable in Windows (10) guest List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org The problem still exists with qemu 2.7.0 and Windows 10 RS1. Btw I just did one more test, that I disable the working nvme controller in Device Manager to see if it makes the non-working one comes alive, but it does not, even if I reboot the virtual machine. For the record, the serial number translation is not fixed in RS1 either. -- = You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1576347 Title: Only one NVMe device is usable in Windows (10) guest Status in QEMU: New Bug description: Full command: qemu-system-x86_64 -enable-kvm -cpu host -smp cores=3D4 -m 4G -net bridge -net nic -full-screen -drive file=3Dovmf_x64.bin,format=3Draw,if=3Dpflash -drive file=3Ddisks/win16_ide.img,format=3Draw,cache=3Dnone,aio=3Dnative -drive file=3Ddisks/one.img,if=3Dnone,format=3Dqcow2,id=3Done -drive file=3Ddisks/two.img,if=3Dnone,format=3Dqcow2,id=3Dtwo -device nvme,drive=3Done,serial=3DE86C3CFC43518D6F -device nvme,drive=3Dtwo,serial=3D2BDAC262CF831698 QEMU version: 2.5.0 Kernel: 4.5.1 (Arch Linux) When there are two NVMe devices specified, only the second one will be usable in Windows. The following error is shown under "Device status" of the failed NVMe controller in Device Manager: "This device cannot start. (Code 10) The I/O device is configured incorrectly or the configuration parameters to the driver are incorrect." The only thing seems suspicious to me is that the nvme emulation in qemu does not have WWN/EUI-64 set for the devices, though I have no idea at all whether that is mandatory: "C:\Windows\system32>sg_vpd -i PD1 Device Identification VPD page: Addressed logical unit: designator type: SCSI name string, code set: UTF-8 SCSI name string: 8086QEMU NVMe Ctrl 00012BDAC262CF831698 C:\Windows\system32>sg_vpd -p sn PD1 Unit serial number VPD page: Unit serial number: 0000_0000_0000_0000." To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1576347/+subscriptions