#18524 closed bug (duplicate)
VirtualBox - Kernel panic: vm_page_fault: unhandled page fault in kernel space at 0x8c688e8f
| Reported by: | perikiyoxd | Owned by: | nobody |
|---|---|---|---|
| Priority: | normal | Milestone: | Unscheduled |
| Component: | Drivers/Input/PS2 | Version: | R1/beta4 |
| Keywords: | Cc: | ||
| Blocked By: | #17852 | Blocking: | |
| Platform: | All |
Description
- Fresh download: https://mirror.truenetwork.ru/haiku/release/r1beta4/haiku-r1beta4-x86_64-anyboot.iso
- Get VirtualBox 6.1.42 hrev155177 (Qt5.6.2) on Windows 10 host (any)
- Create a x64 VM, assign 6208 MB of ram, 2GB HDD
- Change IDE controller to a AHCI controller, add downloaded ISO on a Optical unit, and HDD.
- Boot
After the boot splash I recieve a kernel panic, as described in the image below:
Change History (9)
comment:1 by , 9 months ago
| Component: | - General → Drivers/Input/PS2 |
|---|---|
| Keywords: | kernel panic virtualbox removed |
| Priority: | blocker → normal |
comment:2 by , 9 months ago
| Blocked By: | 17106 added |
|---|---|
| Resolution: | → duplicate |
| Status: | new → closed |
comment:3 by , 9 months ago
| Blocked By: | 17852 added; 17106 removed |
|---|
follow-up: 6 comment:4 by , 9 months ago
comment:6 by , 9 months ago
Replying to waddlesplash:
It is reported this problem does not happen in VirtualBox 7. It appears to be a VirtualBox bug.
Bad PS/2 device should be not able to crash kernel.
follow-up: 8 comment:7 by , 9 months ago
The problem is not with a PS/2 device; please read the ticket: it's with VirtualBox's emulation of x86.
comment:8 by , 9 months ago
There is a page fault (bad memory access), that happens when communicating with PS/2 bus over ioctl, probably caused by some error at the interrupt handling, either code or emulation, and seems that's caused by VBox emulation as updating the version fixed it.
It would be nice if you could provide more context (related tickets) to get more insight of the issue, if it's not an issue.
It is reported this problem does not happen in VirtualBox 7. It appears to be a VirtualBox bug.