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!

Here is my setup:

• I have two proxmox installations (totally not related) on totally different locations
• on both instances I have a few CTs and VMs
• on both instances I run "backup job" where I create backup to a external USB drive - this is a "first" backup from where I can quickly restore if needed

What I want:

• I want to have a separate (off-site) backup
• I have Raspberry PI with 5TB USB storage
• I want to use this raspi for both Proxmoxs

What would be the best solution for this?

What I was thinking (I don't think this is the most elegant solution):

• install tailscale on raspi
  • (same on both proxmoxs)
  • create CT and install tailscale on it
  • in some interval push backup file form proxmox to CT and then this CT pushes backup over tailscale to raspi

edit: spelling

Can anyone share if they are using PBS with remote backup storage only? I’d like to backup directly to an offsite location, so no backing up to a local drive and then syncing that to remote…

What are your considerations for restoring? I am hesitant to use PBS (on the same machine as my PVE) because with my current solution (restic), I only need to install PVE on a new machine and in addition, I’d need the static binary - and then I’m good to restore. If I’d use PBS, then I’d need to first install PVE, then PBS and only then I can restore…

Is it possible to disable login/password when accessing from the LAN?

After a weekend of testing on a beater computer, I finally transitioned my media server over to ProxMox yesterday. It was a real trial to get the drives mounted to the VM correctly without erasing them, but an hour of googling got me to a working solution. Now that I’ve had a few hours to experience it all working correctly…

This thing is amazing. It gives me such a technology boner just to look at all the info it puts at your fingertips, plus I’m getting much better performance out of some programs after isolating them. Only complaint is the subscription pop up, but I’ll live.

So if you’ve been on the fence about making the switch like I was, I can definitely say you should do it. This is a ridiculously useful tool for any computer enthusiast.

cross-posted from: https://lemmy.world/post/1520963

> I have tried using the debian 10/11/12 LXC templates on Proxmox, but I can't get IPv6 to work as expected. Which is weird, since just setting IPv6 to SLAAC/auto works as expected for ubuntu 20.04 containers with no additional configuration in the container itself. > > What I encountered: > 1. Debian overrides the DNS settings set in proxmox with values from DHCP > 1. DHCPv6 DNS updates required manually setting send fqdn.fqdn "..."; in dhclient.conf > 1. DHCPv6 DNS updates only work when manually calling dhclient -6 > > Those all can be fixed, but are bit of a pain, since I have to manually update configuration files in the container itself. I also have to duplicate the configuration, for example the hostname/domain name in the configuration. > > Has anyone got IPv6 working on debian LXCs without any additional config in each container? Or any ideas what's different between the debian and ubuntu LXCs?

Hello, I'm getting into the bandwagon but for the life of me I cannot conceive why the console had these weird and random color palletes (peach background with aqua green foreground, for example). How can I normalize the console colors? Been searching and I cannot find a proper fix.

cross-posted from: https://lemmy.world/post/1411505

> I'm currently using a Windows machine as the "server" in my home lab, but I just ordered some new hardware and I'd like to change things up to add some more flexibility and capability. > > Based on my research so far, my plan is to install Proxmox on the bare metal and use it to run any regular VMs I need. However, I am still trying to figure out what to do about containers. > > I know Proxmox also, supports LXC containers, but based on everything I've read, I think I'd like to use something more "industry standard". I was thinking Docker, but it sounds like Podman is lighter and more secure, so I am now leaning that direction. I plan on setting up an Ubuntu server VM in Proxmox and running Podman on that. > > I'm thinking of running full blown VMs for more complex applications (Plex for example), but containers for simple applications (Pihole, ddclient, cloudflared, etc). > > Does that all sound like a reasonable plan? > Are there any obvious gotchas I might be missing? > Any tips or resources you'd recommend for a first time user of Podman (and containers in general)? > > I have been doing my own research and I think it's going well but sometimes you don't know what you don't know, so I'd value a second opinion. > > I am pretty tech savvy, so I don't mind learning new things. Windows has always been my primary platform, but I would like to branch out a bit and containers are starting to seem like a must for personal and professional growth. I'm pretty familiar with virtualization (mostly VMWare) but I'm new to containers. > > Thanks in advance for taking a look and sharing any tips!

I use a script to update all of my LXC (Debian, Ubuntu and Alpine) and my Proxmox server, it is quite handy, so I wanted to share it with you all!

If you want to give feedback, don't hesitate to comment here or open a gitlab issue!

I found both of these, but I'm not sure which one to use:

https://github.com/tteck/Proxmox/blob/main/ct/syncthing.sh

https://github.com/tteck/Proxmox/blob/main/install/syncthing-install.sh

cross-posted from: https://lemmy.zell-mbc.com/post/1393

> Proxmox Backup Server 3.0 available > > It's based on Debian 12 "Bookworm", but uses the newer Linux kernel 6.2, and includes ZFS 2.1.12. > > * Debian 12, with a newer Linux kernel 6.2 > * ZFS 2.1.12 > * Additional text-based user interface (TUI) for the installer ISO > * Many improvements for tape handling > * Sync jobs: “transfer-last” parameter for more flexibility > > Release notes > https://pbs.proxmox.com/wiki/index.php/Roadmap > > Press release > https://www.proxmox.com/en/news/press-releases/

Does anyone know why the dark theme reverts back to the light theme every few days. So annoying.

Proxmox Backup Server 3.0 available

It's based on Debian 12 "Bookworm", but uses the newer Linux kernel 6.2, and includes ZFS 2.1.12.

• Debian 12, with a newer Linux kernel 6.2
• ZFS 2.1.12
• Additional text-based user interface (TUI) for the installer ISO
• Many improvements for tape handling
• Sync jobs: “transfer-last” parameter for more flexibility

Release notes https://pbs.proxmox.com/wiki/index.php/Roadmap

Press release https://www.proxmox.com/en/news/press-releases/

So I have been running a proxmox server for a few month now, just playing with it a bit blindly. Just recently bough another drive and reading the storage docs I got some question how does everyone else do things... now I'm planning a backup strategy and want to know what are good practices to manage my VMs/LXC and storage in general.

I currently have:

• 250G SSD shared between host and VMs/LXC
• 4TB HDD in RAID1 (ZFS)
• 8TB HDD as LVM

I normally create VMs with 30G base storage in the SSD and add another virtual hard drive to the VM from the HDDs to create a LVM inside the VMs to store data. Is that good enough? Would I have bad performance creating the VMs in the HDDs?

When creating a snapshot I see this warning below:

WARNING: Sum of all thin volume sizes (438.00 GiB) exceeds the size of thin pool pve/data and the size of whole volume group (<223.07 GiB).

That got me wondering:

• How should I store snapshots in another drive? In the ZFS? Would cause issues if I delete old snapshots?
• What about backups for the VMs? I'd like to have automatic weekly backups but how should I plan this?
• Also I'm not sure if the 8TB is ok as LVM or should be LVM-thin or directory?

If you know any proxmox storage management guide for newbies please share, any advice is greatly appreciated.

Thanks for reading.

I installed Proxmox Backup Server in a VM on my nas to see what all the fuss was about. I messed with it for a but but then the install got botched (not PBS's fault) and I didn't bother messing with it anymore. What I have been doing is, on each of my nodes, just setting up scheduled backups of VMs to a share on my NAS. I can't figure out why using PBS would be any better that just doing that but people seem to like it. I only have to do this once on each node. Could anyone enlighten me as to what I am not seeing in PBS that makes it better?

Here is a selection of the highlights of the Proxmox VE 8.0 final version

• Debian 12, but using a newer Linux kernel 6.2
• QEMU 8.0.2, LXC 5.0.2, ZFS 2.1.12
• Ceph Server: Ceph Quincy 17.2 is the default and comes with continued support. There is now an enterprise repository for Ceph which can be accessed via any Proxmox VE subscription, providing the best stability for production systems.
• Additional text-based user interface (TUI) for the installer ISO.
• Integrate host network bridge and VNet access when configuring virtual guests into the ACL system of Proxmox VE.
• Add access realm sync jobs to conveniently synchronize users and groups from an LDAP/AD server automatically at regular intervals.
• New default CPU type for VMs: x86-64-v2-AES
• Resource mappings: between PCI(e) or USB devices, and nodes in a Proxmox VE cluster.
• Countless GUI and API improvements.

I didn't see one when doing a search so I made it. I am absolutely not the right person for this job but here I am!

Feel free to share or ask anything related to Proxmox here. We are in the stages of any content is at least content. As more people join then the range of experience will grow and more information will be available to all.