[Xen-devel] Network still broken, new issue as well , 7468:17a9f111fa93

[Ted Kaczmarek <tedkaz@xxxxxxxxxxxxx>]

xen_changeset : Fri Oct 21 13:51:42 2005 +0100 7468:17a9f111fa93

Tyan 2462 SMP Athlon - FC4 dom0


Not one vif get mapped to the bridge, but the bridge otherwise appear to
work fine with other nodes on the broadcast domain.


I am also seeing a new issue as well. 

I see 2 vifs for a domU that has nics = 1 , this happens on 4 out of 10
domU's. grepping my configs make me think that something has changed the
way they are interpreted, all the the domU's using mac, bridge have 2
vifs, where the one that ony have mac declared have 1 vif.


grep nics idom*
idom1:nics=1
idom10:nics = 1
idom2:nics = 1
idom3:nics = 1
idom4:nics = 1
idom5:nics = 1
idom6:nics = 1
idom7:nics = 1
idom8:nics = 1
idom9:nics = 1

 grep vif idom*
idom1:vif = ['mac=AA:00:00:00:00:17','bridge=xen-br0']
idom1:#vif = ['mac=AA:00:00:11:11:12','bridge=xen-br0',
'mac=AA:00:00:11:11:22','bridge=xen-br1',
'mac=AA:00:00:11:12:22','bridge=xen-br2']
idom1:#vif = ['mac=AA:00:00:11:11:11' , 'bridge=xen-br0' ,
'bridge=xen-br1' , 'bridge=xen-br2']
idom1:#vif = ['mac=AA:00:00:11:11:11' , 'bridge=xen-br0' ,
'bridge=xen-br1' ]
idom1:#vif = ['mac=AA:00:00:11:11:11','bridge=xen-br0' ,
'mac=AA:00:00:11:11:12', 'bridge=xen-br1']
idom1:#vif = ['mac=AA:00:00:11:11:11' 'mac=AA:00:00:11:11:12'] BAD, eth1
won't come up

idom10:#vif = [ 'mac=aa:00:66:00:01:08, bridge=xen-br0',
'mac=aa:00:66:01:01:08, bridge=xen-br1', 'mac=aa:00:66:02:01:08,
bridge=xen-br2' ]
idom10:vif = [ 'mac=AA:00:00:00:01:08, bridge=xen-br0' ]

idom2:vif = ['mac=AA:00:00:00:01:01']

idom3:vif = ['mac=AA:00:00:00:01:02' , 'bridge=xen-br0']

idom4:vif = ['mac=AA:00:00:00:01:03' , 'bridge=xen-br0']

idom5:vif = ['mac=AA:00:00"00"01:04' , 'bridge=xen-br0']

idom6:vif = [ 'mac=AA:00:00:00:01:05' ]

idom7:vif = [ 'mac=AA:00:00:00:01:07' ]

idom8:vif = [ 'mac=AA:00:00:00:01:08' ]

idom9:vif = [ 'mac=AA:00:00:00:01:09' ]

list_vm_nets_backends
idom1
(backend/local/domain/0/backend/vif/1/0)
(backend/local/domain/0/backend/vif/1/1)

idom2
(backend/local/domain/0/backend/vif/2/0)

idom3
(backend/local/domain/0/backend/vif/11/0)
(backend/local/domain/0/backend/vif/11/1)

idom4
(backend/local/domain/0/backend/vif/4/0)
(backend/local/domain/0/backend/vif/4/1)

idom5
(backend/local/domain/0/backend/vif/5/0)
(backend/local/domain/0/backend/vif/5/1)

idom6
(backend/local/domain/0/backend/vif/6/0)

idom7
(backend/local/domain/0/backend/vif/7/0)

idom8
(backend/local/domain/0/backend/vif/8/0)

idom9
(backend/local/domain/0/backend/vif/9/0)

idom10
(backend/local/domain/0/backend/vif/10/0)



I have to get caught up on the archives as I know lots of network
related changes are in progress. Would be great if we could get a little
change summary, I have tried to throw some kind of user help doc
together but you guys are like rabbits :-)

IMHO the configs should start to get stricter as well, right now one can
get away with spaces anywhere it seems, and until today it didn't matter
if I specified mac or mac/bridge. Same goes for many other options such
as cpu = -1, etc.. In the past I have always seen this come back to bite
you in the a@@. If the rules for the config get tighter, their is less
room for error across the board.

Regards,
Ted


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel