2014-07-31 15:26:56 +04:00
# Copyright (C) 2013-2014 Red Hat, Inc.
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
# Copyright (C) 2013 Cole Robinson <crobinso@redhat.com>
#
2018-04-04 16:35:41 +03:00
# This work is licensed under the GNU GPLv2 or later.
2018-03-20 22:00:02 +03:00
# See the COPYING file in the top-level directory.
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
import datetime
2013-10-01 05:41:10 +04:00
import glob
2017-10-11 14:35:50 +03:00
import io
2013-10-01 05:41:10 +04:00
import os
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
2013-10-01 05:41:10 +04:00
from gi . repository import GdkPixbuf
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
from gi . repository import Gtk
2014-02-14 19:20:37 +04:00
from gi . repository import Pango
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
2013-10-01 00:33:45 +04:00
from virtinst import DomainSnapshot
2019-06-09 22:29:44 +03:00
from virtinst import generatename
2019-06-17 04:12:39 +03:00
from virtinst import log
2019-06-08 01:21:24 +03:00
from virtinst import xmlutil
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
2019-06-17 05:19:17 +03:00
from . . lib import uiutil
2019-06-17 04:56:34 +03:00
from . . asyncjob import vmmAsyncJob
from . . baseclass import vmmGObjectUI
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
2013-10-01 05:41:10 +04:00
mimemap = {
" image/x-portable-pixmap " : " ppm " ,
" image/png " : " png " ,
}
2019-05-24 03:34:55 +03:00
def _make_screenshot_pixbuf ( mime , sdata ) :
loader = GdkPixbuf . PixbufLoader . new_with_mime_type ( mime )
loader . write ( sdata )
pixbuf = loader . get_pixbuf ( )
loader . close ( )
maxsize = 450
def _scale ( big , small , maxsize ) :
if big < = maxsize :
2020-08-23 23:56:05 +03:00
return big , small # pragma: no cover
2019-05-24 03:34:55 +03:00
factor = float ( maxsize ) / float ( big )
return maxsize , int ( factor * float ( small ) )
width = pixbuf . get_width ( )
height = pixbuf . get_height ( )
if width > height :
width , height = _scale ( width , height , maxsize )
else :
2020-08-23 23:56:05 +03:00
height , width = _scale ( height , width , maxsize ) # pragma: no cover
2019-05-24 03:34:55 +03:00
return pixbuf . scale_simple ( width , height ,
GdkPixbuf . InterpType . BILINEAR )
2013-10-01 05:41:10 +04:00
def _mime_to_ext ( val , reverse = False ) :
for m , e in mimemap . items ( ) :
if val == m and not reverse :
return e
if val == e and reverse :
return m
2020-08-23 23:56:05 +03:00
log . debug ( " Don ' t know how to convert %s = %s to %s " , # pragma: no cover
2013-10-01 05:41:10 +04:00
reverse and " extension " or " mime " , val ,
reverse and " mime " or " extension " )
2019-05-24 03:34:55 +03:00
class vmmSnapshotNew ( vmmGObjectUI ) :
__gsignals__ = {
" snapshot-created " : ( vmmGObjectUI . RUN_FIRST , None , [ str ] ) ,
}
def __init__ ( self , vm ) :
vmmGObjectUI . __init__ ( self , " snapshotsnew.ui " , " snapshot-new " )
self . vm = vm
self . _init_ui ( )
self . builder . connect_signals ( {
" on_snapshot_new_delete_event " : self . close ,
" on_snapshot_new_cancel_clicked " : self . close ,
" on_snapshot_new_name_changed " : self . _name_changed_cb ,
" on_snapshot_new_name_activate " : self . _ok_clicked_cb ,
" on_snapshot_new_ok_clicked " : self . _ok_clicked_cb ,
} )
self . bind_escape_key_close ( )
#######################
# Standard UI methods #
#######################
def show ( self , parent ) :
2019-06-17 04:12:39 +03:00
log . debug ( " Showing new snapshot wizard " )
2019-05-24 03:34:55 +03:00
self . _reset_state ( )
self . topwin . set_transient_for ( parent )
self . topwin . present ( )
def close ( self , ignore1 = None , ignore2 = None ) :
2019-06-17 04:12:39 +03:00
log . debug ( " Closing new snapshot wizard " )
2019-05-24 03:34:55 +03:00
self . topwin . hide ( )
return 1
def _cleanup ( self ) :
self . vm = None
###########
# UI init #
###########
def _init_ui ( self ) :
buf = Gtk . TextBuffer ( )
self . widget ( " snapshot-new-description " ) . set_buffer ( buf )
def _reset_state ( self ) :
2019-06-09 22:29:44 +03:00
basename = " snapshot "
2019-06-11 17:05:15 +03:00
def cb ( n ) :
return generatename . check_libvirt_collision (
self . vm . get_backend ( ) . snapshotLookupByName , n )
2019-06-09 22:29:44 +03:00
default_name = generatename . generate_name (
2019-06-11 15:51:44 +03:00
basename , cb , sep = " " , start_num = 1 , force_num = True )
2019-05-24 03:34:55 +03:00
self . widget ( " snapshot-new-name " ) . set_text ( default_name )
self . widget ( " snapshot-new-name " ) . emit ( " changed " )
self . widget ( " snapshot-new-description " ) . get_buffer ( ) . set_text ( " " )
self . widget ( " snapshot-new-ok " ) . grab_focus ( )
self . widget ( " snapshot-new-status-text " ) . set_text ( self . vm . run_status ( ) )
self . widget ( " snapshot-new-status-icon " ) . set_from_icon_name (
self . vm . run_status_icon_name ( ) , Gtk . IconSize . BUTTON )
sn = self . _get_screenshot ( )
uiutil . set_grid_row_visible (
self . widget ( " snapshot-new-screenshot " ) , bool ( sn ) )
if sn :
self . widget ( " snapshot-new-screenshot " ) . set_from_pixbuf ( sn )
self . widget ( " snapshot-new-name " ) . grab_focus ( )
###################
# Create handling #
###################
def _take_screenshot ( self ) :
stream = None
try :
stream = self . vm . conn . get_backend ( ) . newStream ( 0 )
screen = 0
flags = 0
mime = self . vm . get_backend ( ) . screenshot ( stream , screen , flags )
ret = io . BytesIO ( )
def _write_cb ( _stream , data , userdata ) :
ignore = stream
ignore = userdata
ret . write ( data )
stream . recvAll ( _write_cb , None )
return mime , ret . getvalue ( )
finally :
try :
if stream :
stream . finish ( )
2020-08-23 23:56:05 +03:00
except Exception : # pragma: no cover
2019-05-24 03:34:55 +03:00
pass
def _get_screenshot ( self ) :
if not self . vm . is_active ( ) :
2019-06-17 04:12:39 +03:00
log . debug ( " Skipping screenshot since VM is not active " )
2019-05-24 03:34:55 +03:00
return
if not self . vm . xmlobj . devices . graphics :
2019-06-17 04:12:39 +03:00
log . debug ( " Skipping screenshot since VM has no graphics " )
2019-05-24 03:34:55 +03:00
return
try :
# Perform two screenshots, because qemu + qxl has a bug where
# screenshot generally only shows the data from the previous
# screenshot request:
# https://bugs.launchpad.net/qemu/+bug/1314293
self . _take_screenshot ( )
mime , sdata = self . _take_screenshot ( )
2020-08-23 23:56:05 +03:00
except Exception : # pragma: no cover
2019-06-17 04:12:39 +03:00
log . exception ( " Error taking screenshot " )
2019-05-24 03:34:55 +03:00
return
ext = _mime_to_ext ( mime )
if not ext :
2020-08-23 23:56:05 +03:00
return # pragma: no cover
2019-05-24 03:34:55 +03:00
newpix = _make_screenshot_pixbuf ( mime , sdata )
setattr ( newpix , " vmm_mimetype " , mime )
setattr ( newpix , " vmm_sndata " , sdata )
return newpix
def _new_finish_cb ( self , error , details , newname ) :
self . reset_finish_cursor ( )
if error is not None :
error = _ ( " Error creating snapshot: %s " ) % error
self . err . show_err ( error , details = details )
return
2020-08-23 23:56:05 +03:00
2019-05-24 03:34:55 +03:00
self . emit ( " snapshot-created " , newname )
2020-08-23 23:56:05 +03:00
self . close ( )
2019-05-24 03:34:55 +03:00
def _validate_new_snapshot ( self ) :
name = self . widget ( " snapshot-new-name " ) . get_text ( )
desc = self . widget ( " snapshot-new-description "
) . get_buffer ( ) . get_property ( " text " )
try :
newsnap = DomainSnapshot ( self . vm . conn . get_backend ( ) )
newsnap . name = name
newsnap . description = desc or None
newsnap . get_xml ( )
2019-06-09 22:29:44 +03:00
newsnap . validate_generic_name ( _ ( " Snapshot " ) , newsnap . name )
2019-05-24 03:34:55 +03:00
return newsnap
except Exception as e :
return self . err . val_err ( _ ( " Error validating snapshot: %s " ) % e )
def _get_screenshot_data_for_save ( self ) :
snwidget = self . widget ( " snapshot-new-screenshot " )
if not snwidget . is_visible ( ) :
return None , None
sn = snwidget . get_pixbuf ( )
2020-08-23 23:56:05 +03:00
if not sn : # pragma: no cover
2019-05-24 03:34:55 +03:00
return None , None
mime = getattr ( sn , " vmm_mimetype " , None )
sndata = getattr ( sn , " vmm_sndata " , None )
return mime , sndata
def _do_create_snapshot ( self , asyncjob , xml , name , mime , sndata ) :
ignore = asyncjob
self . vm . create_snapshot ( xml )
try :
cachedir = self . vm . get_cache_dir ( )
basesn = os . path . join ( cachedir , " snap-screenshot- %s " % name )
# Remove any pre-existing screenshots so we don't show stale data
for ext in list ( mimemap . values ( ) ) :
p = basesn + " . " + ext
if os . path . exists ( basesn + " . " + ext ) :
os . unlink ( p )
if not mime or not sndata :
return
filename = basesn + " . " + _mime_to_ext ( mime )
2019-06-17 04:12:39 +03:00
log . debug ( " Writing screenshot to %s " , filename )
2019-05-24 03:34:55 +03:00
open ( filename , " wb " ) . write ( sndata )
2020-08-23 23:56:05 +03:00
except Exception : # pragma: no cover
2019-06-17 04:12:39 +03:00
log . exception ( " Error saving screenshot " )
2019-05-24 03:34:55 +03:00
def _create_new_snapshot ( self ) :
snap = self . _validate_new_snapshot ( )
if not snap :
return
xml = snap . get_xml ( )
name = snap . name
mime , sndata = self . _get_screenshot_data_for_save ( )
self . set_finish_cursor ( )
progWin = vmmAsyncJob (
self . _do_create_snapshot , [ xml , name , mime , sndata ] ,
self . _new_finish_cb , [ name ] ,
_ ( " Creating snapshot " ) ,
_ ( " Creating virtual machine snapshot " ) ,
self . topwin )
progWin . run ( )
################
# UI listeners #
################
def _name_changed_cb ( self , src ) :
self . widget ( " snapshot-new-ok " ) . set_sensitive ( bool ( src . get_text ( ) ) )
def _ok_clicked_cb ( self , src ) :
return self . _create_new_snapshot ( )
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
class vmmSnapshotPage ( vmmGObjectUI ) :
def __init__ ( self , vm , builder , topwin ) :
2013-09-23 00:10:16 +04:00
vmmGObjectUI . __init__ ( self , " snapshots.ui " ,
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
None , builder = builder , topwin = topwin )
self . vm = vm
self . _initial_populate = False
2014-07-31 18:42:35 +04:00
self . _unapplied_changes = False
2019-05-24 03:34:55 +03:00
self . _snapshot_new = None
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
2013-10-05 22:57:58 +04:00
self . _snapmenu = None
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
self . _init_ui ( )
self . builder . connect_signals ( {
" on_snapshot_add_clicked " : self . _on_add_clicked ,
" on_snapshot_delete_clicked " : self . _on_delete_clicked ,
" on_snapshot_start_clicked " : self . _on_start_clicked ,
" on_snapshot_apply_clicked " : self . _on_apply_clicked ,
2013-10-01 00:04:11 +04:00
" on_snapshot_list_changed " : self . _snapshot_selected ,
2013-10-05 22:57:58 +04:00
" on_snapshot_list_button_press_event " : self . _popup_snapshot_menu ,
2018-01-19 00:44:35 +03:00
" on_snapshot_refresh_clicked " : self . _on_refresh_clicked ,
2016-07-29 12:44:46 +03:00
" on_snapshot_list_row_activated " : self . _on_start_clicked ,
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
} )
self . top_box = self . widget ( " snapshot-top-box " )
self . widget ( " snapshot-top-window " ) . remove ( self . top_box )
2014-07-31 16:28:54 +04:00
selection = self . widget ( " snapshot-list " ) . get_selection ( )
selection . emit ( " changed " )
selection . set_mode ( Gtk . SelectionMode . MULTIPLE )
2014-07-31 18:42:35 +04:00
selection . set_select_function ( self . _confirm_changes , None )
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
2019-05-24 03:34:55 +03:00
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
##############
# Init stuff #
##############
def _cleanup ( self ) :
self . vm = None
2018-03-15 14:43:56 +03:00
self . _snapmenu = None
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
2019-05-24 03:34:55 +03:00
if self . _snapshot_new :
self . _snapshot_new . cleanup ( )
self . _snapshot_new = None
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
def _init_ui ( self ) :
2016-04-18 23:42:12 +03:00
# pylint: disable=redefined-variable-type
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
self . widget ( " snapshot-notebook " ) . set_show_tabs ( False )
buf = Gtk . TextBuffer ( )
buf . connect ( " changed " , self . _description_changed )
self . widget ( " snapshot-description " ) . set_buffer ( buf )
2014-02-01 20:25:35 +04:00
# [name, row label, tooltip, icon name, sortname, current]
model = Gtk . ListStore ( str , str , str , str , str , bool )
2013-10-01 01:53:55 +04:00
model . set_sort_column_id ( 4 , Gtk . SortType . ASCENDING )
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
col = Gtk . TreeViewColumn ( " " )
col . set_min_width ( 150 )
col . set_spacing ( 6 )
2014-02-01 20:25:35 +04:00
2013-10-01 01:36:38 +04:00
img = Gtk . CellRendererPixbuf ( )
img . set_property ( " stock-size " , Gtk . IconSize . LARGE_TOOLBAR )
col . pack_start ( img , False )
2014-02-01 20:25:35 +04:00
col . add_attribute ( img , ' icon-name ' , 3 )
txt = Gtk . CellRendererText ( )
2014-02-14 19:20:37 +04:00
txt . set_property ( " ellipsize " , Pango . EllipsizeMode . END )
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
col . pack_start ( txt , False )
2013-10-01 01:36:38 +04:00
col . add_attribute ( txt , ' markup ' , 1 )
2014-02-01 20:25:35 +04:00
img = Gtk . CellRendererPixbuf ( )
img . set_property ( " stock-size " , Gtk . IconSize . MENU )
2022-02-19 20:01:55 +03:00
img . set_property ( " icon-name " , " emblem-default " )
2014-02-14 19:20:37 +04:00
img . set_property ( " xalign " , 0.0 )
col . pack_start ( img , False )
2014-02-01 20:25:35 +04:00
col . add_attribute ( img , " visible " , 5 )
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
2013-10-01 01:53:55 +04:00
def _sep_cb ( _model , _iter , ignore ) :
return not bool ( _model [ _iter ] [ 0 ] )
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
slist = self . widget ( " snapshot-list " )
slist . set_model ( model )
slist . set_tooltip_column ( 2 )
slist . append_column ( col )
2013-10-01 01:53:55 +04:00
slist . set_row_separator_func ( _sep_cb , None )
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
2013-10-05 22:57:58 +04:00
# Snapshot popup menu
menu = Gtk . Menu ( )
2022-02-19 20:01:55 +03:00
item = Gtk . MenuItem . new_with_mnemonic ( _ ( " _Start snapshot " ) )
2013-10-05 22:57:58 +04:00
item . show ( )
item . connect ( " activate " , self . _on_start_clicked )
menu . add ( item )
2022-02-19 20:01:55 +03:00
item = Gtk . MenuItem . new_with_mnemonic ( _ ( " _Delete snapshot " ) )
2013-10-05 22:57:58 +04:00
item . show ( )
item . connect ( " activate " , self . _on_delete_clicked )
menu . add ( item )
self . _snapmenu = menu
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
###################
# Functional bits #
###################
2014-07-31 16:28:54 +04:00
def _get_selected_snapshots ( self ) :
selection = self . widget ( " snapshot-list " ) . get_selection ( )
def add_snap ( treemodel , path , it , snaps ) :
ignore = path
try :
name = treemodel [ it ] [ 0 ]
for snap in self . vm . list_snapshots ( ) :
if name == snap . get_name ( ) :
snaps . append ( snap )
2020-08-23 23:56:05 +03:00
except Exception : # pragma: no cover
2014-07-31 16:28:54 +04:00
pass
2014-01-27 05:21:12 +04:00
2014-07-31 16:28:54 +04:00
snaps = [ ]
selection . selected_foreach ( add_snap , snaps )
return snaps
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
2013-10-01 05:41:10 +04:00
def _refresh_snapshots ( self , select_name = None ) :
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
self . vm . refresh_snapshots ( )
2013-10-01 05:41:10 +04:00
self . _populate_snapshot_list ( select_name )
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
2020-09-21 04:55:27 +03:00
def vmwindow_refresh_vm_state ( self ) :
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
if not self . _initial_populate :
self . _populate_snapshot_list ( )
def _set_error_page ( self , msg ) :
self . _set_snapshot_state ( None )
self . widget ( " snapshot-notebook " ) . set_current_page ( 1 )
self . widget ( " snapshot-error-label " ) . set_text ( msg )
2013-10-01 05:41:10 +04:00
def _populate_snapshot_list ( self , select_name = None ) :
2014-07-31 16:28:54 +04:00
cursnaps = [ ]
for i in self . _get_selected_snapshots ( ) :
cursnaps . append ( i . get_name ( ) )
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
model = self . widget ( " snapshot-list " ) . get_model ( )
model . clear ( )
try :
snapshots = self . vm . list_snapshots ( )
2020-08-23 23:56:05 +03:00
except Exception as e : # pragma: no cover
2019-06-17 04:12:39 +03:00
log . exception ( e )
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
self . _set_error_page ( _ ( " Error refreshing snapshot list: %s " ) %
str ( e ) )
return
2013-10-01 01:53:55 +04:00
has_external = False
has_internal = False
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
for snap in snapshots :
2013-09-23 16:34:50 +04:00
desc = snap . get_xmlobj ( ) . description
2013-10-01 01:36:38 +04:00
name = snap . get_name ( )
2017-07-11 00:51:04 +03:00
state = snap . run_status ( )
2013-10-01 01:53:55 +04:00
if snap . is_external ( ) :
has_external = True
sortname = " 3 %s " % name
2020-07-15 15:48:57 +03:00
label = _ ( " %(vm)s \n <span size= ' small ' >VM State: "
" %(state)s (External)</span> " )
2013-10-01 01:53:55 +04:00
else :
has_internal = True
sortname = " 1 %s " % name
2020-07-15 15:48:57 +03:00
label = _ ( " %(vm)s \n <span size= ' small ' >VM State: "
" %(state)s </span> " )
2013-10-01 01:53:55 +04:00
2020-07-15 15:48:57 +03:00
label = label % {
" vm " : xmlutil . xml_escape ( name ) ,
" state " : xmlutil . xml_escape ( state )
}
2013-10-01 02:46:54 +04:00
model . append ( [ name , label , desc , snap . run_status_icon_name ( ) ,
2014-02-01 20:25:35 +04:00
sortname , snap . is_current ( ) ] )
2013-10-01 01:53:55 +04:00
if has_internal and has_external :
2014-02-01 20:25:35 +04:00
model . append ( [ None , None , None , None , " 2 " , False ] )
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
2014-07-31 16:28:54 +04:00
def check_selection ( treemodel , path , it , snaps ) :
if select_name :
if treemodel [ it ] [ 0 ] == select_name :
selection . select_path ( path )
elif treemodel [ it ] [ 0 ] in snaps :
selection . select_path ( path )
selection = self . widget ( " snapshot-list " ) . get_selection ( )
model = self . widget ( " snapshot-list " ) . get_model ( )
selection . unselect_all ( )
model . foreach ( check_selection , cursnaps )
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
self . _initial_populate = True
2013-10-01 05:41:10 +04:00
def _read_screenshot_file ( self , name ) :
if not name :
return
cache_dir = self . vm . get_cache_dir ( )
basename = os . path . join ( cache_dir , " snap-screenshot- %s " % name )
files = glob . glob ( basename + " .* " )
if not files :
return
filename = files [ 0 ]
mime = _mime_to_ext ( os . path . splitext ( filename ) [ 1 ] [ 1 : ] , reverse = True )
if not mime :
2020-08-23 23:56:05 +03:00
return # pragma: no cover
2019-05-24 03:34:55 +03:00
return _make_screenshot_pixbuf ( mime , open ( filename , " rb " ) . read ( ) )
2013-10-01 05:41:10 +04:00
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
def _set_snapshot_state ( self , snap = None ) :
self . widget ( " snapshot-notebook " ) . set_current_page ( 0 )
2013-09-23 16:34:50 +04:00
xmlobj = snap and snap . get_xmlobj ( ) or None
name = snap and xmlobj . name or " "
desc = snap and xmlobj . description or " "
2013-10-01 01:11:22 +04:00
state = snap and snap . run_status ( ) or " "
icon = snap and snap . run_status_icon_name ( ) or None
2013-10-01 01:53:55 +04:00
is_external = snap and snap . is_external ( ) or False
2014-02-01 20:25:35 +04:00
is_current = snap and snap . is_current ( ) or False
2013-10-01 01:53:55 +04:00
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
timestamp = " "
if snap :
timestamp = str ( datetime . datetime . fromtimestamp (
2013-09-23 16:34:50 +04:00
xmlobj . creationTime ) )
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
title = " "
if name :
2020-07-15 15:48:58 +03:00
title = ( _ ( " <b>Snapshot ' %(name)s ' :</b> " ) %
{ " name " : xmlutil . xml_escape ( name ) } )
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
2014-02-01 20:25:35 +04:00
uiutil . set_grid_row_visible (
self . widget ( " snapshot-is-current " ) , is_current )
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
self . widget ( " snapshot-title " ) . set_markup ( title )
self . widget ( " snapshot-timestamp " ) . set_text ( timestamp )
self . widget ( " snapshot-description " ) . get_buffer ( ) . set_text ( desc )
self . widget ( " snapshot-status-text " ) . set_text ( state )
2013-10-01 01:11:22 +04:00
if icon :
self . widget ( " snapshot-status-icon " ) . set_from_icon_name (
2014-01-12 23:36:03 +04:00
icon , Gtk . IconSize . BUTTON )
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
2014-01-27 03:15:50 +04:00
uiutil . set_grid_row_visible ( self . widget ( " snapshot-mode " ) ,
2013-10-01 01:53:55 +04:00
is_external )
if is_external :
is_mem = xmlobj . memory_type == " external "
is_disk = [ d . snapshot == " external " for d in xmlobj . disks ]
if is_mem and is_disk :
mode = _ ( " External disk and memory " )
elif is_mem :
mode = _ ( " External memory only " )
else :
mode = _ ( " External disk only " )
self . widget ( " snapshot-mode " ) . set_text ( mode )
2013-10-01 05:41:10 +04:00
sn = self . _read_screenshot_file ( name )
self . widget ( " snapshot-screenshot " ) . set_visible ( bool ( sn ) )
self . widget ( " snapshot-screenshot-label " ) . set_visible ( not bool ( sn ) )
if sn :
self . widget ( " snapshot-screenshot " ) . set_from_pixbuf ( sn )
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
self . widget ( " snapshot-add " ) . set_sensitive ( True )
self . widget ( " snapshot-delete " ) . set_sensitive ( bool ( snap ) )
self . widget ( " snapshot-start " ) . set_sensitive ( bool ( snap ) )
self . widget ( " snapshot-apply " ) . set_sensitive ( False )
2014-07-31 18:42:35 +04:00
self . _unapplied_changes = False
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
2014-07-31 18:42:35 +04:00
def _confirm_changes ( self , sel , model , path , path_selected , user_data ) :
ignore1 = sel
ignore2 = path
ignore3 = model
ignore4 = user_data
if not self . _unapplied_changes or not path_selected :
return True
2019-04-14 23:19:56 +03:00
if self . err . confirm_unapplied_changes ( ) :
2014-07-31 18:42:35 +04:00
self . _apply ( )
return True
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
2014-07-31 18:42:35 +04:00
def _apply ( self ) :
snaps = self . _get_selected_snapshots ( )
if not snaps or len ( snaps ) > 1 :
2020-08-23 23:56:05 +03:00
return False # pragma: no cover
2014-07-31 18:42:35 +04:00
snap = snaps [ 0 ]
desc_widget = self . widget ( " snapshot-description " )
desc = desc_widget . get_buffer ( ) . get_property ( " text " ) or " "
xmlobj = snap . get_xmlobj ( )
2018-08-31 23:52:02 +03:00
origxml = xmlobj . get_xml ( )
2014-07-31 18:42:35 +04:00
xmlobj . description = desc
2018-08-31 23:52:02 +03:00
newxml = xmlobj . get_xml ( )
2014-07-31 18:42:35 +04:00
self . vm . log_redefine_xml_diff ( snap , origxml , newxml )
if newxml == origxml :
2020-08-23 23:56:05 +03:00
return True # pragma: no cover
2015-04-11 00:50:06 +03:00
2014-07-31 18:42:35 +04:00
self . vm . create_snapshot ( newxml , redefine = True )
2015-04-11 00:50:06 +03:00
snap . ensure_latest_xml ( )
2014-07-31 18:42:35 +04:00
return True
2013-09-30 22:28:43 +04:00
#############
# Listeners #
#############
2013-10-05 22:57:58 +04:00
def _popup_snapshot_menu ( self , src , event ) :
ignore = src
if event . button != 3 :
return
2019-04-02 23:18:57 +03:00
self . _snapmenu . popup_at_pointer ( event )
2013-10-05 22:57:58 +04:00
2019-05-24 03:34:55 +03:00
def close ( self , ignore1 = None , ignore2 = None ) :
if self . _snapshot_new :
self . _snapshot_new . close ( )
2013-09-30 22:28:43 +04:00
return 1
def _description_changed ( self , ignore ) :
2014-07-31 18:42:35 +04:00
snaps = self . _get_selected_snapshots ( )
2013-09-30 22:28:43 +04:00
desc_widget = self . widget ( " snapshot-description " )
desc = desc_widget . get_buffer ( ) . get_property ( " text " ) or " "
2014-07-31 18:42:35 +04:00
if len ( snaps ) == 1 and snaps [ 0 ] . get_xmlobj ( ) . description != desc :
self . _unapplied_changes = True
2013-09-30 22:28:43 +04:00
2014-07-31 18:42:35 +04:00
self . widget ( " snapshot-apply " ) . set_sensitive ( True )
def _on_apply_clicked ( self , ignore ) :
self . _apply ( )
2013-09-30 22:28:43 +04:00
self . _refresh_snapshots ( )
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
2019-05-24 03:34:55 +03:00
def _snapshot_created_cb ( self , src , newname ) :
self . _refresh_snapshots ( newname )
2013-09-30 22:28:43 +04:00
def _on_add_clicked ( self , ignore ) :
2019-05-24 03:34:55 +03:00
if not self . _snapshot_new :
self . _snapshot_new = vmmSnapshotNew ( self . vm )
self . _snapshot_new . connect ( " snapshot-created " ,
self . _snapshot_created_cb )
2019-12-20 00:52:34 +03:00
if self . vm . has_managed_save ( ) :
result = self . err . ok_cancel (
_ ( " Saved memory state will not be part of the snapshot " ) ,
_ ( " The domain is currently saved. Due to technical "
" limitations that saved memory state will not become part "
" of the snapshot. Running it later will be the same as "
" having forced the system off mid-flight. It is "
" recommended to snapshot either the running or shut down "
" system instead. " ) )
if not result :
return
2019-05-24 03:34:55 +03:00
self . _snapshot_new . show ( self . topwin )
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
2018-01-19 00:44:35 +03:00
def _on_refresh_clicked ( self , ignore ) :
self . _refresh_snapshots ( )
2016-07-29 12:44:46 +03:00
def _on_start_clicked ( self , ignore , ignore2 = None , ignore3 = None ) :
2014-07-31 16:28:54 +04:00
snaps = self . _get_selected_snapshots ( )
if not snaps or len ( snaps ) > 1 :
2020-08-23 23:56:05 +03:00
return # pragma: no cover
2014-07-31 16:28:54 +04:00
snap = snaps [ 0 ]
2020-07-12 00:31:40 +03:00
2020-07-15 15:48:57 +03:00
if self . vm . is_active ( ) :
msg = _ ( " Are you sure you want to run the snapshot ' %(name)s ' ? "
" All the disk changes since the last snapshot was created "
" will be discarded. " )
else :
msg = _ ( " Are you sure you want to run the snapshot ' %(name)s ' ? "
" All the disk and configuration changes since the last "
" snapshot was created will be discarded. " )
msg = msg % { " name " : snap . get_name ( ) }
2014-03-26 16:54:10 +04:00
result = self . err . yes_no ( msg )
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
if not result :
return
2019-12-20 00:52:33 +03:00
if self . vm . has_managed_save ( ) and not snap . has_run_state ( ) :
result = self . err . ok_cancel (
_ ( " Saved state will be removed to avoid filesystem corruption " ) ,
_ ( " Snapshot ' %s ' contains only disk and no memory state. "
" Restoring the snapshot would leave the existing saved state "
" in place, effectively switching a disk underneath a running "
" system. Running the domain afterwards would likely result in "
" extensive filesystem corruption. Therefore the saved state "
" will be removed before restoring the snapshot. "
) % snap . get_name ( ) )
if not result :
return
self . vm . remove_saved_image ( )
2019-06-17 04:12:39 +03:00
log . debug ( " Running snapshot ' %s ' " , snap . get_name ( ) )
2013-10-05 18:03:56 +04:00
vmmAsyncJob . simple_async ( self . vm . revert_to_snapshot ,
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
[ snap ] , self ,
2013-10-05 22:57:58 +04:00
_ ( " Running snapshot " ) ,
_ ( " Running snapshot ' %s ' " ) % snap . get_name ( ) ,
_ ( " Error running snapshot ' %s ' " ) %
2013-09-07 04:59:01 +04:00
snap . get_name ( ) ,
finish_cb = self . _refresh_snapshots )
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
def _on_delete_clicked ( self , ignore ) :
2014-07-31 16:28:54 +04:00
snaps = self . _get_selected_snapshots ( )
if not snaps :
2020-08-23 23:56:05 +03:00
return # pragma: no cover
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
result = self . err . yes_no ( _ ( " Are you sure you want to permanently "
2014-07-31 16:28:54 +04:00
" delete the selected snapshots? " ) )
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
if not result :
return
2014-07-31 16:28:54 +04:00
for snap in snaps :
2019-06-17 04:12:39 +03:00
log . debug ( " Deleting snapshot ' %s ' " , snap . get_name ( ) )
2014-07-31 16:28:54 +04:00
vmmAsyncJob . simple_async ( snap . delete , [ ] , self ,
_ ( " Deleting snapshot " ) ,
_ ( " Deleting snapshot ' %s ' " ) % snap . get_name ( ) ,
_ ( " Error deleting snapshot ' %s ' " ) % snap . get_name ( ) ,
finish_cb = self . _refresh_snapshots )
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
def _snapshot_selected ( self , selection ) :
2013-10-01 02:46:54 +04:00
ignore = selection
2014-07-31 16:28:54 +04:00
snap = self . _get_selected_snapshots ( )
2013-10-01 02:46:54 +04:00
if not snap :
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
self . _set_error_page ( _ ( " No snapshot selected. " ) )
return
2014-07-31 16:28:54 +04:00
if len ( snap ) > 1 :
self . _set_error_page ( _ ( " Multiple snapshots selected. " ) )
self . widget ( " snapshot-start " ) . set_sensitive ( False )
self . widget ( " snapshot-apply " ) . set_sensitive ( False )
self . widget ( " snapshot-delete " ) . set_sensitive ( True )
return
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
try :
2014-07-31 16:28:54 +04:00
self . _set_snapshot_state ( snap [ 0 ] )
2020-08-23 23:56:05 +03:00
except Exception as e : # pragma: no cover
2019-06-17 04:12:39 +03:00
log . exception ( e )
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 18:18:47 +04:00
self . _set_error_page ( _ ( " Error selecting snapshot: %s " ) % str ( e ) )