- Announce - libvirt List Archives

[Libvirt-announce] Entering freeze for libvirt 5.4.0
by Daniel Veillard 31 May '19

31 May '19

This is tagged in git, I have put the signed tarball and source RPM at the usual place: https://libvirt.org/sources/ I did not build the binaries rpms, first it broke because I was still on F28 c.f. Jan's patch, and second it's true to provides little value, it's doubtful people would just install my binaries as is. Will likely stick to sources as part of releases in the future. Release looks fine in my limited testing, https://ci.centos.org/view/libvirt/ is of a rare uniform green color, which is promising too ! Please give it a try, I will likely cut RC2 on Thrusday, and then if everything goes fine push the GA over the w.e. or Monday, thanks, Daniel -- Daniel Veillard | Red Hat Developers Tools http://developer.redhat.com/ veillard(a)redhat.com | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | virtualization library http://libvirt.org/

1 1

[Libvirt-announce] LSN-2019-0003: Insecure permissions for systemd socket for virtlockd/virtlogd
by Daniel P. Berrangé 21 May '19

21 May '19

Libvirt Security Notice: LSN-2019-0003 ====================================== Summary: Insecure permissions for systemd socket for virtlockd/virtlogd Reported on: 20190430 Published on: 20190421 Fixed on: 20190421 Reported by: Daniel P. Berrangé <berrange(a)redhat.com> Patched by: Daniel P. Berrangé <berrange(a)redhat.com> See also: CVE-2019-10132 Description ----------- The virtlockd-admin.socket and virtlogd-admin.socket unit files do not set the SocketMode parameter and thus create a world accessible UNIX domain socket. Furthermore the code fails to validate the identity of clients connecting to these sockets. Impact ------ An unprivileged user is able to connect to the virtlockd or virtlogd daemons and use the administrative RPC commands to elevate their privileges Workaround ---------- Disable the virtlockd-admin.socket and virtlogd-admin.socket units in systemd. Alternative customize them to add SocketMode=0600 locally. Affected product ---------------- Name: libvirt Repository: git://libvirt.org/git/libvirt.git http://libvirt.org/git/?p=libvirt.git Branch: master Broken in: v4.1.0 Broken in: v4.2.0 Broken in: v4.3.0 Broken in: v4.4.0 Broken in: v4.5.0 Broken in: v4.6.0 Broken in: v4.7.0 Broken in: v4.8.0 Broken in: v4.9.0 Broken in: v4.10.0 Broken in: v5.0.0 Broken in: v5.1.0 Broken in: v5.2.0 Broken in: v5.3.0 Broken by: 85d45ff05db4a41ac3678ee0d4457b6b3323597e Broken by: ce7ae55ea1113bc574c5b5a61828e67fbd0e506f Fixed by: 96f41cd765c9e525fe28ee5abbfbf4a79b3720c7 Fixed by: f111e09468693909b1f067aa575efdafd9a262a1 Fixed by: e37bd65f9948c1185456b2cdaa3bd6e875af680f Branch: v4.1-maint Broken by: 85d45ff05db4a41ac3678ee0d4457b6b3323597e Broken by: ce7ae55ea1113bc574c5b5a61828e67fbd0e506f Fixed by: 39fb5ab3125d1669344bab94ccb71bce814d9ae2 Fixed by: 41f06e6095e17b61b2af35821d204afc5c34777c Fixed by: f0e014133104cdb5af5c7d96a7aa6dc0f1bbb03c Branch: v4.2-maint Broken by: 85d45ff05db4a41ac3678ee0d4457b6b3323597e Broken by: ce7ae55ea1113bc574c5b5a61828e67fbd0e506f Fixed by: 9bef445981a244622bfd64086d91016868656978 Fixed by: 63095b01eb9d9629c34a8a7c8a4b5ffd611b51c3 Fixed by: f845754de1b44375879bae4937acfb5d0965ac08 Branch: v4.3-maint Broken by: 85d45ff05db4a41ac3678ee0d4457b6b3323597e Broken by: ce7ae55ea1113bc574c5b5a61828e67fbd0e506f Fixed by: acf17630336568984e3e00d356fd75cdf2b1f09c Fixed by: 93d9f05684c818fb5eab9ffef7a4f9f9adbd7d02 Fixed by: 59fe946efccc1fe28a734a91de27550ece9467d5 Branch: v4.4-maint Broken by: 85d45ff05db4a41ac3678ee0d4457b6b3323597e Broken by: ce7ae55ea1113bc574c5b5a61828e67fbd0e506f Fixed by: ebc49c1dff2fc1999963dd225c3f9a7beb90e87b Fixed by: 13d340b328ad2d567f2878cfeedacd114a9172a7 Fixed by: faac7d474ad696f7e105ba776167f8d18d78d5d7 Branch: v4.5-maint Broken by: 85d45ff05db4a41ac3678ee0d4457b6b3323597e Broken by: ce7ae55ea1113bc574c5b5a61828e67fbd0e506f Fixed by: d1017aeee9da6d3db4389141b0f07f0a8204303d Fixed by: 618358632b6bfe93e46f038656609cf79b471bef Fixed by: ec58805400e8d394169af2355168bc439586f414 Branch: v4.6-maint Broken by: 85d45ff05db4a41ac3678ee0d4457b6b3323597e Broken by: ce7ae55ea1113bc574c5b5a61828e67fbd0e506f Fixed by: 99decb0a65227aac7b072f9e1751b75ac50a62a5 Fixed by: 223167124cf5c056c12d7c174307e490aa5fd2b3 Fixed by: 0a9c2082e65579ab814fce701e58f91a71a73c11 Branch: v4.7-maint Broken by: 85d45ff05db4a41ac3678ee0d4457b6b3323597e Broken by: ce7ae55ea1113bc574c5b5a61828e67fbd0e506f Fixed by: dfd22fc50f8f268b9810d2ef21adada021f740eb Fixed by: 54005b84b0165b62b2ef88c7df229bddbaa29e76 Fixed by: 030fdf57255f97289a407529194bf26c77548acb Branch: v4.8-maint Broken by: 85d45ff05db4a41ac3678ee0d4457b6b3323597e Broken by: ce7ae55ea1113bc574c5b5a61828e67fbd0e506f Fixed by: 4369e90f8cacb24b55a22321923954874c14b44b Fixed by: 257c5589fe5138fdb36d434162b97599cc470f9b Fixed by: 5c3dcd0dd416f28520ce3a8fd33222b01c5a33a1 Branch: v4.9-maint Broken by: 85d45ff05db4a41ac3678ee0d4457b6b3323597e Broken by: ce7ae55ea1113bc574c5b5a61828e67fbd0e506f Fixed by: b0f788c2d3d9930015258a7df95dde80a498e657 Fixed by: ea014c9fcf19539c75a7cb6926b14858426746a7 Fixed by: a474f18dceed61d562508980999e5f2d7445d683 Branch: v4.10-maint Broken by: 85d45ff05db4a41ac3678ee0d4457b6b3323597e Broken by: ce7ae55ea1113bc574c5b5a61828e67fbd0e506f Fixed by: 8d12118171a250150f2cb16448c49271a1dcb077 Fixed by: a712f01682078f48d3c258bff8cd523ab9100b0d Fixed by: f8d8a7a182c0854fa50d3976077b3a3d8de8980f Branch: v5.0-maint Broken by: 85d45ff05db4a41ac3678ee0d4457b6b3323597e Broken by: ce7ae55ea1113bc574c5b5a61828e67fbd0e506f Fixed by: 78a00c539d271a250c62260bbf2c2594714b7e9b Fixed by: 5aa8b8d1b118f52bb2209c87482824b3ffac74c2 Fixed by: be311e1ba9b7ac7f17a0f3d1a34496de50a7b914 Branch: v5.1-maint Broken by: 85d45ff05db4a41ac3678ee0d4457b6b3323597e Broken by: ce7ae55ea1113bc574c5b5a61828e67fbd0e506f Fixed by: 44a0bcdb107eb7ac251f9aa5a316f4c161f43542 Fixed by: 771a7f2fa86a736770c3470f2a0fccd60cce3e9f Fixed by: 4aa6ce7dad1a0b66afd32f02fa17319762bb12b1 Branch: v5.2-maint Broken by: 85d45ff05db4a41ac3678ee0d4457b6b3323597e Broken by: ce7ae55ea1113bc574c5b5a61828e67fbd0e506f Fixed by: de48bfbe09a00d743eef4b3a7b03b1af0e26fa9d Fixed by: 16a5284eb1be6b0c00e277b604e62f394b426fbc Fixed by: c909c8e185a14bbab82564f219c0bb492a81ca43 Branch: v5.3-maint Broken by: 85d45ff05db4a41ac3678ee0d4457b6b3323597e Broken by: ce7ae55ea1113bc574c5b5a61828e67fbd0e506f Fixed by: fd48a871a9dcdb8b8b1eb39612e5df870a7e2c3c Fixed by: 8c2c611df31d3b37f149385e4597c47300ae1489 Fixed by: a968b3103c503db8a9fb6c9d64f0dd49d3b6f2a3 Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|

