Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • v1.2.19-maint protected
  • v1.3.2-maint protected
  • v1.3.1-maint protected
  • v1.3.0-maint protected
  • v1.2.21-maint protected
  • v1.2.20-maint protected
  • v1.3.3-maint protected
  • v1.3.4-maint protected
  • v1.3.5-maint protected
  • v2.0-maint protected
  • v2.1-maint protected
  • v2.2-maint protected
  • v3.0-maint protected
  • v3.2-maint protected
  • v3.7-maint protected
  • v4.1-maint protected
  • v4.2-maint protected
  • v4.3-maint protected
  • v4.4-maint protected
  • v11.2.0 protected
  • v11.2.0-rc2 protected
  • v11.2.0-rc1 protected
  • v11.1.0 protected
  • v11.1.0-rc2 protected
  • v11.1.0-rc1 protected
  • v11.0.0 protected
  • v11.0.0-rc2 protected
  • v11.0.0-rc1 protected
  • v10.10.0 protected
  • v10.10.0-rc2 protected
  • v10.10.0-rc1 protected
  • v10.9.0 protected
  • v10.9.0-rc2 protected
  • v10.9.0-rc1 protected
  • v10.8.0 protected
  • v10.8.0-rc2 protected
  • v10.8.0-rc1 protected
  • v10.7.0 protected
  • v10.7.0-rc2 protected
40 results

libvirt

  • Clone with SSH
  • Clone with HTTPS
  • Michal Privoznik's avatar
    Michal Privoznik authored
    There are PCI devices with pretty large non-prefetchable memory,
    for instance:
    
      Memory at 9d800000 (64-bit, non-prefetchable) [size=8M]
      Memory at a6800000 (64-bit, non-prefetchable) [size=16K]
    
    For cold plugged devices this is not a problem, because firmware
    sets PCI controllers in a way that make devices behind them just
    work. Problem arises if such PCI device is to be hot plugged.
    Since the PCI device wasn't present at cold boot, firmware could
    not take it into calculations and the amount of reserved memory
    is not sufficient.
    
    Introduce a know that allows users overriding value computed by
    FW and thus allow hot plug of such PCI devices.
    
    Signed-off-by: default avatarMichal Privoznik <mprivozn@redhat.com>
    Reviewed-by: default avatarAndrea Bolognani <abologna@redhat.com>
    05c256f5
    History
    GitLab CI Build Status CII Best Practices Translation status

    Libvirt API for virtualization

    Libvirt provides a portable, long term stable C API for managing the virtualization technologies provided by many operating systems. It includes support for QEMU, KVM, Xen, LXC, bhyve, Virtuozzo, VMware vCenter and ESX, VMware Desktop, Hyper-V, VirtualBox and the POWER Hypervisor.

    For some of these hypervisors, it provides a stateful management daemon which runs on the virtualization host allowing access to the API both by non-privileged local users and remote users.

    Layered packages provide bindings of the libvirt C API into other languages including Python, Perl, PHP, Go, Java, OCaml, as well as mappings into object systems such as GObject, CIM and SNMP.

    Further information about the libvirt project can be found on the website:

    https://libvirt.org

    License

    The libvirt C API is distributed under the terms of GNU Lesser General Public License, version 2.1 (or later). Some parts of the code that are not part of the C library may have the more restrictive GNU General Public License, version 2.0 (or later). See the files COPYING.LESSER and COPYING for full license terms & conditions.

    Installation

    Instructions on building and installing libvirt can be found on the website:

    https://libvirt.org/compiling.html

    Contributing

    The libvirt project welcomes contributions in many ways. For most components the best way to contribute is to send patches to the primary development mailing list. Further guidance on this can be found on the website:

    https://libvirt.org/contribute.html

    Contact

    The libvirt project has two primary mailing lists:

    Further details on contacting the project are available on the website:

    https://libvirt.org/contact.html