WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

RE: [Xen-users] VNC to HVM not starting

To: "'trilok nuwal'" <tc.nuwal@xxxxxxxxx>
Subject: RE: [Xen-users] VNC to HVM not starting
From: "Artur Linhart - Linux communication" <AL.LINUX@xxxxxxxxxxx>
Date: Fri, 21 Sep 2007 07:46:23 +0200
Cc: 'Philippe Vanhaesendonck' <xen@xxxxxxxxxxx>, 'Dylan Martin' <dmartin@xxxxxxxxxxxx>, 'Scott Serr' <serrs@xxxxxxxxxxxx>, "'Alessandro R.'" <lord2y@xxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 20 Sep 2007 23:32:36 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <022c01c7fb77$90184c60$6d58a8c0@xxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <46EF6AAE.9050200@xxxxxxxxxxxx><79a0772d0709180055v84d8ad6qd45e2b221f368303@xxxxxxxxxxxxxx><46EFF667.9070304@xxxxxxxxxxxx> <46EFFD0F.30409@xxxxxxxxxxxx><015401c7fac2$4ef580a0$6d58a8c0@xxxxxxxxxxxxxxxxxxxxxxxxx><017801c7fae1$14a51fe0$6d58a8c0@xxxxxxxxxxxxxxxxxxxxxxxxx><46F192D5.1050000@xxxxxxxxxxx><021101c7fb69$372359f0$6d58a8c0@xxxxxxxxxxxxxxxxxxxxxxxxx><f58fc26d0709200334q759387f9j82d224fad8c4bd0c@xxxxxxxxxxxxxx> <022c01c7fb77$90184c60$6d58a8c0@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acf7cUYkLAkXljC6SEm6xK/vCSjkRgABP1FAACbhQPA=

Hello,

 

            I tested also Your „second“ possibility

vnc=1
vnclisten='IP_of_my_xen_server

vncdisplay=4
vncunused=1

            and in my case on Xen 3.1.0 the vncdisplay parameter was ignored. So, from my point of view if You want to specify the port explicitely by setting vncdisplay, it works only with

vncunused=0

è     exactly like Philippe below wrote...

 

with regards Artur

 


From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Artur Linhart - Linux communication
Sent: Thursday, September 20, 2007 1:16 PM
To: 'trilok nuwal'
Cc: 'Philippe Vanhaesendonck'; 'Dylan Martin'; 'Scott Serr'; 'Alessandro R.'; xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] VNC to HVM not starting

 

Hello,

 

            I could not test all the combinations, but I think You are right. And if the vncunused parameter is omitted, then also vncdisplay parameter is ignored even if specified - like already wrote Philippe...

 

                        With regards, Archie

 


From: trilok nuwal [mailto:tc.nuwal@xxxxxxxxx]
Sent: Thursday, September 20, 2007 12:34 PM
To: Artur Linhart - Linux communication
Cc: Philippe Vanhaesendonck; Dylan Martin; Scott Serr; Alessandro R.; xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] VNC to HVM not starting

 

From my experience :

when

vnc=1
vnclisten='IP_of_my_xen_server

vncdisplay=4
vncunused=0

Always allocate the port 5900 (standard VNC) + 4 (vncdisplay) = 5904 for the display. If it is used by soem other application this will just hang.

vnc=1
vnclisten='IP_of_my_xen_server

vncdisplay=4
vncunused=1

allocate the port 5900 (standard VNC) + 4 (vncdisplay) = 5904 for the display if it is free else allocate other free port.

vnc=1
vnclisten='IP_of_my_xen_server

vncunused=1/0

allocate free port.

 

Please correct me if my understanding is wrong.

Thanks,
Trilok

 

On 9/20/07, Artur Linhart - Linux communication <AL.LINUX@xxxxxxxxxxx> wrote:

Hello,

        Yes, thank You very much, it is it :-)

        So, for me the following configuration

vnc=1
vnclisten='IP_of_my_xen_server' # Here place IP of the Xen server
vncdisplay=4
vncunused=0

        causes the Xen server listens on the given IP on the port
5900 (standard VNC) + 4 (vncdisplay) = 5904
And I can vonnect to it through the VNC viewer!

:-)

The "display" value seems to be valid at least also for the number 21 and
port 5921 (I do not know if there is some max display number)

Dylan, I propose to place such an example into the FAQ You are creating,
sure, if it is not already there ;-)

        With best regards

                Artur

-----Original Message-----
From: Philippe Vanhaesendonck [mailto:xen@xxxxxxxxxxx]
Sent: Wednesday, September 19, 2007 11:21 PM
To: Artur Linhart - Linux communication
Cc: 'Scott Serr'; 'Alessandro R.'; xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] VNC to HVM not starting

Be aware that tere seems to be some precedence in the parameters.
If my memory serves well, you must set vncunused to 0 if you want
vncdisplay to be considered.

/P.

Artur Linhart - Linux communication wrote:
> Hello,
>
>       I've tested it and this is not true what I said and thought, it
> seems to be the fact the display is not influencing the port...
>
>       What does it influence, dies anybody know it? Is it a "bug or a
> feature"? What is then the purpose of the vncdisplay option in the
> configuration?
>


__________ Informace od NOD32 2541 (20070920) __________

Tato zprava byla proverena antivirovym systemem NOD32.
http://www.nod32.cz



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

 



__________ Informace od NOD32 2541 (20070920) __________

Tato zprava byla proverena antivirovym systemem NOD32.
http://www.nod32.cz

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>