Restart host ESXi 4.0 with vCenter 4.0 as a virtual machine

Similar Questions

• VCenter Server installed as a virtual machine within a ESXi servers it manages?

  Hi all.  I'm new in the world of VSphere... still in my evaluation period.

  I have only a single ESXi server running at the moment but plans to add a second later for high availability, vmotion, increase general capacity, etc.  They are / will be ESXi running on the internal storage and the virtual machines running on a shared SAN.

  Today, I installed VCenter Server 4 on a server at bottom of range/Office that I was carrying around running XP Pro x 64.

  As I was installing I read the guide installation and to my surprise, it seems to recommend that I have installed VCenter Server 4 as a virtual machine on my ESXi host.

  Now maybe I just spent too much time setting up my without new Lefthand requiring a 'witness' during the failover of one SAN to another... but I was under the impression that VCenter Server is not designed simply to host configuration, but is also designed to act as a 'witness' or to take account of quorum whenever a failure scenario occurred on one of my ESXi hosts.  I also noticed the VCenter Server features of a port "heartbeat", which I suppose one would use for the ESXi server heartbeat, but perhaps it is used for "connected mode" with other VCenter servers (I was intending to use only one since it is a small scale installation) I also felt that it would be useful enough to restore a damaged or shot ESXi host.

  So my question is, if my ESXi host dies and it is where I have VCenter Server installed, then high availability will be unable to work?  I guess there are going to be other issues with me unable to access VCenter Server while I have an ESXi host shot, too, as a greater difficulty to get the ESXi up?

  Maybe I'm wrong understand the purpose of the VCenter server... maybe it's not something that's necessary for HA, recovery, etc. and acts only as a configuration tool until something is wrong?  Or maybe I misunderstood the installation guide and they recommend only installing VCenter Server on an ESX box... they don't want this ESX box to be part of the group that manages the server?

  Finally, if indeed they recommend I install this on a ESXi host manages... would I ideally be install this for local storage on the server (where I installed ESXi) or on the SAN (where all my other virtual machines are installed)... or is it just personal preference?

  Thank you!!

  When you add hosts an active hemagglutinin vCenter cluster HA agent is installed on it.  This agent is what is actually the HA.  While necessary to add new hosts in a cluster and configure some specific parameters of vCenter vCenter's agents HA are self-sufficient and can handle HA failover so vCenter is offline.

  You must install the vCenter VM on SAN storage, so that he can use the vMotion, sVmotion, DRS, HA, functions etc. that require a SAN.

  -MattG

  If you find this information useful, please give points to "correct" or "useful".

• How to change the memory allocated for VCenter server, which is a virtual machine

  I'm trying reclassification of 3.5 to Vsphere 4.1 and I improved VCenter first, making it a virtual machine.  However, when I created the server I did not allocate enough memory for it and I'm getting errors.  How can I allocate more memory for the virtual machine while it is stopped?  I can not allocate more memory, except if it is closed, but with it being the VCenter server if I stopped him so that I can access with the Vi client.  Is there a service console command?  I searched for a few hours and found nothing.

  Thank you!!

  Discover what the vCenter ON WHAT VM ESX host is marked (e), connect directly to the ESX host and find the vCenter VM and make the change.

• vCenter 4.0 - cannot move virtual machines to records

  I test ESX 4.0 and vCenter. vCenter is installed on a virtual machine. I created folders for Clients and servers, but can't move the VM vCenter to the folded of servers or to create virtual machines in the new folders.

  Switch your main computers view virtual and models, and then click the virtual computers tab and drag and drop the virtual machine in question in the folder you want to move to.

• Problems access to vm/vsphere vcenter client after you restart host ESXi 5.5

  Hello ya'll,

  Looking at you all tips. I had a problem with a virtual machine that hung and could not turn it off. After several failed attempts to turn off the virtual machine via the cli of esxi, I decided to reboot the individual host (Server Blade Dell - 16 guests). Well, without realizing it, the server vcenter VM was this host and I have not put it off or move to another host. We have turned on but not sure if that moved to another host when I rebooted the host of vmotion.

  The host came back to the top of normal, but now I can not access the VM from the vsphere or RDP client vcenter. We did not allow web client so not sure if I can access this way, even if it wasn't initially setup.

  How can I get access to vcenter and the other 20 VM I created? Do I have to make changes via the CLI esxi?

  Any guidance would be appreciated!

  If vSphere HA is enabled in your cluster, then the VM vCenter was lit in one of the other guests. I suspect that services not started correctly after that triggered a HA under tension. Suggest that you locate the vCenter VM by logging in to each host using the root account and once found, the vCenter VM console and check services.

