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:
as subject.
Version-Release number of selected component (if applicable):
host info:
# uname -r && rpm -q qemu-kvm
2.6.32-424.el6.x86_64
qemu-kvm-0.12.1.2-2.414.el6.x86_64
guest info:
2.6.32-424.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1.check the qemu-kvm man help for ide-drive.
# /usr/libexec/qemu-kvm -device ide-drive,?
ide-drive.unit=uint32
ide-drive.drive=drive
ide-drive.logical_block_size=blocksize
ide-drive.physical_block_size=blocksize
ide-drive.min_io_size=uint16
ide-drive.opt_io_size=uint32
ide-drive.bootindex=int32
ide-drive.discard_granularity=uint32
ide-drive.ver=string
ide-drive.wwn=hex64
2.boot guest with serial property for ide-drive device.
e.g:...-drive file=/home/my-data-disk.raw,if=none,id=drive-data-disk,format=raw,aio=native -device ide-drive,drive=drive-data-disk,id=data-disk,serial=sluo-disk
qemu-kvm: -device ide-drive,drive=drive-data-disk,id=data-disk,serial=sluo-disk: Property 'ide-drive.serial' not found
3.boot guest with serial property for ide-drive drive.
e.g:...-drive file=/home/my-data-disk.raw,if=none,id=drive-data-disk,format=raw,aio=native,serial=sluo-disk -device ide-drive,drive=drive-data-disk,id=data-disk
# scsi_id --whitelist /dev/sda
1ATA QEMU HARDDISK sluo-disk
guest ]# scsi_id --whitelist /dev/sdb
Actual results:
after step 2, fail to boot guest with serial property for ide-drive device.
after step 3, it work well with serial property for ide-drive drive.
Expected results:
Add serial property supported for IDE device.
# /usr/libexec/qemu-kvm -device ide-drive,?
...
ide-drive.wwn=hex64
ide-drive.serial=string
...
Additional info:
(In reply to Paolo Bonzini from comment #3)
> Libvirt is able anyway to specify a serial number for IDE devices, so there
> is no benefit from adding this property.
You are correct, but we have such case to cover it, all the ide/virtio-blk/virtio-scsi has two methods to specify the serial number for its drive or device, and rhel7 has no such issue.
I do suggest that we'd better to fix it work in rhel6.6, or we need to make a note to hight it in our test case/plan. Any idea about it ?
Best Regards,
sluo