From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <t.lamprecht@proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits))
 (No client certificate requested)
 by lists.proxmox.com (Postfix) with ESMTPS id 51C35735C5
 for <pve-devel@lists.proxmox.com>; Fri, 28 May 2021 13:54:03 +0200 (CEST)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
 by firstgate.proxmox.com (Proxmox) with ESMTP id 487AC8FA9
 for <pve-devel@lists.proxmox.com>; Fri, 28 May 2021 13:54:03 +0200 (CEST)
Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com
 [94.136.29.106])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits))
 (No client certificate requested)
 by firstgate.proxmox.com (Proxmox) with ESMTPS id AF2428F96
 for <pve-devel@lists.proxmox.com>; Fri, 28 May 2021 13:54:01 +0200 (CEST)
Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1])
 by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 7FF7B466B4
 for <pve-devel@lists.proxmox.com>; Fri, 28 May 2021 13:54:01 +0200 (CEST)
Message-ID: <de7382e9-c61f-d220-f172-cc229bc2a488@proxmox.com>
Date: Fri, 28 May 2021 13:54:00 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:89.0) Gecko/20100101
 Thunderbird/89.0
Content-Language: en-US
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
 Stefan Reiter <s.reiter@proxmox.com>
References: <20210527104334.31743-1-s.reiter@proxmox.com>
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
In-Reply-To: <20210527104334.31743-1-s.reiter@proxmox.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-SPAM-LEVEL: Spam detection results:  0
 AWL -0.234 Adjusted score from AWL reputation of From: address
 KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment
 KAM_NUMSUBJECT 0.5 Subject ends in numbers excluding current years
 SPF_HELO_NONE           0.001 SPF: HELO does not publish an SPF Record
 SPF_PASS               -0.001 SPF: sender matches SPF record
 URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See
 http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more
 information. [proxmox.com]
Subject: [pve-devel] applied-series:  [PATCH 0/3] Upgrade to QEMU 6.0
X-BeenThere: pve-devel@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe>
X-List-Received-Date: Fri, 28 May 2021 11:54:03 -0000

On 27.05.21 12:43, Stefan Reiter wrote:
> Mostly smooth migration, so far testing has shown good results. Both my
> automated tests and some manual ones have shown little issues.
> 
> Smaller issues encountered so far:
> * guest agent (especially fs-thaw) still seems to have some trouble, especially
>   on Windows, updating the agent and virtio drivers in the VM seemed to help the
>   situation though
> * one time, not reproducible, my mouse stopped working entirely in a Windows VM
>   - so far I blame it on Microsoft ;)
> 
> The previously sent qemu-server patches are required for 6.0 to work correctly
> (probably should have been part of this series, but oh well):
> https://lists.proxmox.com/pipermail/pve-devel/2021-May/048327.html
> 
> 
> pve-qemu: Stefan Reiter (3):
>   udpate and rebase to QEMU v6.0.0
>   debian: ignore submodule checks in QEMU build
>   update keycodemapdb for 6.0
> 
>  debian/changelog                              |   6 +

We normally try to keep the actual version bump at the package level in a separate
commit, and sometimes there's a chance that there are some minor (packaging) adaption
to be made, so it can often be left to do for the uploaded.


any how, applied series, thanks!