On 01/30/2012 08:16 PM, Roopa Prabhu wrote:
Laine, I haven't gone through your whole email yet. Was just curious about
one quick thing,
For sriov VF's, are we expecting that a net device (eth interface) be
present on the host if its being used as a hostdev ?.
Either should be possible. If
On 1/31/12 1:16 AM, Laine Stump la...@laine.org wrote:
On 01/30/2012 08:16 PM, Roopa Prabhu wrote:
Laine, I haven't gone through your whole email yet. Was just curious about
one quick thing,
For sriov VF's, are we expecting that a net device (eth interface) be
present on the host if its
On 01/23/2012 09:08 AM, Paolo Bonzini wrote:
devices
interface type='hostdev'
source
address type='pci' bus='0x06' slot='0x02' function='0x0'/
/source
mac address='00:16:3e:5d:c7:9e'/
address type='pci' .../
/interface
/devices
This is the model that I'm now following.
Looking further into
On 1/30/12 11:14 AM, Laine Stump la...@laine.org wrote:
On 01/23/2012 09:08 AM, Paolo Bonzini wrote:
devices
interface type='hostdev'
source
address type='pci' bus='0x06' slot='0x02' function='0x0'/
/source
mac address='00:16:3e:5d:c7:9e'/
address type='pci' .../
/interface
On 1/20/12 1:50 PM, Laine Stump la...@laine.org wrote:
To refresh everyone's memory, the origin of the problem I'm trying to
solve here is that the VFs of an SRIOV-capable ethernet card are given
new random MAC addresses each time the card is initialized. If those VFs
are then
On 01/20/2012 10:50 PM, Laine Stump wrote:
To refresh everyone's memory, the origin of the problem I'm trying to
solve here is that the VFs of an SRIOV-capable ethernet card are given
new random MAC addresses each time the card is initialized. If those VFs
are then passed-through to a guest
On 01/23/2012 09:08 AM, Paolo Bonzini wrote:
On 01/20/2012 10:50 PM, Laine Stump wrote:
To refresh everyone's memory, the origin of the problem I'm trying to
solve here is that the VFs of an SRIOV-capable ethernet card are given
new random MAC addresses each time the card is initialized. If
On 01/23/2012 11:12 AM, Laine Stump wrote:
On 01/23/2012 09:08 AM, Paolo Bonzini wrote:
In view of the discussion on SCSI passthrough, it seems to me that
this should be attached to an interface element:
devices
interface type='hostdev'
source
address type='pci' bus='0x06' slot='0x02'
On 01/23/2012 05:12 PM, Laine Stump wrote:
In view of the discussion on SCSI passthrough, it seems to me that
this should be attached to an interface element:
devices
interface type='hostdev'
source
address type='pci' bus='0x06' slot='0x02' function='0x0'/
/source
mac
Hit send too soon... a couple more observations.
On 01/23/2012 05:12 PM, Laine Stump wrote:
(Note that even with *no new XML*, we already have a problem where just
scanning all the hostdev entries won't tell us about all host devices
that are currently assigned exclusively to guests - using a
On 01/23/2012 01:06 PM, Paolo Bonzini wrote:
On 01/23/2012 05:12 PM, Laine Stump wrote:
In view of the discussion on SCSI passthrough, it seems to me that
this should be attached to an interface element:
devices
interface type='hostdev'
source
address type='pci' bus='0x06' slot='0x02'
To refresh everyone's memory, the origin of the problem I'm trying to
solve here is that the VFs of an SRIOV-capable ethernet card are given
new random MAC addresses each time the card is initialized. If those VFs
are then passed-through to a guest using the existing hostdev config,
the guest
12 matches
Mail list logo
