Re: [libvirt] [RFC] Add a new feild to qemud_save_header to tell if the saved image is corrupt

> Remember, that 'migrate' is a long-running async job command, and can > be interrupted. That is, 'service libvirtd restart' is a legal action > to take during step 3, and it is not as severe as a libvirtd crash, > and we have already recently added patches to remember async job > status across libvirtd restarts with the intention of making it legal > to restart libvirtd in the middle of an async job (whether the async > job should still succeed, or should remove the save file, is a > slightly different question; but removing the save file would require > that we save in the XML the name of the file to remove if libvirtd is > restarted). Hmm, how about restart libvirtd during the process of managed saving? Domain will be restored from the corrupt save image automatically. We report an error like "image is corrupt" and quite the domain starting simply? This might be not good, as one will see a running domain fails to start after libvirtd restarting. Or we want to the managed saving still succeed? If so, we might need: 1) continue the managed saving job, (Per we are already support remeber the async job status across libvirtd restarting) 2) restore from the saved image finished in 1).