1. 17 1月, 2013 3 次提交
  2. 15 1月, 2013 2 次提交
  3. 13 1月, 2013 1 次提交
  4. 11 1月, 2013 1 次提交
  5. 19 12月, 2012 10 次提交
  6. 17 12月, 2012 1 次提交
  7. 31 10月, 2012 1 次提交
  8. 24 10月, 2012 4 次提交
  9. 23 10月, 2012 1 次提交
    • A
      Rename target_phys_addr_t to hwaddr · a8170e5e
      Avi Kivity 提交于
      target_phys_addr_t is unwieldly, violates the C standard (_t suffixes are
      reserved) and its purpose doesn't match the name (most target_phys_addr_t
      addresses are not target specific).  Replace it with a finger-friendly,
      standards conformant hwaddr.
      
      Outstanding patchsets can be fixed up with the command
      
        git rebase -i --exec 'find -name "*.[ch]"
                              | xargs s/target_phys_addr_t/hwaddr/g' origin
      Signed-off-by: NAvi Kivity <avi@redhat.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      a8170e5e
  10. 05 10月, 2012 2 次提交
  11. 29 9月, 2012 1 次提交
    • P
      block: introduce block job error · 32c81a4a
      Paolo Bonzini 提交于
      The following behaviors are possible:
      
      'report': The behavior is the same as in 1.1.  An I/O error,
      respectively during a read or a write, will complete the job immediately
      with an error code.
      
      'ignore': An I/O error, respectively during a read or a write, will be
      ignored.  For streaming, the job will complete with an error and the
      backing file will be left in place.  For mirroring, the sector will be
      marked again as dirty and re-examined later.
      
      'stop': The job will be paused and the job iostatus will be set to
      failed or nospace, while the VM will keep running.  This can only be
      specified if the block device has rerror=stop and werror=stop or enospc.
      
      'enospc': Behaves as 'stop' for ENOSPC errors, 'report' for others.
      
      In all cases, even for 'report', the I/O error is reported as a QMP
      event BLOCK_JOB_ERROR, with the same arguments as BLOCK_IO_ERROR.
      
      It is possible that while stopping the VM a BLOCK_IO_ERROR event will be
      reported and will clobber the event from BLOCK_JOB_ERROR, or vice versa.
      This is not really avoidable since stopping the VM completes all pending
      I/O requests.  In fact, it is already possible now that a series of
      BLOCK_IO_ERROR events are reported with rerror=stop, because vm_stop
      calls bdrv_drain_all and this can generate further errors.
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      Reviewed-by: NEric Blake <eblake@redhat.com>
      Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      32c81a4a
  12. 26 9月, 2012 2 次提交
  13. 07 9月, 2012 1 次提交
  14. 06 9月, 2012 5 次提交
  15. 05 9月, 2012 1 次提交
    • Y
      spice migration: add QEVENT_SPICE_MIGRATE_COMPLETED · 2fdd16e2
      Yonit Halperin 提交于
      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: NYonit Halperin <yhalperi@redhat.com>
      Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
      2fdd16e2
  16. 24 8月, 2012 1 次提交
  17. 23 8月, 2012 1 次提交
    • A
      monitor: move json init from OPEN event to init · 58617a79
      Anthony Liguori 提交于
      At some point in the past, the OPEN event was changed to be issued from a
      bottom half.  This creates a small window whereas a data callback registered in
      init may be invoked before the OPEN event has been issued.
      
      This is reproducible with:
      
       echo "{'execute': 'qmp_capabilities'}" | qemu-system-x86_64 -M none -qmp stdio
      
      We can fix this for the monitor by moving the parser initialization to init.
      
      The remaining state that is set in OPEN appears harmless.
      Reported-by: NDaniel Berrange <berrange@redhat.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      58617a79
  18. 21 8月, 2012 1 次提交
  19. 15 8月, 2012 1 次提交