* [Qemu-devel] the principle of the vm snapshot based on qemu-dm
@ 2011-12-21 9:18 ¤終於aware
0 siblings, 0 replies; only message in thread
From: ¤終於aware @ 2011-12-21 9:18 UTC (permalink / raw)
To: xen-devel; +Cc: qemu-devel
[-- Attachment #1: Type: text/plain, Size: 679 bytes --]
Hi everyone,
I'm not clear about the principle of the vm snapshot based on qemu-dm, so the following below maybe a joke. Sorry for that...
register_savevm() included in ioemu-qemu-xen/hw/*.c covers various kinds of hardware in order to save the state of current running vm. In this way, the file saved by the cmd of 'xm save domain snapshot.save' is of large size and the operation costs much time. Is there anyelse way to qucikly create a snapshot, such as only saving the memory state(similary with Hibernation) or something else?!
If someone who understands the principle or have the relevant statistics, thanks for sharing.
cheers
bruce
[-- Attachment #2: Type: text/html, Size: 850 bytes --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2011-12-21 9:18 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-12-21 9:18 [Qemu-devel] the principle of the vm snapshot based on qemu-dm ¤終於aware
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).