This bug is awaiting verification that the linux-mtk/5.15.0-1030.34
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the
This bug only involves a revert to LP#2032164. We are actively working
on finding a comprehensive solution to address the live migration issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Eventually, I see failures even with kernel 5.15.0-84-generic which
means there's smth else involved then commits in question, as they
shouldn't be there yet.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Folks, is there any way to revive the patch and see actual source code of the
change proposed here?
As I assume the bug was closed due to inactivity, but I'm quite ready to test
it out.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
I'm not sure if this has been really fixed in Jammy default kernel. I've
hit specifically this issue during this week while running 5.15.0-89.
Upgrading to HWE kernel or 5.19.0-50 does fix live migrations.
--
You received this bug notification because you are a member of Kernel
Packages, which
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1025.29 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp'
to
This bug is awaiting verification that the linux-gcp-tcpx/5.15.0-1002.2
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal-linux-gcp-tcpx' to 'verification-done-
This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1018.18~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal-linux-
nvidia-tegra-5.15' to
This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1005.5 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to
This bug is awaiting verification that the linux-intel-
iotg-5.15/5.15.0-1043.49~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
intel-iotg-5.15' to
This bug is awaiting verification that the linux-
bluefield/5.15.0-1027.29 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-bluefield' to
This bug is awaiting verification that the linux-raspi/5.15.0-1040.43
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy-
linux-raspi'. If
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1018.18 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
** Tags removed: verification-needed-jammy-linux-aws
verification-needed-jammy-linux-azure
** Tags added: verification-done-jammy-linux-aws
verification-done-jammy-linux-azure
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
This bug is awaiting verification that the linux-aws/5.15.0-1048.53
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-aws' to 'verification-done-jammy-
linux-aws'. If the
This bug is awaiting verification that the linux-azure/5.15.0-1050.57
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-azure' to 'verification-done-jammy-
linux-azure'. If
This bug was fixed in the package linux - 5.15.0-86.96
---
linux (5.15.0-86.96) jammy; urgency=medium
* jammy/linux: 5.15.0-86.96 -proposed tracker (LP: #2036575)
* 5.15.0-85 live migration regression (LP: #2036675)
- Revert "KVM: x86: Always enable legacy FP/SSE in allowed
FYI, we solved a similar sounding issue by clearing the PKRU bit if it
was set in the to-be-restored XSAVE blob, but not available in the
current vCPU feature flags:
https://git.proxmox.com/?p=pve-
kernel.git;a=blob;f=patches/kernel/0008-kvm-xsave-set-mask-out-PKRU-bit-
in-xfeatures-if-
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Chengen Du (chengendu)
--
You received this bug notification because you
20 matches
Mail list logo
