Problem with FreeBSD port

Bernhard Froehlich decke at bluelife.at
Mon Oct 12 15:02:15 UTC 2009


On Mon, October 12, 2009 3:59 pm, Mario Lobo wrote:
> Hi;
>
> I've been following the FreeBSD port through svn.bluelife.at.
>
> Up to revision 508, everything was fine. On Rev 519 (or before, i'm not
> sure),
> the port was split into 3. virtualbox, virtualbox-additions and
> virtualbox-
> kmod.
>
>
> There is no problem building virtualbox-kmod. and virtualbox. The modules
> load
> without errors and virtualbox starts fine. But when I try to start a VM I
> get
> this:
>
> 00:00:00.644 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005)
> aIID={0a51994b-
> cbc6-4686-94eb-d4e4023280e2} aComponent={Console} aText={Failed to open
> the
> host network interface re0} aWarning=false, preserve=false
>
> 00:00:00.654 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005)
> aIID={0a51994b-
> cbc6-4686-94eb-d4e4023280e2} aComponent={Console} aText={Failed to
> initialize
> Host Interface Networking (VERR_HOSTIF_INIT_FAILED).
>
> 00:00:00.654 Unknown error creating VM (VERR_HOSTIF_INIT_FAILED)}
> aWarning=false, preserve=false
>
> 00:00:00.658 Power up failed (vrc=VERR_HOSTIF_INIT_FAILED,
> rc=NS_ERROR_FAILURE
> (0X80004005))
>
> kldstat
> Id Refs Address            Size     Name
>  1   60 0xffffffff80100000 caeef0   kernel
>  2    2 0xffffffff80daf000 41110    linux.ko
>  3    1 0xffffffff80df1000 5b58     snd_cmi.ko
>  4    3 0xffffffff80df7000 755a8    sound.ko
>  5    1 0xffffffff80e6d000 27d8     amdtemp.ko
>  6    1 0xffffffff80e70000 3e20     amdsmb.ko
>  7    2 0xffffffff80e74000 24d8     smbus.ko
>  8    2 0xffffffff80e77000 227d8    drm.ko
>  9    2 0xffffffff80e9a000 12c88    agp.ko
> 10    1 0xffffffff80ead000 712e0    radeon.ko
> 11    1 0xffffffff80f1f000 5278     atapicam.ko
> 12    1 0xffffffff80f25000 fff0     cpufreq.ko
> 13    1 0xffffffff81022000 3983     linprocfs.ko
> 14    3 0xffffffff81026000 22db6    vboxdrv.ko
> 15    2 0xffffffff81049000 26ce     vboxnetflt.ko
> 16    2 0xffffffff8104c000 8d2c     netgraph.ko
> 17    1 0xffffffff81055000 13a6     ng_ether.ko
> 18    1 0xffffffff81057000 d2c      vboxnetadp.ko
> 19    1 0xffffffff81058000 a8ca     fuse.ko
> 20    1 0xffffffff81063000 b5b2     ext2fs.ko
>
> It is as if virtualbox can't "see" that the modules ARE loaded, and
> connect to
> them.
>
> If I revert to the previous version (with the modules compiled together
> with
> virtualbox), everything works again.
>
> OS:
>  FreeBSD 8.0-RC1 #0: Sat Oct 10 16:16:42 BRT 2009 amd64
>

Good that you have found the correct mailinglist. FreeBSD related vbox
problems are best discussed on freebsd-emulation@ and if we need help from
upstream we contact vbox-dev@ or a few people on the virtualbox side in
private to not annoy them with common or FreeBSD specific problems.

The current svn version is very experimental as they have recently changed
a lot of build and kernel module related things so i am not very surprised
that this code doesn't work at the moment. I have an FreeBSD 8.0-RC1/amd64
box standing around so i will test it myself and see what we get.

-- 
Bernhard Fröhlich
http://www.bluelife.at/



More information about the freebsd-emulation mailing list