Re: More Xen troubles (with xend this time)

["Jérôme Petazzoni" <jp@enix.org>]

>>I did restore the domain, then noticed it was crashed ("-----c" in xm 
>>list). I tried to destroy it, but it didn't work. So I stopped xend, 
>>restarted it ... And there it goes :
>>    
>>
>
>Restarting xend was a bit of a brave move. Although its intended
>to be restartable, there are definitely bugs in the restart code,
>particularly if you have domains in unusual states at the time
>  
>
Okay, and once we "lost" xend, there is no way to do anything ? (create, 
destroy, shutdown, get a console...)

>As to why the domain wouldn't be destroyed, that may turn out to
>be a useful clue as to the resume problem at its root. If we
>could get a crashdump from a known kernel image I'm sure we can
>fix this pretty easily.
>  
>
I will do my best to reboot the box and try to reproduce the problem. 
But if the restore operation crashes xend, I will never be able to get a 
crash dump - unless there's another way to get the information ?

If I don't use save/restore/migrate, can I expect Xen to be stable ? Or 
are there other features that are deemed to cause problems ?


-------------------------------------------------------
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/