Fusion

 View Only
Expand all | Collapse all

The network became extremely slow running win11 arm on my macbook M4

  • 1.  The network became extremely slow running win11 arm on my macbook M4

    Posted Jul 12, 2025 03:24 PM

    I installed vmware fusion 13.63(24585314) on my macbook air(M4 chip with 10 cores) and I installed one win11 arm system by using fusion with the following configuration:

          cpu: 6  ; mem: 5012M ; network: bridged 

    I activated my window in the normal way, and removed malantivirus process that occupied too much cpu time on windows. the restarted my vm.

    Later I started my stock trading software called Tong Hua Shun(in china) that needs heavily on-time network communication, but this software became too much slow on my vm.

    I tried many times to debug and found that it is very possible that the reason comes from network driver included in vmwaretools.

    So my question is : right now is there any obvious network problems in vmware fusion? any other optimization or workround for this ? thanks your help!



  • 2.  RE: The network became extremely slow running win11 arm on my macbook M4

    Posted Jul 13, 2025 12:55 AM

    I can't say that I've seen a lot of people complain about "obvious network problems", although you can search the forum to double check my recollection.

    Can you describe what troubleshooting you did and what tests you performed  that led to your conclusion that there might be a problem with the virtual network driver?



    ------------------------------
    - Paul (technogeezer)
    vExpert 2025
    ------------------------------



  • 3.  RE: The network became extremely slow running win11 arm on my macbook M4

    Posted Jul 13, 2025 12:58 AM
    Edited by Technogeezer Jul 13, 2025 12:58 AM

    Also, is your stock trading software natively compiled for Windows ARM, or is compiled for Windows Intel (running under Microsoft's translator).



    ------------------------------
    - Paul (technogeezer)
    vExpert 2025
    ------------------------------



  • 4.  RE: The network became extremely slow running win11 arm on my macbook M4

    Posted Jul 13, 2025 04:55 AM

    my stock trading software is x86 32 bit, but I think it not reason because I also ran another x86-based software on the system, it has no any network problem.




  • 5.  RE: The network became extremely slow running win11 arm on my macbook M4

    Posted Jul 13, 2025 05:00 AM

    because when I met this network issue each time, my current workround is that I transfer network config from bridge to nat, then transfer back to bridge, it gave me that feeling that the network could become  improved to a certain extent, I guess the real problem could exist in network driver in vmwaretools




  • 6.  RE: The network became extremely slow running win11 arm on my macbook M4

    Posted Jul 13, 2025 12:30 PM

    Switching from bridged to NAT does not change the network driver in the VM - it's still using the vmxnet3 VMware network adapter provided by Fusion. It's only changing the virtual network that's in use by the virtualized adapter.

    Does the network work well when configured via NAT?

    I'd start doing some additional methodical testing to see where the bottleneck is (with tools that can actually measure the response time of the network, host and guest operating systems. At a minimum, network performance testing (with latency measurements) should be done from the host and guest, and on both the local network and the wide-area networking.

    Ancecotal evidence, while helpful,  isn't enough to pinpoint what the true issue is. This could be anything from a poorly performing application when running under Windows ARM to network configuration issues outside the VM.

    There have been infrequent issues reported of with some programs performing badly when 3D acceleration is enabled for the Windows VM. Have you tried disabling 3D acceleration and seeing if that changes anything. 



    ------------------------------
    - Paul (technogeezer)
    vExpert 2025
    ------------------------------



  • 7.  RE: The network became extremely slow running win11 arm on my macbook M4

    Posted Jul 13, 2025 09:36 PM

    I turned off the 3D acceleration function from the beginning. It mainly affects the window display speed and has nothing to do with the network.

    here is link for my stock software download address, https://download.10jqka.com.cn/,  it is free to use by registering one email . you could download it and install on win11 arm with vmware fusion. Please try it yourself and you will know how much pain I suffered, ^_^.




  • 8.  RE: The network became extremely slow running win11 arm on my macbook M4

    Posted Jul 13, 2025 09:39 PM

    By the way I also tried NAT long time ago, but I felt it is much lower speed than bridge, so I did not use it anymore.




  • 9.  RE: The network became extremely slow running win11 arm on my macbook M4

    Posted Jul 17, 2025 04:35 AM

    any feedback?




  • 10.  RE: The network became extremely slow running win11 arm on my macbook M4

    Posted Jul 17, 2025 11:27 AM

    Just a reminder: this is a user-to-user community and not official Broadcom support. We try to help each other out to the best of our ability or time -- and occasionally we'll find a Broadcom employee here, but it's not guaranteed. 

    Have you checked with the software developer to verify that they support or have tested their software running on Windows ARM? Software compile for Intel Windows runs under Microsoft's Prism translator (the equivalent of Apple/s Rosetta 2), and that introduces another layer of complexity to the problem. 

    The only other suggestion I have is to start using Windows performance monitoring tools within the VM while the issue is happening to get an idea what might be occurring - at least measurements can give an indication of where to look next.

    Another idea - you might want to try upgrading to the latest Fusion version (13.6.4). Some changes have been made in the vmxnet3 virtual graphics adapter (the adapter type used by Windows ARM virtual machines) to address a security issue - perhaps the changes might have an impact on what you're seeing. 



    ------------------------------
    - Paul (technogeezer)
    vExpert 2025
    ------------------------------



  • 11.  RE: The network became extremely slow running win11 arm on my macbook M4

    Posted Jul 17, 2025 11:34 AM

    One other suggestion:

    You state you are running a M4 MacBook Air with 10 cores. That machine has 4 performance cores and 6 efficiency (lower performance) cores. You are configuring your virtual machine with 6 virtual cores. That would mean that there's a real chance that virtual cores may be running on the lower performance efficiency cores -- and Windows has no control over that. 

    You may wish to lower your virtual CPUs to 4 and see if that makes any difference.



    ------------------------------
    - Paul (technogeezer)
    vExpert 2025
    ------------------------------



  • 12.  RE: The network became extremely slow running win11 arm on my macbook M4

    Posted Jul 18, 2025 04:46 AM

    thanks your advice. and could you please give me the link for the official Broadcom support? I will send this issue to them to see if there is any other available suggestions. thanks again!




  • 13.  RE: The network became extremely slow running win11 arm on my macbook M4

    Posted Jul 18, 2025 09:43 AM

    There's no link that I can give you because Broadcom does not  provide access to their technical support team for Fusion. This forum  - along with product documentation found at techdocs.broadcom.com and tech notes - are the available types of support for Fusion. 



    ------------------------------
    - Paul (technogeezer)
    vExpert 2025
    ------------------------------



  • 14.  RE: The network became extremely slow running win11 arm on my macbook M4

    Posted 28 days ago

    After several rounds of testing, it can be confirmed that it is a problem with the fusion network card driver. When the network was blocked several times, the network configuration was switched to NAT and then switched back, and the network returned to normal. This is a bug