Install vCenter as a VM on ESXi 4.1?

Sepiraph

Has anyone tried to install vCenter server as a virtual machine running on a ESXi?

This is for a lab environment and instead of adding a 3rd computer to the mix, wanted to just run vCenter as a VM if possible.

Chris:/*

Yes there is no problem with it.

scott28tt

Not only is it possible, it is the most common way that vCenter Server is deployed nowadays.

azjag

I hear they are coming out with a vCenter appliance with the release of vSphere 5. Looking forward to that, just not to deploying a new dbms. The Appliance works on DB2 or Oracle and we are a SQL shop =(

ChooseLife

Virtual vCenter is fully supported as of version 4 and works quite well.

P.S. Tip: Remember to set the vCenter VM to auto-start with the host.

roghan

Sepiraph wrote: »

Has anyone tried to install vCenter server as a virtual machine running on a ESXi?

This is for a lab environment and instead of adding a 3rd computer to the mix, wanted to just run vCenter as a VM if possible.

Read this article on VMware Community:

VMware Communities: vCenter Server Design: Physical vs Virtual

It describes pro and cons of vCenter Server like physical solution and virtual.

jibbajabba

ChooseLife wrote: »

P.S. Tip: Remember to set the vCenter VM to auto-start with the host.

Which only really works on a standalone host. Once you have a DRS enabled cluster you basically have to "hunt" for the VM, logging into each host in order to find that VM so you can start it manually.

You could argue you create vApps instead, which can be used to auto start VMs, but for vApps you need the vCenter which is down at that point - so it's somewhat a catch 22 ...

Or you "pin" the vcenter to a specific host ...

QHalo

jibbajabba wrote: »

Which only really works on a standalone host. Once you have a DRS enabled cluster you basically have to "hunt" for the VM, logging into each host in order to find that VM so you can start it manually.

You could argue you create vApps instead, which can be used to auto start VMs, but for vApps you need the vCenter which is down at that point - so it's somewhat a catch 22 ...

Or you "pin" the vcenter to a specific host ...

This is a key point. I found this out studying for my VCP when I enabled DRS and HA and my vCenter moved when I would power down my lab at night. If I had vCenter on node 1, and I powered it down it would move vCenter to node 2. When I would start my lab I kept wondering why I had to go to the host to start vCenter but eventually figured it out.

ColbyG

As others posted, this works fine. I recently created a VM for vCenter in my home lab.

jibbajabba

QHalo wrote: »

This is a key point. I found this out studying for my VCP when I enabled DRS and HA and my vCenter moved when I would power down my lab at night. If I had vCenter on node 1, and I powered it down it would move vCenter to node 2. When I would start my lab I kept wondering why I had to go to the host to start vCenter but eventually figured it out.

That is what DRS Groups are made for basically. Well for one anyway.

Cluster Settings > VMware DRS > DRS Group Manager

Create a Virtual Machine Group, call it i.e. Virtual Center and add the VM to it click 'ok'

Then add a host DRS group. Here add the host(s) you want the VM running on at all times.

Then under rules you can define that the VM group will always stick to the Host group



Although having said that - DRS requires vCenter in the first place lol - well I haven't tried / played with it myself yet so I leave that to you :P

scott28tt

If my fully-automated DRS cluster hosted a vCenter VM, I'd just set the VMs automation level to "disabled" - I'll decide whether to vMotion it or not thanks. In a HA situation I'd be happy that HA failed the VM over, could easily find out where it ended up once it's restarted, and worry about fixing my dead host...