You can't make a baby in a single month by putting 9 women together.
Just a nice visual for those who are "speechless" about the time putting a patch in place. VMWare has said new binaries will be available August 13th at noon PST, that's 14 hours from now. QA takes times, whether it's a patch, or a general update. This is regardless of the QA team's failure to notice this bug before Update 2 release.
Philip Arnason
There is a support alert on the main VMWare support page. http://www.vmware.com/support/. Not much consulation but it is there.
Well that is funny, because yesterday I set up my first ESXi installation. I've been using VMware Server and Workstation
for a good while now. I just 'happened' upon this thread this morning. Fortunately i am still in test mode
and I hadn't even powered on the ESX box yet this morning...so for me , I was just lucky.
Unbelivable, you claim to be a enterprise solution. You really SUCK BIGTIME. 36 hrs is not acceptable
Had I written this, I would be crucified. But I have to say in my years with Microsoft Products, I don't remember seeing anything quite like this. What you say about MS:
MS has always been the target for people to yell at when it comes to buggy software but they have never managed to do something like this.
Is exactly right. I agree, this hasn't ever been this bad with MS. At a time when its absolutely crucial for VM Ware to shine, they completely dropped the ball at the goal line just as time runs out... This is going to be detrimental.. I know they will over come.. but it's going to go down as perhaps the biggest faux paus in computing history.
3- Windows ME
2- Windows BOB
1- VM Ware ESX 3.5 Date bomb
I have been supporting and getting behind VM Ware for the last 2 years.. But this is very tough pill to swallow...
Please calm down everybody and let the vmware people do the needed work to
resolve this nasty issue. We all know that if the time pressure is high the quality of work dramatically degrade. This
is a severe problem without excuses, but no one is perfect in software development. If we look
in the past VMware has delivered very complex and high quality code. Let us conduct a technical based
discussion and not a flame war against them. We are all sitting in the same boat.
My 2 cent ...
Agreed.
Has there been any update as to which of the updates within U2 caused the problem?
I understand but this is suppose to come from VMWARE and not from third
parties...
This is from a Computerworld.com article -
""Updated product bits with correct licensing will be made available for
download as soon as possible," the spokesman said, adding in a follow-up
e-mail that VMware expects to have a patch available later today."
I hope the today part is correct.
At 11:00 am in the morning there was nothing posted there..I can assure you that. I called VMware and a technical person just send me this link, can you believe it??
The fix was not even coming from VMware??? this is very very scary...
-
Original Message-----
From: Indrajit Mahanta (c) imahanta@vmware.com
Sent: Tuesday, August 12, 2008 10:49 AM
To: Eduardo Triana
Subject: Please refer to the link below for ESX server update 2
Systems Integration Engineer
Rogers Wireless Inc
Montreal, Canada
its just a real shame that the "bug" has nothing to do with the functioning of ESX... it's all because of licensing and is why I am so critical of this particular error
Apprently you didn't read the posts either. It is an intrigal part of ESX, licensing or not, they ALL work TOGETHER. It doesn't matter which piece caused the problem, it's all part of the same CODE. It's not licensing, licensing is fine, it's within ESX itself. And how you can even say nothing to do with functioning..
you can't do DRS, vmotion, or power on VM's, that's pretty much ALL ESX does! It's 100% function.
If you change the date, and you have vm ware sync tools on, you have effectively made an entire environment useless. VM's can't login with AD unless time is within 5 minutes, some databases need time/date to be CRUCIAL to their updates.. this is a MAJOR hit, it's all about function, and nothing to do with licensing.
May I ask you how many VMs do you have in production?? you don't sound like you have a big environment like we do...this is not good for us that today and tomorrow will have to be on site until this issue gets resolved..
Systems Integration Engineer
Rogers Wireless Inc
Montreal, Canada
May I ask you how many VMs do you have in production?? you don't sound like you have a big environment like we do...this is not good for us that today and tomorrow will have to be on site until this issue gets resolved..
Systems Integration Engineer
Rogers Wireless Inc
Montreal, Canada
Lol, I dond`t want to sit on theire phone at the support desk ![]()
hmm,
KB site is down for maintenance for now.....
" Temporary Maintenance - Knowledge Base
The Knowledge Base is currently unavailable while we make important user improvements and upgrades to the site. We apologize for any inconvenience this may cause. "
What I find even worse: not mentioning anything about this mega-big issue on the home page www.vmware.com .... first sight only on the support page
Jan
Can anyone confirm this is limited to ESX 3.5 U2 and not U1? The KB article says it affects ESX 3.5.x....
I'm running ESX 3.5.0 82663 but my paranoia wants to confirm I'll be OK come tomorrow...
Thanks in advance.