After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 692062 - Boxes says it can't connect to VM
Boxes says it can't connect to VM
Status: RESOLVED DUPLICATE of bug 687626
Product: gnome-boxes
Classification: Applications
Component: general
3.6.x
Other Linux
: Normal major
: --
Assigned To: GNOME Boxes maintainer(s)
GNOME Boxes maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2013-01-19 10:05 UTC by Mattias Bengtsson
Modified: 2016-03-31 13:54 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Screenshot (190.94 KB, image/png)
2013-01-19 10:05 UTC, Mattias Bengtsson 		Details
Log of boxes running (3.17 KB, text/x-log)
2013-01-20 03:50 UTC, Mattias Bengtsson 		Details

Description Mattias Bengtsson 2013-01-19 10:05:24 UTC 
Created attachment 233853 [details]
Screenshot

I installed a bunch of virtual machines (windows XP and 7) a while back in Boxes and now when I try to start any of them I get an error saying: "Connection to '{NAME_OF_BOX}' failed". 
I'm running F18 with Boxes 3.6.2 and when I made the virtual machines I was running F18 alpha or beta (I think alpha) and Boxes 3.6 (not sure what micro version).
Comment 1 Zeeshan Ali 2013-01-19 15:01:13 UTC 
Could you verify from the console log that its not this bug?

https://bugzilla.redhat.com/show_bug.cgi?id=892745

Run like this to get debug log: G_MESSAGES_DEBUG=Boxes gnome-boxes
Comment 2 Mattias Bengtsson 2013-01-20 03:50:12 UTC 
Created attachment 233929 [details]
Log of boxes running
Comment 3 Mattias Bengtsson 2013-01-20 03:50:30 UTC 
It's indeed that bug, are there any workarounds?
Comment 4 Mattias Bengtsson 2013-01-20 06:32:33 UTC 
I found one myself. So for anyone finding this through google:

Since I didn't have any important stuff running in my machines I could just clear the saved state I thought. After some googling and man page reading I found these commands helpful for accomplishing that:

# Find the name of your virtual machine(s)
$ virsh list --all
 [list of all VMs...]

# This should force a new boot, discarding any saved state
$ virsh start --force-boot {vm_name}  

# Then shut the virtual machine down again
$ virsh shutdown {vm_name}
Comment 5 Zeeshan Ali 2013-01-21 15:07:00 UTC 

*** This bug has been marked as a duplicate of bug 687626 ***