Date: Tue, 1 Nov 2011 18:18:33 +0100 (CET) From: Marco Steinbach <coco@executive-computing.de> To: Ed Schouten <ed@80386.nl> Cc: Bernhard Froehlich <decke@FreeBSD.org>, Vladimir Kushnir <vkushnir@bigmir.net>, freebsd-ports <freebsd-ports@freebsd.org> Subject: Re: VirtualBox-kmod fails to build on -CURRENT Message-ID: <alpine.BSF.2.00.1111011748170.4120@s560x.c0c0.intra> In-Reply-To: <20111031121511.GL2258@hoeg.nl> References: <alpine.BSF.2.00.1110261224240.14451@kushnir1.kiev.ua> <4EAE690D.1070609@executive-computing.de> <01c0ad0f006967454da602c2812981ce@bluelife.at> <20111031102602.GI2258@hoeg.nl> <20111031110711.GJ2258@hoeg.nl> <20111031111634.GK2258@hoeg.nl> <4EAE905A.9020901@executive-computing.de> <20111031121511.GL2258@hoeg.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 31 Oct 2011, Ed Schouten wrote: > * Marco Steinbach <coco@executive-computing.de>, 20111031 13:11: >> Thanks for having a look into this -- I'm trying out your patch right >> now. This will take a while, as I'll try and test this on 7, also. > > Great. Thanks! I just inspected the code and it seems VirtualBox expects > the device to be named /dev/vboxdrv%d explicitly. If that's the case, > please try to add a symbolic link from vboxdrv0 to vboxdrv. If that > works, I can get that fixed as well. Your patch seems to work for 10-CURRENT/amd64. I noticed no hickups with existing and newly created VMs, and the messages for loading the driver and network support stayed the same: vboxdrv: fAsync=1 offMin=0x34da8a offMax=0x34da8a supdrvGipCreate: omni timer not supported, falling back to synchronous mode vboxnet0: Ethernet address: 0a:00:27:00:00:00 You were right about the device naming, I had to create a symlink. I got another burp on the console. ISTR that I got this one before, also, but am not sure: acquiring duplicate lock of same type: "IPRT Fast Mutex Semaphore" 1st IPRT Fast Mutex Semaphore @ /usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.0.12_OSE/out freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/semfastmutex-r0drv-freebsd.c:100 2nd IPRT Fast Mutex Semaphore @ /usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.0.12_OSE/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/semfastmutex-r0drv-freebsd.c:100 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a kdb_backtrace() at kdb_backtrace+0x37 _witness_debugger() at _witness_debugger+0x2c witness_checkorder() at witness_checkorder+0x93c _sx_xlock() at _sx_xlock+0x55 RTSemFastMutexRequest() at RTSemFastMutexRequest+0x59 g_aUnits() at g_aUnits+0x6963 g_aUnits() at g_aUnits+0x6ea7 g_aUnits() at 0xffffffff8165fe9e g_aUnits() at 0xffffffff81660398 supdrvIOCtl() at supdrvIOCtl+0x1a12 VBoxDrvFreeBSDIOCtl() at VBoxDrvFreeBSDIOCtl+0x1d0 devfs_ioctl_f() at devfs_ioctl_f+0x7a kern_ioctl() at kern_ioctl+0xcd sys_ioctl() at sys_ioctl+0xfd amd64_syscall() at amd64_syscall+0x3ac Xfast_syscall() at Xfast_syscall+0xf7 --- syscall (54, FreeBSD ELF64, sys_ioctl), rip = 0x8012a950c, rsp = 0x7fffff9b7c88, rbp = 0x7fffff9b7c90 --- I'll come back to you with results from testing on 7/amd64. MfG CoCo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1111011748170.4120>