On 07/26/2013 02:16 PM, Eric Blake wrote:
On 07/26/2013 11:47 AM, mrhines@xxxxxxxxxxxxxxxxxx wrote:
From: "Michael R. Hines" <mrhines@xxxxxxxxxx>
QEMU has in tree now planned for 1.6 support for RDMA-based live migration.
Changes to libvirt:
1. QEMU has a new 'setup' phase in their state machine.
2. Expose the 'x-rdma' migration protocol URI.
3. Expose the 'x-rdma-pin-all' capability for pre-registration of memory.
The x- prefix means that the migration is still experimental; do we want
to be codifying the use of experimental API into libvirt, or is it time
for a patch to qemu to remove the x- prefix? Back in the 1.5 timeframe,
when RDMA was first proposed, the x- prefix made sense, but now that we
are closer to qemu 1.6, and you are trying to get libvirt to drive it,
that's a declaration of stability.
That's a good question. I'll consult with the community for guidance.
It has been very extensively tested, though - by several parties,
but I'll find out and be in touch.
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list