Hi Andrew and Corey, first of all thanks for the re-checks. - None is usually not supported on arm, as there are too different cpus and you have to select one. - Host-passthrough fails for "domain is already running" that seems unrelated to the types and actually means it might be running after all :-) - Host-model, as I said is known broken so the refuse via "'host-model' for aarch64 kvm domain on aarch64 host is not supported by hypervisor" seems correct still
About Coreys suggestions: I'm pretty sure there were reasons for the "ARCH_IS_X86" in [1] - especially on a platform as diverse in cpu models as arm just turning it to custom might have side effects we don't see. I haven't discussed #1 with upstream and at least I didn't see anyone else doing it. Therefore #2 might be the much safer solution if you want it to work on arm for now. It might be worth to check the host-passthrough case to work before that, but as I said above "domain already running" sounds like an unrelated issue. [1]: http://libvirt.org/git/?p=libvirt.git;a=commit;h=7ce711a30 -- 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
