VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (64 - 66 of 16363)

Ticket Resolution Summary Owner Reporter
#21333 invalid Critical error on initial start of Windows 10 VM on macOS StefanBK
Description

On the first start/installation of windows 10.

#21332 fixed Guru Meditation (VERR_VMX_INVALID_GUEST_STATE) in the FreeBSD boot loader => fixed in SVN mslw
Description

Booting a newly created VM with the FreeBSD 12.3 ISO from https://download.freebsd.org/releases/amd64/amd64/ISO-IMAGES/12.3/FreeBSD-12.3-RELEASE-amd64-disc1.iso gives the attached Guru Meditation.

This is a regression in VirtualBox 7.

I've looked at what causes it and found the following.

  1. The HM status is:
    00:00:05.485406 CPU[0]: VT-x info:
    00:00:05.485406   HM error           = 0x23a (570)
    00:00:05.485407   rcLastExitToR3     = VERR_VMX_INVALID_GUEST_STATE
    00:00:05.485409   Guest VMCS active
    00:00:05.485410     Real-on-v86 active = true
    00:00:05.485410       EFlags  = 0x7
    00:00:05.485411       Attr CS = 0x9b
    00:00:05.485412       Attr SS = 0xc093
    00:00:05.485412       Attr DS = 0xc093
    00:00:05.485413       Attr ES = 0xc093
    00:00:05.485413       Attr FS = 0xc0f3
    00:00:05.485414       Attr GS = 0xc0f3
    
  1. The above HM error 570 is VMX_IGS_V86_GS_LIMIT_INVALID and indeed the gs register has an invalid limit=ffffffff while the CPU is in real mode:
    00:00:05.481475 gs={0000 base=0000000000000000 limit=ffffffff flags=0000c0f3} cr0=00000010 cr2=00000000
    
  1. The eip=00009568 in the report is the real mode interrupt handler for Int 0x28 (IRQ8 = RTC) from FreeBSD's btx.S.
  1. This interrupt is generated while the CPU is stopped in the hlt instruction inside the 0x86 case of int15_function in src/VBox/Devices/PC/BIOS/system.c.
  1. The problem doesn't happen in VirtualBox 6.1.40 because that case of int15_function didn't use hlt (changed in r87784).
  1. int15_function is called from protected mode using Int 0x31 (v86int) from `delay`.
  1. Running with the VM debugger shows that the limit=ffffffff in the segment registers starts from where Int 0x31 switches to real mode in btx.S.
#21320 fixed Wrong RAM displayed when importing OVA on Windows host tronpydd
Description

The OVA file is located at https://cloud-images.ubuntu.com/releases/22.10/release-20221101/ubuntu-22.10-server-cloudimg-amd64.ova The host system is Windows 10(22H2), 64bit, Hyper-V disabled. While importing OVA, the settings are displayed as follows: https://i.postimg.cc/R0JCpYQ2/2022-11-30-142209.png The correct RAM size should be 1024 MB (which is set in the OVA file). If continue importing without editing RAM size to another value, it can complete correctly (and the result VM has the right RAM size which is 1024 MB). But if continue with an edited RAM size (such as 2048 MB), it will cause an error (0x80070057).

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