From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pve-devel-bounces@lists.proxmox.com>
Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40])
	by lore.proxmox.com (Postfix) with ESMTPS id 6C27E1FF0F5
	for <inbox@lore.proxmox.com>; Mon, 02 Nov 2026 23:01:55 +0100 (CET)
Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1])
	by gate001.proxmox.com (Proxmox) with ESMTP id 825212174F;
	Mon, 02 Nov 2026 23:01:48 +0100 (CET)
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com,
	Stefan Hanreich <s.hanreich@proxmox.com>
Subject: applied: [PATCH proxmox-ve-rs 0/2] fix network interface name parsing
Date: Mon,  2 Nov 2026 23:01:30 +0100
Message-ID: <179365685575.1809735.5848926487566285591.b4-ty@b4>
X-Mailer: git-send-email 2.47.3
In-Reply-To: <20261009090006.104013-1-s.hanreich@proxmox.com>
References: <20261009090006.104013-1-s.hanreich@proxmox.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2
X-Bm-Transport-Timestamp: 1793656904584
X-SPAM-LEVEL: Spam detection results:  0
	AWL                     0.361 Adjusted score from AWL reputation of From:
 address
	DMARC_MISSING             0.1 Missing DMARC policy
	KAM_DMARC_STATUS         0.01 Test Rule for DKIM or SPF Failure with Strict
 Alignment (newer systems)
	RCVD_IN_DNSWL_MED        -2.3 Sender listed at https://www.dnswl.org/,
 medium trust
	SPF_HELO_NONE           0.001 SPF: HELO does not publish an SPF Record
	SPF_PASS               -0.001 SPF: sender matches SPF record
Message-ID-Hash: M4NNWDWRZTH6U5ZDMMBDV425OXO7LLCC
X-Message-ID-Hash: M4NNWDWRZTH6U5ZDMMBDV425OXO7LLCC
X-MailFrom: t.lamprecht@proxmox.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop;
 banned-address; emergency; member-moderation; nonmember-moderation;
 administrivia; implicit-dest; max-recipients; max-size; news-moderation;
 no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.10
Precedence: list
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Owner: <mailto:pve-devel-owner@lists.proxmox.com>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Subscribe: <mailto:pve-devel-join@lists.proxmox.com>
List-Unsubscribe: <mailto:pve-devel-leave@lists.proxmox.com>

On Fri, 09 Oct 2026 11:00:02 +0200, Stefan Hanreich wrote:
> 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.
> 
> 
> [...]

Applied, thanks!

[1/2] fix #7584: ve-config: guest: add missing network interface models
      commit: 955a64b34db5d88ea98bc6f7de800f14d429224f
[2/2] ve-config: guest: add fallback enum variant
      commit: 1105f17a51cee2cc6ec08c26b6bd6bc38f204d06