Migration ESX 4.0 to ESXi 4.1 : BSOD after upgrading VMware tools on vm W2003 R2

[CBO42113]

Dear all,

i have an issue on several vm running W2003 R2 when trying to upgrade VMware tools.

We have a vCenter Server 4.1.0 build 258909 with 2 hosts : 1 with ESXi 4.1.0 260247, 1 with ESX 4.0 261974 (goal is to replace ESX 4.0 by ESXi 4.1 on the seconf host when all 4.1 upgrade issues will be solved).

On several vm running W2003 hosted on ESXi 4.1, each time i try to upgrade vmware tools (to version 8.3.2, build 257589), Windows crah on startup for hardware issue.

I have tried to uninstall previous VMware tools before installing new version, but same issue.

These vm are running well on host ESXi 4.1 with VMware tools 4.0.0 build 261974.

Does someone else experience a similar problem ?

Thank you,

Christophe

[AntonVZhbankov]

Can you create new VM, install Windows and then VMware Tools from the scratch?

---

MCSA, MCTS Hyper-V, VCP 3/4, VMware vExpert

http://blog.vadmin.ru

[CBO42113]

I guess I won't have any issue with a Windows from scratch, as i have no issue with most of th vm.

We have 15 vm with Windows 2003, and only 5 with this issue.

[AntonVZhbankov]

These VMs must have something in common.

---

MCSA, MCTS Hyper-V, VCP 3/4, VMware vExpert

http://blog.vadmin.ru

[CBO42113]

To undestand the issue, I have uninstall VMware tools and restart Windows.

Still BSOD on startup on ESXi 4.1, but If I move the vm on ESX 4.0, its OK ??

Christophe

[CBO42113]

Stil the problem. I'm wiorking on this issue with 1 vm to solve it for te others.

Now I can start up normally a vm, but each time I try to reboot Windows from the vm, bsod on startup.

If the vm is powered off and power on, startup is OK.

This happens only on the ESXi 4.1 server, if I migrate the vm on the other ESX 4.0, no problem.

[CBO42113]

Dear all,

I have found this issue :it was the number of processors. If I reduce the vm to one processor, no more bsod on restart.

This is a strange issue, vm crash only when restarting Windows (no problem when using reset or power off)

I guess there is something changed in ESX 4.1 with CPU hyperthreading.

I will keep vmware suport informed about this.

Christophe

[mlarchet]

Hello,

I'm running into the exact same problem.

Did you have any answer from VMware support ?

I'm considering opening my own case because it's very annoying and I'm already late on my 4.1 migration schedule.

[CBO42113]

Hello,

yes, VMware technical Support has confirmed the bug (after log analysing).

They wrote to me that it should be solved in next release :

---

Message d'origine----- De : VMware Technical Support Envoyé : mercredi 6 octobre 2010 14:50 À : xxxxxxx Objet : RE: VMware Support Request SR# 1564061771

DO NOT CHANGE THE SUBJECT LINE if you want to respond to this email.

Bonjour Mr XXXX,

Mon nom est xxxx, ingénieur de support technique à VMware. Nous nous sommes entretenus au téléphone a l'instant.

Je vous confirme la fermeture de ce dossier comme convenu lors de notre conversation.

Il est vraisemblable que ce problème sera régler dans la prochaine version.

"It is likely that this problem will be resolved in the next version."

[mlarchet]

Il semble que vous soyez Français alors je vous réponds de la même façon.

Votre message date déjà de 2009, je suis étonné que ce problème n'ait pas été corrigé depuis.

Je crois que je vais réouvrir un ticket auprès du support.

Merci beaucoup pour votre réponse.

[CBO42113]

Non, le message date d'octobre 2010. le problème est consécutif à l'upgrade 4.1 du mois d'août 2010.