Hi Christian and Lukas,
For qemu, I can confirm that the patch works as expected:
# qemu-system-x86_64 -cpu ? | grep Milan
x86 EPYC-Milan(alias configured by machine type)
x86 EPYC-Milan-v1 AMD EPYC-Milan Processor
x86 EPYC-Milan-v2 AMD EPYC-Milan-v2 Processor
Since t
Thank you for looking into this.
If you are planning to do a SRU for this and the missing Genoa model ,
please consider the whole patch series:
https://mail.gnu.org/archive/html/qemu-devel/2023-05/msg01202.html
Since you have applied the patch with the updated cache info, you can also
cherry pi
It looks like this bug is related to leaking of the PKRU bit.
Applying the patch from Proxmox mentioned in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036675
resolves the issue
** Summary changed:
- 5.15.0-76: Qemu live migration causes VMs to crash but works with HWE kernel
+ 5.15.0-7
Hi Juul,
these two flags are only present when SVM is enabled (which is unfortunately
default in Ubuntu).
We worked around this issue by modifying the target domain XML in live
migration to disable both flags if they are not present on the source side
(e.g. host running with older kernel).
I am
On focal (5.4.0-56-generic) we are starting to see massive file system
corruptions on systems updated to this kernel version.
These systems are using LVM with discards and thin provisioning on 6 or 8 NVMe
drives in a RAID10 near configuration. We are currently downgrading all systems
back to 5.4
Public bug reported:
While I have found previous reports of this check failing, they are all
resolved years ago.
So I guess this is something for upstream.
device-mapper: btree spine: node_check failed: csum 544691913 != wanted
1983069109
[ cut here ]
kernel BUG at drive
It seems one of the patches also introduced a regression:
* lp-1887490-cpu_map-Add-missing-AMD-SVM-features.patch
adds various SVM-related flags. Specifically npt and nrip-save are now expected
to be present by default as shown in the updated testdata.
This however breaks migration from instances
Same tests as above. Still working as intended
** Tags removed: patch verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Well, for me it's more or less a noop because we have been running a
version with these patches for some time now. But nevertheless I haven't
encountered any problems using your build/patch series. Host
capabilities are correctly detected as EPYC-Rome and I can (still) start
an instance with the EP
Note the fixup patch removing monitor flag:
https://gitlab.com/libvirt/libvirt/-/commit/3bf6f9fe22dfbd3c1dcc614b31f2f4fe8b71a2f2
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1887490
Tit
The new qemu version works as expected together with 5.4.0-49 kernel
required for xsaves
# grep -e 'model name' -e 'flags' /proc/cpuinfo
model name : AMD EPYC-Rome Processor
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush mmx fxsr sse sse2 h
Thanks. It does not look like the "regression" preventing proposed
migration is caused by the qemu changes.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1887490
Title:
Add/Backport EPY
The second one is: https://bugs.launchpad.net/qemu/+bug/1849644
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1887490
Title:
Add/Backport EPYC-v3 and EPYC-Rome CPU model
Status in libv
Actually no. It builds and does not have any downsides, but does not
resolve the issue. Sorry for that. When I looked at the history of
cpu_map and this patch, I did not see that it would require further
patches to actually make it work.
So that would leave it at these four patches:
Add-pschange-m
Thanks for the update. It looks like your libvirt build fails.
Most likely due to the following patch missing:
https://github.com/libvirt/libvirt/commit/58691208e2063285d981a620873d48ddf8df8be5
That patch adds the CooperLake test data (wrongly as CascadeLake-
Server), which is later fixed in
ht
With the 5.4.0-49 from focal-proposed the xsaves flag can now be passed
into instances.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1887490
Title:
Add/Backport EPYC-v3 and EPYC-Rome C
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1887490
Title:
Add/Backport EPYC-v3 and EPYC-Rome CPU mod
Is there anything I can do, regarding the backport of 52297436199d into
focal kernel?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1887490
Title:
Add/Backport EPYC-v3 and EPYC-Rome CPU
Plain qemu with the EPYC-Rome model works without any problems. I
already get xsave, xsaveopt, xsavec and xsaveerptr with the current
focal kernel, which also means that gcc finally uses znver1 (for v3) and
znver2 (for Rome) optimizations.
Libvirt would require cherrypicking a number of commits to
fix was included in 4.4.0-177.207 (xenial), 4.15.0-92.93 (bionic),
5.3.0-46.38 (eoan), 5.4.0-15.18 (focal)
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubu
Patch has been backported to all stable kernel releases, e.g. 4.19:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.19.y&id=1fac9f574cd2536abcdd645ee23d35c0e819d7ec
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
The patch is merged upstream and will be in 5.6.
https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=dm-5.6&id=4feaef830de7ffdd8352e1fe14ad3bf13c9688f8
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/md?id=e9f8ca0ae7b7bc9a032b42992
Patch posted at
https://www.redhat.com/archives/dm-devel/2020-January/msg00021.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1777398
Title:
dm thin block allocation failure
Status
Unfortunately still present in mainline 5.0.13 kernel:
[ cut here ]
kernel BUG at drivers/md/persistent-data/dm-space-map-disk.c:178!
invalid opcode: [#1] SMP PTI
CPU: 5 PID: 1675751 Comm: kworker/u128:1 Not tainted 5.0.13-050013-generic
#201905051330
Hardware name: Q
Still present in 4.15.0-47-generic even though a number of dm/thin fixes
have been backported
kernel: [1120717.622665] Modules linked in: cpuid xt_CHECKSUM xt_nat
iptable_nat nf_nat_ipv4 dm_snapshot veth dummy bridge nf_conntrack_ipv6
nf_defrag_ipv6 ip6table_filter ip6_tables xt_CT iptable_raw i
Currently testing 5.0.10 as we think the issue is related to thin trying
to reallocate a discarded block not working correctly
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/md?id=cffd425b90147296c627dfb13f7ea8f361d962b2
** Changed in: linux (Ubuntu)
Sta
This issue is still present. Possibly fixed by upstream commit
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/md?id=a685557fbbc3122ed11e8ad3fa63a11ebc5de8c3
https://www.redhat.com/archives/dm-devel/2018-April/msg00022.html
kernel: [8860597.921484] kernel BUG at
proposed kernel for trusty still resolves this like test-kernel from #7
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1788563
Title:
L1TF mitigation not effective in some CPU and RAM co
still unresolved in 4.19rc3
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1778475
Title:
i40e: restore workaround for removing default MAC filter
Status in linux package in Ubuntu:
I
kernel from #7 resolves this on trusty as well (according to sysfs)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1788563
Title:
L1TF mitigation not effective in some CPU and RAM combin
This happens pretty much on all Ubuntu kernels with the initial L1TF
implementation, so xenial, bionic and cosmic are also affected.
https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.154
https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.18.6
--
You received this bug notification
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1789834
Title:
off-by-one bug in L1TF mitigation
Status in linux package in
Public bug reported:
due to an off-by-one bug in the L1TF patch, the "rare" case of systems still
vulnerable
is more frequent.
This typically happens on Nehalem+ destop/entry-level server systems
with 32G memory installed.
Originally this was reported in OpenSUSE, but I can confirm this is also
If I'm not mistaken, the fix has been released with the latest kernel
update that was pushed for the L1TF issue. So this bug should be "fix
released"
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1778486
Title:
x86/kvm: fix LAPIC timer drift when gues
Thanks Joseph.
I tested the kernel with OpenBSD and FreeBSD virtual machines and this
patch seems to fix the timing issues.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1778486
Title:
Apparently not, but this was the only mentioning of this bug and the it
can be reproduced just the same way (bonding + vlan)
But after trying the mainline 4.18rc2 kernel, the bug is still present
their. So it needs to be fixed upstream first (again).
For reference:
# uname -a
Linux hostname 4.18
Public bug reported:
OpenBSD guests encounter timing issues when running under bionic kernel.
This issue is actually present since 4.10 and is fixed by:
https://patchwork.kernel.org/patch/10411125/
See also
https://www.spinics.net/lists/kvm/msg161311.html
** Affects: linux (Ubuntu)
Impor
Public bug reported:
Ubuntu Bionic kernel (4.15.0-23) lacks upstream patch for i40e which
results in forced promiscous mode when adding a vlan.
[ 10.847381] i40e :3d:00.0: Error I40E_AQ_RC_EINVAL adding RX filters on
PF, promiscuous mode forced on
Steps to reproduce and patch here:
http
Hi Joseph,
sure, but running an rc- kernel is not ideal for production systems, so I can
only give this limited exposure on a few canary systems.
I hope we can find a way to deterministically trigger this, to confirm a fix.
--
You received this bug notification because you are a member of Kern
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1777398
Title:
dm thin block allocation failure
Status in linux packa
Also present in HWE kernel 4.15.0-23-generic #25~16.04.1-Ubuntu for
xenial
kernel: [450194.803852] [ cut here ]
kernel: [450194.803855] kernel BUG at
/build/linux-hwe-edge-ew4Cb4/linux-hwe-edge-4.15.0/drivers/md/persistent-data/dm-space-map-disk.c:178!
kernel: [450194.803
Public bug reported:
When using the bionic kernel (hwe-edge) on xenial we randomly trigger a
kernel bug when creating or querying a thin provisioned lvm volume.
kernel: [146487.421278] [ cut here ]
kernel: [146487.421281] kernel BUG at
/build/linux-hwe-edge-eBL7So/linux-
fix confirmed spec-ctrl cpu flag is now visible inside kvm guest
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1744244
Title:
linux: 4.4.0-112.135 -proposed tracker
Status in Kernel SR
Since upgrading to 16.04 I have not seen this problem again. So I would
consider this issue resolved.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The -31 Kernel from Stefan's PPA with the patch has been running stable
for 2 weeks and the previous version based on -29 for 3 weeks. So if
that patch will make its way into Ubuntu kernel via the 4.4.16 stable
series update, the bug can be closed from my side at that point
--
You received this b
But that is not the -31 from the PPA. Could you please try the kernel
from the PPA that Stefan has posted?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1568729
Title:
divide error: 000
I have been running the -29 kernel from
http://people.canonical.com/~smb/lp1568729/ for about two weeks now, so
far without triggering the bug. With the kernel from Tim, the bug could
still be triggered. So it seems there were different patches.
I'll try the -33 kernel from ppa as well, to see if
Unfortunately, the issue is still present.
Apr 14 00:34:43 cnode17 kernel: [204922.475156] divide error: [#1] SMP
Apr 14 00:34:43 cnode17 kernel: [204922.475185] Modules linked in: cpuid arc4
md4 nls_utf8 cifs vhost_net vhost macvtap macvlan nfnetlink_queue nfnetlink
xt_CHECKSUM xt_nat ipt
Thanks. Will test and report back in a few days.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1568729
Title:
divide error: [#1] SMP in task_numa_migrate - handle_mm_fault
Status
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1568729
Title:
divide error: [#1] SMP in task_numa_migrate - hand
Public bug reported:
While running qemu 2.5 on a trusty host running 4.4.0-15.31~14.04.1 the
host system has crashed (load > 200) 3 times in the last 3 days.
Always with this stack trace:
Apr 9 19:01:09 cnode9.0 kernel: [197071.195577] divide error: [#1] SMP
Apr 9 19:01:09 cnode9.0 kerne
I have encountered this behaviour on the wily lts kernel in 14.04
(4.2.0-23-generic #28~14.04.1-Ubuntu)
However, i have manually added the route via ip route command, e.g.
# ip r a 192.168.100.1/32 dev br-ext
ip route show shows nothing, but ip route get displays the route.
# ip route show | gr
53 matches
Mail list logo
