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>,
	Victor Hooi <victorhooi@yahoo.com>,
	PVE development discussion <pve-devel@pve.proxmox.com>
Subject: Re: [pve-devel] QEMU 6.0 is out =)
Date: Sat, 1 May 2021 11:17:14 +0200	[thread overview]
Message-ID: <2a4ca31c-61c7-600d-9505-e8ac46fab989@proxmox.com> (raw)
In-Reply-To: <CAMnnoULuRNUaYsFQ8pfRAzvoySzp+_z_hJzTqut2ye6E=YUZGA@mail.gmail.com>

Hi,

On 30.04.21 18:40, Victor Hooi wrote:
> QEMU 6.0 just got announced:
> 
> https://www.qemu.org/2021/04/30/qemu-6-0-0/
> https://wiki.qemu.org/ChangeLog/6.0
> 
> There's some nifty new NVMe 1.4 support/emulation features, a new VNC
> resize features (with virtio-vga) and some improvement to QMP backup speed.

NVMe needs to get first included in PVE anyway, not hard but it isn't yet
hot-pluggable nor migratable, so not really ready for us (we're working with
upstream on that).

QMP backup speed gets faster on "to fast" HW, so those user who put in the
slowest spinner they can get hands one should not hold their breadth that
it will get fast now, the law of basic physic limitation still holds up :-)

The VNC resize thing could be nice indeed, still need to evaluate that one.

> And there's also some AMD encryption features (we run on the AMD EPYC CPUs).
> 

In general interesting yeah, especially for setups with VMs from different
users - it has some overhead though, but we planned to evaluate this since
a bit, some other building blocks got included in earlier kernel/QEMU releases
already.

> I'd love to test some of these - any idea how long before these might hit
> the testing repos?
> 

Note, guestimation ahead. I'd say it will be more than a few weeks and it
with 6.4 out which freshly includes 5.2 (which took quite a bit of work to
get stable for PVE), and extrapolating from past releases, I'd say this won't
be in any 6.x releases from us, and PVE 7.0 is ready when it's ready :-)

cheers,
Thomas
 




      reply	other threads:[~2021-05-01  9:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAMnnoULuRNUaYsFQ8pfRAzvoySzp+_z_hJzTqut2ye6E=YUZGA.ref@mail.gmail.com>
2021-04-30 16:40 ` Victor Hooi
2021-05-01  9:17   ` 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=2a4ca31c-61c7-600d-9505-e8ac46fab989@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=pve-devel@pve.proxmox.com \
    --cc=victorhooi@yahoo.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