1. 21 9月, 2018 1 次提交
    • A
      qemu: Don't duplicate binary name in capabilities · b37b41f8
      Andrea Bolognani 提交于
      virCapabilitiesAddGuestDomain() takes an optional binary
      name: this is intended for cases where a certain domain
      type can't use the default one registered for the guest
      architecture, but has to use a special binary instead.
      
      The current code, however, will pass 'binary' again when
      'kvmbin' is not defined, which is unnecessary as 'binary'
      has been registered as default earlier, and will result
      in capabilities output such as
      
        <emulator>/usr/bin/qemu-system-x86_64</emulator>
        <domain type='qemu'/>
        <domain type='kvm'>
          <emulator>/usr/bin/qemu-system-x86_64</emulator>
        </domain>
      
      with the second <emulator> element providing no additional
      information.
      
      Change it so that, when 'kvmbin' is not defined, NULL is
      passed and so the default emulator will be used instead.
      Signed-off-by: NAndrea Bolognani <abologna@redhat.com>
      b37b41f8
  2. 17 9月, 2018 2 次提交
  3. 05 6月, 2018 1 次提交
  4. 16 5月, 2016 1 次提交
  5. 24 3月, 2015 1 次提交
  6. 26 3月, 2014 1 次提交
    • F
      qemu: add unit tests for the capabilities xml · 231b63e3
      Francesco Romani 提交于
      The test is loosely inspired from qemucapabilitiestest
      and qemuxml2xmltest.
      
      Added a new test instead of extending an existing one because
      the feature being tested don't really fits nicely in any
      existing place.
      231b63e3