Comments on: ESX 3.5 vmtools incompatible with ESX 3.0.x http://vmetc.com/2008/01/23/esx-35-vmtools-incompatible-with-esx-30x/ Go Green with Virtualization. Go UGLY Green with vmetc.com. Wed, 25 Jan 2012 13:41:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Jim http://vmetc.com/2008/01/23/esx-35-vmtools-incompatible-with-esx-30x/comment-page-1/#comment-119 Jim Mon, 11 Feb 2008 14:10:11 +0000 http://vmetc.com/2008/01/23/esx-35-vmtools-incompatible-with-esx-30x/#comment-119 This actually makes a lot of sense when you think about it. When ESX changes major versions (2.x to 3.x) then what the aliens in engineering are doing is virtualizing a new motherboard config. That's how they go from 2 CPUs to 4 CPUs. They are literally changing the virtual hardware your VMs run on. When you go from 3.0.x to 3.5.x then you're not changing underlying motherboard, but you are going to get different tools or tweaks out of the VMtools. This could be as significant as changing the virtual machine bios level or it could be simple optimization code for functionality that's already there. When you go to 3.5 sure there's going to be a tools update. 3.0.anything isn't going to know how to read that new code. It simply doesn't understand the instruction set. What should continue to work is taking a VM from 3.0.x and running it *without* upgrading tools on a 3.5 platform. VC is going to complain about tools being out of date, and you might see some degraded performance compared to 3.5 native machines, but it should continue to work. If you don't upgrade your tools versions for a while, you ensure you have a rollback capability should things go horribly wrong in the first 2 or 3 weeks. This actually makes a lot of sense when you think about it.

When ESX changes major versions (2.x to 3.x) then what the aliens in engineering are doing is virtualizing a new motherboard config. That’s how they go from 2 CPUs to 4 CPUs. They are literally changing the virtual hardware your VMs run on. When you go from 3.0.x to 3.5.x then you’re not changing underlying motherboard, but you are going to get different tools or tweaks out of the VMtools. This could be as significant as changing the virtual machine bios level or it could be simple optimization code for functionality that’s already there.

When you go to 3.5 sure there’s going to be a tools update. 3.0.anything isn’t going to know how to read that new code. It simply doesn’t understand the instruction set. What should continue to work is taking a VM from 3.0.x and running it *without* upgrading tools on a 3.5 platform. VC is going to complain about tools being out of date, and you might see some degraded performance compared to 3.5 native machines, but it should continue to work. If you don’t upgrade your tools versions for a while, you ensure you have a rollback capability should things go horribly wrong in the first 2 or 3 weeks.

]]> By: Jim http://vmetc.com/2008/01/23/esx-35-vmtools-incompatible-with-esx-30x/comment-page-1/#comment-5038 Jim Mon, 11 Feb 2008 14:10:00 +0000 http://vmetc.com/2008/01/23/esx-35-vmtools-incompatible-with-esx-30x/#comment-5038 This actually makes a lot of sense when you think about it. When ESX changes major versions (2.x to 3.x) then what the aliens in engineering are doing is virtualizing a new motherboard config. That's how they go from 2 CPUs to 4 CPUs. They are literally changing the virtual hardware your VMs run on. When you go from 3.0.x to 3.5.x then you're not changing underlying motherboard, but you are going to get different tools or tweaks out of the VMtools. This could be as significant as changing the virtual machine bios level or it could be simple optimization code for functionality that's already there. When you go to 3.5 sure there's going to be a tools update. 3.0.anything isn't going to know how to read that new code. It simply doesn't understand the instruction set. What should continue to work is taking a VM from 3.0.x and running it *without* upgrading tools on a 3.5 platform. VC is going to complain about tools being out of date, and you might see some degraded performance compared to 3.5 native machines, but it should continue to work. If you don't upgrade your tools versions for a while, you ensure you have a rollback capability should things go horribly wrong in the first 2 or 3 weeks. This actually makes a lot of sense when you think about it.

When ESX changes major versions (2.x to 3.x) then what the aliens in engineering are doing is virtualizing a new motherboard config. That’s how they go from 2 CPUs to 4 CPUs. They are literally changing the virtual hardware your VMs run on. When you go from 3.0.x to 3.5.x then you’re not changing underlying motherboard, but you are going to get different tools or tweaks out of the VMtools. This could be as significant as changing the virtual machine bios level or it could be simple optimization code for functionality that’s already there.

When you go to 3.5 sure there’s going to be a tools update. 3.0.anything isn’t going to know how to read that new code. It simply doesn’t understand the instruction set. What should continue to work is taking a VM from 3.0.x and running it *without* upgrading tools on a 3.5 platform. VC is going to complain about tools being out of date, and you might see some degraded performance compared to 3.5 native machines, but it should continue to work. If you don’t upgrade your tools versions for a while, you ensure you have a rollback capability should things go horribly wrong in the first 2 or 3 weeks.

]]> By: Scott Lowe http://vmetc.com/2008/01/23/esx-35-vmtools-incompatible-with-esx-30x/comment-page-1/#comment-99 Scott Lowe Fri, 25 Jan 2008 02:45:10 +0000 http://vmetc.com/2008/01/23/esx-35-vmtools-incompatible-with-esx-30x/#comment-99 Rich, good catch! For companies running farms with mixed versions of ESX Server, this could be an issue. Thanks for bringing it to light. Rich, good catch! For companies running farms with mixed versions of ESX Server, this could be an issue. Thanks for bringing it to light.

]]> By: Scott Lowe http://vmetc.com/2008/01/23/esx-35-vmtools-incompatible-with-esx-30x/comment-page-1/#comment-5037 Scott Lowe Fri, 25 Jan 2008 02:45:00 +0000 http://vmetc.com/2008/01/23/esx-35-vmtools-incompatible-with-esx-30x/#comment-5037 Rich, good catch! For companies running farms with mixed versions of ESX Server, this could be an issue. Thanks for bringing it to light. Rich, good catch! For companies running farms with mixed versions of ESX Server, this could be an issue. Thanks for bringing it to light.

]]>