Recent content by fever_wits

I think pve-qemu-kvm: 11.0.0-3 - works. 1 hour, yum update run. No errors in logs. Best regards, A.H.

Hello, I updated proxmox. I restarted minihv. root@minihv:~# pveversion -v | grep pve-qemu-kvm pve-qemu-kvm: 11.0.0-3 I restored from backup VM, which was causing segmentation faults I reduced RAM from 4GB to 2GB. Apart from this change, I haven't made any other changes. Here is the config...

@fiona, can I or @PVasileff help with something to diagnose the problem faster? If you consider it, later today I can provide direct access to minihv for the proxmox team to diagnose the problem. This is just an idea/suggestion. Just because I don't have a problem right now doesn't mean I...

@EugenMayer - I'm breaking your point of view :) I apologize if I sounded offensive or insulting. I'll describe my thoughts out loud, I don't oblige anyone with them and they are NOT specifically directed at @EugenMayer. I'm just sharing. If I understood correctly @EugenMayer would like to have...

@EugenMayer I can't agree with you regarding the statement about proxmox. Currently thousands of people use proxmox, including me. I have VMs that are +4 years old. Personally I don't have this problem. For this situation that you and PVasileff describe is a coincidence of several things at...

Hello After converting the disk from qcow2 to raw on a VM that had a problem with segmentation faults $ uptime 07:57:08 up 16:43, 1 users, load average: 0.05, 0.08, 0.02 No segmentation faults reported. I can't say for sure if a conversion is necessary or if even a live migration of the disk...

Hello, I spoke to @PVasileff , he tested older kernel versions. That doesn't help. As far as I can tell it's related to disk creation and management. On minihv (Qoton Q20332G9 S20) today we created 2 VMs: - Alma 9.7, then updated - after the last reboot there are no segmentation faults - Alma...

Hello, The amdhv + Supermicro X9DR3-F servers are mine. Both are currently in production. I have a third server on which we are currently doing tests with a restored VM from backup. The VM still had errors. The server has the following data: CPU: Intel(R) Atom(TM) CPU C3758 @ 2.20GHz RAM: 2 x...

Hello,Hello, I have been searching for a solution to this issue but haven’t managed to fix it yet. I am running Proxmox VE with IOMMU enabled and using PCIe passthrough of a network card to a virtual machine where PF_RING is running for network traffic analysis. The kernel boot parameters...

Kernel 6.14, I guess this is test repos ? I didn't see 6.14 in pve-no-subscription.

Here is my contribution :) : # uptime 21:13:04 up 66 days, 8:05, 1 user, load average: 0.31, 0.34, 0.27 # uname -a Linux hiv-spare 6.11.11-1-pve #1 SMP PREEMPT_DYNAMIC PMX 6.11.11-1 (2025-01-17T15:44Z) x86_64 GNU/Linux Nothing to see as problems at the moment. On the other 3 servers I use...

If I understand correctly, the problem is that at boot time the OS changes the resolution to one that the IPMI console does not support. In my experience, if I forget a monitor is connected to VGA and it's at high resolution, IPMI doesn't load for me or loads part of the image full screen. On...

You can try this: consoleblank=0 gfxpayload=1024x768x16 or this: consoleblank=0 gfxpayload=1024x768x16,1024x768 Sometimes it helps.

Hello, After some digging it turned out that the N100 only has powersave and performance mode with intel_pstate. But I'm not surprised, some time ago I saw similar strange behavior of intel_pstate on another OS, and I had to disable intel_pstate and switch to acpi-cpufreq. I'm just sharing my...

This looks like a conservative, not a powersave :) Handy packages to use for CPU mode management are these: cpufrequtils and tuned-utils.