Try to migrate a virtual machine with storage vMotion

Similar Questions

• Migrate a virtual machine with snapshots.  Works?

  In the past, moving VMs between databases or host with snapshots was deadly.

  It still happens in ESX4?

  ESX4 does not throw the warning, as did ESX3.5.

  You can migrate a virtual machine with snapshots, you can just see a different question.  You try to make a vMotion in vCenter?

  What is the symptoms you see?

  http://KB.VMware.com/kb/1005228

• Storage test 55 certification vmotion, storage vmotion fails with "Could not lock file" on the virtual machine during storage vmotion

  In my view, that it is a known problem in ESXi 5.5 Update 2 release notes, someone knows a solution yet? This is an excerpt from the release notes:

  • Attempts to perform live storage vMotion of virtual machines with RDM disks can fail
    Storage vMotion of virtual machines with RDM disks can fail and virtual machines can be considered in turned off of the State. Attempts to turn on the virtual machine fails with the following error:
    
    Cannot lock the file
    
    Workaround: No.

  VMware support for the record said that the patch will update 3, it is known as an intermittent problem. Finally, it happened to me on the 9th attempt.

• Problem migrating a virtual machine

  Hello!

  I have a problem when I try to migrate a virtual machine to the concrete only two hosts. I have no problem in other guests in my infrastructure. When I try to start this operation I get the following error message: "cannot migrate from esx1.domain.com to esx2.domain.com: the host CPU is incompatible with the function CPU requirementes of the virtual machine; problem detected the CPUID level 0 x 80000001 register edx.

  With other virtual machines, I have no problem and I can migrate from any host to any of them.

  Hi Eric,.

  Please check this link below:

  http://KB.VMware.com/selfservice/viewContent.do?externalId=1001131&sliceId=1

  Seems to be the answer to your problems.

  Please give feedback if this solves the problem

  Concerning

  If you find this or any other answer useful please consider giving points by checking the answer useful or appropriate.

• Problem with Migration hot virtual machines Hyper-V

  Dear support

  I am facing problem in Live Migration of Virtual Machine in Windows 2012 of Hyper-V R2 cluster. Here are the details for my current setup.

  Two windows 2012 R2 Datacenter even care Server (HV01 and HV02) both in cluster

  A Virtual Machine created the Volume share of Cluster (c:\Cluster storage\...)

  A network adapter dedicated to the management of server-> 10.0.1.11 (HV01) and 10.0.1.13 (HV02)

  A network card dedicated to Hyper v Virtual Machines-> 10.0.1.12 (HV01) and 10.0.1.14 (HV02) and allow networking option is disabled.

  A network card for the heart beats-> 10.0.20.1 (HV01) and 10.0.20.2 (HV02)

  A network card dedicated for Live Migration-> 10.10.10.50 (HV01) and 10.10.10.51 (HV02) and chosen to be used only for the live migration fails on cluster network settings

  I added the Virtual Machine Cluster Failover successfully without error or warning. When I do a quick migration his works fine but when I do live migration his error giving 21502.

  Please update what's wrong with my setup

  Hello

  Post your question in the TechNet Server Forums, as your question kindly is beyond the scope of these Forums.

  http://social.technet.Microsoft.com/forums/WindowsServer/en-us/home?category=WindowsServer

  See you soon.

• Problem of migration of a virtual machine with multiple vCPUs

  When I try to migrate some of our virtual machines with vMotion, I get the following error.

  «Impossible to migrate from host a to host b: virtual machine has 4 virtual CPUs, but the host only supports 1.» 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".

  The two ESX Server are identical HP DL380 with two quad core Intel Xeon. They are both connected to the same server vCenter (2.5). They both use the same license server. And, the VM OS is set to Windows Server 2003 Enterprise (32-bit), which is responsible for 4 vCPUs (it does now after all).

  I tried moved under voltage power VM off and got the same error, so I changed the vCPU to 1 and it migrated correctly. Then, I changed it to 4 vCPUs with no problems on the new host. Only problem is, I can't stop some of the virtual machines to migrate to the new host because of the availability requirements.

  ~ Brian

  Have you tried to change the settings of your license and apply them, just in case where?  I had the weird services fails when there is a kind of latency hit the license of the ESX host server.

  -KjB

  VMware vExpert

• How to migrate a virtual machine from the server with DAS to another server

  Hi guys,.

  questions. 'More' essential Kit. VMotion is available

  I have 2 physical servers, two of them have DAS (not SAN Central). SO I want to migrate a virtual machine on server A to server B. is it possible in this situation?

  Or should I have versions of more expensive VMWare do?

  Thank you
  Dmitry

  You can use clone. I would close first to the bottom of the virtual machine, but a VM slowed would be very nice clone. You can also use the VMware conveter. VMware converter can make a hot clone, including synchronization of last-minute changes, stop the source machine and put under tension the clone.

