Hi trying to get the status right here. AFAIK these things are changed in libvirt 3.2 to be good - at least for x86, not sure if/how arm followed but since there were major changes we should consider it fixed and re-analyze from there for the development release. So the coming merge of a newer libvirt will fix it for current Ubuntu-dev.
Since it is a "known behavior" on zesty's version I added a task on won't fix as so far - as I understood - we thought to better fix it in Openstack creating the xml's. Furthermore adding a qemu task which will need to be >=2.9 to let the code in libvirt >=3.2 really work correctly. Read [1] for the version references. [1]: https://libvirt.org/formatdomain.html#elementsCPU ** Also affects: libvirt (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: libvirt (Ubuntu Zesty) Status: New => Triaged ** Changed in: libvirt (Ubuntu Zesty) Status: Triaged => Won't Fix ** Also affects: qemu (Ubuntu) Importance: Undecided Status: New ** No longer affects: qemu (Ubuntu Zesty) ** Changed in: qemu (Ubuntu) Status: New => Triaged ** Changed in: libvirt (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1673467 Title: [ocata] unsupported configuration: CPU mode 'host-model' for aarch64 kvm domain on aarch64 host is not supported by hypervisor To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1673467/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
