I also fixed a similar issue that complained about AppArmor and
qemu-system-x86_64 by deleting the /etc/apparmor.d/libvirt/libvirt* files. The
files were owned by root and the first file was zero bytes long.
I did not need to restart and was able to start the VM immediately.
--
You received
> 1. sudo rm /etc/apparmor.d/libvirt/libvirt-
> 2. sudo rm /etc/apparmor.d/libvirt/libvirt-.files
> 3. Restart machine
#1 and #2 are regenerated new on every VM start.
So could it be that it was just 3 for you?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I had this issue and what I did to solve it was:
Deleted relevant files in /etc/apparmor.d/libvirt, e.g.:
1. sudo rm /etc/apparmor.d/libvirt/libvirt-
2. sudo rm /etc/apparmor.d/libvirt/libvirt-.files
3. Restart machine
And then it worked
--
You received this bug notification because you are a
Yeah it is always good to have such insights here to be found by search
engines for the next who hits it.
Glad that my recommendations helped.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384532
Hi Christian,
This is a false-positive reopening of this issue indeed. Still, it may
contain useful bits.
The error occurrence I forwarded is now solved, thanks to what you
advised on a side-subject at
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1786677/comments/6
.
When producing
Hi,
the "file not found" is a red herring - in 99% of the cases it is something in
the actual generated profile that is broken.
Maybe newer libvirt generates a rule now for you (which it didn't before) and
the config for that element contains something (e.g. a bad name) that makes it
break.
To
(sorry for spamming multiple-posts)
When the error occurs, 'dmesg' outputs:
--
[ 1835.178954] audit: type=1400 audit(1534455163.959:121): apparmor="DENIED"
operation="change_profile" info="label not found" error=-2
profile="/usr/sbin/libvirtd"
I reproduce the same on 18.04 LTS:
Log when starting a KVM VM with 'virt-manager':
--
Error starting domain: internal error: Process exited prior to exec: libvirt:
error : unable to set AppArmor profile
'libvirt-a1937a46-2b13-41bd-998b-27ee9a8209a8' for '/usr/bin/kvm-spice': No
such file or
I forgot to mention the VM never triggered AppArmor errors with 16.04.x
LTS. I never checked if AppArmor was really running by the way (this is
not a production host, only a developer machine).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi,
sorry for chiming in so late, but I haven't seen this issue before - the last
update changed that.
Special chars as reported in comment #26 and comment #15 are an issue, but most
of them are fixed or at a better error message now.
First of all since Ubuntu 17.10 (~=UCA-Pike) all files in
this issue still persists. As suggested giving a simple name to the .iso
path worked around it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384532
Title:
Unable to set AppArmor profile [...] no
I'm running libvirt-bin 1.3.1-1ubuntu10.6 and still getting this error.
And it is not related to a space with the directory of a .iso file or
something.
This is really bizarre. Like other's, those files do exist have other
(world) read access set, so no clue what code is asserting that don't
Just to add I think I know a solution to this problem:-
1. The libvirt files created under /etc/apparmor.d/libvirt/ has a
.files
2. If the directory of the ISO specified has spaces it will fail.
Workaround-
1. Change the name of the file to a very simple one( windows.iso, ubuntu.iso)
2. Make
** Description changed:
=
Bugs are not infrequently reported along the lines of
Unable to set Apparmor Profile for [emulator]: No such file or directory
- It is frequently (always?) the result of some value - a cdrom or disk
- file, smbios,
14 matches
Mail list logo
