VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (2143 - 2145 of 16363)

Ticket Resolution Summary Owner Reporter
#12782 fixed After upgrading to 4.3.8, missing environment for command prompt started using vboxmanage guestcontrol exec command smokey
Description

I am running a VM with Windows 7 x32 as the guest OS and Windows 7 x64 as the host OS.

I execute the following command to start a command prompt in the VM:

vboxmanage guestcontrol "Win 7 - 32" exec --verbose --image cmd.exe --username user --password password --wait-stdout --wait-stderr -- "/C start cmd"

The command completes successfully and the prompt is started. But, the environment setup for the command prompt is incorrect. It does not contain anywhere close to all the defined variables that should be present.

Following is the output when a "set" command is run in the prompt:


C:\Windows\system32>set
COMSPEC=C:\Windows\system32\cmd.exe
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.JS;.WS;.MSC
PROMPT=$P$G

C:\Windows\system32>


This issue was not present when I was running 4.3.6 (VirtualBox and Guest Additions). I started seeing this problem only after upgrading to 4.3.8.

I run a automated build environment in the VM and having the right environment set is important for the build to succeed.

As there is no crash I have not included any log files. If they are needed I can upload them.

Any/all help will be appreciated.

#1293 worksforme Windows XP guest fails to boot with STOP 0x7F BSOD smoehle
Description

Windows XP SP2 (fully patched) guest on Windows XP SP2 (fully patched) host usually fails to boot with the BSOD:

STOP: 0x0000007F (0x00000000, 0x00000000, 0x00000000, 0x00000000)

I often briefly see the graphical WindowsXP boot screen before the BSOD. About 1 in 6 attempts results in a successful boot. The presence or absence of the guest host additions seems to make no difference. Enabling or disabling VT-x/AMD-V makes no difference. Type of networking makes no difference. USB is disabled.

This happens with all the guests I have created, and although all were created under Windows XP, the guests work fine when run under Linux.

#1294 fixed VirtualBox.exe pegs CPU when guest idle smoehle
Description

A Windows XP Pro SP2 guest running on a Windows XP Pro SP2 host causes VirtualBox.exe on the host to consume 90% of the CPU even though the guest is idle and its task manager shows CPU usage 1 or 2%. Process Explorer from Sysinternals shows that the call stack of the offending thread in VirtualBox.exe is usually one of the following:

ntkrnlpa.exe+0x6dbeb ntkrnlpa.exe+0xe807c ntkrnlpa.exe+0x6986c ntdll.dllKiFastSystemCallRet VBoxRT.dll!RTSemEventWaitNoResume+0x1a VBoxRT.dll!RTSemEventWait+0x39 VBoxVMM.dll!MMR3Term+0x86b VBoxVMM.dll!VMR3WaitHalted+0xea VBoxVMM.dll!EMR3ExecuteVM+0x248 VBoxVMM.dll!VMR3Wait+0x2d9 VBoxRT.dll!RTThreadGetType+0x1ab VBoxRT.dll!RTSystemProcessorGetActiveMask+0xfd MSVCR71.dll!endthreadex+0xa0 kernel32.dll!GetModuleFileNameA+0x1b4

ntkrnlpa.exe+0x6dbeb ntkrnlpa.exe+0x2b462 hal.dll+0x2ef2 VBoxVMM.dll+0x6a0fd VBoxVMM.dll!TMTimerPoll+0x1b1 VBoxVMM.dll!MMR3Term+0x7a6 VBoxVMM.dll!VMR3WaitHalted+0xea VBoxVMM.dll!EMR3ExecuteVM+0x248 VBoxVMM.dll!VMR3Wait+0x2d9 VBoxRT.dll!RTThreadGetType+0x1ab VBoxRT.dll!RTSystemProcessorGetActiveMask+0xfd MSVCR71.dll!endthreadex+0xa0 kernel32.dll!GetModuleFileNameA+0x1b4

ntkrnlpa.exe+0x6dbeb ntkrnlpa.exe+0x2b462 hal.dll+0x2ef2 VBoxVMM.dll!TMTimerGetMilli+0xf1 VBoxVMM.dll!TMTimerGetMilli+0x498 VBoxVMM.dll!TMVirtualGet+0xe VBoxVMM.dll!TMTimerPoll+0x21 VBoxVMM.dll!MMR3Term+0x7a6 VBoxVMM.dll!VMR3WaitHalted+0xea VBoxVMM.dll!EMR3ExecuteVM+0x248 VBoxVMM.dll!VMR3Wait+0x2d9 VBoxRT.dll!RTThreadGetType+0x1ab VBoxRT.dll!RTSystemProcessorGetActiveMask+0xfd MSVCR71.dll!endthreadex+0xa0 kernel32.dll!GetModuleFileNameA+0x1b4

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