> From: [email protected] [mailto:[email protected]] > On Behalf Of Mathew Snyder > > Our virtual platform is currently hosted with a company that strangely still > uses ESXi 4.0. We have the ability to install RHEL5 from their supplied > templates and can make copies of existing VMs with customization such as > hostname and IPs; things one would expect a robust hypervisor to support.
I don't believe this is an ESXi thing. It's a function of your host provider. When you clone a machine in ESX, all it does is copy the machine, and change the MAC address (and other hardware serial numbers.) All the non-hardware things that make the system unique are left to the user - the IP address, machine name, system id (if applicable) ... It's not a hardware-level thing, so vmware doesn't deal with it. Your provider might have some scripts they use for this purpose on rhel5, that they haven't adapted to rhel6. The vmware compatibility guide shows: http://www.vmware.com/resources/compatibility/search.php?deviceCategory=software rhel 6.0: ESX 4.0u4, ESX 4.1, ESX 4.1u1, ESX 4.1u2, ESXi 5.0, ESXi 5.0u1 rhel 6.1: same as above rhel 6.2: ESX 4.0u4, ESX 4.1u1, ESX 4.1u2, ESXi 5.0, ESXi 5.0u1 rhel 6.3: ESX 4.0u4, ESX 4.1u2, ESXi 5.0, ESXi 5.0u1 This is a hardware compatibility guide. If you're running a configuration that's not on the supported configuration list, then you should expect hardware bugs, driver bugs. This does not indicate any special support for automating the cloning of systems. For this reason, I'm always hesitant to apply OS updates to VM's running on vmware. I've been bitten in the past. _______________________________________________ Tech mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
