#Volume manager vista install#
#Volume manager vista software#
#Volume manager vista mac#

#Volume manager vista mac#

If you clone from a template, VMware will naturally give the new machine a new MAC address for any NICs in the template.

Also, get rid of the udev stuff that sometimes messes up your NIC settings And obviously, networking will be broken.

#Volume manager vista install#

Yum –disablerepo=* –enablerepo=vmware-tools –enablerepo=C-base install open-vm-tools-deployPkgīy the way, the symptoms of this in RHEL 7? Aside from the customization error, you’ll have network cards named ens32 or ens33 in the template, but ens160 in the clone. The solution? Disable all repos except vmware-tools and C-base from the “vault” when you do the installation. This created issues for me trying to install in CentOS 7.2, which ships only 9.10. Note: If you’re using CentOS 7, open-vm-tools-deployPkg requires open-vm-tools < 9.5.

It will be if you simply install “vmware-tools-esx-nox” (I also include vmware-tools-esx-kmods).įor RHEL 7, you need open-vm-tools (which comes standard with RHEL 7) and open-vm-tools-deployPkg (which comes from VMware). Bottom line – install those tools!įor RHEL 6 that means “vmware-tools-plugins-deployPkg” has to be present. Or maybe you like doing it the old fashioned way and installing them from vCenter.

#Volume manager vista software#

You can even bring it into Satellite or Spacewalk, either as an external repo or a software channel. You can clone that repo into your own, or just use theirs. I like using the “3rd party” tools that you can get from VMware’s own repo. If you’re using customization specifications during cloning, VMware cannot do the work unless the tools are installed in the image from which you’re cloning. There were some updates in 6.4 that greatly improved RHEL’s interaction with VMware’s hypervisor, including at the NIC level. If this is happening with RHEL 6, Make sure your version is 6.4 or later When I tried cloning the same RHEL 7 template from an updated vCenter (and had the correct VMware tools installed) all went well. One of our vCenters had not been updated in some time. If this is happening with RHEL 7, make sure the vCenter is a new enough version to support it In most of these cases, you’ll need to convert your template to a VM and power it up, then make the changes, shut it down, and convert it back to a template. So, before you go chasing that wild goose of LVM incompatibility, or telling vCenter your template is RHEL 5, I have a couple of recommendations. Since my customization spec was setting network parameters, I suspected that’s where the root of this problem was.

I have a script that has been happily cloning 64-bit LVM-based RHEL 6 templates in multiple vCenters that are on versions between 5.0 and 5.5. In my case, the error had nothing to do with logical volumes (I suspect that’s true for most people who have run across this message). Not from PowerCLI or PowerShell (which are certainly powerful, but hey, I’m a Linux guy). We had just stood up a new datacenter and I was laying the groundwork for creating masses of virtual machines from a command-line. Refer to vCenter documentation for supported configurations.įor me this happened when (A) I was cloning a RHEL 64-bit template (this occurred both with RHEL 6 and RHEL 7 but for entirely different reasons on each), and (B) I was using a customization specification. Microsoft Vista (TM) and Linux guests with Logical Volume Manager are supported only for recent ESX host and VMware Tools versions. While using VMware’s API and pyVmomi to clone templates into a VM, a couple of times I have run into this error:Ĭannot deploy template: Customization of the guest operating system ‘rhel6_64Guest’ is not supported in this configuration.