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 921492

Summary: vdagent.exe application error on Windows 8 64bit
Product: Red Hat Enterprise Linux 8 Reporter: Jiri Belka <jbelka>
Component: spice-vdagent-winAssignee: Arnon Gilboa <agilboa>
Status: CLOSED CURRENTRELEASE QA Contact: Desktop QE <desktop-qa-list>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: ---CC: acathrow, cfergeau, dblechte, dyasny
Target Milestone: rcKeywords: TestBlocker
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-19 13:05:44 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
libvirt/qemu/w8-x64-vio.log vdsm/vdsm.log
none
vdagent.log and vdservice.log none

Description Jiri Belka 2013-03-14 10:29:43 UTC 
Created attachment 709970 [details]
libvirt/qemu/w8-x64-vio.log vdsm/vdsm.log

Description of problem:
I was able to reproduce SPICE agent crash on Windows 8 64bit.

Log Name:      Application
Source:        Application Error
Date:          3/14/2013 10:54:43 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      w8-x64-vio
Description:
Faulting application name: vdagent.exe, version: 1.1.0.10014, time stamp: 0x510f71f4
Faulting module name: vdagent.exe, version: 1.1.0.10014, time stamp: 0x510f71f4
Exception code: 0xc0000094
Fault offset: 0x0000000000078195
Faulting process id: 0x590
Faulting application start time: 0x01ce20dcf1740c28
Faulting application path: C:\Program Files (x86)\Redhat\RHEV\Drivers\Spice\vdagent.exe
Faulting module path: C:\Program Files (x86)\Redhat\RHEV\Drivers\Spice\vdagent.exe
Report Id: 3ffbf80f-8cd0-11e2-be6b-b5247b8cff85
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-03-14T17:54:43.000000000Z" />
    <EventRecordID>414</EventRecordID>
    <Channel>Application</Channel>
    <Computer>w8-x64-vio</Computer>
    <Security />
  </System>
  <EventData>
    <Data>vdagent.exe</Data>
    <Data>1.1.0.10014</Data>
    <Data>510f71f4</Data>
    <Data>vdagent.exe</Data>
    <Data>1.1.0.10014</Data>
    <Data>510f71f4</Data>
    <Data>c0000094</Data>
    <Data>0000000000078195</Data>
    <Data>590</Data>
    <Data>01ce20dcf1740c28</Data>
    <Data>C:\Program Files (x86)\Redhat\RHEV\Drivers\Spice\vdagent.exe</Data>
    <Data>C:\Program Files (x86)\Redhat\RHEV\Drivers\Spice\vdagent.exe</Data>
    <Data>3ffbf80f-8cd0-11e2-be6b-b5247b8cff85</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Version-Release number of selected component (if applicable):
sf10

How reproducible:
100%

Steps to Reproduce:
1. Have _fresh_ Win8 64bit
2. Install tools from SF10
3. After the installation is done, confirm reboot
4. When OS is up again, SPICE cursors moves between windows OK, check service
5. In Admin Portal check that you see guest info (IP, apps)
6. Click 'Shutdown' icon
7. Start again the VM
8. Check SPICE cursor, evetvwr for 'Error' issues
  
Actual results:
spice agent not running

Expected results:
running spice agent?

Additional info:
Comment 1 Arnon Gilboa 2013-03-14 16:01:41 UTC 
Please attach %windir%\temp\vdservice.log & %windir%\temp\vdagent.log.
I'll add it to the supported matrix after testing it in Sunday.
Comment 2 Jiri Belka 2013-03-15 12:41:10 UTC 
Created attachment 710658 [details]
vdagent.log and vdservice.log
Comment 3 Arnon Gilboa 2013-03-18 07:24:58 UTC 
I still cannot repro on my win8x64 guest. Using virtio-win-prewhql-0.1-55 & vdagent-win-0.1-15. It seems to work well, also after restart.

Please try to repro with the newer versions I used, and ping me for a debug version of vdagent if it continues.
Comment 4 Arnon Gilboa 2013-03-18 07:27:21 UTC 
It might be similar to bug 868254, which was fixed in vdagent-win-0.1-15.
Comment 5 Jiri Belka 2013-03-18 08:44:18 UTC 
I cannot discover what versions are used in 3.2.4 (sf) RHEVM guest tools. Did you try it with exactly this version of iso?
Comment 6 Arnon Gilboa 2013-03-18 15:22:28 UTC 
(In reply to comment #5)
> I cannot discover what versions are used in 3.2.4 (sf) RHEVM guest tools.
> Did you try it with exactly this version of iso?

No, I used brew output. For version, just right-click the binary -> properties. Please follow comment 3, and ping me on #spice.
Comment 7 Jiri Belka 2013-03-18 16:56:56 UTC 
What I did:
- install tools 3.2.4
- i postponed reboot after installation and stopped vdservice
- replaced vdagent and vdservice with version from vdagent-win-0.1-15
- rebooted
- spice was OK, cursor OK
- stopped from Admin Portal
- started, spice was OK, cursor OK

Is this what you wanted to test? I could not find you on #spice.
Comment 8 Arnon Gilboa 2013-03-19 12:25:47 UTC 
(In reply to comment #7)
> What I did:
> - install tools 3.2.4
> - i postponed reboot after installation and stopped vdservice
> - replaced vdagent and vdservice with version from vdagent-win-0.1-15
> - rebooted
> - spice was OK, cursor OK
> - stopped from Admin Portal
> - started, spice was OK, cursor OK
> 
> Is this what you wanted to test? I could not find you on #spice.

So it seems to be solved with vdagent-win-0.1-15, isn't it?
If you can't repro, please close the bug.