Chris_S_UK
Expert
Expert

Unable to install ESX3.5 under WS6

Jump to solution

Whereas it's well documented how to install 3.0.x under WS6, when I try to install 3.5 in the same way, it reports "Unable to find any supported network devices" very early on in the install process and won't go any further.

The VM has 1 virtual NIC installed.

Anyone else tried 3.5 under WS6 yet?

Chris

0 Kudos
1 Solution

Accepted Solutions
Dave_Mishchenko
Immortal
Immortal

Have you enabled Intel VT in the BIOS and added the below lines into the VMX file? I also selected Other \ Other as the guest OS.

monitor_control.restrict_backdoor = "TRUE"

monitor_control.vt32 = "TRUE"

Chris, for your problem did you edit the VMX and add: ethernet0.virtualDev = "e1000"

View solution in original post

0 Kudos
24 Replies
mystereman
Enthusiast
Enthusiast

I just attempted this for fun, and had only minor problems (and one big one). There was an error message presented during boot, relating to something that seemed like an interrupt controller or something. However, it continued booting. The setup program saw the NIC as an Intel GIGABIT controller.

Here is my setup. I gave the VM 1.5GB's and a 16GB SCSI disk. I choose "Other Linux 2.4 kernel".

Now, having said that.. it's SLOW!!!! Very slow. It takes upwards of an hour to install, and over 3.5 hours to boot, pegging the CPU of the host even when you finally get to log in. This is on a Core 2 Duo E6300 with 4GB of memory.

Dave_Mishchenko
Immortal
Immortal

Have you enabled Intel VT in the BIOS and added the below lines into the VMX file? I also selected Other \ Other as the guest OS.

monitor_control.restrict_backdoor = "TRUE"

monitor_control.vt32 = "TRUE"

Chris, for your problem did you edit the VMX and add: ethernet0.virtualDev = "e1000"

View solution in original post

0 Kudos
mystereman
Enthusiast
Enthusiast

Actually, i just went and read the whitepaper here:

It suggests the entries you mention, plus a few more. Upon doing this, i reinstalled ESX 3.5 and boom, it booted up almost instantly.. lol.

Yes, Chris, you obviously missed a step. Reread the whitepaper.

0 Kudos
Chris_S_UK
Expert
Expert

I tried installing 3.5 by booting a VM off the ISO file, the VM being one onto which I had already installed 3.0.2 so presumed the vmx file was ok.

Actually, the ethernet0.virtualDev = "e1000" was missing from the vmx and it works now, but it's a little surprising that 3.0.2 installed without this line, I suppose.

Chris

0 Kudos
Dave_Mishchenko
Immortal
Immortal

I had the same experience earlier with 3.0.2 working with the vlance NIC but not 3.5. The final build of 3.5 was released tonight (64607) so if you downloaded 3.5 last week you'll want to get the final release.

0 Kudos
Chnoili
Enthusiast
Enthusiast

I can install ESX3.5 (the e1000 nic works) but when the esx will boot and load the kernel - i have the error from WS6 --> Virtual machine kernel stack fault (hardware reset)

Has someone a idea where the problem is?

THX

0 Kudos
sgmess
Contributor
Contributor

I had ESX3.02 running under WS6 with no problems after following the xtravirt whitepaper, done the same with ESX3.5 but get the following error in WS6 when starting a VM guest under ESX.

This causes VM6 to turn of the ESX host that is trying to start the VM.

MONITOR PANIC: vcpu-0:ASSERT vmcore/private/physMem_shared.h:38 bugNr=131897

Any ideas?

0 Kudos
mcwill
Expert
Expert

I had the same problem, so had to install 3.5 on real hardware to test it out.

Luckily 3.5 is much more forgiving of hardware so can be run on what you may have lying in the corner.

0 Kudos
esloof
Expert
Expert

I have the same problem, the VM will start-up to 100% and then WS6 crashes. I attached the coredump.

      • VMware Workstation internal monitor error ***

vcpu-0:ASSERT vmcore/private/physMem_shared.h:38 bugNr=131897

Please report this problem by selecting menu item Help > VMware on the Web > Request Support, or by going to the Web page "http://www.vmware.com/info?id=8&logFile=C%3a%5cVirtual%20Machines%5cESX35%5cvmware%2elog&coreLocation=C%3a%5cVirtual%20Machines%5cESX35%5cvmware%2dcore%5b0%2d1%5d%2egz". Please provide us with the log file (C:\Virtual Machines\ESX35\vmware.log) and the core file (C:\Virtual Machines\ESX35\vmware-core[0-1].gz).

If the problem is repeatable, please select 'Run with debugging information' in the Options panel of Virtual Machine Settings. Then reproduce the incident and file it according to the instructions.

