Error creating the windows 11 snapshot

F

frankz

Renowned Member
Nov 16, 2020
417
27
68
I don't have a snapshot on just one Windows 11 VM on NFS disk and in HA.

saving VM state and RAM using storage 'zshare'
3.01 MiB in 0s
997.32 MiB in 1s
1.39 GiB in 2s
1.86 GiB in 3s
1.93 GiB in 4s
completed saving the VM state in 5s, saved 2.02 GiB
snapshotting 'drive-ide0' (evo1tb:124/vm-124-disk-2.qcow2)
snapshotting 'drive-efidisk0' (evo1tb:124/vm-124-disk-0.qcow2)
snapshotting 'drive-tpmstate0' (evo1tb:124/vm-124-disk-1.qcow2)
WARNING: Image format was not specified for '/mnt/pve/evo1tb/images/124/vm-124-disk-1.qcow2' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format explicitly to remove the restrictions.
qemu-img: Could not create snapshot 'office': -95 (Operation not supported)
snapshot create failed: starting cleanup
 
Moayad said:
Hello,

may you post the VM config qm config VMID?
Click to expand...
Code: 
acpi: 1
agent: 1
balloon: 0
bios: ovmf
boot: order=ide0;ide2;net0
cores: 2
efidisk0: evo1tb:124/vm-124-disk-0.qcow2,efitype=4m,pre-enrolled-keys=1,size=528K
hotplug: disk,network,usb
ide0: evo1tb:124/vm-124-disk-2.qcow2,cache=writeback,discard=on,size=80G,ssd=1
ide2: none,media=cdrom
machine: pc-q35-6.1
memory: 2048
name: win11
net0: virtio=7A:CA:D2:CB:F5:76,bridge=vmbr0
numa: 0
onboot: 1
ostype: win10
protection: 1
scsihw: virtio-scsi-pci
smbios1: uuid=648e64ac-f8da-4f62-9e00-b8502a22c4b6
sockets: 1
tpmstate0: evo1tb:124/vm-124-disk-1.qcow2,size=4M,version=v1.2
vmgenid: 3ab55969-f039-49f9-bf1d-91352870acb6
vmstatestorage: zshare
 
Hi,

Thank you for the VM config!

frankz said:
WARNING: Image format was not specified for '/mnt/pve/evo1tb/images/124/vm-124-disk-1.qcow2' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format explicitly to remove the restrictions.
Click to expand...
is the image for the VM qemu? can you check for that using `qemu-img` tool? you can check using e.g command:

Bash: 
qemu-img info /path/to/the/VM/vm-124-disk-0.qcow2
qemu-img info /path/to/the/VM/vm-124-disk-1.qcow2
qemu-img info /path/to/the/VM/vm-124-disk-0.qcow2
 
Moayad said:
Hi,

Thank you for the VM config!


is the image for the VM qemu? can you check for that using `qemu-img` tool? you can check using e.g command:

Bash: 
qemu-img info /path/to/the/VM/vm-124-disk-0.qcow2
qemu-img info /path/to/the/VM/vm-124-disk-1.qcow2
qemu-img info /path/to/the/VM/vm-124-disk-0.qcow2
Click to expand...
Code: 
root@pve3:/etc/pve/qemu-server# qemu-img info /mnt/pve/evo1tb/images/124/vm-124-disk-0.qcow2
image: /mnt/pve/evo1tb/images/124/vm-124-disk-0.qcow2
file format: qcow2
virtual size: 528 KiB (540672 bytes)
disk size: 48.5 KiB
cluster_size: 65536
Format specific information:
    compat: 1.1
    compression type: zlib
    lazy refcounts: false
    refcount bits: 16
    corrupt: false
    extended l2: false

The GUI also refers to only qcow2

11111.png

Code: 
root@pve3:/etc/pve/qemu-server# qemu-img info /mnt/pve/evo1tb/images/124/vm-124-disk-1.qcow2
image: /mnt/pve/evo1tb/images/124/vm-124-disk-1.qcow2
file format: raw
virtual size: 8.5 KiB (8704 bytes)
disk size: 4.5 KiB

Code: 
root@pve3:/etc/pve/qemu-server# qemu-img info /mnt/pve/evo1tb/images/124/vm-124-disk-
vm-124-disk-0.qcow2  vm-124-disk-1.qcow2  vm-124-disk-2.qcow2
root@pve3:/etc/pve/qemu-server# qemu-img info /mnt/pve/evo1tb/images/124/vm-124-disk-2.qcow2
image: /mnt/pve/evo1tb/images/124/vm-124-disk-2.qcow2
file format: qcow2
virtual size: 80 GiB (85899345920 bytes)
disk size: 16.7 GiB
cluster_size: 65536
Format specific information:
    compat: 1.1
    compression type: zlib
    lazy refcounts: false
    refcount bits: 16
    corrupt: false
    extended l2: false

I think only one disk image is raw.
 
Last edited:
Hello,

frankz said:
I think only one disk image is raw.
Click to expand...
Yep, the vm-124-disk-1.qcow2 look like a raw format (file format: raw) can you try to convert it to qemu and try the snapshot again?

Please make sure that you have a valid backup for the VM before you convert the VM image to qemu format.
 
Moayad said:
Hello,


Yep, the vm-124-disk-1.qcow2 look like a raw format (file format: raw) can you try to convert it to qemu and try the snapshot again?

Please make sure that you have a valid backup for the VM before you convert the VM image to qemu format.
Click to expand...
Can you give me the syntax for conversion? Just so as not to make mistakes ...
 
Moayad said:
such as:

Bash: 
qemu-img convert -f raw vm-124-disk-1.qcow2 -O qcow2 vm-124-disk-1.qcow2 -p
Click to expand...
Ok, the conversion was performed, but when the VM starts:


Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Mon Feb 28 11:36:36 CET 2022 from 192.168.3.34 on pts/0
root@pve3:~# qemu-img info /mnt/pve/evo1tb/images/124/vm-124-disk-1.qcow2
image: /mnt/pve/evo1tb/images/124/vm-124-disk-1.qcow2
file format: qcow2
virtual size: 8.5 KiB (8704 bytes)
disk size: 20.5 KiB
cluster_size: 65536
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
root@pve3:~# qemu-img info /mnt/pve/evo1tb/images/124/vm-124-disk-1.qcow2
image: /mnt/pve/evo1tb/images/124/vm-124-disk-1.qcow2
file format: raw
virtual size: 4.5 KiB (4608 bytes)
disk size: 4.5 KiB
root@pve3:~#
 
Hi,
the TPM state file needs to be in raw format, because swtpm doesn't know how to handle qcow2 files. If you need snapshots, you should move the disk to a storage that supports snapshotting raw volumes.
 
  • Like
Reactions: frankz and Moayad
Fabian_E said:
Hi,
the TPM state file needs to be in raw format, because swtpm doesn't know how to handle qcow2 files. If you need snapshots, you should move the disk to a storage that supports snapshotting raw volumes.
Click to expand...
Okay, now everything is explained! Especially the fact that converting a .raw image to qcow2 immediately after it is converted to raw at the start of the ha and the VM
 
You must log in or register to reply here.
Top Bottom