Storage VMotion failed - LUN "Ongoing resource of use"

Similar Questions

• Storage VMotion in LUN protected with SRM

  Hello

  I don't have RS in my environment and do not know what will happen in the next version of SRM (Version 1.5), but I'm caurios to know the answer to this question.

  Now that vSphere officially supports Storage VMotion, is it supported in SRM as well? Which means that if you have two LUNS protected by SRM in a DataCenter. What happens if use you Storage VMotion LUN to one another. (Both protected)

  Move the files in your DR Site as well? No need to reproduce on the internet?

  Thank you

  Currently, if you a data store SVMotion not replicated to replicated store listed in MRS. VM pop-ups in the Protection Group - like 'not protected' as a whole new VM. You can then right-click and choose to protect...

  It is less smooth vice versa - it is as "not configured" and you need to delete manually the list of SRM...

  My free guide to SRM - covers this 179 page...

  http://stores.Lulu.com/RTFM

  Concerning

  Mike Landry

  RTFM education

  http://www.RTFM-ed.co.UK

  Author of the book of MRS: http://www.lulu.com/content/4343147

• Storage vMotion Failed - Help!

  As the title suggests, I tried in vain to run storage vmotion for VM (right click & gt; Migrate storage) of local SAS to a remote NFS share.  I was able to do very well for 12 other virtual machines, but the last of them (wouldn't you know) 600 GB big and has not said 'Operation timed out' in VC.  I know that VC said that normally, if things take too long, however all disk/copy activity has benn stopped for hours, and when I look in my two data stores I have files in BOTH places.  My VM is still in place, and I'm afraid to turn it off in case it is not.  Here are the details:

  In my old file store, local SAS (2 files):

  Vault.VMDK - 630GB

  Dmotion - scsi0:00_vault.vmdk - 70 MB

  In my new store file NFS (14 files):

  Vault.vmx, vault.vmsd, vault.nvram, vmware.log, vmware10 - 15.log, vault.vmxf, Snapshot1.vmsn - vault, vault - a99f9a04.vswp (1 GB), dmotion - scsi0:00_vault - 000001.vmdk (60 MB)

  In VC, my VM was that execution of my NFS file store (Hard Disk 1 is pointing to arch/dmotion - scsi0:00_vault - 000001.vmdk), although it seems that most of my data is always in the local filestore SAS.

  So, how can I put humpty dumpty back together again, all on the new filestore NFS without losing my VM?

  I'm trying to migrate all out it's because I need to rebuild the table to include more disks

  In case it helps, VC reported the following in the pane tasks and events:

  07-09-2009 06:30:38, could not migrate 192.168.2.254 to 192.168.2.254 vault in Noob

  08/07/2009 21:29:08, migration off-host 192.168.2.254 vault in Noob

  08/07/2009 21:28:36, keystone of the migration of 192.168.2.254 to 192.168.2.254 in Noob

  08/07/2009 21:28:35, task: move the Virtual Machine storage

  Evening,

  We had exactly the same problem when service mgmt-vmware has been restarted the ESX Server hosting the VM being SVMotioned.

  The VMware knowledge base has an article that explains a few steps to recover from this process (KB1009113) However, it is somewhat incomplete you must power off the virtual machine to complete.

  Here are the steps I followed to recover without a failure:

  We assume that you have been SVMotioning a VM de LUNA to LUNB and now the virtual machine linking Delta on LUNA with the configuration of the VM on LUNB files.

  1. log in to the Service Console of the ESX Server that has the virtual machine.

  2. to confirm that the virtual machine does not clichés, run the command:

  VMware-cmd < vm-cfg-path > hassnapshot

  The output hassnapshot() = confirms that there are no snapshots

  3. create a snapshot with:

  VMware-cmd createsnapshot < vm-cfg-path > < name > < description > < pause > < memory >

  By doing this, you get files like this on LUNB:

  Dmotion - scsiX:XX_server - 000001.vmdk

  Dmotion - scsiX:XX_server - 000001 - delta.vmdk

  4. Remove snapshots with:

  VMware-cmd < vm-cfg-path > removesnapshots

  This command commits the dmotion snapshot and the snapshot you created in step 3.

  5 VirtualCenter will always think that the virtual machine is in the SVMotion State so to set:

  «"VMware-cmd < vm-cfg-path > setconfig scsiX:X.DMotionParent»»

  Do this for each VMDK attached to this virtual machine.

  Now perform a new SVMotion to move back the VM to LUNA configuration files.

  Clean up the LUNB and remove all the files/folders created by the SVMotion failed. You can now make the SVMotion again.

  Of course while the steps above worked for me, please take this as all care, but no responsibility. The above steps were borrowed from http://communities.vmware.com/message/999890

  Kind regards

  Glen

  Post edited by: ThompsG

• Storage vMotion fails with the error below

  I'm trying to run a virtual machine's storage vMotion. It fails with the error below.

  This method is disabled by 'moref = 17705'

  #1 method - manually remove the entry from the VCDB.

  • Stop the Service of VC.
  • Connect to the SQL Instance.
  • Run the SQL for VCDB.
  • Select * from VPX_VM WHERE name LIKE '% VM_Name % '.
  • Note the ID of VM in column 1.
  • Validate the stale entry.

  Select * from VPX_DISABLED_METHODS WHERE ENTITY_MO_ID_VAL = "vm - ID".

  • Remove obsolete entries.

  delete from VPX_DISABLED_METHODS WHERE ENTITY_MO_ID_VAL = "vm - ID"

  • Start the VC service.
  • Try Storage vMotion.

  Method #2-si this does not work, save the *.vmx file once again which will fix the problem.

  Note: To do this, you will be required to server unavailability.

  • Power off the virtual computer.
  • VM unregistered inventory.
  • Navigate to the path of the data store and VMX re-register.
  • Start the virtual computer.
  • Try Storage vMotion.

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

• Cannot remove vmotion portgroup - "ongoing resource of use"

  Hi all

  I need to remove the portgroup vmware a vswitch without touching the other exchanges. The vmware portgroup is subsequently added to a new vSwitch.

  When I run the command, I get an error that the resource is in use.

  The host is:

  • ESXi 4.1 U1
  • In maintenance mode
  • Restarted
  • Does not contain virtual machines.
  • Can be removed successfully with vSphere Client
  Get-VMHost | Get-VirtualPortGroup-name "vmotion" | Delete-VirtualPortGroup-confirm: $false
  Delete-VirtualPortGroup: 2011-08-24 17:01:11 VirtualPortGroup remove the "vmotion" resource is in use.
  On line: 1 char: 76
  + Get-VMHost | Get-VirtualPortGroup-name "vmotion" | Delete-VirtualPortGroup < < < <-confirm: $false
  + CategoryInfo: NotSpecified: (:)) [remove-VirtualPortGroup], ResourceInUse)
  + FullyQualifiedErrorId: Client20_MoServiceImpl_Invoke_ViError, VMware.VimAutomation.ViCore.Cmdlets.Commands.RemoveVirtualPortGroup

  Any suggestions?

  Thank you

  / Björn

  Hello.

  Thanks for posting this question, I had also the need to complete the same task today.

  I posted my final script I found to work in ESX v4.1 Update 1.

  It is basic and annotated for the community to work with in their scripts.

  #Connect to server
  Write-Host "Connecting to server"
  Connect-VIServer -Server 192.168.1.199 -User root -Password Pa55w0rd | Out-Null
  
  Write-Host "Retrieving server details"
  
  #Retrieve the host details
  $esxhost = Get-VMHost -Name "192.168.1.199"
  
  #Set Port Group to look for (case sensitive)
  $PGName = "vmotion" 
  
  Write-Host "Looking for vmk NIC assigned to vmotion"
  #Look for the vmk NIC for vmotion
  $vmkNic = Get-VMHostNetworkAdapter -VMHost $esxhost | where {$_.PortgroupName -eq $PGName}
  Write-Host "Deleting vmk NIC assigned to vmotion"
  #Remove the vmk NIC for vmotion, once removed it becomes a normal Port Group from a VMKernel one.
  Remove-VMHostNetworkAdapter -Nic $vmkNic -Confirm:$false |Out-Null
  #Set a couple variables
  $redundantpg = "vmotion"
  
  Write-Host "Removing vmotion Port Group"
  #Retrieve the vmotion Port Group details
  $defaultvpg = Get-VirtualPortGroup -Name $redundantpg
  
  #Remove the vmotion Port Group
  Remove-VirtualPortGroup -VirtualPortGroup $defaultvpg -Confirm:$false |Out-Null
  
  Write-Host "Disconnecting from server"
  #Disconnect from the server
  Disconnect-VIServer -Server 192.168.1.199 -Confirm:$false
  

  What I've noticed, is that I had to use the switch -VirtualPortGroup instead of -name to remove VirtualPortGroup

  Kind regards

  Darren

  @dawoo

