This can work even with only one Wi-Fi/Ethernet connection, but if you’ve got a network card with multiple Ethernet ports, you can assign an entire interface directly to a VM. The VM has an actual IP address on your network.

Bridged, which bridges the physical connection straight to the VM.

The NAT network acts as a virtual subnet.

NAT Network, is similar to NAT, except the network is shared among the VMs, and they can talk to each other.

This doesn’t allow VMs to talk to each other, and doesn’t allow host-to-guest contact unless port forwarded.

NAT, the simplest, which simply allows the VM to communicate to the outside world using network address translation (NAT).

Next, we’ll create the network that this VM will use. Sudo VBoxManage modifyvm 'Ubuntu' -largepages on

Then, flip some performance-related switches to prevent slowdowns from excess RAM usage: sudo VBoxManage modifyvm 'Ubuntu' -nestedpaging on

Sudo VBoxManage storageattach 'Ubuntu' -storagectl 'IDE Controller' -port 0 -device 0 -type dvddrive -medium '/home/user/Ubuntu.iso' sudo VBoxManage storagectl 'Ubuntu' -name 'IDE Controller' -add ide -controller PIIX4 This assumes your ISO is located at /home/user/Ubuntu.iso, so change it accordingly. We’ll do the same for the disk that will hold the ISO to install the OS. Sudo VBoxManage storagectl 'Ubuntu' -name 'SAS Controller' -hostiocache on Sudo VBoxManage storageattach 'Ubuntu' -storagectl 'SAS Controller' -port 0 -device 0 -type hdd -medium 'Ubuntu.vdi' Sudo VBoxManage storagectl 'Ubuntu' -name 'SAS Controller' -add sas -controller LSILogicSAS

Ubuntu server iso virtualbox