- Devel - libvirt List Archives

Gsoc2021
by Aaryan Singh 01 Apr '21

01 Apr '21

Hello, This is Aaryan, a 2nd-year undergraduate student at Kalinga institute of industrial technology. I have a keen interest in the " test driver API coverage " project. since I have worked in cloud computing and DevOps that's why I am this interested in this project and would love to share my idea and develop it. Thank you

3 2

Release of libvirt-7.2.0
by Jiri Denemark 01 Apr '21

01 Apr '21

The 7.2.0 release of both libvirt and libvirt-python is tagged and signed tarballs and source RPMs are available at https://libvirt.org/sources/ https://libvirt.org/sources/python/ Thanks everybody who helped with this release by sending patches, reviewing, testing, or providing any other feedback. Your work is greatly appreciated. * New features * qemu: Implement domain memory dirty rate calculation API New API ``virDomainStartDirtyRateCalc()`` and virsh command ``domdirtyrate-calc`` are added to start calculating a live domain's memory dirty rate. * qemu: Support reporting memory dirty rate stats The memory dirty rate stats can be obtained through ``virsh domstats --dirtyrate`` via the virConnectGetAllDomainStats API. * qemu: Full disk backups via ``virDomainBackupBegin`` The qemu hypervisor driver now allows taking full disk backups via the ``virDomainBackupBegin`` API and the corresponding virsh wrapper. In future releases the feature will be extended to also support incremental backups (where only the difference since the last backup is copied) when qemu adds the required functionality. * Add support for audio backend specific settings With this release a new ``<audio/>`` element is introduced that allows users to configure audio output for their guests. * Improvements * qemu: Compatibility with QEMU 6.0 for certain hot-(un)-plug operations Libvirt 7.2.0 is required for compatibility with the upcoming QEMU 6.0 release for hotplug and hotunplug of certain devices and helpers, such as iothreads, chardevs, RNG devices, disks with secret, ... * qemu: Various improvements to embedded mode Embedded mode for the QEMU driver, as well as the ``virt-qemu-run`` tool saw improvements in handling of domain life cycle, temporary directories creation (important when using disk secrets) and other minor fixes. * Documentation of split daemon related config files Split daemons read configuration files upon their start. These were never documented though. * Bug fixes * Check host CPU for forbidden features CPU feature policy did not work as expected with ``host-passthrough`` and features supported by physical host. CPU features were not filtered out when ``@check`` was set to ``full``. * Fix virNetworkUpdate() to work with split daemons Due to a bug in our code, virNetworkUpdate() did not work with split daemon unless management application connected to virtnetworkd directly. * qemu: increase locked memory limit when a vDPA device is present Just like VFIO devices, vDPA devices may need to have all guest memory pages locked/pinned in order to operate properly. These devices are now included when calculating the limit for memory lock. * Don't log error if SRIOV PF has no associated netdev Some SRIOV PFs don't have a netdev associated with them in which case libvirtd reported an error and refused to start. This is now fixed. * qemu: Only raise memlock limit if necessary Attempting to set the memlock limit might fail if we're running in a containerized environment where ``CAP_SYS_RESOURCE`` is not available, and if the limit is already high enough there's no point in trying to raise it anyway. * Restore security context of swtpm.log If a guest with emulated TPM was started and the daemon was restarted afterwards, the security context of the per-domain ``swtpm.log`` file was not restored on domain shutdown leaving it unable to be started again. * virtlogd|virtlockd: Fixed crash when upgrading the daemons in-place A bug preventing the in-place upgrade of ``virtlogd`` and ``virtlockd`` daemons was fixed, so they can again be upgraded without dropping the log file descriptors or locks on files. Enjoy. Jirka

1 0

[PATCH] docs: formatnetworkport: Fix typos
by Han Han 01 Apr '21

01 Apr '21

