From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 7ED891FF146 for ; Tue, 09 Jun 2026 14:10:39 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id BB3F2ED8B; Tue, 9 Jun 2026 14:10:37 +0200 (CEST) From: Dominik Csapak To: pve-devel@lists.proxmox.com Subject: [PATCH manager] ui: qemu: boot order: warn of missing pxe support for ovmf Date: Tue, 9 Jun 2026 14:08:50 +0200 Message-ID: <20260609121033.2610172-1-d.csapak@proxmox.com> X-Mailer: git-send-email 2.47.3 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.049 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment 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: RZ66NO5LKZNC6NXLNPZ3GLFSIXEIMNVW X-Message-ID-Hash: RZ66NO5LKZNC6NXLNPZ3GLFSIXEIMNVW X-MailFrom: d.csapak@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 List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: OVMF can only use PXE/network boot when a virtual RNG device is added for VMs, but this is not obvious from the UI or the error behavior. Add a small warning to the boot order edit that says what is necessary. Signed-off-by: Dominik Csapak --- I guess we don't want to add warnings for every little thing, but this is very non-obvious when one needs its, since ovmf simply does not show the network device, and adding an RNG device would not really come to mind... To be fair, it is written in the docs, but I think a short warning here wouldn't hurt... www/manager6/qemu/BootOrderEdit.js | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/www/manager6/qemu/BootOrderEdit.js b/www/manager6/qemu/BootOrderEdit.js index 521a3d6e..c577c2c2 100644 --- a/www/manager6/qemu/BootOrderEdit.js +++ b/www/manager6/qemu/BootOrderEdit.js @@ -26,6 +26,7 @@ Ext.define('PVE.qemu.BootOrderPanel', { let grid = me.lookup('grid'); let marker = me.lookup('marker'); let emptyWarning = me.lookup('emptyWarning'); + let rngPxeWarning = me.lookup('rngPxeWarning'); marker.originalValue = undefined; @@ -43,6 +44,19 @@ Ext.define('PVE.qemu.BootOrderPanel', { view.inUpdate = false; marker.checkDirty(); emptyWarning.setHidden(val !== ''); + + let showRngPxeWarning = false; + if ( + view.vmconfig?.bios?.toLowerCase().includes('ovmf') && + !view.vmconfig?.rng0 && + val?.includes('net') + ) { + showRngPxeWarning = true; + } + + console.log('pxe?', showRngPxeWarning); + rngPxeWarning.setHidden(!showRngPxeWarning); + grid.getView().refresh(); }, }, @@ -238,6 +252,15 @@ Ext.define('PVE.qemu.BootOrderPanel', { userCls: 'pmx-hint', value: gettext('Warning: No devices selected, the VM will probably not boot!'), }, + { + xtype: 'displayfield', + reference: 'rngPxeWarning', + userCls: 'pmx-hint', + hidden: true, + value: gettext( + 'Warning: PXE boot with OVMF only works when a Virtio RNG device is added!', + ), + }, { // for dirty marking and 'reset' function xtype: 'field', -- 2.47.3