1. 19 Dec, 2012 4 commits
  2. 02 Nov, 2012 4 commits
  3. 23 Oct, 2012 2 commits
    • Paolo Bonzini's avatar
      migration (incoming): add error propagation to fd and exec protocols · 43eaae28
      Paolo Bonzini authored
      And remove the superfluous integer return value.
      Reviewed-by: default avatarLuiz Capitulino <lcapitulino@redhat.com>
      Signed-off-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
      43eaae28
    • Paolo Bonzini's avatar
      migration (outgoing): add error propagation for all protocols · f37afb5a
      Paolo Bonzini authored
      Error propagation is already there for socket backends.  Add it to other
      protocols, simplifying code that tests for errors that will never happen.
      With all protocols understanding Error, the code can be simplified
      further by removing the return value.
      
      Unfortunately, the quality of error messages varies depending
      on where the error is detected, because no Error is passed to the
      NonBlockingConnectHandler.  Thus, the exact error message still cannot
      be sent to the user if the OS reports it asynchronously via SO_ERROR.
      If NonBlockingConnectHandler received an Error**, we could for
      example report the error class and/or message via a new field of the
      query-migration command even if it is reported asynchronously.
      
      Before:
      
          (qemu) migrate fd:ffff
          migrate: An undefined error has occurred
          (qemu) info migrate
          (qemu)
      
      After:
      
          (qemu) migrate fd:ffff
          migrate: File descriptor named 'ffff' has not been found
          (qemu) info migrate
          capabilities: xbzrle: off
          Migration status: failed
          total time: 0 milliseconds
      Signed-off-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
      f37afb5a
  4. 13 Jan, 2012 1 commit
  5. 12 Dec, 2011 2 commits
  6. 20 Oct, 2011 5 commits
  7. 20 Aug, 2011 1 commit
  8. 15 Apr, 2011 1 commit
  9. 22 Jun, 2010 1 commit
  10. 04 Jun, 2010 1 commit
    • Blue Swirl's avatar
      migration-exec: fix OpenBSD build warning · 0ffbba35
      Blue Swirl authored
      Add include directives to get WIFEXITED() and WEXITSTATUS() macros defined.
      
      Fixes warnings:
        CC    migration-exec.o
      /src/qemu/migration-exec.c: In function `exec_close':
      /src/qemu/migration-exec.c:53: warning: implicit declaration of function `WIFEXITED'
      /src/qemu/migration-exec.c:54: warning: implicit declaration of function `WEXITSTATUS'
      Signed-off-by: default avatarBlue Swirl <blauwirbel@gmail.com>
      0ffbba35
  11. 03 Jun, 2010 1 commit
  12. 19 Mar, 2010 1 commit
  13. 17 Mar, 2010 1 commit
  14. 06 Feb, 2010 1 commit
  15. 03 Dec, 2009 1 commit
  16. 17 Nov, 2009 1 commit
    • lirans@il.ibm.com's avatar
      Block live migration · c163b5ca
      lirans@il.ibm.com authored
      This patch introduces block migration called during live migration. Block
      are being copied to the destination in an async way. First the code will
      transfer the whole disk and then transfer all dirty blocks accumulted during
      the migration.
      Still need to improve transition from the iterative phase of migration to the
      end phase. For now transition will take place when all blocks transfered once,
      all the dirty blocks will be transfered during the end phase (guest is
      suspended).
      
      Changes from v4:
      - Global variabels moved to a global state structure allocated dynamically.
      - Minor coding style issues.
      - Poll block.c for tracking of dirty blocks instead of manage it here.
      Signed-off-by: default avatarLiran Schour <lirans@il.ibm.com>
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
      c163b5ca
  17. 24 Aug, 2009 2 commits
  18. 30 Jul, 2009 1 commit
    • Paolo Bonzini's avatar
      fix migration to obey -S · d399f677
      Paolo Bonzini authored
      Since migration returns right away, starting the VM right
      after calling qemu_start_incoming_migration is wrong even
      if -S is not passed.  We have to do this after migration
      has completed.
      
      Cc: Glauber Costa  <glommer@redhat.com>
      Cc: Anthony Liguori  <aliguori@us.ibm.com>
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
      d399f677
  19. 16 Jul, 2009 1 commit
    • Paolo Bonzini's avatar
      honor -S on incoming migration · 89befdd1
      Paolo Bonzini authored
      -S is not honored by qemu on incoming migration.  If a domain is migrated
      while paused, thus, it will start running on the remote machine; this
      is wrong.
      
      Given the trivial patch to fix this, it looks more like a thinko
      than anything else, probably dating back to the qemu-kvm merge.
      The interesting part is that the -S mechanism was in fact *used* when
      migrating (setting autostart = 0) and the incoming migration code was
      starting the VM at the end of the migration.
      
      Since I was removing the vm_start from there, I also corrected a related
      imprecision.  The code was doing a vm_stop "just in case", but we can
      be sure that the VM is not running---the vm_start call in vl.c has not
      been reached yet.  So the vm_stop is removed together with the vm_start.
      Signed-off-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
      89befdd1
  20. 27 May, 2009 1 commit
    • Chris Lalancette's avatar
      Allow monitor interaction when using migrate -exec · 8a43b1ea
      Chris Lalancette authored
      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: default avatarChris Lalancette <clalance@redhat.com>
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
      8a43b1ea
  21. 05 Mar, 2009 2 commits
    • aliguori's avatar
      monitor: Decouple terminals (Jan Kiszka) · 731b0364
      aliguori authored
      Currently all registered (and activate) monitor terminals work in
      broadcast mode: Everyone sees what someone else types on some other
      terminal and what the monitor reports back. This model is broken when
      you have a management monitor terminal that is automatically operated
      and some other terminal used for independent guest inspection. Such
      additional terminals can be multiplexed device channels or a gdb
      frontend connected to QEMU's stub.
      
      Therefore, this patch decouples the buffers and states of all monitor
      terminals, allowing the user to operate them independently. It finally
      starts to use the 'mon' parameter that was introduced earlier with the
      API rework. It also defines the default monitor: the first instantance
      that has the MONITOR_IS_DEFAULT flag set, and that is the monitor
      created via the "-monitor" command line switch (or "vc" if none is
      given).
      
      As the patch requires to rework the monitor suspension interface, it
      also takes the freedom to make it "truely" suspending (so far suspending
      meant suppressing the prompt, but inputs were still processed).
      Signed-off-by: default avatarJan Kiszka <jan.kiszka@siemens.com>
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
      
      
      git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@6715 c046a42c-6fe2-441c-8c8c-71466251a162
      731b0364
    • aliguori's avatar
      monitor: Rework API (Jan Kiszka) · 376253ec
      aliguori authored
      Refactor the monitor API and prepare it for decoupled terminals:
      term_print functions are renamed to monitor_* and all monitor services
      gain a new parameter (mon) that will once refer to the monitor instance
      the output is supposed to appear on. However, the argument remains
      unused for now. All monitor command callbacks are also extended by a mon
      parameter so that command handlers are able to pass an appropriate
      reference to monitor output services.
      
      For the case that monitor outputs so far happen without clearly
      identifiable context, the global variable cur_mon is introduced that
      shall once provide a pointer either to the current active monitor (while
      processing commands) or to the default one. On the mid or long term,
      those use case will be obsoleted so that this variable can be removed
      again.
      
      Due to the broad usage of the monitor interface, this patch mostly deals
      with converting users of the monitor API. A few of them are already
      extended to pass 'mon' from the command handler further down to internal
      functions that invoke monitor_printf.
      
      At this chance, monitor-related prototypes are moved from console.h to
      a new monitor.h. The same is done for the readline API.
      Signed-off-by: default avatarJan Kiszka <jan.kiszka@siemens.com>
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
      
      
      git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@6711 c046a42c-6fe2-441c-8c8c-71466251a162
      376253ec
  22. 05 Feb, 2009 1 commit
  23. 12 Nov, 2008 1 commit
  24. 11 Nov, 2008 1 commit