Feed for content matching tag 'storage_vmotion'

Thin Provisioning not working for storage vmotion

rsaha — Mon, 23 Nov 2009 07:37:33 GMT

I am working in a storage migration project of VMs.In the environment we have VCS ver 4.0 and ESX 3.5 servers.We need to move all the VMs from symmetric to clarion storage.So i did the storage vmotion(GUI) with thin provisioning as a option to move the VMs during pilot phase.After the migration completed,the VM disk till showing Thick format instead of thin.

Also i have moved the VM from one datastore to another datastore in clarion(same storage box,but different lun) using storage vmotion with same option and its working fine.The VM disk showing Thin.

Can anybody help me why thin provisioning is not working when moving to different storage (symmetric to clarion) box using storage vmotion?

VMware ESX 4 with VMware vCenter on VMware Workstation 7

docstibr — Sat, 21 Nov 2009 16:50:57 GMT

Documentation about installation and testing of VMware ESX 4, VMware vCenter Server in VMware Workstation 7.

http://www.docstibr.net/docs/virtualizacao/vmware-vsphere-4

vMotion CPU compatibility issue

chris k — Fri, 13 Nov 2009 17:12:02 GMT

I've read through some of the discussions around CPU compatibility, but I think I have an odd situation. Sorry if this has been covered already.

I have 7 ESX servers (IBM x3550, Xeon E5345), all identical builds. For some VM's (not all) I get CPU compatibility errors when trying to do vMotion. The really silly thing is when I do this with Storage vMotion as the host (and CPU) stays exactly the same.

I've masked the NX bit from the VM's, I've enabled Enhance vMotion compatibility, and still get the error, but only with some VM's. For example, I have 3 identical 64bit Ubuntu machines, 1 of them migrates fine, the other 2 don't. I have 2 Windows 2003 - 32 bit domain controllers, one of them migrates, the other doesn't. It doesn't seem to be limited to any specific host either. The exact error is always the same.

"Host CPU is incompatible with the virtual machine's requirements at CPUID level 0x1 register 'ecx'.
Host bits: 0000:0000:0000:0000:0010:0010:0000:0001
Required: 1000:0000:0000:000x:xxx0:0x1x:xxx0:x001
Mismatch detected for these features:

General incompatibilities; refer to KB article 1993 for possible solutions"

I've read through the KB article, and read through the forums, but they appear to refer to different architectures, which I haven't got. I don't really want to modify the mask bits as ultimately there should be no problem in using Storage vMotion to migrate to itself!

Thanks in advance!

Storage vmotion best practices

Ravi1987 — Thu, 12 Nov 2009 23:32:03 GMT

hi we currently using esx 3.5 with 30 TB of Cx4 storage with 60 LUNs on all esx server. now are preparing to buy new 50 TB storage and will migrate all the virtual machine to new storage with new version of esx server also.vsphere .problem is that for storage vmotion from 3.5 to 4.0 we need to shutdown all the virtual machine then after we can do the storage vmotion.can any body tell me how can i do hot storage vmotion from esx 3.5 to 4.0 with zero downtime.

Does storage vmotion writes data across wire?

Funtoosh — Fri, 23 Oct 2009 14:47:09 GMT

Say if you are doing svmotion on same filer on the aggr/vol or different aggr/vol. When we kick this ,does it go and write via network ? or does it copy from one aggr/vol to different aggr/vol on the filer ?

Because its movement of data on a single filer

Storage vMotion - Remnant Files

aerodevil — Wed, 07 Oct 2009 15:25:23 GMT

I have been performing some Storage vMotions using SVMotion vCenter plugin as we migrate to our new SAN. I noticed that there is still the VM directory remaining on the old LUN/SAN with files remaining. It doesn't appear at first glance to be anything unique that wasn't copied over to the new storage but wanted to know if anyone could enlighten me more as to why these files would be left behind and if there is any reason why i couldn't simply disregard them.

Files left behind

vmxf
vmsd
nvram
vmx
vmware.log
vmware-x.log

Any compelling reason that anyone can think of why I would need to keep these files?

ESX 3.5 + VC 2.5 vmotion unable to access file

var — Thu, 20 Dec 2007 09:26:06 GMT

Hi,

I have installed the new Version of ESX 3.5 on 2 Servers with their own local storage and the VC 2.5.
Now I want to test the feature vmotion, and get the following error:

unable to migrate from esx1 to esx2: Unable to access the virtual machine configuration: unable to acces file. storage1 .....vswp and also the same failure with the vmdk files

