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
2. DHCPv6 DNS updates required manually setting send fqdn.fqdn "..."; in dhclient.conf
3. 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.