We have a 3.2 farm with and upgraded VC (to 2.5). It has been this way for 6 months and running fine however I have noticed that some guests have tool problems and VMOT times out.
I upgraded a couple of the hosts from 3.2 to 3.5 today (fresh install) and now the few guests I am able to migrate then tell me the tools are out of date in the guest info pane (tab of VC).
Is there any way to fix without re-installing and rebooting guests ? I assume no.
TIA
S
From 3.0.2 to 3.5, I am thinking the update to the tools in the vm would require a reboot. It does not always, but since the tools include kernel modules, there's usually a ramdisk update included as well. Typically, you can load the new driver and you're good to go, but I believe when I went to 3.5, I did have to reboot the vm's.
-KjB
Hello,
Moved to Virtual Machine and Guest OS forum.
All my WIndows Guests reboot automatically after install.... Well it does ask you but you are wiser to reboot. For Linux Guests a Reboot is not required as long as you have console access....
Best regards,
Edward L. Haletky
VMware Communities User Moderator
====
Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.
Blue Gears and SearchVMware Pro Blogs: http://www.astroarch.com/wiki/index.php/Blog_Roll
Top Virtualization Security Links: http://www.astroarch.com/wiki/index.php/Top_Virtualization_Security_Links