Tag Info

Hot answers tagged

5

You cannot just unplug a server and plug it into a colo providers network, turn it on and expect it to work. You need to update all the IP Addresses, gateways and so on on those machines and expose them in the correct way. And there might be a bit more to it than just changing each machines IP details. These servers might be inter-related. i.e. they may ...


3

VMware has a hardware compatibility guide (HCL) which outlines which servers are supported by which versions of the ESXi hypervisor. My recommendation if you want to buy a used HP server is to use G6, G7, Gen8 or newer HP servers in the 300-series or higher (DL360/DL380). Anything else is going to be missing critical support or features under VMware.


2

In case the software inside your VMs relies on a CPU feature that the chosen EVC mode hides it will crash. A lot of software doesn't take some CPU features for granted and falls back to doing things themselves ("in software") instead of offloading tasks to specialized CPU instructions. So even if your software can run without certain CPU features you might ...


1

Maybe touch a marker file in the %post script? See docs at https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/s1-kickstart2-postinstallconfig.html


1

The problem encountered here was caused by python or the vcsa-deploy utility attempting to use the proxy defined in the shell environment: https_proxy=http://proxy.example.com:3128/ I ran vcsa-deploy with strace and saw that it was attempting to use that proxy. I used the unset https_proxy command to temporarily disable that proxy, repeated the ...


1

AFAIK you cannot make ESXi to wait for a VM to start before mounting the datastores. I may be wrong though. The datastores are mounted way before any VM can boot up. In general iSCSI connects right away if you do a rescan on the iSCSI sw adapter after your storage VM boots up (and rescan it works way better than NFS, where if it gets disconnected/inactive ...


1

the solution to fix this is to sync all parties (ESXi hosts, vcenter, VRM Appliance) with ntp servers. Once this done - the error is gone.



Only top voted, non community-wiki answers of a minimum length are eligible