VirtualBox

Ticket #6085 (closed defect: fixed)

Opened 4 years ago

Last modified 4 years ago

xubuntu 9.10 installation hangs host when NAT networking in use

Reported by: heipat Owned by:
Priority: major Component: network/NAT
Version: VirtualBox 3.1.2 Keywords:
Cc: Guest type: other
Host type: Windows

Description

We(myself & colleague)'ve tried VirtualBox 3.1.2 on three different computers. In all three, the host OS is Windows XP, and the guest OS is Linux: xubuntu 9.10. USB sharing and cliboard sharing are disabled. Networking is done by using the NAT option.

This report is a simplified version; I've left out several retries with different alternative configurations and tried to strip the report to its raw essence.

Machine 1 runs XP SP2. Setting up Linux worked, but after installation Ubuntu checked for security updates. Letting it download & install them almost immediately caused the host machine to slow down so badly it had to be shut down by keeping the power button down for 10 secs.

Machine 2 runs XP SP2 also. Same story as machine 1, but I retried the installation with bridged networking, and it went fine then. Switch back to NAT networking and boot up xubuntu, let it start downloading updates, and almost immediately host hangs (no BSOD; just any response to any event takes at least minutes). Used the power button again.

Machine 3 runs XP SP3 -> No problems with Xubuntu installation & upgrade when NAT networking used in VBox.

So the current theory is that NAT doesn't work if XP is on SP level 2. I'll attempt to upgrade machine 2 to SP3 and get back when I have results from that. But in any case it seems likely there's a bug lurking somewhere in the NAT code, so I didn't want to wait any longer before submitting a ticket.

Attachment is a log file from machine 2.

(I found open tickets which seemed related, but nothing that matched exactly. So this may be a duplicate but I don't think we know that yet).

Attachments

Paulin USB-tikkutesti-2010-01-27-19-14-43.log Download (36.8 KB) - added by heipat 4 years ago.
Log from machine 2
Machine 1 debug session 2010-01-28.txt Download (30.7 KB) - added by heipat 4 years ago.
VirtualBox-3.1.4-beta-loop.cdb.log Download (32.4 KB) - added by heipat 4 years ago.
Log of 3.1.4 beta debug session on machine 1
VirtualBox-3.1.4_BETA1-57050-Win.machine3.cdb.log Download (48.3 KB) - added by heipat 4 years ago.
VirtualBox-3.1.4_BETA1-57050-Win.machine3.kdb.log Download (59.7 KB) - added by heipat 4 years ago.

Change History

Changed 4 years ago by heipat

Log from machine 2

comment:1 follow-up: ↓ 2 Changed 4 years ago by Hachiman

Could you please check if  build fixes problem for you?

Changed 4 years ago by heipat

comment:2 in reply to: ↑ 1 ; follow-up: ↓ 3 Changed 4 years ago by heipat

Replying to Hachiman:

Could you please check if  build fixes problem for you?

Tried it, no luck. But this time we run VirtualBox in debugger, so I attached a log. Minidump is also available, but it's full --> 539MB in size. So I'll only post it if you absolutely want it :)

comment:3 in reply to: ↑ 2 ; follow-up: ↓ 4 Changed 4 years ago by Hachiman

Replying to heipat:

Replying to Hachiman:

Could you please check if  build fixes problem for you?

Tried it, no luck. But this time we run VirtualBox in debugger, so I attached a log. Minidump is also available, but it's full --> 539MB in size. So I'll only post it if you absolutely want it :)

Thanks for feedback. I've put the upload URL to private message.

comment:4 in reply to: ↑ 3 ; follow-up: ↓ 5 Changed 4 years ago by heipat

Replying to Hachiman:

Replying to heipat:

Replying to Hachiman:

Could you please check if  build fixes problem for you?

Tried it, no luck. But this time we run VirtualBox in debugger, so I attached a log. Minidump is also available, but it's full --> 539MB in size. So I'll only post it if you absolutely want it :)

Thanks for feedback. I've put the upload URL to private message.

I updated machine 2 to XP SP3 this morning, and have since attempted twice to repeat the hang. But for the time being it seems this only occurs on pre-SP3 XP versions.

Machine 1 is still running SP2. 3.1.3 doesn't work any better on it; 3.1.4 hasn't been tried yet (that's the next thing to do).

comment:5 in reply to: ↑ 4 ; follow-up: ↓ 6 Changed 4 years ago by heipat

Replying to heipat:

Replying to Hachiman:

Replying to heipat:

Replying to Hachiman:

Could you please check if  build fixes problem for you?

Tried it, no luck. But this time we run VirtualBox in debugger, so I attached a log. Minidump is also available, but it's full --> 539MB in size. So I'll only post it if you absolutely want it :)

Thanks for feedback. I've put the upload URL to private message.

I updated machine 2 to XP SP3 this morning, and have since attempted twice to repeat the hang. But for the time being it seems this only occurs on pre-SP3 XP versions.

