On Thu, Apr 19, 2012 at 09:03:16AM +0800, Wen Congyang wrote: > Currently, we use migrate to dump guest's memory. There is one > restriction in migrate command: the device's status should be > stored in qemu because the device's status should be passed to > target machine. > > If we passthrough a host device to guest, the device's status > is stored in the real device. So migrate command will fail. > > We usually use dump when guest is panicked. So there is no need > to store device's status in the vmcore. > > qemu will have a new monitor command dump-guest-memory to dump > guest memory, but it doesn't support async now(it will support > later when the common async API is implemented). > > So I use dump-guest-memory only when the guest uses host device > in this patchset. Hmm, doesn't the new command generate dump files in a totally different format to the existing command ? If so I don't think it is nice behaviour to silently switch between 2 different dump formats depending on the XML config. I think we'd want some kind of flag to specify what format is desired. Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list