VirtualBox

Changes between Initial Version and Version 1 of Ticket #7982, comment 18


Ignore:
Timestamp:
Nov 8, 2023 9:37:54 PM (6 months ago)
Author:
wish it would work

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #7982, comment 18

    initial v1  
    1 Changing VirtualSystemType to either vmx-06 or vmx-14 did not resolve the error for me. Since solving errors but simply turning off error messages is a bad idea, I'm not even going to try importing with the loosened restrictions. I'm just going to rebuild my VM from scratch in VMware and use VMware, since this makes me feel like VirtualBox isn't reliable if I need to get my data out of it.
     113 years and this bug hasn't been fixed. Changing VirtualSystemType to either vmx-06 or vmx-14 did not resolve the error for me. Since solving errors but simply turning off error messages is a bad idea, I'm not even going to try importing with the loosened restrictions. I'm just going to rebuild my VM from scratch in VMware and use VMware, since this makes me feel like VirtualBox isn't reliable if I need to get my data out of it, and knowing that bugs go almost a decade and a half without being fixed doesn't give me the confidence I need to depend on it.

© 2023 Oracle
ContactPrivacy policyTerms of Use