1 0

[Libvirt-announce] RElease of libvirt-5.3.0
by Daniel Veillard 04 May '19

04 May '19

A bit late, sorry I was in vacations, but the release is now tagged in git and I pushed the signed tarball and rpms to the normal place: https://libvirt.org/sources/ Please note that following discussion on last release the FTP server will soon be shutdown. I also pushed the related libvirt-python release that you can find in git and at https://libvirt.org/sources/python/ This is a balanced release, one thing to note is the removal of the support for the old 4.x VirtualBox releases New feature: - qemu: Add support for setting the emulator scheduler parameters I/O threads and vCPU threads already support setting schedulers, but until now it was impossible to do so for the main QEMU thread (emulator thread in the libvirt naming). This is, however, requested for some very specific scenarios, for example when vCPU threads are running at such priority that could starve the main thread. Removed feature: - vbox: Drop support for VirtualBox 4.x releases Support for all the 4.x releases was ended by VirtualBox maintainers in December 2015. Therefore, libvirt support for these releases is dropped. Improvements: - qemu: Use PCI by default for RISC-V guests PCI support for RISC-V guests was already available in libvirt 5.1.0, but it required the user to opt-in by manually assigning PCI addresses: with this release, RISC-V guests will use PCI automatically when running against a recent enough (4.0.0+) QEMU release. - qemu: Advertise firmware autoselection in domain capabilities The firmware autoselection feature is now exposed in domain capabilities and management applications can query for accepted values, i.e. values that are accepted and for which libvirt found firmware descriptor files. Firmware Secure Boot support is also advertised. - Drop YAJL 1 support YAJL 2 is widely adopted and maintaining side by side support for two versions is unnecessary. Bug fixes: - rpc: cleanup in virNetTLSContextNew Failed new gnutls context allocations in virNetTLSContextNew function results in double free and segfault. Occasional memory leaks may also occur. - virsh: various completers fixes There were some possible crashers, memory leaks, etc. which are now fixed. - qemu: Make hugepages work with memfd backend Due to a bug in command line generation libvirt did not honor hugepages setting with memfd backend. - Enforce ACL write permission for getting guest time & hostname Getting the guest time and hostname both require use of guest agent commands. These must not be allowed for read-only users, so the permissions check must validate "write" permission not "read". Thanks everybody for your help bringing this release up, Daniel -- Daniel Veillard | Red Hat Developers Tools http://developer.redhat.com/ veillard(a)redhat.com | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | virtualization library http://libvirt.org/

