Recent content by NinthWave

Kernel 30 booted Thanks

Understanding the boot journal is above my paygrade. If I understand correctly, the last comment on the bugzilla link says that it should be fixed on the next Ubuntu baseline update. Isnt't Proxmox based on Debian ? Anyhow, just by the journalclt, can you quickly check if it is the same...

I was on 6.8.12.25 that worked and 6.8.12.29 won't boot after upgrade. The screen goes instantly to standby mode. I have to manually select 6.8.12.25 upon reboot. Anyway to solve that ?

Is it normal that the id changed from the host to the VM? As far as I can remember (which can be wrong), in my previous install, the ids kept the same number but now theyr are totally different. I am asking that because I can't successfully install NVIDIA driver either from .run or APT cause I...

I am not sure I fully grasp what is proper IOMMU isolation. iommugroup =1 device_name=GP107GL [Quadro P600] seems OK iommugroup=14 device_name=SAA7164 [Hauppauge tuner] seems OK iommugroup=15 device_name=Coral Edge TPU seems OK iommugroup=1...

Damn, I just started of fresh install of Proxmox 8 while I was previously on 7. Is it still true in Feb 2024 that its best to have docker in VM instead of LXC ?

ok.. the host has 16GB VM1 has 8GB allowed VM2 has 3GB allowed Apart from updating Proxmox from 7.x to 8.x, nothing changed in the VM.... A recover of the VMs to when it failed should bring it back to normal. Should I investigate more? If yes how? Or should I simply fresh install PM 8?

The Debian-VM works until I restore HomeAssistant, then Debian stops booting. I am confused.

the VM.conf asks for q35 and somehow, at restore, it reverted to i440x. Can it be that the host is now un Debian 12 and the VM at debian 11 ?

I dont' know how this is possible but in order to get passthrough, machine type is supposed to be 135, which it was. And not it's q440x... How is this possible?

this seems ok root@pve1:/etc/modprobe.d# cat /etc/kernel/cmdline root=ZFS=rpool/ROOT/pve-1 boot=zfs quiet intel_iommu=on iommu=pt pcie_acs_override=downstreem,multifunction nofb nomodeset video=vesafb:off,efifb:off intremap=no_x2apic_optout

I checked this on Proxmox host root@pve1:~# lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3 Processor DRAM Controller [8086:0c08] (rev 06) 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [8086:0c01] (rev 06)...

earlier this week, I upgraded the host from 7.x to 8.x It worked fine. If I remove the Quadro and Tuner card from "pcie hardware" in the VM, it boots. If I want to add them back, there is no mapped devices. So something in the host has messed with the passthrough. Anyhelp to investigate this ?

Yesterday, I switched from PVE internal backup to PBS. I don't see how it's relevant but my VM stopped working on the same night. All of them. I retrieved a 2-day earlier backup from PVE (not PBS) to no avail. It won't start journalctl on pastebin

Found it. Solved for my debian VM But, do I understand that I made the mistake of creating a VM on an NFS-Share normally used for backup purposes ?