To collect data to submit to VMware support, select Help > About and click "Collect Support Data". You can also run the "vm-support" script in the Workstation folder directly.

We will respond on the basis of your support entitlement.

We appreciate your feedback,

    • the VMware Workstation team.

Dec 10 20:30:10.944: vcpu-1| SEG_SS 1254 count=119999

Dec 10 20:30:27.881: vcpu-0| SEG_SS 1254 count=79999

Dec 10 20:30:30.923: vcpu-1| SEG_SS 1254 count=129999

Dec 10 20:30:47.946: vcpu-0| SEG_SS 1254 count=89999

Dec 10 20:30:50.979: vcpu-1| SEG_SS 1254 count=139999

Dec 10 20:31:07.983: vcpu-0| SEG_SS 1254 count=99999

Dec 10 20:31:11.021: vcpu-1| SEG_SS 1254 count=149999

Dec 10 20:31:24.898: vcpu-1| SEG_SS 1254 count=159999

Dec 10 20:31:28.527: vcpu-0| SEG_SS 1254 count=109999

Dec 10 20:31:30.361: vcpu-1| MONITOR PANIC: vcpu-1:ASSERT vmcore/private/physMem_shared.h:38 bugNr=131897

Dec 10 20:31:30.361: vcpu-1| Core dump with build build-59824

Dec 10 20:31:30.361: vcpu-1| Writing monitor corefile "C:\Virtual Machines\ESX35\vmware-core0.gz"

Dec 10 20:31:30.406: vcpu-1| Beginning monitor coredump

Dec 10 20:31:30.597: vcpu-1| End monitor coredump

Dec 10 20:31:30.597: vcpu-1| Beginning extended monitor coredump

Dec 10 20:31:30.597: vcpu-1| Writing anonymous pages at pos: 401000

Dec 10 20:31:31.535: vcpu-1| Writing monitor corefile "C:\Virtual Machines\ESX35\vmware-core1.gz"

Dec 10 20:31:31.548: vcpu-1| Beginning monitor coredump

Dec 10 20:31:31.682: vcpu-1| End monitor coredump

Dec 10 20:31:31.682: vcpu-1| Beginning extended monitor coredump

Dec 10 20:31:31.682: vcpu-1| Writing anonymous pages at pos: 401000

Dec 10 20:31:32.636: vcpu-1| Msg_Post: Error

Dec 10 20:31:32.636: vcpu-1| http://msg.log.monpanic *** VMware Workstation internal monitor error ***

Dec 10 20:31:32.636: vcpu-1| vcpu-1:ASSERT vmcore/private/physMem_shared.h:38 bugNr=131897

Dec 10 20:31:32.636: vcpu-1| http://msg.log.monpanic.report Please report this problem by selecting menu item Help > VMware on the Web > Request Support, or by going to the Web page "http://www.vmware.com/info?id=8&logFile=C%3a%5cVirtual%20Machines%5cESX35%5cvmware%2elog&coreLocation=C%3a%5cVirtual%20Machines%5cESX35%5cvmware%2dcore%5b0%2d1%5d%2egz". Please provide us with the log file (C:\Virtual Machines\ESX35\vmware.log) and the core file (C:\Virtual Machines\ESX35\vmware-core[0-1].gz).

Dec 10 20:31:32.636: vcpu-1| http://msg.log.monpanic.win32debug If the problem is repeatable, please select 'Run with debugging information' in the Options panel of Virtual Machine Settings. Then reproduce the incident and file it according to the instructions.

Dec 10 20:31:32.636: vcpu-1| http://msg.log.monpanic.vmSupport.windowsOrLinux To collect data to submit to VMware support, select Help > About and click "Collect Support Data". You can also run the "vm-support" script in the Workstation folder directly.

Dec 10 20:31:32.636: vcpu-1| http://msg.log.monpanic.entitlement We will respond on the basis of your support entitlement.

Dec 10 20:31:32.636: vcpu-1| http://msg.log.monpanic.finish We appreciate your feedback,

Dec 10 20:31:32.636: vcpu-1| -- the VMware Workstation team.

Dec 10 20:31:32.636: vcpu-1| -


Dec 10 20:31:53.186: vcpu-1| Ignoring broadcast request

Dec 10 20:31:53.186: vcpu-1| Exiting vcpu-1

Dec 10 20:31:53.187: vcpu-0| Writing monitor corefile "C:\Virtual Machines\ESX35\vmware-core0.gz"

Dec 10 20:31:53.226: vcpu-0| Beginning monitor coredump

Dec 10 20:31:53.485: vcpu-0| End monitor coredump

Dec 10 20:31:53.485: vcpu-0| Beginning extended monitor coredump

