1. 14 Oct, 2014 1 commit
    • Gonglei's avatar
      qmp: Print descriptions of object properties · 07d09c58
      Gonglei authored
      Add a new "description" field to DevicePropertyInfo.
      The descriptions can serve as documentation in the code,
      and they can be used to provide better help. For example:
      
      $./qemu-system-x86_64 -device virtio-blk-pci,?
      
      Before this patch:
      
      virtio-blk-pci.iothread=link<iothread>
      virtio-blk-pci.x-data-plane=bool
      virtio-blk-pci.scsi=bool
      virtio-blk-pci.config-wce=bool
      virtio-blk-pci.serial=str
      virtio-blk-pci.secs=uint32
      virtio-blk-pci.heads=uint32
      virtio-blk-pci.cyls=uint32
      virtio-blk-pci.discard_granularity=uint32
      virtio-blk-pci.bootindex=int32
      virtio-blk-pci.opt_io_size=uint32
      virtio-blk-pci.min_io_size=uint16
      virtio-blk-pci.physical_block_size=uint16
      virtio-blk-pci.logical_block_size=uint16
      virtio-blk-pci.drive=str
      virtio-blk-pci.virtio-backend=child<virtio-blk-device>
      virtio-blk-pci.command_serr_enable=on/off
      virtio-blk-pci.multifunction=on/off
      virtio-blk-pci.rombar=uint32
      virtio-blk-pci.romfile=str
      virtio-blk-pci.addr=pci-devfn
      virtio-blk-pci.event_idx=on/off
      virtio-blk-pci.indirect_desc=on/off
      virtio-blk-pci.vectors=uint32
      virtio-blk-pci.ioeventfd=on/off
      virtio-blk-pci.class=uint32
      
      After:
      
      virtio-blk-pci.iothread=link<iothread>
      virtio-blk-pci.x-data-plane=bool (on/off)
      virtio-blk-pci.scsi=bool (on/off)
      virtio-blk-pci.config-wce=bool (on/off)
      virtio-blk-pci.serial=str
      virtio-blk-pci.secs=uint32
      virtio-blk-pci.heads=uint32
      virtio-blk-pci.cyls=uint32
      virtio-blk-pci.discard_granularity=uint32
      virtio-blk-pci.bootindex=int32
      virtio-blk-pci.opt_io_size=uint32
      virtio-blk-pci.min_io_size=uint16
      virtio-blk-pci.physical_block_size=uint16 (A power of two between 512 and 32768)
      virtio-blk-pci.logical_block_size=uint16 (A power of two between 512 and 32768)
      virtio-blk-pci.drive=str (ID of a drive to use as a backend)
      virtio-blk-pci.virtio-backend=child<virtio-blk-device>
      virtio-blk-pci.command_serr_enable=bool (on/off)
      virtio-blk-pci.multifunction=bool (on/off)
      virtio-blk-pci.rombar=uint32
      virtio-blk-pci.romfile=str
      virtio-blk-pci.addr=int32 (Slot and optional function number, example: 06.0 or 06)
      virtio-blk-pci.event_idx=bool (on/off)
      virtio-blk-pci.indirect_desc=bool (on/off)
      virtio-blk-pci.vectors=uint32
      virtio-blk-pci.ioeventfd=bool (on/off)
      virtio-blk-pci.class=uint32
      
      Cc: Markus Armbruster <armbru@redhat.com>
      Signed-off-by: default avatarGonglei <arei.gonglei@huawei.com>
      Reviewed-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
      Reviewed-by: default avatarMichael S. Tsirkin <mst@redhat.com>
      Reviewed-by: default avatarEric Blake <eblake@redhat.com>
      Signed-off-by: default avatarAndreas Färber <afaerber@suse.de>
      07d09c58
  2. 15 Aug, 2014 1 commit
  3. 07 Jul, 2014 1 commit
    • Stefan Hajnoczi's avatar
      qmp: show QOM properties in device-list-properties · f4eb32b5
      Stefan Hajnoczi authored
      Devices can use a mix of qdev and QOM properties.  Currently only the
      qdev properties are displayed by device-list-properties.
      
      This patch extends the property enumeration algorithm to also display
      QOM properties (excluding the implicit "type", "realized",
      "hotpluggable", and "parent_bus" properties).
      
      When a qdev property exists, use the qdev type name to preserve
      backwards compatibility.  QOM type names can be different for bool (qdev
      on/off) and str (used by qdev pointers).
      Signed-off-by: default avatarStefan Hajnoczi <stefanha@redhat.com>
      f4eb32b5
  4. 19 Jun, 2014 3 commits
  5. 18 Jun, 2014 1 commit
  6. 09 May, 2014 2 commits
  7. 07 May, 2014 1 commit
  8. 05 May, 2014 1 commit
  9. 25 Apr, 2014 2 commits
  10. 12 Mar, 2014 1 commit
  11. 02 Mar, 2014 1 commit
  12. 28 Jan, 2014 2 commits
  13. 06 Jan, 2014 2 commits
  14. 16 Dec, 2013 1 commit
  15. 01 May, 2013 1 commit
  16. 30 Apr, 2013 1 commit
  17. 15 Apr, 2013 1 commit
  18. 19 Dec, 2012 4 commits
  19. 18 Nov, 2012 1 commit
  20. 02 Nov, 2012 1 commit
  21. 30 Oct, 2012 1 commit
  22. 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>
      1e998146
  23. 23 Oct, 2012 1 commit
  24. 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>
      b224e5e2
  25. 15 Aug, 2012 1 commit
  26. 13 Aug, 2012 2 commits
  27. 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>
      ad02b96a
  28. 24 Feb, 2012 1 commit
  29. 07 Feb, 2012 1 commit
  30. 03 Feb, 2012 1 commit