I agree with you for a production use, but as a developer, being able to have a proxmox (or even a cluster) right inside my (m1) macbook is really interesting, and having the same on my desk with few raspberry pis can allow to do some cluster testing easily (switch off one Pi for example)The proxmox team is earning money by selling licences to big companies that are running alot of big servers. If I were a big company that pays alot of money I would want that the money is invested in developing software for hardware that can actually being used in a data center. So Raspis or M1s aren't really a thing worth to support. We need big racks of enterprise grade ARM servers first.
nice catch, so now I need to be able to run a Debian Official Cloud Images using Apple Virtualization framework (both intel and arm), as used here :
root@armVM:~$ curl https://gitlab.com/minkebox/pimox/-/raw/master/dev/KEY.gpg | apt-key add - root@armVM:~$ curl https://gitlab.com/minkebox/pimox/-/raw/master/dev/pimox.list > /etc/apt/sources.list.d/pimox.list root@armVM:~$ apt update root@armVM:~$ apt install pve-manager
You need at least cores with the second digit being >= 5, e.g. A75 or A55, as only then, it's modern enough to support the ARM v8.2 spec including stuff like the NEON instruction set, which is a must-have for anything server related, especially clustering in Proxmox VE or hashing and (on-the-wire and at-rest) encryption in Proxmox Backup Server.- 16 x A72 cores @ 2.0GHz
Even if it looks somewhat OK spec wise for an entry platform for home lab stuff, I would be surprised if it actually performs better than a 3 to five-year-old amd64 based server, I mean would be expected, the CPU design is from 2016, so def. not bleeding edge anymore.What about the Solid Run HoneyComb LX2?
Ok, this sounds like a real constraint I was not aware of.You need at least cores with the second digit being >= 5, e.g. A75 or A55, as only then, it's modern enough to support the ARM v8.2 spec including stuff like the NEON instruction set, which is a must-have for anything server related, especially clustering in Proxmox VE or hashing and (on-the-wire and at-rest) encryption in Proxmox Backup Server.
Of course x86 is still here and there is nothing against it but I see that x86 is loosing momentum as architecture. No one is asking to forget the x86 architecture right now but rather to have the possibility to get some hands on experience on ARM64 platforms.Even if it looks somewhat OK spec wise for an entry platform for home lab stuff, I would be surprised if it actually performs better than a 3 to five-year-old amd64 based server, I mean would be expected, the CPU design is from 2016, so def. not bleeding edge anymore.
The 4x 10 GBps look nice, ARM was always quite good at providing fast network interfaces, but the IO interfaces available do not seem like one could actually use all that. Could be OK for a pure networking appliance, e.g., as router or the like though.
FWIW, you can also get something like an ASRock Rack EPYC3101D4I-2T (500 to 600 bucks here) or something similar to a Supermicro X11SDV-4C-TLN2F, yes those have fewer cores than 20, but they will probably still get you about the same amount of actual workload done, and that with way less hassle. And those are only models with embedded passive CPUs, there's much more available if one does not have to restrict themselves to that criteria.
But as mentioned a few times, we already invested a bit of work to make our software not locked to a single platform, so bootstrapping PVE and PBS is already possible (there are even some tutorial floating around), if you think the ARM64 is just worth it for you, you can use it. But it's still not worth the time required for us to provide professional enterprise support for those systems, especially as the best HW available, still gets outperformed by years old entry level amd64 based one.
I do not think it makes much sense to release something as official and then not support it, that's IMO contradicting and would mean that users are in limbo on serious issues like data corruption, some HW specific bug or what not, if user run into problems specific to the arm kernel/QEMU/ceph/... we would still need to look into it and thus invest lots of resources, everything else would just shine bad light onto the projects. Also build HW and setups would need to be maintained, and build time is just so slow on those things, we already need an hour for ceph on a high performant x86, I can only imagine that requiring 8+ hours on the Ampere xgene2 we have, would be (somewhat ironically) probably faster to cross compile from our x86 based HW.An official ARM64 community edition (without professional support) with some requirements would be absolutely enough to test and build up experience.
Of course an A72 based CPU is not cutting edge (beside the arch constraints above) but not everybody will be able to get an Ampere Altra system...
Ah ok I see what you're saying. Yes I'm aware of most consumer processors but I was not familiar with some of the intricacies used by arm hardware for boot processes and drivers. Regarding phone adoption, that's also a big part of the reason why the Ubuntu and Windows phones never really went anywhere..."ARM support" in the sense you're discussing already exists for Linux. Nearly every phone has an ARM CPU with a Linux kernel running on it. Debian supports a bunch of ARM boards with their thousands of packages. The instruction set is handled.
The rest of the system is the issue. Bunch of different boot methods (some Raspberry Pi boards boot from the GPU!), locked boot firmware, no standardization of buses or peripherals, lots of proprietary drivers, etc. Why do you think the Android ROM scene is so disorganized? Think about why, say, LineageOS only supports a relative handful of phones and it takes years to add a new one.
Once you understand that you will know why Proxmox is taking a wait and see attitude on ARM.
Rofl...thanks. Didn't know that.(some Raspberry Pi boards boot from the GPU!
I flashed my old smartphones with cyanogenmod and so on to be able to receive security updates. For example I bought a 800€ flagship smartphone and samsung stopped releasing updates after 8 moths or so...and no device should go online without security fixes and I don't wanted to throw it in the trash after only 8 months. I really hope that will get better with the closed source drivers, so everyone can just use some opensource andoids that will get security updates over many years, because smartphone manufacturers won't start increasing the support lenght if they aren't forced to do that by the goverments...ARM Servers (very broad term I understand) in the enterprise setting for say, cloud infrastructure, are really catching on and probably standardizing massively right now. Will be interesting to see how software stacks like PVE, CloudStack and others grow with the change in cloud CPU architecture.
Thanks, but all credits should go to @Tux_1024 (I only `apt install proxmox-ve` what he packaged), then got issues with apparmor (I'm have to make my homework on this)Awesome! Good job man.
Excited too, and 64GB macbooks are near already here ^^ (okay, letting a 120hz display closed isn't a good idea), and the "Mac Pro" and iMac Pro hasn't made the transition to m1 (or m2...)In that same line of thought, the new M1 Pro and M1 Max came out and according to Apple they will be somewhere in the 30,000 on the benchmark score which is 1.5x my Dell XPS 15's i9-11900H. I gotta hand it to Apple, if this keeps up and they release a gen3 M1 MacMini I might be forced to make a Mini-Cluster as my homelab rofl.
Imagine a MacMini with: 64GB DDR5 per node, an absurd amount of GPU and Neural Cores, PCIe Gen4 SSD, and likely 4x Thunderbolt 4 ports. I could build a Ceph cluster with Thunderbolt drive arrays and Thunderbolt to 40Gbps networking and the whole thing could probably fit in a filing cabinet drawer. It's difficult to state how excited I am about these kinds of prospects, I'm starting to really come around to the idea of an ARM PVE within the next 3-5 years.
Oh and don't forget the 200GB/s and 400GB/s memory bandwidth. Heckin' doodle, that's nuts.
Finally got a debian lxc container running on my m1 macbook : https://forum.proxmox.com/threads/how-to-run-pve-7-on-a-raspberry-pi.95658/post-425043