VirtualBox

Opened 9 years ago

Closed 9 years ago

#13630 closed defect (fixed)

Windows 2008 r2 x64 Guest Intermittant Crash

Reported by: Matt Hopkins Owned by:
Component: other Version: VirtualBox 4.3.18
Keywords: Cc:
Guest type: Windows Host type: Mac OS X

Description

Host: OSX Yosemite 10.10 - 10.10.1 Guest: Windows 2008 R2 sp1 x64

The guest ends in an aborted state. I can't find any direct cause. It can happen after the VM's been running for 1 min, or for 2 days. I've seen the problem recur a few times when installing the java browser plugin, and the frequency seems to go way up if I'm running Process Explorer from MS internals.

This occurs with numerous Windows 2008 r2 VMs, including clean installs. The issue does not appear to affect Windows 2003, as I have VMs running that stable.

Thanks in advance for any help / guidance.

Attachments (3)

VBox.log (61.2 KB ) - added by Matt Hopkins 9 years ago.
logWithFix.log (65.8 KB ) - added by Matt Hopkins 9 years ago.
Log file after boot with fix in place
localDev_localDev_1418045484051_43502-2014-12-16-09-29-27.log (61.3 KB ) - added by Matt Hopkins 9 years ago.
crash_97167

Download all attachments as: .zip

Change History (21)

by Matt Hopkins, 9 years ago

Attachment: VBox.log added

comment:1 by Matt Hopkins, 9 years ago

I have a core dump, but it's too large to attach w/ the file upload limit. Where can I place it?

comment:2 by Frank Mehnert, 9 years ago

Would it be possible to compress it and to send it to me at frank _dot_ mehnert _at_ oracle _dot_ com?

comment:3 by Matt Hopkins, 9 years ago

Thanks for the response. Sorry, my notification settings must not have been correct as I missed it initially. I'll keep a closer eye on this.

I was having trouble sending an email w/ an attachment that large. A copy of the core dump is available here:

https://www.dropbox.com/s/brrxcug3yjtqphc/core.25962.zip?dl=0

I've upgraded to 4.20, which seems to reduce the frequency, but it's difficult to tell, as the issue is sporadic.

As mentioned in Ticket 13630, which seems similar, I've attempted:

VBoxManage setextradata <VMname> "VBoxInternal/MM/CanUseLargerHeap" 1

But the problem persists. Next I'll try:

VBoxManage setextradata <VMname> "VBoxInternal/MM/cbHyperHeap" "4194304"

Thanks for any assistance!

comment:4 by Frank Mehnert, 9 years ago

This setting is only related to that specific problem mentioned in that ticket. I'm currently downloading your core dump.

comment:5 by Frank Mehnert, 9 years ago

The crash is most likely related to NAT networking. We are investigating.

comment:6 by Matt Hopkins, 9 years ago

Thanks so much for investigating!! Let me know if there's anything I can do to help.

comment:7 by Valery Ushakov, 9 years ago

Please, can you give VirtualBox-4.3.21-97167-OSX.dmg a try. Please, attach a VBox.log from it. Thanks in advance.

by Matt Hopkins, 9 years ago

Attachment: logWithFix.log added

Log file after boot with fix in place

comment:8 by Matt Hopkins, 9 years ago

Running this version now. So far so good. Attached the new log file. The VM the core dump came from is no longer around, but the VM this log file is from also exhibited the issue.

Thanks!

comment:9 by Matt Hopkins, 9 years ago

This fix is still holding strong. Thanks for the help with this. I believe we have a Windows 7 host machine exhibiting the same issue. Would the issue be cross platform? If so, would it be possible to get a Windows build of the test case build?

Thanks!

comment:10 by Valery Ushakov, 9 years ago

Yes, the issue is cross-platform. You can get test builds from the Testbuilds page.

comment:11 by Frank Mehnert, 9 years ago

Any feedback? Please note that the latest test build from here contains the fix for this problem.

comment:12 by Matt Hopkins, 9 years ago

We've had one recurrence of the issue on a Windows host. This occurred using build 97167. At the very least, this is much less frequent than we experienced previously. Has there been any additional changes relating to this issue since 97167 that would impact the issue?

Log files for the crash are now attached as crash_97167

by Matt Hopkins, 9 years ago

crash_97167

comment:13 by Valery Ushakov, 9 years ago

No, there were no relevant changes since 97167.

I assume you are using DNS proxy on Windows as well. I can't reproduce your Windows host problem so far. Have you seen it again since the last time?

Last edited 9 years ago by Valery Ushakov (previous) (diff)

comment:14 by Matt Hopkins, 9 years ago

We've now seen it another two times on the Windows host since the last log was suppied, but the error has not occurred on the OSX host. Possibly this is different issue, since the original issue on OSX seems to be resolved.

Is there any other information that could help track down the issue on the Windows host?

comment:15 by Valery Ushakov, 9 years ago

You haven't mentioned if NAT dns proxy is enabled on that crashed VMs on the Windows host too. The Mac problem (hopefully fixed now) was in the dns proxy and was triggered by the list of nameservers updated.

crash_97167 log ends with DHCP renewal (which also re-reads the list of nameservers) and based on my quick calculations the crash time (from the log name) seems to match those last log entries assuming east coast timezone if I can still do my math. So it looked like it might be some similar problem, but as I said, I can't reproduce it locally (with lease time artificially reduced to make the potential trigger happen much more often).

comment:16 by Matt Hopkins, 9 years ago

Sorry, yes. That vm has all the same settings as the OSX vm, including the enabled NAT dns proxy. We'll try and produce another log next time the issue occurs.

in reply to:  14 comment:17 by Valery Ushakov, 9 years ago

Replying to thematthopkins:

We've now seen it another two times on the Windows host since the last log was supplied, but the error has not occurred on the OSX host. Possibly this is different issue, since the original issue on OSX seems to be resolved.

I think this remaining issue is indeed a different one, most likely its another manifestation of #13994 where just the right timing of requests and replies may lead to use after free.

comment:18 by Frank Mehnert, 9 years ago

Resolution: fixed
Status: newclosed

The original issue (crash in NAT) should be fixed with VBox 4.3.30. Closing.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use