all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Fiona Ebner <f.ebner@proxmox.com>
Subject: Re: [pve-devel] [PATCH-SERIES qemu-server] QEMU 9.2 compat
Date: Sun, 6 Apr 2025 21:56:32 +0200	[thread overview]
Message-ID: <73c0ab70-6b00-40d3-994b-9492945356b3@proxmox.com> (raw)
In-Reply-To: <20250207141821.74864-1-f.ebner@proxmox.com>

Am 07.02.25 um 15:18 schrieb Fiona Ebner:
> Adapt to deprecated features in QEMU 9.2 and clean up setting
> migration capabilities.
> 
> Fiona Ebner (4):
>   cfg2cmd: replace deprecated 'reconnect' option with 'reconnect-ms'
>   migration: drop removed 'compress' capability
>   migration: drop deprecated 'zero-blocks' capability
>   migration: remove wrong attempt of disabling 'rdma-pin-all' capability
> 

As there is a small merge conflict due to context changes in d/control
and some recent commits that caused some changes in the tests, it might
be best to rebase this.


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


  parent reply	other threads:[~2025-04-06 19:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-07 14:18 Fiona Ebner
2025-02-07 14:18 ` [pve-devel] [PATCH qemu-server 1/4] cfg2cmd: replace deprecated 'reconnect' option with 'reconnect-ms' Fiona Ebner
2025-02-07 14:18 ` [pve-devel] [PATCH qemu-server 2/4] migration: drop removed 'compress' capability Fiona Ebner
2025-02-07 14:18 ` [pve-devel] [PATCH qemu-server 3/4] migration: drop deprecated 'zero-blocks' capability Fiona Ebner
2025-02-07 14:18 ` [pve-devel] [PATCH qemu-server 4/4] migration: remove wrong attempt of disabling 'rdma-pin-all' capability Fiona Ebner
2025-04-06 19:56 ` Thomas Lamprecht [this message]
2025-04-07  7:34   ` [pve-devel] superseded: [PATCH-SERIES qemu-server] QEMU 9.2 compat Fiona Ebner

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=73c0ab70-6b00-40d3-994b-9492945356b3@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=f.ebner@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal