"VboxNetNat.exe" Random crashes -> fixed in 6.0.4

[qidizi]

host OS:window 7; host some software:avast!; noteBook:lenovo k27,intel I3,RAM 8G,ssd 128G; host network:LAN,or LAN wifi; guest OS:centos 7; guest network:NAT network,forwarding port(tcp127.0.0.1:22 => 10.0.2.5:22,tcp127.0.0.1:80=>10.0.2.5:80;tcp127.0.0.1:3306 => 10.0.2.5:3306),interface:Intel Pro/1000 MT server (82545EM) mixed mode is disabled; vm virtualbox VER:4.3.23-98520/4.3.22(test both )

when testing,only this guest OS is runing! my email is :qidizi&qq.com If you are using a NAT(not NAT network), this problem will become more serious, see the following ​https://www.centos.org/forums/viewtopic.php?f=50&t=51112 If you use the "bridging model", this problem would not have arisen; Possible causes:postfix(http://www.postfix.org,Install on CentOS systems) is runing,and A large number of mail is being delivered;and the browser on the host(window on "k27"), constantly refresh a PHP page,the "nginx/php" on Centos;then "VboxNetNat.exe" Random crashes,But I cannot determine what operation caused crash;

[qidizi]

They are normal

[qidizi]

when crash;can ping www.qq.com;but forward port is suspended,ssh/80 be loading...until close the crash message window;

[qidizi]

but some time do not show this crash window,when it crashed;

[qidizi]

after close the crash message window,all "vboxnetnat.exe" is crash;

[Frank Mehnert]

Please attach a VBox.log file of such a VM session when the VM crashed. Also, did these crashes happen for you with VBox 4.3.20 as well?

[Frank Mehnert]

Also, can you provide application crash dumps? See here (scroll down that page).

[qidizi]

ok,i will post these here tomorrow,beijing time,at the 09:00.

[qidizi]

install 4.3.20,clear logs,start vbox,run centos guest,crash,shutdown guest,exit vbox,winrar logs files

[qidizi]

Replying to frank:

Please attach a VBox.log file of such a VM session when the VM crashed. Also, did these crashes happen for you with VBox 4.3.20 as well?

4.3.20crash too,very soon.only connect ssh via "putty" tool.

[qidizi]

4.3.20crash too,very soon.only connect ssh via "putty" tool.

[qidizi]

vbox4.3.20 crash by unknown software exception

[qidizi]

with 4.3.20,when crash,i do not get any dump files,but the regedit key/values is all right,so,i will reinstall vbox4.3.33(or VirtualBox test builds),and Have a look whether the use of stress testing tool, triggering the crash;get the dump files;

[Frank Mehnert]

Still relevant with VBox 4.3.26?

[qidizi]

So far, no longer occur.

maybe crash only when i do something Different?

When it happened, I'll send feedback.

[qidizi]

now my VBox is 4.3.26 r98988; it is still crash;

1 runing centos on the vbox; 2 runing postfix; 3 send very much email via smtp to postfix; 4 then vbox net is crash every times; 5 but window 7 can't get any crash dump files; 6 the dump files get from process explorer(sysinternals.com);

