VMware Fusion

Hello Zoya,

Thanks for using Apple Support Communities.

I see from your post that you're getting an error that the Module Disk power on failed with VMWare Fusion on your new OS X El Capitan installation. As I currently see it, OS X El Capitan (10.11) is not yet listed in the VMWare Fusion list of supported Guest OS's. I suggest that you get in contact with the VMWare support for any further troubleshooting.

Support | United States

VMware Support Contact Options | United States

Take care.

Same problem here.

VMWare Fusion under El Capitan does not start Windows on Bootcamp anymore.

Importing bootcamp completely new to VMWare Fusion does not help.

zoya83

compatible with El Capitan (atleast with the Beta-version)

update your VMFusion

http://store.vmware.com/store/vmware/html/pbPage.windows10

Newest version is installed.

Macs Pain wrote:

Same problem here.

VMWare Fusion under El Capitan does not start Windows on Bootcamp anymore.

Importing bootcamp completely new to VMWare Fusion does not help.

VMWare Fusion (version 7.1 and 7.1.2) works fine on El Capitan (7.1.2 recommended)

Macs Pain wrote:

Newest version is installed.

Which version is that?

First off, can you still boot natively into your Bootcamp install? I believe I have seen

some Bootcamp install issues after 10.11 update.

FWIW, my normal VMWare Fusion VMs seem to be working just fine with Fusion 8.01

and 10.11 (Win10 and Win8 on my late 2013 iMac and Win10 on my early 2011, 13", 2.7Gz i7

MacbookPro).

VMWare Fusion version is 8.01

Booting directly in bootcamp works.

I can post the error messages that come from VMWare but they are in german.

They say something like " the medium "/Users/peter/Library/Application Support/VMware Fusion/Virtual Machines/Boot Camp/Boot Camp.vmwarevm/Boot Camp.vmdk" can not be opened, the VM can not be started.

Trying with the new imported bootcamp, it first looks like it would start, then the error appears that i'm not allowed to get access to that partition but I can click on "Allow". Doing this, the next message is "The data system on which the hard disk "/dev/rdisk1s1" is located is full" or something like this. Clicking on try again does nothing and Cancel makes VMWare crash.

Macs Pain wrote:

....

They say something like " the medium "/Users/peter/Library/Application Support/VMware Fusion/Virtual Machines/Boot Camp/Boot Camp.vmwarevm/Boot Camp.vmdk" .....

For one thing, that is a very odd location for the VM file and could be part of the problem as

/Library is not normally available for access. All my VMs were defaulted as locating in

/Users/"my user name"/Documents/Virtual Machines. Try recreating the VM again and change

where the VM is saved.

Agreed, that is not the place where VMWare saved it's data files in earlier versions (which was on the same path as you report)

Hmm. I never changed that. I thought that was the standard location.

But I even can not find where to change that in VMWare.