Latest activity
-
DDennigma replied to the thread Proxmox VE 9.2.21 - BCM57412 bnxt_en network failure after upgrade to kernel 7.0.14-20-pve.For me it helped to use "pcie_aspm=off". Does anyone want to try / confirm that? Using "pci=notph" didn't do anything for me, right after booting, the connection was gone. Same without "pci=notph". But the other command helped in my case.
-
MMN7675 replied to the thread Ceph Cipers Migration - Windows TPM States "can't map" - Cannot Start / Migrate Windows Guests.I temporarily enabled local storage on the hosts and moved the TPM State disks to that storage in .raw format. I was able to successfully start up the guests that way and will run them in that manner until I can find a solution. The problem...
-
MMN7675 replied to the thread Ceph Cipers Migration - Windows TPM States "can't map" - Cannot Start / Migrate Windows Guests.I tried to restart all of the monitors and managers and that did not resolve it.
-
MMN7675 posted the thread Ceph Cipers Migration - Windows TPM States "can't map" - Cannot Start / Migrate Windows Guests in Proxmox VE: Installation and configuration.CEPHX Disabled. pveversion -v proxmox-ve: 9.2.0 (running kernel: 7.0.14-16-pve) pve-manager: 9.2.18 (running version: 9.2.18/614bede5d65599c6) proxmox-kernel-helper: 9.2.0 proxmox-kernel-7.0: 7.0.14-16 proxmox-kernel-7.0.14-16-pve-signed...
-
Ffwcheck replied to the thread Proxmox VE 9.2.21 - BCM57412 bnxt_en network failure after upgrade to kernel 7.0.14-20-pve.I also observed that a node with a vm was running longer. I decided to downgrade as fast as possible as you might just try your luck. I downgraded/pined the kernel to 7.0.14-19 and everything now remains rock solid.
-
CCoop replied to the thread Proxmox VE 9.2.21 - BCM57412 bnxt_en network failure after upgrade to kernel 7.0.14-20-pve.Note sure if this helps or not, but in our cluster of 4 nodes one of the nodes is running on 7.0.14-20-pve has been running for over an hour with active VM's appears to be working, for us only when the entire cluster went to 7.0.14-20-pve that we...
-
MMN7675 replied to the thread (SOLVED) CEHPX Disabled, CEPH Key Migration - Removing an auth entry?.Wow okay I made significant progress. There is a single keyring for a client which I had to manually refresh I guess. Now I am having a NEW Issue. None of the Windows guests can start anymore. The TPM State disks cannot be mapped: task...
-
Sscottk8 replied to the thread Proxmox VE GUI won't load after upgrade.Actually already did that, found the Beszel service was there, killed it then tried to restart the pvedaemon and pveproxy services and voila, I have a GUI back! Thaks for your help guys, my brain had totally frozen in panic...
-
Ffwcheck replied to the thread Proxmox VE 9.2.21 - BCM57412 bnxt_en network failure after upgrade to kernel 7.0.14-20-pve.I must admit that iommu=pt did run longer (about 32 minutes, but crashed also in the end) Unfortunately i made an error configuring the kernel-parameters, i am rechecking.
-
MManuS replied to the thread Proxmox VE 9.2.21 - BCM57412 bnxt_en network failure after upgrade to kernel 7.0.14-20-pve.A further update regarding the pci=notph testing. I started a new independent test using: - kernel 7.0.14-20-pve - pci=notph enabled I can confirm the parameter was active: BOOT_IMAGE=/boot/vmlinuz-7.0.14-20-pve root=/dev/mapper/pve-root ro...
-
Kkatt replied to the thread Problem with rsync mtime preservation since update to kernel 6.17.13-6-pve (solved by avoidance of nfs 4.2).Did anyone find another solution? I would like to have some of the features from nfs4.2, but I'd rather not have to downgrade all my other machines to LTS just to get everything working. 7.0.14-19-pve on proxmox and 7.2.8-zen1-1-zen on clients
-
Sscottk8 replied to the thread Proxmox VE GUI won't load after upgrade.Yes, there's a Beszel agent running on it. I used it for a while but recently removed it and could have sworn I ran the agent remove command on the pve host.
-
MMN7675 replied to the thread (SOLVED) CEHPX Disabled, CEPH Key Migration - Removing an auth entry?.Wow what a mess. I had to manually refresh a client key: # Export the current keyring (includes key and caps) ceph auth get client.nvr02 -o /tmp/myapp.keyring # Regenerate the key in the keyring file ceph-authtool /tmp/myapp.keyring -n...
-
Sskins4ever86 replied to the thread Stopped start failed: QEMU exited with code 1.I get this when I try and start my VM, if I remove GPU's it will boot fine. kvm: -device vfio-pci,host=0000:dc:00.0,id=hostpci4,bus=ich9-pcie-port-5,addr=0x0: vfio 0000:dc:00.0: hardware reports invalid configuration, MSIX PBA outside of...
-
DDBailey635 reacted to bbgeek17's post in the thread After Upgrading from v8 to 9.2, one node cannot resolve DNS with
Like.
Its not part of our installation here that went through 7>8>9 upgrades. I don't know off hand whether it is part of any standard PVE install, I suspect not. Somehow you, or someone on your team brought it in. I'd examine the journal and dpkg logs... -
TTErxleben replied to the thread EFI, TPM Partitionen.Die PVEs sind alle UEFI-Basis. Die VMs müssen ja vor upgrade eine UEFI und TPM-Partition in der Konfiguration erhalten. Diese werden VM-intern eben immer hinter c: gedonnert. PS: Irgendwie ja logisch, da Win bis heute keine Partitionen...
-
bbgeek17 replied to the thread After Upgrading from v8 to 9.2, one node cannot resolve DNS.Its not part of our installation here that went through 7>8>9 upgrades. I don't know off hand whether it is part of any standard PVE install, I suspect not. Somehow you, or someone on your team brought it in. I'd examine the journal and dpkg logs... -
DDBailey635 reacted to bbgeek17's post in the thread After Upgrading from v8 to 9.2, one node cannot resolve DNS with Like.
Your /etc/resolv.conf is a symlink to systemd-resolved's generated file (as evident by the text at the start), and resolved has no DNS servers, hence "No DNS servers known." Removing the package leaves the symlink behind, pointing at a stale...
-
Ffwcheck replied to the thread Proxmox VE 9.2.21 - BCM57412 bnxt_en network failure after upgrade to kernel 7.0.14-20-pve.College told me to try to add iommu=pt in /etc/kernel/cmdline A similar bug seems to arise in current debian kernels (6.12.111) with crashes after arising after 5-30 minutes. I am checking.
-
DDBailey635 replied to the thread After Upgrading from v8 to 9.2, one node cannot resolve DNS.Thanks. That worked. Any idea why systemd-resolved got installed during the upgrade on just this one machine? I'm pretty sure it wasn't there before (although these machines are available to our MSc students, and they do funny things when we...