Please, read first entry of current thread . It answers your question
http://opensolaris.org/jive/thread.jspa?threadID=122366&tstart=0
On OSOL-131 DomU i've tried to run "vncserver" manually and modified
~.vnc/xstartup replacing "xterm" with "/usr/bin/gnome-session". The last
causes VNC desktop to freeze and OSOL-131 DomU gets unpin-gable from Ubuntu
9.10 Xen 3.4.3 Dom0. I don't know how behaves TCP stack under memory pressure,
but i clearly see that build 131 has serious problems with VNC setup.
P.S.
File ~.vnc/xstartup on 131 looks pretty strange , checking `uname -s` to be
equal "Suse"
--- On Mon, 1/25/10, [email protected] <[email protected]> wrote:
From: [email protected] <[email protected]>
Subject: Re: OSOL131 PV DomU loosing TCP connectivity to Xen 3.4.3 Ubuntu 9.10
Dom0
To: "Boris Derzhavets" <[email protected]>
Cc: [email protected]
Date: Monday, January 25, 2010, 8:09 AM
* [email protected] [2010-01-25 12:50:30]
>> What does 'constantly loosing (sic) TCP connectivity'
>> mean?
>>
>> dme.
>> --
>> David Edmondson, Sun Microsystems, http://dme.org
> After attempt of VNC connection from Dom0 to DomU ( what brings frozen
> desktop)
> i cannot any longer ping DomU ( regardless xnf0 is up per "ifconfig -a" )
> from Dom0 until DomU gets restarted.
That doesn't seem related to the TCP defensive mode messages.
How is VNC configured? Is this an HVM guest where you're trying to use
VNC to access the guest console or something else?
dme.
--
David Edmondson, Sun Microsystems, http://dme.org
_______________________________________________
xen-discuss mailing list
[email protected]
