* Volker A. Brandt ([email protected]) wrote:
> > Ok, thats interesting. Currently I use a Xvm from 3.4 gate based on
> > build 122.
> 
> So you are newer, since I use the xVM that comes with SXCE 122:
> 
> v3.3.2-xvm chgset 'Tue Aug 18 03:21:41 2009 -0700 18433:7e735e9e9bf6'

I'm using the stock xvm from 121.

> > Currently no port aggregation due to other reasons.
> > Futureplan includes the idea to use vlan trunking (thats afaik the term)
> > maybe in combination with port aggregation if possible, need to check
> > this and start testing the idea.
> 
> When you have done some testing I would like to hear the results! :-)

It's been a couple of weeks since I played around with this, so my
mental notes might be a little out of whack.

I'm using LACP on 2 Intel NIC's 
# dladm show-phys
LINK         MEDIA                STATE      SPEED  DUPLEX    DEVICE
e1000g1      Ethernet             up         1000   full      e1000g1
e1000g0      Ethernet             up         1000   full      e1000g0
# dladm show-aggr
LINK            POLICY   ADDRPOLICY           LACPACTIVITY  LACPTIMER   FLAGS
aggr1           L4       auto                 active        short       -----

On top of that I'm using VLAN's (vnic's with vlan option) to do security 
separation between network segments.

# dladm show-vnic
LINK         OVER         SPEED  MACADDRESS        MACADDRTYPE    VID
xvm3_0       aggr1        1000   0:16:36:72:ff:cf  fixed          11
xvm4_0       aggr1        1000   0:16:36:72:ff:d1  fixed          11
wifi0        aggr1        1000   2:8:20:49:a6:9e   random         20
wan0         aggr1        1000   2:8:20:cc:43:e1   random         99
public0      aggr1        1000   2:8:20:a5:39:fa   random         100
server0      aggr1        1000   2:8:20:16:ae:a2   random         11
xvm27_0      aggr1        1000   0:16:36:72:ff:df  fixed          11

As I recall I was unable to get network traffic running for HVM guests 
(Windows, FreeBSD, Debian) when using the vlan option for vif-vnic. 
Using tcpdump in the domU I verified that the domU was receiving traffic
and sending traffic (arp requests and responses) but I never saw them in
dom0. Creating a static arp on the domU for another host on the same
vlan enabled me to ping that host with a RTT of 0.000ms.
Anyway I finally gave up and started using etherstub's and routing on 
dom0 instead. Not optimal but at least it works.

BTW It works perfectly for debian-lenny pv domU's. Hopefully it will
work for FreeBSD's XEN port when/if that ever happens....
-- 
Bjørn Connolly
Mostly RFC3514 compliant.
_______________________________________________
xen-discuss mailing list
[email protected]

Reply via email to