[Bug 1994002] Re: [SRU] migration was active, but no RAM info was set

[Corey Bryant]

This bug was fixed in the package qemu - 1:4.2-3ubuntu6.27~cloud0
---------------

 qemu (1:4.2-3ubuntu6.27~cloud0) bionic-ussuri; urgency=medium
 .
   * New update for the Ubuntu Cloud Archive.
 .
 qemu (1:4.2-3ubuntu6.27) focal-security; urgency=medium
 .
   * SECURITY UPDATE: user-after-free issue
     - debian/patches/CVE-2022-1050.patch: Protect against buggy or
       malicious guest driver
     - CVE-2022-1050
   * SECURITY UPDATE: Out-of-bounds read
     - debian/patches/CVE-2022-4144-*.patch: Have qxl_log_command Return
       early if no log_cmd handler; Document qxl_phys2virt(); Pass requested
       buffer size to qxl_phys2virt(); Avoid buffer overrun in qxl_phys2virt;
       Assert memory slot fits in preallocated MemoryRegion
     - CVE-2022-4144
   * SECURITY UPDATE: reentrancy problem
     - debian/patches/CVE-2023-0330.patch: Fix reentrancy issues in the LSI
       controller
     - CVE-2023-0330
 .
 qemu (1:4.2-3ubuntu6.26) focal; urgency=medium
 .
   * d/p/u/lp-1999885-s390x-tod-kvm-don-t-save-restore-the-TOD-in-PV-guest.patch:
     avoid timer issues in s390x secure execution guests (LP: #1999885)
 .
 qemu (1:4.2-3ubuntu6.25) focal; urgency=medium
 .
   [ Brett Milford ]
   * d/p/u/lp1994002-migration-Read-state-once.patch: Fix for libvirt
     error 'migration was active, but no RAM info was set' (LP: #1994002)
 .
   [ Mauricio Faria de Oliveira ]
   * d/p/u/lp2009048-vfio_map_dma_einval_amd_iommu_1tb.patch: Add hint
     to VFIO_MAP_DMA error on AMD IOMMU for VMs with ~1TB+ RAM (LP: #2009048)


** Changed in: cloud-archive/ussuri
       Status: Fix Committed => Fix Released

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

Title:
  [SRU] migration was active, but no RAM info was set

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive ussuri series:
  Fix Released
Status in qemu package in Ubuntu:
  Fix Released
Status in qemu source package in Bionic:
  Fix Released
Status in qemu source package in Focal:
  Fix Released
Status in qemu source package in Jammy:
  Fix Released
Status in qemu source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

   * While live-migrating many instances concurrently, libvirt sometimes
  return `internal error: migration was active, but no RAM info was
  set:`

   * Effects of this bug are mostly observed in large scale clusters
  with a lot of live migration activity.

   * Has second order effects for consumers of migration monitor such as
  libvirt and openstack.

  [Test Case]

  Synthetic reproducer with GDB in comment #21.

  Steps to Reproduce:
  1. live evacuate a compute
  2. live migration of one or more instances fails with the above error

  N.B Due to the nature of this bug it is difficult consistently reproduce.
  In an environment where it has been observed it is estimated to occur approximately 1/1000 migrations.

  [Where problems could occur]
   * In the event of a regression the migration monitor may report an inconsistent state.

  [Original Bug Description]

  While live-migrating many instances concurrently, libvirt sometimes return internal error: migration was active, but no RAM info was set:
  ~~~
  2022-03-30 06:08:37.197 7 WARNING nova.virt.libvirt.driver [req-5c3296cf-88ee-4af6-ae6a-ddba99935e23 - - - - -] [instance: af339c99-1182-4489-b15c-21e52f50f724] Error monitoring migration: internal error: migration was active, but no RAM info was set: libvirt.libvirtError: internal error: migration was active, but no RAM info was set
  ~~~

  From upstream bug: https://bugzilla.redhat.com/show_bug.cgi?id=2074205

  [Other Information]
  Related bug: https://bugs.launchpad.net/nova/+bug/1982284

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1994002/+subscriptions