GNOME Bugzilla – Bug 774163
Crashed with boxes_libvirt_machine_wait_for_save_co: code should not be reached
Last modified: 2018-01-11 10:48:11 UTC
I was running 2 VMs at the same time (RHEL 7.3 Server, and Fedora 24 Workstation) and switching between them when necessary. I powered off the Fedora VM, and then switched to do the same to the RHEL VM, when it suddenly jumped back to the Fedora box (which was shutting down) before the RHEL one could be restored. When I tried to switch again, Boxes crashed. Versions: gnome-boxes-3.22.2-1.fc25.x86_64 libvirt-glib-0.2.3-2.fc24.x86_64 libvirt-daemon-2.2.0-1.fc25.x86_64 I will provide the backtrace shortly.
Unfortunately, no debug symbols. generate-core-file created a file larger than 165G and still wasn't done after 30 minutes. Hence it isn't possible to look at the core dump with the debug symbols. Boxes:ERROR:/home/rishi/devel/gnome-boxes/git/gnome-boxes/src/libvirt-machine.vala:752:boxes_libvirt_machine_wait_for_save_co: code should not be reached [Thread 0x7fd664900700 (LWP 7136) exited] [Thread 0x7fd6f6a01700 (LWP 6965) exited] [Thread 0x7fd6640ff700 (LWP 7135) exited] [Thread 0x7fd6638fe700 (LWP 7127) exited] [Thread 0x7fd665101700 (LWP 7139) exited] Thread 1 "gnome-boxes" received signal SIGABRT, Aborted. 0x00007ffff226a92f in raise () from /lib64/libc.so.6 (gdb) thread apply all bt
+ Trace 236845
Thread 21414 (Thread 0x7fd6bd196700 (LWP 7134))
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-boxes/issues/118.