From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH proxmox-ve-rs 0/2] fix network interface name parsing
Date: Fri, 9 Oct 2026 11:00:02 +0200 [thread overview]
Message-ID: <20261009090006.104013-1-s.hanreich@proxmox.com> (raw)
The enum in proxmox-ve-config was missing several models that are defined in
qemu-server, which leads to failure in parsing when encountering them in the
guest configurations. Particularly, the e1000e model is used more often in
practice, as it is exposed in the UI, which lead to a few reports via different
channels.
proxmox-ve-rs:
Stefan Hanreich (2):
fix #7584: ve-config: guest: add missing network interface models
ve-config: guest: add fallback enum variant
Cargo.toml | 1 +
proxmox-ve-config/Cargo.toml | 1 +
proxmox-ve-config/src/guest/vm.rs | 48 +++++++++++++++++++++++++++++--
3 files changed, 47 insertions(+), 3 deletions(-)
Summary over all repositories:
3 files changed, 47 insertions(+), 3 deletions(-)
--
Generated by murpp 0.12.0
next reply other threads:[~2026-10-09 9:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 9:00 Stefan Hanreich [this message]
2026-10-09 9:00 ` [PATCH proxmox-ve-rs 1/2] fix #7584: ve-config: guest: add missing network interface models Stefan Hanreich
2026-10-09 9:00 ` [PATCH proxmox-ve-rs 2/2] ve-config: guest: add fallback enum variant Stefan Hanreich
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=20261009090006.104013-1-s.hanreich@proxmox.com \
--to=s.hanreich@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