How to set vm-description/notes and get the name of the data store, where the virtual machine

Similar Questions

• How to install and configure the virtual machine with XP as an operating system on a Machine running Vista

  How to install and configure the virtual machine and XP operating system inside, with vista as my work machine.

  * original title - how to install and configure the computer virtual and XP operating system inside, with vista as my work machine.*

  How to install and configure the virtual machine and XP operating system inside, with vista as my work machine.

  Hey Preethi23

  It comes to the installation of vista operating system instance

  read the links below

  http://www.Microsoft.com/Windows/Virtual-PC/support/Virtual-PC-2007.aspx

  http://www.Microsoft.com/Windows/Virtual-PC/support/FAQ.aspx

  http://www.Microsoft.com/downloads/en/details.aspx?FamilyId=04d26402-3199-48A3-afa2-2dc0b40a73b6&displaylang=en

  Walter, the time zone traveller

• Script in VMWare Server to stop, save and reboot the virtual machine

  Hello!

  I want to create a script from windows vista Pro (which is my vmware server host) this judgment of a virtual machine before you save it and restart the virtual machine after.

  Does anyone know how to do this? This is my first script, so I don't know how to start...

  I saw this link:

  http://www.Petri.co.il/virtual_script_startup_shutdown_vmware_servers.htm

  But it seems to be for VMware Server 1.X because I can't found the vmware-cmd in the server vmware 2.0 folder.

  Thanks for your help!

  I don't know if you are receving notifications to your PMs, just I have sent you a PM >

• cannot not power off the virtual machine, but don't think the host it is running!

  I have two clusters VI3. An older cluster to 3.02 hosts and a new cluster with ESXi hosts. Level of current patch on ESXi hosts. New guests and old presenters sees the same storage, but I have additional storage which can see only the new virtual machine.

  Most of the migration to the new cluster went very well. A few questions. But a VM just GIVES me fits.

  After the failure of attempts to migrate the virtual machine to the new storage, I thought I just migrate the virtual machine to the new host and leave it on the old storage, for now, until we could find something later. VCenter events logs show that the migration has expired. However, the virtual machine appears in the new cluster and is no longer in the old cluster. Also, he turned on itself for some reason any. Turn off in Vcenter gives the error "the operation failed because another task is underway." Having the VM that I could put it off in before Vcenter, and no no unsure of how to use the RCLI for this, I have connected to the host directly mode "not supported" and has run vm-support - x to get the list of running virtual machines and their ID's so that I could kill him. However, the host does not include this virtual machine in the list of virtual machines. So I think a virtual computer that runs Virtual Center, but he thinks the host it runs on is unclear if I can't kill the process.

  Help?

  Have you tried to restart ESXi management officers, as well as the vc service is restarted?

  -KjB

• Transport mode "nbdssl" is not available if the virtual machine has no snapshot

  When I use VixDiskLib_ConnectEx with a vmdk having a snapshot, I "nbdssl". If the virtual machine has no snapshot, I've always had "nbd" no matter what I specified in the parameter transportModes of the VixDiskLib_ConnectEx. I tried NULL, "nbdssl". It affects always unconditionally "nbd" when there is no snapshot.

  Is this expected behavior? If so, I am not able to write safely to a vmdk. During a recovery, I create a new vm. However, there is no snapshot. I want to get back to this vmdk.  How to work around this limitation of security?

  You use 1.1?  nbdssl restores are not supported on 1.1.

  -Remy

• Stop and restart the virtual machines in the remote server

  I need to close virtual machines running guests 4 1 ESX from a remote server (IBM System i).

  The remote server in fact control the storage used by ESX and VM OS, so I'll have to scripts running on the remote server that:

  Stop the virtual machine

  Performs maintenance

  Reboot the virtual machine

  I tried to understand the big picture of the reading discussions here, but I'm still confused.

  VMA is to provide the best way for the virtual machines of withdrawal from a script running on a remote server?

  Scripts can I use SSH to connect to the vSphere environment to run scripts or issue the command?

  Thank you.

  vCLI (really its vSphere SDK for Perl), PowerCLI, VI Java, etc are all vSphere SDK to correct and they are a of the client-side bindings different scripts and programming languages which bind to the vSphere API. When I say 'API', I mean using one of these SDK is you use the vSphere API to perform the work.

  The SDK is initiated on the remote server, this can be windows, linux, etc as long as it supports one of these boxes to tools. In general, for admins, you will use either vCLI (vSphere SDK for Perl) that supports Linux and Windows, or if you are more windows-oriented, you can use PowerCLI.

  Documentation has been referenced in my first post, please take some time the documents because they provide much more detail on the use cases for each + a lot of examples with orders. Yet once, there no involved SSH if you use the vSphere API. As I told, vMA is a virtual appliance, you can download and start using if you do not want to install vCLI or PowerCLI on a remote system, this is assuming that you are comfortable in a Linux environment. If you're not, then I highly recommend using PowerCLI, who will need a remote server for Windows.

  Here are a few started getting additional resources:

  vSphere SDK for Perl + vMA:

  Getting started with vSphere SDK for Perl

  Introduction to the vMA (tips/tricks)

  PowerCLI:

  http://www.VMware.com/support/developer/windowstoolkit/

  http://www.virtu-al.NET/2009/11/10/PowerCLI-where-do-i-start/

  =========================================================================

  William Lam

  VMware vExpert 2009

  Scripts for VMware ESX/ESXi and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

  Twitter: @lamw

  repository scripts vGhetto

  Introduction to the vMA (tips/tricks)

  Getting started with vSphere SDK for Perl

  VMware Code Central - Scripts/code samples for developers and administrators

  VMware developer community

  If you find this information useful, please give points to "correct" or "useful".

