Hide Forgot
Description of problem: boot guest with a VPC format disk which did not specify read-only, qemu will quit with a "'vpc' invalid format" prompt, I suggest that QEMU should give a more friendly prompt for users, like: VPC should use a read-only drive. Version-Release number of selected component (if applicable): host info: 2.6.32-419.el6.x86_64 qemu-kvm-0.12.1.2-2.402.el6.x86_64 guest info: 2.6.32-419.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1.create a vpc image via qemu-img. # qemu-img info sluo-data-disk.vpc image: sluo-data-disk.vpc file format: vpc virtual size: 5.0G (5368946688 bytes) disk size: 1.1G 2.boot guest with this vpc image as a data disk which did not specify read-only for it. e.g:...-drive file=/mnt/sluo-data-disk.vpc,if=none,id=drive-data-disk,format=vpc,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,bus=pci.0,addr=0x7,drive=drive-data-disk,id=data-disk qemu-kvm: -drive file=/mnt/sluo-data-disk.vpc,if=none,id=drive-data-disk,format=vpc,cache=none,werror=stop,rerror=stop: 'vpc' invalid format /etc/qemu-ifdown: could not launch network script Actual results: after step 2, qemu will quit with a "'vpc' invalid format" prompt. Expected results: I suggest that QEMU should give a more friendly prompt for users, like: VPC should use a read-only drive(just like bug 999788). Additional info:
Verify this issue on qemu-kvm-rhev-0.12.1.2-2.431.el6.x86_64. host info: # uname -r && rpm -q qemu-kvm-rhev 2.6.32-493.el6.x86_64 qemu-kvm-rhev-0.12.1.2-2.431.el6.x86_64 e.g.:...-drive file=/home/my-data-disk.vpc,if=none,format=vpc,id=drive-data-disk,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,bus=pci.0,addr=0x7,drive=drive-data-disk,id=data-disk qemu-kvm: -drive file=/home/my-data-disk.vpc,if=none,format=vpc,id=drive-data-disk,cache=none,werror=stop,rerror=stop: 'vpc' can be only used as read-only device. Best Regards, sluo
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1490.html