Did that too, before I posted here. Importing as Linux gives the same error as importing as Other OS. Attempting to import directly from VMware fails with a nondescript error message that I can't find a more descriptive log entry for. The Linux import attempt says at least it can't determine the boot drive when it attempts to import it.


On Oct 22, 2023 at 8:03 AM, Strahil Nikolov <hunter86_bg@yahoo.com> wrote:

Have you googled the problem ?

I find a thread with the same error: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/GGOYZKNLBKE4QTCGJ3YFB7HYNNJID5KV/ 

Try to import it as linux and change the type after that ?

I know that Ovirt can directly connecto to VmWare and ‘pull’ the VM, so why don’t you give it a try ?

Best Regards,
Strahil Nikolov 








On Saturday, October 21, 2023, 10:15 PM, Michaal R via Users <users@ovirt.org> wrote:

I am running into an issue that, from what little Google-fu I've been able to use, should be solved in oVirt 4.5. I'm trying to import WS2019 VMs from ESXi 7 as OVFs or even OVAs. But when I do the import and set the OS to Windows Server 2019 x64 in the admin portal, I get the error "Invalid time zone for the given OS type ". If I leave it at Other OS, the import fails with event ID 1153. I've been banging my head against this for over a week (previously couldn't get the management VM to complete setup), so any guidance is appreciated. Let me know what to pull to help me pin this down?

BTW, yes this is a self hosted install as a nested VM on ESXi. Kinda have to right now to test everything (easiest for me over doing a bare metal on my old PowerEdge 2900 at the moment). Running CentOS 9 Stream.
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org