Failed to create snapshot - now I can not start the virtual machine.

Similar Questions

• Could not start the virtual machine after you use vmkfstools to resize - HELP!

  I thought I knew what I was doing, but apparently not...

  I tried to increase the size of a VM over 36 GB drive and now I can not start the server. Here's the change front of directory list:

  -rw - 1 root root 16781312 Sep 20 19:46 PJAEast-DL01-000001 - delta.vmdk

  -rw - 1 root root 325 28 August to 01:52 PJAEast-DL01 - 000001.vmdk

  -rw - 1 root root 4096 9 February 14:55 PJAEast-DL01-000002 - delta.vmdk

  -rw - 1 root root 277 9 February 14:55 PJAEast-DL01 - 000002.vmdk

  -rw - 1 root root 28201 28 August to 01:52 PJAEast-DL01 - Snapshot1.vmsn

  -rw - 1 root root 28267 9 February 14:55 PJAEast-DL01 - Snapshot2.vmsn

  -rw - 1 root root 131604480 26 August at 08:04 PJAEast-DL01 - flat hard

  -rw - 1 root root 8684 25 August at 21:03 PJAEast - DL01.nvram

  -rw - 1 root root 589 25 August at 15:18 PJAEast - DL01.vmdk

  -rw - r - r - 1 root root 1042 28 August to 01:52 PJAEast - DL01.vmsd

  -rwxr-xr-x 1 root root 2779 Feb 9 15:10 PJAEast - DL01.vmx

  -rw - r - r - 1 root root 267 Feb 9 15:10 PJAEast - DL01.vmxf

  -rw - 1 root root 9898631168 9 February 14:54 PJAEast-DL01_1-000001 - delta.vmdk

  -rw - 1 root root 331 28 August to 01:52 PJAEast-DL01_1 - 000001.vmdk

  -rw - 1 root root 73728 9 February 14:55 PJAEast-DL01_1-000002 - delta.vmdk

  -rw - 1 root root 283 9 February 14:55 PJAEast-DL01_1 - 000002.vmdk

  -rw - 1 root root 36322836480 28 August at 01:41 PJAEast-DL01_1 - flat hard

  -rw - 1 root root 597 25 August at 15:18 PJAEast - DL01_1.vmdk

  -rw - r - r - 1 root root 78710 25 August at 16:06 vmware - 1.log

  -rw - r - r - 1 root root 68108 25 August at 20:43 2.log - vmware

  -rw - r - r - 1 root root 122302 28 August at 01:41 vmware - 3.log

  -rw - r - r - 1 root root 90557 Sep 20 19:54 4.log - vmware

  -rw - r - r - 1 root root 69453 9 February 14:54 vmware.log

  Then, I run the command:

  vmkfstools x 256g PJAEast - DL01_1.vmdk

  And now the virtual machine does not start, return an error: "the virtual disk parent has been changed since the child was created."

  The directory listing is now ("BOLD" indicates the change of information post-vmkfstools):

  -rw - 1 root root 16781312 Sep 20 19:46 PJAEast-DL01-000001 - delta.vmdk

  -rw - 1 root root 325 28 August to 01:52 PJAEast-DL01 - 000001.vmdk

  -rw - 1 root root 4096 Feb 9 16:12 PJAEast-DL01-000003 - delta.vmdk

  -rw - 1 root root 277 Feb 9 16:12 PJAEast-DL01 - 000003.vmdk

  -rw - 1 root root 28201 28 August to 01:52 PJAEast-DL01 - Snapshot1.vmsn

  -rw - 1 root root 28267 9 February 14:55 PJAEast-DL01 - Snapshot2.vmsn

  -rw - 1 root root 131604480 26 August at 08:04 PJAEast-DL01 - flat hard

  -rw - 1 root root 8684 Feb 9 16:12 PJAEast - DL01.nvram

  -rw - 1 root root 589 25 August at 15:18 PJAEast - DL01.vmdk

  -rw - r - r - 1 root root 1015 28 August 01:52 PJAEast - DL01.vmsd

  -rwx - 1 root root 2779 Feb 9 16:12 PJAEast - DL01.vmx

  -rw - 1 root root 267 Feb 9 16:12 PJAEast - DL01.vmxf

  -rw - 1 root root 9898631168 9 February 14:54 PJAEast-DL01_1-000001 - delta.vmdk

  -rw - 1 root root 331 28 August to 01:52 PJAEast-DL01_1 - 000001.vmdk

  -rw - 1 root root 73728 Feb 9 16:12 PJAEast-DL01_1-000003 - delta.vmdk

  -rw - 1 root root 283 Feb 9 16:12 PJAEast-DL01_1 - 000003.vmdk

  -rw - 1 root root 274877906944 28 August 01:41 PJAEast-DL01_1 - flat hard

  -rw - 1 root root 599 9 Feb 16:11 PJAEast - DL01_1.vmdk

  -rw - r - r - 1 root root 68108 25 August at 20:43 2.log - vmware

  -rw - r - r - 1 root root 122302 28 August at 01:41 vmware - 3.log

  -rw - r - r - 1 root root 90557 Sep 20 19:54 4.log - vmware

  -rw - r - r - 1 root root 69453 9 February 14:54 5.log - vmware

  -rw - r - r - 1 root root 39510 Feb 9 16:12 6.log - vmware

  -rw - r - r - 1 root root 39411 Feb 9 16:12 vmware - 7.log

  -rw - r - r - 1 root root 39410 Feb 9 16:14 vmware.log

  I can't do anything else until I get comments. Can anyone recommend a way to solve this problem?

  I thought I knew what I was doing, but apparently not...

  I agree

  Two a problem with the new drive.

  1. You get the error message comes from the basic disk with a different size than the disks of the snapshot.
  2. With a size of 256 GB, you will not be able to create snapshots of the disk (on ESXi prior to 5.0 with a block size of 1 MB)

  What you can try to do is to edit the file PJAEast - DL01_1.vmdk :

  • 536870912 VMFS 'PJAEast-DL01_1 - flat hard' RW--> RW 70943040 VMFS 'PJAEast-DL01_1 - flat hard. "
  • DDB. Geometry.Cylinders = "33418'-> ddb.geometry.cylinders = '4416.

  After that, I would recommend to clone the virtual disk to a new one, replace the virtual disk in the virtual machine settings and resize it to a maximum of 254GB (see "calculates the time system required by the snapshot files" at http://kb.vmware.com/kb/1012384)

  • vmkfstools-i PJAEast-DL01_1 - 000003.vmdk PJAEast - DL01_1a.vmdk

  André

• Could not start the virtual machine: "the specified file is not a virtual disk.

  Hi, I have a problem from a guest vm-workstation.

  Details below - I've done some reading here for some other "the file specified."

  is

  not a virtual disk' messages and I suspect that I am out of luck

  but I have

  wanted to ask just in case there was something miss me

  Here I tried to gather records / logs that other threads

  mentioned - I

  Welcome to all the tips on the revival of the guest, or a

  pointer to a how-to on recovering the files of a given snapshot.

  Thank you

  John

  Summary:

  VMware workstation: 7.0.1 build 227600

  host of os: Vista sp2, 64-bit

  (16 GB of ram)

  guest operating system: sles10 sp2 64-bit (4 GB ram)

  the virtual machine folder:

  drive eSATA (samsung 320, blacx attachment)

  symptom: guest vm

  does not start: says "the specified file is not a virtual disk.

  history: this particular comments works fine; I've done about 30 shots

  during the last 2 months.  The guest is not a copy - even if she did start life as a full-clone

  another linux-client with or without an operating system installed.  In any case, I've used it to very good

  effect for 2 months now.

  So last night I wanted to power off of the host, while I lived my usual steps:

  (1) stop my os of burst (# shutdown - h now)

  (2) even worksation vmware (file - & gt; exit)

  (3) stop start vista (not "suspend" but the real stop turn off the power).

  (4) visa bluescreened.  Now she is doing this every so often, so I thought that it would be

  a big deal.

  (5) this morning I tried to turn on the virtual machine and I got the 'not a virtual disk' error.

  My best guess at this point is the bluescreen stopped some write cache to be

  flushed to disk.  The funny thing is, after the previous bluescreens 3 or 4, the

  Comments to restart without a hitch.

  shrug In any case, just to be weave, I disabled write Vista for outside cache

  device (set to security policy / deletion in Device Manager).  Seems smarter to

  an external device.

  Spare part

  Attached is a file cant_start.zip (191KO) containing:

  dircontents.txt - directory of the client's file listing
  sles10_sp2. NVRAM
  sles10_sp2.vmsd
  sles10_sp2.vmx
  sles10_sp2.vmxf
  VMware.log - other requests asked for *.log files, so I thought
  VMware - 0.log - I should send him these as well.
  VMware - 1.log
  VMware - 2.log
  \ui-logs - 2 IU-logs from C:\Users\jgreve\AppData\Local\Temp\vmware-jgreve
  \vmdk_files - subdirectory of *.vmdk files, light, & can be useful
  -end-

  I checked the VMDK and newspapers - and the VMDK all look great.

  Last departure also seems to succeed?

  As it seems that instant 36 is not used so far - I was just going to throw it away and try again.

  To do this, you would change the line vmx file

  scsi0:0. FileName = 'suse11.2_x64 - cl1 - 000036.vmdk.

  TO

  scsi0:0. FileName = 'suse11.2_x64 - cl1 - 000035.vmdk.

  and then try to restart the virtual machine. If that works then remove all the

  suse11.2_x64 - cl1 - 000036-* files

  ___________________________________

  VMX-settings- Workstation FAQ -[MOA-liveCD | http://sanbarrow.com/moa241.html]- VM-infirmary

• Installation of Vista on the new hard drive was interrupted, and now I can not start the computer

  So I decided that I need a bigger hard drive. I got a 500 GB hard drive, so I have it PLOPPED in my Acer Aspire 5517 with my vista boot drive, turned on and began to go through the process. Once he got to the phase 'installation complete' it seems to take a while, so I let it run all night. Once I got up, it was on a black screen with the mouse, I let stand a few more minutes but still nothing. I turned off and started it expects to find to return at the beginning of the installation, but instead he began to start from what is on the hard drive at this time. It got to the screen with the loading bar and the sign 'Microsoft Corporation'. The loading bar was very frigidity and stopped and started randomly. I let it do this while I went to school, but when I got home, it was always the same loading screen. I rebooted and tried to start in safe mode, but when I do it it stops at crcdisk.sys, and never forwarded charges. I tried to do the reset thing factory start it but that doesn't seem to work. My other puny hard drive still works, but the other does not. I searched the internet but have not seen any other problem like it. I want to just start completely clean of my new 500 GB. Please help!

  Hi James,

  1. What is the number of brand and model of the hard disk of 500 GB?

  2. How did the 500 GB hard drive connected to the computer? It is external or internal?

  To troubleshoot the unable to start the issue to cause corrupted driver, some files that can not be loaded during the startup process must be fixed or restored. So, let's check the disk by using the Windows Recovery Console.

  (a) put the Windows Vista installation disc in the disc drive, and then start the computer.

  (b) press a key when the message "Press any key to boot from CD or DVD ".

  (c) select a language, a time, a currency and a keyboard or another input method, and then click Next.

  (d) click on repair your computer.

  (e) (click on the operating system you want to repair), and then click Next.

  (f) in the System Recovery Options dialog box, click command prompt. Type chkdsk c:/f to try to correct the errors.

  (g) Note: answer them when chkdsk asks you if you want to check the disk next boot Vista

  (h) after the recording of the disc, and then run sfc/scannow to check the corruption of system files.

  Important: when running chkdsk on the drive hard if bad sectors are found on the disk hard when chkdsk attempts to repair this area if all available on which data may be lost.

  Check out TechNet help links and check if that helps:

  The computer starts stops at crcdisk.sys

  Help! Vista won't start... (crcdisk.sys)

  Let us know the status of the issue. If you need help, please after return. We will be happy to help you.

• I can't start the virtual machine

  When I have tray start vm I have this error on newspapers:
  
  < 3 June 2012 15:54:47 BRT > < emergency > < Store > < BEA-280060 > < store persistent "_WLS_mainserver" has encountered an unrecoverable error, and he must be stopped: weblogic.store.PersistentStoreFatalException: [Store: 280105] the persistent store file '_WLS_mainserver' cannot open the file MAINSERVER000000. DAT WLS.
  weblogic.store.PersistentStoreFatalException: [Store: 280105] the persistent store file '_WLS_mainserver' cannot open the file MAINSERVER000000. DAT WLS.
  at weblogic.store.io.file.FileStoreIO.open(FileStoreIO.java:128)
  at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:435)
  at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:423)
  at weblogic.store.admin.AdminHandler.activate(AdminHandler.java:126)
  at weblogic.store.admin.FileAdminHandler.activate(FileAdminHandler.java:191)
  at weblogic.store.admin.DefaultStoreService.start(DefaultStoreService.java:60)
  at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
  at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
  at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
  Caused by: java.io.IOException: error in order for the locking file, errno = 11 Resource temporarily unavailable
  at weblogic.store.io.file.direct.DirectIONative.openConsiderLock (Native Method)
  to weblogic.store.io.file.direct.DirectFileChannel. < init > (DirectFileChannel.java:54)
  at weblogic.store.io.file.direct.DirectIOManager.open(DirectIOManager.java:179)
  at weblogic.store.io.file.StoreFile.openInternal(StoreFile.java:112)
  at weblogic.store.io.file.StoreFile.openDirect(StoreFile.java:168)
  at weblogic.store.io.file.Heap.openStoreFile(Heap.java:398)
  at weblogic.store.io.file.Heap.open(Heap.java:325)
  at weblogic.store.io.file.FileStoreIO.open(FileStoreIO.java:117)
  at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:435)
  at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:423)
  at weblogic.store.admin.AdminHandler.activate(AdminHandler.java:126)
  at weblogic.store.admin.FileAdminHandler.activate(FileAdminHandler.java:191)
  at weblogic.store.admin.DefaultStoreService.start(DefaultStoreService.java:60)
  at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
  at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
  at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
  >
  
  
  What should I do to fix this?

  Hi Alex,

  You have a file store WLSmainserver which cannot be opened because the file WLSMAINSERVER000000. DAT is not accessible.

  Access your config.xml file and look for something like.

  
  WLSmainserver
  some_directory
  some_server
  

  He comment on storing files or change the name of the directory, make sure that the directory exists.

  You should be able to reboot your server.

  See you soon,.
  Vlad