• Migration of virtual machines to vSphere 4.1 to vSphere 6.0

  As the title eludes to, we are standing up a new physics 6.0 Server vCenter Server and need to migrate virtual machines of 4.1 6.0 guest hosts.  I'd love to take the time to create a script that does the following; However, before heading down this path, I wanted to do a ping of the group to see if someone has done something like this before or have pointers to scripts that perform some of these actions already.  Some background and concept:

  • Running 4.1.
  • A new physical Center of vCenter 6.0 will be deployed side-by-side with 4.1.
  • The existing configuration of vSphere HA allows for 1-2 guests down without impact to the virtual machines.
  • The two environment and will be Cisco N1KV, SAN access shared for the same data storages.
  • A new vCenter will be lifted.
  • A single host is identified and VMs evacuated to the remaining hosts.
  • This host will be in maintenance mode, removed from the cluster and close.
  • A clean install of ESXi 6 will be done and set up spec.
  • N1KV will be deployed.

  To digress on the details at the moment... Now markets PowerCLI desired.  This idea is ad hoc and on the fly, so as I write this.

  • identify all the virtual machines associated with a specific data store - will need to work with the local client to schedule downtime for virtual machines
  • Stop the virtual machine
  • Remove the VM of the vCenter 4.1 inventory
  • to connect to vCenter 6.0
  • Add the virtual machine to the vCenter 6.0 inventory (and once we have passed the first host in the new cluster, automatically place the virtual machine by using the DRS)
  • Reconfigure the vmnic with the new Cisco 1000V dvs (will be the same name on both sides, but has a different ID)
  • pull in the keys and the values to a CSV and advancedsetting set to harden
  • Turn on the virtual machine
  • Perhaps a test of ping for the NETWORK card to check connectivity

  The order in which the steps are performed can be switched around, as long as the desired end result is the same: migration effectively virtual machines between two disparate solutions with single medium sharing as a data store.  In which I realize will always be VMFS3.  New data stores VMFS-5 is another task for another time.

  Thank you for your time, suggestions, links, etc...

  @LucD - hi.

  These steps are quite possible with PowerCLI.

  See the script after skeleton, he probably needs some adjustments to fit your environment and requirements

  $dsName = "xyz".

  $vm = get - VM - $dsName data store

  Stop-VMGuest - VM $vm - confirm: $false

  Remove-VM - $vm VM - confirm: $false

  Disconnect-VIServer-Server vc41 - confirm: $false

  $vc6 = Connect-VIServer-Server vc6

  $newVM = $vm | New-VM - DiskPath $_. ExtensionData.Config.Files.VmPathName - confirm: $false

  # Suppose a CSV file with

  # Key, value

  # key1, value1

  # key2, value2

  $advSettings = import-Csv - UseCulture advSettings.csv

  {foreach ($obj in $newVM)

  $advSettings | %{

  Get-AdvancedSetting - $obj entity - name $_. Key |

  Game-AdvancedSetting - value of $_. Value - confirm: $false

  }

  }

  Start-VM - $newVM VM - confirm: $false

  $newVM |

  Select Name,

  @{N = "Available"; E = {Test-Connection - ComputerName $_.} Guest.HostName - County 1 - Quiet}}

• What HA refusing to try to start a virtual machine?

  I'm trying just to clear on how this process works. If HA is enabled, there is a failure of the host, and he's trying to restart the virtual machines on one or several other hosts, when the host will refuse to restart (failover) a virtual machine? Assume that there is no reservation other than the default 37 MHz CPU and some booking fees calculated generals for RAM (these are the default values, right?). A host would continue to attempt to restart the virtual machines as long as there are at least 37 Mhz and a few hundred MB of RAM available for the moment he is trying to restart? And if so, there are algorithms maintains the host master to decide where to start these VMs? I just think that she should try to startups VM alternately between the available hosts and wait a little bit to make sure that there are still some available resources before you start the following, or something like that.

  Also, if there is fragmentation of resources (for example, 8% of availability on each of the 15 hosts), but HA needs to start a virtual machine that requires 15% of host resources (I realize that there is a reserve in order to decide this question of the requirement, even), would automatically make migration of VMS to other hosts (if the DRS is also enabled) or he'd just sorry cannot start this virtual machine, even if the group as a whole has space for him.  [in this case, must not make large reserves because without a reservation, the virtual machine would start upward and like CPU or memory has increased its use would cause some DRS force other virtual machines out of the host, and perhaps that would work.]

  vSphere 5.1 (vCenter and ESXi)

  The master knows where virtual machines are running and try to balance where virtual machines are started. Reservations and overhead costs are the only things taken into account from a point of view of its use (not the actual resources consumed on a host) because HA does what VMs restarted (and if they have reserves prompting these resources, they need to have to start).

  If the DRS is turned on and available, HA will work with DRS to move workloads so that the largest VMs can begin. If you have virtual machines more the thing to think about is what admission control policy you use. It may be wise to use the location function if all your virtual machines are large and close to the same size, or dedicated host of failover so you won't have to deal with shuffling DRS of workloads. Everything depends on your environment and your needs.

  Does that answer your questions?

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

