From: Juergen Gross <jgross@suse.com>
To: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: CONFIG_XEN_VIRTIO{_FORCE_GRANT} interferes with nested virt
Date: Wed, 5 Oct 2022 15:34:56 +0200 [thread overview]
Message-ID: <ecdc11dc-6090-e050-bcba-aafbd8aaf3b6@suse.com> (raw)
In-Reply-To: <Yz2Fvp9Q9aeYKnDY@mail-itl>
[-- Attachment #1.1.1: Type: text/plain, Size: 2423 bytes --]
On 05.10.22 15:25, Marek Marczykowski-Górecki wrote:
> On Wed, Oct 05, 2022 at 02:57:01PM +0200, Juergen Gross wrote:
>> On 05.10.22 14:41, Marek Marczykowski-Górecki wrote:
>>> Hi,
>>>
>>> When booting Xen with Linux dom0 nested under KVM,
>>> CONFIG_XEN_VIRTIO_FORCE_GRANT=y makes it unable to use virtio devices
>>> provided by L0 hypervisor (KVM with qemu). With PV dom0, grants are
>>> required for virtio even if just CONFIG_XEN_VIRTIO is enabled.
>>>
>>> This is probably uncommon corner case, but one that has bitten me in my
>>> CI setup... I think Xen should set smarter
>>> virtio_require_restricted_mem_acc(), that enforces it only for devices
>>> really provided by another Xen VM (not by the "outer host"), but I'm not
>>> sure how that could be done. Any ideas?
>>>
>>
>> It should be possible to add a boot parameter for that purpose. Using it
>> would open a security hole, though (basically like all PCI passthrough to
>> PV guests).
>
> What about excluding just dom0? At least currently, there is no way for
> dom0 to see virtio devices provided by another Xen domU.
Even not via hotplug?
>
> Something like this:
> ---8<---
> diff --git a/arch/x86/xen/enlighten_pv.c b/arch/x86/xen/enlighten_pv.c
> index 9b1a58dda935..6ac32b0b3720 100644
> --- a/arch/x86/xen/enlighten_pv.c
> +++ b/arch/x86/xen/enlighten_pv.c
> @@ -111,7 +111,7 @@ static DEFINE_PER_CPU(struct tls_descs, shadow_tls_desc);
> static void __init xen_pv_init_platform(void)
> {
> /* PV guests can't operate virtio devices without grants. */
> - if (IS_ENABLED(CONFIG_XEN_VIRTIO))
> + if (IS_ENABLED(CONFIG_XEN_VIRTIO) && !xen_initial_domain())
> virtio_set_mem_acc_cb(virtio_require_restricted_mem_acc);
>
> populate_extra_pte(fix_to_virt(FIX_PARAVIRT_BOOTMAP));
> ---8<---
>
> This BTW raises also a question what will happen on Xen nested inside
> Xen, when L0 will provide virtio devices to L1. Grants set by L1 dom0
> wouldn't work on L0, no? Or maybe this is solved already for pv-shim
> case?
This is a similar problem as with normal Xen PV devices.
You will need either a simple grant passthrough like with pv-shim (enabling
such devices for one guest in L1 only), or you need a grant multiplexer in L1
Xen in case you want to be able to have multiple guests in L1 being able to
use L0 PV devices.
Juergen
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3149 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2022-10-05 13:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 12:41 CONFIG_XEN_VIRTIO{_FORCE_GRANT} interferes with nested virt Marek Marczykowski-Górecki
2022-10-05 12:57 ` Juergen Gross
2022-10-05 13:25 ` Marek Marczykowski-Górecki
2022-10-05 13:34 ` Juergen Gross [this message]
2022-10-05 13:51 ` Marek Marczykowski-Górecki
2022-10-05 15:04 ` Juergen Gross
2022-10-05 15:35 ` Marek Marczykowski-Górecki
2022-10-05 15:45 ` Juergen Gross
2022-10-05 16:48 ` Marek Marczykowski-Górecki
2022-10-06 6:37 ` Juergen Gross
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=ecdc11dc-6090-e050-bcba-aafbd8aaf3b6@suse.com \
--to=jgross@suse.com \
--cc=marmarek@invisiblethingslab.com \
--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.