Good day to all!
I have troubles with my ESXI 5.5. Booting process of ESXI server goes as usually instead of showing PSOD purple screen including next text:
VMware ESXi 5.5.0 [Releasebuild-1331820 x86_64]
NOT_IMPLEMENTED bora/vmkernel/core/bootModule.c:122
cr0=0x800010003d cr2=0x0 cr3=0x100102000 cr4=0x216c
*PCPU0:32768/bootstrap
PCPU 0: SSSSH
Code start: 0x418039a00000 VMK uptime: 0:00:00:04.841
0x417fddc08b80:[0x41801dc8cf99]PanicvPanicInt@vmkernel#nover+0x575 stack: 0x417f00000008
0x417fddc08be0:[0x41801dc8d1dd]Panic_NoSave@vmkernel#nover+0x49 stack: 0x417fdds08c60
0x417fddc08cf0:[0x41801dc0b1be]BootModule_LoadAll@vmkernel#nover+0x42e stack: 0x41801dc0bd3e
0x417fddc08df0:[0x41801dc00c72]LegacyBootVMKernel@vmkernel#nover+0xaa2 stack: 0x10000000001
0x417fddc08fe0:[0x41801dc01169]BootVMKernel@vmkernel#nover+0xfd stack: 0x41801de53438
base fs=0x0 gs=0x418040000000 Kgs=0x0
No place on disk to dump data.
No file configured to dump data.
Debugger waiting(world 32768) — no port for remote debugger.
It happened after cutting off electricity while shooting down process of ESXI server. As i see from error message, there are problems with one of the kernel file, maybe i mistaken. Please help with this problem, unfortunately i had no backups of this server, in case of reinstalling ESXI i will have to do a huge work and it will cost me a looot of time. Please anyone help. i would be very appreciate for any help.
I was trying to install Esxi 7.0 on virtual box but I’m getting the following error.
PSOD error
I tried with Esxi 6.5 but was getting similar kind of error.
VM Config: 4Cpus, 4GB RAM,40GB HDD
My Machine Specs: i7 8th Gen 8 cores, 32 RAM
asked Apr 13, 2021 at 6:12
The ESXi installer is itself ESXi and you’re in a chicken and egg situation where the installer is crashing and you have no core dump file or partition configured. You can tell this from the bottom 3 lines:
- No place on disk to dump data.
- No file configured to dump data.
- No port for remote debugger. «Escape» for local debugger.
If you’re really brave press the «Escape» key and you can get to the kernel text logs which can frequently tell you a lot about the cause of the crash. But reading the logs at the PSOD prompt is a pain and something I try to avoid by always having a place to dump the core file (the «data» referred to above).
I’d suggest that you either install ESXi to a USB flash drive on bare hardware (see https://www.nakivo.com/blog/run-esxi-from-usb-flash-drive-guide/) or grab an ESXi dd-image and put that on either a physical or virtual USB flash drive (https://www.virten.net/2014/12/clone-esxi-installations-on-sd-cards-or-usb-flash-drives/). You can then pass the USB image through to your virtual environment. By doing it this way you will already have created a core dump partition so that if ESXi crashes you can get a core dump. The ESXi kernel logs, which are text files, are part of the core dump and https://communities.vmware.com/t5/ESXi-Discussions/Kernel-Dump-Analysis-Tool/td-p/1429887 has some guidance on extracting them from the dump.
Lastly, if you simply must do everything in a virtual environment you could try creating a core dump partition on a second disk (type 0xFC and size 2+GB) and maybe if you’re lucky the installer will pick it up. If you can get to a command prompt before the PSOD then you can use esxcli to create, configure and make active a core dump partition but pay ignore size recommendations under 2 GB. Nothing is as frustrating as a truncated core dump. See https://kb.vmware.com/s/article/2004299 for more info.
Dharman♦
29.2k21 gold badges79 silver badges131 bronze badges
answered Apr 13, 2021 at 13:23
ErikErik
775 bronze badges
1
Posted by Jmeinzen 2018-03-20T10:05:51Z
Home computer (intel Xeonquad core, 4 GB RAM, 500 GB Sata)
I am trying to install EXSI trial version 6.5 from a USB. The computer boots and run ESXi install setup but fails to complete.
Error: purple screen
Failed to mem_map pci bar 0
No place on Disk to dump data
No file configured to dump data
No vsan Object configured to dump data
No port for remote debugger.
P.s- on bios I can’t get the sata hdd as second drive on boot preference if I choose usb.
6 Replies
-
It is probably due to your computer hardware being compatible with Esxi 6.5 , did you check the HCL?
https://www.vmware.com/resources/compatibility/search.php Opens a new window
Was this post helpful?
thumb_up
thumb_down
-
@Scott — Before Installation, read this on vmware documentation but I wanted to skip this part thinking my PC has some super specs. Bad decision!
Checked on the above link. Mine is Intel Core 2 Quad CPU. I cant find this on the compatability list!
Was this post helpful?
thumb_up
thumb_down
-
Well that’s your problem , never skip these skips as they are important and will bite you (often very hard) in the rear. Esxi usually runs on a server not a desktop PC, even if it has got super specs.
Generally if it is not the list , it won’t work.
Was this post helpful?
thumb_up
thumb_down
-
Core 2 Quad is pretty old now. For what it’s worth you can totally run ESXi on a desktop computer, I do it now for my home lab.
But yes I did check with the hardware compatibility list. Only issue I ran into was my NIC — I just purchased a $20 PCIe NIC from Amazon that was on the compatibility list and all was good.
1 found this helpful
thumb_up
thumb_down
-
6.5 ESXi might not run, but 5.5 very well just might run. You can still learn a lot in a home lab from 5.5
1 found this helpful
thumb_up
thumb_down
-
@Michael. Thanks for your input. Will try 5.5. Was trying KVM !
Was this post helpful?
thumb_up
thumb_down
After I upgraded to VMWare ESXi 5.1.0, my server crashed with a purple screen of death as soon as I fired up a VM that was using a passed-through PCI device (1244:0e00, an AVM GmbH Fritz!Card PCI v2.0 ISDN (rev 01)).I have been running the original version of ESXi 5.0.0 for a year and everything worked fine. In fact, I have never ever seen such a purple screen of death.
VMware ESXi 5.1.0 [Releasebuild-799733 x86_64] #PF Exception 14 in world 4077:vmx IP 0x418039cf095c addr 0xl4 cr0=0x80010031 cr2=0x14 cr3=0x15c0d6000 cr4=0x42768 Frame=0x41221fb5bc00 ip=0x418039cf095c err=0 rflags=0x10202 rax=0x0 rbx=0x10 rcx=0x417ff9f084d0 rdx=0x41000168e5b0 rbp=0x41221fb5bcd8 rsi=0x41000168ee90 rdi=0x417ff9f084d0 r8=0x0 r9=0x1 r10=0x3ffd81972a9 r11=0x0 r12=0x41221fb5bd58 r13=0x41000168e350 r14=0xB r15=0x0 *PCPU3:4077/vmx PCPU B: UUVU Code start: 0x418039a00000 VMK uptime: 0:00:06:21.499 0x41221fb5bcd8:[0x418039cf095c]PCI_GetExtCapIdx@vmkernel#nover+0x2b stack: 0x41221fb5bd38 0x41221fb5bd48:[0x418039abadd2]VMKPCIPassthru_GetPCIInfo@vmkernel#nover+0x335 stack: 0x29000030e001 0x41221fb5beb8:[0x418B39ea2c51]UW64VMKSyscallUnpackPCIPassthruGetPCIInfo@<None>#<None>+0x28 stack: 0x41221fb5bef8:[0x4l8039e79791]User_LinuxSyscallHandler@<None>#<None>+0x17c stack: 0x418039a4cc70 0x41221fb5bf18:[0x4l8039aa82be]User_LinuxSyscallHandler@vmkernel#nover+0x19 stack: 0x3ffd8197490 0x41221fb5bf28:[0x418039b10064]gate_entry@vmkernel#nover+0x63 stack: 0x10b base fs=0x0 gs=0x418040c00000 Kgs=0x0 Coredump to disk. Slot 1 of 1. Finalized dump header (9/9) DiskDunp: Successful. Debugger waiting(world 4077) -- no port for remote debugger. "Escape" For local debugger.
Turns out that is a bug in ESXi. Luckily, downgrading an ESXi is simple enough: just hit Shift-R at the boot prompt and tell it to revert to the previous version.
Update: Patch ESXi510-201212401-BG in version ESXi510-201212001 (build 914609), released on December 20th, fixes the PCI passthrough issue (PR924167) according to KB2039030.