Linux-HyperV List
 help / color / mirror / Atom feed
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
Date: Mon, 15 Apr 2024 20:15:27 +0000	[thread overview]
Message-ID: <Zh2K3-HLXOesT_vZ@liuwe-devbox-debian-v2> (raw)
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

      parent reply	other threads:[~2024-04-15 20:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-13 13:06 Early kernel panic in dmi_decode when running 32-bit kernel on Hyper-V on Windows 11 Michael Schierl
2024-04-15  3:17 ` Michael Kelley
2024-04-15 21:03   ` Michael Schierl
2024-04-15 23:31     ` Michael Kelley
2024-04-16 21:24       ` Michael Schierl
2024-04-16 23:20         ` Michael Kelley
2024-04-17  9:43           ` Jean DELVARE
2024-04-17 15:51             ` Michael Kelley
2024-04-17 21:08             ` Michael Schierl
2024-04-17 22:34               ` Michael Kelley
2024-04-19 16:36                 ` Michael Kelley
2024-04-19 20:47                   ` Michael Schierl
2024-04-19 22:32                     ` Michael Kelley
2024-05-02 17:02                     ` Michael Kelley
2024-05-03  9:49                       ` Jean DELVARE
2024-04-15 20:15 ` Wei Liu [this message]

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=Zh2K3-HLXOesT_vZ@liuwe-devbox-debian-v2 \
    --to=wei.liu@kernel.org \
    --cc=decui@microsoft.com \
    --cc=haiyangz@microsoft.com \
    --cc=jdelvare@suse.com \
    --cc=kys@microsoft.com \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schierlm@gmx.de \
    /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