Skip to content

L
libvirt

openeuler / libvirt

通知 3
Star 0
Fork 0
L
libvirt

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 17 3月, 2017 4 次提交
  3. 16 3月, 2017 1 次提交
  5. 15 3月, 2017 5 次提交
    • M
      qemu: Introduce label-size for NVDIMMs · e433546b
      由 Michal Privoznik 提交于 
      For NVDIMM devices it is optionally possible to specify the size
of internal storage for namespaces. Namespaces are a feature that
allows users to partition the NVDIMM for different uses.
Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      e433546b
    • M
      qemu: Implement @access for <memory/> banks · 04dc668a
      由 Michal Privoznik 提交于 
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      04dc668a
    • M
      conf: Introduce @access to <memory/> · 80af11d3
      由 Michal Privoznik 提交于 
      Now that NVDIMM has found its way into libvirt, users might want
to fine tune some settings for each module separately. One such
setting is 'share=on|off' for the memory-backend-file object.
This setting - just like its name suggest already - enables
sharing the nvdimm module with other applications. Under the hood
it controls whether qemu mmaps() the file as MAP_PRIVATE or
MAP_SHARED.

Yet again, we have such config knob in domain XML, but it's just
an attribute to numa <cell/>. This does not give fine enough
tuning on per-memdevice basis so we need to have the attribute
for each device too.
Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      80af11d3
    • M
      qemu: Implement NVDIMM · 1bc17319
      由 Michal Privoznik 提交于 
      So, majority of the code is just ready as-is. Well, with one
slight change: differentiate between dimm and nvdimm in places
like device alias generation, generating the command line and so
on.

Speaking of the command line, we also need to append 'nvdimm=on'
to the '-machine' argument so that the nvdimm feature is
advertised in the ACPI tables properly.
Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      1bc17319
    • M
      Introduce NVDIMM memory model · b4e8a49f
      由 Michal Privoznik 提交于 
      NVDIMM is new type of memory introduced into QEMU 2.6. The idea
is that we have a Non-Volatile memory module that keeps the data
persistent across domain reboots.

At the domain XML level, we already have some representation of
'dimm' modules. Long story short, NVDIMM will utilize the
existing <memory/> element that lives under <devices/> by adding
a new attribute 'nvdimm' to the existing @model and introduce a
new <path/> element for <source/> while reusing other fields. The
resulting XML would appear as:

    <memory model='nvdimm'>
      <source>
        <path>/tmp/nvdimm</path>
      </source>
      <target>
        <size unit='KiB'>523264</size>
        <node>0</node>
      </target>
      <address type='dimm' slot='0'/>
    </memory>

So far, this is just a XML parser/formatter extension. QEMU
driver implementation is in the next commit.

For more info on NVDIMM visit the following web page:

    http://pmem.io/Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      b4e8a49f
  7. 14 3月, 2017 3 次提交
  9. 12 3月, 2017 3 次提交
  11. 11 3月, 2017 1 次提交
    • J
      tests: Add createVHBAByStoragePool-by-parent to fchosttest · 0623945c
      由 John Ferlan 提交于 
      Add a new test to fchosttest in order to test creation of our vHBA
via the Storage Pool logic.  Unlike the real code, we cannot yet use
the virVHBA* API's because they (currently) traverse the file system
in order to get the parent vport capable scsi_host. Besides there's
no "real" NPIV device here - so we have to take some liberties, at
least for now.

Instead, we'll follow the node device tests partially in order to
create and destroy the vHBA with the test node devices.
Signed-off-by: NJohn Ferlan <jferlan@redhat.com>
      0623945c
  13. 10 3月, 2017 1 次提交
    • M
      qemuxml2argvtest: Don't overwrite driver stateDir · 887ffbce
      由 Michal Privoznik 提交于 
      This is a very historic artefact. Back in the old days of
830ba76c when we had macros to add arguments onto qemu command
line (!) we thought it was a good idea to let qemu write out the
PID file. So we passed -pidfile $stateDir/$domName onto the
command line. Thus, in order for tests to work we needed stable
stateDir in the qemu driver. Unfortunately, after 16efa11a
where stateDir is mkdtemp()-d, this approach lead to a leak of
temp dir.
Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      887ffbce
  15. 09 3月, 2017 1 次提交
  17. 08 3月, 2017 10 次提交
  19. 07 3月, 2017 4 次提交
  21. 06 3月, 2017 3 次提交
    • J
      Test virSystemd APIs twice to check the cache effects · 9b1bd138
      由 Ján Tomko 提交于 
      Test virSystemd APIs twice to check the cache effects.
      9b1bd138
    • J
      Cache the presence of machine1 service · f10bd740
      由 Ján Tomko 提交于 
      After the system has been booted, it should not change.

Cache the return value of virSystemdHasMachined.
Allow starting and terminating machines with just one
DBus call, instead of three, reducing the chance of
the call timing out.

Also introduce a small function for resetting the cache
to be used in tests.
      f10bd740
    • J
      Use macros for testing virSystemd APIs · 27cdbcb9
      由 Ján Tomko 提交于 
      This hides the unused third parameter from every line
and prepares for resetting the environment after each test
case in the future.
      27cdbcb9
  23. 04 3月, 2017 4 次提交