Dec 10 20:31:53.485: vcpu-0| Writing anonymous pages at pos: 401000

Dec 10 20:31:53.634: vmx| VTHREAD watched thread 5 "vcpu-1" died

Dec 10 20:31:53.649: mks| VTHREAD watched thread 0 "vmx" died

Dec 10 20:31:54.199: kbh| VTHREAD watched thread 0 "vmx" died

Dec 10 20:31:54.426: vcpu-0| Exiting vcpu-0

0 Kudos
mystereman
Enthusiast
Enthusiast

Indeed, I got the same problem. I hadn't yet tried to start a virtual machine earlier, I was just happy to get ESX 3.5 to boot and run. Upon starting a new virtual machine, I get an identical assert to your in WS6 and when you click OK it shuts down the VM.

Did you submit a support request?

0 Kudos
RGS3
Enthusiast
Enthusiast

I also had this problem

1454_1454.jpg

Has anyone been successful in starting a guest VM in VI3.5 on WS6?

0 Kudos
jose_maria_gonz
Virtuoso
Virtuoso

Hi there,

Same here, I have got the same error when powering on a VM uner ESX3.5 and WS6.

Dec 16 22:39:05.046: vcpu-0| MONITOR PANIC: vcpu-0:ASSERT vmcore/private/physMem_shared.h:38 bugNr=131897

Dec 16 22:39:05.046: vcpu-0| Core dump with build build-59824

Dec 16 22:39:05.046: vcpu-0| Writing monitor corefile "C:\Documents and Settings\jose_maria_gonzalez\My Documents\My Virtual Machines\Demo ESX 3.5\ESX1\vmware-core.gz"

Dec 16 22:39:05.046: vcpu-0| Beginning monitor coredump

Dec 16 22:39:05.250: vcpu-0| End monitor coredump

Dec 16 22:39:05.250: vcpu-0| Beginning extended monitor coredump

Dec 16 22:39:05.250: vcpu-0| Writing anonymous pages at pos: 401000

Dec 16 22:39:05.859: vcpu-0| Msg_Post: Error

Dec 16 22:39:05.859: vcpu-0| http://msg.log.monpanic *** VMware Workstation internal monitor error ***

Dec 16 22:39:05.859: vcpu-0| vcpu-0:ASSERT vmcore/private/physMem_shared.h:38 bugNr=131897

Dec 16 22:39:05.859: vcpu-0| http://msg.log.monpanic.report Please report this problem by selecting menu item Help > VMware on the Web > Request Support, or by going to the Web page "http://www.vmware.com/info?id=8&logFile=C%3a%5cDocuments%20and%20Settings%5cjose%5fmaria%5fgonzalez%5cMy%20Documents%5cMy%20Virtual%20Machines%5cDemo%20ESX%203%2e5%5cESX1%5cvmware%2elog&coreLocation=C%3a%5cDocuments%20and%20Settings%5cjose%5fmaria%5fgonzalez%5cMy%20Documents%5cMy%20Virtual%20Machines%5cDemo%20ESX%203%2e5%5cESX1%5cvmware%2dcore%2egz". Please provide us with the log file (C:\Documents and Settings\jose_maria_gonzalez\My Documents\My Virtual Machines\Demo ESX 3.5\ESX1\vmware.log) and the core file (C:\Documents and Settings\jose_maria_gonzalez\My Documents\My Virtual Machines\Demo ESX 3.5\ESX1\vmware-core.gz).

Dec 16 22:39:05.859: vcpu-0| http://msg.log.monpanic.win32debug If the problem is repeatable, please select 'Run with debugging information' in the Options panel of Virtual Machine Settings. Then reproduce the incident and file it according to the instructions.

Dec 16 22:39:05.859: vcpu-0| http://msg.log.monpanic.vmSupport.windowsOrLinux To collect data to submit to VMware support, select Help > About and click "Collect Support Data". You can also run the "vm-support" script in the Workstation folder directly.

Dec 16 22:39:05.859: vcpu-0| http://msg.log.monpanic.entitlement We will respond on the basis of your support entitlement.

Dec 16 22:39:05.859: vcpu-0| http://msg.log.monpanic.finish We appreciate your feedback,

Dec 16 22:39:05.859: vcpu-0| -- the VMware Workstation team.

Dec 16 22:39:05.859: vcpu-0| -


0 Kudos
VMPK
Contributor
Contributor

I have also had the same problem myself with WS6. I have tried to start the VM up via the VC & directly connected to the ESX server with Inf client and error shown appears.

Once I click OK on the error box the ESX server crashes. I am using a dual core CPU with VT turned on in bios with 2GB memory and setup using Xtravirt guide & I am using Openfiler as my ISCSI storage.

      • VMware Workstation internal monitor error ***

