[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a05b46db-260f-4ba9-b335-4d8cd14292e2@infradead.org>
Date: Sat, 21 Oct 2023 22:10:58 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: gmssixty gmssixty <gmssixty@...il.com>,
linux-kernel@...r.kernel.org,
"linux-hyperv@...r.kernel.org" <linux-hyperv@...r.kernel.org>
Subject: Re: Kernel panic after booting custom kernel [hyperv message]
[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
Powered by blists - more mailing lists