OMG, you won't believe this ..
For some reason, I installed the new version on to an m.2 drive in my chassis, but the boot sequence was coming from an old attached disk from somewhere - that old disk has an old (broken) proxmox install on it, so...
OMG, you won't believe this ..
For some reason, I installed the new version on to an m.2 drive in my chassis, but the boot sequence was coming from an old attached disk from somewhere - that old disk has an old (broken) proxmox install on it, so...
Hi all,
I've been testing live memory expansion (hotplug) on a Proxmox VM and ran into some behavior I'd like to understand better. I'm not reporting a bug — I just want to understand why it works this way.
Setup:
Proxmox VE (latest...
Nachdem Kernelcare den Support für Proxmox eingestellt hat ist die Frage, welcher Dienstleister bietet noch Kernel Live Patching für Proxmox 9 Umgebung an?
Oder hat Proxmox selbst dies vielleicht direkt auf der Roadmap.
Gerade in Umgebungen bei...
OMG, you won't believe this ..
For some reason, I installed the new version on to an m.2 drive in my chassis, but the boot sequence was coming from an old attached disk from somewhere - that old disk has an old (broken) proxmox install on it, so...
Beside all the noice i created, i can fairly confident say, downgrading qemu to 10.1.2-7does fix the actual issue. I no longer have any segfaults on any of my proxmox servers, with qcow2 still in use.
Beside all the noice i created, i can fairly confident say, downgrading qemu to 10.1.2-7does fix the actual issue. I no longer have any segfaults on any of my proxmox servers, with qcow2 still in use.
@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...
This is issue is solved. I managed to install the md raid tools in the rescue environment, chrooted in the pve install and reinstalled grub. Was a nice learning :)
@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...
I have identified the cause of the performance discrepancy.
1. Hardware Specifications
CPU: AMD Ryzen Threadripper PRO 5955WX (16 Cores / 32 Threads)
RAM: 16GB
Storage: Samsung PCIe Gen4 NVMe SSD 1TB
Note: All benchmarks were conducted on the...
I still get the same problem, its like deb / proxmox can't create VLAN on this node for some reason..
FYI IT works just fine , I used to have 4 of these in a VSAN cluster with VCF running, so I know the H/W supports VLANS, it looks like 802.1q...
There was no change. We always picked up QEMU releases as they came in, moving them along to pve-test and pve-no-subscription before a Proxmox VE point release made them available in the enterprise repository as well. Also, QEMU does not have a...
Note that this would be a segfault in QEMU itself so the whole VM process would crash, so it's unlikely to be the same issue. And it would be specific to aio=native which is not the default and doesn't seem to be set in the configurations shared...
Hi @fever_wits,
on the third server, could you first test the older kernel builds with ZFS support:
proxmox-kernel-7.0.0-3-pve
proxmox-kernel-7.0.2-1-pve
proxmox-kernel-7.0.2-2-pve
proxmox-kernel-7.0.2-3-pve
For each kernel, you can run...
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...
Thanks for all the informations and work already done above!
I'am currently on the way to test the downgrade of pve-qemu-kvm to 10.1.2 to see if that helps. In my book, the kernel of the host is less likely the cause here (this is only a bet). I...
Here are the relevant `/var/log/apt/history.log` entries from the AMD Proxmox host `amdhv`.
This is the host where the same restored AlmaLinux 8 VM did not show the issue before the update, but started showing segmentation faults immediately...