all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Wolfgang Bumiller <w.bumiller@proxmox.com>
To: Markus Frank <m.frank@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH docs v4 4/5] added vIOMMU documentation
Date: Tue, 17 Jan 2023 16:01:46 +0100	[thread overview]
Message-ID: <20230117150146.5ouacpymvu7r6rhm@casey.proxmox.com> (raw)
In-Reply-To: <e0097449-e389-86c9-c75a-4023b8172827@proxmox.com>

On Tue, Jan 17, 2023 at 11:55:47AM +0100, Markus Frank wrote:
> 
> 
> On 1/16/23 11:00, Wolfgang Bumiller wrote:
> > On Fri, Jan 13, 2023 at 02:31:36PM +0100, Markus Frank wrote:
> > > Moreover it adds an extra AMDVI-PCI device that is using the first pci address.
> > > `kvm: -device VGA,id=vga,bus=pcie.0,addr=0x1: PCI: slot 1 function 0 not available for VGA, in use by AMDVI-PCI,id=(null)`
> > 
> > For that I'd say, try to add the AMDVI-PCI device manually to an
> > explicitly chosen slot. We need to avoid automatically added devices
> > like the plague, because moving them later can break live snapshots (and
> > windows).
> > 
> I manually added a AMDVI-PCI device with a explicitly chosen slot but
> amd-iommu still adds an extra AMDVI-PCI device.
> I do not see any way to prevent this or to change the address
> of the additionally added AMDVI-PCI device (from amd-iommu).
> 
> I think amd-iommu is very impractical if we cannot set this slot manually.

Okay, let's just not provide it for now.




  reply	other threads:[~2023-01-17 15:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-25 14:08 [pve-devel] [PATCH qemu-server v4 0/5] vIOMMU-Feature Markus Frank
2022-11-25 14:08 ` [pve-devel] [PATCH qemu-server v4 1/5] tests: replaced somemachine&someothermachine with q35&pc Markus Frank
2022-11-25 14:08 ` [pve-devel] [PATCH qemu-server v4 2/5] fix #3784: Parameter for guest vIOMMU & machine as property-string Markus Frank
2023-01-13  9:51   ` Wolfgang Bumiller
2022-11-25 14:08 ` [pve-devel] [PATCH qemu-server v4 3/5] added test-cases for new machine-syntax & viommu Markus Frank
2022-11-25 14:08 ` [pve-devel] [PATCH docs v4 4/5] added vIOMMU documentation Markus Frank
2023-01-13 10:09   ` Wolfgang Bumiller
2023-01-13 13:31     ` Markus Frank
2023-01-16 10:00       ` Wolfgang Bumiller
2023-01-17 10:55         ` Markus Frank
2023-01-17 15:01           ` Wolfgang Bumiller [this message]
2022-11-25 14:08 ` [pve-devel] [PATCH manager v4 5/5] ui: MachineEdit with viommu checkbox Markus Frank
2023-01-12 13:51 ` [pve-devel] [PATCH qemu-server v4 0/5] vIOMMU-Feature Markus Frank

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=20230117150146.5ouacpymvu7r6rhm@casey.proxmox.com \
    --to=w.bumiller@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 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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal