Proxmox VM configuration recovery

A missing Proxmox VM configuration can make a guest vanish while its virtual disks remain intact.

Proxmox stores QEMU guest configuration in the cluster filesystem under node-specific qemu-server paths. A failed node, pmxcfs problem, mistaken deletion or cluster recovery can remove the inventory entry without deleting the VM disk.

Understand the symptom

The configuration describes how storage should be attached; the disk content does not recreate every setting.

WHY

What is happening

A VM config records disk bus, boot order, firmware, machine type, CPU, memory, networks, snapshots and device options. Reconstructing only a VMID can attach the right disk with the wrong controller or overwrite a volume through allocation. Cluster quorum and node ownership should be stabilized before moving or recreating config files.

What you may see

Symptoms that change the recovery path.

01

VM disappears from the UI

The guest config is absent from the current pmxcfs view.

02

Disk volumes remain in storage

LVM, ZFS, Ceph or file storage still contains VM-named media.

03

Config exists under a failed node

Cluster state still associates the guest with an unavailable member.

04

Backup lists the guest but restore conflicts

The VMID or target volume names are still present.

Protect the source

Actions that can make the situation worse.

01

New allocation can overwrite a surviving disk

Reusing the VMID and storage name without mapping is dangerous.

02

Wrong bus or firmware changes boot behavior

SCSI, VirtIO, SATA, BIOS and UEFI settings matter.

03

Forced quorum changes cluster state

Config moves while pmxcfs is inconsistent can compound loss.

Do this now

Safe steps before evaluation.

01

Freeze storage allocation

Do not create guests or disks using the missing VMID.

02

Preserve cluster configuration

Copy /etc/pve state, corosync data, storage.cfg, logs and backups.

03

Inventory every candidate disk

Record volume IDs, sizes, snapshots, paths and modification times.

04

Capture known VM settings

Save CMDB records, backup manifests, screenshots and network assignments.

NEPFOSYS process

How a data-first evaluation proceeds.

01

Guest-to-disk mapping

NEPFOSYS correlates VMID history, storage volumes, backups and cluster metadata.

02

Configuration reconstruction

A non-destructive config is tested with protected copies or snapshots.

03

Boot and data validation

Disk order, firmware, filesystems, applications and networking are checked before return.

A clear next step

Preserve the original device before another repair or recovery attempt.

Start a case with the exact symptoms, incident timeline, prior attempts, encryption details, and the files that matter most. NEPFOSYS will route the case to the appropriate DFW intake or nationwide mail-in path.

Start with a case review

Questions, answered

What customers ask before starting.

Where are Proxmox VM configs stored?

QEMU VM configs appear in the Proxmox cluster filesystem under node qemu-server directories.

Can I recreate the config if the disk remains?

Often, but preserve metadata first and match controller, firmware, boot order and storage identity carefully.

Should I force expected votes to move the config?

Not as a routine recovery shortcut. Proxmox warns against cluster-affecting changes while expected votes are forced.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case