Receiving an IM from slacker, for the matter of lulz he sends me a link reagarding a post about VMware ESX server 3.5 bug.  Little did i know that this was going to potentially own my client.

After reading it a second time i realized that we have vmware esx 3.5. i said FUCK. outloud.

Browsing for a fix, I found out the temporary fix, to revert the clock on the machine and turn off NTP.

The bug itself is pretty awesome, a licensing bug that after today if you shut down a VM you wont be able to power it backup and get a licensing error.

talk about pwnage.

Vmware acknowledged the bug and proposed a patch release time of 6PM today. I hope they follow through, we have some crappy servers that need to be rebooted once in a while.

http://kb2.vmware.com/kb/1006716.html

http://communities.vmware.com/thread/162377?tstart=0

http://twinturbo.org/news/all-your-vmware-esx-are-belong-to-us/

http://www.deploylinux.net/matt/2008/08/all-your-vms-belong-to-us.html

pretty awesome.

One Response to “VMX has left the building 0”
  1. Also note that I discovered this at the exact time a contingency of Dell sales reps was trying to sell a $500k vmware setup to my boss. The irony is delicious.

Leave a Reply

FireStats icon Powered by FireStats