search

utmapp / UTM

Virtual machines for iOS and macOS
https://getutm.app
Apache License 2.0
27.21k stars 1.35k forks source link

Pink screen of death when starting ESXi via emulation #4056

Closed d3adwolf closed 2 years ago

d3adwolf commented 2 years ago

I know exactly what can be raised on QEMU under Arm VMware ESXi through emulation of CPU Westmere based on Q35, but people write that it is necessary to disable the arguments ignore_msrs and report_ignored_msrs, but I do not know where to find them in UTM, because if you install separately QEMU, they will be located at: /sys/module/kvm/parameters/ and /etc/modprobe.d/kvm.conf.

Configuration

So I want to know your experience with ESXi in QEMU/UTM, you can, of course, download Arm version of ESXi, but it is more for Rasberry Pi and other such things, I want to take the basic to be a home lab for virtualization.

Below I will also stick a screenshot of the pink screen in ESXi, maybe someone can figure it out, because I did not google it. :( alt text

conath commented 2 years ago

Our fork of QEMU does not support the "usual" KVM mode. We use our own combo of HyperKit/HVF and Spice (for VMs with graphics). Basically, when the internal QEMU is launched, we pass --accel hvf and not --enable-kvm.

Therefore the properties you are referencing can't be changed in UTM - though there may be similar configs for the HVF accelerator - maybe @agraf can take a quick look.

(In case you're wondering, HVF and KVM can't be used at the same time.)

agraf commented 2 years ago

You're trying to run ESXi for x86_64 on an M1. That means every instruction is going through (relatively slow) binary translation. Even if you manage to get that setup working, you won't get happy with it: It will be too slow to be usable.

The ARM port of ESXi also won't work because M1 does not support nested virtualization. Within a virtual machine on M1, you can not execute a hypervisor.

osy commented 2 years ago

Thanks for the explanation.

d3adwolf commented 2 years ago

Yes, thank you very much for the explanation.

About, ESXi for ARM - everything is clear, but about the architecture x86_64 managed to run the current version 6.5. There are not baked legacy drivers, which are available in QEMU, so it runs, the only thing I need to solve is the question with the storage, the installation does not see IDE and any other virtual disks, probably again not enough ESXi drivers, I think to try to raise some standalone server in a local area with NFS/iSCSI, as file storage and it already installed ESXi, as I will successfully do this - will report! :) Thanks again.

hronro commented 1 year ago

@agraf What if I'm using an Intel MacBook Pro? Seems those won't be an issue on Intel chips.

erikmartinessanches commented 1 year ago

I was hoping to run WSL2 (to run Docker) inside a Win 11 arm VM on Macbook Pro M1 (using UTM). Windows says "enable nested virtualization" but M1 doesn't seem to support this, judging from the responses here? Tough luck?

Is it possible to enable virtualization inside Windows 11 arm guest?

Allen050329 commented 1 year ago

@agraf What if I'm using an Intel MacBook Pro? Seems those won't be an issue on Intel chips.

Yeah, same for AMD hacks, tbh

willie commented 7 months ago

I was hoping to run WSL2 (to run Docker) inside a Win 11 arm VM on Macbook Pro M1 (using UTM). Windows says "enable nested virtualization" but M1 doesn't seem to support this, judging from the responses here? Tough luck?

Is it possible to enable virtualization inside Windows 11 arm guest?

I came here looking for this as well.