{ "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.
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.
http://gerrit.beaker-project.org/4355
Beaker 21.1 has been released.