Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
we support ide disk in 4 slot namely ,
bus=ide.0,unit=0
bus=ide.0,unit=1
bus=ide.1,unit=0
bus=ide.1,unit=1
Version-Release number of selected component (if applicable):
# uname -r ; rpm -q qemu-kvm
2.6.32-228.el6.x86_64
qemu-kvm-0.12.1.2-2.222.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1.install win2k3_bit guest with use default ide and unit
eg :-drive id=ide-0-0-0，XX \
-device ide-drive,,drive=drive-ide0-0-0,id=ide0-0-0
2.start this guest with bus=ide.0
-drive id=ide-0-0-0，XX \
-device ide-drive,*bus=ide.0*,unit=0,drive=drive-ide0-0-0,id=ide0-0-0
3.start this guest with bus=ide.0
-drive id=ide-0-0-1，XX \
-device ide-drive,*bus=ide.0*,unit=1,drive=drive-ide0-0-1,id=ide0-0-1
4 start this guest with bus=ide.1
-drive id=ide-0-1-0，XX \
-device ide-drive,*bus=ide.1*,unit=0,drive=drive-ide0-1-0,id=ide0-1-0
3.start this guest with
-drive id=ide-0-1-1，XX \
-device ide-drive,*bus=ide.1*,unit=1,drive=drive-ide0-1-1,id=ide0-1-1
Actual results:
----------------------------------------------------------------------
bus unit testing result
ide.0 0 fail to boot
ide.0 1 fail to boot
ide.1 0 boot successfully
ide.1 1 boot successfully
Expected results:
guest should boo successfully All the conditions above .
Additional info:
Add bootindex will not hit this problem
(In reply to comment #2)
> Doesn't it clashes with the cdrom? Please provide full description of this
For this bug I don't think it is related with cdrom ,every time I use (qemu)info block to check the the block info , no default cdrom device showed
I also tried start image which bus=ide.0 and append a -cdrom XXX.iso ,Guest still could not start ,it hang at "Booting from Hard Disk"
You should never ever even think about trying to move HDD between devices (or changing bootindex of HDD) and then complain about it not booting. It is not supposed to work. If it works this is because you got lucky this time. I am not sure what are you trying to test but you surely do it wrong.
Description of problem: we support ide disk in 4 slot namely , bus=ide.0,unit=0 bus=ide.0,unit=1 bus=ide.1,unit=0 bus=ide.1,unit=1 Version-Release number of selected component (if applicable): # uname -r ; rpm -q qemu-kvm 2.6.32-228.el6.x86_64 qemu-kvm-0.12.1.2-2.222.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1.install win2k3_bit guest with use default ide and unit eg :-drive id=ide-0-0-0，XX \ -device ide-drive,,drive=drive-ide0-0-0,id=ide0-0-0 2.start this guest with bus=ide.0 -drive id=ide-0-0-0，XX \ -device ide-drive,*bus=ide.0*,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 3.start this guest with bus=ide.0 -drive id=ide-0-0-1，XX \ -device ide-drive,*bus=ide.0*,unit=1,drive=drive-ide0-0-1,id=ide0-0-1 4 start this guest with bus=ide.1 -drive id=ide-0-1-0，XX \ -device ide-drive,*bus=ide.1*,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 3.start this guest with -drive id=ide-0-1-1，XX \ -device ide-drive,*bus=ide.1*,unit=1,drive=drive-ide0-1-1,id=ide0-1-1 Actual results: ---------------------------------------------------------------------- bus unit testing result ide.0 0 fail to boot ide.0 1 fail to boot ide.1 0 boot successfully ide.1 1 boot successfully Expected results: guest should boo successfully All the conditions above . Additional info: Add bootindex will not hit this problem