Search results

Also, just want to say, loving the speed improvements to the GC process. I've gone from a weekly GC that ran for most of a day to a nightly GC that finishes in about 3 hours.

Ben running this update a few days now. Eliminated the errors for my install. Thanks!

I am getting the same phase 1 GC errors now last 3 days since 3.4 upgrade. The number is not growing, first day it was 94 chunks, then next day 56, then last night 52. I definitely have concurrent backup jobs happening. And one of the two daily prune jobs occurs during the GC task.

I believe you are correct that the polling nature of the SNMP monitoring is going to cause slight difference in when each NUT server that's monitoring it would see the UPS transition but the NUT clients do maintain a connection to the NUT server and will see the transition essentially instantly...

The NUT server suggestion is to alleviate the timing problem you pointed out of not all the hosts catching at the same time that the UPS switched to battery. Single source of battery status that all NUT clients can take action on simultaneously.

Not sure what route you took, but I think it’s not ideal to have all the nodes separately monitoring the single UPS. Might be better to have a VM or LXC running the NUT server monitoring the UPS and then have NUT clients attached to that on all the machines you want to shutdown when the grid is...

Hey all, I know this thread is a few weeks old and marked as solved. But since @virtManager wasn't able to go back and confirm I just wanted to comment that I just used the method linked to install Proxmox 7.1 on an HP T730. It was getting this same error and failing in the GUI installer trying...

Anyone know if Proxmox GUI will ever be updated to properly show that the ARC memory is buffer and is not the same as "in use"? HTOP shows it that way, with ARC usage colored the same as other buffers. You can even add ARC specific counters to the display in HTOP. I feel like with how heavily...

How did you build your backing storage for the PBS datastore? If it’s a ZFS dataset, you could use ZFS replication to replicate the dataset and it’s changes to a couple sets of drives that can be swapped offsite on a rotation.

Running into this issue myself. Had it happening in an unimportant container and didn't realize what was happening. Rebuilt a folder structure into multiple nested datasets and now the container that had the parent dataset mounted in and WAS working fine in is now garbage. Going to have to put...

@sammek looks like you registered just to post that. thanks and I'm glad it helped!

Awesome, super psyched to get this newer version of ZFS upgrade. But before I try on my lone single server, anyone have success upgrading a machine with ZFS on root?

Pourya, did you notice this comment in the redhat bugzilla thread? I hadn't noticed this one before but noticed it just now since I was skimming the thread to see if anything new had been posted. It indicates that CPU hotplug also requires greater than 2GB of RAM in the VM Guest. MY VMs all have...

Pourya, I'm not sure what to tell you. This fix works for me on multiple Proxmox hosts and any Server 2016 VM. Either the steps aren't being followed properly or something else is different in your environment that's not being explained here.

I don't think the other commenter was following the directions correctly or had a different problem. This fix has worked for me on multiple proxmox hosts on any Server 2016 VM. I believe Server 2019 does not have this issue, but I haven't tested it myself yet.

That's literally what was explained in my post near the beginning of the thread. I even provided a script to fix it.

Hey LA-Diego, I just saw your questions, only about 6 months late. But, I can answer those. Windows internal unique IDs don't change in this migration process. They stay the same. As for activation, it will very much depend on how your install was previously activated. If you were using Hyper-V...

It's really not a Proxmox problem. Even happened in VMWare - https://vinfrastructure.it/2018/05/windows-server-2016-reboot-after-hot-adding-cpu-in-vsphere-6-5/ You seem to be configured correctly and know how to actually add vCPUs now, you weren't previously configured right or weren't doing it...

Also, how do you have the CPUs configured for the VM? I ask because, there is correct way and wrong way to configure them to use hotplugging. Here's an example of how to do it. 'Cores' needs to be set to the max number of CPU cores the VM will ever be able to use. This number does not...

Are you able to see CPU devices in Device Manager, one for each core the VM booted with? If yes, if you delete them and scan for hardware changes, do they come back?