Bradall's Posts

OK did a blank install of win10 with the iso for vmware tools replaced with 11.1.5 and the svga driver is 8.17.1.1 so i guess that is now the issue to uninstall the driver itself as well as vmware tools. I can confirm that things seem to work with this driver. Update: Uninstalled vmware tools, reboot, manually uninstall video driver, reboot, install 11.1.5 (after replacing windows.iso), and everything works again. Guess it remains this way until the next release if the tech preview fixes it. Thanks.

Is there any trick to getting 11.1.5 to work? I've discovered that i had to change out the windows iso otherwise if i installed 11.1.5 in the guest when the guest rebooted vmware would automatically uninstall and upgrade to 11.3.5. So eventually got 11.1.5 running but the same problem persists. This is with a win10 guest. Is there any other options that may make this work other than using the tech preview below? I do notice that in device manager in the guest that the VMware SVGA 3D driver remains version 9.17.1.2 no matter what....Im assuming it should not be that. I'll test that theory by installing a blank win10 machine and see what happens i guess.

While disabling the shadows under windows fixed chrome browsers I have other applications that just appear as white square boxes with 3d acceleration enabled with a host graphics card of 1050ti. My guest is win10 21H2 as is my host. Driver version is the latest 516.94. I've tried multiple different versions of vmware tools within the guest without any luck. Seems that using vmware workstation for win10 with 3d acceleration is just hit and miss if your applications are going to run. Unclear what else to try here to get guest applications not to show just a blank white display. Appears other hypervisor solutons on windows do not have this issue even with the same VM. 

Well yesterdays announcement was a fizzer and made me much more comfortable with moving to parallels. So possibly another 7 months before a release of Fusion and there is nothing ground breaking in whats coming by the looks.Seems that this will be almost a year after the M1 was released. I suspect this may or may not ever happen. By the time fusion releases the consumers that required virtualization will have moved to parallels. I would not be surprised if Fusion never releases as the available market would mean there is little chance of return on investment. https://blogs.vmware.com/teamfusion/2021/04/fusion-on-apple-silicon-progress-update.html

@petec35_2similar to myself. While I only use a windows machine every now and again for some development it was useful. With no date on the horizon on if fusion will be updated the only alternative is to commit to parallels and spend there. It's a good product and seems to run extremely well for what I want to do and looks like your experience is similar. Given the timeframe, and as a number of users here have said, they are now living without fusion, and the decision for that was probably primarily driven by no product availability. It may well be the end of the line. There probably is not much of a market left after this period.  

Parallels have now released their production version of virtualisation for the M1 with version 16.5. I'm still looking for a timeline for Fusion to even start. The time difference I can see many who still require virtualisation moving to the only product that is available.

Having looked through open VM Tools source the scripts appear to only work with Linux distros that still utilise ifup/down on the interfaces and also Network Manager. Guess that fundamentally answers the questions on later linux distros where these have been migrated. It also answers that anything that is virtual within the guests simply is not dealt with. 

Hi, I'm not so much concerned about the external IP address at all but the internal Guest networking being corrupted. I can live with external IP address changes but what I can not live with is the internal and complex network needing manual turn down and restarting each time. I'll have a look at the scripts but I suspect today they are not dealing with internal virtual networking and the state save is ignoring that save for those items. 

Thank you for that. Seems that Suspend hard keeps the virtual network intact on restore whereas soft appears to corrupt the VM state.  So it appears that the scripts that tools runs probably does not take into consideration a virtual network and the state restoration restores just the state that is associated with just the physical network. Virtual networks are essentially corrupted with Suspend Guest (on workstation) or Suspend (Fusion). Thanks for the heads up I'll live with the VM still being connected to the network.

Sorry, but for clarity. The virtual networking that no longer functions is the networking on the guest. This is not an item regarding the virtual networking of the Type 2 hypervisor.    However to answer the question. VMWare Workstation PRO on Windows 10. VMWARE Fusion 11 on a MACOS.  I'll try the restarting processes on win10 when I get back to the machine. I'm not sure that this will restart the bridge inside of the Guest VM however which is the issue as per the example provided on the bridge on the guest going missing.  