1 0

[Libvirt-announce] Entering freeze for libvirt-5.3.0
by Daniel Veillard 30 Apr '19

30 Apr '19

One day late but RC1 is tagged in git, and I pushed the signed tarball and rpms to the new usual place, it's the same dir, same content, just though https https://libvirt.org/sources/ Looks fine in my minimal testing, but give it a try especially on diverse system and architecture. The fact that https://ci.centos.org/view/libvirt/ is all green except for one edge case is also a good indication. So assuming everything goes as planned, I think RC2 should be cut on Tuesday and we can plan for a May 2nd final release is everything goes well. Give it a good testing, thanks ! Daniel -- Daniel Veillard | Red Hat Developers Tools http://developer.redhat.com/ veillard(a)redhat.com | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | virtualization library http://libvirt.org/

1 1

[Libvirt-announce] Release of libvirt-5.2.0
by Daniel Veillard 03 Apr '19

03 Apr '19

It's out, a bit late but the signed tarball and rpms are at the usual place and it's tagged in git: ftp://libvirt.org/libvirt/ I also pushed the python bindings, with only a single patch since 5.1.0 at: ftp://libvirt.org/libvirt/python/ Note that it's a release with rather large changes, new features and removal of some deprecated init scripts, and as usual a large amount of improvement and bug fixes: New features: - Add Storage Pool Capabilities output Add support to list an enumerated list of supported Storage Pools via the virConnectGetCapabilities API when connected via a Storage Driver. Add support to get a more detailed list XML output Storage Pool Capabilities vis the virConnectGetStoragePoolCapabilites API. - qemu: Support virtio-{non-}transitional device models virtio-transitional and virtio-non-transitional model values were added to the QEMU driver for the following devices: disk, interface, filesystem, rng, vsock, memballoon, controller type scsi, controller type virtio-serial, input bus virtio type passthrough, hostdev type scsi_host. These new models can be used to give fine grained control over what virtio device version is presented to the guest. - qemu: Enable firmware autoselection Libvirt allows users to provide loader path for some time now. However, this puts some burden on users because they need to know what firmware meets their requirements. Now that QEMU ships firmware description files this burden can be moved onto libvirt. It is as easy as setting the firmware attribute in the os element (accepted values are bios and efi). Moreover, libvirt automatically enables domain features needed for firmware it chooses. - snapshots: Add support for topological listings A new flag VIR_DOMAIN_SNAPSHOT_LIST_TOPOLOGICAL is available for the various snapshot listing APIs such as virDomainListAllSnapshots(). For drivers that support the flag, the listed snapshots are guaranteed to be sorted such that parents occur before children. - Xen: Add support for max grant frames setting Add support for Xen's max_grant_frames setting by adding a new xenbus controller type with a maxGrantFrames attribute. E.g. <controller type='xenbus' maxGrantFrames='64'/> - qemu: Add support for parallel migration With QEMU 4.0.0 libvirt can enable parallel migration which causes the memory pages to be processed in parallel by several threads and sent to the destination host using several connections at the same time. This may increase migration speed in case a single thread is unable to saturate the network link. Removed features: - Drop support for Upstart and "Red Hat" init scripts Not a single one of the platforms we target still uses Upstart, and the Upstart project itself has been abandoned for several years now; the same is true for the "Red Hat" (really System V) init scripts, since RHEL 7 and later releases use systemd. Improvements: - Report class information for PCI node device capability. - Split setup of IPv4 and IPv6 top level chain The requirement resulting from private chains improvement done in v5.1.0 was refined so that only tables from corresponding IP version are required. This means that if a network doesn't have IPv6 enabled then those tables are not required. - Don't default to building the QEMU driver Historically, the QEMU driver has been special in that it was enabled by default, with the option to explicitly opt-out of it; starting now, we're enabling it opportunistically if we detect that all requirements are available, just like we do with other drivers. Bug fixes: - virt-host-validate: Fix IOMMU check on s390x - qemu: Allow creating pSeries guests with graphics and no USB mouse It's now possible to prevent libvirt from automatically adding a USB mouse to pSeries guests by including a USB tablet in the input XML: doing so is desiderable as using a tablet results in a much better user experience when working with GUIs. - qemu: Set $HOME and XGD variables for qemu:///system guests This avoids files being accidentally created under / or the guests not being able to start because they lack the necessary permissions to write to that location. Thanks everybody for your contributions for this release, be it with bug reports, patches, reviews, documentation, etc... Enjoy the release ! Daniel -- Daniel Veillard | Red Hat Developers Tools http://developer.redhat.com/ veillard(a)redhat.com | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | virtualization library http://libvirt.org/

