Search results

All of this makes good sense. I appreciate your input and there may be a L3 switch in my near future.

It looks to hover around 20% when I'm running 4 parallel streams iperf3 between the VMs on different VLANs

pve 8.2.2 I'm hoping someone else may have some insight for me that is running pfSense as a VM on their proxmox instance and maybe not seeing the speeds they expect between VLANs. Iperf3 testing between VMs on the same VLAN I can reach transfer speeds of ~30Gbps. But between VMs on different...

I'm hoping someone else may have some insight for me that is running pfSense as a VM on their proxmox instance and maybe not seeing the speeds they expect between VLANs. Iperf3 testing between VMs on the same VLAN I can reach transfer speeds of ~30Gbps. But between VMs on different VLANs (when...

This ended up being a different issue entirely. My home connection (even though being billed as 1G x 25M was severely hobbling my WG connection to my remote server. Once I tested from a known good working fiber connection to my remote server it was blazing fast. Looks like I need to have a...

I'm not passing through the entire card, I'm passing through the single port "0000:01:00.1". "01:00.0" is available to the host (which is the other port on that card ens4f0) and is being successfully used as the bridge interface for all VMs as well as outputting a physical 10Gbe connection to a...

I have a bit of a strange one. I have a pfSense VM setup on proxmox 8.1.3 with the following config: agent: 1 balloon: 0 boot: order=scsi0;ide2 cores: 4 cpu: host hostpci0: 0000:01:00.1,pcie=1 #passed through 10Gbe port from an Intel x540AT2 nic connected to 10Gbe ONT ide2...

Thank you very much! I will try this out and see how it goes.

I've been reading through multiple other online tutorials with suggestions on how to accomplish this but I wanted to ask here if what I plan to do is correct. Currently my Proxmox VE install resides on a 500GB SSD that is starting to throw smart errors. I made a bonehead move early on and...

Welp...this has uncovered a deeper issue. Looks like that SSD is failing...

So. After looking closer...the "stop" backup task was barking about my pihole-FTL.db being corrupted. I stopped pihole-FTL, removed that database file, and restarted it so it would build a new one. After that I tried a "suspend" backup and it still failed. But when I tried a "stop" backup...

Bumping this to see if anyone else has any suggestions? Thanks much.

So I ran "sudo rsync --stats -v --verbose -h -X -A --numeric-ids -aH --delete --no-whole-file --sparse --one-file-system --relative '--exclude=/tmp/?*' '--exclude=/var/tmp/?*' '--exclude=/var/run/?*.pid' /proc/48708/root//./ /mnt/BACKUP_TEMP/test/101baktest2/" and it seemed to run through fine...

Thank you! I'll give this a try this morning.

Proxmox Version 7.1-12 I have 7 LXCs and 2 VMs. All seem to backup correctly without issue except for 1 of my LXCs. When I attempt at suspend backup it fails with the following: Task viewer: VM/CT 101 - Backup OutputStatus Stop INFO: starting new backup job: vzdump 101 --mode suspend INFO...

Wow. Leave it to me to overcomplicate things. Lol. Thank you so much for your help. This worked perfectly!

I apologize ahead of time if this has already been covered somewhere else that I can't find but. I'm attempting to bind mount some NFS shares from my host to a container. The NFS share has spaces in the directory name as will the bind mount point. I've tried using single quotes, double quotes...

This helped me out so much! Thank you! Was having some serious problems and slow downs backing up my containers and VMs to an off-site DR NFS share. This made it work so much better.