Kvm+openvz together — how to solve problems collaboration network?

Put kvm and openvz on the same machine, containers, and the machine itself worked like norms. Then I noticed the network has become unstable and completely disappear. After reboot some time the norms, then problems again. In the stat server traffic has grown like a DDoS. In the logs noticed
device ent0 entered promiscuous mode
device vnet0 entered promiscuous mode
it looks like the traffic began to collect because of this regime.
Disabled libvirtd, libvirtd-guests , overloaded - all norms! If you just disable those services are not helping, only after a reboot.
Containers, kvm, openvz, and core nodes of different white ip.
What is this? They are not compatible at all? Maybe there are some features network settings when working together?
July 12th 19 at 16:51
3 answers
July 12th 19 at 16:53
No wonder they moved down the roof. If you want Frankenstein, to run OpenVZ inside one of virtualos.
July 12th 19 at 16:55
Seem to have implemented some kind of Trojan in kvm-dev and it scored network. Hanging unknown demon, eats the whole CPU.
July 12th 19 at 16:57
Wait a little while Virtuozzo 7 will finish. And that's OpenVZ and KVM out of the box and at the same time.

Find more questions by tags KVMCentOSOpenVZ