No Network

Discussions related to using VirtualBox on Linux hosts.
Post Reply
Chyr0
Posts: 6
Joined: 11. Jul 2022, 16:52

No Network

Post by Chyr0 »

Hello VirtualBox-Forum,

i just installed(for the second time) a new Linux Mint 20.3 on a new Intel NUC 11 (NUC11PAHi5) and tried to get my virtual Machines working as usually on the older NUCs (5 and 8) i used before (they are still running).
Then i updateted and upgraded the system and installed virtualbox 6.1.34 via apt with no errors.
When i import my old Virtual Machines (Win7 Prof. and Win10 Prof.) they dont get any Network connection. I tried every NIC configuration from the GUI and even installed the virtio driver version 1.171.1 but still no network.


lspci -nnk

Code: Select all

00:00.0 Host bridge [0600]: Intel Corporation Device [8086:9a14] (rev 01)
        DeviceName: Onboard - Other
        Subsystem: Intel Corporation Device [8086:3004]
00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:9a49] (rev 01)
        DeviceName: Onboard - Video
        Subsystem: Intel Corporation Device [8086:3004]
        Kernel modules: i915
00:06.0 PCI bridge [0604]: Intel Corporation Device [8086:9a09] (rev 01)
        Kernel driver in use: pcieport
00:07.0 PCI bridge [0604]: Intel Corporation Device [8086:9a23] (rev 01)
        Kernel driver in use: pcieport
00:07.3 PCI bridge [0604]: Intel Corporation Device [8086:9a29] (rev 01)
        Kernel driver in use: pcieport
00:08.0 System peripheral [0880]: Intel Corporation Device [8086:9a11] (rev 01)
        DeviceName: Onboard - Other
        Subsystem: Intel Corporation Device [8086:3004]
00:0d.0 USB controller [0c03]: Intel Corporation Device [8086:9a13] (rev 01)
        DeviceName: Onboard - Other
        Kernel driver in use: xhci_hcd
00:0d.2 USB controller [0c03]: Intel Corporation Device [8086:9a1b] (rev 01)
        DeviceName: Onboard - Other
        Subsystem: Device [2222:1111]
00:0d.3 USB controller [0c03]: Intel Corporation Device [8086:9a1d] (rev 01)
        DeviceName: Onboard - Other
        Subsystem: Device [2222:1111]
00:14.0 USB controller [0c03]: Intel Corporation Device [8086:a0ed] (rev 20)
        DeviceName: Onboard - Other
        Subsystem: Intel Corporation Device [8086:3004]
        Kernel driver in use: xhci_hcd
00:14.2 RAM memory [0500]: Intel Corporation Device [8086:a0ef] (rev 20)
        DeviceName: Onboard - Other
00:14.3 Network controller [0280]: Intel Corporation Device [8086:a0f0] (rev 20)
        DeviceName: Onboard - Ethernet
        Subsystem: Intel Corporation Device [8086:0074]
        Kernel driver in use: iwlwifi
        Kernel modules: iwlwifi
00:15.0 Serial bus controller [0c80]: Intel Corporation Device [8086:a0e8] (rev 20)
        DeviceName: Onboard - Other
        Subsystem: Intel Corporation Device [8086:3004]
        Kernel driver in use: intel-lpss
        Kernel modules: intel_lpss_pci
00:16.0 Communication controller [0780]: Intel Corporation Device [8086:a0e0] (rev 20)
        DeviceName: Onboard - Other
        Subsystem: Intel Corporation Device [8086:3004]
        Kernel driver in use: mei_me
        Kernel modules: mei_me
00:17.0 SATA controller [0106]: Intel Corporation Device [8086:a0d3] (rev 20)
        DeviceName: Onboard - SATA
        Subsystem: Intel Corporation Device [8086:3004]
        Kernel driver in use: ahci
        Kernel modules: ahci
00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:a0bc] (rev 20)
        Kernel driver in use: pcieport
