Hello there,
A couple of weeks ago I~ posted that xen was breaking
'host' and other routing commnds. This is still true. I just tried the
2.6.12-1.1454_FC4xen0 rpm from 'riel'.
One suggestion I got was 'strace route', so I tried this.
By comparing normal and xen-enabled results, the first change I see is
that when "my-gateway" appears on the normal host, the xen enabled
xernel finds "my-machine" appearing instead. Somehow it is trying to
use itself as a gateway.
I do see the following xen eth setup in /var/log/messages
Sep 21 12:54:31 heplnw8 kernel: Bridge firewalling registered
Sep 21 12:54:32 heplnw8 kernel: device vif0.0 entered promiscuous mode
Sep 21 12:54:32 heplnw8 kernel: device peth0 entered promiscuous mode
Sep 21 12:54:32 heplnw8 kernel: xen-br0: port 1(vif0.0) entering
learning state
Sep 21 12:54:32 heplnw8 kernel: xen-br0: topology change detected,
propagating
Sep 21 12:54:32 heplnw8 kernel: xen-br0: port 1(vif0.0) entering
forwarding state
Sep 21 12:54:32 heplnw8 kernel: e100: peth0: e100_watchdog: link up,
100Mbps, full-duplex
Sep 21 12:54:33 heplnw8 kernel: xen-br0: port 2(peth0) entering learning
state
Sep 21 12:54:33 heplnw8 kernel: xen-br0: topology change detected,
propagating
Sep 21 12:54:33 heplnw8 kernel: xen-br0: port 2(peth0) entering
forwarding state
Can anyone suggest anything?
Thanks,
Bill
