We need to learn more about how our customer base or new customers are likely to use ESXi Arm edition for Edge use-cases.
Any plans to update this to 7.0.2 so there is no need to keep an unpatched/old vCenter Appliance?
Is there a way to get a vCenter Server running on ESXi Fling for ARM? I'm trying to cluster 3 Raspberry Pi's all running ESXi Fling on ARM. To Cluster them I need a vCenter Server which should be running as an VM on one of those. Is this possible? If yes, how?
No, there is no ARM vCenter. x86_64 only.
Hi, I'm sorry but vCenter Server does not support arm64 processors.
I am trying to clone a Debian10 VM to keep it as "Golden Image" following "Cloning and converting virtual machine disks with vmkfstools" (https://kb.vmware.com/s/article/1028042). My problem is that it fails to boot (goes over to PXE boot). In the document it is stated "creates a cloned drive with an LSI controller, even if the source disk is using VMware Paravirtual. This results in the virtual machine failing to boot. To resolve this issue, change the controller type to the same as the source." but to be honest this does not help me. Any hint on what am I doing wrong or alternative way of cloning VMs without vCenter?
Is your original Debian VM image for arm64? It's usually the main reason for not booting, and going to PXE boot directly.
I created the Debian10 VM from scratch on my ESXi Arm Fling. The workaround I have found is to manually copy all VM files onto a new folder but I guess that is not the optimal way of doing it.
Okay, I will try to reproduce the issue. Can you detail the configuration used when creating the VM?
2 CPU, 2 MB, 16 GB Thin provisioned, CD/DVD Media: Datastore ISO file -> Debian10 Image: debian-10.9.0-arm64-netinst.iso. Everything else default. No extra features added/modified.
This is the unsuccessful procedure I am following:
2) create a new folder under datastore
3) cd into new folder
4) run vmkfstools -i [input].vmdk [output].vmdk -d thin (--> not the *-flat.vmdk file)
5) Go to ESXi GUI and "Create / Register VM"
6) Remove HD and add new HD option "Existing HD" and select the newly created .vmdk file
8) Power on --> and.... "PXE boot" :(
Thanks! I was able to reproduce it :-) So the debian installer is installing grub in the efi\debian\ directory, and nothing in efi\boot\. This means that without the nvram (that includes the EFI boot variables), EFI does not know what to start. The fix is to copy your .nvram file too, when cloning, and it needs to have the same basename than your cloned VM.
Let me know if that works for you.
Thank you so much for your help. :)
Trying to get Home Assistant VM based on .vmdk (https://github.com/home-assistant/operating-system/releases/download/5.12/hassos_ova-5.12.vmdk.xz) but it does not boot (goes over to PXE). I have used vmkfstools -i but still unsuccessful.
I have also tried the .ova file (https://github.com/home-assistant/operating-system/releases/download/5.12/hassos_ova-5.12.ova) but I get an error.
Source 1: https://www.home-assistant.io/installation/linux/
Source 2: https://www.home-assistant.io/installation/alternative
I believe this vmdk is for x86 processors. Home Assistant needs to provide images for arm64, bootable with EFI. And unfortunately the Pi image does not boot with EFI.
That explains a lot. I guess that is going to be my contribution to HA that is, to export a HA ESXi Arm Fling VM (.ovf, .mf and .vmdk) and make it available there.