public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: Dominik Csapak <d.csapak@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH docs v3 1/1] qm: pve machine version: add section to explain +pveX versions
Date: Fri, 4 Apr 2025 18:08:03 +0200	[thread overview]
Message-ID: <20250404180803.73ca3c6a@rosa.proxmox.com> (raw)
In-Reply-To: <20250404125345.3244659-10-d.csapak@proxmox.com>

some suggestions for rephrasings inline:
On Fri,  4 Apr 2025 14:53:45 +0200
Dominik Csapak <d.csapak@proxmox.com> wrote:

> and clarify what windows guests will be pinned to.
> 
> Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
> ---
> changes from v2:
> * mention that windows gets pinned during guest creation
> 
>  qm.adoc | 15 +++++++++++++++
>  1 file changed, 15 insertions(+)
> 
> diff --git a/qm.adoc b/qm.adoc
> index 2617a7c..ff49c37 100644
> --- a/qm.adoc
> +++ b/qm.adoc
> @@ -173,6 +173,21 @@ This means that after a fresh start, the newest machine version supported by the
>  QEMU binary is used (e.g. the newest machine version QEMU 8.1 supports is
>  version 8.1 for each machine type).
>  
> +PVE Machine Version
> ++++++++++++++++++++
> +
> +Sometimes it's necessary to introduce new defaults or change the existing
> +hardware layout for new guests. For this, we have introduces an additional 'pve
s/introduces/introduced/
but on a meta-level:
https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Avoid_first_person

Maybe something like:
Some changes to the default settings or hardware layout are done by {pve}
on top of QEMU's defaults. Those are recorded in the 'pve machine
version'. 
?

> +machine version'. This version begins with 0 with every new QEMU machine
> +version, for example 'pc-q35-9.2+pve0'. When we want to change the hardware
> +layout or a default option, we bump it to the next one (e.g.
> +'pc-q35-9.2+pve1'), so older running guests are not impacted. When pinning a
When a change is done the number after +pve is increased (e.g.
'pc-q35-9.2+pve1') in order to not impact older running guests.

> +guest to a specific machine, this can be omitted. In that case it defaults to
> +0.
If omitted the 'pve machine version' defaults to 0.

> +
> +Windows guests get pinned to the most current version that is available for the
> +specific machine version during guest creation.
We have a similar statement in the paragraph above (for the qemu-machine
version) - maybe shorten this to:
Windows guests 'pve machine version' is pinnned, along with the QEMU
version during guest creation.



> +
>  QEMU Machine Version Deprecation
>  ++++++++++++++++++++++++++++++++
>  



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


  reply	other threads:[~2025-04-04 16:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-04 12:53 [pve-devel] [PATCH qemu-server/docs v3] disable S3/S4 power states by default Dominik Csapak
2025-04-04 12:53 ` [pve-devel] [PATCH qemu-server v3 1/8] tests: cfg2cmd: add test for windows machine pinning from meta info Dominik Csapak
2025-04-04 12:53 ` [pve-devel] [PATCH qemu-server v3 2/8] config to command: get rid of globalFlags Dominik Csapak
2025-04-04 12:53 ` [pve-devel] [PATCH qemu-server v3 3/8] machine: correctly select pve machine version for non pinned windows guests Dominik Csapak
2025-04-04 12:53 ` [pve-devel] [PATCH qemu-server v3 4/8] machine: incorporate pve machine version when pinning " Dominik Csapak
2025-04-04 12:53 ` [pve-devel] [PATCH qemu-server v3 5/8] machine: add S3/S4 power state properties Dominik Csapak
2025-04-04 12:53 ` [pve-devel] [PATCH qemu-server v3 6/8] machine: bump pve machine version and reverse the s3/s4 defaults Dominik Csapak
2025-04-04 12:53 ` [pve-devel] [PATCH qemu-server v3 7/8] api: qemu machine capabilities: add custom pveX versions too Dominik Csapak
2025-04-04 12:53 ` [pve-devel] [PATCH qemu-server v3 8/8] api: qemu machine capabilities: add description for pveX variants Dominik Csapak
2025-04-04 12:53 ` [pve-devel] [PATCH docs v3 1/1] qm: pve machine version: add section to explain +pveX versions Dominik Csapak
2025-04-04 16:08   ` Stoiko Ivanov [this message]
2025-04-04 15:56 ` [pve-devel] [PATCH qemu-server/docs v3] disable S3/S4 power states by default Stoiko Ivanov
2025-04-06 17:46 ` [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=20250404180803.73ca3c6a@rosa.proxmox.com \
    --to=s.ivanov@proxmox.com \
    --cc=d.csapak@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