1. 12 3月, 2018 1 次提交
    • P
      q35: change default NIC to e1000e · 4b9c264b
      Paolo Bonzini 提交于
      The e1000 NIC is getting old and is not a very good default for a
      PCIe machine type.  Change it to e1000e, which should be supported
      by a good number of guests.
      
      In particular, drivers for 82574 were added first to Linux 2.6.27 (2008)
      and Windows 2008 R2.  This does mean that Windows 2008 will not work
      anymore with Q35 machine types and a default "-net nic -net xxx" network
      configuration; it did work before because it does have an AHCI driver.
      However, Windows 2008 has been declared out of main stream support
      in 2015.  It will get out of extended support in 2020.  Windows 2008
      R2 has the same end of support dates and, since the two are basically
      Vista vs. Windows 7, R2 probably is more popular.
      Reviewed-by: NJason Wang <jasowang@redhat.com>
      Reviewed-by: NThomas Huth <thuth@redhat.com>
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      4b9c264b
  2. 06 3月, 2018 1 次提交
  3. 09 2月, 2018 1 次提交
  4. 19 1月, 2018 2 次提交
  5. 18 1月, 2018 1 次提交
  6. 16 11月, 2017 1 次提交
    • D
      NUMA: Enable adding NUMA node implicitly · 7b8be49d
      Dou Liyang 提交于
      Linux and Windows need ACPI SRAT table to make memory hotplug work properly,
      however currently QEMU doesn't create SRAT table if numa options aren't present
      on CLI.
      
      Which breaks both linux and windows guests in certain conditions:
       * Windows: won't enable memory hotplug without SRAT table at all
       * Linux: if QEMU is started with initial memory all below 4Gb and no SRAT table
         present, guest kernel will use nommu DMA ops, which breaks 32bit hw drivers
         when memory is hotplugged and guest tries to use it with that drivers.
      
      Fix above issues by automatically creating a numa node when QEMU is started with
      memory hotplug enabled but without '-numa' options on CLI.
      (PS: auto-create numa node only for new machine types so not to break migration).
      
      Which would provide SRAT table to guests without explicit -numa options on CLI
      and would allow:
       * Windows: to enable memory hotplug
       * Linux: switch to SWIOTLB DMA ops, to bounce DMA transfers to 32bit allocated
         buffers that legacy drivers/hw can handle.
      
      [Rewritten by Igor]
      Reported-by: NThadeu Lima de Souza Cascardo <cascardo@canonical.com>
      Suggested-by: NIgor Mammedov <imammedo@redhat.com>
      Signed-off-by: NDou Liyang <douly.fnst@cn.fujitsu.com>
      Cc: Paolo Bonzini <pbonzini@redhat.com>
      Cc: Richard Henderson <rth@twiddle.net>
      Cc: Eduardo Habkost <ehabkost@redhat.com>
      Cc: "Michael S. Tsirkin" <mst@redhat.com>
      Cc: Marcel Apfelbaum <marcel@redhat.com>
      Cc: Igor Mammedov <imammedo@redhat.com>
      Cc: David Hildenbrand <david@redhat.com>
      Cc: Thomas Huth <thuth@redhat.com>
      Cc: Alistair Francis <alistair23@gmail.com>
      Cc: Takao Indoh <indou.takao@jp.fujitsu.com>
      Cc: Izumi Taku <izumi.taku@jp.fujitsu.com>
      Reviewed-by: NIgor Mammedov <imammedo@redhat.com>
      Reviewed-by: NMichael S. Tsirkin <mst@redhat.com>
      Signed-off-by: NMichael S. Tsirkin <mst@redhat.com>
      7b8be49d
  7. 15 10月, 2017 1 次提交
  8. 19 9月, 2017 1 次提交
  9. 08 9月, 2017 1 次提交
  10. 18 7月, 2017 1 次提交
  11. 13 7月, 2017 1 次提交
    • A
      Convert error_report() to warn_report() · 3dc6f869
      Alistair Francis 提交于
      Convert all uses of error_report("warning:"... to use warn_report()
      instead. This helps standardise on a single method of printing warnings
      to the user.
      
      All of the warnings were changed using these two commands:
          find ./* -type f -exec sed -i \
            's|error_report(".*warning[,:] |warn_report("|Ig' {} +
      
      Indentation fixed up manually afterwards.
      
      The test-qdev-global-props test case was manually updated to ensure that
      this patch passes make check (as the test cases are case sensitive).
      Signed-off-by: NAlistair Francis <alistair.francis@xilinx.com>
      Suggested-by: NThomas Huth <thuth@redhat.com>
      Cc: Jeff Cody <jcody@redhat.com>
      Cc: Kevin Wolf <kwolf@redhat.com>
      Cc: Max Reitz <mreitz@redhat.com>
      Cc: Ronnie Sahlberg <ronniesahlberg@gmail.com>
      Cc: Paolo Bonzini <pbonzini@redhat.com>
      Cc: Peter Lieven <pl@kamp.de>
      Cc: Josh Durgin <jdurgin@redhat.com>
      Cc: "Richard W.M. Jones" <rjones@redhat.com>
      Cc: Markus Armbruster <armbru@redhat.com>
      Cc: Peter Crosthwaite <crosthwaite.peter@gmail.com>
      Cc: Richard Henderson <rth@twiddle.net>
      Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
      Cc: Greg Kurz <groug@kaod.org>
      Cc: Rob Herring <robh@kernel.org>
      Cc: Peter Maydell <peter.maydell@linaro.org>
      Cc: Peter Chubb <peter.chubb@nicta.com.au>
      Cc: Eduardo Habkost <ehabkost@redhat.com>
      Cc: Marcel Apfelbaum <marcel@redhat.com>
      Cc: "Michael S. Tsirkin" <mst@redhat.com>
      Cc: Igor Mammedov <imammedo@redhat.com>
      Cc: David Gibson <david@gibson.dropbear.id.au>
      Cc: Alexander Graf <agraf@suse.de>
      Cc: Gerd Hoffmann <kraxel@redhat.com>
      Cc: Jason Wang <jasowang@redhat.com>
      Cc: Marcelo Tosatti <mtosatti@redhat.com>
      Cc: Christian Borntraeger <borntraeger@de.ibm.com>
      Cc: Cornelia Huck <cohuck@redhat.com>
      Cc: Stefan Hajnoczi <stefanha@redhat.com>
      Acked-by: NDavid Gibson <david@gibson.dropbear.id.au>
      Acked-by: NGreg Kurz <groug@kaod.org>
      Acked-by: NCornelia Huck <cohuck@redhat.com>
      Reviewed-by: NStefan Hajnoczi <stefanha@redhat.com>
      Reviewed by: Peter Chubb <peter.chubb@data61.csiro.au>
      Acked-by: NMax Reitz <mreitz@redhat.com>
      Acked-by: NMarcel Apfelbaum <marcel@redhat.com>
      Message-Id: <e1cfa2cd47087c248dd24caca9c33d9af0c499b0.1499866456.git.alistair.francis@xilinx.com>
      Reviewed-by: NMarkus Armbruster <armbru@redhat.com>
      Signed-off-by: NMarkus Armbruster <armbru@redhat.com>
      3dc6f869
  12. 04 7月, 2017 1 次提交
    • T
      Move CONFIG_KVM related definitions to kvm_i386.h · 2099935d
      Thomas Huth 提交于
      pc.h and sysemu/kvm.h are also included from common code (where
      CONFIG_KVM is not available), so the #defines that depend on CONFIG_KVM
      should not be declared here to avoid that anybody is using them in a
      wrong way. Since we're also going to poison CONFIG_KVM for common code,
      let's move them to kvm_i386.h instead. Most of the dummy definitions
      from sysemu/kvm.h are also unused since the code that uses them is
      only compiled for CONFIG_KVM (e.g. target/i386/kvm.c), so the unused
      defines are also simply dropped here instead of being moved.
      Signed-off-by: NThomas Huth <thuth@redhat.com>
      Message-Id: <1498454578-18709-3-git-send-email-thuth@redhat.com>
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      2099935d
  13. 19 5月, 2017 1 次提交
  14. 12 5月, 2017 1 次提交
    • L
      numa: equally distribute memory on nodes · 3bfe5716
      Laurent Vivier 提交于
      When there are more nodes than available memory to put the minimum
      allowed memory by node, all the memory is put on the last node.
      
      This is because we put (ram_size / nb_numa_nodes) &
      ~((1 << mc->numa_mem_align_shift) - 1); on each node, and in this
      case the value is 0. This is particularly true with pseries,
      as the memory must be aligned to 256MB.
      
      To avoid this problem, this patch uses an error diffusion algorithm [1]
      to distribute equally the memory on nodes.
      
      We introduce numa_auto_assign_ram() function in MachineClass
      to keep compatibility between machine type versions.
      The legacy function is used with pseries-2.9, pc-q35-2.9 and
      pc-i440fx-2.9 (and previous), the new one with all others.
      
      Example:
      
      qemu-system-ppc64 -S -nographic  -nodefaults -monitor stdio -m 1G -smp 8 \
                        -numa node -numa node -numa node \
                        -numa node -numa node -numa node
      
      Before:
      
      (qemu) info numa
      6 nodes
      node 0 cpus: 0 6
      node 0 size: 0 MB
      node 1 cpus: 1 7
      node 1 size: 0 MB
      node 2 cpus: 2
      node 2 size: 0 MB
      node 3 cpus: 3
      node 3 size: 0 MB
      node 4 cpus: 4
      node 4 size: 0 MB
      node 5 cpus: 5
      node 5 size: 1024 MB
      
      After:
      (qemu) info numa
      6 nodes
      node 0 cpus: 0 6
      node 0 size: 0 MB
      node 1 cpus: 1 7
      node 1 size: 256 MB
      node 2 cpus: 2
      node 2 size: 0 MB
      node 3 cpus: 3
      node 3 size: 256 MB
      node 4 cpus: 4
      node 4 size: 256 MB
      node 5 cpus: 5
      node 5 size: 256 MB
      
      [1] https://en.wikipedia.org/wiki/Error_diffusionSigned-off-by: NLaurent Vivier <lvivier@redhat.com>
      Message-Id: <20170502162955.1610-2-lvivier@redhat.com>
      Reviewed-by: NEduardo Habkost <ehabkost@redhat.com>
      [ehabkost: s/ram_size/size/ at numa_default_auto_assign_ram()]
      Signed-off-by: NEduardo Habkost <ehabkost@redhat.com>
      3bfe5716
  15. 11 5月, 2017 2 次提交
  16. 19 1月, 2017 1 次提交
  17. 22 12月, 2016 3 次提交
  18. 25 10月, 2016 1 次提交
  19. 10 9月, 2016 1 次提交
  20. 08 9月, 2016 2 次提交
  21. 04 7月, 2016 3 次提交
  22. 29 6月, 2016 4 次提交
  23. 24 6月, 2016 1 次提交
  24. 15 6月, 2016 1 次提交
  25. 13 6月, 2016 1 次提交
  26. 08 4月, 2016 1 次提交
    • G
      Sort the fw_cfg file list · bab47d9a
      Gerd Hoffmann 提交于
      Entries are inserted in filename order instead of being
      appended to the end in case sorting is enabled.
      
      This will avoid any future issues of moving the file creation
      around, it doesn't matter what order they are created now,
      the will always be in filename order.
      Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
      
      Added machine type handling for compatibility.  This was
      a fairly complex change, this will preserve the order of fw_cfg
      for older versions no matter what order the firmware files
      actually come in.  A list is kept of the correct legacy order
      and the entries will be inserted based upon their order in
      the list.  Except that some entries are ordered (in a specific
      area of the list) based upon what order they appear on the
      command line.  Special handling is added for those entries.
      Signed-off-by: NCorey Minyard <cminyard@mvista.com>
      Reviewed-by: NMichael S. Tsirkin <mst@redhat.com>
      Signed-off-by: NMichael S. Tsirkin <mst@redhat.com>
      bab47d9a
  27. 16 3月, 2016 1 次提交
  28. 11 3月, 2016 1 次提交
  29. 25 2月, 2016 2 次提交