-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 [2008-10-08 19:14:05 13001] ERROR (XendCheckpoint:157) Save failed on domain klant1_monetdb (17) - resuming. Traceback (most recent call last): File "usr/lib64/python2.5/site-packages/xen/xend/XendCheckpoint.py", line 125, in save forkHelper(cmd, fd, saveInputHandler, False) File "usr/lib64/python2.5/site-packages/xen/xend/XendCheckpoint.py", line 358, in forkHelper child = xPopen3(cmd, True, -1, [fd, xc.handle()]) File "usr/lib64/python2.5/site-packages/xen/util/xpopen.py", line 100, in __init__ self.pid = os.fork() OSError: [Errno 12] Cannot allocate memory [2008-10-08 19:14:05 13001] DEBUG (XendDomainInfo:2456) XendDomainInfo.resumeDomain(17) After this point, I am unable to contact the libvird daemon.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Daniel P. Berrange schreef: > On Wed, Oct 08, 2008 at 07:32:21PM +0200, Stefan de Konink wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA512 >> >> [2008-10-08 19:14:05 13001] ERROR (XendCheckpoint:157) Save failed on >> domain klant1_monetdb (17) - resuming. >> Traceback (most recent call last): >> File "usr/lib64/python2.5/site-packages/xen/xend/XendCheckpoint.py", >> line 125, in save >> forkHelper(cmd, fd, saveInputHandler, False) >> File "usr/lib64/python2.5/site-packages/xen/xend/XendCheckpoint.py", >> line 358, in forkHelper >> child = xPopen3(cmd, True, -1, [fd, xc.handle()]) >> File "usr/lib64/python2.5/site-packages/xen/util/xpopen.py", line 100, >> in __init__ >> self.pid = os.fork() >> OSError: [Errno 12] Cannot allocate memory >> [2008-10-08 19:14:05 13001] DEBUG (XendDomainInfo:2456) >> XendDomainInfo.resumeDomain(17) >> >> After this point, I am unable to contact the libvird daemon. > > Well your host OS has run out of memory, so pretty much everything > will be fubar at this point. If it can't even fork() then there's > not much libvirt until this is resolved. libvirt tries to handle > OOM scenario but there's some places we might have missed, but > even so, the best libvirt can do is to drop all further requests > as gracefully as possible. Not quite right, the host OS still has 32MB of memory at this point. But I agree strange things, even with later saves. If there is anything that is able to remove that painful xend stuff... I'm happy to give it a shot.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Daniel P. Berrange schreef: > This is nothing todo with XenD - the error shows fork() failed due > to lack of OS memory. Whether running XenD or not, if the kernel runs > out of memory you're doomed. You need more RAM allocated to your host. If XenD eats 90% of the available memory (at that time 256MB) I am seriously doomed aswell.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Daniel P. Berrange schreef: > On Wed, Oct 08, 2008 at 09:29:29PM +0200, Stefan de Konink wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA512 >> >> Daniel P. Berrange schreef: >>> This is nothing todo with XenD - the error shows fork() failed due >>> to lack of OS memory. Whether running XenD or not, if the kernel runs >>> out of memory you're doomed. You need more RAM allocated to your host. >> If XenD eats 90% of the available memory (at that time 256MB) I am >> seriously doomed aswell. > > Whatever the cause, its not a libvirt bug. If you think its wrong that > XenD is eating 90% of your ram, then speak to the Xen developers - we > can't help fix XenD here. Yes you can by providing a great technology preview for the alternate technique where XenD is not required anymore.