Disks of the virtual machine consolidation is necessary is Unable to Access file < file_name indeterminate > because it is locked

Similar Questions

• Disks of the virtual machine consolidation is necessary - vCenter 5.1 U1 + ESXi 5.1 + VDP 5.8.0

  Hello

  I am facing problem as many other people do, when snapshot is deleted, the delta files are still there and warning message "consolidation of disks of virtual machines is necessary" is shown on the virtual machine.

  It happened only few but try to find the root cause. He arrived only on virtual machine located on ESXi 5.1 build 799733 which is located in the task of the WTP 5.8.0 backup.

  Is this snapshot problem, a bug in the version of ESXi?

  Unable to find the release notes, where this is documented as bug.

  Thank you

  Finally, I found a reason, therefore, for other users... ESXi 5.1 build 799733 has a bug that is resolved in the update 1 and higher and is connected to the suspended snapshots created by POS, that is why are there so many discs of delta.

  ESXi 5.1 Update 1 Release Notes

  • When the slowdown of snapshot fails the redo logs are not consolidated
    • When you try to take a snapshot of the suspension of a virtual machine, if the snapshot operation fails near the end of its realization, recovery logs created as part of the snapshot are not consolidated. Recovery logs can consume a lot of space to store data.
    • This issue is fixed in this version. If the snapshot suspended operation fails, the redo log files are consolidated.

• Copy of the data of the disk of the virtual machine on a Local disk is too slow

  We have recently implemented vMware view.   We vSphere 5.5 and 5.2 and made Desktop visualization server.

  We have SAN as HP 3Par and Esxi hosts are HP ProLiant DL380p Gen8

  Now all trying to copy the data from the disk of the virtual machine disk of the local computer are too slow. But if we are writing data from Local disk on the disk of the virtual machine is normal. And copying data between the two virtual machine disk is also fast.

  Thanks in advance for your help

  Dear all,

  Thanks for your help.

  We have analyzed the issue in 360 degrees, and we also examined your entries. Finally, we found the problem. It was that a defective fiber link has been creating the problem.

  We have recently implemented vMware and this flaw in fiber can also happened during this period. That's why we thought it may be because of vmware.

  Thanks again for your help

• Connect physical hard disks to the virtual machine (and leave the data intact)

  Hello

  I'm looking to virtualize a SOHO headless server, that I use mainly for secure file storage.

  Currently, the system runs Linux installed on a small disc and has two drives 1.5 TB, used exclusively for data, in a cluster of ZFS mirroring. (I use the ZFS-fuse Linux-based application).

  I want virtualization for two reasons. One is to make administration easier and safer - avoid having to connect a keyboard and the physical monitor to the box from time to time. The other is that the machine is a bit more powerful to handle the load, and I'm hoping to make it work on other, more challenging tasks.

  Now, there is a catch. These discs are as highly important. I mean the data on them. What I need is to convert the current Linux system to a virtual machine, or re - install Linux on a virtual machine (don't like that), then connect the physical disks to the virtual machine as if they were actually connected.

  I certainly don't want to vmware touches those disks somehow.

  I've read the documentation, but I'm a noob when it comes to server virtualization and system engineering and don't quite understand if this is possible or not. These discs are not a SAN, they are physically connected to the server, I want to install vSphere on. (Of course, I'll log out when I run the setup of vSphere. But I need plug them again later, and they need to be sure that vmware will leave them alone and pass them to the virtual machine transparent.)

  Sigmoid wrote:

  Oh yes, the cluster mirrored ZFS. It is essentially a software RAID type thingie.

  http://en.Wikipedia.org/wiki/ZFS

  A material, or the point of view of virtualization, it appears two hard drives with a single huge partition on each that is not transparent to anyone, except the implementation of ZFS.

  OK, means that you can break the RAID, connect the drives to different host and configure RAID once again, right?

  Let's do it this way

  1. We will need a disc player more for VM, cause on flash, we install ESXi
  2. I will share ZFS :-), all you need to do with that before you install ESXi
  3. make the BACKUP!
  4. Disconnect the data host drives
  5. install ESXi 4.1 U1 free version on flash
  6. Download the site VMware vSphere client
  7. Connect the VM disk to ESXi
  8. customer help create the virtual machine and install the OS on it
  9. stop the virtual machine and esxi
  10. connect DATA drives to the ESXi host
  11. begin to ESXi
  12. See how to add RDM on youtube, after client use, change first hardware VM--> add a new hard disk--> choose Raw Device Mapping--> (physical or virtual) mode--> store it with folder VM - FACT
  13. Start the virtual machine, now your VM should see both drives, with good data course :-)

  I have just made this procedure (add ROW with data in Linux VM) on ubuntu VM, works well

  See you soon
  Artur
  

  Please, do not forget the points of call of the "useful" or "correct" answers

• Virtual machine consolidation is necessary.

  Hi guys,.

  I have a problem with esxi no space for vm, it can't start, also cannot consolidate due to no space. Could you please advice what can delete the folder of the virtual computer?

  Thank you.

  I got scared to see a thin virtual disk configured with multiple snapshots. Show file sizes, you may need to up to ~ 37GB (size of 75 GB configured minus 38 GB currently used by file flat th) additional disk space on the data store to consolidate snapshots.

  Unless you have an another data store with enough free disk space to migrate/clone to the virtual machine, your options are limited. What can work, is that you register the virtual machine as an OVF (on the ESXi host file menu) on your PC (assuming that there are enough free space on the disk), then delete the VM on the ESXi host and finally re-import the file of Fiction. Another option to use VMware Converter or a backup application.

  André

• vRO presentation: return the total size of the disk of the virtual machine

  Hi guys,.

  I have a catalog item to extend a drive, which is presented to the vRA advanced services and picks up the vRO workflow. For this reason, the default IaaS vRA no between not affecting resource management. So I would limit the end-users to a maximum size of the virtual machine - that is to say, if the size + total size they intended to expand is > to a specific size, then the workflow will report this.

  I wrote the following code to return the total of all the disks that are attached to a machine. Then, it comes to the tab Presentation vRO to fill the discs max value. It works fine when I use the code as a workflow and connect the output. However, vRO presentation does not return a value any. Anyone had similar problems or I made a stupid mistake and missed something?

  var total = 0;

  size var = new Array();

  var features = vm.config.hardware.device;

  var h = 0;

  for (var i in devices) {}

  If (devices [i] instanceof VcVirtualDisk) {}

  size [h +] = [i] devices, .capacityInKB / 1024 / 1024;

  Total += devices [i] .capacityInKB / 1024 / 1024;

  }

  }

  return to the total;

  
  

  
  

  
  

  Thank you

  bradger33

  resolved - used the wrong presentation vRO variable. Had to use rather than answer pre-defined data binding

• delete a virtual disk of the virtual machine of broken storage

  I have a virtual disk to a virtual machine on a broken iSCSI storage,

  now I can not remove the disc from the virtual machine.

  ESX 4.1 does not see the now broken iSCSI storage.

  See attach.

  Remove the virtual machine from the inventory and edit VMX manually deleting the reference to this disk. After that, add the machine virtual back again for the inventory.

• Having to constantly consolidate the disk of the virtual machine?

  I'm having a problem whereby several virtual machines on several 5.1 ESXi hosts are requiring a consolidation of virtual machine disk. I perform "snapshot consolidation" and it ends after a few seconds, then next day the configuration problem returns?

  There are no snapshots on the affected virtual machines

  OS: 2008R2 and 2012

  ESXi 5.1 stand alone hosts

  Thank you

  Brendan

  Thanks guys, it was in fact the backup software (CommVault) do not clean a vsa backup attempt failed. Everything is good now...

