From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:33334) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ayFwC-0007gI-1C for qemu-devel@nongnu.org; Thu, 05 May 2016 05:51:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ayFw0-0006Ye-9g for qemu-devel@nongnu.org; Thu, 05 May 2016 05:51:10 -0400 Received: from indium.canonical.com ([91.189.90.7]:38589) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ayFw0-0006Vw-32 for qemu-devel@nongnu.org; Thu, 05 May 2016 05:51:04 -0400 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.76 #1 (Debian)) id 1ayFvp-0001Ze-2X for ; Thu, 05 May 2016 09:50:53 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 3D5A72E80D8 for ; Thu, 5 May 2016 09:50:52 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Thu, 05 May 2016 09:45:10 -0000 From: Tom Yan Reply-To: Bug 1529449 <1529449@bugs.launchpad.net> Sender: bounces@canonical.com References: <20151227070342.25181.45645.malonedeb@soybean.canonical.com> Message-Id: <20160505094510.24128.94220.malone@gac.canonical.com> Errors-To: bounces@canonical.com Subject: [Qemu-devel] [Bug 1529449] Re: serial is required for -device nvme List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org ** Attachment added: "1.png" https://bugs.launchpad.net/qemu/+bug/1529449/+attachment/4656269/+files/= 1.png -- = You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1529449 Title: serial is required for -device nvme Status in QEMU: New Bug description: I am not exactly sure if this is a bug, but I don't see why the option "serial" should be required for -device nvme like the option "drive". Truth is it seem to accept random string as its value anyway, if that's the case, couldn't qemu just generate one for it when it's not specified? To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1529449/+subscriptions