• Storage Vmotion failed now VM in limbo

  I was migrating a virtual computer by using the plugin SVmotion who got 90% then failed, and now I can not restart. I have the two stil of vmdk files in their original location, but also two dmotion * vmdk files. Nondurable urgent to return this virtual machine running would be highly appreciated.

  Hello, check these two articles, those who should be able to help solve the problem:

  http://www.van-Lieshout.com/2009/03/how-to-recover-from-failed-SVMotion/

  http://blog.core-it.com.au/?p=441

  If this post was useful/solved your problem, please mark the points of wire and price as seem you. Thank you!

• Is it possible to use Storage Vmotion with VMFS and RDM virtual tool?

  Hello!

  You can use the tool Storage Vmotion to move a server that is running both VMFS disks and RDM virtual drives inside?

  Both SAN is EMC and Vmware ESX and Virtual Center can be reached.

  Thank you!

  For storage on the SAN again the two hosts will need access to the storage. You can then you copuld cold migrate the virtual computer. First, you will need to stop the virtual machine and delete the mapping of RDM. Once the virtual machine is the new data store re-create the mapping of RDM (Bothe hosts will need to access the LUN backend).

• What vmnic Storage vMotion use?

  Hello everyone,

  I created my pile and all around nic teaming vmotion fault tolerance and so on... BUT! :

  There are things that I can't understand...

  What vmnic is used for storage vmotion? !

  I explain, when I have a virtual machine to the host and the other, no problem the correct vmnic is used, with nic teaming definition of vmotion.

  BUT, when I migrated a virtual machine from a to another data store every time, but every time vmnic 0 point?

  Any ideas?

  Thanks a lot because I really don't understand why...

  

  vSontae wrote:

  In addition to my question, I would like to say that when I linked the vmkernel on iSCSI port was on the same subnet and the same configuration of network even vlan (no VLAN sort...).

  OK, that explains my question from above, must have been validated as I wrote.

  What you need to do to be able to get through your desired interfaces iSCSI traffic is to have at least the different IP subnets. Different VLAN is also highly recommended, but not technically necessary, however a best practice for several reasons.

  So, basically, set the IP on the SAN iSCSI target some address a different IP subnet, set in place the VMkernel interfaces on the host with IP on the same subnet. Make sure that the Vmkernels is connected to one the VMNIC you want, which is not the same as your network management on VMNIC0.

  Start with that and make sure it works, then you might look at the mulitpathing / iSCSI binding.

