Hi,
I have a question about how the vmem file works if I may, as follows:
Enviroment:
Host: Win8Pro 64bit, 32GB Ram, 1pCPU w/ 8pCores.
Guest: Win7Pro 32bit, 3GB Ram, 1vCPU w/ 2vCores, ~80GB single file vmdk, vController is SCSI.
Scenario:
Sleep the Win7 Guest.
Close VMware Workstation,
I see the drive activity light on spindle that holds the vmdk is still illuminated (btw, it takes several minutes to go out).
While the drive activity light on spindle that holds the vmdk is still illuminated, Win8's Resource Monitor shows significant, but gradually declining, write activity on the VM's vmem file.
While there is significant, but gradually declining, write activity on the VM's vmem file, Win8's Disk Manager is unresponsive if you try to open it.
After several minutes (as mentioned above), the drive activity light on spindle that holds the vmdk finally goes off. Win8's Resource Monitor now shows no write activity on the VM's vmem file. Win8's Disk Manager now opens immediately and is responsive.
I would think that once the VM was put to sleep, and especially when VMware Workstation is then immediately closed, that the vmem file would also be closed by that time.
Btw, "Disable Memory Paging" is not checked and I did also try it with it checked, but it made no difference.
Any insight why that vmem file hangs onto life that long?
Thanks . . .