eth0 renamed to eth1, eth2, eth3, ... in domU|
Posted March 6, 2008
domU works fine the first time.
After reboot, eth0 doesn't exist. The xen virtual interface appears as eth1.
After a second reboot, the interface appears as eth2, and so on.
Evidently the gutsy domU, noticing that eth0 had a different MAC address than the "saved eth0 MAC address", assigns a brand new eth# and saves the MAC address with the new interface number.
Alternate solution (offered and preferred by Jonathan Addleman):