Search results

Ooooh that makes sense. And works. Thanks!

I have a zfs pool on the host Proxmox system: # zpool list NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT ... zslow 131T 38.2T 92.7T - - 0% 29% 1.00x ONLINE - I have the pool loaded and I've mounted a filesystem: # zfs list...

What does “datacenter options” mean? I thought it was overall bandwidth of the host. Is it something else? If I set it for individual VM/CT, it won’t be an aggregate limit. Is there any way to create an aggregate limit for the whole host?

I'm trying to limit my entire Proxmox host (v8.4.5) to 500 Mbit/s (~59.6 MiB/s). I set the datacenter bwlimit to 59 MiB/s: # cat /etc/pve/datacenter.cfg bwlimit: default=60416 I then tried in a container on my SDN vnet to run a speedtest and it went (almost) full link speed (~900 Mbit/s...

If you’re going to have automated backup you should probably just use the one built into Proxmox, right? I believe that includes the VM config. That’s how I have my nodes setup usually. Oh I suppose if you absolutely can’t spare the drive space and the disk data doesn’t matter, and only the...

Wow that worked absolutely perfectly, thank you!

I pulled a drive from a Proxmox host without backing anything up. If I stick it in a new host I can see the LVM-Thin that has the VM disk images, but what about the configs? I don't even care about restoring them as-is, I just want to look at the old configs for reference. Is this possible?

Someone on reddit mentioned aliasing local_network to block gui access, so I thought I'd try it and... it works! I aliased local_network to my tailscale cidr 100.64.0.0/10: and then the management ipset no longer has the local LAN IP appended: # ipset list ... Name: PVEFW-0-management-v4...

Looks like this behavior is at least documented: https://pve.proxmox.com/pve-docs-9-beta/pve-firewall.8.html#_standard_ip_set_span_class_monospaced_management_span the question is... how do I change this behavior? Can I alias cluster_network myself somehow? (setting my own alias with the same...

Oh, I see the problem: # ipset list Name: PVEFW-0-management-v4 Type: hash:net Revision: 7 Header: family inet hashsize 64 maxelem 64 bucketsize 12 initval 0x7a95b7b9 Size in memory: 552 References: 5 Number of entries: 2 Members: 100.64.0.0/10 192.168.0.0/24 192.168.0.0/24 is being appended...

And /var/log/pveproxy/access.log has this entry for the curl request from LAN: ::ffff:192.168.0.96 - - [21/07/2025:23:15:14 -0700] "GET / HTTP/1.1" 200 2521

Here's everything that looks relevant in iptables-save: # iptables-save | grep 8006 -A PVEFW-HOST-IN -p tcp -m set --match-set PVEFW-0-management-v4 src -m tcp --dport 8006 -j RETURN -A PVEFW-HOST-OUT -d 192.168.0.0/24 -p tcp -m tcp --dport 8006 -j RETURN # iptables-save | grep...

Hello, I'm trying to figure out how to lock down my server so that it can only be administered from Tailscale. I don't have the option of putting the server behind a firewall as it's being colocated directly on public internet. I created a "management" ipset which, as far as I can gather from...

Setting `intel_iommu=off` allowed me to boot and login without error! I was able to do that by editing the grub entry for Proxmox at the boot screen (press 'e') and changing `intel_iommu=on` to `intel_iommu=off`, before pressing F10. Unsurprisingly, I was wrong, and the VM was set to boot...

I edited /etc/network/interfaces at the recovery console and after an `ifreload -a` I confirmed with `ip l` and `ip a` that things looked good. When I reboot I still can't login from the normal login prompt (same reset issue in first post) and I can't access the web GUI. Oh, I didn't see this...

I surprisingly can get into the recovery console (offered as a boot option).

I can't seem to even attempt a login anymore after swapping motherboards. Please note before you read further that the PHYSICAL console login (accessed over IPMI) is broken, not the Web GUI. I know swapping the motherboard rendered my old networking configuration completely wrong. I'm trying to...

These steps worked for me with one addition: After converting an ide disk to scsi you have to add scsi to the boot order or your VM will no longer boot, and NOT from the bios but from the Proxmox GUI here:

Wow that's a pretty intense workaround. Thanks for providing it but I think I'll sit out this upgrade for now.

The youtube video was taken down ("This video has been removed by the uploader"). Anyone have any advice? I'm on Proxmox 7.1-10 and I tried Default, KVM64, and host for CPU. All give me the same error about "Common KVM Processor" being unsupported.