#7007 closed defect (obsolete)
Win 2k Guest crashes every few days - VB guest console shows -Abort-
回報者: | wayne | 負責人: | |
---|---|---|---|
元件: | other | 版本: | VirtualBox 3.2.4 |
關鍵字: | win 2k crash, abort | 副本: | |
Guest type: | Windows | Host type: | Linux |
描述 (由 作最後更新)
My Win2k guest system started crashing with VB 3.2.2. This happens every 4 to 5 days. I've looked in the log and I see nothing that would indicate the system is having problems. My host system is Ubuntu 9.10. I recently switched my host system from Windows to Ubuntu. This may have started then... it's just that as soon as I switch to my Ubuntu host I also upgraded to 3.2.2.
Please let me know if there are logs that I should be watching or if I can send you any additional information
附加檔案 (1)
更動歷史 (8)
14 年 前 由 編輯
comment:3 14 年 前 由 編輯
Any chance to provide a core dump? If so, please contact me via frank _dot_ mehnert _at_ sun _dot_ com. Thank you!
comment:4 14 年 前 由 編輯
I've tried to follow the directions of capturing a core dump but since I run Virtualbox from a GUI on my linux box I can't seem to use the terminal window to start vbox or my virtual machines...
comment:5 14 年 前 由 編輯
Is there no way to start your VM from the command line? Just memorize the name of the VM and start the VM with /usr/lib/virtualbox/VirtualBox --startvm VM_NAME from the command line.
comment:6 14 年 前 由 編輯
Okay.. I'll restart my VM using the command line.
The CORE dump documentation references dump files "core.<pid>". I have no such files present even though my Win2k VM aborts every few days. The documentation refers to "Virtualbox Crash"... when my Virtual Machine crashes, Virtualbox continues to run and my other VM's (linux) are not disturbed.
Without the VBox.log of such a session there's nothing we can say...