Pretty new to proxmos but I've been using the helper scripts to stand up some services quickly. Is it possible to rename some of those services in the proxmox UI to something other than the default it chooses?

I am trying to install and setup proxmox on laptop and use it as daily driver. I want to make network setup that can use both ethernet and WiFi, whichever is available and i want VMs to be able to access LAN because some things dont work otherwise (like NDI). I have writen config file that makes 2 bridges and every VM would have 2 interfaces. I havent installed Proxmox yet because i dont want to mess things up (it wouldn't be first time :) ). My question is does this config look ok and are there some recomendations.

/etc/network/interfaces

auto lo
iface lo inet loopback

# Ethernet interface
auto eth0
iface eth0 inet manual

# WiFi interface
auto wlan0
iface wlan0 inet manual

# Ethernet bridge
auto vmbr0
iface vmbr0 inet dhcp
    bridge_ports eth0
    bridge_stp off
    bridge_fd 0

# WiFi bridge
auto vmbr1
iface vmbr1 inet dhcp
    bridge_ports wlan0
    bridge_stp off
    bridge_fd 0

There is some space next to the British flag. I am going to start working on it

cross-posted from: https://lemmy.sdf.org/post/18367043

Latest announcements for Proxmox.

Latest announcements for Proxmox.

proxmox ZFS uses Systemd boot by default. To switch to grub, run

proxmox-boot-tool init /dev/sda2 grub

Do this for each boot disk. Now you can edit /etc/default/grub and have it actually work

There are two main solutions you can use.

The first one is the quickest and it is to go into storage and create a directory. Set the mount point to a directory of your choice and then choose ISO storage and template storage. I would keep disk storage disabled as directory storage is not good for large data

The second option is to create a NFS share and then mount it in proxmox. This has the benefit of syncing templates across hosts but it does take more setup.

I've setup proxmox, and switched to the community repos.

The issue is the kernel it's now running doesn't have a headers package in said community repos. This means I can't install nvidia drivers properly. I can only install older kernel versions and headers. I tired removing the newer kernel and it tried to remove proxmox-ve meta package.

Do I need to remove proxmox-ve package and install community version or like what?

So I just did my first install of Proxmox a few months ago in my home server, and I'm seriously, seriously in love, enough that I decided to use it to run my media server as well; it runs Plex, act as a NAS for my media and backups, etc.

Specs: CPU: AMD Ryzen 5 5600G Board: ASRock B550 Steel Legend RAM: 32 GB DDR4 3200 OS Drive: Samsung 970 Evo 500GB PCIe 3.0 Storage: 50 TB over six drives (all media), all mounted directly to Proxmox

RGB: Fans: 10 CORSAIR iCUE RGB Elite Performance Power Supply: Corsair CX750F RGB

Running (always): Containers: Plex, Docker, Jellyfin (still experimenting) (Docker runs docker images for MakeMKV, Handbrake and MediaInfo, but it's only up when I am using them.(

Before Proxmox, Cassiope ran on Solus Budgie and before that Xubuntu, and while OpenRGB could be cranky, with Solus I had full control all the RGB elements so I know how to use it. I spun up a Xubuntu VM and installed OpenRGB in it and connected to it after some tinkering but not to everything, but I figured that was just because I hadn't done the hardware connections to the VM correctly. Still, it was there.

It not only did not let me control them, it turned everything RGB off. I had to shut down the server and restart cold for them to come back on and I could not connect and it also started fucking with my lights. I killed the VM, tried again, couldn't connect at all. Just to see what happened, I installed directly to Proxmox with the image and it connected.

It did not go well. Short version, I had to scrub the install and flash my board's BIOS, and so no more experimenting on my media server. I moved some of it to my other server, Watson (similar specs but AMD Ryzen 7 3700X CPU and less storage and 64 GB RAM CORSAIR Vengeance RGB Pro) .

I tried in Xubuntu, Solus, EndeavourOS, Linux Mint, then--just to see what happened--directly on Proxmox. This progressed and ended literally the same way but with more and weirder steps: the VMs would fail, my board started acting up, I (again) tried with a direct install to Proxmox, and yes I had to scrub, flash the BIOS, and reinstall everything.

I am new to Proxmox but I've been jumping distros in Linux for well over a decade and except for EndeavourOS (which is amazing, I finally like Arch), all the VM OSes I used I know very, very well and all worked with OpenRGB perfectly. I have broken many installs and had to scrub over the years like a lot but generally it was something I did either on purpose or because I made a mistake. (or while root, deleted my entire OS; it happens). I was very methodical and very careful, especially when I switched to my other server and took notes; there was nothing I did--or for that matter, was even able to do--that should have caused this. So my guess is I need to do some configuration in Proxmox to get my hardware to connect to the VM (or to use it directly on Proxmox) , but I don't even know where to start and after flashing two separate boards, I'm a little shy on guessing randomly. Yes, I have googled a lot but nothing I read that I tried worked.

I would really really like control and use of my fans and lights but I really, really love Proxmox and the flexibility of a hypervisor and I'm learning so much and barely scratched the surface, so I'd like an alternative to having a lot of very pretty lights that I can't control. Right now, OpenRGB seems to be the only game in town for iCue or Polychrome when not in Windows, so--help?

I've been using a Proxmox home server for quite some time now without many problems. Recently i got an AMD Navi 10 RX 5700 XT and tried to pass it through to a windows VM. I mainly followed the official Proxmox guide but got it running by using some other tutorials too. For now, it works once after i reboot the host. Then its no problem to start the VM, but after a restart the VM doesnt start no more, showing this error: swtpm_setup: Not overwriting existing state file. kvm: ../hw/pci/pci.c:1637: pci_irq_handler: Assertion 0 <= irq_num && irq_num < PCI_NUM_PINS' failed. stopping swtpm instance (pid 98348) due to QEMU startup error TASK ERROR: start failed: QEMU exited with code -1` I tried fixing it using this but it didnt change much.

EDIT: link was not shown

The container I run plex on has plenty of spare memory but is still using 100% SWAP. First off, is this an issue I should be concerned with or try to fix? If so, any ideas?

Hi all,

My use case: I have a server with two identical drives. I wanted to set up my second drive just like Proxmox did the first one; split between storage and VM's.

After a lot of searching I did see people having the same question, but I couldn't find a complete answer.

Here's a small writeup on how to get it done, hopefully it'll help someone someday.

If you see errors/improvements, please submit a PR.

I've followed this guide after setting up an openmediavault LXC using a tteck script. I want to run this container as unprivileged and haven't been able to get it to see my external USB drive.

Things I've tried:

1. Using the actual minor number for the device instead of *
2. Using cgroup2 instead of cgroup
3. changing create=file to create=dir
4. A privileged container

Maybe I'm missing a step after following this guide? To check my success, I go into the Storage→Disks section of openmediavault and see that nothing is listed there. Clicking the 'Scan for new devices' icon results in a 500 - Internal Server Error.

Maybe this guide is horribly outdated? It states: "Note: lsusb will not work inside the container because there are no devices there yet" but I am able to install usbutils and lsusb to see all USB devices on my host from within the LXC console.

I'm running omv as a VM currently while I try to figure this out. If I remember correctly, all I had to do was use the proxmox GUI to add the USB device to the VM in the hardware section, then omv was able to see the drive and interact with it just fine.

For starters, I'm ultra new to proxmox and linux. I have my old PC running proxmox in the corner of my room so I can play around and learn it.

I have my main server (running Windows) sharing an attached hard drive as a samba share for other computers on my network. I can't seem to mount this share in a fresh LXC, but I can in a PlexMediaServer LXC I created using tteck helper scripts. I'll just attach what I'm doing below. Both are using the same container template (Ubuntu 22.04).

Plex LXC

root@plex:~# mkdir -p /mnt/wddrive
root@plex:~# mount -t cifs //192.168.1.3/Media /mnt/wddrive -o username=myusername,password=mypassword
root@plex:~# ls -la /mnt/wddrive
total 73409600
drwxr-xr-x 2 root root        4096 Sep  2 13:48  .
drwxr-xr-x 3 root root        4096 Sep  3 13:40  ..
-rwxr-xr-x 1 root root       14340 Jul  8 08:15  .DS_Store
drwxr-xr-x 2 root root           0 Jul  5 16:50  Books
drwxr-xr-x 2 root root           0 Jun  1 14:53  Financial
drwxr-xr-x 2 root root           0 Aug 24 08:20 'HOA Documents'
drwxr-xr-x 2 root root           0 Aug 26 13:09  Movies
-rwxr-xr-x 1 root root      414702 Jul  8 10:37  PXL_20220114_214638675.PORTRAIT.jpg
drwxr-xr-x 2 root root           0 Sep  2 13:55 'Plex Lib Files'
drwxr-xr-x 2 root root           0 Aug 31 16:32 'TV Shows'
-rwxr-xr-x 1 root root       17408 Jul 14 19:42  Thumbs.db
-rwxr-xr-x 1 root root    53934080 Aug 31 18:36  com.plexapp.plugins.library.db
-rwxr-xr-x 1 root root         420 Mar 15 20:38 'make show folders.bat'
-rwxr-xr-x 1 root root      173497 Jul  8 10:28  photo_2023-05-20_20-34-59.jpg
-rwxr-xr-x 1 root root        3252 Aug 31 18:41 'plex reg.reg'
-rwxr-xr-x 1 root root 53243232462 Nov 27  2022  takeout-20221128T031130Z-001.zip
-rwxr-xr-x 1 root root 21873610486 Nov 27  2022  takeout-20221128T031130Z-002.zip
root@plex:~# 

Fresh LXC Spinup

root@testcontainer:~# mkdir -p /mnt/wddrive
root@testcontainer:~# mount -t cifs //192.168.1.3/Media /mnt/wddrive -o username=myusername,password=mypassword
mount: /mnt/wddrive: permission denied.
root@testcontainer:~# ls -la /mnt/wddrive
total 8
drwxr-xr-x 2 root root 4096 Sep  3 20:42 .
drwxr-xr-x 3 root root 4096 Sep  3 20:42 ..
root@testcontainer:~# 

I think it's pretty obvious that I have a problem with permissions on the bare LXC that I don't with whatever that script is going to set up the LXC and install Plex for me. I'd like to be able to mount network shares as easily as this on all my other LXCs as well. Can anyone point me in the right direction?

I run proxmox on an i7 10700 8c/16t CPU. I have this idea that if I have a gaming VM, I shouldn't over-provision cores and even leave 2 for the host, but is that really the case. Can I somehow ensure VM is basically pinned to say half the cores, and the other half can be fought over by whatever other VMs I'm running and proxmox itself? Could this affect performance on the gaming VM?

Just today I realised that one of the servers in my cluster up their fans RPM every 15 minutes.

I’m planning to asses first it’s because of a VM, container or PVE itself. Then find the offending process(es).

How would you approach these two steps - any ideas for tools, perhaps even by proxmox themselves?

I'm trying to install Proxmox on a server that is going to be running Home Assistant, a security camera NVR setup and other sensitive data, I need to have the drives be encrypted with automatic decryption of drives so the VMs can automatically resume after a power failure.

My desired setup:

• 2 Sata SSDs boot drives in a ZFS mirror
• 1 NVME SSD for L2ARC and VM storage
• 3 HDDs in a RAIDz1 for backups and general large storage
• 1 (maybe more added later) HDD for Camera NVR VM.

I'd prefer every drive encrypted with native ZFS encryption automatically decrypted by either TPM 2.0 or manually by a passphrase if needed as a backup.

Guide I found:

I found a general guide on how to do something similar but it honestly went over my head (I'm still learning) and didn't include much information about additional drives: Proxmox with Secure Boot and Native ZFS Encryption

If someone could adapt that post into a more noob friendly guide for the latest Proxmox version, with directions for decryption of multiple drives, that would be amazing and I'm sure it would make an excellent addition to the Proxmox wiki ;)

My 2nd preferred setup:

• 2 Sata SSDs boot drives in a ZFS mirror with LUKS encryption and automatic decryption with clevis.
• All other drives encrypted using ZFS native encryption with ZFS key (keys?) stored on LUKS boot drive partition.

With this arrangement, every drive could be encrypted at rest and decrypted on boot with native ZFS encryption on most drives but has the downsides of using LUKS on ZFS for the boot drives.

Is storing the ZFS keys in a LUKS partition insecure in some way? Would this result in undecryptable drives if something happened to ZFS keys on the boot drive or can they be also decrypted with a passphrase as a backup?

As it stands right now, I'm really stuck trying to figure this out so any help or well written guides are heavily appreciated. Thanks for reading!