• 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é

• After Encrypting files, I had to reinstall my windows and now I can not decrypt the file

  * O.T. > encrypted files

  So after encryption of files I had to reinstall my windows (changed the name of the owner) and now I can not decrypt the file

  After attempting to decrypt the files, I'm promped with this message:

  Attribute application error

  An error occurred applying attributes to the file:

  driveletter\filename

  Access is denied. \

  I want to say that I added my administrator name in the Security tab, and then gave me full control over the files, but that did not work.

  Hello

  I understand that you cannot decrypt files previously encrypted in Windows 7 after you have reinstalled Windows.

  • What program did you use to encrypt the files?

  From now on, I would ask you to refer to similar questions discussed in the thread below links and check the status.

  Cannot decrypt previously encrypted files

  I'm unable to decrypt files encrypted after reformatting the hard drive.

  Hope this information is useful. Please feel free to answer in the case where you are facing in the future other problems with Windows.

• I've updated to Lightroom and now I can't start, the license agreement will not disappear after the acceptance of this

  I've updated to Lightroom and now I can't start, the license agreement does not disappear after she accepts any ideas?

  Hi Patricia,

  Please let us know very little about, so that we can fix it as soon as possible.

  What operating system are you using.

  You use Lightroom(5/6) as a Standalone Version or its CC.

  In addition, please try and update Adobe Application Manager on your system. See link: can not accept the product launch and end-user license agreement

  Once his finishing update, relaunch the Lightroom and see how it works.

  Let us know if it helps.

  Kind regards

  ~ Mohit

