Changes between Initial Version and Version 1 of Ticket #11160, comment 14
- Timestamp:
- Nov 8, 2023 9:23:34 PM (6 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #11160, comment 14
initial v1 1 1 11 years after the creation of this ticket, it is still an issue. Virtualbox exported as ovf v. 1.0 cannot be imported into VMware. Only difference is, now, the workaround hack suggested elsewhere, changing the virtualsystemtype line to `<vssd:VirtualSystemType>vmx-06</vssd:VirtualSystemType>`, no longer solves the problem. 2 2 3 I especially don't trust running a vm imported the "--lax" option. You don't fix errors by turning the error messages off.3 I especially don't trust running a vm imported with the "--lax" option. You don't fix errors by turning the error messages off. The ovf disks need to be formatted correctly, and not require you to loosen standards to use them. The standards are strict for a reason. 4 4 5 5 I am going to rebuild my vm from scratch in VMware and not use VirtualBox again, since this makes it appear undependable.
