Once installed, ordinarily you shouldn’t need to update again (with certain exceptions). I’m just tired of every time a new kernel is installed vmware might or might not be able to compile a new driver so instead of all those headaches I’m going to try kvm with virt-manager for a replacement. Thanks, it’s just a windows 10 image that I was using under vmware on arch…and it’s a single vmware virtual disk file. But if you do run into a problem then a number of imaging backup apps might fix the problem… Those apps are often created with the ability to restore to dissimilar hardware. Ordinarily, your old system should run just fine in new virtualization, no matter the virtualization the virtualized hardware is known and embedded in the kernel nowadays. Prepare your diskfile by zero-ing out the empty space in the diskfile and compact it before converting.optimize your working physical disks first, a highly fragmented file on an HDD can take much longer than a disk where the files have been compacted and defragmented.For this reason I always create my diskfiles as a single file instead of multiple files which is often the default (typically 2GB files which presumably is for deploying on 32bit file systems). Consolidate your diskfile into one file.BTW - It’s why I generally build my Production machines to use the “raw” disk format, although it might perform a little less than whatever the recommended might be, it’s universally recognized by all virtualization. If you’re not sure whether you found the right utility, post here and ask first. If the current disk format is not supported or you just want to change to something else, then do a search “convert … to …” and run the utility. If it is, then copy the diskfile and try to create a virtual machine using it. Check first whether your current disk format is supported by your new virtualization.

Convert vmdk to bootable iso