As far as I can tell, device-list-properties can do nothing you can't do with qom-list-properties. Both take a QOM type name. device-list-properties rejects types that aren't concrete subtypes of "device". device-list-properties filters out properties named "type", "realized", "hotpluggable", "hotplugged", and "parent_bus". These are precisely the properties every device inherits from "device". Why is that useful?
On 11/19/26 10:17, Markus Armbruster wrote:
As far as I can tell, device-list-properties can do nothing you can't do with qom-list-properties.
Both take a QOM type name.
device-list-properties rejects types that aren't concrete subtypes of "device".
device-list-properties filters out properties named "type", "realized", "hotpluggable", "hotplugged", and "parent_bus". These are precisely the properties every device inherits from "device".
Why is that useful?
I think it's only by inertia (from libvirt's POV). I mean, device-list-properties was introduced to libvirt in 2012 (v1.0.0-rc1~216) and qom-list-properties in 2018 (v4.4.0-rc1~209). Are you looking at obsoleting the former? If so, libvirt should adapt. Michal
participants (2)
-
Markus Armbruster -
Michal Prívozník