VirtualBox

Changes between Initial Version and Version 1 of Ticket #4032, comment 138


Ignore:
Timestamp:
06/22/2018 06:35:14 AM (6 months ago)
Author:
tylerbyte
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #4032, comment 138

    initial v1  
    77I have Vbox 5.2 & Ubuntu Server 16.04 installed on the host, The Ubuntu Server VM runs docker and Vbox 5.2 as well.  
    88 
    9 I thought I would also need the nested virtualization as discussed here but... (Knowing the CPU feature is i-fact enabled in the bios) it seems it won't help adding this feature to vbox at all. 
     9I thought I would also need the nested virtualization as discussed here but... (Knowing the CPU VT-X feature is in-fact enabled in the bios) it seems it won't help adding this feature to vbox at all. 
    1010 
    1111'''Due to an issue with the command:''' 
     
    2929"(myvm1)Awaiting an IP".... 
    3030 
    31 Any thoughts on that issue then we may have a solution to the docker guys needing this feature as it would save you guys a lot of time. 
     31Any thoughts on that issue then we may have a solution to the docker guys needing this feature as it would save you guys a lot of time.  
    3232 
    3333Thanks :) 
    3434 
     35'''//UPDATE\\''' 
     36After installing UbuntuServer 16.04 LTS fresh on brand new desktop with the VTX feature enabled, my waiting for in ip issue disappeared, virtual box has given me zero issues. 
     37 
     38Maybe fix a nested host adapter make it bridge to the original network, might be easier than nested cpu virtualization :) 
     39 
     40Hope this helps somebody! Lotsa luck coding! 
     41 
     42 

www.oracle.com
ContactPrivacy policyTerms of Use