Similar Questions

• Fret is disabled for this virtual machine

  Host environment: Windows XP Professional x 64 SP2

  Environment comments: Windows Server 2003 R2 SP2

  Of disk space free hosting environment: 31.1 GB

  Comments environment size the disc: 13 GB (total 20, 7 for free)

  Comments environment size the disc on host drive: 20 GB

  VMWare version: Workstation 6.5.0 build 118166.

  The question:

  I am currently unable to carry out the reduction operation.

  I did a search on google and find a few scenarios:

  • http://communities.VMware.com/thread/113057

  • http://communities.VMware.com/thread/151594

  However, I was not able to solve the problem.

  The full message is as follows:

  Fret is disabled for this virtual machine.  Shrinkage is disabled for linked clones, parents of clones related, préalloués disks, snapshots, and other factors.

  This virtual machine has definitely shrunk in front.  I tried to reinstall VMWare Tools and it does not correct.  I checked that there are no snapshots in the Snapshot Manager.  I also tried as suggested by one of the sons: adding a snapshot and then remove it.  I'm unable to the fret.  Of course, this isn't a linked clone or a parent of a linked clone (do not know how to use them).  How can I tell if it is a pre-allocated disk (I don't think it's, but who knows)?

  On the file system, the looks of the directory as follows:

  • ------& lt; GUID & gt;. vmem.lck

  • \Windows server 2003 Standard Edition.vmdk.lck

  • \Windows server 2003 Standard Edition.vmx.lck

  • & lt; GUID & gt;. vmem

  • VMware - 0.log

  • VMware - 1.log

  • VMware - 2.log

  • VMware.log

  • Windows Server 2003 Standard Edition.nvram

  • Windows Server 2003 Standard Edition.vmdk

  • Windows Server 2003 Standard Edition.vmsd

  • Windows Server 2003 Standard Edition.vmx

  • Windows Server 2003 Standard Edition.vmxf

  • Windows Server 2003 Standard Edition - flat hard

  Any help would be appreciated.

  The list of files that you show your virtual disk is pre-allocated (*-flat.vmdk).  As the message says, you will not be able to reduce a drive pré-alloués.

• This virtual machine may have been moved or copied during the priming two different Macs from the external SSD drive

  I am using this SSD external boot drive to start two different iMacs at work and home, making all my stuff to update this SSD.

  However, when I open the virtual machine in Mac OS X Server 10.6.8 (Snow Leopard) on VMware Fusion on OS X 10.8.3 5.0.3 (Cougar) installed on startup such external SSD disk, VMware asks what follows by trying to open the virtual machine on the FIRST Mac:

  "This virtual machine may have been moved or copied. In addition, I saw:

  Q.) VMware tells me: "this virtual machine may have been moved or copied. What should I do?

  VulnHub - Frequently asked Questions

  Choose "I moved it", or "I copied it"?

  Is it possible to PREVENT VMware Fusion ASKING such question with each single switch to Mac (as said, I always start the two Macs at work and home from the same SSD drive)?

  Thank you.

  VirtualMac2009 wrote: WoodyZ, the "Mac OS X Server 10.6 64 - bit.vmx" has a lot of lines. I understand that I should just stick

  UUID.action = 'keep '.

  the last line and save. Right?

  The order of placement of the options in the .vmx configuration file are not relevant as long as each is on its own line.

  On the other hand, I hope than boot from SSD external drive to start two different Macs (one at work and one at home) will not break she like says dlhotka.

  The main issue will be the differences between the CPU and according to what difference, say a Core 2 Duo vs Quad Core this by itself may be sufficient to trigger WPA on a Windows Virtual Machine.   Like many a Client in Mac OS X or OS X Client that shouldn't be a problem however with Mac OS X Server or OS X Server so that I moved it with a Core 2 Duo vs Quad Core, I have not had problems yet but the haven of the exhaustive tests with the server version.  I think it will go well, however, we should always do... maintain appropriate backups!

  Post edited by: WoodyZ - point makes it dlhotka about snapshots is a very good and must be taken into account! ;)

• With the help of VM Workstation 8. error when restoring from instant snapshots are not allowed on this virtual machine.

  Hello

  I have takena instant and then try to turn on the machine and get a message:
  "Snapshots are not allowed on this virtual machine!

  When I try to start the snapshot form, I get an error:
  "snapshot restore error, snapshots are not allowed on this virtual machine.

  Can you please help?

  It seems that the configuration (.vmx) file has been deleted (zero byte). I recreated a new you have attached log files. Please replace the file corrupted with VMware Workstation (or at least tab of the virtual machine) closed in order to ensure that the replaced file gets read.

  André

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

  I get this error message:

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

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

  My OS:
  Tumbleweed OpenSUSE x 64

  Thanks in advance

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

