> the VM will fail to boot.
what does that mean ? a bluescreen 7b or a white cursor at the top left of a black screen or a VMware message or .... ?
Windows 7 will attempt to start, fail and reboot into a recovery setup (all within the VM). Recovery will fail in the VM and one can only recover by booting Windows 7 native.
This appears to be a regression from workstation exp 646643 which could create and use Windows 7 within a VM.
this is expected behaviour if this Windows never run as a VM before - did you patch the drivers already ?
I'm sorry but where can I read up on patching drivers?
To clarify, if I have a new machine with a virgin install of Windows 7 on a drive, install VMware-Workstation-Full-e.x.p-790308.x86_64.bundle under Linux, I cannot create a Windows 7 VM using the physical disk that Windows 7 is installed on that will boot successfully.
If I uninstall 790308 and install VMware-Workstation-Full-e.x.p-646643.x86_64.bundle, I can create the VM, boot into Windows 7 and install VMware tools.
Do I need to patch the VMware-Workstation-Full-e.x.p-790308.x86_64.bundle installation before creating the VM?
Sorry - I dont get it - why do you expect a natively installed Windows will boot inside a VM without issues ?
What you see is expected behaviour - if it worked for you earlier you were very lucky - please attach the vmx-file of this VM.
Which chipset does the host machine use ? - is that INTEL ?
It's a dual six core Intel(R) Xeon(R) CPU E5645 @ 2.40GHz
Excuse my ignorance but I expected the VM to boot successfully, that is not have I/O issues. I didn't expect video, networking, etc to work without a VMware tools install. It has worked with:
- Ubuntu 12.04 x64 and VMware-Workstation-Full-e.x.p-646643.x86_64.bundle
- Ubuntu 11.10 x64 with VMware-Workstation-Full-8.0.2-591240.x86_64.bundle
Are you suggesting that I boot into Windows natively and install VMware tools followed by creating the VM?
Windows 7 x64.vmx 3.8 K
It would help to boot natively and activate the LSI-SAS driver in registry - just change the start-setting from 4 to 0
Suddenly, I can't reproduce the failure. I grabbed two more virgin machines, installed VMware-Workstation-Full-e.x.p-790308.x86_64.bundle, setfacl within Linux to give myself access to the Windows drive and created a VM using the physical drive. During creation, VMware detected the drive "by-id" and the VM summary shows it as a scsi device. It booted into Windows just fine. Installed VMware tools and all is good.
I'm not sure what I missed before. Sorry I wasted your time.