All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Jerone Young <jyoung5@us.ibm.com>
Cc: xen-devel <xen-devel@lists.sourceforge.net>
Subject: Re: Big xend bug!
Date: Mon, 28 Feb 2005 09:58:17 -0600	[thread overview]
Message-ID: <42233F99.4050309@us.ibm.com> (raw)
In-Reply-To: <1109568335.7036.21.camel@thinkpad>

LTP is going to put significant strain on the system it's being run on.  
It's quite likely that under these conditions Xend cannot cope.  This 
sort of testing is probably a bit wishful.  It would make sense to start 
with something a bit more fundamental like unit testing of the libxc 
interface.

Xend marshalls it's internal state to disk.  I've not looked into it all 
that much but I've been able to recreate the "Xend totally hosed" 
problem.  It persists even after reinstalling Xend.

I've got a funny feeling that there's a directory somewhere that if you 
just rm -rf Xend will start right up again.

Doing a proper reboot or shutdown requires co-operation from the 
management tools.  That's why you were seeing that problem.

Regards,
Anthony Liguori


-------------------------------------------------------
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-02-28 15:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-28  5:25 Big xend bug! Jerone Young
2005-02-28 15:58 ` Anthony Liguori [this message]
2005-02-28 16:22   ` Jerone Young

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=42233F99.4050309@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=jyoung5@us.ibm.com \
    --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.