Search results

Anyone?

And some ICMP tests: OPENVZ VETH: simple icmp: root@serv1:~# ping -q -s 1 -f 192.168.110.173 -c 100000 PING 192.168.110.173 (192.168.110.173) 1(29) bytes of data. --- 192.168.110.173 ping statistics --- 100000 packets transmitted, 100000 received, 0% packet loss, time 52435ms ipg/ewma...

i did iperf test on 1GB link: openvz veth: # uname -a Linux 2.6.32-37-pve #1 SMP Wed Feb 11 10:00:27 CET 2015 x86_64 x86_64 x86_64 GNU/Linux ..... [SUM] 0.0-30.1 sec 3.24 GBytes 925 Mbits/sec ..... [SUM] 0.0-30.1 sec 3.23 GBytes 923 Mbits/sec ..... [SUM] 0.0- 2.5 sec 274 MBytes 927...

Hello! I have to implement a very hight load network router on a virtual machine and i have some doubts about which is a VM i need to use. I'd like to use openvz, but i don't know who the best in network perfomance kvm virtio or veth openvz? Can you advice me?

Will you do this, if criu will be stable?

Did you implement live migration for lxc ?

OK! I solved the problem. If you use the network interface as a bridge, you must turn off multicast_snooping on a bridge interface. example: echo "0" > /sys/class/net/vmbr0/bridge/multicast_snooping and multicast will work normally: n2 : unicast, seq=1, size=69 bytes, dist=0, time=0.160ms...

oh...really..i'm sorry. what is the problem on 4.2 kernel in bridge?

I have same problem too root@n1:# pvecm add 172.16.1.66 The authenticity of host '172.16.1.66 (172.16.1.66)' can't be established. ECDSA key fingerprint is da:51:f3:18:40:b0:f0:81:4b:1c:92:a1:22:76:c3:61. Are you sure you want to continue connecting (yes/no)? yes root@172.16.1.66's password...

Proxmox 3.4 and nfs very bad idea. I saw too much forum posts with this bug. Why developers doesn't fixing this bug, i dont know. i have same issue too. i tried to mount nfs share with soft option, but this didnt help. Next i try mount remote server with SSFS (fuse driver) and this really...

i have same problem. disable and enable ipv6 in sysctl didn't resolve issue.

Hello! I have cluster with 10 nodes and all nodes red in web interface. root@node0:~# pvecm status Version: 6.2.0 Config Version: 10 Cluster Name: Cluster0 Cluster Id: 57240 Cluster Member: Yes Cluster Generation: 5140 Membership state: Cluster-Member Nodes: 10 Expected votes: 10 Total votes...

hello! i have a problem with create some interface to VM. Why proxmox was create wrong interface with name vlan3102 ? Maybe should create eth0.3102 ? The problem occurs only with the vlan 3102. Any ideas? root@node2:~# cat /etc/pve/nodes/node2/qemu-server/205.conf bootdisk: virtio0 cores: 1...

# ethtool -K eth0 gso off cure the problem

Hello! I have a cluster with 6 nodes. I created CT on node1, but in /var/log/syslog more errors: Apr 2 10:25:01 node1 kernel: CT: 109: started Apr 2 10:25:02 node1 kernel: device veth109.0 entered promiscuous mode Apr 2 10:25:02 node1 kernel: vmbr0: port 2(veth109.0) entering forwarding...

Re: Create VM failure after upgrade to 3.4 Why proxmox updates not all packages during the upgrade? root@node0:/storage/gvz/brick1/images# dpkg -l fuse pve-cluster pve-qemu-kvm qemu-server Desired=Unknown/Install/Remove/Purge/Hold |...

Hi! Please, help me solve the problem! I upgrade proxmox VE 3.1 to proxmox VE 3.4. After reboot VM dont create. Error: root@node1:/mnt/pve/GlusterVolume0-1-3# pveversion -v proxmox-ve-2.6.32: 3.3-147 (running kernel: 2.6.32-37-pve) pve-manager: 3.4-1 (running version: 3.4-1/3f2d890e)...

Re: GlusterFS fail after upgrade from 3.1 to 3.4 Problem solved! If u use glusterfs-server on proxmox node, u r need manually update glusterfs-server packages. cd / wget http://download.proxmox.com/debian/dists/wheezy/pve-no-subscription/binary-amd64/glusterfs-server_3.5.2-1_amd64.deb -O...

Hi! Please, help me solve the problem! I upgrade proxmox VE 3.1 to proxmox VE 3.4. After reboot gluster dont work. i try # gluster peer status but gives an error: gluster: symbol lookup error: gluster: undefined symbol: xdr_gf1_cli_probe_rsp. strace - http://fpaste.org/193676/14255370/...

Its work! Thank you! ;)