vcpu-1:ASSERT vmcore/private/physMem_shared.h:38 bugNr=131897

Please report this problem by selecting menu item Help > VMware on the Web > Request Support, or by going to the Web page "[http://www.vmware.com/info?id=8&logFile=C%3a%5cDocuments%20and%20Settings%username%2eENTERPRISE%5cMy%20Documents%5cMy%20Virtual%20Machines%5cLapESX02%5cvmware%2elog&coreLocation=C%3a%5cDocuments%20and%20Settings%username%5cMy%20Documents%5cMy%20Virtual%20Machines%5cLapESX02%5cvmware%2dcore%5b0%2d1%5d%2egz]". Please provide us with the log file (C:\Documents and Settings\username\My Documents\My Virtual Machines\LapESX02\vmware.log) and the core file (C:\Documents and Settings\username\My Documents\My Virtual Machines\vmware-core[0-1].gz).

If the problem is repeatable, please select 'Run with debugging information' in the Options panel of Virtual Machine Settings. Then reproduce the incident and file it according to the instructions.

To collect data to submit to VMware support, select Help > About and click "Collect Support Data". You can also run the "vm-support" script in the Workstation folder directly.

We will respond on the basis of your support entitlement.

We appreciate your feedback,

-- the VMware Workstation team.

If anyone has any tips or suggestions on getting this running let me know.

Many Thanks

Paul

0 Kudos
pbraren
Hot Shot
Hot Shot

I hope this helps a bit:

http://communities.vmware.com/thread/117712

I'm running 64 bit Vista, with 4GB of memory and VT enabled on dual cores (Lenovo T61p) fyi.

TinkerTry.com
0 Kudos
kchuan
Contributor
Contributor

i do hav similar problem with tis. ESX3.5 unable to detect Hp dc7800 network adaptor (Intel 1000), but it works fine for older model.

Need help.

0 Kudos
esloof
Expert
Expert

I'm running out of options. I desperately want to check out the new features in ESX 3.5 but I can't find a way to run ESX 3.5 in a virtual environment. I tried Workstation 6, VMware Server 2.0 and even VMware Player 2.0. The player starts ESX 3.5 in the blink of an eye but when I power on my first virtual machine I receive the same error I received in Workstation.

      • VMware Player internal monitor error ***

vcpu-1:ASSERT vmcore/private/physMem_shared.h:38 bugNr=131897

Please report this problem by selecting menu item Help > VMware on the Web > Request Support, or by going to the Web page "[http://www.vmware.com/info?id=8&logFile=C%3a%5cUsers%5cEric%20Sloof%5cAppData%5cLocal%5cTemp%5cvmware%2dEric%20Sloof%5cvmware%2dEric%20Sloof%2d2700%2elog&coreLocation=C%3a%5cVirtual%20Machines%5cESX35%5cvmware%2dcore%5b0%2d1%5d%2egz]". Please provide us with the log file (C:\Users\Eric Sloof\AppData\Local\Temp\vmware-Eric Sloof\vmware-Eric Sloof-2700.log) and the core file (C:\Virtual Machines\ESX35\vmware-core[0-1].gz).

If the problem is repeatable, please select 'Run with debugging information' in the Options panel of Virtual Machine Settings. Then reproduce the incident and file it according to the instructions.

To collect data to submit to VMware support, select Help > About and click "Collect Support Data". You can also run the "vm-support" script in the Workstation folder directly.

We will respond on the basis of your support entitlement.

We appreciate your feedback,

-- the VMware Player team.

0 Kudos
jose_maria_gonz
Virtuoso
Virtuoso

Hi there,

Just a quick note to let you all know that it appears that this error would be fix with Workstation 6.5!

I reported the error to VMWare and that's what I was told. does anyone know when Workstation 6.5 would be out?

Thanks,

rgds,

J.

0 Kudos
esloof
Expert
Expert

News from Xtravirt:

Since VMware ESX 3.5 was released many of those in the community have found that the previous methodology to install and run ESX in a VM on Workstation 6 stopped working when a VM nested in ESX 3.5 was powered on. This short paper explores some of the background to this and makes some observations as to why this happens and the possible future of 'VI3 in a Box'.

Download it here.

http://www.xtravirt.com/index.php?option=com_content&task=view&id=120&Itemid=64

0 Kudos
cgb
Contributor
Contributor

Great summary of the problem - definitely clarifies things for everybody reading the thread.

If Workstation 6.5 does resolve this problem, does anyone have ideas of the release date for it? (or if they are part of the limited beta trials, maybe they could test it? Smiley Happy)

0 Kudos