Re: [libvirt] RFC: managing pci passthrough usage of sriov VFs via a new network forward type

2011-08-24 Thread Laine Stump
On 08/23/2011 06:50 AM, Daniel P. Berrange wrote: On Mon, Aug 22, 2011 at 05:17:25AM -0400, Laine Stump wrote: For some reason beyond my comprehension, the designers of SRIOV ethernet cards decided that the virtual functions (VF) of the card (each VF corresponds to an ethernet device, e.g.

Re: [libvirt] RFC: managing pci passthrough usage of sriov VFs via a new network forward type

2011-08-24 Thread Daniel P. Berrange
On Wed, Aug 24, 2011 at 04:16:33AM -0400, Laine Stump wrote: On 08/23/2011 06:50 AM, Daniel P. Berrange wrote: Although I realize that many people are predisposed to not like the idea of PCI passthrough of ethernet devices (including me), it seems that it's going to be used, so we may as well

Re: [libvirt] RFC: managing pci passthrough usage of sriov VFs via a new network forward type

2011-08-24 Thread Laine Stump
On 08/24/2011 05:48 AM, Daniel P. Berrange wrote: Having transient hostdevs does not really work nicely, because we want all PCI devices in the guest to be persistently in the XML, so we can ensure the guest PCI address does not get changed each time the guest is run. Ah, well that clinches

Re: [libvirt] RFC: managing pci passthrough usage of sriov VFs via a new network forward type

2011-08-23 Thread Gerhard Stenzel
On Mon, 2011-08-22 at 05:17 -0400, Laine Stump wrote: For some reason beyond my comprehension, the designers of SRIOV ethernet cards decided that the virtual functions (VF) of the card (each VF corresponds to an ethernet device, e.g. eth10) should each be given a new+different+random MAC

Re: [libvirt] RFC: managing pci passthrough usage of sriov VFs via a new network forward type

2011-08-23 Thread Daniel P. Berrange
On Mon, Aug 22, 2011 at 05:17:25AM -0400, Laine Stump wrote: For some reason beyond my comprehension, the designers of SRIOV ethernet cards decided that the virtual functions (VF) of the card (each VF corresponds to an ethernet device, e.g. eth10) should each be given a new+different+random

Re: [libvirt] RFC: managing pci passthrough usage of sriov VFs via a new network forward type

2011-08-23 Thread D. Herrendoerfer
On Aug 23, 2011, at 12:50 PM, Daniel P. Berrange wrote: [...snip...] This makes using SRIOV VFs via PCI passthrough very unpalatable. The problem can be solved by setting the MAC address of the ethernet device prior to assigning it to the guest, but of course the hostdev element used to

Re: [libvirt] RFC: managing pci passthrough usage of sriov VFs via a new network forward type

2011-08-23 Thread Daniel P. Berrange
On Tue, Aug 23, 2011 at 01:53:42PM +0200, D. Herrendoerfer wrote: On Aug 23, 2011, at 12:50 PM, Daniel P. Berrange wrote: [...snip...] This makes using SRIOV VFs via PCI passthrough very unpalatable. The problem can be solved by setting the MAC address of the ethernet device prior to

[libvirt] RFC: managing pci passthrough usage of sriov VFs via a new network forward type

2011-08-22 Thread Laine Stump
For some reason beyond my comprehension, the designers of SRIOV ethernet cards decided that the virtual functions (VF) of the card (each VF corresponds to an ethernet device, e.g. eth10) should each be given a new+different+random MAC address each time the hardware is rebooted. Normally, udev