From: Fiona Ebner <f.ebner@proxmox.com>
To: Eneko Lacunza <elacunza@binovo.es>, pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [RFC kernel] revert problematic TSC multiplier commit
Date: Wed, 14 Sep 2022 09:50:24 +0200 [thread overview]
Message-ID: <af47f876-c80d-4c55-e0fc-e836fa647807@proxmox.com> (raw)
In-Reply-To: <c7e45768-c09a-1128-4f5a-5e9f3e0ec06d@binovo.es>
Am 05.09.22 um 10:25 schrieb Eneko Lacunza:
> Hi Fiona,
>
> I just confirmed that in addition to issue reported in
> https://bugzilla.proxmox.com/show_bug.cgi?id=4073 (live migrated VM hung
> using 100% CPU), we also reproduce issue reported in
>
> https://forum.proxmox.com/threads/zeitspr%C3%BCnge-in-vms-seit-pve-7-2.112756/
>
> At least what I understand google translating it :)
>
> - From 5.15.39-4-pve (Ryzen 2600X) to 5.15.39-4-pve (Ryzen 1700): Problems
> * Migration of a VM hung 4 other VMs in destination host (no 100% CPU use, consoles show time related issues, watchdog, etc.).
>
> We can test the patch if you can provide a kernel .deb package.
>
Hi,
a kernel package for 5.19 is available in all repositories now [0]. The
fix for the TSC multiplier issue is included there.
[0]: https://forum.proxmox.com/threads/115090/
Best Regards,
Fiona
next prev parent reply other threads:[~2022-09-14 7:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 13:28 Fiona Ebner
2022-09-01 6:25 ` Fiona Ebner
[not found] ` <f7d1ae7c-5b8a-8cf7-8aff-979348b216ca@binovo.es>
2022-09-02 7:47 ` Fiona Ebner
[not found] ` <536bbaea-9f39-0b96-e16e-70c04c0852a5@binovo.es>
[not found] ` <1ca8041f-5099-ad72-9c86-ddc86c1aafff@binovo.es>
[not found] ` <c7e45768-c09a-1128-4f5a-5e9f3e0ec06d@binovo.es>
2022-09-14 7:50 ` Fiona Ebner [this message]
[not found] ` <4530687c-86ea-e9f6-c932-7f1f702d6647@binovo.es>
[not found] ` <be970183-0eae-9fc8-ad44-f8e90b78b62c@binovo.es>
2022-09-15 8:37 ` Fiona Ebner
[not found] ` <mailman.140.1663148345.354.pve-devel@lists.proxmox.com>
2022-09-15 10:44 ` Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=af47f876-c80d-4c55-e0fc-e836fa647807@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=elacunza@binovo.es \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.