From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:34721)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <peter.maydell@linaro.org>) id 1bKTEF-0002N2-Bg
	for qemu-devel@nongnu.org; Tue, 05 Jul 2016 12:29:44 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <peter.maydell@linaro.org>) id 1bKTED-0007yI-6J
	for qemu-devel@nongnu.org; Tue, 05 Jul 2016 12:29:42 -0400
Received: from mail-vk0-x232.google.com ([2607:f8b0:400c:c05::232]:34786)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <peter.maydell@linaro.org>) id 1bKTEC-0007xs-M1
	for qemu-devel@nongnu.org; Tue, 05 Jul 2016 12:29:41 -0400
Received: by mail-vk0-x232.google.com with SMTP id c2so271554379vkg.1
	for <qemu-devel@nongnu.org>; Tue, 05 Jul 2016 09:29:40 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <20160705152058.23593.92860.malone@gac.canonical.com>
References: <20160620032122.2878.51451.malonedeb@chaenomeles.canonical.com>
	<20160705152058.23593.92860.malone@gac.canonical.com>
From: Peter Maydell <peter.maydell@linaro.org>
Date: Tue, 5 Jul 2016 17:29:19 +0100
Message-ID: <CAFEAcA_ms5ea594OYE90wKgPd=RgA2WcwD-6osP_T7rCfoN1rw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [Qemu-devel] [Bug 1594239] Re: After adding more scsi disks for
 Aarch64 virtual machine, start the VM and got Qemu Error
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel/>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Bug 1594239 <1594239@bugs.launchpad.net>
Cc: QEMU Developers <qemu-devel@nongnu.org>

On 5 July 2016 at 16:20, Tom Hanson <thomas.hanson@linaro.org> wrote:
> So, in the original minimal command line above (#3) is the transport/bus
> missing?  Or is mmio implied? Or?

The virt board creates a collection of virtio-mmio transports,
so if you create just a backend on the command line (via
"-device virtio-scsi-device") it will be plugged into a
virtio-bus on a virtio-mmio transport.

You almost certainly didn't want to do this -- virtio-mmio
is only there for legacy reasons [it predates pci support
in the 'virt' board and the device-tree-driven kernel and
for a time it was the only way to do virtio].

You want to use virtio-pci, which is more flexible and has more
features (so either use -device virtio-scsi-pci, or use -device
virtio-scsi-device with -device virtio-pci and suitable id/bus
options to explicitly wire them together).

thanks
-- PMM