Cannot snapshot a virtual machine

Similar Questions

• [Q] cannot start a virtual machine - internal error [SOLVED]

  Hallo,

  I installed Workstation 8 and cannot start a virtual machine - or those created those previous or new. Turn the machine gives me an "internal error."

  My characteristics: Win 7 64-bit (SP1), Core i7 2600 K with 8 GB of Ram

  The newspaper of vmware:

  011 10 - 03 T 19: 22:38.013 + 02:00 | VMX | I120: Log for VMware Workstation pid = 3424 version 8.0.0 = Build = build-471780 option = output
  2011-10 - 03T 19: 22:38.013 + 02:00 | VMX | I120: The process is 64-bit.
  2011-10 - 03T 19: 22:38.013 + 02:00 | VMX | I120: Host = encoding windows-1252 = windows-1252 codepage
  2011-10 - 03T 19: 22:38.013 + 02:00 | VMX | I120: Host is Windows 7 Home Premium, 64-bit Service Pack 1 (Build 7601)
  2011-10 - 03T 19: 22:37.713 + 02:00 | VMX | I120: VTHREAD initialize main thread id 0 "vmx" host 6336
  2011-10 - 03T 19: 22:37.738 + 02:00 | VMX | I120: Settings REGIONAL windows-1252-> user NULL = System = c07 c07
  2011-10 - 03T 19: 22:37.738 + 02:00 | VMX | I120: Msg_SetLocaleEx: HostLocale = windows-1252 UserLocale = NULL
  2011-10 - 03T 19: 22:37.743 + 02:00 | VMX | I120: FILE: FileLockDynaLink: other process validation tools are: available
  2011-10 - 03T 19: 22:38.014 + 02:00 | VMX | I120: Hostname = KOENIG
  2011-10 - 03T 19: 22:38.017 + 02:00 | VMX | I120: IP = d fe80::41: e6a3:5dd2:fa9f % 11
  2011-10 - 03T 19: 22:38.017 + 02:00 | VMX | I120: IP = fe80::1cf:3682:36e8:4ccb % 17
  2011-10 - 03T 19: 22:38.017 + 02:00 | VMX | I120: IP = fe80::1 d 80: 2f6e:979 c: b57d 18%
  2011-10 - 03T 19: 22:38.017 + 02:00 | VMX | I120: IP 192.168.1.4 =
  2011-10 - 03T 19: 22:38.017 + 02:00 | VMX | I120: IP = 192.168.30.1
  2011-10 - 03T 19: 22:38.017 + 02:00 | VMX | I120: IP = 192.168.158.1
  2011-10 - 03T 19: 22:38.017 + 02:00 | VMX | I120: HOSTINFO 1074415970 @ 3331240Hz-> 0 Hz 1000000000
  2011-10 - 03T 19: 22:38.017 + 02:00 | VMX | I120: HOSTINFO ((x * 2518163806) > > 23) + 322527338056
  2011-10 - 03T 19: 22:38.037 + 02:00 | VMX | I120: System uptime 321912074 us
  2011-10 - 03T 19: 22:38.037 + 02:00 | VMX | I120: command line: "C:\Program Files (x 86) \VMware\VMware" "-s" 'vmx.stdio.keep = TRUE' "-#" "product = 1; name = VMware Workstation; version 8.0.0 =; BuildNumber = 471780; licensename = VMware Workstation; licenseversion = + 8.0; ""-@ ""pipe=\\.\pipe\vmxf3ce37cf9b6f9c3e;" "D:\VM\Windows 7 x64\Windows 7 x64.vmx".
  2011-10 - 03T 19: 22:38.037 + 02:00 | VMX | I120: Msg_SetLocaleEx: HostLocale = windows-1252 UserLocale = NULL
  2011-10 - 03T 19: 22:38.056 + 02:00 | VMX | "I120: UI connection on pipes '\\.\pipe\vmxf3ce37cf9b6f9c3e' user (null)".
  2011-10 - 03T 19: 22:38.057 + 02:00 | VMX | I120: VMXVmdb: local connection timeout: 60000 ms.
  2011-10 - 03T 19: 22:38.104 + 02:00 | VMX | I120: VmdbAddConnection: cnxPath = / db/connection / #1 /, cnxIx = 1
  2011-10 - 03T 19: 22:38.105 + 02:00 | VMX | I120: Vix: [6336 mainDispatch.c:483]: VMAutomation: initialize VMAutomation.
  2011-10 - 03T 19: 22:38.105 + 02:00 | VMX | I120: Vix: [6336 mainDispatch.c:780]: VMAutomationOpenListenerSocket() to listen
  2011-10 - 03T 19: 22:38.122 + 02:00 | VMX | I120: Vix: [6336 mainDispatch.c:4067]: VMAutomation_ReportPowerOpFinished: VarEtat = 0, newAppState = 1870, success = 1 additionalError = 0
  2011-10 - 03T 19: 22:38.122 + 02:00 | VMX | I120: Past vmx/execState/val of poweredOff
  2011-10 - 03T 19: 22:38.122 + 02:00 | VMX | I120: Vix: [6336 mainDispatch.c:4067]: VMAutomation_ReportPowerOpFinished: VarEtat = 1, newAppState = 1873, success = 1 additionalError = 0
  2011-10 - 03T 19: 22:38.122 + 02:00 | VMX | I120: Vix: [6336 mainDispatch.c:4067]: VMAutomation_ReportPowerOpFinished: VarEtat = 2, newAppState = 1877, success = 1 additionalError = 0
  2011-10 - 03T 19: 22:38.122 + 02:00 | VMX | I120: Vix: [6336 mainDispatch.c:4067]: VMAutomation_ReportPowerOpFinished: VarEtat = 3, newAppState = 1881, success = 1 additionalError = 0
  2011-10 - 03T 19: 22:38.122 + 02:00 | VMX | I120: VMMon_GetkHzEstimate: calculated 3411189 kHz
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: VMMon_RememberkHzEstimate: calculated 3411189 kHz
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: TSC kHz estimates: Memoirs of vmmon 3411189, 3411189, osReported 3401000. With the help of 3411189 kHz.
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: CPU 0 # TSC = 1100186590922
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: CPU # 1 TSC = 1100186590888
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: # 2 CPU TSC = 1100186590603
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: CPU # 3 TSC = 1100186590637
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: CPU # 4 TSC = 1100186590948
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: CPU # TSC 5 = 1100186590906
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: CPU # 6 TSC = 1100186590898
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: CPU # 7 TSC = 1100186590836
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: TSC of measured first delta 345
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: TSC 387 min Delta
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: PTSC: RefClockToPTSC 0 3331240 Hz-> 0 to 3411189000 Hz
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: PTSC: RefClockToPTSC ((x * 4294966339) > > 22) +-1100565306901
  2011-10 - 03T 19: 22:38.124 + 02:00 | VMX | I120: PTSC: tscOffset-1100187618517
  2011-10 - 03T 19: 22:38.124 + 02:00 | VMX | I120: PTSC: using TSC
  2011-10 - 03T 19: 22:38.124 + 02:00 | VMX | I120: PTSC: material TSCs are synchronized.
  2011-10 - 03T 19: 22:38.124 + 02:00 | VMX | I120: PTSC: PTSC current = 289960
  2011-10 - 03T 19: 22:38.124 + 02:00 | VMX | I120: Module CPUID initialization failed.
  2011-10 - 03T 19: 22:38.124 + 02:00 | VMX | I120: Vix: [6336 mainDispatch.c:869]: VMAutomation_LateShutdown()
  2011-10 - 03T 19: 22:38.124 + 02:00 | VMX | I120: Vix: [6336 mainDispatch.c:819]: VMAutomationCloseListenerSocket. Close the socket of the receiver.
  2011-10 - 03T 19: 22:38.125 + 02:00 | VMX | I120: VMX VMDB Flushing connections
  2011-10 - 03T 19: 22:38.125 + 02:00 | VMX | "I120: VmdbDbRemoveCnx: remove Cnx Db for ' / db/connection / #1 /"
  2011-10 - 03T 19: 22:38.125 + 02:00 | VMX | I120: VmdbCnxDisconnect: Disconnect: pipe closed for pub cnx ' / db/connection / #1 /' (0)
  2011-10 - 03T 19: 22:38.129 + 02:00 | VMX | W110: Failed to initialize the virtual machine.

  I scored an error... I tried to reinstall, clean... nothing helps.

  Curiously, I can use the Player app to run all VM´s without problem...

  All solutions?

  Thanks in advance

  Marcus4Aspern

  Is - the name change "vmware.exe" with something else?

