GNOME Bugzilla – Bug 751696
Virtual machines sometimes don't show up on in the collection
Last modified: 2016-09-20 08:15:55 UTC
Sometime when starting Boxes, virtual machines don't appear in the collection until I restart the application. This warning is thrown when it happen: Boxes-WARNING **: libvirt-broker.vala:105: Impossible d'ouvrir qemu+unix:///session: Cannot write data: Noeud final de transport n'est pas connecté The french part roughly translate to "Final transport node isn't connected".
(In reply to Adrien Plazas from comment #0) > Sometime when starting Boxes, virtual machines don't appear in the > collection until I restart the application. This warning is thrown when it > happen: > Boxes-WARNING **: libvirt-broker.vala:105: Impossible d'ouvrir > qemu+unix:///session: Cannot write data: Noeud final de transport n'est pas > connecté > > The french part roughly translate to "Final transport node isn't connected". Translation of translation isn't always a good idea. :) You might want to run with en_US locale or check the fr.po file to see the actual error. Anyway, sounds like some issue with connecting to libvirt. If I had to guess the autostart of libvirt takes too long and connection timesout.
I have seen that happening too recently (especially when I'm not connected to the Internet). IIRC the error message is: Transport endpoint is not connected. Daniel, do you know this one?
BTW, when this happens, it seems like libvirt gets hang on autolaunch cause if I you immediately restart Boxes, the error is gone. i-e it only happens (if it does) connecting to libvirt when it's not running already.
*** Bug 754095 has been marked as a duplicate of this bug. ***
jimmac is actually able to reproduce this 100% of the time and he filed a bug on libvirt: https://bugzilla.redhat.com/show_bug.cgi?id=1259070 .
*** Bug 755987 has been marked as a duplicate of this bug. ***
Red Hat #1259070 has been closed, but this is still broken with gnome-boxes-3.18.1-1.fc23, libvirt-daemon-1.2.18.1-2.fc23, libvirt-glib-0.2.2-1.fc23.
By the way, the English error is: (gnome-boxes:18856): Boxes-WARNING **: libvirt-broker.vala:98: Unable to open qemu+unix:///session: Cannot write data: Transport endpoint is not connected It happens 100% for me the first time I start Boxes after logging in to my desktop, or after having not used Boxes in a long time. It can always be fixed by simply closing Boxes and reopening it. I guess starting Boxes triggers some action that makes the VMs available (starting the virtual network thing?), but Boxes doesn't wait for it to finish before giving up.
(In reply to Michael Catanzaro from comment #7) > Red Hat #1259070 has been closed, but this is still broken with > gnome-boxes-3.18.1-1.fc23, libvirt-daemon-1.2.18.1-2.fc23, > libvirt-glib-0.2.2-1.fc23. That doesn't mean it's a Boxes issue. :) (In reply to Michael Catanzaro from comment #8) > > It happens 100% for me the first time I start Boxes after logging in to my > desktop, or after having not used Boxes in a long time. It can always be > fixed by simply closing Boxes and reopening it. I guess starting Boxes > triggers some action that makes the VMs available (starting the virtual > network thing?), but Boxes doesn't wait for it to finish before giving up. Try reproducing against virsh and virt-manager (you'd need to tell it to connect to session libvirt) and if you can't reproduce with those, then it's a Boxes issue.
*** Bug 757412 has been marked as a duplicate of this bug. ***
(In reply to Zeeshan Ali (Khattak) from comment #9) > Try reproducing against virsh and virt-manager (you'd need to tell it to > connect to session libvirt) and if you can't reproduce with those, then it's > a Boxes issue. virsh # list error: failed to connect to the hypervisor error: no valid connection error: Cannot write data: Transport endpoint is not connected
*** Bug 760129 has been marked as a duplicate of this bug. ***
(In reply to Zeeshan Ali (Khattak) from comment #9) > (In reply to Michael Catanzaro from comment #7) > > Red Hat #1259070 has been closed, but this is still broken with > > gnome-boxes-3.18.1-1.fc23, libvirt-daemon-1.2.18.1-2.fc23, > > libvirt-glib-0.2.2-1.fc23. > > That doesn't mean it's a Boxes issue. :) Has anyone filed a new libvirt bug? Or shall I file one?
https://bugzilla.redhat.com/show_bug.cgi?id=1271183 libvirt developers don't seem interested: "Someone is going to need to instrument the code to figure out where the problem is."
(In reply to Michael Catanzaro from comment #14) > https://bugzilla.redhat.com/show_bug.cgi?id=1271183 > > libvirt developers don't seem interested: "Someone is going to need to > instrument the code to figure out where the problem is." Cole is more a virt-manager dev than libvirt and I think he is talking to libvirt devs in there mainly.
*** Bug 764500 has been marked as a duplicate of this bug. ***
*** Bug 767802 has been marked as a duplicate of this bug. ***