Hi, guys. During domain creation from xml like this: <domain type="openvz" id="3005"> <name>3005</name> <memory>131072</memory> <currentMemory>131072</currentMemory> <vcpu>1</vcpu> <os> <type>exe</type> </os> <devices> <filesystem type="template"> <source name="altlinux-4.0"/> <target dir="/"/> </filesystem> <interface type="bridge"> <source bridge="vzrb0"/> <target dev="veth3005.0"/> </interface> </devices> i get veth3005.0 on a HW node connected to virtual bridge vzbr0 and eth0 inside a container. So that annoying bug with confused <source> and <target> tags seems to be fixed. Thanks for that! But mac generation still seems to be an issue, caz mac of eth0 and veth3005.0 are the same: [root@alt-03 ~]# cat /etc/vz/conf/3005.conf | grep NETIF NETIF="ifname=eth0,bridge=vzbr0,mac=52:54:00:97:72:8E,host_ifname=veth3005.0,host_mac=52:54:00:97:72:8E" So when i connect two containers via bridge they cannot "talk" to each other due to macs conflict. Can something be done to improve mac generation behaviour? Version I use at the moment: [root@alt-03 ~]# rpm -qa | grep libvirt libvirt-python-0.5.0-alt1 libvirt-0.5.0-alt1 libvirt-devel-0.5.0-alt1 And one more not an OpenVZ-specific question: I am working on a project using python and python API bindings in libvirt. I don't see a python method for virNetworkCreateXML: Traceback (most recent call last): File "<stdin>", line 1, in <module> AttributeError: class virConnect has no attribute 'networkCreateXML' There are two methods for virNetworkDefineXML and virNetworkCreate separately: ['__call__', '__class__', '__cmp__', '__delattr__', '__doc__', '__get__', '__getattribute__', '__hash__', '__init__', '__new__', '__reduce__', '__reduce_ex__', '__repr__', '__setattr__', '__str__', 'im_class', 'im_func', 'im_self'] ['__call__', '__class__', '__cmp__', '__delattr__', '__doc__', '__get__', '__getattribute__', '__hash__', '__init__', '__new__', '__reduce__', '__reduce_ex__', '__repr__', '__setattr__', '__str__', 'im_class', 'im_func', 'im_self'] Is networkCreateXML missed? ________________________________ This message (including attachments) is private and confidential. If you have received this message in error, please notify us and remove it from your system.