• Cannot convert a virtual machine while it is powere on or suspended. Shut down and power off the virtual machine before the conversion.

  Hi all

  I am currently using preinstalled VMware 7.1 and I try to import a virtual machine, I used to work on my windows XP. Recently, I am using windows VISTA and I am trying to import my VM (.vmx) and I get this error "cannot convert a virtual machine, although it is powere on or suspended. "Shut down and power off the virtual machine before the conversion.

  This virtual machine worked very well under windows XP and VMware 6.5, but now I am not able to import it. Please suggest how I can make this virtual machine running in my VISTA and vmware 7.1.

  I am also attaching the converter file logs and .vmx vmware.

  Thank you...

  Is there a problem with this backup?

  It is possible. How big is she?

  Right-click on the vmdk file in Solution Explorer, then select «Map virtual disk...» "Does it work?

  André

• Snapshots for virtual machines fault-tolerant

  VSphere availability guide says that you can not fault tolerant VMs snapshot. Otherwise, how would a backup virtual machines?

  If you need to snap for backup, you can stop FT, do the blink of an eye, make the backup, delete the snap and reactivate FT.

  You cannot schedule directly (in the special section), but there are useful scripts that can toggle pi of CLI.

  André

• Cannot create a virtual machine with a vmdk file copied from another location, please find the attached error

  Hi all

  I copied a file from one place vmdk and try to make a new virtual machine with this vmdk file. But when I turn on after the creation of vm error is coming. Error in the text and the image below

  Power on the virtual machine: cannot open scsi0:0 disc: disc not supported or not valid type 7. Ensure that the disk has been imported.

  See the error of the stack for more details on the cause of this problem.

  Time: 31/03/2015-14:40:05

  Target: DBServer

  vCenter Server: vcsa

  Error stack

  An error was received from the ESX host turning on DBServer VM.

  Unable to start the virtual machine.

  Power DevicePowerOn module has failed.

  Unable to create the virtual SCSI device for scsi0:0, ' / vmfs/volumes/543d140b-feb33d52-7640-90b11c9796c3/vmdk/kapuatdb.vmdk'

  Could not open scsi0:0 disc: disc not supported or not valid type 7. Ensure that the disk has been imported.

  This error message generally if the hard files have been copied hosted as VMware Workstation product, which uses a format of sparse file that is not supported on an ESXi host. Instead of the hard copy, you can use VMware Converter, or - if you prefer - you can convert the hard using vmware-vdiskmanager (before transfer) or vmkfstools (after downloading). I deal to use vmkfstools you will need to load the mutliextent module (see for example "Clone or migration operations involving virtual discs non-VMFS on ESXi fail with an error" vSphere 5.1 Release Notes)

  André

