Error Configuration file 'nodes/proxmox01/qemu-server/100.conf' does not exist

[Guille De La Torre]

Hi, I have the image of the virtual machine:
root @ proxmox01: / var / lib / vz / images / 100 # ls
vm-100-disk-1.qcow2


but I do not have the configuration file for some reason, it was deleted, in which way I could solve this problem since I do not have a backup of the file, what I was doing was removing the cluster that I had previously joined and when I rebooted the system it came out said error of which way could approach said inconvenience thanks.

Error:

The error configuration file 'nodes / proxmox01 / qemu-server / 100.conf' does not exist

 

[Klaus Steinberger]

It should be not very complicated to recreate a config file, if you at least know some details about the vm like type of system / number of cpus / etc.

you should copy the image away before you do that, and after creation copy it back.

After that learn the rule: Backup .. Backup ... Backup

 

[Frank87]

Hi friends, I have the same problem and I have a full backup of the file, but it doesn't allow me to create a file in the same 116.conf or restore this file to /etc/pve/nodes/proxmox2/qemu-server/

 

[asmar]

Did you found a solution on this? I have the same problem. After converting to qcow2 from raw I get a "Configuration file does not exist" but when I try to copy the old .conf file into the path that it says it throws a message that already exist but there is nothing inside that directory!

 

[nttec]

I have this same problema as well, as I check there is no file on that folder

"/etc/pve/nodes/proxmox2/qemu-server/"

system is not allowing you to recreate or put a copy of the conf file on that folder.

Thus, anyone has this problem and solution to this?

 

[dcsapak]

maybe there is a left over config in another directory?

check /etc/pve/nodes/*/qemu-server
not only the node that you currently are on

 

[ccms]

I had this same problem. The issue in my case was that this 'qm set' command works only on VMs and not containers.

 

[Kenny.Petty]

To better clarify ccms above, the qm commands are not meant for Containers, you should use pct commands, so the proper way to unlock a Container is pct unlock <container>. Verify that your VM is actually and qemu VM before executing qm commands.

 

[buck2825]

I have this same problema as well, as I check there is no file on that folder

"/etc/pve/nodes/proxmox2/qemu-server/"

system is not allowing you to recreate or put a copy of the conf file on that folder.

Thus, anyone has this problem and solution to this?

I had this issue as well. My system had moved moved the conf file to a different node on my cluster but left the virtual disk on the original. This broke the VM.

to resolve I made a backup of the conf file using WinSCP to transfer a copy off the server. then found the VM in the web gui and removed that vm. Next I copied the conf to the node that had the virtual disk.

In the gui the vm showed up and I was able to start the vm without issue.

 

[Patricio11CG]

Hola, me pueden ayudar, cambie el nombre de mi nodo y ahora no puedo iniciar las máquinas virtuales

 

[Andre_x]

Hola, me pueden ayudar, cambie el nombre de mi nodo y ahora no puedo iniciar las máquinas virtuales

Hi, how did you solve this problem?

 

[DeadTedX]

To better clarify ccms above, the qm commands are not meant for Containers, you should use pct commands, so the proper way to unlock a Container is pct unlock <container>. Verify that your VM is actually and qemu VM before executing qm commands.

This is the answer you are looking for if qm doesn't work. Thanks @Kenny.Petty