Changes between Initial Version and Version 1 of Ticket #4032, comment 138
- Timestamp:
- Jun 22, 2018 6:35:14 AM (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #4032, comment 138
initial v1 7 7 I have Vbox 5.2 & Ubuntu Server 16.04 installed on the host, The Ubuntu Server VM runs docker and Vbox 5.2 as well. 8 8 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.9 I 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. 10 10 11 11 '''Due to an issue with the command:''' … … 29 29 "(myvm1)Awaiting an IP".... 30 30 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. 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. 32 32 33 33 Thanks :) 34 34 35 '''//UPDATE\\''' 36 After 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 38 Maybe fix a nested host adapter make it bridge to the original network, might be easier than nested cpu virtualization :) 39 40 Hope this helps somebody! Lotsa luck coding! 41 42
