well, it actually worked with the binary translator and 32bit guests in VirtualBox 4.2
but with 4.3 RC1 it just dies with a pink screen of death: http://i.imgur.com/ovSWLr1.pngVMware ESXi 5.1 does not boot
-
CME
- Posts: 49
- Joined: 28. Aug 2009, 00:24
- Primary OS: Debian other
- VBox Version: PUEL
- Guest OSses: windows 98se, 2k, xp, 7, solaris, opensolaris, reactos, ubuntu, debian,...
- Contact:
VMware ESXi 5.1 does not boot
HI,
well, it actually worked with the binary translator and 32bit guests in VirtualBox 4.2 but with 4.3 RC1 it just dies with a pink screen of death: http://i.imgur.com/ovSWLr1.png
well, it actually worked with the binary translator and 32bit guests in VirtualBox 4.2
but with 4.3 RC1 it just dies with a pink screen of death: http://i.imgur.com/ovSWLr1.png
- Attachments
-
vmware esxi-2013-10-13-02-50-04.log- (47.92 KiB) Downloaded 29 times
Re: VMware ESXi 5.1 does not boot
VirtualBox 4.3 is a LOT more strict now with MSR accesses, and that's where ESXi dies now. It should be prepared to get #GP for any MSR access, but obviously isn't. There is no guarantee that any MSR is accessible in a VM - that's what the CPU vendors say, and VM products should be able to arbitrarily restrict access without guests exploding. Many MSRs make no sense whatsoever in a VM.