VMware Cloud Community
cdomanski
Enthusiast
Enthusiast
Jump to solution

Can't install 64-bit Windows, guest shuts down after "Setup is Starting Windows..." phase.

Hi everyone, this problem is killing me. I'm running an IBM x3650 with 2 Xeon 5160 CPU's. The CPU supports 64-bit, and the VT option is enabled in the BIOS.

I've now tried installing Windows 2003 R2 64-bit and Windows 2008, I always choose the appropriate operating system in the setup wizard.

The install starts fine and I see the setup loading files from the CD, or ISO. At the point where the install says "Setup is starting Windows" the machine pauses for about 10 seconds, the the guest vm shuts down. I've tried booting from CD, ISO, Windows 2003, Windows 2008, all fail with the exact problem. Any Windows 32-bit OS works fine.

I've searched all the forums, and read about enabling VT, which I've done.

Please help!

Reply
0 Kudos
1 Solution

Accepted Solutions
admin
Immortal
Immortal
Jump to solution

It sounds like you may have mismatched steppings of Xeons in this system. Stepping B and stepping G have incompatible VT revisions. If this is the case, please check with IBM for a BIOS update. Intel has provided OEMs with a microcode patch that downgrades the VT revision on higher stepping processors to match the VT revision of lower stepping processors in a mixed-stepping system.

View solution in original post

Reply
0 Kudos
7 Replies
kjb007
Immortal
Immortal
Jump to solution

Go into the vm settings, and make sure vmi/para-virtualization is turned off.

If that option is disabled, look in the vmware.log of that vm to see if it offers more clues.

-KjB

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB
Reply
0 Kudos
cdomanski
Enthusiast
Enthusiast
Jump to solution

Thanks, I've checked that setting, which btw I've never touched before, and it is disabled.

I'm posting the vmware.log which shows mks| VTHREAD watched thread 0 "vmx" died. I searched the forums for this error, and there's one post which indicates updating to ESX 3.5 Update1. I've recentlyinstalled Update2. The exact version I'm running is: 3.5.0 110268.

Oct 14 11:55:43.755: vmx| DISK: DISK/CDROM timeout of 4.551 seconds on ide0:0 (ok)

Oct 14 11:55:43.755: vmx| POLL device deleted

Oct 14 11:55:45.903: vmx| DISK: DISK/CDROM timeout of 1.539 seconds on ide0:0 (ok)

Oct 14 11:55:45.903: vmx| POLL device deleted

Oct 14 11:55:49.824: mks| VNCENCODE 2 encoding mode change: (1024x768x24depth,32bpp)

Oct 14 12:01:27.098: vcpu-0| MonitorInitReserveMem64: vmm64OverheadPages=0

Oct 14 12:01:27.112: vcpu-0| Monitor64_PowerOn()

Oct 14 12:01:27.116: vcpu-0| vmm64->cr3 = 0x895d4000, vmkContext = 0xa9aa170, vmkCR3 = 0xa9f7c000

Oct 14 12:01:29.801: vcpu-0| vmm64->cr3 = 0x2debc000, vmkContext = 0xa9aa650, vmkCR3 = 0x9fbea000

Oct 14 12:01:29.802: vcpu-0| vmm64->cr3 = 0x89be4000, vmkContext = 0xa9aab30, vmkCR3 = 0x986b5000

Oct 14 12:01:29.802: vcpu-0| vmm64->cr3 = 0x89c4c000, vmkContext = 0xa9d0cc8, vmkCR3 = 0x74340000

Oct 14 12:01:29.822: vcpu-0| vmm64-modules: vmm.vmm64 .data:0xfffffffffc04b000 .sdata:0xfffffffffc04d000 .statvars:0xfffffffffc04e000 .peer:0xff...

Oct 14 12:01:29.832: vcpu-0| APIC: version = 0x14, max LVT = 5

Oct 14 12:01:29.832: vcpu-0| APIC: LDR = 0x2000000, DFR = 0xffffffff

Oct 14 12:01:29.866: vcpu-0| HV enabled

Oct 14 12:01:29.869: vcpu-0| VMM64 initialized

Oct 14 12:01:29.870: vcpu-3| APIC: version = 0x14, max LVT = 5

Oct 14 12:01:29.870: vcpu-3| APIC: LDR = 0x4000000, DFR = 0xffffffff

Oct 14 12:01:29.871: vcpu-2| APIC: version = 0x14, max LVT = 5

Oct 14 12:01:29.871: vcpu-2| APIC: LDR = 0x1000000, DFR = 0xffffffff

Oct 14 12:01:29.871: vcpu-1| APIC: version = 0x14, max LVT = 5

Oct 14 12:01:29.872: vcpu-1| APIC: LDR = 0x1000000, DFR = 0xffffffff

Oct 14 12:01:30.870: vcpu-0| MONITOR PANIC: vcpu-3:VMM64 fault 6: src=MONITOR rip=0xfffffffffc27a3e2 regs=0xfffffffffc008d50

Oct 14 12:01:30.870: vcpu-0| Core dump with build build-110268