2 2

[Libvirt-announce] Entering freeze for libvirt-5.2.0
by Daniel Veillard 31 Mar '19

31 Mar '19

I'm a bit late but the Candidate Release 1 is tagged in git and I have pushed the signed tarball and rpms to the usual place: ftp://libvirt.org/libvirt/ This seems to be working in my limited testing, the CI is mostly green https://ci.centos.org/view/libvirt/ except for a few side things, so with a bit of luck that will work well. I may push the RC2 saturday morning, and then if everything looks good we can have the release on Tuesday. In the meantime, give it a try, especially on different platforms or OSes, thanks, Daniel -- Daniel Veillard | Red Hat Developers Tools http://developer.redhat.com/ veillard(a)redhat.com | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | virtualization library http://libvirt.org/

1 1

[Libvirt-announce] Release of libvirt-5.1.0
by Daniel Veillard 04 Mar '19

04 Mar '19

A few days late after some travel, but everything is now pushed, freeze is over ! The release is tagged in git, signed tarball and rpms are available from the usual place: ftp://libvirt.org/libvirt/ I also pushed the Python bindings release at: ftp://libvirt.org/libvirt/python/ This is a rather large release, with a fair amount of new features, improvement and bug fixes: New features: - bhyve: Add support for additional command-line arguments The bhyve driver now supports passing additional command-line arguments to the bhyve process using the new <bhyve:commandline> element in domain configuration. - network: Support setting a firewalld "zone" for virtual network bridges All libvirt virtual networks with bridges managed by libvirt (i.e. those with forward mode of "nat", "route", "open", or no forward mode) will now be placed in a special firewalld zone called "libvirt" by default. The zone of any network bridge can be changed using the zone attribute of the network's bridge element. - bhyve: Support for ignoring unknown MSRs reads and writes A new <features> element <msrs unknown='ignore'/> was introduced and the bhyve driver supports it to control unknown Model Specific Registers (MSRs) reads and writes. - qemu: Add support for encrypted VNC TLS keys Use the password stored in the secret driver under the uuid specified by the vnc_tls_x509_secret_uuid option in qemu.conf. - Add storage pool namespace options Allow for adjustment of RBD configuration options via Storage Pool XML Namespace adjustments. - qemu: Add support for setting post-copy migration bandwidth Users can now limit the bandwidth of post-copy migration, e.g. via virsh migrate --postcopy-bandwidth. Improvements: - Create private chains for virtual network firewall rules Historically firewall rules for virtual networks were added straight into the base chains. This works but has a number of bugs and design limitations. To address them, libvirt now puts firewall rules into its own chains. - Detect CEPH and GPFS as shared FS When starting a migration libvirt performs some sanity checks to make sure domain will be able to run on the destination. One of the requirements is that the disk has to either be migrated too or be accessible from a network filesystem. CEPH and GPFS weren't detected as a network filesystem. - Advertise network MTU via DHCP when specified If network MTU is set and the network has DHCP enabled, advertise the MTU in DHCP transaction too so that clients can adjust their link accordingly. - qemu: Allocate memory at the configured NUMA nodes from start Libvirt used to just start QEMU, let it allocate memory for the guest, and then use CGroups to move the memory to configured NUMA nodes. This is suboptimal as huge chunks of memory have to be moved. Moreover, this relies on ability to move memory later which is not always true. A change was made to set process affinity correctly from the start so that memory is allocated on the configured nodes from the beginning. - Support for newer Wireshark Adapt libvirt to use the more recent release requiring a source build configuration of libvirt --with-wireshark to upgrade to the more recent version. - Batch mode virsh and virt-admin parsing improvements When parsing a single-argument command_string in batch mode, virsh and virt-admin now permit newlines in addition to semicolons for splitting commands, and backslash-newline for splitting long lines, to be more like shell parsing. Bug fixes: - qemu: Use CAP_DAC_OVERRIDE during QEMU capabilities probing By default, libvirt runs the QEMU process as qemu:qemu which could cause issues during probing as some features like AMD SEV might be inaccessible to QEMU because of file system permissions. Therefore, CAP_DAC_OVERRIDE is granted to overcome these for the purposes of probing. - storage: Add default mount options for fs/netfs storage pools Altered the command line generation for fs/netfs storage pools to add some default options. For Linux based systems, the options added are "nodev, nosuid, noexec". For FreeBSD based systems, the options added are "nosuid, noexec". - qemu: Allow use of PCI for RISC-V guests This works with QEMU 4.0.0+ only and is opt-in at the moment, since it requires users to manually assign PCI addresses, but is otherwise fully functional. - network: Fix virtual networks on systems using firewalld+nftables Because of the transitional state of firewalld's new support for nftables, not all iptables features required by libvirt are yet available, so libvirt must continue to use iptables for its own packet filtering rules even when the firewalld backend is set to use nftables. However, due to the way iptables support is implemented in kernels using nftables (iptables rules are converted to nftables rules and processed in a separate hook from the native nftables rules), guest networking was broken on hosts with firewalld configured to use nftables as the backend. This has been fixed by putting libvirt-managed bridges in their own firewalld zone, so that guest traffic can be forwarded beyond the host and host services can be exposed to guests on the virtual network without opening up those same services to the rest of the physical network. This means that host access from virtual machines is no longer controlled by the firewalld default zone (usually "public"), but rather by the new firewalld zone called "libvirt" (unless configured otherwise using the new zone attribute of the network bridge element). - qemu: Fix i6300esb watchdog hotplug on Q35 Ensure that libvirt allocates a PCI address for the device so that QEMU did not default to an address that would not allow for device hotplug. - lxc: Don't reboot host on virDomainReboot If the container is really a simple one (init is just bash and the whole root is passed through) then virDomainReboot and virDomainShutdown would reboot or shutdown the host. The solution is to use different method to reboot or shutdown the container in that case (e.g. signal). - rpc: Various stream fixes One particular race was fixed, one locking problem and error reporting from streams was made better. - qemu: Fix guestfwd hotplug/hotunplug Fixed the generation of the guestfwd hotplug/unplug command sent to QEMU to match the syntax used when creating the initial command line. - qemu: Forbid CDROMs on virtio bus Attempting to create an empty virtio-blk drive or attempting to eject it results into an error. Forbid configurations where users would attempt to use CDROMs in virtio bus. - qemu: Use 'raw' for 'volume' disks without format Storage pools might want to specify format of the image when translating the volume thus libvirt can't add any default format when parsing the XML. Add an explicit format when starting the VM and format is not present neither by user specifying it nor by the storage pool translation function. - qemu: Assume 'raw' default storage format also for network storage Post parse callback adds the 'raw' type only for local files. Remote files can also have backing store (even local) so we should do this also for network backed storage. - qemu: Fix block job progress reporting and advocate for READY event In some cases QEMU can get to 100% and still not reach the synchronised phase. Initiating a pivot in that case will fail. Therefore it is strongly advised to wait for VIR_DOMAIN_BLOCK_JOB_READY event which does not suffer from this problem. - qemu: Don't format image properties for empty drive If a -drive has no image, then formatting attributes such as cache, readonly, etc. would cause errors to be reported from QEMU. This was fixed by not supplying the attributes for devices without an image. - External snapshot metadata redefinition is fixed Attempting to use VIR_DOMAIN_SNAPSHOT_CREATE_REDEFINE to reinstate the metadata describing an external snapshot created earlier for an offline domain no longer fails. Thanks everybody for your contributions to this new release, enjoy ! Daniel -- Daniel Veillard | Red Hat Developers Tools http://developer.redhat.com/ veillard(a)redhat.com | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | virtualization library http://libvirt.org/

