Bug 46639 - VDAgent stops working after several connects with spicy
Summary: VDAgent stops working after several connects with spicy
Status: RESOLVED WORKSFORME
Alias: None
Product: Spice
Classification: Unclassified
Component: win32 agent (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Spice Bug List
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-26 02:44 UTC by brickwedde
Modified: 2014-11-03 02:00 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
Qemu Log (21.36 KB, text/plain)
2012-02-26 02:45 UTC, brickwedde 		Details
View All

Description brickwedde 2012-02-26 02:44:48 UTC 
Hello all,

I have two virtual machines (Windows 7 Sp1 32bit and Windows Server 2003R2)
both machines have the latest vdagent  installed with the virtio drivers from
http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/
(I also tried latest drivers from https://github.com/YanVugenfirer/kvm-guest-drivers-windows).

If I connect the first time with spicy to the machines all is working fine but after several connects(mostly between 2 or 10) vdagent stops working.
qemu log shows:
dispatch_vdi_port_data: invalid port
or
kvm: virtio-serial-bus: Unexpected port id 0 for device virtio-serial0.0


Sometimes it helps to restart the VdAgent Service in the machine. Most time it is necessary to reboot the machines.


Iam using:qemu 1.0 and current spice 0.10.1

Thanks 
Bastian
Comment 1 brickwedde 2012-02-26 02:45:37 UTC 
Created attachment 57653 [details]
Qemu Log
Comment 2 Marc-Andre Lureau 2014-11-03 02:00:00 UTC 
Can you still reproduce? This is more likely a virtio bug to report to qemu.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.