I had frequent freezes with VMWare 7.1.1 and so thought I would upgrade to 7.1.2
I am running a Windows XP 32-bit guest on a Windows 7 64-bit host on an Core i7 machine.
First problem with 7.1.2: Power on takes almost 10 minutes. When you maximize or minimize windows, you can literally see the redraw ... slowly.
Here are some excerpts from the vmware.log:
Oct 03 08:46:43.196: vcpu-1| CPU reset: soft (mode 2)
Oct 03 08:46:46.703: mks| SVGA: display status changed, using optimizations for local consoles.
Oct 03 08:48:03.967: vcpu-2| CPU reset: soft (mode 2)
Oct 03 08:48:43.140: mks| MKSHostOps_Exit3D: 0, 1
Oct 03 08:49:25.226: vcpu-3| CPU reset: soft (mode 2)
Oct 03 08:48:43.140: mks| MKSHostOps_Exit3D: 0, 1
Oct 03 08:49:25.226: vcpu-3| CPU reset: soft (mode 2)
Oct 03 08:50:53.775: vcpu-0| SVGA: Unregistering IOSpace at 0x10f0
....
(4 minutes for the SVGA stuff? ... between display status changed .... Unregistering IOSpace)
And then there are lots of:
Oct 03 09:12:24.534: vmx| VIDE: ATAPI DMA 0x25 Failed: key 0x2, asc 0x3a, ascq 0x1
Oct 03 09:12:24.539: vmx| VIDE: ATAPI DMA 0x25 Failed: key 0x2, asc 0x3a, ascq 0x1
Oct 03 09:12:24.549: vmx| VIDE: ATAPI DMA 0x25 Failed: key 0x2, asc 0x3a, ascq 0x1
Oct 03 09:12:24.554: vmx| VIDE: ATAPI DMA 0x25 Failed: key 0x2, asc 0x3a, ascq 0x1
Oct 03 09:12:24.562: vmx| VIDE: ATAPI DMA 0x25 Failed: key 0x2, asc 0x3a, ascq 0x1
Oct 03 09:12:24.565: vmx| VIDE: ATAPI DMA 0x25 Failed: key 0x2, asc 0x3a, ascq 0x1
Oct 03 09:12:24.569: vmx| VIDE: ATAPI DMA 0x25 Failed: key 0x2, asc 0x3a, ascq 0x1
....
I have also attached another log .. all I did here was to power it up and then turn it off (from the Windows XP startup screen without even logging in).
This is, to say the least, frustrating. I will try going back to vmware 7.0.1 ... at least I can live with occasional freezes.
Subu
Moved to the VMware Workstation forum.
Dave
VMware Communities User Moderator
Now available - vSphere Quick Start Guide
Do you have a system or PCI card working with VMDirectPath? Submit your specs to the Unofficial VMDirectPath HCL.
numvcpus = 4
no wonder that VM is slow - use 1 or max 2 vCPUs instead
_________________________
VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook
In addition to continuum's suggestion to reduce the number of virtual CPUs - which most likely is the root cause of your issue - you should also consider to delete some or all of your snapshots. If you consider to delete all snapshots, delete them one-by-one and always the one next to the base disk in order to not run out of disk space. Right now - with the 2GB sparse disks and the 6 snapshots - VMware Workstation has to handle 700 files which make up your 200GB virtual disk!
@Continuum:
Does it make a huge difference running a VM with 1002GB files compared to 1200GB file? Would it be advisable to convert/clone it to a single file?
André
Does it make a huge difference running a VM with 1002GB files compared to 1200GB file? Would it be advisable to convert/clone it to a single file?
In lab conditions where you create the 200gb file on an otherwise blank disk I guess yes - here the monolithic file should be slightly faster.
In real life conditions it may be the other way round as probably the monolithic file would also be created in many fragments.
In this case the 2gb slices would have an advantage as the single 2gb slices can be defragmented - defragmenting a 200gb file maybe impossible depending on the amount of free space on disk.
Another aspect is the amount of open files the host can handle - here the monolithic file of course has an advantage.
_________________________
VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook