VirtualBox

Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#16544 closed defect (fixed)

VB v5.1.16 continually crashes with Win7 VM and IAR (shared folders)

Reported by: BrendanSimon Owned by:
Component: other Version: VirtualBox 5.1.16
Keywords: crash IAR Embedded Workbench Cc:
Guest type: Windows Host type: Mac OS X

Description (last modified by Frank Mehnert)

My Win7 VM, running VB v5.1.16 on macOS Sierra host (late 2016 MacBook Pro) continually crashes when I run the IAR Embedded Workbench application and open a workspace.

I've been running IAR EW in a VB VM for a year or two now without any major issues (apart from USB support), and very rarely have VM crashes. Now I continually get crashses after opening an IAR workspace file. If I open the app but don't open a workspace file the VM seems to be ok, but within a minute or two after opening a workspace file ... BOOM !!

Reverting back to v5.1.14 => IAR EW does not crash.

Change History (17)

comment:1 by Frank Mehnert, 8 years ago

Description: modified (diff)

comment:2 by Frank Mehnert, 8 years ago

Removed the pasted content. Please do NOT paste log file into tickets. Use the Attach file function instead. Please attach the log files again.

comment:3 by Mapache, 8 years ago

Same issues here - it seems that activity on the virtual filesystem caused the crash. Reverting back to v5.1.14 and the crashes stopped.

OSX 10.12.3 16 GB RAM Guest that crashed: Windows 7 64bit, Debian Stretch 64bit All crashed guests had activity on virtual file systems and did not crash right away - only after I started to work on them and started build processes that access the virtual file system.

comment:4 by Frank Mehnert, 8 years ago

As I said above, I would like to see log files.

comment:5 by Socratis, 8 years ago

@Mapache

A crash can have a lot of reasons for occuring. You seem to think that it is due to increased disk activity over a shared folder, something that isn't even mentioned in the OP. Yours looks very similar to #15662, which was reported as fixed after 5.1.8.

Since you are reporting that it works with 5.1.14 but not with 5.1.16, this could be an (unwanted) regression. Can you please try with the following versions?

  • 5.1.6
  • 5.1.8

and see if you get the same crash? As #frank mentioned, you'll need the logs from the runs, but I would suggest that if the crash happens with high shared folder activity, that you re-open #15662, or look for something similar.

in reply to:  description comment:6 by S_Vbox_User, 8 years ago

Replying to BrendanSimon:

My Win7 VM, running VB v5.1.16 on macOS Sierra host (late 2016 MacBook Pro) continually crashes when I run the IAR Embedded Workbench application and open a workspace.

I've been running IAR EW in a VB VM for a year or two now without any major issues (apart from USB support), and very rarely have VM crashes. Now I continually get crashses after opening an IAR workspace file. If I open the app but don't open a workspace file the VM seems to be ok, but within a minute or two after opening a workspace file ... BOOM !!

Reverting back to v5.1.14 => IAR EW does not crash.

I also upgraded to 5.1.16 from 5.1.14 and had similar issues. At random times when accessing a USB external drive, my Windows 10 virtual machine would crash (abort). I have a similar model MacBook Pro updated to the latest macOS Sierra for the host as you have. The Windows 10 virtual machine is Windows 10 Pro also updated to the latest build and running solidly for several months. I reverted to Vbox v5.1.14 and rolled back Guest Additions. Everything is back to normal and no crashes. I guess I will have to stick with 5.1.14, lost a bit of confidence in the software - hopefully the broken update will be fixed.

comment:7 by Socratis, 8 years ago

@S_Vbox_User

This is the same comment that you added in the bug that you opened (#16555), right? Because neither here, nor there did I see any logs attached. But don't worry, you're not the only one, everybody seems to ignore the request from the developers to help them help you...

comment:8 by Frank Mehnert, 8 years ago

Any VBox.log file available for such a crashing VM session?

comment:9 by Mapache, 8 years ago

I have tried version 5.1.17 and experienced no more crashes to far. It seems that the fix works.

I just want to mention that the sound effects in Windows sound scratchy and rattling. (this was different in version 5.1.14 - maybe someone already mentioned this in a different bug report - I personally don't care about the sound in VMs)

Last edited 8 years ago by Mapache (previous) (diff)

comment:10 by Frank Mehnert, 8 years ago

Summary: VB v5.1.16 continually crashes with Win7 VM and IARVB v5.1.16 continually crashes with Win7 VM and IAR (shared folders)

In that case it's known that your problem is related to shared folders. It's also expected that Audio in this 5.1.17 build could be buggy.

comment:11 by mikeyj, 8 years ago

Thanks for the advice, I've experienced a few crashes today for my Windows 7 guest VM. I have downloaded and installed 5.1.17. I couldn't see a new version of the VirtualBox Additions, so they are still 5.1.16. Fingers crossed.

comment:12 by Frank Mehnert, 8 years ago

The bug is in the host-side part so running the 5.1.16 Guest Additions is fine.

comment:13 by mikeyj, 8 years ago

Thanks frank, I've been running the Windows 7 guest for a few hours without any issues. I'm not knowingly using shared folders, but this version seems stable.

comment:14 by Kaplan, 8 years ago

Just in case it may help someone in trouble:

Same issue here but my guest system is different:

  • Host: Mac OS Sierra
  • Guest: Ubuntu 16.04 LTE 64 Bit
  • CPU: 2
  • Use 3D Acceleration: Checked

As stated here, did a rollback of virtualbox from 5.1.16 back to 5.1.14. (And also downgraded the extension packs.) For now it seems stable.

Last edited 8 years ago by Kaplan (previous) (diff)

comment:15 by Socratis, 8 years ago

@Kaplan

Did you try the test build and it didn't work for you? You read about the test build, right?

comment:16 by Frank Mehnert, 8 years ago

Resolution: fixed
Status: newclosed

Should be really fixed with VBox 5.1.18.

in reply to:  15 comment:17 by Kaplan, 8 years ago

Replying to socratis:

@socratis Sorry for late resp, at that time I could not have tried the test build since http://download.virtualbox.org/virtualbox/5.1.17 was empty.

Now I saw http://download.virtualbox.org/virtualbox/5.1.18 is in place. My comments were regardless of the new versions.

So briefly, no problem for now, I'll let you know unless 5.1.18 solve the issue.

Note: See TracTickets for help on using tickets.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette