Same issue here. Removing space fixes the AppArmour message.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/77
Title:
error happen when using virsh to start a vm internal error cannot
That is on Ubuntu 14.04 with recent updates by the way:
virsh --version
1.2.2
3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 x86_64 x86_64
x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I see three things happening when I reproduce this.
First, to do this with domxml-from-native you need to give a more
complete command. (Whether or not this is a bug in virsh depends on
whether qemu is still *supposed* to support giving the drive disk as
a standalone argument.)
Second, your
Yep, I've struck the original bug.
Create a basic qemu VM, which runs fine
qemu-img create -f qcow2 /VMs/p2.img 4G
Feed it some CD ROM to install
qemu -cdrom /VMs/Downloads/some.iso -m 512 -boot d /VMs/p2.img
Then start it normally without a cd
qemu -m 512 -boot d /VMs/p2.img
Put the
has anyone reproduced the original bug
(/etc/apparmor.d/libvirt/libvirt-$uuid.files missing) lately?
** Changed in: libvirt (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have removed spaces from hostname that did the trick with 13.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/77
Title:
error happen when using virsh to start a vm internal error cannot
Note: This is time critical. If I cannot find a solution within the next
couple days, I will have to either rip apparmor out by the roots or
switch to Debian... a week from now I will be 8000 miles from this
machine, so by definition it will be operating properly before then...
--
You received
Due to the way libvirt handles logging, this error message could be many
things and is unfortunately quite generic. For people having this
problem, can you post your domain xml for the affected VM and any
apparmor denials from /var/log/kern.log?
As a workaround, people don't need to 'rip out
# virsh dumpxml myhost..org
domain type='qemu'
namemyhost.org/name
uuid6445bf42-7513-985a-7920-9e89a4c42ffe/uuid
memory unit='KiB'524288/memory
currentMemory unit='KiB'524288/currentMemory
vcpu placement='static'1/vcpu
os
type arch='i686' machine='pc-1.0'hvm/type
boot
A typical (though unfortunately undocumented (we should really add this
to the wiki somewhere)) is to do something like (see /usr/lib/libvirt
/virt-aa-helper -h more more info (-u/--uuid is of form
'libvirt-domuuid'):
If profile does not exist:
export VM=foo ; virsh dumpxml $VM | sudo
Oh my. I would call that a bug. True, I can do a workaround to cover my
immediate emergency, I will probably have to change my disk structure
since the root disk is intentionally pretty small... but what if I were
running hundreds or thousands of VM's? And even worse, on another system
(which is
I would worry that my small complaints are the least of your worries. If
someone with a very large farm of VM's happens to update to this
version... you could be hearing from someone with thousands of screaming
customers. It would not be surprising to me if someone with large
systems had their own
Okay, I used the suggested hack and changed my mount point from lib4 to
srv. I have my VM up so I am sorted. But I only have a handful. I would
hate to be in shoes of the person responsible for this change if someone
is so foolish as to upgrade a critical system without lab testing the
upgrade
virt-aa-helper has done this for as long as I can remember. /lib4 is not
an FHS compliant location to store volatile data like VMs, which is what
virt-aa-helper is trying to enforce (ie, if someone is trying to also
restrict libvirtd itself, then virt-aa-helper has to be careful to not
allow
I have the same issue. I brought up a machine with a de novo install of
Quantal server amd64.
I transferred a VM from the old server that is out of service by moving the
disk containing. Made the one edit
change to the xml of the VM so that path to its main disk was correct in the
new
I also met the error.
I think it may the program have no access to create a file in
/etc/apparmor.d/libvirt
I try to `aa-complain libvirtd` ,but it didn't work.
I think if you install a lxc ,then install the libvirt.You may met the
error again.
Help!
--
You received this bug notification
FWIW I ran into this error when I changed a KVM guest name from
kvm-4.0 to kvm-4.0 (new) in the xml file and performed a virsh
define. The naming convention is enforced in Virt Manager (no brackets
or special symbols). There seems to be no checking on virsh define from
the cmd line. There seems
@Ryan,
thanks for the info. The adduser libvirt-qemu libvirtd should however
be spurious. libvirt-qemu is never plced in group libvirtd,
/etc/apparmor.d/libvirt is owned by root:root, and libvirt-qemu is only
used to run the actual kvm command, not to set up the domains.
Has anyone had this
This is happening to me on precise. I try to create a virtual machine in
virt-manager, customize the configuration, click Begin Installation,
then the error pops up:
Unable to complete install: 'internal error cannot load AppArmor profile
'libvirt-f0986b73-5557-62bb-1f46-261d044dec4e''
where
I had to run adduser libvirt-qemu libvirtd to get past this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/77
Title:
error happen when using virsh to start a vm internal error cannot
Quoting Ursula Junque (799...@bugs.launchpad.net):
Hi Serge, sorry about the delay. I managed to create another windows
virtual machine successfully, after removing the old disk image and
By this do you mean that the windows VM actually runs fine? Or does
it fail to start the same way as the
By this do you mean that the windows VM actually runs fine? Or does
it fail to start the same way as the other?
Yes, sorry, I mean it now runs fine, I got no more of that error after
deleting the image and creating it again.
Are the virt-manager client and the libvirt server running the same
(marking incomplete awaiting answer to comment #19)
** Changed in: libvirt (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/77
Title:
error happen
Hi Serge, sorry about the delay. I managed to create another windows
virtual machine successfully, after removing the old disk image and
creating another one (the removal was accidental, oops :/). So this is
what's left:
19:01:47 ursula@marvin: ~ $ ls -l /etc/apparmor.d/libvirt
total 12
Quoting Ursula Junque (799...@bugs.launchpad.net):
Here it is:
16:12:57 ursula@marvin: ~ $ ls -l /etc/apparmor.d/libvirt
total 4
-rw-r--r-- 1 root root 164 Sep 14 13:24 TEMPLATE
16:13:06 ursula@marvin: ~ $ sudo grep -Hi uuid /etc/libvirt/qemu/*.xml
/etc/libvirt/qemu/windows3.xml:
Hi Serge,
I tried to create a new Windows VM yesterday and today, and the error is
the same, BUT when trying to create an Ubuntu VM, it worked!
Unable to complete install: 'internal error cannot load AppArmor profile
'libvirt-23860d44-d9ef-3528-7f65-609bbb727707''
Traceback (most recent call
Ursula,
After trying to create the new windows vm, can you please show the
contents of /etc/apparmor.d/libvirt and the result of
sudo grep -Hi uuid /etc/libvirt/qemu/*.xml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The package should not have deleted that file, and neither precise nor
quantal have libvirt-bin.postrm doing that, which is why I worry
something else may be going on.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm running Quantal, just removed/purged libvirt0 and installed that
again. I'm still not able to run or create any other virtual machines
using virt-manager, as this error message appears.
** Tags added: apport-collected quantal running-unity
--
You received this bug notification because you
@Ursula,
could you show the result of 'dpkg -l | grep libvirt' ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/77
Title:
error happen when using virsh to start a vm internal error cannot
Hi Serge, sure:
14:59:48 ursula@marvin: ~ $ dpkg -l | grep libvirt
ii libvirt-bin0.9.13-0ubuntu10
amd64programs for the libvirt library
ii libvirt0 0.9.13-0ubuntu10
Thanks, Ursula - that gives me an idea, i will test.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/77
Title:
error happen when using virsh to start a vm internal error cannot
generate
@Ursula,
hm, unable to reproduce this still.
Can you please show the contents of /etc/apparmor.d/libvirt and the
result of
sudo grep -Hi uuid /etc/libvirt/qemu/*.xml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: libvirt (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/77
Title:
error happen when using virsh to start a vm internal error cannot
Here it is:
16:12:57 ursula@marvin: ~ $ ls -l /etc/apparmor.d/libvirt
total 4
-rw-r--r-- 1 root root 164 Sep 14 13:24 TEMPLATE
16:13:06 ursula@marvin: ~ $ sudo grep -Hi uuid /etc/libvirt/qemu/*.xml
/etc/libvirt/qemu/windows3.xml:
uuide7921c81-2628-ec0b-a425-28f455ec9e77/uuid
** Changed in:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libvirt (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/77
Title:
@Mikkel,
if you are still having this problem, please run 'apport-collect 77'
to have apport post debug info to this bug.
In the future please file a new bug rather than re-opening an invalid
bug as we are more likely to see that.
** Changed in: libvirt (Ubuntu)
Status: Confirmed =
error: Failed to start domain pinova.example.com
error: internal error cannot load AppArmor profile
'libvirt-1337abc-54b2-fd6f-19f5-6862588b195d
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/77
I have the same issue with libvirt 0.9.8-2ubuntu1 on Precise. It is the
version that ships with Precise, so no custom versions here.
** Changed in: libvirt (Ubuntu)
Status: Invalid = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Error starting domain: internal error cannot generate AppArmor profile
'libvirt-abe9380c-eab7-fe6f-1b49-21a511bdd129'
Traceback (most recent call last):
File /usr/local/share/virt-manager/virtManager/asyncjob.py, line 45, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
File
when create a vm ,it also appears:
'internal error cannot generate AppArmor profile
'libvirt-aa1e3827-e4d3-044e-21e3-f25660ad1d93''
Traceback (most recent call last):
File /usr/local/share/virt-manager/virtManager/asyncjob.py, line 45, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
Thank you for using Ubuntu and reporting a bug. Unfortunately, the
version of libvirt you are using is not a supported version and
therefore I am marking this bug as Invalid. If you can reproduce this in
a supported version of libvirt, please feel free to reopen, giving
detailed instructions on
Error starting domain: internal error cannot generate AppArmor profile
'libvirt-abe9380c-eab7-fe6f-1b49-21a511bdd129'
Traceback (most recent call last):
File /usr/local/share/virt-manager/virtManager/asyncjob.py, line 45, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
File
when create a vm ,it also appears:
'internal error cannot generate AppArmor profile
'libvirt-aa1e3827-e4d3-044e-21e3-f25660ad1d93''
Traceback (most recent call last):
File /usr/local/share/virt-manager/virtManager/asyncjob.py, line 45, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
Thank you for using Ubuntu and reporting a bug. Unfortunately, the
version of libvirt you are using is not a supported version and
therefore I am marking this bug as Invalid. If you can reproduce this in
a supported version of libvirt, please feel free to reopen, giving
detailed instructions on
45 matches
Mail list logo
