From: Wolfgang Bumiller <w.bumiller@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH v2 0/4] <add meta info and bandaid for QEMU 6.1 and unpinned q35 machine backward compat
Date: Thu, 4 Nov 2021 15:16:26 +0100 [thread overview]
Message-ID: <20211104141626.iys35roshf66fch2@olga.proxmox.com> (raw)
In-Reply-To: <20211103155812.1461208-1-t.lamprecht@proxmox.com>
I guess that's okay...
for all those weirdos who don't create `.link` files to pin their
network interface names in place :-P
Acked-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
On Wed, Nov 03, 2021 at 04:58:08PM +0100, Thomas Lamprecht wrote:
> changes v1 -> v2:
> * move checks into own method
> * ensure forced machine is parsed so that min_version can work
> * only apply on `l26` ostype
> * fix test file name and comment
>
> v1 cover letter:
>
> First add a new meta property that is currently exclusively set on new
> VM creation and then read-only, initially add the creation time as UNIX
> epoch and the QEMU version that was installed during installation
> (thought about using the one on first start but that actually does not
> gives any more guarantee, so just go for simple).
>
> Use that information to band aid around a change regarding hotplug in
> QEMU 6.1 that can affected older VMs on fresh start (migration and
> rollback is covered by force-machine mechanisms as always already).
>
> I'm not 100% convinced of the whole thing, albeit I see some merit in
> the meta property even if we do not go with the last patch, anyhow, I
> proposed this off-list to Dominik (and those thing is partly his idea
> too), Wolfgang, Fabian and Stefan and none of them rejected the idea nor
> communicated a better/more preferred alternative, so I went for it
> (still not steaming from enthusiasm though)
>
> Thomas Lamprecht (4):
> config: add new meta property withe creation time
> config: meta: also save the QEMU version installed during creation
> tests: cfg2cmd: add a few q35 related tests
> cfg2cmd: switch off ACPI hotplug on bridges for q35 VMs
>
> PVE/API2/Qemu.pm | 2 +
> PVE/QemuServer.pm | 73 +++++++++++++++++++
> .../q35-linux-hostpci-multifunction.conf.cmd | 1 +
> test/cfg2cmd/q35-linux-hostpci.conf.cmd | 1 +
> test/cfg2cmd/q35-simple-6.0.conf | 13 ++++
> test/cfg2cmd/q35-simple-6.0.conf.cmd | 28 +++++++
> test/cfg2cmd/q35-simple-7.0.conf | 14 ++++
> test/cfg2cmd/q35-simple-7.0.conf.cmd | 28 +++++++
> test/cfg2cmd/q35-simple-pinned-6.1.conf | 13 ++++
> test/cfg2cmd/q35-simple-pinned-6.1.conf.cmd | 28 +++++++
> test/cfg2cmd/q35-simple.conf | 13 ++++
> test/cfg2cmd/q35-simple.conf.cmd | 29 ++++++++
> 12 files changed, 243 insertions(+)
> create mode 100644 test/cfg2cmd/q35-simple-6.0.conf
> create mode 100644 test/cfg2cmd/q35-simple-6.0.conf.cmd
> create mode 100644 test/cfg2cmd/q35-simple-7.0.conf
> create mode 100644 test/cfg2cmd/q35-simple-7.0.conf.cmd
> create mode 100644 test/cfg2cmd/q35-simple-pinned-6.1.conf
> create mode 100644 test/cfg2cmd/q35-simple-pinned-6.1.conf.cmd
> create mode 100644 test/cfg2cmd/q35-simple.conf
> create mode 100644 test/cfg2cmd/q35-simple.conf.cmd
>
> --
> 2.30.2
next prev parent reply other threads:[~2021-11-04 14:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 15:58 Thomas Lamprecht
2021-11-03 15:58 ` [pve-devel] [PATCH v2 1/4] config: add new meta property withe creation time Thomas Lamprecht
2021-11-03 15:58 ` [pve-devel] [PATCH v2 2/4] config: meta: also save the QEMU version installed during creation Thomas Lamprecht
2021-11-03 15:58 ` [pve-devel] [PATCH v2 3/4] tests: cfg2cmd: add a few q35 related tests Thomas Lamprecht
2021-11-03 15:58 ` [pve-devel] [PATCH v2 4/4] cfg2cmd: switch off ACPI hotplug on bridges for q35 VMs Thomas Lamprecht
2021-11-04 8:05 ` [pve-devel] [PATCH v2 0/4] <add meta info and bandaid for QEMU 6.1 and unpinned q35 machine backward compat Dominik Csapak
2021-11-04 14:16 ` Wolfgang Bumiller [this message]
2021-11-04 14:33 ` [pve-devel] applied-series: " 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=20211104141626.iys35roshf66fch2@olga.proxmox.com \
--to=w.bumiller@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@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