VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (2122 - 2124 of 16363)

Ticket Resolution Summary Owner Reporter
#1105 fixed Windows XP guest network problems Krotow
Description

Have Windows XP Professional SP2 guest, installed under VirtualBox 1.5.2. Host is Linux - openSUSE 10.3 (i386). Vbox 1.5.2 Guest Additions for Windows was also installed on guest. Guest network access is established by bridge (br0 -> vbox0). No big problems so far. Actually Vbox 1.5.2 was pretty stable until last SUSE kernel update to 2.6.22-13, that broke down my host system. After host was restored (that same openSUSE 10.3), I now installed newest VirtualBox 1.5.4 from openSUSE 10.3 (i386) RPM, provided by http://www.virtualbox.org/wiki/Downloads and put latest Guest Additions (1.5.4r27032) to my WinXP guest. And... now I in trouble. When I access network shares or browse Internet with Internet Explorer (IE7), guest networking randomly crashes with application error:

Generic Host Process for Win32 Services has encountered a problem and needs to close. We are sorry for the inconvenience.

continued by

Faulting application svchost.exe, version 5.1.2600.2180, faulting module tapisrv.dll, version 5.1.2600.2716, fault address 0x00018a5f.

After those crashes network shares is no more accessible from Explorer GUI windows (Network Places etc.), but may be opened from command line (console or Start -> Run command: \machine\share). Also Internet Explorer show error before each page opening or refresh

svchost.exe - Application Error: The exception Illegal Instruction An attempt was made to execute an illegal instruction. (0xc000001d) occurred in the application at location 0x733f8a5f.

Other browsers (FF, Opera) is not affected. I guess, that problem lies somewhere in those VirtualBox or Guest Additions parts, that is responsible to Windows Networking. Maybe in combination with last SUSE kernel.

#20358 duplicate VM launch fail on Windows 10 when WSL2 and Docker is enabled Janis Baumanis
Description

We are using Docker containers and Vagrant + VirtualBox virtual machines in Windows 10 (now 20H2). Would be very convenient to make both parties (Docker+WSL2 and VirtualBox) working together on same machine. However when Docker Desktop with WSL2 support is installed, existing VirtualBox virtual machines (Linux 64-bit quests with installed VirtualBox Guest additions) fail to launch. Instead error message appear:

WHvCapabilityCodeHypervisorPresent is FALSE! Make sure you have enabled the 'Windows Hypervisor Platform' feature. (VERR_NEM_NOT_AVAILABLE). VT-x is not available (VERR_VMX_NO_VMX).

"Windows Hypervisor Platform" feature enabling in Windows features does not change anything. It is not possible to change paravirtualization interface type under VM "Settings - System - Acceleration" too - OK button remain disabled.

To get VirtualBox VMs running again either "hypervisorlaunchtype" must be disabled through Windows Command Prompt with command

bcdedit /set hypervisorlaunchtype off

or Docker Desktop must be uninstalled together with "Windows Hypervisor Platform", "Virtual Machine Platform" and "Windows Subsystem for Linux" feature disabling in Windows Features with subsequential Windows restart. Both actions obviously permit Docker container using together with VirtualBox. Are there is another way how to use VirtualBox 64-bit VMs in Windows host together with WSL2 + Docker installed in same Windows host?

I seen Hyper-V virtualization support appearing in VirtualBox changelog starting from version 6.1.18 with Hyper-V related fixes in 6.1.22. However it does not help for us. Didn't found any useful information about how to run Docker+WSL2 and VirtualBox together in Internet either.

Environment info:

Host: Windows 10 20H2, 64-bit
Guests: Ubuntu Linux 18.04 LTS, 64-bit
Hardware: Dell OptiPlex 980, Intel Core i5-750 CPU (has VT-x support), 16 GB RAM
Dell BIOS, version A18, VT-x is enabled
#20323 fixed VM Machine wont to start after upgrade to 6.1.20 => fixed in svn/6.1.x x>20 Krzychull
Description

Hi, I'm running virtualbox on debian 10.9 linux host After upgrade to 6.1.20 no virtual machine wants to start and ends with message "The VM session was aborted" On syslog I found such message:

Apr 24 22:04:41 kailan kernel: SUPR0GipMap: fGetGipCpu=0x13 Apr 24 22:04:42 kailan kernel: vboxdrv: 0000000068e25721 VMMR0.r0 Apr 24 22:04:42 kailan kernel: vboxdrv: 00000000856fd8ba VBoxDDR0.r0 Apr 24 22:04:42 kailan kernel: EMT-0[28549]: segfault at 1 ip 00007fa8116e3b27 sp 00007fa83c619890 error 6 in VBoxDD.so[7fa8115ed000+160000] Apr 24 22:04:42 kailan kernel: Code: 40 f5 03 c6 40 f4 03 48 39 d0 75 c7 e9 5a fe ff ff 66 90 4d 8b 5c 24 28 41 be 07 39 00 00 ba ff ff ff ff 4d 8b bb b0 04 00 0 0 <41> c6 47 01 01 66 45 89 77 02 41 8b 8b b8 04 00 00 89 ce c1 ee 02

VirtualBox 6.1.20 Oracle VM VirtualBox Extension Pack was installed on host. VBox.log of the machine I am trying to run attached. After downgrade to virtualbox-6.1.18 everything works correctly.

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