Ticket #16221 (reopened defect)

Opened 12 months ago

Last modified 3 days ago

After upgrading to 5.1.10 Network interface is not working enp0s3: Detected Tx Unit Hang

Reported by: vdv Owned by:
Priority: major Component: network
Version: VirtualBox 5.1.10 Keywords:
Cc: Guest type: Linux
Host type: Windows


After upgrading to virtualbox 5.1.10 Network interface is not working after boot unless its manually reset after boot.Downgrading to virtualbox 5.1.8 fixes the problem.However, upgrading to 5.1.11 is mostly working but not 100% of the time. During the testing it didn't work a few times. Linux arch 4.8.10-1-ARCH guest on windows 10 Host.

journalctl -b kernel: e1000 0000:00:03.0 enp0s3: Detected Tx Unit Hang

Change History

comment:1 Changed 12 months ago by jvdv

I have the same issue here with an Arch Linux guest and Virtualbox 5.1.10 on an Arch Linux host.

I suspect that there is some kind of race condition going on during the initialization of the e1000 interface, because the errors occur intermittently. Sometimes the guest boots up without problems, sometimes it gives a few "Tx unit hang" errors during boot and then recovers, and sometimes it hangs completely. Once the guest's network interface is up and running, the error does not reoccur.

I noticed that I could reproduce the problem by manually bringing up the network and leaving no pause between inserting the e1000 module and configuring the network interface.

If I put it in a script and run it, this will usually trigger the "Tx unit hang" errors:

modprobe e1000
netctl start ethernet-dhcp

While this always works:

modprobe e1000
sleep 2
netctl start ethernet-dhcp

If you use netctl, I suppose a workaround could be to put a short sleep statement in the /usr/lib/network/network initialization script, though I haven't tried this myself. It's a bit of an ugly hack, and future system updates could overwrite your change so you'd have to keep track of it everytime.

If you don't need gigabit ethernet, another workaround is to configure your VM to use one of the PCnet adapter types instead of Intel PRO/1000. You'll be limited to 100Mbps, but at least you'll have reliable networking.

For the time being, I downgraded to VirtualBox 5.1.8.

Last edited 12 months ago by jvdv (previous) (diff)

comment:2 Changed 12 months ago by aleksey

Please try the latest test build 5.1.x from here. It should solve the issue.

comment:3 Changed 11 months ago by frank

  • Status changed from new to closed
  • Resolution set to fixed

Fixed in VBox 5.1.12.

comment:4 Changed 10 months ago by sancelot

I thought it would solve my problem, I have recurrent tx unit hangs using an nfs client with linux (x86).

e1000 0000:00:03.0 eth0: Detected Tx Unit Hang

Tx Queue <0> TDH <b2> TDT <bb> next_to_use <bb> next_to_clean <b2>


time_stamp <10001119c> next_to_watch <ba> jiffies <100011355> next_to_watch.status <0>

[ 583.811563] e1000 0000:00:03.0 eth0: Detected Tx Unit Hang

Tx Queue <0>

Last edited 10 months ago by sancelot (previous) (diff)

comment:5 Changed 10 months ago by sancelot

  • Status changed from closed to reopened
  • Resolution fixed deleted

comment:6 Changed 3 days ago by aleksey

Can anybody try to reproduce the issue with VirtualBox 5.2?

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use