1. 28 Jan, 2014 2 commits
  2. 06 Jan, 2014 2 commits
  3. 16 Dec, 2013 1 commit
  4. 01 May, 2013 1 commit
  5. 30 Apr, 2013 1 commit
  6. 15 Apr, 2013 1 commit
  7. 19 Dec, 2012 4 commits
  8. 18 Nov, 2012 1 commit
  9. 02 Nov, 2012 1 commit
  10. 30 Oct, 2012 1 commit
  11. 24 Oct, 2012 1 commit
    • Paolo Bonzini's avatar
      qmp: handle stop/cont in INMIGRATE state · 1e998146
      Paolo Bonzini authored
      Right now, stop followed by an incoming migration will let the
      virtual machine start.  cont before an incoming migration instead
      will fail.
      This is bad because the actual behavior is not predictable; it is
      racy with respect to the start of the incoming migration.  That's
      because incoming migration is blocking, and thus will delay the
      processing of stop/cont until the end of the migration.
      In addition, there's nothing that really prevents the user from
      typing the block device's passwords before incoming migration is
      done, so returning the DeviceEncrypted error is also helpful in
      the QMP case.
      Both things can be fixed by just toggling the autostart variable when
      stop/cont are called in INMIGRATE state.
      Note that libvirt is currently working around the race by looping
      if the MigrationExpected answer is returned.  After this patch, the
      command will return right away without ever raising an error.
      Signed-off-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
      Signed-off-by: default avatarLuiz Capitulino <lcapitulino@redhat.com>
  12. 23 Oct, 2012 1 commit
  13. 26 Sep, 2012 1 commit
    • Luiz Capitulino's avatar
      qapi: convert add_client · b224e5e2
      Luiz Capitulino authored
      Also fixes a few issues while there:
       1. The fd returned by monitor_get_fd() leaks in most error conditions
       2. monitor_get_fd() return value is not checked. Best case we get
          an error that is not correctly reported, worse case one of the
          functions using the fd (with value of -1) will explode
       3. A few error conditions aren't reported
       4. We now "use up" @fdname always.  Before, it was left alone for
          invalid @protocol
      Signed-off-by: default avatarLuiz Capitulino <lcapitulino@redhat.com>
      Reviewed-by: default avatarMarkus Armbruster <armbru@redhat.com>
  14. 15 Aug, 2012 1 commit
  15. 13 Aug, 2012 2 commits
  16. 08 May, 2012 1 commit
    • Luiz Capitulino's avatar
      runstate: introduce suspended state · ad02b96a
      Luiz Capitulino authored
      QEMU enters in this state when the guest suspends to ram (S3).
      This is important so that HMP users and QMP clients can know that
      the guest is suspended. QMP also has an event for this, but events
      are not reliable and are limited (ie. a client can connect to QEMU
      after the event has been emitted).
      Having a different state for S3 brings a new issue, though. Every
      device that doesn't run when the VM is stopped but wants to run
      when the VM is suspended has to check for RUN_STATE_SUSPENDED
      explicitly. This is the case for the keyboard and mouse devices,
      for example.
      Signed-off-by: default avatarLuiz Capitulino <lcapitulino@redhat.com>
      Acked-by: default avatarGerd Hoffmann <kraxel@redhat.com>
  17. 24 Feb, 2012 1 commit
  18. 07 Feb, 2012 1 commit
  19. 03 Feb, 2012 2 commits
    • Anthony Liguori's avatar
      qom: move properties from qdev to object · 57c9fafe
      Anthony Liguori authored
      This is mostly code movement although not entirely.  This makes properties part
      of the Object base class which means that we can now start using Object in a
      meaningful way outside of qdev.
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
    • Anthony Liguori's avatar
      qom: add new command to search for types · 5eeee3fa
      Anthony Liguori authored
      This adds a command that allows searching for types that implement a property.
      This allows you to do things like search for all available PCIDevices.  In the
      future, we'll also have a standard interface for things with a BlockDriverState
      property that a PCIDevice could implement.
      This will enable search queries like, "any type that implements the BlockDevice
      interface" which would allow management tools to present available block devices
      without having to hard code device names.  Since an object can implement
      multiple interfaces, one device could act both as a BlockDevice and a
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
  20. 18 Jan, 2012 5 commits
  21. 13 Jan, 2012 1 commit
  22. 15 Dec, 2011 2 commits
  23. 06 Dec, 2011 1 commit
  24. 27 Oct, 2011 3 commits
  25. 04 Oct, 2011 2 commits