• Prices (not storage vmotion) vmotion, DRS (Distributed Resource Scheduler) features available in ESXi cluster?

  Prices (not storage vmotion) vmotion, DRS (Distributed Resource Scheduler) features available in ESXi cluster?

  I thought that ESXi is a correct free download?

  Yes and no. ESXi Hypervisor binaries are the same for all editions (free and paid). It depends only on the license key that you have what features are available and if you can add an instance of vCenter server host.

  If you just want to test vSphere, you can sign up for a free 60-day trial (no required license key) during this period, all the features of the 'Business Plus' edition are available.

  André

• Spend RDM to VMFS using Storage vMotion

  I have a server that is running Windows server 2003 SP2 Enterprise edition.

  This server is using a SAN EVA8000 raw device mappings. We want to get rid of the device mappings gross and use instead a regular VMFS data store.

  I tried to use storage vmotion to migrate the storage of a new vmfs datastore, hoping it would pass all the data from the mapping of raw device to a new VMFS datastore.

  Completion of storage vmotion to the new data store, I still connected to the server raw device mappings.

  It is still possible to migrate data on a raw device mapping to the data without downtime and manual filecopy vmfs store?

  Is it possible to move from physical to virtual mode?

  You can turn off the virtual machine, remove the diskette RDM and readd in virtual mode.

  André

