Additional info on the VM that don't responses to autostart:
r...@baal:~# virsh dominfo enm-fw
Id: 3
Name: enm-fw
UUID: bdf8b960-4f96-653f-b36f-58d03261dce3
OS Type:hvm
State: running
CPU(s): 1
CPU time: 1231.4s
Max memory: 262144
FunkyM0nk3y, this is (potentially) a different issue. If you are using a
different emulator or wrapper script, you will need to adjust
/etc/apparmor.d/usr.sbin.libvirtd to add a rule allowing access to your
non-default emulator, then run:
$ sudo apparmor_parser -r /etc/apparmor.d/usr.sbin.libvir
I'm testing kvm on 10.04 and have some similar problems. I found that
sometimes after rebooting the host don't responses virsh
r...@baal:~# virsh vncdisplay enm-fw
error: unable to connect to '/var/run/libvirt/libvirt-sock': No such file or
directory
error: failed to connect to the hypervisor
r.
I've got similar symptoms without a custom wrapper script.
Ubuntu (10.04) won't start my machines with apparmor enabled.
I had a normal /usr/bin/kvm entry in each machine.
After removing this entry, it works with apparmor, too.
Just want to leave this info here in case someone is having the same
** Summary changed:
- Cannot start guest when apparmor is running
+ Cannot start guest with emulator wrapper
--
Cannot start guest with emulator wrapper
https://bugs.launchpad.net/bugs/490370
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