00:1c.6 PCI bridge [0604]: Intel Corporation Device [8086:a0be] (rev 20)
        Kernel driver in use: pcieport
00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:a082] (rev 20)
        DeviceName: Onboard - Other
        Subsystem: Intel Corporation Device [8086:3004]
00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a0c8] (rev 20)
        DeviceName: Onboard - Sound
        Subsystem: Intel Corporation Device [8086:3004]
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_hda_intel, snd_sof_pci
00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a0a3] (rev 20)
        DeviceName: Onboard - Other
        Subsystem: Intel Corporation Device [8086:3004]
        Kernel driver in use: i801_smbus
        Kernel modules: i2c_i801
00:1f.5 Serial bus controller [0c80]: Intel Corporation Device [8086:a0a4] (rev 20)
        DeviceName: Onboard - Other
        Subsystem: Intel Corporation Device [8086:3004]
01:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd Device [144d:a809]
        Subsystem: Samsung Electronics Co Ltd Device [144d:a801]
        Kernel driver in use: nvme
        Kernel modules: nvme
58:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader [10ec:525a] (rev 01)
        Subsystem: Intel Corporation RTS525A PCI Express Card Reader [8086:3004]
        Kernel driver in use: rtsx_pci
        Kernel modules: rtsx_pci
59:00.0 Ethernet controller [0200]: Intel Corporation Device [8086:15f3] (rev 03)
        Subsystem: Intel Corporation Device [8086:3004]
        Kernel driver in use: igc
        Kernel modules: igc

VBoxManage showvminfo "Win7_64-Klon"

Code: Select all

Name:                        Win7_64-Klon
Groups:                      /
Guest OS:                    Windows 7 (64-bit)
UUID:                        0e70a9ba-3ec7-4f02-a318-452295f28916
Config file:                 /home/administrator/Virtualbox VM/Win7_64-Klon/Win7_64-Klon.vbox
Snapshot folder:             /home/administrator/Virtualbox VM/Win7_64-Klon/Snapshots
Log folder:                  /home/administrator/Virtualbox VM/Win7_64-Klon/Logs
Hardware UUID:               0e70a9ba-3ec7-4f02-a318-452295f28916
Memory size:                 4096MB
Page Fusion:                 disabled
VRAM size:                   128MB
CPU exec cap:                100%
HPET:                        disabled
CPUProfile:                  host
Chipset:                     piix3
Firmware:                    BIOS
Number of CPUs:              1
PAE:                         disabled
Long Mode:                   enabled
Triple Fault Reset:          disabled
APIC:                        enabled
X2APIC:                      disabled
Nested VT-x/AMD-V:           disabled
CPUID Portability Level:     0
CPUID overrides:             None
Boot menu mode:              message and menu
Boot Device 1:               Floppy
Boot Device 2:               DVD
Boot Device 3:               HardDisk
Boot Device 4:               Not Assigned
ACPI:                        enabled
IOAPIC:                      enabled
BIOS APIC mode:              APIC
Time offset:                 0ms
RTC:                         local time
Hardware Virtualization:     enabled
Nested Paging:               enabled
Large Pages:                 disabled
VT-x VPID:                   enabled
VT-x Unrestricted Exec.:     enabled
Paravirt. Provider:          Default
Effective Paravirt. Prov.:   HyperV
State:                       saved (since 2022-07-10T22:58:44.000000000)
Graphics Controller:         VBoxSVGA
Monitor count:               1
3D Acceleration:             enabled
2D Video Acceleration:       disabled
Teleporter Enabled:          disabled
Teleporter Port:             0
Teleporter Address:
Teleporter Password:
Tracing Enabled:             disabled
Allow Tracing to Access VM:  disabled
Tracing Configuration:
Autostart Enabled:           disabled
Autostart Delay:             0
Default Frontend:
VM process priority:         default
Storage Controller Name (0):            SATA
Storage Controller Type (0):            IntelAhci
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0):  30
Storage Controller Port Count (0):      2
Storage Controller Bootable (0):        on
SATA (0, 0): /home/administrator/Virtualbox VM/Win7_64-Klon/Win7_64-Klon.vdi (UUID: 72bdde2a-e2d4-4037-9a03-b77f776eb5da)
SATA (1, 0): /home/administrator/Downloads/virtio-win-0.1.171.iso (UUID: b1293a95-c7a4-4aa4-9164-a0f297ab2f56)
NIC 1:                       MAC: 08002768F0BA, Attachment: Bridged Interface 'enp89s0', Cable connected: on, Trace: off (file: none), Type: virtio, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 2:                       disabled
NIC 3:                       disabled
NIC 4:                       disabled
NIC 5:                       disabled
NIC 6:                       disabled
NIC 7:                       disabled
NIC 8:                       disabled
Pointing Device:             USB Tablet
Keyboard Device:             PS/2 Keyboard
UART 1:                      disabled
UART 2:                      disabled
UART 3:                      disabled
UART 4:                      disabled
LPT 1:                       disabled
LPT 2:                       disabled
Audio:                       enabled (Driver: PulseAudio, Controller: HDA, Codec: STAC9221)
Audio playback:              enabled
Audio capture:               disabled
Clipboard Mode:              Bidirectional
Drag and drop Mode:          disabled
VRDE:                        disabled
OHCI USB:                    disabled
EHCI USB:                    disabled
xHCI USB:                    enabled

