Re: [pve-devel] [PATCH qemu-server 3/3] fix #2794: allow legacy IGD passthrough

2020-06-25 Thread Stefan Reiter
On 6/24/20 9:46 AM, Thomas Lamprecht wrote: Am 6/22/20 um 10:17 AM schrieb Stefan Reiter: @@ -89,7 +97,8 @@ sub get_pci_addr_map {   $pci_addr_map = {   piix3 => { bus => 0, addr => 1, conflict_ok => qw(ehci)  },   ehci => { bus => 0, addr => 1, conflict_ok => qw(piix3) }, # 

Re: [pve-devel] [PATCH qemu-server 3/3] fix #2794: allow legacy IGD passthrough

2020-06-24 Thread Thomas Lamprecht
Am 6/22/20 um 10:17 AM schrieb Stefan Reiter: >>> @@ -89,7 +97,8 @@ sub get_pci_addr_map { >>>   $pci_addr_map = { >>>   piix3 => { bus => 0, addr => 1, conflict_ok => qw(ehci)  }, >>>   ehci => { bus => 0, addr => 1, conflict_ok => qw(piix3) }, # instead  >>> of piix3 on arm >>> -

Re: [pve-devel] [PATCH qemu-server 3/3] fix #2794: allow legacy IGD passthrough

2020-06-22 Thread Stefan Reiter
On 6/18/20 5:00 PM, Thomas Lamprecht wrote: Am 6/18/20 um 4:36 PM schrieb Stefan Reiter: Legacy IGD passthrough requires address 00:1f.0 to not be assigned to anything on QEMU startup (currently it's assigned to bridge pci.2). Changing this in general would break live-migration, so introduce a

Re: [pve-devel] [PATCH qemu-server 3/3] fix #2794: allow legacy IGD passthrough

2020-06-18 Thread Thomas Lamprecht
Am 6/18/20 um 4:36 PM schrieb Stefan Reiter: > Legacy IGD passthrough requires address 00:1f.0 to not be assigned to > anything on QEMU startup (currently it's assigned to bridge pci.2). > Changing this in general would break live-migration, so introduce a new > hostpci parameter "legacy-igd",

[pve-devel] [PATCH qemu-server 3/3] fix #2794: allow legacy IGD passthrough

2020-06-18 Thread Stefan Reiter
Legacy IGD passthrough requires address 00:1f.0 to not be assigned to anything on QEMU startup (currently it's assigned to bridge pci.2). Changing this in general would break live-migration, so introduce a new hostpci parameter "legacy-igd", which if set to 1 will move that bridge to be nested