OK, so we need to fix uvt-kvm in the first instance; Juju cannot be expected to support KVM containers until uvtool works.
Take a look at /usr/share/uvtool/libvirt/template.xml. This is what is supplied to libvirt by default (after some automatic manipulation for other command line arguments and defaults such as a disk image to use, memory size, etc). You can override this baseline definition with "uvt- kvm create --template=... release=trusty arch=arm64 label=release". The XML schema here is defined by libvirt (specified in http://libvirt.org/formatdomain.html). What we need is either a corrected XML that uvtool should use for all architectures, or per- architecture XML definitions and a feature in uvtool to use the correct architecture's XML definitions by default (I'm curious as to how it should detect this; should detection be based on the architecture on the host, on the guest, or both?). This may involve pushing patches to libvirt if support is not already there. I don't see anything PCI-specific in the default XML, so why does libvirt fail with that error? Do we know what the status of arm64 is in libvirt? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1349854 Title: kvm container creation failed: exit status 1 on arm64 with juju 1.20.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1349854/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