• After copying a machine a host for another vspehere vsphere virtual machine I can not load the VM machine upwards. Can't open the Flash "hard" or one of the disks disk that this depends on

  Here is the error msg I get from vsphere client.

  Cannot open the Flash '/vmfs/volumes/52120f68-3f09e8f0-affd-f01fafcf18af/w2k3SE-base-20101005/Windows w2k3.vmdk' or one of the disks disk that it depends on.

  The system cannot find the specified file

  VMware ESX can not find the virtual disk '/vmfs/volumes/52120f68-3f09e8f0-affd-f01fafcf18af/w2k3SE-base-20101005/Windows w2k3.vmdk '. Check that the path is valid and try again.

  I have ssh client due to vmware ESX.

  ls # vmfs/volumes/52120f68-3f09e8f0-conf-f01fafcf18af/apple

  564d73b4-7443-6b7f-9a70-cd355ad76d3b.vmem Windows XP Professional.vmx.0 Windows w2k3 - s004.vmdk Windows w2k3 - vmware - 16.log s009.vmdk

  Windows XP Professional - 24367b9b.hlog Windows XP Professional.vmxf Windows w2k3 - s005.vmdk Windows w2k3.vmdk vmware - 17.log

  Windows XP Professional.nvram Windows w2k3 - s001.vmdk Windows w2k3 - s006.vmdk hiding vmware - 18.log

  Windows XP Professional.vmsd Windows w2k3 - s002.vmdk Windows w2k3 - 14.log - vmware vmware - 19.log s007.vmdk

  Windows XP Professional.vmx Windows w2k3 - s003.vmdk Windows w2k3 - vmware - 15.log vmware.log s008.vmdk

  It seems that all the files are there. Except that there are some spaces.

  / vmfs/volumes/52120f68-3f09e8f0-AFFD-f01fafcf18af/Apple # cat "Windows w2k3.vmdk".

  # Disk DescriptorFile

  version = 1

  Encoding = "windows-1252".

  CID = 97c834c1

  parentCID = ffffffff

  isNativeSnapshot = 'no '.

  createType = "twoGbMaxExtentSparse.

  # Description of the measure

  RW 4192256 CLAIRSEMES "Windows w2k3 - s001.vmdk.

  RW 4192256 CLAIRSEMES "Windows w2k3 - s002.vmdk.

  RW 4192256 CLAIRSEMES "Windows w2k3 - s003.vmdk.

  RW 4192256 CLAIRSEMES "Windows w2k3 - s004.vmdk.

  RW 4192256 CLAIRSEMES "Windows w2k3 - s005.vmdk.

  RW 4192256 CLAIRSEMES "Windows w2k3 - s006.vmdk.

  RW 4192256 CLAIRSEMES "Windows w2k3 - s007.vmdk.

  RW 4192256 CLAIRSEMES "Windows w2k3 - s008.vmdk.

  RW 16384 SPARSE "Windows w2k3 - s009.vmdk.

  # The database disk

  #DDB

  ddb.virtualHWVersion = "7".

  DDB. UUID = "60 00 C2 91 86 bb a5 - 5 c bc 28 89 75 01 c9 b0 e1"

  DDB. Geometry.Cylinders = "16383.

  DDB. Geometry.Heads = "16".

  DDB. Geometry.sectors = "63".

  ddb.adapterType = 'ide '.

  ddb.toolsVersion = "8228.

  ddb.longContentID = "9d219dcc524591ac1095297d97c834c1".

  and here's a copy of the vmware.log file

  2014-08-14 T 19: 01:56.925Z | VMX | I120: DISKLIB-STRING: "/ vmfs/volumes/52120f68-3f09e8f0-conf-f01fafcf18af/apple/Windows w2k3.vmdk ': cannot open (the system cannot find the specified file).

  2014-08-14 T 19: 01:56.925Z | VMX | I120: DISKLIB-VMFS: ' / vmfs/volumes/52120f68-3f09e8f0-conf-f01fafcf18af/apple/Windows w2k3 - s001.vmdk ": closed.

  2014-08-14 T 19: 01:56.925Z | VMX | I120: DISKLIB-VMFS: ' / vmfs/volumes/52120f68-3f09e8f0-conf-f01fafcf18af/apple/Windows w2k3 - s002.vmdk ": closed.

  2014-08-14 T 19: 01:56.925Z | VMX | I120: DISKLIB-VMFS: ' / vmfs/volumes/52120f68-3f09e8f0-conf-f01fafcf18af/apple/Windows w2k3 - s003.vmdk ": closed.

  2014-08-14 T 19: 01:56.925Z | VMX | I120: DISKLIB-VMFS: ' / vmfs/volumes/52120f68-3f09e8f0-conf-f01fafcf18af/apple/Windows w2k3 - s004.vmdk ": closed.

  2014-08-14 T 19: 01:56.925Z | VMX | I120: DISKLIB-VMFS: ' / vmfs/volumes/52120f68-3f09e8f0-conf-f01fafcf18af/apple/Windows w2k3 - s005.vmdk ": closed.

  2014-08-14 T 19: 01:56.926Z | VMX | I120: DISKLIB-VMFS: ' / vmfs/volumes/52120f68-3f09e8f0-conf-f01fafcf18af/apple/Windows w2k3 - s006.vmdk ": closed.

  2014-08-14 T 19: 01:56.926Z | VMX | I120: DISKLIB-VMFS: ' / vmfs/volumes/52120f68-3f09e8f0-conf-f01fafcf18af/apple/Windows w2k3 - s007.vmdk ": closed.

  2014-08-14 T 19: 01:56.926Z | VMX | I120: DISKLIB-VMFS: ' / vmfs/volumes/52120f68-3f09e8f0-conf-f01fafcf18af/apple/Windows w2k3 - s008.vmdk ": closed.

  2014-08-14 T 19: 01:56.926Z | VMX | I120: DISKLIB-VMFS: ' / vmfs/volumes/52120f68-3f09e8f0-conf-f01fafcf18af/apple/Windows w2k3 - s009.vmdk ": closed.

  2014-08-14 T 19: 01:56.926Z | VMX | I120: DISKLIB-LIB: can't open ' / vmfs/volumes/52120f68-3f09e8f0-conf-f01fafcf18af/apple/Windows w2k3.vmdk' with flags 0xa, the system cannot find the specified file (25).

  2014-08-14 T 19: 01:56.926Z | VMX | I120: Msg_Post: error

  2014-08-14 T 19: 01:56.926Z | VMX | I120: [msg.disk.fileNotFound] VMware ESX can not find the virtual disk "/ vmfs/volumes/52120f68-3f09e8f0-conf-f01fafcf18af/apple/Windows w2k3.vmdk» Check that the path is valid and try again.

  2014-08-14 T 19: 01:56.926Z | VMX | I120: [msg.disklib.FILENOTFOUND] the system cannot find the specified file

  2014-08-14 T 19: 01:56.926Z | VMX | I120: [msg.disk.noBackEnd] cannot open disk ' / vmfs/volumes/52120f68-3f09e8f0-conf-f01fafcf18af/apple/Windows w2k3.vmdk' or one of the snapshot disks it depends on.

  2014-08-14 T 19: 01:56.926Z | VMX | I120: ----------------------------------------

  2014-08-14 T 19: 01:56.939Z | VMX | I120: DISC: discs of opening had 24 ms.

  2014-08-14 T 19: 01:56.939Z | VMX | I120: Module DiskEarly market failed.

  2014-08-14 T 19: 01:56.939Z | VMX | I120: VMX_PowerOn: ModuleTable_PowerOn = 0

  2014-08-14 T 19: 01:56.942Z | VMX | I120: WORKER: asyncOps = 1 maxActiveOps = 1 maxPending = 0 maxCompleted = 0

  2014-08-14 T 19: 01:56.950Z | VMX | I120: Vix: [12787513 mainDispatch.c:3870]: VMAutomation_ReportPowerOpFinished: VarEtat = 1, newAppState = 1873, success = 1 additionalError = 0

  2014-08-14 T 19: 01:56.951Z | VMX | I120: Vix: [12787513 mainDispatch.c:3870]: VMAutomation_ReportPowerOpFinished: VarEtat = 0, newAppState = 1870, success = 1 additionalError = 0

  2014-08-14 T 19: 01:56.951Z | VMX | I120: Past vmx/execState/val of poweredOff

  2014-08-14 T 19: 01:56.951Z | VMX | I120: Vix: [12787513 mainDispatch.c:3870]: VMAutomation_ReportPowerOpFinished: VarEtat = 0, newAppState = 1870, success = 0 additionalError = 0

  2014-08-14 T 19: 01:56.951Z | VMX | I120: Vix: [12787513 mainDispatch.c:3909]: error VIX_E_FAIL in VMAutomation_ReportPowerOpFinished(): unknown error

  2014-08-14 T 19: 01:56.951Z | VMX | I120: Vix: [12787513 mainDispatch.c:3870]: VMAutomation_ReportPowerOpFinished: VarEtat = 0, newAppState = 1870, success = 1 additionalError = 0

  2014-08-14 T 19: 01:56.951Z | VMX | I120: Past vmx/execState/val of poweredOff

  2014-08-14 T 19: 01:56.952Z | VMX | I120: VMIOP: output

  2014-08-14 T 19: 01:56.956Z | VMX | I120: Vix: [12787513 mainDispatch.c:861]: VMAutomation_LateShutdown()

  2014-08-14 T 19: 01:56.956Z | VMX | I120: Vix: [12787513 mainDispatch.c:811]: VMAutomationCloseListenerSocket. Close the socket of the receiver.

  2014-08-14 T 19: 01:56.957Z | VMX | I120: VMX VMDB Flushing connections

  2014-08-14 T 19: 01:56.957Z | VMX | "I120: VmdbDbRemoveCnx: remove Cnx Db for ' / db/connection / #1 /"

  2014-08-14 T 19: 01:56.957Z | VMX | I120: VmdbCnxDisconnect: Disconnect: pipe closed for pub cnx ' / db/connection / #1 /' (0)

  2014-08-14 T 19: 01:56.961Z | VMX | I120: Exit VMX (0).

  2014-08-14 T 19: 01:56.961Z | VMX | I120: AIOMGR-S: o stat = 1 r = 3 w = 0 I = 0 br = 49152 bw = 0

  2014-08-14 T 19: 01:56.961Z | VMX | I120: OBJLIB-LIB: ObjLib cleaning done.

  2014-08-14 T 19: 01:56.961Z | VMX | W110: VMX has left the building: 0.

  Assuming that you have enough free disk space on the host ESXI 5.1 data store, I suggest you that you load the multiextent module as shown in the link, I posted and then clone the virtual disk using the vmkfstools command line utility.

  vmkfstools 'Windows w2k3.vmdk'-i 'clone.vmdk' slim-d - an ide

  vmkfstools EI 'Windows w2k3.vmdk' 'old.vmdk '.

  vmkfstools EI "clone.vmdk" "Windows w2k3.vmdk".

  The first line of the clones of the virtual disk in a virtual drive put in service end format, and the following two lines renaming virtual disks, so that you can delete the "old*.vmdk" files once the VM works as expected.

  Alternatively, you can also run the commands on the host ESXi 4.1 and then copy the new files hard again to avoid loading the multiextent module in the new host.

  André