See the filesyst-rw------- 1 root root 268435456 Dec 20 22:42 test_windows2008-c3133b37.vswp
-rw------- 1 root root 21474836480 Dec 20 23:04 test_windows2008-flat.vmdk
-rw------- 1 root root 8684 Dec 20 21:57 test_windows2008.nvram
-rw------- 1 root root 409 Dec 20 21:59 test_windows2008.vmdk
-rw------- 1 root root 0 Dec 18 02:45 test_windows2008.vmsd
-rw-r--r-- 1 root root 1618 Dec 20 22:03 test_windows2008.vmx
-rw------- 1 root root 271 Dec 20 22:03 test_windows2008.vmxf
-rw-r--r-- 1 root root 85309 Dec 18 02:28 vmware-1.log
-rw-r--r-- 1 root root 49382 Dec 18 06:21 vmware-2.log
-rw-r--r-- 1 root root 49612 Dec 20 23:01 vmware.logem authorization:

Can anybody help me??

thanks a lot
andi

Message was edited by: Badsah (added tags for RCLI tag group)

ESX 3.0.2 upgrade to 3.5 & Storage VMotion

boamek — Wed, 12 Aug 2009 13:50:22 GMT

If I do an in place upgrade of an ESX 3.0.2 Host to ESX 3.5 can I use Storage vMotion immediately OR do I have to upgrade the VMware tools on each Guest before I can Storage
vMotion them to a new home?

help after failed storage vmotion

goyer — Fri, 19 Jun 2009 10:34:40 GMT

Hi,

i failed a migration with storage vmotion. The configuration file gone to the new location but the vmdk stayed to the old. I tried to repare that after searching on the web with creating end erasing snapshot, modify the vmx file....

Now i always have my vm-flat.vmdk but i would like to create a new vm using this vmdk. How can i do ?

I don't why storage vmotion failed. Certain person say that migrate storage from LUN to Local is not possible and other say that's OK.

Can you help in creating my new vm ?

Storage Issues & Storage vMotion

KGoch — Mon, 08 Jun 2009 14:06:40 GMT

Over the weekend apparently several of my VMs shut down because the datastore was critically low on space. However on Friday the datastore had about 100GB free on it. Now its down to around 25GB. My environment is back up and running, but Im not sure whats happening with the storage.

Also Im getting an error now when I try to do a Storage vMotion. I use Andrew's graphical plugin for the VIC, but when I do a Migrate Storage I recieve this error:
"A general system error occured: failed to copy VM config to VMotion dest (vim.fault.InvalidDeviceBacking)"

Any help on any or both issues would be helpful.

Thanks!

Failed VMotion from ESX2.5.4 to ESX 3.5.0 U4

campbellj — Fri, 29 May 2009 23:04:21 GMT

hi,

I have used upgrade vMotion to migrate about 25 machines from our esx 2.5 machines to our esx 3.5 machines and all have gone over smoothly except for the last one, our primary mail server

this machine failed after about 1 minute with the generic error "Failed to migrate Our Exchange from newhostname to newhostname" and a BSOD on the console.

I was presented with a warning to power the machine off and finish the migration cold, which i attempted to do by righclicking on the guest within the new host, and selecting "Complete Migration"

When I try this, i get a message after a few seconds " failed to relocate virtual machine 'Our Exchange' in 'Our datacenter'

I have sshd'd to the new server and that that the original vmdks are still on the old vmfs vm store, and the new vmstore has the following files:

-rw------- 1 root root 1627408384 May 29 22:15 DMotion-scsi0:00_AK DC Disk1-delta.vmdk
-rw------- 1 root root 291 May 29 23:43 DMotion-scsi0:00_AK DC Disk1.vmdk
-rw------- 1 root root 43008 May 29 22:13 DMotion-scsi0:01_AK DC Disk2-delta.vmdk
-rw------- 1 root root 291 May 30 07:43 DMotion-scsi0:01_AK DC Disk2.vmdk
-rw------- 1 root root 616448 May 29 22:13 DMotion-scsi0:02_AK DC-delta.vmdk
-rw------- 1 root root 280 May 30 07:43 DMotion-scsi0:02_AK DC.vmdk
-rw------- 1 root root 53248 May 29 22:13 DMotion-scsi0:03_AK DC Disk4-delta.vmdk
-rw------- 1 root root 291 May 30 07:43 DMotion-scsi0:03_AK DC Disk4.vmdk
-rw------- 1 root root 602112 May 29 22:13 DMotion-scsi0:04_JFEXCHANGE01_SG02_DB-delta.vmdk
-rw------- 1 root root 310 May 30 07:43 DMotion-scsi0:04_JFEXCHANGE01_SG02_DB.vmdk
-rw------- 1 root root 62464 May 29 22:13 DMotion-scsi0:05_JFEXCHANGE01_SG02_LOG-delta.vmdk
-rw------- 1 root root 311 May 30 07:43 DMotion-scsi0:05_JFEXCHANGE01_SG02_LOG.vmdk
-rw------- 1 root root 0 May 29 22:10 JF Exchange.vmsd
-rwxr-xr-x 1 root root 4003 May 30 00:00 JF Exchange.vmx
-rw------- 1 root root 271 May 30 00:00 JF Exchange.vmxf
-rw------- 1 root root 8684 May 30 00:00 nvram
-rw-r--r-- 1 root root 29213 May 29 22:10 vmware-0.log
-rw-r--r-- 1 root root 38057 May 29 22:10 vmware-1.log
-rw-r--r-- 1 root root 30548 May 29 22:10 vmware-2.log
-rw-r--r-- 1 root root 24574 May 29 22:10 vmware-3.log
-rw-r--r-- 1 root root 88737 May 29 22:15 vmware-4.log
-rw-r--r-- 1 root root 45904 May 30 00:00 vmware.log

