Search results

Update: I managed to resolve the issue. The problem was in the configuration file of the VM: The ID of the PCI devices for my NIC were missing the decimal portion. Proxmox tried to attach the device with the PCI-ID 0000:04:00, however, "lspci" shows that each port of my NIC has the ID...

I have done the following: edited /etc/default/grub and changed GRUB_CMDLINE_LINUX_DEFAULT="quiet" to GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on iommu=pt pcie_acs_override=downstream,multifunction nofb nomodeset" applied changes with "update-grub" added vfio modules to /etc/modules...

I am trying to set up pfSense in a VM based on Techno Tim's tutorial video (except for UEFI). I also recently acquired a Dell 5719 quad port PCI-e which I want to use for both WAN and LAN connectivity. However, when attempting to start the VM, my network connection dies and I am unable to use...

The metrics server apparently got shut down and got assigned a new IP when rebooted. I have fixed the issue by setting it on a static IP and updating the entry for the metrics server. TL;DR: If you have a metrics server configured that cannot be reached pvestatd will apparently not update the...

Already done that when I had the problem that the welcome message did still show the old IP. IPv4 config in /etc/hosts: 127.0.0.1 localhost.localdomain localhost 192.168.178.169 pve.fritz.box pve I have also already rebooted and restarted pvestatd multiple times.

I have recently changed the IP for my HomeLab from '192.168.178.54' to '192.168.178.169'. Since doing so pvestatd still tries to connect to the old IP, which leads to a timeout and all my system info in the web interface not being accessible. Jun 25 09:55:16 pve pvestatd[1639]: lxc status...