* Gerd Hoffmann (kra...@redhat.com) wrote:
> Hi,
>
> Yep, spice worker thread ...
>
> > Thread 7 (Thread 0x7fbe7f9ff700 (LWP 22383)):
> > #0 0x7fc0aa42f49d in read () from /lib64/libpthread.so.0
> > #1 0x7fc0a8c36c01 in spice_backtrace_gstack () from
> > /lib64/libspice-server.so.1
>
Hi,
Yep, spice worker thread ...
> Thread 7 (Thread 0x7fbe7f9ff700 (LWP 22383)):
> #0 0x7fc0aa42f49d in read () from /lib64/libpthread.so.0
> #1 0x7fc0a8c36c01 in spice_backtrace_gstack () from
> /lib64/libspice-server.so.1
> #2 0x7fc0a8c3e4f7 in spice_logv () from /lib64/libspi
* Gerd Hoffmann (kra...@redhat.com) wrote:
> Hi,
>
> > >> On a quick glance I'd blame the guest for sending corrupted commands.
> > >> Strange though that it happens on migration only, so there could be
> > >> a host issue too. Or a timing issue triggered by migration.
> > >>
> > >> Which migra
Hi,
> >> On a quick glance I'd blame the guest for sending corrupted commands.
> >> Strange though that it happens on migration only, so there could be
> >> a host issue too. Or a timing issue triggered by migration.
> >>
> >> Which migration phase?
> >
> > This is the point at which it switche
On 12/05/2016 11:46 AM, Dr. David Alan Gilbert wrote:
* Gerd Hoffmann (kra...@redhat.com) wrote:
On Fr, 2016-12-02 at 17:44 +, Dr. David Alan Gilbert wrote:
Hi Gerd,
I've got a moderately repeatable crash with spice playing
a video + postcopy. Some of the time I just get a warning
(that
