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.
---Problem Description---
Specifying serial number on a virtio-block backed disk (via <serial> tag in XML) does not work.
---uname output---
Linux alaska.linuxperf9025.net 2.6.32-71.el6.x86_64 #1 SMP Wed Sep 1 01:33:01 EDT 2010 x86_64 x86_64
x86_64 GNU/Linux
Machine Type = System Information Manufacturer: IBM Product Name: BladeCenter HS22V
-[7871AC1]- Version: 02
---Steps to Reproduce---
Create RHEL6.0 Guest (on RHEL6.0 host) with virtio-block virtual disk (or alternatively use the
virsh attach-device command to add later) specifying a serial number for the disk via the <serial>
tag.
Once the guest is started one should be able to view the serial number for this virtual disk in
/dev/disk/by-id.
No serial number is being propogated through to /dev/disk/by-id.
[root@localhost ~]# ls /dev/disk/by-id/
dm-name-VolGroup-lv_root
dm-name-VolGroup-lv_swap
dm-uuid-LVM-gKyZKm5h3jr0gwsvKGyNpnJM4a3NlqlEdNV7INjcLs9lVxOAml5ETPkWga2zuWHZ
dm-uuid-LVM-gKyZKm5h3jr0gwsvKGyNpnJM4a3NlqlEtvDt4W1c7ZONUKN4W8U6MWT2qYVjglie
Note: <serial> does work for IDE backed disks,
Note: It doesn't require attach-device. Just hand-editing a shutdown guest XML and restarting would
exhibit this problem as well.
Attachments:
- Guest XML (post creation/start) from virsh dumpxml
- XML used to 'attach' new disk via virsh attach-device. Specifies <serial> number for disk.
- DumpXML of guest after 'virsh attach-device rhel6vm1 att.xml'
Comment 4Don Dutile (Red Hat)
2011-06-07 18:42:43 UTC
I believe this is a dupe of 694553 that was patch-posted by Amit Shah for 6.2 on 5/31/2011.
Added Amit Shah to cc:; asking him to confirm, and if so, close this bz.