VMware Communities: BIG bug in ESX 3.5 Update 2

Up to Discussions in VI: VMware ESX™ 3.5

This Question is Possibly Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)

1 ... 22 23 24 25 26 ... 47 Previous Next 704 Replies Last post: Aug 25, 2008 11:18 PM by dipaksharma Go to original post

Re: BIG bug in ESX 3.5 Update 2 - If you're using 3.5u2 read this now! - A general system error occurred: Internal Error

345. Aug 12, 2008 10:45 AM

in response to: bluedrake

Kevin Gao

206 posts since
Mar 27, 2008

Thanks for the calm & logical comments! Good change from the flames / rants.

That's a good idea actually - just reinstall...only takes 30 minutes to get an ESX host up and running.

Re: BIG bug in ESX 3.5 Update 2 - If you're using 3.5u2 read this now! - A general system error occurred: Internal Error

346. Aug 12, 2008 10:49 AM

in response to: shane.presley

RParker

5,288 posts since
Dec 6, 2006

can I upgrade my Virtual Center server to 2.5 U2?

YES.

It seems this bug only affects ESX itself.

That is correct. You can manage the ESX U1, U2 and other ESX versions, but only the ESX U2 has this problem. VC will be fine.

Re: BIG bug in ESX 3.5 Update 2 - If you're using 3.5u2 read this now! - A general system error occurred: Internal Error

347. Aug 12, 2008 10:50 AM

in response to: Kevin Gao

JoeCasanova

6 posts since
Aug 12, 2008

Wow, 24 pages!

ESXi 3.5 U2 here.

I was working late last night in the middle of a transition from MS Virtual Server 2005 to VMWare ESXi 3.5 and caught the bug an hour or so shy of midnight. I came here and found the answer. Rolled back to August 10th and all is OK. Bookmarked this page and expected an answer by VMWare by now, but I didn't expect to see it become 24 pages long!

I'm eagerly awaiting a permanent solution so I can continue my work without worry!

Re: BIG bug in ESX 3.5 Update 2 - If you're using 3.5u2 read this now! - A general system error occurred: Internal Error

348. Aug 12, 2008 10:51 AM

in response to: mattjk

JPerf

31 posts since
Oct 22, 2006

I think that in the future I will never to install no release with marking "U2"
only U1 and then U3, U4,...
BTW
U2 (aeroplane) on the May 01 1960, at that time had the same problem...well I never ?

JPerf

Re: BIG bug in ESX 3.5 Update 2 - If you're using 3.5u2 read this now! - A general system error occurred: Internal Error

349. Aug 12, 2008 10:52 AM

in response to: mattjk

RickPollock

73 posts since
Jul 25, 2007

Yes, I am very disappointed in this bug. How did this get past QA? It's a good thing I haven't deployed this in production yet. Looks like its time to spin up Hyper-V....

I would be lucky to have my job if this happened in production. OMG ... VMware get it together. First the bogus download and now this? It almost can't get any worse!

Re: BIG bug in ESX 3.5 Update 2 - If you're using 3.5u2 read this now! - A general system error occurred: Internal Error

350. Aug 12, 2008 10:55 AM

in response to: sshamilt

BryanMcC

280 posts since
Feb 20, 2007

Just goes to show you... Like I always say... Unless there is a specific bug being fixed you should always wait before applying updates.. And even then testing/validation/acceptance????

And tisk tisk to you all who applied this to all of your production ESX hosts.

If anyone has been installing the latest greatest from VMware you may have known that something like this could happen.. My VC 2.5 and ESX3.5 install was buggy as all hell.. Finally I applied update 1 a few months ago and lost many of the annoying bugs.

At least shares are holding steady..

Just figured I would through in my 2.

Help me help you by scoring points.

Re: BIG bug in ESX 3.5 Update 2 - If you're using 3.5u2 read this now! - A general system error occurred: Internal Error

351. Aug 12, 2008 10:55 AM

