VC 2.5 problems unending problems

[richG]

The question below I added to a thread on this forum earlier today. I then discovered another problem so I started a new thread about VC2.5 problems.

I just went to uese a template I created earlier which is now located to a ESX 3.5.1 fully patched server, when I went to go use it the server was grayed out with nothing else after it. I could make any changes to the template so I had to go in via the terminal and change the vmtx file to a vmx file and then add it to the inventory again under a different name. It is really getting hard to do my job as I am spending all my time chasing my tail with problems with the VC. So it is this a DB problem or a VC problem??

Hi all,

I am having a real problem with the drop outs of my ESX 3.02. with all updated patches installed, VC 2.5.0 newest patch to 2.5.1 not done yet. Here is the situation similar to this one but with a different twist.

The server has been up and running for months now no problem in the last couple of weeks it will just drop out of the VC or lose it connection all the VM Guest will continue to run no problem I have tried all the solutions on the threads

Restart the vmware-vpxa service stop and restart the mgmt-vmware service (this one the VM-host agent hangs) I then have to remove the vmware-vpxa package remove the host from the VC and reboot the host bring it back into the VC and it will be fine for a week or so then we start all over again. I also have a server in QA that does the same thing. I would just rebuild the server as stated here, but I also have 35-40 guest running and it a little hard to just shut them down when ever this happens.

So my questions are:

1. When I upgrade my VC to 2.51 will this fix this problem?

2. if not then is there a fix out there for it or is VMWare working on a fix for it, from what I have read on the forums it has to do with the VPXA driver??

3. Once again another company that rushes products to the market to make the share holders happy and we in the field have to fix the bugs that should have been fix before it was released. I have been using VMware for quite some time here, but there has been some serious problems with the VC and ESX 3.5 that need to be fix and fix right not just patched each month. Once again greed is the kill of all applications in this market.

Thanks all I need to vent sorry.

Rich

[HyperSprite]

1) There were a lot of fixes in 2.5u1 one of them might fix your issues. If you read the VC2.5u1 release notes for resolved issues, the first one listed under VirtualCenter sounds like your issue. . Before you upgrade, my best advice would be to scour the known issues list on that page to avoid any other pitfalls.

2) See 1

3) How can VMware get fixes into your VC if you don't install the updates? I worked for a BtoB connections company for seven years and it really seemed like a loose/loose situation for software development. If we waited until everything was perfect, we never release and our customers got mad. If we push hard to release to give them features they wanted, things broke and our customers got mad. Getting a balance somewhere in between with competition breathing down your neck is the hard part. Hopefully VMware can work that out.

Good luck in any case.

[richG]

Hi,

Thanks very much for the update and yes I do agree on the developement side of things. It is just we are applying so many patches to these servers at the moment I feel like I am running a MS product LOL.

Thanks we are applying the VC 2.5.1 update tomorrow night so if fixes my problems I will reply on this thread. I will also take your advice on reading the known issues, I have read it once, but will do so again as well.

Hey I love the product it is great it just gets hard when you spend half your day chasing your tail.

Regards,

Rich