Re: current now panics when starting VBox VM

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

Re: current now panics when starting VBox VM

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

Re: current now panics when starting VBox VM

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 bise

current now panics when starting VBox VM

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

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

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 fails to build on -current; more no-common fall-out?

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

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

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

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

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

virtualbox-ose-5.2.30 fails to build on current

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'

Re: Virtualbox build fails

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 .. ***

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

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:

Re: SVN r316648 breaks virtualbox-ose-kmod

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

SVN r316648 breaks virtualbox-ose-kmod

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

Re: webcam Logitech C920 on virtualbox guest machine

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

SVN r296272 breaks virtualbox

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

Re: VirtualBox mangles memory

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

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

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

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

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

Re: Error running VirtualBox 4.3.20_4 on PC-BSD 10.0

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

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

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

Re: boot hangs on fsck with linprocfs enabled.

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

vboxdrv et al on -current

-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

dbus 1.6.8 breaks VBox :-(

-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 :-(

Re: dbus 1.6.8 breaks VBox :-(

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

VirtualBox driver patch for -current post SVN r248084

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

Re: Freeze with 10.0 and VirtualBox {4.1.4|4.1.6|4.1.51r38464}

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,

Re: Freeze with 10.0 and VirtualBox {4.1.4|4.1.6|4.1.51r38464}

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

current post svn r222813

-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

Re: Call for Testers: VirtualBox 4.0.4

-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

Re: Call for Testers: VirtualBox 4.0.4

-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

virtualbox-ose-kmod breakage after svn r218425

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

Re: virtualbox-ose-kmod breakage after svn r218425

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

recent virtualbox breakage

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 -

Re: VirtualBox 2D acceleration

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

Re: VirtualBox 3.2.2 on -current

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

Re: CFT: VirtualBox 3.2.0

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