Bug 35649 - vm just shutdown after a while with spice assert
Summary: vm just shutdown after a while with spice assert
Status: RESOLVED WORKSFORME
Alias: None
Product: Spice
Classification: Unclassified
Component: server (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium critical
Assignee: Spice Bug List
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-25 00:57 UTC by RedUEC
Modified: 2014-10-24 17:02 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description RedUEC 2011-03-25 00:57:54 UTC
I met a spice-0.8.0 issue. After running for a while, the vm just shutdown. Please help. Thanks.
I changed ring_remove() to be macro and then got this message from libvirt log file:

reds_show_new_channel: channel 2:0, connected successfully, over Non Secure link
red_dispatcher_set_peer:
handle_dev_input: connect
handle_new_display_channel: jpeg disabled
handle_new_display_channel: zlib-over-glz disabled
reds_show_new_channel: channel 4:0, connected successfully, over Non Secure link
red_dispatcher_set_cursor_peer:
handle_dev_input: cursor connect
reds_show_new_channel: channel 3:0, connected successfully, over Non Secure link
inputs_link:
current_remove_drawable:1693
current_remove_drawable: ASSERT (&item->tree_item.base.siblings_link)->next != NULL && (&item-tree_item.base.siblings_link)->prev != NULL failed
2011-03-23 05:11:04.814: shutting down


The platform is Ubuntu 10.10, x86_64, qemu-kvm is kvm.v28 from spice qemu git. Guest is windows xp 32bit, with virtserialio and vdagent isntalled.

Best Regards
reduec
Comment 1 Alon Levy 2011-07-20 10:13:08 UTC
what were you doing in the guest? could it have gone to sleep (suspend)? can you give more information - qemu version, what is running in the guest.

Alon
Comment 2 Marc-Andre Lureau 2014-10-24 17:02:32 UTC
not seeing this issue anymore, feel free to reopen if you can reproduce


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.