OK, finally got rid of the old aliasing.
I briefly saw the peth0 and vif0.0 interface after doing a "service start xend".
I thought, AHA! So, I switched off any IPTABLES stuff and rebooted dom0.
Rebooting should wipe those out until you start xend again. They don't persist over reboots. No peth0 or vif0.0.
Keep in mind that the basic setup actually creates some of these interfaces by renaming existing ones. You'll usually have something like this:
eth0
Then you load the netback driver (if its modularized, otherwise it's always there) and you see:
eth0 veth0 vif0.0
Then you start xend and see:
eth0 peth0 xenbr0 vif0.0
Essentially the veth0 and vif0.0 devices are two ends of the same pipe. It's used to make a fake eth0 that plugs into the software ethernet bridge (xenbr0). peth0 is just the real eth0 renamed. The actual dance goes like this (I may have the order a bit mixed up):
State: eth0 (physical device), veth0 (virtual domain side), vif0.0 (virtual switch side)
1. Create bridge xenbr0.
State: eth0 (physical device), veth0 (virtual domain side), vif0.0 (virtual switch side), xenbr0 (magical management interface for bridge)
2. Plug vif0.0 into xenbr0
State: nothing visibly different
3. Rename eth0 to peth0 and veth0 to eth0 (pull a switcheroo)
State: eth0 (virtual device), peth0 (physical device), vif0.0 (virtual switch side, plugged in), xenbr0 (bridge interface)
4. Move MAC Address, IPs, Routes, etc from peth0 to eth0
5. Plug peth0 into xenbr0
At this point, you have a virtual switch, with a loopback plugged into it and the physical interface plugged into it. All of your logical network configuration has been moved to the other end of the loopback. As domains are added, the end of their network device on this side (vifM.N where M is the domain and N is ethN inside of the domain) is plugged into that same switch. This is a lot of magic and a lot can go wrong. I don't know if this will help you solve your particular issue or not. Warning doesn't sound fatal, and a package called "python-pam" does not exist anywhere on the internet (well, it's referenced as ancient).
I'm not sure if this is a problem. Nothing should be this hard....it makes Microsoft look good (which is almost impossible).
Please don't say things like that. It makes people like me not want to take the time to help you. I mean this in the nicest possible way.
I recommend the little squishy stress balls for expressing frustration.
If you need some one-on-one and can make a phone call (or may a conference over iChat) to the US, contact me off list and I can probably help.
-- Jayson Vantuyl Systems Architect
| 