• With instant full VM LUN and now the virtual machine will not start or register

  Hello

  I have a case here, where we have a virtual machine that quickly filled the logic unit number and the snapshot is currently 110 GB. It is now available on the new LUN space, but the VM does not start and he was also addressed as 'unknown' in the viclient. I tried to cancel the registration and check-in again, but he refuses to register. It seems that the snapshot is damaged.

  When you try to save it, I get the following in hostd.log:

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA-flat.vmdk ': (17) successfully opened size = 48348147712, hd = 0. Type 3

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA-flat.vmdk ': open with success (21) size = 48348147712, hd = 0. Type 3

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA-flat.vmdk ': closed.

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA-flat.vmdk ': closed.

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-flat.vmdk ': (17) successfully opened size = 214764819456, hd = 0. Type 3

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-flat.vmdk ': open with success (21) size = 214764819456, hd = 0. Type 3

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-flat.vmdk ': closed.

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-flat.vmdk ': closed.

  DISKLIB-LINK: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000001-delta.vmdk ': cannot open (the specified file is not a virtual disk).

  DISKLIB-STRING: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000001-delta.vmdk ': cannot open (the specified file is not a virtual disk).

  DISKLIB-LIB: unable to open ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000001-delta.vmdk ' with flags 0 x 11 (the specified file is not a virtual disk).

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000002-delta.vmdk ': (17) successfully opened size = 214764819456, hd = 0. Type 8

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000002-delta.vmdk ': open with success (21) size = 214764819456, hd = 0. Type 8

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000002-delta.vmdk ': closed.

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000002-delta.vmdk ': closed.

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000001-delta.vmdk ': (17) successfully opened size = 214764819456, hd = 0. Type 8

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000001-delta.vmdk ': open with success (21) size = 214764819456, hd = 0. Type 8

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000001-delta.vmdk ': closed.

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000001-delta.vmdk ': closed.

  DISKLIB-LINK: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000002-delta.vmdk ': cannot open (the specified file is not a virtual disk).

  DISKLIB-STRING: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000002-delta.vmdk ': cannot open (the specified file is not a virtual disk).

  DISKLIB-LIB: unable to open ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000002-delta.vmdk ' with flags 0 x 11 (the specified file is not a virtual disk).

  Referred to as registry: AXAPTA/AXAPTA.vmx

  Vmsvc indicates file is loaded, by: /vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA.vmx

  I also tried to copy virtual machines directory down to a local PC and run via VMware Converter, but I get the message "the source VMware Consolidated Backup"filename.vmx"has a missing catalog file.

  1. VMware - v

  VMware ESX Server 3.5.0 build-130756

  Any help is appreciated.

  Lars

  The problem (according to the newspaper) is AXAPTA_1-000001 - delta.vmdk no AXAPTA_1-000002 - delta.vmdk (the error on the second snapshot is probably because of the broken parent snapshot).

  The descriptors are ok, which means that the VMDK itself is broken.

  If you do not have a backup, you can try the following:

  -Copy the files in another data store

  -change the second snapshot descriptor to point to the basedisk as the parent

  -Try and mount the drive

  -If you're lucky, you should be able to recover at least some data of

  -If the disklib is complaining again then the two snapshots are broken - which is unlikely

  Depending on how old the second snapshot (the older one is better it is) the method above will not help.

• NOT available in the Virtual Machine from CD/DVD

  
  I have 5.5 installed ESXi but I can't mount CD/DVD, it tells me that it is supported. I think it's down for not having installed IDE or SCSI device.

  I'm running a SUSE Linux server, how do I show that I need to boot from an ISO file to extend a partition.

  John.

  I found what the issue was. The customer has been tinkering with the hardware and had disconnected the DVD player. Once connected, I could get the CD/DVD to ISO files

