Search results

I have A LOT of VMs running on Proxmox VE across several Servers. Most of the VMs run Debian GNU/Linux Bookworm. Overall the KVMs seems quite inefficient, especially in Terms of: - RAM Usage (a bit less on Xeon E3 v5/v6, since up to 64GB RAM can be used there) - Disk Space (each VM takes 16GB...

I migrated my Podman Data from ZFS on top of ZVOL to EXT4 on top of ZVOL. I tried to do zpool trim rpool on the Proxmox VE Host to see if that would improve Things. It didn't unfortunately. The Issue still persists. I also tested on Kernel 6.5.x, same thing. IOWait can jump above 80% very...

Well Kernel 6.1.x is the LTS one on Kernel.org and the default one provided by Debian. If you go the Debian Backports Route, you will get Kernel 6.9.x at the Moment. I also have linux-image-6.6.13+bpo-amd64 but that's because I installed it, it's not in the Repos anymore (and quite old ...

Well the EXTREME Iowait 60%-80% seems more on those Podman Systems (ZFS on top of ZVOL) so maybe there it's a similar Issue to what the User reported on #openzfs (ZFS Pool Deadlock), although not to the same extent. On the other systems it might indeed be lower, but still somewhat 20% or so.

Uhm I never got that Memory Issue. But that's also probably because I force ZFS to do what I want instead of leaving it on a very loose leash ;) . I reduced the amount of ARC I allow ZFS to use. Maximum 4GB for the Proxmox VE Host on a 32GB System (otherwise ZFS can eat up to 50%, i.e. 16GB...

Weird ... The GUI being picky about the Kernel Version :oops: ? I mean, if the Kernel is good to run VMs/CTs, then it should also be for the GUI (IMHO). I don't see how the Kernel Version would break the GUI in that regards ... Did you check Services pvestatd and pveproxy ? I think I'll try a...

Any further Discoveries ? I'm quite disappointed that all the Proxmox VE Team and other Users say "Do NOT use Consumer SSD", when the Issue arise after a Package /Kernel and/or ZFS) Upgrade ... I guess I could maybe take Kernel 6.5.x config from Proxmox VE, Download Kernel 6.6.41 Sources, then...

The only feedback I got from the OpenZFS IRC Channel is that Kernel 6.8 changed MANY THINGS. Not very specific I know, but that's what I know. Not sure if the Issue was already on Kernel 6.5.x. Granted my Workload might have changed since (and was probably fairly light on Kernel 6.5.x), so the...

Just experienced this as well on my latest Proxmox VE Upgrade to PVE 8.x. In my case removing /tmp/.ifupdown2-first-install fixed / bypassed this Issue.

It's a weird choice (by Ubuntu Developers and Proxmox VE Developers) to NOT use LTS Kernels (LTS defined on kernel.org Website), like 6.1 and 6.6 Instead. Given the IOwait Issue I am currently experiencing, the ideal scenario would have been to build a custom Kernel based on 6.6 which is the...

Well you might have a point, at least to some extent, I am not debating that. I just think that if a new Issue shows up on 3-4 Servers of mine after an Update, it's a BUG, not a feature. I am debating that being the only cause. And while I tend to agree that the Issue seems more predominant in...

LVM is an absolute PITA to manage. I tried to recover previous systems. Never again :rolleyes: ! Why are you so focused on PBS ? I am talking about Proxmox VE, not Proxmox Backup Server. So is having to change a Partition Layout when you have Data on it already ... Let alone to setup backups...

What exactly do you mean there ? I don't want to change my entire infrastructure just for the fun of it whenever there is a new BUG popping up ....

Again you seem to miss the Point ... It is a new occurrence with Proxmox 8 and Kernel 6.8.x (at least for me), it didn't happen before. Never before I was getting hangups when saving a 100KB file with nano ! As for the Write Amplification I can sort of agree, I looked at the TBW and I was VERY...

I don't recall 6.5 being *THIS* Problematic. You could be right though, as I'm doing some more work now that I used to do back then ... Definitively 6.8 is an Issue. But having to install Kernel 6.2 on the latest Proxmox VE ... That seems really a Hack. Did you have to recompile the Kernel ...

Any update from Proxmox Developers would be appreciated. I am experiencing this on SEVERAL Servers. And it cannot be that I need NVME Drives for the very limited amount of work that I am currently doing :rolleyes: .

I am (re)debating this Issue, as I have done in the Past. My use Case, as a Homelab user, is that some/many Hosts are up only when needed (at specific Times, in order to reduce Power Consumption), and so the "normal" way with Quorum doesn't really work. I had a look at...

But also if I removed the chown command I still get one error. See attached files in the original Post. It works, but it's weird to have failure logs in that case ...

salt-minion is definitively running as REAL root, otherwise it won't be able to do anything on the minion: root@PVE:~# ps aux | grep salt root 6257 0.2 0.0 131264 26368 ? Ss 12:14 0:00 /opt/saltstack/salt/bin/python3.10 /usr/bin/salt-minion root 6266 1.6 0.0 734016...

I am bit surprised (and I think it's only happening since a few Weeks/Months) by the Error but it seems to be working somehow. I use certbot in a Podman/Docker Container to generates ALL Certificates for my Infrastructure. No, I do NOT use the ACME "plugin" of Proxmox VE, since I have wildcard...