29.06.2011 19:20, Iordan Iordanov wrote:
On 06/28/11 18:29, Michael Tokarev wrote:
The process listening on this socket no longer exist,
it finished. With this command line it should stay in
foreground till finished (there's no -daemonize etc),
so you should see error messages if any.
Hi Michael,
On 06/29/11 11:52, Michael Tokarev wrote:
The only other explanation I can think of is that you tried
to run two instances of kvm, and when second instance initialized
it re-created the monitor socket but failed later (eg, when
initin network or something else) and exited, but left
On 06/28/11 18:29, Michael Tokarev wrote:
The process listening on this socket no longer exist,
it finished. With this command line it should stay in
foreground till finished (there's no -daemonize etc),
so you should see error messages if any.
The kvm command was backgrounded, not
Hello,
We are using KVM on Debian Squeeze (QEMU 0.12.5). Yesterday, I started a
virtual machine and let it run overnight. I don't recall doing anything
out of the ordinary to it.
This morning, I wanted to issue some commands to it through the control
socket, but socat is unable to connect
28.06.2011 23:20, Iordan Iordanov wrote:
Hello,
We are using KVM on Debian Squeeze (QEMU 0.12.5). Yesterday, I started a
virtual machine and let it run overnight. I don't recall doing anything
out of the ordinary to it.
This morning, I wanted to issue some commands to it through the
