Bug 2135200 - RFE: support to get the serial of virtio disks
Summary: RFE: support to get the serial of virtio disks
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: lshw
Version: 9.2
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: ltao
QA Contact: Jeff Bastian
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-10-17 03:04 UTC by Han Han
Modified: 2023-08-14 12:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-14 12:10:39 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-136630 0 None None None 2022-10-17 03:06:42 UTC

Description Han Han 2022-10-17 03:04:28 UTC
Description of problem:
as subject

Version-Release number of selected component (if applicable):
lshw-B.02.19.2-7.el9.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Start an VM with the serial of a virtio disk:
VM xml
...
<disk type="file" device="disk">
  <driver name="qemu" type="raw" ats="on" packed="on"/>
  <source file="/var/lib/libvirt/images/1" index="1"/>
  <backingStore/>
  <target dev="vda" bus="virtio"/>
  <serial>test</serial>
  <alias name="virtio-disk0"/>
  <address type="pci" domain="0x0000" bus="0x00" slot="0x07" function="0x0"/>
</disk>
...

2. Check the serial in VM by lsblk:
[root@localhost lshw]# lsblk /dev/vda -o name,serial
NAME          SERIAL
vda           test
├─vda1        
└─vda2        
  ├─rhel-root 
  └─rhel-swap

3. Get the serial by lshw:
# lshw|grep test

Nothing is got by grep

Actual results:
As above

Expected results:
Expect to get the virtio disk serial

Additional info:
Reproduced at B.02.18-214-g42fef56 as well

Comment 2 ltao 2022-10-27 10:13:51 UTC
patch posted upstream:

https://github.com/lyonel/lshw/pull/90

Comment 3 ltao 2023-08-14 12:10:39 UTC
The upstream doesn't response to the patch for a long time. Since the bug is not a serious one. So I will close the bug as won't fix. Feel free to reopen it if you think the bug should be fixed. Thanks!


Note You need to log in before you can comment on or make changes to this bug.