Custom Query (16363 matches)
Results (118 - 120 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1907 | fixed | Incorrect bit adjustment in PCIDevSetBaseAddress | ||
| Description |
In trying to do some testing with the serial driver, I noticed that there was an incorrect bit adjustment in the PCIDevSetBaseAddress method in "VBox/pci.h". The second bit adjustment is rotating 16 bits while it should be using 8 bits. u32Addr = RT_H2LE_U32(u32Addr);
pPciDev->config[iReg] = u32Addr & 0xff;
pPciDev->config[iReg + 1] = (u32Addr >> 16) & 0xff; /* - */
pPciDev->config[iReg + 2] = (u32Addr >> 16) & 0xff;
pPciDev->config[iReg + 3] = (u32Addr >> 24) & 0xff;
The only device in the standard source tree using this code that I'm aware of is the "Audio/DevIchAc97.cpp". |
|||
| #17017 | duplicate | Modality issues with update dialog and about pane | ||
| Description |
VirtualBox 5.1.24 OS X 10.11.6 Steps to reproduce:
Expected results:
Actual results:
Possibly related:
|
|||
| #12601 | obsolete | 4.3.6 Cannot access the kernel driver | ||
| Description |
Host: Windows Vista Home Premium 32 bit SP2 Intel Core 2 Cpu 6600 Upgrading from 4.2.18 (or 4.2.16) Installed 4.3.6, and getting this error. Failed to open a session for the virtual machine fed13. The virtual machine 'fed13' has terminated unexpectedly during startup with exit code 1. Result Code: E_FAIL (0x80004005) Component: Machine Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048} I then:
I have UAC turned off. (But trying with it turned on made no difference) [1] According to autoruns from SysInternals, there where a few Vbox.... files in system32/drivers that where registered as part of "Sun Virtualbox" (very old). I removed them too. Still get the error. (With a newly created guest (fedora) I have a log of the MSI install. |
|||

