Similar Questions

• VMware Workstation 6.5.1 - Drive error is not ready - Everytime - 5 other computer - 5 different installer downloads

  Hello

  It seems that whenever I have to "turn on" a virtual machine using VMware Workstation 6.5.1 I get an error disc is not ready . Give me continue, ignoring and Cancel the options I always support on continue.

  I think it's a memory allocation error.

  I tried it on 4 different computers and with 4 different operating systems. Every computer that I tried on was completely different, custom built computers. Except one, which is a laptop, to be precise, Dell Inspiron 700 Mr. others included Windows XP x 64 (on Computer1), Windows Vista x 64 (on Computer1), Windows XP (on laptop), Windows XP (on computer2) & Windows Vista (on computer3).

  Whenever I got it redownloaded from the VMware Web site, certainly isn't a problem on my end.

  One of these computers/OS I get an error similar to this one, below, when I turn "on" a virtual machine;

  

  Please fix this bug in your next version of VMware Workstation.

  Thanks in advance,

  Panarchy

  See this thread:

  http://communities.VMware.com/thread/105764

• VMware Workstation 10.0.3 on Debian Wheezy compilation error

  Hello

  I am trying to run VMware Workstation 10.0.3 on Debian Wheezy with custom RHEL kernel 3.10.0 - 4.

  Installation went well but when I try: vmware-modconfig - console - install-all I get the following error:

  Stopping VMware services:

  Demon of authentication makes VMware

  VM communication interface socket family is

  Virtual machine communication interface is

  Virtual machine monitor makes

  File system is blocking

  Using 2.6.x kernel build system.

  do: enter the directory "/ tmp/modconfig-Df4vT2/vmmon-only '.

  / usr/bin/make /lib/modules/3.10.0-4-pve/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = modules

  make [1]: Entering directory ' / usr/src/linux-headers-3.10.0-4-pve'

  CC [M] /tmp/modconfig-Df4vT2/vmmon-only/linux/driver.o

  CC [M] /tmp/modconfig-Df4vT2/vmmon-only/linux/driverLog.o

  CC [M] /tmp/modconfig-Df4vT2/vmmon-only/linux/hostif.o

  CC [M] /tmp/modconfig-Df4vT2/vmmon-only/common/comport.o

  CC [M] /tmp/modconfig-Df4vT2/vmmon-only/common/apic.o

  CC [M] /tmp/modconfig-Df4vT2/vmmon-only/common/cpuid.o

  CC [M] /tmp/modconfig-Df4vT2/vmmon-only/common/hashFunc.o

  CC [M] /tmp/modconfig-Df4vT2/vmmon-only/common/memtrack.o

  CC [M] /tmp/modconfig-Df4vT2/vmmon-only/common/phystrack.o

  CC [M] /tmp/modconfig-Df4vT2/vmmon-only/common/task.o

  CC [M] /tmp/modconfig-Df4vT2/vmmon-only/common/vmx86.o

  CC [M] /tmp/modconfig-Df4vT2/vmmon-only/vmcore/moduleloop.o

  /tmp/modconfig-Df4vT2/vmmon-only/Linux/driver.c:1342:1: warning: always_inline function might not be inlinable [-Wattributes]

  LD [M] /tmp/modconfig-Df4vT2/vmmon-only/vmmon.o

  Construction modules, step 2.

  MODPOST modules 1

  CC /tmp/modconfig-Df4vT2/vmmon-only/vmmon.mod.o

  LD [M] /tmp/modconfig-Df4vT2/vmmon-only/vmmon.ko

  make [1]: leaving directory ' / usr/src/linux-headers-3.10.0-4-pve'

  / usr/bin/make - c $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = postgeneration

  make [1]: entering directory ' / tmp/modconfig-Df4vT2/vmmon-only '.

  make [1]: 'postgeneration' is up-to-date.

  make [1]: leaving directory ' / tmp/modconfig-Df4vT2/vmmon-only '.

  CP f vmmon.ko. /... vmmon.o

  make: leaving directory ' / tmp/modconfig-Df4vT2/vmmon-only '.

  Using 2.6.x kernel build system.

  make: entering directory ' / tmp/modconfig-Df4vT2/vmnet-only»

  / usr/bin/make /lib/modules/3.10.0-4-pve/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = modules

  make [1]: Entering directory ' / usr/src/linux-headers-3.10.0-4-pve'

  CC [M] /tmp/modconfig-Df4vT2/vmnet-only/driver.o

  CC [M] /tmp/modconfig-Df4vT2/vmnet-only/hub.o

  CC [M] /tmp/modconfig-Df4vT2/vmnet-only/userif.o

  CC [M] /tmp/modconfig-Df4vT2/vmnet-only/netif.o

  CC [M] /tmp/modconfig-Df4vT2/vmnet-only/bridge.o

  CC [M] /tmp/modconfig-Df4vT2/vmnet-only/filter.o

  CC [M] /tmp/modconfig-Df4vT2/vmnet-only/procfs.o

  CC [M] /tmp/modconfig-Df4vT2/vmnet-only/smac_compat.o

  /tmp/modconfig-Df4vT2/vmnet-only/filter.c: in function 'VNetFilterHookFn ':

  /tmp/modconfig-Df4vT2/vmnet-only/filter.c:262:16: error: 'hooknum' undeclared (first use in this function)

  /tmp/modconfig-Df4vT2/vmnet-only/filter.c:262:16: Note: each identifier not declared is reported only once for each function it appears in

  make [2]: * [/ tmp/modconfig-Df4vT2/vmnet-only/filter.o] error 1

  make [2]: * waiting unfinished...

  make [1]: * 2 error [_module_/tmp/modconfig-Df4vT2/vmnet-only]

  make [1]: leaving directory ' / usr/src/linux-headers-3.10.0-4-pve'

  make: * [vmnet.ko] error 2

  make: leaving directory ' / tmp/modconfig-Df4vT2/vmnet-only.

  Cannot install all modules.  See the log for more details.

  Is there a solution for this?

  Thank you

  I just found a solution:

  1. CD/usr/lib/vmware/modules/source
  2. CP vmnet.tar vmnet.tar.bak
  3. tar - xvf vmnet.tar
  4. VI vmnet-only/filter.c
  5. replace all the entries with - #if LINUX_VERSION_CODE > = KERNEL_VERSION (3, 13, 0) to #if LINUX_VERSION_CODE > = KERNEL_VERSION (3, 10, 0) and save the file.
  6. tar vmnet.tar - uvf vmnet-only
  7. RM - r vmnet-only.
  8. VMware-modconfig - console - install-all

