Avast WEBforum
Business Products => Avast Business => Cloud Management Console & Clients => Topic started by: -matteo- on March 09, 2017, 11:52:12 AM
-
Hi,
many devices are reporting heavy problems with virtual machines since the last week. I checked personally many of these notebooks/desktops and I saw it's impossible to use the installed virtual machines both by using VMware Player/Workstation and VirtualBox.
I think so I found out a workaround by reading the post https://forum.avast.com/?topic=196714.0. Exactly I followed these instructions:
- Go to "Settings" - "Troubleshooting" - remove checkmark at "Enable hardware-assisted virtualization" - reboot PC
However, even if I uncheck the flag "Enable hardware-assisted virtualization" on a client machine after a little the Avast client synchronizes itself to the cloud server. So, the sync process resets the flag to its original configuration ("Enable hardware-assisted virtualization" -> ON). How can I set this flag by using the cloud console? I don't see any option to disable "Enable hardware-assisted virtualization" from the cloud console.
I am in touch with the support with no success for now, and we have dozens of laptops with this issue :(.
Thanks to everyone!!
-
Hi matteo,
we will add the ability to change the "Enable hardware-assisted virtualization" setting remotely into next version. ETA for release is 15/3/2017.
Meanwhile we are working on micro-update which should fix the root cause.
-
Hi matteo,
we will add the ability to change the "Enable hardware-assisted virtualization" setting remotely into next version. ETA for release is 15/3/2017.
Meanwhile we are working on micro-update which should fix the root cause.
Ok, misak... I will wait for the next release of 15/03/2017.
Many thanks!
-
Has the micro update been released yet that fixes these virtualization problems? We are on build 17.2.3419.61 and are still experiencing this problem.
-
I just applied manually the micro update on some PCs but they are facing the same issues :'(. So, I'm trying to disable the "Enable hardware-assisted virtualization" feature by using the remote console.
In the meanwhile on some PCs we needed to remove totally Avast in order to allow to users to work by using the local virtual machines.
I am also in touch with the Avast support, and they suggested me these instructions:
Hello. We have released a micro update to correct some of the issues with our recent version release.
There are two ways to update the version. The first is to go into the C:\Program Files\AVAST Software\Avast folder and run the AvastEmUpdate exe. Once the update is done a reboot will be necessary.
Or
This update will require two reboots to complete the install. The first reboot is to start the AvastEmUpdate task to look for and download the new micro update. You should only need to allow 3-5 minutes for the update to happen and then you can reboot. If you want to confirm the update has been applied, you can review the following registry keys to see if the Microupdate version is now 239.
It can be found in registry in:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\AVAST Software\Avast (64bit)
or
HKEY_LOCAL_MACHINE\SOFTWARE\AVAST Software\Avast (32bit)
and the value is MicroUpdates.
-
Thanks for sharing that. I tried the instructions from Avast support and that did not work. Disabling the "Enable hardware-assisted virtualization" setting did not work either. Like you, the only we we can run virtual machines is to uninstall Avast. It is frustrating that Avast can't get this fixed.
-
Thanks for sharing that. I tried the instructions from Avast support and that did not work. Disabling the "Enable hardware-assisted virtualization" setting did not work either. Like you, the only we we can run virtual machines is to uninstall Avast. It is frustrating that Avast can't get this fixed.
You're welcome... I just reopened the ticket to the support since they signed the ticket as solved >:(.
Let you know as soon as they answer to me.
-
I just updated to the latest micro update, 64,and it did not fix the virtual machine problem.
-
I just updated to the latest micro update, 64,and it did not fix the virtual machine problem.
The support answered me they are working for a few new fixes.
In the meanwhile I tried to disable the feature "Enable hardware-assisted virtualization" on some notebooks and the situation seems to be better even if not perfect.
I suggest you to disable this feature...
-
We are having the same issue. Micro-update has not solved it.
Disabling Enable hardware-assisted virtualization from the settings template in the console does nothing as the client continues to have the box ticked. (After reboots and waiting days not hours)
We cannot run VM's and Avast at the same time. No solution after all these weeks??
-
We continue to have this issue. I opened a support ticket 1 week ago, and still have not received any update on when this will be fixed. We are seriously considering moving on to a different endpoint protection vendor.
-
Any updates on this problem getting resolved or even being worked on? It's now been over a month and a half and still no answers.
-
I'm curious to know what version of VirtualBox you have running? I have 5.0.x and it runs just fine, but I tested a new desktop with 5.1.x and it seems sluggish, particularly to boot the guest. The hardware is different and thought it was something to do with that until I read this thread. I haven't tried turning off Avast hardware assisted VM yet but might give it a try or go back to 5.0.x for a while longer. Perhaps this is also an option for you?
-
I haven't tried turning off Avast hardware assisted VM yet but might give it a try or go back to 5.0.x for a while longer.
I just disabled Hardware Assisted Visualization in the console for a test group, and my XP virtual guests under Virtualbox 5.1.18 are noticeably faster to boot and seem more responsive. So I don't exactly know why the two products contend with each other but both the Avast and VirtualBox forums suggest using one or the other and not both for best performance.
-
Had been having performance issues on my VM and been playing with giving more cores and RAM etc. but with no improvement in performance.
However, after disabling H/W assisted virtualization in AVAST, I'm seeing a tremendous improvement in performance on my VMs, tremendous.
This is Horrible... Maybe Avast is trying to improve their AV but this feature has come short and they really need to revisit this.
-
However, after disabling H/W assisted virtualization in AVAST, I'm seeing a tremendous improvement in performance on my VMs, tremendous.
This is Horrible... Maybe Avast is trying to improve their AV but this feature has come short and they really need to revisit this.
What version of Avast do you have now? 17.5 has "nested virtualization", which in theory should solve the problems with multiple VMs. I haven't checked that myself, so I've be curious to see if you still had issue with 17.5 with assisted (and nested) virtualization or not.
What I'd really like to see is the interactive installer checking for known VM installations like VirtualBox, VMWare etc, and giving a notice prior to installation that for performance reasons you should consider disabling H/W assisted virtualization later. Could save people a lot of headaches who don't know about this issue.
-
Running Avast 6.0.8 r130520 on Windows 7 Professional 64-bit. I use VirtualBox to run VMs, and it has been working fine for years. Then just today, trying to start my largest and most important VM would crash every time. I ran it 2 days ago without issue. I did some searching about "virtualbox crash", and found a link about disabling "Enable hardware-assisted virtualization" in Avast. I did this and the problem went away. The VM runs Ubuntu 64-bit. I have a 64-bit AMD CPU (Opteron 4234) with hardware virtualization enabled.
I can only guess that Avast updated itself and turned on this hardware-assisted virtualization feature. Please default this setting to OFF for existing installations.