• How to move a virtual machine to another host ESXi running when HA vCenter is not operational... !

  Hey

  We have a few guests of ESXi running the 5.0.0 original version and some running the latest 5.1 U1 or whatever and the last vCenter to do this too.

  the vCenter server is one of the hosts running 5.0.0 and these do not allow HA either active correctly. The problem is a known bug, and you switch to maintenance mode and do funky stuff on the cli to make it work. However, I just want to spend all my virtual machines off the old 5.0.0. hosts and on the new, as the 'old' will be dismantled. I can do all virtual machines by just when close them down and moving off, but I won't be able to do this in with the vm off vCenter vCenter!

  can I turn off, connect directly to the ESXi host, remove it its inventory (this option exists even on the ESXi host live?) and save it to the new 5.1.0 host U1 and fire?

  vCenter complain or fail when she returns to the top?

  they share all the same warehouses of data, so I need to move the backend.

  thoughts?

  Thank you

  Roger

  HA and vMotion (i.e. live migration) are two different things and are independent of each other, so if vMotion is configured correctly, you should be able to migrate the virtual machines (including the vCenter Server VM) to another host.

  André

• Adding a host ESXi 4.0 to vCenter 5.1 supported?

  Hi all

  I intend to improve our environment to 5.1. I was going to go 5.0 but as 5.1 is available which is the point of law. While doing research on the upgrade to 5.0, I came across a few articles indicating that we can expect a purple screen when adding an ESXi 4.0 to vCenter 5.0 host if that host 4.0 is under patch level of 4.0 Update 2

  We still have some remote hosts with some sensitive servers and no disaster-recovery procedure or the ability in place for these sites. Therefore, we abstained to patch these boxes so far. (At least until we have backups and DR in place) If the connection or the upgrade goes wrong which refers to the site would be down without the possibility of recovering virtual machines. (Only the host by site with local storage btw. no quick vMotioning anything anywhere before the interview or the other.)

  We are happy to run until next year when the material is due to an environment joint replacement anyway. For these stand-alone hosts will worm 5 to 4 for now would not win us a lot. (taking into account resources are limited, it is autonomous and running a standard lic) My only concern is the issue of "Purple screen" which was mentioned can expect a vc5 instance when adding ESXi 4.0 U2 or below box. 0.

  Is this problem still the case when you add an ESXi 4.0 U2 or less than a 5.1 vCenter server or this problem has been fixed in 5.1?

  You are right, there is a problem with vCenter Server 5.0 (without Update 1) and ESX (i) 4.0 Update 2. However, with vCenter Server 5.0 Update 1 and/or vCenter Server 5.1 it is now supported. Please take a look at http://partnerweb.vmware.com/comp_guide2/sim/interop_matrix.php to see the supported configurations.

  André

• Cannot Connect to Host ESXi 4.1 with browser or Client VI

  Hi, I have a strange problem which has persisted since I first installed ESXi 4.1 on a server. First my setup:

  • ESXi Installable on a HP DL380 G6 server, 32 GB of RAM, 4xEmbedded NETWORK ports, Port NIC, 2 iSCSI x QLogic QLE4060C HBAs 1xDual adapter

  • HBAs configured for Jumbo and static IP frames but except that all the settings are default

  We have installed ESXi 4.1 with only the built-in port #1 connected to the switch. Everything went well and we were allocated the only active NIC (vmnic0) as the management interface. Once installation is complete, we were able to connect to the management interface using a browser and the VI client.

  We then connected NETWORK card and remaining HBA ports to the switch without loss of connectivity to the management interface. During our next restart we could no longer connect directly to the host using a browser or the VI client but could still ping the IP.

  We tried to restart the management agents, but it did not help.

  Here are the different startup scenarios, we tested and the results:

  Scenario #1 - Boot with built-in NICs, DP adapter cards, network and HBAs connected to the switch.

  • Can we ping the IP of host of Mgmt? = Yes

  Can • we consult to the IP host of Mgmt or connect using the VI Client? = NO

  Even if we try to unplug the adapter DP and HBA ports after starting we still cannot connect to the management using the Explorer or the VI Client interface. A reboot is required, and the script #2 or #3 must be followed.

  Scenario #2 - start with only the embedded and DP adapter NIC connected to the switch.

  • Can we ping the IP of host of Mgmt? = Yes

  Can • we consult to the IP host of Mgmt or connect using the VI Client? = NO

  If disconnect us the two ports of adapter DP we can then connect to the host via the browser or the VI client without having to restart. We can reconnect them and we continue to have access to the host, and everything is fine.

  Scenario n ° 3 -Boot with only the NIC integrated, including the Mgmt NIC connected to the switch.

  • Can we ping the IP of host of Mgmt? = Yes

  Can • we consult to the IP host of Mgmt or connect using the VI Client? = Yes

  Then we connected the DP adapter and the adapter port HBAS to the switch and all the connectivity was very good. This scenario is our solution for now.

  Other information

  The QLE6xxx ESXi module takes about 5 minutes to load during startup, when the HBAs are connected to the switch, but it loads successfully. Not sure if this is normal or not.

  Thank you in advance for your help!

  Paul

  This looks like a very unusual network for me configuration.

  Could you post a screenshot of virtual network configuration and add a few comments on the different configuration of the vSwitches and uplink connected.

  If I understand correctly that you have at least 3 vSwitches (management, virtual machines, and iSCSI), however, from what you wrote so far I do not completely understand how implement you.

  André

