[Qemu-devel] aarch64: -device virtio-scsi-device, id=scsi: No 'virtio-bus' bus found for device 'virtio-scsi-device'

[Qemu-devel] aarch64: -device virtio-scsi-device, id=scsi: No 'virtio-bus' bus found for device 'virtio-scsi-device'

[Richard W.M. Jones]

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'
Could not access KVM kernel module: No such file or directory
failed to initialize KVM: No such file or directory
Back to tcg accelerator.
qemu-system-aarch64: -device virtio-scsi-device,id=scsi: No 'virtio-bus' bus found for device 'virtio-scsi-device'

qemu: Upstream from git yesterday
kernel: 3.13.0-0.rc7
Hardware: real aarch64(!)

I also tried adding `-device virtio-bus' to the command line, but that
just changes the error message to:

qemu-system-aarch64: -device virtio-bus: 'virtio-bus' is not a valid device model name

Also:

$ ~/d/qemu/aarch64-softmmu/qemu-system-aarch64 -device \? |& grep virtio
name "vhost-scsi", bus virtio-bus
name "virtio-9p-device", bus virtio-bus
name "virtio-9p-pci", bus PCI
name "virtio-blk-device", bus virtio-bus
name "virtio-blk-pci", bus PCI, alias "virtio-blk"
name "virtio-scsi-device", bus virtio-bus
name "virtio-scsi-pci", bus PCI
name "virtio-net-device", bus virtio-bus
name "virtio-net-pci", bus PCI, alias "virtio-net"
name "virtconsole", bus virtio-serial-bus
name "virtio-serial-device", bus virtio-bus
name "virtio-serial-pci", bus PCI, alias "virtio-serial"
name "virtserialport", bus virtio-serial-bus
name "virtio-balloon-device", bus virtio-bus
name "virtio-balloon-pci", bus PCI, alias "virtio-balloon"
name "virtio-rng-device", bus virtio-bus
name "virtio-rng-pci", bus PCI

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top

Re: [Qemu-devel] aarch64: -device virtio-scsi-device, id=scsi: No 'virtio-bus' bus found for device 'virtio-scsi-device'

[Paolo Bonzini]

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")?

Paolo

Re: [Qemu-devel] aarch64: -device virtio-scsi-device, id=scsi: No 'virtio-bus' bus found for device 'virtio-scsi-device'

[Peter Maydell]

On 25 March 2014 13:53, Paolo Bonzini <pbonzini@redhat.com> wrote:
> Probably you're missing "-M" (such as "-M virt")?

Yes, default for qemu-system-aarch64 is integratorcp,
which even stupider than having that be the default
for qemu-system-arm.

For 2.1 when the system emulation stuff actually lands
I think I'll just remove the default and force users
to specify a machine. (In fact it's very tempting to
do that for qemu-system-arm as well since the set of
users who don't specify a machine because they expect
ARM to be like x86 here is much larger than the set of
users who really wanted integratorcp...)

thanks
-- PMM

Re: [Qemu-devel] aarch64: -device virtio-scsi-device, id=scsi: No 'virtio-bus' bus found for device 'virtio-scsi-device'

[Paolo Bonzini]

Il 25/03/2014 15:04, Peter Maydell ha scritto:
> Yes, default for qemu-system-aarch64 is integratorcp,
> which even stupider than having that be the default
> for qemu-system-arm.
>
> For 2.1 when the system emulation stuff actually lands
> I think I'll just remove the default and force users
> to specify a machine. (In fact it's very tempting to
> do that for qemu-system-arm as well since the set of
> users who don't specify a machine because they expect
> ARM to be like x86 here is much larger than the set of
> users who really wanted integratorcp...)

Could "virt" be a sane default for qemu-system-arm?  2.0 might be the 
right time to change it.

Paolo

Re: [Qemu-devel] aarch64: -device virtio-scsi-device, id=scsi: No 'virtio-bus' bus found for device 'virtio-scsi-device'

[Peter Maydell]

On 25 March 2014 14:13, Paolo Bonzini <pbonzini@redhat.com> wrote:
> Il 25/03/2014 15:04, Peter Maydell ha scritto:
>> Yes, default for qemu-system-aarch64 is integratorcp,
>> which even stupider than having that be the default
>> for qemu-system-arm.
>>
>> For 2.1 when the system emulation stuff actually lands
>> I think I'll just remove the default and force users
>> to specify a machine. (In fact it's very tempting to
>> do that for qemu-system-arm as well since the set of
>> users who don't specify a machine because they expect
>> ARM to be like x86 here is much larger than the set of
>> users who really wanted integratorcp...)
>
>
> Could "virt" be a sane default for qemu-system-arm?
>  2.0 might be the right time to change it.

Really I don't think there is a sane default at all for
ARM. Boards are just too different and you must know
which one you want. Anything other than "the user
must always specify" is just too confusing for people
who are expecting something closer to x86 monoculture.

If we want to remove the default for both for 2.0
I'm happy to do that -- it's a oneliner.

thanks
-- PMM

Re: [Qemu-devel] aarch64: -device virtio-scsi-device, id=scsi: No 'virtio-bus' bus found for device 'virtio-scsi-device'

[Paolo Bonzini]

Il 25/03/2014 19:59, Peter Maydell ha scritto:
>> > Could "virt" be a sane default for qemu-system-arm?
>> >  2.0 might be the right time to change it.
> Really I don't think there is a sane default at all for
> ARM. Boards are just too different and you must know
> which one you want. Anything other than "the user
> must always specify" is just too confusing for people
> who are expecting something closer to x86 monoculture.
>
> If we want to remove the default for both for 2.0
> I'm happy to do that -- it's a oneliner.

It's your call as the maintainer.  I certainly wouldn't object to that, 
though (perhaps it's my delusion) I would have hoped that "virt" would 
have been a suitable choice for users coming from x86.

Paolo

Re: [Qemu-devel] aarch64: -device virtio-scsi-device, id=scsi: No 'virtio-bus' bus found for device 'virtio-scsi-device'

[Peter Maydell]

On 26 March 2014 09:51, Paolo Bonzini <pbonzini@redhat.com> wrote:
> It's your call as the maintainer.  I certainly wouldn't object to that,
> though (perhaps it's my delusion) I would have hoped that "virt" would have
> been a suitable choice for users coming from x86.

It's one option, but it's still (for instance) not the right
choice if what you have is a kernel and fs for a
RaspberryPi that you're trying to run on QEMU.

thanks
-- PMM

Re: [Qemu-devel] aarch64: -device virtio-scsi-device, id=scsi: No 'virtio-bus' bus found for device 'virtio-scsi-device'

[Richard W.M. Jones]

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