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 0318E1FF13F for ; Thu, 29 Jan 2026 14:13:26 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id E29D03B07; Thu, 29 Jan 2026 14:13:49 +0100 (CET) Message-ID: <70676d12-bda7-4f8a-bf87-b7b985afa7fc@proxmox.com> Date: Thu, 29 Jan 2026 14:13:40 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [pve-devel] [PATCH manager 00/10] enable qemu vm architecture selection To: Proxmox VE development discussion , Dominik Csapak References: <20260128123035.2576774-1-d.csapak@proxmox.com> Content-Language: en-US From: Fiona Ebner In-Reply-To: <20260128123035.2576774-1-d.csapak@proxmox.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1769692352711 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.015 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: PN3KKMM7QHD6TPY2EXWREPQIMK6YIUGH X-Message-ID-Hash: PN3KKMM7QHD6TPY2EXWREPQIMK6YIUGH X-MailFrom: f.ebner@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: Am 28.01.26 um 1:29 PM schrieb Dominik Csapak: > This series brings the emulated aarch64 vms to the gui. This could > be configured on the api only previously. > > The code also handles if the host has a non-x86 architecture, and is > generally structured in a way that should make it (relatively) easy > to add other architectures in the future. > > Some fields/panels needed adaptions to hide some values or change some > defaults, since not every combination that can be configured makes > sense. (e.g. seabios on aarch64 cannot work currently) > > Generally the backend allows many combinations that don't make sense on > all architectures, so i tried to limit the users here to the 'correct' > ones, but we should think about limiting them in the backend too. > > Also, the backend made some inconsistent choices with different > architectures, such as the default controller changes with the > architecture, but things like 'bios' or 'scsihw' do not. So I worked > around these things a bit differently. > > What is still missing: > * make the disk controllers selective per architecture > (e.g. aarch64 has no ide controller, ovmf+aarch64 cannot boot from sata) Related, but maybe independent patch-wise: * do not add the ISO(s) from the wizard as IDE. > * cpumodel + cpuflags need to be architecture aware For reference: https://lore.proxmox.com/pve-devel/20260129131021.118199-1-f.ebner@proxmox.com/ (v2 because I had forgotten to adapt the endpoint for flags) > > other nice to haves not yet done, that also invovle changing the backend: > * 'virt' machine support in our api, so one can choose older versions AFAICT, this is already supported by the API? > * allow 'pcie' passthrough on 'virt' Nice work so far! :)