• root password back on empty and disappear the virtual machines

  We arrived after the weekend and our virtual machine wasn't so I tried to log in the infrastructure client and the password did not work.  We tried to leave the empty password and it connected with root.  Then we saw that our virtual machine did not appear in the inventory list.  The data store still exists on the computer with the files that it contains.  That's happened?  How can I get it back?

  Welcome to communities

  I couldn't tell you what happened. There has been cases with a new installation where the configuration is not saved but be?

  If you are looking for your virtual machine, the data store and do a right-click on the VMX file and select Add to inventory, you will get your machines virtual return.

• CD/DVD drive not recognized inside the virtual machine

  No matter what I do, I can't get my VM (XP) to recognize the CD/DVD drive. I am running version 2.0.6 of merger and under Mac OS X (10.5.8) on a MacBook Pro. I did a right click on the CD icon in the lower right corner of the computer virtual window, then select 'connect' CD/DVD - I see while the disc turns black (which indicates it's supposed to be connected). I launch Windows Explorer in my virtual machine, but I do not see the CD/DVD drive listed anywhere! Help, please. I have the VM settings to connect to the physical CD/DVD (DVD-R MATSHITA UJ-875) drive. Thanks in advance.

  Take a look at: your CD-ROM drive or DVD drive is missing or is not recognized by Windows or other programs

• the other hard drive to the host system does not show in the virtual machine

  I tried but I couldn't find an article on how to get the other host hard disk appears in the my window of the computer of the VM guest.  I don't want a virtual disk or anything like that, just access the other hard disk of the local host without having to map a drive to it if possible.  Thank you!

  Physical disks are not supported on VMware Server 2 (at least not via GUI options).

• How to get the MAC address of the virtual machine on which vmware tool is not installed

  Hello

  In our project, we communicate to vCenter/ESX and details of virtual machines using the VI - Java 4.0.0 SDK APIs

  I use PropertyCollector for details.

  But in the following cases

  1. a virtual machine is poweredOff.

  2 VMware tool is not installed on the virtual machine.

  I am not able to get the mac using the PropertyColector address.

  To get the macaddress property I use after crossing spec:

  rootFolder (folder)-> childEntity (data center)-> hostFolder (Folder)-> childEntity (ComputerResource)

  -> host (Hostsystem)-> vm-> guest (GuestInfo)-> net (GuestNicInfo)-> macaddress (in Virtualmachine)

  I know the vSphere client uses the VI SDK to perform all operations, and I am able to see the macAddress of VirtualMachine in cases using vSphere client.

  Is any body please help me get the macaddress of VM in the two cases.

  Thank you

  Deepak

  Take a look at the dashboard feature of the virtual machine and specifically "VirtualEthernetCard": http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.vm.device.VirtualEthernetCard.html

  When you assign a new vNIC to each virtual machine, a unique MAC address generated is given by default. If you still want to map the actual interface of the guestOS, then you would take a look at guestInfo as you may have noticed IF you have the VMware Tools. Although the default is whence the MAC address

  =========================================================================

  William Lam

  VMware vExpert 2009

  Scripts for VMware ESX/ESXi and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

  Twitter: @lamw

  repository scripts vGhetto

  Introduction to the vMA (tips/tricks)

  Getting started with vSphere SDK for Perl

  VMware Code Central - Scripts/code samples for developers and administrators

  150 VMware developer

  If you find this information useful, please give points to "correct" or "useful".

