Problem with FreeBSD port (re-post)

[Mario Lobo-2]

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))

Neither "Bridge adapter" or "host only" are avaliable anymore.


kldstat
Id Refs Address            Size     Name
 1   60 0xffffffff80100000 caeef0   kernel
 2    2 0xffffffff80daf000 41110    linux.ko
 3    1 0xffffffff80df1000 3ec0     ng_ether.ko
 4    3 0xffffffff80df5000 14d78    netgraph.ko
 5    1 0xffffffff80e0a000 5b58     snd_cmi.ko
 6    3 0xffffffff80e10000 755a8    sound.ko
 7    1 0xffffffff80e86000 27d8     amdtemp.ko
 8    1 0xffffffff80e89000 3e20     amdsmb.ko
 9    2 0xffffffff80e8d000 24d8     smbus.ko
10    2 0xffffffff80e90000 227d8    drm.ko
11    2 0xffffffff80eb3000 12c88    agp.ko
12    1 0xffffffff80ec6000 712e0    radeon.ko
13    3 0xffffffff80f38000 41070    vboxdrv.ko
14    2 0xffffffff80f7a000 6c40     vboxnetflt.ko
15    1 0xffffffff80f81000 25e8     vboxnetadp.ko
16    1 0xffffffff80f84000 5278     atapicam.ko
17    1 0xffffffff80f8a000 fff0     cpufreq.ko
18    1 0xffffffff81022000 3983     linprocfs.ko
19    1 0xffffffff81026000 a8ca     fuse.ko
20    1 0xffffffff81031000 b5b2     ext2fs.ko

[~]>ifconfig
re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=389b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC>
        ether 00:19:66:d7:a3:45
        inet 10.10.10.2 netmask 0xffffff00 broadcast 10.10.10.255
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
vboxnet0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 0a:00:27:00:00:00
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=3<RXCSUM,TXCSUM>
        inet 127.0.0.1 netmask 0xff000000


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 - ports/emulators/virtualbox/Makefile,v 1.3 2009/06/15 22:24:42 nox
Exp $), everything works again.

OS:
 FreeBSD 8.0-RC1 #0: Sat Oct 10 16:16:42 BRT 2009 amd64

Any suggestions?

Thanks,
--
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since version 2.2.8 [not Pro-Audio.... YET!!] (99,7% winedows FREE)
_______________________________________________
freebsd-emulation@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscribe@..."

[miwi-2]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, Oct 13, 2009 at 09:27:58AM -0300, 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.
>

Mario,

PLEASE PLEASE Stop now your cross posting, we are know about that error
and we're working on that error. BUT we've ever said svn.bluelife.at.
is our developers repo SO PLEASE DON'T BUG us for any errors in bluelife,
if we're not call for test.
At the moment we're working on a split of virtualbox and kernel module
that's why you have the error. We call for testing if we are think
it's ready for a public test.

- - Martin on behalf of FreeBSD vbox team

>
> 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))
>
> Neither "Bridge adapter" or "host only" are avaliable anymore.
>
>
> kldstat
> Id Refs Address            Size     Name
>  1   60 0xffffffff80100000 caeef0   kernel
>  2    2 0xffffffff80daf000 41110    linux.ko
>  3    1 0xffffffff80df1000 3ec0     ng_ether.ko
>  4    3 0xffffffff80df5000 14d78    netgraph.ko
>  5    1 0xffffffff80e0a000 5b58     snd_cmi.ko
>  6    3 0xffffffff80e10000 755a8    sound.ko
>  7    1 0xffffffff80e86000 27d8     amdtemp.ko
>  8    1 0xffffffff80e89000 3e20     amdsmb.ko
>  9    2 0xffffffff80e8d000 24d8     smbus.ko
> 10    2 0xffffffff80e90000 227d8    drm.ko
> 11    2 0xffffffff80eb3000 12c88    agp.ko
> 12    1 0xffffffff80ec6000 712e0    radeon.ko
> 13    3 0xffffffff80f38000 41070    vboxdrv.ko
> 14    2 0xffffffff80f7a000 6c40     vboxnetflt.ko
> 15    1 0xffffffff80f81000 25e8     vboxnetadp.ko
> 16    1 0xffffffff80f84000 5278     atapicam.ko
> 17    1 0xffffffff80f8a000 fff0     cpufreq.ko
> 18    1 0xffffffff81022000 3983     linprocfs.ko
> 19    1 0xffffffff81026000 a8ca     fuse.ko
> 20    1 0xffffffff81031000 b5b2     ext2fs.ko
>
> [~]>ifconfig
> re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
>         options=389b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC>
>         ether 00:19:66:d7:a3:45
>         inet 10.10.10.2 netmask 0xffffff00 broadcast 10.10.10.255
>         media: Ethernet autoselect (100baseTX <full-duplex>)
>         status: active
> vboxnet0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
>         ether 0a:00:27:00:00:00
> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
>         options=3<RXCSUM,TXCSUM>
>         inet 127.0.0.1 netmask 0xff000000
>
>
> 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 - ports/emulators/virtualbox/Makefile,v 1.3 2009/06/15 22:24:42 nox
> Exp $), everything works again.
>
> OS:
>  FreeBSD 8.0-RC1 #0: Sat Oct 10 16:16:42 BRT 2009 amd64
>
> Any suggestions?
>
> Thanks,
> --
> Mario Lobo
> http://www.mallavoodoo.com.br
> FreeBSD since version 2.2.8 [not Pro-Audio.... YET!!] (99,7% winedows FREE)
> _______________________________________________
> freebsd-emulation@... mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
> To unsubscribe, send any mail to "freebsd-emulation-unsubscribe@..."
>

- --

+-----------------------+-------------------------------+
|  PGP    : 0xB1E6FCE9  |  Jabber : miwi(at)BSDCrew.de  |
|  Skype  : splash_111  |  Mail   : miwi(at)FreeBSD.org |
+-----------------------+-------------------------------+
| Mess with the Best, Die like the Rest! |
+-----------------------+-------------------------------+
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (FreeBSD)

iEYEARECAAYFAkrUg/MACgkQdLJIhLHm/OnTQACfReH8isBs2VPWroEyAyJw3hUK
m1QAn04EiNZVRCFMu8c5B4WRiqX1RdIM
=4/Au
-----END PGP SIGNATURE-----
_______________________________________________
freebsd-emulation@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscribe@..."

[Mario Lobo-2]

On Tuesday 13 October 2009 10:43:15 Martin Wilke wrote:
>
> Mario,
>
> PLEASE PLEASE Stop now your cross posting, we are know about that error
> and we're working on that error. BUT we've ever said svn.bluelife.at.
> is our developers repo SO PLEASE DON'T BUG us for any errors in bluelife,
> if we're not call for test.

I am aware of that. My only wish was to contribute but please forgive
my wrong approach.

> At the moment we're working on a split of virtualbox and kernel module
> that's why you have the error. We call for testing if we are think
> it's ready for a public test.
>
> - Martin on behalf of FreeBSD vbox team


I'll just seat quietly and keep on trying what comes out of svn (just like
I've been doing all along).

Sorry about the noise. It won't happen again.

--
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since version 2.2.8 [not Pro-Audio.... YET!!] (99,7% winedows FREE)
_______________________________________________
freebsd-emulation@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscribe@..."