Original article: http://hi.baidu.com/chenghui2050/blog/item/80cb323df7dcd9e73d6d97e3.html
This is the workflow of the xen network bridging model I mentioned in an email from an Italian. The translation is below for future use.
When xend is started, with the default configuration (in/etc/xen/xend-config.sxp), It'll execute/etc/xen/scripts/network-Bridge to re-configure yonetworkur ing.
When the xend process is enabled, the process will be based on the content in the default configuration file/etc/xen/xend-config.sxp, run the/etc/xen/scripts/network-bridge script to configure your network.
It'll rename the physical eth0 interface to peth0, change it's MAC address to Fe: FF: ff, and then create a virtual ethernet interface called eth0, configure it with the real MAC address, and bridge both of those interfaces to xenbr0 bridge.
It will rename your eth0 to peth0, and change the MAC value of eth0 to Fe: FF: ff. Then create a new virtual network interface named eth0 and configure it to have a physical MAC address, then, a bridge is established between the peth0 and eth0 interfaces and xenbr0 interfaces.
This way the virtual eth0 interface shoshould have a real Mac, and it can be used for dom0 management, and at the same time allow other VMS/Domus to share the physical Ethernet interface by using xenbr0 bridge.
Therefore, in this way, the virtual eth0 interface will have a physical MAC value, and use the function of surfing the Internet in domain0, it also allows domainu to use the physical network interface with domain0 through the xenbr0 bridge interface.