linux-kernel - 5.10.189 and 5.10.190 breaks nested virtualization

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:   Mon, 14 Aug 2023 12:56:44 +0000
From:   Blair Strater <strater@...tonmail.com>
To:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: 5.10.189 and 5.10.190 breaks nested virtualization

Per the request at https://lwn.net/Articles/940798/, I'm reaching out to let you know that this patch breaks nested virtualization on AMD processors.

I've tested 5.10.189 and 5.10.190 on the "outer" virtual host, and both Debian 12 running libvirt, and Proxmox 7 as "inner" hosts. For Debian, the nested VM fails to start at all, and consumes the entirety of one CPU core. For Proxmox, 100-200MB/second of memory is allocated and never released, and also the guest fails to start. The problems go away when taking the outer host back to 5.10.188.

The processor in question is a Ryzen 7 2700. The kernel revision for Proxmox is 5.15.108-1-pve, and the kernel revision for Debian 12 is 6.1.0-11-amd64. I've run into another person who can confirm that this bug also occurs in the 6.4 series, "somewhere between 6.4.3 and 6.4.9", 6.4.9 being the likely culprit.

Please let me know if you need any other information. 

I apologize for bothering an entire mailing list, Greg's email bot told me to.