Custom Query (16363 matches)
Results (985 - 987 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10334 | fixed | This VM crashes after the install of the Guest Additions => Fixed in SVN | ||
| Description |
I updated the host, and then updated all the guests. This guest will not take the Guest Additions without crashing. I also deleted the guest machine and restored it from about 2 weeks back and got the same crash right after the update. |
|||
| #11525 | obsolete | Windows XP Guest USB devices appear with VendorID and DeviceID 0000 when running with multiple processor cores | ||
| Description |
USB Devices that are properly captured by VB are detected by a WinXP host as having VendorID = 0000 and DeviceID = 0000 when running with multiple processor cores. Devices show as "Unknown Device" in Device Manager, and no drivers can be installed. Devices are properly detected by USB filters, and can be enabled / disabled as normal via Devices->USB Devices menu. Workaround is to set Processors = 1. Other problem reports here: https://forums.virtualbox.org/viewtopic.php?f=7&t=34925&start=0 https://forums.virtualbox.org/viewtopic.php?f=8&t=52814 Workaround is listed in second link. |
|||
| #18625 | obsolete | Unable to start VM ( Error - VT-x is not available (VERR_VMX_NO_VMX).) | ||
| 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} |
|||

