[Spice-commits] Changes to 'rebase/spice-next'

Wed Aug 29 23:32:54 PDT 2012

New branch 'rebase/spice-next' available with the following commits:
commit 92cf0041df6cde5e48bd4f52a1750e4b65a07c5f
Author: Alon Levy <alevy at redhat.com>
Date:   Wed Aug 22 11:16:26 2012 +0300

    configure: print spice-protocol and spice-server versions
    
    Signed-off-by: Alon Levy <alevy at redhat.com>
    Signed-off-by: Gerd Hoffmann <kraxel at redhat.com>

commit 462fdbddbd37439ed7553391b6815e4cb4b3a7fc
Author: Alon Levy <alevy at redhat.com>
Date:   Wed Aug 22 11:16:25 2012 +0300

    qxl: add QXL_IO_MONITORS_CONFIG_ASYNC
    
    Revision bumped to 4 for new IO support, enabled for spice-server >=
    0.11.1. New io enabled iff revision is 4. Revision can be set to 4, and
    defaults to 4, iff spice-server >= 0.11.1 && spice-protocol >=
    0.12.0.
    
    This io calls the corresponding new spice api
    spice_qxl_monitors_config_async to let spice-server read a new guest set
    monitors config and notify the client.
    
    On migration reissue spice_qxl_monitors_config_async.
    
    RHBZ: 770842
    
    Signed-off-by: Alon Levy <alevy at redhat.com>
    Signed-off-by: Gerd Hoffmann <kraxel at redhat.com>

commit 99390f657f2b58550e2ee73d1815dedf6a3d2a3f
Author: Alon Levy <alevy at redhat.com>
Date:   Tue Aug 21 13:51:32 2012 +0300

    qxl: disallow unknown revisions
    
    Signed-off-by: Alon Levy <alevy at redhat.com>
    Signed-off-by: Gerd Hoffmann <kraxel at redhat.com>

commit 8a69643598ac589a197a6c65618f5ccdc0a37038
Author: Alon Levy <alevy at redhat.com>
Date:   Tue Aug 21 13:51:31 2012 +0300

    qxl/update_area_io: guest_bug on invalid parameters
    
    Signed-off-by: Alon Levy <alevy at redhat.com>
    Signed-off-by: Gerd Hoffmann <kraxel at redhat.com>

commit 1aaa50635ba646441f9e1da578b8ca6f1dc4499c
Author: Yonit Halperin <yhalperi at redhat.com>
Date:   Tue Aug 21 13:54:20 2012 +0300

    spice: increase the verbosity of spice section in "qemu --help"
    
    Added all spice options to the help string. This can be used by libvirt
    to determine which spice related features are supported by qemu.
    
    Signed-off-by: Yonit Halperin <yhalperi at redhat.com>
    Signed-off-by: Gerd Hoffmann <kraxel at redhat.com>

commit 5851cf8944b09f1b8e4166f997b945b9e01f6ff3
Author: Yonit Halperin <yhalperi at redhat.com>
Date:   Tue Aug 21 11:51:59 2012 +0300

    spice: adding seamless-migration option to the command line
    
    The seamless-migration flag is required in order to identify
    whether libvirt supports the new QEVENT_SPICE_MIGRATE_COMPLETED or not
    (by default the flag is off).
    New libvirt versions that wait for QEVENT_SPICE_MIGRATE_COMPLETED should turn on this flag.
    When this flag is off, spice fallbacks to its old migration method, which
    can result in data loss.
    
    Signed-off-by: Yonit Halperin <yhalperi at redhat.com>
    Signed-off-by: Gerd Hoffmann <kraxel at redhat.com>

commit f2d6bb747f2791e4c44ccd4bb61268f08d909ff0
Author: Yonit Halperin <yhalperi at redhat.com>
Date:   Tue Aug 21 11:51:58 2012 +0300

    spice: add 'migrated' flag to spice info
    
    The flag is 'true' when spice migration has completed on the src side.
    It is needed for a case where libvirt dies before migration completes
    and it misses the event QEVENT_SPICE_MIGRATE_COMPLETED.
    When libvirt is restored and queries the migration status, it also needs
    to query spice and check if its migration has completed.
    
    Signed-off-by: Yonit Halperin <yhalperi at redhat.com>
    Signed-off-by: Gerd Hoffmann <kraxel at redhat.com>

commit cb57846efd3fb821fc56abf5e8da1298f8eb7361
Author: Yonit Halperin <yhalperi at redhat.com>
Date:   Tue Aug 21 11:51:57 2012 +0300

    spice migration: add QEVENT_SPICE_MIGRATE_COMPLETED
    
    When migrating, libvirt queries the migration status, and upon migration
    completions, it closes the migration src. On the other hand, when
    migration is completed, spice transfers data from the src to destination
    via the client. This data is required for keeping the spice session
    after migration, without suffering from data loss and inconsistencies.
    In order to allow this data transfer, we add QEVENT for signaling
    libvirt that spice migration has completed, and libvirt needs to wait
    for this event before quitting the src process.
    
    Signed-off-by: Yonit Halperin <yhalperi at redhat.com>
    Signed-off-by: Gerd Hoffmann <kraxel at redhat.com>

commit b91957275570611ac1dec29773a1cff5dd368825
Author: Yonit Halperin <yhalperi at redhat.com>
Date:   Tue Aug 21 11:51:56 2012 +0300

    spice: notify on vm state change only via spice_server_vm_start/stop
    
    QXLWorker->start/stop are deprecated since spice-server 0.11.2
    
    Signed-off-by: Yonit Halperin <yhalperi at redhat.com>
    Signed-off-by: Gerd Hoffmann <kraxel at redhat.com>

commit c64d3807b0faefef2fb01829055826b8d314845f
Author: Yonit Halperin <yhalperi at redhat.com>
Date:   Tue Aug 21 11:51:55 2012 +0300

    spice: notify spice server on vm start/stop
    
    Spice server needs to know about the vm state in order to prevent
    attempts to write to devices when they are stopped, mainly during
    the non-live stage of migration.
    Instead, spice will take care of restoring this writes, on the migration
    target side, after migration completes.
    
    Signed-off-by: Yonit Halperin <yhalperi at redhat.com>
    Signed-off-by: Gerd Hoffmann <kraxel at redhat.com>

commit a906ed8fbccf2e286bcd1fedcb77ac96462005e3
Author: Christophe Fergeau <cfergeau at redhat.com>
Date:   Mon Aug 13 10:32:32 2012 +0200

    spice: abort on invalid streaming cmdline params
    
    When parsing its command line parameters, spice aborts when it
    finds unexpected values, except for the 'streaming-video' option.
    This happens because the parsing of the parameters for this option
    is done using the 'name2enum' helper, which does not error out
    on unknown values. Using the 'parse_name' helper makes sure we
    error out in this case. Looking at git history, the use of
    'name2enum' instead of 'parse_name' seems to have been an oversight,
    so let's change to that now.
    
    Fixes rhbz#831708
    
    Signed-off-by: Gerd Hoffmann <kraxel at redhat.com>