USB Device Filters:

<none>

Bandwidth groups:  <none>

Shared folders:<none>

Capturing:                   not active
Capture audio:               not active
Capture screens:             0
Capture file:                /home/administrator/Virtualbox VM/Win7_64-Klon/Win7_64-Klon.webm
Capture dimensions:          1024x768
Capture rate:                512kbps
Capture FPS:                 25kbps
Capture options:             ac_enabled=false

Guest:

Configured memory balloon size: 0MB

ip a

Code: Select all

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp89s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 88:ae:dd:01:5e:0d brd ff:ff:ff:ff:ff:ff
    inet 192.168.178.52/24 brd 192.168.178.255 scope global dynamic noprefixroute enp89s0
       valid_lft 860850sec preferred_lft 860850sec
    inet6 fe80::2d8c:5970:d8da:2142/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
3: wlo1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 60:dd:8e:69:a3:89 brd ff:ff:ff:ff:ff:ff
4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:cf:3d:24 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
5: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000
    link/ether 52:54:00:cf:3d:24 brd ff:ff:ff:ff:ff:ff
Can anybody see my mistake or give me a clue what to search for or to do?

It is not only this virtual machine. I tried a previously working Win10 and a openwrt just to test if the network would appear on this machines but no network either.

Greetings Chyr0
Chyr0
Posts: 6
Joined: 11. Jul 2022, 16:52

Re: No Network

Post by Chyr0 »

i cant post the full dmesg becouse it is to long.
Please request any additional analytic output which will be helpfull. I will respond asap.

Greetings Chyr0
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: No Network

Post by scottgus1 »

Not that I know how to fix this yet, but:
Chyr0 wrote:i cant post the full dmesg becouse it is to long.
The Upload Attachment tab is good for zipped text files.
Chyr0
Posts: 6
Joined: 11. Jul 2022, 16:52

Re: No Network

Post by Chyr0 »

Thank your for the very fast reply.

Here is the dmesg

Greets Chyr0
Attachments
dmesg.zip
dmesg
(20.57 KiB) Downloaded 7 times
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: No Network

Post by scottgus1 »

The VM's Bridged does in fact look to be tied to the correct host network adapter, and the cable looks plugged in.

Virtualbox Bridged has a driver that must be installed for Bridged to work with the physical host adapter. I don't know how to test this on a Linux host, but in Windows hosts there is a Properties box for the network adapters that show the bindings on the adapter, and which show the Bridged binding if it installed correctly:

