1. 12 10月, 2016 11 次提交
  2. 11 10月, 2016 1 次提交
  3. 07 10月, 2016 1 次提交
    • D
      qemu: fix command line building for iommu devices · 5dee6686
      Daniel P. Berrange 提交于
      The intel-iommu device has existed since QEMU 2.2.0, but
      it was only possible to create it with -device since
      QEMU 2.7.0, thanks to:
      
        commit 621d983a1f9051f4cfc3f402569b46b77d8449fc
        Author: Marcel Apfelbaum <marcel@redhat.com>
        Date:   Mon Jun 27 18:38:34 2016 +0300
      
          hw/iommu: enable iommu with -device
      
          Use the standard '-device intel-iommu' to create the IOMMU device.
          The legacy '-machine,iommu=on' can still be used.
      
      The libvirt capability check & command line formatting code
      is thus broken for all QEMU versions 2.2.0 -> 2.6.0 inclusive.
      
      This fixes it to use iommu=on instead.
      Signed-off-by: NDaniel P. Berrange <berrange@redhat.com>
      5dee6686
  4. 06 10月, 2016 4 次提交
  5. 05 10月, 2016 7 次提交
  6. 30 9月, 2016 5 次提交
  7. 29 9月, 2016 1 次提交
    • M
      qemu: Only use memory-backend-file with NUMA if needed · ff3112f3
      Martin Kletzander 提交于
      If this reminds you of a commit message from around a year ago, it's
      41c2aa72 and yes, we're dealing with
      "the same thing" again.  Or f309db1f and
      it's similar.
      
      There is a logic in place that if there is no real need for
      memory-backend-file, qemuBuildMemoryBackendStr() returns 0.  However
      that wasn't the case with hugepage backing.  The reason for that was
      that we abused the 'pagesize' variable for storing that information, but
      we should rather have a separate one that specifies whether we really
      need the new object for hugepage backing.  And that variable should be
      set only if this particular NUMA cell needs special treatment WRT
      hugepages.
      
      Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1372153Signed-off-by: NMartin Kletzander <mkletzan@redhat.com>
      ff3112f3
  8. 28 9月, 2016 2 次提交
    • J
      conf: add xen type for channels · 031abbc5
      Joao Martins 提交于
      So far only guestfwd and virtio were supported. Add an additional
      for Xen as libxl channels create a Xen console visible to the guest.
      Signed-off-by: NJoao Martins <joao.m.martins@oracle.com>
      Signed-off-by: NJim Fehlig <jfehlig@suse.com>
      031abbc5
    • J
      qemu: Fix crash in qemucapsprobe · c2c43912
      Jiri Denemark 提交于
      The qemucapsprobe helper calls virQEMUCapsNewForBinaryInternal with
      caps == NULL, causing the following crash:
      
          Program received signal SIGSEGV, Segmentation fault.
          #0  0x00007ffff788775f in virQEMUCapsInitHostCPUModel
              (qemuCaps=qemuCaps@entry=0x649680, host=host@entry=0x10) at
              src/qemu/qemu_capabilities.c:2969
          #1  0x00007ffff7889dbf in virQEMUCapsNewForBinaryInternal
              (caps=caps@entry=0x0, binary=<optimized out>,
              libDir=libDir@entry=0x4033f6 "/tmp", cacheDir=cacheDir@entry=0x0,
              runUid=runUid@entry=4294967295, runGid=runGid@entry=4294967295,
              qmpOnly=true) at src/qemu/qemu_capabilities.c:4039
          #2  0x0000000000401702 in main (argc=2, argv=0x7fffffffd968) at
              tests/qemucapsprobe.c:73
      
      Caused by v2.2.0-182-g68c70118.
      Signed-off-by: NJiri Denemark <jdenemar@redhat.com>
      c2c43912
  9. 27 9月, 2016 2 次提交
    • M
      qemuDomainUpdateDeviceConfig: Allow full disk update · 3193a594
      Michal Privoznik 提交于
      https://bugzilla.redhat.com/show_bug.cgi?id=1368417
      
      So far, when it comes to 'virsh update-device --config' of disks
      we are limiting ourselves for just the disk source update and
      just for CDROMs and floppies. This makes no sense. Especially if
      you look around and see that we already allow full update to
      graphics and net devices. So let's just take whatever XML user
      wants to have there and replace our internal definition with it.
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      3193a594
    • D
      qemu: make qemuGetCompressionProgram return int not an enum · 1d4634db
      Daniel P. Berrange 提交于
      enum types are unsigned and the qemuGetCompressionProgram
      function can return -1 on error. It is therefore inappropriate
      to return an enum type. This fixes a build error where the
      internal 'ret' variable was used in a comparison with -1
      
      ../../src/qemu/qemu_driver.c: In function 'qemuGetCompressionProgram':
      ../../src/qemu/qemu_driver.c:3280:5: error: comparison of unsigned expression < 0 is always false [-Werror=type-limits]
      ../../src/qemu/qemu_driver.c:3289:5: error: comparison of unsigned expression < 0 is always false [-Werror=type-limits]
      cc1: all warnings being treated as errors
      Signed-off-by: NDaniel P. Berrange <berrange@redhat.com>
      1d4634db
  10. 26 9月, 2016 6 次提交