Recent content by PhantexTech

I would almost say that if you are keeping massive amount of data in a virtual drive, it's not recommended. I get your point though. Until persistant bitmaps can be introduced or another alternative such as it depending in snapshots in some fashion, I would say use in-guest backup methods, like...

This is a hardware issue with bad memory. As usual :) This does not appear to be a software issue. If anyone comes across something similar, test your ram.

Alright. Had another system lock up and managed to capture the logs. This is related to the i/o errors. As if I try to migrate any of the data that shows i/o errors, the system i/o goes to 100%, locks up, and then reboots. This appears to be a ZFS related crash. Specifically with something in...

I've been chasing a ghost since upgrading to proxmox 8.3 (correlation is not causation, so I can't point to 8.3 just yet). Random LXC containers start to exhibit i/o errors. This is only "noticed" when a nightly backup runs as it then errors, but fails on those specific LXC's. The storage is...

I just ran into the same situation. When I do a batch linked clone of 50 VMs for a job, half of them fail because it couldn't get a lock. OP, did you ever figure this out? This might need to be resolved via a feature requests, where clone jobs wait for a lock or just try again for X amount of time.

Thanks! You are right. I should be querying for the resources. That will help big time. Not sure how I overlooked that.

Currently, there doesn't appear to be a single http get to obtain all VMs in the cluster. Right now, I have to query the cluster to obtain the nodes, then query each node for what VMs they have, then on top of that, query each node again for each individual VM config. As you can imagine, when...

Did you ever figure this out? I also have a dkms module and would like to be pinned to a specific version and specific kernel version until I can safely upgrade.

I have a more technical question regarding resource scheduling. Does non-basic one ignore ZFS arc cache when it comes to memory weight? Seems like cache should be completely ignored as it can be evicted.

This seriously needs to addressed. It's SOOOOO annoying.

I have discovered something else with further testing. It appears that the migration does in fact not take up bandwidth (when going nfs to nfs), but is very cpu intensive. This dual core test machine had it's cpu pegged at 100% the entire disk move (nfs to nfs). I did confirm that the data is...

That's interesting. I installed netdata on proxmox and monitored it. When montoring what happened when I migrated from one nfs share to the other, all free space on the virtual drive was still read bit by bit from my nfs share, even though it was empty. Here is a test that I just did that...

If you have a thin provisioned disk (say 128GB), but the actual size of the disk is only 6GB after install, why does proxmox need to physically move 128GB of data when migrating a disk to another network storage location (even though the file is 6GB)? What is the limitation here? It does not...

I have noticed that if I try to clone a VM, the clone process will read the entire virtual disk, including empty space, even though it's a qcow2 > qcow2 clone, within the same nfs share. Is there a way to optimize that? When you have virtual disk that span more than 100 gigs, it really becomes a...

I stand corrected. I did not know that existed. Thanks.