Update: Root cause found — HPET clocksource, not kernel 7.0
After further investigation, the high CPU usage was not caused by kernel 7.0 itself, but by the HPET (High Precision Event Timer) being used as the system clocksource.
Using perf top...
Hi,
My datacenter will need to install Debian for me before I can install proxmox.
what instructions should I give them in regards to filesystems / partitioning.
The host will have a pair of 1tb SSD and will need to use software raid.
ie one...
Has anyone continued to upgrade their kernel and/or Proxmox versions, and are your X533 ports continuing to work?
I purchased a Qotom Q20300S9 Mini PC exactly a year ago but have only been using the RJ45 ports up until now. After trying the SFP+...
Hello.
I have switched to only ipv6 containers and using SLAAC no ip is shown when the container is running in the main information tab.
Why dowsn't show it?
will really confortable to make a copy and paste from the statistic tab.
thank you.
@sbraz I think you're gonna have a "thanks" here from every OVH customer who updates their PVE8 to 9 in the next 10 months ...
Thanks ! merci !
You should really think about making a proactive communication : EVERY single PVE8 customer is...
Hi,
I work for OVHcloud on our OS images and I can indeed reproduce the problem on UEFI boot servers with PVE 8 installed on more than one disk with OVHcloud's installer. I'll first provide the solution and then explain why this issue occurs...
Hi. After struggling a little to upgrade from Proxmox 8 to 9 on bare metal servers hosted by OVH, I thought I'd explain how I succeeded.
First of all, this is not a generic tutorial, this is just how I could solve my problem on my 2 servers (one...
small update:
after flattening the image with crane i now have this error:
TASK ERROR: unable to create CT 100 - Error while extracting OCI image: IO error: failed to unpack...
From the analysis until now, the IO pressure seems to be a cosmetic issue or rather accounting issue in the kernel. QEMU switched to using io_uring for event loops with QEMU 10.2. The issue appears in combination with IO threads, where a blocking...
its like using debian sid and then complaining about issues with it.
according to his logic debian sid should be qc-tested since the repository is available to thousands.
thats not how it works.
test = bleeding edge stuff with a decent chance...
Those expectations arise precisely because you’ve actually used it and experienced its shortcomings firsthand.
I understand your concerns, but ultimately, the use of the test repository is at your own risk.
i repeat, dont use the test-repo for production.
developers state its only for testing-purposes and not for production-use as evidenced by my screenshot from their own wiki.
you ignoring this is purely on you and on noone else.
you could have run...
Sorry, I'm out. All of the above is on you. Who told you to implement the "test" repository in "an enterprise-grade environment of this scale".
It is not published in either pve-no-subscription or pve-enterprise repositories.
I don't dispute...
@djsami thats why you dont use the test repository in production.
as the name implies it is a repository for testing things. its bleeding edge stuff.
if you need things to just work, use the enterprise repository, where only well tested releases...
FYI I upgraded my PBS VMs and a secondary PVE server today with no issues. Full backups beforehand.
The problematic PBS VM was upgraded in-place from PBS v3 to v4 and apparently did not have the proxmox-network-interface-pinning .deb package...