Search results

@bbgeek17 many thank for super quick reply. And you have identified the source of the rogue 380GB! root@pve001:/var/lib/vz/template/qcow# qemu-img info WIN-4GSGQMJ1U8A.qcow2 image: WIN-4GSGQMJ1U8A.qcow2 file format: qcow2 virtual size: 477 GiB (512110190592 bytes) disk size: 18.1 GiB...

I have successfully migrated a test Windows server 2022 to Proxmox. Yay! :) The server boots and appears to be working perfectly. . Double Yay! :) :) However, when I issued the command to import the disk: qm importdisk 101 /var/lib/vz/template/qcow/WIN-4GSGQMJ1U8A.qcow2 local-lvm The...

Ok. Thanks to more searching I found the step I was missing from this invaluable site: https://www.vinchin.com/vm-backup/import-qcow2-proxmox.html Follows these instructions and all works ... almost... But I will create a sperate Post

Thankyou for you reply. But the machines re not on the same network.

I am trying to migrate a physical windows test server to Proxmox. These are the steps so far: 1. used Disk2vhd and created a vhd file on a USB Drive. 2. Connected the USB to a Ubuntu machine and ran qemu-img convert -p -f vpc -O qcow2 WIN-4GSGQMJ1U8A.VHD WIN-4GSGQMJ1U8A.qcow2 So, I now...

Just had the same issue after upgrade to Linux 5.15.102-1-pve #1 SMP PVE 5.15.102-1 The code above resolved the problem.. You will need to replace the "pve" above with the correct VG for your volume. which can be found usig the lvs -a command which in may case is "vmvolume". root@pve001:~# lvs...