[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Question about xm save

  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Dietmar Hahn <dietmar.hahn@xxxxxxxxxxxxxxxxxxx>
  • Date: Mon, 12 Mar 2007 08:53:40 +0100
  • Delivery-date: Mon, 12 Mar 2007 00:52:49 -0700
  • Domainkey-signature: s=s768; d=fujitsu-siemens.com; c=nofws; q=dns; b=tQvK84LgwVhtGIKaX50ZTRRh3+Dr9Kb3bRNwGDxWKTyYKqOiKcvE75QMX3zDdLC0V8qfnQd5jK5pq27LInX5Abk8IdW0vE6F5Ojxz7S0Su3z4PRojLnOKTxY/sOcuk0S;
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>


I'm trying to understand what's going on while calling 'xm save ...'.
I looked through the sources and found in xend stuff:
XendCheckpoint.py -> saveInputHandler() -> dominfo.shutdown('suspend')
This makes an entry in the xenstore:
control = ""
    shutdown = "suspend"
The function dominfo.waitForShutdown() is startet and waits for an event.
In parallel (with the forkHelper) the command
'/usr/lib/xen/bin/xc_save 21 1 0 0 0' is started and never returns.
What I miss is the connection between these both things.
Can anybody give me a hint?
(For the tests I simply added some tracer in the python scripts and startet 
the mini-os.)
Many thanks in advance!


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.