GNOME Bugzilla – Bug 710947
Gnome-boxes coredumps after start
Last modified: 2016-03-31 13:22:07 UTC
Once gnome-boxes is started, it segfaults: (gnome-boxes:17850): Libvirt.GObject-CRITICAL **: gvir_storage_vol_get_info: assertion 'GVIR_IS_STORAGE_VOL(vol)' failed Segmentation fault (core dumped) This bug has been reported on both Fedora and Ubuntu: https://bugs.launchpad.net/ubuntu/+source/gnome-boxes/+bug/1245086 https://bugzilla.redhat.com/show_bug.cgi?id=999957 I have tried both gnome-boxes 3.8 and 3.10 with the exact same result. I am able to create and start VMs using virt-manager. $ gnome-boxes --checks (gnome-boxes:28221): Boxes-WARNING **: util-app.vala:247: Failed to execute child process "restorecon" (No such file or directory) • The CPU is capable of virtualization: yes • The KVM module is loaded: yes • Libvirt KVM guest available: yes • Boxes storage pool available: yes • The SELinux context is default: no Report bugs to <https://bugzilla.gnome.org/enter_bug.cgi?product=gnome-boxes>. Boxes home page: <http://live.gnome.org/Boxes>. $ virsh -c qemu:///session pool-dumpxml gnome-boxes p11-kit: invalid config filename, will be ignored in the future: /usr/share/p11-kit/modules/. p11-kit: couldn't read config file: /usr/share/p11-kit/modules/. <pool type='dir'> <name>gnome-boxes</name> <uuid>b9f4f520-d857-48e9-aae3-e4656ae5fb7e</uuid> <capacity unit='bytes'>350211670016</capacity> <allocation unit='bytes'>131072</allocation> <available unit='bytes'>350211538944</available> <source> </source> <target> <path>/sub/boxes</path> <permissions> <mode>0744</mode> <owner>1000</owner> <group>1000</group> </permissions> </target> </pool>
<path>/sub/boxes</path> This is weird, did you make changes to get this /sub/ directory in the pool list?
Yes, I used virsh pool-edit to change the path. I've removed the pool, recreated it with original paths, but it still crashed. Then, I removed the pool and gnome-boxes, and reinstalled. The pool was recreated, but gnome-boxes still crashes.
OK, semi fixed. I did the following: - Remove the pool using virsh - rm -r ~/.local/share/gnome-boxes - reset all dconf values to their default - Reinstall gnome-boxes Skipping either the dconf or the ~/.local/share/gnome-boxes folder resulted in the exact same segfault. After the new install, gnome-boxes starts again. I edited the pool again, to point to the /sub/boxes directory, and I successfully created a domain. Now, I have a new problem; When the VM is started, I cannot connect to the console of it. I get "Connection to <name of domain> Failed". No other errors, nothing. But that's another bug, for another day. Marking this as INVALID. (even though the software should ideally never segfault, no matter what's wrong in it's settings or storage).
(In reply to comment #3) > > Marking this as INVALID. (even though the software should ideally never > segfault, no matter what's wrong in it's settings or storage). Sure but you are talking of an older version of the software so would be nice to know if you can reproduce this against latest stable version: 3.10.