Am Wednesday, den 5 December hub Luis Vinay folgendes in die Tasten:
Hi!
> I'm working on adding the 802.1Q vlan suport to Xen. Half of the work
> is done. The idea is that we can specify something like this on the domU
> configuration file:
> vlan = [ 'pdev=eth1, vlanid=123, bridge=xenbr1123',
> 'pdev=eth1, vlanid=100 ' ]
What should that actualy do?
I guess you want to connect vlan 123 from a trunk on eth1 to
xenbr1123. And the next line?
Why not just use the linux way and create vlan interfaces?
e.g.
# vconfig add eth1 123
# vconfig add eth1 100
and then put eth1.123 to xenbr123 and use this?
> perhaps even specify an IP address (I founded this usefull in some
> implementations), and then, as allways:
What's the purpose of the IP here?
[...]
> I'll check if the bridge is already created before connecting the VIF,
> at domU creation, if not bring it up, and when destroying the domU, also
> check if other domU is using the same bridge before shuting it down.
I just create all the vlan interfaces, bondings and bridges via the
networking setup of my OS on bootup so everything is just there.
No need to think about networking stuff after setup once.
> All this raises me some questions:
> - Suggestions/advices regarding on where/how put my code?
> - Could it bring problems if I add this code in 'xen/xm/create.py'?
> gopts.var('vlan', val="iface=IFACE,vlanid=VLANID,vlanbridge=VLANBRIDGE",
> fn=append_value, default=[],
> [...]
I don't speak parseltongue :)
Ciao
Max
--
Follow the white penguin.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home