VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1012 - 1014 of 16363)

Ticket Resolution Summary Owner Reporter
#18633 fixed Direct 3D is no longer working after guest reboot (Fixed in 6.0.8) mes
Description

I am using a Windows VM on my Linux Laptop. I have 3D support enabled and want to use the WDDM driver.

Problem description: After rebooting the VM, the D3D support is shown is not available by dxdiag, also Aero is disabled

Steps to reproduce:

  • Install VBox Tools with 3D support, choose 3D support using WDDM driver
  • Power off VM
  • Power on VM
  • Open dxdiag and check D3D support -> Expected result: Enabled -> Actual result: Enabled
  • Reboot VM from within guest (do not power off / power on)
  • Open dxdiag and check D3D support -> Expected result: Enabled -> Actual result: NOT AVAILABLE

Further information:

  • Host: Dell XPS 13 9343, Linux Ubuntu 19.04
  • VirtualBox from official Repo, Version 6.0.6
  • Guest: Windows 7 x64 (initial installation is quite old)
#18632 fixed Guru meditation with SW virtualization and serial port (VirtualBox 5->6 regression) => fixed in SVN/next maintenance Ambroz Bizjak
Description

With VirtualBox 6.0.6, when SW virtualization is used, a serial port is enabled and the guest runs Linux, guru meditation results during guest kernel startup. This is a regression compared to 5.2.28.

To reproduce:

  • Create a new VM with type "Linux / Other Linux (32-bit)".
  • Attach CD image: Debian 32-bit netinst ISO. (probably any 32-bit Linux will do)
  • Disable hardware virtualization (Enable VT-x/AMD-V = off).
  • Enable serial port 1 (COM1, can be Disconnected).
  • Run this command to prevent a kernel panic that would otherwise occur: VBoxManage modifyvm VM_NAME --cpu-profile "Intel Xeon X5482 3.20GHz".
  • Start the VM.
  • Result: Guru Meditation during guest kernel startup.
00:00:15.463906 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:15.463907 !!
00:00:15.463908 !!         VCPU0: Guru Meditation -2403 (VERR_TRPM_DONT_PANIC)
00:00:15.463915 !!
00:00:15.463918 !! TRAP=0e ERRCD=0000000000000010 CR2=00000000a0622f60 EIP=a0622f60 Type=0 cbInstr=ff
00:00:15.463926 !! EIP is not in any code known to VMM!
00:00:15.463931 !!
00:00:15.463932 !!
00:00:15.463932 !!

This was originally experienced in automated tests for the NixOS distribution, a fragment of the error from there can be found in this comment. The guru meditation happens just as the kernel initializes the serial port (this is not clear with this debian iso).

This could be the same bug as experienced in this forum post. Here VBox crashes with the same error while running a Windows XP guest, just as a program tries to open a serial port, and it was also with SW-based virtualization.

#18625 obsolete Unable to start VM ( Error - VT-x is not available (VERR_VMX_NO_VMX).) Devyan
Description

I have installed VM 5.2.28 on Windows 10. I am getting below error while starting (Hortonworks Docker Sandwork ).Also I have verified that Virtualization is enabled in the BIOS setup and Hyper-V is disable.

Could you please help me in troubleshooting this issue.

Failed to open a session for the virtual machine Hortonworks Docker Sandbox. VT-x is not available (VERR_VMX_NO_VMX). Result Code: E_FAIL (0x80004005) Component: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

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