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

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1272

           Summary: Incorrect default binding behavior with VNC under Xen
                    3.2.1
           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.
/vm/365db4c4-4efc-54dc-2b01-19287a470079/vncpasswd.
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: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs