We have about 60 ESX servers and use them with various guest OSes (+500 virtual machines). However, we have troubles with SuSE 11.2 as guest OS. To solve the problems, we have to uninstall the open vmware tools and install the “original” VMwareTools from VMware/ESX.
No problem, one might think.
…unless the open vmware tools wouldn’t reinstall themselves every time we enter the YaST software manegement or run YOU. I have four packages regarding kernel and Vmware installed and like to keep it that way:
some-vm# rpm -qa | grep -Ei ‘(kernel|vmware|<\vm>)’ | sort
VMwareTools-7304-213532.i386
kernel-default-2.6.31.12-0.2.1.i586
kernel-source-2.6.31.12-0.2.1.noarch
linux-kernel-headers-2.6.31-3.4.noarch
Whenever I start `yast -i´, add not software but sipmply accept the empty list, it wants to install
kernel-default-devel
libvmtools0
open-vm-tools
vmware-guest-kmp-default
Why? How can I stop this?
We don’t like to install RPMs by hand in the future.
Using YaST set the open VMware tools to Taboo.
HTH.
>
> Hello!
>
> We have about 60 ESX servers and use them with various guest OSes (+500
> virtual machines). However, we have troubles with SuSE 11.2 as guest OS.
> To solve the problems, we have to uninstall the open vmware tools and
> install the “original” VMwareTools from VMware/ESX.
>
> No problem, one might think.
>
> …unless the open vmware tools wouldn’t -reinstall- themselves every
> time we enter the YaST software manegement or run YOU. I have four
> packages regarding kernel and Vmware installed and like to keep it that
> way:
> some-vm# rpm -qa | grep -Ei ‘(kernel|vmware|<\vm>)’ | sort
> VMwareTools-7304-213532.i386
> kernel-default-2.6.31.12-0.2.1.i586
> kernel-source-2.6.31.12-0.2.1.noarch
> linux-kernel-headers-2.6.31-3.4.noarch
> Whenever I start `yast -i´, add not software but sipmply accept the
> empty list, it wants to install
> kernel-default-devel
> libvmtools0
> open-vm-tools
> vmware-guest-kmp-default
> Why? How can I stop this?
>
> We don’t like to install RPMs by hand in the future.
>
> I have removed all those “patterns-” RPMs.
>
> Please help!
> Thank you!
>
>
Did you find any resolution to this? I’m having a similar issue, where all of my other distributions install and run the VMware tools fine, but my OPenSuse 11.2 VM’s all say “unmanaged”