Search results

Hi all, After several years of good experience in running proxmox on desktop and home machines as kind of home servers, I just decided to buy my first real enterprise server equipment from second hand ebay. I choose a used: HPE ProLiant DL380 Gen9 BIOS: P89 v2.80 (10/16/2020) CPUs: 2x Xeon...

Thank you! So the goal, in having a ballooned RAM for this VM can't be reached. Just to be sure... Do you know, is this just for the VM that uses PCIe passthrough or does this requirement apply to all VMs on that VE? As you have written I understand that this just applys to the VM with...

Thanks for your answer. To the first point. I have not seen this behavior that win10 fills up 31GB of RAM right after boot. To ballooning... Yes that's the behavior I also have seen in a kind. I was not expecting that ballooning already kicks in right after boot, I just wanted to explain why...

Hi all, The problem is that after a fresh boot the Win10 loads and loads more RAM until about 98%. Then the system still runs stable but the VM is wasting huge RAM that I want to share with other VMS by ballooning. Here is my system: Proxmox VE 8.1.3 64GB RAM VM: Win 10 Enterprise 22H2 VirtIO...

Hi Aaron, Thank you again for your patience during training. xD (can recommend) I was able to ping all nodes from each other. In this case it is my home setup so no special networking. Just one NIC for each node and corosync and mgmt should run on the same network. However, it works again and...

Hmmm... I rebooted node 2 and node 3 and suddly everything works fine again. Learned nothing today. -_-

Hi, Once again, it seems that I messed up something in my config. I had troubles in the past in getting instabilities with corosync/cluster config. One time I hade issues with a bad network cable and one time the ssh keys were out of sync. This time the problem seems to be different. I can...

Thanks, I think I have identified the disks over the logs. The strange thing is that one is a HDD and one is a SSD for storage tiering and cache. I now replaced the HDD only and currently rebuilding the parity but it seems to work just fine. Not sure why the SSD also had mentions in the logs...

Hi, I have a proxmox running with a WS2022 VM. This VM bundles multiple physical disks as a storage space. That runs quite well until now. I was getting the yellow sign with "io-error". Since I hear some strange noise from the disks I guess one of the disks fails but I am not sure which one...

Thanks for the note. I think I now have managed to get everything running even on the problematic network interface. Although I had a pretty stable and good ping I noticed that something has been wrong with my ethernet connection. First, I noticed that the router degraded the connection to...

I just double checked my latency between the original networking ports that were not working. In my opinion that does not look that bad. In https://pve.proxmox.com/wiki/Cluster_Manager it is written that the default cluster config requires 5 ms and the worst case is 10 ms. How can I rise this...

Finally... After days of investigation and numerous reinstalls and config hacks, I think I had a breakthrough. I moved the second PC physically next to the first one and they are now both connected directly to the switch next to each other. And now, suddenly the cluster join is working again...

Thanks for your input. I successfully upgraded Proxmox 8. Still the same issue. How did you managed to manually copy the certificates? When I join the second node to the first one's cluster the problem begins. Can't access the web interface of node2. I can access via SFTP but I can't write to...

I have to reopen this. It was working well and I successfully migrated one vm to the second node but after about one day the cluster was broken again. It is getting a little bit annoying... Ok, back to the beginning and going through what could be wrong: 1.) Time Sync I manually configured a...

I think I solved the problem myself... Executing the following on both nodes has solved the problem: rm -f /etc/pve/pve-root-ca.pem /etc/pve/priv/pve-root-ca.* /etc/pve/local/pve-ssl.* pvecm updatecerts -f Don't ask me why, I am sure an expert could tell... For me it is not understandable how...

I just did some further testing: I swaped the network cable to be sure. I manually copied the /etc/pve/nodes/LayProx2/pve-ssl.pem file from the LayProx2 to the LayProx machine. Now the error message in "Datacenter" -> "Cluster" disappeard but the connection still does not work. I also tested...

yeah, I do know that nomally 3 nodes are required. I was using 2 nodes before since is still quite handy to migrate vms between the two nodes.

Hi all, I think the whole mess came up because I tried to setup a cluster between two different pve versions, but I am not sure about that. I managed to upgrade both machines to 7.4-16, but still the system seems to be messed up. The cluster join still fails. This is what I get: Cluster...

Ok, I figured out how to remove the directories. The trick was once again, to remove the whole cluster with rm -f /etc/pve/cluster.conf /etc/pve/corosync.conf rm -f /etc/cluster/cluster.conf /etc/corosync/corosync.conf rm /var/lib/pve-cluster/.pmxcfs.lockfile After reboot the cluster disappeard...

Hi there, I think I am currently in a similar problem. The whole mess kind of started when I tried to create a cluster between two different versions of pve nodes. I have learned now and tried to cleanup everything and apgrade both nodes. now they are on same version 7.4-16 . However I still...