From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH-SERIES qemu-server] adapt to QEMU 8.0 removed and deprecated features
Date: Tue, 6 Jun 2023 08:35:41 +0200 [thread overview]
Message-ID: <8bf40d2a-3cf5-897a-5b1c-624be568862d@proxmox.com> (raw)
In-Reply-To: <20230403120945.51924-1-f.ebner@proxmox.com>
Am 03.04.23 um 14:09 schrieb Fiona Ebner:
> Fiona Ebner (4):
> cfg2cmd: use actual backend names instead of removed tty and paraport
> aliases
> cfg2cmd: replace deprecated no-acpi option with acpi=off machine flag
> cfg2cmd: replace deprecated no-hpet option with hpet=off machine flag
> schema: avoid using deprecated -no-hpet in example for 'args' property
Ping, especially for the first, because that is a removed feature. But
the others lead to warnings which is also confusing to users.
next prev parent reply other threads:[~2023-06-06 6:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 12:09 Fiona Ebner
2023-04-03 12:09 ` [pve-devel] [PATCH qemu-server 1/4] cfg2cmd: use actual backend names instead of removed tty and paraport aliases Fiona Ebner
2023-04-03 12:09 ` [pve-devel] [PATCH qemu-server 2/4] cfg2cmd: replace deprecated no-acpi option with acpi=off machine flag Fiona Ebner
2023-04-03 12:09 ` [pve-devel] [PATCH qemu-server 3/4] cfg2cmd: replace deprecated no-hpet option with hpet=off " Fiona Ebner
2023-04-03 12:09 ` [pve-devel] [PATCH qemu-server 4/4] schema: avoid using deprecated -no-hpet in example for 'args' property Fiona Ebner
2023-06-06 6:35 ` Fiona Ebner [this message]
2023-06-07 15:40 ` [pve-devel] applied-series: [PATCH-SERIES qemu-server] adapt to QEMU 8.0 removed and deprecated features Thomas Lamprecht
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=8bf40d2a-3cf5-897a-5b1c-624be568862d@proxmox.com \
--to=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