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 9842E1FF15C for ; Fri, 5 Sep 2025 12:56:08 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 9BED8126C2; Fri, 5 Sep 2025 12:56:22 +0200 (CEST) Message-ID: <09ed9154-5c52-444d-a26f-53c4cef3b595@proxmox.com> Date: Fri, 5 Sep 2025 12:55:49 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: pve-devel@lists.proxmox.com, Daniel Kral References: <20250902112307.124706-1-d.kral@proxmox.com> <20250902112307.124706-6-d.kral@proxmox.com> Content-Language: en-US From: Fiona Ebner In-Reply-To: <20250902112307.124706-6-d.kral@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1757069731619 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.023 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 Subject: Re: [pve-devel] [RFC qemu-server v2 4/4] machine: warn intel-iommu users about too large address width X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" Am 02.09.25 um 1:23 PM schrieb Daniel Kral: > Similarily to the guest address width exceeding the vIOMMU address > width, also warn users about the Intel vIOMMU address width being larger > than the maximum allowed value, the maximum guest address width, as > reported by the hardware. > > Signed-off-by: Daniel Kral > --- > I only added this as it was relatively cheap to implement now, but the > user will be stopped by starting the VM anyway by issuing something > like: > > kvm: -device vfio-pci,host=0000:00:02.0,id=hostpci0,bus=pci.0,addr=0x10: > vfio 0000:00:02.0: Failed to set vIOMMU: aw-bits 48 > host aw-bits 39 I feel like we don't gain much by having an additional warning here. The error from QEMU is already rather clear IMHO. If it's still cheap after deciding which way we go with patch qemu-server 3/4, then we can still go for it, but the warning should mention what the user can do to fix the issue. _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel