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?vm1.png

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é

Tags: VMware

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.
  • Disks of the virtual machine consolidation is necessary is Unable to Access file < file_name indeterminate > because it is locked

    Hola a tod@s,

    After using the application of only backup '5.5 virtual Data Protection' y no las snapshot los correctamente foot VM´s, me appears a message en the pestana "Summary" indicating:

    Consolidation of disks of virtual machines is necessary

    Bueno... mirando the documentation oficial, are several soluciones, the first are pulsar en option "SnapShot-> Consolidate" pero muestra el error:

    Unable to access file < unspecified file name > because it is locked

    What is seria el siguiente paso?

    -ESXi version 5.1

    -En VM´s production...

    Gracias por todo.

    Saludos.

    Please if you ha sido util the respuesta correcta como marca respond.

    Gracias!

  • Consolidation of virtual machine disk is necessary

    Hi all, I met one of my VM that have the warning message "disc of virtual machine consolidation is necessary" and I check and there is no existing snapshots in snapshot Manager.

    When I browse the data store I have a lot of vmdk files such as below. How can I correctly to clear up? It is a production server so it would be safe for me to power off?

    Running the ESX ESX Server 5.1 U1

    Server1_00.VMDK 157GB

    Server1.VMDK 41GB

    Server1_1 - 000002.vmdk 18 MB

    Server1 - 000001.vmdk 18 MB

    Server1-0000001 - ctk.vmdk 2. 5 MB

    Server1_1 - 000001.vmdk 18 MB

    Server1_1-0000001 - ctk.vmdk 4 MB

    Server1_1-0000002 - ctk.vmdk 4 MB

    Server1 - 000002.vmdk 18 MB

    Server1-0000002 - ctk.vmdk 4 MB

    Server1 Snapshot.vmsn 19KO

    Server1 - 000003.vmdk 210 MB

    Server1-000003 - ctk.vmdk 2 MB

    Server1_1 - 000003.vmdk 250 MB

    Server1_1-000003 - ctk.vmdk 4 MB

    Just right click on the virtual machine and select "snapshot" and then select "consolidate."

  • Consolidation of Virtual Machine disk is necessary question

    Today, I have one of my virtual downwards because the error message that says that "there is no more space for disk virtual xxxxx - 000018.vmdk.» you might be able to continue this session by freeing up disk space on the relevant volume by clicking on try again"

    I want to know why this happened if I make my virtual with 1.5 to and my server is new... so for the most part the server have 300 GB in use... I also had 750 GB available for an another virtual and that the question, why this virtual grow too much and too quickly?

    Also when this happened how can I do to solve this problem, how disk space if I did a single data store with al the available space.

    The suggestions will be welcome.

    Thanks for you comments.

    Concerning

    JP

    In the files you posted, it appears that 000002 and 000007 files are not in use by the virtual machine, but the others are. What I recommend you do is to open the Snapshot Manager, create a new snapshot and then run "Delete All". This should clean all the snapshots except for the two mentioned above. If this is the case, shut down the virtual computer and move the two snapshots listed in a subfolder (to be able to restore them in case I'm wrong), then power on the virtual machine again. If there is no error, you can delete the moved files.

    Unfortunately I can't see any rule, snapshots are used and that have been created just for adding hot backup not, so you should always have to understand this from scratch. At least for the moment until Acronis comes up with a fix, you need to delete snapshots manually on a daily basis since the Snapshot Manager (create a new cliché-> Delete All) to avoid any trouble with too many active snapshot on the virtual computer.

    You have another virtual computer that has NOT "changed block Tracking" on, to see if the problem is related to the CBT!

    André

  • Question alarm "State of Consolidation necessary virtual machine.

    I have a virtual machine showing an alarm "State of the virtual machine Consolidation necessary."  What I've read online, this can happen if a snapshot file exists and is not recognized by the Snapshot Manager, which is not the case here.  I checked the Snapshot Manager and without clichés exist and I checked the data store, and there is no file snapshot.  Should I recognize just the alarm, or do I consolidate?  In my mind, if there is no snapshot file, there is no point in running the consolidation... it could simply error-out or tell me there are no snapshots.  I wanted expert advice before taking any action, thank you.

    You are able to do the following? :

    http://KB.VMware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalID=2003638

  • Virtual MACHINE created on VMWare Workstation for Windows - move to VMWare Workstation for Linux?

    I have a bunch of VMs that I built using VMWare Workstation for Windows running on a Win2003 Server 7.1.3. The virtual machine is running Windows XP sp3. Can I move these Ubuntu VM to run under VMWare for Linux, if I buy a license for the current version or any version?

    Thank you

    Yes, but with some reservations.  Of course, Windows and Linux use different ways to represent the paths and devices so a few changes to the virtual machine may be necessary.  All that is hard coded in the configuration file .vmx depicting the paths of type Windows and device names must be changed by the GUI settings or manually edit the .vmx config file.  In addition any virtual machine containing snapshots where the parentFileNameHint in the DescriptorFile of disc, so drowned in a monolithicSparse or the first measure not binary snapshot virtual hard drive, which uses a QPF (fully qualified path name), it will have to be changed.  If you are unsure how to do this then I suggest a delete all snapshots before moving on to another system.

    A Windows VM that fall under the WPA will in all likelihood have to be reactivated if the host CPU are not in the same class.

    If you copy a Windows VM for the delivery of a copy on the source system, that you must have and or get the appropriate number of licenses and or product keys for the copy number you keep.

  • Virtual machine set up their: consolidation of necessary virtual machine disk.

    a virtual machine guest: set up number: consolidation of necessary virtual machine disk.

    I click on this virtual machine > > snapshot > > Consolidation.then about a minute.

    He failed: cannot access < unspecified file name > file because it is locked

    02.jpg

    This question well in the base backup tool VADP Storage API. This file is locked by worker VPXA get. Then restart (host managegemnt connection) services vpxa and spend on your host and redo the consolidation 1) disable alarm processing host connection failure and failure of network connection (to avoid unnecessary alarm0 2) connection to the host through ssh) 3 run # /etc/init.d/hostd restart and restart # etc/init.d/vpxa, 4) re-do the consolidation of the vm.

  • Consolidation of disks of virtual machines is necessary

    I did something really stupid and cancelled snapshot creation task.  Sound running on ESXi 5.5.0, server there are a few other vm running on it.  Now there is a message saying that the consolidation of the disk is necessary.

    Thing is that it was the first snapshot of this virtual machine. Should I try to consolidate, ignore this message or maybe try to make the new snapshot?

    John,

    I know, it shouldn't be a problem. You can simply consolidate the disks. He speaks, because when a snapshot is made, a new delta vmdk (VM disk file) is created. All the new changes from there are saved in this new VMDK, but since you abandoned the snapshot process, the virtual machine is probably running on a delta disc, but the database snapshot does not report an instant success.

    I would like to know if it works for you,

  • How to remove the msg: "consolidation of disks of virtual machines is necessary."

    Hi all

    I implement vSphere 5, and I have the following message displayed in the vCenter (virtual machine Summary tab). Does anyone know how to remove the message without consolidating the snapshot?
    ----------------------------------------------------
    "Consolidation of disks of virtual machines is necessary."
    ----------------------------------------------------

    I think vCenter is detect the Delta for this virtual machine and warning me that I have to consolidate the snapshot. However, I do not want to consolidate the snapshot because the database is still running when the snapshot was taken, and there is a great chance that the data will be corrupt when I consolidate this delta disk file.

    I looked towards the top of the Knowledge Base, but it does not say how to stop the message without actually consolidate the snapshot.
    ----------------------------------------------------
    Instant KB:2003638 in vSphere consolidation 5
    http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 2003638
    ----------------------------------------------------

    Thanks for you information in advance!

    < environment >

    -VMWare vSphere 5 ESXi
    -VMWare vSphere vCenter 5
    -NetApp storage

    the message will disappear as soon as snapshots are consolidated.  There is no way to remove the message otherwise.  Just think of it as a reminder that the snapshots should be engaged.

  • List of instant and virtual machines in need of consolidation?

    In the vSphere client 5, it is possible to display all the VM in need of consolidation. In PowerCLI, I can't find this option.

    Is it possible to list all the VM who have snapshot in need of Consolidation?

    It is not (yet) available in the regular cmdlets, but it's pretty simple display this as a calculated property.

    Get-VM | Select Name,
    @{N="Needs Consolidation";E={$_.ExtensionData.Runtime.consolidationNeeded}}
    

    And a Variant perhaps useful, only list virtual machines in need of consolidation of the snapshot.

    Get-VM | where {$_.ExtensionData.Runtime.consolidationNeeded} | Select Name
    
  • Help converting a physical server 'live' in a virtual machine VMware VirtualCenter Consolidation 2.5.0

    Hello, I read the manuals and understand the process as much as I have not actually started the consolidation. I have a Compaq ML350 server which has a default of fan cooling and want to make a virtual machine as a starting point. It will be important for the virtual machine to have the same computer name and be a member of our domain. The only question which does not seem to be addressed has to do with the old server. I need to have the available printserver. I know that you cannot have two SID, names of computers or IP addresses on a network domain at the same time. There is an option to change the name of the virtual machine before you start building. It would be wise to use a temporary computer name while doing my first consolidiation/conversion. Once completed, I could stop the printserver, remove the domain, start the virtual machine, rename it, join it to the domain, and then set the IP address to match my old material printserver. I guess correctly? I can't wait to leave the company without a printserver for more than a little bit. I guess additional servers, I wanted to convert should be treated in the same way? If I posted in the wrong place, please accept my apologies. If there is other material that I may have missed that might also be useful, but I have about 4 different PDF so far. Thank you. brand

    I forgot an important step - sorry, you must add the converter

    plugin - in the menu there is a plugins to manage - it's here where you

    can add the client plugin

    Once you do this, you should get this option

    January 28, 2009 at 15:08, 'rsxsr' [email protected]

  • Is it necessary that the guest OS to support SSD if the file of the virtual machine is placed on an SSD?

    Dear,

    I have a plan to set up a file of the virtual machine on an SSD. The host system is windows 10 (on an other SSD, I'll use 2 SSD), it should support the SSD very well.  Then comes the question: should I also install an OS that needs support also guest SSD?

    My opinion is it does not matter since the disk i/o operation is made by host operating system, it is the host operating system which finally determin whick block data will be published (optimization of the disk).

    Am I wrong? Thank you.

    Sorry for the enigmatic answer...

    In your case, the answer is Yes: he cares about the type of media, while the virtual disk is a vmdk (virtual material treaty) and placed in an SSD.

    There are a few cases where you might use a physical disk directly to the virtual machine (called peripheral raw disk or RDM in vSphere environment).

    Concerning

  • New vmdk virtual machine, comments system really necessary?

    The scenario: I used the tool from Terabyteunlimited (Copyp2v) to create a vmdk to a physical Win XP Pro machine.  Works like a charm.  Installed VMware Workstation 10, created a new virtual machine and skipped the guest operating system, has chosen the vmdk and started the virtual machine.  He started on the office and started looking for drivers.  Down on a bar looking for ToolTip appears "install Windows XP Professional as you ' d on a physical computer.". When you are finished and that the operating system starts, click "I've finished the installation. »


    I'm confused as the vmdk is a disk with Win XP Pro installed.  I have a new unused copy of Win XP Pro, but I have to install it?  The virtual machine is running without him?  What is a performance problem or a problem of license?  Thanks for the help!

    You can ignore this message, but on the missing drivers, you will need to install VMware Tools on this new VM.

  • Consolidation of virtual machines to a custom policy

    I have a group of VMs that currently do not reside in the same folder, but are identified by a naming only through multiple vcenters scheme.  * acmevms *.

    I can't combine them into the same folders. In vSphere UI-> Configuration-> manage strategies, how can I better apply a strategy custom for them?  I don't want to have to manually select the 400 VMS and add them to the group...

    Thank you!

    Create a custom group. Is he filled dynamically. Add virtual machines by criteria name contains acmevms. This will dynamically fill all virtual machines with this generic term.

Maybe you are looking for