Signed-off-by: Han Han <hhan(a)redhat.com> --- docs/formatnetworkport.html.in | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/formatnetworkport.html.in b/docs/formatnetworkport.html.in index 199a05f929..2d41552618 100644 --- a/docs/formatnetworkport.html.in +++ b/docs/formatnetworkport.html.in @@ -31,13 +31,13 @@ </p> <pre> -<networkport +<networkport> <uuid>7ae63b5f-fe96-4af0-a7c3-da04ba1b3f54</uuid> <owner> <uuid>06578fc1-c686-46fa-bc2c-220893b466a6</uuid> - <name>myguest<name> + <name>myguest</name> </owner> - <group>webfront<group> + <group>webfront</group> <mac address='52:54:0:7b:35:93'/> ...</pre> -- 2.31.1

2 1

[PATCH resend] lib: Drop internal virXXXPtr typedefs
by Michal Privoznik 01 Apr '21

01 Apr '21

1 0

[PATCH 0/6] qemu: Allow control of deprecation behaviour
by Peter Krempa 01 Apr '21

01 Apr '21

For debugging purposes it's very useful to disable all deprecated commands and fields in qemu. This series implements a qemu.conf knob and a qemu namespace element to control this. The implementation tries to be very conservative to allow downgrades of qemu and such without breaking the startup of the VM. The intention is that developers and CI deployments use the 'crash' option to catch any unexpected qemu disappearance. Note that this applies on top of my series for -object QAPIfication. Based on Markus' -compat series which was now merged to upstream qemu. Peter Krempa (6): docs/drvqemu: Convert to RST qemu: capabilities: Introduce QEMU_CAPS_COMPAT_DEPRECATED qemu: conf: Add 'deprecation_behavior' setting to qemu.conf qemuxml2xmltest: Enable 'qemu-ns' case qemu: Add per-VM control of deprecation behavior qemu: command: Handle formatting of '-compat' options docs/drvqemu.html.in | 743 ------------------ docs/drvqemu.rst | 636 +++++++++++++++ docs/formatdomain.rst | 2 +- docs/manpages/virt-qemu-run.rst | 2 +- docs/meson.build | 2 +- docs/schemas/domaincommon.rng | 16 + src/qemu/libvirtd_qemu.aug | 1 + src/qemu/qemu.conf | 31 + src/qemu/qemu_capabilities.c | 8 + src/qemu/qemu_capabilities.h | 1 + src/qemu/qemu_command.c | 80 ++ src/qemu/qemu_conf.c | 4 + src/qemu/qemu_conf.h | 2 + src/qemu/qemu_domain.c | 10 +- src/qemu/qemu_domain.h | 5 + src/qemu/test_libvirtd_qemu.aug.in | 1 + .../caps_6.0.0.x86_64.xml | 1 + .../qemu-ns.x86_64-latest.args | 1 + tests/qemuxml2argvdata/qemu-ns.xml | 1 + .../qemu-ns.x86_64-latest.xml | 52 ++ tests/qemuxml2xmltest.c | 1 + 21 files changed, 853 insertions(+), 747 deletions(-) delete mode 100644 docs/drvqemu.html.in create mode 100644 docs/drvqemu.rst create mode 100644 tests/qemuxml2xmloutdata/qemu-ns.x86_64-latest.xml -- 2.29.2

2 15

[libvirt PATCH 0/2] qemu: wire up support for rotation rate for disks
by Daniel P. Berrangé 01 Apr '21

01 Apr '21

