> The most common related mistake is the lac of <gic version='3'/>
This is what I found too, but it's seems like in my case something else cause this error. Below is attempt to run https://paste.ubuntu.com/25423471/ from Comment 9 which definitely have <gic version='3'/> :
~$ virsh start instance-00000007
error: Failed to start domain instance-00000007
error: internal error: process exited while connecting to monitor: 2019-06-11T18:49:31.843203Z qemu-system-aarch64: -device ioh3420,port=0x8,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x1: MSI is not supported by interrupt controller
> The most common related mistake is the lac of <gic version='3'/>
This is what I found too, but it's seems like in my case something else cause this error. Below is attempt to run https:/ /paste. ubuntu. com/25423471/ from Comment 9 which definitely have <gic version='3'/> :
~$ virsh start instance-00000007 11T18:49: 31.843203Z qemu-system- aarch64: -device ioh3420, port=0x8, chassis= 1,id=pci. 1,bus=pcie. 0,multifunction =on,addr= 0x1: MSI is not supported by interrupt controller
error: Failed to start domain instance-00000007
error: internal error: process exited while connecting to monitor: 2019-06-
Detailed log in bug 1832394.
> If you happen to discuss more for the virt-manager@arm case I'd ask to open a new bug (refer to this one, but keep the discussions separate)
Done: /bugs.launchpad .net/ubuntu/ +source/ virt-manager/ +bug/1832394 /bugs.launchpad .net/ubuntu/ +source/ virt-manager/ +bug/1832395
https:/
https:/