Hi Aaron,
If could either be like this
auto lo
iface lo inet loopback
iface nic7 inet manual
iface nic0 inet manual
iface nic1 inet manual
iface nic2 inet manual
iface nic3 inet manual
iface nic4 inet manual
iface nic5 inet manual
iface...
This indicates you added/mounted that disk using a systemd mount file. Hence it does not show up in fstab.
Probably check with:
ls /etc/systemd/system/mnt-pve-nvme2tb.mount -lh
# It maybe in another dir, so you'll have to check
I've never done...
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...
If we have Debian linux VM's running secure boot and the older 2011 certificate.
Let say Debian releases a new shim update after June and is singed by the 2023 cert, will all those VM fail to boot?
Thank you.
I decided to use the newly added feature to create a custom CPU and edit the conf file as shown below to resolve this issue for now.
cpu: custom-Nested,level=30
machine: pc-q35-11.0,viommu=virtio
We're pleased to announce the release of Proxmox Backup Server 4.2.
This version is based on Debian 13.4 ("Trixie"), uses Linux kernel 7.0 as the new stable default for improved hardware support, and comes with ZFS 2.4 for reliable...
Hope it's OK that I resurrect this thread and add another question here -
I'm currently setting up kubernetes on guests on the proxmox cluster and want them to directly provision storage on ceph instead of on their local disks, does that mean...
Thank you.
I decided to use the newly added feature to create a custom CPU and edit the conf file as shown below to resolve this issue for now.
cpu: custom-Nested,level=30
machine: pc-q35-11.0,viommu=virtio
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...
Ok, too bad. In case you only want to keep the 7.0 kernels you can mount your efi partition and manually remove all the 6.x initrd.img and vmlinuz files there to make space so the apt process can complete.
mount /dev/disk/by-uuid/665C-E3E3...