Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:4 as permitted sender) client-ip=2620:137:e000::3:4;
Message-ID: <a05b46db-260f-4ba9-b335-4d8cd14292e2@infradead.org>
Date:   Sat, 21 Oct 2023 22:10:58 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Kernel panic after booting custom kernel [hyperv message]
Content-Language: en-US
To:     gmssixty gmssixty <gmssixty@gmail.com>,
        linux-kernel@vger.kernel.org,
        "linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>
References: <CAOx-CDU4_3j-mQcczscZ-xqq+XF7R=H62i1SoojczG8WELUMgQ@mail.gmail.com>
From:   Randy Dunlap <rdunlap@infradead.org>
In-Reply-To: <CAOx-CDU4_3j-mQcczscZ-xqq+XF7R=H62i1SoojczG8WELUMgQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk

[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