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

xen-devel

[Top] [All Lists]

Re: [Xen-devel] domU crash

To: Stephan Böni <boeni@xxxxxx>
Subject: Re: [Xen-devel] domU crash
From: Ted Kaczmarek <tedkaz@xxxxxxxxxxxxx>
Date: 2005年10月17日 09:59:06 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Ewan Mellor <ewan@xxxxxxxxxxxxx>
Delivery-date: 2005年10月17日 13:56:32 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <983B408465C04C49B0344D51FA21C7553E757F@xxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <983B408465C04C49B0344D51FA21C7553E757F@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Mon, 2005年10月17日 at 15:34 +0200, Stephan Böni wrote:
>
> > > > > The log you sent shows the domain being successfully created 
> > > > > and unpaused;
> > > > > it should then start to boot. What happens next?
> > > > 
> > > > Nothing.
> > > > 
> > > > # xm list
> > > > Name ID Mem(MiB) CPU VCPUs State Time(s)
> > > > Domain-0 0 251 0 1 r----- 36.1
> > > > inhouse 8 1024 0 1 ------ 252.2
> > > 
> > > You have a domain here, and it's already used 252 seconds of 
> > > CPU time, so it's
> > > doing _something_. Is that time going up rapidly? Try xm 
> > > list a few times to
> > > find out. What's on the domain's console (xm console 
> > > inhouse)? And it's
> > > Ctrl-] to exit the console again.
> > 
> > Oops. I've rebooted the hole system and now it works. :-)
>
> Bullshit! It works only one time and then i've got the same problem:
>
> # xm list
> Name ID Mem(MiB) CPU VCPUs State Time(s)
> Domain-0 0 251 0 1 r----- 26.4
> inhouse 3 1024 0 1 ------ 28.9
> # xm list
> Name ID Mem(MiB) CPU VCPUs State Time(s)
> Domain-0 0 251 0 1 r----- 26.5
> inhouse 3 1024 0 1 ------ 36.1
> # xm list
> Name ID Mem(MiB) CPU VCPUs State Time(s)
> Domain-0 0 251 0 1 r----- 26.8
> inhouse 3 1024 0 1 ------ 165.8
> # xm list
> Name ID Mem(MiB) CPU VCPUs State Time(s)
> Domain-0 0 251 0 1 r----- 27.0
> inhouse 3 1024 0 1 ------ 178.8
>
> # xm console inhouse
>
> (nothing displayed!)
>
> Stephan
>
Make sure you start the domU in console and have a serial console
connected to xend. You will likely have a better chance of seeing what
is happening.
Regards,
Ted
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date: Re: [Xen-devel] domU crash , Stephan Böni
Next by Date: [Xen-devel] libxenstat python bindings , Travis Vachon
Previous by Thread: Re: [Xen-devel] domU crash , Stephan Böni
Next by Thread: Re: [Xen-devel] domU crash , Stephan Böni
Indexes: [Date] [Thread] [Top] [All Lists]

Copyright ©, Citrix Systems Inc. All rights reserved. Legal and Privacy
Citrix This site is hosted by Citrix

AltStyle によって変換されたページ (->オリジナル) /