Cannot resize the virtual disk, the virtual machine by using a «child» vmdk file

Similar Questions

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

• Why the GUI vmware.exe resizes when virtual machines?

  Why the GUI vmware.exe resizes when virtual machines?
  For me, it's very annoying - how can I disable this behavior?

  Hi Continuum,

  Have you checked the settings of automatic adjustment under "Preference-> Display? I guess that your "Autofit window" is checked.

• Workstation 8; cannot resize the disk on the full clone

  I have a related clone I want to create a complete clone so that I can expand the virtual hard disk.  But after I created the full clone and try to use the indicator Workstation 8 utility I have an error message: "You can't develop this virtual disk because it is a linked clone."  I tried this three times, with great attention the last two times to read all dialog boxes to make sure I'm not a mistake, but the same error comes back every time.

  Here are the steps I go through:

  (1) turn off the linked clone

  (2) delete all snapshots for the linked clone

  (3) file-> open-> choose the clone of linke

  (4) VM-> manage-> Clone - to pen the Clone Virtual Machine Wizard. in the wizard:

  (5) "The current state of the virtual machine" pick (I tried as long as and create a snapshot and try to clone from that)

  (6) select "CREATE FULL CLONE' (not ' create a linked clone)

  (7) name the new complete cloned machine, and then click on finish

  After about 10-15 minutes, I get a message indicates the complete clone is finished.  I then close VMware, open it back up, open the new full clone that I created and select chose to: edit virtual machine settings-> tab-> click on the hard drive to extend hardware-> utilities-> Expand.  The error box I mentioned above pop and 8 workstations does not indicator the hard drive.and error as described above.

  Am I missing something here?

  If you can confirm the virtual disk of the new virtual machine is not a Flash disk (i.e. with 00000x.vmdk in its name) and the vmware.log file (created after you turn on the virtual machine) shows not all other hard files, you can check if the .vmsd of the virtual machine file contains incorrect entries. Essentially - after making sure that no other hard files are used - you could just delete the .vmsd file.

  André

• ESXi 4.0 on Dell 1850 this host doesn't support VT you have configured the virtual machine to use an operating system 64-bit client.

  Hello

  , I have in 3 data centers Dell 1850, identical hardware configurations.  I installed Esxi 4.0 to the ISO from site Web de VMware dell custom help. He is successfully installed on all servers, without error at all. I've updated them all to the last generation, using VMware vSphere Client. I have a problem with one of the server when I want to use 64-bit machines, he realizes: this host does not support VT you have configured the virtual machine to use an operating system 64-bit client.  However, this host is not able to run 64-bit virtual machines or virtual computer has 64-bit support disabled. For more information, see http://www.vmware.com/info?id=152. I don't understand why I got this, servers are identical, versions of BIOS, firmware, and all updates are the same. There is also a warning in the configuration tab, on the State of health link.

  Thanks in advance for any helpful suggestion.

  Yes according to the description of CPU, it seems that they do not support intel VT:

  http://Ark.Intel.com/product.aspx?ID=28016&processor=&spec-codes=SL7DX, SL7HH, SL7PF, SL7TD, SL8KQ

  Please give points for any helpful answer.

• [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?

• Firefox cannot resize the files of gmail download dialog

  When you use Gmail and I click on the attachment link to see the file download dialog box, it is always displayed full screen and I cannot resize. the small < < thing in the lower right corner does nothing and there is no resizing does not control in the upper right where X is. execution of Gmail using Chrome does not exhibit this problem. I recently did a Firefox "refresh" and it has not changed this behavior. It is a new problem that must be linked to a recent change somewhere that I saw this problem over the years of a prior use of Firefox and Gmail. He just did the same thing when you click Browse on this Mozilla support page - is not a specific problem of Gmail.

  Can you open the system menu via Alt + space and use Restore or resize?

• How can I connect to a virtual machine that uses a NAT map from outside via RDP

  Hi, I'm under workstation 7.11. I have a windows xp virtual machines all use adapter NAT of VMware Workstation for connectivity. I am only able to connect to the VMs with RDP client via the host. If I try to anywhere else, I am unable to connect.

  You can use linked by a bridge instead of NAT?  If this isn't the case, you need to enable Port Forwarding on the VMnet in the virtual network Editor.  FWIW, if you do not enable Port Forwarding I recommend setting up on a VMnet custom as VMnet2 example and assign the NIC of the virtual machine.  This keep the default VMnet8 for an unaltered NAT network.

  Default port for RDP is TCP 3389

• Cannot find the left column that used to be on the documents and photo files.

  Cannot find the left column that used to be on the documents and photo files. On this missing column I know was there before, had options fax, copy and other things we could do with these files. I want to get that back. Thank you.

  With my Documents folder open, go to Toolsand then click on Options files . On the general tab, tasks section, choose Show tasks in folders.

  I would like to know if it works. Thank you.

• cannot resize the disk on a virtual machine

  Hello!

  I have a little problem, I can not resize the size of the disk on some of my virtual machines.

  I tried yesterday on two and worked well, tried to day (different vm) and it does not work so well for me.

  I first stop the virtual machine, rightklick, change the size to 20 GB, 4 GB and press OK.

  When I then rightklick on the virtual machine after pushing OK the size is always 4 GB (I don't mean in VI client for Windows).

  Why? workaround solution?

  Thnx for help.

  VM there snapshots?

  ---

  VMware vExpert 2009

  http://blog.vadmin.ru

• cannot resize the virtual disk (vmdk) after successful hyper-v conversion

  Hello

  We are experiencing an environment vSphere 4.1. I have a problem on the Ramdisk resizing.

  We had managed to convert a hyper v VM. Virtual machine operating system is Windows 2008.

  After that, I can't resize the virtual disk (GB in disk options was gray-ed out, even when the virtual machine is power down)

  It's strange

  I have attached several screenshot of the virtual machine.

  Need your advice.

  Thank you

  His grace is on the IDE interface and you can not resize. the only way is to reclone using vmware converter and resize in the wizard. For more information: http://www.yellow-bricks.com/2010/05/28/resizing-your-ide-virtual-harddisk/

• Cannot resize the virtual disk

  My vm upgraded allows no expansion vdisk in the pane settings; said must delete all snapshots, yet no old clichés exist. Version 2.0.2 (147997) to run on a MBP 17 "intel 2.16 g.

  Based on list stamps and the date/time of file on the files, you have a snapshot in place and you can try to remove it by trying the following with the not suspended, and Virtual Machine within Windows to stop.

  Take a snapshot, and then immediately delete the snapshot.

  Note: I personally don't do without first making sure that I have all the user data saved from within the Virtual Machine from a store outside of the Virtual Machine and or a manual full copy of all of the Virtual Machine.  Just in case!

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