• Fatal error of VMware Workstation

  Hello

  I have serious problems with VMware Workstation (version 9.02) and unique virtual machine to Windows 8. VMware Workstation is installed x 64 host Windows 8. This unique virtual machine crashes randomly with the following error message:

  

  I have other virtual machines also but I have no problems with them. First of all, I thought it was a physical disk error and I moved this virtual machine to another drive, but it did not help. I reinstalled VMware Tools and even created a new virtual machine and cloned this issue with Acronis Backup & Restore machine for this. This due to the machine crashes with the same error, but every time you start so things went even worse.

  Any ideas what to do with it?

  I attach a log file.

  Post edited by: Demuz

  I updated to VMware Workstation 10 and reinstalled the whole problematic virtual machine from scratch, but it still crashed at random several times a day with the same error.

  But now things look well so far.

  Yesterday, I changed a setting. I unchecked "Accelerate 3D Graphics" settings of the virtual machine (under the display settings). After that, the virtual machine crashed 0 times and I've been using a whole day! I have Nvidia display with the latest adapter drivers Win 8.1 x 64 installed on the host machine. I think drivers Nvidia has something to do with this virtual machine crashing, maybe...

  I started to suspect the display driver Nvidia after seeing this nvd3dumpx.dll appears more than once in the log file (this is VMware Workstation logfile ater the crash):

  2013-10 - 07T 18: 14:03.625 + 03:00 | vthread-14 | I120: backtrace [00] framework 0x1004ee48 IP 0x7ff8c64db9af params 0 x 1 0 0 0? [C:\Windows\SYSTEM32\nvd3dumx.dll base 0x7ff8c5e00000 0x0001: 0x006da9af]

  2013-10 - 07T 18: 14:03.626 + 03:00 | vthread-14 | I120: backtrace [01] framework 0x1004eea0 IP 0x7ff8c655ee5c params 0xf2c680 0 0x116d5ee0 0? [C:\Windows\SYSTEM32\nvd3dumx.dll base 0x7ff8c5e00000 0x0001: 0x0075de5c]

  2013-10 - 07T 18: 14:03.627 + 03:00 | vthread-14 | I120: backtrace [02] frame IP 0x7ff8c649c5f8 params 0 x 1 0x1004f6c0 0 0x7ff800000000 0? [C:\Windows\SYSTEM32\nvd3dumx.dll base 0x7ff8c5e00000 0x0001: 0x0069b5f8]

  2013-10 - 07T 18: 14:03.627 + 03:00 | vthread-14 | I120: backtrace [03] framework 0x1004f6f0 IP 0x7ff8c649860d params 0xf2f280 0 0 0? [C:\Windows\SYSTEM32\nvd3dumx.dll base 0x7ff8c5e00000 0x0001: 0x0069760d]

  2013-10 - 07T 18: 14:03.628 + 03:00 | vthread-14 | I120: backtrace [04] framework 0x1004f720 IP 0x7ff8c64b7f43 params 0xf2f280 0 0 0? [C:\Windows\SYSTEM32\nvd3dumx.dll base 0x7ff8c5e00000 0x0001: 0x006b6f43]

  2013-10 - 07T 18: 14:03.628 + 03:00 | vthread-14 | I120: backtrace [05] framework 0x1004f750 IP 0x7ff8c673c2cf params 0x7ff800000000 0 0 0 QueryOglResource + 0x1d5c2f [C:\Windows\SYSTEM32\nvd3dumx.dll base 0x7ff8c5e00000 0x0001: 0x0093b2cf]

  2013-10 - 07T 18: 14:03.628 + 03:00 | vthread-14 | I120: backtrace [06] frame IP 0x7ff8c673c51a params 0 0x1004f780 0 0 0 QueryOglResource + 0x1d5e7a [C:\Windows\SYSTEM32\nvd3dumx.dll base 0x7ff8c5e00000 0x0001: 0x0093b51a]

  2013-10 - 07T 18: 14:03.630 + 03:00 | vthread-14 | I120: backtrace [07] frame IP 0x7ff8df941611 params 0 0x1004f788 0 0 0 BaseThreadInitThunk + 0x000d [C:\Windows\system32\KERNEL32. [DLL base 0x7ff8df940000 0x0001: 0 x 00000611]

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120: backtrace [08] frame IP 0x7ff8e08664ad params 0 0x1004f7b8 0 0 0 RtlUserThreadStart + 0x001d [C:\Windows\SYSTEM32\ntdll.dll base 0x7ff8e07f0000 0x0001: 0x000754ad]

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120: Msg_Post: error

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120: fatal error [msg.log.error.unrecoverable] VMware Workstation: (vthread-14)

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120 + Exception 0xc0000005 (access violation) occurred.

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120: [msg.panic.haveLog], a log file is available in "F:\VMware\Virtual Machines\vmware.log".

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120: [msg.panic.requestSupport.withoutLog] you can ask support.

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120: [msg.panic.requestSupport.vmSupport.windowsOrLinux]

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120 + to collect data to be submitted to VMware support, choose "Collect load data" in the Help menu.

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120 + you can also run the script 'vm-support' in the folder my computer directly.

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120: [msg.panic.response] we will respond on the basis of your entitlement to support.

• Problem with VMWare Workstation combo, .vhd virtual drives and physical disks in the sector of size 4K?

  All,

  I suspect something wrong with some of my virtual machines.  I have been using these virtual machines for a while, and I see some weird behaviour recently.

  I see a lot of corruption in the virtual hard disk (.vhd based).  CHKDSK automatically gets performed many large files such as Oracle datafiles get damaged etc...  It all seems quite random and inconsistent, but I am using .vhd virtual machines in VMWare Workstation for years without problem.  This problem is new, and hard drives are basically unstable.

  I * think * (and I'm totally off base) that is perhaps the issue with my new external hard drives.  These discs have a 4 KB sector size, without e512.  Thanks to this architecture of hard drive, don't mount not the tools of Microsoft or manupulate .vhd files on these disks.  The questions seem to go away if I switch to vmdk or switch to the physical hard disk size-one-sector 512kb.  Because errors are not compliant, that I don't really have a way to document/prove that is the case, but it seems to be.

  I use version 9.0.0 on Windows 7 Workstation, and the guest is Windows Server 2008R2.

  My question is:

  (1) what meaning?

  (2) how I prove/document, since it is a contradiction?

  (3) is this a known problem?

  (Btw, switching HDD's vmdk is not an option in our case due to an obscure legal agreement with Microsoft.  I have to distribute my VMs in vhd format, even if they are designed to run on VMWare...)

  -> Adam

  These discs have a 4 KB sector size, without e512.

  (I've highlighted "without e512" in "BOLD" to key in my answer to the host operating system.)

  -L'OS is Windows 7 Enterprise

  According to the political support for the 4 K sector hard drives in Windows, Windows 7 does not support the native 4 K (logical 4 k sector size) but it does not support Advanced Format or 512th (size of logical sector physical and 512 bytes of 4 K) and that is can be the question.

• Problem with keyboard Windows 8 on VMware Workstation 8 + start error!

  Hello

  I installed VMware Workstation 8 today to use Windows 8 Preview developers. But I have a problem.

  When I finished with the installation of Windows 8 I can't type anything. When I go to settings, the settings said: VMware keyboard driver is not installed on the host computer. How can I install it?

  EDIT: I had another problem. When I want to launch Windows 8 I get an error: the VMware authorization Service does not work.

  I can get 2 answers please?

  Thank you!

  Post edited by: MrMvanDoorn

  Install the keyboard on a Windows host, improved driver read page 130:

  http://www.VMware.com/PDF/WS80-using.PDF

  To start the VMware authorization Service: services.msc open with window to open the properties of privileges, select VMware authorization Service, administration and press start button.

• VMWare Workstation UI error

  I have a HP Pavilion DV7 running Windows 7 64-bit 4 GB of ram

  I'm trying to install VMWare Workstation as part of a communications car software install, whenever I get the same expired error, I downloaded from the internet the same version, the latest version and still the same, so I think that the problem is with my machine, even though everything else works perfectly.

  I don't have any antivirus installed and I tried to not disable the firewall... no joy.

  I read all kinds online but it is all over my head as I try fails.

  Y at - it someone who can display a resolution that is simple to follow and makes sense for a dummy code?

  Everyone please help.

  Thank you.

  Hi Mark,

  You can post your question to the community of VMware using the link below.

  http://communities.VMware.com/index.jspa

  I hope this helps.

• Error: "VMware Workstation has suspended this virtual machine because the disk on which the virtual machine is stored is almost full."

  I get this error message:

  VMware Workstation has suspended this virtual machine because the disk on which the virtual machine is stored is almost full. To continue, free 1.3 GB of additional disk space.

  I read up on the subject and found that I have to re size a partition. Anyone know what it could be? I can't find anything that looks like it has something to do with VMware. Does anyone know what size and what file system is it?

  My OS:
  Tumbleweed OpenSUSE x 64

  Thanks in advance

  On more creative, my home and root file systems were not extended to my full disk space :^)

• installation of vmware workstation 6.5 on windows 10 error

  After you install vmware workstation 6.5 on windows 10 it gets error and restart. Is vmware workstation 6.5 support windows 10? FAILED TO INSTALL. vmware workstation 6.5 on windows 8, 8.1 and 10 support. ALL SUPPORT. I still don't understand...

  VMware Workstation 6.x do not support Windows 10 and will never support Windows 10.

  VMware Workstation 6.x reached "end of support" four years, October 1, 2011: Matrix.pdf product lifecycle

  We produce updates for release until its date of "end of support".  A product may not work properly with host OSes, processors or comments OSes that are not compatible with the product, especially the things that have been published after the date of "end of support".  We put a huge amount of effort to ensure that new hardware and operating systems works with each new major release of VMware Workstation, but we cannot go back and update any previous version of product to add support for all hardware and operating systems more recent.  If we tried to do this, VMware Workstation cost much more that it is today, simply because of the amount of work required to maintain!

  You need to upgrade your installation of VMware Workstation to something more recent, or downgrade your host operating system to a version compatible with VMware Workstation 6.5.

  I hope this helps!

  --

  Darius

• VMware Workstation 12 Pro Maximum number of standard error of virtual Macines

  

  I get this error when I open many clones of virtual machine to WIn 2K12R2. now, I opened a new instance of workstation for

  run a new VM clones. I don't have this problem in the Workstation 11.0.2

  There is a limitation in Windows that will sometimes hit when an instance of VMware Workstation tries to manage a lot of virtual machines simultaneously.  If the workstation user interface knock this architectural limit (which can happen to about 28 VMs), the user interface will break.

  Earlier versions of workstation had a check in place to prevent that from happening, but that the cheque has been omitted by mistake of recent versions, you to eventually open a little more VMs, but risk of accident.  12 workstation restores the audit.  In a future version of Workstation I hope will eventually be restructured to avoid the underlying limitation altogether, but we are not yet there.

  This particular limitation is not related to the total number of virtual machines that are running on the computer host, so (as the message says) you should be able to simply open a second instance of VMware Workstation and run several virtual machines in this second case.  If I remember correctly, I think that we have a strict limit of 64 virtual machines running simultaneously on Windows hosts.

  I hope this helps!

  --

  Darius

• Installation of VMWare Workstation 11.1.0 on Win 8.1 is THAT MSI will fail with the error "could not write value vmware - tray.exe for \software\microsoft\windows'currentversion\run-cles.

  Hi all

  The MSI failed with the error message as "could not write value vmware - tray.exe in \SOFTWARE\Microsoft\Windows'CurrentVersion\Run key.  Make sure you have fufficient access to that key, or contact your support staff' while trying to install vmware workstation 11.1.0 in windows 8.1.
  I tried to call the installer with run as administrator but it does not help, please suggest me overcome this error.

  Hi Vincentand welcome to the VMware communities!

  This error indicates that you have some security software (antivirus or antimalware software) that protects the part of the registry.  Can you try to temporarily disable all security software on your host computer and see if the installation can move forward?

  See you soon,.

  --

  Darius

• VMware Workstation 11 fatal error

  Whenever I try to do a virtual machine with Windows 2000 / ME or lower, Workstation refuses to start it

  I got this error message when you try to configure Windows 2000 to today:

  Fatal error VMware Workstation: (vcpu-0)

  vCPU 0: CHECK vmcore/vmm/main/cpuid.c:382 bugNr = 1036521

  A log file is available at 'C:\Users\XXX\Documents\Virtual Machines\Windows 2000 Professional\vmware.log.

  You can request support.

  To collect the data to submit to the VMware support, choose "Collect load data" in the Help menu.

  You can also run the script 'vm-support' in the folder my computer directly.

  We will respond on the basis of your entitlement to support.

  Does anyone know how to fix this? There is no solution on the internet that I can find to thisvmware

  Try to set the preferred mode (VM-> settings-> processors) "Intel VT-x/EPT or AMD-V/IVR."

• Missing network drive prevents uninstalling VMWare Workstation

  I am difficult to uninstall VMware Workstation, we reassigned to a laptop computer of a user who has left the company however somewhere along the line of the installation of VMware has become broken (2 services does not [authorization and Workstation Server], I tried the registry changes suggested here with no luck (: https://communities.vmware.com/message/2178663#2178663). To work around this I want to reinstall VMWare Workstation. When do I receive an error that Setup search a network location that is not accessible and cannot continue.

  ""Could not access network location"\\network_location\username\My Documents\Shared Virtual Machines.

  Can someone point me in the right direction for re-pointing to this location so that the installation program can complete?

  Thank you

  Roland.

  Can you not just quickly and easily temporarily recreate the missing part, do the uninstall and then remove the is no longer need for action?

  If not, look in the Windows registry or files in "C:\ProgramData\VMware\hostd".  Or uninstall manually by using the information in: cleaning after incomplete uninstall on a Windows host (1308).

• Fatal error VMware Workstation: (svga) Exception 0xc0000005 (access violation) - VMware keeps crashing and our controls engineer was not able to understand, can someone help to solve?

  
  So I'm a summer at a paper factory and my boss, the engineer of controls has not been able to understand why VMware Workstation on a certain laptop hangs. I tried to create the log file I see posted the number of threads, but what I have is a compressed file which doesn't seem to have the info I've seen... or at least not in the same format. So I'm a complete newbie to VMware, and I searched the knowledge base and could not find any direct matches, at - it ready to help a newb? Really appreciate it and it would really help me as far as my training goes. TQ ahead!

  Just in case where I did maybe right I have attached two support files that I created.

  https://www.thebuddyforum.com/demonbuddy-Forum/65752-video-drivers-constantly-crashing-VMware-9.html

  I noticed that many people have the same problem with my computer when their computer/laptop has an AMD/ATI video card. Here's all I did and I got now work stations facing up and running for a week without any apparent problem

  1 back up your Virtual Machines a safe place and uninstall the workstation

  2 uninstall the AMD/ATI drivers

  3 reinstall the drivers

  4 reinstall the workstation

  5 follow the instructions below exactly to make a registry change

  a. Open regedit.exe and backup the registry, if you don't know how just google it is incredibly easy to make and the instructions are abundant so I don't post them here.

  b. open Notepad and enter the following text, make sure it is correct that the registry change can be risky, but if you enter the text exactly as it is below, you shouldn't have any problems because I have none. I take no responsibility if you have errors after this regedit so do at your own risk. Be sure and enter all the notebook INSTRUCTIONS below. DO NOT WRITE THE INSTRUCTIONS IN NOTEPAD IN YOUR NOTEPAD FILE. Everything below.

  NOTEBOOK INSTRUCTIONS

  Windows Registry Editor Version 5.00

  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\DCI]

  "Timeout" = dword:00000014

  TdrDdiDelay "= dword:00000014".

  "TdrDelay" = dword:00000014

  "TdrLevel" = dword:000000

  [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers]

  TdrDdiDelay "= dword:00000014".

  TdrDelay "= dword:00000014".

  TdrLevel "= dword:000000".

  END NOTEBOOK INSTRUCTIONS

  c. then navigate to the file and click on Save AS, when you arrive at the location you want to save the file, click the type box and change text to all documents, and then name the file regardless of your choice and add the .reg at the end. Once you have saved the file to its location and double click it to open it, windows will ask if you want to merge with the registry click Yes, windows will be also alert you on editing the registry and if you don't know that you want to try it go ahead and do it. So far, it has worked great for me.

  For more information about editing the registry, I used click here

• Fatal error VMWare Workstation: (vmx)

  Hello

  I created a VM to Oracle Red Hat Linux Enterprise (RHEL 5) and got this error message. This virtual machine is used as a database (Oracle, RedHat) server and connected to another virtual computer that is used as a device.

  

  I'm using VMWare Workstation version 9.02 and installed in Windows 7 64 bit. In this virtual machine, I created a snapshot. The last State of the virtual machine is interrupted and all I take it back, this error is displayed. I can't change the settings and go back also to any cliché that created before.

  I tried to restart the VMWare services and also used an earlier version of VMWare Workstation version 9.01, but he always does'nt work.

  I have attached the log file. No idea how I can fix this problem?

  Thanks for any help

  You must take the State suspended - something serious has changed since suspend you the VM.
  Looking at the newspaper, I guess that you do not have the same mouse than the one that you used when the virtual machine is suspended.

  Delete these files:

  G:\RHEL 5 2.6 18-8 x86_64\Oracle RHEL 5 2.6. 18-8 x86_64 - Snapshot14.vmsn

  G:\RHEL 5 2.6 18-8-x86_64\564d16bd-1ae0-7f67-3423 - 5ff35c59b4e7.vmem

  Remove these lines from the vmx:

  checkpoint.vmState.readOnly = 'TRUE '.

  checkpoint.vmState = 'Oracle RHEL 5 2.6 18 - 8 x86_64 - Snapshot14.vmsn.

  Then try to start the virtual machine - this time, it should not crash.
  It can still display a warning on a disc that could have a repair, but this could be a bluff, and we can deal with that later.