I have read a number of posts such as

http://communities.vmware.com/message/999890

and tried the suggestions regarding creating and removing snapshots without success.

we are waiting for the renewal of our maintenance contract to go through, so calling vmware support is not an option at the moment.

Meet the Engineer Series: VMware vStorage VMFS and Volume Grow

Badsah — Thu, 21 May 2009 23:00:45 GMT

Real people, real faces, discussing VMware vSphere topics...

In this video, a VMware Engineer will discuss VMware vStorage VMFS and Volume Grow:

{youtube}http://www.youtube.com/watch?v=FKDHvADNW48{youtube}

Meet the Engineer Series: Enhanced Storage VMotion

Badsah — Thu, 21 May 2009 22:00:46 GMT

Real people, real faces, discussing VMware vSphere topics...

In this video, a VMware Engineer will discuss Enhanced Storage VMotion which is now available on VMware vSphere:

{youtube}http://www.youtube.com/watch?v=AuuPX9lk540{youtube}

Storage vmotion terminated halfway through in VC.

Runner1979 — Tue, 07 Oct 2008 19:24:20 GMT

I was storage vmotioning several servers when one "timed out" in virtual center. The name of the VM is "equitrac". What it shows now is the original server as ... "equitrac (1)" and another as "equitrac (orphaned)" with the (1) vm running, and the orphaned one offline. If I open the vmware host directly in my client, I do not see the
orphaned server listed there. Is there any way to resume this vmotion? There are two folders, one on each connected drive, with the same Server name. It seems like most everything came over except the logs, swap, and config file. I am probably just going to shutdown the client, unregister it, move the files manually, and reconnect/restart it. Has anyone else seen this yet?

One has

ls -lh
total 2.1G
-rw------- 1 root root 2.0G Oct 7 14:59 equitrac-19d0981c.vswp
-rw------- 1 root root 8.5K Oct 6 15:01 equitrac.nvram
-rw------- 1 root root 0 Oct 6 13:50 equitrac.vmsd
-rwxr-xr-x 1 root root 2.9K Oct 6 20:48 equitrac.vmx
-rw------- 1 root root 263 Oct 6 20:48 equitrac.vmxf
-rw-r--r-- 1 root root 39K Oct 6 13:50 vmware-197.log
-rw-r--r-- 1 root root 31K Oct 6 13:50 vmware-198.log
-rw-r--r-- 1 root root 32K Oct 6 13:50 vmware-199.log
-rw-r--r-- 1 root root 41K Oct 6 13:50 vmware-200.log
-rw-r--r-- 1 root root 39K Oct 6 13:50 vmware-201.log
-rw-r--r-- 1 root root 33K Oct 6 13:50 vmware-202.log
-rw-r--r-- 1 root root 49K Oct 6 20:48 vmware.log

The other has

ls -lh
total 53G
-rw------- 1 root root 8.4G Oct 7 2008 DMotion-scsi0:00_equitrac-delta.vmdk
-rw------- 1 root root 320 Oct 6 15:02 DMotion-scsi0:00_equitrac.vmdk
-rw------- 1 root root 9.1G Oct 7 15:09 DMotion-scsi0:01_equitrac_1-delta.vmdk
-rw------- 1 root root 324 Oct 6 15:04 DMotion-scsi0:01_equitrac_1.vmdk
-rw------- 1 root root 15G Oct 6 14:57 equitrac_1-flat.vmdk
-rw------- 1 root root 342 Sep 29 10:34 equitrac_1.vmdk
-rw------- 1 root root 20G Oct 6 15:01 equitrac-flat.vmdk
-rw------- 1 root root 340 Sep 29 10:34 equitrac.vmdk

"Migrate Storage" greyed out on some vms

khenry567 — Wed, 15 Apr 2009 16:25:53 GMT

Hey guys,

Need some help as I can't seem to find anything concrete out about this problem. Probably because it is so simple to fix. Anyway, I have 8 vms out of about 27 vms that the "migrate storage" in the drop down box is greyed out. There seems to be no commonality between the 8 where "migrate storage" is greyed out, and nothing I can see different from the other 19 where "migrate storage" is not greyed out. If I clik on the cluster or on each of the hosts in that cluster, "migrate storage" is not greyed out. Anyone have an idea as to what might be going on here?