Re: [Qemu-devel] Re: KVM call agenda for Oct 19

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 10/19/2010 03:57 PM, Ayal Baron wrote:
Yeah, concurrent is a little trickier.  Simple solution is for a
management tool to just do a stop + multiple snapshots + cont.  It's
equivalent to what we'd do if we don't do it aio which is probably how

we'd do the first implementation.

But in the long term, I think the most elegant solution would be to
expose the freeze api via QMP and let a management tool freeze
multiple
devices, then start taking snapshots, then unfreeze them when all
snapshots are complete.

Regards,

Anthony Liguori
qemu should call the freeze as part of the process (for all of the relevant devices) then take the snapshots then thaw.

Yeah, I'm not opposed to us providing simpler interfaces in addition to or in lieu of lower level interfaces.

Regards,

Anthony Liguori

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux