Recent content by darkpixel

Funny: > Starting with v197 systemd/udev will automatically assign --->predictable<--, stable network interface names for all local Ethernet, WLAN and WWAN interfaces. From Proxmox: > Upgrading kernels always carries the risk of network interface names changing, which can lead to invalid...

Sorry--the forums didn't alert me to all the replies. Yes, the VMs (according to top) are using around 1/4 of the memory on the box. There's plenty of "avail mem" (plenty being 10-20 GB) around the time it happens. VMs aren't using ballooning or anything--just a fixed amount of memory. Root is...

Yeah...the horrible part about it is (on ~40% of the systems I manage) it boots to the login prompt....but if you type in 'root' and hit enter, it hangs for 30-60 seconds then quickly flashes some error message before immediately clearing the screen and returning you to the login prompt. Not...

Bug created: https://bugzilla.proxmox.com/show_bug.cgi?id=5311

Yeah, we already have a salt state that looks at running VMs and adjusts the score because the "unimportant" VM has the same name and ID at every location. But I guess the "feature-request" tag is pointless and should be deleted in the forum software? ;)

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...

In the past 30 minutes, I had two more offices die, had to drop the memory from 16 GB to 8 GB and boot the VM back up. I'm also seeing a pattern where this OOM kill and restart of the VM is frequently followed an hour or so later by the hypervisor spontaneously rebooting with nothing in syslog...

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 just ran into this on one of my boxes. It had been in production for years, and suddenly stopped working after upgrading to the latest proxmox. Turns out the CPU battery died and apparently the BIOS reset at some point during rebooting and disabled the Intel VT extensions.

Same issues. Getting ~21 kB/s. Traceroute from Washington state ends up in Germany. Are there 'closer' servers?

Odd. Maybe you should just stop posting on forums. In fact, maybe Proxmox will just delete this forum since no one is paying for it. No one is demanding free support. We are posting about issues we've run into, hoping someone who is more knowledgeable can point us in the right direction or...

Since some of us here don't know the intimate details of everything from the Linux Kernel, to virtualization, to BIOS, etc...we're mostly hoping that someone with a bit more knowledge can point us in the right direction or give us troubleshooting tips. As a counter-argument though: If you're...

I'm not blaming Proxmox. I'm saying it appears to only *occur* when running as a VM under Proxmox. It doesn't occur on any of the physical workstations. It doesn't occur on the vSphere servers we manage. It doesn't occur under hyper-v. It only occurs running under Proxmox (qemu/kvm/whatever)...

We are running in to the same issues. We host a handful of Linux and Windows VMs for clients. Linux, and Windows Server 2012 have no issues. Specifically Windows 7 and Windows 2008 will randomly decide not to boot (going into System Recovery) after installing Windows Updates. I've tested with...

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...