• Cannot start the virtual machine after you create snapshop

  I found a strange behaviour. I have a Windows 2008 guest that I just copied in my new box ESXi. I am trying to create a snapshot before upgrading the guest to 2012 Windows operating system. The virtual machine has currently no snapshots. Whenever I have create a snapshot, he succeeds, but then I can't start the virtual machine saying that it does not find the vmdk file delta even though I see there in the data store. In order to start the virtual machine, I have to delete the inventory and it readd, but then I lose the snapshot. I also have another computer virtual running Windows 8.1 that does exactly the same thing. How can I create snapshots safely without damaging the virtual machine? I also tried to create the snapshot while the virtual machine has been activated but that makes crashing and then it does not start again, so I have to repeat the process to remove the inventory and it time. Frustrating. See the screenshots, I have attached.

  Once these virtual machines have been in Hyper-V in the past and I just convert to VMware format using the StarWind V2V converter.

  Yes, for an ESXi host and target you must either select the ESX f.vmdk as format target (growable option is for VMware Workstation), or you must convert the virtual machine once more instead of simply upload the files to an ESXi host.

  André

• Cannot RDP into virtual machine after the reboot

  Hi all

  I use VMware ESXi4.0

  I'm having a problem where if I reboot a virtual machine, once it restarts I try to use the Remote Desktop Connection Manager to access and receive this error:

  "The connection cannot be completed because the remote computer that has been reached is not the one that you specified.  This could be caused by an outdated entry in the DNS cache.  Try using the IP address of the computer instead of the name. »

  The current machine I noticed the error is Windows 7 but also for me Server 2008.  not sure if this relevant.  I can still access the machine through vSphere, but not Remote Desktop.  When I ping the name of the machine as well as IP address, they both similar deadlines.

  I checked my DC for dns entries, and they are there for this computer as well as in the reverse lookup zones.  I tried to do a/flushdns and / registerdns on the virtual machine.

  I would usually have for this problem to connect to vSphere virtual machine, then RDCM is there to connect.

  I saw another post on this topic in the forum, but he had a solution. This post is here > http://communities.vmware.com/message/1304004

  I tried the recommendations here and they did not help.

  Any ideas on what I can try?

  Thanks in advance,

  John

  Here's the update to which I was referring... He had to be reissued in June because of the problems that it caused on some systems.

  http://support.Microsoft.com/kb/2667402

  But, if you are able to connect via IP, then the RDP patch will probably not help.

