What you need to do if you have taken a dd or real raw image dump of a hard disk:
VBoxManage convertdd windows2019-eval-template.img windows2019.vdi --format VDI
The .img is the raw dd dump and the .vdi is the output file.
--format VDI specifies to output to .vdi format
If you are in a pinch you can always use qemu-kvm binary and manually specify the .img as your disk and it will just work.
*Even the above didn't work for some reason with VBOX
VBoxManage convertdd windows2019-eval-template.img windows2019.vdi --format VDI
Converting from raw image file="windows2019-eval-template.img" to file="windows2019.vdi"...
Creating dynamic image with size 21474836480 bytes (20480MB)...
*Note if you are mounting the .vdi over SMB or SSHFS you may still get the below error (sometimes it only works well locally)
VD: error
VERR_NET_OPERATION_NOT_SUPPORTED
I tried the raw image and you get:
Could not get the storage format of the medium (VERR_NOT_SUPPORTED).
Then I converted it to qcow2:
qemu-img convert -f raw -O qcow2 windows2019-eval-template.img windows2019-eval-template.qcow2
But I still got the same error.
So then I tried to convert it to .vdi:
qemu-img convert -f raw -O vdi windows2019-eval-template.img windows2019-eval-template.vdi
VD: error
VERR_NET_OPERATION_NOT_SUPPORTED
The original partition of the .img looks like this:
fdisk -l windows2019-eval-template.img
Disk windows2019-eval-template.img: 21.5 GB, 21474836480 bytes
255 heads, 63 sectors/track, 2610 cylinders, total 41943040 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xb5ad7258
Device Boot Start End Blocks Id System
windows2019-eval-template.img1 * 2048 1126399 562176 7 HPFS/NTFS/exFAT
windows2019-eval-template.img2 1126400 41940991 20407296 7 HPFS/NTFS/exFAT