1. 06 12月, 2011 2 次提交
  2. 05 12月, 2011 2 次提交
  3. 27 10月, 2011 1 次提交
  4. 25 10月, 2011 1 次提交
    • Y
      spice: turn client_migrate_info to async · edc5cb1a
      Yonit Halperin 提交于
      RHBZ 737921
      Spice client is required to connect to the migration target before/as migration
      starts. Since after migration starts, the target qemu is blocked and cannot accept new spice client
      we trigger the connection to the target upon client_migrate_info command.
      client_migrate_info completion cb will be called after spice client has been
      connected to the target (or a timeout). See following patches and spice patches.
      Signed-off-by: NYonit Halperin <yhalperi@redhat.com>
      Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
      edc5cb1a
  5. 06 10月, 2011 1 次提交
  6. 04 10月, 2011 4 次提交
  7. 03 10月, 2011 1 次提交
  8. 01 9月, 2011 3 次提交
  9. 03 8月, 2011 1 次提交
  10. 22 7月, 2011 1 次提交
  11. 01 6月, 2011 1 次提交
    • L
      HMP: Use QMP inject nmi implementation · e9b4b432
      Luiz Capitulino 提交于
      This **CHANGES** the human monitor "nmi" command behavior.
      
      Currently it accepts an CPU argument which, when provided, will send
      the NMI to the specified CPU. This feature is of discussable value
      though and HMP shouldn't have more features than QMP, so let's use
      QMP's instead (it's also simpler).
      Signed-off-by: NLuiz Capitulino <lcapitulino@redhat.com>
      e9b4b432
  12. 11 3月, 2011 1 次提交
  13. 10 2月, 2011 1 次提交
  14. 31 1月, 2011 1 次提交
    • C
      block: add block_resize monitor command · 6d4a2b3a
      Christoph Hellwig 提交于
      Add a monitor command that allows resizing of block devices while
      qemu is running.  It uses the existing bdrv_truncate method already
      used by qemu-img to do it's work.  Compared to qemu-img the size
      parsing is very simplicistic, but I think having a properly numering
      object is more useful for non-humand monitor users than having
      the units and relative resize parsing.
      
      For SCSI devices the new size can be updated in Linux guests by
      doing the following shell command:
      
      	echo > /sys/class/scsi_device/0:0:0:0/device/rescan
      
      For ATA devices I don't know of a way to update the block device
      size in Linux system, and for virtio-blk the next two patches
      will provide an automatic update of the size when this command
      is issued on the host.
      Signed-off-by: NChristoph Hellwig <hch@lst.de>
      Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      6d4a2b3a
  15. 24 1月, 2011 1 次提交
    • G
      spice/vnc: client migration. · e866e239
      Gerd Hoffmann 提交于
      Handle spice client migration, i.e. inform a spice client connected
      about the new host and connection parameters, so it can move over the
      connection automatically.
      
      The monitor command has a not-yet used protocol argument simliar to
      set_password and expire_password commands.  This allows to add a simliar
      feature to vnc in the future.  Daniel Berrange plans to work on this.
      Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
      e866e239
  16. 22 1月, 2011 1 次提交
    • J
      Add "broadcast" option for mce command · 31ce5e0c
      Jin Dongming 提交于
      When the following test case is injected with mce command, maybe user could not
      get the expected result.
          DATA
                     command cpu bank status             mcg_status  addr   misc
              (qemu) mce     1   1    0xbd00000000000000 0x05        0x1234 0x8c
      
          Expected Result
                 panic type: "Fatal Machine check"
      
      That is because each mce command can only inject the given cpu and could not
      inject mce interrupt to other cpus. So user will get the following result:
          panic type: "Fatal machine check on current CPU"
      
      "broadcast" option is used for injecting dummy data into other cpus. Injecting
      mce with this option the expected result could be gotten.
      
      Usage:
          Broadcast[on]
                 command broadcast cpu bank status             mcg_status  addr   misc
          (qemu) mce     -b        1   1    0xbd00000000000000 0x05        0x1234 0x8c
      
          Broadcast[off]
                 command cpu bank status             mcg_status  addr   misc
          (qemu) mce     1   1    0xbd00000000000000 0x05        0x1234 0x8c
      Signed-off-by: NJin Dongming <jin.dongming@np.css.fujitsu.com>
      Signed-off-by: NMarcelo Tosatti <mtosatti@redhat.com>
      31ce5e0c
  17. 24 12月, 2010 1 次提交
  18. 19 12月, 2010 1 次提交
  19. 17 12月, 2010 1 次提交
  20. 09 12月, 2010 1 次提交
  21. 25 11月, 2010 1 次提交
    • R
      Implement drive_del to decouple block removal from device removal · 9063f814
      Ryan Harper 提交于
      Currently device hotplug removal code is tied to device removal via
      ACPI.  All pci devices that are removable via device_del() require the
      guest to respond to the request.  In some cases the guest may not
      respond leaving the device still accessible to the guest.  The management
      layer doesn't currently have a reliable way to revoke access to host
      resource in the presence of an uncooperative guest.
      
      This patch implements a new monitor command, drive_del, which
      provides an explicit command to revoke access to a host block device.
      
      drive_del first quiesces the block device (qemu_aio_flush;
      bdrv_flush() and bdrv_close()).  This prevents further IO from being
      submitted against the host device.  Finally, drive_del cleans up
      pointers between the drive object (host resource) and the device
      object (guest resource).
      Signed-off-by: NRyan Harper <ryanh@us.ibm.com>
      Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      9063f814
  22. 04 11月, 2010 1 次提交
  23. 01 10月, 2010 3 次提交
  24. 10 9月, 2010 2 次提交
    • S
      trace: Add trace-file command to open/close/flush trace file · c5ceb523
      Stefan Hajnoczi 提交于
      This patch adds the trace-file command:
      
        trace-file [on|off|flush]
      
        Open, close, or flush the trace file.  If no argument is given,
        the status of the trace file is displayed.
      
      The trace file is turned on by default but is only written out when the
      trace buffer becomes full.  The flush operation can be used to force
      write out at any time.
      
      Turning off the trace file does not change the state of trace events;
      tracing will continue to the trace buffer.  When the trace file is off,
      use "info trace" to display the contents of the trace buffer in memory.
      Signed-off-by: NStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      
      This commit also contains the trace-file sub-command from the following
      commit:
      
      commit 5ce8d1a957afae2c52ad748944ce72848ccf57bd
      Author: Prerna Saxena <prerna@linux.vnet.ibm.com>
      Date:   Wed Aug 4 16:23:54 2010 +0530
      
          trace: Add options to specify trace file name at startup and runtime
      
          This patch adds an optional command line switch '-trace' to specify the
          filename to write traces to, when qemu starts.
          Eg, If compiled with the 'simple' trace backend,
          [temp@system]$ qemu -trace FILENAME IMAGE
          Allows the binary traces to be written to FILENAME instead of the option
          set at config-time.
      
          Also, this adds monitor sub-command 'set' to trace-file commands to
          dynamically change trace log file at runtime.
          Eg,
          (qemu)trace-file set FILENAME
          This allows one to set trace outputs to FILENAME from the default
          specified at startup.
      Signed-off-by: NPrerna Saxena <prerna@linux.vnet.ibm.com>
      Signed-off-by: NStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      c5ceb523
    • P
      trace: Support for dynamically enabling/disabling trace events · 22890ab5
      Prerna Saxena 提交于
      This patch adds support for dynamically enabling/disabling of trace events.
      This is done by internally maintaining each trace event's state, and
      permitting logging of data from a trace event only if it is in an
      'active' state.
      
      Monitor commands added :
      1) info trace-events 		: to view all available trace events and
      				  their state.
      2) trace-event NAME on|off 	: to enable/disable data logging from a
      				  given trace event.
      				  Eg, trace-event paio_submit off
      				  	disables logging of data when
      					paio_submit is hit.
      
      By default, all trace-events are disabled. One can enable desired trace-events
      via the monitor.
      Signed-off-by: NPrerna Saxena <prerna@linux.vnet.ibm.com>
      Signed-off-by: NStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      
      trace: Monitor command 'info trace'
      
      Monitor command 'info trace' to display contents of trace buffer
      Signed-off-by: NPrerna Saxena <prerna@linux.vnet.ibm.com>
      Signed-off-by: NStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      
      trace: Remove monitor.h dependency from simpletrace
      
      User-mode targets don't have a monitor so the simple trace backend
      currently does not build on those targets.  This patch abstracts the
      monitor printing interface so there is no direct coupling between
      simpletrace and the monitor.
      Signed-off-by: NStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      22890ab5
  25. 23 8月, 2010 2 次提交
  26. 02 7月, 2010 1 次提交
  27. 13 6月, 2010 1 次提交
  28. 02 6月, 2010 2 次提交
    • J
      QMP: Introduce commands documentation · b40292e7
      Jan Kiszka 提交于
      One of the most important missing feature in QMP today is its
      supported commands documentation.
      
      The plan is to make it part of self-description support, however
      self-description is a big task we have been postponing for a
      long time now and still don't know when it's going to be done.
      
      In order not to compromise QMP adoption and make users' life easier,
      this commit adds a simple text documentation which fully describes
      all QMP supported commands.
      
      This is not ideal for a number of reasons (harder to maintain,
      text-only, etc) but does improve the current situation. To avoid at
      least divering from the user monitor help and texi snippets, QMP bits
      are also maintained inside qemu-monitor.hx, and hxtool is extended to
      generate a single text file from them.
      Signed-off-by: NJan Kiszka <jan.kiszka@siemens.com>
      Signed-off-by: NLuiz Capitulino <lcapitulino@redhat.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      b40292e7
    • J
      monitor: Reorder info documentation · 33572ece
      Jan Kiszka 提交于
      Push the doc fragments for the info command to the end of
      qemu-monitor.hx. This helps to establish a proper layout in the upcoming
      QMP documentation.
      Signed-off-by: NJan Kiszka <jan.kiszka@siemens.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      33572ece