Windows Server 2022

[Pascal179]

Wenn ich meinen Windows VM Starten möchte bekomme ich folgenden Error:


()

Task viewer: VM 100 - Start

AusgabeStatus

Stopp
kvm: -drive file=/media/hdd/images/100/vm-100-disk-0.qcow2,if=none,id=drive-ide1,discard=on,format=qcow2,cache=none,aio=io_uring,detect-zeroes=unmap: Could not read qcow2 header: Input/output error
TASK ERROR: start failed: QEMU exited with code 1

Danke an jede hilfe

 

[apmuthu]

Check if the file: /media/hdd/images/100/vm-100-disk-0.qcow2 exists

Which version of Proxmox are you using?

If you migrated your VM from VMWare or VirtualBox or afrom any other virtualisation platform, the paths may be different.

 

[Pascal179]

Check if the file: /media/hdd/images/100/vm-100-disk-0.qcow2 exists

Which version of Proxmox are you using?

If you migrated your VM from VMWare or VirtualBox or afrom any other virtualisation platform, the paths may be different.

Ich benutzen die Version 7.2-11

Ja diese datei ist vorhanden

 

[apmuthu]

Then it should be a relative path and not such an absolute one you have.
In one windows machine that has a qcow2 file for the virtual hdd, I have:

bootdisk: ide0
cores: 1
cpu: kvm32
ide0: local:150/vm-150-disk-0.qcow2,size=32G
ide2: none,media=cdrom
memory: 1024
name: WinXPN01
net0: e1000=12:34:56:78:9A:BC,bridge=vmbr0
onboot: 1
ostype: wxp
sockets: 1

 

[apmuthu]

The actual path of the config file is:
/etc/pve/nodes/<NODE>/qemu-server/101.conf
and the qcow2 file is in:
/var/lib/vz/images/150/vm-150-disk-0.qcow2

 

[Pascal179]

Okay verstehe

The actual path of the config file is:
/etc/pve/nodes/<NODE>/qemu-server/101.conf
and the qcow2 file is in:
/var/lib/vz/images/150/vm-150-disk-0.qcow2

Okay verstehe und was genau muss ich jetzt ändern ?

 

[apmuthu]

Check your config file - /etc/pve/nodes/<NODE>/qemu-server/<VMID>.conf
and suitably correct the path to be relative like the one I showed.
Then make sure the storage path to your QEMU Disk Images in the PVE GUI matches the physical location that I have alluded to by moving your qcow2 file is moved to somewhare like:
/var/lib/vz/images/<VMID>/vm-<VMID>-disk-0.qcow2

In your case it might be:

mv /media/hdd/images/100/vm-100-disk-0.qcow2 /var/lib/vz/template/images/100/vm-100-disk-0.qcow2

 

[fiona]

Hi,

Check your config file - /etc/pve/nodes/<NODE>/qemu-server/<VMID>.conf
and suitably correct the path to be relative like the one I showed.
Then make sure the storage path to your QEMU Disk Images in the PVE GUI matches the physical location that I have alluded to by moving your qcow2 file is moved to somewhare like:
/var/lib/vz/images/<VMID>/vm-<VMID>-disk-0.qcow2

In your case it might be:

mv /media/hdd/images/100/vm-100-disk-0.qcow2 /var/lib/vz/template/images/100/vm-100-disk-0.qcow2

@Pascal179 said that the file does exist at the path given to the kvm command, so I think moving the image would rather make the configuration outdated and not help.

@Pascal179 Are there any messages about I/O errors in /var/log/syslog about the disk the image resides on?
If not, please share the output of

qemu-img info /media/hdd/images/100/vm-100-disk-0.qcow2
qemu-img check /media/hdd/images/100/vm-100-disk-0.qcow2
pveversion -v