October 2023 - Announce - libvirt List Archives

ANNOUNCE: Mailing list move complete
by Daniel P. Berrangé 01 Nov '23

01 Nov '23

This is an announcement to the effect that the mailing list move is now complete. TL;DR the new list addresses are: * announce(a)lists.libvirt.org (formerly libvirt-announce(a)redhat.com) Low volume, announcements of releases and other important info * users(a)lists.libvirt.org (formerly libvirt-users(a)redhat.com) End user questions and discussions and collaboration * devel(a)lists.libvirt.org (formerly libvir-list(a)redhat.com) Patch submission for development of main project * security(a)lists.libvirt.org (formerly libvir-security(a)redhat.com) Submission of security sensitive bug reports The online archive and membership mgmt interface is https://lists.libvirt.org In my original announcement[1] I mentioned that people would need to manually re-subscribe. Due to a mixup in communications, our IT admins went ahead and migrated across the existing entire subscriber base for all lists. Thus there is NO need to re-subscribe to any of the lists. If you were doing filtering of mail, you may need to update filters for the new list ID matches. With the new list server, HyperKitty is providing the web interface. Thus if you wish to interact with the lists entire via the browser this is now possible. Note that it requires you to register for an account and set a password, even if you are already a list subscriber. If you mistakenly send to the old lists you should receive an auto-reply about the moved destinations. Note, we had some technical issues on Thursday/Friday, so if you sent mails on those two days they probably will not have reached any lists, and so you may wish to re-send them. With regards, Daniel [1] https://listman.redhat.com/archives/libvirt-announce/2023-October/000650.ht… -- |: 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 :|

2 2

libvirt-9.9.0 release candidate 2
by Jiri Denemark 30 Oct '23

30 Oct '23

I have just tagged v9.9.0-rc2 in the repository and pushed signed tarballs and source RPMs to https://download.libvirt.org/ Please give the release candidate some testing and in case you find a serious issue which should have a fix in the upcoming release, feel free to reply to this thread to make sure the issue is more visible. If you have not done so yet, please update NEWS.rst to document any significant change you made since the last release. Thanks, Jirka

1 0

ANNOUNCE: Forthcoming changes to libvirt mailing list hosting
by Daniel P. Berrangé 13 Oct '23

13 Oct '23

Hello Libvirt Community, For the last 18(!) years, libvirt community mailing lists have been kindly hosted by Red Hat Corporate IT on the redhat.com Mailman installation. In retrospect this wasn't the ideal home for community mailing lists but that decision is ancient history. Unfortunately as a consequence of infrastructure changes, the redhat.com Mailman service is scheduled to be decomissioned, and in the very near future ($low weeks) will cease to be able to send/receive mail for libvirt lists. As a result, all the libvirt mailing lists will need to move to a new Mailman installation, managed on our behalf by the Red Hat Open Source Community Infrastructure team[1], who provide services for a variety of OSS projects. It is intended that this new service will be dedicated for our community and thus located somewhere under the libvirt.org domain. It should go without saying that all existing mail archives will be migrated over to the new server. None of the historical record should be lost. It is not considered appropriate netiquette, however, to bulk-resubscribe all current list members under a new domain. Thus anyone who wants to remain on the community lists will soon be requested to take action to enroll on the new mailman service. The new service is not quite ready for use yet. This mail serves as a heads up that the changes will be coming in the next couple of weeks that will require action. A further announcement will be sent when the new mailman is ready to accept subscriptions, as well as warnings before the old lists stop accepting messages. With regards, Daniel [1] https://www.osci.io/ -- |: 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

Release of libvirt-9.8.0
by Jiri Denemark 02 Oct '23

02 Oct '23

The 9.8.0 release of both libvirt and libvirt-python is tagged and signed tarballs and source RPMs are available at https://download.libvirt.org/ https://download.libvirt.org/python/ Thanks everybody who helped with this release by sending patches, reviewing, testing, or providing feedback. Your work is greatly appreciated. * New features * network: New metadata change event The network object now has a new event ID ``VIR_NETWORK_EVENT_ID_METADATA_CHANGE`` that can be used to get notifications upon changes in any of ``<title>``, ``<description>`` or ``<metadata>``. * qemu: Add support for vDPA block devices With a new enough version of qemu, libvirt will allow you to assign vDPA block devices to a domain. This is configured with:: <disk type='vhostvdpa'> <source dev='/dev/vhost-vdpa-0'> ... * Improvements * qemu: add nbdkit backend for network disks Up until now, libvirt supported network disks (http, ftp, ssh) by passing the URL to qemu and having the appropriate qemu block drivers handle the disk I/O. However, by handling the network I/O outside of the qemu process, we get several advantages, such as reduced attack surface and improved stability of qemu. Therefore, when available, libvirt will use nbdkit as a backend for these network disks and export an NBD disk to qemu. * virnetdevopenvswitch: Propagate OVS error messages When configuring OVS interfaces/bridges libvirt used to report its own error messages instead of passing (more accurate) error messages from `ovs-vsctl`. This is now changed. * Various virtio-mem/virtio-pmem fixes Now libvirt validates more values of virtio-mem and virtio-pmem devices, e.g. overlapping memory addresses or alignment. Enjoy. Jirka

1 0