Thaks for the response and sorry for the lack of detail but it applies to any libvirt installation by the looks. This only appears to be an issue with VMWare products as i have imported the VM into virtual box and the sleep facility there does not impact the networking. This is a stock standard RHEL8.3 install with default Server with GUI install. No changes at all to any selection. After the VM boots the following routes will exist. ip route default via 172.16.50.2 dev ens160 proto dhcp metric 100 172.16.50.0/24 dev ens160 proto kernel scope link src 172.16.50.134 metric 100 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown If you suspend the then awake the VM the resulting routes are. ip route default via 172.16.50.2 dev ens160 proto dhcp metric 100 172.16.50.0/24 dev ens160 proto kernel scope link src 172.16.50.134 metric 100 The VM still thinks the bridge is running. You can use virt-manager to stop and restart the bridge and then the routes return. The more complicated networks behave in the same manner after sleep you need to disable and then reenable each to get them to work again.  As stated, I can import this exact VM into virtual box and this does not happen.  Any suggestions are welcome. Thanks.     

Yes your 100% correct that I moved away from exfat due to the fact that it has no jourmneling but I do suppose a corrupt drive is far better than a kernel lock+corrupt drive. I was hoping that before wasting some more of my $$$ that there may be a solution out there for MAC that is compatible with a journel format that would work. I have largely given up on the products that i have paid for that advertised they work with Fusion only to find out that they do not work when you actually use them. I'll chase down paragon maybe they have fixed there MAC issues. How is every one else with a MAC managing there VM images?? I'm looking at maybe moving to docker would fix this alotogether? I'm assuming everyone else just dedicates an entire drive to your MAC and do not try and use a common drive across Mac/Windows?

This looks like it stops the key bounce behaviour on my 2017 Touch Bar MAC. Shame that VMware could not find it after 2 years. Think that reflects upon the effort involved. Thanks for the hint but I had to move to an alternate product a year ago for anything to be usable. Still nice to know that there is some way for Fusion to behave on a later MAC.

Thanks for the response. Yes this has been an issue since version 8 of Fusion. There is another thread High Sierra and Fusion "stuck" keys |VMware Communitieshttps://communities.vmware.com/thread/577500 that is 12 pages long on this topic. VMware did seem to fix it in a 10.3 patch release that did not seem to go public. Release 11 returned to the same old problem and 12 the issue remained. It is extremely simple to replicate on my machine. Simply install ubuntu server, get to a cli line and then wait for the Touch Bar to turn off. The next key the MAC lights up the touch bar and the key bounces in the ubuntu terminal. Has not changed in the years and makes using Linux inside of fusion almost impossible. Luckily there are alternatives to Fusion that do not suffer from this issue. It is a pity because I like Fusion, and I keep returning in hope that some year the issue may be addressed but as you point out its unlikely this will ever occur and I'm best to remain using alternative products.

Yes happens with VMWare on MACOS12, 13 and 14 with internal and external keyboards seems that those with touchbars are effected more greatly than those without. Any itttttt can be annnnnnnny key as you say. Its been this way for well over a year now and obviously not going to be fixed by VMWare. Best t head towards an alternative product if you want to use a VM.

well while having time off at present thought  would try and solve this other ways because its obvious that VMWare are using some old calls that do not behave the way they used to and that VMWare can not actually see or even recognide they have a problem. I've tried all sorts of things to stop this from occurring and the closest i can come is to permanent enable the touch bar. Nothing else seems to impact the outcome except for this. Seems that when th touchbar switches modes then the key repeat occurs. Simply can not remove that issue. Seems back toparallels.

As this thread was for High Sierra and shows as resolved using the once off VMWare patch I created a new threadfor Mojave to record the issue. Although after so long its obvious that VMware can not fix the issue. I can confirm that a move to Parallels fixes the issue. The new thread is VMWare Fusion Stuck Keys i simply removed the reference to a particular release of Apple because it looks like it will persist for many years.