I have a pair of new clustered servers running SLES 11 SP3 with the high availability extensions. These two hosts are running the XEN kernel. I followed the instructions for Enabling VNC Server on startup of the X server with SLE 11 (https://www.novell.com/support/kb/doc.php?id=7003097) to the letter. The server refuses my VNC connection with port:0, 5900, and no port. When I look for a running instance of VNC I find only the following:
Which seems to be only for console access to a running guest. I do not know what else to look at. Once I login as root the VNC connection is accepted. I would appreciate any pointers.
[QUOTE=tkindig;23505]I have a pair of new clustered servers running SLES 11 SP3 with the high availability extensions. These two hosts are running the XEN kernel. I followed the instructions for Enabling VNC Server on startup of the X server with SLE 11 (https://www.novell.com/support/kb/doc.php?id=7003097) to the letter. The server refuses my VNC connection with port:0, 5900, and no port. When I look for a running instance of VNC I find only the following:
Which seems to be only for console access to a running guest. I do not know what else to look at. Once I login as root the VNC connection is accepted. I would appreciate any pointers.[/QUOTE]
the problem most probably is caused by an “inconsistent” configuration:
the KB article describes to use port 5900 for the X server’s VNC port ([FONT=Courier New]Option “rfbport” “5900”[/FONT]), which it will like try to open on “all interfaces”
your DomU is configured to provide VNC access and is either configured explicitly to use 5900 or chose so because it (then) was the first free port. It will only listen on “lo”, though
most likely, the X server got started after the VM, hence it no longer could listen on *:5900 (since 127.0.0.1:5900 already is opened by qemu-dm)
Personally, I recommend setting explicit ports for VNC access to DomUs anyhow, so you very well may set those to something starting at 5910 or similar, to avoid clashes.