I was taking a look to nova's source code to determine what would be a good approach to fix this issue, so far what I've found is:
- Nova always add `<acpi />` when the instance is qemu or kvm[0]
- At the moment the <features></features> tree is not being parsed when reading the capabilities supported by the host[1]
So a fix would involve creating a new class named "LibvirtConfigCapsFeatures" that implements a `parse_dom()` method to read, in this first iteration, the acpi node.
I was taking a look to nova's source code to determine what would be a good approach to fix this issue, so far what I've found is:
- Nova always add `<acpi />` when the instance is qemu or kvm[0] </features> tree is not being parsed when reading the capabilities supported by the host[1]
- At the moment the <features>
So a fix would involve creating a new class named "LibvirtConfigC apsFeatures" that implements a `parse_dom()` method to read, in this first iteration, the acpi node.
[0] https:/ /github. com/openstack/ nova/blob/ cd5b7e806855fa3 7461bc2da865435 b16408fbd3/ nova/virt/ libvirt/ driver. py#L6203 /github. com/openstack/ nova/blob/ cd5b7e806855fa3 7461bc2da865435 b16408fbd3/ nova/virt/ libvirt/ config. py#L120C1- L131C1
[1] https:/