- KIWI FOR GMAIL CRASHES ON STARTUP WINDOWS 10
- KIWI FOR GMAIL CRASHES ON STARTUP PRO
- KIWI FOR GMAIL CRASHES ON STARTUP MAC
I'm just kind of reminding myself to try to pay attention to the details if it happens again. Sorry that's not very precise (and it's off-topic for this thread).
KIWI FOR GMAIL CRASHES ON STARTUP MAC
I suspect it's when you're doing a drag-drop in Windows in full-screen mode, then use Cmd-Tab or Cmd-LeftArrow to get out of that space and go to the Mac desktop or another Mac app while still holding down the mouse button but I'm not entirely certain. This seemed to happen under circumstances that involved drag-and-drop, but I've not managed to precisely replicate it. The only safe way I have found to recover from this is to use the command-line utility to suspend any running VMs, then force-quit VMWare Fusion when those operations have completed. PS: Twice in the last week I have managed to get VMWare Fusion stuck in a mode in which it will not respond to keypresses or mouse clicks and cannot be quit (normally). Also attached is a list from `unzip -l` on the VMware Fusion Problem Report at 19.53.12.zip file (which has way more stuff in it than VMware ought to be grabbing a copy of, I would think, but I could selectively provide some of it if it's needed). The last Kernel_*.panic file in there is four days earlier, March 4. hang files in there are much older and pertain to other processes (Kiwi for Gmail, Keychain Access, Lingon X, coreaudiod, Activity Monitor, mds_stores and most of them seem to date to a day on which I ran out of application memory due to a particular mal-behaving application, a since-fixed dev version of Keka). I don't see any VMWare-related crash logs at all in there. Not crash logs, but some logs from the same day. PS: "\\Network\vmware-host\Shared Folders" in this case is also mounted as drive-letter "Z:". There's still a danger of entering "Shared Folders" via "This PC" > "Network locations", and other avenues. This has the benefit of not putting me into "\\Network\vmware-host\Shared Folders" if I go into one of these shared directories via a symlink and try to go up a directory (doing so puts me back in Desktop instead of in Shared Folders, which is where I would end up if I'd gotten into the shared directory in question via a shortcut. I symlink (not shortcut – use mklink in Command Prompt) each of the shared directories onto my Windows Desktop. My work-around so far to prevent triggering this VM-destructive crash problem has been to avoid going into that "Shared Folders" pseudo-directory at all. Half the stuff I do with this VM actually lives in those shared directories (though I have to be careful about deletion – it'll be permanent, since deleted files and directories on these shares, when done in Windows, go to neither Windows's Recycle Bin nor to macOS's Trash, but are just wiped). Using the shared directories themselves isn't a problem it's the virtual directory "Shared Folders" which contains them that is the problem.
KIWI FOR GMAIL CRASHES ON STARTUP WINDOWS 10
Guest: Windows 10 圆4, v1903 (build 18362.657) VMWare Hardware Version 16 (granted 4 cores and 8 GB of RAM).
KIWI FOR GMAIL CRASHES ON STARTUP PRO
Host: macOS 10.13.6 on a 2010 Mac Pro 12-core box. There's no choice so far but replacing the VM and moving the original virtual HD into it. Nothing I have attempted by way of repairing the broken VM has ever worked. Attempting to start the old one results in a "Failed to power on '/Volumes/SSD2/VMs/Windows 10 圆4.vmwarevm/Windows 10 圆4.vmx'" error.
I end up having to re-create the VM from scratch, and then move the original's hard drive into the new one and using that as the new one's boot drive.
It does not happen every single time, but often enough that it's mega-annoying, and very dangerous both in lost work, and in near-destruction of the VM, which has already happened to me twice this week. Nothing unusual about the directories that I can think of. I've been getting the problem for about a week, ever since changing which directories are shared (removed one, added a different one).
0 kommentar(er)
