[pve-devel] qemu-server : implement pending changes v2

[Daniel Hunsaker]

The pending changes are added to the configuration file, so the changes
would likely be migrated, but they wouldn't be applied until the normal
process for applying them is performed.  The benefit here is that they
aren't immediately applied to the VM's settings, the way they are without
this patch.  Basically, this change makes it so you can change anything you
want, and the VM will live-migrate cleanly between systems.  The changes
will then be committed at whatever point you apply them, be it via
restarting the VM or otherwise.  Suddenly it's safe to change any setting
you like on a VM under HA, which is very useful.
On Oct 30, 2014 5:00 PM, "Cesar Peschiera" <brain at click.com.py> wrote:

> Hi
>
> I have a question, please see below
>
> ----- Original Message ----- From: "Alexandre DERUMIER" <
> aderumier at odiso.com>
> To: "Stanislav German-Evtushenko" <ginermail at gmail.com>
> Cc: <pve-devel at pve.proxmox.com>
> Sent: Thursday, October 30, 2014 1:32 PM
> Subject: Re: [pve-devel] qemu-server : implement pending changes v2
>
>
>  Some questions regarding this patch:
>>>> - What happens when we do online migration with pending changes?
>>>>
>>>
>> pending changes not applied.
>> (Currently if you do a change a non-hotpluggage value and you do a live
>> migration, you have good chance to crash)
>>
>>  .... :-(
> Is possible that the change a non-hotpluggage value also be migrated with
> the VM?
>
> Best regards
> Cesar Peschiera
> _______________________________________________
> pve-devel mailing list
> pve-devel at pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.proxmox.com/pipermail/pve-devel/attachments/20141030/520d4cd0/attachment.htm>