Proxmox VM Icon Shows Question Mark? Fix It Now

Quick answer

Run qm list in the shell. If the VM isn't listed, its config file in /etc/pve/qemu-server/ is missing or corrupt. Restore from your Proxmox backup (vzdump) or recreate the config manually.

Why this happens

I've seen this a bunch of times. The question mark icon means Proxmox's web GUI can't find the VM's config file. Usually it's because someone deleted the file by accident, or a backup restore went wrong. The config file lives at /etc/pve/qemu-server/.conf. If that file is gone or has bad syntax, the GUI shows a question mark instead of the VM icon. The VM still exists in the storage (like local-lvm or ZFS), but Proxmox doesn't know how to start it.

This tripped me up the first time too. I thought the VM was dead. But the disks are still there. You just need to point the GUI back to them.

Fix steps

1. Find the VM ID – Look at the URL in your browser when you click on the question mark. The VM ID is in the address, like qemu/100. Write it down.
2. Check if the config file exists – SSH into your Proxmox host and run:

   ls -la /etc/pve/qemu-server/

   Look for a file named .conf. If it's missing, you're in the right place.
3. Restore from backup – If you have a vzdump backup (maybe in /var/lib/vz/dump/), restore just the config:

   vzdump --restore /path/to/backup/vzdump-qemu--*.vma.lzo 

   This recreates the .conf file. Then refresh the web GUI (F5).
4. No backup? Recreate the config manually – Use qm create with the right settings. For example, if the VM had 2GB RAM and a disk on local-lvm:

   qm create  --memory 2048 --net0 virtio,bridge=vmbr0 --scsihw virtio-scsi-pci --name my-restored-vm

   Then attach the existing disk:

   qm set  --scsi0 local-lvm:vm--disk-0

   (Replace the disk name with what you see in ls /dev/pve/ or pvesm list local-lvm.)
5. Start the VM – Run qm start . If it works, the icon changes back to normal in a few seconds.

Alternative fixes if the main one fails

If restoring or recreating the config doesn't work, try these:

• Check for syntax errors – If the .conf file exists but VM still shows a question mark, open it with nano /etc/pve/qemu-server/.conf. Look for lines like ide2: none,media=cdrom that might have a typo. Fix and save, then refresh the GUI.
• Use the GUI's 'Add' button – Go to your node, click 'Create VM', but set the VM ID to the same ID as the missing one. Proxmox will ask if you want to overwrite. Say yes, then quickly stop the creation (don't add a disk). This often makes the GUI re-scan and show the VM again.
• Check storage status – Sometimes the storage itself is offline. Run pvesm status to see if local-lvm or other storages are active. If they're 'inactive', do pvesm activate .
• Last resort: reinstall pve-manager – Rare, but a corrupt package can do this. Run apt update && apt install --reinstall pve-manager. Then reboot the node.

Prevention tip

Back up your config files separately from the VM disks. I use a cron job to copy /etc/pve/qemu-server/*.conf to a safe location every day. You can also enable Proxmox's automatic backup of the cluster filesystem (pmxcfs) with pmxcfs -l, but manual copies are safer. Write a simple script:

#!/bin/bash
cp /etc/pve/qemu-server/*.conf /root/vm-config-backups/
date >> /root/vm-config-backups/backup.log

This saves you from the question mark heartache. Trust me, I've been there.