Jump to content
XPEnology Community

Search the Community

Showing results for tags 'nested virtualizatio'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Information
    • Readers News & Rumours
    • Information and Feedback
    • The Noob Lounge
  • XPEnology Project
    • F.A.Q - START HERE
    • Loader Releases & Extras
    • DSM Updates Reporting
    • Developer Discussion Room
    • Tutorials and Guides
    • DSM Installation
    • DSM Post-Installation
    • Packages & DSM Features
    • General Questions
    • Hardware Modding
    • Software Modding
    • Miscellaneous
  • International
    • РУССКИЙ
    • FRANÇAIS
    • GERMAN
    • SPANISH
    • ITALIAN
    • KOREAN

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 1 result

  1. Following is my setup Core i5-4250u running windows and then VMWorkstation 15.5 Pro. Inside VMWorkstation, running 1.04(b) loader DS918+ - Lets say SYN-A Now inside SYN-A running two virtual machines (Windows 10 Lite and another Synology SYN-B) SYN A has two NICs, One is bridged to local LAN and other is Natted (VMWorkstation NAT) Issue is that Windows Lite is getting the IP on both NICs but SYN-B is booting but not getting an IP on boot I have already checked Virtualiz Intel VT-x/EPT or AMD-V/RVI inside the SYN-A properties of CPU for SYN-A in VMWorkstation. Does anyone know why I am not able to get the IP for the SYN-B (Nested virtualization - SYN B is nested inside SYN A)? Read some posts that it is Ubuntu issue with NIC not enabled for promiscuous mode in nested situation. Any other clues or thoughts?
×
×
  • Create New...