can't open remote virt-viewer connections

Bug #201340 reported by Nick Barcet
4
Affects Status Importance Assigned to Milestone
libvirt (Ubuntu)
Invalid
Undecided
Unassigned
Nominated for Hardy by Nick Barcet
netcat-openbsd (Ubuntu)
Fix Released
Undecided
Unassigned
Nominated for Hardy by Nick Barcet

Bug Description

Opening a remote virt-viewer connection hangs before getting the vnc connection.

Steps to reproduce:
- Create an account on a remote machine
- add it to libvirtd group
- define some ssh key to connect to it
- start a virtual machine installation from iso
- on the remote machine: virt-viewer -c qemu+ssh://<email address hidden>:portnumber/server virt_install

--> connection hangs indefinitely without ever providing a VNC screen

Comment from soren:
As you pointed out yourself, it first connects to the hypervisor to figure out where to look for the vnc display..
after that, it connects again and starts the vnc session.
The problem is that the hypervisor connection hangs.
I've seen this before, but have yet to track it down. It's on my list (libvirt will only accept a set number of connections, so at some point it becomes unavailable, so it's a quite important bug).

Workaround from soren:
What I do to make it work anyway is run virt-viewer, wait for it to hang, log on to your server, kill the nc process, and then I get the vnc connection.

Revision history for this message
Soren Hansen (soren) wrote : Re: [Bug 201340] [NEW] can't open remote virt-viewer connections

Aha! Tracked it down to a netcat issue. Will upload a fix in a little
bit.

 affects ubuntu/netcat-openbsd
 status inprogress

 affects ubuntu/libvirt
 status invalid

--
Soren Hansen |
Virtualisation specialist | Ubuntu Server Team
Canonical Ltd. | http://www.ubuntu.com/

Changed in libvirt:
status: New → Invalid
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package netcat-openbsd - 1.89-2ubuntu1

---------------
netcat-openbsd (1.89-2ubuntu1) hardy; urgency=low

  * Remove quit-timer.patch. It added a bad, bad default behaviour of keeping
    connections open even though the client had closed the connection. (LP:
    #201340)
  * Modify Maintainer value to match the DebianMaintainerField
    specification.

 -- Soren Hansen <email address hidden> Wed, 12 Mar 2008 11:49:28 +0100

Changed in netcat-openbsd:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.