public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] qemu live migration: bigger downtime recently
Date: Mon, 25 Jan 2021 09:47:45 +0100	[thread overview]
Message-ID: <1611564401.3sjx0tyrat.astroid@nora.none> (raw)
In-Reply-To: <8cdf4d6536899de1c6a6a43ff7fa21e28ac87331.camel@odiso.com>

On January 23, 2021 9:38 am, aderumier@odiso.com wrote:
> about qemu version,  
> 
> theses vms was started around 6 november, after an update of the qemu
> package the 4 november.
> 
> 
> looking at proxmox repo, I think it should be 5.1.0-4 or -5.
> 
> 
> pve-qemu-kvm-dbg_5.1.0-4_amd64.deb                 29-Oct-2020 17:28  
> 75705544
> pve-qemu-kvm-dbg_5.1.0-5_amd64.deb                 04-Nov-2020 17:41  
> 75737556
> pve-qemu-kvm-dbg_5.1.0-6_amd64.deb                 05-Nov-2020 18:08  
> 75693264
> 
> 
> Could it be a known bug introduced by new backups dirty-bitmap patches,
> and fixed later ?  (I see a -6 version one day later)
> 

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? ;)




  reply	other threads:[~2021-01-25  8:48 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 [this message]
2021-01-25  9:26         ` aderumier

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=1611564401.3sjx0tyrat.astroid@nora.none \
    --to=f.gruenbichler@proxmox.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal