Search results

On my other proxmox server, running a consumer ASRockRack board with a AMD Ryzen 7 3800X processor, I can get SVM/Virtualization passed through to a vm with the same settings. Any advice on what else to check on my Supermicro board with Intel Xeon(R) CPU E5-2680 v4 processors?

Not a silly question. The host has 4x Intel(R) Xeon(R) CPU E5-2680 v4 @ 2.40GHz. Here's the output of my cpuinfo: ❯ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 79 model name : Intel(R) Xeon(R) CPU E5-2680 v4 @ 2.40GHz stepping...

I have been trying to get a nested VM working for a few days with little success. Host is Proxmox 8 Steps I've taken: Confirmed the following: # dmesg | grep -E "DMAR|IOMMU" [ 0.000000] ACPI: DMAR 0x0000000078EB1D98 000168 (v01 SUPERM SMCI--MB 00000001 INTL 20091013) [ 0.000000] ACPI...

This worked for me as well. It wasn't booting to the install disk. I ran this command on my EFI drive and it got through to booting from the ISO.

This is exactly my setup, and the Proxmox manual doesn't do a great job of indicating that the configuration we have (assuming yours is similar), which looks as below, is systemd and not grub: Boot0005* UEFI OS HD(2,GPT,<UUID>)/File(\EFI\BOOT\BOOTX64.EFI) Boot0006* UEFI OS...

I know it's best to run docker in a VM, and maybe someday I will switch to kubernetes or something in a vm, but for now I found the solution to this: source: https://discuss.linuxcontainers.org/t/how-to-build-nvidia-docker-inside-lxd-lxc-container/17582/5

TIL - I've been using proxmox for years and have missed that I need to use dist-upgrade. That fixed the issue of held-back packages.

Would you please place this information in the wiki (https://pve.proxmox.com/wiki/Network_Configuration)? I spent some time looking for this information, and it would be nice to have it in the wiki. Thanks.

This is great. Hope a staff member responds, especially since you did all of the troubleshooting for them...

Created bug here: https://bugzilla.proxmox.com/show_bug.cgi?id=3646

I'm using the Tuxis PBS server to back up my server, and I'm pleased with it so far. The only issue is that the `pbs` storage type doesn't appear to allow the `bwlimit` property. When I enter the command root:~# pvesm set tuxis_pbs --bwlimit default=100000, I get the error update storage failed...

Thanks for the help. I went through and deleted all of the mac addresses and forced new ones, but my issue still persists. One container (based on Ubuntu 18.04) has some very strange and inconsistent networking behavior I hoped was just a duplicate mac, but that's not the case apparently.

I'm having the exact same symptoms, but none of my containers share a mac address as far as I can determine. How did you find your duplicate mac addresses? In my experience duplicating a template container, it will automatically generate a new mac address if you leave it blank. Maybe that's a...

I think I'm having the same issue - I have the Intel I211 and my `ethtool -l` shows ~ ❯ ethtool -l enp4s0 Channel parameters for enp4s0: Pre-set maximums: RX: 0 TX: 0 Other: 1 Combined: 2 Current hardware settings: RX: 0 TX...

All I had to do was /etc/init.d/networking restart and it worked right away.

Thank you so much, I was banging my head because somehow my adapter had inexplicably changed its name. Possibly because I was moving pcie devices around, but I don't know enough about how the nic is connected to the chipset and how the naming works. In any case, thank you for the little guide, I...

I just migrated to 5.0 as a fresh install. I'm trying to get my containers back up, which in my last config (Proxmox 4.4) had mount points that pointed to directories (bind) for my different zfs subvolumes. After the upgrade, my containers can't access the subdirectories in the shares, and I'm...

To follow up, I successfully passed through my Nvidia GT 710 to a LXC container where I used ffmpeg to do GPU encoding on a 1080p video - 115 fps or so. I did a write-up on it, you might be interested in it: How To: GPU (NVENC) Accelerated FFMPEG in an LXC Container

Is your template the same as your host? I mean, is your container template based off Debian 8.6? Switching to that fixed the issue for me.

Last night I actually fixed this issue, I will post more later, but I read somewhere that making sure the template for the container was the same operating system as the host is important - so I rebuilt my container using Debian 8.6 instead of Ubuntu 16.04. The main difference is that the nvidia...