From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Sergiy Kibrik <sergiy_kibrik@epam.com>
Cc: xen-devel@lists.xenproject.org, Jan Beulich <jbeulich@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [XEN PATCH] x86/hvm: make stdvga support optional
Date: Mon, 16 Sep 2024 09:42:33 +0200 [thread overview]
Message-ID: <ZufhafDwU-jgYusv@macbook.local> (raw)
In-Reply-To: <0f256ef4-2059-4068-a38d-1293efbb35ca@epam.com>
On Mon, Sep 16, 2024 at 09:37:16AM +0300, Sergiy Kibrik wrote:
> 12.09.24 12:14, Roger Pau Monné:
> > Shouldn't Xen report an error if a user attempts to create a domain
> > with X86_EMU_VGA set in emulation_flags, but stdvga has been built
> > time disabled?
>
> I'm afraid this can accidentally render the system unbootable, because it
> looks like toolstack always sets X86_EMU_VGA flag.
Not for PV or PVH guests. It won't render the system unbootable, it
would just leave it unable to create HVM guests. dom0 however, and PV
or PVH guests don't use the X86_EMU_VGA flag.
As pointed out by Jan, we need slightly better integration with the
toolstack. IMO if we want to pursue this route we need a way for Xen
to advertise which X86_EMU_* are supported at least.
Thanks, Roger.
next prev parent reply other threads:[~2024-09-16 7:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 8:57 [XEN PATCH] x86/hvm: make stdvga support optional Sergiy Kibrik
2024-09-12 9:14 ` Roger Pau Monné
2024-09-16 6:37 ` Sergiy Kibrik
2024-09-16 6:41 ` Jan Beulich
2024-09-16 7:42 ` Roger Pau Monné [this message]
2024-09-12 10:22 ` Jan Beulich
2024-09-12 20:15 ` Stefano Stabellini
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=ZufhafDwU-jgYusv@macbook.local \
--to=roger.pau@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=sergiy_kibrik@epam.com \
--cc=sstabellini@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.