1. 24 Jan, 2014 1 commit
  2. 06 Jan, 2014 3 commits
  3. 09 Dec, 2013 1 commit
    • Vincenzo Maffione's avatar
      net: Adding netmap network backend · 58952137
      Vincenzo Maffione authored
      This patch adds support for a network backend based on netmap.
      netmap is a framework for high speed packet I/O. You can use it
      to build extremely fast traffic generators, monitors, software
      switches or network middleboxes. Its companion software switch
      VALE lets you interconnect virtual machines.
      netmap and VALE are implemented as a non-intrusive kernel module,
      support NICs from multiple vendors, are part of standard FreeBSD
      distributions and available in source format for Linux too.
      To compile QEMU with netmap support, use the following configure
          ./configure [...] --enable-netmap --extra-cflags=-I/path/to/netmap/sys
      where "/path/to/netmap" contains the netmap source code, available at
      The same webpage contains more information about the netmap project
      (together with papers and presentations).
      Signed-off-by: default avatarVincenzo Maffione <v.maffione@gmail.com>
      Signed-off-by: default avatarStefan Hajnoczi <stefanha@redhat.com>
  4. 12 Sep, 2013 2 commits
  5. 30 Aug, 2013 2 commits
  6. 15 Jul, 2013 1 commit
    • Stefan Hajnoczi's avatar
      block: add drive_backup HMP command · de90930a
      Stefan Hajnoczi authored
      Make "drive_backup" available on the HMP monitor:
        drive_backup [-n] [-f] device target [format]
      The -n flag requests QEMU to reuse the image found in new-image-file,
      instead of recreating it from scratch.
      The -f flag requests QEMU to copy the whole disk, so that the result
      does not need a backing file.  Note that this flag *must* currently be
      passed since the other sync modes ('none' and 'top') have not been
      implemented yet.  Requiring it ensures that "drive_backup" behaves like
      Signed-off-by: default avatarStefan Hajnoczi <stefanha@redhat.com>
      Reviewed-by: default avatarEric Blake <eblake@redhat.com>
      Signed-off-by: default avatarKevin Wolf <kwolf@redhat.com>
  7. 04 Jul, 2013 1 commit
    • David Gibson's avatar
      pci: Cleanup configuration for pci-hotplug.c · 79ca616f
      David Gibson authored
      pci-hotplug.c and the CONFIG_PCI_HOTPLUG variable which controls its
      compilation are misnamed.  They're not about PCI hotplug in general, but
      rather about the pci_add/pci_del interface which are now deprecated in
      favour of the more general device_add/device_del interface.  This patch
      therefore renames them to pci-hotplug-old.c and CONFIG_PCI_HOTPLUG_OLD.
      CONFIG_PCI_HOTPLUG=y was listed twice in {i386,x86_64}-softmmu.make for no
      particular reason, so we clean that up too.  In addition it was included in
      ppc64-softmmu.mak for which the old hotplug interface was never used and is
      unsuitable, so we remove that too.
      Most of pci-hotplug.c was additionaly protected by #ifdef TARGET_I386.  The
      small piece which wasn't is only called from the pci_add and pci_del hooks
      in hmp-commands.hx, which themselves were protected by #ifdef TARGET_I386.
      This patch therefore also removes the #ifdef from pci-hotplug-old.c,
      and changes the ifdefs in hmp-commands.hx to use CONFIG_PCI_HOTPLUG_OLD.
      Signed-off-by: default avatarDavid Gibson <david@gibson.dropbear.id.au>
      Signed-off-by: default avatarMichael S. Tsirkin <mst@redhat.com>
  8. 11 Jun, 2013 1 commit
    • Andreas Färber's avatar
      dump: Drop qmp_dump_guest_memory() stub and build for all targets · 2a78636b
      Andreas Färber authored
      qmp_dump_guest_memory() calls dump_init() and returns an Error when
      cpu_get_dump_info() returns an error, as done by the stub.
      So there is no need to have a stub for qmp_dump_guest_memory().
      Enable the documentation of the always-present dump-guest-memory command.
      That way we can drop CONFIG_HAVE_CORE_DUMP and leave configure
      completely out of the picture for target CPU features.
      Signed-off-by: default avatarAndreas Färber <afaerber@suse.de>
  9. 06 Jun, 2013 1 commit
  10. 05 Jun, 2013 1 commit
    • Stefan Hajnoczi's avatar
      blockdev: reset werror/rerror on drive_del · 293c51a6
      Stefan Hajnoczi authored
      Paolo Bonzini <pbonzini@redhat.com> suggested the following test case:
      1. Launch a guest and wait at the GRUB boot menu:
        qemu-system-x86_64 -enable-kvm -m 1024 \
         -drive if=none,cache=none,file=test.img,id=foo,werror=stop,rerror=stop
         -device virtio-blk-pci,drive=foo,id=virtio0,addr=4
      2. Hot unplug the device:
        (qemu) drive_del foo
      3. Select the first boot menu entry
      Without this patch the guest pauses due to ENOMEDIUM.  The guest is
      stuck in a continuous pause loop since the I/O request is retried and
      fails immediately again when the guest is resumed.
      With this patch the error is reported to the guest.
      Note that this scenario actually happens sometimes during libvirt disk
      hot unplug, where device_del is followed by drive_del.  I/O may still be
      submitted to the drive after drive_del if the guest does not process the
      PCI hot unplug notification.
      Reported-by: default avatarDafna Ron <dron@redhat.com>
      Signed-off-by: default avatarStefan Hajnoczi <stefanha@redhat.com>
      Reviewed-by: default avatarKevin Wolf <kwolf@redhat.com>
  11. 29 Apr, 2013 1 commit
  12. 12 Apr, 2013 1 commit
  13. 25 Mar, 2013 1 commit
  14. 13 Mar, 2013 1 commit
  15. 12 Mar, 2013 1 commit
    • Stefan Berger's avatar
      Support for TPM command line options · d1a0cf73
      Stefan Berger authored
      This patch adds support for TPM command line options.
      The command line options supported here are
      ./qemu-... -tpmdev passthrough,path=<path to TPM device>,id=<id>
                 -device tpm-tis,tpmdev=<id>,id=<other id>
      ./qemu-... -tpmdev help
      where the latter works similar to -soundhw help and shows a list of
      available TPM backends (for example 'passthrough').
      Using the type parameter, the backend is chosen, i.e., 'passthrough' for the
      passthrough driver. The interpretation of the other parameters along
      with determining whether enough parameters were provided is pushed into
      the backend driver, which needs to implement the interface function
      'create' and return a TPMDriverOpts structure if the VM can be started or
      'NULL' if not enough or bad parameters were provided.
      Monitor support for 'info tpm' has been added. It for example prints the
      (qemu) info tpm
      TPM devices:
       tpm0: model=tpm-tis
        \ tpm0: type=passthrough,path=/dev/tpm0,cancel-path=/sys/devices/pnp0/00:09/cancel
      Signed-off-by: default avatarStefan Berger <stefanb@linux.vnet.ibm.com>
      Reviewed-by: default avatarCorey Bryant <coreyb@linux.vnet.ibm.com>
      Reviewed-by: default avatarJoel Schopp <jschopp@linux.vnet.ibm.com>
      Message-id: 1361987275-26289-2-git-send-email-stefanb@linux.vnet.ibm.com
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
  16. 27 Feb, 2013 1 commit
  17. 26 Feb, 2013 1 commit
    • Peter Maydell's avatar
      qemu-log: default to stderr for logging output · 989b697d
      Peter Maydell authored
      Switch the default for qemu_log logging output from "/tmp/qemu.log"
      to stderr. This is an incompatible change in some sense, but logging
      is mostly used for debugging purposes so it shouldn't affect production
      use. The previous behaviour can be obtained by adding "-D /tmp/qemu.log"
      to the command line.
      This change requires us to:
       * update all the documentation/help text (we take the opportunity
         to smooth out minor inconsistencies between the phrasing in
         linux-user/bsd-user/system help messages)
       * make linux-user and bsd-user defer to qemu-log for the default
         logging destination rather than overriding it themselves
       * ensure that all logfile closing is done via qemu_log_close()
         and that that function doesn't close stderr
      as well as the obvious change to the behaviour of do_qemu_set_log()
      when no logfile name has been specified.
      Signed-off-by: default avatarPeter Maydell <peter.maydell@linaro.org>
      Reviewed-by: default avatarStefan Hajnoczi <stefanha@redhat.com>
      Reviewed-by: default avatarMarkus Armbruster <armbru@redhat.com>
      Message-id: 1361901160-28729-1-git-send-email-peter.maydell@linaro.org
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
  18. 06 Feb, 2013 3 commits
    • Markus Armbruster's avatar
      hmp: Disable chardev-add and chardev-remove · 8a14952c
      Markus Armbruster authored
      As a general rule, HMP commands must be built on top of the QMP API.
      Luiz and others have worked long & hard to make HMP conform to this
      Commit f1088908 added chardev-add, in violation of this rule.  QMP
      command chardev-add was added right before, with minimal features, and
      the idea to complete it step by step, then switch over the HMP command
      to use it.
      Unfortunately, we're not there, yet, and we don't want to release with
      chardev-add in a "HMP is more powerful than QMP" state.
      Disable the HMP command for now, along with its chardev-remove buddy.
      Signed-off-by: default avatarMarkus Armbruster <armbru@redhat.com>
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
    • Markus Armbruster's avatar
    • Markus Armbruster's avatar
      qemu-char: Saner naming of memchar stuff & doc fixes · 3949e594
      Markus Armbruster authored
      New device, has never been released, so we can still improve things
      without worrying about compatibility.
      Naming is a mess.  The code calls the device driver CirMemCharDriver,
      the public API calls it "memory", "memchardev", or "memchar", and the
      special commands are named like "memchar-FOO".  "memory" is a
      particularly unfortunate choice, because there's another character
      device driver called MemoryDriver.  Moreover, the device's distinctive
      property is that it's a ring buffer, not that's in memory.  Therefore:
      * Rename CirMemCharDriver to RingBufCharDriver, and call the thing a
        "ringbuf" in the API.
      * Rename QMP and HMP commands from memchar-FOO to ringbuf-FOO.
      * Rename device parameter from maxcapacity to size (simple words are
        good for you).
      * Clearly mark the parameter as optional in documentation.
      * Fix error reporting so that chardev-add reports to current monitor,
        not stderr.
      * Replace cirmem in C identifiers by ringbuf.
      * Rework documentation.  Document the impact of our crappy UTF-8
        handling on reading.
      * QMP examples that even work.
      I could split this up into multiple commits, but they'd change the
      same documentation lines multiple times.  Not worth it.
      Signed-off-by: default avatarMarkus Armbruster <armbru@redhat.com>
      Reviewed-by: default avatarEric Blake <eblake@redhat.com>
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
  19. 25 Jan, 2013 2 commits
  20. 17 Jan, 2013 1 commit
  21. 15 Jan, 2013 1 commit
  22. 16 Nov, 2012 1 commit
  23. 12 Nov, 2012 1 commit
  24. 24 Oct, 2012 2 commits
  25. 28 Sep, 2012 1 commit
  26. 27 Sep, 2012 1 commit
  27. 05 Sep, 2012 4 commits
  28. 08 Aug, 2012 2 commits