[Bug 270460] i386 guest panic when booting VirtualBox client
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 270460] i386 guest panic when booting VirtualBox client"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 270460] i386 guest panic when booting VirtualBox client"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 270460] i386 guest panic when booting VirtualBox client"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 270460] i386 guest panic when booting VirtualBox client"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 270460] i386 CURRENT guest boot time panics in emulators/virtualbox-ose on amd64 13.1 and 13.2-RELEASE-p1 hosts"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 270460] i386 CURRENT guest boot time panics in emulators/virtualbox-ose on amd64 13.1 and 13.2-RELEASE-p1 hosts"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 270460] i386 CURRENT guest boot time panics in emulators/virtualbox-ose on amd64 host (FreeBSD 13.1, Windows 10, FreeBSD 13.2-RELEASE-p1)"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 270460] i386 CURRENT guest boot time panics in emulators/virtualbox-ose on amd64 host (FreeBSD 13.1, Windows 10, FreeBSD 13.2-RELEASE-p1)"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 270460] i386 CURRENT guest boot time panics in emulators/virtualbox-ose on amd64 host (FreeBSD 13.1, Windows 10, FreeBSD 13.2-RELEASE-p1)"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 270460] i386 CURRENT guest boot time panics in emulators/virtualbox-ose on amd64 host (FreeBSD 13.1, Windows 10, FreeBSD 13.2-RELEASE-p1)"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 270460] i386 CURRENT guest boot time panics in emulators/virtualbox-ose on amd64 host (FreeBSD 13.1, Windows 10, FreeBSD 13.2-RELEASE-p1)"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 270460] i386 CURRENT guest boot time panics in emulators/virtualbox-ose on amd64 host (FreeBSD 13.1, Windows 10, FreeBSD 13.2-RELEASE-p1)"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 270460] i386 CURRENT guest boot time panics in emulators/virtualbox-ose on amd64 host (FreeBSD 13.1, Windows 10, FreeBSD 13.2-RELEASE-p1)"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 270460] i386 CURRENT guest boot time panics in emulators/virtualbox-ose on amd64 host (FreeBSD 13.1, Windows 10, FreeBSD 13.2-RELEASE-p1)"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 270460] i386 CURRENT guest boot time panics in emulators/virtualbox-ose on amd64 host (FreeBSD 13.1, Windows 10, FreeBSD 13.2-RELEASE-p1)"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 270460] i386 CURRENT guest boot time panics in emulators/virtualbox-ose on amd64 host (FreeBSD 13.1, Windows 10, FreeBSD 13.2-RELEASE-p1)"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 270460] i386 CURRENT guest boot time panics in emulators/virtualbox-ose on amd64 host (FreeBSD 13.1, Windows 10, FreeBSD 13.2-RELEASE-p1)"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 270460] i386 CURRENT guest boot time panics in emulators/virtualbox-ose on amd64 host (FreeBSD 13.1, Windows 10, FreeBSD 13.2-RELEASE-p1)"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 270460] i386 CURRENT guest boot time panics in emulators/virtualbox-ose on amd64 host (FreeBSD 13.1, Windows 10, FreeBSD 13.2-RELEASE-p1)"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 270460] i386 CURRENT guest boot time panics in emulators/virtualbox-ose on amd64 host (FreeBSD 13.1, Windows 10, FreeBSD 13.2-RELEASE-p1)"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 270460] i386 CURRENT guest boot time panics in emulators/virtualbox-ose on amd64 host (FreeBSD 13.1, Windows 10, FreeBSD 13.2-RELEASE-p1)"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 270460] i386 CURRENT guest boot time panics in emulators/virtualbox-ose on amd64 host (FreeBSD 13.1, Windows 10, FreeBSD 13.2-RELEASE-p1)"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 270460] i386 CURRENT guest boot time panics in emulators/virtualbox-ose on amd64 host (FreeBSD 13.1, Windows 10, FreeBSD 13.2-RELEASE-p1)"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 270460] i386 CURRENT guest boot time panics in emulators/virtualbox-ose on amd64 host (FreeBSD 13.1, Windows 10, FreeBSD 13.2-RELEASE-p1)"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 270460] i386 CURRENT guest boot time panics in emulators/virtualbox-ose on amd64 host (FreeBSD 13.1, Windows 10, FreeBSD 13.2-RELEASE-p1)"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 270460] i386 CURRENT guest boot time panics in emulators/virtualbox-ose on amd64 host (FreeBSD 13.1, Windows 10, FreeBSD 13.2-RELEASE-p1)"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 270460] i386 CURRENT guest boot time panics in emulators/virtualbox-ose on amd64 host (FreeBSD 13.1, Windows 10, FreeBSD 13.2-RELEASE-p1)"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sun, 26 Mar 2023 07:52:01 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270460 Bug ID: 270460 Summary: i386 guest panic when booting VirtualBox client Product: Base System Version: CURRENT Hardware: i386 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: pjfloyd@wanadoo.fr I have no problem booting other i386 versions in a VBox VM. Host is amd64 running FreeBSD 13.1. I don't remember when this first started, something like 6 months ago. Because of this problem I am unable to do any testing of Valgrind on 14.0 i386. Here is the start of the panics from the VBox VM serial output. smist: found supported isa bridge Intel PIIX4 ISA bridge panic: td 0x1d94840 stack 0x2424ee8 not in kstack VA 0x2420000 4 cpuid = 0 time = 1 KDB: stack backtrace: db_trace_self_wrapper(0,1d94840,4,2424000,9,...) at db_trace_self_wrapper+0x28/frame 0x2424e9c vpanic(1491c57,2424ed8,2424ed8,2424f9c,1415b35,...) at vpanic+0xf4/frame 0x2424eb8 panic(1491c57,1d94840,2424ee8,2420000,4,...) at panic+0x14/frame 0x2424ecc trap(2424fa8,0,0,0,0,...) at trap+0x975/frame 0x2424f9c calltrap() at 0xffc0321f/frame 0x2424f9c --- trap 0x9, eip = 0xa02, esp = 0xffe, ebp = 0 --- KDB: enter: panic panic: td 0x1d94840 stack 0x2424d90 not in kstack VA 0x2420000 4 cpuid = 0 time = 1 KDB: stack backtrace: db_trace_self_wrapper(0,1d94840,4,2424000,3,...) at db_trace_self_wrapper+0x28/frame 0x2424d44 vpanic(1491c57,2424d80,2424d80,2424e48,1415b35,...) at vpanic+0xf4/frame 0x2424d60 panic(1491c57,1d94840,2424d90,2420000,4,...) at panic+0x14/frame 0x2424d74 trap(2424e54,8,28,28,100,...) at trap+0x975/frame 0x2424e48 calltrap() at 0xffc0321f/frame 0x2424e48 --- trap 0x3, eip = 0x1042444, esp = 0x2424e94, ebp = 0x2424e94 --- kdb_enter(1527748,1527748) at kdb_enter+0x34/frame 0x2424e94 vpanic(1491c57,2424ed8,2424ed8,2424f9c,1415b35,...) at vpanic+0x11f/frame 0x2424eb8 panic(1491c57,1d94840,2424ee8,2420000,4,...) at panic+0x14/frame 0x2424ecc trap(2424fa8,0,0,0,0,...) at trap+0x975/frame 0x2424f9c calltrap() at 0xffc0321f/frame 0x2424f9c -- You are receiving this mail because: You are the assignee for the bug.