1. 30 3月, 2017 2 次提交
  2. 27 3月, 2017 5 次提交
  3. 25 3月, 2017 1 次提交
    • J
      qemu: Add TLS params to _qemuMonitorMigrationParams · 3d06cb96
      John Ferlan 提交于
      Add the fields to support setting tls-creds and tls-hostname during
      a migration (either source or target). Modify the query migration
      function to check for the presence and set the field for future
      consumers to determine which of 3 conditions is being met (NULL,
      present and set to "", or present and sent to something). These
      correspond to qemu commit id '4af245dc3' which added support to
      default the value to "" and allow setting (or resetting) to ""
      in order to disable. This reset option allows libvirt to properly
      use the tls-creds and tls-hostname parameters.
      
      Modify code paths that either allocate or use stack space in order
      to call qemuMigrationParamsClear or qemuMigrationParamsFree for cleanup.
      Signed-off-by: NJohn Ferlan <jferlan@redhat.com>
      3d06cb96
  4. 23 3月, 2017 1 次提交
  5. 22 3月, 2017 1 次提交
  6. 17 3月, 2017 1 次提交
  7. 16 3月, 2017 1 次提交
  8. 04 3月, 2017 3 次提交
  9. 06 1月, 2017 1 次提交
  10. 21 12月, 2016 1 次提交
  11. 06 12月, 2016 1 次提交
  12. 28 11月, 2016 1 次提交
    • J
      qemu: Add support for unavailable-features · a1adfb0f
      Jiri Denemark 提交于
      QEMU 2.8.0 adds support for unavailable-features in
      query-cpu-definitions reply. The unavailable-features array lists CPU
      features which prevent a corresponding CPU model from being usable on
      current host. It can only be used when all the unavailable features are
      disabled. Empty array means the CPU model can be used without
      modifications.
      
      We can use unavailable-features for providing CPU model usability info
      in domain capabilities XML:
      
          <domainCapabilities>
            ...
            <cpu>
              <mode name='host-passthrough' supported='yes'/>
              <mode name='host-model' supported='yes'>
                <model fallback='allow'>Skylake-Client</model>
                ...
              </mode>
              <mode name='custom' supported='yes'>
                <model usable='yes'>qemu64</model>
                <model usable='yes'>qemu32</model>
                <model usable='no'>phenom</model>
                <model usable='yes'>pentium3</model>
                <model usable='yes'>pentium2</model>
                <model usable='yes'>pentium</model>
                <model usable='yes'>n270</model>
                <model usable='yes'>kvm64</model>
                <model usable='yes'>kvm32</model>
                <model usable='yes'>coreduo</model>
                <model usable='yes'>core2duo</model>
                <model usable='no'>athlon</model>
                <model usable='yes'>Westmere</model>
                <model usable='yes'>Skylake-Client</model>
                ...
              </mode>
            </cpu>
            ...
          </domainCapabilities>
      Signed-off-by: NJiri Denemark <jdenemar@redhat.com>
      a1adfb0f
  13. 22 11月, 2016 2 次提交
  14. 09 11月, 2016 1 次提交
  15. 26 10月, 2016 1 次提交
    • J
      qemu: Add length for bps/iops throttling parameters to driver · 223438a2
      John Ferlan 提交于
      Add support for a duration/length for the bps/iops and friends.
      
      Modify the API in order to add the "blkdeviotune." specific definitions
      for the iotune throttling duration/length options
      
          total_bytes_sec_max_length
          write_bytes_sec_max_length
          read_bytes_sec_max_length
          total_iops_sec_max_length
          write_iops_sec_max_length
          read_iops_sec_max_length
      223438a2
  16. 25 10月, 2016 1 次提交
  17. 22 9月, 2016 1 次提交
  18. 14 9月, 2016 1 次提交
  19. 12 9月, 2016 1 次提交
    • J
      qemu: Don't use query-migrate on destination · 56258a38
      Jiri Denemark 提交于
      When migration fails, we need to poke QEMU monitor to check for a reason
      of the failure. We did this using query-migrate QMP command, which is
      not supposed to return any meaningful result on the destination side.
      Thus if the monitor was still functional when we detected the migration
      failure, parsing the answer from query-migrate always failed with the
      following error message:
      
          "info migration reply was missing return status"
      
      This irrelevant message was then used as the reason for the migration
      failure replacing any message we might have had.
      
      Let's use harmless query-status for poking the monitor to make sure we
      only get an error if the monitor connection is broken.
      
      https://bugzilla.redhat.com/show_bug.cgi?id=1374613Signed-off-by: NJiri Denemark <jdenemar@redhat.com>
      56258a38
  20. 25 8月, 2016 6 次提交
    • P
      qemu: monitor: Add algorithm for combining query-(hotpluggable-)-cpus data · 9bbbc88a
      Peter Krempa 提交于
      For hotplug purposes it's necessary to retrieve data using
      query-hotpluggable-cpus while the old query-cpus API report thread IDs
      and order of hotplug.
      
      This patch adds code that merges the data using a rather non-trivial
      algorithm and fills the data to the qemuMonitorCPUInfo structure for
      adding to appropriate place in the domain definition.
      9bbbc88a
    • P
      qemu: monitor: Add support for calling query-hotpluggable-cpus · 1213f0f8
      Peter Krempa 提交于
      Add support for retrieving information regarding hotpluggable cpu units
      supported by qemu. Data returned by the command carries information
      needed to figure out the granularity of hotplug, the necessary cpu type
      name and the topology information.
      
      Note that qemu doesn't specify any particular order of the entries thus
      it's necessary sort them by socket_id, core_id and thread_id to the
      order libvirt expects.
      1213f0f8
    • P
      qemu: monitor: Extract QOM path from query-cpus reply · c91be16b
      Peter Krempa 提交于
      To allow matching up the data returned by query-cpus to entries in the
      query-hotpluggable-cpus reply for CPU hotplug it's necessary to extract
      the QOM path as it's the only link between the two.
      c91be16b
    • P
      qemu: capabilities: Extract availability of new cpu hotplug for machine types · 920bbe5c
      Peter Krempa 提交于
      QEMU reports whether 'query-hotpluggable-cpus' is supported for a given
      machine type. Extract and cache the information using the capability
      cache.
      
      When copying the capabilities for a new start of qemu, mask out the
      presence of QEMU_CAPS_QUERY_HOTPLUGGABLE_CPUS if the machine type
      doesn't support hotpluggable cpus.
      920bbe5c
    • P
      qemu: monitor: Return struct from qemuMonitor(Text|Json)QueryCPUs · b3180425
      Peter Krempa 提交于
      Prepare to extract more data by returning an array of structs rather than
      just an array of thread ids. Additionally report fatal errors separately
      from qemu not being able to produce data.
      b3180425
    • P
      qemu: monitor: Return structures from qemuMonitorGetCPUInfo · 5b5f494a
      Peter Krempa 提交于
      The function will gradually add more returned data. Return a struct for
      every vCPU containing the data.
      5b5f494a
  21. 04 8月, 2016 1 次提交
  22. 25 7月, 2016 1 次提交
  23. 22 6月, 2016 3 次提交
  24. 25 5月, 2016 2 次提交