Custom Query (16611 matches)
Results (34 - 36 of 16611)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #21979 | duplicate | Installing Guest Additions in Windows 8.1 leads to non-bootable system | ||
| Description |
After installing Guest Additions on a fresh Windows 8.1 system with all current system patches installed, the system would not boot anymore. Windows 8.1 went into automatic repair mode but could not fix the problem. During Guest Addition installation, there were 4 errors about non-signed drivers that Windows prevented to install:
Guest ist Windows 8.1 Pro build 9600. Host is Debian unstable running VirtualBox 7.0.12_Debian. |
|||
| #21978 | wontfix | Virtual machine crashes when trying attach host LPT | ||
| Description |
I run VirtualBox on the Windows 11 host. My host machine has a LPT port which I need to have attached to the VM. I set it up with the following commands VBoxManage modifyvm <VMname> --lptmode1 <host LPT device name> VBoxManage modifyvm <VMname> --lpt1 0x378 7 With VirtualBox 6 it worked fine. But since I moved to the version 7, VM crashes during boot. It happens in the very beginning of the boot process, before the VirtualBox logo appears on the screen, and seems not to depend on the VM type. I created a new VM with the default settings, without attaching any hard drives and without installing any OS, and got the same result. Here's a log file from this VM. |
|||
| #21972 | duplicate | System log spammed with UBSAN: array-index-out-of-bounds in /tmp/vbox.0/r0drv/linux/memobj-r0drv-linux.c:903:37 | ||
| Description |
Using Ubuntu but with mainstream kernel provided by Zabbly (https://github.com/zabbly). Running Virtualbox 7.0.14 on 6.7.1-zabbly+ #ubuntu22.04. I'm getting messages like this all the time: ================================================================================ [ 259.819856] UBSAN: array-index-out-of-bounds in /tmp/vbox.0/r0drv/linux/memobj-r0drv-linux.c:903:37 [ 259.819858] index 511 is out of range for type 'page *[1]' [ 259.819860] CPU: 6 PID: 3207 Comm: EMT-0 Tainted: G W OE 6.7.1-zabbly+ #ubuntu22.04 [ 259.819862] Hardware name: To Be Filled By O.E.M. N7 Z590/N7 Z590, BIOS P1.50 10/20/2021 [ 259.819863] Call Trace: [ 259.819864] [ 259.819867] dump_stack_lvl+0x48/0x70 [ 259.819876] dump_stack+0x10/0x20 [ 259.819878] ubsan_handle_out_of_bounds+0xa2/0x100 [ 259.819881] ? alloc_pages+0x5e/0xd0 [ 259.819885] rtR0MemObjNativeAllocLarge+0x219/0x250 [vboxdrv] [ 259.819924] VBoxHost_RTR0MemObjAllocLargeTag+0x6a/0xe0 [vboxdrv] [ 259.819952] ? try_to_wake_up+0x271/0x6d0 [ 259.819954] ? mod_timer+0x292/0x430 [ 259.819957] ? wake_up_common+0x78/0xb0 [ 259.819960] ? rtR0MemFree+0x27/0x40 [vboxdrv] [ 259.819981] ? supdrvIOCtlFast+0x5a/0xf0 [vboxdrv] [ 259.820000] ? VBoxDrvLinuxIOCtl_7_0_14+0x66/0x260 [vboxdrv] [ 259.820016] ? fget_light+0xa0/0x150 [ 259.820019] ? x64_sys_ioctl+0x9d/0xe0 [ 259.820022] ? do_syscall_64+0x5c/0xf0 [ 259.820025] ? do_syscall_64+0x6b/0xf0 [ 259.820027] ? syscall_exit_to_user_mode+0x38/0x60 [ 259.820030] ? do_syscall_64+0x6b/0xf0 [ 259.820032] ? syscall_exit_to_user_mode+0x38/0x60 [ 259.820034] ? do_syscall_64+0x6b/0xf0 [ 259.820036] ? entry_SYSCALL_64_after_hwframe+0x6e/0x76 [ 259.820040] [ 259.820049] ================================================================================ Seems the kernel is telling about an issue with Virtualbox addressing non existing members of an array? Anyway, seems that this was already a thing with 6.5 kernel and VB 7.0.12. Couldn't find a solution for my case, though. |
|||
