This does not match James finding of missing the gic version in the generated 
XML.
Also the error is to not start the guest at all.
Yet still on the changed MSI interrupt behaviour the following change might be 
related:

commit b4b9862b536f41fcdf6ad193a306a852c5b5b71a
Author: Michael S. Tsirkin <[email protected]>
Date:   Fri Feb 17 04:52:16 2017 +0200

    virtio: Fix no interrupt when not creating msi controller

    For ARM virt machine, if we use virt-2.7 which will not create ITS node,
    the virtio-net can not recieve interrupts so it can't get ip address
    through dhcp.
    This fixes commit 83d768b(virtio: set ISR on dataplane notifications).

    Signed-off-by: Shannon Zhao <[email protected]>
    Reviewed-by: Michael S. Tsirkin <[email protected]>
    Signed-off-by: Michael S. Tsirkin <[email protected]>

This commit is contained in 2.9.
James suggested that this might be fixed in 2.9/2.10 therefore I'll update here 
once I have a 2.10 to test.
If one wants/can test on Artful there is a daily qemu available at 
https://launchpad.net/~ubuntu-virt/+archive/ubuntu/virt-daily-upstream (I'd not 
recommend to also pull the libvirt from there to only change one component).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706630

Title:
  aarch64: MSI is not supported by interrupt controller

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1706630/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to