1. 10 7月, 2015 1 次提交
  2. 09 7月, 2015 1 次提交
  3. 03 7月, 2015 2 次提交
  4. 02 7月, 2015 1 次提交
  5. 30 6月, 2015 1 次提交
    • J
      mpath: Don't allow more than one mpath pool at a time · a77056bd
      John Ferlan 提交于
      https://bugzilla.redhat.com/show_bug.cgi?id=1232606
      
      Since an mpath pool contains all the Multipath devices on a host, allowing
      more than one defined on a host at a time should be disallowed under the
      policy of disallowing duplicate source pools for the host.
      
      Adjust to docs to clarify the Multipath target path value usage for both
      the storage driver (only 1 pool per host) and formatstorage references
      (ignore the target element in favor of the default target mapping of
      /dev/mapper).
      a77056bd
  6. 28 6月, 2015 2 次提交
  7. 27 6月, 2015 3 次提交
    • J
      docs: Clarification for when allowed to use 'lun' for "volume" · 91b96438
      John Ferlan 提交于
      While re-reading what I wrote for commit id '785a8940', I realized
      I needed to clarify that being able to present as a 'lun', the mode
      property for the pool source element needed to be "host" (or empty)
      and not "direct".
      
      It was described correctly later in the mode host description, but
      this just ensures it's not missed here as well.
      Signed-off-by: NJohn Ferlan <jferlan@redhat.com>
      91b96438
    • L
      docs: document when pcie-root/dmi-to-pci-bridge support was added · 10e207bb
      Laine Stump 提交于
      Also move the mention of version numbers for the various PCI
      controller models up to the end of the sentence where they are first
      given, to avoid confusion.
      10e207bb
    • L
      qemu: always permit PCI devices to be manually assigned to a PCIe bus · 1e15be1b
      Laine Stump 提交于
      When support for the pcie-root and dmi-to-pci-bridge buses on a Q35
      machinetype was added, I was concerned that even though qemu at the
      time allowed plugging a PCI device into a PCIe port, that it might not
      be supported in the future. To prevent painful backtracking in the
      possible future where this happened, I disallowed such connections
      except in a few specific cases requested by qemu developers (indicated
      in the code with the flag VIR_PCI_CONNECT_TYPE_EITHER_IF_CONFIG).
      
      Now that a couple years have passed, there is a clear message from
      qemu that there is no danger in allowing PCI devices to be plugged
      into PCIe ports. This patch eliminates
      VIR_PCI_CONNECT_TYPE_EITHER_IF_CONFIG and changes the code to always
      allow PCI->PCIe or PCIe->PCI connection *when the PCI address is
      specified in the config. (For newly added devices that haven't yet
      been given a PCI address, the auto-placement still prefers using the
      correct type of bus).
      1e15be1b
  8. 26 6月, 2015 1 次提交
  9. 24 6月, 2015 3 次提交
  10. 23 6月, 2015 4 次提交
    • M
      docs: Properly mark acl.html dependencies · 1310b135
      Michal Privoznik 提交于
      The acl.html file includes aclperms.htmlinc which is generated.
      However, acl.html is generated too from acl.html.tmp. And in fact,
      this is the place where the aclperms file is needed. Fix the
      dependency in Makefile.
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      1310b135
    • J
      docs: Adjust Disk storage rng · f1538322
      John Ferlan 提交于
      Currently the grammar uses "none" for a "valid" Disk Storage Pool
      format type; however, virStoragePoolFormatDisk uses "unknown" so
      virt-xml-validate will fail to validate when "unknown" is found
      f1538322
    • E
      docs: Correct typos in scsi hostdev and address elements · d10a5f58
      Eric Farman 提交于
      The type='scsi' parameter of an address element is ignored
      if placed within a hostdev section, and rejected by the XML
      schema used by virt-xml-validate. Remove it from the doc,
      and correct a typo in the remaining address arguments.
      Signed-off-by: NEric Farman <farman@linux.vnet.ibm.com>
      Reviewed-by: NMatthew Rosato <mjrosato@linux.vnet.ibm.com>
      Reviewed-by: NStefan Zimmermann <stzi@linux.vnet.ibm.com>
      Reviewed-by: NBoris Fiuczynski <fiuczy@linux.vnet.ibm.com>
      d10a5f58
    • E
      docs: Fix XML schema handling of LUN address in hostdev tag · c733e973
      Eric Farman 提交于
      Defining a domain with a SCSI disk attached via a hostdev
      tag and a source address unit value longer than two digits
      causes an error when editing the domain with virsh edit,
      even if no changes are made to the domain definition.
      The error suggests invalid XML, somewhere:
      
        # virsh edit lmb_guest
        error: XML document failed to validate against schema:
        Unable to validate doc against /usr/local/share/libvirt/schemas/domain.rng
        Extra element devices in interleave
        Element domain failed to validate content
      
      The virt-xml-validate tool fails with a similar error:
      
        # virt-xml-validate lmb_guest.xml
        Relax-NG validity error : Extra element devices in interleave
        lmb_guest.xml:17: element devices: Relax-NG validity error :
        Element domain failed to validate content
        lmb_guest.xml fails to validate
      
      The hostdev tag requires a source address to be specified,
      which includes bus, target, and unit address attributes.
      According to the SCSI Architecture Model spec (section
      4.9 of SAM-2), a LUN address is 64 bits and thus could be
      up to 20 decimal digits long.  Unfortunately, the XML
      schema limits this string to just two digits.  Similarly,
      the target field can be up to 32 bits in length, which
      would be 10 decimal digits.
      
        # lsscsi -xx
        [0:0:19:0x4022401100000000]  disk    IBM      2107900          3.44 /dev/sda
        # lsscsi
        [0:0:19:1074872354]disk    IBM      2107900          3.44  /dev/sda
        # cat lmb_guest.xml
        <domain type='kvm'>
          <name>lmb_guest</name>
          <memory unit='MiB'>1024</memory>
        ...trimmed...
          <devices>
            <controller type='scsi' model='virtio-scsi' index='0'/>
            <hostdev mode='subsystem' type='scsi'>
              <source>
                <adapter name='scsi_host0'/>
                <address bus='0' target='19' unit='1074872354'/>
              </source>
            </hostdev>
        ...trimmed...
      
      Since the reference unit and target fields are used in
      several places in the XML schema, create a separate one
      specific for SCSI Logical Units that will permit the
      greater length.  This permits both the validation utility
      and the virsh edit command to succeed when a hostdev
      tag is included.
      Signed-off-by: NEric Farman <farman@linux.vnet.ibm.com>
      Reviewed-by: NMatthew Rosato <mjrosato@linux.vnet.ibm.com>
      Reviewed-by: NStefan Zimmermann <stzi@linux.vnet.ibm.com>
      Reviewed-by: NBoris Fiuczynski <fiuczy@linux.vnet.ibm.com>
      c733e973
  11. 18 6月, 2015 1 次提交
  12. 16 6月, 2015 5 次提交
  13. 15 6月, 2015 1 次提交
  14. 13 6月, 2015 1 次提交
  15. 11 6月, 2015 6 次提交
  16. 10 6月, 2015 1 次提交
  17. 04 6月, 2015 2 次提交
  18. 01 6月, 2015 3 次提交
  19. 26 5月, 2015 1 次提交