I'm running version 7 on one machine and am struggling to find any real benefit in "upgrading". My other machines are running 8.5 and I really can't see any significant new Fusion features. Sorry, but a UI tweak and touch bar support doesn't cut the mustard for splashing out on "the latest version".
And as for Mike's marketing blog... gosh. Almost surprised he didn't mention the shiny new logo as a benefit.
I have tried this to fix the same problem on my computer. I am running Mojavi and a win10 machine (guest). once installed version 11 i lost all of my USB ports and VMtools is not working to remove or reinstall. It says it is missing a file in the temp forlder (the .MSI for the installer)
I've just updated to Mojave and installed Fusion 11 as a trial. With that said, perhaps I'm doing something wrong, but it looks more like a bug.
When I select a file in Fusion and right click "open with," or for that matter, when I select a Mac application (I've tried Photoshop and just the Calendar app) that I've added to the Windows 7 start menu, it will not open. I can see the quick flash of an icon on the end of the Mac dock as it tries to open, but it closes immediately, even before I see a window on the mac desktop.
I've looked through the console but didn't see anything obvious.
I've searched a bunch of different terms Googling this, but all I get back are entries on Fusion not starting, which is not the issue here.
Any suggestions on what to try?
Hi, Eskimoke
Sorry for such thing happens.
In such case, we need the log files to find the root cause at your side.
Would you please collect and send it to us please?
1. Make sure the vm is powered off
2. Open VM settings > Advanced > TroubleShooting and choose Hang/Cash
3. Try to power on the VM
4. Fusion main menu > Help > Collect Support Information
5. A zip file will be generated and would you please send it to us?
If the log files size is big, would you please send it to my Dropbox file request?
Thanks and best regards
Hi EMR, Could you send your contact info to my email, hkang@vmware.com? Our support team to contact you to investigate and collect logs if you are OK with it. Sorry for the inconvenience and thanks for your support!
I found the possible reason to my problem:
Because i prefer the 'Light Dark'-Mode from High Sierra (only Menu bar and Dock in black),
i tried following workaround in Terminal:
> defaults write -g NSRequiresAquaSystemAppearance -bool Yes
=> It worked and Fusion 11 did too.
Then i undid that command with:
> defaults write -g NSRequiresAquaSystemAppearance -bool False
=> my W10-VM in Fusion 11 went blank.
I rechecked with:
> defaults write -g NSRequiresAquaSystemAppearance -bool Yes=> the Win10-VM was fine again.
Now i don't know why that happens exactly, but at least i can use Fusion 11 again.
Regards,
GH
Sorry seams i copy not the hole link !
so here you go a brnad new Error Report :Dropbox - VMware Fusion Problem Report 2018-10-01 at 17.20.21.ziphttps://www.dropbox.com/s/8vd2gorexrc87tk/VMware%20Fusion%20Problem%20Report%202018-10-01%20at%2017.20.21.zip?dl=0
hope this works !
sincerly
jarre
Thanks, but I can no longer proceed along that route, as I have finally updated my Mojave DP11 to macOS Mojave 10.14.1 beta1 via Software Update of System Preferences. As I said, I was unable to update to the release version of Mojave from DP11, as the installer (run in Mojave DP11) complained about the non-Metal GPU. Oddly enough, a Software Update is not as stringent as running the regular installer. In any case, I suppose Fusion 11 is capable of creating a brand-new Mojave virtual machine from scratch using the installer. The problem is in running the installer in a previous version of macOS on a virtual machine, because the Installer (not Mojave itself) doesn't see the virtual GPU as a valid Metal card.
I tried adding the CCID settings one at a time.
With the 'usb.generic.allowCCID = "TRUE"' setting I am seeing the Yubikey device in shared passthrough mode:
With the 'usb.ccid.disable = "TRUE"' setting I do not see the Yubikey device at all:
I know that with the 2017 MacBrook Pro I have USB type C connectors and I am using dongles/adapters.
However I have other devices that are connected via these dongles and are working fine (mouse, keyboard, monitor, etc.).
So I am hoping that the Yubikey should also work. Even more so given that I can see it in shared passthrough mode.
I am thinking that I am missing just the right parameter setting.
usb.generic.allowCCID = "TRUE" enables the exclusive mode access to the CCID while usb.ccid.disable = "TRUE" disables the shared CCID.
So it would appear the allowCCID = "TRUE" is not taking effect. I would suspect it might be related to the adapters/dongles. One test would be to connect another USB device such as a USB thumb drive through the same dongle/adapter and see whether it appears in the USB and Bluetooth menu. If you are using the USB type A ports from a Thunderbolt 3 dock, that could also be problem with the USB devices not being visible in the menu to connect to the VM.
As for the Apple USB Keyboard appearing in the 2015 MacBook Pro, it was because of the allowHID setting recommended by the Yubico article. Normally, HIDs are not presented for connection to VMs to avoid the problem that if there is only one USB keyboard or one USB mouse the host loses any keyboard/mouse if the VM gets connected to it.
You could try adding back the quirk line recommened by the Yubico article but I doubt if that would have any effect if the adapters/dongles is the issue. You have to make sure that the vendor ID/device ID in the quirk settings matches the model of Yubikey that you have. It is possible that the device ID could be different if the model is different but the vendor ID should remain the same unless Yubico does not have their own vendor but relies on OEM vendor and if they use different OEMs for different models it might have a different vendor ID. You should be able to see the vendor ID/device ID in the System Report.
BTW, why not via Time Machine?
thanks! working again now
this worked for me! thanks
Two reasons: Time machine backs up files regardless of their being in use, so if the virtual machine is running, you end up with the virtual disk in an inconsistent state. Second, it purges individual files, so you can end up with parts of the disk that were backed up at different times.
last, time machine itself isn't completely reliable - it's notorious for silent corruption, though much better with more recent iterations - as long as you started a completely new backup history.
7 to 11 is a massive upgrade. Vastly improved performance, much higher graphics levels, better cleanup capabilities. And you haven't gotten security patches in years - those VM's shouldn't connect to the internet.
Nope.
Just a side note - OSX can only be virtualized on real apple hardware (if you're trying to put it on PC's). Parallels and Fusion are the only supported options for that.
I'm using a Mac OS X High Sierra on a New Mac Pro Hardware, but it won't let me install a Mac OS X in a Virtual Machine.
I'm so frustrated with Apple these days, first a friend buys an iPhone X, tries to connect it to his iMac and iTunes won't let it because the Mac OS in it is too old, after an upgrade, when the iPhone is connected it won't show in iTunes, now this.
I don't understand how Apple got to be so popular.
I'm having the similar issues on Mojave with VMWare Fusion 8.5.9. It was working just fine for at least a week after I installed Mojave, and I've been running VMs with no problem until today. It appeared to start after I rebooted my machine for the first time since my initial Mojave install. It's not showing up as being blocked under Security & Privacy, and vmmon definitely doesn't exist under /dev. This isn't happening on an install, it just... stopped working. I've tried reinstalling, to no avail.
dev1 at MacBook-Pro in ~
$ kextstat | grep vmware
183 1 0xffffff7f84caa000 0x11000 0x11000 com.vmware.kext.vmci (90.8.1) F7FEC1A0-6065-3C60-82FA-CD514D144D16 <12 5 4 3 1>
184 0 0xffffff7f84cbb000 0x15000 0x15000 com.vmware.kext.vmnet (0752.74.38) 8D3E716A-99B9-3729-BFFD-8F799079DB18 <183 5 4 3 1>
dev1 at MacBook-Pro in ~
$ sudo kextutil /Applications/VMware\ Fusion.app/Contents/Library/kexts/vmmon.kext
(kernel) Kext com.vmware.kext.vmx86 start failed (result 0x5).
(kernel) Kext com.vmware.kext.vmx86 failed to load (0xdc008017).
(kernel) Failed to load kext com.vmware.kext.vmx86 (error 0xdc008017).
Failed to load /Library/StagedExtensions/Applications/VMware Fusion.app/Contents/Library/kexts/vmmon.kext - (libkern/kext) kext (kmod) start/stop routine failed.
Just to complete the info, I tried to do the same on the fixed computer instead of the portable computer and unfortunately the method did not work this time. I guess that it is because I can only unmount one of the two partitions in the external disk (the other one is in use). With the portable computer, I was able to boot with the first partition and the reboot with the second one. This seems to be dead-end. Maybe the only possibility is to raw access the whole disk but not just some partition.
Nevertheless, if you have any suggestion, please let me know.
... And here is an article:
How to Make Linux and macOS Virtual Machines for Free with Parallels Lite
... which explains, among other things, how to create a macOS VM: always interesting, even if it is for a competing product.