ASAv not working

[hazem.shoeib]

Hi There,

I am really struggling with this issue for more than 10 days without any clue for a resolution
Problem:
I am trying to install ASAv on EVE-NG latest version 2.0.3-86 by following all steps included in HowTo.. during the step of "guestfish -a virtioa.qcow2" --> run, it either shows nothing or stuck at 25%. I noticed some time that it is showing below error from VM console:



Here is my settings:
- Host laptop properties:



- VM resources settings:



- "uname -a" command output

root@eve-ng:~# uname -a
Linux eve-ng 4.9.40-eve-ng-ukms-2+ #4 SMP Fri Sep 15 02:07:02 CEST 2017 x86_64 x86_64 x86_64 GNU/Linux

TShooting steps done so far:
- tried multiple ASAv images.
- Re-installed EVE-NG image.
- Re-installed VMWare workstation 14 Pro
- Even Re-installed Win10 and did the same sequence from scratch.

I am ready to provide as much details as I can to have this working.
Thank you so much for your help in advance.

[Uldis (UD)]

Visit live support chat

ASAv Works great on eve, seems yo simply missed something...

http://www.eve-ng.net/live-helpdesk


UD

[hazem.shoeib]

Visit live support chat

ASAv Works great on eve, seems yo simply missed something...

http://www.eve-ng.net/live-helpdesk


UD

I am still having the same issue! I even tried with fortigate image and it didn't work.
I tried to get help by providing more details via this thread with no luck: https://answers.launchpad.net/ubuntu/+question/668906
Please have deeper look and don't just keep saying "follow the HowTo and it will work" because I followed every single steps and even more and it is still not working!

[Uldis (UD)]

visit live chat please,
lets talk there...

http://www.eve-ng.net/live-helpdesk

and show me output from your EVE CLI:

kvm-ok


UD

[hazem.shoeib]

Hello Support team,

I would like to thank you for your great assistance.. Issue was resolved last Saturday with your help. The problem was related to a feature in Avast Antivirus that does inspection in EVE-NG VM while running any qemu image inside. By disabling this feature, all is working fine using the same images I have been trying with