• Storage VMotion for a virtual machine with SAN LUNS attached to it. They are all going to?

  Hello

  Don't know which section of this post, so sorry if its wrong.

  We are eager to Storage VMotion of our SQL VM. These are our SAN 3040 of NetApp. In the virtual machine (windows 2003), they have also connected to the network SAN NetApp 3040 LUN.

  What I need to know is, if we tried to do the other (NetApp 3170) SAN Storage VMotion problems due to the fact that its storage not only fast vMotioning of VMs its self, but also the LUN or LUNS will remain on 3040, and the virtual machines moved to the 3170?

  Who is?

  If more info should help just shout!

  Cheers in advance...

  Rik

  RDM's Raw card device.

  As I posted earlier, you need to move data to the Raw LUN for LUN Raw new either through data copy inside the VM if you map the new LUNS brutes who him or copy.

• VMotion fails with «Host CPU is incompatible...» »

  After setting our vCenter 4 / environment laboratory of ESX 4 with two hosts ESX 4, I added two of our ESX 3.5 hosts in vCenter 4 managed environment. These 3.5 hosts had 10 Windows 2003 EE 64-bit Server identical virtual machines, running on them. I then used storage vMotion (migration) to move all ten VMs over a LUN share by the ESX 4 hosts and migrate them while they are now running on the ESX 4 hosts.  They came over the fine. Activated fine. Ran very well. vMotioned back between the two ESX 4 hosts fine.

  I then put off 5 of the 10 computers virtual and enhanced their virtual hardware version 4 to version 7. I have them fed up.

  I have also built several new virtual machines on the host ESX 4 from scratch using the same process and the same image that I used to create virtual machines hosted on ESX 3.5 hosts. So far so good.  Can I vMotion between all 5 virtual machines that are still at version 4 guests two ESX 4 and I can vMotion new computers virtual 7 built on ESX4 host, but if I try to vMotion of 5 virtual machines have been upgraded to version 7, I get the message below.

  Host CPU is incomaptible with the requirements of the virtual machine to CPUID level 0 x 1 register 'cex '.
  Bits of the host: 0000:0000:0000:0000:0010:0000:0001
  Required: 1000:0000:0000:000 x: x 10 xx10:0: xxx0:x 001
  Inconsistency detected for these features:
  * General incompatibilities; see section 1993 of possible solutions.

  I read the KB article referenced, but this is to overcome the problems with fast vMotioning between levels or different processor types. These two hosts ESX 4 (10-esx-mp and mp-esx-11) are identical DL580 G5. It's only the improved VMs that fail to migrate.

  I stop each host ESX 4, restarted in the BIOS and set the option of VT processor on 'disable', of booted up the box, let it come completely up, then again, rebooted the box of ebb in BIOS and by setting the option VT back on 'enable '. It's not helping.

  Someone else has seen this?

  If you have identical CPU, then check the configuration of virtual machine (in the .vmx file) to see if there is an old CPUID mask value and simply remove them.

  Then again turn on the virtual machine.

  See also:

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

  André

