I finally found (my) error - had nothing to do with the cluster reconfiguration. When it did the same thing after deleting one node from the cluster and cleaning its clusterconfiguration I finally realized that as it is a network issue - might...
I dont understand this, I can successfully configure replication of vms in both directions - they successfully finish. I also wasable to successfully migrate a node which was started at node2 to node1.
But as soon as I start a vm on node I the...
After having installed and configured a separate cluster network again, it first seems everything ok on pvecm status. And one node also starts its vms that are set to autostart.
Changed /etc/corosyncd/corosync.conf and /etc/pve/corosync.conf...
It looks like everything is ok though I dont know about the votes, as I had put expected 1 while troubleshooting.
root@PVE002:~# pvecm status
Cluster information
-------------------
Name: PVExCL001
Config Version: 6
Transport...
I made some progress. By stopping corosync pvestad and pve-cluster service and issuing a pmxcfs -l I was also able to edit /etc/pve/corosync.conf which I thought came in handy as the server needs some physical rebuilding for the clusternetwork...
I migrated all guests to the remaining node, and removed the empty node from the cluster. I then tried to add a new pve server to the cluster. Unfortunatelly I had not deleted the entry of the removed node from known_hosts file on the remaining...
Hello Johannes,
our company has different sites - connected by a dedicated 500 Mbit Wan provided by our internetprovider. No there is no dedicated connection for backup, so its running on the same network link. As written in the opening post I...
Hi all - first of all I want to express a big thank you for your great products pve and pbs which serve us very well. Keep up the impressive work.
While testing a multiple pbs setup for our company we discovered a severe problem with one of our...
Hello and thanks for posting - thats indeed what I asked myself too but thought, would be better to first ask and learn what would be the best way to optimize performance while not running into probs. Esp. the v3 ones seem all supported, but what...
Hi,
why not choose any of the higher versions? They expose AVX2.
x86-64-v3 exposes these flags compared to x86-64-v2-AES:
+avx, +avx2, +bmi1, +bmi2, +f16c, +fma, +movbe, +xsave
x86-64-v4 exposes these additional flags compared to x86-64-v3...
Hi, I understand that setting host in cpu type has its limitations esp. when using different hardware, but as long as the hardware has a minimum standard it could make sense to get most performance out of the guests.
I stumbled across this a an...
Edit to add - while porting another winxp system, I can report the following about the virtio versions:
- newest successfully installing most drivers (QXL GPU, Balloon, Serial, Virto Serial and Network Driver) from 0.1.248 ISO. The newest...
Thanks @Blonov but I managed without those links to keygen downloads n stuff.
Basically the two last links, I posted helped me to fix the issues remaining. I had to first boot into safemode with command prompt in order to be able to manipulate...
yes, "wim" capture/restore from another Windows 7 or 10 more easy,
then need correct bootsect /nt52 afterward.
As already said, that's Windows things, which existed before virtualization, not really a Proxmox issue.