Search results

Yes the second try worked perfectly. The problem is that, during the conversion there is a timeout problem due to a storage lock, the VM will be Template but the disk not.

pvesm status Name Type Status Total Used Available % local dir active 308587328 142952244 149890060 46.32% As I know the conversion only renames the file and sets the permission to read only. I did it. I removed the...

Thanks The /nodes/<nodename>/tasks with filters is better for me. Will the limit=1 (with vmid= and typefilter=qmtemplate ) send back only the last one task, or one of the tasks?

~$ pveversion -v proxmox-ve: 7.0-2 (running kernel: 5.11.22-4-pve) pve-manager: 7.0-11 (running version: 7.0-11/63d82f4e) pve-kernel-5.11: 7.0-7 pve-kernel-helper: 7.0-7 pve-kernel-5.4: 6.4-6 pve-kernel-5.11.22-4-pve: 5.11.22-9 pve-kernel-5.4.140-1-pve: 5.4.140-1 ceph-fuse: 14.2.21-1 corosync...

Sometimes the application may send the request in parallel. Does it mean the worker can handle only one task in the same time on the same storage? The template creation doesn't send back UPID. Could you please offer workaround?

Please double check all repository in /etc/apt/source.list and /etc/apt/source.list.d/{all_files} Could you send more detals about the error message from apt dist-upgrade.

You can use root user in the first time. And select the "Linux PAM standard authentication" If the root user doesn't have password, you should set it.

As I see the phsical disk or its partition has an LVM. This LVM volume contains your VM disk. This VM disk has partitions and LVM as well. But you reduced the VM disk size without reduce the partition inside the VM disk, didn't you? It means your partition is corrupt inside the VM disk. And...

My application creates VMs step by step, But usually some VM creation gets error. trying to acquire lock... TASK ERROR: unable to create VM 105 - can't lock file '/var/lock/pve-manager/pve-storage-local' - got timeout It is a very simple configuration. There is only one directory storage with...

During the template creation I got lock error. Task viewer: VM 120 - Convert to template trying to acquire lock... TASK ERROR: can't lock file '/var/lock/pve-manager/pve-storage-local' - got timeout But the service convert to template the VM, it means the configuration of VM increased with...

Hi, As I see you will have only one node. It is depend on the VMs and what do you want. Please refer to the storage section of the documentation first. https://pve.proxmox.com/wiki/Storage (Dir, LVM, LVM-thin) Because lot of things depend on the type of the storage. (snapshot, etc.) For...

Hi, I want to use the best performance configuration. I need help to find out which VM configuration is the best for me. The best performance means the drivers use low CPU time. I will use local storage with a separate disk. Which file system is best for sata qcow2 virtual machines? All VMs...

It is very good news. I'm familiar in the API. That's why I faced that issues. In that case I'll use workaround to solve my problem. Thanks a lot.

Hi, If I use "template: 1" during vm creation the vm will be a template but the disk will be "-rw-r--r-- 1 root root vm-101-disk-0.qcow2" a vm disk. (I know there is no different between the vm and the base disk.) If I create a vm and after that I convert it to template there will be get an...

I have a proxmox cluster with 5 nodes. The system uses ceph. It has been working without problems for 3 years. There was nothing changing But the ceph shows this error. cluster: id: fb926dd9-17b9-42fb-88d6-27f4944fd554 health: HEALTH_WARN Long heartbeat ping times on...

You are right. There is no relevant different. All container are located on ceph. Maybe the chep doens't update the parameters of the row device. But my point of view in this case the task result is not OK. The user is not informet about this situation. A additional test is needed to check the...

All containers are cloned from a template (Full clone). From this reason all containers have the same configuration. root@vNTDB-host-1:~# pct config 264 arch: amd64 cores: 1 features: nesting=1 hostname: Nat-system-2-225 memory: 2048 nameserver: 10.102.102.132 net0...

Here is the next one. root@vNTDB-host-1:~# pct resize 264 rootfs 10G Resizing image: 100% complete...done. resize2fs 1.43.4 (31-Jan-2017) The filesystem is already 1310720 (4k) blocks long. Nothing to do!

This output is the same that I sent before. Sometimes it works and sometimes doesn't. But after the disk moved to another storage (and back) solved this problem. # pct resize 150 rootfs 15G Resizing image: 100% complete...done. resize2fs 1.43.4 (31-Jan-2017) Filesystem at...

# pveversion -v proxmox-ve: 5.4-2 (running kernel: 4.15.18-18-pve) pve-manager: 5.4-13 (running version: 5.4-13/aee6f0ec) pve-kernel-4.15: 5.4-9 pve-kernel-4.15.18-21-pve: 4.15.18-48 pve-kernel-4.15.18-20-pve: 4.15.18-46 pve-kernel-4.15.18-19-pve: 4.15.18-45 pve-kernel-4.15.18-18-pve: 4.15.18-44...