vif0.0: received packet with own address as source address

[greno]

I just installed FC6 on a machine and I'm seeing this over and over in dmesg:
vif0.0: received packet with own address as source

and .. I"ve got no networking. Can't ping in or out.

My first indicator of a problem is when I tried to apply the updates after first reboot and nothing happened - I mean nothing. No window, nothing. So I went looking for the source of the problem and of course typed dmesg and then saw all these vif0.0 messages.

I"ve been googling this problem for a while and there isn't much out there. There are a couple references to this problem but none of the threads showed a solution. Anyone know what the root cause of this might be? I know it's xen, but where?

[greno]

What's also wierd is that every MAC address is set to FE:FF:FF:FF:FF:FF even eth0. Can this be right? I've reused the same ip that the machine had previously with a normal MAC address. Is this somehow related? Also, in the network part of the setup I told it static ip and gave it gateway and netmask /24 but after the first reboot what I had was two configs:
ifcfg-eth0 which had dhcp config with the FE:FF:FF:FF:FF:FF MAC and
ifcfg-eth0.bak which had the setup that I had defined during the install and my old MAC. Both of them got activated.
After having a lot of trouble shutting down eth0 because the MACs didn't match. I finally copied the eth0.bak over eth0 and restarted eth0 again but it came up with the FE:FF:FF:FF:FF:FF MAC again instead of the one in the eth0 script.

How the DHCP script got into this picture is beyond me. But it sure seems to have messed things up. Maybe this was some xen initial config thing. Again, anyone have any ideas how to fix this?

[greno]

Finally ended up reinstalling FC6. Everything was normal this time. Still do not know what was the cause of the problem. Xen got confused somewhere along the line.