recreate vm.conf
- Thread starter rkepler
- Start date
You don't say what sort of configuration you typically use in general terms - local storage, iSCSI, multiple network
interfaces, version of Proxmox etc.
The network interface info could be retrieved from your running VMs (e.g. get the MAC address, but you may also
be using bridges/VLANs which complicates things).
Again, number of cores/amount of RAM could be determined from the running VMs (I have no idea what OS
you're running though!).
I think the trickiest thing to resurrect is exactly where all your disks are on either the local filing system or
across the network (e.g. iSCSI).
I think the best way to do this is all via the command line - find another working <VMID>.conf and use that as
a template to start your edits.
Sorry, it's a little vague, but without any more detailed info, it's difficult to help any further.
One tip: make backups of the whole of /etc periodically - I just copy it to another central server using rsync (without the --delete option!). If the proxmox server crashes and burns, it can be resurrected with a re-install of Proxmox and recovery of /etc. This assumes you're using networked filestore like iSCSI (which I recommend, particularly if you ever think you'll cluster 2 or more Proxmoxes together).
How can you lost vm settings? You don't have an backup of you vm's? In the Backup there is the vm.conf. You can extract the file, and copy it back to the server. Or you can copy an vm.conf file from another vm. Change some settings in the file to your vm, and it works again.