Le Fri, 11 Sep 2015 10:45:34 -0600,
Eric Blake a écrit :
> But if the guest is
> malicious, it can pretend to be a guest agent, but intentionally
> refuse to reply to the --quiesce request, and leave libvirt hung
> waiting for a reply. So it boils down to whether you trust your
> guests to be re
[. . .]
On Fri, Sep 11, 2015 at 10:45:34AM -0600, Eric Blake wrote:
> On 09/11/2015 10:18 AM, Jérôme wrote:
>
> >> Yep, that about covers it. Note that the --quiesce step in snapshot
> >> creation requires qemu-guest-agent running in the guest, and that you
> >> trust interaction with your guest
On 09/11/2015 10:18 AM, Jérôme wrote:
>> Yep, that about covers it. Note that the --quiesce step in snapshot
>> creation requires qemu-guest-agent running in the guest, and that you
>> trust interaction with your guest.
>
> Yes, I think I get this. I don't really figure out what these cases
> co
Hi Eric.
Thank you so much for your quick and relieving answer.
Le 2015-09-11 17:05, Eric Blake a écrit :
> Yes, using active block-commit is the ideal way to perform a live backup.
Great.
> Yep, that about covers it. Note that the --quiesce step in snapshot
> creation requires qemu-guest-age
On 09/11/2015 06:45 AM, Jérôme wrote:
> AFAIU, live backups using libvirt may be done thanks to blockcommit as
> explained here on the wiki [2].
>
> -> Considering our use case, is this the recommended way?
Yes, using active block-commit is the ideal way to perform a live backup.
>
> Assuming
Hi.
I'm following here a conversation that was initiated on Kashyap's
website [1].
We have a server we use as a host for virtual machines using KVM
(virt-manager used for VM creation) and we would like to setup VM
backups. Basically, we're thinking of a backup schedule like "keep 7
daily and 4 we
