From: Doug Barton on 28 Dec 2009 13:24 Bernhard Froehlich wrote: > Looks like you installed the guest additions on the host. You should not > do that. They should only be installed on FreeBSD guests running in an > virtualbox. The pkg-descr and COMMENT should probably be amended to reflect this since it was confusing to me too. :) Perhaps something like the attached? Also, in looking at the shell script that is provided for the additions it would be nice if it could be updated to an rc.d style script. If anyone wants to tackle that and needs help feel free to follow up on the -ports list, or freebsd-rc(a)FreeBSD.org. Doug -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/
From: John Baldwin on 28 Dec 2009 12:44 On Monday 28 December 2009 11:46:36 am Brandon Gooch wrote: > On Mon, Dec 28, 2009 at 10:04 AM, John Baldwin <jhb(a)freebsd.org> wrote: > > On Monday 28 December 2009 9:25:28 am Gary Jennejohn wrote: > [SNIP] > >> > >> Does vboxguest.ko have silent dependencies on other vbox modules? I only > >> loaded vboxdrv.ko. > > > > Look in dmesg for the real kldload error message. > > > > I'm seeing this as well: > > kernel: link_elf_obj: symbol _Z6strlenPKc undefined > > ...which, I suppose, is the real kldload error message. Looks like it is trying to use a C++ named-version of strlen(): % echo _Z6strlenPKc | c++filt strlen(char const*) Is the kernel module compiled using c++ instead of cc? -- John Baldwin _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Gary Jennejohn on 28 Dec 2009 14:08 Bernhard Froehlich wrote: > Looks like you installed the guest additions on the host. You should not > do that. They should only be installed on FreeBSD guests running in an > virtualbox. > I installed it in the guest (PC-BSD) and got _exactly_ the same error as on the host. Something is fubar. --- Gary Jennejohn _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: "Bernhard Froehlich" on 28 Dec 2009 14:23 On Mon, December 28, 2009 7:24 pm, Doug Barton wrote: > Bernhard Froehlich wrote: >> Looks like you installed the guest additions on the host. You should not >> do that. They should only be installed on FreeBSD guests running in an >> virtualbox. > > The pkg-descr and COMMENT should probably be amended to reflect this > since it was confusing to me too. :) Perhaps something like the attached? > > Also, in looking at the shell script that is provided for the > additions it would be nice if it could be updated to an rc.d style > script. If anyone wants to tackle that and needs help feel free to > follow up on the -ports list, or freebsd-rc(a)FreeBSD.org. Thanks. I've applied the patch and will write a new rc.d startscript for the guest additions. Looks like they need a bit love anyway. http://svn.bluelife.at/index.cgi/blueports/revision/?rev=607 -- Bernhard Fr�hlich http://www.bluelife.at/ _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: David Southwell on 29 Dec 2009 07:21
> Beat Gaetzi wrote: > > Philipp Wuensche wrote: > >> Martin Wilke wrote: > >>> Please report any functionality which was working with previous > >>> versions of VirtualBox and no longer working with 3.1.2 or any build > >>> failure. > >> > >> Seem like the fix from > >> http://www.freebsd.org/cgi/cvsweb.cgi/ports/emulators/virtualbox/files/p > >>atch-src-VBox-HostDrivers-VBoxNetAdp-freebsd-VBoxNetAdp-freebsd.c was not > >> incorporated?! > > > > This fix is also included in 3.1.2: > > http://svn.bluelife.at/index.cgi/blueports/revision/?rev=580 > > Interesting, I have to load the modules in the correct order, otherwise > I get this error in the VBox.log: > > 00:00:00.470 IntNet#0: szNetwork={HostInterfaceNetworking-em0} > enmTrunkType=3 szTrunk={em0} fFlags=0x0 cbRecv=223232 cbSend=36864 > 00:00:00.470 VMSetError: > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.2_OSE/src/VBox/Devi > ces/Network/DrvIntNet.cpp(1071) int drvIntNetConstruct(PDMDRVINS*, > CFGMNODE*, uint32_t) > 00:00:00.470 VMSetError: Failed to open/create the internal network > 'HostInterfaceNetworking-em0' > 00:00:00.470 PDM: Failed to construct 'pcnet'/0! > VERR_SUPDRV_COMPONENT_NOT_FOUND (-3700) - The component factory was not > found. > 00:00:01.033 VMSetError: > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.2_OSE/src/VBox/VMM/ > VM.cpp(323) int VMR3Create(uint32_t, void (*)(VM*, void*, int, const char*, > unsigned int, const char*, const char*, __va_list_tag*), void*, int > (*)(VM*, void*), void*, VM**) > 00:00:01.033 VMSetError: Unknown error creating VM > 00:00:01.034 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) > aIID={6375231a-c17c-464b-92cb-ae9e128d71c3} aComponent={Console} > aText={Failed to open/create the internal network > 'HostInterfaceNetworking-em0' (VERR_SUPDRV_COMPONENT_NOT_FOUND). > 00:00:01.034 Unknown error creating VM > (VERR_SUPDRV_COMPONENT_NOT_FOUND)} aWarning=false, preserve=false > 00:00:01.036 Power up failed (vrc=VERR_SUPDRV_COMPONENT_NOT_FOUND, > rc=NS_ERROR_FAILURE (0X80004005)) > Any chance of being able to run snow leopard in an openbox environment? David _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org" |