public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: Dominik Csapak <d.csapak@proxmox.com>,
	Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH manager 06/10] ui: qemu: make os type selector architecture aware
Date: Thu, 29 Jan 2026 13:09:19 +0100	[thread overview]
Message-ID: <3ca99b13-c357-41e1-9380-4a82534219f6@proxmox.com> (raw)
In-Reply-To: <1f10f299-b792-4cca-b83f-fbd8c56870ce@proxmox.com>

Am 29.01.26 um 10:46 AM schrieb Dominik Csapak:
> On 1/29/26 10:40 AM, Fiona Ebner wrote:
>> Am 28.01.26 um 1:30 PM schrieb Dominik Csapak:
>>> diff --git a/www/manager6/Utils.js b/www/manager6/Utils.js
>>> index d8b212bc..de1ee0ba 100644
>>> --- a/www/manager6/Utils.js
>>> +++ b/www/manager6/Utils.js
>>> @@ -63,6 +63,17 @@ Ext.define('PVE.Utils', {
>>>               Other: [{ desc: '-', val: 'other' }],
>>>           },
>>>   +        kvmOSTypesPerArchitecture: {
>>> +            x86_64: {
>>> +                bases: undefined, // include all
>>> +                ostypes: undefined, // include all
>>> +            },
>>> +            aarch64: {
>>> +                bases: ['Linux', 'Other'],
>>> +                ostypes: ['l26', 'other'],
>>
>> What about Windows? Do we really want to hide that compeletely in the
>> UI? Unfortunately [;P], I expect that to be a non-negligible use case
>> and many requests to come in (which will miss that it's available on the
>> CLI). Or is it not properly supported in the backend? If yes, that
>> should be fixed, note that I have sent a patch at least for the
>> unavailable hyperv flags [0]. I mean, we can also wait and see if I'm
>> right. Maybe people don't care about it as much on ARM, I'd be glad ;)
>>
>> [0]:
>> https://lore.proxmox.com/pve-devel/20260127134626.127432-3-
>> f.ebner@proxmox.com/
>>
> 
> yeah, sorry should have expanded on the why here a bit:
> 
> yes, there are a few things in the backend still missing for windows arm
> support, namely:
> * display: the only device i could get windows to show anything was 'ramfb'
> * iso/storage: since aarch64 does not support ide (at least in my tests
> i couldn't get it to work, maybe there is a way), we have to use a
> different bus for the iso/cdrom drives. virtio-scsi works theoretically,
> but the windows installer stops at some point because the drivers are
> missing. OVMF can't boot from other scsi controllers or sata.
> 
> so the only other way would be to implement usb-storage support, but
> that's not here yet
> 
> so all in all i opted to hide windows for the moment because one cannot
> make it work with the current options anyway

Seems like there are virtio-win drivers for win11:
https://virtio-win.github.io/Knowledge-Base/Windows-arm64-vm-using-qemu.html

But also requires going into regedit during installation to disable TPM ;P

Yeah, let's just not expose it in the UI for now if there is no
first-class support for it yet.




  reply	other threads:[~2026-01-29 12:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-28 12:18 [pve-devel] [PATCH manager 00/10] enable qemu vm architecture selection Dominik Csapak
2026-01-28 12:18 ` [pve-devel] [PATCH manager 01/10] api/pvestatd: broadcast and expose non-x86 host architecture Dominik Csapak
2026-01-28 16:05   ` Fiona Ebner
2026-01-29  9:20     ` Dominik Csapak
2026-01-28 12:18 ` [pve-devel] [PATCH manager 02/10] ui: resource store: add architecture field Dominik Csapak
2026-01-28 12:18 ` [pve-devel] [PATCH manager 03/10] ui: qemu: add architecture field in wizard and hardware view Dominik Csapak
2026-01-28 16:32   ` Fiona Ebner
2026-01-28 12:18 ` [pve-devel] [PATCH manager 04/10] ui: qemu: make scsi hw selector architecture aware Dominik Csapak
2026-01-28 12:18 ` [pve-devel] [PATCH manager 05/10] ui: qemu: make osdefaults " Dominik Csapak
2026-01-29  9:25   ` Fiona Ebner
2026-01-28 12:18 ` [pve-devel] [PATCH manager 06/10] ui: qemu: make os type selector " Dominik Csapak
2026-01-29  9:41   ` Fiona Ebner
2026-01-29  9:47     ` Dominik Csapak
2026-01-29 12:09       ` Fiona Ebner [this message]
2026-01-29 10:18     ` Dominik Csapak
2026-01-29 12:10       ` Fiona Ebner
2026-01-28 12:18 ` [pve-devel] [PATCH manager 07/10] ui: qemu: make machine panels/fields " Dominik Csapak
2026-01-29 11:12   ` Fiona Ebner
2026-01-29 12:16     ` Dominik Csapak
2026-01-29 12:25       ` Fiona Ebner
2026-01-28 12:18 ` [pve-devel] [PATCH manager 08/10] ui: qemu: make bios selector " Dominik Csapak
2026-01-28 12:18 ` [pve-devel] [PATCH manager 09/10] ui: qemu: make sortByPreviousUsage " Dominik Csapak
2026-01-28 12:18 ` [pve-devel] [PATCH manager 10/10] ui: qemu: wizard: use defaults to populate machine and bios Dominik Csapak
2026-01-29 13:13 ` [pve-devel] [PATCH manager 00/10] enable qemu vm architecture selection Fiona Ebner
2026-01-29 13:15   ` Fiona Ebner

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=3ca99b13-c357-41e1-9380-4a82534219f6@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=d.csapak@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal