This also affects us in production: OpenStack (OpenStack-Ansible, Nova
31.2) with live_migration_with_native_tls = true on Ubuntu 24.04.

Package versions:

qemu-system-x86 1:8.2.2+ds-0ubuntu1.18
libgnutls30t64 3.8.3-1.1ubuntu3.6
libvirt-daemon 10.0.0-2ubuntu8.19

Several live migrations of large, busy guests (72–256 GB RAM) crashed
the source QEMU with SIGSEGV inside libgnutls, in the migration return-
path thread, a few minutes into the migration:

Signal: 11 (SEGV)
#0  libgnutls.so.30 + 0x3f8cd
#1  libgnutls.so.30 + 0x436c9
#2  qemu-system-x86_64 + 0x917bdc
#3  qemu-system-x86_64 + 0xb27995
#4  qemu_get_byte
#5  qemu_get_be16
#6  qemu-system-x86_64 + 0x6fb0ac
#7  qemu-system-x86_64 + 0xab87c9


This matches GnuTLS issue #1717 / QEMU issue #1937 (TLS 1.3 automatic rekey 
while send and recv run concurrently). In another case on the same setup, the 
destination QEMU failed with postcopy_ram_listen_thread: loadvm failed: -5 
right after the post-copy switchover, after about 54 GB had been transferred.

Because QEMU on Ubuntu is built without tls_priority, we cannot apply
the upstream-recommended workaround (disabling TLS 1.3 or AES-GCM for
QEMU via a priority string). Our libvirt 10.0.0 also lacks
migrate_tls_priority. Our only options right now are disabling post-copy
or disabling native TLS for migration.

Two things would help:

Building qemu with --tls-priority=@QEMU,SYSTEM (as Fedora/RHEL do), so 
administrators can override the TLS profile via /etc/gnutls/config.
Backporting the GnuTLS fix “key_update: rework the rekeying logic” (gnutls MR 
!1990, included in gnutls 3.8.11) to noble’s gnutls28. RHEL has backported it 
to its 3.8.3 base (gnutls-3.8.3-6.2, RHEL-107498).

Should a separate bug be filed against gnutls28 for (2), or can it be
tracked here?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2106021

Title:
  Not possible to configure TLS profile for QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2106021/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to