• All,
         I've recently been playing around with migration via exec.  Unfortunately,
    when starting the incoming qemu process with "-incoming exec:cmd", it suffers
    the same problem that -incoming tcp used to suffer; namely, that you can't
    interact with the monitor until after the migration has happened.  This causes
    problems for libvirt usage of -incoming exec, since libvirt expects to be able
    to access the monitor ahead of time.  This fairly simple patch allows you to
    access the monitor both before and after the migration has completed using exec.
    
    (note: developed/tested with qemu-kvm, but applies perfectly fine to qemu)
    
    Signed-off-by: Chris Lalancette <clalance@redhat.com>
    Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
    Chris Lalancette authored
     
    Browse Code »

  • Add the parameter 'order' to qemu_register_reset and sort callbacks on
    registration. On system reset, callbacks with lower order will be
    invoked before those with higher order. Update all existing users to the
    standard order 0.
    
    Note: At least for x86, the existing users seem to assume that handlers
    are called in their registration order. Therefore, the patch preserves
    this property. If someone feels bored, (s)he could try to identify this
    dependency and express it properly on callback registration.
    
    Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
    Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
    Jan Kiszka authored
     
    Browse Code »
  • This patch converts the current callers of qemu_fopen_ops().
    
    Signed-off-by: Glauber Costa <glommer@redhat.com>
    Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
    Glauber Costa authored
     
    Browse Code »

  • The only target dependency for most hardware is sizeof(target_phys_addr_t).
    Build these files into a convenience library, and use that instead of
    building for every target.
    
    Remove and poison various target specific macros to avoid bogus target
    dependencies creeping back in.
    
    Big/Little endian is not handled because devices should not know or care
    about this to start with.
    
    Signed-off-by: Paul Brook <paul@codesourcery.com>
    Paul Brook authored
     
    Browse Code »



  • KVM's live migration support included support for exec: URLs, allowing system
    state to be written or received via an arbitrary popen()ed subprocess. This
    provides a convenient way to pipe state through a compression algorithm or an
    arbitrary network transport on its way to its destination, and a convenient way
    to write state to disk; libvirt's qemu driver currently uses migration to exec:
    targets for this latter purpose.
    
    This version of the patch refactors now-common code from migrate-tcp.c into
    migrate.c. 
    
    Signed-off-by: Charles Duffy <Charles_Duffy@messageone.com>
    Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
    
    
    
    git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@5694 c046a42c-6fe2-441c-8c8c-71466251a162
    aliguori authored
     
    Browse Code »


  • This patch allows QEMUFile's read and write operations to return 
    negative error codes.  This is necessary to detect things like closed 
    streams during live migration.
    
    It also removes unused code for QEMUFileFD write path.  Finally, it 
    makes sure to avoid attempting to flush an output buffer if the file
    is only being used for input.  This was spotted by Uri Lublin.
    
    Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
    
    
    
    git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@5474 c046a42c-6fe2-441c-8c8c-71466251a162
    aliguori authored
     
    Browse File »

  • The current savevm/loadvm protocol has some draw backs.  It does not support
    the ability to do progressive saving which means it cannot be used for live
    checkpointing or migration.  The sections sizes are 32-bit integers which
    means that it will not function when using more than 4GB of memory for a guest.
    It attempts to seek within the output file which means it cannot be streamed.
    The current protocol also is pretty lax about how it supports forward
    compatibility.  If a saved section version is greater than what the restore
    code support, the restore code generally treats the saved data as being in
    whatever version it supports.  This means that restoring a saved VM on an older
    version of QEMU will likely result in silent guest failure.
    
    This patch introduces a new version of the savevm protocol.  It has the
    following features:
    
     * Support for progressive save of sections (for live checkpoint/migration)
     * An asynchronous API for doing save
     * Support for interleaving multiple progressive save sections
       (for future support of memory hot-add/storage migration)
     * Fully streaming format
     * Strong section version checking
    
    Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
    
    
    
    git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@5434 c046a42c-6fe2-441c-8c8c-71466251a162
    aliguori authored
     
    Browse Code »