• The list of the snapshot active virtual machines

  In our environment, we will automation upgrade to new versions of the tests. I need regularly to ensure that virtual machines are running with a snapshot taken at the same time (via PowerCLI, we use the same description).

  In other words, is there a way to retrieve the current name of the active snapshot for all virtual machines?

  With the help of:

  Get-resourcepool 'MyResPool ' | Get - vm | Get-snapshot | Select @{Name = 'The virtual computer name';  Expression = {$_.} UMM name}}, created, name, description. Tri-objet created. Format-Table-auto

  Don't highlight that one is active.

  A snapshot IsCurrent property tells you if a snapshot is updated. I modified your script to display only active snapshots:

  Get-ResourcePool "MyResPool" | `
  Get-VM | `
  Get-Snapshot | `
  Where-Object {$_.IsCurrent} | `
  Select @{Name="VM Name";Expression={$_.VM.Name}},Created,Name,Description | `
  Sort-Object -Property Created | `
  Format-Table -AutoSize
  

  Best regards, Robert

• VMware 6.5.5 cannot import the virtual machine that uses 2GB "disks of split.

  Hello

  I'm using VMware Workstation 6.5.5 under Win XP. I tried to import a virtual machine that was created by using the option 'Split' virtual disks into files of 2 GB. The import fails and presents a pop-up: ' Conversion Assistant/cannot determine the guest operating system. The log file includes the line "could not find the disk cofortcol3v01 - cl1.vmdk. This file does not exist of course, there are more files cofortcol3v01-cl1 - s001.vmdk, cofortcol3v01-cl1 - s002.vmdk and so on. The machine virtual original (cofortcol3v01) has been created under VMware Workstation 5.1, and it does not under Workstation 6.5.5.

  Is this a known problem in the conversion utility? Is there a work around for this problem?

  Thank you.

  -Phil Anzel

  FYI... VMware Workstation peut import a Virtual Machine that uses twoGbMaxExtentSparse discs.

  The log file includes the line "could not find the disk cofortcol3v01 - cl1.vmdk. This file does not exist of course, rather there are files cofortcol3v01-cl1 - s001.vmdk, cofortcol3v01-cl1 - s002.vmdk and so on. The machine virtual original (cofortcol3v01) has been created under VMware Workstation 5.1, and it does not under Workstation 6.5.5.

  Is this a known problem in the conversion utility? Is there a work around for this problem?

  The problem is that you're missing the "disk DescriptorFile", "cofortcol3v01 - cl1.vmdk" and which is why it's a failure and not a limitation of the Conversion utility.

  Also if you actually had a Virtual Machine created in VMware Workstation 5.1 you can simply run directly under VMware Workstation 6.5.5 without having to run the import command.

  Anyway, if you have a backup that you can recover the file "cofortcol3v01 - cl1.vmdk" then you should be fine and if you have not then a new can be created.  If you can archive (compress) files vmware*.log (usually 4 of them) in a single zip file archive and tied him to a post in response, then one of us will create a new file "cofortcol3v01 - cl1.vmdk", based on the information contained in files vmware.log for you, if you don't know how to do it yourself.

