Received-SPF: pass (google.com: domain of linux-kernel+bounces-145869-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Date: Mon, 15 Apr 2024 20:15:27 +0000
From: Wei Liu <wei.liu@kernel.org>
To: Michael Schierl <schierlm@gmx.de>
Cc: Jean Delvare <jdelvare@suse.com>,
	"K. Y. Srinivasan" <kys@microsoft.com>,
	Haiyang Zhang <haiyangz@microsoft.com>,
	Wei Liu <wei.liu@kernel.org>, Dexuan Cui <decui@microsoft.com>,
	linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Early kernel panic in dmi_decode when running 32-bit kernel on
 Hyper-V on Windows 11
Message-ID: <Zh2K3-HLXOesT_vZ@liuwe-devbox-debian-v2>
References: <2db080ae-5e59-46e8-ac4e-13cdf26067cc@gmx.de>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2db080ae-5e59-46e8-ac4e-13cdf26067cc@gmx.de>

On Sat, Apr 13, 2024 at 03:06:05PM +0200, Michael Schierl wrote:
> [please cc: me as I am not subscribed to either mailing list]
> 
[...]
> [Slightly off-topic: As 64-bit kernels work fine, if there are ways to
> run a 32-bit userland containerized or chrooted in a 64-bit kernel so
> that the userland (espeically uname and autoconf) cannot distinguish
> from a 32-bit kernel, that might be another option for my use case.
> Nested virtualization would of course also work, but the performance
> loss due to nested virtualization negates the effect of being able to
> pass more than one of the (2 physical, 4 hyperthreaded) cores of my
> laptop to the VM].
> 

Have you tried `linux32`?

See https://linux.die.net/man/8/linux32

Thanks,
Wei.

> 
> 
> Thanks for help and best regards,
> 
> 
> Michael