New answers tagged vmware-vsphere
It's technically possible and will work, but definitely not ethical or legal.
No there is no vMotion in VMware Workstation. There is the notion of Upload where you can connect to your vCenter server from Workstation itself and upload your local VMs to vCenter. But that does not happen as a vMotion operation (i.e.: while the VM is running).
Steps 1 and 2 are great, for step 3 simply add the existing hosts to the new VCSA, yes you'll have to drag all the VMs/Templates/Networks/Datastores to any new folder hierarchy as that'll be lost but the VMs will just migrate over just fine - no need for any VM or host power-offs. Then all you need to do is vMotion the VMs from the old hosts to the new ones ...
When I deploy a CentOS 7 VM from a template, the customizations successfully apply and then the VM hangs and must be powered off. When I power it back up, the network config and hostname revert to the previous settings. What am I missing?
I don't believe there is a direct way to do this in the vCenter clients (I've searched for it previously as well). To confirm alarm actions are triggering, you can manually adjust an alarm's thresholds so that it triggers the 'failed' state, and then change the threshold back to its original value afterwards. We commonly use the Datastore usage on disk ...
FYI redhat-release is symlinked to centos-release. If you edit redhat-release, you are actually modifying centos-release. To follow the solution's recommendation in not modifying distro specific version files, do this instead: rm -f /etc/redhat-release && touch /etc/redhat-release && echo ‘Red Hat Enterprise Linux Server release 7.0 ...
To answer your questions: RAID5 is not advisable, period. A single bad read during a rebuild kills your entire array. This is more of an issue with HDDs than SSDs, but it's still a consideration. RAID10 is generally the best option, but RAID6 (dual-parity) can also do quite well. You're comparing Jaguars to Hyundais, there. SSDs have better random access, ...
This is most likely because a different node, with a different fingerprint, previously existed at that IP address (10.40.6.23). Confirm that this is the case, but generally, when you're SSHing to a new host for the first time you can expect to see this kind of warning - when you should be worried is when it's an existing host whose key has unexpectedly ...
First off, please read the VMware docs available here and here. Your question clearly shows that you didn't read it at all. vCenter is how you manage ESXi Servers professionally in a multi-ESXi-host environment, it provides lots of features like host profiles, VM and Host Management via a web client, powerful scripting API, inventory etc. On to your ...
Yes free logon to VMware and request a key. Free does not do vmotion ( move system from one to other host.) and such like enterprise features. vSphere client is only way on the free version, there is vCenter that is a appliance or windows based, bot not free.
Memory allocation in VMware is a complex topic. It really can't be distilled to a "allocate X amount" per machine. You really have to look at utilization inside the VMs as well as from the host, cluster and and resource pool levels. Can you give a specific situation or scenario that you need help with? What is the layout of your cluster?
Top 50 recent answers are included