public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Aaron Lauterer <a.lauterer@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Markus Frank <m.frank@proxmox.com>
Subject: Re: [pve-devel] [PATCH qemu-server 0/3] vIOMMU-Feature
Date: Mon, 24 Oct 2022 16:28:41 +0200	[thread overview]
Message-ID: <959423dc-e646-e479-d11a-6fbc9374b2bd@proxmox.com> (raw)
In-Reply-To: <20220921090748.47445-1-m.frank@proxmox.com>

On which CPU vendors have you tested this?

We use similar settings in our training env, and even on AMD CPUs it is 
necessary to follow the Intel steps to enable it in a VM as Qemu implements the 
Intel variant, apparently.

I think this should be added to the (eventual) documentation after verifying it 
again :)

On 9/21/22 11:07, Markus Frank wrote:
> Patches for enabling virtual IOMMU inside guests for nested pci
> passthrough.
> 
---8<---




      parent reply	other threads:[~2022-10-24 14:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-21  9:07 Markus Frank
2022-09-21  9:07 ` [pve-devel] [PATCH qemu-server 1/3] tests: replaced somemachine&someothermachine with q35&pc Markus Frank
2022-09-21  9:07 ` [pve-devel] [PATCH qemu-server 2/3] fix #3784: Parameter for guest vIOMMU & machine as property-string Markus Frank
2022-10-24 14:19   ` Dominik Csapak
2022-09-21  9:07 ` [pve-devel] [PATCH qemu-server 3/3] added test-cases for new machine-syntax & viommu Markus Frank
2022-10-24 14:20   ` Dominik Csapak
2022-09-21  9:07 ` [pve-devel] [PATCH manager] ui: MachineEdit with viommu checkbox Markus Frank
2022-10-24 14:22   ` Dominik Csapak
2022-10-24 14:28 ` Aaron Lauterer [this message]

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=959423dc-e646-e479-d11a-6fbc9374b2bd@proxmox.com \
    --to=a.lauterer@proxmox.com \
    --cc=m.frank@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal