enesdemir wrote:i couldn't figure out what should i do completely..
No problem. In the main Virtualbox window, click on New. Run through the wizard to make a Windows 10 VM with a new vdi disk file. Once the wizard completes, you'll have a new Windows 10 VM in the VM list. No need to actually install 10 in the new VM. Now right-click that VM and export it. Once the export completes, the OVF will show how Virtualbox labels its SATA controller in the OVF standard format. Snice you're able to edit the OVF file for the VMware VM, you can copy the SATA controller code into the VMware OVF. This should put the VMware Windows 10's disk file on a SATA controller instead of the faulting NVME controller. Try to import the edited VMware OVF. If it imports, try to run the VM. If it works, then you're done.
If the VM imports but the VM does not boot (perhaps because there's something special about the NVME controller) you could edit the new VM you made with the wizard to add an NVME controller then move its disk file from the default SATA to the new NVME. Then try the export and VMware OVF edit again.
Please note that this concept is all theoretical; I haven't had the need to try it myself, so I'm not skilled enough to walk you further through the steps.
enesdemir wrote:I converted all my VMs (Vmware Workstation) to .ovf via Ovftool. After i converted i deleted Vmware Workstation VMs.
Though it amounts to locking the barn door after the horse has escaped, I'd suggest in the future to not delete the good source until the new destination is tested working. Upon seeing the Virtualbox error, you could have moved the 10 VMware VM's drive file from NVME to SATA, confirm that it worked on SATA, then export. Also, Virtualbox can use VMware vmdk format drives directly without conversion, so you could have disconnected the drives from the VMware VMs, export/import the VMs via very tiny OVAs, then reattach the drive files in Virtualbox. Just some thoughts for future projects.