1. 10 3月, 2015 4 次提交
  2. 09 3月, 2015 23 次提交
  3. 06 3月, 2015 13 次提交
    • M
      domain_conf: Format <pvpanic/> without address correctly · b39b1397
      Michal Privoznik 提交于
      We have something like pvpanic device. However, in some cases it does
      not have any address assigned, in which case we produce this ugly XML
      (still valid though):
      
        <devices>
          <emulator>/usr/bin/qemu</emulator>
          ...
          <panic>
          </panic>
        </devices>
      
      Lets format "<panic/>" instead.
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      b39b1397
    • D
      Refresh translations from Zanata · d196444c
      Daniel P. Berrange 提交于
      Delete .po files which contain zero translated strings. Refresh
      the .pot file and pull down latest translations from Zanata.
      
      When refreshing the libvirt.pot, it can be pushed to zanata
      and .po files resynchonized using
      
       # cd po
       # rm libvirt.pot
       # make libvirt.pot
       # zanata-cli push
       # zanata-cli pull
      
      Note there is no need for 'make update-po', as long as you do
      a zanata push, immediately followed by zanata pull, as the
      Zanata server will ensure the .po files downloaded match the
      just pushed .pot file.
      
      Note at time of writing, it is strongly recommended to only
      use the zanata Java client binary (zanata-cli), and not the
      python client binary (zanata). This is because the moderately
      large size of the libvirt pot file is causing errors when the
      python client tries to push, which have been known to result
      in the loss of all translations on the server, as well as also
      preventing uploading of .po files themselves :-(
      d196444c
    • J
      virsh: Add 'iothreadsinfo' command · f41a5b84
      John Ferlan 提交于
      Add the 'iothreadsinfo' command to display IOThread Info data. Allow for
      [--live] or [--config] options in order to display live or config data
      for an active domain.
      
      $ virsh iothreadsinfo --help
        NAME
          iothreadsinfo - view domain IOThreads
      
        SYNOPSIS
          iothreadsinfo <domain> [--config] [--live] [--current]
      
        DESCRIPTION
          Returns basic information about the domain IOThreads.
      
        OPTIONS
          [--domain] <string>  domain name, id or uuid
          --config         affect next boot
          --live           affect running domain
          --current        affect current domain
      
      An active domain may return:
      
      $ virsh iothreads $dom
       IOThread ID     CPU Affinity
      ---------------------------------------------------
        1               2
        2               3
        3               0
      
      $ echo $?
      0
      
      For domains which don't have IOThreads the following is returned:
      
      $ virsh iothreads $dom
      No IOThreads found for the domain
      
      $ echo $?
      0
      
      For domains which are not running the following is returned:
      
      $ virsh iothreads $dom --live
      error: Unable to get domain IOThreads information
      error: Requested operation is not valid: domain is not running
      
      $ echo $?
      1
      
      Editing a domains configuration and modifying the iothreadpin data for
      thread 3 from nothing provided to setting a cpuset of '0-1' and then
      displaying using --config would display:
      
      $ virsh iothreads f18iothr --config
       IOThread ID     CPU Affinity
       ----------------------------
        1               2
        2               3
        3               0-1
      
      $
      Signed-off-by: NJohn Ferlan <jferlan@redhat.com>
      f41a5b84
    • J
      qemu: Implement the qemu driver fetch for IOThreads · 82649eb7
      John Ferlan 提交于
      Depending on the flags passed, either attempt to return the active/live
      IOThread data for the domain or the config data.
      
      The active/live path will call into the Monitor in order to get the
      IOThread data and then correlate the thread_id's returned from the
      monitor to the currently running system/threads in order to ascertain
      the affinity for each iothread_id.
      
      The config path will map each of the configured IOThreads and return
      any configured iothreadspin data
      Signed-off-by: NJohn Ferlan <jferlan@redhat.com>
      82649eb7
    • J
      remote: Implement the remote plumbing for virDomainGetIOThreadsInfo · 1e5a8ddc
      John Ferlan 提交于
      Implement the remote plumbing for virDomainGetIOThreadsInfo
      Signed-off-by: NJohn Ferlan <jferlan@redhat.com>
      1e5a8ddc
    • J
      Implement public API for virDomainGetIOThreadsInfo · 11a5a095
      John Ferlan 提交于
      Add virDomainGetIOThreadInfo in order to return a list of
      virDomainIOThreadInfoPtr structures which list the IOThread ID
      and the CPU Affinity map for each IOThread for the domain.
      
      For an active domain, the live data will be returned, while for
      an inactive domain, the config data will be returned.
      
      The API supports either the --live or --config flag, but not both.
      
      Also added virDomainIOThreadsInfoFree in order to free the cpumap
      and the IOThreadInfo structure.
      Signed-off-by: NJohn Ferlan <jferlan@redhat.com>
      11a5a095
    • P
      memtune: change the way how we store unlimited value · cf521fc8
      Pavel Hrdina 提交于
      There was a mess in the way how we store unlimited value for memory
      limits and how we handled values provided by user.  Internally there
      were two possible ways how to store unlimited value: as 0 value or as
      VIR_DOMAIN_MEMORY_PARAM_UNLIMITED.  Because we chose to store memory
      limits as unsigned long long, we cannot use -1 to represent unlimited.
      It's much easier for us to say that everything greater than
      VIR_DOMAIN_MEMORY_PARAM_UNLIMITED means unlimited and leave 0 as valid
      value despite that it makes no sense to set limit to 0.
      
      Remove unnecessary function virCompareLimitUlong.  The update of test
      is to prevent the 0 to be miss-used as unlimited in future.
      
      Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1146539Signed-off-by: NPavel Hrdina <phrdina@redhat.com>
      cf521fc8
    • P
      virutil: introduce helper functions for memory limits · a73395ae
      Pavel Hrdina 提交于
      The first one is to truncate the memory limit to
      VIR_DOMAIN_MEMORY_PARAM_UNLIMITED if the value is greater and the second
      one is to decide whether the memory limit is set or not, unlimited means
      that it's not set.
      Signed-off-by: NPavel Hrdina <phrdina@redhat.com>
      a73395ae
    • P
      virsh: fix memtune to also accept 0 as valid value · c2020b08
      Pavel Hrdina 提交于
      Fix vshMemtuneGetSize to return correct value.  We can then decide
      according that return code whether a parameter is present and valid or
      not.  This will allow as to accept 0 as a valid value.
      Signed-off-by: NPavel Hrdina <phrdina@redhat.com>
      c2020b08
    • S
      qemu: Pass file descriptor when using TPM passthrough · 9954a8bf
      Stefan Berger 提交于
      Pass the TPM file descriptor to QEMU via command line.
      Instead of passing /dev/tpm0 we now pass /dev/fdset/10 and the additional
      parameters -add-fd set=10,fd=20.
      
      This addresses the use case when QEMU is started with non-root privileges
      and QEMU cannot open /dev/tpm0 for example.
      Signed-off-by: NStefan Berger <stefanb@linux.vnet.ibm.com>
      9954a8bf
    • S
      qemu: Move TPM command line build code into own function · 42bee147
      Stefan Berger 提交于
      Move the TPM command line build code into its own function.
      Signed-off-by: NStefan Berger <stefanb@linux.vnet.ibm.com>
      42bee147
    • S
      utils: Implement virCommandPassFDGetFDIndex · a06e9ce1
      Stefan Berger 提交于
      Implement virCommandPassFDGetFDIndex to determine the index a given
      file descriptor will have when passed to the child process.
      Signed-off-by: NStefan Berger <stefanb@linux.vnet.ibm.com>
      a06e9ce1
    • J
      libxl: remove unneeded cleanup_unlock label · 3b7f5895
      Jim Fehlig 提交于
      In the old days of a global driver lock, it was necessary to unlock
      the driver after a domain restore operation.  When the global lock
      was removed from the driver, some remnants were left behind in
      libxlDomainRestoreFlags.  Remove this unneeded (and incorrect) code.
      Signed-off-by: NJim Fehlig <jfehlig@suse.com>
      3b7f5895