Guannan Ren wrote:
> On 03/02/2013 12:41 AM, Jim Fehlig wrote:
>> Guannan Ren wrote:
>>
>>> Hi Jim
>>>
>>> In selinux, libvirt added a label for tapfd.
>>> Do you think this patch makes sense for apparmor?
>>> https://www.redhat.com/archives/libvir-list/2012-October/msg01461.ht
On 03/02/2013 12:41 AM, Jim Fehlig wrote:
Guannan Ren wrote:
Hi Jim
In selinux, libvirt added a label for tapfd.
Do you think this patch makes sense for apparmor?
https://www.redhat.com/archives/libvir-list/2012-October/msg01461.html
Hi Gunannan,
Apologies for missing yo
Guannan Ren wrote:
> On 03/01/2013 08:37 AM, Jim Fehlig wrote:
>> Eric Blake wrote:
>>> On 02/27/2013 04:51 PM, Jim Fehlig wrote:
>>>
With the apparmor security driver enabled, qemu instances fail
to start
# grep ^security_driver /etc/libvirt/qemu.conf
security_driver =
On 03/01/2013 08:37 AM, Jim Fehlig wrote:
Eric Blake wrote:
On 02/27/2013 04:51 PM, Jim Fehlig wrote:
With the apparmor security driver enabled, qemu instances fail
to start
# grep ^security_driver /etc/libvirt/qemu.conf
security_driver = "apparmor"
# virsh start test-kvm
error: Failed to
Eric Blake wrote:
> On 02/27/2013 04:51 PM, Jim Fehlig wrote:
>
>> With the apparmor security driver enabled, qemu instances fail
>> to start
>>
>> # grep ^security_driver /etc/libvirt/qemu.conf
>> security_driver = "apparmor"
>> # virsh start test-kvm
>> error: Failed to start domain test-kvm
>
On 02/27/2013 04:51 PM, Jim Fehlig wrote:
> With the apparmor security driver enabled, qemu instances fail
> to start
>
> # grep ^security_driver /etc/libvirt/qemu.conf
> security_driver = "apparmor"
> # virsh start test-kvm
> error: Failed to start domain test-kvm
> error: internal error security
With the apparmor security driver enabled, qemu instances fail
to start
# grep ^security_driver /etc/libvirt/qemu.conf
security_driver = "apparmor"
# virsh start test-kvm
error: Failed to start domain test-kvm
error: internal error security label already defined for VM
The model field of virSecur
