Recent content by deepcloud

3 years late but still :) sudo systemctl mask ctrl-alt-del.target

Hello, We have been using Proxmox for a long time along with ceph. but I feel the report of the space usage by Proxmox is misleading. for eg. we have a 3 node cluster with 3 disks of 7.68TB NVMe on it. now we have a 3 way replicated pool which means we should have 1/3rd the capacity of 3...

Hello, This is not true, AMD does have multiple GPU supported by MxGPU, but they are expensive, AMD MI210, MI300X, MI325X and MI350X other cards are all end of life and no longer supported but if you can get your hands on the MI Series we do have MxGPU Supported.

found the issue.. it was due to lack of ram on the physical host. some user had increased the VM Guest memory I put this reply in the interest of somebody else in the community facing a similar issue

Hello I have a strange problem with the latest update of proxmox i have a machine that is shutting down and then refusing the start unless the node is rebooted. I get the below error in the Task Viewer: swtpm_setup: Not overwriting existing state file. stopping swtpm instance (pid 36801) due...

just do - ps -eaX if you find any other tty apart from pts/0 - kill thoes unknown processes (if you have no other session running) and you should be ok

Got mine solved finally. did a #ps -eaX got the output - found 2 nos. ssh daemons running - dont know why they were there - but it was a ssh to another host - not done by us but proxmox for sure. - killing them worked and now I have no unknown terminal / tasks running

This problem exists even now in 2025. I have shells open since oct 2024 and nov 2024. how do I find the tty value for the below commands. who reports only me logged in and nobody else. ps -A | grep <tty-id> and with ps auxwf | grep <tty-id> I understand i can kill the task but how do I...

have a Nvidia A40 GPU - this is supported I have proxmox 8.3.0 - With Kernel 6.5.13-6-pve pinned and installed nvidia VGPU Linux drivers - 535.161.05 I have got the responce from nvidia-smi, nvidia-smi vgpu, mdevctl types... all ok i can even assign the PCIe-vGPU to the VM but cant start it i...

I have a Nvidia A40 GPU - this is supported I have proxmox 8.3.0 - With Kernel 6.5.13-6-pve pinned and installed nvidia VGPU Linux drivers - 535.161.05 I have got the responce from nvidia-smi, nvidia-smi vgpu, mdevctl types... all ok i can even assign the PCIe-vGPU to the VM but cant start it i...

disable hotplug of cpu and ram and shutdown and start again

ok - update folks problem only appears if you enable hotplug of ram/cpu - and only on debian (12 for sure - not sure about other versions) wasted over 6 hrs to figure this out posted this so that it might help someone

Got a enterprise subscription and switched to it... but still no luck as the packages of proxmox are updated with the test repo - any way to undo this and get the latest updates of enterprise repo only this problem has come up only after the recent upgrade to proxmox and the problem is only...

We have a similar problem on some non-production servers running pve-no-subscription repo. windows and fedora vms seem to work fine but after we upgraded proxmox and are running kernel ver. 6.8.12-1-pve with pve-manager/8.2.4/faa83925c9641325 (running kernel: 6.8.12-1-pve) the debian vm's...

2024-09-07T11:27:11+05:30: starting garbage collection on store backup01 2024-09-07T11:27:11+05:30: Start GC phase1 (mark used chunks) 2024-09-07T11:27:11+05:30: TASK ERROR: update atime failed for chunk/file...