All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jérôme Petazzoni" <jp@enix.org>
To: Christian Limpach <Christian.Limpach@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: More Xen troubles (with xend this time)
Date: Tue, 30 Nov 2004 18:10:10 +0100	[thread overview]
Message-ID: <41ACA972.2090200@enix.org> (raw)
In-Reply-To: <20041130165753.GE22112@cl.cam.ac.uk>


>>Okay, and once we "lost" xend, there is no way to do anything ? (create, 
>>destroy, shutdown, get a console...)
>>    
>>
>You could try removing xend's database in /var/xen/xend-db -- you will
>lose your domain's names but I've found that sometimes this allows
>restarting xend when it's in the state where it doesn't want to start
>anymore.
>  
>
Interesting ! I did that, and then :

# xm list
Name              Id  Mem(MB)  CPU  State  Time(s)  Console
Domain-0           0       59    0  r----   5915.7       
Domain-16         16       63    0  -b---    328.7       
Domain-17         17      127    0  -b---    699.8       
Domain-21         21        0    0  ----c      0.0       
Domain-22         22        0    0  ----c      0.0       

I could successfully create a new domain attached to a console, and stop 
it ; but other stuff didn't work :

# xm console 16
Error: No console information

And xm shutdown didn't do anything, it seems. Destroying crashed domains 
didn't work either. It keeps spitting those messages every couple of 
seconds in xend.log :

[2004-11-30 18:06:44 xend] DEBUG (XendDomain:244) XendDomain>reap> 
domain died name=Domain-21 id=21
[2004-11-30 18:06:44 xend] INFO (XendDomain:564) Destroying domain: 
name=Domain-21
[2004-11-30 18:06:44 xend] DEBUG (XendDomain:244) XendDomain>reap> 
domain died name=Domain-22 id=22
[2004-11-30 18:06:44 xend] INFO (XendDomain:564) Destroying domain: 
name=Domain-22
[2004-11-30 18:06:44 xend] INFO (XendRoot:91) EVENT> xend.domain.exit 
['Domain-21', '21', 'crash']
[2004-11-30 18:06:44 xend] INFO (XendRoot:91) EVENT> xend.domain.destroy 
['Domain-21', '21']
[2004-11-30 18:06:44 xend] INFO (XendRoot:91) EVENT> xend.domain.exit 
['Domain-22', '22', 'crash']
[2004-11-30 18:06:44 xend] INFO (XendRoot:91) EVENT> xend.domain.destroy 
['Domain-22', '22']

xend-debug.log and xm dmesg are silent.

Anything useful I can try to get more information about this before I 
reboot the beast ? :-)



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

  reply	other threads:[~2004-11-30 17:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-30 13:45 More Xen troubles (with xend this time) Jérôme Petazzoni
2004-11-30 14:09 ` Ian Pratt
2004-11-30 16:45   ` Jérôme Petazzoni
2004-11-30 16:57     ` Christian Limpach
2004-11-30 17:10       ` Jérôme Petazzoni [this message]
2004-12-01 10:19         ` Mike Wray
2004-11-30 17:02     ` Ian Pratt
2004-11-30 17:14       ` Jérôme Petazzoni
2004-11-30 14:09 ` Keir Fraser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=41ACA972.2090200@enix.org \
    --to=jp@enix.org \
    --cc=Christian.Limpach@cl.cam.ac.uk \
    --cc=xen-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.