operating-system icon indicating copy to clipboard operation
operating-system copied to clipboard

mport OVA in vmware >7 --> Line 30: Unsupported hardware family 'vmx-10'.

Open andrewt81 opened this issue 1 year ago • 4 comments

Describe the issue you are experiencing

When trying to import OVA in vmware >7 i receive error

Line 30: Unsupported hardware family 'vmx-10'.

I can bypass the error manually editing with ovftool but should be >vmx-11 by default

What operating system image do you use?

ova (for Virtual Machines)

What version of Home Assistant Operating System is installed?

11.5

Did you upgrade the Operating System.

Yes

Steps to reproduce the issue

When trying to import OVA in vmware >7 i receive error

Line 30: Unsupported hardware family 'vmx-10'.

I can bypass the error manually editing with ovftool but should be >vmx-11 by default

Anything in the Supervisor logs that might be useful for us?

no

Anything in the Host logs that might be useful for us?

no

System information

no

Additional information

No response

andrewt81 avatar Feb 09 '24 17:02 andrewt81

I am sorry to say so, but is vmWare ESX at all a valid target virtualization platform for HomeAssistant anymore since Broadcom crushes vmWare stuff to the ground, thus no free ESXi, etc.? I actually do feel that in future using the ova images with vmWare products is about to end at some point, thus only forum community might help to keep up some compatibility...

jens-maus avatar Feb 12 '24 16:02 jens-maus

I'm aware of the broadcom plans.. but until free esxi are available and .ova are released regularly i think is reasonable to give to the community an "effort free" tool

andrewt81 avatar Feb 12 '24 16:02 andrewt81

I'm aware of the broadcom plans.. but until free esxi are available and .ova are released regularly i think is reasonable to give to the community an "effort free" tool

First of all, the "plans" have just gone reality, see:

https://kb.vmware.com/s/article/2107518

Thus, no free ESXi anymore. However, I do of course not suggest to drop the OVA platform altogether, since this is still a standard and the ova images can be used by other virtualization solutions like Synology VMM, etc. which are Qemu/KVM based. I am just saying that now after the End-of-Life of free ESXi the focus has clearly shifted now to free virtualization platforms like ProxmoxVE. Thus, IMHO the focus of the OVA support in HomeAssistantOS should also clearly focus on these free and IMHO also more powerful platforms and every still existing user of ESX should consider moving over better now than too late...

jens-maus avatar Feb 13 '24 15:02 jens-maus

There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant OS version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] avatar May 14 '24 05:05 github-actions[bot]