Oct 14 12:01:30.997: vcpu-0| Writing monitor corefile "/vmfs/volumes/48ecb81e-135609fe-a349-001a64071fef/Exchange2007/vmware-core0.gz"

Oct 14 12:01:30.998: vcpu-0| CoreDump: dumping core with superuser privileges

Oct 14 12:01:31.138: vcpu-0| VMK Stack for vcpu 0 is at 3c01000

Oct 14 12:01:31.138: vcpu-0| Beginning monitor coredump

Oct 14 12:01:31.315: vcpu-0| End monitor coredump

Oct 14 12:01:31.316: vcpu-0| Beginning extended monitor coredump

Oct 14 12:01:31.316: vcpu-0| Writing anonymous pages at pos: 404000

Oct 14 12:01:32.415: vcpu-0| Writing monitor corefile "/vmfs/volumes/48ecb81e-135609fe-a349-001a64071fef/Exchange2007/vmware-core1.gz"

Oct 14 12:01:32.415: vcpu-0| CoreDump: dumping core with superuser privileges

Oct 14 12:01:32.503: vcpu-0| VMK Stack for vcpu 1 is at 3c05000

Oct 14 12:01:32.503: vcpu-0| Beginning monitor coredump

Oct 14 12:01:32.605: vcpu-0| End monitor coredump

Oct 14 12:01:32.605: vcpu-0| Beginning extended monitor coredump

Oct 14 12:01:32.605: vcpu-0| Writing anonymous pages at pos: 404000

Oct 14 12:01:33.731: vcpu-0| Writing monitor corefile "/vmfs/volumes/48ecb81e-135609fe-a349-001a64071fef/Exchange2007/vmware-core2.gz"

Oct 14 12:01:33.731: vcpu-0| CoreDump: dumping core with superuser privileges

Oct 14 12:01:33.750: vcpu-0| VMK Stack for vcpu 2 is at 3c09000

Oct 14 12:01:33.750: vcpu-0| Beginning monitor coredump

Oct 14 12:01:33.851: vcpu-0| End monitor coredump

Oct 14 12:01:33.851: vcpu-0| Beginning extended monitor coredump

Oct 14 12:01:33.851: vcpu-0| Writing anonymous pages at pos: 404000

Oct 14 12:01:34.981: vcpu-0| Writing monitor corefile "/vmfs/volumes/48ecb81e-135609fe-a349-001a64071fef/Exchange2007/vmware-core3.gz"

Oct 14 12:01:34.981: vcpu-0| CoreDump: dumping core with superuser privileges

Oct 14 12:01:35.020: vcpu-0| VMK Stack for vcpu 3 is at 3c0d000

Oct 14 12:01:35.021: vcpu-0| Beginning monitor coredump

Oct 14 12:01:35.128: vcpu-0| End monitor coredump

Oct 14 12:01:35.129: vcpu-0| Beginning extended monitor coredump

Oct 14 12:01:35.129: vcpu-0| Writing anonymous pages at pos: 404000

Oct 14 12:01:36.304: vcpu-0| Writing monitor corefile "/vmfs/volumes/48ecb81e-135609fe-a349-001a64071fef/Exchange2007/vmware64-core0.gz"

Oct 14 12:01:36.304: vcpu-0| CoreDump: dumping core with superuser privileges

Oct 14 12:01:36.340: vcpu-0| Beginning monitor coredump

Oct 14 12:01:37.179: vcpu-0| End monitor coredump

Oct 14 12:01:37.179: vcpu-0| Beginning extended monitor coredump

Oct 14 12:01:37.179: vcpu-0| Writing anonymous pages at pos: 4001000

Oct 14 12:01:38.374: vcpu-0| Writing monitor corefile "/vmfs/volumes/48ecb81e-135609fe-a349-001a64071fef/Exchange2007/vmware64-core1.gz"

Oct 14 12:01:38.374: vcpu-0| CoreDump: dumping core with superuser privileges

Oct 14 12:01:38.490: vcpu-0| Beginning monitor coredump

Oct 14 12:01:39.297: vcpu-0| End monitor coredump

Oct 14 12:01:39.297: vcpu-0| Beginning extended monitor coredump

Oct 14 12:01:39.297: vcpu-0| Writing anonymous pages at pos: 4001000

Oct 14 12:01:40.405: vcpu-0| Writing monitor corefile "/vmfs/volumes/48ecb81e-135609fe-a349-001a64071fef/Exchange2007/vmware64-core2.gz"

Oct 14 12:01:40.405: vcpu-0| CoreDump: dumping core with superuser privileges

Oct 14 12:01:40.429: vcpu-0| Beginning monitor coredump

Oct 14 12:01:41.246: vcpu-0| End monitor coredump

Oct 14 12:01:41.246: vcpu-0| Beginning extended monitor coredump

Oct 14 12:01:41.246: vcpu-0| Writing anonymous pages at pos: 4001000

Oct 14 12:01:42.324: vcpu-0| Writing monitor corefile "/vmfs/volumes/48ecb81e-135609fe-a349-001a64071fef/Exchange2007/vmware64-core3.gz"

