VMware

This Question is Answered

1 "helpful" answer available (6 pts)
1 2 Previous Next 23 Replies Last post: Oct 9, 2009 12:11 AM by dreamz020  

pink screening - spin count exceeded..possible deadlock posted: Jul 26, 2008 8:16 AM

Click to view mikemcsw's profile Enthusiast 67 posts since
Jul 25, 2008

I have tried to install esx 3.5 3 times now, and it keeps "pink screening" (if that's what you refer to it as?), saying spin count exceeded...possible deadlock.

any help would be appreciated, this is getting very frustrating...

Click to view lamw's profile Champion 2,814 posts since
Nov 27, 2007
also known as Purple Screen of Death, usually this deals with hardware faults in either the cpu or memory, usually the coredump of the PSOD will indicate whether it might be memory or cpu. Depending on your hardware vendor, you might be able to install some hardware monitoring agents like HP SIM. You might want to open a support call with VMware to determine what hardware is cuasing this issue or have your hardware vendor take a look to see if they can diagnose the error while booting into their diagonostic CD like HP Smartstart CD.
Click to view lamw's profile Champion 2,814 posts since
Nov 27, 2007

Before this continues, I want to make sure you know what you're running? You're posting under VI ESX 3.5 which is the enterprise hypervisor that runs on physical hardware, yet your posts talks about VMware workstation????? If you're talking about VMware workstation, then you're in the wrong forum and workstation run's on top of another operating system whether that be Linux or Windows.

In any case, what is the issue, you're reporting 2 seperate issues: pink/purple screening which with respect to ESX is "almost" always hardware related issues. In terms of your pegasus issue, this is a known issue that certain packages were not installed properly and Duncan on yellow-bricks has provided a fix. If that does not work, you can always boot into rescue mode and disable that service, assuming thats what's really causing your system not to boot up properly. So you have stated two issues and there's too many variables to determine what exactly you're seeing. If you don't have anything running on the hypervisor, I suggest re-installing ESX.

Click to view kjb007's profile Guru 5,486 posts since
Sep 18, 2006
What version of workstation are you using? You need to have 6.5 for ESX 3.5 to work correctly. You can use version 6 for ESX 3.0.x. I have 3.5 correctly running on 6.5

-KjB

Click to view kjb007's profile Guru 5,486 posts since
Sep 18, 2006
The instructions I used are the same from the xtravirt site. They provide good guidance to get you started. Not sure if you've already seen that or not. See here for those docs: http://www.xtravirt.com/index.php?option=com_content&task=view&id=99&Itemid=124

-KjB
Click to view Texiwill's profile Guru 10,213 posts since
Jan 13, 2004
Hello,

In order to use ESX within WS you need Intel-VT enabled hardware or AMD-V enabled hardware. WIthout it, nothing really works. For installing ESX 3.5 within WS 6.5 (which is Beta) I followed http://www.ntpro.nl/blog/archives/470-ESX-3.5-is-running-on-Workstation-6.5-Build-91182-!!!.html and it worked just fine. But if you do not have Intel-VT enabled then there could be problems. Verify that you have hardware that supports this first.


Best regards,
Edward L. Haletky
VMware Communities User Moderator
====
Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.
CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354
As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization
Click to view Texiwill's profile Guru 10,213 posts since
Jan 13, 2004
Hello,

You may have to hunt through the BIOS to see if its enabled. I had to do that for my laptop and then I ran the, Intel(R) Processor ID Utility - Windows* version to verify that it really did set it. Note however that the utility claims to not always be correct.


Best regards,
Edward L. Haletky
VMware Communities User Moderator
====
Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.
CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354
As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization
Click to view lamw's profile Champion 2,814 posts since
Nov 27, 2007
Get the CPU information and check either Intel or AMD's site to see if Intel VT or AMD-V is available, this feature has only been introduced in the newer laptop/desktops probably late 05/early 06/07 timeframe. It's all dependent on your CPU's and you can find this out easily by using that CPU utility that was recommended or browsing the vendor's site for cpu info. Sounds like you'll probably need to invest in either upgrading the CPU or a new workstation (laptop/desktop)
Click to view Texiwill's profile Guru 10,213 posts since
Jan 13, 2004
Hello,

Hunt through the BIOS on your system. If it is a Core 2 DUO or Quad Core then INtel-VT may be there. But generally takes a BIOS setting to be changed to be made available. If it is a New system then there may be a BIOS change required. You would need to discuss this with the vendor. BTW, as for the Older Dell that depends also on its BIOS, chipset, and CPU in use.


Best regards,
Edward L. Haletky
VMware Communities User Moderator
====
Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.
CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354
As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization
Click to view Datto's profile Expert 259 posts since
Mar 10, 2006

You dont suppose my older DELL workstation (GX270) supports it do you?

You can load ESX 3.5 directly onto the bare metal of a Dell GX270 (with PATA disk, SATA may not work) and ESX 3.5 will work. Don't use VMware Workstation -- just load ESX 3.5 right onto the bare metal of the GX270.

From your other computer at home, install the Virtual Infrastructure Client (The VIC) and point the VIC to the GX270's IP address after ESX 3.5 is loaded. You'll then be able to see and manage your ESX 3.5 Dell GX270 server.

Datto

VMware Developer

SDKs, APIs, Videos, Learn and much more in the Developer community.

Learn More

Developer Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

VMware vSphere

Come witness the next giant leap in virtualization.

Register Today

Incoming Links

Communities