Machine 1 is still running SP2. 3.1.3 doesn't work any better on it; 3.1.4 hasn't been tried yet (that's the next thing to do).

3.1.2 just hanged on machine 2, and earlier we managed to hang machine 3 as well. So SP3 doesn't seem to help. But maybe this issue has to do with multitasking? Machine 3 didn't have any problems until we realized we had been running it on two cores while the other two were running on a single core. So we disabled the second core in the BIOS and that did the trick!

3.1.4 beta on machine 1 also hanged.

comment:6 in reply to: ↑ 5 Changed 4 years ago by Hachiman

Replying to heipat:

Replying to heipat:

Replying to Hachiman:

Replying to heipat:

Replying to Hachiman:

Could you please check if  build fixes problem for you?

Tried it, no luck. But this time we run VirtualBox in debugger, so I attached a log. Minidump is also available, but it's full --> 539MB in size. So I'll only post it if you absolutely want it :)

Thanks for feedback. I've put the upload URL to private message.

I updated machine 2 to XP SP3 this morning, and have since attempted twice to repeat the hang. But for the time being it seems this only occurs on pre-SP3 XP versions.

Machine 1 is still running SP2. 3.1.3 doesn't work any better on it; 3.1.4 hasn't been tried yet (that's the next thing to do).

3.1.2 just hanged on machine 2, and earlier we managed to hang machine 3 as well. So SP3 doesn't seem to help. But maybe this issue has to do with multitasking? Machine 3 didn't have any problems until we realized we had been running it on two cores while the other two were running on a single core. So we disabled the second core in the BIOS and that did the trick!

3.1.4 beta on machine 1 also hanged.

Thanks for testing, could you please take mini dump and upload the place we've discussed privately.

Changed 4 years ago by heipat

Log of 3.1.4 beta debug session on machine 1

comment:7 in reply to: ↑ description ; follow-up: ↓ 8 Changed 4 years ago by heipat

Attachment added of debug session on machine 1. Here's what was done:

Installed VirtualBox-3.1.4_BETA1-57050-Win.exe in machine 1. While installing, disabled all USB, networking, and Python features. Started the Xubuntu virtual machine from a snapshot where USB, sound, and clipboard sharing had already been disabled and the RAM size was 128 MB. Updated the package list there; that went OK. Then started downloading packages. Meanwhile hit Reload in Mozilla Firefox running in the host Windows XP. At this point, VirtualBox began consuming excessive CPU, and the Xubuntu download halted.

The minidump file VirtualBox-3.1.4-beta-loop.mdmp is from user mode only.

comment:8 in reply to: ↑ 7 ; follow-up: ↓ 9 Changed 4 years ago by Hachiman

Replying to heipat:

Attachment added of debug session on machine 1. Here's what was done:

Installed VirtualBox-3.1.4_BETA1-57050-Win.exe in machine 1. While installing, disabled all USB, networking, and Python features. Started the Xubuntu virtual machine from a snapshot where USB, sound, and clipboard sharing had already been disabled and the RAM size was 128 MB. Updated the package list there; that went OK. Then started downloading packages. Meanwhile hit Reload in Mozilla Firefox running in the host Windows XP. At this point, VirtualBox began consuming excessive CPU, and the Xubuntu download halted.

thanks, will take a look.

The minidump file VirtualBox-3.1.4-beta-loop.mdmp is from user mode only.

comment:9 in reply to: ↑ 8 Changed 4 years ago by heipat

New logs and dumps:

Tested on machine 3 with Windows XP SP3 32-bit, two CPU cores but only one enabled, only Windows Firewall, and no antivirus. Disabled all USB and network and Python features when installing VirtualBox-3.1.4_BETA1-57050-Win.exe. Debugged over the network with DbgSrv.

First tried attaching the debugger to VirtualBox and triggering the bug, but it did not happen. Stopped the virtual machine and restored it from a snapshot. Did not save the debugger log from this.

Then ran VirtualBox without the debugger and successfully triggered the bug. Attached the debugger to the process and collected VirtualBox-3.1.4_BETA1-57050-Win.machine3.mdmp and VirtualBox-3.1.4_BETA1-57050-Win.machine3.cdb.log. Detached again; left VirtualBox hogging the host.

Finally attached WinDbg to the kernel of the host over IEEE 1394. Collected VirtualBox-3.1.4_BETA1-57050-Win.machine3.kdb.log and VirtualBox-3.1.4_BETA1-57050-Win.machine3.dmp (small memory dump). The thread consuming the most CPU (THREAD 8642ca50 Cid 0c84.0814) doesn't appear to have any VirtualBox kernel drivers in its stack trace. The only one with those is THREAD 863e3280 Cid 0c84.0ca0.

Changed 4 years ago by heipat

Changed 4 years ago by heipat

comment:10 Changed 4 years ago by Hachiman

Thank you, heipat, for great observation.

comment:11 follow-up: ↓ 12 Changed 4 years ago by heipat

Hachiman suggested we try a test build that solved ticket 6237:

 http://www.virtualbox.org/download/testcase/VirtualBox-2010-02-26-10-04-31-win-rel-3.1.51-r58091-MultiArch.exe

Testing with that version, there's no longer a total hang but the system becomes incredibly slow - downloading less than half of the security updates xubuntu suggested after installation took about 4 hours, and took all available CPU time at least during that time. After that I called it a day and went home :)

Thus, it seems this ticket is about two problems, one of which has already been nailed:

  1. Guest process hangs at some point when using the network. This seems to be the same as ticket 6237.
  2. When running with a single core only and using NAT networking, simultaneous network activity in guest and host can cause excessive CPU usage and extreme slowdown of host.

comment:12 in reply to: ↑ 11 ; follow-up: ↓ 13 Changed 4 years ago by Hachiman

Replying to heipat:

  1. When running with a single core only and using NAT networking, simultaneous network activity in guest and host can cause excessive CPU usage and extreme slowdown of host.

What happens on two cores in your case?

comment:13 in reply to: ↑ 12 ; follow-up: ↓ 14 Changed 4 years ago by heipat

Replying to Hachiman:

Replying to heipat:

  1. When running with a single core only and using NAT networking, simultaneous network activity in guest and host can cause excessive CPU usage and extreme slowdown of host.

What happens on two cores in your case?

Sorry for the long delay.

We didn't try with that version, but in previous tests running on two cores vbox hasn't crashed.

A week after the last test results I reported, we noticed we had left the test machine on and it was still running VirtualBox. My colleague had xubuntu check for updates and it found some, so he let it start downloading them. This went fine for a while, but then started consuming all CPU time again as before. This time xubuntu stopped responding, not even mouse cursor moved no matter how long he waited. Start menu opened fine on host, but programs (e.g. Command Prompt) wouldn't start. So I think issue 1 wasn't the same as ticket 6237 after all, although fixing it probably helped a bit.

I checked the changelog for 3.1.6 and didn't notice any relevant fixes besides 6237; if there's something there that isn't mentioned in the changelog please let me know.

comment:14 in reply to: ↑ 13 ; follow-up: ↓ 15 Changed 4 years ago by Hachiman

Replying to heipat:

A week after the last test results I reported, we noticed we had left the test machine on and it was still running VirtualBox. My colleague had xubuntu check for updates and it found some, so he let it start downloading them. This went fine for a while, but then started consuming all CPU time again as before. This time xubuntu stopped responding, not even mouse cursor moved no matter how long he waited. Start menu opened fine on host, but programs (e.g. Command Prompt) wouldn't start. So I think issue 1 wasn't the same as ticket 6237 after all, although fixing it probably helped a bit.

Issue 1 sounds like #2845 (if take the host machine hw profile into account), which was fixed in 3.1.6 as well. So I'd recommend to upgrade up to 3.1.6 and if issue will repeat please update the ticket.

comment:15 in reply to: ↑ 14 ; follow-up: ↓ 16 Changed 4 years ago by heipat

Replying to Hachiman:

Replying to heipat:

A week after the last test results I reported, we noticed we had left the test machine on and it was still running VirtualBox. My colleague had xubuntu check for updates and it found some, so he let it start downloading them. This went fine for a while, but then started consuming all CPU time again as before. This time xubuntu stopped responding, not even mouse cursor moved no matter how long he waited. Start menu opened fine on host, but programs (e.g. Command Prompt) wouldn't start. So I think issue 1 wasn't the same as ticket 6237 after all, although fixing it probably helped a bit.

Issue 1 sounds like #2845 (if take the host machine hw profile into account), which was fixed in 3.1.6 as well. So I'd recommend to upgrade up to 3.1.6 and if issue will repeat please update the ticket.

3.1.6 solves issue 1, and I suspect issue 2 as well. Will get back to this next week for a final confirmation.

comment:16 in reply to: ↑ 15 ; follow-up: ↓ 17 Changed 4 years ago by heipat

Replying to heipat:

Replying to Hachiman:

Issue 1 sounds like #2845 (if take the host machine hw profile into account), which was fixed in 3.1.6 as well. So I'd recommend to upgrade up to 3.1.6 and if issue will repeat please update the ticket.

3.1.6 solves issue 1, and I suspect issue 2 as well. Will get back to this next week for a final confirmation.

Issue 2 seems to be solved too, so you can close this ticket. Thanks!

comment:17 in reply to: ↑ 16 Changed 4 years ago by Hachiman

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

3.1.6 solves issue 1, and I suspect issue 2 as well. Will get back to this next week for a final confirmation.

Issue 2 seems to be solved too, so you can close this ticket. Thanks!

Thanks for feedback.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use