in response to: RickPollock

Kevin Gao

206 posts since
Mar 27, 2008

If you shut down all your production mission critical VM's (i.e. Exchange DC's etc) the previous night then you'll definitely be in trouble. Otherwise - you're not in bad shape as your VM's that were powered on will continue to work.

Re: BIG bug in ESX 3.5 Update 2 - If you're using 3.5u2 read this now! - A general system error occurred: Internal Error

352. Aug 12, 2008 10:56 AM

in response to: bluedrake

jpratt_at_nor…

30 posts since
Nov 9, 2006

Wow. normally we are "bleeding-edge" but have been to busy to upgrade from u1 to u2..

So.... just to let it be known....

HEY VMWARE - YOU JUST LOST ANOTHER "BLEEDING-EDGE" SHOP. Maybe you will STOP including experimental code in production-release builds now?... PLEASE??

regards,

Re: BIG bug in ESX 3.5 Update 2 - If you're using 3.5u2 read this now! - A general system error occurred: Internal Error

353. Aug 12, 2008 10:58 AM

in response to: xprez

RParker

5,288 posts since
Dec 6, 2006

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 didthen turning back time on 1 host is no big deal as long as you haveproper time keeping on your VM's.

First did you read the posts? I don't think you did. This affects EVERY ESX 3.5 U2 server in the world.

Secondly, proper time keeping is PRECISELY what is preventing the VM's from powering on. The fact that the servers ARE up to date is why the VM's can't power on. The DATE has a drop dead time/date of 8/12/08 (12:00 AM). So ALL VM's after that time will NOT be able to turn on. That's the issue.

Third you lose the ability to load balance via vmotion, that could cause serious issues with ESX servers also.

Fourth the work around (which is FAR from ideal) is to change the date on the ESX server. The problem is if you have the VM's set to time sync, and the VM's start, the bios will have a date/time in the past. So you have to manually update each and every VM to ensure they are not going to synch with the server.

This is a HUGE bug and not one to be simply dismissed by your posting.. It's a LOT more serious than you evidently understand.. So Media or whatever, is going to have a field day with this, BECAUSE it DOES.. Affect servers handling billions today...

So READ the details next time before you ASSUME you understand what's at stake. Maybe you don't power off your VM's, but the rest of the world doesn't share your opinion...

Re: BIG bug in ESX 3.5 Update 2 - If you're using 3.5u2 read this now! - A general system error occurred: Internal Error

354. Aug 12, 2008 10:57 AM

in response to: mattjk

Speedbmp

248 posts since
Feb 12, 2007

http://digg.com/tech_news/MAJOR_BUG_VMWare_s_ESX_3_5US_Servers_will_not_boot_8_12_08

somebody has already posted it to Digg

Stephen

Re: BIG bug in ESX 3.5 Update 2 - If you're using 3.5u2 read this now! - A general system error occurred: Internal Error

355. Aug 12, 2008 11:01 AM

in response to: dispatch

rlabhart

3 posts since
Feb 27, 2008

Dispatch,

The version number you have is not affected. The affected versions should be:

ESX3.5, Build 103908

ESX3.5i, Build 103909

Your build, 82663, is ESX3.5 (U1) with patches up to April 10th.

VMWare updates the build # based on your installed patch level. (Your safely? well behind in patches....)

Re: BIG bug in ESX 3.5 Update 2 - If you're using 3.5u2 read this now! - A general system error occurred: Internal Error

356. Aug 12, 2008 11:03 AM

in response to: Speedbmp

MicroAdmin

72 posts since
Feb 17, 2006

Someone needs to mention that you shouldn't change the clocks on an ESX server that hosts a domain controller...not every one(unfortunately) is aware of the consequences.

Re: BIG bug in ESX 3.5 Update 2 - If you're using 3.5u2 read this now! - A general system error occurred: Internal Error

357. Aug 12, 2008 11:06 AM

in response to: MicroAdmin

