Opened 15 years ago
Closed 15 years ago
#6217 closed defect (fixed)
VB 3.14 causes host crash
Reported by: | (none) | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 3.1.4 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Linux |
Description (last modified by )
hi,
I have upgraded yesterday to Vbox 3.14 (r57640). Host: Ubuntu 9.10 64bit Guest: WinXP Pro Note: 3D and 2D acceleration are disabled
Since I updated, Vbox regularly causes the Host to shut down... This is my last log:
I never ever encountered this kind of bug on the previous version of Vbox... any clues ?
Attachments (1)
Change History (9)
comment:1 by , 15 years ago
comment:2 by , 15 years ago
me again
d* I am encountering the same issue in 3.12 now I am running a rather memory-consuming app in my virtual XP environment but this used to go well, until yesterday
I attached the newest log (the one in my initial post was not the correct one - dumb)
Hope somebody can make sense out of all this... thanks a lot in advance
comment:3 by , 15 years ago
Description: | modified (diff) |
---|
comment:4 by , 15 years ago
Reporter: | removed |
---|
comment:5 by , 15 years ago
just some further info... I reinstalled 3.14 and created a new VM with the existing HD.
still having the same issue but, I noticed that when the application is running both of my CPU's are used up to 100% although I only allocated one to the VM... How is this possible ?
Thus, it is quite possible that Ubuntu shuts down the computer because of over-usage or heating.
The question is... why is Virtualbox using 100% of both my CPU's ? And, how can I prevent this ?
thanks,
comment:7 by , 15 years ago
hi again...
It appears this bug is not due to Virtualbox but to the latest Ubuntu kernel version. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/432670
comment:8 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Please reopen if still relevant with VBox 3.2.6.
hi again,
sorry... I did not notice that we are not supposed to paste the log directly in the ticket I am apparently not able to edit my post... so my apologies.
As I need it for work, I did have to remove 3.14 right now and went back to 3.12
I will reinstall 3.14 as soon as there might be a possible solution to test though.
thanks in advance dmitri