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.

Description of problem:
Connecting to a XP VM over really slow WAN (>300 ms latency, ~ 2 MBit/s) can result in agent stopping after logging in (without SSO). 

Version-Release number of selected component (if applicable):
vdagent-win-0.1-18

How reproducible:
Random, not all that often

Steps to Reproduce:
1. Make sure you have a slow network
2. Start the VM in RHEVM, don't connect to it until it's up and running
3. Connect to the VM, manually log in (you don't want SSO) 

Actual results:
The agent occasionally doesn't work, only service is up and running

Expected results:
Agent should be working

Additional info:
Agent seems to work before logging in, as the resolution of the guest gets changed. 
Also, it's important to login during this "adjustment" phase. Agent is more likely to work after you login when the resolution is set properly

Could not reproduce after updating virtio

(In reply to Tomas Jamrisko from comment #1)
> Could not reproduce after updating virtio

so far tested with virtio-win-prewhql-0.1-64