aboutsummaryrefslogtreecommitdiff
path: root/roms
diff options
context:
space:
mode:
authorMarkus Armbruster <armbru@redhat.com>2011-12-21 11:37:57 +0100
committerStefan Hajnoczi <stefanha@linux.vnet.ibm.com>2012-01-06 15:07:00 +0000
commit6a84cb1f2822e494839b93dd8c7f7f8fa6c261a9 (patch)
tree4cac89f6dfa794568f2d30abedb9e78d8d029da9 /roms
parentbe62a2ebab29eef7dc66c112d60271890ebbbee2 (diff)
downloadqemu-6a84cb1f2822e494839b93dd8c7f7f8fa6c261a9.zip
qemu-6a84cb1f2822e494839b93dd8c7f7f8fa6c261a9.tar.gz
qemu-6a84cb1f2822e494839b93dd8c7f7f8fa6c261a9.tar.bz2
scsi virtio-blk usb-msd: Clean up device init error messages
Replace error_report("DEVICE-NAME: MESSAGE"); by just error_report("MESSAGE"); in block device init functions. DEVICE-NAME is bogus in some cases: it's "scsi-disk" for device scsi-hd and scsi-cd, "virtio-blk-pci" for virtio-blk-s390, and "usb-msd" for usb-storage. There is no real need to put a device name in the message, because error_report() points to the offending command line option already: $ qemu-system-x86_64 --nodefaults --enable-kvm -vnc :0 -S -monitor stdio -usb -device virtio-blk-pci upstream-qemu: -device virtio-blk-pci: virtio-blk-pci: drive property not set upstream-qemu: -device virtio-blk-pci: Device 'virtio-blk-pci' could not be initialized And for a monitor command, it's obvious anyway: $ qemu-system-x86_64 --nodefaults --enable-kvm -vnc :0 -S -monitor stdio -usb (qemu) device_add virtio-blk-pci virtio-blk-pci: drive property not set Device 'virtio-blk-pci' could not be initialized Reported-by: Amit Shah <amit.shah@redhat.com> Signed-off-by: Markus Armbruster <armbru@redhat.com> Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Diffstat (limited to 'roms')
0 files changed, 0 insertions, 0 deletions