Hi,
I am running Vista 64-bit host and VMWARE 6.03. I am getting 0xc000035a when I try to start a W2K8 64-bit guest or if I try to start a Vista 64-bit guest.
I ran the VMWARE test utility to verify that I can run 64-bit guests and I passed.
Where am I going wrong?
Thanks!
Which processor do you use?
Have you enabled V (AMD or VT (Intel) in the system BIOS?
Read VMware KB 1901: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1901
AWo
Message was edited by: AWo
Google: "HP 8510p"
I have configured the bios correctly. Ran the VMWARE test program for 64-bit with flying colors.
I am natively running Windows 2008 with Hyper-V with no issues. Hyper-v only runs on 64-bit.
Are you trying to run a 64-bit VMware virtual machine inside a Hyper-V virtual machine? That won't work, since Hyper-V doesn't virtualize the VT extensions.
My original post states "I am running Vista 64-bit host and VMWARE 6.03."
My first diagnostic was to run the VMWARE test tool for 64-bit on my Vista 64-bit host install with VMWARE 6.03. It tested with flying colors.
My second diagnostic was to install Windows 2008 64-bit and Hyper-V to prove the 64-bit settings in BIOS were configured correctly. This test was successful! I am running a Wnidows 2003 R2 SP2 in this Hyper-V. Sorry I am not crazy enough to run two Virutal products on one host. So NO VMWARE product is installed on this Windows 2008 host.
So the my original post is still an issue.
Can you post your vmware.log file for the failing 64-bit VM?
Unfortunately the physical drive now has Windows 2008 on it. I will try to find some time do another Vista to reproduce this. I was hoping it was a common occurance. This Vista 64-bit was a MSDN iso with SP1 on it.
I would love to know if anyone else out there is running an hp 8510P Laptop and having these issues with Vista 64-bit and VMWARE 6.03 trying to run a Windows 2008 64-bit virtual machine or a Vista 64-bit virtual machine. This 8510p has a Intel® CoreTM 2 Duo Processor T7700 (2.4 GHz, 800 MHz FSB, 4 MB L2 cache).
I have 2 boxes that are using the same version of Vista Ultimate. The HP Compaq nx9420 has Intel Core 2 T7400 2.16ghz cpu with 4gb ram. This box has no problems running any of my 64-bit vms.
The other box, is hand-built desktop box wih an Intel Core2 Quad 8200. 2.33ghz cpu with 4gb ram. This box cannot run any of my 64-bit vms.
The utility provided by VMware to determine whethr or not the box will suport 64-bit VMs is typical of VM's quality control process. It frequently works - but your results may vary. With quality diagnostics such as this, is it any wonder that using a VMware product is such a crapshoot?
So you actually are not asking for help, and are in fact being slightly insulting, yet you felt compelled to bump a post that was almost a year old?
What a waste of time.
I know better than to ask for help from VMware. Like I said, their diagnostic products are of dubious benefit. As for a year-old post, I wasn't aware that google searches for relevant issues expired after 1 year. My comments would be useful for anyone trying to figure out if they're the only one who is unsuccessful getting 64-bit guests to work. Why don't you concentrate your efforts on getting VMware to put out better diagnostic tools.
I'm getting the excact same error: HP 8510p (VT-mode enabled), trying to run Vista Enterprise 64-bit on a Windows7 Enterprise 64-bit host. If anyone knows how to make this combination work I would love to hear the answer...
Please see .
Please upload a vmware.log file for the failing VM.
Your log file shows that VMware Player is using VT-x for this guest and could enable 64-bit mode. However, you are resuming a suspended VM that did not have 64-bit capability, and the resumed VM will preserve the original characteristics.
Rather than suspending the VM, just power it off. When you power it on again, it should be 64-bit capable.
Hi,
I think I may ask for further details. The guest that I'm trying to power on, is that captured at a suspended state? And if so, how do I change that according to your last advice?
Yes, the log file shows that you are resuming a suspended VM. The next time you resume this VM, power it off instead of suspending it. When you power it on again, it should be 64-bit capable.