Closed Raizo62 closed 1 week ago
I manually run the node (not linked) and noticed errors like "Could not write to allocated cluster for streamOptimized".
/bin/qemu-system-x86_64 -name Windows-11-Dev-Env2212-2 -m 4096M -smp cpus=4,sockets=1 -enable-kvm -machine smm=off -boot order=c -bios /home/gns3/GNS3/images/QEMU/OVMF-edk2-stable202305.fd -device ahci,id=ahci0 -drive file=/home/gns3/GNS3/images/QEMU/WinDev2212Eval-disk1.vmdk,if=none,id=drive0,index=0,media=disk -device ide-hd,drive=drive0,bus=ahci0.0,id=drive0 -uuid 8b545393-6486-4f7b-bdc8-c53c0451596a -spice addr=localhost,port=5004,disable-ticketing -vga qxl -monitor tcp:127.0.0.1:42701,server,nowait -net none -device e1000,mac=0c:54:53:93:00:00,netdev=gns3-0 -netdev socket,id=gns3-0,udp=127.0.0.1:10001,localaddr=127.0.0.1:10000
qemu-system-x86_64: -spice addr=localhost,port=5004,disable-ticketing: warning: short-form boolean option 'disable-ticketing' deprecated
Please use disable-ticketing=on instead
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]
qemu-system-x86_64: Could not write to allocated cluster for streamOptimized
qemu-system-x86_64: Could not write to allocated cluster for streamOptimized
qemu-system-x86_64: Could not write to allocated cluster for streamOptimized
qemu-system-x86_64: Could not write to allocated cluster for streamOptimized
qemu-system-x86_64: Could not write to allocated cluster for streamOptimized
When checking the disk format I also noticed it says streamOptimized
.
qemu-img info /home/gns3/GNS3/images/QEMU/WinDev2212Eval-disk1.vmdk
image: /home/gns3/GNS3/images/QEMU/WinDev2212Eval-disk1.vmdk
file format: vmdk
virtual size: 125 GiB (134217728000 bytes)
disk size: 22.9 GiB
cluster_size: 65536
Format specific information:
cid: 915282386
parent cid: 4294967295
create type: streamOptimized
extents:
[0]:
compressed: true
virtual size: 134217728000
filename: /home/grossmj/GNS3/images/QEMU/WinDev2212Eval-disk1.vmdk
cluster size: 65536
format:
So I guessed the problem comes from the image being VMDK. I converted the base image to qcow2 using qemu-img convert -f vmdk -O qcow2 /home/gns3/GNS3/images/QEMU/WinDev2212Eval-disk1.vmdk /home/gns3/Downloads/WinDev2212Eval-disk1.qcow2
and imported the new image in the node and it booted correctly.
OK. But it's strange: I would have thought that the problem would have appeared with the particular method of starting a VM (snapshots: the linked VM) and not with the traditional method.
Hi
With the last GNS3 2.2 (on a LiveRaizo)
I tried to run a DEV VM of Win11 with QEMU
The win11 works. I don't see any problems.
But, if i disable the "Use as a linked base VM" in the template, the win11 doesn't boot :