#1212 closed defect (fixed)
virtualbox crashes on windows on heavy load
| 回報者: | Ritesh Raj Sarraf | 負責人: | |
|---|---|---|---|
| 元件: | other | 版本: | VirtualBox 1.5.4 |
| 關鍵字: | 副本: | rrs@… | |
| Guest type: | other | Host type: | other |
描述
I'm running VirtualBox 1.5.4 on Windows XP with a Debian Guest in it. I've attached my USB HDD to the Guest and am able to access it.
I'm using SSH Portforwarding to execute gtk-gnutella, a torrent application, from the guest to the host. When gtk-gnutella does heavy I/O on the guest in the USB HDD, VirtualBox crashes with an error in virtualboxd.dll This is immediate, in around 1-2 minutes. If I don't execute the app and just let the guest remain idle, it keeps running and nothing crashes.
更動歷史 (6)
comment:2 17 年 前 由 編輯
Replying to frank:
We fixed several bugs in VirtualBox 1.5.6 which could be related to your problem. Please could you try this version.
Just checked it. VirtualBox still crashes. Do you have a Debug Build? It'll be easier for me to help you with the exact root-cause of the bug.
跟進: 4 comment:3 17 年 前 由 編輯
We don't have debug build available for the public but you could
- provide a minidump
- try to build the SVN version
Please could you provide a VBox.log file of a crashed VM session as well?
comment:4 17 年 前 由 編輯
Replying to frank:
We don't have debug build available for the public but you could
- provide a minidump
- try to build the SVN version
Please could you provide a VBox.log file of a crashed VM session as well?
How do I take a minidump when Virtual Box crashes ?
Since the crash was consistent, I moved to host filesystem feature, where you attach a directory from the host and access in the guest. I was able to crash it sometimes, but not as consistently as was with directly accessing the USB device from the guest.
I think, for me, the P2P application gtk-gnutella has been very good in generating heavy I/O and make the system crash. Maybe you can try this app in your testcases.
Next time Virtual Box crashes, I'll make sure I retain a copy ob VBox.log file.
We fixed several bugs in VirtualBox 1.5.6 which could be related to your problem. Please could you try this version.