- #REDHAT LINUX VM INSTALL#
- #REDHAT LINUX VM UPDATE#
- #REDHAT LINUX VM DOWNLOAD#
- #REDHAT LINUX VM WINDOWS#
10/29/17 – added the two links – static IP and DNS help for those of us weak in Linux.2/3/18 – added the yum line for mlocate.I have left the old parts of this article in the article in case people still need them for older vSphere and older Centos but will remove it soon. It is amazing how much easier things are with later builds of Centos and vSphere 6.7. 8/9/18 – improved and updated for vSphere 6.7.I am not a Linux guy so I might have more info here in this article then necessary but I can tell you it works! With this info you should be successful in building out a Centos template for use in your VMware environment and without all the issues that I had. VMware KB article on installing deployPkg – Which is why I added it to the list above! And that worked great. I had problems with this, so I used wget.
#REDHAT LINUX VM INSTALL#
If you try and install the deploypkg and get an error like below you are missing the VMware certs.
#REDHAT LINUX VM UPDATE#
Which means Perl is not installed (so I had to update this article again!) Missing Certificates If your deploy from template is not successful, like mine was, meaning that the template name remained and the VM name was not taken by the VM, you should check the following folder and file for clues. You can find a good short list of tweaks in this article.Īt this time I am not using any of these tweaks but when I do I will update this section of the article. You can find a really good long list of tweaks in this article.
#REDHAT LINUX VM WINDOWS#
Just like I do a lot of tweaks to my Windows if you are a Linux Admin you would do the same. Further Customization of your Linux Image For so many tests the DNS name said centos.tmpl as it was the template name and wasn’t being updated. Note about how the VM name is test7, and the DNS name is. If you need help with the custom spec you can find it in this article. You should be able to turn the VM into a template and deploy from it successfully. Not required from here up to the beginning of Crazy section. The certs we installed is what lets it be installed successfully.Yum install open-vm-tools-deploypkg (something newer likely already installed so this step not needed) Now we need to load the package that will do customization.Yum install open-vm-tools (likely already installed) We may, or may not need to install the open-vm-tools package.This file and contents will look like below.
#REDHAT LINUX VM DOWNLOAD#
Download the VMware package certs from here –.I did work through it and things were ok, but stuff was already in place so that makes me think it is not needed but will need to test. It is possible that with 1611 of 7.0 this section is not needed. This is not required any longer as you can create a VM of type Centos, and you get VMware Tools as part of it. Yum -y install mlocate (this installs some sort of file search tool that Veeam uses to do indexed backups) Crazy Stuff – NOT REQUIRED ANY LONGER Yum install net-tools (likely already installed) we need to add a few typical things to the OS.Rm -f /etc/redhat-release & touch /etc/redhat-release & echo "Red Hat Enterprise Linux Server release 7.0 (Maipo)" > /etc/redhat-release You should do a copy and paste of this long command and execute it at the command prompt:.You can find out more on this subject in this article. There were two things wrong – NETWORKING=YES did not exist and ONBOOT=No did exist. NOT REQUIRED ANY LONGER – Ignore – I had some issues in that networking did not work. Update the OS with the following command.BTW, when you do the TZ, also enter Network and toggle it on – you should see a DHCP address. I kept all the defaults, but had to confirm the disk, pick the right TZ, and add a good root password. You need to create a VM of the type Redhat Enterprise 7 64-bit Centos 7 64-bit.Incidentally I used Centos 7.0 and vSphere 5.5 U2 and everything patched to current (updated for vSphere 6.0 and Centos 7.0 1611). You will need the media – Centos 7 in my case and uploaded where you can find it easily. Update, it has improved significantly as VMware has updated vSphere. So I am very happy I figured it out and can share it with you! I hope that this helps you avoid the fuss I had. This has been very painful and frustrating.