Custom Query (16363 matches)
Results (673 - 675 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #19518 | fixed | Guest command execution fails if more than 2 environment vars are provided => fixed in svn/6.1.x x>6 | ||
| Description |
If more than 2 environment vars are provided during the guest command execution, we get an error VERR_ENV_INVALID_VAR_NAME: C:\WINDOWS\system32>"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" guestcontrol TestVM run --username root --password keins --exe /bin/ls --putenv "test1=test" --putenv "test2=test" --putenv "test3=test" --wait-stdout VBoxManage.exe: error: VERR_ENV_INVALID_VAR_NAME VBoxManage.exe: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component GuestProcessWrap, interface IGuestProcess, callee IUnknown VBoxManage.exe: error: Context: "WaitForArray(ComSafeArrayAsInParam(aWaitStartFlags), gctlRunGetRemainingTime(msStart, cMsTimeout), &waitResult)" at line 1470 of file VBoxManageGuestCtrl.cpp With 2 vars it works fine: C:\WINDOWS\system32>"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" guestcontrol TestVM run --username root --password keins --exe /bin/ls --putenv "test1=test" --putenv "test2=test" --wait-stdout bin boot data dev .... The problem happens with a Debian 10 guest with GAs 6.1.6. It does not happen with GAs 6.1.4 (or earlier). |
|||
| #19516 | fixed | Linux kernel version: 5.7 - we need changes (fixed in 6.1.10) | ||
| Description |
From: "Larry Finger" <> To: vbox-dev@… Subject: [vbox-dev] Fixes for kernel 5.7 Date: Fri, 17 Apr 2020 17:47:11 +0200 Hi, Attached are the fixes required by API changes in kernel 5.7 as follows:
and has been eliminated. As usual, these patches are released under the MIT license. Larry |
|||
| #19513 | wontfix | VT-x is not available | ||
| Description |
VMMR0_DO_NEM_INIT_VM failed: VERR_NEM_MISSING_KERNEL_API_2 (VERR_NEM_MISSING_KERNEL_API_2). VT-x is not available (VERR_VMX_NO_VMX).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
It was previously working before I moved the disk image to a different folder and installed Hyper-V and Windows's "Virtual Machine Platform" feature and "Windows Hypervisor Platform". I installed those for performance benefits. What is the deal? |
|||