7 you can get more infomation from my pc via teamview (​https://www.teamviewer.com/zhCN/index.aspx) or QQ (​http://im.qq.com/download/);

8 my email :qidizi$qq.com

[qidizi]

crash before press ok

[qidizi]

crash after press ok

[qidizi]

the dump files is too big;i can't post here; please download it from ​http://share.weiyun.com/9cb8126b8d48e49ddc8db0b26d66cc36

[VVP]

I can't download dump file from ​http://share.weiyun.com/9cb8126b8d48e49ddc8db0b26d66cc36. I was asked to scan QR code and about login\password. And it was in Chinese.

[qidizi]

Replying to VVP:

I can't download dump file from ​http://share.weiyun.com/9cb8126b8d48e49ddc8db0b26d66cc36. I was asked to scan QR code and about login\password. And it was in Chinese.

please try this url ​http://pan.baidu.com/s/1gdnJEHP

and click "普通下载" or "下载(33.5)M"

[Valery Ushakov]

Replying to qidizi:

Thanks, that worked.

[clive darra]

same problem with a NAT Network of 192.168.168.0/24

[Valery Ushakov]

Please, can you give recent test build a try? 103571+ for 5.x, 103575+ for 4.x.

[Frank Mehnert]

Hopefully fixed in VBox 5.0.10. Please reopen if necessary.

[Porsche_maniak]

This bug is still there @ 5.0.14 version. The guest os is Windows XP x86 and the host is Windows 2008R2 x64 The guest os is sending large amounts of emails. Get this error at random times.

[Valery Ushakov]

Please, provide a full crash dump of VBoxNetNAT.exe

[u309452]

VBox 5.0.18, 1 VM & 1 NATNet with forwarding crash

[u309452]

Affected too, VBox 5.0.18, 1 VM with 1 NAT Network with 2 port forwarding (127.0.0.50:80 -> 10.0.56.50:80 & the same for port 443). I cannot provide crash dump sorry. Isn't #14774 related ?

[Frank Mehnert]

Unfortunately without a crash dump there is nothing we can do as we cannot reproduce the problem.

[aeichner]

No response, closing. Please reopen if still relevant and you provided the requested crash dump of VBoxNetNAT.exe.

[par7133_2]

I'm using VirtualBox Version 5.1.6 r110634 (Qt5.5.1) on Windows 7 SP1 with Fedora 24 as guest and VBoxNetNAT.exe often stops working, sometimes crashes.

I'm using WiFi, with the DHCP and I setup "VBoxManage modifyvm 'VM name' --natdnshostresolver1 on".

To restore the Nat Network while running, I have to set the network adapter on "not attached" and then reset the Nat Network. This restarts VBoxNetNat.exe

I did a dump of the three processes after a stop (not a crash). I did them manually: from Task Manager, "Show processes from all users", right click on the single process, Create Dump file: ​https://1drv.ms/u/s!ArwJYLwiUJKMqTTAvupYx6MhCyzP

A second stop: ​https://1drv.ms/u/s!ArwJYLwiUJKMqTXmevmd-5GlOZkh

[mr_raphael_martin]

Exactly the same intempestive crash : every 5 minutes.

Context : Windows 7 64bits 16Go RAM hosting 4 Virtual Ubuntu 16.04 linux servers.

VirtualBox version 5.1.6. Previously seen also on version 5.0.24

I have captured dumps of 3 VBoxNetNat.exe processes (~90mo). Where can I upload them ?

[Frank Mehnert]

mr_raphael_martin, could you contact me via private e-mail at frank _dot_ mehnert _at_ oracle _dot_ com? Please refer to this ticket. I cannot provide you a server URL, perhaps you find a server and can pass me the URL via e-mail? Thank you!

[par7133_2]

Continue from #comment:22

After a crash VBoxNetNat.exe doesn't run properly anymore also if I switch from "not attached" or I relaunch VirtualBox. When I tried with "Nat" is all okay.

The dump of the crash didn't happen after having set the registry settings published here and from Microsoft. So I made a dump of the faulty VBoxNetNat.exe as from the instructions in #comment:22 ​https://1drv.ms/u/s!ArwJYLwiUJKMqTZ-CPYxfZfT3Txd

When I went to reboot the pc, the shutdown blocked itself on the process VBoxSVC.exe "VirtualBox Interface" saying "VirtualBox Interface has some active connections". Something that I can't understand as VirtualBox was already closed down. Here the dump of VBoxSVC.exe: ​https://1drv.ms/u/s!ArwJYLwiUJKMqTcsTVkLs_kjO3QP

After the reboot of Windows, VBoxNetNat.exe started to run properly again.

[Valery Ushakov]

Replying to par7133_2:

So I made a dump of the faulty VBoxNetNat.exe has from the instructions in #comment:22 ​https://1drv.ms/u/s!ArwJYLwiUJKMqTZ-CPYxfZfT3Txd

Are these dumps from live VBoxNetNat.exe processes (via "Create Dump File" in task manager or the like)?

[par7133_2]

yes, via "Create Dump File" from Task Manager

Replying to vushakov:

Are these dumps from live VBoxNetNat.exe processes (via "Create Dump File" in task manager or the like)?

[Valery Ushakov]

Replying to mr_raphael_martin:

I have captured dumps of 3 VBoxNetNat.exe processes (~90mo). Where can I upload them ?

Thanks for the dumps!

By Murphy's Law we could never reproduce the crash and this is the first dump we get where the stack of the relevant thread is not completely smashed, so I was able to finally get some clues as to what might be going wrong and that helps reducing the search space.

If you could kindly help by running a test build with extra instrumentation/logging I'll try to provide one some time next week.

[Valery Ushakov]

Sorry for the delay. Please, can you give a try to a 5.1 test build r111559 or higher.

It will still crash, but it adds a bit of extra instrumentation to help confirm some hypotheses.

To enable the extra logs, you need to set these two environment variables:

VBOXNET_your_natnet_name_RELEASE_LOG="+nat_service.l2 -nat_service.restrict"
VBOXNET_your_natnet_name_RELEASE_LOG_FLAGS="thread timeprog"

The your_natnet_name portion of the variable names should be replaced with the name of your natnet. Use underscores for any characters in the natnet name that are not suitable for an identifier. E.g. for a network test-0 use VBOXNET_test_0_RELEASE_LOG.

It's probably easiest to set them globally via Window GUI. E.g. Control Panel -> System -> Advanced system settings -> Advanced -> Environment Variables.

The extra logging will be in %USERPROFILE%/.VirtualBox/your-natnet-name.log

If the environment vars are set correctly you should see

NAT_SERVICE LogRel2 enabled

near the beginning of that log to provide you immediate feedback.

[par7133_2]

a crash log, with the test built

[par7133_2]

With the test build goes much better, few crashes.

However, here the attachment <<NatNetwork.zip>> with the log of a crash.

[par7133_2]

an other log with test build

[par7133_2]

a 4th crash log, with the test built

[lewinbo]

still met this issue with latest VirtualBox: 5.1.22r 115126 (Win7 64bit)

[Omugile]

I also encounter VboxNetNat.exe silent crashes. By restarting the process with "VBoxManage.exe natnetwork start --netname NAT" network connectivity is restored.

I would like to help, so if you would like me to collect a dump please let me know. Could you then send me a link with instruction for collecting this dump?

[Valery Ushakov]

You can find instructions on how to get a minidump under Windows here.

[Rainer]

The silent crash of /usr/lib/virtualbox/VBoxNetDHCP and /usr/lib/virtualbox/VBoxNetNAT happens on VB 5.2 Beta3 too. I am seeing these crashes since I first started to use Virtualbox around VB4.

Host: Ubuntu 17.04, VB 5.2.0 Beta3 Guest: RHEL6 x86_64

I somehow get the impression it happens with RHEL6 guest more frequently than with for example RHEL7 guest.

[Mihai Hanor]

-- edited Apparently the Google DNS servers return SERVFAIL, but I can only reproduce it in the VM with NAT Network. You can delete my reply.

[Valery Ushakov]

Replying to MihaiH.:

I don't see the crashes, but I see the failed connections.

Interesting. But my first uneducated guess is that this is likely something completely unrelated. Please, can you file a new bug for this?

[Chris Friesen]

I'm seeing VBoxNetNAT.exe crash on a Windows 10 Pro host with VirtualBox 5.2.12 r122591. The guest is running linux (a modified Centos 7), and it's not doing any sort of strenuous networking, just ssh console traffic. I'm using "NAT network".

[Valery Ushakov]

VirtualBox 6.0.4 and 5.2.26 should hopefully fix this. Please, give it a try.