Bug 1249462
| Summary: | beaker-system-scan (lshw branch) does not report PCIID for virtio memory balloon device | ||
|---|---|---|---|
| Product: | [Retired] Beaker | Reporter: | Dan Callaghan <dcallagh> |
| Component: | inventory | Assignee: | Dan Callaghan <dcallagh> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | tools-bugs <tools-bugs> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 21 | CC: | dcallagh, dowang, mjia, rjoost |
| Target Milestone: | 21.1 | Keywords: | Patch |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-10-21 03:25:47 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
The class="memory" is coming from the PCI class of the mem balloon device. It seems to depend on the version of the host hypervisor. Testing with a recent qemu version on the host, the mem balloon class is 0x00ff00 which is "other". This is actually more accurate (the balloon is not a piece of memory, it's a thing that *consumes* memory according to instructions from the host) so I guess it has been fixed in qemu at some point. ... And indeed, here is the commit: http://git.qemu.org/?p=qemu.git;a=commitdiff;h=2ba1d381c2f5f5868fe071b45977c2ed459d78f0 I would be tempted to close this bug as WONTFIX on that basis. However I am guessing RHEL6 qemu does not have this fix and so guests hosted on RHEL6 hosts will continue to have this problem. So we probably need a workaround in beaker-system-scan. Beaker 21.1 has been released. |
{ "vendorID": "1af4", "description": "Virtio memory balloon", "subsysVendorID": "1af4", "bus": "pci", "driver": "virtio-pci", "deviceID": "1002", "subsysDeviceID": "0005", "type": "OTHER" } Missing from new beaker-system-scan's output. The problem is that the lshw device has class="memory" which beaker-system-scan explicitly skips in order to avoid reporting DIMMs/banks as devices.