VMware ESXi and vSphere Cluster Management
Virtual Networking in Oracle VirtualBox
Learn how VirtualBox virtual network adapters, guest drivers, hardware models, and network modes work together, including PCNet, Intel PRO/1000, and virtio-net.
Virtual networking lets a guest operating system communicate through a network interface presented by Oracle VirtualBox. The guest sees a virtual PCI Ethernet card, while VirtualBox connects that card to a host, external network, another guest, or an isolated virtual network according to the selected network mode.
The adapter hardware model and the network mode are separate decisions. The hardware model determines which network controller the guest believes it has. The network mode determines where that controller is connected. A correct adapter model does not guarantee connectivity if the attachment mode is unsuitable, and a correct network mode cannot help if the guest lacks a driver for its adapter.
For an overview of the configuration area, see Virtual Networking.
How VirtualBox virtual networking works
A network adapter is the virtual Ethernet device configured for a virtual machine (VM). VirtualBox presents the device to the guest as PCI hardware. The guest operating system detects the PCI device, loads a matching network driver, and uses that driver to send and receive Ethernet traffic.
Behind the guest device, VirtualBox applies the selected attachment or network mode. Depending on that choice, traffic can be connected to the host, an external physical network, other virtual machines, or a private network that is not connected to the outside.
- Virtual adapter hardware: the controller model presented to the guest, such as AMD PCNet or Intel PRO/1000.
- Guest driver: software inside the guest that recognizes and operates that controller.
- Network mode: the VirtualBox connection method that determines the adapter's reachable network.
Virtual network adapter capacity
A VirtualBox VM can be configured with up to eight virtual PCI Ethernet adapters. Each position is called an adapter slot. An enabled slot can have its own adapter hardware model and its own attachment setting.
Multiple adapters are useful when a guest has separate network roles, for example:
- A management adapter for administration traffic.
- A LAN-facing adapter for access to a connected network.
- A test adapter for a controlled lab network.
- An isolated adapter for service-to-service traffic that should not reach other networks.
Inside the guest, each adapter normally appears as a separate network interface. Use distinct interface names, addresses, or routing rules so that the guest can apply the intended role to each interface.
VirtualBox virtual network adapter models
VirtualBox can emulate several familiar physical Ethernet controllers. Hardware emulation means that VirtualBox presents a software model of a known controller so that an existing guest driver can operate it.
Choosing an adapter based on guest drivers
The most important selection criterion is the network driver available in the guest operating system. Do not assume that the default AMD PCNet FAST III model will work in every guest. Check whether the guest recognizes the controller and has an active driver before investigating IP addresses or network modes.
Emulated adapters and virtio-net
The AMD and Intel choices emulate conventional physical Ethernet controllers. A guest can often use them with drivers that were designed for real hardware of the same model.
virtio-net is different. It does not pretend to be an AMD or Intel physical Ethernet controller. It is a paravirtualized adapter: a virtual device designed for a driver that understands virtualization directly.
Paravirtualization may provide efficiency benefits because the guest and hypervisor use a virtualization-aware interface rather than reproducing every behavior of a physical controller. The trade-off is compatibility. A guest without a suitable virtio driver may show an unknown device or no usable network interface at all.
Adapter hardware versus network mode
Choosing an adapter model is only one part of VirtualBox network configuration. The network mode, also called the attachment type, determines how VirtualBox connects the selected virtual adapter.
For example, an Intel PRO/1000 adapter can be attached through NAT to provide translated outbound access, or through bridged networking to connect more directly to a physical network. The adapter model remains an Intel controller; only its connection path changes.
Configuration workflow
- Select the VM in VirtualBox Manager.
- Open Settings and select Network.
- Choose an adapter slot, such as Adapter 1, and enable Enable Network Adapter.
- Select the attachment or network mode appropriate to the goal. Consider whether the guest needs access to the host, an external network, other guests, or an isolated virtual network.
- Select the Adapter Type based on guest driver support and interoperability requirements.
- Enable the cable-connected setting when the virtual link should be active.
- Repeat the process for additional adapter slots if the VM needs separate management, LAN, test, or isolated networks.
- Boot the guest and verify that its operating system detects the selected controller.
- Confirm that a suitable driver is installed and active.
- Test address assignment, such as DHCP or a configured static address, and then test basic network reachability.
Practical configuration examples
General-purpose guest using the default adapter
Configure Adapter 1 as AMD PCNet FAST III and select a suitable network mode. This is a reasonable starting point for a guest with a compatible built-in PCNet driver. After booting, confirm that the guest detects the adapter and obtains or can use an IP address.
Vista or later without a usable PCNet driver
Change the adapter type to Intel PRO/1000 MT Desktop. Boot the guest and check whether its included Intel driver recognizes the device. If the controller appears correctly, retest address assignment and connectivity.
Windows XP adapter selection
For a Windows XP guest where out-of-box recognition is important, try Intel PRO/1000 T Server. Verify device detection first. Only after the guest has a functioning interface should you diagnose the network mode, addressing, or routing.
Imported appliance
An imported appliance may retain assumptions about its original virtual hardware. For an appliance imported using the Open Virtualization Format (OVF), try Intel PRO/1000 MT Server when compatibility with its expected network device is required. After changing the adapter, check the guest's interface names and network configuration because the guest may treat the device as a new interface.
Performance-oriented guest with virtio drivers
Select Paravirtualized Network (virtio-net) only when the guest includes or can be supplied with a virtio network driver. The guest should identify it as a virtio device, not as a conventional AMD or Intel Ethernet controller.
VM with separate network roles
Enable multiple adapter slots. Attach one adapter to a management-oriented network mode and another to an isolated or service network. Inside the guest, use interface naming and separate addressing to distinguish the roles. With up to eight adapters available, a single VM can model several network segments for testing or administration.
Troubleshooting virtual adapter problems
Unknown Ethernet controller or no usable interface
- Determine which adapter model is configured in VirtualBox.
- Check whether the guest has a driver for that model.
- If virtio-net is selected, confirm that the virtio network driver is installed.
- Install a suitable driver or select an emulated adapter supported by the guest.
- For older Windows guests, try the Intel model appropriate to the guest version.
Vista-or-later guest has no network with the default adapter
The guest may not include the required AMD PCNet driver. Switch to Intel PRO/1000 MT Desktop, restart or request hardware detection in the guest, and verify that the Intel driver is loaded.
Windows XP does not work with the selected Intel adapter
The selected Intel emulation may not match the driver bundled with the guest. Try Intel PRO/1000 T Server and confirm that Windows XP recognizes the device before changing broader network settings.
Imported appliance has network problems
The appliance may expect a different emulated controller. Review the adapter type, try Intel PRO/1000 MT Server when compatibility with the imported OVF-based guest is needed, and check the guest interface configuration after the change.
Guest recognizes the adapter but cannot reach the intended network
- Verify that the cable-connected setting is enabled when appropriate.
- Check the selected network mode or attachment.
- Confirm the guest's IP address, subnet, default route, and name-resolution configuration.
- Test basic reachability separately from DNS or application access.
- Keep the diagnosis separated: a recognized adapter with a loaded driver usually points toward attachment, addressing, routing, or policy rather than hardware emulation.
Exam-relevant summary
- VirtualBox presents a guest with a virtual PCI Ethernet card.
- A VM can have up to eight virtual PCI Ethernet adapters.
- Each enabled adapter can have an independent hardware model and network attachment.
- AMD PCNet FAST III, using the Am79C973 model, is the default adapter type.
- AMD PCNet PCI II uses the Am79C970A model.
- Intel PRO/1000 MT Desktop uses 82540EM, Intel PRO/1000 T Server uses 82543GC, and Intel PRO/1000 MT Server uses 82545EM.
- virtio-net is paravirtualized and requires a suitable guest virtio driver.
- Adapter hardware selection answers “what controller does the guest see?” Network mode answers “where is that controller connected?”
- Always verify guest driver availability instead of assuming the default adapter will work.