• Newbie - how to add another hard disk to the virtual machine

  We have just started to try ESXI on a new database server.

  The previous server got an SSD, it is necessary that our needs. Now, we got the new Intel Server, was paid $ 3000. There are 2 hard drives and SSD, all on the integrated chipset. We can't find anywere in the interface of PC ESXI or VMWare Go web site to add the SSD to the list of storage. We imported to test an installation of Windows Server 2008 and it works, but only C:, no other hard drive found!

  Help, please!

  pay? -None
  If you connect to http://ip-of-your-esxi , you should see a hint where to download it if I remember correctly

• Impossible to expand the D: drive on the virtual machine

  I tried to increase disk vmdk file to another 20Gb.When D: I went to change the setting, the option to increase the size of the disk is grayed out.

  My ESX Server that is having the VM is not added to the virtual Center Server.

  In Edit framework I have seen

  Vitual machine version: 4

  type of thick disk configuration

  size of 25GB available

  Maximum S/o

  Please let me know if there is an option to increase the size of vmdk file.

  have you created a snapshot of the virtual machine? If there is a snapshot, you are not able to extend the disks of the virtual machine.

  Are you unable to extend all or only the road d disks? I have had this a few times and the only way to extend the drive was by turn off the virtual machine. Never understood why it was.

  With sincere friendships.

  Ruud