Image

See if you can find the Linux version of this and check if the Bridged binding is there.

Also, see if you can undo this:
Chyr0 wrote:I tried every NIC configuration from the GUI
back to what it was before on the old VMs. The Virtualbox network adapter in use then was the correct one and would not stop working on a new host.
fth0
Volunteer
Posts: 5677
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: No Network

Post by fth0 »

scottgus1 wrote:Virtualbox Bridged has a driver that must be installed for Bridged to work with the physical host adapter. I don't know how to test this on a Linux host
In a terminal on the host, lsmod | grep -i vbox shows the current number of users of the VirtualBox kernel modules vboxdrv (support driver), vboxnetflt (netfilter driver) and vboxnetadp (host-only adapter). Issue the command while the VM is running.
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: No Network

Post by scottgus1 »

Thanks for the info, fth0! That's going in my list.
Chyr0
Posts: 6
Joined: 11. Jul 2022, 16:52

Re: No Network

Post by Chyr0 »

Danke schonmal für die Hilfe. Ich habe jetzt

Code: Select all

# modprobe vboxdrv
ausgeführt, aber leider vorher

Code: Select all

lsmod|grep -e vbox
nicht überprüft.

Jetzt gibt es aber bei laufender VM

Code: Select all

vboxnetadp             28672  0
vboxnetflt             28672  1
vboxdrv               499712  3 vboxnetadp,vboxnetflt
aus. und bei nicht laufender:

Code: Select all

vboxnetadp             28672  0
vboxnetflt             28672  0
vboxdrv               499712  2 vboxnetadp,vboxnetflt
Unter lspci -k wird für den Ethernet Controller I225-V noch der "igc" Treiber angezeigt. Was hab ich da falsch verstanden?

Code: Select all

59:00.0 Ethernet controller: Intel Corporation Device 15f3 (rev 03)
	Subsystem: Intel Corporation Device 3004
	Kernel driver in use: igc
	Kernel modules: igc
Ich hatte auch gelesen dass der Treiber bei einem UEFI boot auch signiert sein müssen. Das sind sie aber sicherlich schon, oder? sonst würde lsmod sie ja nicht anzeigen?

Das Netzwerk der VM ist leider immer noch nicht verfügbar.
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: No Network

Post by scottgus1 »

It would probably be good to see the VM's config file and a VM log.

1. Start the VM from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.

Right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log, zip it, and post the zip file, using the forum's Upload Attachment tab.

2. Right-click the VM in the main Virtualbox window's VM list, choose Show in Explorer/Finder/File Manager. Zip the VM's .vbox file (not the .vbox-prev file), and post the zip file, using the forum's Upload Attachment tab. (Configure your host OS to show all extensions if the folder that opens does not show a .vbox file.)

3. Run this command in the host's terminal and post the output:
vboxmanage list bridgedifs
Chyr0
Posts: 6
Joined: 11. Jul 2022, 16:52

Re: No Network

Post by Chyr0 »

thank you.

Here are the required files and trhe output of "VBoxManagae list bridgedifs"

Code: Select all

vboxmanage list bridgedifs
Name:            enp89s0
GUID:            38706e65-7339-4030-8000-88aedd015e0d
DHCP:            Disabled
IPAddress:       192.168.178.52
NetworkMask:     255.255.255.0
IPV6Address:     fd0b:5057:57a3::af3
IPV6NetworkMaskPrefixLength: 128
HardwareAddress: 88:ae:dd:01:5e:0d
MediumType:      Ethernet
Wireless:        No
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-enp89s0

Name:            virbr0
GUID:            62726976-3072-4000-8000-525400cf3d24
DHCP:            Disabled
IPAddress:       192.168.122.1
NetworkMask:     255.255.255.0
IPV6Address:     
IPV6NetworkMaskPrefixLength: 0
HardwareAddress: 52:54:00:cf:3d:24
MediumType:      Ethernet
Wireless:        No
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-virbr0

