vmhgfs module not compilable for VMware Tools 9.9.0 (Fusion7.1) and VMware Tools 9.9.2 (Fusion7.1.1 Build 2496486) after Ubuntu Linux kernel update to 3.13.0-46-generic (Febr. 2015) (Shared Folder Feature of VMware Tools not working in Ubuntu 14.04 LTS (Guest) on MacOSX Yosemite (Host))?
Hello Community and the VMware Developer Team,
On February, 13th 2015 we lost the Shared Folder Feature between Ubuntu and MacOSX. Probably, the update of the Linux kernel to 3.13.0-46-generic caused this problem (although the existing, compiled vmhgfs module of the VMware Tools in Ubuntu wouldn't be damaged by the Linux kernel update!). We use VMware Fusion 7.0.0 with Ubuntu 14.04 LTS and MacOSX for one year without problems with older Linux kernels.
We updated to VMware Fusion 7.1.0 and Fusion7.1.1 Build 2496486 with VMware Tools 9.9.2 in the hope to fix the Shared Folder Feature problem that occured first in vers. 7.0.0.
We can suppose that there is an incompatibility between the compiled vmhgfs module and the new Linux kernel 3.13.0-46-generic.
We tried to reinstall VMware tools 9.9.0 and vers. 9.9.2 but the vmhgfs module couldn't be compiled and the Shared Folder Feature is not working. All other VMware tool features are working fine.
1. In Ubuntu 14.04 LTS the terminal command lsmod | grep "vm." lists no vmhgfs module
2. During vmhgfs module compilation there were several "errors" near "/vmhgfs-only/" and "make[]:"
Here is one of our terminal journals for you:
"
include/linux/compiler-gcc4.h:14:34: error: ‘struct dentry’ has no member named ‘d_alias’
#define __compiler_offsetof(a,b) __builtin_offsetof(a,b)
^
include/linux/stddef.h:17:31: note: in expansion of macro ‘__compiler_offsetof’
#define offsetof(TYPE,MEMBER) __compiler_offsetof(TYPE,MEMBER)
^
include/linux/kernel.h:794:29: note: in expansion of macro ‘offsetof’
(type *)( (char *)__mptr - offsetof(type,member) );})
^
include/linux/list.h:687:40: note: in expansion of macro ‘container_of’
#define hlist_entry(ptr, type, member) container_of(ptr,type,member)
^
include/linux/list.h:698:15: note: in expansion of macro ‘hlist_entry’
____ptr ? hlist_entry(____ptr, type, member) : NULL; \
^
include/linux/list.h:710:13: note: in expansion of macro ‘hlist_entry_safe’
pos = hlist_entry_safe((pos)->member.next, typeof(*(pos)), member))
^
/tmp/modconfig-h4Zwi0/vmhgfs-only/inode.c:1920:7: note: in expansion of macro ‘hlist_for_each_entry’
hlist_for_each_entry(dentry,
^
make[2]: *** [/tmp/modconfig-h4Zwi0/vmhgfs-only/inode.o] Error 1
make[1]: *** [_module_/tmp/modconfig-h4Zwi0/vmhgfs-only] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-3.13.0-46-generic'
make: *** [vmhgfs.ko] Error 2
make: Leaving directory `/tmp/modconfig-h4Zwi0/vmhgfs-only'
"
3. And /mnt/hgfs is empty but folder sharing is enabled for Mac's "Documents" directory for example. If we run vmware-hgfsclient in a terminal, we get the list of shared folders but /mnt/hgfs is empty.
Could you fix the incompatibility between the vmhgfs module and the new Linux kernel 3.13.0-46-generic, please?
Best regards,
Toni
Far too little and far too late for me, moving on was easier than I thought.
Ray
In case it matters, I am seeing similar issues with Debian 8, which also incorporates systemd. It was just released. I hope Steve Goddard has time to test with Debian 8 as well.
Likewise. I have successfully installed Ubuntu from an .iso image and also migrated a Fusion VM from instructions at
http://brianflove.com/2014/06/09/vmware-fusion-to-virtual-box/
After migration and installation of Guest Additions, I needed to increase display memory, add myself to the vboxsf group (sudo <username> vboxsf) and reboot.
I will verify Debian 8 and fix any issues I find.
Thanks for reporting!
Steve
steve goddard wrote:
I will verify Debian 8 and fix any issues I find.
Thanks for reporting!
Steve
Sorry to hijack the thread, but I found this issue with Debian 8 as well.
With at least one desktop environment (Cinnamon, probably others), an error dialog box appears after login:
"Running in software rendering mode - Cinnamon is currently running without video hardware acceleration and, as a result, you may observe much higher than normal CPU usage. There could be a problem with your drivers or some other issue. For the best experience, it is recommended that you only use this mode for troubleshooting purposes."
I installed gcc, make, and the kernel headers. After that I installed the latest VMware Tools, version 9.9.2.44151 (build-2496486) (Note: there is an error building VMware Tools related to file sharing, as we already know.) After that, I rebooted the VM. The dialog box still appears.
... This is FYI for Steve's testing only. Back to the Shared Folder Feature not working thread...
Hi again,
I have verified the Shared Folders driver component builds and installs in Debian 8 RC2 (linux kernel 3.16.0-4) and shares are accessible.
I will keep an eye on further release candidates too to see if anything other issues come up.
FYI I installed it with the Gnome desktop, which did not raise any issues. This was using Workstation as not my Mac.
However, I will verify the same on the Mac with Fusion on Monday for the desktop environment.
The kernel driver component will be the same for both Workstation and Fusion.
Thanks
Steve
Hi Steve - Thanks for taking the time to do the additional testing.
The "Running in software rendering mode / without video hardware acceleration" error appears with Cinnamon. I did the basic non-graphical install from the downloaded 64-bit DVD ISO image. When the prompt appears to choose features (e.g., Desktop, SSH server, Print Server etc.), I chose the default other than adding Cinnamon by cursoring down the list and pressing the space bar to select Cinnamon. An asterisk appears. At the time, I was trying various desktop environments to see which one I prefer.
I do not know whether this is an important issue related to video drivers, or a corner case that can be ignored. I trust your judgement on that.
This is a big headache. I have Yosemite 10.10.3 Host and Ubuntu Studio Ubuntu 14.04.2 LTS.
Anyway to expedite a fix?
Any temporary workaround?
Thanks
You've basically got three options:
1. Patch the code yourself. I know this seems strange, it's not as if you paid good money in the first place with the expectation that software updates would be made available in an expeditious manner.
2. Develop the patience of a Saint. This may involve waiting for the next major release of Fusion and forking out even more money for future software updates that fail to materialise.
3. Ditch Fusion and transition to VirtualBox. You can even use existing disk images. It works. I'll admit it's not quite as polished as Fusion. But did I mention, it works! And best of all, it's free! And, IT WORKS!
VMWare have really dropped the ball here.
I'll leave it up to you as to which option I, and I suspect, many other dissatisfied VMWare Fusion users have chosen. I'd have used the expression 'ex-customers' instead of 'users' but that may have been a little too obvious.
I feel your pain Palomnik, I really do. What you do next is up to you. It is, after all, blatantly clear that VMWare couldn't care less. They have your money. And they will continue to behave the way they are until people stop giving it to them.
I too have been hit by this issue. I raised a support ticket with VMWare, who called back and suggested I try the workaround here: http://askubuntu.com/a/592127
I tried the script suggested to patch the source. This fixed vmhgfs for me with Fusion 7.1.1 on OSX 10.10.3 host, with Ubuntu 14.04 guest, and has worked with kernel updates since - currently I'm on 3.13.0-52.
That workaround was quicker for me than moving to VirtualBox, but I am disappointed that there is still no official fix after all this time. A FUSE based replacement for vmhgfs would be good.
I was sent a private message, but the system does not allow my to hit "reply". This is the requested info:
root@ubuntu:~# vmware-config-tools.pl
Initializing...
Making sure services for VMware Tools are stopped.
vmware-tools-thinprint stop/waiting
vmware-tools stop/waiting
The module vmci has already been installed on this system by another installer
or package and will not be modified by this installer.
The module vsock has already been installed on this system by another installer
or package and will not be modified by this installer.
The module vmxnet3 has already been installed on this system by another
installer or package and will not be modified by this installer.
The module pvscsi has already been installed on this system by another
installer or package and will not be modified by this installer.
The module vmmemctl has already been installed on this system by another
installer or package and will not be modified by this installer.
The VMware Host-Guest Filesystem allows for shared folders between the host OS
and the guest OS in a Fusion or Workstation virtual environment. Do you wish
to enable this feature? [yes]
Before you can compile modules, you need to have the following installed...
make
gcc
kernel headers of the running kernel
Searching for GCC...
Detected GCC binary at "/usr/bin/gcc".
The path "/usr/bin/gcc" appears to be a valid path to the gcc binary.
Would you like to change it? [no]
Searching for a valid kernel header path...
Detected the kernel headers at
"/lib/modules/3.13.0-52-lowlatency/build/include".
The path "/lib/modules/3.13.0-52-lowlatency/build/include" appears to be a
valid path to the 3.13.0-52-lowlatency kernel headers.
Would you like to change it? [no]
Using kernel build system.
make: Entering directory `/tmp/modconfig-toB78q/vmhgfs-only'
/usr/bin/make -C /lib/modules/3.13.0-52-lowlatency/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.13.0-52-lowlatency'
CC [M] /tmp/modconfig-toB78q/vmhgfs-only/backdoor.o
CC [M] /tmp/modconfig-toB78q/vmhgfs-only/backdoorGcc64.o
CC [M] /tmp/modconfig-toB78q/vmhgfs-only/bdhandler.o
CC [M] /tmp/modconfig-toB78q/vmhgfs-only/cpName.o
CC [M] /tmp/modconfig-toB78q/vmhgfs-only/cpNameLinux.o
CC [M] /tmp/modconfig-toB78q/vmhgfs-only/cpNameLite.o
CC [M] /tmp/modconfig-toB78q/vmhgfs-only/dentry.o
CC [M] /tmp/modconfig-toB78q/vmhgfs-only/dir.o
CC [M] /tmp/modconfig-toB78q/vmhgfs-only/file.o
CC [M] /tmp/modconfig-toB78q/vmhgfs-only/filesystem.o
CC [M] /tmp/modconfig-toB78q/vmhgfs-only/fsutil.o
CC [M] /tmp/modconfig-toB78q/vmhgfs-only/hgfsBd.o
CC [M] /tmp/modconfig-toB78q/vmhgfs-only/hgfsEscape.o
CC [M] /tmp/modconfig-toB78q/vmhgfs-only/hgfsUtil.o
CC [M] /tmp/modconfig-toB78q/vmhgfs-only/inode.o
In file included from /usr/src/linux-headers-3.13.0-52-lowlatency/arch/x86/include/asm/percpu.h:44:0,
from /usr/src/linux-headers-3.13.0-52-lowlatency/arch/x86/include/asm/preempt.h:5,
from include/linux/preempt.h:18,
from include/linux/spinlock.h:50,
from include/linux/mmzone.h:7,
from include/linux/gfp.h:4,
from include/linux/mm.h:8,
from include/linux/pagemap.h:7,
from /tmp/modconfig-toB78q/vmhgfs-only/inode.c:29:
/tmp/modconfig-toB78q/vmhgfs-only/inode.c: In function ‘HgfsPermission’:
include/linux/kernel.h:793:27: error: ‘struct dentry’ has no member named ‘d_alias’
const typeof( ((type *)0)->member ) *__mptr = (ptr); \
^
include/linux/list.h:687:40: note: in expansion of macro ‘container_of’
#define hlist_entry(ptr, type, member) container_of(ptr,type,member)
^
include/linux/list.h:698:15: note: in expansion of macro ‘hlist_entry’
____ptr ? hlist_entry(____ptr, type, member) : NULL; \
^
include/linux/list.h:708:13: note: in expansion of macro ‘hlist_entry_safe’
for (pos = hlist_entry_safe((head)->first, typeof(*(pos)), member);\
^
/tmp/modconfig-toB78q/vmhgfs-only/inode.c:1920:7: note: in expansion of macro ‘hlist_for_each_entry’
hlist_for_each_entry(dentry,
^
include/linux/kernel.h:793:48: warning: initialization from incompatible pointer type [enabled by default]
const typeof( ((type *)0)->member ) *__mptr = (ptr); \
^
include/linux/list.h:687:40: note: in expansion of macro ‘container_of’
#define hlist_entry(ptr, type, member) container_of(ptr,type,member)
^
include/linux/list.h:698:15: note: in expansion of macro ‘hlist_entry’
____ptr ? hlist_entry(____ptr, type, member) : NULL; \
^
include/linux/list.h:708:13: note: in expansion of macro ‘hlist_entry_safe’
for (pos = hlist_entry_safe((head)->first, typeof(*(pos)), member);\
^
/tmp/modconfig-toB78q/vmhgfs-only/inode.c:1920:7: note: in expansion of macro ‘hlist_for_each_entry’
hlist_for_each_entry(dentry,
^
In file included from include/linux/compiler-gcc.h:106:0,
from include/linux/compiler.h:54,
from include/uapi/linux/stddef.h:1,
from include/linux/stddef.h:4,
from /usr/src/linux-headers-3.13.0-52-lowlatency/include/uapi/linux/posix_types.h:4,
from include/uapi/linux/types.h:13,
from include/linux/types.h:5,
from /tmp/modconfig-toB78q/vmhgfs-only/./shared/driver-config.h:71,
from /tmp/modconfig-toB78q/vmhgfs-only/inode.c:26:
include/linux/compiler-gcc4.h:14:34: error: ‘struct dentry’ has no member named ‘d_alias’
#define __compiler_offsetof(a,b) __builtin_offsetof(a,b)
^
include/linux/stddef.h:17:31: note: in expansion of macro ‘__compiler_offsetof’
#define offsetof(TYPE,MEMBER) __compiler_offsetof(TYPE,MEMBER)
^
include/linux/kernel.h:794:29: note: in expansion of macro ‘offsetof’
(type *)( (char *)__mptr - offsetof(type,member) );})
^
include/linux/list.h:687:40: note: in expansion of macro ‘container_of’
#define hlist_entry(ptr, type, member) container_of(ptr,type,member)
^
include/linux/list.h:698:15: note: in expansion of macro ‘hlist_entry’
____ptr ? hlist_entry(____ptr, type, member) : NULL; \
^
include/linux/list.h:708:13: note: in expansion of macro ‘hlist_entry_safe’
for (pos = hlist_entry_safe((head)->first, typeof(*(pos)), member);\
^
/tmp/modconfig-toB78q/vmhgfs-only/inode.c:1920:7: note: in expansion of macro ‘hlist_for_each_entry’
hlist_for_each_entry(dentry,
^
In file included from include/linux/preempt.h:10:0,
from include/linux/spinlock.h:50,
from include/linux/mmzone.h:7,
from include/linux/gfp.h:4,
from include/linux/mm.h:8,
from include/linux/pagemap.h:7,
from /tmp/modconfig-toB78q/vmhgfs-only/inode.c:29:
include/linux/list.h:710:35: error: ‘struct dentry’ has no member named ‘d_alias’
pos = hlist_entry_safe((pos)->member.next, typeof(*(pos)), member))
^
include/linux/list.h:697:12: note: in definition of macro ‘hlist_entry_safe’
({ typeof(ptr) ____ptr = (ptr); \
^
/tmp/modconfig-toB78q/vmhgfs-only/inode.c:1920:7: note: in expansion of macro ‘hlist_for_each_entry’
hlist_for_each_entry(dentry,
^
include/linux/list.h:710:35: error: ‘struct dentry’ has no member named ‘d_alias’
pos = hlist_entry_safe((pos)->member.next, typeof(*(pos)), member))
^
include/linux/list.h:697:28: note: in definition of macro ‘hlist_entry_safe’
({ typeof(ptr) ____ptr = (ptr); \
^
/tmp/modconfig-toB78q/vmhgfs-only/inode.c:1920:7: note: in expansion of macro ‘hlist_for_each_entry’
hlist_for_each_entry(dentry,
^
In file included from /usr/src/linux-headers-3.13.0-52-lowlatency/arch/x86/include/asm/percpu.h:44:0,
from /usr/src/linux-headers-3.13.0-52-lowlatency/arch/x86/include/asm/preempt.h:5,
from include/linux/preempt.h:18,
from include/linux/spinlock.h:50,
from include/linux/mmzone.h:7,
from include/linux/gfp.h:4,
from include/linux/mm.h:8,
from include/linux/pagemap.h:7,
from /tmp/modconfig-toB78q/vmhgfs-only/inode.c:29:
include/linux/kernel.h:793:27: error: ‘struct dentry’ has no member named ‘d_alias’
const typeof( ((type *)0)->member ) *__mptr = (ptr); \
^
include/linux/list.h:687:40: note: in expansion of macro ‘container_of’
#define hlist_entry(ptr, type, member) container_of(ptr,type,member)
^
include/linux/list.h:698:15: note: in expansion of macro ‘hlist_entry’
____ptr ? hlist_entry(____ptr, type, member) : NULL; \
^
include/linux/list.h:710:13: note: in expansion of macro ‘hlist_entry_safe’
pos = hlist_entry_safe((pos)->member.next, typeof(*(pos)), member))
^
/tmp/modconfig-toB78q/vmhgfs-only/inode.c:1920:7: note: in expansion of macro ‘hlist_for_each_entry’
hlist_for_each_entry(dentry,
^
include/linux/kernel.h:793:48: warning: initialization makes pointer from integer without a cast [enabled by default]
const typeof( ((type *)0)->member ) *__mptr = (ptr); \
^
include/linux/list.h:687:40: note: in expansion of macro ‘container_of’
#define hlist_entry(ptr, type, member) container_of(ptr,type,member)
^
include/linux/list.h:698:15: note: in expansion of macro ‘hlist_entry’
____ptr ? hlist_entry(____ptr, type, member) : NULL; \
^
include/linux/list.h:710:13: note: in expansion of macro ‘hlist_entry_safe’
pos = hlist_entry_safe((pos)->member.next, typeof(*(pos)), member))
^
/tmp/modconfig-toB78q/vmhgfs-only/inode.c:1920:7: note: in expansion of macro ‘hlist_for_each_entry’
hlist_for_each_entry(dentry,
^
In file included from include/linux/compiler-gcc.h:106:0,
from include/linux/compiler.h:54,
from include/uapi/linux/stddef.h:1,
from include/linux/stddef.h:4,
from /usr/src/linux-headers-3.13.0-52-lowlatency/include/uapi/linux/posix_types.h:4,
from include/uapi/linux/types.h:13,
from include/linux/types.h:5,
from /tmp/modconfig-toB78q/vmhgfs-only/./shared/driver-config.h:71,
from /tmp/modconfig-toB78q/vmhgfs-only/inode.c:26:
include/linux/compiler-gcc4.h:14:34: error: ‘struct dentry’ has no member named ‘d_alias’
#define __compiler_offsetof(a,b) __builtin_offsetof(a,b)
^
include/linux/stddef.h:17:31: note: in expansion of macro ‘__compiler_offsetof’
#define offsetof(TYPE,MEMBER) __compiler_offsetof(TYPE,MEMBER)
^
include/linux/kernel.h:794:29: note: in expansion of macro ‘offsetof’
(type *)( (char *)__mptr - offsetof(type,member) );})
^
include/linux/list.h:687:40: note: in expansion of macro ‘container_of’
#define hlist_entry(ptr, type, member) container_of(ptr,type,member)
^
include/linux/list.h:698:15: note: in expansion of macro ‘hlist_entry’
____ptr ? hlist_entry(____ptr, type, member) : NULL; \
^
include/linux/list.h:710:13: note: in expansion of macro ‘hlist_entry_safe’
pos = hlist_entry_safe((pos)->member.next, typeof(*(pos)), member))
^
/tmp/modconfig-toB78q/vmhgfs-only/inode.c:1920:7: note: in expansion of macro ‘hlist_for_each_entry’
hlist_for_each_entry(dentry,
^
make[2]: *** [/tmp/modconfig-toB78q/vmhgfs-only/inode.o] Error 1
make[1]: *** [_module_/tmp/modconfig-toB78q/vmhgfs-only] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-3.13.0-52-lowlatency'
make: *** [vmhgfs.ko] Error 2
make: Leaving directory `/tmp/modconfig-toB78q/vmhgfs-only'
The filesystem driver (vmhgfs module) is used only for the shared folder
feature. The rest of the software provided by VMware Tools is designed to work
independently of this feature.
If you wish to have the shared folders feature, you can install the driver by
running vmware-config-tools.pl again after making sure that gcc, binutils, make
and the kernel sources for your running kernel are installed on your machine.
These packages are available on your distribution's installation CD.
[ Press Enter key to continue ]
The vmxnet driver is no longer supported on kernels 3.3 and greater. Please
upgrade to a newer virtual NIC. (e.g., vmxnet3 or e1000e)
The vmblock enables dragging or copying files between host and guest in a
Fusion or Workstation virtual environment. Do you wish to enable this feature?
[yes]
VMware automatic kernel modules enables automatic building and installation of
VMware kernel modules at boot that are not already present. This feature can be
enabled/disabled by re-running vmware-config-tools.pl.
Would you like to enable VMware automatic kernel modules?
[no]
Thinprint provides driver-free printing. Do you wish to enable this feature?
[yes]
Disabling timer-based audio scheduling in pulseaudio.
Do you want to enable Guest Authentication (vgauth)? [yes]
Detected X server version 1.15.1
Distribution provided drivers for Xorg X server are used.
Skipping X configuration because X drivers are not included.
Creating a new initrd boot image for the kernel.
update-initramfs: Generating /boot/initrd.img-3.13.0-52-lowlatency
vmware-tools-thinprint start/running
vmware-tools start/running
The configuration of VMware Tools 9.9.2 build-2496486 for Linux for this
running kernel completed successfully.
You must restart your X session before any mouse or graphics changes take
effect.
You can now run VMware Tools by invoking "/usr/bin/vmware-toolbox-cmd" from the
command line.
To enable advanced X features (e.g., guest resolution fit, drag and drop, and
file and text copy/paste), you will need to do one (or more) of the following:
1. Manually start /usr/bin/vmware-user
2. Log out and log back into your desktop session; and,
3. Restart your X session.
Enjoy,
--the VMware team
root@ubuntu:~#
Thanks to all who responded, especially Retry111, who provided the link to the script. I ran the script and then vmware-tools-config.pl and that fixed it!
Now I will have to check my Debian instance and see if there is a fix for that. It would be really nice if VMware does an official fix soon.
Well the patch *was* working, but of course I just *had* to upgrade to Ubuntu Studio 15.04 (Vivid Vervet) and now it is not!
I'm really hoping that vmware brings fusion up to date, but I have to ask again if there is any workaround for 15.04?
TIA
I installed yesterday debian 8 jessie and tried the patch, but it didn't work for me. I also hope that we will get soon an update of vmware.
I know that we discussed the opportunity to supply the tools separated from vmware upgrades. I even think that it would be better. We see it this time. We are waiting now three months for a solution, that by the way exists, only cause the upgrade of vmware is not ready yet. It isn't really a good picture.
I hate to pile on but... it's June. Our installations of VMWare Fusion have been fscked since February!
In the past I've recommended VMWare to a couple of purchasing departments and now it has turned into a support nightmare as more new developers either upgrade or follow our documentation (which still foolishly implies that Fusion actually works as advertised). The status of this outstanding issue is painful and expensive and ensures that VMWare will never receive my money again.
Fusion 8 is just around the corner. You'll be able to upgrade for the low price of $$$.
I can't help but think that a new version will be released to coincide with the new release of Windows. Odds are it'll support the latest Linux kernels too.
Until then.... <tumbleweed>
I'm using Vagrant/VirtualBox.
I am tired of fussing with VMWare
AdrianDay wrote:
Fusion 8 is just around the corner. You'll be able to upgrade for the low price of $$$.
I can't help but think that a new version will be released to coincide with the new release of Windows. Odds are it'll support the latest Linux kernels too.
Until then.... <tumbleweed>
I came to the same conclusion weeks ago. I concluded that the tested fixes are not likely to be released as an update to Fusion 7, but as an upgrade to Fusion 8. The last few years, upgrades have appeared at the end of summer, and the best predictor of future behavior is past behavior. In my opinion, Fusion 7 has been a fiasco for many users, and I wonder whether the incremental improvements from Fusion 6 to Fusion 7 were worth it. Most of the performance improvements do not apply to my primary mid-2011 iMac Ivy Bridge computer anyway.
I use Fusion because:
* VMware is an industry standard that is well supported on Mac, Windows, and Linux. VMware-based virtual machines can be easily moved from one operating system platform to another, and I have been able to share them at work as we develop and test our own cross-platform software. It is what many companies use.
* Fusion costs are lower for me at home compared with Parallels, especially because one license extends to my family's computers - I have college age children at home.
* Inertia - I have used VMware Fusion for many years, and have built up experience with it. Who want to start over with a new product?
Please excuse me for bashing the company on its own forums. I try to be supportive overall.
The fact that the last official answer is more than one month old is speaking for themselves. Now I/we have few months to decide how The Capitan will virtually host other operating systems.
I finally solved my problems by rolling back to the last supported (or at least working) releases. I use VMware Workstation on a PC and VMware Fusion on 2 macs where I have VMs for windows 7, Ubuntu Studio and a Debian (server) instance. I have just started playing with vagrant (Vagrant) which adds auto building and auto provisioning magic to creating VMs. It works with VMware, but works out of the box with VirtualBox, so I have been trying that. Virtualbox is open source. The performance and support is not as good as VMware, But if VMware turns into crippleware due to lack of support, I may have to give it another think before renewing the VMware licenses.