Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1433266

Summary: [virtio-win][netkvm] cannot launch anti-virus software(ESET Endpoint Antivirus) with virtio NetKVM driver
Product: Red Hat Enterprise Linux 7 Reporter: Yu Wang <wyu>
Component: virtio-winAssignee: ybendito
virtio-win sub component: virtio-win-prewhql QA Contact: Virtualization Bugs <virt-bugs>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: medium CC: 386510952, lijin, lmiksik, yvugenfi
Version: 7.4   
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-01 12:58:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
endpoint-screenshot none

Description Yu Wang 2017-03-17 09:11:46 UTC
Created attachment 1263981 [details]
endpoint-screenshot

Description of problem:
when launch ESET Endpoint Antivirus on ws2012r2, it occurred error "Error communicating with kernel"

Version-Release number of selected component (if applicable):
virtio-win-prewhql-126

How reproducible:
100%

Steps to Reproduce:
1. create vm and install OS windowns2012r2(6.3.9600) but not install virtio NetKVM driver(0.1.126 version);
2.install ESET Endpoint Antivirus(5.0.2242.2)
3.install virtio NetKVM driver(0.1.126);
4.restart the VM 


Actual results:
after restart the vm, it could not lunch the app, occurred error "Error communicating with kernel"

more details refer to the attachments

check the service in the services.msc, the “ESET Service” is not running (it is running before reboot without virtio-netkvm driver)

Expected results:
launch sccussfully with out any error

Additional info:
1 try to start the service manually , failed as "Error 1053: The service did not respond to the start or control request in a timely fashion"

Comment 2 Yu Wang 2017-03-17 09:17:28 UTC
Hi,

It cannot reproduce it on build 134 driver. So this bug has been fixed now.

Thanks
Yu Wang

Comment 3 lijin 2017-03-20 09:56:31 UTC
change status to verified according to comment#2

Comment 4 Qingzheng zhang 2017-03-27 10:02:07 UTC
Hi,

It can  reproduce  in on build 0.1.126-2 driver which is the latest stable version.

When will the next stable version release?

Thanks

Comment 7 errata-xmlrpc 2017-08-01 12:58:08 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2341