Hi, I have 2 VM running on my windows PC. It seems that it is not possible to split these two vm to have separate network?
I noticed, if i set VM-A to Bridged to WIFI, VM-B to bridged to ethernet. Then i go back to VM-A, i noticed it goes back to WIFI.
What can i do to split them so they have independant network connection?
Thanks,
AT
I'm getting this message when using VMWare player 12 on windows 7 x64 (running windows 7 x64 image) - "No 3D support is available from the host".
Graphics card is a Nvidia Quadro FX 580 and I'm using the latest available nvidia drivers in the host (341.81)
Everything worked ok on all previous player versions (6 and 7) - reverted to 7.1.2 and 3D work ok.
Is vmware dropping 3D support on Nvidia Quadro FX 580 graphics card? Any ideas on how to have this sorted?
Thanks
Hello again. This is not the first time I've had a problem like this (see Streaming not working in Player 5.0.0 and 5.0.1 on Windows)
Streaming is documented in the manual, for Workstation 12 Player VMware Workstation 12 Player for Windows Documentation Center
When Player 7 was released, streaming stopped working again, popping up a "File not found" error. I just stayed on Player 6.
Now I saw that the new Player was released. I installed it, anxious to see if the killer feature I have come to rely on has started working again. It has not.
Interesting excerpts from the log:
2015-08-25T22:33:09.479-07:00| vmplayer| I125: Command line: "C:\Program Files (x86)\VMware\VMware Player\vmplayer.exe" "http://my.host/vm_images/test/test.vmx" 2015-08-25T22:33:12.739-07:00| vmplayer| I125: DictionaryLoad: Cannot open file "http://my.host/vm_images/test/test.vmx": The filename, directory name, or volume label syntax is incorrect. 2015-08-25T22:33:12.739-07:00| vmplayer| W115: CnxFSVMDB::IsEncryptedConfigFile: Failed to load dictionary. Cannot open file "http://my.host/vm_images/test/test.vmx": The filename, directory name, or volume label syntax is incorrect. 2015-08-25T22:33:12.739-07:00| vmplayer| W115: 2015-08-25T22:33:13.270-07:00| vmplayer| I125: VMMgr::OpenVM (cfgPath=C:\Users\myuser\mycwd\http:\my.host\vm_images\test\test.vmx) 2015-08-25T22:33:13.270-07:00| vmplayer| I125: DictionaryLoad: Cannot open file "C:\Users\myuser\mycwd\http:\my.host\vm_images\test\test.vmx": The filename, directory name, or volume label syntax is incorrect. 2015-08-25T22:33:13.270-07:00| vmplayer| W115: CnxFSVMDB::IsEncryptedConfigFile: Failed to load dictionary. Cannot open file "C:\Users\myuser\mycwd\http:\my.host\vm_images\test\test.vmx": The filename, directory name, or volume label syntax is incorrect. 2015-08-25T22:33:13.270-07:00| vmplayer| W115: 2015-08-25T22:33:13.285-07:00| vthread-9| I125: VTHREAD initialize thread 9 "vthread-9" host id 2084 2015-08-25T22:33:13.285-07:00| vthread-9| I125: VMHS_ManageVM failed: ret = File not found 2015-08-25T22:33:13.285-07:00| vthread-9| I125: Cmd /host2/#_client/util/vm/cmd/##9/op/manageVM/ failed: File not found 2015-08-25T22:33:13.285-07:00| vmplayer| I125: DlgUI: Error while opening the virtual machine: File not found. 2015-08-25T22:33:13.301-07:00| vmplayer| I125: VMMgr: Failed to open pending VM: File not found 2015-08-25T22:35:02.782-07:00| vmplayer| I125: WORKER: asyncOps=0 maxActiveOps=0 maxPending=0 maxCompleted=0 2015-08-25T22:35:02.797-07:00| vmplayer| I125: Clean exit.
Let me know if you need any more information to track down this bug, or if there's some better place to go about reporting it. This forum seemed to work OK last time. In retrospect, I should have reported the issue when Player 7 came out. Maybe you guys need to add this as a regression test to your test suite
Thanks,
Jeremy
I have a few VM's that are always suspended.
While Player 6 recognized size and position, player 7 only recognized the size.
With Player 12 it doesn't do both, the VM always starts in fullscreen mode.
That's annoying
Hi,
I'm running WMware Player 4.0.4 and need to use the autofit feature for my guest.
I put the following lines to my ..\userprofile\Applikation Data\VMware\prefernces.ini file:
pref.autoFitGuestToWindow = "TRUE"
pref.autoFit = "FALSE"
pref.autoFitFullScreen = "fitGuestToHost"
These settings are working in VMware Worlstation 8 but somehow not in VMware Player 4.
Are there any other settings for WMware Player?
Any other suggestions?
Thanks in advance,
Alex
- VMware Tools are installed
- Host -> W2K3
- Guest -> WinXP
It really sucks - VMWare killed unity mode in Player 12. Had I known I would have stuck to Player 7 - it was working fine.
Anyone know if there's any way to get the installer for 7?
Thanks
I've got a CentOS VM running a family-only OwnCloud server (non-commercial in every sense of the word - I have 4 users, and the heaviest is my mom, who uses it to sync recipes and Bible study notes).
The VM is currently running in VMware Workstation Player 12 on a CentOS server. It would be most convenient to have this thing run as a daemon, but it looks like VIX standalone either isn't available yet or won't be available at all - so what I've done is installed Workstation in demo mode and I'm using vmrun -T player blah blah nogui to get it running in the background.
So now here's the question: What happens at the end of 30 days? Will Player continue to work?
version=7.1.2 build=build-2780323
on Ubuntu Server 15.04
Hello everyone,
I experience from time to time a strange storage size issue: an error message says that the disk storing the VM is almost full, although:
Is Player expecting the available space on the disk to be the same as the current size of the VM?
Does anyone know a workaround - besides deleting/moving files from the disk - before that issue is fixed?
After my upgrade to Windows 10 I was unable to use VMWare Player 6.0.1 but also unable to upgrade or remove.
To upgrade the installer needed to remove the previous version but was unable to locate the MSI and if I run the 6.0.1 installer Windows tells me "This app can't run on this PC". I've tried using the 6.0.0 and 6.0.2 and 7.1.2 installed but they all fail on locating the 6.0.1 MSI.
I've tried running the VMWare remove executable, it did run successfully but still I am not able to remove the program. I've used Revo Uninstaller. remove the VMWare directories from Program Files and ProgramData but somehow the 7.1.2 installer still SEES an installation of VMWare.
My question is, how is it that the 7.1.2 installer (or any other installer for that matter) still see a previous install? They can't even see which version is installed: "Before setup can proceed with installing VMWare Player, the following products must be uninstalled: (Version: ) "
when I try to open the ova file usign vmware player I get the attached error message. The log file is also attached for reference. Please provide suggestion to successfully use the required software.
Regards
Lakshmi
Hi,
I'm using VMWare Player 6.0.3 for running a 64 Bit Ubuntu machine under Windows 8.1. When I start a Virtualbox Vagrant machine (64 Bit Debian) inside the Ubuntu machine, I get Windows bluescreens approximately every half an hour with a CRITICAL_STRUCTURE_CORRUPTION error. I have already read that there were such errors in earlier versions of VMWare Player that have been fixed, however the problem still exists in the latest version given my setup. Is there any possible fix for this problem?
Thank you,
Jörg
Hello,
I can't configure network adapters for using VIRL. According to VIRL via VMware Player I should choose VMnet1, VMnet2, etc. after import image. But I can see only VMnet0, VMnet1 and VMnet8. (See screen-shot attached)
Could you please help me to resolve the problem?
Thank you.
What is the difference between VMware Player 7, which I've been using for close to a year (and earlier versions before that), and VMware Workstation 12 Player which has just been released, both of which are available on the same download page. Is it simply a name change for the latest version? And if so, why isn't it offered as an update from within VMware Player 7?
I tried installing v12 over v7 in a VMware Fusion 8 Pro Win 7 Pro VM and the installation simply wouldn't work, essentially grinding to a halt when the v12 Tools were being installed. I eventually tried uninstalling Tools from the v7 guest, then uninstalling v7, and then installing v12. While that worked, the v12 Tools still failed with an ongoing problem with video support and guest screen resolution.
Up until now, progression from one version of Player to another has been problem-free. Is the issue with VMware Workstation 12 Player, or is it, perhaps, with Fusion 8 Pro, which seems to have its own Tools installation problems?
My VM Player gets stuck- does not boot up. It says, configuring DHCP.. and waits there ad infinitum.
I have 3 large .vmdk files (about 65 gb).
At the minimum, I want to retrieve my data from inside those files.
Can someone please suggest what I might be able to do?
I want to go in somehow and fix the troubling DHCP server (inside the VM), come back and restart. Is it even possible?
What was that movie, when the sun had some kind of problem, a team of brave scientists went inside the sun, did some explosion work and safely came back, that's why we have (will have) a working sun.
So may be someone know how to fix this as well.
Thanks for reading.
Hi,
I'm running VMWare Player 7.1.2 with Windows 8.1 as the host and Debian Linux as the target. I want to run the network adapter in NAT mode for the isolation it provides to Linux. I have hardened my windows machines and thus, have configured the windows firewall to block all outgoing connections except those covered by specific rules. When I turn this firewall blocking OFF, NAT networking works fine, when I turn it ON, NAT doesn't work. I've tried adding every firewall rule I can think of, such as allowing vmnat, VMnetDHCP, and vmware-authd, both as a program and as a service. The rules I've configured include all ports and protocols. No rule allows NAT traffic from VMWare Player.
Thoughts?
Product: VMware® Player
Version 6.0.5 build-2443746
Host Operating system: Windows XP
Virtual Machine Op System : Windows XP
Hello I am new to the forum so hope this is posted correctly and my knowledge of VMware products is very much limited so please bear with me.
I am experiencing some issue while installing VMware Player. I have the required VMDK file and have correctly selected it within the program but upon launch the program faults with a Trap 00000006 Error (image attached). I have uninstalled and gone through the process again but I am still met with the same error!
After looking online this would seem to suggest that the system files of my VMDK are corrupt or damaged?
Any advice would be much appreciated.
Hello,
it was possible some years ago to use comercial Fusion licenses to run Player too.
Now on Fusion 8 this doesn't work.
I cant find any information on VMware's website.
How as clearer informations?
best regards,
Mike
Hello -- I have an old version of player on my computer (v2.5) -- I can't seem to find an uninstall option to
remove it -- is there a manual way to do this? Thanks
Hello Forum!
Because of my Project for the school leaving examination, I need to run the Mac OS X Lion in my VMware player.
When I want to start the VM, i get this Error:
>>Mac OS X is not supported with binary translation. To run Mac OS X you need a host on which VMware Player supports Intel VT-x or AMD-V.<<
Its my first use of the VMware player, so i don't really know what to do.
Could anybody help me, and say whats the problem and how can i fix it?
best regards from Austria, Franz
Hi All,
I am using VMWarePlayer, freebie version, 6.0.7 build-2844087.
I am running windows7 ultimate as the host operating system.
I am an MSDN so I have the MSDN versions of all these things.
I have been using vmware for ages and, quite suddenly, I am getting errors.
I suspect it is the underlying hard drive so let me tell you the symptoms.
It might not be the hard drive...it could be a vmware player problem too.
The log below tells you what is coming out of the log.
However I notice that on the two VMs that I use the most that the virtual disks have grown to 219GB for my win7 and 236GB for my Windows Server 2012 VM. This is very excessive growth since the last backup versions were win7 186gb and 2012 windows server 161GB.
It is not reasonable to add 40GB and 60GB in a few weeks. The last backups were on 2015-08-15.
I have twice run the win7 checkdisk with repair. The underlying disk is 3TB so it takes about 8 hours to do that.
The checkdisk repair does find a bad sector in the win7 machine each time but I think the problem must be different.
Why? Because I have never had a problem on the windows server 2012 disk. And I have not used it for a couple of weeks. I started it today just to empty out the drop box associated with it and it immediately got the same problem.
I downloaded vmware-vdiskmanager in the SDK and ran these two commands as follows.
E:\temp\vmware sdk\bin>vmware-vdiskmanager -R "E:\01-VirtualMachines\Win7Desktop\Windows 7 Desktop.vmdk"
VixDiskLib: Invalid configuration file parameter. Failed to read configuration file.
The virtual disk, 'E:\01-VirtualMachines\Win7Desktop\Windows 7 Desktop.vmdk', was corrupted and has been successfully repaired.
E:\temp\vmware sdk\bin>vmware-vdiskmanager -R "E:\01-VirtualMachines\IBIDEV02\IBIDEV02.vmdk"
VixDiskLib: Invalid configuration file parameter. Failed to read configuration file.
The virtual disk, 'E:\01-VirtualMachines\IBIDEV02\IBIDEV02.vmdk', was corruptedand has been successfully repaired.
Even so I started the Win7 VMWare again and it issued the same error very soon after starting.
This is making my VMs unusable and I an concerned to start any more VMs for fear this is a VMware problem that is actually somehow damaging the virtual disks.
Has anyone seen this before? I am thinking of unistalling and re-installing VMWARE just to see if that makes the machine stable again.
Any and all tips would be very much appreciated.
Best Regards
Peter
2015-09-07T15:39:42.812+02:00| vmx| I120: Msg_Question:
2015-09-07T15:39:42.812+02:00| vmx| I120: [msg.vmxaiomgr.retrycontabort.rudeunplug] The operation on file "E:\01-VirtualMachines\Win7Desktop\Windows 7 Desktop.vmdk" failed.
2015-09-07T15:39:42.812+02:00| vmx| I120+ If the file resides on a remote file system, make sure that the network connection and the server where this disk resides are functioning properly. If the file resides on removable media, reattach the media.
2015-09-07T15:39:42.812+02:00| vmx| I120+ Select Retry to attempt the operation again.
2015-09-07T15:39:42.812+02:00| vmx| I120+ Select Cancel to end this session.
2015-09-07T15:39:42.812+02:00| vmx| I120+ Select Continue to forward the error to the guest operating system.
2015-09-07T15:39:42.812+02:00| vmx| I120: ----------------------------------------
2015-09-07T15:39:50.021+02:00| vmx| I120: MsgQuestion: msg.vmxaiomgr.retrycontabort.rudeunplug reply=2
2015-09-07T15:39:50.021+02:00| vmx| I120: DISKLIB-LIB : RWv failed ioId: #46125 (1507337) (9) .
2015-09-07T15:39:50.021+02:00| vmx| I120: DISK: Disk i/o on scsi0:0 failed: Data error (cyclic redundancy check) (1507337)
2015-09-07T15:39:50.021+02:00| vmx| I120: ###### dumping content of iov ######
2015-09-07T15:39:50.021+02:00| vmx| I120: READ
2015-09-07T15:39:50.021+02:00| vmx| I120: startSector = 90502920
2015-09-07T15:39:50.021+02:00| vmx| I120: numSectors = 56
2015-09-07T15:39:50.021+02:00| vmx| I120: numBytes = 28672
2015-09-07T15:39:50.021+02:00| vmx| I120: numEntries = 7
2015-09-07T15:39:50.021+02:00| vmx| I120: entries[0] = 1C387F000 / 4096
2015-09-07T15:39:50.021+02:00| vmx| I120: entries[1] = 1B9400000 / 4096
2015-09-07T15:39:50.021+02:00| vmx| I120: entries[2] = 1B9581000 / 4096
2015-09-07T15:39:50.021+02:00| vmx| I120: entries[3] = 188102000 / 4096
2015-09-07T15:39:50.021+02:00| vmx| I120: entries[4] = 188683000 / 4096
2015-09-07T15:39:50.021+02:00| vmx| I120: entries[5] = 187484000 / 4096
2015-09-07T15:39:50.021+02:00| vmx| I120: entries[6] = 188505000 / 4096
2015-09-07T15:39:50.021+02:00| vmx| I120: scsi0:0: Command READ(10) took 44.796 seconds (ok)
2015-09-07T15:39:50.021+02:00| vmx| I120: scsi0:0: Command WRITE(10) took 7.560 seconds (ok)
2015-09-07T15:39:50.021+02:00| vmx| I120: scsi0:0: Command WRITE(10) took 7.560 seconds (ok)
2015-09-07T15:39:50.021+02:00| vmx| I120: scsi0:0: Command READ(10) took 10.326 seconds (ok)
2015-09-07T15:39:50.021+02:00| vmx| I120: scsi0:0: Command READ(10) took 10.337 seconds (ok)
2015-09-07T15:39:50.021+02:00| vmx| I120: scsi0:0: Command READ(10) took 13.530 seconds (ok)
2015-09-07T15:39:50.021+02:00| vmx| I120: scsi0:0: Command READ(10) took 13.528 seconds (ok)
2015-09-07T15:39:50.021+02:00| vmx| I120: scsi0:0: Command READ(10) took 10.420 seconds (ok)
2015-09-07T15:39:53.034+02:00| vmx| I120: scsi0:0: Command WRITE(10) took 2.598 seconds (ok)
2015-09-07T15:39:53.034+02:00| vmx| I120: scsi0:0: Command WRITE(10) took 2.568 seconds (ok)
2015-09-07T15:39:53.050+02:00| vmx| I120: scsi0:0: Command READ(10) took 2.935 seconds (ok)
2015-09-07T15:39:53.059+02:00| vmx| I120: scsi0:0: Command READ(10) took 2.935 seconds (ok)
2015-09-07T15:39:53.087+02:00| vmx| I120: scsi0:0: Command READ(10) took 2.953 seconds (ok)
2015-09-07T15:39:56.120+02:00| vmx| I120: VMXAIOMGR: Retry on read "E:\01-VirtualMachines\Win7Desktop\Windows 7 Desktop.vmdk" : Data error (cyclic redundancy check).
2015-09-07T15:39:56.120+02:00| vmx| I120: VMXAIOMGR: system : err=170002 errCode=23 freeSpace=1338803728384
2015-09-07T15:39:56.120+02:00| vmx| I120: VMXAIOMGR: "E:\01-VirtualMachines\Win7Desktop\Windows 7 Desktop.vmdk" : read s=155051954176 n=28672 ne=7, fai=0
2015-09-07T15:39:56.120+02:00| vmx| I120: VMXAIOMGR: v[0]=12BF7000:4096
2015-09-07T15:39:56.120+02:00| vmx| I120: VMXAIOMGR: v[1]=12C15000:4096
2015-09-07T15:39:56.120+02:00| vmx| I120: VMXAIOMGR: v[2]=12C19000:4096
2015-09-07T15:39:56.120+02:00| vmx| I120: VMXAIOMGR: v[3]=12C21000:4096
2015-09-07T15:39:56.120+02:00| vmx| I120: VMXAIOMGR: v[4]=1557A000:4096
2015-09-07T15:39:56.120+02:00| vmx| I120: VMXAIOMGR: v[5]=155B6000:4096
2015-09-07T15:39:56.120+02:00| vmx| I120: VMXAIOMGR: v[6]=F179000:4096
2015-09-07T15:39:56.120+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.004 seconds (ok)
2015-09-07T15:39:56.120+02:00| vmx| I120: scsi0:0: Command WRITE(10) took 1.663 seconds (ok)
2015-09-07T15:39:56.120+02:00| vmx| I120: scsi0:0: Command WRITE(10) took 1.663 seconds (ok)
2015-09-07T15:39:56.120+02:00| vmx| I120: scsi0:0: Command READ(10) took 2.998 seconds (ok)
2015-09-07T15:39:56.121+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.033 seconds (ok)
2015-09-07T15:39:56.121+02:00| vmx| I120: scsi0:0: Command READ(10) took 6.090 seconds (ok)
2015-09-07T15:39:56.121+02:00| vmx| I120: scsi0:0: Command READ(10) took 6.093 seconds (ok)
2015-09-07T15:39:59.332+02:00| vmx| I120: scsi0:0: Command WRITE(10) took 1.875 seconds (ok)
2015-09-07T15:39:59.342+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.128 seconds (ok)
2015-09-07T15:39:59.355+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.175 seconds (ok)
2015-09-07T15:39:59.356+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.175 seconds (ok)
2015-09-07T15:39:59.376+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.125 seconds (ok)
2015-09-07T15:40:02.497+02:00| vmx| I120: VMXAIOMGR: Retry on read "E:\01-VirtualMachines\Win7Desktop\Windows 7 Desktop.vmdk" : Data error (cyclic redundancy check).
2015-09-07T15:40:02.497+02:00| vmx| I120: VMXAIOMGR: system : err=170002 errCode=23 freeSpace=1338803728384
2015-09-07T15:40:02.497+02:00| vmx| I120: VMXAIOMGR: "E:\01-VirtualMachines\Win7Desktop\Windows 7 Desktop.vmdk" : read s=155051954176 n=28672 ne=7, fai=0
2015-09-07T15:40:02.497+02:00| vmx| I120: VMXAIOMGR: v[0]=12BF7000:4096
2015-09-07T15:40:02.497+02:00| vmx| I120: VMXAIOMGR: v[1]=12C15000:4096
2015-09-07T15:40:02.497+02:00| vmx| I120: VMXAIOMGR: v[2]=12C19000:4096
2015-09-07T15:40:02.497+02:00| vmx| I120: VMXAIOMGR: v[3]=12C21000:4096
2015-09-07T15:40:02.497+02:00| vmx| I120: VMXAIOMGR: v[4]=1557A000:4096
2015-09-07T15:40:02.497+02:00| vmx| I120: VMXAIOMGR: v[5]=155B6000:4096
2015-09-07T15:40:02.497+02:00| vmx| I120: VMXAIOMGR: v[6]=F179000:4096
2015-09-07T15:40:02.497+02:00| vmx| I120: scsi0:0: Command WRITE(10) took 2.048 seconds (ok)
2015-09-07T15:40:02.497+02:00| vmx| I120: scsi0:0: Command WRITE(10) took 1.434 seconds (ok)
2015-09-07T15:40:02.497+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.140 seconds (ok)
2015-09-07T15:40:02.498+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.124 seconds (ok)
2015-09-07T15:40:02.498+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.106 seconds (ok)
2015-09-07T15:40:02.498+02:00| vmx| I120: scsi0:0: Command READ(10) took 6.245 seconds (ok)
2015-09-07T15:40:02.498+02:00| vmx| I120: scsi0:0: Command READ(10) took 6.255 seconds (ok)
2015-09-07T15:40:05.399+02:00| vmx| I120: scsi0:0: Command READ(10) took 2.900 seconds (ok)
2015-09-07T15:40:05.401+02:00| vmx| I120: scsi0:0: Command READ(10) took 2.902 seconds (ok)
2015-09-07T15:40:08.499+02:00| vmx| I120: VMXAIOMGR: Retry on read "E:\01-VirtualMachines\Win7Desktop\Windows 7 Desktop.vmdk" : Data error (cyclic redundancy check).
2015-09-07T15:40:08.499+02:00| vmx| I120: VMXAIOMGR: system : err=170002 errCode=23 freeSpace=1338803728384
2015-09-07T15:40:08.499+02:00| vmx| I120: VMXAIOMGR: "E:\01-VirtualMachines\Win7Desktop\Windows 7 Desktop.vmdk" : read s=155051954176 n=28672 ne=7, fai=0
2015-09-07T15:40:08.499+02:00| vmx| I120: VMXAIOMGR: v[0]=12BF7000:4096
2015-09-07T15:40:08.499+02:00| vmx| I120: VMXAIOMGR: v[1]=12C15000:4096
2015-09-07T15:40:08.499+02:00| vmx| I120: VMXAIOMGR: v[2]=12C19000:4096
2015-09-07T15:40:08.499+02:00| vmx| I120: VMXAIOMGR: v[3]=12C21000:4096
2015-09-07T15:40:08.499+02:00| vmx| I120: VMXAIOMGR: v[4]=1557A000:4096
2015-09-07T15:40:08.499+02:00| vmx| I120: VMXAIOMGR: v[5]=155B6000:4096
2015-09-07T15:40:08.499+02:00| vmx| I120: VMXAIOMGR: v[6]=F179000:4096
2015-09-07T15:40:08.499+02:00| vmx| I120: scsi0:0: Command WRITE(10) took 2.045 seconds (ok)
2015-09-07T15:40:08.499+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.099 seconds (ok)
2015-09-07T15:40:08.499+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.098 seconds (ok)
2015-09-07T15:40:08.499+02:00| vmx| I120: scsi0:0: Command READ(10) took 5.990 seconds (ok)
2015-09-07T15:40:08.500+02:00| vmx| I120: scsi0:0: Command READ(10) took 5.997 seconds (ok)
2015-09-07T15:40:08.500+02:00| vmx| I120: scsi0:0: Command READ(10) took 6.000 seconds (ok)
2015-09-07T15:40:11.442+02:00| vmx| I120: scsi0:0: Command READ(10) took 2.938 seconds (ok)
2015-09-07T15:40:11.458+02:00| vmx| I120: scsi0:0: Command READ(10) took 1.998 seconds (ok)
2015-09-07T15:40:11.461+02:00| vmx| I120: scsi0:0: Command READ(10) took 2.939 seconds (ok)
2015-09-07T15:40:11.472+02:00| vmx| I120: scsi0:0: Command READ(10) took 2.971 seconds (ok)
2015-09-07T15:40:11.483+02:00| vmx| I120: scsi0:0: Command READ(10) took 2.981 seconds (ok)
2015-09-07T15:40:14.712+02:00| vmx| I120: VMXAIOMGR: Retry on read "E:\01-VirtualMachines\Win7Desktop\Windows 7 Desktop.vmdk" : Data error (cyclic redundancy check).
2015-09-07T15:40:14.712+02:00| vmx| I120: VMXAIOMGR: system : err=170002 errCode=23 freeSpace=1338803728384
2015-09-07T15:40:14.712+02:00| vmx| I120: VMXAIOMGR: "E:\01-VirtualMachines\Win7Desktop\Windows 7 Desktop.vmdk" : read s=155051954176 n=28672 ne=7, fai=0
2015-09-07T15:40:14.712+02:00| vmx| I120: VMXAIOMGR: v[0]=12BF7000:4096
2015-09-07T15:40:14.712+02:00| vmx| I120: VMXAIOMGR: v[1]=12C15000:4096
2015-09-07T15:40:14.712+02:00| vmx| I120: VMXAIOMGR: v[2]=12C19000:4096
2015-09-07T15:40:14.712+02:00| vmx| I120: VMXAIOMGR: v[3]=12C21000:4096
2015-09-07T15:40:14.712+02:00| vmx| I120: VMXAIOMGR: v[4]=1557A000:4096
2015-09-07T15:40:14.712+02:00| vmx| I120: VMXAIOMGR: v[5]=155B6000:4096
2015-09-07T15:40:14.712+02:00| vmx| I120: VMXAIOMGR: v[6]=F179000:4096
2015-09-07T15:40:14.712+02:00| vmx| I120: scsi0:0: Command WRITE(10) took 1.922 seconds (ok)
2015-09-07T15:40:14.713+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.269 seconds (ok)
2015-09-07T15:40:14.713+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.088 seconds (ok)
2015-09-07T15:40:14.713+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.079 seconds (ok)
2015-09-07T15:40:14.713+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.216 seconds (ok)
2015-09-07T15:40:14.713+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.101 seconds (ok)
2015-09-07T15:40:14.713+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.123 seconds (ok)
2015-09-07T15:40:17.648+02:00| vmx| I120: scsi0:0: Command WRITE(10) took 1.194 seconds (ok)
2015-09-07T15:40:17.662+02:00| vmx| I120: scsi0:0: Command READ(10) took 2.949 seconds (ok)
2015-09-07T15:40:17.677+02:00| vmx| I120: scsi0:0: Command READ(10) took 2.963 seconds (ok)
2015-09-07T15:40:17.685+02:00| vmx| I120: scsi0:0: Command READ(10) took 2.967 seconds (ok)
2015-09-07T15:40:17.694+02:00| vmx| I120: USBGW: Write arbitrator op:13 len:22
2015-09-07T15:40:17.703+02:00| vmx| I120: scsi0:0: Command READ(10) took 2.987 seconds (ok)
2015-09-07T15:40:17.712+02:00| vmx| I120: scsi0:0: Command READ(10) took 2.998 seconds (ok)
2015-09-07T15:40:17.778+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.058 seconds (ok)
2015-09-07T15:40:20.864+02:00| vmx| I120: VMXAIOMGR: Retry on read "E:\01-VirtualMachines\Win7Desktop\Windows 7 Desktop.vmdk" : Data error (cyclic redundancy check).
2015-09-07T15:40:20.864+02:00| vmx| I120: VMXAIOMGR: system : err=170002 errCode=23 freeSpace=1338803728384
2015-09-07T15:40:20.864+02:00| vmx| I120: VMXAIOMGR: "E:\01-VirtualMachines\Win7Desktop\Windows 7 Desktop.vmdk" : read s=155051954176 n=28672 ne=7, fai=0
2015-09-07T15:40:20.864+02:00| vmx| I120: VMXAIOMGR: v[0]=12BF7000:4096
2015-09-07T15:40:20.864+02:00| vmx| I120: VMXAIOMGR: v[1]=12C15000:4096
2015-09-07T15:40:20.864+02:00| vmx| I120: VMXAIOMGR: v[2]=12C19000:4096
2015-09-07T15:40:20.864+02:00| vmx| I120: VMXAIOMGR: v[3]=12C21000:4096
2015-09-07T15:40:20.864+02:00| vmx| I120: VMXAIOMGR: v[4]=1557A000:4096
2015-09-07T15:40:20.864+02:00| vmx| I120: VMXAIOMGR: v[5]=155B6000:4096
2015-09-07T15:40:20.864+02:00| vmx| I120: VMXAIOMGR: v[6]=F179000:4096
2015-09-07T15:40:20.865+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.170 seconds (ok)
2015-09-07T15:40:20.865+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.086 seconds (ok)
2015-09-07T15:40:20.865+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.091 seconds (ok)
2015-09-07T15:40:20.867+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.080 seconds (ok)
2015-09-07T15:40:20.989+02:00| vmx| I120: USBGW: Write arbitrator op:13 len:22
2015-09-07T15:40:21.181+02:00| vmx| I120: USBGW: Write arbitrator op:13 len:22
2015-09-07T15:40:21.237+02:00| vmx| I120: USBGW: Write arbitrator op:13 len:22
2015-09-07T15:40:21.325+02:00| vmx| I120: USBGW: Write arbitrator op:13 len:22
2015-09-07T15:40:21.805+02:00| vmx| I120: USBGW: Write arbitrator op:13 len:22
2015-09-07T15:40:23.764+02:00| vmx| I120: scsi0:0: Command READ(10) took 2.875 seconds (ok)
2015-09-07T15:40:23.764+02:00| vmx| I120: scsi0:0: Command WRITE(10) took 1.054 seconds (ok)
2015-09-07T15:40:23.783+02:00| vmx| I120: scsi0:0: Command READ(10) took 6.072 seconds (ok)
2015-09-07T15:40:26.752+02:00| vmx| I120: VMXAIOMGR: Retry on read "E:\01-VirtualMachines\Win7Desktop\Windows 7 Desktop.vmdk" : Data error (cyclic redundancy check).
2015-09-07T15:40:26.752+02:00| vmx| I120: VMXAIOMGR: system : err=170002 errCode=23 freeSpace=1338803728384
2015-09-07T15:40:26.752+02:00| vmx| I120: VMXAIOMGR: "E:\01-VirtualMachines\Win7Desktop\Windows 7 Desktop.vmdk" : read s=155051954176 n=28672 ne=7, fai=0
2015-09-07T15:40:26.752+02:00| vmx| I120: VMXAIOMGR: v[0]=12BF7000:4096
2015-09-07T15:40:26.752+02:00| vmx| I120: VMXAIOMGR: v[1]=12C15000:4096
2015-09-07T15:40:26.752+02:00| vmx| I120: VMXAIOMGR: v[2]=12C19000:4096
2015-09-07T15:40:26.752+02:00| vmx| I120: VMXAIOMGR: v[3]=12C21000:4096
2015-09-07T15:40:26.752+02:00| vmx| I120: VMXAIOMGR: v[4]=1557A000:4096
2015-09-07T15:40:26.752+02:00| vmx| I120: VMXAIOMGR: v[5]=155B6000:4096
2015-09-07T15:40:26.752+02:00| vmx| I120: VMXAIOMGR: v[6]=F179000:4096
2015-09-07T15:40:26.752+02:00| vmx| I120: Msg_Question:
2015-09-07T15:40:26.752+02:00| vmx| I120: [msg.vmxaiomgr.retrycontabort.rudeunplug] The operation on file "E:\01-VirtualMachines\Win7Desktop\Windows 7 Desktop.vmdk" failed.
2015-09-07T15:40:26.752+02:00| vmx| I120+ If the file resides on a remote file system, make sure that the network connection and the server where this disk resides are functioning properly. If the file resides on removable media, reattach the media.
2015-09-07T15:40:26.752+02:00| vmx| I120+ Select Retry to attempt the operation again.
2015-09-07T15:40:26.752+02:00| vmx| I120+ Select Cancel to end this session.
2015-09-07T15:40:26.752+02:00| vmx| I120+ Select Continue to forward the error to the guest operating system.
2015-09-07T15:40:26.752+02:00| vmx| I120: ----------------------------------------
2015-09-07T15:41:43.780+02:00| vmx| I120: MsgQuestion: msg.vmxaiomgr.retrycontabort.rudeunplug reply=1
2015-09-07T15:41:43.780+02:00| vmx| I120: Msg_Post: Warning
2015-09-07T15:41:43.781+02:00| vmx| I120: [msg.vmxaiomgr.corrupted] VMware Player cannot synchronize with the disk before canceling. Disk E:\01-VirtualMachines\Win7Desktop\Windows 7 Desktop.vmdk may be inconsistent.
2015-09-07T15:41:43.781+02:00| vmx| I120: ----------------------------------------
2015-09-07T15:41:43.816+02:00| vmx| I120: User requested abort: Exiting because of failed disk operation.
2015-09-07T15:41:43.816+02:00| vmx| W110: Win32 object usage: GDI 13, USER 22
2015-09-07T15:41:43.816+02:00| vmx| W110: Writing monitor corefile "E:\01-VirtualMachines\Win7Desktop\vmmcores.gz"
2015-09-07T15:41:43.816+02:00| vmx| I120: Counting amount of anonymous memory
2015-09-07T15:41:43.826+02:00| vmx| I120: Total Count of Anon Pages and CR3 pages 7395
2015-09-07T15:41:43.826+02:00| vmx| W110: Dumping core for vcpu-0
2015-09-07T15:41:43.827+02:00| vmx| I120: Beginning monitor coredump
2015-09-07T15:41:44.470+02:00| vmx| I120: End monitor coredump
2015-09-07T15:41:44.470+02:00| vmx| W110: Dumping core for vcpu-1
2015-09-07T15:41:44.470+02:00| vmx| I120: Beginning monitor coredump
2015-09-07T15:41:45.106+02:00| vmx| I120: End monitor coredump
2015-09-07T15:41:45.106+02:00| vmx| W110: Dumping core for vcpu-2
2015-09-07T15:41:45.106+02:00| vmx| I120: Beginning monitor coredump
2015-09-07T15:41:45.747+02:00| vmx| I120: End monitor coredump
2015-09-07T15:41:45.747+02:00| vmx| W110: Dumping core for vcpu-3
2015-09-07T15:41:45.748+02:00| vmx| I120: Beginning monitor coredump
2015-09-07T15:41:46.387+02:00| vmx| I120: End monitor coredump
2015-09-07T15:41:46.387+02:00| vmx| W110: Dumping extended monitor data
2015-09-07T15:41:48.286+02:00| vmx| I120: CoreDump: ei->size 38719488 : len = 38719488
2015-09-07T15:41:48.287+02:00| vmx| I120: Backtrace:
2015-09-07T15:41:48.294+02:00| vmx| I120: backtrace[00] frame 0x0012e388 IP 0x13f9cf12e params 0 0x170002 0x2 0x124546 ??? [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x13f980000 0x0001:0x0004e12e]
2015-09-07T15:41:48.295+02:00| vmx| I120: backtrace[01] frame 0x0012ecb0 IP 0x13f9a92c0 params 0x1400d30a0 0xb09007a0017 0x3d0e080 0xffffffffff ??? [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x13f980000 0x0001:0x000282c0]
2015-09-07T15:41:48.295+02:00| vmx| I120: backtrace[02] frame 0x0012ed60 IP 0x13fbc3272 params 0x17c7ae30 0x13fc011d4 0x137b6ebb000 0x7000 ??? [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x13f980000 0x0001:0x00242272]
2015-09-07T15:41:48.295+02:00| vmx| I120: backtrace[03] frame 0x0012edc0 IP 0x13fbc32dd params 0x183ac698 0x3a0420 0 0 ??? [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x13f980000 0x0001:0x002422dd]
2015-09-07T15:41:48.296+02:00| vmx| I120: backtrace[04] frame 0x0012edf0 IP 0x13fbc47ac params 0x39cf660 0 0x1f0 0x13f9a4744 ??? [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x13f980000 0x0001:0x002437ac]
2015-09-07T15:41:48.296+02:00| vmx| I120: backtrace[05] frame 0x0012ee20 IP 0x13fbc4d81 params 0x39cf660 0 0 0x13 ??? [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x13f980000 0x0001:0x00243d81]
2015-09-07T15:41:48.296+02:00| vmx| I120: backtrace[06] frame 0x0012ee50 IP 0x13f9e7634 params 0xffffffff 0x6 0 0x31c810 ??? [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x13f980000 0x0001:0x00066634]
2015-09-07T15:41:48.297+02:00| vmx| I120: backtrace[07] frame 0x0012f6c0 IP 0x13f9ea584 params 0x18169165b00 0 0x31c810 0x39cfca0 ??? [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x13f980000 0x0001:0x00069584]
2015-09-07T15:41:48.297+02:00| vmx| I120: backtrace[08] frame 0x0012f710 IP 0x13f9eab51 params 0 0 0x1403e2b30 0x13ff23e4e ??? [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x13f980000 0x0001:0x00069b51]
2015-09-07T15:41:48.297+02:00| vmx| I120: backtrace[09] frame 0x0012f760 IP 0x13f9aa25d params 0x3997e70 0 0x489d00 0x3997ab0 ??? [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x13f980000 0x0001:0x0002925d]
2015-09-07T15:41:48.297+02:00| vmx| I120: backtrace[10] frame 0x0012f840 IP 0x13f9aa841 params 0x487d60 0x3997ab0 0x2 0x140038b88 ??? [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x13f980000 0x0001:0x00029841]
2015-09-07T15:41:48.298+02:00| vmx| I120: backtrace[11] frame 0x0012f870 IP 0x13f98318f params 0 0x1 0 0 ??? [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x13f980000 0x0001:0x0000218f]
2015-09-07T15:41:48.298+02:00| vmx| I120: backtrace[12] frame 0x0012f8c0 IP 0x13f983257 params 0 0 0 0 ??? [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x13f980000 0x0001:0x00002257]
2015-09-07T15:41:48.298+02:00| vmx| I120: backtrace[13] frame 0x0012f970 IP 0x13f9811de params 0 0 0 0 ??? [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x13f980000 0x0001:0x000001de]
2015-09-07T15:41:48.300+02:00| vmx| I120: backtrace[14] frame 0x0012f978 IP 0x771959cd params 0 0 0 0 BaseThreadInitThunk + 0x000d [C:\Windows\system32\kernel32.dll base 0x77180000 0x0001:0x000149cd]
2015-09-07T15:41:48.302+02:00| vmx| I120: backtrace[15] frame 0x0012f9a8 IP 0x772cb981 params 0 0 0 0 RtlUserThreadStart + 0x0021 [C:\Windows\SYSTEM32\ntdll.dll base 0x772a0000 0x0001:0x0002a981]
2015-09-07T15:41:48.302+02:00| vmx| I120: Exiting
