1. 10 4月, 2020 1 次提交
  2. 09 4月, 2020 7 次提交
  3. 08 4月, 2020 12 次提交
  4. 06 4月, 2020 2 次提交
    • D
      formatdomain.html.in: fix 'sockets' info in topology element · 0895a0e7
      Daniel Henrique Barboza 提交于
      In the 'topology' element it is mentioned, regarding the sockets
      value, "They refer to the total number of CPU sockets".
      
      This is not accurate. What we're doing is calculating the number
      of sockets per NUMA node, which can be checked in the current
      implementation of virHostCPUGetInfoPopulateLinux(). Calculating
      the total number of sockets would break the topology sanity
      check nodes*sockets*cores*threads=online_cpus.
      
      This documentation fix is important to avoid user confusion when
      seeing the output of 'virsh capabilities' and expecting it to be
      equal to the output of 'lscpu'. E.g in a Power 9 host this 'lscpu'
      output:
      
      Architecture:        ppc64le
      Byte Order:          Little Endian
      CPU(s):              160
      On-line CPU(s) list: 0-159
      Thread(s) per core:  4
      Core(s) per socket:  20
      Socket(s):           2
      NUMA node(s):        2
      Model:               2.2 (pvr 004e 1202)
      Model name:          POWER9, altivec supported
      
      And this XML output from virsh capabilities:
      
          <cpu>
            <arch>ppc64le</arch>
            <model>POWER9</model>
            <vendor>IBM</vendor>
            <topology sockets='1' dies='1' cores='20' threads='4'/>
            (...)
          </cpu>
      
      Both are correct, as long as we mention in the Libvirt documentation
      that 'sockets' in the topology element represents the number of sockets
      per NUMA node.
      Signed-off-by: NDaniel Henrique Barboza <danielhb413@gmail.com>
      Reviewed-by: NMichal Privoznik <mprivozn@redhat.com>
      0895a0e7
    • C
      conf: add 'multidevs' option · c3a18568
      Christian Schoenebeck 提交于
      Introduce new 'multidevs' option for filesystem.
      
        <filesystem type='mount' accessmode='mapped' multidevs='remap'>
          <source dir='/path'/>
          <target dir='mount_tag'>
        </filesystem>
      
      This option prevents misbehaviours on guest if a qemu 9pfs export
      contains multiple devices, due to the potential file ID collisions
      this otherwise may cause.
      Signed-off-by: NChristian Schoenebeck <qemu_oss@crudebyte.com>
      Signed-off-by: NJán Tomko <jtomko@redhat.com>
      Reviewed-by: NJán Tomko <jtomko@redhat.com>
      c3a18568
  5. 03 4月, 2020 3 次提交
  6. 02 4月, 2020 2 次提交
  7. 30 3月, 2020 3 次提交
  8. 28 3月, 2020 1 次提交
  9. 27 3月, 2020 1 次提交
  10. 26 3月, 2020 1 次提交
  11. 25 3月, 2020 1 次提交
  12. 24 3月, 2020 5 次提交
  13. 23 3月, 2020 1 次提交