Kevin Gao

206 posts since
Mar 27, 2008

Yes good thing in our environment - all Windows boxes sync to DC's (VM tools sync is disabled). Also got a NTP server running to point to the outside world...we don't rely on VMware ESX hosts for NTP.

It's unfortunately for those who did though cause they can't use the NTP time fix to power on their VM's easily.

Re: BIG bug in ESX 3.5 Update 2 - If you're using 3.5u2 read this now! - A general system error occurred: Internal Error

358. Aug 12, 2008 11:09 AM

in response to: Kevin Gao

MicroAdmin

72 posts since
Feb 17, 2006

What's weird for my server farm is that when vmotioning a VM, for some reason it would pick up the ESX server time even with tools sync disabled. We found out the hard way that ESX will force the VM to grab the ESX time as a "feauture". We couldn't figure it out how to to make it NOT do that so we have to keep the ESX server time synced with an NTP.

Re: BIG bug in ESX 3.5 Update 2 - If you're using 3.5u2 read this now! - A general system error occurred: Internal Error

359. Aug 12, 2008 11:10 AM

in response to: mattjk

kstailey

2 posts since
Aug 12, 2008

Is there anywhere we can register to get a call back or E-mail indication when this issue becomes resolved?

It would beat polling news forums to find out.

----

So funny when ESX 3i became free there was so much less news than there is about this today.

1 ... 22 23 24 25 26 ... 47 Previous Next Go to original post

Go to original post

Search VMware Communities Advanced Search

Actions

View as PDF

Up to Discussions in VI: VMware ESX™ 3.5

This Question is Possibly Answered

Re: BIG bug in ESX 3.5 Update 2 - If you're using 3.5u2 read this now! - A general system error occurred: Internal Error

Re: BIG bug in ESX 3.5 Update 2 - If you're using 3.5u2 read this now! - A general system error occurred: Internal Error

Re: BIG bug in ESX 3.5 Update 2 - If you're using 3.5u2 read this now! - A general system error occurred: Internal Error

Re: BIG bug in ESX 3.5 Update 2 - If you're using 3.5u2 read this now! - A general system error occurred: Internal Error

Re: BIG bug in ESX 3.5 Update 2 - If you're using 3.5u2 read this now! - A general system error occurred: Internal Error

Re: BIG bug in ESX 3.5 Update 2 - If you're using 3.5u2 read this now! - A general system error occurred: Internal Error

Re: BIG bug in ESX 3.5 Update 2 - If you're using 3.5u2 read this now! - A general system error occurred: Internal Error

Re: BIG bug in ESX 3.5 Update 2 - If you're using 3.5u2 read this now! - A general system error occurred: Internal Error

Re: BIG bug in ESX 3.5 Update 2 - If you're using 3.5u2 read this now! - A general system error occurred: Internal Error

Re: BIG bug in ESX 3.5 Update 2 - If you're using 3.5u2 read this now! - A general system error occurred: Internal Error

Re: BIG bug in ESX 3.5 Update 2 - If you're using 3.5u2 read this now! - A general system error occurred: Internal Error

Re: BIG bug in ESX 3.5 Update 2 - If you're using 3.5u2 read this now! - A general system error occurred: Internal Error

Re: BIG bug in ESX 3.5 Update 2 - If you're using 3.5u2 read this now! - A general system error occurred: Internal Error

Re: BIG bug in ESX 3.5 Update 2 - If you're using 3.5u2 read this now! - A general system error occurred: Internal Error

Re: BIG bug in ESX 3.5 Update 2 - If you're using 3.5u2 read this now! - A general system error occurred: Internal Error

Actions

Communities

Community Resources

VMworld

Get Support

Other Links

This Question is Possibly Answered

Actions

VMware Developer

Developer Sample Code

VMworld Sessions & Labs

Purchase PSO Credits Online

Community Hardware Software

VMware vSphere

Community Resources

VMworld

Get Support

Other Links