• Average throughput of the network to a virtual machine with PowerCLI

  I would get average network throughput for a virtual machine with PowerCLI including all e-cards, the virtual machine has for the last week (not including NFS or storage of traffic-related).

  How best should add this report:

  Get - vm myvm | Select name, numcpu

  Thank you!

  Try like this

  Get-VM | Select Name, @{N="Avg Network Throughput MBPs";E={    [math]::Round((Get-Stat -Entity $_ -Start (Get-Date).AddDays(-7) -Stat "net.throughput.usage.average" |    where {$_.Instance -eq ""} |    Measure-Object -Property Value -Average | Select -ExpandProperty Average)/1KB,2)}}
  

  The script takes the aggregate value for all NICs for (the one where the Instance is an empty string).

  Then we take the average and converts the Kbps, Mbps.

• vMotion is not migrate running virtual machines

  It is a new installation of 2 host VSA.  I can only migrate computers when they are turned off.  When I try to migrate a virtual computer running, I get this error:

  Migrate virtual machine: a general system error occurred: vMotion migration failed because the ESX hosts were not able to connect to the network for vMotion.  Check network vMotion and physical network configuration settings.

  See the error of the stack for more details on the cause of this problem.

  Time: 14:47:04 09/11/2012

  Target: Test 1

  vCenter Server: MW-VCENTER-01. DerseInc.com error stack migration vMotion failed because the ESX hosts were not able to connect to the network for vMotion. Check network vMotion and physical network configuration settings.

  vMotion migration [173015045:1352494025051601] could not create a connection with the remote host

  < 10.80.0.4 >: ESX host the failed to connect on the network for VMotion Migration [173015045:1352494025051601] unable to connect to the remote host < 10.80.0.4 > < 10.80.0.5 > host: Timeout the vMotion failed because the destination host has not received the data from the source on the vMotion network host. Please check your network vMotion and physical network onfiguration settings and make sure they are correct.

  I have 2 VLANS on my extreme switch.  I can not vmkping by the hosts for the vMotion IPs.  What VLAN the vMotion IPs should be in?  Front-end or Back-End?  Here's my intellectual property structure:

  MW-VSPHERE-01 (VSA-1)	10.80.0.1 front End VLAN
  MW-VSPHERE-02 (VSA-0)	10.80.0.2 front End VLAN

  Default gateway	10.80.0.62
  vMotion on host MW-VSPHERE-01	10.80.0.4 front End VLAN
  vMotion on host MW-VSPHERE-02	10.80.0.5 front End VLAN

  VSA Cluster	10.80.0.8 front End VLAN
  VSA Cluster service	10.80.0.9 front End VLAN
  Mgmt IP for VSA - 1	10.80.0.10 front End VLAN
  IP for VSA - 1 data store	10.80.0.11 front End VLAN
  Primary IP address for VSA - 1	192.168.0.1 back-End VLAN
  vSphere functionality IP for MW-VSPHERE-01	10.80.0.4 front End VLAN
  Mgmt IP for VSA - 0	10.80.0.12 front End VLAN
  IP for VSA - 0 data store	10.80.0.13 front End VLAN
  Primary IP address for VSA - 0	192.168.0.2 back-End VLAN
  vSphere functionality IP for MW-VSPHERE-02	10.80.0.5 front End VLAN

  What is different when migrating a computer running and an engine out of VM migration?

  I've attached screenshots of the network for guests and the VSA Cluster configs.  What other information can I provide for troubleshooting?

  Thank you very much for your help!

  Tzuriel

  If ESXi hosts are still able to communicate with each other via a network that is enabled for management, the host is not partitioned.  Do you have other vmk interfaces enabled for management traffic?  If so, the two hosts would still be able to communicate with each other and would not be considered an event of host isolation.

  Take a look at the excellent deep dive HA post of Duncan.

  http://www.yellow-bricks.com/VMware-high-availability-deepdiv/#HA-50isolated