• Cannot start multiple virtual machines.  Maybe I corrupted the model

  We had problems with disk space, and I was looking around to see if he had left garbage data store.  I am very new to VM, but even though I'm new I'm responsible for helping maintain.  So I learn a lesson the hard way.

  I found a number of virtual machines in organized which did not seem to relate to existing models.  For example, we have a model name 000729-Server2008 Server 2008, that they are in lm401\729.  But it appers to be a clone of 729 to lm401\16.  I'm going to guess that 16 was the original version and changes or clones have been made for him and we are now sitting to 729.

  Then I moved 16 in another data store, but it failed because there is a lock on the hard master.  So I moved everything back.  Now, when we try to start up of VMs driven from this model we get "file & lt; filename not specified & gt; not found"I went back and tried to deploy and supply on the model but I get

  Impossible to deploy virtual machines in the pool of resources 'resgroup-131.

  • Not to feed one or more virtual machines.

  • Error when powering on a virtual machine '2008 X 86'.

  • Cannot power on the operation on a virtual machine
    carried out because one of the files is locked. Consolidation of the
    virtual machine can solve this problem.

  • The operation cannot be performed because a file is locked.

  So I cancelled and tried to consolidate while I get

  Host '172.31.7.111' reported an error. A disk error has occurred: the parent of this virtual disk could not be opened. Host '172.31.7.111' reported an error. A disk error has occurred: the parent of this virtual disk could not be opened.

  Can someone help me?

  This article may help: http://www.vmware.com/kb/1007969

  If you have found this helpful at all prices please points using the correct or useful!  Thank you!

• VCB backup snapshot or virtual machine?

  Hello

  Workflow of VCB, I read these procedures frequently and I'm confused by what backup software is stored:

  ".....  Put the virtual machine snapshot mode and take a snapshot.

  .. .Mount snapshot of the VM for the proxy backup (to win)

  .. software backup .the performs a regular backup of the snapshot of the virtual machine moving data from backup media... »

  So I wonder what backup software is saved: any virtual machine or virtual machine snapshot? and why?

  And for linux, it will export (copy) the snapshot of the machine the VCB proxy virtual of the SAN. If a single snapshot is stored to the proxy of VCB mount point, why VCB proxy must have enough space to contain the largest virtual machine?

  Can someone give me some clarification?

  LAN

  To clearify:

  In the world of VMware ESX, a snapshot is the same as the 'entire virtual machine' as you say. It's just the disks 'frozen' in a State of know. VCB can then move up and back up this disk (or copy it to the VCB proxy) while the virtual machine is placing the changed data in the temporary file. Some people refer to this temporary file that the file 'snapshot', while the other, see you in the frozen file as the 'snapshot' file, and creates confusion for users/students. A 'snapshot' is simply the functionality described above.

  When the backup action is finalized, VCB tells vCenter to "remove the snapshot" which actually means that the data in the temporary file are merged with the 'frozen' disk that is then back 'defrosted' and put into live operation.

  / R

• Question about snapshots and virtual machines

  Hi all

  I have a small question about snapshots. I use VMware for about 6 months and I read about snapshots and how they work but still have a question to make sure that I understand how it works and it will work the way I think it works.

  I have a Windows 2003 server, which is a virtual machine. I have an application that uses MSDE database. I want to upgrade the database to MS SQL 2005, but to do this I need to back up the MSDE database, uninstall MSDE, and then install SQL 2005 and move the SQL database. This happens on the same VM.

  What I was thinking if I well Snapshots correctly is to snap turned the virtual machine before doing anything. Then do my upgrade steps and see if everything works. If its all messed up so I should be able to return to my shot and everything should be the way he had. What is the good? One of the main reasons I moved the server VM was because of this upgrade.

  After reading the documentation for the snapshots, it's how I undestood it. Pretty much any change could be reversed with snapshots. I wish just they had put in a few examples in the PDF file. Also it would be the same for all type of grades of the OS? Could I snapshot a Windows 2000 Server, and then "in the upgrade of the square" to Windows 2003? I've cloned a VM to do this but was curious about whether snapshots would be just as easy.

  Thanks for your help.

  Hello.

  What I was thinking if I well Snapshots correctly is to snap turned the virtual machine before doing anything. Then do my upgrade steps and see if everything works. If its all messed up so I should be able to return to my shot and everything should be the way he had. What is the good?

  That is right.

  After reading the documentation for the snapshots, it's how I undestood it. Pretty much any change could be reversed with snapshots. I wish just they had put in a few examples in the PDF file. Also it would be the same for all type of grades of the OS? Could I snapshot a Windows 2000 Server, and then "in the upgrade of the square" to Windows 2003? I've cloned a VM to do this but was curious about whether snapshots would be just as easy.

  Exactly the same thing for the upgrades of the OS.

  Perhaps the most important thing with the snapshots is to keep an eye on them and don't let them sit too long or become too big.  You have described the use cases are very good uses for snapshots.  Just make sure you have a solid plan with a schedule set, so that you can come back or validate changes before the snapshot becomes too large.

  Good luck!

