[Bug 44306] New: libvirt shutting down guest after SPICE assertion failure

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=44306

             Bug #: 44306
           Summary: libvirt shutting down guest after SPICE assertion
                    failure
    Classification: Unclassified
           Product: Spice
           Version: unspecified
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: critical
          Priority: medium
         Component: server
        AssignedTo: spice-bugs at lists.freedesktop.org
        ReportedBy: gvenkat at attglobal.net


Not sure if this is a SPICE problem or a different problem that affects SPICE
while libvirt shuts down.

Twice in a week, libvirt has shutdown a Windows XP guest with the following log
entries for the Guest. Other entries before it are all normal.

dispatch_vdi_port_data: invalid port
qemu-kvm: spice-qemu-char.c:141: spice_chr_write: Assertion `s->datalen == 0'
failed.
2011-12-30 06:37:49.956+0000: shutting down

The entries before that are all normal entries.

The assertion failure may be the cause or a consequence of the real problem
that makes libvirt shutdown guest (presumably because it thinks guest has died
or gone away with no monitor connection).

Problem is I have no idea how to reproduce this, since it seems to happen
during regular use and after as much as a week of continuous uptime. As far as
I can see, there is no particular action in the user client that causes this.
It is not the guest going to sleep or hibernation (both of which have been
disabled). 

This started to happen only after updating to v1.0 KVM, 0.10 spice. Had no
problem like this for a year or so of continuous use going all the way back to
0.8.

System: Opensuse 11.4
kvm-1.0-129.6.x86_64
libspice-server1-0.10.0-25.1.x86_64
spice-client-0.10.0-25.1.x86_64

libvirt-0.9.8-185.3.x86_64

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.