OK. After 20-25 min of extensive testing OS 2008.11 DomU crashed and dropped into stack trace, running VNC session, started via gnome terminal at remote Dom0 desktop same way as Nevada 106 did. For now there is no any exception for this issue.
But, VNC session crash should not in general crash DomU.
Would be glad to troubleshoot, been instructed.
Boris.
--- On Sat, 3/28/09, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:
From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Subject: Re: [Xen-devel] Failure to setup VNC at CentOS 5.2 PV DomU at Xen Unstable ( 2.6.29-rc8 kernel)
To: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>
Cc: "Xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Date: Saturday,
March 28, 2009, 6:18 AM
Solaris Nevada b106 is also affected in schema bellow.
Looks like hotplug scripts gets locked after VNC Session failure
WS -------------->Vncserver Dom0 ------ xm create -c SNV_DomU.pyrun-------
| |
| Vncviewer 1 Vncviewer
2 | |
|
|---------------------> Gnome Desktop Dom0 ----------->Vncserver SNV_DomU
--- On Sat, 3/28/09, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:
From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Subject: Re: [Xen-devel] Failure to setup VNC at CentOS 5.2 PV DomU at Xen Unstable ( 2.6.29-rc8 kernel)
To: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>
Cc: "Xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Date: Saturday, March 28, 2009, 4:41 AM
OpenSolaris 2008.11 PV DomU may run VNC session started
via gnome terminal invoked on remote pvops Dom0 desktop pretty stable.
So , OpenSolaris PV DomU is not affected.
Actually , any remote VNC session with CentOS 5.2 PV DomU doing "yum upgrade" may be considered as network-intensive test and it works.
I don't think that network at DomU is broken in general.
But , path for vncviewer to CentOS 5.2 DomU via vncserver at Dom0 and vncserver at DomU seems to be broken in meantime.
This doesn't work for CentOS 5.2 DomU:-
WS - Work Station (Linux , Ubuntu Desktop)
WS --------------------->Vncserver Dom0 ------- xm create -c DomU.pyrun----
| |
| Vncviewer 1 Vncviewer 2
| | |
|----------------------------> Gnome Desktop Dom0 ----------->Vncserver DomU
This
works:-
WS -------------------->SSH conn to Dom0 ---- xm create -c DomU.pyrun-----
|
|
| Vncviewer |
|
|
|----------------------------> Gnome Desktop WS --------------->Vncserver DomU
Boris
--- On Fri, 3/27/09, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] Failure to setup VNC at CentOS 5.2 PV DomU at Xen Unstable ( 2.6.29-rc8 kernel)
To: bderzhavets@xxxxxxxxx
Cc: "Xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Date: Friday, March 27, 2009, 7:21 PM
Boris Derzhavets wrote:
> I believe i have to describe the issue in more details:-
> 1. Xen Unstable Dom0 with 2.6.29-rc8 pvops kernel is installed on top
> of Ubuntu 8.10 Server with ubuntu desktop up and running. GDM service is
running,
> with gdm.conf configured to allow remote connections, xinetd is running
Xvnc configured for remote connection as well.
>
2.
This configuration provides remote connection to Dom0 with pvops
kernel via Gnome Desktop. Crash happens when i run VNC session opened via gnome
terminal at remote Dom0's desktop ( it worked fine with rc5 or rc6 for
sure).
> If i ussue :-
> # vncviewer IP_DomU:1
> from gnome terminal running on remote host (i.e. without any interaction
with Ubuntu
> specific X-Server clients services) VNC session seems to be running
stable.
>
That's a bit worrying, because it would suggest that networking in general
is broken. If you don't start Xvnc (or whatever), but run some other
network-intensive test, does that crash?
J
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
