On Wed, Apr 08, 2009 at 12:09:06PM +0100, Daniel P. Berrange wrote:
On Wed, Apr 08, 2009 at 01:06:48PM +0200, Maximilian Wilhelm wrote:
Anno domini 2009 Daniel P. Berrange scripsit:
[...]
In the (nearish) future NICs will start appearing with SR-IOV
capabilities.
This gives you
Anno domini 2009 Daniel P. Berrange scripsit:
[...]
In the (nearish) future NICs will start appearing with SR-IOV capabilities.
This gives you one physical PCI device, whcih exposes multiple functions.
So a single physical NIC appears as 8 NICs to the OS. You can thus directly
assign each of
Anno domini 2009 Daniel P. Berrange scripsit:
On Wed, Apr 08, 2009 at 01:06:48PM +0200, Maximilian Wilhelm wrote:
Anno domini 2009 Daniel P. Berrange scripsit:
That was a *really* _fast_ reply :)
[...]
In the (nearish) future NICs will start appearing with SR-IOV
capabilities.
On Tue, Apr 07, 2009 at 06:32:43PM -0700, David Lutterkort wrote:
On Tue, 2009-04-07 at 18:39 -0300, Klaus Heinrich Kiwi wrote:
I was thinking about the semantics I described above. It ultimately
means that we'll have a bridge for each VLAN tag that crosses the trunk
interface. So for
On Wed, Apr 08, 2009 at 01:06:48PM +0200, Maximilian Wilhelm wrote:
Anno domini 2009 Daniel P. Berrange scripsit:
[...]
In the (nearish) future NICs will start appearing with SR-IOV capabilities.
This gives you one physical PCI device, whcih exposes multiple functions.
So a single
On Tue, Apr 07, 2009 at 06:39:17PM -0300, Klaus Heinrich Kiwi wrote:
I was thinking about the semantics I described above. It ultimately
I just caught this discussion. We have implemented basic vlan support
(for xend, bridged only). Is there an existing patch from you guys for
the user
Are there any plans to support configuring 802.1q VLAN tagging through
libvirt?
My understanding is that libvirt would use vconfig to create tagged
interfaces, while using a physical interface as trunk (e.g., eth0 is the
trunk, eth0.20 the interface with the '20' vlan tag).
Then it would add
On Thu, Apr 02, 2009 at 03:50:32PM -0300, Klaus Heinrich Kiwi wrote:
Are there any plans to support configuring 802.1q VLAN tagging through
libvirt?
My understanding is that libvirt would use vconfig to create tagged
interfaces, while using a physical interface as trunk (e.g., eth0
Hi Klaus,
On Thu, 2009-04-02 at 15:50 -0300, Klaus Heinrich Kiwi wrote:
My understanding is that libvirt would use vconfig to create tagged
interfaces, while using a physical interface as trunk (e.g., eth0 is the
trunk, eth0.20 the interface with the '20' vlan tag).
Then it would add the
I don't know how libvirt would need to be extended to be able to
properly 'manage' those 802.1q-enabled virtual switches. Another
question would be how libvirt-CIM would support this.
Once libvirt provides the network interface functionality, then the
libvirt-CIM developers can map it into
10 matches
Mail list logo
