Latest activity
-
abied-charreton reacted to abufrejoval's post in the thread Incorrect supported CPU flags with
Like.
I guess you get thrown off by the "amd-ssbd" and the "amd-stibp" flags on Intel CPUs. I just had a look at those flags ony my mixed CPU infra, which includes some Goldmont Intel Atoms as well as Zen3/4/5 hosts and was somewhat thrown off by... -
Ssyxxness replied to the thread 9.2 idmap problem.This is sort of what I was suspected was going on. Thanks for clarifying!
-
UdoB reacted to leesteken's post in the thread [SOLVED] kernel update fail 6.14 to 7.0 no space left on device with Like.
Don't run 'apt upgrade' as it might not pull in all dependencies; use the official instructions instead: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#system_software_updates And here is a (another) recent thread where the same problem... -
TTrickyTrix posted the thread I need help for setting up backup solution in Proxmox Backup: Installation and configuration.I built my Proxmox homelab on Z890 chipset with Intel Core Ultra 5 235 and 64GB of RAM a year ago. OS and VMs are on enterprise SSD with single disk ZFS configured (RAID1 would be great, but I don't have it), and cheap storage consists of five WD...
-
BBarryS83 replied to the thread Opt-in Linux 7.0 Kernel for Proxmox VE 9 available.Is this the correct way to set it to force TSC? nano /etc/default/grub and than change the line: GRUB_CMDLINE_LINUX_DEFAULT="quiet clocksource=tsc tsc=reliable" Is there any risk to set this? Do I risk the host not booting at all?
-
Aabufrejoval replied to the thread Way more NAGware, very little functionality, bugs galore."Wehret der Anfänge" is the secondary aspect; my understanding is that the PDM isn't meant to remain a alternate tool to achieve more or less the same things the legacy UI delivered, but will ultimately replace it. And if Proxmox is aiming at...
-
Mmeyergru replied to the thread Way more NAGware, very little functionality, bugs galore.I do not think the argument was fired against a "supposed freeloader" (I am one, too), however let's be realistic: The concerns against PDM that you expressed boil down to two points: 1. PDM is not yet ripe enough. Granted. 2. PDM nags you more...
-
LLSX3 replied to the thread Server-Disk I/O delay 100% during cloning and backup.Hello everyone, unfortunately I still have not been able to resolve the issue on my side. However, I think it is important that more than one person is now seeing the same or at least a very similar behavior. This makes it less likely that this...
-
Mmeyergru reacted to Johannes S's post in the thread Way more NAGware, very little functionality, bugs galore with Like.
If you don't like the nag screen and don't want to contribute to the development ( guess what developers need to pay bills too ) there is an easy fix: Don't use the software. For cross-cluster migration you can also use the pct remote-migrate and...
-
Aabufrejoval reacted to cwt's post in the thread Way more NAGware, very little functionality, bugs galore with Like.
I believe both points are valid to a certain extent. It is entirely reasonable that Proxmox developers are compensated for their work, and subscription models are clearly appropriate for production environments. The concern many users express is...
-
Aabufrejoval replied to the thread Way more NAGware, very little functionality, bugs galore.Do you honestly think that this is a valuable and thoroughly valid argument in this debate? Or did you just shoot off against a supposed freeloader? You should do well to remember that the Linux ecosystem isn't just people paying for support or...
-
Hi Fabian, Sorry for not getting back to you sooner. After a thorough investigation, we found out that one (1) of the cores in our Intel Xeon Gold 6154 CPU was faulty, causing the unexpected reboots. -
UdoB reacted to Johannes S's post in the thread Way more NAGware, very little functionality, bugs galore with Like.
If you don't like the nag screen and don't want to contribute to the development ( guess what developers need to pay bills too ) there is an easy fix: Don't use the software. For cross-cluster migration you can also use the pct remote-migrate and...
-
Aabufrejoval reacted to leesteken's post in the thread [SOLVED] kernel update fail 6.14 to 7.0 no space left on device with Like.
Don't run 'apt upgrade' as it might not pull in all dependencies; use the official instructions instead: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#system_software_updates And here is a (another) recent thread where the same problem...
-
Aabufrejoval replied to the thread Incorrect supported CPU flags.I guess you get thrown off by the "amd-ssbd" and the "amd-stibp" flags on Intel CPUs. I just had a look at those flags ony my mixed CPU infra, which includes some Goldmont Intel Atoms as well as Zen3/4/5 hosts and was somewhat thrown off by...
-
jsterr reacted to leesteken's post in the thread [SOLVED] kernel update fail 6.14 to 7.0 no space left on device with Like.
Don't run 'apt upgrade' as it might not pull in all dependencies; use the official instructions instead: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#system_software_updates And here is a (another) recent thread where the same problem... -
jsterr replied to the thread [SOLVED] kernel update fail 6.14 to 7.0 no space left on device.what about proxmox-boot-tool kernel remove? root@pveneo:~# proxmox-boot-tool kernel E: subcommand is mandatory for 'kernel'. /usr/sbin/proxmox-boot-tool kernel <add|remove> <kernel-version> /usr/sbin/proxmox-boot-tool kernel pin...
-
Aadris replied to the thread [SOLVED] kernel update fail 6.14 to 7.0 no space left on device.No I keep getting the same error message: the /boot directory is full, and that's what's causing the problem. But since this involves a critical phase of the boot process, I don't want to make a mistake.
-
jsterr replied to the thread [SOLVED] kernel update fail 6.14 to 7.0 no space left on device.is a apt autoremove not enough to fix this? did the job on my site a few weeks ago.
-
cwt replied to the thread Way more NAGware, very little functionality, bugs galore.I believe both points are valid to a certain extent. It is entirely reasonable that Proxmox developers are compensated for their work, and subscription models are clearly appropriate for production environments. The concern many users express is...