mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Teddy Astie <teddy.astie@vates.tech>
Cc: Juergen Gross <jgross@suse.com>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>,
	xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] x86/xen: Consider Xen PVH support in CONFIG_XEN_PVHVM
Date: Tue, 24 Feb 2026 12:01:29 +0100	[thread overview]
Message-ID: <3a08a2d0-a18f-40e1-b9bf-9b71e0c797c0@suse.com> (raw)
In-Reply-To: <7b17bfbb4b25a59514707f91546ce8c3a24369e0.1771929804.git.teddy.astie@vates.tech>

On 24.02.2026 11:51, Teddy Astie wrote:
> It's currently possible to build Linux with CONFIG_PVH|CONFIG_XEN_PVHVM
> and no CONFIG_XEN_PVH.

In which case, how can you expect Xen PVH to work?

> That leads to inconsistent kernels that fails with
> "Missing xen PVH initialization" when booting using PVH boot method or
> display various errors and fail to initialize Xen PV drivers when booting
> with PVH-GRUB.
> 
>     platform_pci_unplug: Xen Platform PCI: unrecognised magic value
>     ...
>     # modprobe xen-blkfront
>     modprobe: ERROR: could not insert 'xen_blkfront': No such device
>     # modprobe xen-netfront
>     modprobe: ERROR: could not insert 'xen_netfront': No such device
> 
> When built without CONFIG_XEN_PVH, PVH-specific logic is disabled, hence when
> booting with e.g PVH-OVMF, Linux assumes we are a HVM guest, even when we aren't
> actually one (in the "with HVM emulated devices" sense).
> 
> As it is actually possible to boot Xen PVH without CONFIG_PVH; and that most
> Xen-related logic exist within CONFIG_XEN_PVHVM; consider PVH guests support
> within CONFIG_XEN_PVHVM instead of CONFIG_XEN_PVH.

XEN_PVHVM serves a different purpose though, iirc.

Jan

  reply	other threads:[~2026-02-24 11:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-24 10:51 Teddy Astie
2026-02-24 11:01 ` Jan Beulich [this message]
2026-02-24 11:13   ` Jürgen Groß
2026-02-24 11:14 ` Roger Pau Monné
2026-02-24 11:23   ` Jürgen Groß
2026-02-24 12:46     ` Teddy Astie
2026-02-24 13:53       ` Jürgen Groß
2026-02-24 12:34   ` Teddy Astie
2026-02-24 14:26     ` Roger Pau Monné

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=3a08a2d0-a18f-40e1-b9bf-9b71e0c797c0@suse.com \
    --to=jbeulich@suse.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleksandr_tyshchenko@epam.com \
    --cc=teddy.astie@vates.tech \
    --cc=xen-devel@lists.xenproject.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®