Il 28/01/2014 06:52, Dietmar Maurer ha scritto:
>> If is possible without lose performance into this VM, the write cache for
>> "KVM
>> Live Backup" not must to execute it. In this mode the "KVM Live Backup" will
>> be
>> fantastic.
>
> Sorry, but I do not really understand that question?
>
> W
applied
> changelog : rebase on last git
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
applied, thanks!
> - collie command is now 'dog'
> - KB size is now k
> - snapshot rollback need force -f flag, to avoid confirm prompt
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
> If is possible without lose performance into this VM, the write cache for "KVM
> Live Backup" not must to execute it. In this mode the "KVM Live Backup" will
> be
> fantastic.
Sorry, but I do not really understand that question?
We have done many improvement on backup code, so you should first
Hi Developers
Only want to say a detail that will be a big problem with this strategy of
change on the code of "KVM Live Backup", and please thinks that most people
schedule their backups at night when the most people is sleeping:
If I have HA for my VM that have a data base, and the "KVM Live
I tried todo this but i fail at adding a listener to the hdpanel.
This listener is never called:
// setDrive
var hdpanel = Ext.create('PVE.qemu.HDInputPanel', {
title: gettext('Hard Disk'),
create: true,
insideWizard: true,
listeners: {
changelog : rebase on last git
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Please note that sheepdog 0.8 cluster format is not compatible with < 0.8
sheepdog format.
you need to backup your vdi before upgrade, and restore them after.
They are no upgrade path
Signed-off-by: Alexandre Derumier
---
Makefile |4 ++--
debian/changelog