Storage vMotion issue License - license of moving between ESX Hosts 4.1?

I have a question about Storage vMotion with ESX 4.1 license.

One of my environments ESX 3.5 existing consists of 10 ESX 3.5 hosts - 8 ESX 3.5 servers Standard and 2 ESX 3.5 Enterprise servers.  I use a centralized license server (I think that's the correct term).

I found that I can "move" the vMotion (and vMotion) Storage capacity of two of my 10 servers that only two of them are enabled for vMotion, both.  I do this by topic under VI Client-> select the host ESX-> Configuration-> network-> properties-> VMkernel-> Edit-> toggle the box "VMotion" activated-> OK.   I guess that by doing this, that I'm actually just spend my licenses 'ESX Enterprise' between the hosts.

Be able to run Storage vMotion on one or two guests at a time is a lot for a few times a year I need to reconfigure my back-end storage.

Two Questions:

1. this use is technically legal in a perspective of VMware licenses?

2. now, I'm looking to upgrade to ESX 4.1 and wonder if I'll be able to keep doing this?  I have read that ESX 4.x got rid of the centralized server license model, so not sure if I could 'move' licenses around like that... In fact since vMotion is now included in Standard Edition, I guess I could 'pull out' through a license only one ESX Enterprise server in order to obtain the license of storage vMotion.

I let my support/subscription lapse for as long it is cheaper to purchase new licenses rather than paying for support costs with retroactive effect on my existing licenses.   The price difference between Standard and Enterprise is large (3 times the cost) that I don't think I can swing is business licenses for all of my guests past the bean counters, where the reason for this post.

Reflections and comments?

Each host has a license key number. You can apply a new license key to a host, and it is immediately activated. I guess you would be technically violate licensing for seconds as a license number was recorded at two hosts. There is a place in the vSphere client to "assign a new license key to this host. When a license key has been assigned, it remains as a choice, then you can simply choose the functionality licensed one and below the other.

Tags: VMware

Similar Questions

  • V2V between ESX hosts

    I just want to ask, I have to do cold V2V a VM on Wan via fibre-optic line and intend to use the 4 converter to resize the original hard during the process.

    ESX HAS | VM A (source) | VMFS on local disk-

    migrate - & gt; ESX B | (destination). VMFS on shared storage

    My question is, do I need an additional license for Converter 4 making the migration from different ESX hosts without vCenter?

    VMware newbie...

    Zen Systems Sdn Bhd

    www.no-x.org

    No, you don't not need another license for Convertter as long as you use an instance of mono converter - also be warned converter on the WAN will take some time.

    If you find this or any other answer useful please consider awarding points marking the answer correct or useful

  • Disable vmotion for 1 virtual machine in an ESX host

    Hello

    We have an ESX environment that is configured with vMotion.

    As a result, I've seen VMs from one ESX to another very frequently.

    Among these virtual machines, I have a very critical virtual machine, I want to move to any other host ESX.

    Y at - it an option that I can use to disable VMotion only for this particular virtual machine of mine (in order to keep constant on the ESX on which it is right now) and allow the other virtual machines to continue.

    Appreciate your help.

    Thanks in advance

    I guess that your VMS migrate between ESX servers because configuration automated DRS ESX cluster level. You can replace it for a specific virtual machine. Cluster of right click Select-> "Settings"-> click on options of the Virtual Machine under VMware DRS,. On the right, make sure 'Enable the levels of automation individuak virtual machine' is checked. You can see VMs list below. Select the virtual machine that you want to replace and change the level of automation for people with reduced mobility

  • SMV flicking between ESX hosts and generate HA errors

    Dear all

    This may seem obvious, but I'd really appreciate a confirmation of my thoughts.

    We have an ESX3.5 U3 environment with 16 hosts managed by virtual Center. Each physical host has two network adapters for each of the three vSwitches (Service Console, vmkernel and VM network). The two network adapters in each vswitch are powered by two different Cisco 6509 s for redundancy purposes. Last week, for a separate ground, one of Ciscoes was closed, which means that none of the three vswitches had network redundancy in place.

    Yesterday, it was noted that VMs were flicking between hosts - i.e. a VM would be visible on ESX06 for 5 seconds, then ESX11 to 5, then 06 once again, etc. The event log shows that HA is seeking to exchange the virtual machine per physical host x physical host there several times. It is always possible to RDP to the virtual machines, but there is no possibility to manage other aspects of the virtual machine by VC (i.e. vmotion), as I suppose, VC never knows exactly where it should be!

    My first feeling is that HA look at the Console of Service of all physical hosts vswitches and determine that there is a lack of redundancy and therefore seeks to move virtual machines from one host to another, then get stuck in a loop. However, I think that HA has been invoked only (which is actually to move a virtual machine from one host to another) If a particular host actually exit blinked eye and fell completely network - not only if she lost a redundancy...

    I would appreciate your opinion. And by the way, I'm not sure when the networking team will be able to get the second Cisco and running again, so want to rule out the possibility that this problem can be caused by something else.

    Thank you very much in advance for your help.

    have you seen this KB?

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

  • Storage vMotion with advanced vsphere license

    I have the vSphere advanced license that doesn't include a Storage vMotion.

    This does mean that I won't be able to do manually storage vmotion with this license, or is what is not included in the new vSphere GUI?

    You will not be able to make Storage VMotion.

    But many people say Storage VMotion, even when cold migration is performed. Thus, you will not be able to move VMS on another store data seamlessly, without power off VM.

    ---

    VMware vExpert 2009

    http://blog.vadmin.ru

  • License of moving from the old computer to new computer

    Hello

    How can I do this? Just uninstall the old and download it again?

    If so, I need to some license information-, I guess. But when I go to my account page and look at my products it is empty. That is my products are not registered. But obviously, I produced (creative cloud, PS) otherwise I would not be able to access the page of accounts in the first place...

    Concerning

    Jonas

    Adobe products must be installed by using installation files - they cannot be moved between machines.  Your license allows installation enabled on both machines so there is no need to do anything on the original, except if you wish to cancel the ability to work with her.

    Download/install the desktop application, connect and install applications subscription.

    https://helpx.Adobe.com/creative-cloud/help/download-install-app.html

    Creative cloud to desktop

    https://helpx.Adobe.com/creative-cloud/help/creative-cloud-desktop.html

    Sign out, sign in | Creative office cloud app

    http://helpx.Adobe.com/creative-cloud/KB/sign-in-out-creative-cloud-desktop-app.html

    Install, update, or uninstall applications

    http://helpx.Adobe.com/creative-cloud/help/install-apps.html

  • Cannot Storage Vmotion between EMC Celerra NFS and NFS VNX

    Recently we have improved our infrastructure VMware 3.5 to 5.0. Managed to migrate all virtual machines to the Esxi5.0 without any problems. More recently, we bought new storage EMC VNX 5300, set up and configured the NFS storage for the early. All the warehouses of new data related to blades and all storage pools, old and new can be found under vCenter.

    Problem we have is that we can not Storage vMotion virtual machines of the old Celerra NFS for new NFS VNX stores. It comes back with the error "cannot access file VM VNX {datastore} filename '. We got a similar message appears when you try to create a new virtual machine or import an OVF on VNX new data warehouses.

    We have the license of the company, with Dell M600 blades with EMC storage as mentioned above.

    Pointers would be appreciated

    Kem

    Thanks for your contributions, but I solved it. A bit of a 'schoolboy error', but although I had added to the VMKernel IP in the host root and read-write in the NFS export properties, I also need to add the IP address of the hosts/blades. Storage vMotion successfully in new stores VNX. THX Kem

  • Microsoft has stopped issuing licenses for windows 2008R2 Enterprise edition?

    Please specify if Microsoft has stopped issuing licenses for windows 2008 R2 64-bit Enterprise edition.

    Kind regards

    Aravind.

    This issue is beyond the scope of this site and must be placed on Technet or MSDN

    http://social.msdn.Microsoft.com/forums/en-us/home

  • vMotion (without shared storage) between two hosts with different vSwitches standard s VM

    I can VM vMotion (without shared storage) between two hosts with different vSwitches standard? The vSwitches on these two hosts have different names and number of NIC, but have the same name of portgroup.


    Thank you.

    Yes, you can in a Storage VMotion to one Esxi to another with no shared storage...

    It is important the portgroup bears the same name... This is the reference for the VM...

  • Storage vmotion, between data warehouses when the block size is different

    Hi all

    I would like to know, is it possible to do a vmotion of storage between two data warehouses, when they have different block sizes. The case is as a former vmfs data store 3 which has been upgraded direct to vmfs5 there, but since it has been updated it maintains its own block size. While the newly created vmfs datastore 5 a block size of 1 MB.

    Thus, storage Vmotion will work in this case? It will fail OR will be with degraded performance?

    Finally, storage vmotion is possible even if you do not have a cluster DRS for storage?

    Thank you

    Yes you can!

    Check some info on the effects of block size: http://www.yellow-bricks.com/2011/02/18/blocksize-impact/

  • Storage vMotion-Direct between ESXi hosts

    Hi all

    It is my first time on the boards, I hope it's the right way to go on this subject.

    I have problems with Storage vMotion, it's not a set up us would use normally, rather than by necessity with the current scenario.

    We have a desktop which has 2 x 5.1 ESXi hosts. They do not have a budget for SAN with the installation of HBA, and it is only a single requirement. I have to migrate virtual machines from one to the other, but with no external storage. I wait with Storage vMotion directly from a local data store to another.

    I activated the software iSCSI on both ESXi hosts

    Created a vSwitch separated with a VMkernal on two physical hosts

    The two VMkernals are on a separate subnet * 172.16.1 and production vSwitch is 192.168.5. *.

    The NIC allocated for the 172.16.1 network. * is both connected to the same physical switch.

    I ping the VMkernal and the vmkping the VMkernal

    Scan for storage again and nothing shows up.

    I used software iSCSI before, for a long time so I'm probably rusty. Dynamic discovery is normally indicated in the SAN to pick up storage, and finds it just local storage on each host itself.

    In this scenario, I told the IP address of the ESX2 VMkernal on 172.16.1 ESX1. * since I have no external storage. I think it is, I'm wrong, but I don't know what else to do to recover local data warehouses.

    Any ideas to try would be very appreciated.

    Thank you

    Sorted by using 5.1 feature Shared-Nothing vMotion

  • Issue licenses during the upgrade to vcenter 2.5 to 5.0

    I have 4 ESX host running 3.5 update 5. I just upgraded from 2.5 to 5.0 vcenter. One of my ESX hosts still contains the old license server. I try to change it to the correct server, but I get the cannot change the license server error. I couldn't ping the server licenses from this host. I noticed that on my 4 host, that host was the only server where DNS is not configured. I set up the DSN and I can now ping on the license server, but still I can't change it. From the console, I did a service network restart hoping that would clearly be DNS.

    The customer, I go to Administration - vCenter Server Settings and the licensing option is configured correctly. Any reason why it changed on my other host 3 but not this one?

    Thank you

    You'll have to mainrain one license server until you can upgrade your ESX, ESXi 5 hosts - and don't forget not there is Noah ESX in vSphere 5 so you will have to reinstall to ESXi.

  • Storage vmotion of storage facilities to storage San in ESXi 5.0

    Hello

    I have the host couple ESXi 5.0 with license free of all is vmdk are located in storage facilities. Moving all the vm for local to the SAN storage data store, but the local data store attached failed to attend several ESX host as storage shared, is there a way that allow me to use the method of storage vmotion to migrate all the vmdk to centralize SAN without interruption?

    I have a vcenter to manage whole army but only for normal administrative task. How can I set the local data store storage shared storage and able to present multiple hosts?

    Hello

    Do you have the vSphere licenses?
    If so, you can add the vCenter ESXi hosts, present SAN storage for ESXi hosts and perform Storage vMotion (migrate the data store) local storage to SAN storage.

    You will need because the function of storage vMotion (migrate) is a feature of vCenter vCenter, this option is not available in standalone ESXi.

    See the documentation here - migration of Virtual Machines with svmotion: vSphere Documentation Center

    If you can accept interruptions of service, you can use the migration cold: vSphere Documentation Center

    Thank you

    Bayu

  • Storage vmotion to another data store on a different san

    Hello

    We have a 3.5 ESX cluster running 4 host ESX and Virtual Center. The licensing is ESX Server standard edition. We are migrating to ESXi 4.1 vSphere and a new SAN. One of the issues that we are going through is because we are only in standard edition, we have no storage vmotion to migrate the virtual machines of data stores in the old SAN for data warehouses in the new San. Other than purchasing the add-on storage vmotion, what other options can I. I thought to add a new ESX 3.5 server to the cluster and make storage vmotion from this server while it is running trial license. I would probably need only a few days to storage vmotion on about 45 VMs. Please let me know if one were to do this or any other alternatives available.

    Hello

    There is an unofficial plugin that does not require an authorization.

    More about http://www.virtualizationadmin.com/articles-tutorials/vmware-esx-and-vsphere-articles/vmotion-drs-high-availability/storage-vmotion-svmotion-vi-plugin.html

    plugin http://sourceforge.net/projects/vip-svmotion/

  • 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

Maybe you are looking for