By default QEMU doesn't report any rotation information to guests, so guests assume rotational media. This lets the user specify an explicit speed in RPM, or 1 for SSD. This may allow the user to achieve better performance for their virtual disks. Note, however, this doesn't mean that the guest should be given the same setting as the host storage. It is possible that better performance may be achieved with contrary settings from the host. Testing is required to determine this on a case by case basis. Daniel P. Berrangé (2): conf: add support for disk "rotation_rate" property qemu: implement setting of rotation rate for SCSI/IDE disks docs/formatdomain.rst | 13 ++++- docs/schemas/domaincommon.rng | 5 ++ src/conf/domain_conf.c | 11 ++++ src/conf/domain_conf.h | 1 + src/qemu/qemu_capabilities.c | 2 + src/qemu/qemu_capabilities.h | 1 + src/qemu/qemu_command.c | 3 + src/qemu/qemu_validate.c | 22 ++++++++ .../caps_2.12.0.aarch64.xml | 1 + .../caps_4.0.0.aarch64.xml | 1 + .../qemucapabilitiesdata/caps_4.0.0.ppc64.xml | 1 + .../caps_4.0.0.riscv32.xml | 1 + .../caps_4.0.0.riscv64.xml | 1 + .../qemucapabilitiesdata/caps_4.0.0.s390x.xml | 1 + .../caps_4.0.0.x86_64.xml | 1 + .../caps_4.1.0.x86_64.xml | 1 + .../caps_4.2.0.aarch64.xml | 1 + .../qemucapabilitiesdata/caps_4.2.0.ppc64.xml | 1 + .../qemucapabilitiesdata/caps_4.2.0.s390x.xml | 1 + .../caps_4.2.0.x86_64.xml | 1 + .../caps_5.0.0.aarch64.xml | 1 + .../qemucapabilitiesdata/caps_5.0.0.ppc64.xml | 1 + .../caps_5.0.0.riscv64.xml | 1 + .../caps_5.0.0.x86_64.xml | 1 + .../qemucapabilitiesdata/caps_5.1.0.sparc.xml | 1 + .../caps_5.1.0.x86_64.xml | 1 + .../caps_5.2.0.aarch64.xml | 1 + .../qemucapabilitiesdata/caps_5.2.0.ppc64.xml | 1 + .../caps_5.2.0.riscv64.xml | 1 + .../qemucapabilitiesdata/caps_5.2.0.s390x.xml | 1 + .../caps_5.2.0.x86_64.xml | 1 + .../caps_6.0.0.x86_64.xml | 1 + .../disk-rotation.x86_64-latest.args | 56 +++++++++++++++++++ tests/qemuxml2argvdata/disk-rotation.xml | 38 +++++++++++++ tests/qemuxml2argvtest.c | 1 + .../disk-rotation.x86_64-latest.xml | 55 ++++++++++++++++++ tests/qemuxml2xmltest.c | 1 + 37 files changed, 230 insertions(+), 3 deletions(-) create mode 100644 tests/qemuxml2argvdata/disk-rotation.x86_64-latest.args create mode 100644 tests/qemuxml2argvdata/disk-rotation.xml create mode 100644 tests/qemuxml2xmloutdata/disk-rotation.x86_64-latest.xml -- 2.30.2

4 9

[PATCH] docs: Fix broken link in migrationinternals
by Han Han 31 Mar '21

31 Mar '21

Signed-off-by: Han Han <hhan(a)redhat.com> --- docs/kbase/migrationinternals.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/kbase/migrationinternals.rst b/docs/kbase/migrationinternals.rst index 2e187936a7..f7b4b5a10e 100644 --- a/docs/kbase/migrationinternals.rst +++ b/docs/kbase/migrationinternals.rst @@ -7,7 +7,7 @@ Libvirt migration internals Migration is a multi-step operation with at least two distinct actors, the source and the destination libvirtd daemons, and a lot of failure points. This document describes the basic migration workflow in the -code level, as a way to complement `the base migration docs <migration.html>`_ +code level, as a way to complement `the base migration docs <../migration.html>`_ and help developers to get up to speed quicker with the code. In this document, unless stated otherwise, these conventions are followed: -- 2.30.2

2 1

[PATCH] NEWS: Fix typo swtmp -> swtpm
by Andrea Bolognani 31 Mar '21

31 Mar '21

Signed-off-by: Andrea Bolognani <abologna(a)redhat.com> --- Pushed as trivial. NEWS.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/NEWS.rst b/NEWS.rst index 9eb771cd0b..3f4380ff23 100644 --- a/NEWS.rst +++ b/NEWS.rst @@ -91,7 +91,7 @@ v7.2.0 (unreleased) * Restore security context of swtpm.log If a guest with emulated TPM was started and the daemon was restarted - afterwards, the security context of the per-domain ``swtmp.log`` file was + afterwards, the security context of the per-domain ``swtpm.log`` file was not restored on domain shutdown leaving it unable to be started again. * virtlogd|virtlockd: Fixed crash when upgrading the daemons in-place -- 2.26.3

1 0

[Libvirt] Attach qemu commands to an running xml domain
by Waleed Musa 31 Mar '21

31 Mar '21

Hi all, I see in libvirt you are supporting attach/detach devices to existing xml domain using attachDeviceFlags and detachDeviceFlags APIs. Now we are adding some qemu command to the xml domain related to some interfaces using alias names before starting the VM, but we will face an issue with hot plug such devices, so I have two question here: 1. Is it applicable to set the alias names for interfaces because I saw it's ignored when I add it to xml domain before starting the VM? 2. Is there a way or API to attach qemu commands to running domain as you are doing in attaching the device using attachDeviceFlags? Example of my xml <domain type='kvm' id='5' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <devices> <interface type='vhostuser'> <mac address='fa:16:3e:ac:12:4c'/> <source type='unix' path='/var/lib/vhost_sockets/sockbbb6bbe9-eb5' mode='server'/> <target dev='tapbbb6bbe9-eb'/> <model type='virtio'/> <driver queues='4' rx_queue_size='512' tx_queue_size='512'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> </devices> <qemu:commandline> <qemu:arg value='-set'/> <qemu:arg value='device.net0.page-per-vq=on'/> <qemu:arg value='-set'/> <qemu:arg value='device.net0.host_mtu=8942'/> </qemu:commandline> </domain> Regards, Waleed Mousa Software Engineer, Nvidia <https://www.nvidia.com/en-me/geforce/>

5 10

[PATCH] news: Update for upcoming release
by Michal Privoznik 31 Mar '21

31 Mar '21

Mention some of the stuff we dealt with in this release. Signed-off-by: Michal Privoznik <mprivozn(a)redhat.com> --- NEWS.rst | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 51 insertions(+) diff --git a/NEWS.rst b/NEWS.rst index 71f357e39f..f823fc8575 100644 --- a/NEWS.rst +++ b/NEWS.rst @@ -33,6 +33,11 @@ v7.2.0 (unreleased) backups (where only the difference since the last backup is copied) when qemu adds the required functionality. + * Add support for audio backend specific settings + + With this release new ``<audio/>`` element is introduced that allows users + to configure audio output for their guests. + * **Improvements** * qemu: Compatibility with QEMU 6.0 for certain hot-(un)-plug operations @@ -41,8 +46,54 @@ v7.2.0 (unreleased) release for hotplug and hotunplug of certain devices and helpers, such as iothreads, chardevs, RNG devices, disks with secret, ... + * Various improvements for embed driver + + The embed driver and ``virt-qemu-run`` tool saw improvements in handling of + domain life cycle, temporary directories creation (important when using + disk secrets) and other minor fixes. + + * Documentation of split daemon related config files + + Split daemons read configuration files upon their start. These were never + documented though. + * **Bug fixes** + * Check host cpu for forbidden features + + CPU feature policy did not work as expected with host-passthrough and + features supported by physical host. CPU features were not filtered out + when ``@check`` was set to ``full``. + + * virNetworkUpdate() can not work with the split daemon + + Due to a bug in our code, virNetworkUpdate() did not work with split daemon + unless management application connected to virtnetworkd directly. + + * qemu: increase locked memory limit when a vDPA device is present + + Just like VFIO devices, vDPA devices may need to have all guest memory + pages locked/pinned in order to operate properly. These devices are now + included when calculating the limit for memory lock. + + * Don't log error if SRIOV PF has no associated netdev + + Some SRIOV PFs don't have a netdev associated with them in which case + libvirtd reported an error and refused to start. This is now fixed. + + * qemu: Only raise memlock limit if necessary + + Attempting to set the memlock limit might fail if we're running + in a containerized environment where CAP_SYS_RESOURCE is not + available, and if the limit is already high enough there's no + point in trying to raise it anyway. + + * Restore security context of swtpm.log + + If a guest with emulated TPM was started and the daemon was restarted + afterwards, the security context of per domain swtmp.log file was not + restored on domain shutdown leaving it unable to be started again. + * virtlogd|virtlockd: Fixed crash when upgrading the daemons in-place A bug preventing the in-place upgrade of ``virtlogd`` and ``virtlockd`` -- 2.26.3

3 2