Posts tagged vmware
When having to edit VMWare virtual machine settings, you need to find the proper .vmx file.
Connect to the hypervisor and do:
This will output the xml contents, each VM is named
<vmname>.xml, so you will get the full path to each vm config file.
Since I always mix these up:
thin = disk is created, but not completely allocated. overprovisioning is possible. thick = disk is created with actual size
VMWare has furter
eager provisioned thick drives:
lazy zeroed thick: disk is created with actual size, nothing else is done at create time. But every newly used block is zeroed first: Thus a little bit slower than eagerly provisioning during runtime. eager zeroed thick: disk is created AND zeroed during creating, thus wiped completely then.
If you use the free version of the current ESXi (5.5), all hosted VM's have to be lower than version 10, if you plan on keeping it free.
See here in the vmware blog:
For troubleshooting purposes we have added read only support to the vSphere C# Client for compatibility levels 5.1, 5.5 and 6 aka virtual hardware 9, 10 and 11 features. This allows you to edit settings available in compatibility level 5 aka vHW8 and have access to view vHW9+ settings. The use case for this would be to connect directly to a host to add CPU or RAM to your powered off vCenter Server.
Up to now there for the free version there was no restriction on the amount of physical cores of the hypervisor, limit was the maximum of 8 cores per VM. The other restriction was, there were no Backups possible, for that you needed minimum the Essentials edition. Also there existed a limit of 1024 connections per hypervisor IIRC, but I have no source to back that up currently.
Now VM's which are of version 10 or higher, cannot be administered with the free vSphere client. Just with the vSphere web client, for which you have to have a vCenter set up and running.
See here for pricing.
This is some from a while ago, I just found the pen and paper notes. Beware, there may be errors in here. There may be errors in here.
The settings go in here:
Look for an entry like:
# x here is just a number, increment to the highest one not present yet /firewall/services/sshServer/allowedip[000x]/ipstr='10.0.0.10'
Save and exit.
The next part was not neccessarily in this order:
services.sh start, to restart all daemons (since I didn't know which one was exactly needed) and restart the firewall:
esxcli network firewall unload esxcli network firewall load esxcli network firewall refresh
To restart the cim provider (service for hardware monitoring), when it dies on the German edition, do:
- connect to the hypervisor
- mark hypervisor in left frame
- 'konfiguration' tab
- box 'software', choose 'sicherheitsprofil'
- 'eigenschaften' of 'sicherheitsprofil/dienste'
- choose 'cim-server', the last option when you scroll down
- button 'optionen...'
- button 'neu starten'
- or first 'beenden' then 'starten', if 'neu starten' does not want to work.
Easy, you see? There's a reason I prefer proxmox to this 'enterprise software'...
When trying to create a new datastore on a HDD which was partitioned previously, and you have chosen
VMFS-5 the creating will fail with some strange partitioning error.
Solution is to create the datastore with
VMFS-3 file format, which will work.
Afterwards delete the datastore, and try recreating it with
VMFS-5, which will work then.
Being stuck in the VSphere console while working on a host? (You cannot exit to your host OS.)
and be happy.
View posts from 2017-03, 2017-02, 2017-01, 2016-12, 2016-11, 2016-10, 2016-09, 2016-08, 2016-07, 2016-06, 2016-05, 2016-04, 2016-03, 2016-02, 2016-01, 2015-12, 2015-11, 2015-10, 2015-09, 2015-08, 2015-07, 2015-06, 2015-05, 2015-04, 2015-03, 2015-02, 2015-01, 2014-12, 2014-11, 2014-10, 2014-09, 2014-08, 2014-07, 2014-06, 2014-05, 2014-04, 2014-03, 2014-01, 2013-12, 2013-11, 2013-10