Hi Walter,
I`d be very interested in your config files.
I`m hitting the wall with a reliable bridging configuration for a
dualhomed dom0 for a couple days now:
either xenbr0 or xenbr1 come up, the vif counter in dom0 increases,
the w2k3 detects a new nic (Lan5, currently) - each time the vm is
started. And of course no networking from domU to dom0.
After i have tried anything, even specifically naming the vif in the
configuration of the vm, but to no avail.
in the vm configuration i have:
vif = [ 'vifname=vm1, type=ioemu, mac=00:16:3e:00:0e:11,
bridge=xenbr0, model=pcnet' ]
but it results always in log entries like the following:
kernel: ADDRCONF(NETDEV_UP): vm1: link is not ready
kernel: xenbr0: port 2(vm1) entering disabled state
kernel: device vm1 left promiscuous mode
kernel: audit(1181574843.162:9): dev=vm1 prom=0 old_prom=256 auid=4294967295
(Without the vifname directive, the above lines show the vif name).
On 6/10/07, Schober Walter <Walter.Schober@xxxxxxxxx> wrote:
Hi Tony!
Maybe not a solution to your problem, but it may help you to reach the
target:
...
(I can provide the infos, if you
need them).
..
Br
Walter
many thanks in advance,
Dirk
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|