1. 27 Nov, 2017 1 commit
  2. 20 Nov, 2017 1 commit
    • Jason Wang's avatar
      Revert "Add new PCI ID for i82559a" · 2ec40552
      Jason Wang authored
      This reverts commit 5e89dc01 since:
      - we should use ID in the spec instead the one used by OEM
      - in the future, we should allow changing id through either property
        or EEPROM file.
      Cc: Stefan Weil <sw@weilnetz.de>
      Cc: Michael Nawrocki <michael.nawrocki@gtri.gatech.edu>
      Cc: Peter Maydell <peter.maydell@linaro.org>
      Cc: Michael S. Tsirkin <mst@redhat.com>
      Reviewed-by: 's avatarStefan Weil <sw@weilnetz.de>
      Signed-off-by: 's avatarJason Wang <jasowang@redhat.com>
  3. 13 Nov, 2017 1 commit
  4. 13 Oct, 2017 1 commit
  5. 10 Oct, 2017 1 commit
  6. 26 Sep, 2017 1 commit
  7. 19 Sep, 2017 1 commit
  8. 15 Sep, 2017 4 commits
  9. 01 Aug, 2017 1 commit
  10. 17 Jul, 2017 5 commits
  11. 11 Jul, 2017 1 commit
    • Eric Blake's avatar
      tests: Avoid non-portable 'echo -ARG' · b43671f8
      Eric Blake authored
      POSIX says that backslashes in the arguments to 'echo', as well as
      any use of 'echo -n' and 'echo -e', are non-portable; it recommends
      people should favor 'printf' instead.  This is definitely true where
      we do not control which shell is running (such as in makefile snippets
      or in documentation examples).  But even for scripts where we
      require bash (and therefore, where echo does what we want by default),
      it is still possible to use 'shopt -s xpg_echo' to change bash's
      behavior of echo.  And setting a good example never hurts when we are
      not sure if a snippet will be copied from a bash-only script to a
      general shell script (although I don't change the use of non-portable
      \e for ESC when we know the running shell is bash).
      Replace 'echo -n "..."' with 'printf %s "..."', and 'echo -e "..."'
      with 'printf %b "...\n"', with the optimization that the %s/%b
      argument can be omitted if the string being printed is a strict
      literal with no '%', '$', or '`' (we could technically also make
      this optimization when there are $ or `` substitutions but where
      we can prove their results will not be problematic, but proving
      that such substitutions are safe makes the patch less trivial
      compared to just being consistent).
      In the qemu-iotests check script, fix unusual shell quoting
      that would result in word-splitting if 'date' outputs a space.
      In test 051, take an opportunity to shorten the line.
      In test 068, get rid of a pointless second invocation of bash.
      CC: qemu-trivial@nongnu.org
      Signed-off-by: 's avatarEric Blake <eblake@redhat.com>
      Message-id: 20170703180950.9895-1-eblake@redhat.com
      Signed-off-by: 's avatarMax Reitz <mreitz@redhat.com>
  12. 10 Jul, 2017 2 commits
  13. 29 Jun, 2017 1 commit
    • Tobias Schramm's avatar
      9pfs: local: Add support for custom fmode/dmode in 9ps mapped security modes · b96feb2c
      Tobias Schramm authored
      In mapped security modes, files are created with very restrictive
      permissions (600 for files and 700 for directories). This makes
      file sharing between virtual machines and users on the host rather
      complicated. Imagine eg. a group of users that need to access data
      produced by processes on a virtual machine. Giving those users access
      to the data will be difficult since the group access mode is always 0.
      This patch makes the default mode for both files and directories
      configurable. Existing setups that don't know about the new parameters
      keep using the current secure behavior.
      Signed-off-by: 's avatarTobias Schramm <tobleminer@gmail.com>
      Signed-off-by: 's avatarGreg Kurz <groug@kaod.org>
  14. 26 Jun, 2017 2 commits
  15. 04 Jun, 2017 2 commits
    • Suraj Jitindar Singh's avatar
      help: Add newline to end of thread option help text · f603164a
      Suraj Jitindar Singh authored
      The help text for the thread sub option of the accel option is missing
      a newline at the end. This is annoying as it makes it hard to see the
      help text for the next option.
      Add the new line so that the following option help text (-smp) is
      displayed on a new line rather on the same line and directly after
      the thread help.
      Before patch:
      -accel [accel=]accelerator[,thread=single|multi]
                      select accelerator (kvm, xen, hax or tcg; use 'help' for a list)
                      thread=single|multi (enable multi-threaded TCG)-smp [cpus=]n[,maxcpus=cpus][,cores=cores][,threads=threads][,sockets=sockets]
                      set the number of CPUs to 'n' [default=1]
                      maxcpus= maximum number of total cpus, including
                      offline CPUs for hotplug, etc
                      cores= number of CPU cores on one socket
                      threads= number of threads on one CPU core
                      sockets= number of discrete sockets in the system
      After patch:
      -accel [accel=]accelerator[,thread=single|multi]
                      select accelerator (kvm, xen, hax or tcg; use 'help' for a list)
                      thread=single|multi (enable multi-threaded TCG)
      -smp [cpus=]n[,maxcpus=cpus][,cores=cores][,threads=threads][,sockets=sockets]
                      set the number of CPUs to 'n' [default=1]
                      maxcpus= maximum number of total cpus, including
                      offline CPUs for hotplug, etc
                      cores= number of CPU cores on one socket
                      threads= number of threads on one CPU core
                      sockets= number of discrete sockets in the system
      Signed-off-by: 's avatarSuraj Jitindar Singh <sjitindarsingh@gmail.com>
      Signed-off-by: 's avatarMichael Tokarev <mjt@tls.msk.ru>
    • Markus Armbruster's avatar
  16. 29 May, 2017 1 commit
  17. 23 May, 2017 1 commit
  18. 19 May, 2017 1 commit
  19. 11 May, 2017 2 commits
    • Igor Mammedov's avatar
      numa: add '-numa cpu,...' option for property based node mapping · 419fcdec
      Igor Mammedov authored
      legacy cpu to node mapping is using cpu index values to map
      VCPU to node with help of '-numa node,nodeid=node,cpus=x[-y]'
      option. However cpu index is internal concept and QEMU users
      have to guess /reimplement qemu's logic/ to map it to
      a concrete cpu socket/core/thread to make sane CPUs
      placement across numa nodes.
      This patch allows to map cpu objects to numa nodes using
      the same properties as used for cpus with -device/device_add
      At present valid properties/values to address CPUs could be
      fetched using hotpluggable-cpus monitor/qmp command, it will
      require user to start qemu twice when creating domain to fetch
      possible CPUs for a machine type/-smp layout first and
      then the second time with numa explicit mapping for actual
      usage. The first step results could be saved and reused to
      set/change mapping later as far as machine type/-smp stays
      the same.
      Proposed impl. supports exact and wildcard matching to
      simplify CLI and allow to set mapping for a specific cpu
      or group of cpu objects specified by matched properties.
      For example:
         # exact mapping x86
         -numa cpu,node-id=x,socket-id=y,core-id=z,thread-id=n
         # exact mapping SPAPR
         -numa cpu,node-id=x,core-id=y
         # wildcard mapping, all cpu objects that match socket-id=y
         # are mapped to node-id=x
         -numa cpu,node-id=x,socket-id=y
      Signed-off-by: 's avatarIgor Mammedov <imammedo@redhat.com>
      Message-Id: <1494415802-227633-18-git-send-email-imammedo@redhat.com>
      Reviewed-by: 's avatarDavid Gibson <david@gibson.dropbear.id.au>
      Signed-off-by: 's avatarEduardo Habkost <ehabkost@redhat.com>
    • He Chen's avatar
      numa: Allow setting NUMA distance for different NUMA nodes · 0f203430
      He Chen authored
      This patch is going to add SLIT table support in QEMU, and provides
      additional option `dist` for command `-numa` to allow user set vNUMA
      distance by QEMU command.
      With this patch, when a user wants to create a guest that contains
      several vNUMA nodes and also wants to set distance among those nodes,
      the QEMU command would like:
      -numa node,nodeid=0,cpus=0 \
      -numa node,nodeid=1,cpus=1 \
      -numa node,nodeid=2,cpus=2 \
      -numa node,nodeid=3,cpus=3 \
      -numa dist,src=0,dst=1,val=21 \
      -numa dist,src=0,dst=2,val=31 \
      -numa dist,src=0,dst=3,val=41 \
      -numa dist,src=1,dst=2,val=21 \
      -numa dist,src=1,dst=3,val=31 \
      -numa dist,src=2,dst=3,val=21 \
      Signed-off-by: 's avatarHe Chen <he.chen@linux.intel.com>
      Message-Id: <1493260558-20728-1-git-send-email-he.chen@linux.intel.com>
      Reviewed-by: 's avatarIgor Mammedov <imammedo@redhat.com>
      Reviewed-by: 's avatarAndrew Jones <drjones@redhat.com>
      Signed-off-by: 's avatarEduardo Habkost <ehabkost@redhat.com>
  20. 10 May, 2017 1 commit
    • Chris Webb's avatar
      virtfs: allow a device id to be specified in the -virtfs option · 3baa0a6a
      Chris Webb authored
      When using a virtfs root filesystem, the mount_tag needs to be set to
      /dev/root. This can be done long-hand as
        -fsdev local,id=root,path=/path/to/rootfs,...
        -device virtio-9p-pci,fsdev=root,mount_tag=/dev/root
      but the -virtfs shortcut cannot be used as it hard-codes the device identifier
      to match the mount_tag, and device identifiers may not contain '/':
        $ qemu-system-x86_64 -virtfs local,path=/foo,mount_tag=/dev/root,security_model=passthrough
        qemu-system-x86_64: -virtfs local,path=/foo,mount_tag=/dev/root,security_model=passthrough: duplicate fsdev id: /dev/root
      To support this case using -virtfs, we allow the device identifier to be
      specified explicitly when the mount_tag is not suitable:
        -virtfs local,id=root,path=/path/to/rootfs,mount_tag=/dev/root,...
      Signed-off-by: 's avatarChris Webb <chris@arachsys.com>
      Signed-off-by: 's avatarMichael Tokarev <mjt@tls.msk.ru>
  21. 07 May, 2017 1 commit
  22. 05 May, 2017 2 commits
  23. 27 Apr, 2017 1 commit
  24. 26 Apr, 2017 2 commits
  25. 21 Apr, 2017 2 commits
  26. 14 Mar, 2017 1 commit