Search results

Hi all, I hope I'm not off topic talking about this. I am making a small guide that explains all steps to install the latest version of Proxmox in an HP DL 380 G7 server and how to enable HBA mode on the P410i SCSI controller. Unfortunately I am having some difficulties compiling the kernel...

Hi to all. I would like to install proxmox on SecureDigital to simplify updates (to switch from one version of Proxmox to another I could prepare an installation on my server and then do a simple swap of the SD memory) and above all to avoid binding the installation of Proxmox on the same SSDs...

Hi, I'm trying to do the same. Have you find a solution?

I had read in another post "For now, I'd avoid enabling the new zstd for the root pool, especially if you boot with BIOS and not UEFI and an EFI System Part ion (setup since Proxmox VE 5.4 ISO installer)." so I had understood that I could enable zstd compression in rpool/data ... but I suppose...

Hi, in my test environment (HP DL380e Gen8) I have verified that there is a problem in proxmox 6.3.4 and it can be reproduced doing the following steps: install Proxmox 6.3-1 (using the last iso available from website) in zfs-raid1 mode; update system to 6.3-4 (by apt dist-upgrade procedure)...

Hi I have the same problem tonight... Proxmox 6.2-4 snapshot stays in prepare status forever...

Thank you for your reply... please can you read my answer to guletz ?

I understand what you say, but the problem still occurs in other situations. I try to explain. I know that qcow is a shrinked file (it means that if I create a qcow of 5 TB size for the first time, Proxmox will spend few seconds because it will not allocate 5 TB of empty file of "00"...

Hi all, why is backing up an empty VM under Proxmox is so slow? Is it possible that no one has ever noticed? example: whether I create an empty 1 TB qcow file, or I create a 1 TB KVM in a ZFS partition, and install, for example, debian 10 (ssh server only and nothing else), my server with a CPU...

The short story: In proxmox 6 fallocate: fallocate failed: Operation not supported The long story: Sometimes I can't start my virtual machine because Proxmox says that there is not enough memory space (and it is very strange because I have a server with 16GB of RAM and my KVM is configured to...

Thank you, it works!

Is there anyone who knows?

Quota in OpenVZ(Proxmox 3.3)+ZFS works perfectly... and even if OpenVZ team would fix it, version 3.4 is no longer supported.

Thank you for you reply.

Hi all, after many hours spent to understand why quota in OpenVZ in Proxmox 3.4 doens't work anymore, I found that it happens when OpenVZ container stays in a ZFS partition; the problem doesn't occur in EXT4 partition. I hope that you'll fix this issue because I believe that Proxmox 3.4 is the...

Hi Udo, you can find your answer in this link.

Hi Alessandro, if you take a better look to my post, you'll see that I have written this code: [...] grub-install /dev/sdb

Hi, according to my post, this italian translation is for you: Having the need to purchase a second 8-TB disk and put it in RAID-1 on a already working system consisting of only one RAID 0 disk, I wanted to write this step-by-step guide hoping to be of help to someone. First, let's repeat the...

How can I see these messages?

Hi dcsapak, the server is 4 GB, Windows 7 has 1 GB, the second and the third kvm have 512 MB; filesystem zfs only one drive (4 TB) .