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:
In kdump (kexec-tools) we are introducing better features for device identification so that we reduce the probably of dumping on wrong device in
second kernel which can possibly happen due to device renaming issues. (see bz 682244).
Kexec-tools will use scsi_id in host and save the unique id of device. Will need similar mechanism for virtio blk devices in guest. Though it is not
clear whether device renumbering will happen for virtio blk devices or not
but having a common mechanism does not hurt.
There is a upstream patch to report serial id of block device and there
is an associated fix. (Thanks to mike snitzer for the background). We need
to backport those fixes.
commit a5eb9e4ff18a33e43557d44b205f953b0c1efade
Author: Ryan Harper <ryanh.com>
Date: Wed Jun 23 22:19:57 2010 -0500
virtio_blk: Add 'serial' attribute to virtio-blk devices (v2)
commit e4c4776dea9fd0295ebb3b215599d52938d6d7a3
Author: Mike Snitzer <snitzer>
Date: Sat Oct 9 12:12:13 2010 +1030
virtio-blk: fix request leak.
Must drop reference taken by blk_make_request().
There seems to be a qemu patch also which makes sure a serial id is generated
for the disk. Shall have to make sure that 6.2 qemu has that patch.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
looks like following is upstream qemu-kvm commit to make this work in guest.
commit 2930b313dd602d67a568815b0b031b824916cec9
Author: john cooper <john.cooper>
Date: Fri Jul 2 13:44:25 2010 -0400
Add virtio disk identification support
This patch adds the final missing bits for support of
passing a serial/id string to a virtio-blk guest driver.
The guest-side component already exists in the virtio
driver, and has recently been reworked by Ryan to export
a /sys interface for retrieval of the id from guest userland.
Signed-off-by: john cooper <john.cooper>
Signed-off-by: Kevin Wolf <kwolf>
Opened a qemu-kvm bz 688604 to track qemu-kvm changes required to make this work.
Comment 4RHEL Program Management
2011-04-04 02:35:28 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.