On Thu, Apr 06, 2023 at 09:32:28AM +0200, Peter Krempa wrote: > On Wed, Apr 05, 2023 at 15:19:07 -0600, Jim Fehlig wrote: > > # virsh create test.xml > > error: Failed to create domain from test.xml > > error: internal error: process exited while connecting to monitor: > > 2023-04-05T20:36:19.564896Z qemu-system-aarch64: Property > > 'integratorcp-machine.acpi' not found > > This is a known issue which should be already fixed if you use the > upcoming qemu version. > > Historically ACPI was controled via '-no-acpi' which is issued when you > don't use the '<acpi/>' feature element in the definition. Also > historically it was only used on x86. With development of the 'virt' > machine type for arm which does use acpi this was un-carefully extended > to aarch64 as well where it didn't work with non-virt machines. > > Now with the latest qemu which reports which machine type actually > support ACPI we avoid use of '-no-acpi' for those which don't support > it. > > Unfortunately the workaround of adding <acpi/> element to definition for > a machine which doesn't have it doesn't work either, because a further > validation check forces you to configure uefi if you want acpi. And even if you try to pile another workaround on top of that one by configuring the VM to use EFI, the end result is just a QEMU error: Property 'integratorcp-machine.pflash0' not found Further proof that was never possible to build a useful working integratorcp-based VM with libvirt. -- Andrea Bolognani / Red Hat / Virtualization
