On Wed, 2005-08-31 at 13:01 +0100, Ian Pratt wrote:
One fix would be for you to just hack the hotplug script. Another,
slightly better, way would be to grep around in xend's
config script
to find out what script should be run, and call that. We might even
take that as an interim patch.
Can you confirm that things work OK if you rename vif-route to
vif-bridge?
Any idea when this would be implemented?
Getting this cleaned up is important.
Made no difference.
These are the interface I get on Domain-0
eth0 configured and up
lo configured and up
peth0 configured and up ipv6
vif0.0 configured and up ipv6
xen-br0 configured and up cole of eth0 but HWaddr FE:FF:FF:FF:FF:FF
The all foxes mac address on xen-br0 is a little odd to say the least.
This is with no network related configs for the xm domain.
If I add a vif line after the fact kill everything and restart I still
see xen-br0 with an all foxes mac address.
In both cases netstat -rn only shows xen-br0 devices.
Will try another reboot and see what happens.
If their is any specific configs you want me to try in the domains
config let me know.
Still see all the
xend ERROR (process:37) [network-bridge] errors in the xend.log as well.
Regards,
Ted
14 messages in com.xensource.lists.xen-develRE: [Xen-devel] BUG? domu network in...
