VMware

This Question is Possibly Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
1 ... 21 22 23 24 25 ... 47 Previous Next 704 Replies Last post: Aug 25, 2008 11:18 PM by dipaksharma   Go to original post
Click to view rob.nance's profile Novice 18 posts since
Jul 14, 2008
gi-minni wrote: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 ...

Well, I am lucky, this only affected a monitoring VM. There are people with mission critical services down, so yes, it is a big deal, and people have every right to be upset. True, PEOPLE make mistakes, but that's why you should have whole teams of people looking at the code to make sure no one person misses this. VMware is not a person, they are a company providing a mission critical product, one that has a very terribly designed system for licensing to where if licensing fails, all shuts down. Hopefully the result of this will be VMWare fixing this so it doesn't break, just cripple, upon license failure.

Click to view RParker's profile Champion 5,288 posts since
Dec 6, 2006

When a vm is powered on it gets its time from the esx server. There is no other possibility. Even without vmtools.

That is not true. If you don't have the tools or have the sync option, the time syncs with Windows normal time sources. That's why it's an OPTION.

Click to view Kevin Gao's profile Hot Shot 206 posts since
Mar 27, 2008
I don't know...but the easiest thing for you to do - is shut down 1 of your test VM's and see if you can start it back up again. If you can then you're probably NOT affected.
Click to view xprez's profile Lurker 1 posts since
Sep 27, 2006

Did a major upgrade on all ESX hosts last week, typically..

But it's a production environment, and all we loose is DRS and HA.. We don't power down VM's on our production environment, and even if we did then turning back time on 1 host is no big deal as long as you have proper time keeping on your VM's.

So time bomb and what ever media is making this sound like, it has no affection on our servers handling billions today ;)

Click to view dpomeroy's profile Virtuoso 3,901 posts since
Apr 12, 2004

Eric,

I could not agree more. Over the last few years it seems VMware has become so focused on releasing new products and new features that QA has taken a big hit. I understand they are under constant pressure to stay two steps ahead of Microsoft, Xen, and others, but not at the expense of stability and reliability. One of the major things that helped ESX spread in the Enterprise data center was its reliability and stability, and they need to make it priority #1 if they expect us large companies to continue to put our critical applications on top of their virtualization layer.

Don Pomeroy
VMware Communities User Moderator

Click to view MicroAdmin's profile Enthusiast 72 posts since
Feb 17, 2006
Unfortunately all of my test vm's are shut off as I was conserving resources during my update the other night to 3.5u2 X-(
Click to view dbuchanan's profile Lurker 5 posts since
Sep 18, 2007
This is limited to 3.5 u2 only does not affect 3.5 u1

Dan L. Buchanan | Microsoft Engineer
Barclaycard | Business Technology Group | Infrastucture
Engineering
Telephone (302) 255-8970 | Mobile (302) 507-6297

COMPANY CONFIDENTIAL
Click to view CLowe's profile Enthusiast 40 posts since
Apr 13, 2007

I agree. Everyone take a deep breath...walk around the block once or twice. Take another look around and rationally evaluate your position.

I have to say I have never seen so many people got from 0 to full blown rage so fast. It makes me think that either 1) They were just looking for ANY excuse to start a rant 2) Are MS/XEN fans again looking for ANY excuse 3) Love starting flame wars from sheer voredom or 4) They are so perfect in their own lives that seeing anything less from anyone else is a cause for rage.

Is this a big problem? Absolutely. Is is the end of the world? Depends on how shaky your world already was. There was a mistake made (like any of us never made any) but a fix is on the way and will hopefully correct the issue. I am more concerned with how frequently problems like this occur which would show an inability to get get things right, than I am with the fact that one happened in the first place. In our environment we have about 70 vm's and this problem (providing it is corrected in a day or two) almost rates as a non-event for us.

Click to view MicroAdmin's profile Enthusiast 72 posts since
Feb 17, 2006
Actually, if I would use my brain :) It's a good thing my test vm is off. I tried starting it and no go, crap :(
Click to view dispatch's profile Lurker 2 posts since
Dec 13, 2007

Dan,

Thanks for the confirmation. Is there a definitive way to ascertain what version I am running? (Does 3.5.0, 82663 = U1?)

Click to view interix's profile Novice 13 posts since
Mar 27, 2006

Ill have to agree with CLowe VMware has been stable (been working with it since 1.x) create an update policy and stick to it, i will agree with anyone who says no way to prepape for this type of issue... use a work around and be patient. Issue was identified and they will resolve it.

Farm 100+hosts with 1 effected.

Click to view Kevin Gao's profile Hot Shot 206 posts since
Mar 27, 2008

Sorry to hear that Micro...but at least it's a test VM. I just talked to a friend who works for a group of lawyer's offices. He's not really affected because all his VM's are up and working.

Everyone's just hoping that there's no "incidents" between now and the time the permanent fix comes out.

Click to view gi-minni's profile Enthusiast 48 posts since
Mar 22, 2006

We have dozens of clustered ESX servers in production with hundreds of VM boxes on it. All our stuff is alerted, because
we have mission critical applications, but you can not change anything s*it happens and no one is perfect.
I know that vmware and we all together will get our lessons learned on this sad day.
Of course our production ESX serverfarms are not updated frequently nor automatically and we are in a good shape,
but shouting will not change anything it will get things worser. Now is better to have a cool and thinking head than a
red and angry one.

Click to view bluedrake's profile Novice 24 posts since
Jan 7, 2008
Well just an update we reinstalled one of our production esx servers with 3.5 update 1 and could vmotion servers to that esx server, so now going to reinstall other 3 esx servers and save not having to worry about downtime
Click to view BenConrad's profile Expert 577 posts since
Mar 20, 2006
That paragraph is certainly not clear as it references that U1 is the same as U2. "ESX350-Update01 (ESX350-Update02)" is to be interpreted as that they are the same or similar.

Anyway, It looks like vmware has pulled all patches and U2 release in July.

Ben

VMware Developer

SDKs, APIs, Videos, Learn and much more in the Developer community.

Learn More

Developer Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

VMware vSphere

Come witness the next giant leap in virtualization.

Register Today

Communities