Opened 14 years ago
Closed 13 years ago
#8608 closed defect (fixed)
fedora 14 32bit get frozen while updating and setting change
Reported by: | anonymous | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 4.0.4 |
Keywords: | Cc: | ||
Guest type: | Linux | Host type: | Linux |
Description
I`ve set the settings of the fedora machine from 1CPU to 4 CPU and the RAM from 1024MB to 4096MB, with activating IO APIC.
Fedora starts up normally, but was very slow during running. Starting an update -> fetching package list, get fedora frozen.
Attachments (1)
Change History (8)
by , 14 years ago
Attachment: | fedora 14 32-bit-2011-03-22-12-56-21.log added |
---|
comment:1 by , 13 years ago
comment:2 by , 13 years ago
Actually the guest froze is most probably a duplicate of #7930. In that case there should be crash messages in the host kernel log. Disabling either nested paging or PAE for the guest will workaround this bug. But it would be still interesting if you could test the test build mentioned above.
comment:3 by , 13 years ago
Forget my last comment. The bug I mentioned is only relevant for VT-x (Intel processors).
comment:4 by , 13 years ago
O.K and sorry the testbuild is gone and obsolete with the release of 4.0.8.
Under 4.0.8 there are still problems with multicore configurations, so far. This affects fedora, ubuntu,lubuntu, biolinux,... it is ubiquitous. Can´t remember what is with Windows->I think 2 cores was more or less o.k with windows7(I´ve done so). I was never brave enough to try more-> would be properly cause the same problems I guess.
comment:5 by , 13 years ago
VBox 4.0.10 contains timer fixes for SMP Linux guests so it would be worth a try.
comment:6 by , 13 years ago
Fixed -> Close it!
Just tested with fedora14: all works fine: a little delay is still there, but that is all.
Could you check if this build fixes your problem? We fixed a bug which caused memory corruption in guests with SATA controller and high amount of guest RAM.