On 08/15/2011 04:12 AM, Tom Hughes wrote:
> My specific example was that this morning qemu-kvm updated from
> 0.15.0-1.fc15 to 0.15.0-0.3.201108040af4922.fc15 and shortly after that
> I restarted my host only to find that the VM that had been running for
> some time wouldn't start. Looking at the logs showed:
>
>     Unknown savevm section or instance 'kvmclock' 0
>     load of migration failed

That's not good, and it would be nice if we could improve the situation. 
  However,

> There also doesn't seem to be any way to tell libvirt to ignore the
> saved image and do a new boot.

This already exists.  'virsh managedsave-remove dom' prior to 'virsh 
start' will nuke the saved image and let the start do a fresh boot.

-- 
Eric Blake   [email protected]    +1-801-349-2682
Libvirt virtualization library http://libvirt.org
_______________________________________________
virt mailing list
[email protected]
https://admin.fedoraproject.org/mailman/listinfo/virt

Reply via email to