[sles-beta] SLES12 Beta7 x86_64 vmtoolsd now activated automatically?

[Marcus Meissner]

Hi,

The autostart was actually requested by our partner VMWare itself.

Ciao, Marcus
On Mon, May 26, 2014 at 11:51:55AM +0000, urs.frey at post.ch wrote:
> Hi
> 
> When installing SLES12 x86_64 Beta7 on VMware ESX I can see that the vmtoolsd gets activated automatically
> 
> I state that this is unwanted, as the support state of the SLES12 included open-vm-tools is not clear with VMware
> Within the changelog Beta6-> Beta7 there is nothing mentioned.
> 
> -----------------------------------------------------------------------------
> 
> o Updated open-vm-tools (security/bugfix/feature)       [x86_64]
> 
> - Modify vmware-user-autostart-wrapper to unconditionally start
>   vmware-user-suid-wrapper, and no longer delay for vmblock-fuse
>   if under systemd. (bnc#876074)
> - added forgotten %pre snippet for service addition, this made
>   systemd service not auto-start. bnc#870737
> - Set ExclusiveArch to x86_64 only (for SLE-12).
> 
> -----------------------------------------------------------------------------
> 
> With SLES12 I need to have a platform working on VMware ESX in a supported state.
> Today with open-vm-tools I still have the "unsupported, third party state" in the v-sphere console
> 
> This is not feasible for production environment
> 
> If I need to install the professional VMwareTools coming with ESX there should be an easy way to remove, or to lock the installation of open-vm-tools
> No automatic activation of open-vm-tools please.
> 
> Best regards
> 
> Urs Frey
> Post CH AG
> Informationstechnologie
> IT Betrieb
> Webergutstrasse 12
> 3030 Bern (Zollikofen)
> Telefon : ++41 (0)58 338 58 70
> FAX     : ++41 (0)58 667 30 07
> E-Mail:   urs.frey at post.ch<mailto:urs.frey at post.ch>
> 
> 
> 

> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta