I've been running vmware server 2.0.2 for a couple of years and everything worked great up until last Friday. My host system got hit with a virus which has since been cleaned. After getting rid of the virus all my vms hang at 95% when starting up.
Here are my system details:
Host OS: Windows XP x64 SP2
Hardware: Asus M2N-E, AMD Athlon 64 x2, 8GB Ram, 3Ware and Highpoint Raid controllers
Guests: Varied (example in attached log files is an XP64 OS but have the same problem with 32bit XP and CentOS guests)
After reading several other posts here and around the web here is what I've tried so far (not necessarily in this order):
- Completely uninstalling and reinstalling vmware server, including the "/c" option to clear the registry, and manually removing remaining vmware files and registry entries.
- Reinstalling Windows SP2 (no SP3 available for xp64) and running all windows updates
- Reinstalling latest nvidia drivers (MB has NVIDIA chipset)
- Moving the vms to different disks and adding/removing them from the inventory
It seems obvious that the virus (or the recovery process) knocked something out of whack but I have not been able to track it down. I've attached my latest hostd.log and vmware.log files for my "wxp64_jm_mabot" vm. I get similar log entries when I try running other vms. Here are a couple of note:
Sep 27 09:06:15.421: vcpu-0| VIDE: (0x1f0) OUTB Cmd 0xb0, Unknown ATA Command on drive 0
Sep 27 09:06:30.984: vcpu-0| DecoderIsInvalidInstruction:686 0xfffffadfe62b821e #UD f184aa8f sz=6 ct=1
If I let it sit at 95% for awhile new "DecoderIsInvalidInstruction" log entries are added periodically.
Please review and let me know if anything stands out that indicates what I should try next.
Thank you!
