Thanks for looking into it. 1. raspi3b or similar ARM machines do not support ACPI, so the <acpi/> snippet should not exist in libvirt VM's domain XML, or it will complain this or that, refusing to start just as you'd tried. That's also why my example machine XML does not have it.
2. without the <acpi/> snippet, I see that libvirt is constructing the VM startup QEMU command with "-no-acpi" 3. with this parameter passed to QEMU, it seems that QEMU will try to set a "machine variable", which my guess is "raspi3b-machine.acpi", maybe trying to set it to 0 as disable? Given that this machine type does not support ACPI, this variable may be not defined, and thus failed to be set, and hence failed to start. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936831 Title: libvirt ACPI on unsupported machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1936831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
