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. > > The kvm command was backgrounded, not -daemonize(d). It was still > running, and I was accessing the VM via VNC. So kvm was running at the time you tried to access the mointor. >> 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? It is the kvm process that listens on the socket, it spawns no other processes. 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 the "stray" socket (JFYI, you can remove a unix-domain socket where some process is listening, and create another - that one will really be different socket, even if named the same way, -- just like you can re-create a plain file the same way). In any way, there hasn't been any problems/bugs in that area for ages. /mjt -- 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
