People have a hard time understanding nested virtual machine architectures.  Usually it comes down to "Stop talking and just show me your configs"

Here's a pattern for communication for the purposes of conversational uses, see note below about specification uses

basic:
{ [ name/OS ] [ virtualization ] [ application(s) ] }

more:
{ [ name/OS ] [ virtualization ]
    { [ name/OS ] [ virtualization ] [ application(s) ] }
    { [ name/OS ] [ virtualization ] [ application(s) ] }
}

more more:
{ [ name/OS ] [ virtualization ]
    { [ name/OS ] [ virtualization ] [ application(s) ]
        other [ other parameters]
    }
    { [ name/OS ] [ virtualization ] [ application(s) ]
        [ other parameters]
    }
] }

horribly contrived example:
darwin_macbook3672 vbox
    windows hyperv
            ubuntu-Homestead none appX-client
                other:
                    http: host 8080 -> guest 80
                    db: host 6306 -> guest 3306
            ubuntu-Homestead none appX-api
                selenium
                appX-test
                other:
                    http: host 8080 -> guest 80
    cent66laravel vbox
            linux none appY-client
            linux none appY-api
            linux none
                selenium
                appY-test

Note that if you look at this long enough, it starts to look like a specification language--so take a break and just use it conversationally and don't follow natural tendencies to ruin its conversational utility by forcing it to grow into a full-blown specification language.