Fusion 11 doesn't work with this workaround. I skipped 10, but suspect it was broken in 10 too.
What is the current workaround to stop full-screen modailty?
(Modal screen = one where other windows cannot be placed above it. This is the default for Macs running in full screen, but used to be supported in the big-cat days.)
One of my Fusion VMs got corrupted recently, and it took quite a while to retrieve the data from the virtual disk .vmdk file.
I don't want to go through that again, and therefore would like to implement an automated backup solution. With that in mind, I'm curious what solutions others are using to efficiently backup the data that is stored on the virtual disk to a location outside of the .vmdk file.
Thanks in advance for all suggestions!
Ken
https://www.vimalin.com/ would be the perfect tool by that, authored by wila
Welcome to the Community,
"<vmname>-s00#.vmdk" files make up a virtual disk, and all of them are required.
In many cases disk space issues are caused by unwanted/unneeded/forgotten snapshots "<vmname>-00000x-s00#.vmdk", which may be deleted from within the "Snapshot Manager".
Caution: Deleting such files directly from the file system will cause data corruption and/or loss, and may render the VM unusable!
André
Upgraded from last stable Fusion 10 to Fusion 11 on iMac. Upgraded virtual machine from v10 to v11 as prompted when opening Fusion 11 for first time.
VM is windows 7
Worked fine under Fusion 10, IE Aero and all graphics worked as expected, no error.
With Fusion 11, I get the error from title on booting the VM.
Minimizing/Maximizing windows now appears very choppy, VM at times appears to be sluggish without any apparent use.
Aero no longer works. Aero based themes are able to be selected, but none of the effects are visible.
Did not have the issue with Fusion 10. All worked as expected.
Tried repairing VMTools within the VM, but to no avail.
Not sure what else to try/do, looking for suggestions.
Model Name: iMac
Model Identifier: iMac12,2
Processor Name: Intel Core i7
Processor Speed: 3.4 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 8 MB
Memory: 32 GB
Boot ROM Version: IM121.004F.B00
SMC Version (system): 1.72f1
AMD Radeon HD 6970M:
Chipset Model: AMD Radeon HD 6970M
Type: GPU
Bus: PCIe
PCIe Lane Width: x16
VRAM (Dynamic, Max): 2048 MB
Vendor: AMD (0x1002)
Device ID: 0x6720
Revision ID: 0x0000
ROM Revision: 113-C2960K-152
VBIOS Version: 113-C2960900-101
EFI Driver Version: 01.00.507
Displays:
iMac:
Display Type: LCD
Resolution: 2560 x 1440 (QHD/WQHD - Wide Quad High Definition)
UI Looks like: 2560 x 1440
Framebuffer Depth: 24-Bit Color (ARGB8888)
Main Display: Yes
Mirror: Off
Online: Yes
Rotation: Supported
Automatically Adjust Brightness: No
Connection Type: DisplayPort
Thunderbolt Display:
Display Type: LCD
Resolution: 2560 x 1440 (QHD/WQHD - Wide Quad High Definition)
UI Looks like: 2560 x 1440
Framebuffer Depth: 24-Bit Color (ARGB8888)
Display Serial Number: C02G98BCDJGR
Mirror: Off
Online: Yes
Rotation: Supported
Automatically Adjust Brightness: No
Connection Type: DisplayPort
Thunderbolt Display:
Display Type: LCD
Resolution: 2560 x 1440 (QHD/WQHD - Wide Quad High Definition)
UI Looks like: 2560 x 1440
Framebuffer Depth: 24-Bit Color (ARGB8888)
Display Serial Number: C02G9888DJGR
Mirror: Off
Online: Yes
Rotation: Supported
Automatically Adjust Brightness: No
Connection Type: DisplayPort
I have reinstalled multiple times, I followed the instructions multiple times. But I cannot get it to launch properly.
Refer to the release notes...VMware Fusion 11.0 Release Notes
Yep, that's a great choice.
The big challenge with automated backups is that if the VM is running, the backup will be invalid, but you won't know it until it's too late. That's why time machine often breaks (among other reasons). Even something like Carbon Copy Cloner or SuperDuper only works reliably if the VM is shut down.
I don't use full screen mode, so can't directly help, but yep, I'd contact support - haven't seen reports of that before.
Can you launch any VM's at all? If not, then check system preferences/security and make sure you enabled the system extension.
If you can, and it's just these two, then there's instructions in another post on how to delete the memory image and boot fresh. Make VERY sure you have a good backup before doing that though, just in case.
The reference is not particularly helpful since it includes vulnerabilities from before Fusion 10. No way to filter the vulnerabilities for Fusion 10 or those not resolved in Fusion 10. Still no good explanation of why I would want to upgrade to Fusion 11 when I have an iMac that doesn't support Mojave, which consequently eliminates some features available in the upgrade.
Unfortunately, until this is addressed at the source by VMware by using a sync/quiescence driver, there's really not a viable, safe alternative to shutting the VM down.
Yes, you can compress them and send them.
Hopefully, if you have a OneDrive or something you can email the share link to sgoddard@vmware.com.
It looks like the MSI database was in an inconsistent state somehow.
Would be great to get hold of the logs at least to see if they show anything.
Thanks for reporting this.
Steve
Hello,
Thanks guys for the recommendations.
With Vimalin you can make backups of a running VM, because when your VM runs at the time of making a backup, it uses VMware Fusion automation features to make a snapshot before it starts copying the data. After the copy has completed it will -also automatically- commit that snapshot again.
The advantage of doing it that way is that it does not require additional drivers such as a sync/quiescence driver within the guest.
As a result it also supports all operating systems that are supported by VMware Fusion itself.
When restoring a VM like that it looks like it has been suspended at the time of backup.
You can download the latest version of Vimalin from the https://www.vimalin.com website and run with the demo/trial license for 60 days.
After those 60 days you can buy a license to keep all the features, or keep on using it on the free license.
The free license excludes scheduling features (so it runs automatically) and email notifications.
If you are fine without that then you can continue using it for free (although I of course appreciate sales )
Let me know if you have any additional questions and I will try to answer them here.
--
Wil
Hi renegad3,
You can see this thread: Enabling legacy OpenGL support in Fusion 11 if you are running Fusion 11 on a Mac 2011 model.
Regards,
-Rick
Hi,
Fusion 10 is still supported right now and thus does still receive all the security patches.
The reply with the link was in reference to user GlennyG who was using Fusion 7, it was not a reply to your original post.
Sorry for the confusion.
--
Wil
It seems like all VMs IPs in a subnet configured as custom private network will reply to ping while they're stopped
It happens after a clean startup of the system and there are no running VMs at all
I found out that only after I open the fusion window from the dock the ping starts to give "Request timeout" "ping: sendto: Host is down"
I left a ping running on a vm IP and just after clicking fusion from dock the ping stopped to give replies
This is a total failure if you're automating stuff with "vmrun"
This is on Fusion 11.0.0 / macOS Mojave 10.14 on a custom private network
The workaround for me right now is to add Fusion as a hidden login item and keep it running all the time
Same issue. As the original poster noted, this happens when no machines are currently running. This needs a fix asap and is not trivial. This has left me in a bad spot several times.
> The reply with the link was in reference to user GlennyG who was using Fusion 7, it was not a reply to your original post.
Alas I've "upgraded" one machine to 11 which has broken a key feature. I *definitely* won't be "upgrading" the other machines and will be looking at getting the now broken "upgraded" machine back to working with version 8.5 if I can't resolve it.
All the so-called security updates have had no affect; it was tinkering with something that didn't need fixing that broke it.
And people wonder why we don't upgrade more quickly.
Definitely not a happy bunny with VMWare for this.
Anyone???
