Nicholas Geovanis <nickgeova...@gmail.com> wrote: > On Wed, Oct 18, 2017 at 11:34 AM, Sven Hartge <s...@svenhartge.de> wrote:
>> You will get the "suspect GRO implementation" with 5.5 as well, but >> it is harmless. I have not yet found any performance problems. > Yes, still receive that message, even with the VM option set. > It's an ugly story, but a Win 7 update Monday broke Flash, so the > VSphere client stopped working (was OK on Win10). The breakage with Flash 27.0.0.170 hit *every* OS. > Unfortunately the flash and pepper plugins were total failures on > Debian 8.9 too (yes, I upgraded, downgraded, tried every permutation). https://www.reddit.com/r/vmware/comments/77airk/adobe_releases_beta_flash_fix/ https://www.reddit.com/r/vmware/comments/76ol8n/shockwave_flash_has_crashed_workaround_for/ https://www.reddit.com/r/vmware/comments/76mndv/vcenter_65_crashing_shockwave_flash_in_firefox/ https://kb.vmware.com/kb/2151945 > And unfortunately the HTML5 version of the VSphere app doesn't permit > editing of, for example, that vmxnet3 parameter for mitigation of > https://bugzilla.kernel.org/show_bug.cgi?id=191201#c49 You don't need all that stuff if you are not on ESX 6.5. So no need to try to edit those values. And if you upgrade to 6.5 eventually, just use at least 6.5u1, then you are safe. S° -- Sigmentation fault. Core dumped.
