Opened 14 years ago
Closed 14 years ago
#8300 closed defect (fixed)
VBox Guest Debian on debian host freezes
Reported by: | jlueters | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 4.0.2 |
Keywords: | freeze | Cc: | |
Guest type: | Linux | Host type: | Linux |
Description
I am running a debian sid Guest on a debian 6 host. Vbox is Version 4.0.2.
The guest is configured with all gnome bells and whistels as it shall be used as a desktop system. The guest is working for some time (15- 30 minutes ) and does freeze suddenly. The host system is reporting 100% cpu utilization for the vbox process.
Beside the vbox logs i do supply the lsof information for that process and strace logs.
Regards Jürgen
Attachments (8)
Change History (16)
by , 14 years ago
by , 14 years ago
Attachment: | VBox.2.log added |
---|
by , 14 years ago
Attachment: | VBox.log.1 added |
---|
by , 14 years ago
Attachment: | VBox.log.2 added |
---|
by , 14 years ago
Attachment: | VBox.log.3 added |
---|
by , 14 years ago
Attachment: | strace-vbox.log added |
---|
by , 14 years ago
Attachment: | vbox-22820.log added |
---|
comment:1 by , 14 years ago
comment:2 by , 14 years ago
I have the changes recommended in #8008 applied. I am just trying the guest and will come back with results later.
Jürgen
comment:3 by , 14 years ago
After migrating to a complete new server and Debian 6.0 host, i might have found the cause. Running the guest with 1 cpu works fine. Now it is Xeon 5500 with hyperthreads activated.
If i am activating a second cpu the guest does not answer (crashed?) after some usage and the vboxhost process is at 100%.
Jürgen
comment:4 by , 14 years ago
Could you attach a new VBox.log for a VM session with a second CPU enabled on that Xeon with hyperthreads?
comment:6 by , 14 years ago
The log was take with VirtualBox 4.0.2 not 4.0.4. Could you attach the proper log file please?
comment:7 by , 14 years ago
I am running 4.08 now and it seems to work. Since more than one day the system is up with 4 cpus. I had the same nic configuration which has been mentioned in the relase notes.
The bug can be close now.
Jürgen
Could this be a duplicate of #8008? Could you disable the power management in the guest?