Opened 16 years ago
Closed 16 years ago
#1375 closed defect (fixed)
AMD-V: system reboot -> fixed in SVN
Reported by: | riker | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 1.5.6 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | other |
Description
Dear All,
The system would reboot immediately after running a VM inside virtualbox. The detail information is summzried as below.
Hardware System: AMD64x2 3600 + AMD690G + 2GB RAM. Host System: Windows XP SP2. Virtualbox version: v1.5.6. Gust System: Fedora v6 and Kubuntu v7.10.
This issue is not happened every time. But, I encouner it today twice. First, I start the virtualbox. Chose a VM to execute. The whole system would be rebooted immeidately during the booting progress of guest system.
Could anyone give me some idea and I could capture something for the developemnt team to identify this issue? The log file I found in the VM direcotry is attached with this report. Thanks!
Attachments (1)
Change History (7)
by , 16 years ago
Attachment: | VBox.log.1 added |
---|
comment:1 by , 16 years ago
comment:2 by , 16 years ago
Summary: | The system would reboot immediately after running a VM inside virtualbox. → AMD-V: system reboot -> fixed in SVN |
---|
comment:3 by , 16 years ago
priority: | major → critical |
---|
comment:5 by , 16 years ago
Dear sandervl73,
Thanks very much for your kindly reply. As your comments, I enable the AMD-V in the global setting and VM settings. The AMD-V is also enabled by BIOS. But, I installed the AMD CPU utility from mothorboard CD. The utility is the same one on the AMD web site after I confirmed. The information is summarized as below for your reference.
http://www.amd.com/us-en/Processors/TechnicalResources/0,,30_182_871_13118,00.html:
- AMD Dual-Core Optimizer.
- AMD Processor Driver Version 1.3.2.0053 for Windows XP and Windows Server 2003 (x86 and x64)
I would turn off the AMD-V first and wait the next release. Thanks a lot.
comment:6 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Your BIOS probably doesn't initialize AMD-V properly on all cores. I've changed our init routines to check all cores in our development branch already. Turn off hardware virtualization in VirtualBox to work around it for now.