Skip to content

L
libvirt

openeuler / libvirt

通知 3
Star 0
Fork 0
L
libvirt

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

切换分支/标签
  1. 11 6月, 2015 1 次提交
  3. 10 6月, 2015 1 次提交
  5. 21 5月, 2015 1 次提交
  7. 18 5月, 2015 1 次提交
  9. 05 5月, 2015 1 次提交
    • M
      Introduce GIC feature · 921c52b0
      由 Michal Privoznik 提交于 
      Some platforms, like aarch64, don't have APIC but GIC. So there's
no reason to have <apic/> feature turned on. However, we are
still missing <gic/> feature. This commit introduces the feature
to XML parser and formatter, adds documentation and updates RNG
schema.
Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      921c52b0
  11. 04 5月, 2015 1 次提交
    • M
      docs: add domain vmport feature · 208abbcb
      由 Marc-André Lureau 提交于 
      A new feature that can be turned on or off.

The QEMU machine vmport option allows to set the VMWare IO port
emulation. This emulation is useful for absolute pointer input when the
guest has vmware input drivers, and is enabled by default for kvm.

However it is unnecessary for Spice-enabled VM, since the agent already
handles absolute pointer and multi-monitors. Furthermore, it prevents
Spice from switching to relative input since the regular ps/2 pointer
driver is replaced by the vmware driver. It is thus advised to disable
vmport when using a Spice VM. This will permit the Spice client to
switch from absolute to relative pointer, as it may be required for
certain games or applications.
      208abbcb
  13. 28 4月, 2015 1 次提交
    • J
      conf: Add new domain XML element 'iothreadids' · 93383c1f
      由 John Ferlan 提交于 
      Adding a new XML element 'iothreadids' in order to allow defining
specific IOThread ID's rather than relying on the algorithm to assign
IOThread ID's starting at 1 and incrementing to iothreads count.

This will allow future patches to be able to add new IOThreads by
a specific iothread_id and of course delete any exisiting IOThread.

Each iothreadids element will have 'n' <iothread> children elements
which will have attribute "id".  The "id" will allow for definition
of any "valid" (eg > 0) iothread_id value.

On input, if any <iothreadids> <iothread>'s are provided, they will
be marked so that we only print out what we read in.

On input, if no <iothreadids> are provided, the PostParse code will
self generate a list of ID's starting at 1 and going to the number
of iothreads defined for the domain (just like the current algorithm
numbering scheme).  A future patch will rework the existing algorithm
to make use of the iothreadids list.

On output, only print out the <iothreadids> if they were read in.
      93383c1f
  15. 20 4月, 2015 2 次提交
  17. 17 4月, 2015 1 次提交
  19. 25 3月, 2015 1 次提交
    • G
      Don't validata filesystem target type · db1edae8
      由 Guido Günther 提交于 
      When using QEMU's 9pfs the target "dir" element is not necessarily an
absolute path but merely an arbitrary identifier. So validation in that
case currently fails with the misleading

   $ virt-xml-validate /tmp/test.xml
   Relax-NG validity error : Extra element devices in interleave
   /tmp/test.xml:24: element devices: Relax-NG validity error : Element domain failed to validate content
   /tmp/test.xml fails to validate
      db1edae8
  21. 23 3月, 2015 3 次提交
    • P
      conf: Add interface to parse and format memory device information · 3e4230d2
      由 Peter Krempa 提交于 
      This patch adds code that parses and formats configuration for memory
devices.

A simple configuration would be:
<memory model='dimm'>
  <target>
    <size unit='KiB'>524287</size>
    <node>0</node>
  </target>
</memory>

A complete configuration of a memory device:
<memory model='dimm'>
  <source>
    <pagesize unit='KiB'>4096</pagesize>
    <nodemask>1-3</nodemask>
  </source>
  <target>
    <size unit='KiB'>524287</size>
    <node>1</node>
  </target>
</memory>

This patch preemptively forbids use of the <memory> device in individual
drivers so the users are warned right away that the device is not
supported.
      3e4230d2
    • P
      conf: Add device address type for dimm devices · 62b825a2
      由 Peter Krempa 提交于 
      Dimm devices are described by the slot and base address. Add a new
address type to be able to describe such address.
      62b825a2
    • P
      conf: Add support for parsing and formatting max memory and slot count · bffb9163
      由 Peter Krempa 提交于 
      Add a XML element that will allow to specify maximum supportable memory
and the count of memory slots to use with memory hotplug.

To avoid possible confusion and misuse of the new element this patch
also explicitly forbids the use of the maxMemory setting in individual
drivers's post parse callbacks. This limitation will be lifted when the
support is implemented.
      bffb9163
  23. 17 3月, 2015 1 次提交
  25. 16 3月, 2015 1 次提交
    • P
      conf: Make specifying <memory> optional · 4bca6192
      由 Peter Krempa 提交于 
      Now that the size of guest's memory can be inferred from the NUMA
configuration (if present) make it optional to specify <memory>
explicitly.

To make sure that memory is specified add a check that some form of
memory size was specified. One side effect of this change is that it is
no longer possible to specify 0KiB as memory size for the VM, but I
don't think it would be any useful to do so. (I can imagine embedded
systems without memory, just registers, but that's far from what libvirt
is usually doing).

Forbidding 0 memory for guests also fixes a few corner cases where 0 was
not interpreted correctly and caused failures. (Arguments for numad when
using automatic placement, size of the balloon). This fixes problems
described in https://bugzilla.redhat.com/show_bug.cgi?id=1161461

Test case changes are added to verify that the schema change and code
behave correctly.
      4bca6192
  27. 11 3月, 2015 1 次提交
  29. 05 3月, 2015 1 次提交
  31. 03 3月, 2015 2 次提交
  33. 26 2月, 2015 1 次提交
  35. 25 2月, 2015 1 次提交
  37. 21 2月, 2015 1 次提交
  39. 13 2月, 2015 1 次提交
  41. 12 2月, 2015 1 次提交
  43. 11 2月, 2015 1 次提交
    • E
      schema: allow multiple seclabel for devices in domaincommon.rng · 862bbf8a
      由 Erik Skultety 提交于 
      In our RNG schema we do allow multiple (different) seclabels per-domain,
but don't allow this for devices, yet we neither have a check in our XML parser,
nor in a post-parse callback. In that case we should allow multiple
(different) seclabels for devices as well.
      862bbf8a
  45. 29 1月, 2015 1 次提交
    • M
      schemas: Allow all generic elements and attributes for all interfaces · 52222568
      由 Michal Privoznik 提交于 
      There are some interface types (notably 'server' and 'client')
which instead of allowing the default set of elements and
attributes (like the rest do), try to enumerate only the elements
they know of. This way it's, however, easy to miss something. For
instance, the <address/> element was not mentioned at all. This
resulted in a strange behavior: when such interface was added
into XML, the address was automatically generated by parsing
code. Later, the formatted XML hasn't passed the RNG schema. This
became more visible once we've turned on the XML validation on
domain XML changes: appending an empty line at the end of
formatted XML (to trick virsh think the XML had changed) made
libvirt to refuse the very same XML it formatted.

Instead of trying to find each element and attribute we are
missing in the schema, lets just allow all the elements and
attributes like we're doing that for the rest of types. It's no
harm if the schema is wider than our parser allows.
Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      52222568
  47. 21 1月, 2015 1 次提交
  49. 16 1月, 2015 3 次提交
  51. 13 1月, 2015 1 次提交
  53. 06 1月, 2015 3 次提交
  55. 25 11月, 2014 1 次提交
  57. 21 11月, 2014 3 次提交
  59. 12 11月, 2014 1 次提交