public inbox for pve-devel@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: [pve-devel] applied:  [PATCH-SERIES qemu v2 0/2] QEMU 9.2.0
Date: Tue, 4 Feb 2025 10:01:40 +0100	[thread overview]
Message-ID: <189c24e3-634c-43be-87f2-9a9e43157cf8@proxmox.com> (raw)
In-Reply-To: <20250128151559.147227-1-f.ebner@proxmox.com>

Am 28.01.25 um 16:15 schrieb Fiona Ebner:
> Changes in v2:
> * rebase for current master
> * add a few more stable fixes
> 
> Very small diff in our patches this time and only a couple of stable
> fixes seemed worth picking up, see the patches for details.
> 
> Did only a very quick sanity check with v2, focussing on the
> difference in our patches to v1.
> 
> Basic tests for the following were done with v1 (disclaimer: not each
> combination of the mentioned settings):
> * OS boot testing: Win 11/10/Server 2019, Debian 12 (32 and 64 bit),
>   FreeBSD 14, OpenBSD 7.6
> * OS install testing: Win 10, Ubuntu 24.10
> * snapshot with/without RAM
> * live-migration 9.0 <-> 9.2, 9.2 <-> 9.2, 
> * disk: IDE/SATA/VirtIO SCSI/VirtIO block
> * with/without iothread
> * different SCSI controllers
> * NIC: e1000, VirtIO-net, vmxnet3
> * KVM and non-KVM
> * display: VirtIO GPU/VGA/SPICE
> * VNC clipboard
> * disk resize, move storage (online/offline, various storage
>   combinations)
> * PBS backup, restore and live-restore, dirty bitmap in combination
>   with live-migration
> * VirtIO NIC with German Win10 ISO
> * SeaBIOS/OVMF
> * q35/i440fx
> * OVA import online/offline
> * ESXi import online/offline
> 
> Didn't notice any issues with QEMU 9.2.0 itself.
> 
> Found an issue with OVA live-import in qemu-server, fix sent (and was already
> applied):
> https://lore.proxmox.com/pve-devel/20250120155705.120718-1-f.ebner@proxmox.com/T/#u
> 
> Fiona Ebner (2):
>   update submodule and patches to QEMU 9.2.0
>   stable fixes for QEMU 9.2.0
> 
applied series, thanks!


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


      parent reply	other threads:[~2025-02-04  9:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-28 15:15 [pve-devel] " Fiona Ebner
2025-01-28 15:15 ` [pve-devel] [PATCH qemu v2 1/2] update submodule and patches to " Fiona Ebner
2025-01-28 15:15 ` [pve-devel] [PATCH qemu v2 2/2] stable fixes for " Fiona Ebner
2025-02-04  9:01 ` Thomas Lamprecht [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=189c24e3-634c-43be-87f2-9a9e43157cf8@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 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