Please confirm that a proper fix for this issue is a priority for the Fusion team. We're coming up on two months since this issue was originally reported on this thread and asking your paying customers to downgrade and patch the tools supplied directly from VMWare for a "Professional" version of Fusion is a very frustrating nuisance.
Yes, Dave, my priority is to get this addressed.
When the releases are made though is beyond my control. A proper fix will be made to get all the known issues addressed. It just happens to be a complicated issue to get the caching within the VM correct and not miss host side updates in-between uses. I apologize that it is not a quick fix and out in very short order, which is why I am spending a lot of time just keeping everyone running with the 6.0.1 tools correctly until that change is correctly addressed.
Thanks for acknowledging the high priority to fix this, Steve. I appreciate the fact that it is a complicated issue and the schedule is beyond your control.
It seems that VMware have a rather poor strategy to updating and testing the tools and fixes are reactive rather than proactive. This renders a major feature of Fusion unusable and it seems there is no sense of urgency to resolve the problem. This is not the first time either that there have been major issues with the tools. There was the issue that required a symlink to version.h (I don't remember which kernel version) or the installer failed to see the kernel headers. Also, back in May last year I blogged about the multiple compile issues with tools and Ubuntu 13.04, or more specifically the 3.8 kernel. At the time of writing Ubuntu 13.04 had been available a month and the kernel released for over 3 months (plus there would have been beta and RC releases prior to this) and to this day I'm still getting messages and comments thanking me for the post compiling all the various fixes together (not just from Fusion users either).
This bug does not even relate to external changes but an internal VMware change so also suggests a serious failure in testing/quality control, which I find unacceptable for company the size of VMware. What are VMware doing to ensure that bug fixes and support for future kernel/OS releases are provided in a timely manor? Also, what are you doing to ensure such catastrophic failures are not going to be repeated in future versions of your software?
yes what I posted is what I did. Things work smoothly now.
By the way, do you know if Unity with a macos host and Ubuntu guest will be supported soon?
It's been a little over a month since the last status update. Is a standard update to the tools still in progress? Is there any kind of timeline that can be shared?
Yes there are many releases going to be hitting the streets.
Since there has been some especially urgent issues that are going out probably ahead of this.
I am still working on this issue with a couple of security related changes.
Excellent - great news!
(Please please don't let 6.0.3 ship without this issue getting properly sorted)
To get around this problem for now, I am mounting the folder using NFS and not using hgfs.
Does anyone know how to get rid of the 'The virtual machine must have up-to-date Vmware Tools installed and running' message on the screen? It sits on top of every window and is a real pain.
Is there any more info on when this is going to be released? I run my local dev environments off of fusion and whenever I save a file to the shared drive it still truncates with 6.0.1. If I add a new line and keep doing it I can eventually get it to work, but it is getting really old having to save a file 5 times before it is seen correctly on the vm. If there is a way you guys know to get around this aside from editing it directly on the vm it would be appreciated.
+1 it would be great to get an update.
I have this issue fixed in house but am waiting on getting it into the next tools releases.
It is VMware policy that I am not allowed to state when that will be.
I hope it is not too long.
I will update here again when I know for sure which release it will be included in but even then all I will be able to say is watch out and update your tools when you see it.
When it does become public I will also update to say that you should be able to download and install.
Thanks so much for your patience with this frustrating issue.
Steve, we very much appreciate the update. I am just excited to see something about it being fixed! We'll stay tuned.
You might think you have 6.0.1, when in reality you have 6.0.2. Unless you make a change in your .vmx settings, installing 6.0.1 will actually install the buggy 6.0.2
Run this from your command line:
You should see build-1294478 in the output; if you see build-1378637 then you have the 6.0.2 tools installed.
To fix this problem, you will need to change your .vmx settings and then reinstall 6.0.1
Read Steve's post here.
After I did that, the truncating problem stopped.