Search results

Can you post a screenshot from GPU-Z ( https://www.techpowerup.com/download/techpowerup-gpu-z/ ), to identify the right BIOS.

Have you tried to patch the bios?

It's looking good now. Have you tried to pass the card?

I think you should remove textonly and video=astdrmfb from your GRUB_CMDLINE_LINUX_DEFAULT and replace it with iommu=pt and video=vesafb:off (nano /etc/default/grub) Don't forget to recreate boot config with update-grub than reboot. Than please post the output from cat /proc/cmdline and check...

That is strange... Can you post the output from following files: cat /boot/grub/grub.cfg | grep linux cat /etc/default/grub | grep CMDLINE cat /etc/kernel/cmdline

Make sure that you have enabled iommu in cmdline ( intel_iommu=on iommu=pt ) Make sure that your GPU is disabled in cmdline ( video=vesafb:off video=efifb:off ) (cat /proc/cmdline) after reboot Make sure vfio modules are loaded Make sure you disabled the GPU in /etc/modprobe.d/vfio.conf (Use...

Please tell me your PVE version.

Please tell us your hardware and PVE version. Than I can tell you some steps.

Bitte fülle auch RID2 (zweiten identischen TXT Records erstellen und dessen ID nehmen), ACMEv2 API muss mindestens 2 Keys setzten können. Bitte poste auch einmal die konfigurierten TXT recoded von selfhost

Hast du den PMG einmal neugestartet?

Sorry hatte übersehen das es sich um PMG handelt. Der Befehl zum Service restart lautet hier: systemctl restart pmgproxy.service Edit: Einrichtung hier über Konfiguration -> Zertifikate -> ACME-Konten/-Challenges

Hallo, im Moment ist es noch nicht offizell von Proxmox unterstüzt, aber man könnte es von Hand implementieren. dns_selfhost.sh Hinzufügen: cd /usr/share/proxmox-acme/dnsapi/ wget https://raw.githubusercontent.com/Marvo2011/acme.sh/dev/dnsapi/dns_selfhost.sh Proxmox API Erweitern: nano...

Hallo zusammen, Ich habe einen DNS Challenge Plugin für selfhost erstellt: https://github.com/acmesh-official/acme.sh/pull/3873

Nice! Looks good! Yes you are right, all clients on your LAN can simply connect to any VLAN. A Linux client simply by creating the interface eth0.100 or eth0.10 ... At your first setup it would be the same. When your subnets schuld not be available from the LAN simply remove the network port...

You don't need more physical NICs to do that. Simply create a new Bridge vmbr2 with (bridge-ports) enp4s0.100 for VLAN 100, it's simply possible over the Proxmox GUI or by adding in /etc/network/interfaces auto vmbr2 iface vmbr2 inet manual bridge-ports enp4s0.100 bridge-stp off bridge-fd 0...

I think the simplest way is to create a vmbr for every VLAN. And take some more NICs in pfsense. Simply set bridge-ports enp4s0.100 (für VLAN 100). Now you can add an address in Proxmox to have it connected to "SERVERS".

Hello, we use luks for encrypted volumes, pbs/debian unlocks it with his stored keys. For other access it give some passwords. https://wiki.ubuntuusers.de/LUKS/ https://linux.die.net/man/8/cryptsetup But I think it would be better to use the pbs internal encryption. Edit: I think it should...

Yes, with aes-256-gcm encryption it was reproducible, at any try. Around 14TB of backup data, at 1 CT, 6 Host and 47 VMs. Edit: Prune/GC wars set to 14 days and 4 months.

At the moment we are on: zfsutils-linux: 2.0.5-pve1 proxmox-backup-server: 2.0.11-1 pve-kernel-5.11.22-5-pve We installed pbs on top of an pve because we will use the host for an direct restore. Since we reduced the ZFS encryption from aes-256-gcm to aes-128-ccm it seams to work, but very slow...

Have you disabled Hardware Checksum Offloading ? I think is necessary for pfSense on virtio. https://docs.netgate.com/pfsense/en/latest/virtualization/virtio.html