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, [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, 11:12 AM * [email protected] [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
_______________________________________________ xen-discuss mailing list [email protected]
