Skip to content

L
libvirt

openeuler / libvirt

通知 3
Star 0
Fork 0
L
libvirt
切换分支/标签
  1. 27 9月, 2017 1 次提交
  3. 21 9月, 2017 2 次提交
  5. 20 9月, 2017 3 次提交
  7. 18 9月, 2017 2 次提交
  9. 15 9月, 2017 3 次提交
    • J
      conf: Add invalid domain disk encryption test · 411cdb61
      由 John Ferlan 提交于 
      Add a test to prove checking for invalid luks disk formatting check.
The error message will indicate supplying the <cipher> element is
unnecessary.
      411cdb61
    • J
      conf: Add invalid secrettype checks · fbad3ed0
      由 John Ferlan 提交于 
      Add a couple of tests to "validate" checks in domain_conf that either
a missing secrettype (CONFIG_UNSUPPORTED) or an mismatched secrettype
of ceph for an iSCSI disk (INTERNAL_ERROR) will cause a parsing error.
      fbad3ed0
    • J
      docs: Remove unnecessary <auth> example for iscsi disk type='volume' · 4775ca27
      由 John Ferlan 提交于 
      Alter the example to remove the <auth> from:

  <disk type='volume' device='disk'>
    <driver name='qemu' type='raw'/>
    <source pool='iscsi-pool' volume='unit:0:0:1' mode='host'/>
    <auth username='myuser'>
      <secret type='iscsi' usage='libvirtiscsi'/>
    </auth>
    <target dev='vdb' bus='virtio'/>
  </disk>

and

  <disk type='volume' device='disk'>
    <driver name='qemu' type='raw'/>
    <source pool='iscsi-pool' volume='unit:0:0:2' mode='direct'/>
    <auth username='myuser'>
      <secret type='iscsi' usage='libvirtiscsi'/>
    </auth>
    <target dev='vdc' bus='virtio'/>
  </disk>

The reality is, it's not even used. For a <source pool> the authdef
from the storage source pool will supercede whatever is in the <disk>
definition during virStorageTranslateDiskSourcePool processing. In fact,
if the pool doesn't have/need authentication, then the authdef would
be removed anyway as the storage pool would be handling things.

