Latest activity

  • news
    that doesn't really tell us much, and in any case, that consumer SSDs don't give much performance with ZFS is not a kernel bug ;) if you can reproduce the acpi_pad kernel threads pegging the CPU and have a reliable trigger for that, please...
  • W
    Seeing the same behavior. CPU usage is reported in Proxmox between 8% to 11% when idle. taskmanager in the VM reports below 1%. Server2025 Ryzen 4800h CPU Happens both with default "x86-64-v2-AES" as well as "host" CPU type. "hv_emcs" is not...
  • R
    Hi everyone, I'd like to summarize this investigation in case someone encounters a similar issue in the future. First of all, thank you to everyone who took the time to review the logs and suggest ideas. This was my first serious OpenZFS...
  • A
    alpha754293 replied to the thread Containers on GlusterFS?.
    Pardon my stupid question but why can't the "native" GlusterFS client in Proxmox 8 handle LXC rootdirs? I understand that if I want to use it with it, that I will have to create a directory and then use that instead, but I am just trying to...
  • K
    @SteveITS mhh so the other nodes are running the same kernel. The existing older Kernels do not really matter. Maybe some different BIOS Settings? Intel Nested Virtualization maybe off? But v3 shouldnt even use that, if I understood that...
  • SteveITS
    One would think but I upgraded them about 15 minutes apart. The one that works has a few extra older kernel versions as I hadn't run autoremove yet. I use the PVE GUI to upgrade. "uname -a" is the same on both. Which might imply some hardware...
  • powersupport
    powersupport replied to the thread VM Migration error.
    Hi, This is expected behavior. Although both nodes have an LVM storage with the same name, they are still separate local storages. Proxmox does not support storage migration directly from local LVM to local LVM, which is why you see the error
  • K
    I am currently running an HP ProLiant ML350p Gen 8 with an P420i RAID controller. I was thinking about using ext4, but I read that ZFS might be better in some usecases.
  • K
    My first guess would be, that the other nodes are not on the same page as the initial node. Compare them via: pveversion -v Do all nodes show the same version? Upgrade via apt dist-upgrade? Does the original node run the new kernel after...
  • L
    longer replied to the thread VM Migration error.
    Okay, I will test this and update you hopefully tomorrow. If possible please also share journalctl log from the source pve covering the migration time, for example: root@pve :# journalctl --since "2026-08-xx xx:00:00" --until "2026-08-yy...
  • SteveITS
    Not sure if you prefer this here or in another thread but I installed updates today on all nodes. On a VM using machine type 11.0 and CPU x86-64-v3, I changed it to 11.0+pve2. When I restarted it via PVE GUI, it fails to start on or migrate to...
  • F
    Frank-75 replied to the thread VM Migration error.
    VM Windows Server 2016 (with last security updates), this is on node A (ML350gen8) agent: 1 balloon: 6144 bios: ovmf boot: cores: 1 cpu: kvm64 efidisk0...
  • P
    Dear all, Since a while I'm having the problem that updating to kernel 7.0.6+ my System Log in Live Mode wasn't updating anymore. See my earlier post here: Live logs not updating after boot finishes kernel 7-0-14-1-pve Meanwhile working on an...
  • H
    Just adding my 2 cents here, since I see using aur seems to be the main method of acquiring ssacli here. You can just use HPE's repository, just did it recently (they have quite a lot of public keys, 4th public key I found actually worked): #...
  • L
    longer replied to the thread VM Migration error.
    Okay, please also attach the vm config of one of the affected vms: root@pve ~$ qm config [vmid]
  • Red56
    We are experiencing problems using inbound IPv6 traffic (https and mail) with FreeBSD as a VM. Connectivity is unstable; sometimes there is no inward connection and sometimes there is. When we check IPv6 through...
  • J
    Good point! I realized that I wrote the incorrect model, they are actually M90q G5: So I am pretty sure they will be possible to fit with this little fella that I also did buy together with the cards: It's a riser card that should fit...
  • J
    I am troubleshooting repeated Proxmox VE host-level outages that appear temporally correlated with recent Proxmox kernel/runtime updates. I am not trying to assign blame prematurely, but I would like guidance on what evidence would be most useful...
  • F
    Frank-75 replied to the thread VM Migration error.
    Thank's! Notes: the migration with QCOW2 works only if I do 2 step: 1° move disk to i-SCSI lvm (NAS) and 2° move to datastore 2° NODE A-to-B and B-to-A same issues. VM migration issues with Windows Server 2016, 2019 and 2022. Linux: Debian and...
  • L
    longer replied to the thread VM Migration error.
    Hmm so the problem only occurs whenever you use qcow2, Interesting finding. I am not aware of such problems when using snapshot-as-volume chain. I will try to reproduce and share my result.