• virtual machine cannot start, because the snapshot of the virtual machine has been deleted by mistake.

  virtual machine cannot start, because the snapshot of the virtual machine has been deleted by mistake.

  When I start this virtual machine, it prompts: unable to find the 0001.vmdk, this disc is my shot, has been deleted by mistake.

  How to restore this virtual machine.

  You need help with a revival of the 000001.vmdk deleted or do you want to repair the virtual machine so that it works without the snapshot?

  The last option, follow these steps:
  remove the virtual machine from the inventory and edit the vmx file so that it uses the basedisk. Then add the virtual machine to inventory.
  If you need data from the snapshot call me through Skype "sanbarrow" - I may be able to help

• VMware Workstation is unable to open one of the virtual disks required by this virtual machine because it is larger than the maximum file size supported by the host file system.

  I'm transitioning from Windows XP (64-bit) on a new computer with Windows 7 installed.  I undertook to VMWare Workstation 6 7.0.1 in the process.  The problem is with a very large RAID 5 volume on the new system.  It's a score of 5.45 TB (TPG and NTFS).

  When I try to start a virtual machine on this volume, I get the message "VMware Workstation cannot open one of the virtual disks required by this virtual machine because it is larger than the maximum size of the files supported by the host file system.".  This is obviously not true.  If I copy the virtual machine to another drive on the system, it starts without a problem.

  Anyone have any ideas on how to work around this problem?

  try to add this line in the vmx file:

  diskLib.sparseMaxFileSizeCheck = "false".

  Maybe it helps.

  VMDK-type do you use?

  monolithicSparse? -C' is the only part type more?

  ___________________________________

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

• Blue screen at the start of WinSrv2008r2 recovered from the backup of windows virtual machine image

  Hello

  At first, everything seems fine:

  -to create the new virtual machine

  -startup disc for instalation of Windows Server 2008 on this VM

  -Select "Repair system" and point the backup image file (full backup - made with standard Windows backup tool)

  -system recovered successfully.

  But then, when the system restart recovered fresh - start start Windows normally - and suddenly it is blue screen with the error 0x0000007b

  IMHO, this first initiated boot of the recovered system trying to twist something in the special part of the disc and he cannot (because it's a virtual disk?)

  Is it possible to recover the system windows image file system server to virtual classic?

  Thanks in advance for all voice :-)

  Greetings,

  RA

  Welcome to the community,

  the error message is related to the controller to start the virtual machine, which is different from the original system, and its drivers are not loaded in Windows. What you try, it is to use the free VMware Converter and run the option "Set up the Machine", which should inject the necessary drivers in the virtual machine. Before doing this, please make sure that the Windows 2008 virtual machine has the default "LSI Logic SAS' controller configured in its settings.

  André

• Virtual machine has 12 virtual processors, but the host only supports 8?

  Hi all I am using ESX 5.1 and have a machine Windows 2012 R2 Standard of virtual (vmx-09) comments that I'm moving to 8 processors to 12 processors.  But when I turn on the virtual machine after changing the UC 12 I get the error message

  "Virtual Machine has 12 virtual processors, but the host only supports 8. The number of virtual processors can be limited by the selected guest OS for the virtual machine or the granting of licenses for the host".

  Now, I know that 2012 R2 Standard Windows can handle 12 processors and I thought that ESX 5.1 could also, but I'm wrong?  This is the Standard of vSphere license 5.  Thank you!

  Hello

  vSphere 5.1 Standard license has a 8 vCPU per VM limit.

  Company = 32 vCPU

  Business + 64 vCPU

  You must upgrade to vSphere 5.5. This can be done with your vSphere license 5, as it is for all versions 5.X of vSphere and vCPU limit has been deleted in 5.5.

  So you can have as many vCPU per VM that your host has logical cores.

  Tim

