On Tue, Dec 08, 2009 at 12:48:22PM +0100, Gabor Gombas wrote: > On Mon, Dec 07, 2009 at 09:41:25PM +0100, Guido Günther wrote: > > > Is this still an issue with 0.8.1? > > Yes. Actually it got worse (or just more reliable): I now managed to > hang virt-manager by opening/closing just a single VM window. Summary: > > - VM #1 runs Linux (all the other VMs run Windows). Opening/closing just > this VM causes virt-manager to hang reliably. > > - If I open multiple windows and then close them in the exact reverse > order, then there is no hang. > > - If close windows in any other order, then virt-manager hangs. That is, > if I open 3 windows and close the second, it hangs. > > AFAIR 0.8.0 hung only when closing the window that was opened first; > opening/closing subsequent windows did not cause problems as long as > the first window was alive. OTOH 0.8.0 crashed sometimes instead, > which 0.8.1 did not do so far. > > - Even if I close all the windows in the "right" order and exit > virt-manager normally, the ssh process to the remote machine remains > there in the background. > > - Even if I kill this ssh process, on the remote node an "nc -U > /var/run/libvirt/libvirt-sock" process remains alive. Not sure if this > is really a problem or not; at least killing these processes and > trying again does not change anything. This might be caused by nc calls needing a "-q 0" argument. Could you try adding these, it would involve adding this to libvirt in src/remote/remote_driver.c as well as virt-manager in src/virtManager/console.py (the later one only for console usage).
I'll check once I get around to, but this might not be too soon. Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
