qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Richard W.M. Jones" <rjones@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] aarch64: -device virtio-scsi-device, id=scsi: No 'virtio-bus' bus found for device 'virtio-scsi-device'
Date: Tue, 25 Mar 2014 14:17:40 +0000	[thread overview]
Message-ID: <20140325141740.GB31003@redhat.com> (raw)
In-Reply-To: <53318A4F.7040203@redhat.com>

On Tue, Mar 25, 2014 at 02:53:19PM +0100, Paolo Bonzini wrote:
> Il 25/03/2014 14:30, Richard W.M. Jones ha scritto:
> >Does anyone have any thoughts on what I'm missing / doing wrong here?
> >
> >[00616ms] /home/remote/rjones/d/qemu/aarch64-softmmu/qemu-system-aarch64 \
> >    -global virtio-blk-device.scsi=off \
> >    -nodefconfig \
> >    -enable-fips \
> >    -nodefaults \
> >    -display none \
> >    -machine accel=kvm:tcg \
> >    -m 500 \
> >    -no-reboot \
> >    -rtc driftfix=slew \
> >    -global kvm-pit.lost_tick_policy=discard \
> >    -kernel /discer.farm/home/remote/rjones/d/libguestfs/tmp/.guestfs-11538/appliance.d/kernel \
> >    -initrd /discer.farm/home/remote/rjones/d/libguestfs/tmp/.guestfs-11538/appliance.d/initrd \
> >    -device virtio-scsi-device,id=scsi \
> >    -drive file=/discer.farm/home/remote/rjones/d/libguestfs/tmp/libguestfsueW63b/scratch.1,cache=unsafe,format=raw,id=hd0,if=none \
> >    -device scsi-hd,drive=hd0 \
> >    -drive file=/discer.farm/home/remote/rjones/d/libguestfs/tmp/.guestfs-11538/appliance.d/root,snapshot=on,id=appliance,cache=unsafe,if=none \
> >    -device scsi-hd,drive=appliance \
> >    -device virtio-serial-device \
> >    -serial stdio \
> >    -chardev socket,path=/discer.farm/home/remote/rjones/d/libguestfs/tmp/libguestfsueW63b/guestfsd.sock,id=channel0 \
> >    -device virtserialport,chardev=channel0,name=org.libguestfs.channel.0 \
> >    -append 'panic=1 console=ttyS0 udevtimeout=600 no_timer_check lpj=500000 acpi=off printk.time=1 cgroup_disable=memory root=/dev/sdb selinux=0 guestfs_verbose=1 TERM=screen'
> 
> Probably you're missing "-M" (such as "-M virt")?

Ah, I see.  Using this gets past that error, thanks.

I was suffering some temporary confusion about -M, device trees etc
on aarch64 :-(

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

      parent reply	other threads:[~2014-03-25 14:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-25 13:30 [Qemu-devel] aarch64: -device virtio-scsi-device, id=scsi: No 'virtio-bus' bus found for device 'virtio-scsi-device' Richard W.M. Jones
2014-03-25 13:53 ` Paolo Bonzini
2014-03-25 14:04   ` Peter Maydell
2014-03-25 14:13     ` Paolo Bonzini
2014-03-25 18:59       ` Peter Maydell
2014-03-26  9:51         ` Paolo Bonzini
2014-03-26 10:36           ` Peter Maydell
2014-03-25 14:17   ` Richard W.M. Jones [this message]

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=20140325141740.GB31003@redhat.com \
    --to=rjones@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).