From: aderumier@odiso.com
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] qemu live migration: bigger downtime recently
Date: Mon, 25 Jan 2021 10:26:01 +0100 [thread overview]
Message-ID: <b5bf424187d8e4d1a2c00cee7ad0a63863bd2c78.camel@odiso.com> (raw)
In-Reply-To: <1611564401.3sjx0tyrat.astroid@nora.none>
>
> pve-qemu-kvm (5.1.0-6) pve; urgency=medium
>
> * migration/block-dirty-bitmap: avoid telling QEMU that the bitmap
> migration
> is active longer than required
>
> -- Proxmox Support Team <support@proxmox.com> Thu, 05 Nov 2020
> 18:59:40 +0100
>
> sound like that could be the case? ;)
yes, I was not sure about this.
So,I was just out of luck when I have upgraded ^_^
I have tried to change dirty-bitmaps=0 in set_migration_caps, but it
don't fix it.
So, I think I'm good to plan some migrations with downtime.
Thanks for your response !
Alexandre
prev parent reply other threads:[~2021-01-25 9:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 14:34 aderumier
2021-01-22 15:06 ` aderumier
2021-01-22 18:55 ` aderumier
2021-01-23 8:38 ` aderumier
2021-01-25 8:47 ` Fabian Grünbichler
2021-01-25 9:26 ` aderumier [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b5bf424187d8e4d1a2c00cee7ad0a63863bd2c78.camel@odiso.com \
--to=aderumier@odiso.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox