xen discuss - Jan 2010 - OSOL131 PV DomU loosing TCP connectivity to Xen 3.4.3 Ubuntu 9.10 Dom0

Follow up recent thread i''ve installed OSOL131 PV DomU even via virsh (
per John Levon)
Could BUG :- http://defect.opensolaris.org/bz/show_bug.cgi?id=14098 
to be the reason of constantly loosing  TCP connectivity between Ubuntu 9.10
Dom0 and OSOL-131 PV  DomU.
Next:-  GDM VNC setup seems to be completely broken.
-- 
This message posted from opensolaris.org

I''ve also installed OSOL-129 PV DomU. In this case VNC may be still set
up via /etc/X11/gdm/custom.conf ( which doesn''t exist at all on
OSOL-131 DomU) . DomU behaves normal.
  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"
-- 
This message posted from opensolaris.org

* bderzhavets@yahoo.com [2010-01-24 14:26:58]
> Follow up recent thread i''ve installed OSOL131 PV DomU even via
virsh
> ( per John Levon) Could BUG :-
> http://defect.opensolaris.org/bz/show_bug.cgi?id=14098 to be the
> reason of constantly loosing TCP connectivity between Ubuntu 9.10 Dom0
> and OSOL-131 PV DomU.  Next:- GDM VNC setup seems to be completely
> broken.
What does ''constantly loosing (sic) TCP connectivity'' mean?

dme.
-- 
David Edmondson, Sun Microsystems, http://dme.org

> 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.
-- 
This message posted from opensolaris.org

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, dme@dme.org <dme@dme.org> wrote:

From: dme@dme.org <dme@dme.org>
Subject: Re: OSOL131 PV DomU loosing TCP connectivity to Xen 3.4.3 Ubuntu 9.10
Dom0
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: xen-discuss@opensolaris.org
Date: Monday, January 25, 2010, 8:09 AM

* bderzhavets@yahoo.com [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

Seems like i finally succeeded with VNC on PV DomU OSOL-131 keeping
.vnc/xstartup exactly the same as it gets automatically created by
"vncserver" first run in user''s home directory. TCP
connection to DomU stay stable now. Every new build of OSOL is supposed to be a
charade. Right ?

--- On Mon, 1/25/10, dme@dme.org <dme@dme.org> wrote:

From: dme@dme.org <dme@dme.org>
Subject: Re: OSOL131 PV DomU loosing TCP connectivity to Xen 3.4.3 Ubuntu 9..10
Dom0
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: xen-discuss@opensolaris.org
Date: Monday, January 25, 2010, 11:12 AM

* bderzhavets@yahoo.com [2010-01-25 15:27:38]
> 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.
I''ve seen other reports of problems with the VNC parts of build 131,
but
I don''t know how that would relate to more general network problems.

Can you access the PV console of the guest? Are there any interesting
message in the output of ''dmesg''?
> File ~.vnc/xstartup on 131 looks pretty strange , checking `uname -s`
> to be equal "Suse"
That code comes straight from the open source version upstream.

dme.
-- 
David Edmondson, Sun Microsystems, http://dme.org