[Bug 1546978] Re: apparmor does not allow to run qemu-dm executable

2016-04-06 Thread Mathew Hodson
** No longer affects: libvirt (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1546978 Title: apparmor does not allow to run qemu-dm executable To manage notifications about this bug go to:

[Bug 1546978] Re: apparmor does not allow to run qemu-dm executable

2016-04-05 Thread Adam Conrad
Hello Pablo, or anyone else affected, Accepted libvirt into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libvirt/1.2.2-0ubuntu13.1.19 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Bug 1546978] Re: apparmor does not allow to run qemu-dm executable

2016-03-11 Thread Stefan Bader
It does not necessarily need to as the Trusty version of Xen has everything needed to run in libxl mode. We even have attempted to provide tools to convert the old configurations over from handled by xend into handled by libvirt. There is really no "excuse" to run the old toolstack. That said

Re: [Bug 1546978] Re: apparmor does not allow to run qemu-dm executable

2016-03-11 Thread Serge Hallyn
Hi Stefan, Ok so for 14.04 this should be added. But if trusty was the last release which had that, and kilo cloud archive for trusty has libvirt from vivid, does that mean the vivid xen should be included in the kilo cloud archive? -- You received this bug notification because you are a

[Bug 1546978] Re: apparmor does not allow to run qemu-dm executable

2016-03-11 Thread Stefan Bader
I guess as the binary is still there it has to be enabled in apparmor. Though on the other hand, qemu-dm is the old device-model which would/should only be used when the old xm/xend toolstack is used. And Trusty was the last release that had that code in at all and I tried hard to get users

[Bug 1546978] Re: apparmor does not allow to run qemu-dm executable

2016-03-11 Thread Stefan Bader
I guess as the binary is still there it has to be enabled in apparmor. Though on the other hand, qemu-dm is the old device-model which would/should only be used when the old xm/xend toolstack is used. And Trusty was the last release that had that code in at all and I tried hard to get users

[Bug 1546978] Re: apparmor does not allow to run qemu-dm executable

2016-03-10 Thread Serge Hallyn
Hi James, the kilo libvirt package (which I assume this is?) does indeed not have a rule for qemu-dm, which does exist in xen-utils-4.4 in trusty (and there is no xen-utils in kilo archive). Note this bug is not valid against the xenial libvirt package, as there is no qemu-dm binary in

[Bug 1546978] Re: apparmor does not allow to run qemu-dm executable

2016-03-10 Thread Serge Hallyn
Hi James, the kilo libvirt package (which I assume this is?) does indeed not have a rule for qemu-dm, which does exist in xen-utils-4.4 in trusty (and there is no xen-utils in kilo archive). Note this bug is not valid against the xenial libvirt package, as there is no qemu-dm binary in

[Bug 1546978] Re: apparmor does not allow to run qemu-dm executable

2016-03-10 Thread Serge Hallyn
** Changed in: libvirt (Ubuntu) Assignee: (unassigned) => James Page (james-page) ** Changed in: libvirt (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1546978] Re: apparmor does not allow to run qemu-dm executable

2016-02-18 Thread Pablo Orviz
There is a typo in the line to be added to /etc/apparmor.d/usr.sbin.libvirtd: /usr/lib/xen-*/bin/pygrub PUx, + /usr/lib/xen-*/bin/qemu-dm PUx, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.