Hi, > Hmm, so it occurrs to me that this is really about detecting what > BIOS capabilities QEMU is able to support. IMHO this isn't a property of qemu, but a property of the firmware. Thats why I think the firmware packages should include some config file with the meta data. > We have standardized on > interogating QEMU via QMP for this purpose. So rather than libvirt > having to know about paths, or config files, I wonder if QEMU should > own this knowledge and then expose the information via QMP. We could have qemu parse the firmware config files and export this via qmp, but I fail to see the benefits this extra indirection brings us. cheers, Gerd -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list