Recent content by emanuelebruno

Hello Sterzy, I've investigated the possibility of limiting the data transfer rate between the two servers to avoid potential overloads, especially concerning disk and network usage during the ZFS send/receive operation. I found a solution that can effectively control the transfer speed. The...

Hello Sterzy, I've reviewed your discussion on the Proxmox forum about transferring ZFS volumes from one server to another and would like to share the approach I'm planning to use for minimal downtime VM migration. Here are the steps: Initial Snapshot Creation: While the VM is still running...

Good morning everyone. I have two Proxmox servers (the first one in version 7.4-15 and the second in version 7.1-7) and I need to move two KVMs that are on a ZFS disk. I was looking on the web to check the fastest solution and I came across some posts talking about snapshots, hot cloning, full...

For all those who are struggling with not showing up as removable devices like network card, hard drive, etc.. here is the solution I found for you: The secret is to set the machine version change to pc-q35-5.1. Attention! Only for Windows 11 it is necessary to create the virtual machine...

Hello Kiler129, I'm also investigating the operation of the "numa" and especially on maximizing CPU performance. It all started with an old Opteron 6328, which despite being an old processor of late 2013, doing some tests with the latest version of proxmox 7.4, I realized that it worked too...

Hi, try to do this: apt install pve-kernel-5.15

Thank you for your reply. In the first picture I try to import the corrupted volume without success using the "-f" option (the system goes stuck and I tryed to wait about 2 minutes..but no response)

Hi to allo, today for the first time I ran into this error and I don't know how to proceed: The disk that is currently inaccessible was installed on another server that crashed (for unknown reasons). The following video shows the server crashing after booting when the disk is attached. If I...

It is not broken. I have a backup (of some months ago) of the container before proxmox update and it is the same: it can't start and I don't want to downgrade proxmox for starting the container again...

disco3 is a lvm-thin volume... digiting "fsck -fy /dev/mapper/disco3-vm--105--disk--0" this is the output: fsck from util-linux 2.36.1 e2fsck 1.46.2 (28-Feb-2021) Pass 1: Checking inodes, blocks, and sizes Inode 12473802 extent tree (at level 1) could be shorter. Optimize? yes Inode 12483321...

This is the configura ok thank you

Hi, after Proxmox update (from 7.0-x to 7.1-7) one container doesn't start correctly... It freezes at startup: Executing the container with the debug option, this is the output: I have attacched the log file with the hope that someone can help me. This is the configuration file: arch: i386...

perfect! it was the solution I was looking for .. THANKS 1000!

Hi to all, today I noticed the presence of these processes that repeatedly appear by typing the command ps aux from proxmox console... do I have to worry? i am using proxmox 7.0-11 thank in advance to all those who will answer me

Hi uiffu, did you edit Makefile and patch.sh according to your needs as in my guide above ?