VirtualBox客户虚拟机网络故障排查：无法访问互联网

Hey there! Let's troubleshoot this VirtualBox network issue step by step. Since you mentioned everything was working smoothly before, this is almost certainly a small config hiccup or a subtle system change that's throwing things off. Let's start with the most likely culprits:

First, let's make sure VirtualBox is bridging to the right network interface:

• Open VirtualBox, go to File > Host Network Manager. Confirm your laptop's wireless adapter is listed here and isn't disabled.
• For each problematic VM, go to Settings > Network. Ensure Network Adapter 1 is set to "Bridged Adapter", and the dropdown menu selects your actual wireless card (it might be named something like wlan0 or have a brand-specific name). Don't forget to check "Enable Network Adapter"—it's easy to accidentally uncheck that!

Since your host is Debian, let's rule out permission issues and confirm the host's network is solid:

• Check if your user is in the vboxusers group (required for VirtualBox to access network adapters): run groups in your terminal. If vboxusers isn't listed, add yourself with sudo usermod -aG vboxusers $USER, then log out and back in.
• Confirm your host's wireless connection is working: run ip a to check if your wireless adapter (e.g., wlan0) has a valid IP address and shows UP status. If the host can't connect either, that's a separate issue—but you said the host is fine, so this is just a sanity check.
• Quick Docker sanity check: Run docker network ls to see if any Docker networks are using the same IP range as your home router. While you said Docker works, it's rare but possible for a Docker bridge to conflict with VirtualBox's bridging.

Let's dive into each VM's settings:

Windows 7 VM #

• Open Control Panel > Network and Sharing Center > Change Adapter Settings. Right-click the network adapter, select Properties, and confirm "Internet Protocol Version 4 (TCP/IPv4)" is checked, and set to "Obtain an IP address automatically" and "Obtain DNS server address automatically".
• Open Command Prompt and run ipconfig /release followed by ipconfig /renew to force a DHCP refresh. If it still doesn't get an IP, try setting a static IP in the same range as your host (e.g., if host is 192.168.1.100, use 192.168.1.105, gateway = your router's IP, DNS = router IP or 8.8.8.8), then ping the router to test connectivity.

Debian VM #

• Open a terminal and run ip a to check if your VM's network adapter (e.g., enp0s3) has an IP address. If not, try restarting the network service:
  • For older Debian versions: sudo systemctl restart networking
  • For newer systems using NetworkManager: sudo nmcli networking off && sudo nmcli networking on
• Manually request a DHCP address with sudo dhclient enp0s3 (replace enp0s3 with your VM's actual adapter name). Then test connectivity by pinging your router's IP (e.g., ping 192.168.1.1) and a public IP like ping 8.8.8.8—this will tell you if it's a connectivity issue or a DNS problem.

Debian kernel updates can sometimes break VirtualBox's kernel modules:

• Check your current VirtualBox version with virtualbox --version. If it's not the latest available, update it with:

  sudo apt update && sudo apt install --only-upgrade virtualbox
  

• Reload VirtualBox's kernel modules to fix any mismatches:

  sudo modprobe vboxnetflt
  sudo modprobe vboxdrv
  

• If you get errors here, reinstall the DKMS package to rebuild modules for your current kernel:

  sudo apt install virtualbox-dkms
  

  Then reboot your host and try the VMs again.

To narrow down the issue, switch the VM's network mode to NAT (instead of Bridged) and start the VM. If NAT works, the problem is specific to bridged mode (likely host adapter permissions or router DHCP settings). If NAT also fails, the issue is either with VirtualBox itself or a deeper VM network config problem.

Start with the first couple of steps—they're the most common fixes for suddenly broken bridged networking. Let me know which step leads you to the root cause!

内容的提问来源于stack exchange，提问作者jia103