OOM killer is a headache in Proxmox 8.x.
Systems that have been running for years under previous versions are now getting OOM killed several times per week.
Every site we manage that uses Proxmox has the VMs--their main Windows Server, a remote access server, and a "vendor" machine that we...
Apparently our internal testing missed this...but we recently (over the holiday break) upgraded a client with 36 locations from Proxmox 7.x to 8.x.
They have been using Proxmox for a *long* time. These servers started out running Proxmox 5.x, and have been upgraded all along the way...
I had three Proxmox 2.x servers. I don't recall the exact version, just that they were NOT the latest.
These servers worked well--specifically we were able to migrate virtual machines between them.
Yesterday we added two new servers to the cluster. We did so by updating the software on the...
I found several threads where people are getting HTTP404's when trying to download templates. The solution was to run 'pveam update' from the command line.
I am unable to download the ticket tracker for a client due to a 404 error, so I ran 'pveam update'. The command took about a second to...
I've run into a strange issue using Proxmox 2.x where it displays the wrong VNC console.
root@kvm1:~# pveversion
pve-manager/2.1/f32f3f46
root@kvm1:~#
Two weeks ago I had this problem and I figured I had just messed something up. I ended up stopping all my virtual machines and rebooting the...
About a week ago I did my usual 'apt-get update && apt-get dist-upgrade' on one of my Proxmox machines and rebooted.
Now the nightly backup is suspending the VM rather than doing a snapshot.
Other than installing the updates, the box hasn't seen changes in several months.
I missed the problem...
I have three proxmox boxes (kvm1, kvm2, kvm3). All the virtual machines are running under kvm using iscsi targets as their storage.
It doesn't seem to matter what host I am transferring to or what guest I am moving--they fail:
kvm3:~# qmigrate --online --verbose 10.47.0.181 109
Mar 22...
I have 3 physical machines clustered together named KVM1, KVM2, and KVM3.
I logged directly into the KVM3 web interface and setup vmbr100 using physical interface eth0.1.
After rebooting KVM3, eth0.1 is correctly brought up and put into the bridge vmbr100.
When I log into the cluster...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.