Hi All,
I've decided to try ESXi at home just to fiddle with and ran into a problem. I have an extra Dell Optiplex GX260 and decided I would attempt to use ESXi on it. I already knew that the hard drives would n't accept the install (IDE) but I thought that if I put the image on a USB thumbdrive, I should be in the clear. (I intend to setup a box with openNAS to house the VMs). I was able to put the latest image onto the USB drive no problem, and it began to boot. However, a few ticks into the yellow screen I run into a pink error screen. It says NOT_IMPLEMENTED /build/mts/release/bora-110271/bora/vmkernel/filesystems/visorfs/visorfsOjb.c:2411
<error stuff from the stack>
VMK uptime: 0:00:00:00.462 TSC: 178034315850
No place on disk to dump data
Waiting for debugger...
Does this mean I'm totally out of luck, or is there hope?
Thanks,
Casey
Am I out of luck?
Casey
You might want to disable any devices you won't need and try the noapic setting - see this thread - http://communities.vmware.com/message/1024894. What sort of processor do you have in the system?
Hey Dave,
It is an Intel Pentium 4 2.00GHz. I watched the boot sequence more closely, and the processor was exactly where it failed. I tried the USB in another PC and it worked like a charm, so I'm using it instead. It actually worked out for the better because the other PC is faster and has more RAM.
Thanks,
Casey
What's the other type of PC that you're using?
It is a custom desktop I built myself a few years ago. AMD Athlon 64 Processor 3500+ 2GB RAM A8N-SLI Premium 939 Motherboard.
Casey
I am getting the exact same error. Any solution yet?
I gave up on using that particular computer as the server. I believe the processor isn't yet compatible with ESXi.
Casey
My server has Intel Core2 Duo E7200 @ 2.53GHz. Can anyone tell me if it is compatible or not?
You should be OK with the CPU - what sort of PC / motherboard are you using? Can you post the details of the pink screen?
ObNit: Purple screen.
There's another PSoD thread with an assert at the same point here, http://communities.vmware.com/thread/171061
I'll pass a pointer to this thread along as well.
ObNit: Purple screen.
OMG, there are gay VMWare servers, the virtual world never ceases to surprise me... LOL
Sorry about the pun, it isn't fun to be in this situation.
--
Wil
edit: added apology
>
>
> >
> >
> > ObNit: Purple screen.
>
> OMG, there are gay VMWare servers, the virtual world never ceases to surprise me... LOL
> Sorry about the pun, it isn't fun to be in this situation.
>
> --
> Wil
>
> edit: added apology
blink Wow.
Y'know, it really isn't purple per-se... it is closer to Magenta. Either way, amusing to consider GLBT in the context of computing.
GLBT So I learned a new word... well it doesn't have to be serious in here all the time is it? Besides my brother made it very clear to me that pink is a special color.. he loves his pink monday's. With all the current heisse around black monday I think I prefer that partying crowd over that too, coz they sure know how to party.
--
Wil
The thread at http://communities.vmware.com/message/1166259 suggests that this is an out-of-RAM condition.
If anybody finds their way to this thread looking for this same error on a MacBook Pro:
The same condition occurs on the new unibody MacBook Pros while attempting to boot ESXi (following the instructions posted at http://communities.vmware.com/docs/DOC-6590 and/or http://www.brandonfreitag.com/vmware/VI35.pdf). Raising the RAM to 1.4 GB clears it up.