For this to happen you have to enable a secondary network adapter that is set as Internal Network (make sure you assign both guests to the same Internal Network, default is “intnet”)
The next step is to enable DHCP server on that network by this command:
VBoxManage dhcpserver add –netname intnet –ip 10.0.0.100 –netmask 255.255.255.0 –lowerip 10.0.0.101 –upperip 10.0.0.150 –enable
This is good explanation why not to use thin provisioning especially in small business where we cannot afford any vm redundancy.
expected survival rate after one year:
Windows 2008 system installed on certified hardware: 98%
same system on thick provisioned eagerzeroed vmdk running on ESXi: 97%
same system on thin provisioned vmdk running on ESXi: 60%
same as before plus automatic backup by Veeam or similar: 50 %
I dont think those numbers are completely off but I dont have statistics to backup such a claim.
Continue reading Thin or thick provisioning?
This has to do with all sorts of backup tape drives (HP, IBM) including external ones that are not supported by VMware, but you still want to make use of them on one of your VMs.
Follow THIS article and bear in mind that you will have to restart the hypervisor once then destination VM another time.
Unfortunately it is not that easy to get a discount comparing to Microsoft or Adobe products.
All details are HERE.
This issue can happen on a new physical servers with the latest ESXi 5 and virtualized Windows Server 2012. This will more likely cause a network communication havoc.
Double check the settings and make sure that none of the VMs has vNIC of “e1000”
You have to create a new one and change it to at least “e1000E” VMXNET2 (Enhanced).
For Server 2012 it should be the latest VMXNET3 really.
This article explains the differences between virual NICs.
1. set Power-on Boot Delay to 5000ms in virtual machine settings
2. press Fn + F8 to bring Windows Safe Mode
rpm -qa | grep Virt
rpm -e VirtualBox-4.2
rpm -i VirtualBox-4.3
It looks like that after the latest VB update to 4.2.18 I am not able to install Windows Server 2012. The installation is stuck on “Getting files ready for installation”. Depending how big is the virtual disk it gets stuck on 47% or 57%.
The only solution was to place the virtual disk file on a partition with EXT3.
The other VMs I have are on EXT4 partition are in working order however the new ones fail to install.
VBoxManage modifyhd YOUR_HARD_DISK.vdi --resize SIZE_IN_MB
Make sure the VDI is not fixed size otherwise you will not be able to resize it in easy manner.
I have noticed that during initial load up Server 2012 fails with some error.
However I have resolved it by using dynamically allocated hard drive image not the fixed size one.
Just go to Settings -> System and check “Enable IO APIC” in VBox.
If your processor is 6 core and you set up 2 VMs then it will be 3 and 3, if 3 VMs then 2 and 2.
What is vMA?
vMA is a Linux-based virtual machine that is pre-installed with a command-line interface and select third-party agents needed to manage your vSphere infrastructure
One of the examples how to utilize it is to deploy APC Powerchute agent on vMA to monitor UPS.
To start any VM without display windows please hold Shift, click on desired VM and press Start.
The command is:
This will generate all logs and TAR-GZ them.
To download them from iESX please use the following commands:
ssh -l root 192.168.x.x vm-support -s > vm-support-192.168.x.x.tgz
Make sure SSH service is running, bu going to Advanced settings in VSphere and turning that service on.
The generation process can take up to even 10 minutes so be patient.
This is what HP or Dell will ask you to do if your hypervisor will start pink screening.