Search results

intel_iommu=on Can't figure out for the life of me what is keeping the kernels from upgrading. Strangely enough, even though it says the newer kernels did not install correctly, I can still boot into 6.14.11.1 . I believe I am just going to rebuild this server from VM backups on a fresh...

So I am now booting from kernel 6.14.11-2-pve in grub without issues. root@pve:~# uname -r 6.14.8-2-pve root@pve:~# But when I run apt-get dist-upgrade I am still seeing: root@pve:~# apt-get dist-upgrade Reading package lists... Done Building dependency tree... Done Reading state...

root@pve:~# proxmox-boot-tool refresh Running hook script 'proxmox-auto-removal'.. Running hook script 'zz-proxmox-boot'.. Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace.. No root= parameter in /etc/kernel/cmdline found! root@pve:~# The symptoms are worse...

It think you meant mount /dev/disk/by-uuid/27F0-332F /tmp/esp root@pve:/tmp/esp# find /tmp/esp /tmp/esp /tmp/esp/EFI /tmp/esp/EFI/proxmox /tmp/esp/EFI/proxmox/shimx64.efi /tmp/esp/EFI/proxmox/grubx64.efi /tmp/esp/EFI/proxmox/mmx64.efi /tmp/esp/EFI/proxmox/fbx64.efi...

Turns out that dev does not exist. Not sure why that happened. Note your instructions told me to mount 27F0-3332F, but the error message I posted above reported: No such file or directory 27F0-332F root@pve:/# mount /dev/disk/by-id/27F0-332F /tmp/esp mount: /tmp/esp: fsconfig() failed...

Thank you for looking into this; Here you go. root@pve:/# proxmox-boot-tool status Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace.. System currently booted with uefi ls: cannot access '/var/tmp/espmounts/27F0-332F/vmlinuz-*': No such file or directory 27F0-332F is...

Managed to remove the old 6.8* kernel that was causing issues, now seeing this: Setting up proxmox-kernel-6.14.11-1-pve-signed (6.14.11-1) ... Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/dkms 6.14.11-1-pve /boot/vmlinuz-6.14.11-1-pve run-parts: executing...

Good morning, I recently upgrade my proxmox 8.x.x install to PVE 9.0.x using the update guidelines. Everything went well and the new system is up and running with one problem. When I try to do apt dist-upgrade apt fails on removing a non-existing historical kernel. root@pve:/# apt update Hit:1...

I actually thought I deleted this message, as I figured put my problem. It had to due with using git checkout to switch from master to the correct kernel.

So installed the proxmox 7 beta and the kernel built without any issues. Now for the newbie question of the day. How the heck do I get the git clonning process to identify and download the correct kernels builds.

I'll try building from the 5.4 kernel on a buster version of proxmox this morning. Thank you for the help.

Good morning, I am attempting to build a custom Proxmox kernel following these instructions. I have attempted to utilize many other tutorials from Fabian's Edge kernels and proxmox with all ending up in some sort of build error (not disk full). So I am now asking for help as I have spent much...

So that was my first thought. However, this install was done as a VM and the only options for display ever used was the Spice Driver, which should seamlessly move from one VM to another. x11.conf shows Intel driver on bother systems.

Good morning. I am fairly new to Virtualization and Proxmox 6.x. Have about a year or so under my belt and have had a good experience. So. I am a tinkerer. I had two nodes and a proxmox backup server running across a 1G network with 20 or so various types of virtual machines. My primary node is...

chudak, When did this problem start for you? I have a proxmox secondary node, PVE2, running on an Asus board with the Intel Pro/1000 and it just recently , last two months, started behaving like this. [ 1902.246655] e1000e 0000:00:19.0 eno1: Detected Hardware Unit Hang: TDH...

Good evening from Savannah, Ga., Just curious. Why are you using CIFS instead of NFS? I ask because using Proxmox 6.2-12 and trying to backup to a NAS via NFS, I consistently drop the NFS connection. Seems to be an issue with the NFS/RPC server on my NAS.