Re: Re: Next features and target for development

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

 



AL> The goal is to eliminate the distinction between savevm/migrate since
AL> they are really the same thing (savevm just pauses the VM first).

But from a high level, there are (at least) two distinct management
operations in my mind: relocation and checkpointing.  Relocation
implies that a guest leaves the source machine and appears on the
destination.  Checkpointing implies that the domain doesn't move.  If
we take these two actions, can we not still provide for all the cases?
For example:

  /* Migrate explicitly undefines the host */
  virDomainMigrate(dom, "host"); /* Xen case */
  virDomainMigrate(dom, "tcp://host"); /* qemu case */
  virDomainMigrate(dom, "lvm://foo"); /* qemu error case */
  
  /* Checkpoint does not undefine the host */
  virDomainCheckpoint(dom, "foo"); /* Xen unimplemented case */
  virDomainCheckpoint(dom, "lvm://foo"); /* qemu case */

Is that not sane?

-- 
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms@xxxxxxxxxx

Attachment: pgpEsR5eu8zjY.pgp
Description: PGP signature

--
Libvir-list mailing list
Libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list

[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]