Q: Can I run Proxmox VE on a Raspberry Pi or a similar single-board computer?
A: No. An arm64 host must boot through UEFI and describe its hardware through ACPI. Device-tree-only boards and legacy boot are not supported.
Basically no consumer facing arm SBCs, NAS boxes, etc will work with this. Frankly, I see this as a good thing though: Maybe it'll make the SBC market get its stuff together and start actually doing UEFI instead of every board needing a custom build.
Let's say that one does want to use a raspberry pi as a hypervisor and run a bunch of VMs on it... But why? A raspberry pi 5 with current market pricing for the 8GB or 16GB model is a really bad price/performance decision.
Not when you can go to ebay and get a 16GB RAM gently used, ultra small form factor corporate desktop, quad core intel core i5/i7 computer for less money. With real NVME SSD and such. Yeah, it'll consume more like 25 watts idle, not 7W, but as a hypervisor platform it'll also be vastly more capable.
The raspberry pi with 1GB RAM have some very good use cases for things that need their I/O pins, but if you're just trying to use it as a general purpose computer, there's so many other better options.
You can run it on a anything. Now officially. About a year back i had proxmox cluster on 3 orange pi 5+. As long as you have a some sort of Debian it's pretty seamless.
This would be interesting on a Spark or two. I don't know how seamless the GPU and networking cluster setup would be when resource sharing between agent and post-training VMs.
> Device-tree-only single-board computers, such as the Raspberry Pi, are not supported
> Virtual machines always boot through UEFI, provided by the ARM build of OVMF (AAVMF). SeaBIOS is not available on arm64.
> Device-tree-only single-board computers, such as the Raspberry Pi, are not supported
Good. The more software vendors require UEFI, the more arm board manufacturers will have to support it.
As an embedded developer I don't hate device-tree-only devices per se, and I have the skills to make any distro (that supports ARM) work on any board, but I absolutely do not have the patience to do it.
FWIW there exist UEFI implementations for Raspberry Pi 4 and 5, they can be used to boot Windows 11 aarch64 images as well as 'generic' Linux distro images, so I suppose they will support this one as well.
17 comments
[ 0.25 ms ] story [ 6.4 ms ] threadQ: Can I run Proxmox VE on a Raspberry Pi or a similar single-board computer? A: No. An arm64 host must boot through UEFI and describe its hardware through ACPI. Device-tree-only boards and legacy boot are not supported.
Basically no consumer facing arm SBCs, NAS boxes, etc will work with this. Frankly, I see this as a good thing though: Maybe it'll make the SBC market get its stuff together and start actually doing UEFI instead of every board needing a custom build.
Not when you can go to ebay and get a 16GB RAM gently used, ultra small form factor corporate desktop, quad core intel core i5/i7 computer for less money. With real NVME SSD and such. Yeah, it'll consume more like 25 watts idle, not 7W, but as a hypervisor platform it'll also be vastly more capable.
The raspberry pi with 1GB RAM have some very good use cases for things that need their I/O pins, but if you're just trying to use it as a general purpose computer, there's so many other better options.
This was necessary, but guys you got the memo too late
A good alternative is incus and running LXC and or OCI containers, GPU works in those and can be shared with multiple instances
Good. The more software vendors require UEFI, the more arm board manufacturers will have to support it.
As an embedded developer I don't hate device-tree-only devices per se, and I have the skills to make any distro (that supports ARM) work on any board, but I absolutely do not have the patience to do it.