The "proof" for this is in the adjustment to the test to add an
<auth> for a disk. The resulting .args file won't add what normally
would be added "myname:encodedpassword@" prior to the hostname in
the IQN (e.g. iscsi://myname:encodedpassword@iscsi.example.org:3260/...
      4775ca27
  11. 12 9月, 2017 1 次提交
    • J
      qemu: Provide default LUN=0 for iSCSI if not provided · f64f03b5
      由 John Ferlan 提交于 
      https://bugzilla.redhat.com/show_bug.cgi?id=1477880

If the "/#" is missing from the provided iSCSI path, then we need
to provide the default LUN of /0; otherwise, QEMU will fail to parse
the URL causing a failure to either create the guest or hotplug
attach the storage.

During post parse, for any iSCSI disk or hostdev, scan the source
path looking for the presence of '/', if found, then we can assume
the LUN is provided.  If not found, alter the input XML to add the
"/0".  This will cause the generated XML to have the generated
value when the domain config is saved after post parse.
      f64f03b5
  13. 11 9月, 2017 1 次提交
    • J
      tests: merge iommu tests · 190a5bc1
      由 Ján Tomko 提交于 
      Using intremap without <ioapic driver='qemu'/> does not work.
Merge the tests to avoid a duplicit test once we start validating it.
      190a5bc1
  15. 05 9月, 2017 1 次提交
  17. 30 8月, 2017 3 次提交
  19. 29 8月, 2017 2 次提交
  21. 21 8月, 2017 2 次提交
  23. 17 8月, 2017 1 次提交
    • C
      tests: add qemu x86 kvm 32-on-64 test · 21de51c3
      由 Cole Robinson 提交于 
      There's some specific logic in qemuBuildCpuCommandLine to support
auto adding -cpu qemu 32 for arch=i686 with an x86_64 qemu binary.
Add a test case for it
      21de51c3
  25. 10 8月, 2017 1 次提交
  27. 07 8月, 2017 1 次提交
  29. 03 8月, 2017 2 次提交
    • C
      qemu: command: rework adding of default cpu model · 05583fcb
      由 Cole Robinson 提交于 
      Certain XML features that aren't in the <cpu> block map to -cpu
flags on the qemu cli. If one of these is specified but the user
didn't explicitly pass an XML <cpu> model, we need to format a
default model on the command line.

The current code handles this by sprinkling this default cpu handling
among all the different flag string formatting. Instead, switch it
to do this just once.

This alters some test output slightly: the previous code would
write the default -cpu in some cases when no flags were actually
added, so the output was redundant.
Reviewed-by: NJán Tomko <jtomko@redhat.com>
Signed-off-by: NCole Robinson <crobinso@redhat.com>
      05583fcb
    • N
      qemu: command: align disk serial check to schema · cc6d43bb
      由 Nikolay Shirokovskiy 提交于 
      Disk serial schema has extra '.+' allowed characters in comparison
with check in code. Looks like there is no reason for that as qemu
allows any character AFAIK for serial. This discrepancy is originated
in commit id '85d15b51' where the ability to add serial was added.

Alter the disk-serial test to add a disk with all the possible
characters listed as the serial value.
      cc6d43bb
  31. 02 8月, 2017 1 次提交
  33. 27 7月, 2017 1 次提交
  35. 26 7月, 2017 2 次提交
    • A
      tests: Prepare for stricter NIC model validation · 9e6fb861
      由 Andrea Bolognani 提交于 
      While using "definitely-not-virtio" as a model name is very
cute, it will also cause the relevant test to fail once we
introduce stricter validation.

Use "e1000", which is definitely not virtio but also a valid
model name, instead.
Signed-off-by: NAndrea Bolognani <abologna@redhat.com>
      9e6fb861
    • S
      Generate unique socket file · a7bc2c8c
      由 Scott Garfinkle 提交于 
      It's possible to have more than one unnamed virtio-serial unix channel.
We need to generate a unique name for each channel. Currently, we use
".../unknown.sock" for all of them. Better practice would be to specify
an explicit target path name; however, in the absence of that, we need
uniqueness in the names we generate internally.

Before the changes we'd get /var/lib/libvirt/qemu/channel/target/unknown.sock
for each instance of
    <channel type='unix'>
        <source mode='bind'/>
        <target type='virtio'/>
    </channel>

Now, we get vioser-00-00-01.sock, vioser-00-00-02.sock, etc.
Signed-off-by: NScott Garfinkle <seg@us.ibm.com>
      a7bc2c8c
  37. 21 7月, 2017 1 次提交
    • S
      qemu: Enable NUMA node tag in pci-root for PPC64 · e5a05799
      由 Shivaprasad G Bhat 提交于 
      This patch addresses the same aspects on PPC the bug 1103314 addressed
on x86.

PCI expander bus creates multiple primary PCI busses, where each of these
busses can be assigned a specific NUMA affinity, which, on x86 is
advertised through ACPI on a per-bus basis.

For SPAPR, a PHB's NUMA affinities are assigned on a per-PHB basis, and
there is no mechanism for advertising NUMA affinities to a guest on a
per-bus basis. So, even if qemu-ppc manages to get some sort of multi-bus
topology working using PXB, there is no way to expose the affinities
of these busses to the guest. It can only be exposed on a per-PHB/per-domain
basis.

So patch enables NUMA node tag in pci-root controller on PPC.

The way to set the NUMA node is through the numa_node option of
spapr-pci-host-bridge device. However for the implicit PHB, the only way
to set the numa_node is from the -global option. The -global option applies
to all the PHBs unless explicitly specified with the option on the
respective PHB of CLI. The default PHB has the emulated devices only, so
the patch prevents setting the NUMA node for the default PHB.
Signed-off-by: NShivaprasad G Bhat <sbhat@linux.vnet.ibm.com>
Reviewed-by: NAndrea Bolognani <abologna@redhat.com>
      e5a05799
  39. 18 7月, 2017 1 次提交
  41. 15 7月, 2017 4 次提交
  43. 11 7月, 2017 4 次提交