Re: [Xen-users] Xen domains will not reboot or destroy as they should be

[Peter Viskup <skupko.sk@xxxxxxxxx>]

On Tue, Dec 14, 2010 at 11:50 AM, Jarkko Santala <jake@xxxxxxxxxxxxx> wrote:

I don't know if the same setting is the reason for another bug I ran into - I tried running some other xm commands instead of destroy on one of these domains in "s" limbo and what happened was that it started spawning as many copies of that domU as it could fit into memory - killing them would spawn another one in the freed memory. The situation finally resolved itself after I had ran xm destroy in a loop, but I was unable to start any new domUs after that until I rebooted. Not sure which xm command set it off in the first place.

       -jake

--
Jarkko Santala <jake&portalify,com>   http://www.portalify.com
System Administrator

I have been experiencing same issue with spawning processes of domU. The solution for this was stopping xend and then killing of all domU-related processes. Sometimes there were some xenstore entries remaining and I had to remove them with xenstore-rm before starting domU again.

Unfortunately Debian stable forward-porting Xen kernels are not as stable as someone would expect and I am thinking of switching to XenSource 'official' kernel versions.

--

Peter Viskup

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users