• One of the disks of rhe in this virtual machine is already in use by a virtual machine or a snapshot

  Hi all.

  An apologize for my bad English.

  I have 10 VmWare installed on Linux Centos 5.

  I worked with the Windows 7 virtual machine and hang on it.

  Now when I try to run this VM, I get this message:

  "One of rhe in this virtual machine disk is already used by a virtual machine or a snapshot.

  I try to fix it in this way:

  Re: Could not open the hard file. One of the disks in this virtual machine is already in use by a virtual machine or a s...

  mkdir ./clone
  vmware-vdiskmanager -r "Windows 7 x64-000008.vmdk" -t 0 "Windows 7 x64.vmdk"  
  mkdir /backup
  mv *.* ./backup/
  cp ./backup/*vmx ./
  cp ./backup/*vmxf ./
  
  

  But after that, I got the error: "cannot change the power state of VM: can't open ' / * /Windows 7 x 64 - 000008.vmdk.»» The system cannot find the specified file.

  Please, help me to solve the problem.

  Once again apologize for my English :)
  

  
  

  
  

  
  

  
  

  I really don't see what could be causing the problem, except that there are some .lck files in the subdirectory "lock"!

  Anyway, if worry ends snapshots and the current state is what you need, you can follow these steps (which are close to what you have already done) to merge snapshots of virtual disk in and use this virtual disk to the virtual machine:

  • Close VMware Workstation
  • Create a new subdirectory and move the VM files and folders to backup purposes
  • "" since this subdirectory run: vmware-vdiskmanager-r "Windows 7 x 64 - 000008.vmdk" t 1 '... / X64.vmdk of Windows 7 '
  • Copy the .vmx file to the parent directory and edit it as follows:
    scsi0:0.fileName = "Windows 7 x 64 - 000008.vmdk" --> scsi0:0.fileName = "Windows 7 x64.vmdk"

  Now you should be able to start the virtual machine with the cloned virtual disk.

  André

• Change tracking (CTK) block is supported for this virtual machine, but was refused. This will increase the CPU proxy and consumption of IOP.

  I have problems with a client of VMware image-level in an EMC Avamar backup.  So far, we have not been able to find information about this message in the backup log file.  It is originally the backup to take a very long period of time (on average 10-11 hours).

  2014-02-28 14:20:57 avvcbimage < 14681 > Info: change tracking (CTK) block is supported for this virtual machine, but was refused. This will increase the CPU proxy and consumption of IOP.

  We cannot determine why CBT is "denied".  Has anyone here run across this issue before or seen any other type of backup VMware image have denied CBT?

  Everything I checked watch that CBT is successfully activated since the file vmx for the customer to the Avamar config.

  ESXi host is Enterprise Plus 4.1.0 260247

  After spending some time on this issue, the ultimate resolution withdrew the Avamar vm and then add it again.  After that, CBT began to work properly.  It seems that there is a parameter that has been 'stuck' pertaining to this virtual machine that wasn't behaving properly.

• Transfer data from the laptop to the Virtual Machine.

  Hello

  I'm trying to transfer some data from my laptop to a virtual machine. This virtual machine is not in a domain or network. Not assigned an IP. How can I transfer files? I tried to mount VM to the local data store, but she only accepts ISO files. I'm trying to transfer files .txt and the .vbs file. Any idea?

  Kind regards

  ZaraRose.

  If you are dealing with just text files you can activated copy / paste via the vSphere client - kb.vmware.com/kb/1026437.

• VMware Workstation 6.5 - not enough physical memory is available to power on this virtual machine

  My host is a processor Intel Core i5 (active VT) and 8 GB of RAM Windows 7 64 bit running with hardware virtualization enabled.
  
  Apart from McAfee Antivirus and the usual Windows updates, no other software has been installed on the host machine.
  
  I am running Vmware Workstation 6.5 and I installed 3 popular VM with below guest OS, s/w and memory:
  
  VMware ESX 4-2 GB
  Server 2003 (DC and DNS) - 1 GB

  Server 2003 (vCenter Server) - 1 GB
  
  However, it is not possible for me to all 3 virtual machines run simultaneously. If I turn on Vmware ESX 4 and try to start Windows 2003 VM, it displays the following message:

  Not enough physical memory is available to power on this virtual machine with its configured settings.

  To resolve this problem, set the parameters in additional memory to allow for more virtual memory machine to swap.

  If you were able to on this Windows virtual machine on that host computer in the past, try restarting the host computer. Reboot may allow you to use a little more memory host to run virtual machines.

  Can you get it someone please let me know where are the rest of the memory is busy? Size of total memory of 3 virtual machines are only 4 GB and I have to be able to run all the VMs set 3, but in this case I can't even run two virtual machines simultaneously.

  Please help what should I do?

  With 8 GB of RAM on the host allowing why only 1 GB to be reserved for all you run virtual machines?

• Copy or duplicate virtual machines

  I installed ESXi 3.5 and I use VMware Infrastructure Client to manage.

  How can I copy/duplicate existing virtual machines the simplest and fastest way?

  I tried to copy files between folders, but the server hanging, so I presume that there is a better way...

  Concerning

  Marius

  Simplest is to clone virtual machines, but this feature is not available in free ESXi, you have vCenter.

  So I guess the only way is to use FastSCP (free tool), download power power VM off to your office and new different directory. Then right click on .vmx datastore browser and "add to the inventory.

  ---

  VMware vExpert 2009

  http://blog.vadmin.ru

• This virtual machine to become protected vsphere HA and HA can not try to restart after a power failure

  I got a 5.1 cluster with some problems HA.

  a few virtual machines are showing this

  This virtual machine to become protected vsphere HA and HA can not try to restart after a power failure.

  When I try to reconfigure HA on the host. It times out and fails.

  any idea?

  Instead of reconfiguring HA on the concerned host, have you tried to disable HA on the cluster and enable again? See: VMware KB: State of the virtual machine changes from protected to Unprotected