On Thu, Jul 4, 2013 at 9:07 AM, chandrashekar shastri <email address hidden> wrote: > Public bug reported: > > qcow2 [virtio-scsi] devices when mapped to the guest shows as 0MB > irrespective of the volume size.
qemu-system-x86_64 -enable-kvm -m 1024 -cpu host,+x2apic \ -device virtio-scsi-pci,id=virtio-scsi0 \ -drive if=none,cache=none,file=test2.qcow2,format=qcow2,id=drive0 \ -device scsi-hd,drive=drive0 \ -cdrom rhel64_live.iso
Works fine in qemu.git/master with a RHEL6.4 guest.
What happens when you run "blockdev --getsize64 /dev/sdb" in your guest?
Please also post the output of "qemu-img info /home/images/virtio-scsi11.img" on the host.
Stefan
On Thu, Jul 4, 2013 at 9:07 AM, chandrashekar shastri
<email address hidden> wrote:
> Public bug reported:
>
> qcow2 [virtio-scsi] devices when mapped to the guest shows as 0MB
> irrespective of the volume size.
qemu-system-x86_64 -enable-kvm -m 1024 -cpu host,+x2apic \ scsi-pci, id=virtio- scsi0 \ cache=none, file=test2. qcow2,format= qcow2,id= drive0 \ drive=drive0 \
-device virtio-
-drive if=none,
-device scsi-hd,
-cdrom rhel64_live.iso
Works fine in qemu.git/master with a RHEL6.4 guest.
What happens when you run "blockdev --getsize64 /dev/sdb" in your guest?
Please also post the output of "qemu-img info virtio- scsi11. img" on the host.
/home/images/
Stefan