HPReg's Posts

When your machine freezes, your mouse still works, so interrupts still work, so networking probably still works and it is likely that only the WindowServer is hosed. Something you might want to try: ssh into the frozen machine from another box. Then run the "sample" utility, from the remote shell, on the "VMware Fusion" process. This will likely tell us where the process is blocked, and what is going on.

No good news. The change we are making to fix this issue impacts enough things that we did not feel comfortable putting it in 8.0.2 without enough testing. So it will have to wait for the next micro update. Sorry. That is bad news for you, but at least that is news.

We are aware of an issue where vmrun fails to work with OS X VMs, with this error message: Error: Authentication failure or insufficient permissions in guest operating system This issue is being internally tracked as bug 1437434. It is caused by https://support.apple.com/en-us/HT204659: ============================================== Kernel Available for: OS X Mountain Lion v10.8.5, OS X Mavericks v10.9.5, OS X Yosemite v10.10 to v10.10.2 Impact: A local application may escalate privileges using a compromised service intended to run with reduced privileges Description: setreuid and setregid system calls failed to drop privileges permanently. This issue was addressed by correctly dropping privileges. CVE-ID CVE-2015-1117 : Mark Mentovai of Google Inc. ============================================== Which was introduced by Apple in 10.10.3, and then backported to 10.9.5 and 10.8.5, so sadly *all* up-to-date recent OS X guests are affected by this We have a fix, that is currently being tested.

> I need to continue running Snow Leopard, as the primary program I use to run my business needs Rosetta to run. The proper way to handle this is: 1) You update your Mac host to Yosemite or El Capitan. 2) In VMware Fusion, you create a virtual machine in which you install Snow Leopard _Server_ (regular Snow Leopard will not run because of Apple EULA restrictions). In that VM, you run Rosetta and your business program.

Please boot the VM in verbose mode (Cmd-V) so it will display text on screen to tell us what it is waiting for. Which version of OS X are you running in the VM? If you have 2 ESX hosts, consider vMotion'ing the VM to the second host while you upgrade the first one.

Weird. Can you try this? 1) Uninstall VMware Fusion by moving it to the trash 2) Restart your El Capitan host 3) Re-install VMware Fusion by double-clicking the .dmg, then double-clicking the VMware Fusion.app inside the .dmg (this will prompt you to enter your admin credentials). If the above does not work, please file a bug and attach the bundle created by the "Help > Collect Support Information" menu entry.

> In order for these to work on ESXi 6.0 for my 10.10 VM, I had to tinker with the amount of video ram size in the VM settings as well. The nvram settings worked only after adjusting the default of  4MB, after testing with 10MB and getting a display width of only 1850-something, I put it at automatic, and lo and behold, the 1920*1080 setting works. Yes, a lot of people are hitting this issue (the video ram size is too small). Would you mind telling other forum users how you put it at automatic?

> Can you give me please a hint? I would like to have the resolution 1280x1024 1280 in decimal is 0x500, i.e. on 32-bit 0x00000500 (that is 0xmnklijgh in my comment) 1024 in decimal is 0x400, i.e. on 32-bit 0x00000400 (that is 0xuvstqrop in my comment) So run these commands once for all in the guest (in Terminal.app):    sudo nvram AC20C489-DD86-4E99-992C-B7C742C1DDA9:width=%00%05%00%00    sudo nvram AC20C489-DD86-4E99-992C-B7C742C1DDA9:height=%00%04%00%00 then restart the Mac OS guest. That resolution will now automatically be applied for you at each restart of the guest.

> Is there a listing of all known Fusion 7 issues with OSX 10.x Usually we make such a list in the release notes. So the latest list was for the release notes of Fusion 7.1. >When I review the known issues documentation for Fusion 7 I don't see anything reported that fits many of the issues users are reporting. Issues happen in one of two ways: o Either because we have not tested a configuration in-house. We try to do as much as possible, but the test matrix is explosive (consider the combination of Mac hardware, multiply by the number of guest OSes we support, multiply by the software installed on the host, multiply by the 3rd party hardware installed on the Mac, ...) o Apple updates their OS and changes some behavior that our software relied on. Sometimes, this is Fusion's fault: we relied on undefined behavior. Sometimes this is Apple's fault: they introduced a bug (this is the case for this particular thread. Apple introduced a bug in 10.10.2, and we had to report the bug to Apple and workaround the issue.) >My organization has over 400+ users with Fusion installed and we are all suffering from issues. Many of us are starting to consider migrating to Linux and VMware Workstation and it seems more stable than Fusion. Sorry if this question is blunt, but, is the issue VMware or Apple? It depends on the issue. Workstation gets about the same testing coverage as Fusion in-house. Linux tends to break less things than OS X over time, but is plagued with other issues (like 3rd party kernel module compatibility and compilation, and sub-par graphics device support).

> Soon as I boot, the fans kick on at 5700rpm and the VMs are always slow. This is a different issue from what this thread is about. Please run Activity Monitor when you hear your fans, and determine which process is consuming all the CPU time. If it happens to be a VMware process, then sample it (there is a Sample button in Activity Monitor) and send the resulting file (which contains the samples) to us. This will tell us where our process is looping like crazy, which will give us a clue as to what is going on.

> could you (VMWARE) please provide a working solution for number 2? We are working on it. > this is frustrating to have to do the debugging after buying the license for a premium rate. Note that nobody could do the debugging earlier: Fusion 7.1 was released Dec 01, 2014 and Yosemite 10.10.2 was released Jan 28, 2015. VMware does not have a time machine to jump into the future, so when we wrote Fusion 7.1 there was no way for us to anticipate that Apple would break our app when they would release Yosemite 10.10.2 later. > PS, it is not ok, to use other reported details without credit. Sorry about that. I'll edit my message to credit you.

There are two known "slow VM" issues : 1) The first only happened on iMac, affected all virtualization products, and was caused by an interrupt storm (to check for it, we recommended people run the "sudo powermetrics -s interrupts" command). This issue was tracked by the thread Fusion 7 is running VERY SLOW on the GM of Yosemite . It was an Apple bug that Apple has solved in Yosemite 10.10.2. 2) The second only happens with Fusion VMs, and started to happen with Yosemite 10.10.2. It is tracked by this thread. It is being investigated by VMware. As reported by mjhd , in the meantime the workaround is to turn off the Settings > Sharing > Mirrored Folders > Desktop checkbox. [Edited to credit mjhd.] [Edited to clarify that issue #2 is not specific to Windows VMs.]

mjhd and xsived, Thanks for the info. This the issue tracked by this thread has been answered (when Apple released Yosemite 10.10.2), let's use the new thread Re: 10.10.2 and Fusion pro 7.1.0 superslow to track the new issue from now on. Thanks!

What you are experiencing may have the same symptoms (slow VM), but the cause is different. This thread was mainly about the Apple bug on iMac. What you describe, however, seems to be a VMware bug indeed. We are investigating...