From: Xin Li <xin@zytor.com>
To: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"Jürgen Groß" <jgross@suse.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
alexandre.chartre@oracle.com,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Zhang, Tao1" <tao1.zhang@intel.com>
Subject: Re: [Bug Report] Linux v6.15-rc7 boot failure on Xen-4.17
Date: Tue, 27 May 2025 10:54:55 -0700 [thread overview]
Message-ID: <86cec0d4-96fa-49dc-aac9-29dcae48b425@zytor.com> (raw)
In-Reply-To: <20250527174612.ml4raiueqdophhxl@desk>
On 5/27/2025 10:46 AM, Pawan Gupta wrote:
>> Attached is the serial console log and my kernel config.
> Serial logs aren't telling much. I do not have a Xen setup to test, without
> Xen the config that you provided is booting a KVM guest just fine.
Yeah, as I replied to Juergen, the same kernel binary boots fine as
"native".
Unfortunately when booting as dom0 on Xen, it keeps rebooting w/o
helpful log.
>
> Adding Andrew if he has any pointers on debugging this.
Oh, I should have done it...
next prev parent reply other threads:[~2025-05-27 17:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-25 4:42 [Bug Report] Linux v6.15-rc7 boot failure on Xen-4.17 Xin Li
2025-05-25 6:58 ` Jürgen Groß
2025-05-25 8:34 ` Xin Li
2025-05-27 17:46 ` Pawan Gupta
2025-05-27 17:54 ` Xin Li [this message]
2025-05-27 18:35 ` Jürgen Groß
2025-05-27 19:21 ` Xin Li
2025-05-27 19:29 ` Andrew Cooper
2025-05-28 5:11 ` Jürgen Groß
2025-05-28 6:49 ` Juergen Gross
2025-05-28 7:27 ` Xin Li
2025-05-28 8:26 ` Xin Li
2025-05-28 8:57 ` Jürgen Groß
2025-05-28 9:19 ` Juergen Gross
2025-05-28 21:53 ` Gupta Pawan
2025-05-29 6:02 ` Jürgen Groß
2025-05-28 8:39 ` Jürgen Groß
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=86cec0d4-96fa-49dc-aac9-29dcae48b425@zytor.com \
--to=xin@zytor.com \
--cc=alexandre.chartre@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=dave.hansen@linux.intel.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=peterz@infradead.org \
--cc=tao1.zhang@intel.com \
--cc=x86@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