• can not power on virtual machine after activating the VR

  This is the error I get after activation of the replication of Vsphere and turn on/off the machine. I say feeding because allowing the VR blocks virtual machine. If I disable the replication, the machine starts correctly. The Bayt thing is that I can reproduce a 80 GB drive on this machine, but the minute I have activate the duplication of a 2 TB drive, I have this problem.

  Any idea?

  "An error was received from the ESX host turning on VM Novastor.
  Unable to start the virtual machine.
  Power DevicePowerOn module has failed.
  Unable to create the virtual SCSI device for scsi0:1, ' / vmfs/volumes/4ffda1f1-22a39f8e-bd7d-e61f13f6d8ff/Novastor/Novastor.vmdk'
  Impossible to attach the 'hbr_filter' filter to scsi0:1: limit exceeded (195887110). "

  I guess that's under the limit of 2032GB of Vsphere replication then why make this mistake when I enable replication for this disc?

  2 TB is equal to 2 048 GB that exceeds the maximum size supported 2 032 GB (= to 1,984375).

  André

• Getting error: could not open the Virtual Machine: failed to query the Source for more information

  When I have a virtual machine to export to the FVO on an ESXi 4.0 and then try again to import the FVO on VMware Player or Workstation 7.1, I get the following message:

  «Could not open the Virtual Machine: failed to query the Source for more information.» I can successfully re-import this file OVF in an ESXi server without any problems. Anyone know why this is happening and what can be done to remedy this?

  Thank you

  Christopher

  Hello.

  Try to use ovftool to convert a VMX of the FVO.

  Good luck!

