[Xen-users] network up after create, but down after reboot on domU

["J. R. Harvey" <harvey@xxxxxxxx>]

I'm running 2.6.18-5-xen-amd64 on debian etch with the 
xen-hypervisor-3.0.3-1-amd64 package installed.
When I create a domU with the vifname specified in the config file, 
it works fine after it's created, but if it is rebooted from domU or 
xm reboot vpsname, the network doesn't work when it comes back up. 
If I shutdown the domU and create it again with xm create vpsname, 
the network works fine again.
If I do not specify the vifname in the config file, the network comes 
back up after a reboot.
Does anyone know why specifying the vifname in the .cfg file might 
cause the network to not work on domU after a reboot?


a config with vif specified this way works after reboot:

vif = [ '' ]

this does not work after reboot:

vif = [ 'vifname=vps25vif' ]

from the kern.log, it looks like the vif comes up, but then goes 
right down again.  I don't see an error in the xend.log.
from kern.log:

Nov 20 01:33:39 xenmachine kernel: device vps25vif entered promiscuous mode
Nov 20 01:33:39 xenmachine kernel: audit(1195518820.379:27): 
dev=vps25vif prom=256 old_prom=0 auid=4294967295
Nov 20 01:33:39 xenmachine kernel: xenbr0: port 4(vps25vif) entering 
learning state
Nov 20 01:33:39 xenmachine kernel: xenbr0: topology change detected, 
propagating
Nov 20 01:33:39 xenmachine kernel: xenbr0: port 4(vps25vif) entering 
forwarding state
Nov 20 01:33:39 xenmachine kernel: device vps25vif left promiscuous mode
Nov 20 01:33:39 xenmachine kernel: audit(1195518820.707:28): 
dev=vps25vif prom=0 old_prom=256 auid=4294967295
Nov 20 01:33:39 xenmachine kernel: xenbr0: port 4(vps25vif) entering 
disabled state
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users