• Physical disk how can I add in the Virtual Machine?

  I am trying to set up a network of storage, but I discovered it is there is a limitation for the addition of physical hard disks in the virtual machine.

  I have 1 virtual hard disk for the operating system (SCSI), an invited so I try to add more than 4 disks, but it should not add more than 3. They showed that (IIRC).

  I try to add 4 x 1 TB as physical hard disk in virtual machine hard disks, but it says that I must remove one to add.

  1. in the settings of the Virtual Machine, is there a difference between (SCSI) (IDE) and why are the physical disks (IDE)?

  2. What is the limitation of total hard drives under the VM settings, four?

  Johwwy

  physical disks can be detected such as IDE or SCSI - depends on the drivers used by the host

  SATA in ide-compat mode is used as IDE

  SATA AHCI mode is detected as SCSI

  It is possible to rewrite the descriptions after their creation.

  It is a little advanced - see my notes

  http://sanbarrow.com/VMDK-basics.html#changeadapter

  for a start, it may be necessary to also change the geometry... ask first so uncertain.

  I think the limit of physical disks that can be attached to a virtual machine is 64 = 4 x 15 - scsi and IDE 4-disc drives

  _________________________

  VMX-settings- WS FAQ -[MOAcd | http://sanbarrow.com/moa241.html]- VMDK-manual

• Move ROW with dynamic disk to another virtual machine

  Hello

  I'm in a situation where I have to leave my RDM Win2003 VM to win2008, but the complexity and multiple physical RDMs here make only dynamic partition (RDM1 1.5 TB, RDM2 1.5 TB, is drive G RDM3 1 TB 4 TB),

  Now my question is if I can move this partition of G (which includes 3 disks RDM) again an another VM (win2008)

  Thanks, SD

  Hello

  This does not resemble a specific question VMware.  On the contrary, seems like a question of Microsoft Windows.  Just make sure the hosts on which the virtual machine of 2008 runs can see the same ROW and follow this procedure to remove dynamic disks of the virtual machine of 2003 and add them to the virtual machine of 2008.

  Move disks to another computer

  All the best,

  Mike

  -----------------------------------------

  Remember to mark this reply 'proper' or 'useful', if you found it useful.

  Mike Brown

  NetApp, VMware and Cisco data center guy

  Consultant engineer

  [email protected]

  Twitter: @VirtuallyMikeB

  Blog: http://VirtuallyMikeBrown.com

  LinkedIn: http://LinkedIn.com/in/michaelbbrown

• How to move the virtual machine from one host to another?

  The two boxes under ESXi 5.0 (hypervisors freely licensed).

  I have a virtual machine (FreeBSD) that I need to go to another box.

  Network ports are not the same, but I guess that's not a biggie to reconfigure the network cards. Other than that, I have to follow a few best practices/SOPS or copy & paste is everything I need to run perfectly on a different host?

  Thank you very much!

  FastSCP allows you to copy directly between hosts, so it can save a lot of time you copy.  I don't know what you mean by 'manually' copy files.  Do you mean using the vShpere client and download the files to a location then download them to the new host?  Either way works perfectly, but FastSCP you must save a step.

  If you have currently snapshots, you can consolidate first or leave em and just copy them with the rest of the virtual machine. There should be no need to do something with snapshots, if you perform a migration 'offline '.  As long as you take all the files, snapshots will be displayed on the destination host computer when you save the vm on the host.

  I did 'on-line' migration of large virtual machines first to the take a snapshot on the source host, copy basic to the first destination host disks while the virtual machine was still running on the source host.  When I was ready to migrate the CPU processing, I power off the virtual machine, copy the other files (which would include the deltas from disk and whatnot) and turn on the vm on the destination host (which would cause only a few minutes of downtime).  Later, I consolidate records by removing the snapshot on the destination host.  Way to a poor man to do a migration of vm on ESXi free edition with little downtime.

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

• Mount an .iso that is stored IN the virtual machine.

  Briefing Note: deploy us thin client on several campuses. Create us the model, deploy in each site, and then rebuild each pool. We now need to mount an image file .iso for one of the required programs. The .iso image file cannot be mounted with the software of in the virtual environment, because it uses a software of PortectDISC. We have the right number of drives, but customers have no disk drives.

  Problem: Since deploying the model, we must include the file .iso with her image. Normally, you would ride a .iso manually. However, load the file on each remote server .iso image and enter in each of hundreds of machines virtual one at a time to set the .iso way are not possible. Mount the .iso image file is our only option. Is there a way to store the .iso image file in the hard disk of the virtual machine and the virtual machine settings to rise from this point .iso? Or is it possible to include the image .iso with the model file when we deploy it is with each virtual machine and the path in the settings is already pointing to it?

  We tried to put the file .iso image on a store of data on one of our ESX servers, and then modified the model gold on this machine to point to the .iso image file. We reconstructed the pool, and the image .iso file mounted correctly. The problem with that is that we have 20 + machines trying to access the same file at the same time. Let the first few machines work, but the rest said it had disc read errors. So, we want to each machine to have its own .iso.

  Any help is greatly appreciated.

  Hello

  I have to add a warning that I use not models, but I don't think it is very relevant to my answer.

  @wila: well, I had thought about it, but when deploy us the image, it will automatically change the path to the file? For example, if we note the virtual drive to mount the .iso file to "\vm_template\cd.iso", then deploy, each of the virtual machines will not have this same path in their settings? Then they will all point to '\vm_template\cd.iso' instead of their own institution ' "\vm_##\cd.iso? '" If so, this would require we go each of hundreds of machines and set up manually every time that we deploy a model.

  If you do not add a path, then the iso that the virtual machine will try to open will be local to the virtual machine. You can simply do this by copying the vm to the path of your virtual machine, for example "[storage1] \vm_template" and affecting the CD this specific path.

  As is the same way, you can wait for the vSphere client is smart enough, it does not remove the path for drives in such a case, but not for CD...

  To use the vSphere Client to create the bases so far

  What I just did, go in the vmx file, deleted information path of superfluous and only left the name of the iso file, and all the true startConnected, not the virtual machine to make sure that my edit is OK, again registered the VM in the vSphere client, then started my VM and mounted the cdrom without any problem whatsoever.

  So - as expected - it works fine the iso file is local to the virtual machine and the local path comes first unless you assign specifically it different in the vmx file.

  --
  Wil
  _____________________________________________________
  VI Toolkit & scripts wiki at http://www.vi-toolkit.com

  Writer to the blog www.planetvm.net

  Twitter: @wilva