VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1000 - 1002 of 16363)

Ticket Resolution Summary Owner Reporter
#1025 fixed FreeBSD(guest) hangs in Vista(Host) with Intel-VT (VB 1.5.4) Martin
Description

I have a problem running a FreeBSD Guest in a Vista host, when switching on Hardware Virtualization (VT).

The Guest FreeBSD system hangs after the boot loader. (This is when loading the kernel)

  • With VBox 1.52 it used to hang at the Freebsd Boot Menu (select boot with/without ACPI etc)
  • With VBOx 1.54 the hang appears after selecting the boot device in the boot loader menu.

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.

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"

2) My system (feel free to ask for more info)

  • Dell Dimension (with DELL BIOS DM061 Vers 2.2.1 from 23/3/07)
  • Intel Core2 CPU 6600 2.4 GHZ
  • 4GB Ram (3GB visible to Windows)
  • Window Vista Home Premium 32 bit

From the logs:

The following lines are only present if VT is ENABLED

HWACCM: Host CR4=000006F9
 HWACCM: MSR_IA32_FEATURE_CONTROL      = 5
 HWACCM: MSR_IA32_VMX_BASIC_INFO       = 1a040000000007
 HWACCM: VMCS id                       = 7
 HWACCM: VMCS size                     = 800
 HWACCM: VMCS physical address limit   = None
 HWACCM: VMCS memory type              = 6
 HWACCM: Dual monitor treatment        = 1
 HWACCM: MSR_IA32_VMX_PINBASED_CTLS    = 1f00000016
 HWACCM:    VMX_VMCS_CTRL_PIN_EXEC_CONTROLS_EXT_INT_EXIT
 HWACCM:    VMX_VMCS_CTRL_PIN_EXEC_CONTROLS_NMI_EXIT
 HWACCM: MSR_IA32_VMX_PROCBASED_CTLS   = 77b9fffe0401e172
 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_IRQ_WINDOW_EXIT
 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_TSC_OFFSET
 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_HLT_EXIT
 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_INVLPG_EXIT
 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_MWAIT_EXIT
 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_RDPMC_EXIT
 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_RDTSC_EXIT
 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_CR8_LOAD_EXIT
 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_CR8_STORE_EXIT
 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_USE_TPR_SHADOW
 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_MOV_DR_EXIT
 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_UNCOND_IO_EXIT
 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_USE_IO_BITMAPS
 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_USE_MSR_BITMAPS
 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_MONITOR_EXIT
 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_PAUSE_EXIT
 HWACCM: MSR_IA32_VMX_ENTRY_CTLS       = 1fff000011ff
 HWACCM:    VMX_VMCS_CTRL_ENTRY_CONTROLS_IA64_MODE
 HWACCM:    VMX_VMCS_CTRL_ENTRY_CONTROLS_ENTRY_SMM
 HWACCM:    VMX_VMCS_CTRL_ENTRY_CONTROLS_DEACTIVATE_DUALMON
 HWACCM: MSR_IA32_VMX_EXIT_CTLS        = 3efff00036dff
 HWACCM:    VMX_VMCS_CTRL_EXIT_CONTROLS_HOST_AMD64
 HWACCM:    VMX_VMCS_CTRL_EXIT_CONTROLS_ACK_EXTERNAL_IRQ
 HWACCM: MSR_IA32_VMX_MISC             = 403c0
 HWACCM:    MSR_IA32_VMX_MISC_ACTIVITY_STATES 7
 HWACCM:    MSR_IA32_VMX_MISC_CR3_TARGET      4
 HWACCM:    MSR_IA32_VMX_MISC_MAX_MSR         200
 HWACCM:    MSR_IA32_VMX_MISC_MSEG_ID         0
 HWACCM: MSR_IA32_VMX_CR0_FIXED0       = 80000021
 HWACCM: MSR_IA32_VMX_CR0_FIXED1       = ffffffff
 HWACCM: MSR_IA32_VMX_CR4_FIXED0       = 2000
 HWACCM: MSR_IA32_VMX_CR4_FIXED1       = 27ff
 HWACCM: MSR_IA32_VMX_VMCS_ENUM        = 2c
 HWACCM: VMX enabled!

AND these are only present if VT is disabled (the vt enabled log terminates before)
 Guest Log: BIOS: int13_diskette: unsupported AH=41
 Guest Log: BIOS: int13_harddisk: function 08, unmapped device for ELDL=81
 Guest Log: BIOS: int13_harddisk: function 08, unmapped device for ELDL=82
 Guest Log: BIOS: int13_harddisk: function 08, unmapped device for ELDL=83
 Guest Log: BIOS: int13_harddisk: function 08, unmapped device for ELDL=84
 Guest Log: BIOS: int13_harddisk: function 08, unmapped device for ELDL=85
 Guest Log: BIOS: int13_harddisk: function 08, unmapped device for ELDL=86
 Guest Log: BIOS: int13_harddisk: function 08, unmapped device for ELDL=87
....

I attach the full logs

#1026 fixed "Select"-Button in Virtual disc manager does not work when selecting existing vdi ugemkow
Description

The following scenorio does not work as expected:

Creating a new VM, adding an existing VDI with the VDI-Manager by using the "Existing" Button, then selecting the wanted vdi, then pressing the "Select" Button.

Double clicking on the VDI in the VDI manager works.

#1027 duplicate Windows XP Pro crashing sjstafford
Description

Host is Fedora 8 64 bit, with all current updates. VirtualBox 1.5.4 using the 64bit RPM for Fedora 8. Guest is Windows XP Pro with all current updates.

Guest crashes without warning.

See attached log.

Notice the file location in the log for the assertion. The folder path and file do not exist.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy