1 2 Previous Next 19 Replies Latest reply on Aug 19, 2019 9:52 AM by wila

    Continuous Problem when switching between host and guest

    peter_w2019 Novice

      Dear All

       

      I am using Vmware Fusion 11.1 and running a Windows10 guest on a 2018 MacBook Pro. I created the windows10 guest virtual machine on a MacBook Air 2015 and recently switched.

      Shortly after switching to a new computer the problem started. Every time I switch between host and guest Vmware Fusion stalls and the guest is unusable while the physical Vmware process runs at 100% CPU. When I send countless CTRL-ALT-DEL commands to the guest and finally after 5-10 min task manager comes up it works again. But this is really annoying me to death. Searching the log I see the following timeout:

       

      2019-08-08T18:46:59.602+01:00| vmx| I125: GuestRpcSendTimedOut: message to toolbox-dnd timed out.

       

      Does anyone have an idea or had similar issues? Any thoughts are greatly appreciated.

      Many thanks and regards

      Peter

        • 1. Re: Continuous Problem when switching between host and guest
          wila Guru
          vExpertUser ModeratorsCommunity Warriors

          Hi,

           

          It looks like you have bumped into the issue debated here: https://planetvm.net/blog/?p=67185

           

          The good news is that there's a hotfix on the way (hopefully by Monday).

           

          As a workaround you can temporarily change your VM RAM to only use 2GB of RAM.

           

          --

          Wil

          | Author of Vimalin. The virtual machine Backup app for VMware Desktop Products
          | Vimalin : Automated backups for VMware Fusion and VMware Workstation Professional
          | More info at https://www.vimalin.com
          | Twitter @wilva
          | VMware Wiki at http://www.vi-toolkit.com
          • 2. Re: Continuous Problem when switching between host and guest
            rachelsunsm Enthusiast
            VMware Employees

            Hi,

             

            Fusion 11.1.1 is just pushed live. We have a mitigation fix for the VM performance issue on macOS 10.14.6 with this release.

             

            Root cause for the VM performance issue, is “the behavior of paging memory from an unlinked file.” Check KSC’s updates in community if you want to understand the technical details. And this one have further details: https://communities.vmware.com/message/2877617#2877617

             

            Per our internal testing, the performance issue has been greatly improved. If you experienced performance issue with macOS 10.14.6, pls upgrade to this build and let us know if it works for you.

             

            Thank you for your patience! We appreciate all of you working together with us to understand the root cause and figuring out the solution!

             

            VMware Fusion Team

            1 person found this helpful
            • 3. Re: Continuous Problem when switching between host and guest
              peter_w2019 Novice

              Hi there

               

              I am afraid the issue is not yet resolved. Just a couple of minutes ago I encountered the exact same issue as before again. Since yesterday I stopped using encryption and installed the latest version of Vmware Fusion 11.1.1. It worked really well until now. Again I was seeing the timeout error as mentioned in my initial post.

               

              I enclosed the Vmware.log for review.

               

              I am sorry to post the bad news, but it doesn't seem to be completely resolved.

               

              Thanks and regards,

              Peter

              • 4. Re: Continuous Problem when switching between host and guest
                peter_w2019 Novice

                Hi All,

                 

                I still having this problem. 100%CPU while getting timeouts

                2019-08-12T10:07:57.606+01:00| vmx| I125: scsi0:0: Command READ(10) took 28.118 seconds (ok)

                2019-08-12T10:07:57.606+01:00| vmx| I125: scsi0:0: Command READ(10) took 28.119 seconds (ok)

                2019-08-12T10:07:57.606+01:00| vmx| I125: scsi0:0: Command READ(10) took 28.120 seconds (ok)

                2019-08-12T10:07:57.606+01:00| vmx| I125: scsi0:0: Command READ(10) took 28.122 seconds (ok)

                2019-08-12T10:07:57.606+01:00| vmx| I125: scsi0:0: Command READ(10) took 28.120 seconds (ok)

                2019-08-12T10:07:57.606+01:00| vmx| I125: scsi0:0: Command READ(10) took 28.117 seconds (ok)

                2019-08-12T10:07:57.606+01:00| vmx| I125: scsi0:0: Command READ(10) took 28.118 seconds (ok)

                2019-08-12T10:07:57.607+01:00| vmx| I125: scsi0:0: Command READ(10) took 28.117 seconds (ok)

                2019-08-12T10:07:57.607+01:00| vmx| I125: scsi0:0: Command READ(10) took 28.116 seconds (ok)

                2019-08-12T10:07:57.607+01:00| vmx| I125: scsi0:0: Command READ(10) took 28.114 seconds (ok)

                2019-08

                 

                2019-08-12T10:22:57.576+01:00| vmx| I125: scsi0:0: Command WRITE(10) took 4.737 seconds (ok)

                2019-08-12T10:22:57.576+01:00| vmx| I125: scsi0:0: Command READ(10) took 5.144 seconds (ok)

                2019-08-12T10:22:57.576+01:00| vmx| I125: scsi0:0: Command READ(10) took 3.007 seconds (ok)

                2019-08-12T10:22:57.576+01:00| vmx| I125: scsi0:0: Command READ(10) took 5.142 seconds (ok)

                2019-08-12T10:22:57.576+01:00| vmx| I125: scsi0:0: Command READ(10) took 5.144 seconds (ok)

                2019-08-12T10:22:57.576+01:00| vmx| I125: scsi0:0: Command READ(10) took 5.144 seconds (ok)

                2019-08-12T10:22:57.576+01:00| vmx| I125: scsi0:0: Command READ(10) took 3.011 seconds (ok)

                2019-08-12T10:22:57.576+01:00| vmx| I125: scsi0:0: Command WRITE(10) took 1.170 seconds (ok)

                2019-08-12T10:22:57.576+01:00| vmx| I125: scsi0:0: Command READ(10) took 5.016 seconds (ok)

                2019-08-12T10:22:57.576+01:00| vmx| I125: scsi0:0: Command READ(10) took 5.145 seconds (ok)

                2019-08-12T10:22:57.577+01:00| vmx| I125: scsi0:0: Command READ(10) took 5.143 seconds (ok)

                2019-08-12T10:22:57.577+01:00| vmx| I125: scsi0:0: Command READ(10) took 5.143 seconds (ok)

                2019-08-12T10:22:57.577+01:00| vmx| I125: scsi0:0: Command READ(10) took 5.146 seconds (ok)

                2019-08-12T10:22:57.578+01:00| vmx| I125: scsi0:0: Command READ(10) took 5.145 seconds (ok)

                2019-08-12T10:22:57.580+01:00| vmx| I125: scsi0:0: Command READ(10) took 5.147 seconds (ok)

                2019-08-12T10:22:57.581+01:00| vmx| I125: scsi0:0: Command READ(10) took 5.148 seconds (ok)

                 

                2019-08-12T10:26:57.983+01:00| vmx| I125: GuestRpcSendTimedOut: message to toolbox-dnd timed out.

                2019-08-12T10:26:57.984+01:00| vmx| I125: GuestRpcSendTimedOut: message to toolbox-dnd timed out.

                 

                has anyone seen this before?

                 

                Thanks and regards,

                Peter

                • 5. Re: Continuous Problem when switching between host and guest
                  peter_w2019 Novice

                  PLEASE HELP, I can't work like this!!!!

                  • 6. Re: Continuous Problem when switching between host and guest
                    wila Guru
                    vExpertUser ModeratorsCommunity Warriors

                    Hi,

                     

                    As mentioned in an earlier post, you have to drop the virtual Machine RAM to 2GB in order to not have this issue at the moment.

                    Your VM's memory is still at 9GB

                     

                    2019-08-12T09:18:47.086+01:00| vmx| I125: DICT              numvcpus = "4"
                    2019-08-12T09:18:47.086+01:00| vmx| I125: DICT  cpuid.coresPerSocket = "4"
                    2019-08-12T09:18:47.086+01:00| vmx| I125: DICT               memsize = "9216"

                     

                    Personally I also think you have overcommitted the CPUs on your intel i7-8559U, it only has 4 physical cores (threads don't count) and you're not leaving any for the host.

                     

                    Another user in the mega thread mentioned that his/her VM worked OK with 3.6GB, so you might try that, but I'm not too optimistic about it.

                     

                    A VMware employee mentioned that the "Cant' use much RAM" issue will be resolved in a later update, but that will probably be weeks away.

                    --

                    Wil

                    | Author of Vimalin. The virtual machine Backup app for VMware Desktop Products
                    | Vimalin : Automated backups for VMware Fusion and VMware Workstation Professional
                    | More info at https://www.vimalin.com
                    | Twitter @wilva
                    | VMware Wiki at http://www.vi-toolkit.com
                    • 7. Re: Continuous Problem when switching between host and guest
                      peter_w2019 Novice

                      hi

                       

                      thanks for you reply. I will try working with less cores, but I can't change the RAM since the application I am working with has a minimum memory requirement of 8 GB. so if I set it to use only 2 gb ram I can't work either...

                       

                      thanks and regards,

                      peter

                      • 8. Re: Continuous Problem when switching between host and guest
                        peter_w2019 Novice

                        also with only 2 cores the problem persists

                        • 9. Re: Continuous Problem when switching between host and guest
                          wila Guru
                          Community WarriorsvExpertUser Moderators

                          Hi,

                           

                          re. not being able to reduce the RAM. That basically puts you between a rock and a hard place.

                           

                          re. the 2 CPU's. Your main issue is the RAM problem as evidenced by the slow reads in your log file. Sorry for distracting you on that one. I would still change it, but you've got bigger fish to fry before that even comes into play.

                           

                          From the earlier posts by VMware employee ksc, let me quote a bit of when the RAM problem gets triggered:

                          Triggers after 2GB of modified data is cached, regardless of file. Once triggered, it stays triggered as long as the file is open.

                           

                          Your VM has 9GB of RAM and the VM's RAM is backed by a file. So perhaps the issue can be mitigated a bit by turning off that feature, but I'm only stabbing in the dark here.

                           

                          OTOH if your VM changes a lot of data all the time (>2GB) then it wouldn't make a difference based on the above statement

                           

                          I think it would be best to open a support case with VMware and see if they can help you on a user case bases.

                           

                          --

                          Wil

                          | Author of Vimalin. The virtual machine Backup app for VMware Desktop Products
                          | Vimalin : Automated backups for VMware Fusion and VMware Workstation Professional
                          | More info at https://www.vimalin.com
                          | Twitter @wilva
                          | VMware Wiki at http://www.vi-toolkit.com
                          • 10. Re: Continuous Problem when switching between host and guest
                            peter_w2019 Novice

                            Hi there

                             

                            Thanks for your input. Well, I did now reduce the numbers of CPU down to 2 and reduced the vm's RAM down to 5. This makes the application I am using difficult in handling but, at least so far, I have not experienced any stalls no more. Although I am still getting errors in the log as shown below. As long as it doesn't unexpectedly hang as before, this is some improvement for me. Still it's not a real solution for me, but for the time being until there is a fix from Vmware I am trying to work like this.

                             

                            2019-08-13T07:25:29.273+01:00| vcpu-1| I125: SCSI DEVICE (scsi0:0): MODE SENSE(6) for unsupported page 0x8

                            2019-08-13T07:25:29.273+01:00| vcpu-0| I125: SCSI DEVICE (scsi0:0): MODE SENSE(6) for unsupported page 0x8

                            2019-08-13T07:25:29.274+01:00| vcpu-1| I125: SCSI DEVICE (scsi0:0): MODE SENSE(6) for unsupported page 0x8

                            2019-08-13T07:25:29.274+01:00| vcpu-1| I125: SCSI DEVICE (scsi0:0): MODE SENSE(6) for unsupported page 0x8

                            2019-08-13T07:25:29.275+01:00| vcpu-1| I125: SCSI DEVICE (scsi0:0): MODE SENSE(6) for unsupported page 0x8

                            2019-08-13T07:25:29.275+01:00| vcpu-1| I125: SCSI DEVICE (scsi0:0): MODE SENSE(6) for unsupported page 0x8

                             

                            but at least the timeout issue seems to have disappeared, which seem to have caused the stalls.

                             

                            Many thanks again for your continuous support!

                             

                            Cheers,

                            Peter

                            • 11. Re: Continuous Problem when switching between host and guest
                              DaveP Master

                              I switched the vmem file off and reverted to RAM plus swap for the VM. It seems to make a significant difference and I am running VMs now without any particular issues on MacBook Pro 15" 2018 model with 16GB RAM.

                               

                              Add these 2 lines to ~/Library/Preferences/VMware Fusion/config

                               

                              mainmem.backing = "swap"

                              mainmem.useNamedFile = "FALSE"

                               

                              I would be interested in if this makes a difference for you.

                              • 12. Re: Continuous Problem when switching between host and guest
                                peter_w2019 Novice

                                Hi there

                                 

                                I did enter the two above lines into the .vmx config file. I upped the RAM to 6 GB and after a while I got again errors and stalls.

                                 

                                2019-08-13T19:56:06.674+01:00| vcpu-1| I125: SCSI DEVICE (scsi0:0): MODE SENSE(6) for unsupported page 0x8

                                2019-08-13T19:56:06.675+01:00| vcpu-1| I125: SCSI DEVICE (scsi0:0): MODE SENSE(6) for unsupported page 0x8

                                2019-08-13T19:56:06.676+01:00| vcpu-2| I125: SCSI DEVICE (scsi0:0): MODE SENSE(6) for unsupported page 0x8

                                2019-08-13T19:56:06.676+01:00| vcpu-2| I125: SCSI DEVICE (scsi0:0): MODE SENSE(6) for unsupported page 0x8

                                2019-08-13T19:56:06.678+01:00| vcpu-2| I125: SCSI DEVICE (scsi0:0): MODE SENSE(6) for unsupported page 0x8

                                2019-08-13T19:56:06.678+01:00| vcpu-2| I125: SCSI DEVICE (scsi0:0): MODE SENSE(6) for unsupported page 0x8

                                2019-08-13T19:56:06.679+01:00| vcpu-2| I125: SCSI DEVICE (scsi0:0): MODE SENSE(6) for unsupported page 0x8

                                2019-08-13T19:56:06.679+01:00| vcpu-2| I125: SCSI DEVICE (scsi0:0): MODE SENSE(6) for unsupported page 0x8

                                2019-08-13T19:56:06.681+01:00| vcpu-2| I125: SCSI DEVICE (scsi0:0): MODE SENSE(6) for unsupported page 0x8

                                2019-08-13T19:56:06.681+01:00| vcpu-2| I125: SCSI DEVICE (scsi0:0): MODE SENSE(6) for unsupported page 0x8

                                2019-08-13T19:56:06.682+01:00| vcpu-0| I125: SCSI DEVICE (scsi0:0): MODE SENSE(6) for unsupported page 0x8

                                2019-08-13T19:56:06.682+01:00| vcpu-0| I125: SCSI DEVICE (scsi0:0): MODE SENSE(6) for unsupported page 0x8

                                 

                                not sure if it was the right place to put the lines to. but in ~/Library/Preferences/VMware Fusion/config

                                there was neither a config directory nor a config file.

                                 

                                but anyway, still getting errors and hangs.

                                • 13. Re: Continuous Problem when switching between host and guest
                                  peter_w2019 Novice

                                  what version of macOS are you using?

                                  are you running 10.14.6?

                                  • 14. Re: Continuous Problem when switching between host and guest
                                    peter_w2019 Novice

                                    now I am back at 4GB RAM, which is really the least I can set, since the app I am working with is not working otherwise....

                                     

                                    despite the changes for swap file I am getting this nasty stalls. it is sooo annoying and let's one freak out every couple of minutes

                                     

                                    could anyone please explain, WHAT IS REALLY GOING ON AND WHY THIS IS HAPPENING?
                                    I am getting choleric more and more everyday, since this is not a way to work.

                                    I start asking myself why I the world, did I buy a Vmware license for... I assumed this product works.

                                     

                                     

                                     

                                    2019-08-14T06:57:48.480+01:00| vmx| I125: GuestRpcSendTimedOut: message to toolbox-dnd timed out.

                                    2019-08-14T06:57:59.258+01:00| vmx| I125: GuestRpcSendTimedOut: message to toolbox-dnd timed out.

                                    2019-08-14T06:58:04.781+01:00| mks| I125: SWBWindow: Number of MKSWindows changed: 1 rendering MKSWindow(s) of total 1.

                                    2019-08-14T06:58:06.621+01:00| vmx| I125: scsi0:0: Command READ(10) took 1.064 seconds (ok)

                                    2019-08-14T06:58:07.696+01:00| vmx| I125: scsi0:0: Command READ(10) took 1.075 seconds (ok)

                                    2019-08-14T06:58:09.307+01:00| vmx| I125: scsi0:0: Command READ(10) took 1.484 seconds (ok)

                                    2019-08-14T06:58:09.307+01:00| vmx| I125: scsi0:0: Command READ(10) took 1.488 seconds (ok)

                                    2019-08-14T06:58:09.307+01:00| vmx| I125: scsi0:0: Command READ(10) took 1.488 seconds (ok)

                                    2019-08-14T06:58:09.307+01:00| vmx| I125: scsi0:0: Command READ(10) took 1.604 seconds (ok)

                                    2019-08-14T06:58:09.307+01:00| vmx| I125: scsi0:0: Command READ(10) took 1.527 seconds (ok)

                                    2019-08-14T06:58:09.307+01:00| vmx| I125: scsi0:0: Command READ(10) took 1.290 seconds (ok)

                                    2019-08-14T06:58:09.308+01:00| vmx| I125: scsi0:0: Command READ(10) took 1.606 seconds (ok)

                                    2019-08-14T06:58:12.677+01:00| vcpu-1| I125: TOOLS call to  failed.

                                    2019-08-14T06:58:24.790+01:00| vmx| I125: GuestRpcSendTimedOut: message to toolbox timed out.

                                    2019-08-14T06:58:24.790+01:00| vmx| I125: Tools: [AppStatus] Last heartbeat value 2103 (last received 8s ago)

                                    2019-08-14T06:58:34.269+01:00| vmx| I125: GuestRpcSendTimedOut: message to toolbox-dnd timed out.

                                    2019-08-14T06:58:36.764+01:00| vcpu-0| I125: Tools: Tools heartbeat timeout.

                                    2019-08-14T06:58:36.764+01:00| vcpu-0| I125: Tools: Running status rpc handler: 1 => 0.

                                    2019-08-14T06:58:36.764+01:00| vcpu-0| I125: Tools: Changing running status: 1 => 0.

                                    2019-08-14T06:58:36.764+01:00| vcpu-0| I125: Tools: [RunningStatus] Last heartbeat value 2103 (last received 20s ago)

                                    1 2 Previous Next