• Can not see a virtual machine server connection mode

  Hello

  I'm testing VMWare View and I have a problem. I installed the ESX, vCenter and the view connection server. I have installed a virtual Windows XP machine and installed VMWare Tools + Agent and can not see this virtual machine when I want to create a "individual desktop" under "Desktop and pools. The connection to the vCenter works very well.

  Any ideas?

  Concerning

  Are the other machines available when you try to add an invidiaul machine?  I was wondering if you virtual center connectivity is working properly.

  If you have found this device or any other useful post please consider the use of buttons useful/correct to award points

• Yesterday, I downloaded the upgrade to El Capitan in a Mac Pro (early 2008) running Yosemite 10.10.5, and today I can not start the upgrade

  Yesterday, I downloaded the upgrade to El Capitan in a Mac Pro (early 2008) running Yosemite 10.10.5, and today I can not start the upgrade.

  The only option I have found is to click again on the download button, but the circle of download rest bike for a long time and ultimately that nothing happens.

  See if that helps...

  Start with CMD + r or the Option/alt key to boot from the recovery partition & use utility disk from there to repair the disk, and then repair permissions.

• I have age of empires 3 and I can not start the program.

  Hello

  I have age of empires 3 and I can not start the program.
  The program is installed, but once the autorun.exe appears (with the icons of the game, uninstall, website, out) I click on play and the game does not just start. My computing needs are fairly good for the game because I used to play the game on the same computer later.

  Thanks for your help

  David

  Bink is what plays the scenes cut in many games.

  Installation folder of AOE 3 the binkw32.dll should be in games.
  If it is then it is may be damaged and reinstall the game normally would set the
  problem.

  AutoPatcher.exe - I do not know because I never use auto-patchers with games.
  I have always to download the patch and install manually.
  However, my game has the RockallDLL.dll file.

  I don't really know a good site to lead you to these files.
  You can find a binkw32.dll in another game. Try doing a search of
  Program Files (x 86) (or another location if you install games to the default locations). If you have the file in another game you can copy into your AOE3
  folder of the master installation.

  There was a lot of discussion on these forums about AOE3 so a
  search of these forums may find another suggestion.
  You can also try the specific AOE3 forums-

  Age of Empires Forums - Forums

  Age of Empires III heaven Forum

  .

