Hi Guido, > This patch does the actual saving and removal of the vm status. It does > so only at vm creation time at the moment. We need to update the config > every time the life config changes later. sorry for asking such "dumb" questions here on a developer-list, but would you mind to tell a bit how libvirt with qemu/kvm should work with your patches (all 5 you posted + something you plan for the near future): - libvirt is shut down gracefully, qemu-domain still running Will the qemu-domain get a (soft) shutdown and libvirt waits some time (configurable?) until the domain is down? Or will libvirt make a snapshot of the domain state and save it into some file? Or can I select between these two modes of operation with some config value? The last one would be my favorite as it is often faster and more reliable. - libvirt starts, a qemu-domain has autostart enabled, memory/state is saved to a file into a special directory will the snapshot be loaded or the domain started from scratch (with unclean filesystem)? what will happen if there is a error during loading the state? - libvirt is buggy and gets a segfault, qemu-domain (autostart set) still running, libvirt is restarted what will happen to the still-running qemu? Thank you very much. Kind regards, Gerd -- Libvir-list mailing list Libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list