Am 24.09.2012 12:15, schrieb Dietmar Maurer:
Subject: Re: [pve-devel] [PATCH] first bridge device is selected by default
Subject: Re: [pve-devel] [PATCH] first bridge device is selected by default
Am 14.09.2012 13:58, schrieb tgrodzinski:
This patch selects the first bridge device by default.
>>We still stop the VM for a short period, and I think vm_stop() flush all
>>driver cache.
ok. savevm state live -> pausevm ->disk snapshots-> unpausevm
seem good :)
I'll do tests this afternoon, I'll keep you in touch.
- Mail original -
De: "Dietmar Maurer"
À: "Alexandre DERUMIE
> do you think image = size of memory if enough ? (if we have some bytes
> more with incremental ?)
PVE/QemuServer.pm:
my $driver_state_size = 32; # assume 32MB is enough to safe all driver
state;
my $size = $conf->{memory} + $driver_state_size;
> Also, any problem if some datas in vms
>>I currently allocate am image equal to the size of the VM memory.
>>Then I simply do an incremental state save (like a vm migration), and keep
>>the VM running until (saved_bytes + remaining_bytes < available_space).
do you think image = size of memory if enough ? (if we have some bytes more
> Subject: Re: [pve-devel] [PATCH] first bridge device is selected by default
>
> > Subject: Re: [pve-devel] [PATCH] first bridge device is selected by default
> >
> > Am 14.09.2012 13:58, schrieb tgrodzinski:
> > > This patch selects the first bridge device by default.
> >
> > Any thoughts / comm
> How is it possible to save the vmstate if the vm is not paused ? (with a lot a
> memory write access by example ?)
I currently allocate am image equal to the size of the VM memory.
Then I simply do an incremental state save (like a vm migration), and keep
the VM running until (saved_bytes + rem
I'll test that today.
How is it possible to save the vmstate if the vm is not paused ? (with a lot a
memory write access by example ?)
- Mail original -
De: "Dietmar Maurer"
À: pve-devel@pve.proxmox.com
Envoyé: Lundi 24 Septembre 2012 10:50:30
Objet: [pve-devel] snapshot improvem
I tried to improve snapshot behavior a bit:
- take snapshot is now a background task (does not block monitor)
- try to save VM state while VM is online
So downtime during snapshot should be shorter now, especially if the VM use
much RAM.
Feel free to test and report bugs ;-)
- Dietmar
