Latest activity
-
FFoLg0re replied to the thread Considering Proxmox use case...doubts..Thank you so much for that detailed reply, @DerekG !! That is incredibly helpful and encouraging. It's great to get direct confirmation that the iGPU passthrough for the 780M is working well for you on Proxmox, as that was my biggest uncertainty...
-
DDerekG replied to the thread Does PCIE passthrough work on Dell OptiPlex 5050 with Intel Core i3-6100.You don't need to passthrough the NIC on Proxmox, you can setup a bridge NIC which the TrueNAS VM can use, and if required a 2nd Bridge using the onboard NIC for the other traffic.
-
UdoB reacted to Johannes S's post in the thread Docker IPv6 killt IPv6 SLAAC auf dem LXC host with
Like.
Warum? Ich finde docker in lxcs zu betreiben extrem frickelig, zum einen muss man für Netzwerkfreigaben mit bind mounts o.ä. arbeiten, zum anderen geht das gerne mal nach Updates kaputt, einige Beispiele: Dezember 2022... -
Jjdancer replied to the thread Proxmox HA cluster with Ceph.Yes, for live migration, manual/HA. Hence, should really have same amount memory across nodes.
-
Bbanksiaboy posted the thread Host-initiated ping dropped on VLAN-aware Thunderbolt bridge (vmbr1, kernel 6.8.12) in Proxmox VE: Networking and Firewall.I'm running Proxmox VE 8.4.14 (kernel 6.8.12-15-pve) on a Mac mini with a Thunderbolt Gigabit Ethernet adapter (Apple A1433). Apple Mac mini "Core i7" 2.3 (Late 2012) The NIC (ens9) is bridged as vmbr1, with `bridge-vlan-aware yes` and...
-
Aathompson3117 replied to the thread Proxmox VE host backup - best option for now.It says in the post you "removed --one-file-system (twice) from script." Since is appears three times, which one did you leave in?
-
Hhans66 replied to the thread Proxmox blocking DNS of Virtual IP.Did you find a solution? I run into similar issue with 2 piholes in lxc containers on proxmox. Port 53 (tcp & udp dns) from the virtual IP to the piholes does not work (reliable). port 80 & 22 is fine. Thanks
-
Ccurruscanis replied to the thread TrueNAS Storage Plugin.I had a similar issue with pve9.x The error indicates that you are not using a ZFS volume, are you using a dataset instead of a volume? I fought the setup quite a bit but don't have the exact steps written out, but I would look at your pathing...
-
Sspetrillo replied to the thread GPU Passthrough crash PVE.Can you also dump the following cmd to text file: pvesh get /nodes/name of your server/hardware/pci --pci-clsss-blacklist ""
-
FIn case anybody stumbles accross this issue: Enabling "nesting=1" for the privileged container fixed the issue.
-
DDerekG replied to the thread Considering Proxmox use case...doubts..I have a similar setup as one of the nodes in my Proxmox home lab. Mine has an AMD Ryzen 7 PRO 8845HS w/ Radeon 780M Graphics & 96GB RAM Currently running is a Windows 11 VM with the iGPU passthrough, really only used for Handbrake transcoding...
-
WWhatever reacted to dcuadrados's post in the thread Redhat VirtIO developers would like to coordinate with Proxmox devs re: "[vioscsi] Reset to device ... system unresponsive" with Like.
I've already completed the full driver downgrade, so let's see what happens. I hope the yellow triangles and the damn IO error stop. I’ll keep you updated.
-
Hhans66 replied to the thread [SOLVED] UDP Port 53 Unreachable for Docker Pi-hole in Unprivileged LXC.Did you find a solution? I have 2 piholes in LXC om pve with keepalived. On initial startup it works, but if I kill the master, backup takes over, but port 53 is blocked (udp & tcp) while port 80 & 22 is no issue at all. Restarting master...
-
TTHE_BIG_ONE replied to the thread Opt-in Linux 6.17 Kernel for Proxmox VE 9 available on test & no-subscription.I am using vGPU unlock on an older Pascal series card (nVidia GeForce 1080 GTX). Updated all my rigs to 6.17.2-1 today and the one with the vGPU unlock fails building DKMS on any driver version attempted to install. This was working on 6.14.x...
-
UdoB reacted to alexskysilk's post in the thread Proxmox VE host backup - best option for now with Like.
Backing up PVE in itself is not all that useful or even desirable, and should be downright avoided if a member of a cluster- cluster members are cattle not pets. If you DO want to back up the host (lord knows why) any linux backup method would...
-
G_gabriel reacted to dcuadrados's post in the thread Redhat VirtIO developers would like to coordinate with Proxmox devs re: "[vioscsi] Reset to device ... system unresponsive" with Like.
I've already completed the full driver downgrade, so let's see what happens. I hope the yellow triangles and the damn IO error stop. I’ll keep you updated.
-
bbgeek17 replied to the thread Migrating from XCP-NG to Proxmox with Shared Storage and High Availability.Hi @wesleysilva01 , welcome to the forum. Both LVM/iSCSI and NFS are valid choices. NFS is generally more suitable for file operations and cross-host concurrent access. LVM/iSCSI is block storage, where concurrent access means different thing... -
Jjt_telrite replied to the thread TrueNAS Storage Plugin.@warlocksyno is there any reason why PVE 8.4.1 and TrueNAS Version: 25.10.0 - Goldeye would not support or work with your plugin. everytime I try to create a VM (either with your test script or the webui) I get this error. I have completely...