These are Linux kernel versions, not Proxmox versions. So you are booting your updated Proxmox 9 with Linux kernel 7.0.2-6-pve.
At the end of the existing kernel command line, append systemd.unit=rescue.target or systemd.unit=emergency.target...
I think the OP is talking about MailGateway (not sure since his post doesn't say much about what he actually wants to achieve) not PVE. The recommendation is the same though: https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#chapter_pmgupgrade
Have you tried it on PVE 6.x? I'm having issues with an e1000e NIC not working under 7.x on a single node. Port doesn't even light up, but works fine when I boot into 6.x.
Thanks for clarification. I had around 20 single servers updated yesterday at different times and seeing a different menu only on one of them, was a bit confusing.
I've finally narrowed down the exact settings / what is causing the issue. I've been repeating installs on 4 different proxmox host machines over and over changing one thing at a time and comparing. It's the SSD and Discard flag being set...
The Roadmap states
I did see this Datacenter → Guest Resources/Hardware on a PVE 9.1.19 yesterday evening, but not today anymore on a PVE 9.2.2. The menu is flat again without Guest Resources/Hardware.
What am I missing?
Happy to report that we have successfully run our storage-oriented CI/CD workflows against PVE 9.2, and no issues were uncovered during the initial test runs.
Congratulations again on a solid release.
Sincerely,
Blockbridge
Blockbridge ...
Kernel: 7.0.2-6-pve
HW CPU: AMD GX-424CC
I am experiencing very high CPU usage after a kernel update.
There is a huge overhead in CPU usage in SY time.
perf output:
+ 41.10% 0.05% [kernel] [k] entry_SYSCALL_64_after_hwframe
+ 41.05% 0.10%...
I think the OP is talking about MailGateway (not sure since his post doesn't say much about what he actually wants to achieve) not PVE. The recommendation is the same though: https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#chapter_pmgupgrade
Today, I upgraded my pve from 8 to 9. This is a basic pve (36 cores, 64GB ram) that runs 4 pct.
Ran the pve8to9 test, all good. All containers stopped. Changed bookworm to trixie on sources and pve-no-sub.
apt update, then apt dist-upgrade...
What would be the sentense of a "filesystem cache" ? It caches the filesystem and so hide I/O requests to the underlaying disks. So as the cache for read and write is mostly always better as the more far I/O path instead of just to memory ideal...
Würde ich nie kaufen. Dafür dass die "leer" sind und halt doch nicht richtig erweitert werden können, sind die mir zu teuer.
Der kleinste kostet leer 440 Euro. Wenn ich 100 Euro für Netzteil und Gehäuse rechne (das geht...), dann habe ich 340...
Ich würde mir einen 19" Einschub wünschen, in dem diverse unterschiedliche Mini-PCs vertikal arretiert werden könnten und per Gleitschiene komplett ausgezogen werden könnten. So ähnlich wie damals die Bladeserver von IBM, nur eben in modern.
So...
I actually doubt this. Most users on reddit maybe, but I doubt that the largest part of Proxmox revenue (which actually funds the development) comes from homelabbers instead of companys ditching Vmware
hmm.
yes, I see your point.
I am guilty of thinking of PVE as an infrastructure. I forget that many (most?) of its users are homelabbers. consider me chastised :)
True generally, untrue in the OPs testing matrix. LVM-thin introduces its own problems. Since it is of almost no benefit in a modern deployment (LVM thick for SAN, zfs/btrfs for local) I dont know why OP even bothered testing it.
Hi, I have defined this mountpoint. /mnt/pve/containers is a NFS mount
mp0: /mnt/pve/containers/media/immich,mp=/opt/immich/upload,idmap=u:999:1026:1;g:991:100:1
and when I try to start the container I get the following error
DEBUG utils -...