From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:46356)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rjones@redhat.com>) id 1VHhod-0001ms-4Q
	for qemu-devel@nongnu.org; Thu, 05 Sep 2013 18:14:19 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <rjones@redhat.com>) id 1VHhoY-0007uW-88
	for qemu-devel@nongnu.org; Thu, 05 Sep 2013 18:14:15 -0400
Received: from mx1.redhat.com ([209.132.183.28]:61833)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rjones@redhat.com>) id 1VHhoY-0007uR-0a
	for qemu-devel@nongnu.org; Thu, 05 Sep 2013 18:14:10 -0400
Date: Thu, 5 Sep 2013 23:14:03 +0100
From: "Richard W.M. Jones" <rjones@redhat.com>
Message-ID: <20130905221403.GC28430@redhat.com>
References: <20130905214149.GB28430@redhat.com>
	<CAFEAcA9GPr4V=e=KGkrAap97efk839g+yx+R9wsjOzp3ckV69Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAFEAcA9GPr4V=e=KGkrAap97efk839g+yx+R9wsjOzp3ckV69Q@mail.gmail.com>
Subject: Re: [Qemu-devel] ARM virtio-scsi - disks never show up
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: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>

On Thu, Sep 05, 2013 at 10:50:02PM +0100, Peter Maydell wrote:
> On 5 September 2013 22:41, Richard W.M. Jones <rjones@redhat.com> wrote:
> > I don't know if there is a more appropriate place to ask about
> > ARM / virtio questions.  If there is please let me know.
> >
> > I'm trying to get qemu to boot an ARM appliance.  Everything works up
> > to the point where the kernel loads virtio drivers.  The disks never
> > show up.  The full qemu command line and kernel messages are attached
> > (this is a libguestfs boot test).
> >
> > virtio-blk-device fails the same way.
> >
> > I have no idea where to go next.  Is there a missing kernel module?
> > Missing kernel config?  Non-upstream patches?
> 
> Can you get any virtio device to work at all?
> 
> Does it work if you compile the virtio drivers and
> the virtio_mmio transport into the kernel instead of
> making them modules? That's the obvious difference
> between what you're doing and the configs I've tested with...

It turns out to be due to missing -dtb (device tree) parameter.

Thanks, Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-p2v converts physical machines to virtual machines.  Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
http://libguestfs.org/virt-v2v