arm64 support

[pipounix]

very good morning or night depending on where you read this!! I am trying to run an arm operating system but I see that there is no arm support so I looked for information with qemu-system-arm and qemu-system-aarch would have support for arm within proxmox the problem is that if I install those options it uninstalls proxmox completely yes I compile the cpu support options by hand but I can only use them from a terminal I have no way to launch that machine created with qemu in the terminal from the proxmox interface does anyone know how to combine the added cpu support so that it appears in the options to choose when creating a vm

root@noibm:~# qemu-system-arm -cpu help
Available CPUs:
arm1026
arm1136
arm1136-r2
arm1176
arm11mpcore
arm926
arm946
cortex-a15
cortex-a7
cortex-a8
cortex-a9
cortex-m0
cortex-m3
cortex-m33
cortex-m4
cortex-m55
cortex-m7
cortex-r5
cortex-r52
cortex-r5f
max
pxa250
pxa255
pxa260
pxa261
pxa262
pxa270-a0
pxa270-a1
pxa270
pxa270-b0
pxa270-b1
pxa270-c0
pxa270-c5
sa1100
sa1110
ti925t
root@noibm:~#
these are the cpu options added for arm

 

[fiona]

Hi,
see https://forum.proxmox.com/threads/question-about-vm-importation.140299/post-627550

 

[pipounix]

thanks for answering!!!!
The instructions are good but that does not solve the problem. What I want is for Proxmox to let me create a vm from scratch to which I want to install an Arm OS. This could be a Linux on Arm or in particular I would like to run Android but in its arm version to be able to test android applications that do not run on android x86

 

[pipounix]

This would be a way to do it on any debian that has qemu installed qemu-system-arm -M virt -cpu cortex-a57 -m 1024 -drive file=debian-arm64.img,if=none,id=drive0 -device virtio -blk-device,drive=drive0 -device virtio-net-device,netdev=net0 -netdev user,id=net0,hostfwd=tcp::2222-:22 -nographic -serial mon:stdio

 

[fiona]

This would be a way to do it on any debian that has qemu installed qemu-system-arm -M virt -cpu cortex-a57 -m 1024 -drive file=debian-arm64.img,if=none,id=drive0 -device virtio -blk-device,drive=drive0 -device virtio-net-device,netdev=net0 -netdev user,id=net0,hostfwd=tcp::2222-:22 -nographic -serial mon:stdio

What if you use qemu-system-aarch64 for that command?

 

[pipounix]

It is the same thing what I am referring to is because there is no option to create the machine directly from the proxmox environment, even if I create it with aarch, the machine when I try to import it later does not start because the virtual cpu that I tried to use proxmox does. I don't know that I edited the conf by hand of the created vm and it doesn't start from the proxmox interface from the terminal, yes it works but to be able to use it I have to put a vnc client on the remote machine and put together a whole script when the idea of proxmox is to use it For testing, I would also not have the backup, export and import options of the created vm available, that is why I want to reach out to the people at Proxmox to see if it can be added as another option in the cpus list when creating the vms.

 

[fiona]

Changing architecture options is not possible via UI, but you should be able to manage the VM via Proxmox VE after initially creating it via CLI:

qm create 123 --arch aarch64 --machine virt ...

The cortex-a57 CPU is already the default one when using aarch64, so no need to specify it. If you need another one, use e.g.

qm set 123 --args "cpu cortex-a15"

 

[pipounix]

root@noibm:/disco2/images# qm status 123
status: running
root@noibm:/disco2/images#
arch: aarch64
#args: -vga virtio
bios: /usr/share/pve-edk2-firmware/OVMF_CODE.fd
boot: order=scsi1;scsi0;net0
cores: 2
cpu: max
machine: virt
memory: 2048
meta: creation-qemu=8.1.2,ctime=1706548529
name: MiVM
net0: virtio=BC:24:11:FB:72:12,bridge=vmbr0
numa: 0
scsi0: backup:123/vm-123-disk-0.qcow2,size=32G
scsi1: CDs:iso/debian-12.4.0-arm64-netinst.iso,media=cdrom,size=537900K
smbios1: uuid=bc6e6f8d-b7a7-4c2d-aabd-edb084e25748
sockets: 1
vga: virtio

The vm starts in arm64 but I can't find a way to give me video

 

[fiona]

bios: /usr/share/pve-edk2-firmware/OVMF_CODE.fd

bios can only be seabios or ovmf. It's best not to manually edit the configuration files, but use the UI or for settings not exposed in the UI, qm set 123 --setting value which will complain about invalid values.

When using qm set 123 --bios ovmf, Proxmox VE will select the appropriate EFI code matching the VM's architecture (which is /usr/share/pve-edk2-firmware/AAVMF_CODE.fd for aarch64).

 

[nalle]

Fiona, what about creating a wiki about ARM?

 

[fiona]

Unfortunately, it's not really a focus for further development from our side right now. Bug reports, especially about regressions, are welcome of course.

 

[emunt6]

Unfortunately, it's not really a focus for further development from our side right now. Bug reports, especially about regressions, are welcome of course.

What about the Promox VE host installation on aarch64/arm64 architecture support?
AMPERE CPU - (https://amperecomputing.com/)

https://www.youtube.com/watch?v=Hz5k5WgTkcc

 

[LnxBil]

What about the Promox VE host installation on aarch64/arm64 architecture support?

@fiona's answer was about arm in general.

 

[fiona]

Hi,

What about the Promox VE host installation on aarch64/arm64 architecture support?

that's not officially supported from our side. If you can get it to work, good for you! Only running ARM guests on an x86_64 host is officially supported by us.

 

[eit-jc]

Hi,

that's not officially supported from our side. If you can get it to work, good for you! Only running ARM guests on an x86_64 host is officially supported by us.

We are much interested in this. Do you know if any work is in progress to enable running Proxmox on ARM?

 

[fiona]

There is no such work in progress from our side. It was evaluated a few years ago, but not deemed worth pursuing further. But there are some community projects, e.g. I've seen mentions of PiMox on the forum. Please be aware this is not officially endorsed in any way.