Yellow Bricks

by Duncan Epping

Bugs

So what if I would have $ 50.000

· ·

Sometimes you wished you hadn’t invested all of your 50.000 dollars on an employee who will be doing “migrations” for you. So what am I talking about? Well imagine yourself in a 24×7 environment, or anyother environment for that matter and you just received an email about this patch. Yeah this patch NEEDS to be applied a.s.a.p. cause it’s a major vulnerability. So in other words, patch your Hyper-V. This means either a quick migration or shutdown the vm’s in any environment that would cause downtime either way. I think your $ 50.000(which probably isn’t the correct amount anyway) is well spend within matter of days.

Thanks for making our arguments valid.

By the way, make sure to patch your systems asap cause a new worm virus can be expected that takes advantage of this feature(;)) soon…

Rollup pack for 3.0.2

· ·

VMware just released a rollup bundle for 3.0.2. So those still on 3.0.2 and looking for a quick way to get up to the latest patch level take a look at this KB article and download the patch here.

Roll‐ups provide you with a convenient way to download and install multiple bundles at one time. Installing this roll-up bundle zip file will provide all the fixes for the ESX Server 3.0.2 as of September 30, 2008.
The roll-up bundle zip file only contains fixes for the ESX Server 3.0.2 software. The roll-up bundle zip file cannot be used to upgrade from prior ESX Server releases.
 

VirtualCenter 2.5 Update 3 may fail to start after upgrade

· ·

I just wanted to point you guys out to the following:

Issue: After attempting to upgrade to VirtualCenter 2.5 Update 3 using the VirtualCenter Update Wizard, and not the VMware Unified Installer, the VirtualCenter service may fail to start. The issue is caused by an incomplete update of the database information for VirtualCenter resulting in incorrect database versioning, which is verified, and required to be correct, by the VirtualCenter service upon startup.

I’m not gonna post the answer to this problem, cause the article might change over the next day and than this info will be outdated and misleading. So check this KB article for more info.

VirtualCenter 2.5 Update 3 and HA networks

· ·

I wrote about a new patch for ESX(i) 3.5 yesterday and the fact that VirtualCenter 3.5 Update 3 was mentioned. Well today VirtualCenter 2.5 Update 3 has been released! You can pick it up here.

I think the most important fixes are the ones for HA. With Update 2 VM started checking the subnets of the heartbeat network for HA. If these weren’t compatible than HA bailed out. With Update 3 a new advanced option has been introduced ,”das.bypassNetworkVerification”. When this setting is set to “true” the Network compatibility check isn’t done and thus it’s possible to have an incompatible but routable HA heartbeat network.

Another important one is that as of U3 it’s possible again to delete HA advanced options, this problem was introduced in U2 and has been fixed.

An error that was also much talked about on the VMTN forum was the fact that VM’s weren’t vmotioned when maintenance mode was entered even if the admision control was disabled. This error has also been fixed.

These are three most important fixes in U3 in my opinion. Be sure to update and read the release notes for more info and fixes. Please not that the plugins for Update Manager and Converter has also been updated.

Update for ESX 3.5

· ·

After the 3.0.X updates the 3.5 updates couldn’t be far away, and here you go… And if you have a close look at the KB article of the patch you can see that VirtualCenter 2.5 Update 3 is also coming soon.