Re: Virtualbox deadlocks on starting guest
I would start by updating to the latest virtualbox version and please make sure that the virtualbox-ose-kmod port is compiled with DEBUG option enabled. This will add debugging symbols to the kernel module. Then it would be good to obtain a kernel stacktrace via a kernel crashdump or break to the kernel debugger when the deadlock happens. Probably you need to recompile your kernel with those debugging knobs: http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-deadlocks.html Btw do you run BHyVe and VirtualBox on the same machine? This sounds like the beginning of lot's of problems. You could try to unload all byhve kernel modules and see if the problem still persists after that. On Mon, Jul 8, 2013 at 5:14 AM, hiren panchasara hiren.panchas...@gmail.com wrote: Anyone? any pointers to debug this? cheers, Hiren On Sat, Jul 6, 2013 at 12:28 PM, hiren panchasara hiren.panchas...@gmail.com wrote: Hi all, I have: flymockour-l7% uname -a FreeBSD flymockour-l7.corp.yahoo.com 10.0-CURRENT FreeBSD 10.0-CURRENT #4 r252757M: Thu Jul 4 23:06:03 PDT 2013 r...@flymockour-l7.corp.yahoo.com:/usr/obj/usr/home/hirenp/head/sys/GENERIC amd64 flymockour-l7% flymockour-l7% pkg info | grep -i virtualbox virtualbox-ose-4.2.14_1A general-purpose full virtualizer for x86 hardware virtualbox-ose-kmod-4.2.14 VirtualBox kernel module for FreeBSD flymockour-l7% flymockour-l7% groups wheel operator vboxusers fuse flymockour-l7% kldstat | grep -i vbox 121 0x82a6 519b8vboxdrv.ko flymockour-l7% kldstat | grep -i vmm 111 0x828dd000 182c50 vmm.ko flymockour-l7% I start virtualbox as myself (not root) from cli and whenever I try to launch any guest (be it freebsd, ubuntu or windows) laptop deadlocks right away and I have to hard reset. This has been happening for many months but now I have decided to sit down and fix it. I believe I am missing something simple as I do not see any other such reports. cheers, Hiren ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: Virtualbox deadlocks on starting guest
On Sun, Jul 7, 2013 at 11:45 PM, Bernhard Fröhlich de...@freebsd.org wrote: I would start by updating to the latest virtualbox version and please make sure that the virtualbox-ose-kmod port is compiled with DEBUG option enabled. This will add debugging symbols to the kernel module. Then it would be good to obtain a kernel stacktrace via a kernel crashdump or break to the kernel debugger when the deadlock happens. Probably you need to recompile your kernel with those debugging knobs: http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-deadlocks.html Btw do you run BHyVe and VirtualBox on the same machine? This sounds like the beginning of lot's of problems. You could try to unload all byhve kernel modules and see if the problem still persists after that. wow, so I guess that was it. unloading vmm.ko and if_tap.ko fixed it for me :-) Why would it be that way? Thanks a ton, Hiren On Mon, Jul 8, 2013 at 5:14 AM, hiren panchasara hiren.panchas...@gmail.com wrote: Anyone? any pointers to debug this? cheers, Hiren On Sat, Jul 6, 2013 at 12:28 PM, hiren panchasara hiren.panchas...@gmail.com wrote: Hi all, I have: flymockour-l7% uname -a FreeBSD flymockour-l7.corp.yahoo.com 10.0-CURRENT FreeBSD 10.0-CURRENT #4 r252757M: Thu Jul 4 23:06:03 PDT 2013 r...@flymockour-l7.corp.yahoo.com:/usr/obj/usr/home/hirenp/head/sys/GENERIC amd64 flymockour-l7% flymockour-l7% pkg info | grep -i virtualbox virtualbox-ose-4.2.14_1A general-purpose full virtualizer for x86 hardware virtualbox-ose-kmod-4.2.14 VirtualBox kernel module for FreeBSD flymockour-l7% flymockour-l7% groups wheel operator vboxusers fuse flymockour-l7% kldstat | grep -i vbox 121 0x82a6 519b8vboxdrv.ko flymockour-l7% kldstat | grep -i vmm 111 0x828dd000 182c50 vmm.ko flymockour-l7% I start virtualbox as myself (not root) from cli and whenever I try to launch any guest (be it freebsd, ubuntu or windows) laptop deadlocks right away and I have to hard reset. This has been happening for many months but now I have decided to sit down and fix it. I believe I am missing something simple as I do not see any other such reports. cheers, Hiren ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Virtualbox deadlocks on starting guest
Hi all, I have: flymockour-l7% uname -a FreeBSD flymockour-l7.corp.yahoo.com 10.0-CURRENT FreeBSD 10.0-CURRENT #4 r252757M: Thu Jul 4 23:06:03 PDT 2013 r...@flymockour-l7.corp.yahoo.com:/usr/obj/usr/home/hirenp/head/sys/GENERIC amd64 flymockour-l7% flymockour-l7% pkg info | grep -i virtualbox virtualbox-ose-4.2.14_1A general-purpose full virtualizer for x86 hardware virtualbox-ose-kmod-4.2.14 VirtualBox kernel module for FreeBSD flymockour-l7% flymockour-l7% groups wheel operator vboxusers fuse flymockour-l7% kldstat | grep -i vbox 121 0x82a6 519b8vboxdrv.ko flymockour-l7% kldstat | grep -i vmm 111 0x828dd000 182c50 vmm.ko flymockour-l7% I start virtualbox as myself (not root) from cli and whenever I try to launch any guest (be it freebsd, ubuntu or windows) laptop deadlocks right away and I have to hard reset. This has been happening for many months but now I have decided to sit down and fix it. I believe I am missing something simple as I do not see any other such reports. cheers, Hiren ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
