by giving the mapping config to assert_valid, not only the specific mapping
Signed-off-by: Dominik Csapak <d.csa...@proxmox.com>
---
changes in v6:
* add `my $config ...` line since that was introduced in a different
patch in v5 that was dropped with v6
depends on changes from pve-guest-common
PVE/QemuServer/PCI.pm | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/PVE/QemuServer/PCI.pm b/PVE/QemuServer/PCI.pm
index d758ae9d..a0d99692 100644
--- a/PVE/QemuServer/PCI.pm
+++ b/PVE/QemuServer/PCI.pm
@@ -432,8 +432,10 @@ sub parse_hostpci {
my $devices = PVE::Mapping::PCI::find_on_current_node($mapping);
die "PCI device mapping not found for '$mapping'\n" if !$devices ||
!scalar($devices->@*);
+ my $config = PVE::Mapping::PCI::config();
+
for my $device ($devices->@*) {
- eval { PVE::Mapping::PCI::assert_valid($mapping, $device) };
+ eval { PVE::Mapping::PCI::assert_valid($mapping, $device,
$config->{ids}->{$mapping}) };
die "PCI device mapping invalid (hardware probably changed): $@\n"
if $@;
push $alternatives->@*, [split(/;/, $device->{path})];
}
--
2.39.5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