1 0

[Libvirt-announce] Entering freeze for libvirt-5.1.0
by Daniel Veillard 28 Feb '19

28 Feb '19

As planned I just tagged it in git, and pushed the signed tarball and rpms to the usual place: ftp://libvirt.org/libvirt/ I'm travelling this week so my testing is even more limited than usual, but that seems fine with me and https://ci.centos.org/view/libvirt/ seems to be all green so I'm hopeful :-) I will push rc2 on Wednesday, and possibly GA on Friday if everything looks fine, worse case I will push it over the week-end. Please give it some testing, thanks ! Daniel -- Daniel Veillard | Red Hat Developers Tools http://developer.redhat.com/ veillard(a)redhat.com | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | virtualization library http://libvirt.org/

1 1

[Libvirt-announce] ANNOUNCE: libvirt-dbus 1.3.0 released
by Pavel Hrdina 18 Jan '19

18 Jan '19

I'm happy to announce the release of libvirt-dbus 1.3.0. libvirt-dbus wraps libvirt API to provide high-level object-oriented API better suited for dbus-based applications. You can download it here: https://libvirt.org/sources/dbus/libvirt-dbus-1.3.0.tar.xz * New features - Support for all relevant interface APIs up to libvirt 3.0.0 * Bug fixes - Storage volumes and with special characters in the name are now correctly listed * Build-system improvements - Detect flake8 automatically - Install daemon under @sbindir@ - Fix version check for dependencies Thanks everybody who contributed! Pavel

