Changes between Initial Version and Version 2 of Ticket #1025
- Timestamp:
- Apr 7, 2008 9:04:16 AM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #1025 – Description
initial v2 2 2 3 3 The Guest FreeBSD system hangs after the boot loader. (This is when loading the kernel) 4 -With VBox 1.52 it used to hang at the Freebsd Boot Menu (select boot with/without ACPI etc)5 -With VBOx 1.54 the hang appears after selecting the boot device in the boot loader menu.4 * With VBox 1.52 it used to hang at the Freebsd Boot Menu (select boot with/without ACPI etc) 5 * With VBOx 1.54 the hang appears after selecting the boot device in the boot loader menu. 6 6 7 In both cases the CPU load on my PC goes to 100%, and VBOX does no longer respond. The only way to stop it, is to kill the *process*via the taskmanager.7 In both cases the CPU load on my PC goes to 100%, and VBOX does no longer respond. The only way to stop it, is to kill the '''process''' via the taskmanager. 8 8 9 9 1) My BIOS has a feature to disable/enable VT availability. The issue only arises if I enable VT in the BIOS. Otherwise VT is not used and the log would say "HWACCM: No VMX or SVM CPU extension found. Reason VERR_VMX_ILLEGAL_FEATURE_CONTROL_MSR" … … 11 11 12 12 2) My system (feel free to ask for more info) 13 -Dell Dimension (with DELL BIOS DM061 Vers 2.2.1 from 23/3/07)14 -Intel Core2 CPU 6600 2.4 GHZ15 -4GB Ram (3GB visible to Windows)16 -Window Vista Home Premium 32 bit13 * Dell Dimension (with DELL BIOS DM061 Vers 2.2.1 from 23/3/07) 14 * Intel Core2 CPU 6600 2.4 GHZ 15 * 4GB Ram (3GB visible to Windows) 16 * Window Vista Home Premium 32 bit 17 17 18 18 From the logs: 19 19 20 20 The following lines are only present if VT is ENABLED 21 21 {{{ 22 22 HWACCM: Host CR4=000006F9 23 23 HWACCM: MSR_IA32_FEATURE_CONTROL = 5 … … 77 77 Guest Log: BIOS: int13_harddisk: function 08, unmapped device for ELDL=87 78 78 .... 79 79 }}} 80 80 I attach the full logs 81 82
