This weekend was my first experiences with Xen 4.1 and my god man, what a fun use of 14hours... not to mention i destroyed a production zentyal box for its hardware! Scary stuff getting it back up before office hours monday!
Could not get zentyal to install from the iso, only base ubuntu. I credit this mostly to my complete non understanding of debootsrap.
Xen documentation is all over the dam place!!! Xen 4.1+ doesnt run the network scripts like most of the documentation talks about. All config is done via iptables and /etc/network/interfaces.
Bridging is not the end all solution for networking like the docs make u believe. Spent so long trying to track down connectivity issues, when I was bridging a dhcp address from the bridged cable modem..
Nat the external interfaces. Give the bridge a private IP. Port forward all packets on external nic. Masquerade the internal ip adresses on external nic via iptables. Add default route to domUs pointing to the bridge. - why couldnt someone point out the networking intricacies in the documentation and that bridging is basically only a good solution for internal virtualization, not on the perimeter - or for someone that has plenty of public IPs available to them.
Overall, I have learned quite alot from jumping into XenProject with no knowledge of virtualization and only very basic noob knowledge of linux/networking. I turned a xeon v3 box running zentyal only @1% sys utilization (complete waste of resources) into 3 virtual machines that still runs @1%, but get to enjoy all the benefits of a para virtualized environment!
In my opinion, virtualization of Zentyal is the way to go for any type of deployment outside of a home network perimeter box. One can separate the PDC from the rest of the services, and not to mention the benefits of all domUs being stored via LVM.