Custom Query (16363 matches)
Results (307 - 309 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #11788 | obsolete | RDP connected client vm crash in VBoxHeadless started VM - Guru Meditation - 4011 (VERR_VMX_IN_VMX_ROOT_MODE) | ||
| Description |
Host: Ubuntu 13.04 Server AMD64 Client: Ubuntu 13.04 Desktop AMD64 When I try to install a client vm on Ubuntu 13.04 Server (AMD64) on VirtualBox 4.2.10 from command line, the client vm keeps crash each time with error message as below: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !! !! Guru Meditation -4011 (VERR_VMX_IN_VMX_ROOT_MODE) !! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! DBGF: No debugger attached, waiting 1 second for one to attach (event=100) 1.Stopping the VM! see full log in attached log file, and below is the commands I use to create and start the vm: VBoxManage createvm --name "Ubuntu" --ostype Ubuntu --register VBoxManage modifyvm "Ubuntu" --memory 1000 --acpi on --boot1 dvd --nic1 bridged --bridgeadapter1 em1 --vrdeport 5000,5010-5012 VBoxManage createhd --filename "vms/Ubuntu.vdi" --size 30000 VBoxManage storagectl "Ubuntu" --name "IDE Controller" --add ide --controller PIIX4 VBoxManage storageattach "Ubuntu" --storagectl "IDE Controller" --port 0 --device 0 --type hdd --medium vms/Ubuntu.vdi VBoxManage storageattach "Ubuntu" --storagectl "IDE Controller" --port 0 --device 1 --type dvddrive --medium ubuntu-13.04-desktop-i386.iso VBoxHeadless --startvm "Ubuntu" |
|||
| #7229 | obsolete | VBox conflict with AWB Mobile WiMAX USB Adapter | ||
| Description |
Now I am using WiMAX connection with the AWB(Accton Wireless Broadband Corp., from Taiwan, China) US211 Mobile WiMAX USB Adapter and it works well before I install VBox. During Installation of VBox, sometimes it goes to Blue Screen at the last stage, sometimes it is ok. And I tried by using both 3.2.0 and 3.2.6, but I had the same results. If I start VBox first then my WiMAX connection can not be started and in the Device Manager I found WiMAX Bus Driver reported error with yellow "Exclaimation" and the details was: "Windows cannot load the device driver for this hardware because a previous instance of the device driver is still in memory. (Code 38)". If I start my WiMAX connection first and then VBox GUI can not be shown properly but I can see the processes of both VBoxSVC.exe and VirtualBox.exe running without GUI. When I quit the WiMAX connection then it can be shown. My OS information:
|
|||
| #14678 | fixed | Invalid check of authenticated attributes from certificates when loading custom device plugin | ||
| Description |
I use a custom virtual PCI device plugin. I've signed it with a code-signing key from GoDaddy, but VirtualBox 5.0.0 refuses to load my DLL on Windows 7. Error It gives the follow error: Failed to open a session for the virtual machine vbox-signed.
Unable to load R3 module C:\Users\vbox-win7\VirtualBox VMs\vbox-signed\img_ipc_device\img_ipc_device.dll (img_ipc_device): : \Device\HarddiskVolume2\Users\vbox-win7\VirtualBox VMs\vbox-signed\img_ipc_device\img_ipc_device.dll (VERR_INTERNAL_ERROR_3).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
Debugging In order to track the error, I have tried to build a debug version of VirtualBox 5.0.0 OSE with test signing. When loading my custom dll (cross signed), VERR_INTERNAL_ERROR_3 was hit in ..\src\VBox\Runtime\common\crypto\pkcs7-sanity.cpp as follows: static int rtCrPkcs7SignedData_CheckSanityExtra(PCRTCRPKCS7SIGNEDDATA pSignedData, uint32_t fFlags, PRTERRINFO pErrInfo, const char *pszErrorTag)
{
...
if (RTCrPkcs7Attributes_IsPresent(&pSignerInfo->AuthenticatedAttributes))
{
...
AssertReturn(pAttrib->enmType == RTCRPKCS7ATTRIBUTETYPE_UNKNOWN, VERR_INTERNAL_ERROR_3);
}
}
Bug Analysis From debugging into the failure, it showed loading my custom dlls failed when VBox checked the attribute of Sigining Time (1.2.840.113549.1.9.5) in our certificate. In the VBox source code, it expected the type enum of this attribute (pAttrib->enmType) to be RTCRPKCS7ATTRIBUTETYPE_UNKNOWN. However, it turned out to be RTCRPKCS7ATTRIBUTETYPE_SIGNING_TIME when I debugged to check. I think it is a bug here, because it is surely not an unknown attribute and shouldn't be considered as an error. The attribute of Signing Time should be checked to match it's own pAttrib->enmType as SIGNING_TIME, instead of UNKNOWN. I have attached relevant log files for reference. |
|||

