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 688263 - restarting a live image doesn't work
restarting a live image doesn't work
Status: RESOLVED DUPLICATE of bug 685846
Product: gnome-boxes
Classification: Applications
Component: general
unspecified
Other Linux
: Normal normal
: --
Assigned To: GNOME Boxes maintainer(s)
GNOME Boxes maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-11-13 15:18 UTC by Matthias Clasen
Modified: 2016-03-31 13:55 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Matthias Clasen 2012-11-13 15:18:11 UTC
I changed the memory size, and then clicked 'restart' in the notification.
The vm shuts down, but then I just have a black screen, no restarting vm.

Similar when I restart from inside the vm. It shuts down, then I end up in the boxes overview, no vm restarting.

Here is what I see on the boxes stderr:

Boxes-Message: machine.vala:127: display Fedora-18-Nightly-20121112.11-x86_64-Live-desktop.iso disconnected

(gnome-boxes:18016): Boxes-WARNING **: libvirt-machine.vala:447: Failed to get information on 'Fedora-18-Nightly-20121112.11-x86_64-Live-desktop.iso'
[angela@dhcp-190-53 ~]$ gnome-boxes /opt/demo/Fedora-18-Nightly-20121112.11-x86_64-Live-desktop.iso 
Boxes-Message: machine.vala:127: display Fedora-18-Nightly-20121112.11-x86_64-Live-desktop.iso disconnected

(gnome-boxes:19228): Boxes-WARNING **: libvirt-machine.vala:682: Failed to start 'Fedora-18-Nightly-20121112.11-x86_64-Live-desktop.iso': Unable to start domain: Domain not found: no domain with matching uuid 'd6d5f250-5525-997f-3b23-696ac3bda5ba'

(gnome-boxes:19228): GSpice-CRITICAL **: spice_inputs_key_press: assertion `SPICE_CHANNEL(channel)->priv->state != SPICE_CHANNEL_STATE_UNCONNECTED' failed

(gnome-boxes:19228): GSpice-CRITICAL **: spice_inputs_key_press_and_release: assertion `channel->priv->state != SPICE_CHANNEL_STATE_UNCONNECTED' failed

(gnome-boxes:19228): GSpice-CRITICAL **: spice_inputs_key_press: assertion `SPICE_CHANNEL(channel)->priv->state != SPICE_CHANNEL_STATE_UNCONNECTED' failed

(gnome-boxes:19228): GSpice-CRITICAL **: spice_inputs_key_release: assertion `SPICE_CHANNEL(channel)->priv->state != SPICE_CHANNEL_STATE_UNCONNECTED' failed

(gnome-boxes:19228): GSpice-CRITICAL **: spice_inputs_key_release: assertion `SPICE_CHANNEL(channel)->priv->state != SPICE_CHANNEL_STATE_UNCONNECTED' failed

(gnome-boxes:19228): GSpice-CRITICAL **: spice_inputs_key_press: assertion `SPICE_CHANNEL(channel)->priv->state != SPICE_CHANNEL_STATE_UNCONNECTED' failed

(gnome-boxes:19228): GSpice-CRITICAL **: spice_inputs_key_press_and_release: assertion `channel->priv->state != SPICE_CHANNEL_STATE_UNCONNECTED' failed

(gnome-boxes:19228): GSpice-CRITICAL **: spice_inputs_key_release: assertion `SPICE_CHANNEL(channel)->priv->state != SPICE_CHANNEL_STATE_UNCONNECTED' failed

(gnome-boxes:19228): GSpice-CRITICAL **: spice_inputs_key_press: assertion `SPICE_CHANNEL(channel)->priv->state != SPICE_CHANNEL_STATE_UNCONNECTED' failed
Comment 1 Alexander Larsson 2012-11-13 15:21:35 UTC
Due to being live/transient the domain was deleted when it shut down during the reboot. Need to keep it alive in this case.
Comment 2 Zeeshan Ali 2013-01-07 01:39:46 UTC
(In reply to comment #1)
> Due to being live/transient the domain was deleted when it shut down during the
> reboot. Need to keep it alive in this case.

This would be bug#685846, thats already fixed. Mathias, you can still reproduce? Which version of Boxes?
Comment 3 Tobias Mueller 2013-06-09 11:39:39 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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