Search results

Yes, but it seems that hot migration from 5.15 to 6.2 works (that was my point). Thus this allow to upgrade to 6.2 with no need to stop the VMs.

I had the same problem with proxmox v7.4-17 and kernel 5.15: serv1 : Intel(R) Xeon(R) CPU E5-4620 serv2 : Intel(R) Xeon(R) Silver 4310 Migrations from serv1 to serv2 works, but migration from serv2 to serv1 results in VM freeze (actually debian ones but not centos). After upgrading to...

Hi, Is there a way to specify the default bridge selected on new VM creation (not vmbr0) ? Indeed, I have different bridge (for different vlans) thus vmbr0 is not the bridge I use generally. Then when I create a new VM I need to change the bridge (because vmbr0 is selected by default). Is it...

Hello, I just upgraded from version 4 to 5 and I got some error messages in /var/log/syslog : Aug 30 17:01:56 virt113 rrdcached[1531]: queue_thread_main: rrd_update_r (/var/lib/rrdcached/db/pve2-vm/119) failed with status -1. (/var/lib/rrdcached/db/pve2-vm/119: Function update_pdp_prep, case...

I got the point !!!! On our old cluster, all nodes were configured as igmp querier (/sys/devices/virtual/net/vmbr0/bridge/multicast_querier was set to 1) But in the new cluster, it was set to 0 (so no querier). I still have to check, but I am pretty convinced that igmp querier was not activated...

Hi, I tryed what you suggested (pvecm delnode nodename for all the machines already reintalled in the new cluster).... but it didn't solve the problem ! After a while the new cluster went down !

I shutdowned one of the two remaining machines in the old cluster and then unplug the network cable of the last one. The new cluster went wrong : # pvecm status Quorum information ------------------ Date: Tue Feb 28 12:26:49 2017 Quorum provider: corosync_votequorum Nodes...

Hi, Thanks for your answer. Yesterday night I already tryed to stop all the services on the old cluster (service cman stop, service pve-manager stop, service pve-manager stop, etc...) and it didn't trigger anything on the new cluster ! For now, I still keep 2 nodes up on the old cluster (to have...

Hi, I had a 8 nodes proxmox v3.4 cluster (named LPNHE-CLUSTER) To migrate to v4, I did the following : - Migrate all VM out from node 1 and 2 - Shutdown node 1 and 2 and reinstall in v4 with new name and IP - create new cluster (with name different from the old v3 cluster, i.e. new name is...

Same problem here. Migrating VM from proxmox 3 to 4. Most of the VM with E1000 shows errors !!!