Name:            virbr0-nic
GUID:            62726976-3072-4e2d-a963-525400cf3d24
DHCP:            Disabled
IPAddress:       0.0.0.0
NetworkMask:     0.0.0.0
IPV6Address:     
IPV6NetworkMaskPrefixLength: 0
HardwareAddress: 52:54:00:cf:3d:24
MediumType:      Ethernet
Wireless:        No
Status:          Down
VBoxNetworkName: HostInterfaceNetworking-virbr0-nic

Name:            wlo1
GUID:            316f6c77-0000-4000-8000-60dd8e69a389
DHCP:            Disabled
IPAddress:       0.0.0.0
NetworkMask:     0.0.0.0
IPV6Address:     
IPV6NetworkMaskPrefixLength: 0
HardwareAddress: 60:dd:8e:69:a3:89
MediumType:      Ethernet
Wireless:        Yes
Status:          Down
VBoxNetworkName: HostInterfaceNetworking-wlo1
The virbr0 and virbr0-nic are propably there because i installed qemu/kvm to test if it is only virtualbox that has the problem. It is not.
Attachments
vbox.zip
(2.2 KiB) Downloaded 9 times
log.zip
(36.57 KiB) Downloaded 8 times
fth0
Volunteer
Posts: 5677
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: No Network

Post by fth0 »

I don't see any problems so far:

The VirtualBox kernel modules usage matches my expectations: vboxneflt is only used (by the VirtualBoxVM process) while the VM is running, and vboxdrv is used by vboxnetadp and vboxnetflt (and by the VirtualBoxVM process).

The Win7_64-Klon-2022-07-12-20-05-16.log file shows that 1560 Ethernet frames have been received by the VM, and 2006 Ethernet frames have been sent. I'd suggest to investigate further inside the guest OS, looking at the network configuration and use Wireshark to capture the network traffic.
Chyr0 wrote:Unter lspci -k wird für den Ethernet Controller I225-V noch der "igc" Treiber angezeigt. Was hab ich da falsch verstanden?
Warum sollte das Deiner Meinung nach nicht so sein?
Chyr0
Posts: 6
Joined: 11. Jul 2022, 16:52

Re: No Network

Post by Chyr0 »

Chyr0 wrote:
Unter lspci -k wird für den Ethernet Controller I225-V noch der "igc" Treiber angezeigt. Was hab ich da falsch verstanden?
Warum sollte das Deiner Meinung nach nicht so sein?
Ich hatte vermutet der vboxdrv ersetzt den igc, was ich wohl falsch angenommen habe, deswegen die Frage.

I will try to investigate further and face up to wireshark.


Could it be the UEFI? SecureBoot is disabled.
Since This Version of the NUC (11) the legacyboot is disabled.
The older Machines (NUC5, 8 and 10) never showed this Problem.

Because of that i switched the NUC11 with a NUC10 which doesnt host any VMs till i understand the Problem...

Thanks for all the help,
Greeting Chyr0
fth0
Volunteer
Posts: 5677
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: No Network

Post by fth0 »

Chyr0 wrote:Ich hatte vermutet der vboxdrv ersetzt den igc
Der Host benutzt weiterhin den igc-Treiber für seinen eigenen Netzwerkverkehr. VirtualBox verwendet einen Filter-Treiber namens vboxnetflt, um Pakete für den Gast in den Netzwerk-Stack des Hosts zu injizieren und abzufangen.
Chyr0 wrote:Could it be the UEFI? SecureBoot is disabled.
I don't think so.
Eugene2008
Posts: 1
Joined: 8. Dec 2022, 16:39

Re: No Network

Post by Eugene2008 »

I faced to same problem.
but after install kernel version 5.15.0-56 issue resolved.
Post Reply