This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-bugs] [Bug 1272] New: Incorrect default binding behavior with VNC u

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1272] New: Incorrect default binding behavior with VNC under Xen 3.2.1
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Mon, 9 Jun 2008 07:33:12 -0700
Delivery-date: Mon, 09 Jun 2008 07:33:28 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

           Summary: Incorrect default binding behavior with VNC under Xen
           Product: Xen
           Version: unspecified
          Platform: x86
        OS/Version: Linux-2.6
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Tools
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: whi@xxxxxxxxxxxx

If a user specifies vfb = [ 'type=vnc' ] in a domU config file, the domU is
launched and VNC bound to :5900.  If a second domU is launched with the same
parameter, the domain builder apparently attempts to bind to :5900 and fails,
throwing the following to logs:

xs_read(): vncpasswd get error.
bind() failed

The domain tells the user it started, but does nothing.  CPU on the guest goes
to 100% and subsequent invocation of "xm console" yields "xenconsole: Could not
open tty `/dev/pts/1': No such file or directory".  The domU will stay in this
limbo state presumably forever.

It's my understanding that Xen should pick an unused port above 5900 and bind
to that.  I'm basing my assumption that this has to do with port binding on the
fact that there is a global default password in xend-config.sxp.

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 1272] New: Incorrect default binding behavior with VNC under Xen 3.2.1, bugzilla-daemon <=