RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 593541 - werror and rerror is no supported when using -drive ... -device... options boot guests
Summary: werror and rerror is no supported when using -drive ... -device... options...
Keywords:
Status: CLOSED DUPLICATE of bug 565609
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.0
Hardware: All
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-19 05:05 UTC by juzhang
Modified: 2010-05-19 07:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-19 07:14:23 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description juzhang 2010-05-19 05:05:53 UTC 
Description of problem:
when using "-drive file=/root/zhangjunyi/rhel6_64_ide.qcow2,if=none,boot=on,cache=off,format=qcow2,id=test,werror=stop,rerror=stop -device ide-drive,drive=test" in stead of "-drive file=/root/zhangjunyi/rhel6_64_ide.qcow2,if=ide,boot=on,cache=off,werror=stop,rerror=stop,format=qcow2" lead to qemu-kvm aborted with the error "werror is no supported by this format".

Version-Release number of selected component (if applicable):
qemu-kvm-0.12.1.2-2.53.el6
host kernel:2.6.32-25.el6.x86_64

How reproducible:


Steps to Reproduce:
1.boot guest
/usr/libexec/qemu-kvm  -no-hpet -usbdevice tablet -rtc-td-hack -m 2G -smp 2 -drive file=/root/zhangjunyi/rhel6_64_ide.qcow2,if=none,boot=on,cache=off,format=qcow2,id=test,werror=stop,rerror=stop -device ide-drive,drive=test -net nic,vlan=0,macaddr=22:11:22:45:66:97,model=virtio -net tap,vlan=0,script=/etc/qemu-ifup -uuid `uuidgen` -cpu qemu64,+sse2 -device virtio-balloon-pci -boot order=cn,menu=on -M rhel6.0.0 -monitor stdio -vnc :11


Actual results:
qemu-kvm was aborted with the error "werror is no supported by this format"

Expected results:
guest should be boot successful and  werror/rerror should be supported.

Additional info:
when using the following command boot guest,we can boot guest successfully and werror/rerror is supported. 

/usr/libexec/qemu-kvm  -no-hpet -usbdevice tablet -rtc-td-hack -m 2G -smp 2 -drive file=/root/zhangjunyi/rhel6_64_ide.qcow2,if=ide,boot=on,cache=off,werror=stop,rerror=stop -net nic,vlan=0,macaddr=22:11:22:45:66:97,model=virtio -net tap,vlan=0,script=/etc/qemu-ifup -uuid `uuidgen` -cpu qemu64,+sse2 -device virtio-balloon-pci -boot order=cn,menu=on -M rhel6.0.0 -monitor stdio -vnc :11
Comment 2 juzhang 2010-05-19 07:14:23 UTC 
duplicate bz565609,close this issue,I will fellow up bz565609.

*** This bug has been marked as a duplicate of bug 565609 ***
Note You need to log in before you can comment on or make changes to this bug.