Oct 14 12:01:42.324: vcpu-0| CoreDump: dumping core with superuser privileges

Oct 14 12:01:42.378: vcpu-0| Beginning monitor coredump

Oct 14 12:01:43.199: vcpu-0| End monitor coredump

Oct 14 12:01:43.199: vcpu-0| Beginning extended monitor coredump

Oct 14 12:01:43.199: vcpu-0| Writing anonymous pages at pos: 4001000

Oct 14 12:01:44.333: vcpu-0| Msg_Post: Error

Oct 14 12:01:44.333: vcpu-0| http://msg.log.monpanic *** VMware ESX Server internal monitor error ***

Oct 14 12:01:44.333: vcpu-0| vcpu-3:VMM64 fault 6: src=MONITOR rip=0xfffffffffc27a3e2 regs=0xfffffffffc008d50

Oct 14 12:01:44.333: 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=%2fvmfs%2fvolumes%2f48ecb81e%2d135609fe%2da349%2d001a64071fef%2fExchange2007%2fvmware%2elog&coreLocation=%2fvmfs%2fvolumes%2f48ecb81e%2d135609fe%2da349%2d001a64071fef%2fExchange2007%2fvmware%2dcore%5b0%2d3%5d%2egz%2c%20%2fvmfs%2fvolumes%2f48ecb81e%2d135609fe%2da349%2d001a64071fef%2fExchange2007%2fvmware64%2dcore%5b0%2d3%5d%2egz". Please provide us with the log file (/vmfs/volumes/48ecb81e-135609fe-a349-001a64071fef/Exchange2007/vmware.log) and the core file (/vmfs/volumes/48ecb81e-135609fe-a349-001a64071fef/Exchange2007/vmware-core[0-3].gz, /vmfs/volumes/48ecb81e-135609fe-a349-001a64071fef/Exchange2007/vmware64-core[0-3].gz).

Oct 14 12:01:44.333: vcpu-0| http://msg.log.monpanic.serverdebug If the problem is repeatable, please set 'Use Debug Monitor' to 'Yes' in the 'Misc' section of the Configure Virtual Machine Web page. Then reproduce the incident and file it according to the instructions.

Oct 14 12:01:44.333: vcpu-0| http://msg.log.monpanic.vmSupport To collect files to submit to VMware support, run "vm-support".

Oct 14 12:01:44.333: vcpu-0| http://msg.log.monpanic.entitlement We will respond on the basis of your support entitlement.

Oct 14 12:01:44.333: vcpu-0| http://msg.log.monpanic.finish We appreciate your feedback,

Oct 14 12:01:44.333: vcpu-0| -- the VMware ESX Server team.

Oct 14 12:01:44.333: vcpu-0| -


Oct 14 12:01:44.353: vcpu-0| Exiting vcpu-0

Oct 14 12:01:45.334: vmx| VTHREAD watched thread 4 "vcpu-0" died

Oct 14 12:01:45.440: mks| VTHREAD watched thread 0 "vmx" died

Oct 14 12:01:45.876: vcpu-2| VTHREAD watched thread 0 "vmx" died

Oct 14 12:01:45.877: vcpu-1| VTHREAD watched thread 0 "vmx" died

Oct 14 12:01:45.884: vcpu-3| VTHREAD watched thread 0 "vmx" died

Reply
0 Kudos
Texiwill
Leadership
Leadership
Jump to solution

Hello,

Moved to Virtual Machine and Guest OS forum.


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

--
Edward L. Haletky
vExpert XIV: 2009-2023,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill
Reply
0 Kudos
admin
Immortal
Immortal
Jump to solution

It sounds like you may have mismatched steppings of Xeons in this system. Stepping B and stepping G have incompatible VT revisions. If this is the case, please check with IBM for a BIOS update. Intel has provided OEMs with a microcode patch that downgrades the VT revision on higher stepping processors to match the VT revision of lower stepping processors in a mixed-stepping system.

Reply
0 Kudos
AndrewSt
Enthusiast
Enthusiast
Jump to solution

Have to second this. The only time I have seen this has been with paravirt issue, and when the VT in bios was not working right.

-


-Andrew Stueve

----------------------- -Andrew Stueve -Remember, if you found this or any other answer useful, please consider the use of the Helpful or Correct buttons to award points
Reply
0 Kudos
cdomanski
Enthusiast
Enthusiast
Jump to solution

Thanks guys, I am a couple of releases behind on the BIOS, and I see this was noted as one of the fixes from IBM:

Fixed : Booting with mixed processors with VT enabled.

Maybe this is my problem? I will only be able to get to this in a couple of days, then I will update. We definately added the 2nd CPU to these machines after the initial purchase, so your solution seems pretty good.

Reply
0 Kudos
cdomanski
Enthusiast
Enthusiast
Jump to solution

Thanks everyone, it was a BIOS issue. Updating from 1.08 to 1.11 fixed my problem, now installing Windows 2008.

Reply
0 Kudos