• Storage VMotion - a general error occurred: could not wait for the data.  Error bad0007.

  People,

  I searched through this forum and have not found an answer that works in many positions out there, I say to myself that I would ask him once again.

  Here's the context:

  We have 12 identical Dell M600 blades in 2 chassis with 16 GB of Ram, 2 x Xeon E5430, they are all connected to an Equallogic PS 5000XV iSCSI SAN on a separate iSCSI (vswitch1) with 2 cards network dedicated network and dedicated switch, console svc iscsi dedicated, dedicated VMkernel port for iscsi access. Net access (vswitch0) contains port groups VM for our various networks and a console port and vmkernel svc for VMotion with 2 separate NETWORK cards as well.

  We are running ESX 3.5 U3 and VCenter 2.5 U3 on Win2k3 R2

  VMotion works between all servers, Storage Vmotion works for most machines, HA works and the value 2 host failurs with no monitoring of vm, DRS is set to manual for now I have a few machines on the local stores that I complete my rebuilt LUN, there is no set of rules for DRS and VMware EVC is enabled for guests of the Intel. However, I'll just describe one machine to do svmotion below.

  Here's the problem:

  I'm trying to Svmotion via svmotion.pl - interactive, a Machine to Windows 2000 with a virtual disk and a virtual RDM. I am aware of the requirements for the RDM and required parameters for svmotion, independent is not selected for the RDM, and I also have svmotioned several machines linux and win2k3 with the same configuration without problem. In the interactive session, I choose to individually place the disks and I chose the virtual disk to only the virtual machine to be moved, essentially, as I saw it move vdisk virtual machine and then copy to the pointer of the RDM.

  The use of the processor in this machine is about 25% average. but I try to run migrations at the time the lowest. and The Host it itself shows only about 5.5 GB of the 16 GB of RAM used. so I think we're good on the RAM. the volume/datastore that I'm migrating from has 485 GB free and the volume/datastore I migration towards a 145 GB free. the VM virtual disk is only about 33 GB.

  I run the script the windows version of the RCLI svmotion. and when to begin the process, I get the following error at around 2 percent of the progress:

  "Since the server has encountered an error: a general error occurred: could not wait for the data."  Error bad0007. Invalid parameter. »

  After searching around, I found the following hotfixes to the U2 release notes

  • Migrate.PageInTimeoutResetOnProgress: Set the value to 1.

  • Migrate.PageInProgress: The value 30, if you get an error even after the setting of the Migrate.PageInTimeoutResetOnProgress variable.

  I've made these changes, and I still get the same error.

  When I dig in the newspaper, I see these entries in the journal of vmkwarning:

  (Feb 24 00:17:32 vmkernel iq-virt-c2-b6: 82:04:13:56.794 cpu4:1394) WARNING: bunch: 1397: migHeap0 already at its maximumSize bunch. Cannot extend.

  (Feb 24 00:17:32 vmkernel iq-virt-c2-b6: 82:04:13:56.794 cpu4:1394) WARNING: bunch: 1522: Heap_Align (migHeap0, 1030120338/1030120338 bytes, 4 align) failed.  calling: 0x988f61

  (Feb 24 00:17:32 vmkernel iq-virt-c2-b6: 82:04:13:56.794 cpu4:1394) WARNING: migrate: 1243: 1235452646235015: failure: out of memory (0xbad0014) @0x98da8b

  (Feb 24 00:17:32 vmkernel iq-virt-c2-b6: 82:04:13:56.794 cpu2:1395) WARNING: MigrateNet: 309: 1235452646235015: 5 - 0xa023818: sent only 4096 bytes of data in message 0: Broken pipe

  (Feb 24 00:17:32 vmkernel iq-virt-c2-b6: 82:04:13:56.794 cpu6:1396) WARNING: migrate: 1243: 1235452646235015: failed: Migration protocol error (0xbad003e) @0x98da8b

  (Feb 24 00:17:32 vmkernel iq-virt-c2-b6: 82:04:13:56.794 cpu2:1395) WARNING: migrate: 6776: 1235452646235015: could not send data for 56486: Broken pipe

  At this point, I'm stuck... What is Windows RCLI? the vcenter Server? or the service console with not enough of RAM? We have already increased all our consoles service 512 MB...

  Any help would be greatly appreciated...

  Thanks in advance.

  Alvin

  The vmkernel on out of memory error, I had that before. And vmware support recommends setting 800M Max service console memory. And I did it and have no problems after that.

  See if that helps the issue.

  Mike

• Storage vMotion with Syncrep on Equallogic San

  Hello

  We recently bought 2 San Equallogic (PS6510ES) and turned on synchronous replication between them.

  We use ESXi 5.5 and followed the best practices guide to disable TCP ack and 60 logintimeout value.

  Everything seems to work fine until we tried Storage vMotion/migration and cloning VMS on the San.

  When we did the migration of 2 volumes on the EQL SAN storage (the target volume has active syncrep), the target volume will be out-of-sync and then the storage vMotion will hang sometimes.

  The worst is when such a problem has occurred, all other volumes on the EQL constantly to respond also. All volumes will not respond until we rebooted the corresponding ESXi host (NOTE: simple shut down/power outside the host won't help.) The San EQL will only return to normal after a reboot of the ESXi host).

  If we pause / off the syncrep before Storage vMotion, the problem will not happen.

  Is this normal or not?

  In addition, whenever the problem occurred, the latency of writing the corresponding volume will be dry and we will receive alerts similar to the following:

  connection iSCSI target ' xx.xx.xx.xx:3260, iqn.2001 - 05.com.equallogic:xxxxx - test-volume ' initiator 'xx.xx.xx.xx:xxxxx, eqlinitiatorsyncrep' failed for the following reason:

  Initiator, disconnected from the target when connecting.

  Thanks in advance.

  Hi Joerg,

  What is a #SR? I opened a record of support to 24 June and still waiting for Dell to contact me.

  Ryan