Activity log for bug #2019766

Date Who What changed Old value New value Message
2023-05-15 22:32:03 dann frazier bug added bug
2023-05-16 02:48:32 dann frazier description [Impact] KVM-accelerated virtual machines sometimes fail to start on ARM. [Test Case] On an arm64 system, create and destroy KVM-accelerated virtual machines in a loop. virt-install --name vm3 --numatune 0,mode=preferred --vcpus vcpus=8,maxvcpus=8,cpuset=0-74 --memory 3072 --import --noautoconsole --os-variant name=ubuntu22.04 --disk path=/var/lib/libvirt/images/vm3.qcow2 --boot loader=/usr/share/AAVMF/AAVMF_CODE.fd,loader_ro=yes,loader_type=pflash When it fails you'll get an error message like: Error is: ERROR internal error: process exited while connecting to monitor: 2023-04-27T20:21:01.686783Z qemu-system-aarch64: failed to create scratch VCPU with SVE enabled [Fix] https://gitlab.com/qemu-project/qemu/-/commit/bbde13cd14ad4eec18529ce0bf5876058464e124 [What Could Go Wrong] [Impact] KVM-accelerated virtual machines sometimes fail to start on ARM. [Test Case] On an arm64 system, create and destroy KVM-accelerated virtual machines in a loop. virt-install --name vm3 --numatune 0,mode=preferred --vcpus vcpus=8,maxvcpus=8,cpuset=0-74 --memory 3072 --import --noautoconsole --os-variant name=ubuntu22.04 --disk path=/var/lib/libvirt/images/vm3.qcow2 --boot loader=/usr/share/AAVMF/AAVMF_CODE.fd,loader_ro=yes,loader_type=pflash When it fails you'll get an error message like: Error is: ERROR internal error: process exited while connecting to monitor: 2023-04-27T20:21:01.686783Z qemu-system-aarch64: failed to create scratch VCPU with SVE enabled [Fix] https://gitlab.com/qemu-project/qemu/-/commit/bbde13cd14ad4eec18529ce0bf5876058464e124 [What Could Go Wrong] There may exist conditions that could cause the added loop to block for a long time, burning CPU. However, the fix uses a seemingly common pattern.
2023-05-16 06:26:39 Christian Ehrhardt  nominated for series Ubuntu Kinetic
2023-05-16 06:26:39 Christian Ehrhardt  bug task added qemu (Ubuntu Kinetic)
2023-05-16 06:26:39 Christian Ehrhardt  nominated for series Ubuntu Jammy
2023-05-16 06:26:39 Christian Ehrhardt  bug task added qemu (Ubuntu Jammy)
2023-05-16 06:26:45 Christian Ehrhardt  qemu (Ubuntu): status New Fix Released
2023-05-16 06:28:06 Christian Ehrhardt  bug added subscriber Ubuntu Server
2023-05-16 06:28:14 Christian Ehrhardt  tags server-todo
2023-05-16 14:54:28 dann frazier qemu (Ubuntu Jammy): assignee dann frazier (dannf)
2023-05-16 14:54:31 dann frazier qemu (Ubuntu Kinetic): assignee dann frazier (dannf)
2023-05-16 14:54:38 dann frazier qemu (Ubuntu Kinetic): status New In Progress
2023-05-16 14:54:43 dann frazier qemu (Ubuntu Jammy): status New In Progress
2023-05-16 21:36:58 dann frazier attachment added test.sh https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2019766/+attachment/5673389/+files/test.sh
2023-05-16 21:39:05 dann frazier description [Impact] KVM-accelerated virtual machines sometimes fail to start on ARM. [Test Case] On an arm64 system, create and destroy KVM-accelerated virtual machines in a loop. virt-install --name vm3 --numatune 0,mode=preferred --vcpus vcpus=8,maxvcpus=8,cpuset=0-74 --memory 3072 --import --noautoconsole --os-variant name=ubuntu22.04 --disk path=/var/lib/libvirt/images/vm3.qcow2 --boot loader=/usr/share/AAVMF/AAVMF_CODE.fd,loader_ro=yes,loader_type=pflash When it fails you'll get an error message like: Error is: ERROR internal error: process exited while connecting to monitor: 2023-04-27T20:21:01.686783Z qemu-system-aarch64: failed to create scratch VCPU with SVE enabled [Fix] https://gitlab.com/qemu-project/qemu/-/commit/bbde13cd14ad4eec18529ce0bf5876058464e124 [What Could Go Wrong] There may exist conditions that could cause the added loop to block for a long time, burning CPU. However, the fix uses a seemingly common pattern. [Impact] KVM-accelerated virtual machines sometimes fail to start on ARM. [Test Case] My reproducer is to run 6 parallel VM create/destroy loop - using the attached test.sh script. When this issue is hit, a VM will fail with the following in its log: 2023-05-16T21:07:37.300791Z qemu-system-aarch64: Failed to retrieve host CPU features 2023-05-16 21:07:37.466+0000: shutting down, reason=failed [Fix] https://gitlab.com/qemu-project/qemu/-/commit/bbde13cd14ad4eec18529ce0bf5876058464e124 [What Could Go Wrong] There may exist conditions that could cause the added loop to block for a long time, burning CPU. However, the fix uses a seemingly common pattern.
2023-05-18 20:46:50 Andreas Hasenack qemu (Ubuntu Kinetic): status In Progress Fix Committed
2023-05-18 20:46:51 Andreas Hasenack bug added subscriber Ubuntu Stable Release Updates Team
2023-05-18 20:46:53 Andreas Hasenack bug added subscriber SRU Verification
2023-05-18 20:46:57 Andreas Hasenack tags server-todo server-todo verification-needed verification-needed-kinetic
2023-05-18 20:47:29 Andreas Hasenack qemu (Ubuntu Jammy): status In Progress Fix Committed
2023-05-18 20:47:34 Andreas Hasenack tags server-todo verification-needed verification-needed-kinetic server-todo verification-needed verification-needed-jammy verification-needed-kinetic
2023-05-19 00:31:38 dann frazier tags server-todo verification-needed verification-needed-jammy verification-needed-kinetic server-todo verification-done verification-done-jammy verification-done-kinetic
2023-06-05 09:18:17 Launchpad Janitor qemu (Ubuntu Kinetic): status Fix Committed Fix Released
2023-06-05 09:18:22 Łukasz Zemczak removed subscriber Ubuntu Stable Release Updates Team
2023-06-05 09:30:55 Launchpad Janitor qemu (Ubuntu Jammy): status Fix Committed Fix Released