Pkg xen devel - Mar 2013 - Bug#702337: possible documentation issue

It appears that this issue may be a result of documentation problems

When I was having this problem, I had xenbr0 declared in my
/etc/network/interfaces file.  I have now stripped out everything in the
interfaces file except the loopback interface, rebooted, and now my
xcp+openvswitch system appears to be adding domUs to the bridge
automatically, so the problem is no longer there.

Specifically, I had originally configured my system following the advice
from /usr/share/doc/xcp-xapi/README.Debian.gz:

"4.2/ Configure network to use a bridge xenbr0
The following will convert a static IP configuration on eth0 to a bridged
physical interface using xenbr0:
sed -i "s/allow-hotplug eth0/auto xenbr0/" /etc/network/interfaces
sed -i "s/iface eth0/iface xenbr0/"/etc/network/interfaces
echo "  bridge_ports eth0" >>/etc/network/interfaces

..."

Various wiki pages also propose putting xenbr0 in /etc/network/interfaces

However, I also found this contradictory advice:

http://lists.xen.org/archives/html/xen-api/2012-05/msg00102.html
"Have you configured eth0 with xe pif-reconfigure-ip [2] ? Doing it
manually
(e.g. in /etc/network/interfaces) won't do, as it's xcp-networkd who
configures
networking after boot. Leave nothing but the loopback interface config
in the
interfaces file."

Using this latter approach solves the problem.