• Cannot ping the Virtual Machine by host

  Hi all,

  Please help, I use VMWare Workstation 6.5 and I have a physical operating system which is Windows XP SP2, I have a network card, but not connected to a physical switch, the IP address is 192.168.0.1. I installed a Virtual Machine using Microsoft Windows 2003 server as the operating system, promote as domain controller, install the DHCP, DNS service and assign an IP 192.168.0.2, no default gateway.

  My VMnet1 on physical operating system has an IP 192.168.204.1 and VMNet8 has an IP 192.168.126.1.

  The host, I cannot ping the 192.168.0.2 which is the IP address of the Virtual Machine. Even in the Virtual Machine, I can not ping 192.168.0.1 is the IP address of the host. From what I read, the physical and the virtual machine were connected with a virtual switch. Am I wrong?

  Any advice?

  Thanks in advance.

  They SEEM to be in different networks, you need search routing between them,... since they differnet networks...

  on the other

  they do host and the virtual machine on the same subnet / network for EXAMPLE: class C class network 192.168.200.0/24

  granting of points if my answer was helpful... Thank you > > > > > > > >

  concerning

  Joe

• Cannot open 2 Virtual Machines at the same time to access the same database

  People,
  
  Hello.
  I'm installing RAC Oracle Database 11 g 2 system with 2 Virtual Machines (rac1 and rac2) on top 3 VMPlayer.
  
  The VM rac1 and rac2 when one of them is stopped.
  Their locations are F:\VM_RAC\rac1 and F:\VM_RAC\rac2.
  
  
  I opened rac1 rac2 is running. But this error message appears:
  
  Error: "cannot open F:\VM_RAC\sharerac\asm1.vmdk drive or one instant records, that depends. Reason: cannot lock the file. »
  
  
  While rac1 running, I opened rac2. But this error message appears:
  
  Error: "cannot open F:\VM_RAC\sharerac\asm1.vmdk drive or one instant records, that depends. Reason: cannot lock the file. »
  
  
  2 error messages are the same. This means that I can not open 2and rac1 rac2 VMs at the same time. When we run RAC system, must open 2 "machines" or machines to more than 2 at the same time, so that all machines can access the same database server.
  
  My question is:
  
  Can all folk tell me how have rac1 and rac2 run at the same time?
  
  Thank you.

  Unfortunately no, Oracle RAC requires that all nodes can visit the same set of shared disks. If your database resides within the DSO, each instance ASM (one per node) must also see the same set of disks to ASM diskgroup containing the data of the database files.

  Best regards
  Bryan Wood

• Cannot access Windows Virtual Machine in OSX! Help, please!

  Attached is a screenshot of the error I get when I try to open my virtual machine and a screenshot of the error if I try to remove the snapshot through "settings".  I restored an older VM with Time Machine, now I get this error when you try to run the virtual machine.  I tried to uninstall, delete the virtual machine, shut down the computer, reinstall VMware Fusion (which already had my serial number filled in for me) and then back to the VM backed up by Time Machine.  No luck.  Now, instead of a few files missing I want to recover... I can't access my VM at all.  Not good, any help would be appreciated.

  No doubt useful to add that I had the idea to uninstall from another thread of subject "fangs" tiled "Lost access to the merger after restoring from Time Machine" maybe it would work if I reinstalled and my serial number has not been filled

  in?  Anyone know any more and more stuff inbetween closing

  Uninstall and install?

  Well, that was good of you talk and after getting your data from the files just mounting hard copy create a new Virtual Machine from the hard base file and go from there.  Once you are satisfied, you have all of your data, you can get rid of the copy that you made on the external hard drive.  If you have any other questions just post and one of us will try to answer.

  Have a good.

  Woody