Re: current now panics when starting VBox VM

2021-11-03 Thread Michael Butler via freebsd-emulation 

On 11/3/21 11:13, Konstantin Belousov wrote:

On Wed, Nov 03, 2021 at 11:05:11AM -0400, Michael Butler via freebsd-emulation 
wrote:

On 11/3/21 10:36, Ed Maste wrote:
The kgdb back-trace isn't any more enlightening to me :-(

__curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55
55  __asm("movq %%gs:%P1,%0" : "=r" (td) : "n" (offsetof(struct
pcpu,
(kgdb) bt
#0  __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55
#1  doadump (textdump=) at
/usr/src/sys/kern/kern_shutdown.c:399
#2  0x808cbac5 in kern_reboot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:487
#3  0x808cbedb in vpanic (fmt=,
ap=0xfe0129a6a8d0) at /usr/src/sys/kern/kern_shutdown.c:920
#4  0x808cbd33 in panic (fmt=) at
/usr/src/sys/kern/kern_shutdown.c:844
#5  0x80ca920c in trap_fatal (frame=frame@entry=0xfe0129a6aac0,
eva=0) at /usr/src/sys/amd64/amd64/trap.c:946
#6  0x80ca95af in trap_pfault (frame=frame@entry=0xfe0129a6aac0,
usermode=false, signo=, signo@entry=0x0, ucode=, ucode@entry=0x0)
 at /usr/src/sys/amd64/include/cpufunc.h:417
#7  0x80ca89bc in trap (frame=0xfe0129a6aac0) at
/usr/src/sys/amd64/amd64/trap.c:443
#8  
#9  strlen () at /usr/src/sys/amd64/amd64/support.S:751
#10 0x808b4d79 in sysctl_kern_proc_pathname (oidp=,
arg1=0xfe0129a6ad8c, arg2=, req=0xfe0129a6acc0) at
/usr/src/sys/kern/kern_proc.c:2330
#11 0x808dc331 in sysctl_root_handler_locked
(oid=oid@entry=0x810cf0e0 ,
arg1=arg1@entry=0xfe0129a6ad8c, arg2=arg2@entry=1,
 req=0xfe0129a6acc0, tracker=tracker@entry=0xfe0129a6ac38) at
/usr/src/sys/kern/kern_sysctl.c:185
#12 0x808db88b in sysctl_root (oidp=,
arg1=0xfe0129a6ad8c, arg1@entry=0xfe0129a6ad80, arg2=1,
arg2@entry=4, req=req@entry=0xfe0129a6acc0)
 at /usr/src/sys/kern/kern_sysctl.c:2305
#13 0x808dbdf3 in userland_sysctl (td=td@entry=0xfe012991a000,
name=name@entry=0xfe0129a6ad80, namelen=4, old=,
oldlenp=,
 inkernel=, inkernel@entry=0, new=0x0, newlen=0,
retval=0xfe0129a6ade8, flags=0) at /usr/src/sys/kern/kern_sysctl.c:2462
#14 0x808dbc3c in sys___sysctl (td=0xfe012991a000,
uap=0xfe012991a3f0) at /usr/src/sys/kern/kern_sysctl.c:2335
#15 0x80ca9b5c in syscallenter (td=0xfe012991a000) at
/usr/src/sys/amd64/amd64/../../kern/subr_syscall.c:189
#16 amd64_syscall (td=0xfe012991a000, traced=0) at
/usr/src/sys/amd64/amd64/trap.c:1191
#17 
#18 0x00080315a71a in ?? ()
Backtrace stopped: Cannot access memory at address 0x7fffc778
(kgdb)



Try this

commit 2d3f95bd1fd4f71769f60b8037c1ff27c75d8258
Author: Konstantin Belousov 
Date:   Wed Nov 3 17:11:33 2021 +0200

 proc_get_binpath(): return empty string instead of NULL
 
 for strange case where process does not have text.
 
 Sponsored by:   The FreeBSD Foundation

 MFC after:  3 days

