Vmware bug
Ξ August 13th, 2008 | → | ∇ Uncategorized |
All your VM’s are belong to us
As of tomorrow morning, VM’s running on all hosts with ESX 3.5U2 in enterprise configurations will not power on. VMotion/HA/DRS will probably also not work.
Boom.
Apparently, there is some bug in the vmware license management code. VMware is scrambling to figure out what happened and put out a patch.
Running VM’s will not be immediately impacted.
There is a major discussion going on in the vmware communities about the issue: http://communities.vmware.com/thread/162377?tstart=0
Vmware Bug
Vmware Bug. … Vmware Bug Articles. Convergence Technology Consulting With Microsoft Vmware Network. Computers & Internet >> Convergence Technology …
OK, while we’re all remaining calm….just imagine the implications that bugs like this can occur and get past QA testing….5 years down the road, nearly all server apps worldwide running in VM’s if you believe a lot of forecasts ……some country decides to initiate cyberwarfare and manages to get a backdoor into whatever is the prevailing hypervisor of the day…..boom. All your VM’s are belong to us.
I honestly think a lot of the hype from those who want to build a vm security industry is crap, but god protect us if the baseline code for critical hypervisors like ESX isn’t kept secure and regularly audited.
I’d love to find out what happened here.
What regression testing on new releases does vmware do to check for date based bugs? I’d think they’d at least check for simple things like changing the date to 1 year or 1 month in the future.
VMware bug causes worldwide disruption - ZDNet.co.uk
Aug 12, 2008 … VMware virtual machines on all hosts with the company's latest hypervisor, ESX 3.5 Update 2, in enterprise configurations have found that it …
UPDATE: Frank Wegner has posted the following suggestions:
you can see the latest status here: http://kb.vmware.com/kb/1006716 please check back time after time, because it determination notify you when this issue has been fixed. until then the best workaround i can think of is:
* Do nothing * Turn DRS off * Avoid VMotion * Avoid to power off VM’s
Slashdot Massive VMware Bug Shuts Systems Down
Massive VMware Bug Shuts Systems Down — article related to Bug and Technology.
I’d council against turning DRS off as that actually deletes resource pool settings….instead, set sensitivity to 5 which should effectively disable it w/ minimal impact.
UPDATE 2: VMware Website appears to be having trouble keeping up with people requesting updates.
UPDATE 3: VMware has stated they will have fixes available in 36hrs at the earliest.
UPDATE 4: Anand Mewalal comments:
we used the following workaround to power on the vm’s. identify the host where a vm is located run ‘ vmware-cmd -l ‘ to list the vms. issue the commands: service ntpd stop date -s 08/01/2008 vmware-cmd /vmfs/volumes/vm viagra kaufen path/vmname.vmx start service ntpd start
UPDATE 5: Apparently, there are no easily seen warnings in logs/etc or VC prior to hitting the bug. VC will continue to show the hosts as licensed and no errors will appear in vmkernel log file until you try to start up a new vm, reboot a vm, or reboot the host.
VMware Communities: httpd.vmware bug init script …
Re: httpd.vmware bug init script Feb 15, 2006 10:54 PM in response to: bac · Click to view Markske's profile Novice Markske 22 posts since Feb 9, 2006 …
UPDATE 6: Welcome Slashdot readers! I’ve temporarily disabled comments to allow the server vm to handle the load. Apparently Movable Type 4.1 executes a seperate perl cgi script to handle comments on each page load. Load times might have been slow for the last 45 minutes, but should be OK now.
UPDATE 7: I made some minor corrections to this entry that others have requested.
UPDATE 8: VMware has provided a FAQ about the bug with an updated ETA and a few responses to common complaints.
UPDATE 9: Here are some additional external links to blogs/media covering the bug:
VMware bug revisited - c0t0d0s0.org
For my non-german speaking readers a link to an english background article in the Register -
searchservervirtualization.com the annals - date bugs kills vmware systemsblog.scottlowe.orgvirtualization.infovmware continues to make a tenable argument that all software will possess biggest bugs at some nucleus, and customers keeping unruffled and being patient is the paramount course for everyone to embezzle at this time.most of the blogs are naturally quite conquer about the lack of qa for the most part…..but i am seeing just as much incense, if not more, is being generated due to the high wait stretch for a patch. in the discussion forums, vmware points out that they want to run qa on the patch itself last to release and that they experience to classify the patch in innumerable many languages/locales….still, i have to regard as that if a bug have a fondness this occurred in a major open source project, we’d have a patch from cialis someone square if it was not the vendor public within 12-24hrs? of course, it would not be qa’d and may cause more damage than the larva it is vexing to fix. it always comes down to making you’re making your choices and attractive your chances.update 10: feedback from slashdot:
VMware Communities: vmware bug …
Can someone help me fix this bug ? my vmware keep crashing I use VMware Workstation 5.5.3 … Re: vmware bug Mar 26, 2007 7:57 PM in response to: garung …
VMware bug bombs virtual servers - Network World
Aug 12, 2008 … VMware customers find their systems won't power up Tuesday as a bug triggers a license management issue within the servers.
Related posts: Zimbabweans seek refuge at U.S. Embassy, Clui, Jose luis castillo, Believe eurovision, Charles
2 Responses to ' Vmware bug '
Leave a reply
You must be logged in to post a comment.
on September 19th, 2008 at 11:12 pm
[…] posts: Vmware bug, Nintendo channel, Bigbang, Chargers schedule, Ha […]
on September 20th, 2008 at 9:56 am
[…] posts: Vmware bug, Dr. death, Gmail issues, Nlrb, Chargers […]