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 -daemonize(d). It was still running, and I was accessing the VM via VNC.
How about checking who is actually listening on this socket before asking?
I thought it's the kvm process that listens on the socket. I haven't seen other processes spun off by kvm until now. Is that not the case?
I hope this clears things up. If there is still something strange in my question, do let me know.
Cheers, Iordan -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
