Search results

  1. L

    multicast problem after upgrade from 1.8 to 1.9

    Ok i will attempt to secribe the problem. could you give me which version of openvz kernel is used in pve2.6.32-4, -6 and -7. Thks
  2. L

    multicast problem after upgrade from 1.8 to 1.9

    OK we have extracted libs and scripts to run the tool alone. We have tested this extract from another server and the result is the same. The guest doesn't receive the packet ans is blocked for five minutes. The probleme, here, is now reproducible. I can send this archive in order you can test...
  3. L

    multicast problem after upgrade from 1.8 to 1.9

    comparing packets i can't see differences....... Just the IP ID field which always set to 0 with oracle tools and random number for netcat. We have used tcpreplay tool in order to replay the packet captured from oracle tool. In this case, the IP ID field is set to 0, and all worked fine, the...
  4. L

    multicast problem after upgrade from 1.8 to 1.9

    my problem is the error appear only with the oracle rwdiag tool...... It's always reproducible with this tools but you can't install all the oracle products to reproduce this test :) I have captured the data sent from the rwdiag tool and resend the data via netcat using the same ip/udp/src/dest...
  5. L

    multicast problem after upgrade from 1.8 to 1.9

    We have "identified" the problem. All work fine with 2.6.32-4-pve kernel. We have tested with 2.6.32-6-pve kernel and that doesn't work anymore. We have tested with the new 2.6.32-7-pve kernel and that doesn't work anymore. Two questions about this problem : Is there any problem to...
  6. L

    multicast problem after upgrade from 1.8 to 1.9

    Perhaps a problem at the kernel level..... we run the 2.6.32-6-pve kernel. Can anyone confirm that i can revert to 2.6.32-4-pve kernel just rebooting the server and don't modifying other pve packages ? I'm running only kvm guests. Thks
  7. L

    multicast problem after upgrade from 1.8 to 1.9

    In order to resolve the problem we have disabled bonding at the proxmox host level. We have disabled Multi Link Trunk at the switch level. always the same problem...
  8. L

    multicast problem after upgrade from 1.8 to 1.9

    More information about my problem. In order to exclude a problem in the guest, we have changed the network card driver from virtio to rtlxxx but no change. We make some test and a strange behaviour appear. Consider the following : SENDER : is the multicast packet sender CLIENT : is the...
  9. L

    multicast problem after upgrade from 1.8 to 1.9

    Same problem. We have rebooted the systeme but nothing on the guest interface..... We have disabled iptables, ebtables is not installed. We have tunned bridge using this parameters following bridge howto : # Test bridge/multicast net.bridge.bridge-nf-call-ip6tables = 0...
  10. L

    multicast problem after upgrade from 1.8 to 1.9

    Hi, We have Oracle Application Server on our KVM proxmox vm. This VM is connected to a bridge on the proxmox host (interface bonding + vlan tagging). Our vm should receive multicast packets in order to work with a central database server. All worked fine with proxmox 1.8 but since migration to...
  11. L

    proxmox 1.8 randomly freeze

    I wil update our servers. I always ask the same question :) Can i update from 1.8 to 1.9 each node and migrate kvm vm runnning on 1.8 to 1.9 in order to migrate smoothly. We have now 70 vm in production... Thks for your help
  12. L

    proxmox 1.8 randomly freeze

    The output of the pveversion : # pveversion --verbose pve-manager: 1.8-18 (pve-manager/1.8/6070) running kernel: 2.6.32-4-pve proxmox-ve-2.6.32: 1.8-33 pve-kernel-2.6.32-4-pve: 2.6.32-33 qemu-server: 1.1-30 pve-firmware: 1.0-11 libpve-storage-perl: 1.0-17 vncterm: 0.9-2 vzctl: 3.0.28-1pve1...
  13. L

    proxmox 1.8 randomly freeze

    Hi, We use here a 7 node proxmox cluster. We use only kvm virtual machine on dell m610 servers. We started this cluster two years ago and all worked perfectly. Since two weeks, nodes freeze randomly. The only solution was to reset the server.... Reading the forum i saw that was frequently due to...
  14. L

    Problem after storage misconfiguration on master node

    thks guys !!! that did the trick. we have get again the web interface and all seems good
  15. L

    Problem after storage misconfiguration on master node

    Hi, We use proxmox 1.8 We use lvm storage on shared .SAN We have made a mistake adding disk to vm. After we add the disk in the vm we tag this disk with LVM from the vm without partitionning the fresh disk. Now in the host when we do pvscan or lvscan we can see the "guest lvm" disks. The master...
  16. L

    node nosync after 1.8 upgrade

    ok the problem is resolved. The failing node was not updated, the update procedure has failed and we don't take care about that....... all other nodes are in 1.8 and this node in 1.7. re-updating the node solve the problem. all is synchronized thks for your help
  17. L

    node nosync after 1.8 upgrade

    it seems that the "virt5" node as a specific problem with the "virt4" node..... how work the sync mechanism, i view perl module PVE::etc It seems all is encapsulated on the ssh port, is it correct ? i attempt scp transfert between hosts and all is fine....
  18. L

    node nosync after 1.8 upgrade

    i have removed the file but nothing better. always the same nosync status for the node....
  19. L

    node nosync after 1.8 upgrade

    yep all seems okvirt5:~# pvesm listbackup dir 0 1 83214928 8881340 11%guests lvm 0 1 1572851712 1279275008 81%local dir 0 1 83214928 8881340 11%
  20. L

    node nosync after 1.8 upgrade

    we use shared storage on san. Our vm use LVM disk on san. we use only kvm virtualisation and no openvz. all seems ok on the cluster, all our 50 vms running smoothly..... Deleting the faiing node and adding it again doesn't resolve the problem