Search results

It seems, there is currently work being done on s3 support: https://lists.proxmox.com/pipermail/pbs-devel/2025-May/013295.html

I'm currently working on a similar proof of concept with our PCC at OVH. From my understanding, the primary issue is that most migration solutions require direct access to the VMware hosts, which aren't network-accessible at OVH. If it helps, one solution that has worked for me so far is using...

As far as I can remember the tests I've done on that subject with an older version on pve, Yes you can use the vmdk directly (as Lapointemar said) as long as it is accessible from a datastore and migrate the storage (or qemu convert) at a later time.

are you logged in with a user that has the 'Sys.Modify' privileges? Thanks dcsapak, the new group wasn't properly configured, My bad I should have caught that!

Still the same issue In incognito:

Hi, For some unknown reason, I no longer have the "Update" menu from my node. This probably happened following an update but I'm not sure since I often update via the console. Any ideas why this did happen or how to fix it? Thanks, Packages: proxmox-ve: 5.3-1 (running kernel...

An option I used in the past was to backup VM and containers uncompressed and then use borg backup to backup the data. Since it can deduplicate/compress and can have retention you can get pretty good results. https://www.borgbackup.org I remember that the deduplication wasn't optimal because of...

There is few way you can use to accelerate your vzdump, an easy way if you are not already and have a lot of unused CPU could be to replace gzip by pigz. https://pve.proxmox.com/pve-docs/chapter-vzdump.html A zfs snapshotting solutions should works. You can make it work with only one host...

Here's few thing to keep in mind. Hope it's usefull : - If you are looking to have your nfs server in a container you might need to tweak it's settings. Personally, to keep future maintenance simple I would not. Have a look at this thread for more details why...

One way to do it would be to create a NFS share on the host and share and mount it within the VMs.

I would be extremly supprised if changing the kernel would change anything related to your problem.

If you are using zfs, you can check issue 6171 on zfsonlinux github to see if it's related, hopefully a patch is coming.. https://forum.proxmox.com/threads/z_null_int-with-99-99-io-load-after-5-1-upgrade.38136/page-3

I'm on a similar build on a Supermicro with a E3-1230 v3, 32GB, 1 x 850 Samsung SSD (yes EVO!) with more HDs coming and everything fine so far. I dont run much more than few vm and lxc containers. I don't see why you couldn't run few vm unless you don't have much ram or having a lot of heavy...