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:
Virtio-blk devices does not have ID_SERIAL and no way to uniquely identify virtual devices under guest OS. I tried to add <serial>SERIAL_ID</serial>
to existing virtio-blk devices using virsh command. I tried this command
on active and inactive guest but it is failing with different errors.
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
1. setup a guest using virtio-blk disk, without giving a serial id to
the disk, this is the default situation.
2. In guest, run `udevadm info /dev/vda | grep ID_SERIAL`, it returns empty.
3. Create an XML file to update a specific device. To add a line for the
source device
<disk type='file' device='disk'>
<driver name='qemu' type='raw'/>
<source file='/var/lib/libvirt/images/mydisk.img'/>
<target dev='vdb' bus='virtio'/>
<alias name='virtio-disk1'/>
<serial>1234565453</serial>
<address type='pci' domain='0x0000' bus='0x00'
slot='0x07' function='0x0'/>
</disk>
4. add serialID by updating the device with the help of below command:
$ virsh update-device <GuestName> guest-device.xml
Actual results:
1. Step2 o/p is null.
2. Step4 o/p is as below.
###
error: Failed to update device from t.xml
error: unsupported configuration: disk bus 'virtio' cannot be updated.
###
Expected results:
All virtio-blk devices should have ID_SERIAL.
Additional info:
Hi all,
Qemu-kvm did not support serial property for virtio_blk device before qemu-kvm-0.12.1.2-2.350.el6, you could check it by '/usr/libexec/qemu-kvm -device virtio-blk-pci,?'.
But it support later than qemu-kvm-0.12.1.2-2.350.el6. BTW, there are two ways to specify the serial number for virtio_blk device, e.g: -drive serial=xxxxx,.... and ....-device virtio-blk-pci serial=xxxxx.
note: the serial ws limited to 20 charachters.
and we can check serial number in guest.
- Linux guest.
# cat /sys/block/vdX/serial
- Windows guest.
] hddsn.exe YYY ----> YYY is the disk you want to check.
Best Regards.
sluo
The feature was introduced by 0458d1ca16af0a6903e3409634bcd3cb5d445ca6, necessary for Bug 877836 (VERIFIED) and backported by Stefan. It'll be part of RHEL6.4.
Reassigning, marking it TestOnly and status:ON_QA.
Hi all,
Base on comment #2 and comment #3, disk serial numbers are supported later than qemu-kvm-0.12.1.2-2.350.el6, it'll be part of RHEL6.4, and i also tried latest qemu-kvm-0.12.1.2-2.352.el6, it works well. Close this issue as duplicated to bug 877836, free to correct me if any mistake.
Best Regards.
sluo
*** This bug has been marked as a duplicate of bug 877836 ***
Description of problem: Virtio-blk devices does not have ID_SERIAL and no way to uniquely identify virtual devices under guest OS. I tried to add <serial>SERIAL_ID</serial> to existing virtio-blk devices using virsh command. I tried this command on active and inactive guest but it is failing with different errors. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. setup a guest using virtio-blk disk, without giving a serial id to the disk, this is the default situation. 2. In guest, run `udevadm info /dev/vda | grep ID_SERIAL`, it returns empty. 3. Create an XML file to update a specific device. To add a line for the source device <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/var/lib/libvirt/images/mydisk.img'/> <target dev='vdb' bus='virtio'/> <alias name='virtio-disk1'/> <serial>1234565453</serial> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </disk> 4. add serialID by updating the device with the help of below command: $ virsh update-device <GuestName> guest-device.xml Actual results: 1. Step2 o/p is null. 2. Step4 o/p is as below. ### error: Failed to update device from t.xml error: unsupported configuration: disk bus 'virtio' cannot be updated. ### Expected results: All virtio-blk devices should have ID_SERIAL. Additional info: