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

[Xen-users] Debian Sarge - breakdown

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Debian Sarge - breakdown
From: "Mathias Diehl" <md@xxxxxxxxxxxxx>
Date: Mon, 10 Oct 2005 13:06:10 +0100
Cc: md@xxxxxxxxxxxxx
Delivery-date: Mon, 10 Oct 2005 10:08:01 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi @ all,

sonce a few month I'm running a XEN (stable) on debian sarge. I run the dom0 
with 64 MB RAM, three domU with 128 and one with 512.

For development I had the machine at home and everything worked fine. Some days 
ago I brought the server to a server center and since then I face a strange 
problem.

Booting the server works fine, all dom's are booting and online. I can access 
all domains via ssh, start additinal domains and stop domains. 

For the second time now the server just "died". I can't reach it any more. I 
sent a technichian to the server and he told me that the machine was still 
running even though there was no monitor output.

After reebot I was able to ssh again... I checked all the logs but found 
nothing strange. dom0 was running up to a certain time and then the next log 
entries were about the reboot.

I connected via ssh to one of the domU's and tried to end the session with 
"exit"  and nothing happened. The server was down again.

I'm not sure (as I'm actually no specialist) if the exit command on the ssh 
shell might be the reason for my problem. Actually I thought that dom0 would 
never be affected from anything done within a domU. Please help me 
understanding where to find my problem. Do I have to check domU's as well? 

thanx

M.

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

<Prev in Thread] Current Thread [Next in Thread>