• How to make a virtual computer to connect to a CD player with an ISO mounted when you start the virtual machine?

  I am the creation of virtual machines using PowerCLI 5.5 on vSphere 5.0; and while the virtual machine is turned off, I am able to mount an ISO on a CD player and change the boot order to boot from the CD-ROM (for another post).  I have the flag startConnected set to true, but am not having much luck getting the virtual machine to connect to the CDDrive

  $cdObj = $Vm | New-CDDrive - IsoPath $isoPathName - StartConnected: $true

  If ($cdObj - no $null)
  {
  #Power off VM if it is on
  $VmState = $Vm.PowerState
  
  If ($VmState - eq "Receptor")
  {
  $Vm | Stop-Vm-confirm: $false - ea 0
  }

  $BootHardDiskName = 'disk 1 '.
  $VmView = get - VM $VmName - Server $serverObj.Name | Get-View
  $HardDiskDeviceKey = ($VmView.Config.Hardware.Device |) Where-Object {$_.} DeviceInfo.Label - eq $BootHardDiskName}). Key

  $BootableHardDisk = new-Object - TypeName VMware.Vim.VirtualMachineBootOptionsBootableDiskDevice - property @{'DeviceKey' = $HardDiskDeviceKey}
  $BootableCDRom = new-Object-Type VMware.Vim.VirtualMachineBootOptionsBootableCdromDevice
  
  #Set for CDRom boot order
  $BootIso = new-Object VMware.Vim .VirtualMachineConfigSpec - property @ {}
  "BootOptions' = New-Object VMware.Vim.VirtualMachineBootOptions - property @ {}
  BootOrder = $BootableCDRom
  }
  }
  
  #Set VM from the start settings at the start of the first CD and forces the display to update (sometimes delayed)
  $VmView.ReconfigVM_Task ($BootIso) | out-null
  $VmView.UpdateViewData ("Config.BootOptions.BootOrder")
  
  #Power on VM
  $Vm | Start-VM-confirm: $false - ea - global 0EV: vmOpsError | out-null

  When I start the VM, it does start the ISO.

  If I go to vCenter, the CD is pointing to the ISO file, but the 'Connected' to change settings option is not checked;  I can restart the VM of vCenter and then the VM restarts the ISO, but not in the script.

  I even put code to add a lead time of 5 to 10 seconds; I restart the virtual machine twice in the script and I can't CD to connect to start the virtual computer.

  Appreciate any suggestions.

  Maureen

  Have you tried to do a

  Game-CDDrive - CD $cdObj - connected - confirm: $false

  immediately after the start-VM?

• Create the virtual machine by using the file PowerCLI and csv

  I know there is a lot of info out there on this and I think I have a working script prety good.  Much was borrowed from this thread, http://communities.vmware.com/thread/315193 many thanks to LucD.

  My code is as follows:

  # Deploy virtual machines from CSV file
  # Much borrowed from http://communities.VMware.com/thread/315193?start=15 & tstart = 0

  
  # CSV import file
  Import-Csv "C:\guests.csv" - UseCulture | %{
  # Gets the customization information to configure the static NETWORK card and assign the static IP address
  Get-OSCustomizationSpec $_. Customization | Get-OSCustomizationNicMapping | `
  Game-OSCustomizationNicMapping - UseStaticIP - IpAddress IpMode $_. ""IP address""
  -Subnet mask $_. Subnet - DefaultGateway $_. Gateway - Dns $_. DNS
  $vm = New-VM-Name $_. "" Server name "-model $_. Model-host $_. ' "The ESX host" '
  -Datastore $_. Data store - OSCustomizationSpec $_. Customization"
  -Confirm: $false - RunAsync
  ## .......
  }

  He's going to cross and clone the virtual machine, and looks like he's running of the OSCustomizaitonSpec then it bombards.  It cleans bad VM.  Recent tasks shows "failed virtual machine clone that a specified parapeter was not correct." hostname ".

  The problem is that I don't mean to set a hostname with the OSCustomixationSpec, I try only to IP address info.

  I'm runningn PowerCLI 5.0.1 build 581491

  My ESXi host is 5.0.0 build 914586

  My vCenter Server is Ver 5.0.0 build 623373

  I opened a new thread, because the age of the old thread.  Not sure if this is the best way to do things.

  A very simple and intuitive brake system :-)

  ## Deploy VMs from CSV File
  ## Much borrowed from http://communities.vmware.com/thread/315193?start=15&tstart=0  
  
  $maxJobs = 3 $currentJobs = 0
  ## Imports CSV file
  Import-Csv "C:\temp\TestDeploy1" -UseCulture | %{
  ## Gets Customization info to set NIC to Static and assign static IP address
      Get-OSCustomizationSpec $_.Customization | Get-OSCustomizationNicMapping | ` ## Sets the Static IP info
      Set-OSCustomizationNicMapping -IpMode UseStaticIP -IpAddress $_."IP Address" `        -SubnetMask $_.Subnet -DefaultGateway $_.Gateway -Dns $_.DNS## Sets the name of the VMs OS
      $cust = Get-OSCustomizationSpec -Name Test    Set-OSCustomizationSpec -OSCustomizationSpec $cust -NamingScheme Fixed -NamingPrefix $_.VMName## Creates the New VM from the template
      $vm=New-VM -Name $_."Server Name" -Template $_.Template -Host $_."Esx Host" `        -Datastore $_.Datastore -OSCustomizationSpec $_.Customization `        -Confirm:$false -RunAsync
  
      $currentJobs = Get-Job -State Running | Measure-Object | Select -ExpandProperty Count    while($currentJobs -ge $maxJobs){
        sleep 30      $currentJobs = Get-Job -State Running | Measure-Object | Select -ExpandProperty Count    }
  ## .......
  }
  

  You can be more selective about the current jobs. For example, you can check if the name of the job shows that they are actually cloning jobs.

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