mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: gmssixty gmssixty <gmssixty@gmail.com>,
	linux-kernel@vger.kernel.org,
	"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>
Subject: Re: Kernel panic after booting custom kernel [hyperv message]
Date: Sat, 21 Oct 2023 22:10:58 -0700	[thread overview]
Message-ID: <a05b46db-260f-4ba9-b335-4d8cd14292e2@infradead.org> (raw)
In-Reply-To: <CAOx-CDU4_3j-mQcczscZ-xqq+XF7R=H62i1SoojczG8WELUMgQ@mail.gmail.com>

[adding linux-hyperv mailing list]


On 10/21/23 22:05, gmssixty gmssixty wrote:
> I have compiled kernel-6.4.12 from source. I have put the bzImage in
> /dev/sda3/boot. Booted it. I am on virtualbox. After booting got this
> message:
> 
> Kernel panic - not syncing: XSAVE has to be disabled as it is not
> supported by this module
> 

The next line should say:

	Please add 'noxsave' to the kernel command line.

That's one (maybe temporary) solution.

> Note that, no other software has been installed in /dev/sda3. I am
> trying to boot custom linux kernel.
> 
> Why did I get this message? What should I do after this?

Do you mean to be using hyperv?
Do hyperv and virtualbox mix well?

You should post your full custom .config file.

-- 
~Randy

  reply	other threads:[~2023-10-22  5:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-22  5:05 Kernel panic after booting custom kernel gmssixty gmssixty
2023-10-22  5:10 ` Randy Dunlap [this message]
2023-10-22  5:23   ` Kernel panic after booting custom kernel [hyperv message] gmssixty gmssixty
2023-10-22  5:34     ` Michael Kelley (LINUX)

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=a05b46db-260f-4ba9-b335-4d8cd14292e2@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=gmssixty@gmail.com \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®