From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: Big xend bug! Date: Mon, 28 Feb 2005 09:58:17 -0600 Message-ID: <42233F99.4050309@us.ibm.com> References: <1109568335.7036.21.camel@thinkpad> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit In-Reply-To: <1109568335.7036.21.camel@thinkpad> Sender: xen-devel-admin@lists.sourceforge.net Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Jerone Young Cc: xen-devel List-Id: xen-devel@lists.xenproject.org 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