VirtualBox

Opened 4 years ago

Last modified 3 years ago

#20095 new defect

Virtualbox still resets intel adapters

Reported by: Sanitariu Owned by:
Component: network Version: VirtualBox 6.1.14
Keywords: e1000 driver Cc:
Guest type: Linux Host type: other

Description

Using virtualbox 6.1.14 on linux host with linux guest makes intel driver to reset adapter. This maybe duplicate but someone is closing not fixed bugs. Seems like the bug is present from over 10 years. I tried virtio but its not usable because after 2-3 days or so it just freez my virtual machines and they need to be power cycled. E1000 driver just makes disconnects way better. Using PCNet drivers are no option for me because i need gigabit connection.

Attachments (2)

intel-reset.txt (7.7 KB ) - added by Sanitariu 4 years ago.
intel e1000 driver reset
VBox.log (82.8 KB ) - added by Sanitariu 4 years ago.
Vbox.log

Download all attachments as: .zip

Change History (7)

by Sanitariu, 4 years ago

Attachment: intel-reset.txt added

intel e1000 driver reset

comment:1 by Aleksey Ilyushin, 4 years ago

VBox.log would be nice, along with the description of steps to reproduce the issue. Btw, virtual adapters are not constrained by the physical medium speed, so there is no difference between e1000 and pcnet in this regard. e1000 is faster mostly because it supports offloading features.

by Sanitariu, 4 years ago

Attachment: VBox.log added

Vbox.log

comment:2 by Sanitariu, 4 years ago

Added attachment. You can reproduce easy. Just use any of the gigabit drivers in virtualbox and do a lot of traffic in guest. Thats all.

comment:3 by Sanitariu, 4 years ago

cat /etc/debian_version - 9.13 A lot of traffic means you can run disk copy rsync or similar for 1 hour.

comment:4 by Sanitariu, 4 years ago

Tested any variations of these: ethtool -K enp0s3 gso off gro off tso off Still the same. Tested with/without virtualbox guest additions. Guest kernel ->

uname -a

Linux host1 4.9.0-11-amd64 #1 SMP Debian 4.9.189-3+deb9u2 (2019-11-11) x86_64 GNU/Linux

I tested with kernel 5.10.6 compiled not package which i hope uses other driver but it is still the same.

[Sat Jan 16 09:37:48 2021] e1000 0000:00:03.0 enp0s3: Reset adapter
[Sat Jan 16 09:37:51 2021] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
[Sat Jan 16 11:19:24 2021] e1000 0000:00:03.0 enp0s3: Reset adapter
[Sat Jan 16 11:19:26 2021] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
[Sat Jan 16 11:52:44 2021] e1000 0000:00:03.0 enp0s3: Reset adapter
[Sat Jan 16 11:52:46 2021] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
Last edited 3 years ago by janitor (previous) (diff)

comment:5 by Sanitariu, 3 years ago

Some more information from resets:

[66169.615963] ------------[ cut here ]------------
[66169.615978] WARNING: CPU: 0 PID: 0 at /build/linux-o3gOgM/linux-4.9.189/net/sched/sch_generic.c:316 dev_watchdog+0x233/0x240
[66169.615980] NETDEV WATCHDOG: enp0s3 (e1000): transmit queue 0 timed out
[66169.615981] Modules linked in: binfmt_misc vboxvideo(O) ipt_REJECT nf_reject_ipv4 xt_multiport xt_tcpudp ip6table_filter ip6_tables iptable_filter sb_edac edac_core iTCO_wdt intel_powerclamp kvm_intel iTCO_vendor_support kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel evdev sg intel_rapl_perf lpc_ich serio_raw vmwgfx mfd_core pcspkr rng_core vboxguest(O) ttm drm_kms_helper drm video button ac ip_tables x_tables autofs4 ext4 crc16 jbd2 crc32c_generic fscrypto ecb mbcache sd_mod ata_generic crc32c_intel ata_piix ahci libahci aesni_intel aes_x86_64 glue_helper lrw gf128mul ablk_helper cryptd psmouse e1000 libata scsi_mod i2c_piix4
[66169.616064] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G           O    4.9.0-11-amd64 #1 Debian 4.9.189-3+deb9u2
[66169.616066] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
[66169.616069]  0000000000000000 ffffffffa4136404 ffff9550e3c03e20 0000000000000000
[66169.616075]  ffffffffa3e7b83b 0000000000000000 ffff9550e3c03e78 ffff9550ccd1a000
[66169.616080]  0000000000000000 ffff9550cd242a80 0000000000000001 ffffffffa3e7b8bf
[66169.616085] Call Trace:
[66169.616088]  <IRQ>
[66169.616097]  [<ffffffffa4136404>] ? dump_stack+0x5c/0x78
[66169.616102]  [<ffffffffa3e7b83b>] ? __warn+0xcb/0xf0
[66169.616106]  [<ffffffffa3e7b8bf>] ? warn_slowpath_fmt+0x5f/0x80
[66169.616112]  [<ffffffffa433eb93>] ? dev_watchdog+0x233/0x240
[66169.616117]  [<ffffffffa433e960>] ? dev_deactivate_queue.constprop.26+0x60/0x60
[66169.616122]  [<ffffffffa3eea292>] ? call_timer_fn+0x32/0x120
[66169.616126]  [<ffffffffa3eea607>] ? run_timer_softirq+0x1d7/0x430
[66169.616132]  [<ffffffffa413f564>] ? timerqueue_add+0x54/0xa0
[66169.616136]  [<ffffffffa3eec2f8>] ? enqueue_hrtimer+0x38/0x80
[66169.616141]  [<ffffffffa44220ad>] ? __do_softirq+0x10d/0x2b0
[66169.616147]  [<ffffffffa3e81e52>] ? irq_exit+0xc2/0xd0
[66169.616150]  [<ffffffffa4421b2c>] ? smp_apic_timer_interrupt+0x4c/0x60
[66169.616156]  [<ffffffffa442025e>] ? apic_timer_interrupt+0x9e/0xb0
[66169.616158]  <EOI>
[66169.616162]  [<ffffffffa441da92>] ? mwait_idle+0x72/0x160
[66169.616171]  [<ffffffffa3ebf33a>] ? cpu_startup_entry+0x1ca/0x240
[66169.616180]  [<ffffffffa4b3ef5e>] ? start_kernel+0x447/0x467
[66169.616185]  [<ffffffffa4b3e120>] ? early_idt_handler_array+0x120/0x120
[66169.616188]  [<ffffffffa4b3e408>] ? x86_64_start_kernel+0x14c/0x170
[66169.616191] ---[ end trace b2398e43d8835b28 ]---
[66169.616224] e1000 0000:00:03.0 enp0s3: Reset adapter
[66171.728617] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[68665.596236] e1000 0000:00:03.0 enp0s3: Reset adapter
[68667.676228] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX

Virtualbox still has no usable and stable gigabit card. e1000 crashes on heavy traffic and virtionet stucks all the guest and need power cycle. This is observed on version 6.1.14 different types of guests like ubuntu and debian. I can collect more information if someone is interested.

Last edited 3 years ago by janitor (previous) (diff)
Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use