• ESXi 4.0 really slows with only 4 minimum of running virtual machines

  My ESXi server is a processor Quad Core (2.4 GHz) server with 8 GB or RAM

  It works very well with the three virtual machines it seems, but when adding the fourth they all slow to a crawl.

  There are several tabs that don't make sense, for example:

  I watch tab resource allocation, it shows capacity 8149 MHz CPU - so I guess he uses 1.5 GHz which is a lot, but I can live with that, but says memory total RAM capacity is 1572 MB - if the system uses more than 6 GB of RAM? What is the problem?

  I look at the physical memory - Configuration tab and it says memory: Total 8114 MB, MB system 5288, physical Machines virtual 2826 MB

  Currently, there are three machine running - an I limited to 512 MB (currently using 52MO and the host uses 127 MB), another is limited to 1.5 GB, but it uses only 600 MB (host uses 1014 MB) and has no limit, but has only 1 GB allocated (it is currently using 80 MB and the host uses 913 MB)

  BTW Machines 1 and 2 above are limited to 500 MHz and 3 Machine is limited to 1200 MHz.

  Until the devil is the problem? Where are all my resources going? My VM are not using almost nothing. If I try to start a virtual machine, which is limited to 512 MB and 500 MHz of 4th, all useless machines. Connections network starts to fall sharply, RDP cannot connect, the console window is only good for trying to stop him. As soon as one of them is off, it works well again.

  I tried tons of parameters of affecting all unlimited and obliging all for unreasonably low speed and memory and nothing works.

  Where should I start to understand this?  I have dealt with this for over 6 months and I am very frustrated.

  You can put the latest bios on this system as well as check that the default bios are defined (with the exception of things vt

• Problem with ESXi 4.0 with Allocation of disk on a virtual computer

  Hello Experts

  Physical server:

  HP DL 380 2 proc Intel Xeon 4 GB RAM

  6 x 146 GB HDD (with RAID5) = > total available capacity 650 GB

  Problem:

  I am creating a VM with OS = DEBIAN6

  When I allocate 300 GB HARD drive for the virtual machine, it gives me just 256GB.

  I don't understand the reason.

  I read that this could be linked to the BLOCK SIZE.

  What is your opinion? If so, how can I change the block size?

  Thanks in advance

  Options of your choice after.

  Block size of 1 MB = Max VMDK 256 GB

  2MB block size = Max VMDK 512 GB

  4MB block size = Max VMDK 1024 GB

  Block size of 8MB = Max VMDK 2048 GB

  First calculation of disk space when set up 2 MB to 512 GB.

• Free version of ESXi can support for configuration of start and stop virtual machines via vSphere Client?

  I have read and found some documents on ESXi.

  According to the documents, I know that ESXi free version does not support some advanced virtual machine configurations and does not support write to ESXi host permission. But when I download ESXi from vmware.com, I can't find the free version. He will always be a trial of the licensed version edition because I can always do the configuration of start and stop virtual machines via vSphere Client installation. I can also run scripts (lamw) pl in vMA to stop the ESXi host (authorization to write ok?)

  Then I confused. How can I get the really free version of ESXi? Or will the free version after 60 days of evaluation?

  Start/stop above configuration is in vSphere Client via 'Configuration'-> "start/stop VM"-> "Properties"... «-> "Allow the virtual computers start and stop automatically with the system" actions setting and stop virtual machines can be configured to "comments"turn off computer"or"Suspend".» Can any body tell me if it's supported by ESXi free edition?

  Is the free version of vSphere Client too? Because when I use the vSphere Client, he told me that I have 60 days of evaluation. This confused me again. I think that vSphere Client is always free, am I right?

  Any suggestion or advice is much appreciated.  ^_

  Micky

  Configuration of start and stop virtual machines is available with the free version and licensed, with the free version you would be configured everything via vSphere Client, where as with a licensed version, you can optionally use scripts to configure it and also issue restarts/stops using scripts.

  Second, shutdownHostViaSOAPAPICall.pl for the version licensed and free of ESX (i), this script will work in both free and licensed because it uses direct SOAP calls emulating the vSphere Client communication. Take a look at the documentation for details, but this of course is not supported by VMware.

  =========================================================================

  William Lam

  VMware vExpert 2009

  Scripts for VMware ESX/ESXi and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

  Twitter: @lamw

  repository scripts vGhetto

  Introduction to the vMA (tips/tricks)

  Getting started with vSphere SDK for Perl

  VMware Code Central - Scripts/code samples for developers and administrators

  VMware developer community

  If you find this information useful, please give points to "correct" or "useful".

• VCenter are running in a virtual machine: now, it is a good idea?

  This article:

  http://searchvirtualdatacentre.TechTarget.co.UK/news/column/0, 294698, sid203_gci1512874, 00.html?

  says it is recommended.  He will then raise a problem with the Update Manager.  I do not use the Update Manager, so I'm interested to know if anyone can confirm and tell me what document of VMware's vCenter recommended to run on the virtual machine as a 'best practice '.

  I'm more ready to go this way than before, but I'm always cautious when I consider the complexity of chess.

  If host ESX running vCenter server completely failed, then, Yes, vCenter will re-start on another host.

  But there are opportunities far more problems than that.  What happens if the data store becomes unavailable?  What happens if the ESX host is suspended from a problem that connects the CPU?

  Be extremely careful, I can not far because virutalizing vCenter means basically that it have more complexity in the layers beneath him and therefore more opportunities for the failure of the recovery are introduced.

  I know vCenter running on material means that layer may still fail, but we're watching all of our physical servers that run our ESX host.

  Put a hypervisor on them prevents us from having to deal with the problems of disk/network/fiber channel / local memory.

  the search for VMware, I found a doc who wrote in 2009, don't know if it's always the last Gospel.  I will raise a support call to ask VMware, but I wanted to first see if you can give me a link to the answer.

  http://communities.VMware.com/docs/doc-11197

  Interesting that this doc on the VMware site binds effectively to that on the techtarget site.  That's fine, but I want VMware reference that mentions the techtarget article.

  Congratulations in advance for your time and your help.

  Points of generous and enthusiastic congratulations to all those who could be the key here.

  see you soon,

  Kevin

  The design of vSphere course has this as the best exercise of the profession - the reasons have already been identified. From VMware, it's a virtual vCenter server has high levels of resilience and redundancy, you can not necessarily with a physical server or having to pay a significant premium to achieve, that is to say MS clustering.

  It also gives you the possibility of increasing resources - CPU and ram discs if you need to. With the help of a physical server you reaches the limits of physical capacity.

  If it works as aVM you use common sense - if you have one or two hosts then risks may outway the benefits, that is a failure of a single host leaves Infrastructure depend on the remaining host. If you have 10 hosts and a resilient storage solution then why not.

  There is quite a response to the host to vcenter environment - person has never shot to run on a physical server and can say the same for virtual.

• How to configure HA when vCenter is running as a virtual machine in one of the army?

  To install HA with VMware EVC, guests must be first maintenance mode before moving into the HA cluster. The problem is, vCenter runs as a virtual machine inside one of these hosts. If I stop vCenter downwards so that the host in maintenance mode, how do I setup with VMware EVC HA without using vCenter?

  If you do not feature vMotion, right down your vCenter VM and you unsubscribe eg. ESX1 can record for example. ESX2 then turn back on. ESX1 maintenance mode and then back ESX1 on your cluster file and exit once done maintenance mode. It goes the same for ESX2 and the rest of the ESX host.

• Returns the name of the FQDN for a vcenter based on a given virtual machine

  Slowly, I am working on a set of workflow that will integrate a powershell module, I created.

  For my first stream of work, I'm trying to find all the information I need when a user runs a workflow on a VM orchestrator.

  I understood the cluster so far, but I can't identify the right script object that will give me the full domain name of a host corresponding to this virtual machine vcenter.

  Being new vCO does not help much, either.

  I thought that it would be part of VcManagedEntity, but for some reason, this page translates into a big ol' 404!

  https://www.VMware.com/support/Orchestrator/doc/vco_vsphere51_api/HTML/VcManagedEntity.html#configStatus

  I thought that maybe it would be part of vm.runtime.parent.parent but my script results in errors.

  Any help would be greatly appreciated!

  Thank you.

  I think that now you are a the right way, the full name of the vCenter server will be localhost, so the answer of vm.sdkConnection.setting.sdkConnection is localhost.

  Maybe this will help you:

  var sdkConnection = vm.sdkConnection;
  var optionManager = sdkConnection.optionManager;
  
  var vCenterInstanceName = optionManager.queryOptions( "VirtualCenter.InstanceName" ).shift().value;
  var vCenterFqdn = optionManager.queryOptions( "VirtualCenter.FQDN" ).shift().value;
  
  System.log( "vCenter Instance Name: " + vCenterInstanceName );
  System.log( "vCenter FQDN: " + vCenterFqdn );
  

  Where I think that the name of your instance will show localhost.

  But the FULL domain name should be the thing you are looking.

  See you soon

• Help with VM monitoring parameter at the virtual machine level

  Hi, I'm new to powershell and got the script (from http://damiankarlson.com/2011/01/13/managing-vmware-has-vm-monitoring-powercli/ thanks Damian Karlson) that will allow me to set the "VM Monitoring" setting for each virtual computer in a cluster to 'Disabled' below State. This is necessary to allow a 'monitoring VM and application' at the highest level and keep only selective VMs allowed for surveillance. When I run this script, it is applied VM1. When I try to do this for another virtual machine with a virtual machine name change (VM2), it get error "specified parameter was not correct" in the tasks of vCenter. Not sure whats wrong, any help is appreciated.

  
  $srv = Connect-VIServer vcenter01
  $vm = get-VM-name VM1
  $spec = new-Object VMware.Vim.ClusterConfigSpecEx
  $spec.dasVmConfigSpec = new-Object VMware.Vim.ClusterDasVmConfigSpec [] (1)
  $spec.dasVmConfigSpec [0] = new-Object VMware.Vim.ClusterDasVmConfigSpec
  $spec.dasVmConfigSpec [0] .operation = "Edit."
  $spec.dasVmConfigSpec [0] = new-Object VMware.Vim.ClusterDasVmConfigInfo .info
  $spec.dasVmConfigSpec [0].info.key = new-Object VMware.Vim.ManagedObjectReference
  $spec.dasVmConfigSpec [0].info.key.type = 'VirtualMachine '.
  $spec.dasVmConfigSpec [0].info.key.value = $vm. ExtensionData.MoRef.Value
  $spec.dasVmConfigSpec [0].info.dasSettings = new-Object VMware.Vim.ClusterDasVmSettings
  $spec.dasVmConfigSpec [0].info.dasSettings.vmToolsMonitoringSettings = new-Object VMware.Vim.ClusterVmToolsMonitoringSettings
  $spec.dasVmConfigSpec [0].info.dasSettings.vmToolsMonitoringSettings.enabled = $false
  $spec.dasVmConfigSpec [0].info.dasSettings.vmToolsMonitoringSettings.vmMonitoring = "vmMonitoringDisabled".
  $spec.dasVmConfigSpec [0].info.dasSettings.vmToolsMonitoringSettings.clusterSettings = $false
  _this $ = get-view-Id $vm. VMHost.Parent.Id

  Hello, vSphereUser7-

  I've seen your follow-up to your thread on this topic at http://communities.vmware.com/message/1859219#1859219.  Between your answer and your question you mention in this thread, I came to realize what seems to be the problem for you.  I have re-written a code in the other thread, based on that blog DKarlson on and commented on why you may receive this error in the vSphere client.  See this thread for more info on what is happening here.

  And let us know if it was the question that you run in to.