• Migrate a virtual machine Fisical VCenter

  Buenas,

  Hello.

  I need to migrate a Vcenter 4.1 running in a virtual machine (with the default installation) to a physical machine.

  I know the process is like this:

  • Stop the Vmware services
  • Open SQL management studio and make a backup a Vmware DB.

  My doubts are:

  Should I install separately located in the Vcenter ISO Sql create a DSN pointing to this SQL instance, create DB, restore it from the backup and installing vcenter, choose this DSN and "keep existing DB" or similar.

  or

  What can I install Vcenter in default mode (then then finish etc. ), automatically install SQL Server, DB, and the DSN; and restore this DB form the backup (in other words, crushing the fresh new DB created automatically)
  

  In the first option, I'm afraid because according to this file official http://www.vmware.com/pdf/vsphere4/r40/vsp_compatibility_matrix.pdf , vmware provides that if you use SQl express (as the default installation), you will have a 5host and 50 VM limit, but I am runnig 6 guests right now without any problem! Any comment on this?

  Another problem is to create the DSN. In data sources, I see that sql server and client installed nativle, but I get a timeout of the connection when I try to set up the system DSN. I have the firewall turned off, etc., but it's like there is a missing configuration... Do I have to install the native client anyway?

  On the second option, I do not know if restoring the backup would be an adequate procedure...

  PS: care of the machine: Win 2008 R1 x 64, Vcenter 4.1.

  Thx a lot.

  Yes it is possible.

• Create the virtual machine with the type of controller SCSI LSI logic SAS with PowerCLi

  Hey guys,.

  IM the difficulty to create a virtual machine with the type of controller SCSI to "LSI Logic SAS". The cmdlet New - VM im struggling to find where to create the type of controller?

  If you create a virtual machine without specifying a disk it will create a 4 GB SCSI type thick (0:0) hard drive 1 with 0 Parrall default BusLogic SCSI controller.

  What im wanting to do is to create a disk hard which is thin Prov. and create SCSI LSI logic SAS controller is set to.

  New-VM -name VMSTORE23 -$vmhost $esxhost MemoryMB- 4096 NumCpu- 2 -NetworkName "Vlan 6 Machine Virtual Network" | Get-NetworkAdapter | Set-NetworkAdapter -Type Vmxnet3 -MacAddress '00:50:56:00:00:21' -confirm:$false

  I have recived of aid by some LucD who helped direct the value of the network card in the New - VM cmdlet as follows. But I'm not able to add a hose for hard disk also like:

  | Get-hard drive | Together-hard drive - Datastore $datastore - slim StorageFormat

  And I have no idea how change the type of SCSI conroller or create it with the correct configuration?

  Any help would be great,

  Thanks in advance

  Eddie

  Greetings, steddyeddie-

  You should be able to use Set - hard drive and SCSI controller Set cmdlets to set the storage format of your hard drive and the SCSI controller type, respectively.  You were close to on the part of game - hard drive .  Try something like:

  ## get the VM object $vmVMSTORE23 = Get-VM VMSTORE23 ## set the harddisk storageformat to thin$vmVMSTORE23 | Get-HardDisk | Set-HardDisk -StorageFormat Thin ## set the SCSI controller type$vmVMSTORE23 | Get-ScsiController | Set-ScsiController -Type VirtualLsiLogicSAS
  

  It could pack in to your existing order to keep it as a good word, but for readability.

  Enjoy

• Virtual machines with oscillating clusters RDM

  People,

  We have two clusters at two knots with all nodes running ESX3.5 U1. Clusters have different CPU types that prevent from VMotion between clusters. All nodes are attached CF and share storage on an EMC CLARiiON CX3-80. Currently VMFS data warehouses, which are for most of the OS disks, are shared by all clusters, but the RDM (data readers) are presented specifically to one or other of the clusters. We are planning a major reorganization of our infrastructure which means Exchange effectively clusters for the majority of our virtual machines. Is there a more effective way of migration that detach the RDM, cold, migrate virtual machines and adding the back ROW on the other side?

  As you can tell my experience of internals VMware is currently quite limited, but I learn - as sometimes the hard way!

  Kind regards

  Paul Esson

  Hi Paul:

  Everyone here has some excellent suggestions. However, cold migrate a virtual machine that has the RDM will actually convert or clone the content of the ROW in a virtual disk. The original content of the RDM will be left intact, and the only way to avoid the conversion with a cold-migrate is to remove from the configuration of your virtual machine first ROW (as you mentioned). With the help of Storage Vmotion will only move the pointer of the RDM files and actually does nothing with the RDM themselves. You'd still have to place them in your storage array to another cluster.

  See the following article for a bit more detail:

  http://KB.VMware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1005241&sliceId=1&docTypeID=DT_KB_1_1&dialogID=42936094&StateID=0%200%2041484096

  -Dave