1 0

[Libvirt-announce] Release of libvirt-5.0.0
by Daniel Veillard 15 Jan '19

15 Jan '19

Hi all, as planned I just tagged the new release in git, and pushed signed tarball and rpms to the usual place: ftp://libvirt.org/libvirt/ I also pushed the python bindings, identical to 4.10 with just the versioning bump, you can find them at: ftp://libvirt.org/libvirt/python/ This release includes new features, but also remove the old apparently unused UML driver support. There is also a rather large set of improvements: New features: - Xen: Add support for openvswitch The libxl driver now supports virtual interfaces that connect to an openvswitch bridge, including interfaces with VLAN tagging and trunking configuration. - qemu: Report whether KVM nesting is available Running nested KVM guests requires specific configuration steps to be performed on the host; libvirt will now report in the host capabilities whether KVM nesting support is available. Removed features: - Drop UML driver The UML driver was unmaintained and not tested for quite some time now. Worse, there is a bug that causes it to deadlock on some very basic operations (e.g. dumping domain XML). These facts make us believe no one uses it. Improvements: - qemu: Add support for ARMv6l guests - Support more NVDIMM configuration options Introduce more configuration options. For the source element, add the 'alignsize' and 'pmem' subelements. For the target element, add the 'readonly' subelement. - cpu: Add support for "stibp" x86_64 feature Add cpu flag stibp (Single Thread Indirect Branch Predictors) to prevent indirect branch predictions from being controlled by the sibling Hyperthread. - libxl: Handle external domain destroy Historically, if a domain was destroyed using xl rather than through libvirt APIs, libvirt would not be aware of the fact and keep considering it as running. This is no longer the case. - Start selecting the first available DRI device for OpenGL operations If OpenGL support is needed (either with SPICE gl enabled or with egl-headless), libvirt is now able to pick the first available DRI device for the job. At the same time, this improvement is also a bugfix as it prevents permission-related issues with regards to our mount namespaces and the default DRI render node's permissions which would normally prevent QEMU from accessing such a device. - qemu: Add support for postcopy-requests migration statistics The virDomainJobInfo can get number page requests received from the destination host during post-copy migration. Bug fixes: - lxc: Don't forbid interfaces with type=direct Such interfaces are supported by lxc and should be allowed. - qemu: Fully clean up RNG devices on detach Some RNG device types, such as those using EGD, might need extra clean up on the host in addition to removing the guest-side device. Thanks everybody for your help toward this release, be it with patches reviews, bug description, documentation and localizations ! As a reminder, the next release is scheduled at the end of February, in the meantime, enjoy the new release ! Daniel -- Daniel Veillard | Red Hat Developers Tools http://developer.redhat.com/ veillard(a)redhat.com | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | virtualization library http://libvirt.org/

1 0