Custom Query (16363 matches)
Results (1774 - 1776 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #6753 | duplicate | WinNT fails to boot, missing symbol in VBoxGuestNT.sys | ||
| Description |
STOP: c0000263 {Driver Entry Point Not Found} The \SystemRoot\System32\Drivers\VBoxGuestNT.sys device driver could not locate the entry point MmAllocateConftiguousMemorySpecifyCache in driver ntoskrnl.exe. Well, I reported a similar bug some months ago. It was another symbol, and it was fixed, and now this. Do you actually test with WinNT SP 6 ? |
|||
| #9352 | fixed | unstable clocksource when running Xen inside virtualbox | ||
| Description |
I'm using virtualbox to test Xen 4.1.1 + Linux 3.0 dom0. By default, the Xen hypervisor tries to use the ACPI PM timer as a clocksource. It seems to be unstable and Xen complains about the timer wrapping around unexpectedly. A HPET doesn't seems to be available. The only clocksource that seems to be stable is clocksource=pit. (The dom0 kernel has clocksource=xen) Note, that with ACPI PM timer as a clocksource, dom0 becomes and unstable and AHCI various errors pop up during HDD I/O. This is easily reproducable here (it doesn't happen every time, but it happens very often) with VirtualBox 4.1, 64Bit Core i5 Linux host, dual core, hyperthreading. The guest is configured as OS=Other/Unknown, 4 CPUs, VT-x and Nested Paging enabled. |
|||
| #9643 | fixed | VBoxManage showhdinfo should show data alignment | ||
| Description |
Hi, it would be very useful, if VBoxManage would show the alignment of the datablocks inside the VDI file. There are tools out there (CloneVDI, tool announced in the forums) which modify the alignment of the data such that sector 63 of the virtual harddisk is aligned to 4K. While this is good for Windows XP/DOS and the default partition layout, it is bad for Windows where partitions start at a 1MB boundary. Also, there seem to be "old" VDI files, where data blocks are not aligned on a 4K boundary which AFAIK results in poor AIO/DIO performance. For example I have a flat VDI file with Windows 7 on it, where the MBR is at offset 0x20200 within the file (which is a 512 byte boundary, and not a 4KB boundary). I had to verify this using a hex editor. I would suggest that VBoxManage shows
|
|||

