From: Alexandru Elisei <alexandru.elisei@arm.com>
To: Dongli Si <sidongli1997@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH kvmtool] x86: Fixed Unable to execute init process since glibc version 2.33
Date: Tue, 8 Mar 2022 12:12:38 +0000 [thread overview]
Message-ID: <YidINk5BxfZLaFyL@monolith.localdoman> (raw)
In-Reply-To: <20220226060048.3-1-sidongli1997@gmail.com>
Hi,
Hi, I was unable to apply the patch as is because your base is missing
commit 20b93be583f6 ("x86: Set the correct APIC ID"). Changing it is so it
applies was trivial though.
I tested the patch with a VM image using glibc 2.36 and Linux v5.17-rc7,
the glibc error went away and I was able to boot to userspace; as an added
bonus, this kernel message went away:
[ 0.000000] CPU: vendor_id 'LKVMLKVMLKVM' unknown, using generic init.
[ 0.000000] CPU: Your system may be unstable.
But this warning is new:
[ 0.000000] [Firmware Bug]: TSC doesn't count with P0 frequency!
I don't know what causes it (kvmtool's bios implementation is not feature
complete with regards to my CPU features?), and doesn't look like it's
something introduced by this patch, so as far as I'm concerned the patch is
working as intended:
Tested-by: Alexandru Elisei <alexandru.elisei@arm.com>
Thanks,
Alex
On Sat, Feb 26, 2022 at 02:00:48PM +0800, Dongli Si wrote:
> From: Dongli Si <sidongli1997@gmail.com>
>
> glibc detected invalid CPU Vendor name will cause an error:
>
> [ 0.450127] Run /sbin/init as init process
> /lib64/libc.so.6: CPU ISA level is lower than required
> [ 0.451931] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
> [ 0.452117] CPU: 0 PID: 1 Comm: init Not tainted 5.17.0-rc1 #72
>
> Signed-off-by: Dongli Si <sidongli1997@gmail.com>
> ---
> x86/cpuid.c | 14 +++++++++-----
> 1 file changed, 9 insertions(+), 5 deletions(-)
>
> diff --git a/x86/cpuid.c b/x86/cpuid.c
> index c3b67d9..d58a027 100644
> --- a/x86/cpuid.c
> +++ b/x86/cpuid.c
> @@ -2,6 +2,7 @@
>
> #include "kvm/kvm.h"
> #include "kvm/util.h"
> +#include "kvm/cpufeature.h"
>
> #include <sys/ioctl.h>
> #include <stdlib.h>
> @@ -10,7 +11,7 @@
>
> static void filter_cpuid(struct kvm_cpuid2 *kvm_cpuid)
> {
> - unsigned int signature[3];
> + struct cpuid_regs regs;
> unsigned int i;
>
> /*
> @@ -22,10 +23,13 @@ static void filter_cpuid(struct kvm_cpuid2 *kvm_cpuid)
> switch (entry->function) {
> case 0:
> /* Vendor name */
> - memcpy(signature, "LKVMLKVMLKVM", 12);
> - entry->ebx = signature[0];
> - entry->ecx = signature[1];
> - entry->edx = signature[2];
> + regs = (struct cpuid_regs) {
> + .eax = 0x00,
> + };
> + host_cpuid(®s);
> + entry->ebx = regs.ebx;
> + entry->ecx = regs.ecx;
> + entry->edx = regs.edx;
> break;
> case 1:
> /* Set X86_FEATURE_HYPERVISOR */
> --
> 2.32.0
>
next prev parent reply other threads:[~2022-03-08 12:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-26 6:00 [PATCH kvmtool] x86: Fixed Unable to execute init process since glibc version 2.33 Dongli Si
2022-03-07 10:43 ` Alexandru Elisei
2022-03-08 12:12 ` Alexandru Elisei [this message]
2022-03-08 17:31 ` Andre Przywara
2022-03-10 12:17 ` Alexandru Elisei
2022-03-11 12:10 ` Andre Przywara
2022-03-11 13:43 ` Alexandru Elisei
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=YidINk5BxfZLaFyL@monolith.localdoman \
--to=alexandru.elisei@arm.com \
--cc=kvm@vger.kernel.org \
--cc=sidongli1997@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox