New answers tagged vmware-vsphere
I had a similar problem with my configuration, you might be surprised but adding an entry for each esx host inside the /etc/hosts (IP hostname hostname) file of the QNAP solved my issue. Hope this helps.
So this is a very open ended question but I'll take a shot You can virtualize your desktops before servers BUT it's actually usually easier to do the servers first - you know them better, they are usually more constant in their load and there is hopefully less complexity as far as installed software is concerned. For the sizing question - Add the RAM in ...
Can you unhook an (active) interface from a virtual switch without disrupting traffic? Yes, you can, assuming there's another uplink available to that vswitch. Can the network configuration be inconsistent across a cluster (not using HA) without causing global problems? Yes and no. You need to make sure your vmkernel interfaces are reachable. ...
I have had success using http://www.veeam.com/virtual-machine-backup-solution-free.html It's a lot faster than a datastore copy and paste in the infrastructure client.
While there shouldn't be a difference here, my benchmarks have shown a slight (but clean nonetheless) performance increase in Windows guests when using single core multi-socket emulation (e.g. 4 vCPUs are mapped as 4 sockets, single core, single thread). No visible difference in Linux guests though. Tests were done on KVM, using Windows 2003R2 and 2008R2 ...
The best generic approaches are: Export the VM as an OVF file, move to a local system, then reimport the OVF to your ESXi destination. Use vSphere and perform a host/storage migration. Leverage one of Veeam's free products to handle the ad hoc move. Solutions like rsync or scp will be rate-limited and have no knowledge of the content (e.g. sparse VMDK ...
There's no major difference here. The main purpose of the cores/socket designation is to provide options for software that may have runtime or licensing requirements based on the number of "physical" sockets or CPU cores (cough, databases...) There's no significant performance difference between multiple cores on one socket versus a combination of multiple ...
Short answer: Probably none that you would notice. Long answer: Maybe. The issue that comes to my mind first and foremost is that modern CPUs operate much faster than the main memory they use. This is the primary reason why NUMA (non-uniform memory access) was invented. CPUs on the same die (ex. two cores on the same chip) would share the same NUMA node... ...
Not considerable enough to make an impact. The adjustments are more for licensing. For example, Windows Server is licensed per processor slot, so you'd pay more to have 1 core and 4 CPUs than to have 1 CPU and 4 cores. Same goes with other products whose costs quickly rise with more processors (looking at you, Oracle).
I think over Update Manager you can only update your ESX / ESXi Servers. For Updating vCenter Server you have to download the 3GB iso and install it over this way... If your vCenter Server is an Windows Server your can unzip the iso File on the Server and start autorun.exe. Here you can use "easy-Install" which contains alle the bundles you need (vCenter ...
No. You'd need to download the .ISO package... In this case, you'd need: VMware-VIMSetup-all-5.5.0-2105955-20140901-update02.iso Since you're on the Windows platform, you'd load the .ISO and run the installer on top of your existing installation.
Don't worry about it. It's just a rounding issue... 2267MHz is usually represented as 2.27GHz From dmidecode on a similar system: Version: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz Voltage: 1.4 V External Clock: 133 MHz Max Speed: 4800 MHz Current Speed: 2267 MHz Or look at how a 2.8GHz CPU is represented...
I'd suggest just running the updates as-is. There's no harm in it. If this is a single machine, it will require downtime. Without going into this mess, think of the ESXi patches as being delivered as a full image. See: Are VMware ESXi 5 patches cumulative?
vCenter Operations Manager needs to be tuned for your environment and business hours. There are tunables you can set that impact its recommendations for VM sizing. The default thresholds are way too aggressive. But in general, I don't see anything wrong with the recommendations you've. I actually think 256MB of RAM is too small, depending on what you ...
I'm not sure if I can help you much because we're not using Dell servers. But it looks like I can at least help you with the acronym VIB: VIB stands for vSphere Installation Bundle. It's basically a software packaging format like RPM. Dell Custom ESXi distribution should contain at least one, but quite probably several, additional VIBs with drivers and ...
Install the Dell Custom ESXi distribution or just add the Dell .VIBs to an existing install. That will provide you with Manufacturer-specific hardware awareness. In your vCenter, add the requisite alerts for the "Host Hardware Health". That's all I monitor, since it's a bit of a catch-all for host health conditions.
Top 50 recent answers are included