I've the same problem. I've just upgraded my host this morning.
All my VMs (Debian and Ubuntu Server) didn't start anymore.
r...@lucid-server:~# virsh start guest1
error: Failed to start domain guest1
error: monitor socket did not show up.: Connection refused
r...@lucid-server:~# cat
I've the same problem. I've just upgraded my host this morning.
All my VMs (Debian and Ubuntu Server) didn't start anymore.
r...@lucid-server:~# virsh start guest1
error: Failed to start domain guest1
error: monitor socket did not show up.: Connection refused
r...@lucid-server:~# cat
Yes I think you are true. But the Debian bug (debbugs #567818) in
relation to this bug is the same. Maybe I could try to report my bug as
a new one?
I already check the xml configuration of my VM. Apparently, this path is
created directly by the hypervisor when the VM is started. I tried to
set
Yes I think you are true. But the Debian bug (debbugs #567818) in
relation to this bug is the same. Maybe I could try to report my bug as
a new one?
I already check the xml configuration of my VM. Apparently, this path is
created directly by the hypervisor when the VM is started. I tried to
set
I have approximatively the same problem on Lucid server - alpha 3.
# virsh console guest1
Connected to domain guest1
Escape character is ^]
14:25:40.056: error : vshRunConsole:77 : unable to open tty /dev/pts/3 : No
such file or directory
When I dump the configuration of my VM, something is
I have approximatively the same problem on Lucid server - alpha 3.
# virsh console guest1
Connected to domain guest1
Escape character is ^]
14:25:40.056: error : vshRunConsole:77 : unable to open tty /dev/pts/3 : No
such file or directory
When I dump the configuration of my VM, something is
