Open GitMarshallBill opened 1 year ago
Not sure how much the automatic detection of the Ubuntu (64-Bit) profile affects things, if at all, but I do see on VirtualBox (for example) you can change the profile upon import:
I will pay extra close attention to this with the next build. For now, please select the Other Linux (64-Bit) profile when importing the appliance.
Side note while on that screen: Don't forget to also change the MAC address policy during the import.
I see no place on ESXi 7.0 to change the OS or set new MAC address when creating VM from ova file. If I am missing it, please enlighten me.
In scope for 1.7.
Oddly enough, here's what the NEMS Linux 1.6 source configuration looks like in ESXi:
So it may take some digging why the OVA is then selecting something other than "Other Linux" on import. But at least now I know I didn't build it with the incorrect identifier back when 1.6 was released.
I will do some testing with 1.7 and VirtualBox, and see if I can track down where the issue lies. Perhaps a bug in the ESXi export, but since OVA are an open format, I can edit the XML after the export separately of ESXi, so I'm hopeful I can track this one down.
1.7 OVA detected correctly (Kernel 5.x Linux) in VirtualBox:
Let me know how it looks in ESXi once you test.
When deploying an ova file to VirtualBox or ESXi the Guest OS that gets "chosen" is Ubuntu Linux instead of Debian.