Hi, Is anyone clear about the format of qemu file for savevm or loadvm? bruce
Do you mean the file format? qcow2, qed, raw? Or the content layout in the file image? On 2011-12-23 13:17, ¤終於aware wrote:> Hi, > Is anyone clear about the format of qemu file for savevm or loadvm? > bruce-- Shu Ming<shuming@linux.vnet.ibm.com> IBM China Systems and Technology Laboratory
On Fri, Dec 23, 2011 at 01:17:00PM +0800, ¤終於aware wrote:> Is anyone clear about the format of qemu file for savevm or loadvm?If you are interested in the serialized device state format (e.g. the e1000 NIC''s serialized state) then the answer is no. I''m not aware of any specification or schema that documents the device state. It has been known to change in the past and writing tools that depend on a specific device state layout outside of qemu.git is not viable today because you''ll have to watch qemu.git hw/ code changes and update your external code every time something changes. It seems like a bad idea to duplicate the device state layout outside of qemu.git. For a temporary hack, read the QEMUFile and hw/ save/load code. You can try qemu-io -c "read -b 0 $length" to extract the vmstate from a qcow2 image file. Stefan
Reasonably Related Threads
- Re: Nested KVM: L0 guest produces kernel BUG on wakeup from managed save (while a nested VM is running)
- Re: Nested KVM: L0 guest produces kernel BUG on wakeup from managed save (while a nested VM is running)
- Re: Create multiple domains from single saved domain state (is UUID/name fixed?)
- Re: Nested KVM: L0 guest produces kernel BUG on wakeup from managed save (while a nested VM is running)
- Re: Nested KVM: L0 guest produces kernel BUG on wakeup from managed save (while a nested VM is running)