Search results

Hi, @paulsk answered that nicely, I'd say! If you have further needs in term of load balancing, and don't want to wait for the upcoming CRS evolution, there is a nice tool that can help you load balance using live metrics: ProxLB ! As for the high CPU usage, I assume you have a lot of VMs /...

Hi, I don't speak Italian, but I'll take a guess… and answer in English. PBS is quite unique, and provide a full feature backup solution for your Proxmox Cluster. Developing and maintaining it so that it stays relevant and that feature full cost a lot more than for PVE, I guess. Also you...

Hi, This probably means your ZFS storage is corrupted… Or you hit a bug in zfs, or both. That issue was mentioned on Github. And the last comment points to a way to recover the data, but for a truenas scale install, not proxmox. However, I'm guessing it could be useful, or even work in your case.

Hi, try to get an idea of what is causing the IO delay? iostat or atop should at least tell you which devices are in troubles, and what processes are impacted (though… it's probably VMs ;)) If you have another monitoring tool up, try to get insight there… And you can also use SMART to get some...

I don't know of any existing script, I'm usually assuming that if I lose a host, I'll just install a new one, and bring it in as a fresh one.. But your list seems nice… Maybe things in /var especially if you care about stats and logs. And root's SSH key if you don't want to deploy a new one…...

OK. It is rather unclear what you want. I'm guessing.. you want to resize the ZFS storage used for all your containers, right? The zfspool called VM-Import? If so, you need to have space available on the underlying device… Or is it the container volume itself?

I'm not sure what you're trying to do now.. So your first screenshot was inside the container, not on PVE right? So … can you do findmnt / inside the same container? Also, could you show us that container configuration (pct config 105 most likely), and especially the rootfs property? And…...

Haha, the workaround is actually clever!! vzdump (the command) doesn't have such a feature, probably because all the logic for that is hold in Qemu Server. The way it seems to be set is getting the list of volumes, and decide based on their properties or specific setting (backup=0/1), add them...

As a general note, I'm not sure why you're using the 169.254/16 IPs, why not using another range from RFC1918 there? and if it's for direct communication, surely something smaller than a /16 (or even a /24) would work… Which leads to my other point, why bother? Either it's full mesh, either it...

Are you trying to use e2fsck on a BTRFS subvolume? Can you provide the result of findmnt /? If what I assume is correct, you'll need to check how to resize a btrfs partition, not ext4. Something along the lines of https://btrfs.readthedocs.io/en/latest/btrfs-filesystem.html#man-filesystem-resize

I would say that it is like that because nobody uses them that way, so the GUI doesn't really reflect that possibility. Maybe that could be a nice patch to provide? ;) I don't think it's a problem, and you probably don't want all those LUNs to be displayed in the GUI anyway... so it's may need...

There is a qm importdisk command as well, but it probably won't help you in that case, as it wants images, not devices such as LVs. There is room for improvement here on Proxmox though, there could be an option to somehow ease re-attaching disks even from another VM… It would also make cloud...

No, it's not the same. Backup of the VM has the configuration backed up as well as the disk, but maybe you don't care about that, or may be backing that up on your own? And of course, you get all the disks, rather than just one... Then, as for the disk, if the VM is running, the same stuff...

If it works, you could get lucky and if you have a VM with the same VMID your LV is set to, it might be detected as an Unused disk, that you could attach to the VM. That could work... But it probably won't. So create a VM with the same spec in the GUI, with a (or many) disks the same size as...

Hi, You probably won't be able to do this using only the GUI. Add the old disk (or rather its volume group, that should be detected by using pvs/vgs/lvs) as a LVM storage on your new setup, See if you can see them by clicking on the "old" storage, in VM Disks already.

What may not be addressed however, is the fact that the DHCP/NDP rules seem to be set backwards, preventing "client" service when set to no in the options, when the iptables system did it "correctly". There may be room for improvement in the docs, mentionning that DHCP means in fact DHCP server...

This is addressed in https://forum.proxmox.com/threads/nftables-when-output-policy-drop-is-set-on-a-vm-theres-no-way-to-accept-arp-output.146015/

Solution, as it's not very configurable as it is, change proxmox-firewall/resources/proxmox-firewall.nft so that for vm-out it reads: chain vm-out { type filter hook prerouting priority 0; policy accept; ct state related,established accept iifname vmap @vm-map-out }

There are two parts I'm interested in in the nft rulesets: chain output { type filter hook output priority filter; policy accept; jump default-out jump option-out jump host-out jump cluster-out }...

Well, your rules end up with… accept, so it's probably not the same issue, as connection state is probably not directly your issue, I'd say