On 22.05.2017 15:12, Andrea Bolognani wrote:
On Thu, 2017-05-18 at 10:53 +0200, Stefan Bader wrote:
> @@ -102,6 +103,7 @@
> /usr/bin/qemu-system-or32 rmix,
> /usr/bin/qemu-system-ppc rmix,
> /usr/bin/qemu-system-ppc64 rmix,
> + /usr/bin/qemu-system-ppc64le rmix,
Why does Ubuntu have qemu-system-ppc64le at all?
Hm, apparently it is not really there. It is a soft-link to qemu-system-ppc64.
So that hunk really makes no sense because apparmor is following the link before
checking permissions.
I will refresh that one to drop the ppc64le path.
-Stefan
qemu-system-ppc64 can run both ppc64 and ppc64le guests just
fine, it's emulating the same hardware and the endianness is
decided at runtime AFAIK.
Upstream QEMU doesn't seem to know anything about this:
$ ./configure --target-list=ppc64le-softmmu
ERROR: Unknown target name 'ppc64le-softmmu'
and it's not in the Debian package, so it must have been
added specifically for Ubuntu.
--
Andrea Bolognani / Red Hat / Virtualization
--
libvir-list mailing list
libvir-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list