• Can not power on virtual machines "cannot access the file because it is locked.

  Virtual machines have been working well - then the storage system is down.  After the storage system returns upwards that I can't turn on a number of virtual machines.  Get this error when I try to turn it on:

  Cannot power on vmname on esxhostname.xxxxx.com. Unable to access file < unspecified file name > because it is locked
  error

  1. To check the locks on the Service Console on non ESXi servers, run the command:

     lsof | grep

     COMMAND PID USER FD TYPE SIZE NŒUD NOM_PERIPHERIQUE
     71fd60b6-3631 root 4r REG 0.9 10737418240 23533

     Note: If there is no Console of Service process the locking file, you should receive no printed output. If you receive results, however, file a support request to identify the process and to determine the causes.  If it is a third-party process, however, contact the appropriate provider to determine the cause before you kill the process ID, because it can happen again in the future.

     Stop the process and the lock ID using the kill command. In the example above, the process ID is 3631:

     kill the 3631

     After the termination of the process, you can try to turn on the virtual machine or access the file resource.

  2. To check if the virtual machine is always a world ID assigned, run these commands on all ESX/ESXi hosts:

     CD/tmp
     VM-support - x

     Available to debug worlds:
     WID =

     On the ESX/ESXi host where the virtual machine still works, kill the VM, which releases the lock on the file. To kill the virtual machine, run the command:

     VM-support - X

     Where the is the ID of the world of the virtual machine with the locked file.

     Note: this command takes 5-10 minutes to complete. Answer No to "can I include a screenshot of the virtual machine", and answer Yes to all subsequent questions.

     After the termination of the process, you can turn on the virtual machine or access the file resource.

  Deleting the file .lck (NFS only)

  The virtual machine files can be locked via NFS storage. You can identify this as reported by .lck files. # (where # is the ID of the world that holds the lock file) at the end of the file name. It is a NFS file lock and appears only when you use the ls command as it is the hidden file.
  Beware: they can be removed safely only if the virtual machine is not running.

  Note: VMFS volumes have no .lck files. The locking mechanism for VMFS volumes is managed within VMFS metadata on the volume.

  You must kill the process that is locked, if it is not the case, you probably need to restart the VMware host.
  I tell you from experience most likely end up rebooting it.