Hi!
I got a similar issue on our production environment...
I noticed that after a clean install shutdown and start of domains works BUT
if you restart the libvirt-bin service you can shutdown domains but not start
them again.
If you while in this state purge the libvirt-bin packaga and install it again
(with aptitude)
it works until the next restart of libvirt-bin.
In this case I did not touch apparmor and I did not reboiot the server.
Output from the terminal:
r...@srvsxu0001:~# virsh
Welcome to virsh, the virtualization interactive terminal.
Type: 'help' for help with commands
'quit' to quit
virsh # list
Id Name State
--
1 xus1004-001 running
virsh # shutdown xus1004-001
Domain xus1004-001 is being shutdown
virsh # list
Id Name State
--
virsh # start xus1004-001
Domain xus1004-001 started
virsh # list
Id Name State
--
2 xus1004-001 running
virsh # quit
r...@srvsxu0001:~# service libvirt-bin stop
libvirt-bin stop/waiting
r...@srvsxu0001:~# service libvirt-bin start
libvirt-bin start/running, process 13645
r...@srvsxu0001:~# virsh
Welcome to virsh, the virtualization interactive terminal.
Type: 'help' for help with commands
'quit' to quit
virsh # list
Id Name State
--
2 xus1004-001 running
virsh # shutdown xus1004-001
Domain xus1004-001 is being shutdown
virsh # list
Id Name State
--
virsh # start xus1004-001
error: Failed to start domain xus1004-001
error: monitor socket did not show up.: No such file or directory
virsh #
--
VMs won't start after purging apparmor
https://bugs.launchpad.net/bugs/585964
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