diff --git a/sys/kern/kern_proc.c b/sys/kern/kern_proc.c
index 2156c5c465ba..d11f651960c0 100644
--- a/sys/kern/kern_proc.c
+++ b/sys/kern/kern_proc.c
@@ -2252,7 +2252,7 @@ proc_get_binpath(struct proc *p, char *binname, char 
**retbuf,
vp = p->p_textvp;
if (vp == NULL) {
PROC_UNLOCK(p);
-   *retbuf = NULL;
+   *retbuf = "";
*freebuf = NULL;
return (0);
}



Interestingly, when I went to log out of KDE afer applying this patch 
and rebuilding the kernel, it also paniced without VBox ruuning. The log 
looks similar but the back-trace points to this possibility .. see 
frames 8 through 10 .


__curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55
55  __asm("movq %%gs:%P1,%0" : "=r" (td) : "n" 
(offsetof(struct pcpu,

(kgdb) #0  __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55
#1  doadump (textdump=)
at /usr/src/sys/kern/kern_shutdown.c:399
#2  0x808cbac5 in kern_reboot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:487
#3  0x808cbedb in vpanic (fmt=, 
ap=0xfe011c1858d0)

at /usr/src/sys/kern/kern_shutdown.c:920
#4  0x808cbd33 in panic (fmt=)
at /usr/src/sys/kern/kern_shutdown.c:844
#5  0x80ca920c in trap_fatal (frame=frame@entry=0xfe011c185ac0,
eva=0) at /usr/src/sys/amd64/amd64/trap.c:946
#6  0x80ca95af in trap_pfault 
(frame=frame@entry=0xfe011c185ac0,

usermode=false, signo=, signo@entry=0x0,
ucode=, ucode@entry=0x0)
at /usr/src/sys/amd64/include/cpufunc.h:417
#7  0x80ca89bc in trap (frame=0xfe011c185ac0)
at /usr/src/sys/amd64/amd64/trap.c:443
#8  
#9  strlen () at /usr/src/sys/amd64/amd64/support.S:751
#10 0x808b4d79 in sysctl_kern_proc_pathname (oidp=,
arg1=0xfe011c185d8c, arg2=, req=0xfe011c185cc0)
at /usr/src/sys/kern/kern_proc.c:2330
#11 0x808dc331 in sysctl_root_handler_locked (
oid=oid@entry=0x810c

Re: current now panics when starting VBox VM

2021-11-03 Thread Michael Butler via freebsd-emulation 

On 11/3/21 10:36, Ed Maste wrote:

On Tue, 2 Nov 2021 at 18:32, Michael Butler via freebsd-emulation
 wrote:


Before reporting this, I rebuilt world including kernel, all kmods and
virtualbox itself to no avail :-(


Thanks for confirming.

Now that the WARN_ON noise is disabled by default would you mind
rebuilding a new kernel and obtaining a less-noisy log?


Dump header from device: /dev/ada1s3b
  Architecture: amd64
  Architecture Version: 2
  Dump Length: 853581824
  Blocksize: 512
  Compression: none
  Dumptime: 2021-11-03 10:57:00 -0400
  Hostname: toshi.auburn.protected-networks.net
  Magic: FreeBSD Kernel Dump
  Version String: FreeBSD 14.0-CURRENT #50 main-dbfe5dd3f9: Wed Nov  3 
10:26:58 EDT 2021


r...@toshi.auburn.protected-networks.net:/usr/obj/usr/src/amd64.amd64/sys/TOSHI
  Panic String: page fault
  Dump Parity: 351593830
  Bounds: 0
  Dump Status: good

Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x0
fault code  = supervisor read data, page not present
instruction pointer = 0x20:0x80ca54e4
stack pointer   = 0x28:0xfe0129a6ab80
frame pointer   = 0x28:0xfe0129a6ab80
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 1384 (plasmashell)
trap number = 12
WARNING !drm_modeset_is_locked(>mutex) failed at 
/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.144_2/drivers/gpu/drm/drm_atomic_helper.c:621
WARNING !drm_modeset_is_locked(>mutex) failed at 
/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.144_2/drivers/gpu/drm/drm_atomic_helper.c:621
WARNING !drm_modeset_is_locked(>mutex) failed at 
/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.144_2/drivers/gpu/drm/drm_atomic_helper.c:621
WARNING !drm_modeset_is_locked(>mode_config.connection_mutex) 
failed at 
/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.144_2/drivers/gpu/drm/drm_atomic_helper.c:666
WARNING !drm_modeset_is_locked(>mutex) failed at 
/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.144_2/drivers/gpu/drm/drm_atomic_helper.c:871
WARNING !drm_modeset_is_locked(>mutex) failed at 
/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.144_2/drivers/gpu/drm/drm_atomic_helper.c:871
WARNING !drm_modeset_is_locked(>mutex) failed at 
/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.144_2/drivers/gpu/drm/drm_atomic_helper.c:871
WARNING !drm_modeset_is_locked(>mutex) failed at 
/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.144_2/drivers/gpu/drm/drm_atomic_helper.c:871
WARNING !drm_modeset_is_locked(>mutex) failed at 
/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.144_2/drivers/gpu/drm/drm_atomic_helper.c:871
WARNING !drm_modeset_is_locked(>mutex) failed at 
/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.144_2/drivers/gpu/drm/drm_atomic_helper.c:871
WARNING !drm_modeset_is_locked(>mutex) failed at 
/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.144_2/drivers/gpu/drm/drm_atomic_helper.c:871
WARNING !drm_modeset_is_locked(>mutex) failed at 
/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.144_2/drivers/gpu/drm/drm_atomic_helper.c:871
WARNING !drm_modeset_is_locked(>mutex) failed at 
/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.144_2/drivers/gpu/drm/drm_atomic_helper.c:871

WARN_ON(!mutex_is_locked(>struct_mutex))

WARN_ON(!mutex_is_locked(>lock))WARN_ON(!mutex_is_locked(>lock))WARN_ON(!mutex_is_locked(>lock))
panic: page fault
cpuid = 0
time = 1635951420
WARNING !drm_modeset_is_locked(>mutex) failed at 
/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.144_2/drivers/gpu/drm/drm_atomic_helper.c:621
WARNING !drm_modeset_is_locked(>mutex) failed at 
/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.144_2/drivers/gpu/drm/drm_atomic_helper.c:621
WARNING !drm_modeset_is_locked(>mutex) failed at 
/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.144_2/drivers/gpu/drm/drm_atomic_helper.c:621
WARNING !drm_modeset_is_locked(>mode_config.connection_mutex) 
failed at 
/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.144_2/drivers/gpu/drm/drm_atomic_helper.c:666
WARNING !drm_modeset_is_locked(>mutex) failed at 
/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.144_2/drivers/gpu/drm/drm_atomic_helper.c:871
WARNING !drm_modeset_is_locked(>mutex) failed at 
/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.144_2/drivers/gpu/drm/drm_atomic_helper.c:871
WARNING !drm_modeset_is_locked(>mutex) failed at 
/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.144_2/drivers/gpu/drm/drm_atomic_helper.c:871
WARNING !drm_modeset_is_locked(>mutex) failed at 
/usr/ports/graphics/drm-current-kmod/w

Re: current now panics when starting VBox VM

2021-11-02 Thread Michael Butler via freebsd-emulation 

On 11/2/21 17:48, Cy Schubert wrote:

In message <36923A7F-23DE-490D-B1FA-A8B064740BD6@unrelenting.technology>,
Greg
V via freebsd-current writes:



On November 2, 2021 5:16:35 PM GMT+03:00, Michael Butler via freebsd-current
 wrote:

On current as of this morning (I haven't tried to bisect yet) ..

  .. with either graphics/drm-devel-kmod or graphics/drm-current-kmod,
trying to start a VirtualBox VM triggers this panic ..




#16 0x80c81fc8 at calltrap+0x8
#17 0x808b4d69 at sysctl_kern_proc_pathname+0xc9


something something https://reviews.freebsd.org/D32738 ? sysctl_kern_proc_pat
hname was touched recently there.

(Also can someone commit https://reviews.freebsd.org/D30174 ? These warning-f
illed reports are unreadable >_<)


Usually the first thing to do with virtualbox is rebuild it. That usually
fixes any panics I experience here. Of course, make sure your virtualbox
ports subdirs are fully patched, as it's an opportune time to update it too.


Before reporting this, I rebuilt world including kernel, all kmods and 
virtualbox itself to no avail :-(


I agree; most issues I've had in the past have been resolvable using 
this approach. Not this time,


Michael

current now panics when starting VBox VM

2021-11-02 Thread Michael Butler via freebsd-current 

On current as of this morning (I haven't tried to bisect yet) ..

FreeBSD toshi.auburn.protected-networks.net 14.0-CURRENT FreeBSD 
14.0-CURRENT #42 main-a670e1c13a: Tue Nov  2 09:29:28 EDT 2021 
r...@toshi.auburn.protected-networks.net:/usr/obj/usr/src/amd64.amd64/sys/TOSHI 
 amd64


 .. with either graphics/drm-devel-kmod or graphics/drm-current-kmod, 
trying to start a VirtualBox VM triggers this panic ..


Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x0
fault code  = supervisor read data, page not present
instruction pointer = 0x20:0x80ca5564
stack pointer   = 0x28:0xfe011c036b80
frame pointer   = 0x28:0xfe011c036b80
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 1378 (plasmashell)
trap number = 12
WARNING !drm_modeset_is_locked(>mutex) failed at 
/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.144_2/drivers/gpu/drm/drm_atomic_helper.c:621

#0 0x81ec2c63 at linux_dump_stack+0x23
#1 0x81e403b2 at drm_atomic_helper_check_modeset+0xb2
#2 0x81d3870c at intel_atomic_check+0x8c
#3 0x81e3f383 at drm_atomic_check_only+0x423
#4 0x81e3f783 at drm_atomic_commit+0x13
#5 0x81e4c2e8 at drm_client_modeset_commit_atomic+0x148
#6 0x81e4c046 at drm_client_modeset_commit_force+0x66
#7 0x81e8bf1a at drm_fb_helper_restore_fbdev_mode_unlocked+0x7a
#8 0x81e85ef6 at vt_kms_postswitch+0x166
#9 0x807a59f0 at vt_window_switch+0x120
#10 0x807a2b4f at vtterm_cngrab+0x4f
#11 0x80865716 at cngrab+0x16
#12 0x808cbe1c at vpanic+0xec
#13 0x808cbd23 at panic+0x43
#14 0x80ca928c at trap_fatal+0x2dc
#15 0x80ca962f at trap_pfault+0x32f
#16 0x80ca8a3c at trap+0x23c
#17 0x80c81fc8 at calltrap+0x8
WARNING !drm_modeset_is_locked(>mutex) failed at 
/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.144_2/drivers/gpu/drm/drm_atomic_helper.c:621

#0 0x81ec2c63 at linux_dump_stack+0x23
#1 0x81e403b2 at drm_atomic_helper_check_modeset+0xb2
#2 0x81d3870c at intel_atomic_check+0x8c
#3 0x81e3f383 at drm_atomic_check_only+0x423
#4 0x81e3f783 at drm_atomic_commit+0x13
#5 0x81e4c2e8 at drm_client_modeset_commit_atomic+0x148
#6 0x81e4c046 at drm_client_modeset_commit_force+0x66
#7 0x81e8bf1a at drm_fb_helper_restore_fbdev_mode_unlocked+0x7a
#8 0x81e85ef6 at vt_kms_postswitch+0x166
#9 0x807a59f0 at vt_window_switch+0x120
#10 0x807a2b4f at vtterm_cngrab+0x4f
#11 0x80865716 at cngrab+0x16
#12 0x808cbe1c at vpanic+0xec
#13 0x808cbd23 at panic+0x43
#14 0x80ca928c at trap_fatal+0x2dc
#15 0x80ca962f at trap_pfault+0x32f
#16 0x80ca8a3c at trap+0x23c
#17 0x80c81fc8 at calltrap+0x8
WARNING !drm_modeset_is_locked(>mutex) failed at 
/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.144_2/drivers/gpu/drm/drm_atomic_helper.c:621

#0 0x81ec2c63 at linux_dump_stack+0x23
#1 0x81e403b2 at drm_atomic_helper_check_modeset+0xb2
#2 0x81d3870c at intel_atomic_check+0x8c
#3 0x81e3f383 at drm_atomic_check_only+0x423
#4 0x81e3f783 at drm_atomic_commit+0x13
#5 0x81e4c2e8 at drm_client_modeset_commit_atomic+0x148
#6 0x81e4c046 at drm_client_modeset_commit_force+0x66
#7 0x81e8bf1a at drm_fb_helper_restore_fbdev_mode_unlocked+0x7a
#8 0x81e85ef6 at vt_kms_postswitch+0x166
#9 0x807a59f0 at vt_window_switch+0x120
#10 0x807a2b4f at vtterm_cngrab+0x4f
#11 0x80865716 at cngrab+0x16
#12 0x808cbe1c at vpanic+0xec
#13 0x808cbd23 at panic+0x43
#14 0x80ca928c at trap_fatal+0x2dc
#15 0x80ca962f at trap_pfault+0x32f
#16 0x80ca8a3c at trap+0x23c
#17 0x80c81fc8 at calltrap+0x8
WARNING !drm_modeset_is_locked(>mode_config.connection_mutex) 
failed at 
/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.144_2/drivers/gpu/drm/drm_atomic_helper.c:666

#0 0x81ec2c63 at linux_dump_stack+0x23
#1 0x81e40542 at drm_atomic_helper_check_modeset+0x242
#2 0x81d3870c at intel_atomic_check+0x8c
#3 0x81e3f383 at drm_atomic_check_only+0x423
#4 0x81e3f783 at drm_atomic_commit+0x13
#5 0x81e4c2e8 at drm_client_modeset_commit_atomic+0x148
#6 0x81e4c046 at drm_client_modeset_commit_force+0x66
#7 0x81e8bf1a at drm_fb_helper_restore_fbdev_mode_unlocked+0x7a
#8 0x81e85ef6 at vt_kms_postswitch+0x166
#9 0x807a59f0 at vt_window_switch+0x120
#10 0x807a2b4f at vtterm_cngrab+0x4f
#11 0x80865716 at cngrab+0x16
#12 0x808cbe1c at vpanic+0xec
#13 0x808cbd23 at panic+0x43
#14

Re: VirtualBox fails to build on -current; more no-common fall-out?

2020-10-27 Thread Michael Butler via freebsd-emulation 

On 9/24/20 12:06 PM, Michael Butler wrote:

I get a duplicate symbol error as follows ..

kBuild: Linking VBoxVNCMain
kBuild: Linking VBoxVNC
The failing command:
@c++ -shared   '-Wl,-rpath,/usr/local/lib/virtualbox' -fPIC 
  -m64   -o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/VBoxREM.so 
-Wl,-soname=VBoxREM.so 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/VBoxRecompiler.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/cpu-exec.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/exec.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/translate-all.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/host-utils.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/cutils.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/tcg-runtime.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/tcg/tcg.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/tcg/tcg-dyngen.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/fpu/softfloat-native.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/target-i386/op_helper.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/target-i386/helper.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/target-i386/translate.o 
   -L/usr/local/lib 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/bin/VBoxVMM.so 

/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/bin/VBoxRT.so 
   -lpthread

kBuild: Linking VBoxRemPrimary
ld: error: duplicate symbol: r14
 >>> defined at exec.h:41 (src/recompiler/target-i386/exec.h:41)
 >>> 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/cpu-exec.o:(r14) 


 >>> defined at exec.h:41 (src/recompiler/target-i386/exec.h:41)
 >>> 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/target-i386/op_helper.o:(.bss+0x0) 

c++: error: linker command failed with exit code 1 (use -v to see 
invocation)
kmk: *** 
[/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/kBuild/footer-pass2-compiling-targets.kmk:653: 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/VBoxREM.so] 
Error 1

kmk: *** Waiting for unfinished jobs


Still failing in the same way on -current ..

kBuild: Linking VBoxVNCMain
kBuild: Linking VBoxVNC
kBuild: Linking VBoxAPIWrap
The failing command:
@c++ -shared   '-Wl,-rpath,/usr/local/lib/virtualbox' -fPIC 
  -m64   -o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/VBoxREM.so 
-Wl,-soname=VBoxREM.so 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/VBoxRecompiler.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/cpu-exec.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/exec.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/translate-all.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/host-utils.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/cutils.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/tcg-runtime.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/tcg/tcg.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/tcg/tcg-dyngen.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/fpu/softfloat-native.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/target-i386/op_helper.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/target-i386/helper.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/target-

VirtualBox fails to build on -current; more no-common fall-out?

2020-09-24 Thread Michael Butler via freebsd-emulation 

I get a duplicate symbol error as follows ..

kBuild: Linking VBoxVNCMain
kBuild: Linking VBoxVNC
The failing command:
@c++ -shared   '-Wl,-rpath,/usr/local/lib/virtualbox' -fPIC 
 -m64   -o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/VBoxREM.so 
-Wl,-soname=VBoxREM.so 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/VBoxRecompiler.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/cpu-exec.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/exec.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/translate-all.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/host-utils.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/cutils.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/tcg-runtime.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/tcg/tcg.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/tcg/tcg-dyngen.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/fpu/softfloat-native.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/target-i386/op_helper.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/target-i386/helper.o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/target-i386/translate.o 
  -L/usr/local/lib 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/bin/VBoxVMM.so 

/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/bin/VBoxRT.so 
  -lpthread

kBuild: Linking VBoxRemPrimary
ld: error: duplicate symbol: r14
>>> defined at exec.h:41 (src/recompiler/target-i386/exec.h:41)
>>> 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/cpu-exec.o:(r14)

>>> defined at exec.h:41 (src/recompiler/target-i386/exec.h:41)
>>> 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/target-i386/op_helper.o:(.bss+0x0)
c++: error: linker command failed with exit code 1 (use -v to see 
invocation)
kmk: *** 
[/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/kBuild/footer-pass2-compiling-targets.kmk:653: 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxRemPrimary/VBoxREM.so] 
Error 1

kmk: *** Waiting for unfinished jobs

imb
___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"

Re: [package - head-amd64-default][emulators/virtualbox-ose] Failed for virtualbox-ose-5.2.34 in build

2019-10-22 Thread Michael Butler 
On 10/22/19 5:47 PM, Jung-uk Kim wrote:

 [ .. ]

> I went ahead and committed it.  Let me know if it still has issues.

Seems to do the trick. It applies equally well against v6.0.14 in my
local tree (cloned from your GIT repo).

Thanks!

imb

___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"

Re: [package - head-amd64-default][emulators/virtualbox-ose] Failed for virtualbox-ose-5.2.34 in build

2019-10-22 Thread Michael Butler 
On 10/22/19 1:33 PM, pkg-fall...@freebsd.org wrote:

 

> /wrkdirs/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.34/out/freebsd.amd64/release/obj/VBoxDD/vboxssdt_cpuhotplug.hex.pre1
>  29:  Processor (CPU1, 0x01, 0x0, 0x0 ) { Name (_HID, "ACPI0007") Name 
> (_UID, "SCK1-CPU0") Name (_PXM, 0x00) 
> Warning  3168 -   
>   Legacy Processor() keyword detected. Use Device() keyword instead. 
> ^ 
> 
> /wrkdirs/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.34/out/freebsd.amd64/release/obj/VBoxDD/vboxssdt_cpuhotplug.hex.pre1
>  29:  Processor (CPU1, 0x01, 0x0, 0x0 ) { Name (_HID, "ACPI0007") Name 
> (_UID, "SCK1-CPU0") Name (_PXM, 0x00) 
> Error6167 -   
>   
>  _UID inside processor declaration must be an integer ^  (found a string)

It seems that SVN r514730 update to sysutils/acpica-tools has broken
iasl's compatibility with VBox dsl sources :-(

imb
___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"

virtualbox-ose-5.2.30 fails to build on current

2019-05-16 Thread Michael Butler 
As follows ..

===>  Building for virtualbox-ose-5.2.30
cd /usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.30 && /bin/sh
-c '. /usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.30/env.sh
&&  VBOX_LIBPATH_X11=/usr/local VBOX_FREEBSD_SRC=/usr/src/sys
/usr/local/bin/kmk -j5'
Config.kmk:2885:
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.30/out/freebsd.amd64/release/DynamicConfig.kmk:
No such file or directory
Config.kmk:7277:
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.30/out/freebsd.amd64/release/revision.kmk:
No such file or directory
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.30/src/VBox/Main/Makefile.kmk:221:
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.30/out/freebsd.amd64/release/vboxapiwrap.kmk:
No such file or directory
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.30/src/libs/Makefile.kmk:87:
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.30/src/libs/libopus-1.2.1/Makefile.kmk:
No such file or directory
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.30/kBuild/footer-pass2-installs.kmk:67:
warning: overriding recipe for target
`/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.30/out/freebsd.amd64/release/bin/src/vboxdrv/include/iprt/crc.h'
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.30/kBuild/footer-pass2-installs.kmk:67:
warning: ignoring old recipe for target
`/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.30/out/freebsd.amd64/release/bin/src/vboxdrv/include/iprt/crc.h'
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.30/kBuild/footer-pass2-installs.kmk:67:
warning: overriding recipe for target
`/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.30/out/freebsd.amd64/release/dist/bin/src/vboxdrv/include/iprt/crc.h'
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.30/kBuild/footer-pass2-installs.kmk:67:
warning: ignoring old recipe for target
`/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.30/out/freebsd.amd64/release/dist/bin/src/vboxdrv/include/iprt/crc.h'
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.30/kBuild/footer-pass2-installs.kmk:67:
warning: overriding recipe for target
`/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.30/out/freebsd.amd64/release/bin/src/vboxdrv/include/iprt/net.h'
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.30/kBuild/footer-pass2-installs.kmk:67:
warning: ignoring old recipe for target
`/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.30/out/freebsd.amd64/release/bin/src/vboxdrv/include/iprt/net.h'
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.30/kBuild/footer-pass2-installs.kmk:67:
warning: overriding recipe for target
`/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.30/out/freebsd.amd64/release/dist/bin/src/vboxdrv/include/iprt/net.h'
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.30/kBuild/footer-pass2-installs.kmk:67:
warning: ignoring old recipe for target
`/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.30/out/freebsd.amd64/release/dist/bin/src/vboxdrv/include/iprt/net.h'
kmk: *** No rule to make target
`/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.30/src/libs/libopus-1.2.1/Makefile.kmk'.
 Stop.
*** Error code 2

Stop.
make[1]: stopped in /usr/ports/emulators/virtualbox-ose
*** Error code 1

What am I missing? 5.2.28 builds ok,

imb
___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"

Re: Virtualbox build fails

2018-07-08 Thread Michael Butler 
On 07/06/18 15:36, Sam Fourman Jr. wrote:
> I can also confirm virtualbox will not build on FreeBSD 12.0-CURRENT r336020

It may not be strictly correct but this patch will allow it to compile
and run on -current ..

As I'm not sure if the attachment will make it on the list, it reads ..

*** src/VBox/HostDrivers/Support/SUPDrvInternal.h.orig  Fri Jun 29
09:15:51 2018
--- src/VBox/HostDrivers/Support/SUPDrvInternal.h   Sun Jul  8
00:26:54 2018
***
*** 115,120 
--- 115,122 
  #   error "unsupported OS."
  #endif

+ #undef PVM
+
  #include "SUPDrvIOC.h"
  #include "SUPDrvIDC.h"




___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"

Re: [package - head-i386-default][emulators/virtualbox-ose-kmod] Failed for virtualbox-ose-kmod-5.1.18 in build

2017-04-18 Thread Michael Butler 

Looks like SVN r317061 broke VBox :-(

imb

On 4/18/17 12:46 AM, pkg-fall...@freebsd.org wrote:

You are receiving this mail as a port that you maintain
is failing to build on the FreeBSD package build server.
Please investigate the failure and submit a PR to fix
build.

Maintainer: v...@freebsd.org
Last committer: j...@freebsd.org
Ident:  $FreeBSD: head/emulators/virtualbox-ose-kmod/Makefile 436259 
2017-03-15 22:22:59Z jkim $
Log URL:
http://beefy11.nyi.freebsd.org/data/head-i386-default/p438755_s317076/logs/virtualbox-ose-kmod-5.1.18.log
Build URL:  
http://beefy11.nyi.freebsd.org/build.html?mastername=head-i386-default=p438755_s317076
Log:

>> Building emulators/virtualbox-ose-kmod
build started at Tue Apr 18 04:44:18 UTC 2017
port directory: /usr/ports/emulators/virtualbox-ose-kmod
building for: FreeBSD head-i386-default-job-10 12.0-CURRENT FreeBSD 
12.0-CURRENT r317076 i386
maintained by: v...@freebsd.org
Makefile ident:  $FreeBSD: head/emulators/virtualbox-ose-kmod/Makefile 
436259 2017-03-15 22:22:59Z jkim $
Poudriere version: 3.1.17-9-gf49c6f78
Host OSVERSION: 1200027
Jail OSVERSION: 1200028
Job Id: 10




!!! Jail is newer than host. (Jail: 1200028, Host: 1200027) !!!
!!! This is not supported. !!!
!!! Host kernel must be same or newer than jail. !!!
!!! Expect build failures. !!!



---Begin Environment---
SHELL=/bin/csh
UNAME_p=i386
UNAME_m=i386
OSVERSION=1200028
UNAME_v=FreeBSD 12.0-CURRENT r317076
UNAME_r=12.0-CURRENT
BLOCKSIZE=K
MAIL=/var/mail/root
STATUS=1
SAVED_TERM=
MASTERMNT=/usr/local/poudriere/data/.m/head-i386-default/ref
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin
POUDRIERE_BUILD_TYPE=bulk
PKGNAME=virtualbox-ose-kmod-5.1.18
OLDPWD=/
PWD=/usr/local/poudriere/data/.m/head-i386-default/ref/.p/pool
MASTERNAME=head-i386-default
SCRIPTPREFIX=/usr/local/share/poudriere
USER=root
HOME=/root
POUDRIERE_VERSION=3.1.17-9-gf49c6f78
SCRIPTPATH=/usr/local/share/poudriere/bulk.sh
LIBEXECPREFIX=/usr/local/libexec/poudriere
LOCALBASE=/usr/local
PACKAGE_BUILDING=yes
POUDRIEREPATH=/usr/local/bin/poudriere
---End Environment---

---Begin OPTIONS List---
===> The following configuration options are available for 
virtualbox-ose-kmod-5.1.18:
  DEBUG=off: Debug symbols, additional logs and assertions
  VIMAGE=off: VIMAGE virtual networking support
===> Use 'make config' to modify these settings
---End OPTIONS List---

--CONFIGURE_ARGS--
--build-headless --disable-alsa  --disable-dbus  --disable-docs  --disable-libvpx  --disable-pulse  
--disable-python  --disable-sdl-ttf  --disable-xpcom --nofatal --with-gcc="cc" 
--with-g++="c++"
--End CONFIGURE_ARGS--

--CONFIGURE_ENV--
XDG_DATA_HOME=/wrkdirs/usr/ports/emulators/virtualbox-ose-kmod/work  
XDG_CONFIG_HOME=/wrkdirs/usr/ports/emulators/virtualbox-ose-kmod/work  
HOME=/wrkdirs/usr/ports/emulators/virtualbox-ose-kmod/work TMPDIR="/tmp" 
SHELL=/bin/sh CONFIG_SHELL=/bin/sh
--End CONFIGURE_ENV--

--MAKE_ENV--
KMODDIR="/boot/modules" SYSDIR="/usr/src/sys" NO_XREF=yes XDG_DATA_HOME=/wrkdirs/usr/ports/emulators/virtualbox-ose-kmod/work  XDG_CONFIG_HOME=/wrkdirs/usr/ports/emulators/virtualbox-ose-kmod/work  
HOME=/wrkdirs/usr/ports/emulators/virtualbox-ose-kmod/work TMPDIR="/tmp" NO_PIE=yes MK_DEBUG_FILES=no MK_KERNEL_SYMBOLS=no SHELL=/bin/sh NO_LINT=YES PREFIX=/usr/local  LOCALBASE=/usr/local  LIBDIR="/usr/lib"  CC="cc" 
CFLAGS="-O2 -pipe  -fno-strict-aliasing"  CPP="cpp" CPPFLAGS=""  LDFLAGS="" LIBS=""  CXX="c++" CXXFLAGS="-O2 -pipe -fno-strict-aliasing "  MANPREFIX="/usr/local" 
BSD_INSTALL_PROGRAM="install  -s -m 555"  BSD_INSTALL_LIB="install  -s -m 0644"  BSD_INSTALL_SCRIPT="install  -m 555"  BSD_INSTALL_DATA="install  -m 0644"  BSD_INSTALL_MAN="install  -m 444"
--End MAKE_ENV--

--PLIST_SUB--
DEBUG="@comment
"
NO_DEBUG=""
VIMAGE="@comment
"
NO_VIMAGE=""
KMODDIR="boot/modules"
SYMBOLSUFFIX=debug
OSREL=12.0
PREFIX=%D
LOCALBASE=/usr/local
RESETPREFIX=/usr/local
PORTDOCS=""
PORTEXAMPLES=""
LIB32DIR=lib
DOCSDIR="share/doc/virtualbox-ose"
EXAMPLESDIR="share/examples/virtualbox-ose"
DATADIR="share/virtualbox-ose"
WWWDIR="www/virtualbox-ose"
ETCDIR="etc/virtualbox-ose"
--End PLIST_SUB--

--SUB_LIST--
DEBUG="@comment
"
NO_DEBUG=""
VIMAGE="@comment
"
NO_VIMAGE=""
PREFIX=/usr/local
LOCALBASE=/usr/local
DATADIR=/usr/local/share/virtualbox-ose
DOCSDIR=/usr/local/share/doc/virtualbox-ose
EXAMPLESDIR=/usr/local/share/examples/virtualbox-ose
WWWDIR=/usr/local/www/virtualbox-ose
ETCDIR=/usr/local/etc/virtualbox-ose
--End SUB_LIST--

---Begin make.conf---
USE_PACKAGE_DEPENDS=yes
BATCH=yes
WRKDIRPREFIX=/wrkdirs
PORTSDIR=/usr/ports
PACKAGES=/packages
DISTDIR=/distfiles
MACHINE=i386
MACHINE_ARCH=i386
ARCH=${MACHINE_ARCH}
 /usr/local/etc/poudriere.d/make.conf 
# XXX: We really need this but cannot use it while 'make checksum' does not
# try the next mirror on checksum failure.  It currently retries the same
# failed mirror and then fails rather then trying another.  It *does*
# try the next if

Re: SVN r316648 breaks virtualbox-ose-kmod

2017-04-09 Thread Michael Butler 
On 04/09/17 16:09, Michael Butler wrote:
> Today's renaming of smp_no_rendevous_barrier to
> smp_no_rendezvous_barrier breaks the kernel module build,

 patch didn't make it through list-serv.

The only affected source file is
src/VBox/Runtime/r0drv/freebsd/mp-r0drv-freebsd.c. A simple substitution
appears to be sufficient,

imb
___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"

SVN r316648 breaks virtualbox-ose-kmod

2017-04-09 Thread Michael Butler 
Today's renaming of smp_no_rendevous_barrier to
smp_no_rendezvous_barrier breaks the kernel module build,

imb
___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"

Re: webcam Logitech C920 on virtualbox guest machine

2016-08-12 Thread Michael Butler 
On 08/12/16 18:10, Hans Petter Selasky wrote:

>> but, on both machines, when I'm using USB 2.0 EHCI for USB support and
>> plug my webcam C920 I get
>>
> 
> Are there any VM debug logs showing USB errors? It is likely an
> emulation problem.

AFAIK, there is no USB 2 or 3 in Virtualbox for FreeBSD; no "PUEL"
extension pack,

imb


___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"

SVN r296272 breaks virtualbox

2016-03-01 Thread Michael Butler 
The removal of "taskqueue_enqueue_fast" breaks the virtualbox kmods:

Mar  1 16:54:36 toshi kernel: vboxdrv: fAsync=0 offMin=0x914 offMax=0x151c
Mar  1 16:54:36 toshi kernel: link_elf_obj: symbol
taskqueue_enqueue_fast undefined
Mar  1 16:54:36 toshi kernel: linker_load_file: Unsupported file type
Mar  1 16:54:36 toshi kernel: link_elf_obj: symbol
taskqueue_enqueue_fast undefined
Mar  1 16:54:36 toshi kernel: linker_load_file: Unsupported file type
Mar  1 16:54:36 toshi kernel: KLD vboxnetadp.ko: depends on vboxnetflt -
not available or version mismatch
Mar  1 16:54:36 toshi kernel: linker_load_file: Unsupported file type

Michael



___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"

Re: VirtualBox mangles memory

2015-09-22 Thread Michael Butler 
On 09/22/15 16:20, Adam Vande More wrote:
> On Tue, Sep 22, 2015 at 2:26 PM, Martin Birgmeier  wrote:

>> I am quite sure that the
>> cause is to be found there
>>
> 
> I don't see any cause for surety in the info you have given us.  Have you
> tried any basic steps like monitoring usage during these events or running
> it under truss/valgrind etc to find out what is going on?
> 

Another data point ..

I run it on -CURRENT and there have been a number of VM-related changes
of late but I don't have any problems with it.

However, you *must* recompile (at least) the modules whenever the kernel
is rebuilt as they depend heavily on the underlying kernel structures,

imb

___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"

Re: Unable to build virtualbox-ose after latest round up updates

2015-04-26 Thread Michael Butler 
On 04/26/15 00:02, Kevin Oberman wrote:
 On Sat, Apr 25, 2015 at 6:40 PM, michael butler
 
 Any idea how to deal with this? Is anyone else seeing this?
 
 Running 10-Stable r281259 with almost all ports up to date
 except chromium
 (which should have nothing to do with this issue).
 
 I really need to get my Windows 7 VM running again.
 
 I ran into something similar with KDE (still dealing with that :-()
 but the situation was improved somewhat by recompiling qt4-core,
 
 imb
 
 
 Michael,
 
 Thanks so much! That did the trick, though I am at a loss as to why. I
 rebuilt qt4-corelib and just finished a successful build of VB.

With or about the time of the ICU update, there was apparently a change
in name-mangling for one symbol related to libgthread. This seemed to
cause all manner of mysterious failures.

I'm glad that worked, I haven't made it that far yet; Too much time on
aircraft and too little on maintenance :-(

imb



___
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: Unable to build virtualbox-ose after latest round up updates

2015-04-25 Thread michael butler 

On 4/25/2015 5:22 PM, Kevin Oberman wrote:

After doing all of the updates yesterday and today, mostly due to the icu
shareable version bump,  virtualbox no longer starts.It finds a symbol in a
library from qt4-gui missing.

I reinstalled qt4-gui and tried rebuilding virtualbox-ose, but the rebuild
fails with:
kBuild: Installing
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.26/out/freebsd.amd64/release/bin/VMMGC.debug


 [ .. snip .. ]


kmk: *** Waiting for unfinished jobs
kmk: *** Exiting with status 2
*** Error code 2

Any idea how to deal with this? Is anyone else seeing this?

Running 10-Stable r281259 with almost all ports up to date except chromium
(which should have nothing to do with this issue).

I really need to get my Windows 7 VM running again.

I ran into something similar with KDE (still dealing with that :-() but 
the situation was improved somewhat by recompiling qt4-core,


imb

___
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: Error running VirtualBox 4.3.20_4 on PC-BSD 10.0

2015-03-22 Thread Michael Butler 
On 03/22/15 12:41, Miroslav Lachman wrote:
 Chris Newman wrote on 03/22/2015 14:07:

 [ .. snip .. ]

 VirtualBox: Error -610 in supR3HardenedMainInitRuntime!
 VirtualBox: dlopen(/usr/local/lib/virtualbox/VBoxRT.so,) failed: Shared
 object libcurl.so.4 not found, required by VBoxRT.so

 VirtualBox: Tip! It may help to reinstall VirtualBox.

 Reinstall did not help,  nor did trying to run it as root.
 
 You can try two things:
 
 ldd /usr/local/lib/virtualbox/VBoxRT.so
 
 And see if it shows you an existing libcurl line. For example
 libcurl.so.4 = /usr/local/lib/libcurl.so.4 (0x8021d4000)
 

This appears to be fall-out from the now disabled SSLv2 ..

imb@toshi:/home/imb VirtualBox
VirtualBox: Error -610 in supR3HardenedMainInitRuntime!
VirtualBox: dlopen(/usr/local/lib/virtualbox/VBoxRT.so,) failed:
/usr/local/lib/libcurl.so.4: Undefined symbol SSLv2_client_method

VirtualBox: Tip! It may help to reinstall VirtualBox.

curl needs to be rebuilt,

imb





signature.asc
Description: OpenPGP digital signature

Re: Error message at boot - Shared object libxml2.so.2 not found, required by VBoxRT.so

2015-01-23 Thread Michael Butler 
On 01/23/15 12:49, Steve Robertson wrote:
 Hello,
 
 I'm running Virtualbox under FreeBSD-10.1.  I noticed the following
 error at boot
 Shared object libxml2.so.2 not found, required by VBoxRT.so
 
 The link, libxml2.so.2, is present in /usr/local/lib/ and points to
 libxml2.so.2.9.2
 
 I've tried reinstalling virtualbox-ose, virtualbox-ose-kmod, and libxml2
 from ports.
 But the error message reappeared at the next reboot.
 
 The currently installed versions are:
 virtualbox-ose-kmod-4.3.20
 virtualbox-ose-4.3.20_4
 libxml2-2.9.2_2
 
 For an experiment I temporarily copied the libxml2* files and linked
 them in /lib.
 The result was that the libxml2 message was gone but a new error occured.
 Shared object *libcurl.so.4* not found, required by VBoxRT.so
 So I think the problem is that /usr/local/lib isn't in the search path
 at the time it's searched.
 
 Please let me know if I can provide any other information that can help
 troubleshoot the problem.


This seems to be as a consequence of /etc/rc.d/ldconfig requiring
mountcritremote which forces it down the chain when NFS is enabled even
when no 'critical' filesystems are on NFS mounts :-(

I simply remove that dependency by hand ..

imb





signature.asc
Description: OpenPGP digital signature

Re: boot hangs on fsck with linprocfs enabled.

2014-11-30 Thread Michael Butler 
On 11/30/14 14:27, Chris Roberts wrote:
 ###
 my /etc/fstab
 # DeviceMountpointFStypeOptionsDumpPass#
 /dev/ada0p2.elinoneswapsw00
 linproc  /compat/linux/proc   linprocfs   rw   0  1

This is wrong - pass should be 0

imb


___
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

vboxdrv et al on -current

2013-09-02 Thread Michael Butler 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

With recent header file changes in -current, the virtualbox modules have
ceased to compile :-( Has anyone looked at this yet?

imb

cd
/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.2.16/out/freebsd.x86/release/bin/src
 make SYSDIR=/usr/src/sys
*** Building 'vboxdrv' module ***
Warning: Object directory not changed from original
/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.2.16/out/freebsd.x86/release/bin/src/vboxdrv
@ - /usr/src/sys
machine - /usr/src/sys/i386/include
x86 - /usr/src/sys/x86/include
awk -f @/tools/makeobjops.awk @/kern/device_if.m -h
awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h
cc -O2 -pipe -march=prescott -DRT_OS_FREEBSD -DIN_RING0 -DIN_RT_R0
- -DIN_SUP_R0 -DSUPDRV_WITH_RELEASE_LOGGER -DVBOX -DRT_WITH_VBOX -w
- -DVBOX_WITH_HARDENING -DVBOX_WITH_64_BITS_GUESTS -DRT_ARCH_X86
- -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc  -Iinclude
- -I. -Ir0drv -I. -I@ -I@/contrib/altq -finline-limit=8000 --param
inline-unit-growth=100 --param large-function-growth=1000 -fno-common
- -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-sse
- -msoft-float -ffreestanding -fstack-protector -std=iso9899:1999
- -fstack-protector -Wall -Wredundant-decls -Wnested-externs
- -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline
- -Wcast-qual  -Wundef -Wno-pointer-sign -fformat-extensions
- -Wmissing-include-dirs -fdiagnostics-show-option   -c SUPDrv.c
In file included from SUPDrv.c:57:
include/iprt/x86.h:862:1: error: MSR_IA32_PLATFORM_ID redefined
In file included from ./machine/specialreg.h:6,
 from ./machine/atomic.h:37,
 from @/sys/systm.h:41,
 from @/sys/libkern.h:39,
 from include/iprt/string.h:67,
 from SUPDrvInternal.h:43,
 from SUPDrv.c:32:
./x86/specialreg.h:344:1: error: this is the location of the previous
definition
In file included from SUPDrv.c:57:
include/iprt/x86.h:869:1: error: MSR_IA32_FEATURE_CONTROL redefined
In file included from ./machine/specialreg.h:6,
 from ./machine/atomic.h:37,
 from @/sys/systm.h:41,
 from @/sys/libkern.h:39,
 from include/iprt/string.h:67,
 from SUPDrvInternal.h:43,
 from SUPDrv.c:32:
./x86/specialreg.h:348:1: error: this is the location of the previous
definition
In file included from SUPDrv.c:57:
include/iprt/x86.h:933:1: error: MSR_IA32_MISC_ENABLE redefined
In file included from ./machine/specialreg.h:6,
 from ./machine/atomic.h:37,
 from @/sys/systm.h:41,
 from @/sys/libkern.h:39,
 from include/iprt/string.h:67,
 from SUPDrvInternal.h:43,
 from SUPDrv.c:32:
./x86/specialreg.h:377:1: error: this is the location of the previous
definition
*** Error code 1
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (FreeBSD)

iEYEARECAAYFAlIkqfIACgkQQv9rrgRC1JKAdQCfS6EiyRU9QOo1obJw8N4S19kj
rNkAoMS0kakgqtYTQNT62gseBTm6QaDE
=sCuP
-END PGP SIGNATURE-
___
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

dbus 1.6.8 breaks VBox :-(

2013-04-14 Thread Michael Butler 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Apologies if this has been mentioned before but the update from dbus
1.4.14 to 1.6.8 breaks the file open dialogue when trying to attach a
new ISO file to a VM for installation.

The only fix I've found so far is to revert dbus to 1.4.14 :-(

Michael


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.13 (FreeBSD)

iEYEARECAAYFAlFq2N8ACgkQQv9rrgRC1JKLzACfWIBFbnTf9U9jWPLbOb/hTsGe
9IkAoKhvrAlzR7BNY5mFmR6fexYfzhpt
=LYP4
-END PGP SIGNATURE-
___
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: dbus 1.6.8 breaks VBox :-(

2013-04-14 Thread Michael Butler 
I rebuild all modules as part of any upgrade .. On the other hand, I'm running 
this on an Intel T-2300 (x86)

Sent from my iPhone

On Apr 14, 2013, at 20:26, Warren Block wbl...@wonkity.com wrote:

 On Sun, 14 Apr 2013, Michael Butler wrote:
 
 Apologies if this has been mentioned before but the update from dbus
 1.4.14 to 1.6.8 breaks the file open dialogue when trying to attach a
 new ISO file to a VM for installation.
 
 The only fix I've found so far is to revert dbus to 1.4.14 :-(
 
 Just tried, and it works here on amd64 9-stable with virtualbox-ose-4.2.6.  
 Could you have updated the operating system but not yet rebuilt the 
 VirtualBox kernel module?
___
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 driver patch for -current post SVN r248084

2013-03-09 Thread Michael Butler 
With the changing of the vm_object mutex to a rwlock, the VirtualBox
drivers (emulators/virtualbox-ose-kmod) need the attached patch to run,

imb
___
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: Freeze with 10.0 and VirtualBox {4.1.4|4.1.6|4.1.51r38464}

2011-11-26 Thread Michael Butler 

On 11/26/11 11:33, Gleb Kurtsou wrote:

On (26/11/2011 14:44), Andriy Gapon wrote:

vm_phys_alloc_contig implementation has been recently changed and now it seems
to require that vm_page_queue_free_mtx is held.


Using new vm_page_alloc_contig() may be a better option here. Can't help
with patch, stuck with pre Nov 15 CURRENT myself.


If I understand the change in locking semantics (post SVN r227568?), a 
good number of chunks of 
src/VBox/Runtime/r0drv/freebsd/memobj-r0drv-freebsd.c need updating to 
follow this :-(.


It is now insufficient to hold only the queue lock when calling 
vm_page_unwire or vm_page_free (and maybe others). The page itself must 
now also be locked,


imb

___
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: Freeze with 10.0 and VirtualBox {4.1.4|4.1.6|4.1.51r38464}

2011-11-25 Thread Michael Butler 

On 11/25/11 05:56, Gustau Pérez wrote:


Hi,

I'm seeing freezes with AMD64/CURRENT r227817 (as of Nov 22th). The
machine freezes hard when starting a virtual machine. It used work a few
weeks ago.

I've been using Bernhard's from a lot of time. 4.1.4 from a month ago
freezes. I had to apply the patch to fix the D_PSEUDO problem. I see it
was posted in the vbox mailing lists and commited upstream. So I
yesterday picked last virtualbox-port.tar.gz version at
http://svn.bluelife.at/nightlies. 4.1.6 included there also freezes the
machine.

So I recompiled the kernel with WITNESS, DEADLKRES and friends I see a
deadlock. This is the trace I got in my messages after rebooting the
machine:

Nov 25 08:57:06 portgus kernel: acquiring duplicate lock of same type:
IPRT Fast Mutex Semaphore
Nov 25 08:57:06 portgus kernel: acquiring duplicate lock of same type:
IPRT Fast Mutex Semaphore
Nov 25 08:57:06 portgus kernel: 1st IPRT Fast Mutex Semaphore @ \
/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.6_OSE/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/semfastmutex-r0drv-freebsd.c:100


I don't know if I'll have time to check this. I will try the versions in
the ports tree (4.012?) but if it works it will allow us to work until
4.1.X gets into the tree.


This appears to be related to recent changes in the locking mechanisms - 
specifically, SVN r227758 and r227788. I have not had time to explore 
further :-(


imb

___
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

current post svn r222813

2011-06-12 Thread Michael Butler 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Just a heads-up: the kernel module for VirtualBox no longer compiles
after the removal of cpumask_t type as it's now been replaced with
cpuset_t and a whole new set of functions to find the first free, etc.

Sadly, this change was not associated with an OS version bump making it
more difficult to automate the selection between APIs :-(

imb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (FreeBSD)

iEYEARECAAYFAk31XK8ACgkQQv9rrgRC1JIf8QCgpIhwfbgWty3PTgiBf63pj0BX
tbEAoMrGEnYz+qDYi4u4KJggYmmR7vmi
=5LHs
-END PGP SIGNATURE-
___
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: Call for Testers: VirtualBox 4.0.4

2011-02-23 Thread Michael Butler 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 02/23/11 05:32, Bernhard Froehlich wrote:
 I'm now at r1226 and this is *awesome* .. I can now see (and use!) my
 external USB drives from within a VirtualBox guest .. thanks!

 Thats great! Can you share which Host and Guest you use? I've tried it
 with a few USB sticks and had some problems mounting them in the guest
 so it's not working perfectly yet.

After testing a little more extensively:

Host is -current (SVN r218976) on an aging Toshiba laptop (T2300 CPU)

With a 2.5 SATA drive attached to a SunPlus USB2 to SATA bridge:

Guests that work are: Windows XP (SP3?), Windows XP MCE

Guests that don't: Windows Server 2003, Windows-7, Windows 7 SP1, CentOS 5.5

The failing Windows guests complain that the service 'USBSTOR' won't
start. Under 'Device Manager', the 'USB Mass Storage' driver does appear
but with a (triangular yellow) warning symbol.

Same results with a 4GB Verbatim Store'n'Go USB stick.

Even so - I think this is a *huge* step forward :-)

imb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (FreeBSD)

iEYEARECAAYFAk1lzbIACgkQQv9rrgRC1JKzAwCgjBHE/a5S+Cyua0bVrUaV2mV7
I+UAn0vVZBLFQmkDVZIz1Rf7SIpGkanU
=y5H/
-END PGP SIGNATURE-
___
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: Call for Testers: VirtualBox 4.0.4

2011-02-22 Thread Michael Butler 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 02/18/11 09:17, Bernhard Froehlich wrote:
 A few of you have probably wondered what happened to our VirtualBox
 efforts for FreeBSD. Well it took a bit longer then expected and a few
 problems were found that needed to be resolved first but most of the
 things are looking fine now and almost all patches have been pushed
 upstream with 4.0.4 so here we are now.

[ .. snip .. ]

 Highlights with 4.0:
 - USB support (by Hans Petter Selasky)

I'm now at r1226 and this is *awesome* .. I can now see (and use!) my
external USB drives from within a VirtualBox guest .. thanks!

imb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (FreeBSD)

iEYEARECAAYFAk1j8fEACgkQQv9rrgRC1JL6OACeMbGgTPrt+fBOLkpCTTR39Rh7
TvgAnR3j4UCBnD4hes0goVxS7aT/0U7c
=deFi
-END PGP SIGNATURE-
___
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-ose-kmod breakage after svn r218425

2011-02-09 Thread Michael Butler 
Attached is a patch required for vboxdrv.ko to load after the (public)
disappearance of uio_yield.

Presumably, this will need to be applied to the other branches at
bluelife.at

imb
___
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-ose-kmod breakage after svn r218425

2011-02-09 Thread Michael Butler 
On 02/09/11 14:00, Michael Butler wrote:
 Attached is a patch required for vboxdrv.ko to load after the (public)
 disappearance of uio_yield.
 
 Presumably, this will need to be applied to the other branches at
 bluelife.at
 
   imb

Mailman ate my homework!

*** ./src/VBox/Runtime/r0drv/freebsd/thread-r0drv-freebsd.c~Wed Dec
 1 12:09:43 2010
--- ./src/VBox/Runtime/r0drv/freebsd/thread-r0drv-freebsd.c Wed Feb
 9 13:44:28 2011
***
*** 101,107 
--- 101,111 

  RTDECL(bool) RTThreadYield(void)
  {
+ #if (__FreeBSD_version = 900032)
+ kern_yield(curthread-td_user_pri);
+ #else
  uio_yield();
+ #endif
  return false; /** @todo figure this one ... */
  }
___
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

recent virtualbox breakage

2010-10-15 Thread Michael Butler 
kBuild: iasl DevicesR3 -
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.2.10_OSE/src/VBox/Devices/PC/vbox.dsl
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.2.10_OSE/src/VBox/Devices/PC/vbox.dsl
   736: Name (_CID, smc-napa)
Error4001 -
String must be entirely alphanumeric ^
(smc-napa)

ASL Input:
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.2.10_OSE/src/VBox/Devices/PC/vbox.dsl
- 1305 lines, 46193 bytes, 288 keywords
Compilation complete. 1 Errors, 0 Warnings, 0 Remarks, 404 Optimizations
kmk[2]: ***
[/usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.2.10_OSE/out/freebsd.x86/release/obj/DevicesR3/vboxaml.hex]
Error 255
kmk[2]: *** Deleting file
`/usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.2.10_OSE/out/freebsd.x86/release/obj/DevicesR3/vboxaml.hex'
kmk[2]: *** Waiting for unfinished jobs
kmk[2]: Leaving directory
`/usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.2.10_OSE'
kmk[2]: Entering directory
`/usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.2.10_OSE'
kmk[2]: *** Exiting with status 2
kmk[1]: *** [pass_libraries_this] Error 2
kmk[1]: Leaving directory
`/usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.2.10_OSE'
kmk: *** [pass_libraries_order] Error 2
*** Error code 2

Stop in /usr/ports/emulators/virtualbox-ose.
*** Error code 1
___
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 2D acceleration

2010-10-07 Thread Michael Butler 
On 10/07/10 16:43, Sean C. Farley wrote:
 I do not know if all the zeros have to be ones for 2D to be supported or
 not.  The Intel v2.7 driver may not support 2D at least for your video
 card.  You could try xf86-video-intel29 instead of xf86-video-intel to
 see if that helps.  You need to remove the IGNORE line in the Makefile
 first.  I have no Intel hardware, so I do not know if this will help at
 any.

I have i915 DRM compiled into my kernel and, it seems, the 2.9 driver
doesn't agree with it :-(

Kernel message:

kernel: module_register: module vgapci/i915 already exists!
kernel: Module vgapci/i915 failed to register: 17

 .. which then yields (from /var/log/Xorg.0.log) ..

(EE) intel(0): [drm] Failed to detect GEM.  Kernel 2.6.28 required.
(EE) intel(0): Failed to become DRM master.

 [ .. ]

(II) AIGLX: Screen 0 is not DRI2 capable
(II) AIGLX: Screen 0 is not DRI capable
(II) AIGLX: Loaded and initialized /usr/local/lib/dri/swrast_dri.so
(II) GLX: Initialized DRISWRAST GL provider for screen 0

So it looks like a slightly larger mine-field than that for which I
currently have the time .. thanks anyways,

imb

___
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 3.2.2 on -current

2010-06-03 Thread Michael Butler 
On 06/03/10 15:06, Michael Butler wrote:
 On 06/03/10 15:04, Michael Butler wrote:
 Two patches are required to get VirtualBox 3.2.2 to compile on -current
 SVN r208788 (and, likely, before).
 
 Unofficial fixes for both attached,
 
 Hmmpff!

*** include/iprt/string.h~  Tue Apr 27 16:23:42 2010
--- include/iprt/string.h   Thu Jun  3 14:56:23 2010
***
*** 60,66 
  #if(defined(RT_OS_DARWIN)  defined(KERNEL)) \
  || (defined(RT_OS_FREEBSD)  defined(_KERNEL))
  RT_C_DECLS_BEGIN
! void *memchr(const void *pv, int ch, size_t cb);
  char *strpbrk(const char *pszStr, const char *pszChars);
  RT_C_DECLS_END
  #endif
--- 60,66 
  #if(defined(RT_OS_DARWIN)  defined(KERNEL)) \
  || (defined(RT_OS_FREEBSD)  defined(_KERNEL))
  RT_C_DECLS_BEGIN
! /* void *memchr(const void *pv, int ch, size_t cb); */
  char *strpbrk(const char *pszStr, const char *pszChars);
  RT_C_DECLS_END
  #endif

*** src/VBox/Frontends/VirtualBox/src/settings/vm/VBoxVMSettingsHD.h~
Wed Jun  2 10:04:53 2010
--- src/VBox/Frontends/VirtualBox/src/settings/vm/VBoxVMSettingsHD.h
Thu Jun  3 14:21:11 2010
***
*** 20,27 
  #define __VBoxVMSettingsHD_h__

  /* Global includes */
- #include qglobal.h /* for Q_WS_MAC */
  #ifdef Q_WS_MAC
  /* Somewhere Carbon.h includes AssertMacros.h which defines the macro
check.
   * In QItemDelegate a class method is called check also. As we not
used the
   * macro undefine it here. */
--- 20,27 
  #define __VBoxVMSettingsHD_h__

  /* Global includes */
  #ifdef Q_WS_MAC
+ #include qglobal.h /* for Q_WS_MAC */
  /* Somewhere Carbon.h includes AssertMacros.h which defines the macro
check.
   * In QItemDelegate a class method is called check also. As we not
used the
   * macro undefine it here. */
___
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: CFT: VirtualBox 3.2.0

2010-05-31 Thread Michael Butler 
On 05/31/10 04:55, Anton Berezin wrote:
 On Mon, May 31, 2010 at 11:01:04AM +0900, Daichi GOTO wrote:
 Memory leaks there I have noticed. Look at follow message of top(1):
 
 I also experience memory leaks.  WinXP guest, amd64-CURRENT (from
 2010-05-10) host.  100% CPU load when the guest is doing nothing, and memory
 usage keeps growing at a rather alarming pace.

Just an observation - this appears to be related to using the additions
from 3.2.0. Using VBox 3.2.0 with the 3.1.8 additions doesn't appear to
display the leak - no idea what triggers this behaviour,

imb
___
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