[Call For Testing] VirtualBox for FreeBSD!

[Martin Wilke]

Howdy Guys,

After the announcement from Alexander Eichner about
Virtualbox on FreeBSD, we started the work on a port
for FreeBSD. Now we think that we solved the most
problems and are ready for the first Call for Testing.

Some notes before you can test the port:
Make sure you are using RELENG_7 or higher. You have
to use a fresh portstree with uptodate ports!! Please
read carefully the pkg-messages.

Some known issues / Troubleshooting:
Sometimes the kernel on HEAD coredumps when loading
or unloading the kernel module. A small workaround
to prevent the crash is to not start X, mount proc,
then load the kernel module and start X from the
console. That helped me and some testers, maybe you
too. :P AMD64 should be work in general, it builds
and start. But not right tested at the moment. We
want here also some feedback.

Some Thanks:
First of all we'd like to say many thanks to _ALL_
vbox developers. Next people are Bernhard Froehlich
(aka decke), Beat Gaetzi (beat@), Dennis Herrmann
(dhn@), Pietro Cerutti (gahr@), myself (*gg*),
and _ALL_ who helped and provided feedback.

Happy Testing :-)

Download:

http://people.freebsd.org/~miwi/vbox/vboxport.tgz

Wiki Page:
http://wiki.freebsd.org/VirtualBox

- Martin

- --

+-----------------------+-------------------------------+
| PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de |
| ICQ : 169139903 | Mail : miwi(at)FreeBSD.org |
+-----------------------+-------------------------------+
| Mess with the Best, Die like the Rest! |
+-----------------------+-------------------------------+

[Gustau Pérez]

Post by Martin Wilke
Howdy Guys,
After the announcement from Alexander Eichner about Virtualbox on
FreeBSD, we started the work on a port for FreeBSD. Now we think
that we solved the most problems and are ready for the first Call
for Testing.
Some notes before you can test the port: Make sure you are using
RELENG_7 or higher. You have to use a fresh portstree with uptodate
ports!! Please read carefully the pkg-messages.
Some known issues / Troubleshooting: Sometimes the kernel on HEAD
coredumps when loading or unloading the kernel module. A small
workaround to prevent the crash is to not start X, mount proc, then
load the kernel module and start X from the console. That helped me
and some testers, maybe you too. :P AMD64 should be work in
general, it builds and start. But not right tested at the moment.
We want here also some feedback.
Some Thanks: First of all we'd like to say many thanks to _ALL_
vbox developers. Next people are Bernhard Froehlich (aka decke),
Happy Testing :-)
http://people.freebsd.org/~miwi/vbox/vboxport.tgz
Wiki Page: http://wiki.freebsd.org/VirtualBox

I'm testing with i386/HEAD. I have two issues :

1.- The first time I start a machine. The window stays gray. If
I pause and resume the window turns to
black. Virtualbox says it is running, but it is not.

2.- The second and subsequent times I start a virtual machine,
virtualbox says that there isn't the kernel driver. The
error is :

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: Machine
Interface: IMachine {4d1df26d-d9c1-4c7e-b689-15e85ecf8ffc}

And :

Kernel driver not installed (rc=-1908)

Make sure the kernel module has been loaded successfully.

What can be done ?

Regards,

Gustau

Post by Martin Wilke
- Martin

_______________________________________________
freebsd-***@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-***@freebsd.org"

- --
PGP KEY : http://www-entel.upc.edu/gus/gus.asc

[Martin Wilke]

Post by Sergey V. Dyatko
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Post by Martin Wilke
Howdy Guys,
After the announcement from Alexander Eichner about Virtualbox on
FreeBSD, we started the work on a port for FreeBSD. Now we think
that we solved the most problems and are ready for the first Call
for Testing.
Some notes before you can test the port: Make sure you are using
RELENG_7 or higher. You have to use a fresh portstree with uptodate
ports!! Please read carefully the pkg-messages.
Some known issues / Troubleshooting: Sometimes the kernel on HEAD
coredumps when loading or unloading the kernel module. A small
workaround to prevent the crash is to not start X, mount proc, then
load the kernel module and start X from the console. That helped me
and some testers, maybe you too. :P AMD64 should be work in
general, it builds and start. But not right tested at the moment.
We want here also some feedback.
Some Thanks: First of all we'd like to say many thanks to _ALL_
vbox developers. Next people are Bernhard Froehlich (aka decke),
Happy Testing :-)
http://people.freebsd.org/~miwi/vbox/vboxport.tgz
Wiki Page: http://wiki.freebsd.org/VirtualBox

1.- The first time I start a machine. The window stays gray. If
I pause and resume the window turns to
black. Virtualbox says it is running, but it is not.
2.- The second and subsequent times I start a virtual machine,
virtualbox says that there isn't the kernel driver. The
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: Machine
Interface: IMachine {4d1df26d-d9c1-4c7e-b689-15e85ecf8ffc}
Kernel driver not installed (rc=-1908)
Make sure the kernel module has been loaded successfully.
What can be done ?
Regards,
Gustau

Unfortunately, I saw this problem today also, I'll set this to our todo.

Thanks

Post by Sergey V. Dyatko

Post by Martin Wilke
- Martin

_______________________________________________
http://lists.freebsd.org/mailman/listinfo/freebsd-current
- --
PGP KEY : http://www-entel.upc.edu/gus/gus.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkoMh9AACgkQAvcpDulVChDtMACdGK3ggUplPWifN4ozP2Ac5fOa
pjQAn2ErwBcuTAfn/coIaY12J4lGQrUX
=5myk
-----END PGP SIGNATURE-----

- --

+-----------------------+-------------------------------+
| PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de |
| ICQ : 169139903 | Mail : miwi(at)FreeBSD.org |
+-----------------------+-------------------------------+
| Mess with the Best, Die like the Rest! |
+-----------------------+-------------------------------+

[Artem Belevich]

I'm trying to build on CURRENT/amd64

kBuild binaries that come with the port are for FreeBSD-6.3 and seem
to depend on KSE and would at the very minimum need /etc/libmap.conf
tweaking in order to get them to work.

Perhaps it would be better to make port depend on kBuild and just do
ln -s /usr/local/bin work/virtualbox-2.2.2r19673/kBuild/bin/freebsd.amd64

with kBuild installed from ports vbox did finish building.

--Artem

[Artem Belevich]

Few more notes from -CURRENT/amd64

* VirtualBox needs /proc mounted, otherwise it fails to start.
* Kernel module must be loaded with "kldload vboxdrv"

In my case, I de see bunch of relocation errors on the console,
though the module does load:

kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
vboxdrv: fAsync=0 offMin=0xb25 offMax=0x39a8

* Attempt to boot new VM (64-bit FreeBSD) from -current snapshot DVD
ISO results in an error:

Failed to start the virtual machine FreeBSD.
Failed to load VMMR0.r0 (VERR_SYMBOL_VALUE_TOO_BIG).
Unknown error creating VM (VERR_SYMBOL_VALUE_TOO_BIG).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: Console
Interface: IConsole {a7f17a42-5b64-488d-977b-4b2c639ada27}

* Subsequent attempts to start VM result in an error message that
kernel module is not present, even though kldstat shows it just fine.


Any suggestions on how to make it work?

--Artem

Post by Artem Belevich
I'm trying to build on CURRENT/amd64
kBuild binaries that come with the port are for FreeBSD-6.3 and seem
to depend on KSE and would at the very minimum need /etc/libmap.conf
tweaking in order to get them to work.
Perhaps it would be better to make port depend on kBuild and just do
ln -s /usr/local/bin work/virtualbox-2.2.2r19673/kBuild/bin/freebsd.amd64
with kBuild installed from ports vbox did finish building.
--Artem

[Martin Wilke]

Post by Artem Belevich
Few more notes from -CURRENT/amd64
* VirtualBox needs /proc mounted, otherwise it fails to start.
* Kernel module must be loaded with "kldload vboxdrv"

- From my mail:
Some notes before you can test the port:
Make sure you are using RELENG_7 or higher. You have
to use a fresh portstree with uptodate ports!! Please
read carefully the pkg-messages.

Post by Artem Belevich
In my case, I de see bunch of relocation errors on the console,
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
vboxdrv: fAsync=0 offMin=0xb25 offMax=0x39a8
* Attempt to boot new VM (64-bit FreeBSD) from -current snapshot DVD
Failed to start the virtual machine FreeBSD.
Failed to load VMMR0.r0 (VERR_SYMBOL_VALUE_TOO_BIG).
Unknown error creating VM (VERR_SYMBOL_VALUE_TOO_BIG).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: Console
Interface: IConsole {a7f17a42-5b64-488d-977b-4b2c639ada27}
* Subsequent attempts to start VM result in an error message that
kernel module is not present, even though kldstat shows it just fine.

Maybe is here the problem you link to devel/kbuild.

Post by Artem Belevich
Any suggestions on how to make it work?
--Artem

Post by Artem Belevich
I'm trying to build on CURRENT/amd64
kBuild binaries that come with the port are for FreeBSD-6.3 and seem
to depend on KSE and would at the very minimum need /etc/libmap.conf
tweaking in order to get them to work.
Perhaps it would be better to make port depend on kBuild and just do
ln -s /usr/local/bin work/virtualbox-2.2.2r19673/kBuild/bin/freebsd.amd64
with kBuild installed from ports vbox did finish building.
--Artem

- --

+-----------------------+-------------------------------+
| PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de |
| ICQ : 169139903 | Mail : miwi(at)FreeBSD.org |
+-----------------------+-------------------------------+
| Mess with the Best, Die like the Rest! |
+-----------------------+-------------------------------+

[Artem Belevich]

Post by Martin Wilke

Post by Artem Belevich
* VirtualBox needs /proc mounted, otherwise it fails to start.
* Kernel module must be loaded with "kldload vboxdrv"

Make sure you are using RELENG_7 or higher. You have
to use a fresh portstree with uptodate ports!! Please
read carefully the pkg-messages.

Oops. Indeed it warns about /proc and kernel module. I guess I just
was too eager to get VirtualBox running to pause and read
documentation.

Post by Martin Wilke
Maybe is here the problem you link to devel/kbuild.

As I explained, kbuild that comes with the port does not work for me.
And I *do* have compat6-amd64 installed. Apparently I'm not alone. See
Benoit's email in this thread.

Here's what needs to be added to /etc/libmap.conf in order to make
supplied libraries work:
libpthread.so.2 libthr.so.2

I'll re-do the build with supplied kbuild and see if that makes any difference.

In any case, I appreciate all the work you and others have done to get
VirtualBox on FreeBSD running.

--Artem

[Artem Belevich]

Post by Artem Belevich
Here's what needs to be added to /etc/libmap.conf in order to make
libpthread.so.2 libthr.so.2
I'll re-do the build with supplied kbuild and see if that makes any difference.

Re-built virtualbox with kBiuild supplied in the tarball and behavior
didn't change compared to the one built with kBuild from ports.

Loading module still shows relocation errors "kldload: unexpected
relocation type 10" and attempt to run VM fails with the same errors
I've reported before.

--Artem

[Bernhard Fröhlich]

Post by Artem Belevich
Few more notes from -CURRENT/amd64
[snip]
* Attempt to boot new VM (64-bit FreeBSD) from -current snapshot DVD
Failed to start the virtual machine FreeBSD.
Failed to load VMMR0.r0 (VERR_SYMBOL_VALUE_TOO_BIG).
Unknown error creating VM (VERR_SYMBOL_VALUE_TOO_BIG).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: Console
Interface: IConsole {a7f17a42-5b64-488d-977b-4b2c639ada27}

That is an amd64 problem and it is already being worked on. Sorry no
solution yet.

[Martin Wilke]

Post by Artem Belevich
I'm trying to build on CURRENT/amd64
kBuild binaries that come with the port are for FreeBSD-6.3 and seem
to depend on KSE and would at the very minimum need /etc/libmap.conf
tweaking in order to get them to work.
Perhaps it would be better to make port depend on kBuild and just do
ln -s /usr/local/bin work/virtualbox-2.2.2r19673/kBuild/bin/freebsd.amd64
with kBuild installed from ports vbox did finish building.

You should try to install misc/compat6.

- - Martin

Post by Artem Belevich
--Artem

- --

+-----------------------+-------------------------------+
| PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de |
| ICQ : 169139903 | Mail : miwi(at)FreeBSD.org |
+-----------------------+-------------------------------+
| Mess with the Best, Die like the Rest! |
+-----------------------+-------------------------------+

[Sergey V. Dyatko]

On Thu, 14 May 2009 21:12:37 +0200
Martin Wilke <***@FreeBSD.org> wrote:

MW> -----BEGIN PGP SIGNED MESSAGE-----
MW> Hash: SHA1
MW>
MW>
MW> Howdy Guys,
MW>
MW> After the announcement from Alexander Eichner about
MW> Virtualbox on FreeBSD, we started the work on a port
MW> for FreeBSD. Now we think that we solved the most
MW> problems and are ready for the first Call for Testing.
MW>
MW> Some notes before you can test the port:
MW> Make sure you are using RELENG_7 or higher. You have
MW> to use a fresh portstree with uptodate ports!! Please
MW> read carefully the pkg-messages.
MW>
MW> Some known issues / Troubleshooting:
MW> Sometimes the kernel on HEAD coredumps when loading
MW> or unloading the kernel module. A small workaround
MW> to prevent the crash is to not start X, mount proc,
MW> then load the kernel module and start X from the
MW> console. That helped me and some testers, maybe you
MW> too. :P AMD64 should be work in general, it builds
MW> and start. But not right tested at the moment. We
MW> want here also some feedback.

I can't start a virtual machine (current from May, 9).
screenshot: Loading Image...
After kldunload vboxdrv I got kernel panic:(
MW>
MW> Some Thanks:
MW> First of all we'd like to say many thanks to _ALL_
MW> vbox developers. Next people are Bernhard Froehlich
MW> (aka decke), Beat Gaetzi (beat@), Dennis Herrmann
MW> (dhn@), Pietro Cerutti (gahr@), myself (*gg*),
MW> and _ALL_ who helped and provided feedback.

I would like to join thanks, thank you for good job

MW> Happy Testing :-)
MW>
MW> Download:
MW>
MW> http://people.freebsd.org/~miwi/vbox/vboxport.tgz
MW>
MW> Wiki Page:
MW> http://wiki.freebsd.org/VirtualBox
MW>
MW> - Martin


--
wbr, tiger

[Andrei]

Post by Sergey V. Dyatko
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Howdy Guys,
After the announcement from Alexander Eichner about
Virtualbox on FreeBSD, we started the work on a port
for FreeBSD. Now we think that we solved the most
problems and are ready for the first Call for Testing.
Make sure you are using RELENG_7 or higher. You have
to use a fresh portstree with uptodate ports!! Please
read carefully the pkg-messages.
Sometimes the kernel on HEAD coredumps when loading
or unloading the kernel module. A small workaround
to prevent the crash is to not start X, mount proc,
then load the kernel module and start X from the
console. That helped me and some testers, maybe you
too. :P AMD64 should be work in general, it builds
and start. But not right tested at the moment. We
want here also some feedback.
First of all we'd like to say many thanks to _ALL_
vbox developers. Next people are Bernhard Froehlich
and _ALL_ who helped and provided feedback.
Happy Testing :-)
http://people.freebsd.org/~miwi/vbox/vboxport.tgz<http://people.freebsd.org/%7Emiwi/vbox/vboxport.tgz>
http://wiki.freebsd.org/VirtualBox
- Martin
- --
+-----------------------+-------------------------------+
| PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de |
| ICQ : 169139903 | Mail : miwi(at)FreeBSD.org |
+-----------------------+-------------------------------+
| Mess with the Best, Die like the Rest! |
+-----------------------+-------------------------------+
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (FreeBSD)
iEYEARECAAYFAkoMbSUACgkQdLJIhLHm/OnNnACeJsT7H9hW1J7CV70P3Ty+q0CA
kD8AoMLCPbltY999/8qO6fnaqv4UQ9QT
=LcoD
-----END PGP SIGNATURE-----
_______________________________________________
http://lists.freebsd.org/mailman/listinfo/freebsd-current

I downloaded http://people.freebsd.org/~miwi/vbox/vboxport.tgz
The compilation was successful. Started well.
But when I start a new machine with achlinux iso.
Sends me this message:
Loading Image...

uname-a:
FreeBSD workstation.bsd-es.org 7.2-STABLE FreeBSD 7.2-STABLE #0: Tue May 5
01:35:00 CEST 2009 ***@workstation.bsd-es.org:/usr/obj/usr/src/sys/ANX
amd64


Regards.

Andrey.

[Benoit Calvez]

Post by Sergey V. Dyatko
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Howdy Guys,
After the announcement from Alexander Eichner about
Virtualbox on FreeBSD, we started the work on a port
for FreeBSD. Now we think that we solved the most
problems and are ready for the first Call for Testing.
Make sure you are using RELENG_7 or higher. You have
to use a fresh portstree with uptodate ports!! Please
read carefully the pkg-messages.
Sometimes the kernel on HEAD coredumps when loading
or unloading the kernel module. A small workaround
to prevent the crash is to not start X, mount proc,
then load the kernel module and start X from the
console. That helped me and some testers, maybe you
too. :P AMD64 should be work in general, it builds
and start. But not right tested at the moment. We
want here also some feedback.
First of all we'd like to say many thanks to _ALL_
vbox developers. Next people are Bernhard Froehlich
and _ALL_ who helped and provided feedback.
Happy Testing :-)
http://people.freebsd.org/~miwi/vbox/vboxport.tgz<http://people.freebsd.org/%7Emiwi/vbox/vboxport.tgz>
http://wiki.freebsd.org/VirtualBox
- Martin
- --
+-----------------------+-------------------------------+
| PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de |
| ICQ : 169139903 | Mail : miwi(at)FreeBSD.org |
+-----------------------+-------------------------------+
| Mess with the Best, Die like the Rest! |
+-----------------------+-------------------------------+
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (FreeBSD)
iEYEARECAAYFAkoMbSUACgkQdLJIhLHm/OnNnACeJsT7H9hW1J7CV70P3Ty+q0CA
kD8AoMLCPbltY999/8qO6fnaqv4UQ9QT
=LcoD
-----END PGP SIGNATURE-----
_______________________________________________
http://lists.freebsd.org/mailman/listinfo/freebsd-current

I'm trying to build from amd64, but got the following error. Sorry but I
didn't look, and it's a fresh paste:
===> Configuring for virtualbox-2.2.2r19673
Checking for environment: Determined build machine: freebsd.amd64, target
machine: freebsd.amd64, OK.
Checking for kBuild: found, OK.
Checking for gcc: found version 4.2.1, OK.
Checking for as86: found version 0.16.17, OK.
Checking for bcc: found version 0.16.17, OK.
Checking for iasl: found version 20070320, OK.
Checking for xslt: found, OK.
Checking for pthread: found, OK.
Checking for libxml2: found version 2.7.3, OK.
Checking for libxslt: found version 1.1.24, OK.
Checking for libIDL: found version 0.8.13, OK.
Checking for zlib: found version 1.2.3, OK.
Checking for SDL: found version 1.2.13, OK.
Checking for X libraries: found, OK.
Checking for Xcursor: found, OK.
Checking for Xmu: found, OK.
Checking for Mesa / GLU: Xlib: extension "Generic Event Extension" missing
on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
found version 1.2, OK.
Checking for Qt4: found version 4.4.3, OK.
Checking for Qt4 devtools: found version 4.4.3, OK.
Checking for python support: found version 2.5.4, OK.

Successfully generated
'/usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/AutoConfig.kmk'
and '/usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/env.sh'.
Source '/usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/env.sh'
once before you start to build VBox:

source /usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/env.sh
kmk


+++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING
+++
Hardening is enabled which means that the VBox binaries will not run from
the binary directory. The binaries have to be installed suid root and some
more prerequisites have to be fulfilled which is normally done by
installing
the final package. For development, the hardening feature can be disabled
by specifying the --disable-hardening parameter. Please never disable that
feature for the final distribution!
+++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING
+++

Enjoy!
===> Building for virtualbox-2.2.2r19673
cd /usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673 && /bin/sh
env.sh && VBOX_LIBPATH_X11=/usr/local
/usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/kBuild/bin/freebsd.amd64/kmk
Config.kmk:1664:
/usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/GCCConfig.kmk:
No such file or directory
Config.kmk:3789:
/usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/revision.kmk:
No such file or directory
Fatal error 'kse_create() failed
' at line 469 in file /usr/src/lib/libpthread/thread/thr_kern.c (errno = 2)
*** Error code 1

[Martin Wilke]

Benoit,

can you please tell me which FreeBSD Version you use?

Post by Benoit Calvez
I'm trying to build from amd64, but got the following error. Sorry but I
===> Configuring for virtualbox-2.2.2r19673
Checking for environment: Determined build machine: freebsd.amd64, target
machine: freebsd.amd64, OK.
Checking for kBuild: found, OK.
Checking for gcc: found version 4.2.1, OK.
Checking for as86: found version 0.16.17, OK.
Checking for bcc: found version 0.16.17, OK.
Checking for iasl: found version 20070320, OK.
Checking for xslt: found, OK.
Checking for pthread: found, OK.
Checking for libxml2: found version 2.7.3, OK.
Checking for libxslt: found version 1.1.24, OK.
Checking for libIDL: found version 0.8.13, OK.
Checking for zlib: found version 1.2.3, OK.
Checking for SDL: found version 1.2.13, OK.
Checking for X libraries: found, OK.
Checking for Xcursor: found, OK.
Checking for Xmu: found, OK.
Checking for Mesa / GLU: Xlib: extension "Generic Event Extension" missing
on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
found version 1.2, OK.
Checking for Qt4: found version 4.4.3, OK.
Checking for Qt4 devtools: found version 4.4.3, OK.
Checking for python support: found version 2.5.4, OK.
Successfully generated
'/usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/AutoConfig.kmk'
and '/usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/env.sh'.
Source '/usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/env.sh'
source /usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/env.sh
kmk
+++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING
+++
Hardening is enabled which means that the VBox binaries will not run from
the binary directory. The binaries have to be installed suid root and some
more prerequisites have to be fulfilled which is normally done by
installing
the final package. For development, the hardening feature can be disabled
by specifying the --disable-hardening parameter. Please never disable that
feature for the final distribution!
+++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING
+++
Enjoy!
===> Building for virtualbox-2.2.2r19673
cd /usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673 && /bin/sh
env.sh && VBOX_LIBPATH_X11=/usr/local
/usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/kBuild/bin/freebsd.amd64/kmk
No such file or directory
No such file or directory
Fatal error 'kse_create() failed
' at line 469 in file /usr/src/lib/libpthread/thread/thr_kern.c (errno = 2)
*** Error code 1
--
Benoit C.
_______________________________________________
http://lists.freebsd.org/mailman/listinfo/freebsd-ports

- --

+-----------------------+-------------------------------+
| PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de |
| ICQ : 169139903 | Mail : miwi(at)FreeBSD.org |
+-----------------------+-------------------------------+
| Mess with the Best, Die like the Rest! |
+-----------------------+-------------------------------+

[Benoit Calvez]

Post by Benoit Calvez

Post by Sergey V. Dyatko
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Howdy Guys,
After the announcement from Alexander Eichner about
Virtualbox on FreeBSD, we started the work on a port
for FreeBSD. Now we think that we solved the most
problems and are ready for the first Call for Testing.
Make sure you are using RELENG_7 or higher. You have
to use a fresh portstree with uptodate ports!! Please
read carefully the pkg-messages.
Sometimes the kernel on HEAD coredumps when loading
or unloading the kernel module. A small workaround
to prevent the crash is to not start X, mount proc,
then load the kernel module and start X from the
console. That helped me and some testers, maybe you
too. :P AMD64 should be work in general, it builds
and start. But not right tested at the moment. We
want here also some feedback.
First of all we'd like to say many thanks to _ALL_
vbox developers. Next people are Bernhard Froehlich
and _ALL_ who helped and provided feedback.
Happy Testing :-)
http://people.freebsd.org/~miwi/vbox/vboxport.tgz<http://people.freebsd.org/%7Emiwi/vbox/vboxport.tgz>
http://wiki.freebsd.org/VirtualBox
- Martin
- --
+-----------------------+-------------------------------+
| PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de |
| ICQ : 169139903 | Mail : miwi(at)FreeBSD.org |
+-----------------------+-------------------------------+
| Mess with the Best, Die like the Rest! |
+-----------------------+-------------------------------+
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (FreeBSD)
iEYEARECAAYFAkoMbSUACgkQdLJIhLHm/OnNnACeJsT7H9hW1J7CV70P3Ty+q0CA
kD8AoMLCPbltY999/8qO6fnaqv4UQ9QT
=LcoD
-----END PGP SIGNATURE-----
_______________________________________________
http://lists.freebsd.org/mailman/listinfo/freebsd-current
"

I'm trying to build from amd64, but got the following error. Sorry but I
===> Configuring for virtualbox-2.2.2r19673
Checking for environment: Determined build machine: freebsd.amd64, target
machine: freebsd.amd64, OK.
Checking for kBuild: found, OK.
Checking for gcc: found version 4.2.1, OK.
Checking for as86: found version 0.16.17, OK.
Checking for bcc: found version 0.16.17, OK.
Checking for iasl: found version 20070320, OK.
Checking for xslt: found, OK.
Checking for pthread: found, OK.
Checking for libxml2: found version 2.7.3, OK.
Checking for libxslt: found version 1.1.24, OK.
Checking for libIDL: found version 0.8.13, OK.
Checking for zlib: found version 1.2.3, OK.
Checking for SDL: found version 1.2.13, OK.
Checking for X libraries: found, OK.
Checking for Xcursor: found, OK.
Checking for Xmu: found, OK.
Checking for Mesa / GLU: Xlib: extension "Generic Event Extension" missing
on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
found version 1.2, OK.
Checking for Qt4: found version 4.4.3, OK.
Checking for Qt4 devtools: found version 4.4.3, OK.
Checking for python support: found version 2.5.4, OK.
Successfully generated
'/usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/AutoConfig.kmk'
and '/usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/env.sh'.
Source '/usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/env.sh'
source /usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/env.sh
kmk
+++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING
+++
Hardening is enabled which means that the VBox binaries will not run from
the binary directory. The binaries have to be installed suid root and some
more prerequisites have to be fulfilled which is normally done by
installing
the final package. For development, the hardening feature can be disabled
by specifying the --disable-hardening parameter. Please never disable that
feature for the final distribution!
+++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING
+++
Enjoy!
===> Building for virtualbox-2.2.2r19673
cd /usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673 && /bin/sh
env.sh && VBOX_LIBPATH_X11=/usr/local
/usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/kBuild/bin/freebsd.amd64/kmk
No such file or directory
No such file or directory
Fatal error 'kse_create() failed
' at line 469 in file /usr/src/lib/libpthread/thread/thr_kern.c (errno = 2)
*** Error code 1
--
Benoit C.

I just tryed with the last tarball (
http://people.freebsd.org/~miwi/vbox/virtualbox_1.tgz) and it compiles fine.

the kernel module loads, and I'll try to boot an opensolaris in a few
moments.

Nice job everyone !

[Greg Byshenk]

Post by Benoit Calvez

Post by Benoit Calvez

Post by Martin Wilke
After the announcement from Alexander Eichner about
Virtualbox on FreeBSD, we started the work on a port
for FreeBSD. Now we think that we solved the most
problems and are ready for the first Call for Testing.
Make sure you are using RELENG_7 or higher. You have
to use a fresh portstree with uptodate ports!! Please
read carefully the pkg-messages.
Sometimes the kernel on HEAD coredumps when loading
or unloading the kernel module. A small workaround
to prevent the crash is to not start X, mount proc,
then load the kernel module and start X from the
console. That helped me and some testers, maybe you
too. :P AMD64 should be work in general, it builds
and start. But not right tested at the moment. We
want here also some feedback.
First of all we'd like to say many thanks to _ALL_
vbox developers. Next people are Bernhard Froehlich
and _ALL_ who helped and provided feedback.
Happy Testing :-)
http://people.freebsd.org/~miwi/vbox/vboxport.tgz<http://people.freebsd.org/%7Emiwi/vbox/vboxport.tgz>
http://wiki.freebsd.org/VirtualBox
- Martin

I'm trying to build from amd64, but got the following error. Sorry but I
[...]

I just tryed with the last tarball (
http://people.freebsd.org/~miwi/vbox/virtualbox_1.tgz) and it compiles fine.
the kernel module loads, and I'll try to boot an opensolaris in a few
moments.

I've just tried with virtualbox_1.tgz, and it builds without a problem, the
module installs without a problem, but attempting to start VirtualBox fails.
I get no error at all, VirtualBox just hangs.

If I attempt to run 'truss VirtualBox', I get the error:

Effective UID is not root (euid=1001 egid=1001 uid=1001 gid=1001) (rc=-10)
It may help to reinstall VirtualBox.

But checking shows that VirtualBox is SUID root:

$ ls -l /usr/local/lib/virtualbox/VirtualBox
-r-s--x--x 1 root vboxusers 21016 May 17 10:21 /usr/local/lib/virtualbox/VirtualBox

It seems that I can create a vm:

$ VBoxManage createvm --name test
VirtualBox Command Line Management Interface Version 2.2.51_OSE
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.

Virtual machine 'test' is created.
UUID: 9be28271-55c2-4299-b69a-266c58716db7
Settings file: '/home/gbyshenk/.VirtualBox/Machines/test/test.xml'
$ VirtualBox

$ ls -l /home/gbyshenk/.VirtualBox/Machines/test/test.xml
-rw------- 1 gbyshenk gbyshenk 2302 May 17 10:37 /home/gbyshenk/.VirtualBox/Machines/test/test.xml

But VirtualBox itself fails to start -- even if I run as root.

System is amd64, 7-STABLE as of 26-04-2009. Does it need to be more
recent...?

[David E. Thiel]

Post by Martin Wilke
After the announcement from Alexander Eichner about
Virtualbox on FreeBSD, we started the work on a port
for FreeBSD. Now we think that we solved the most
problems and are ready for the first Call for Testing.

Installed on 7.2-STABLE i386 and working fabulously. I'm amazed the port
progressed so quickly! Huge congrats and thank yous to the porters and
the vbox team. This is a big win for FreeBSD.

[Glen Barber]

Post by Sergey V. Dyatko
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Howdy Guys,
After the announcement from Alexander Eichner about
Virtualbox on FreeBSD, we started the work on a port
for FreeBSD. Now we think that we solved the most
problems and are ready for the first Call for Testing.

Fantastic! Can't wait to test it out.

(And "thank you!")

[Martin Wilke]

Ok

We uploaded a new tarball what should be fix the build on AMD64.

Small changelog:
- - devel/kbuild is now dependency
- - remove misc/compat6 support

Note:
Use devel/bcc instead of devel/dev86 what means
If you have devel/bcc installed please deinstall

http://people.freebsd.org/~miwi/vbox/virtualbox_1.tgz

Please give us feedback :P


- - Martin

- --

+-----------------------+-------------------------------+
| PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de |
| ICQ : 169139903 | Mail : miwi(at)FreeBSD.org |
+-----------------------+-------------------------------+
| Mess with the Best, Die like the Rest! |
+-----------------------+-------------------------------+

[Masahiko KIMOTO]

I'm testing on today's 8-CURRENT/i386.

When start the virtual machine, kernel got panic with;

May 15 19:31:23 eterna kernel: panic: clone_create() on cdevsw without minor numbers
May 15 19:31:23 eterna kernel: cpuid = 0
May 15 19:31:23 eterna kernel: KDB: enter: panic

So I'm looking up the source code of vboxdrv.ko but couldn't find . -name
'vboxdrv.*' or something like.

What should I check out then?

----------------------------------------------------------------------
Masahiko KIMOTO, Ph. D.
E-mail: ***@ohnolab.org URL: http://www.ohnolab.org/~kimoto

[Boris Samorodov]

Post by Masahiko KIMOTO
I'm testing on today's 8-CURRENT/i386.

So do I. But virtualbox works here. Until any VM got shutdown -- none
can be started.

Post by Masahiko KIMOTO
When start the virtual machine, kernel got panic with;
May 15 19:31:23 eterna kernel: panic: clone_create() on cdevsw without minor numbers
May 15 19:31:23 eterna kernel: cpuid = 0
May 15 19:31:23 eterna kernel: KDB: enter: panic
So I'm looking up the source code of vboxdrv.ko but couldn't find . -name
'vboxdrv.*' or something like.
What should I check out then?

Do you have all kernel modules from ports up to date with world/kernel?


WBR

[Masahiko KIMOTO]

Post by Boris Samorodov

Post by Masahiko KIMOTO
When start the virtual machine, kernel got panic with;
May 15 19:31:23 eterna kernel: panic: clone_create() on cdevsw without minor numbers
May 15 19:31:23 eterna kernel: cpuid = 0
May 15 19:31:23 eterna kernel: KDB: enter: panic
So I'm looking up the source code of vboxdrv.ko but couldn't find . -name
'vboxdrv.*' or something like.
What should I check out then?

Do you have all kernel modules from ports up to date with world/kernel?

Hmm,
Under /boot/kernel/ is up to date by make build/installkernel.
Under /boot/modules/, only vboxdrv.ko is in it, and is up to date.

----------------------------------------------------------------------
Masahiko KIMOTO, Ph. D.
E-mail: ***@ohnolab.org URL: http://www.ohnolab.org/~kimoto

[Sergey V. Dyatko]

В Fri, 15 May 2009 19:50:26 +0900 (JST)
Masahiko KIMOTO <***@ohnolab.org> пишет:

MK> I'm testing on today's 8-CURRENT/i386.
MK>
MK> When start the virtual machine, kernel got panic with;
MK>
MK> May 15 19:31:23 eterna kernel: panic: clone_create() on cdevsw
MK> without minor numbers May 15 19:31:23 eterna kernel: cpuid = 0
MK> May 15 19:31:23 eterna kernel: KDB: enter: panic
MK>
MK> So I'm looking up the source code of vboxdrv.ko but couldn't find .
MK> -name 'vboxdrv.*' or something like.
MK>
MK> What should I check out then?
MK>
/boot/modules/vboxdrv.ko ?

MK> ----------------------------------------------------------------------
MK> Masahiko KIMOTO, Ph. D.
MK> E-mail: ***@ohnolab.org URL:
MK> http://www.ohnolab.org/~kimoto



--
wbr, tiger

[Boris Samorodov]

Post by Martin Wilke
We uploaded a new tarball what should be fix the build on AMD64.
- devel/kbuild is now dependency
- remove misc/compat6 support
Use devel/bcc instead of devel/dev86 what means
If you have devel/bcc installed please deinstall
http://people.freebsd.org/~miwi/vbox/virtualbox_1.tgz
Please give us feedback :P

I've got an error at my 8-CURRENT tinderbox:
-----
====================<phase 7: make package>====================
===> Building package for virtualbox-2.2.2r19673
tar: lib/virtualbox/VBoxREM32.so: Cannot stat: No such file or directory
tar: lib/virtualbox/VBoxREM64.so: Cannot stat: No such file or directory
tar: Removing leading '/' from member names
tar: Error exit delayed from previous errors.
pkg_create: make_dist: tar command failed with code 256
-----

Seems that for 64 bit platform none of VBoxREM[32|64].so are
created.

BTW, those who are interested at the subject from mail lists
ports@, emulation@ and current@ already knows the great news.
May be it's time to move to one list, say, virtualization@?


WBR

[Martin Wilke]

Post by Boris Samorodov

Post by Martin Wilke
We uploaded a new tarball what should be fix the build on AMD64.
- devel/kbuild is now dependency
- remove misc/compat6 support
Use devel/bcc instead of devel/dev86 what means
If you have devel/bcc installed please deinstall
http://people.freebsd.org/~miwi/vbox/virtualbox_1.tgz
Please give us feedback :P

-----
====================<phase 7: make package>====================
===> Building package for virtualbox-2.2.2r19673
tar: lib/virtualbox/VBoxREM32.so: Cannot stat: No such file or directory
tar: lib/virtualbox/VBoxREM64.so: Cannot stat: No such file or directory
tar: Removing leading '/' from member names
tar: Error exit delayed from previous errors.
pkg_create: make_dist: tar command failed with code 256
-----
Seems that for 64 bit platform none of VBoxREM[32|64].so are
created.

Ups :(. Seems we was to fast. I'll fix that soon ;).

Post by Boris Samorodov
BTW, those who are interested at the subject from mail lists

Maybe :-). But for the moment it's a good place to deal with
vbox.

Post by Boris Samorodov
WBR
--
Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone & Internet SP
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve

- --

+-----------------------+-------------------------------+
| PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de |
| ICQ : 169139903 | Mail : miwi(at)FreeBSD.org |
+-----------------------+-------------------------------+
| Mess with the Best, Die like the Rest! |
+-----------------------+-------------------------------+

[Paul Wootton]

Post by Sergey V. Dyatko
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ok
We uploaded a new tarball what should be fix the build on AMD64.
- - devel/kbuild is now dependency
- - remove misc/compat6 support
Use devel/bcc instead of devel/dev86 what means
If you have devel/bcc installed please deinstall
http://people.freebsd.org/~miwi/vbox/virtualbox_1.tgz
Please give us feedback :P
- - Martin
- --
+-----------------------+-------------------------------+
| PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de |
| ICQ : 169139903 | Mail : miwi(at)FreeBSD.org |
+-----------------------+-------------------------------+
| Mess with the Best, Die like the Rest! |
+-----------------------+-------------------------------+
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (FreeBSD)
iEYEARECAAYFAkoNQCUACgkQdLJIhLHm/OmgeQCgptEW5FhkmB8huDhs5LL63PhI
+04AoONjytolxD892zcCnlv81MRLceEv
=UJL8
-----END PGP SIGNATURE-----
_______________________________________________
http://lists.freebsd.org/mailman/listinfo/freebsd-ports

Hi,
When compiling I get the following error

kBuild: Installing tstUtf8 =>
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/bin/testcase/tstUtf8
kBuild: Installing tstUuid =>
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/bin/testcase/tstUuid
kBuild: Installing tstVMStructGC =>
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/bin/tstVMStructGC
kBuild: Generating tstVMStructSize -
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/bin/tstVMStructGC:
1: Syntax error: "(" unexpected
kmk[2]: ***
[/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h]
Error 2
kmk[2]: *** Deleting file
`/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h'
kmk[2]: *** Waiting for unfinished jobs....
awk -f /usr/src/sys/conf/kmod_syms.awk
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/vboxdrv/vboxdrv.ko
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.def
| xargs -J% objcopy %
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/vboxdrv/vboxdrv.ko
awk: can't open file
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.def
source line number 10
kmk[2]: Leaving directory
`/root/vBox/virtualbox/work/virtualbox-2.2.2r19673'
kmk[2]: Entering directory
`/root/vBox/virtualbox/work/virtualbox-2.2.2r19673'
kmk[2]: *** Exiting with status 2
kmk[1]: *** [pass_binaries_this] Error 2
kmk[1]: Leaving directory
`/root/vBox/virtualbox/work/virtualbox-2.2.2r19673'
kmk: *** [pass_binaries_order] Error 2
*** Error code 2

Stop in /root/vBox/virtualbox.
demophon#


demophon# uname -a
FreeBSD demophon 8.0-CURRENT FreeBSD 8.0-CURRENT #10: Wed May 6
09:04:17 UTC 2009 ***@demophon:/usr/obj/usr/src/sys/DEMOPHON amd64

Any ideas?

Cheers
Paul

[Adam McDougall]

Post by Paul Wootton

Post by Sergey V. Dyatko
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ok
We uploaded a new tarball what should be fix the build on AMD64.
- - devel/kbuild is now dependency
- - remove misc/compat6 support
Use devel/bcc instead of devel/dev86 what means
If you have devel/bcc installed please deinstall
http://people.freebsd.org/~miwi/vbox/virtualbox_1.tgz
Please give us feedback :P
- - Martin
- --
+-----------------------+-------------------------------+
| PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de |
| ICQ : 169139903 | Mail : miwi(at)FreeBSD.org |
+-----------------------+-------------------------------+
| Mess with the Best, Die like the Rest! |
+-----------------------+-------------------------------+
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (FreeBSD)
iEYEARECAAYFAkoNQCUACgkQdLJIhLHm/OmgeQCgptEW5FhkmB8huDhs5LL63PhI
+04AoONjytolxD892zcCnlv81MRLceEv
=UJL8
-----END PGP SIGNATURE-----
_______________________________________________
http://lists.freebsd.org/mailman/listinfo/freebsd-ports

Hi,
When compiling I get the following error
kBuild: Installing tstUtf8 =>
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/bin/testcase/tstUtf8
kBuild: Installing tstUuid =>
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/bin/testcase/tstUuid
kBuild: Installing tstVMStructGC =>
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/bin/tstVMStructGC
kBuild: Generating tstVMStructSize -
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h
1: Syntax error: "(" unexpected
kmk[2]: ***
[/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h]
Error 2
kmk[2]: *** Deleting file
`/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h'
kmk[2]: *** Waiting for unfinished jobs....
awk -f /usr/src/sys/conf/kmod_syms.awk
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/vboxdrv/vboxdrv.ko
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.def
| xargs -J% objcopy %
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/vboxdrv/vboxdrv.ko
awk: can't open file
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.def
source line number 10
kmk[2]: Leaving directory
`/root/vBox/virtualbox/work/virtualbox-2.2.2r19673'
kmk[2]: Entering directory
`/root/vBox/virtualbox/work/virtualbox-2.2.2r19673'
kmk[2]: *** Exiting with status 2
kmk[1]: *** [pass_binaries_this] Error 2
kmk[1]: Leaving directory
`/root/vBox/virtualbox/work/virtualbox-2.2.2r19673'
kmk: *** [pass_binaries_order] Error 2
*** Error code 2
Stop in /root/vBox/virtualbox.
demophon#
demophon# uname -a
FreeBSD demophon 8.0-CURRENT FreeBSD 8.0-CURRENT #10: Wed May 6
Any ideas?
Cheers
Paul
_______________________________________________
http://lists.freebsd.org/mailman/listinfo/freebsd-ports

I am getting this error too from the latest test port on amd64 7-stable
and 8-current:

kBuild: Installing tstVMStructGC =>
/usr/home/mcdouga9/virtualbox/work/virtualbox-2.2.2r19852/out/freebsd.amd64/release/bin/tstVMStructGC
kBuild: Generating tstVMStructSize -
/usr/home/mcdouga9/virtualbox/work/virtualbox-2.2.2r19852/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h
/usr/home/mcdouga9/virtualbox/work/virtualbox-2.2.2r19852/out/freebsd.amd64/release/bin/tstVMStructGC:
1: Syntax error: "(" unexpected
kmk[2]: ***
[/usr/home/mcdouga9/virtualbox/work/virtualbox-2.2.2r19852/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h]
Error 2
kmk[2]: *** Deleting file
`/usr/home/mcdouga9/virtualbox/work/virtualbox-2.2.2r19852/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h'
kmk[2]: *** Waiting for unfinished jobs....
kmk[2]: Leaving directory
`/usr/home/mcdouga9/virtualbox/work/virtualbox-2.2.2r19852'
kmk[2]: Entering directory
`/usr/home/mcdouga9/virtualbox/work/virtualbox-2.2.2r19852'
kmk[2]: *** Exiting with status 2
kmk[1]: *** [pass_binaries_this] Error 2
kmk[1]: Leaving directory
`/usr/home/mcdouga9/virtualbox/work/virtualbox-2.2.2r19852'
kmk: *** [pass_binaries_order] Error 2
*** Error code 2


The OS builds are 1-3 days old (full kernel + world) and ports were up
to date. Help? Thanks.

[Adam McDougall]

I figured it out. I needed "options COMPAT_IA32"
in my kernel config.

Post by Paul Wootton
Hi,
When compiling I get the following error
kBuild: Installing tstUtf8 =>
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/bin/testcase/tstUtf8
kBuild: Installing tstUuid =>
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/bin/testcase/tstUuid
kBuild: Installing tstVMStructGC =>
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/bin/tstVMStructGC
kBuild: Generating tstVMStructSize -
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h
1: Syntax error: "(" unexpected
kmk[2]: ***
[/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h]
Error 2
kmk[2]: *** Deleting file
`/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h'
kmk[2]: *** Waiting for unfinished jobs....
awk -f /usr/src/sys/conf/kmod_syms.awk
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/vboxdrv/vboxdrv.ko
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.def
| xargs -J% objcopy %
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/vboxdrv/vboxdrv.ko
awk: can't open file
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.def
source line number 10
kmk[2]: Leaving directory
`/root/vBox/virtualbox/work/virtualbox-2.2.2r19673'
kmk[2]: Entering directory
`/root/vBox/virtualbox/work/virtualbox-2.2.2r19673'
kmk[2]: *** Exiting with status 2
kmk[1]: *** [pass_binaries_this] Error 2
kmk[1]: Leaving directory
`/root/vBox/virtualbox/work/virtualbox-2.2.2r19673'
kmk: *** [pass_binaries_order] Error 2
*** Error code 2
Stop in /root/vBox/virtualbox.
demophon#
demophon# uname -a
FreeBSD demophon 8.0-CURRENT FreeBSD 8.0-CURRENT #10: Wed May 6
Any ideas?
Cheers
Paul
_______________________________________________
http://lists.freebsd.org/mailman/listinfo/freebsd-ports

I am getting this error too from the latest test port on amd64 7-stable
and 8-current:

kBuild: Installing tstVMStructGC =>
/usr/home/mcdouga9/virtualbox/work/virtualbox-2.2.2r19852/out/freebsd.amd64/release/bin/tstVMStructGC
kBuild: Generating tstVMStructSize -
/usr/home/mcdouga9/virtualbox/work/virtualbox-2.2.2r19852/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h
/usr/home/mcdouga9/virtualbox/work/virtualbox-2.2.2r19852/out/freebsd.amd64/release/bin/tstVMStructGC:
1: Syntax error: "(" unexpected
kmk[2]: ***
[/usr/home/mcdouga9/virtualbox/work/virtualbox-2.2.2r19852/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h]
Error 2
kmk[2]: *** Deleting file
`/usr/home/mcdouga9/virtualbox/work/virtualbox-2.2.2r19852/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h'
kmk[2]: *** Waiting for unfinished jobs....
kmk[2]: Leaving directory
`/usr/home/mcdouga9/virtualbox/work/virtualbox-2.2.2r19852'
kmk[2]: Entering directory
`/usr/home/mcdouga9/virtualbox/work/virtualbox-2.2.2r19852'
kmk[2]: *** Exiting with status 2
kmk[1]: *** [pass_binaries_this] Error 2
kmk[1]: Leaving directory
`/usr/home/mcdouga9/virtualbox/work/virtualbox-2.2.2r19852'
kmk: *** [pass_binaries_order] Error 2
*** Error code 2


The OS builds are 1-3 days old (full kernel + world) and ports were up
to date. Help? Thanks.
_______________________________________________
freebsd-***@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-***@freebsd.org"

[Paul Wootton]

That makes perfect sense. On my machine, I commented out 32bit
compatibility as I figured I would not need it. This is the first time
it has caught me out...

Post by Adam McDougall
I figured it out. I needed "options COMPAT_IA32"
in my kernel config.

Post by Paul Wootton
Hi,
When compiling I get the following error
kBuild: Installing tstUtf8 =>
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/bin/testcase/tstUtf8
kBuild: Installing tstUuid =>
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/bin/testcase/tstUuid
kBuild: Installing tstVMStructGC =>
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/bin/tstVMStructGC
kBuild: Generating tstVMStructSize -
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h
1: Syntax error: "(" unexpected
kmk[2]: ***
[/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h]
Error 2
kmk[2]: *** Deleting file
`/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h'
kmk[2]: *** Waiting for unfinished jobs....
awk -f /usr/src/sys/conf/kmod_syms.awk
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/vboxdrv/vboxdrv.ko
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.def
| xargs -J% objcopy %
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/vboxdrv/vboxdrv.ko
awk: can't open file
/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.def
source line number 10
kmk[2]: Leaving directory
`/root/vBox/virtualbox/work/virtualbox-2.2.2r19673'
kmk[2]: Entering directory
`/root/vBox/virtualbox/work/virtualbox-2.2.2r19673'
kmk[2]: *** Exiting with status 2
kmk[1]: *** [pass_binaries_this] Error 2
kmk[1]: Leaving directory
`/root/vBox/virtualbox/work/virtualbox-2.2.2r19673'
kmk: *** [pass_binaries_order] Error 2
*** Error code 2
Stop in /root/vBox/virtualbox.
demophon#
demophon# uname -a
FreeBSD demophon 8.0-CURRENT FreeBSD 8.0-CURRENT #10: Wed May 6
Any ideas?
Cheers
Paul
_______________________________________________
http://lists.freebsd.org/mailman/listinfo/freebsd-ports

I am getting this error too from the latest test port on amd64 7-stable
kBuild: Installing tstVMStructGC =>
/usr/home/mcdouga9/virtualbox/work/virtualbox-2.2.2r19852/out/freebsd.amd64/release/bin/tstVMStructGC
kBuild: Generating tstVMStructSize -
/usr/home/mcdouga9/virtualbox/work/virtualbox-2.2.2r19852/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h
1: Syntax error: "(" unexpected
kmk[2]: ***
[/usr/home/mcdouga9/virtualbox/work/virtualbox-2.2.2r19852/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h]
Error 2
kmk[2]: *** Deleting file
`/usr/home/mcdouga9/virtualbox/work/virtualbox-2.2.2r19852/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h'
kmk[2]: *** Waiting for unfinished jobs....
kmk[2]: Leaving directory
`/usr/home/mcdouga9/virtualbox/work/virtualbox-2.2.2r19852'
kmk[2]: Entering directory
`/usr/home/mcdouga9/virtualbox/work/virtualbox-2.2.2r19852'
kmk[2]: *** Exiting with status 2
kmk[1]: *** [pass_binaries_this] Error 2
kmk[1]: Leaving directory
`/usr/home/mcdouga9/virtualbox/work/virtualbox-2.2.2r19852'
kmk: *** [pass_binaries_order] Error 2
*** Error code 2
The OS builds are 1-3 days old (full kernel + world) and ports were up
to date. Help? Thanks.
_______________________________________________
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
_______________________________________________
http://lists.freebsd.org/mailman/listinfo/freebsd-ports

-----------------------------------------------------------------------------------
Fletcher Moorland Limited is a company registered in England and Wales.
Registration number: 2984467.
Registered office: Elenora Street, Stoke on Trent, Staffordshire, ST4 1QG.
VAT Registration number: 478730606
Telephone: [phone] | Fax: [phone] | http://www.fletchermoorland.co.uk

[Glen Barber]

Good evening everyone.

Earlier today, I finished a VBox build on a fresh system.

After the build succeeded, I 'kldload /boot/modules/vboxdrv.ko' which
caused a panic. The machine runs a GENERIC kernel with KDB and
KDB_UNATTENDED added -- no other changes.

-- The machine --
FreeBSD orion 7.2-STABLE FreeBSD 7.2-STABLE #1 r193481: Sat Jun 6
10:22:25 EDT 2009 ***@orion:/usr/obj/usr/src/sys/ORION i386

-- Snippet from 'dmesg' --

FreeBSD 7.2-STABLE #0 r193481: Fri Jun 5 01:55:06 EDT 2009
***@orion:/usr/obj/usr/src/sys/ORION
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz (2217.69-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x6fd Stepping = 13
Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
Features2=0xe39d<SSE3,DTES64,MON,DS_CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM>
AMD Features=0x20100000<NX,LM>
AMD Features2=0x1<LAHF>
Cores per package: 2
real memory = 2128793600 (2030 MB)
avail memory = 2073436160 (1977 MB)
ACPI APIC Table: <INTEL DG33FB >
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 1
ioapic0: Changing APIC ID to 2



-- The panic --
orion# kgdb kernel.debug /var/crash/vmcore.0
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd"...

Unread portion of the kernel message buffer:

!!Assertion Failed!!
Expression: cMillies != RT_INDEFINITE_WAIT
Location : /usr/home/gbarber/virtualbox/virtualbox/work/virtualbox-2.2.2r19980/
src/VBox/Runtime/r0drv/freebsd/semevent-r0drv-freebsd.c(212) rtSemEventWait


Fatal trap 3: breakpoint instruction fault while in kernel mode
cpuid = 1; apic id = 01
instruction pointer = 0x20:0xc5e180be
stack pointer = 0x28:0xe7a73c08
frame pointer = 0x28:0xe7a73c34
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = IOPL = 0
current process = 1838 (TIMER)
trap number = 3
panic: breakpoint instruction fault
cpuid = 1
Uptime: 6h58m4s
Physical memory: 2017 MB
Dumping 180 MB: 165 149 133 117 101 85 69 53 37 21 5

Reading symbols from /boot/kernel/coretemp.ko...Reading symbols from /boot/kerne
l/coretemp.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/coretemp.ko
Reading symbols from /boot/kernel/acpi.ko...Reading symbols from /boot/kernel/ac
pi.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/acpi.ko
Reading symbols from /boot/modules/vboxdrv.ko...done.
Loaded symbols for /boot/modules/vboxdrv.ko
#0 doadump () at pcpu.h:196
196 __asm __volatile("movl %%fs:0,%0" : "=r" (td));
(kgdb) bt
#0 doadump () at pcpu.h:196
#1 0xc07e45a7 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418
#2 0xc07e48b2 in panic (fmt=Variable "fmt" is not available.
) at /usr/src/sys/kern/kern_shutdown.c:574
#3 0xc0ae6d83 in trap_fatal (frame=0xe7a73bc8, eva=0)
at /usr/src/sys/i386/i386/trap.c:939
#4 0xc0ae7bdc in trap (frame=0xe7a73bc8) at /usr/src/sys/i386/i386/trap.c:726
#5 0xc0acc05b in calltrap () at /usr/src/sys/i386/i386/exception.s:159
#6 0xc5e180be in rtSemEventWait (EventSem=0xc5d2a110, cMillies=4294967295,
fInterruptible=false)
at /usr/home/gbarber/virtualbox/virtualbox/work/virtualbox-2.2.2r19980/src/V
Box/Runtime/r0drv/freebsd/semevent-r0drv-freebsd.c:212
#7 0xc5e181b0 in RTSemEventWait (EventSem=0xc5d2a110, cMillies=4294967295)
at /usr/home/gbarber/virtualbox/virtualbox/work/virtualbox-2.2.2r19980/src/V
Box/Runtime/r0drv/freebsd/semevent-r0drv-freebsd.c:240
#8 0xc5e157f1 in rtTimerThread (Thread=0xc5d2b990, pvUser=0xc5d2be90)
at /usr/home/gbarber/virtualbox/virtualbox/work/virtualbox-2.2.2r19980/src/V
Box/Runtime/generic/timer-generic.cpp:238
#9 0xc5e1a6c0 in rtThreadMain (pThread=0xc5d2b990, NativeThread=3316025600,
pszThreadName=0xc5d2b9d0 "TIMER")
at /usr/home/gbarber/virtualbox/virtualbox/work/virtualbox-2.2.2r19980/src/V
Box/Runtime/common/misc/thread.cpp:635
#10 0xc5e26ee7 in rtThreadNativeMain (pvThreadInt=0xc5d2b990)
at /usr/home/gbarber/virtualbox/virtualbox/work/virtualbox-2.2.2r19980/src/V
Box/Runtime/r0drv/freebsd/thread2-r0drv-freebsd.c:112
---Type <return> to continue, or q <return> to quit---
#11 0xc07bdbc9 in fork_exit (callout=0xc5e26ec0 <rtThreadNativeMain>,
arg=0xc5d2b990, frame=0xe7a73d38) at /usr/src/sys/kern/kern_fork.c:811
#12 0xc0acc0d0 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:264
(kgdb)


Any thoughts? If needed, I will test patches.

[Guy Brand]

Martin Wilke (***@freebsd.org) on 15/05/2009 at 12:12 wrote:

Hello

Post by Martin Wilke
We uploaded a new tarball what should be fix the build on AMD64.
- devel/kbuild is now dependency
- remove misc/compat6 support
Use devel/bcc instead of devel/dev86 what means
If you have devel/bcc installed please deinstall
http://people.freebsd.org/~miwi/vbox/virtualbox_1.tgz
Please give us feedback :P

I hit the "Failed to load VMMR0.r0 (VERR_SYMBOL_VALUE_TOO_BIG)" issue
when trying to start any created VM.

FreeBSD 8.0-CURRENT #12: Wed May 13 11:22:30 CEST 2009 amd64
virtualbox-2.2.2r19673 (svn revision 373 of the port)

[Ion-Mihai Tetcu]

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

On Fri, 15 May 2009 12:12:54 +0200

Post by Sergey V. Dyatko
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ok
We uploaded a new tarball what should be fix the build on AMD64.
- - devel/kbuild is now dependency
- - remove misc/compat6 support
Use devel/bcc instead of devel/dev86 what means
If you have devel/bcc installed please deinstall
http://people.freebsd.org/~miwi/vbox/virtualbox_1.tgz
Please give us feedback :P

Seems you need to be root to build it and it will fail on tindy/pointy
because of touching the fs outside WRKDIR before install.:

===> Building for virtualbox-2.2.2r19673
cd /home/itetcu/wrk/usr/home/itetcu/tmp/virtualbox/work/virtualbox-2.2.2r19673 && /bin/sh env.sh && VBOX_LIBPATH_X11=/usr/local /usr/local/bin/kmk
Makefile.kmk:23: /usr/local/share/kBuild/subheader.kmk: Permission denied
Makefile.kmk:809: /usr/local/share/kBuild/subfooter.kmk: Permission denied
kmk: stat: /usr/local/share/kBuild/subfooter.kmk: Permission denied
kmk: stat: /usr/local/share/kBuild/subheader.kmk: Permission denied
kmk: *** No rule to make target `/usr/local/share/kBuild/subfooter.kmk'. Stop.
*** Error code 2



- --
IOnut - Un^d^dregistered ;) FreeBSD "user"
"Intellectual Property" is nowhere near as valuable as "Intellect"
FreeBSD committer -> ***@FreeBSD.org, PGP Key ID 057E9F8B493A297B

[Alberto Villa]

Post by Martin Wilke
Happy Testing :-)

thank you for your great work!

anyway i can't get to start a virtual machine. if i select a bootable iso (ot
doesn't show up in the file selection dialog, i have to write its name) to
boot from (it doesn't find my dvd device) the virtual machine starts saying
"running", but neither the session information dialog nor the log show any
activity. also tried using VBoxSDL

[Alberto Villa]

Post by Alberto Villa
anyway i can't get to start a virtual machine. if i select a bootable iso
(ot doesn't show up in the file selection dialog, i have to write its name)
to boot from (it doesn't find my dvd device) the virtual machine starts
saying "running", but neither the session information dialog nor the log
show any activity. also tried using VBoxSDL

tested again with virtualbox_2 on 7-stable, built right after the kernel:
loading the module results in a kernel panic
attached the `crashinfo` output

[Gorbatovsky Dmitry]

Thanks for grate work!

I install on VirtualBox FreeBSD 7.1, Ubuntu, Windows 7
and it work fine.

%uname -a
FreeBSD user 7.2-RELEASE FreeBSD 7.2-RELEASE #1: Thu May 7 15:46:13 MSD
2009 ***@user:/usr/obj/usr/src/sys/GENERIC i386

Dmitry.

[Renato Botelho]

Post by Sergey V. Dyatko
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Howdy Guys,
After the announcement from Alexander Eichner about
Virtualbox on FreeBSD, we started the work on a port
for FreeBSD. Now we think that we solved the most
problems and are ready for the first Call for Testing.
Make sure you are using RELENG_7 or higher. You have
to use a fresh portstree with uptodate ports!! Please
read carefully the pkg-messages.
Sometimes the kernel on HEAD coredumps when loading
or unloading the kernel module. A small workaround
to prevent the crash is to not start X, mount proc,
then load the kernel module and start X from the
console. That helped me and some testers, maybe you
too. :P AMD64 should be work in general, it builds
and start. But not right tested at the moment. We
want here also some feedback.
First of all we'd like to say many thanks to _ALL_
vbox developers. Next people are Bernhard Froehlich
and _ALL_ who helped and provided feedback.
Happy Testing :-)
 http://people.freebsd.org/~miwi/vbox/vboxport.tgz
 http://wiki.freebsd.org/VirtualBox

Hello Martin

I've built it on i386/CURRENT r191522, but I couldn't load the
module, when i try, i got:

KLD vboxdrv.ko: depends on kernel - not available
kldload: can't load vboxdrv: File exists

It says file exists, but the module is not loaded

***@botelhor:/home/garga# kldstat
Id Refs Address Size Name
1 18 0xc0400000 b584bc kernel
2 1 0xc0f59000 809c snd_via8233.ko
3 2 0xc0f62000 4a438 sound.ko
4 1 0xc46af000 8000 linprocfs.ko
5 1 0xc46c8000 24000 linux.ko

Any idea?

[Gustau Pérez]

Post by Renato Botelho

Post by Sergey V. Dyatko
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Howdy Guys,
After the announcement from Alexander Eichner about
Virtualbox on FreeBSD, we started the work on a port
for FreeBSD. Now we think that we solved the most
problems and are ready for the first Call for Testing.
Make sure you are using RELENG_7 or higher. You have
to use a fresh portstree with uptodate ports!! Please
read carefully the pkg-messages.
Sometimes the kernel on HEAD coredumps when loading
or unloading the kernel module. A small workaround
to prevent the crash is to not start X, mount proc,
then load the kernel module and start X from the
console. That helped me and some testers, maybe you
too. :P AMD64 should be work in general, it builds
and start. But not right tested at the moment. We
want here also some feedback.
First of all we'd like to say many thanks to _ALL_
vbox developers. Next people are Bernhard Froehlich
and _ALL_ who helped and provided feedback.
Happy Testing :-)
http://people.freebsd.org/~miwi/vbox/vboxport.tgz
http://wiki.freebsd.org/VirtualBox

Hello Martin
I've built it on i386/CURRENT r191522, but I couldn't load the
KLD vboxdrv.ko: depends on kernel - not available
kldload: can't load vboxdrv: File exists
It says file exists, but the module is not loaded
Id Refs Address Size Name
1 18 0xc0400000 b584bc kernel
2 1 0xc0f59000 809c snd_via8233.ko
3 2 0xc0f62000 4a438 sound.ko
4 1 0xc46af000 8000 linprocfs.ko
5 1 0xc46c8000 24000 linux.ko
Any idea?

It seems to me you csup'ed your sources but you are still using the
old kernel. Try make buildkernell && make installkernel and then try
loading the module.

Gus

PS : as a advice, I would do the installworld with
KODIR=/boot/test && nextboot -k test. If i works, you can reinstall
again the kernel as your default kernel .

- --
PGP KEY : http://www-entel.upc.edu/gus/gus.asc

[Boris Samorodov]

Post by Renato Botelho
I've built it on i386/CURRENT r191522, but I couldn't load the
KLD vboxdrv.ko: depends on kernel - not available

I didn't see that message.

Post by Renato Botelho
kldload: can't load vboxdrv: File exists

While this is familiar for me. I've got it when build virtualbox
with newer kernel sources (it so happened that I csuped src but
had no time to rebuild/reinstall) than the installed kernel.

Post by Renato Botelho
It says file exists, but the module is not loaded
Id Refs Address Size Name
1 18 0xc0400000 b584bc kernel
2 1 0xc0f59000 809c snd_via8233.ko
3 2 0xc0f62000 4a438 sound.ko
4 1 0xc46af000 8000 linprocfs.ko
5 1 0xc46c8000 24000 linux.ko
Any idea?

WBR

[Rink Springer]

Post by Renato Botelho
I've built it on i386/CURRENT r191522, but I couldn't load the
KLD vboxdrv.ko: depends on kernel - not available
kldload: can't load vboxdrv: File exists

This generally means your kernel sources and binary are not in sync.
Just rebuild and reinstall your kernel and all modules and you will be
fine.

Regards,

[Sam Fourman Jr.]

Post by Renato Botelho
I've built it on i386/CURRENT r191522, but I couldn't load the
KLD vboxdrv.ko: depends on kernel - not available
kldload: can't load vboxdrv: File exists
It says file exists, but the module is not loaded
Id Refs Address    Size     Name
 1   18 0xc0400000 b584bc   kernel
 2    1 0xc0f59000 809c     snd_via8233.ko
 3    2 0xc0f62000 4a438    sound.ko
 4    1 0xc46af000 8000     linprocfs.ko
 5    1 0xc46c8000 24000    linux.ko
Any idea?

it Probably means that you are running a kernel that is not in sync
with the src in your /usr/src

do csup -g -L 2 -h cvsup15.freebsd.org /usr/share
examples/cvsup/standard-supfile

then build your kernel && install your kernel

uninstall the Virtualbox port and rebuild it. all will work

Sam Fourman Jr.

[Alexander Best]

hi there,

this panic has been reported beforehand. i'm also experiencing it when
powering on a new image:

panic: clone_create() on cdevsw without minor numbers
cpuid = 0


here's a bt:

#0 doadump () at pcpu.h:246
#1 0xc05ac869 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:420
#2 0xc05acb4f in panic (fmt=Variable "fmt" is not available.
) at /usr/src/sys/kern/kern_shutdown.c:576
#3 0xc0575efd in clone_create (cdp=0xc83fbe80, csw=0xc83fa5c0, up=0xe81a1870,
dp=0xe81a1900, extra=0) at /usr/src/sys/kern/kern_conf.c:935
#4 0xc83e13a1 in VBoxDrvFreeBSDClone () from /boot/modules/vboxdrv.ko
#5 0xc053ffbf in devfs_lookup (ap=0xe81a19b0) at
/usr/src/sys/fs/devfs/devfs_vnops.c:796
#6 0xc074ad9a in VOP_LOOKUP_APV (vop=0xc07f30e0, a=0xe81a19b0) at
vnode_if.c:123
#7 0xc062514e in lookup (ndp=0xe81a1bac) at vnode_if.h:54
#8 0xc0625daa in namei (ndp=0xe81a1bac) at /usr/src/sys/kern/vfs_lookup.c:256
#9 0xc063b169 in vn_open_cred (ndp=0xe81a1bac, flagp=0xe81a1c60, cmode=0,
cred=0xc8885000, fp=0xc82762d8) at /usr/src/sys/kern/vfs_vnops.c:189
#10 0xc063b408 in vn_open (ndp=0xe81a1bac, flagp=0xe81a1c60, cmode=0,
fp=0xc82762d8) at /usr/src/sys/kern/vfs_vnops.c:96
#11 0xc063a424 in kern_openat (td=0xc7aebb40, fd=-100, path=0xbfbfd5af
<Address 0xbfbfd5af out of bounds>, pathseg=UIO_USERSPACE, flags=3, mode=0) at
/usr/src/sys/kern/vfs_syscalls.c:1091
#12 0xc063a8e8 in kern_open (td=0xc7aebb40, path=0xbfbfd5af <Address
0xbfbfd5af out of bounds>, pathseg=UIO_USERSPACE, flags=2, mode=0) at
/usr/src/sys/kern/vfs_syscalls.c:1045
#13 0xc063a91a in open (td=0xc7aebb40, uap=0xe81a1cf8) at
/usr/src/sys/kern/vfs_syscalls.c:1021
#14 0xc073792b in syscall (frame=0xe81a1d38) at
/usr/src/sys/i386/i386/trap.c:1073
#15 0xc071d170 in Xint0x80_syscall () at
/usr/src/sys/i386/i386/exception.s:261
#16 0x00000033 in ?? ()
Previous frame inner to this frame (corrupt stack?)

vboxdrv.ko got loaded before starting X (using /boot/loader.conf). all ports
are up-to-date and the running kernel is in sync with the kernel sources.

right now i'm running r192089 (CURRENT) and virtualbox-2.2.2r19673.

cheers.

[Hyogeol Lee]

Post by Martin Wilke
Ok
We uploaded a new tarball what should be fix the build on AMD64.
- - devel/kbuild is now dependency
- - remove misc/compat6 support
Use devel/bcc instead of devel/dev86 what means
If you have devel/bcc installed please deinstall
http://people.freebsd.org/~miwi/vbox/virtualbox_1.tgz

<http://people.freebsd.org/%7Emiwi/vbox/virtualbox_1.tgz>

Post by Martin Wilke
Please give us feedback :P
- - Martin
- --
+-----------------------+-------------------------------+
|/ PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de |
/|/ ICQ : 169139903 | Mail : miwi(at)FreeBSD.org |
/+-----------------------+-------------------------------+
|/ Mess with the Best, Die like the Rest! |
/+-----------------------+-------------------------------+

Hi,

Great works!

Build success, but error on virtual machine running.

In with amd64/-current, I got


Failed to load VMMR0.r0 (VERR_SYMBOL_VALUE_TOO_BIG).
Unknown error creating VM (VERR_SYMBOL_VALUE_TOO_BIG).

Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
Console
Interface:
IConsole {a7f17a42-5b64-488d-977b-4b2c639ada27}


at first time and I got


Kernel driver not installed (rc=-1908)

Make sure the kernel module has been loaded successfully.

Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
Machine
Interface:
IMachine {4d1df26d-d9c1-4c7e-b689-15e85ecf8ffc}


at after.

At that point, VirtualBox dumped core, but there is no good

information. This is backtrace,


GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and
you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for
details.
This GDB was configured as "amd64-marcel-freebsd"...
(gdb) core VirtualBox.core
Core was generated by `VirtualBox'.
Program terminated with signal 6, Aborted.
Reading symbols from /lib/libthr.so.3...done.
Loaded symbols for /lib/libthr.so.3
Reading symbols from /usr/lib/libstdc++.so.6...done.
Loaded symbols for /usr/lib/libstdc++.so.6
Reading symbols from /lib/libm.so.5...done.
Loaded symbols for /lib/libm.so.5
Reading symbols from /lib/libgcc_s.so.1...done.
Loaded symbols for /lib/libgcc_s.so.1
Reading symbols from /lib/libc.so.7...done.
Loaded symbols for /lib/libc.so.7
Reading symbols from /usr/local/lib/virtualbox/VirtualBox.so...done.
Loaded symbols for /usr/local/lib/virtualbox/VirtualBox.so
Reading symbols from /usr/local/lib/virtualbox/VBoxDDU.so...done.
Loaded symbols for /usr/local/lib/virtualbox/VBoxDDU.so
Reading symbols from /usr/local/lib/virtualbox/VBoxKeyboard.so...done.
Loaded symbols for /usr/local/lib/virtualbox/VBoxKeyboard.so
Reading symbols from /usr/local/lib/virtualbox/VBoxRT.so...done.
Loaded symbols for /usr/local/lib/virtualbox/VBoxRT.so
Reading symbols from /usr/local/lib/virtualbox/VBoxREM.so...done.
Loaded symbols for /usr/local/lib/virtualbox/VBoxREM.so
Reading symbols from /usr/local/lib/virtualbox/VBoxVMM.so...done.
Loaded symbols for /usr/local/lib/virtualbox/VBoxVMM.so
Reading symbols from /usr/local/lib/libXcursor.so.1...done.
Loaded symbols for /usr/local/lib/libXcursor.so.1
Reading symbols from /usr/local/lib/libXext.so.6...done.
Loaded symbols for /usr/local/lib/libXext.so.6
Reading symbols from /usr/local/lib/libX11.so.6...done.
Loaded symbols for /usr/local/lib/libX11.so.6
Reading symbols from /usr/local/lib/virtualbox/VBoxXPCOM.so...done.
Loaded symbols for /usr/local/lib/virtualbox/VBoxXPCOM.so
Reading symbols from /usr/local/lib/qt4/libQtCore.so.4...done.
Loaded symbols for /usr/local/lib/qt4/libQtCore.so.4
Reading symbols from /usr/local/lib/qt4/libQtGui.so.4...done.
Loaded symbols for /usr/local/lib/qt4/libQtGui.so.4
Reading symbols from /usr/local/lib/qt4/libQtNetwork.so.4...done.
Loaded symbols for /usr/local/lib/qt4/libQtNetwork.so.4
Reading symbols from /usr/local/lib/libSDL-1.2.so.11...done.
Loaded symbols for /usr/local/lib/libSDL-1.2.so.11
Reading symbols from /usr/local/lib/libiconv.so.3...done.
Loaded symbols for /usr/local/lib/libiconv.so.3
Reading symbols from /usr/lib/librt.so.1...done.
Loaded symbols for /usr/lib/librt.so.1
Reading symbols from /lib/libz.so.4...done.
Loaded symbols for /lib/libz.so.4
Reading symbols from /usr/local/lib/libXrender.so.1...done.
Loaded symbols for /usr/local/lib/libXrender.so.1
Reading symbols from /usr/local/lib/libXfixes.so.3...done.
Loaded symbols for /usr/local/lib/libXfixes.so.3
Reading symbols from /usr/local/lib/libxcb.so.2...done.
Loaded symbols for /usr/local/lib/libxcb.so.2
Reading symbols from /usr/local/lib/libXdmcp.so.6...done.
Loaded symbols for /usr/local/lib/libXdmcp.so.6
Reading symbols from /usr/lib/librpcsvc.so.4...done.
Loaded symbols for /usr/lib/librpcsvc.so.4
Reading symbols from /usr/local/lib/libXau.so.6...done.
Loaded symbols for /usr/local/lib/libXau.so.6
Reading symbols from /usr/local/lib/libgthread-2.0.so.0...done.
Loaded symbols for /usr/local/lib/libgthread-2.0.so.0
Reading symbols from /usr/local/lib/libglib-2.0.so.0...done.
Loaded symbols for /usr/local/lib/libglib-2.0.so.0
Reading symbols from /usr/local/lib/libpng.so.5...done.
Loaded symbols for /usr/local/lib/libpng.so.5
Reading symbols from /usr/local/lib/libSM.so.6...done.
Loaded symbols for /usr/local/lib/libSM.so.6
Reading symbols from /usr/local/lib/libICE.so.6...done.
Loaded symbols for /usr/local/lib/libICE.so.6
Reading symbols from /usr/local/lib/libXi.so.6...done.
Loaded symbols for /usr/local/lib/libXi.so.6
Reading symbols from /usr/local/lib/libXrandr.so.2...done.
Loaded symbols for /usr/local/lib/libXrandr.so.2
Reading symbols from /usr/local/lib/libfreetype.so.9...done.
Loaded symbols for /usr/local/lib/libfreetype.so.9
Reading symbols from /usr/local/lib/libfontconfig.so.1...done.
Loaded symbols for /usr/local/lib/libfontconfig.so.1
Reading symbols from /usr/local/lib/libaa.so.1...done.
Loaded symbols for /usr/local/lib/libaa.so.1
Reading symbols from /usr/lib/libusbhid.so.3...done.
Loaded symbols for /usr/lib/libusbhid.so.3
Reading symbols from /usr/local/lib/libintl.so.8...done.
Loaded symbols for /usr/local/lib/libintl.so.8
Reading symbols from /usr/local/lib/libpcre.so.0...done.
Loaded symbols for /usr/local/lib/libpcre.so.0
Reading symbols from /usr/local/lib/libexpat.so.6...done.
Loaded symbols for /usr/local/lib/libexpat.so.6
Reading symbols from /lib/libncurses.so.7...done.
Loaded symbols for /lib/libncurses.so.7
Reading symbols from /usr/local/lib/libXinerama.so.1...done.
Loaded symbols for /usr/local/lib/libXinerama.so.1
Reading symbols from /usr/local/lib/libgobject-2.0.so.0...done.
Loaded symbols for /usr/local/lib/libgobject-2.0.so.0
Reading symbols from /usr/local/lib/libgconf-2.so.4...done.
Loaded symbols for /usr/local/lib/libgconf-2.so.4
Reading symbols from /usr/local/lib/libgmodule-2.0.so.0...done.
Loaded symbols for /usr/local/lib/libgmodule-2.0.so.0
Reading symbols from /usr/local/lib/libORBit-2.so.0...done.
Loaded symbols for /usr/local/lib/libORBit-2.so.0
Reading symbols from /usr/local/lib/libdbus-glib-1.so.2...done.
Loaded symbols for /usr/local/lib/libdbus-glib-1.so.2
Reading symbols from /usr/local/lib/libdbus-1.so.3...done.
Loaded symbols for /usr/local/lib/libdbus-1.so.3
Reading symbols from /libexec/ld-elf.so.1...done.
Loaded symbols for /libexec/ld-elf.so.1
#0 0x0000000800c6d03c in kill () from /lib/libc.so.7
[New Thread 800e021c0 (LWP 100290)]
(gdb) bt
#0 0x0000000800c6d03c in kill () from /lib/libc.so.7
#1 0x0000000800c6c033 in abort () from /lib/libc.so.7
#2 0x00000008023114d6 in qt_message_output ()
from /usr/local/lib/qt4/libQtCore.so.4
#3 0x00000008023115ed in qFatal () from /usr/local/lib/qt4/libQtCore.so.4
#4 0x0000000800fb5419 in TrustedError (pszWhere=Variable "pszWhere"
is not available.
)
at
/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19673/src/VBox/Frontends/VirtualBox/src/main.cpp:639
#5 0x0000000000401817 in supR3HardenedStaticFatalMsgV (
pszWhere=0x402eb9 "suplibOsInit", enmWhat=kSupInitOp_Driver,
rc=-1908,
pszMsgFmt=0x402e9d "Kernel driver not installed", va=0x7fffffffd4f0)
at
/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19673/src/VBox/HostDrivers/Support/SUPR3HardenedMain.cpp:465
#6 0x00000000004018ce in supR3HardenedStaticFatalMsg
(pszWhere=Variable "pszWhere" is not available.
)
at
/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19673/src/VBox/HostDrivers/Support/SUPR3HardenedMain.cpp:484
#7 0x0000000000401cfe in SUPR3HardenedMain (
pszProgName=0x402e53 "VirtualBox", fFlags=Variable "fFlags" is not
available.
)
at
/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19673/src/VBox/HostDrivers/Support/SUPR3HardenedMain.cpp:573
#8 0x0000000000400fee in _start ()
#9 0x0000000800532000 in ?? ()
#10 0x0000000000000000 in ?? ()
- ---Type <return> to continue, or q <return> to quit---



Best Regards,
- ----
Hyogeol Lee
***@gmail.com

[Tim Bishop]

Hi Martin,

Post by Martin Wilke
After the announcement from Alexander Eichner about
Virtualbox on FreeBSD, we started the work on a port
for FreeBSD. Now we think that we solved the most
problems and are ready for the first Call for Testing.

Is the VRDP stuff meant to work? When following these instructions it
just appears athat it doesn't start it up (nothing is listening on
3389):

http://www.virtualbox.org/manual/UserManual.html#vboxheadless

Thanks for your work making VirtualBox available to us!

Tim.

[Tim Bishop]

Post by Tim Bishop

Post by Martin Wilke
After the announcement from Alexander Eichner about
Virtualbox on FreeBSD, we started the work on a port
for FreeBSD. Now we think that we solved the most
problems and are ready for the first Call for Testing.

Is the VRDP stuff meant to work? When following these instructions it
just appears athat it doesn't start it up (nothing is listening on
http://www.virtualbox.org/manual/UserManual.html#vboxheadless

To answer my own question, VRDP isn't available on the Open Source
Edition of VirtualBox. Differences can be found here:

http://www.virtualbox.org/wiki/Editions

Tim.

[Андрей]

Post by Martin Wilke
We uploaded a new tarball what should be fix the build on AMD64.
- - devel/kbuild is now dependency
- - remove misc/compat6 support
Use devel/bcc instead of devel/dev86 what means
If you have devel/bcc installed please deinstall
http://people.freebsd.org/~miwi/vbox/virtualbox_1.tgz

<http://people.freebsd.org/%7Emiwi/vbox/virtualbox_1.tgz>

Post by Martin Wilke
Please give us feedback :P

I've got an make error at my 8-CURRENT amd64 Wed Apr 29 20:02:37 MSD 2009


kBuild: Compiling RuntimeR3NoCRTGCC -
/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19673/src/VBox/Runtime/common/string/strcmp_alias.c
kBuild: Compiling RuntimeR3NoCRTGCC -
/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19673/src/VBox/Runtime/common/string/strlen_alias.c
kmk[2]: *** No rule to make target `/usr/src/sys/kern/bus_if.m', needed by
`/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/RuntimeR0Drv/bus_if.h'.
Stop.
kmk[2]: *** Waiting for unfinished jobs....
kmk[2]: Leaving directory
`/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19673'
kmk[2]: Entering directory
`/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19673'
kmk[2]: *** Exiting with status 2
kmk[1]: *** [pass_libraries_this] Error 2
kmk[1]: Leaving directory
`/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19673'
kmk: *** [pass_libraries_order] Error 2
*** Error code 2

Stop in /usr/ports/emulators/virtualbox.

[Martin Wilke]

We rolled a new tarball with the patch from Juergen Lock [1]
with a posible fix for AMD64 users, tested on 3 machines
which now works without problems. Many Thanks to him for
his nice work!

http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz

Martin

- --

+-----------------------+-------------------------------+
| PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de |
| ICQ : 169139903 | Mail : miwi(at)FreeBSD.org |
+-----------------------+-------------------------------+
| Mess with the Best, Die like the Rest! |
+-----------------------+-------------------------------+

[Sam Fourman Jr.]

Post by Sergey V. Dyatko
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
We rolled a new tarball with the patch from Juergen Lock [1]
with a posible fix for AMD64 users, tested on 3 machines
which now works without problems. Many Thanks to him for
his nice work!
http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz
Martin

Does this version still have the kernel module crashing at random on current?

Sam Fourman Jr.

[Benoit Calvez]

Post by Sam Fourman Jr.

Post by Sergey V. Dyatko
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
We rolled a new tarball with the patch from Juergen Lock [1]
with a posible fix for AMD64 users, tested on 3 machines
which now works without problems. Many Thanks to him for
his nice work!
http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz<http://people.freebsd.org/%7Emiwi/vbox/virtualbox_2.tgz>
Martin

Does this version still have the kernel module crashing at random on current?
Sam Fourman Jr.
_______________________________________________
http://lists.freebsd.org/mailman/listinfo/freebsd-current

I uninstalled the last virtualbox (from virtualbox_1.tgz port). It compiled
fine and I could start an opensolaris vm.
It crashed cauz' I created the virtual hard drive in a smal partition. Since
then I couldn't restart the vm.
I got two Errors:

"Kernel driver not instaled (rc =-1908)
"Make sure the kernel module has beed loaded successfully"

Sure it is.

the other one is :


Result Code:

NS_ERROR_FAILURE (0x80004005)

Component:

Machine

Interface:

IMachine {4d1df26d-d9c1-4c7e-b689-15e85ecf8ffc}

I could give more informations if needed

[Ivan Voras]

Post by Benoit Calvez
I uninstalled the last virtualbox (from virtualbox_1.tgz port). It compiled
fine and I could start an opensolaris vm.
It crashed cauz' I created the virtual hard drive in a smal partition. Since
then I couldn't restart the vm.
"Kernel driver not instaled (rc =-1908)
"Make sure the kernel module has beed loaded successfully"
Sure it is.
NS_ERROR_FAILURE (0x80004005)
Machine
IMachine {4d1df26d-d9c1-4c7e-b689-15e85ecf8ffc}

Same here, AMD64, 8-CURRENT.

[Greg Byshenk]

Post by Martin Wilke
We rolled a new tarball with the patch from Juergen Lock [1]
with a posible fix for AMD64 users, tested on 3 machines
which now works without problems. Many Thanks to him for
his nice work!
http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz

I've just updated my system (to 7-STABLE amd64 as of today) and
installed the new version. It runs for me now. Tomorrow I will
try to create virtual machine.

[Sam Fourman Jr.]

Post by Martin Wilke
We rolled a new tarball with the patch from Juergen Lock [1]
with a posible fix for AMD64 users, tested on 3 machines
which now works without problems. Many Thanks to him for
his nice work!
http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz

Does the FreeBSD version have USB passthrough support like Linux?

Sam Fourman

[Greg Byshenk]

Post by Greg Byshenk

Post by Martin Wilke
We rolled a new tarball with the patch from Juergen Lock [1]
with a posible fix for AMD64 users, tested on 3 machines
which now works without problems. Many Thanks to him for
his nice work!
http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz

I've just updated my system (to 7-STABLE amd64 as of today) and
installed the new version. It runs for me now. Tomorrow I will
try to create virtual machine.

As a followup, the 'virtualbox_2.tgz' version appears to work for
me, at least minimally. I've just installed NetBSD4.1 virtual
machine, and it appears to be working (even though NetBSD isn't
listed as a supported guest -- I just happened to have the NetBSD
install iso sitting on my hard drive).

[Doug Poland]

Post by Martin Wilke
We rolled a new tarball with the patch from Juergen Lock [1]
with a posible fix for AMD64 users, tested on 3 machines
which now works without problems. Many Thanks to him for
his nice work!
http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz

Working for me with a fresh cvsup of 7.2-STABLE (17 May 09).
Installing a 7.2-RELEASE amd64 guest as I write this.

[Tim Bishop]

Post by Doug Poland

Post by Martin Wilke
We rolled a new tarball with the patch from Juergen Lock [1]
with a posible fix for AMD64 users, tested on 3 machines
which now works without problems. Many Thanks to him for
his nice work!
http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz

Working for me with a fresh cvsup of 7.2-STABLE (17 May 09).
Installing a 7.2-RELEASE amd64 guest as I write this.

Works for me, but I've not been able to get a 64 bit guest to work. I
get the following error when booting the installer:

CPU doesn't support long mode

I think I've got all the right options set. Maybe my CPU doesn't support
the necessary VM stuff to let a 64 bit guest work?

I'm also still seeing the following on loading vboxdrv:

kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
vboxdrv: fAsync=0 offMin=0x41f offMax=0x53b

Are others still seeing that on amd64?

Tim.

[Tim Bishop]

Post by Tim Bishop

Post by Doug Poland

Post by Martin Wilke
We rolled a new tarball with the patch from Juergen Lock [1]
with a posible fix for AMD64 users, tested on 3 machines
which now works without problems. Many Thanks to him for
his nice work!
http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz

Working for me with a fresh cvsup of 7.2-STABLE (17 May 09).
Installing a 7.2-RELEASE amd64 guest as I write this.

Works for me, but I've not been able to get a 64 bit guest to work. I
CPU doesn't support long mode
I think I've got all the right options set. Maybe my CPU doesn't support
the necessary VM stuff to let a 64 bit guest work?

I'm getting good at answering my own questions :D Yes, it's my CPU.
Found a different machine and confirmed it has the VMX extension, and
all is fine.

Post by Tim Bishop
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
vboxdrv: fAsync=0 offMin=0x41f offMax=0x53b
Are others still seeing that on amd64?

Not that I thought it'd make any difference, but I can confirm those
still happen even with the VMX extension.

Tim.

[Benoit Calvez]

Post by Tim Bishop

Post by Doug Poland

Post by Martin Wilke
We rolled a new tarball with the patch from Juergen Lock [1]
with a posible fix for AMD64 users, tested on 3 machines
which now works without problems. Many Thanks to him for
his nice work!
http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz<http://people.freebsd.org/%7Emiwi/vbox/virtualbox_2.tgz>

Working for me with a fresh cvsup of 7.2-STABLE (17 May 09).
Installing a 7.2-RELEASE amd64 guest as I write this.

Works for me, but I've not been able to get a 64 bit guest to work. I
CPU doesn't support long mode
I think I've got all the right options set. Maybe my CPU doesn't support
the necessary VM stuff to let a 64 bit guest work?
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
vboxdrv: fAsync=0 offMin=0x41f offMax=0x53b
Are others still seeing that on amd64?

got the same in dmesg:

kldload: unexpected relocation type 10
vboxdrv: fAsync=1 offMin=0xff94c offMax=0xff94c
supdrvGipCreate: omni timer not supported, falling back to synchronous mode

Post by Tim Bishop
Tim.
--
Tim Bishop
http://www.bishnet.net/tim/
PGP Key: 0x5AE7D984
_______________________________________________
http://lists.freebsd.org/mailman/listinfo/freebsd-current

[Andrey Fesenko]

Post by Tim Bishop

Post by Doug Poland

Post by Martin Wilke
We rolled a new tarball with the patch from Juergen Lock [1]
with a posible fix for AMD64 users, tested on 3 machines
which now works without problems. Many Thanks to him for
his nice work!
http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz<http://people.freebsd.org/%7Emiwi/vbox/virtualbox_2.tgz>

Working for me with a fresh cvsup of 7.2-STABLE (17 May 09).
Installing a 7.2-RELEASE amd64 guest as I write this.

Works for me, but I've not been able to get a 64 bit guest to work. I
CPU doesn't support long mode
I think I've got all the right options set. Maybe my CPU doesn't support
the necessary VM stuff to let a 64 bit guest work?
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
kldload: unexpected relocation type 10
vboxdrv: fAsync=0 offMin=0x41f offMax=0x53b
Are others still seeing that on amd64?

FreeBSD 8.0-CURRENT #0: Sun May 17 07:56:14 MSD 2009 amd64

got the same in/var/log/messages
May 18 22:00:02 my_book newsyslog[25948]: logfile turned over due to
size>100K
May 18 22:07:28 my_book kernel: kldload: unexpected relocation type 10
May 18 22:07:28 my_book last message repeated 11 times
May 18 22:07:28 my_book kernel: vboxdrv: fAsync=0 offMin=0x499 offMax=0x8744

[Glen Barber]

Post by Sergey V. Dyatko
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
We rolled a new tarball with the patch from Juergen Lock [1]
with a posible fix for AMD64 users, tested on 3 machines
which now works without problems. Many Thanks to him for
his nice work!

Is there need for the i386 folks to rebuild, or does it only affect amd64?

[Andrey Fesenko]

Post by Martin Wilke
We rolled a new tarball with the patch from Juergen Lock [1]
with a posible fix for AMD64 users, tested on 3 machines
which now works without problems. Many Thanks to him for
his nice work!
http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz<http://people.freebsd.org/%7Emiwi/vbox/virtualbox_2.tgz>
Martin

FreeBSD 8.0-CURRENT #0: Sun May 17 07:56:14 MSD 2009 amd64
new port virtualbox_2.tgz<http://people.freebsd.org/%7Emiwi/vbox/virtualbox_2.tgz>
make - OK
install - OK
load module - OK
run -OK
run VM - crush :( only 1 time. more have not yet tried.

[Marius Nünnerich]

Post by Sergey V. Dyatko
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
We rolled a new tarball with the patch from Juergen Lock [1]
with a posible fix for AMD64 users, tested on 3 machines
which now works without problems. Many Thanks to him for
his nice work!
http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz
Martin

I'm impressed, everything I tried worked ootb. Thank you all!

(FreeBSD/i386 7.2-STABLE)

[Martin Wilke]

Howdy ..

Next run,

We updated the port to 2.2.2r19801.
The Patch files/patch-amd64-r0-exec-alloc
was removed in favor of a similar fix
commited to upstream. Also was fixed a
bug on HEAD which should be fix the Kernel
crash. Please test test test .. :-)

PS: Yes this run is for AMD64 and HEAD
users!


http://people.freebsd.org/~miwi/vbox/virtualbox_3.tgz


Happy Testing!

- --

+-----------------------+-------------------------------+
| PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de |
| ICQ : 169139903 | Mail : miwi(at)FreeBSD.org |
+-----------------------+-------------------------------+
| Mess with the Best, Die like the Rest! |
+-----------------------+-------------------------------+

[Paul Wootton]

Post by Sergey V. Dyatko
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Howdy ..
Next run,
We updated the port to 2.2.2r19801.
The Patch files/patch-amd64-r0-exec-alloc
was removed in favor of a similar fix
commited to upstream. Also was fixed a
bug on HEAD which should be fix the Kernel
crash. Please test test test .. :-)
PS: Yes this run is for AMD64 and HEAD
users!
http://people.freebsd.org/~miwi/vbox/virtualbox_3.tgz
Happy Testing!
- --
+-----------------------+-------------------------------+
| PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de |
| ICQ : 169139903 | Mail : miwi(at)FreeBSD.org |
+-----------------------+-------------------------------+
| Mess with the Best, Die like the Rest! |
+-----------------------+-------------------------------+
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (FreeBSD)
iEYEARECAAYFAkoSeCYACgkQdLJIhLHm/OkuOQCfVzr7yTxydbo6npBgO2LyZNk1
RpUAnAmxjlHTBsM8pJ5SIiPIqQRCWElu
=LoBM
-----END PGP SIGNATURE-----
_______________________________________________
http://lists.freebsd.org/mailman/listinfo/freebsd-current

Hi,

Im still having build issues. This is the same issue I get when
compiling this and the last 2 revisions.

Have you got any ideas?

Cheers
Paul

demophon# uname -a
FreeBSD demophon 8.0-CURRENT FreeBSD 8.0-CURRENT #15: Mon May 18
10:13:13 BST 2009 ***@demophon:/usr/obj/usr/src/sys/DEMOPHON amd64
demophon#

kBuild: Generating tstVMStructSize -
/root/vBox/virtualbox/work/virtualbox-2.2.2r19801/out/freebsd.amd64/release/obj/VMM/tstAsmStructsHC.h
/root/vBox/virtualbox/work/virtualbox-2.2.2r19801/out/freebsd.amd64/release/bin/tstVMStructGC:
1: Syntax error: "(" unexpected
kmk[2]: ***
[/root/vBox/virtualbox/work/virtualbox-2.2.2r19801/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h]
Error 2
kmk[2]: *** Deleting file
`/root/vBox/virtualbox/work/virtualbox-2.2.2r19801/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h'
kmk[2]: *** Waiting for unfinished jobs....
awk: can't open file
/root/vBox/virtualbox/work/virtualbox-2.2.2r19801/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.def
source line number 10
objcopy --strip-debug
/root/vBox/virtualbox/work/virtualbox-2.2.2r19801/out/freebsd.amd64/release/obj/vboxdrv/vboxdrv.ko
kmk[2]: Leaving directory
`/root/vBox/virtualbox/work/virtualbox-2.2.2r19801'
kmk[2]: Entering directory
`/root/vBox/virtualbox/work/virtualbox-2.2.2r19801'
kmk[2]: *** Exiting with status 2
kmk[1]: *** [pass_binaries_this] Error 2
kmk[1]: Leaving directory
`/root/vBox/virtualbox/work/virtualbox-2.2.2r19801'
kmk: *** [pass_binaries_order] Error 2
*** Error code 2

Stop in /root/vBox/virtualbox.
demophon#

[Gustau Pérez]

Martin Wilke wrote: Howdy ..
Next run,
We updated the port to 2.2.2r19801. The Patch
files/patch-amd64-r0-exec-alloc was removed in favor of a similar
fix commited to upstream. Also was fixed a bug on HEAD which should
be fix the Kernel crash. Please test test test .. :-)
PS: Yes this run is for AMD64 and HEAD users!
http://people.freebsd.org/~miwi/vbox/virtualbox_3.tgz
Happy Testing!

Reporting,

For my system :

FreeBSD portatil 8.0-CURRENT FreeBSD 8.0-CURRENT #40: Mon
May 18 09:09:07 CEST 2009
***@gusiport:/usr/obj/usr/src/sys/CUSTOM i386

the second run problem (when virtualbox argued about the missing
kernel support) has dissapeared. The only problem is that when I try
to start the virtual machine, its screen remains gray. Any hint about
this particular problem ? Any has an idea where the problem can be, to
start looking for a solution ?

Moreover, will try to try :) in CURRENT-AMD64 in the same. Will
take me long, cause I think I wipe the installation some time ago :(

Regards,

Gus


- --
PGP KEY : http://www-entel.upc.edu/gus/gus.asc

[Carl Johan Gustavsson]

Post by Sergey V. Dyatko
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Howdy ..
Next run,
We updated the port to 2.2.2r19801.
The Patch files/patch-amd64-r0-exec-alloc
was removed in favor of a similar fix
commited to upstream. Also was fixed a
bug on HEAD which should be fix the Kernel
crash. Please test test test .. :-)
PS: Yes this run is for AMD64 and HEAD
users!
http://people.freebsd.org/~miwi/vbox/virtualbox_3.tgz
Happy Testing!

Hi,

It seems as this version has solved the problems I had with the earlier
versions, it hung my machine when starting the VM. I'm running i386
HEAD. Now I'm able to install and boot 32bit Ubuntu and the performance
seems very nice.

Great job!

cjg

Post by Sergey V. Dyatko
- --
+-----------------------+-------------------------------+
| PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de |
| ICQ : 169139903 | Mail : miwi(at)FreeBSD.org |
+-----------------------+-------------------------------+
| Mess with the Best, Die like the Rest! |
+-----------------------+-------------------------------+
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (FreeBSD)
iEYEARECAAYFAkoSeCYACgkQdLJIhLHm/OkuOQCfVzr7yTxydbo6npBgO2LyZNk1
RpUAnAmxjlHTBsM8pJ5SIiPIqQRCWElu
=LoBM
-----END PGP SIGNATURE-----
_______________________________________________
http://lists.freebsd.org/mailman/listinfo/freebsd-current

[Sergey V. Dyatko]

В Tue, 19 May 2009 11:13:10 +0200
Martin Wilke <***@FreeBSD.org> пишет:

MW> -----BEGIN PGP SIGNED MESSAGE-----
MW> Hash: SHA1
MW>
MW> Howdy ..
MW>
MW> Next run,
MW>
MW> We updated the port to 2.2.2r19801.
MW> The Patch files/patch-amd64-r0-exec-alloc
MW> was removed in favor of a similar fix
MW> commited to upstream. Also was fixed a
MW> bug on HEAD which should be fix the Kernel
MW> crash. Please test test test .. :-)
Thanks,
after kldload vboxdrv start/stop vm (winxp) is work fine for me.
But...
kldunload vboxdrv - ok
kldload vboxdrv - system hungs. solution: hw reset:(

/var/log/messages:
May 19 13:22:12 tiger kernel: vboxdrv: fAsync=0 offMin=0x9a8
offMax=0xda0
May 19 14:15:56 tiger kernel: Warning: memory type iprtheap leaked
memory on destroy (3 allocations, 192 bytes leaked).
May 19 14:16:04 tiger kernel: vboxdrv: fAsync=0 offMin=0x898
offMax=0xb38

[***@tiger]~%uname -a
FreeBSD tiger.minsk.domain 8.0-CURRENT FreeBSD 8.0-CURRENT #26: Fri
May 8 15:32:29 EEST 2009
***@tiger.minsk.domain:/usr/obj/usr/src/sys/tiger-desktop i386

backtrace - http://tiger.ipfw.ru/files/bt.txt

MW>
MW> PS: Yes this run is for AMD64 and HEAD
MW> users!
MW>
MW>
MW> http://people.freebsd.org/~miwi/vbox/virtualbox_3.tgz
MW>
MW>
MW> Happy Testing!
MW>
MW> - --
MW>
MW> +-----------------------+-------------------------------+
MW> | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de |
MW> | ICQ : 169139903 | Mail : miwi(at)FreeBSD.org |
MW> +-----------------------+-------------------------------+
MW> | Mess with the Best, Die like the Rest! |
MW> +-----------------------+-------------------------------+
MW> -----BEGIN PGP SIGNATURE-----
MW> Version: GnuPG v2.0.11 (FreeBSD)
MW>
MW> iEYEARECAAYFAkoSeCYACgkQdLJIhLHm/OkuOQCfVzr7yTxydbo6npBgO2LyZNk1
MW> RpUAnAmxjlHTBsM8pJ5SIiPIqQRCWElu
MW> =LoBM
MW> -----END PGP SIGNATURE-----

--
wbr, tiger

[Martin Wilke]

? Tue, 19 May 2009 11:13:10 +0200
MW> -----BEGIN PGP SIGNED MESSAGE-----
MW> Hash: SHA1
MW>
MW> Howdy ..
MW>
MW> Next run,
MW>
MW> We updated the port to 2.2.2r19801.
MW> The Patch files/patch-amd64-r0-exec-alloc
MW> was removed in favor of a similar fix
MW> commited to upstream. Also was fixed a
MW> bug on HEAD which should be fix the Kernel
MW> crash. Please test test test .. :-)
Thanks,
after kldload vboxdrv start/stop vm (winxp) is work fine for me.
But...
kldunload vboxdrv - ok
kldload vboxdrv - system hungs. solution: hw reset:(

How old is your src?

May 19 13:22:12 tiger kernel: vboxdrv: fAsync=0 offMin=0x9a8
offMax=0xda0
May 19 14:15:56 tiger kernel: Warning: memory type iprtheap leaked
memory on destroy (3 allocations, 192 bytes leaked).
May 19 14:16:04 tiger kernel: vboxdrv: fAsync=0 offMin=0x898
offMax=0xb38
FreeBSD tiger.minsk.domain 8.0-CURRENT FreeBSD 8.0-CURRENT #26: Fri
May 8 15:32:29 EEST 2009
backtrace - http://tiger.ipfw.ru/files/bt.txt
MW>
MW> PS: Yes this run is for AMD64 and HEAD
MW> users!
MW>
MW>
MW> http://people.freebsd.org/~miwi/vbox/virtualbox_3.tgz
MW>
MW>
MW> Happy Testing!
MW>
MW> - --
MW>
MW> +-----------------------+-------------------------------+
MW> | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de |
MW> | ICQ : 169139903 | Mail : miwi(at)FreeBSD.org |
MW> +-----------------------+-------------------------------+
MW> | Mess with the Best, Die like the Rest! |
MW> +-----------------------+-------------------------------+
MW> -----BEGIN PGP SIGNATURE-----
MW> Version: GnuPG v2.0.11 (FreeBSD)
MW>
MW> iEYEARECAAYFAkoSeCYACgkQdLJIhLHm/OkuOQCfVzr7yTxydbo6npBgO2LyZNk1
MW> RpUAnAmxjlHTBsM8pJ5SIiPIqQRCWElu
MW> =LoBM
MW> -----END PGP SIGNATURE-----
--
wbr, tiger

- --

+-----------------------+-------------------------------+
| PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de |
| ICQ : 169139903 | Mail : miwi(at)FreeBSD.org |
+-----------------------+-------------------------------+
| Mess with the Best, Die like the Rest! |
+-----------------------+-------------------------------+

[Sergey V. Dyatko]

В Tue, 19 May 2009 13:38:52 +0200
Martin Wilke <***@FreeBSD.org> пишет:

MW> -----BEGIN PGP SIGNED MESSAGE-----
MW> Hash: SHA1
MW>
MW> On Tue, May 19, 2009 at 02:34:51PM +0300, Sergey V. Dyatko wrote:
MW> > ? Tue, 19 May 2009 11:13:10 +0200
MW> > Martin Wilke <***@FreeBSD.org> ?????:
MW> >
MW> > MW> -----BEGIN PGP SIGNED MESSAGE-----
MW> > MW> Hash: SHA1
MW> > MW>
MW> > MW> Howdy ..
MW> > MW>
MW> > MW> Next run,
MW> > MW>
MW> > MW> We updated the port to 2.2.2r19801.
MW> > MW> The Patch files/patch-amd64-r0-exec-alloc
MW> > MW> was removed in favor of a similar fix
MW> > MW> commited to upstream. Also was fixed a
MW> > MW> bug on HEAD which should be fix the Kernel
MW> > MW> crash. Please test test test .. :-)
MW> > Thanks,
MW> > after kldload vboxdrv start/stop vm (winxp) is work fine for me.
MW> > But...
MW> > kldunload vboxdrv - ok
MW> > kldload vboxdrv - system hungs. solution: hw reset:(
MW>
MW> How old is your src?

Fri May 8 15:32:29 EEST 2009

virtualbox is 2.2.2r19801


MW>
MW> >
MW> > /var/log/messages:
MW> > May 19 13:22:12 tiger kernel: vboxdrv: fAsync=0 offMin=0x9a8
MW> > offMax=0xda0
MW> > May 19 14:15:56 tiger kernel: Warning: memory type iprtheap leaked
MW> > memory on destroy (3 allocations, 192 bytes leaked).
MW> > May 19 14:16:04 tiger kernel: vboxdrv: fAsync=0 offMin=0x898
MW> > offMax=0xb38
MW> >
MW> > [***@tiger]~%uname -a
MW> > FreeBSD tiger.minsk.domain 8.0-CURRENT FreeBSD 8.0-CURRENT #26:
MW> > Fri May 8 15:32:29 EEST 2009
MW> > ***@tiger.minsk.domain:/usr/obj/usr/src/sys/tiger-desktop i386
MW> >
MW> > backtrace - http://tiger.ipfw.ru/files/bt.txt
MW> >
MW> > MW>
MW> > MW> PS: Yes this run is for AMD64 and HEAD
MW> > MW> users!
MW> > MW>
MW> > MW>
MW> > MW> http://people.freebsd.org/~miwi/vbox/virtualbox_3.tgz
MW> > MW>
MW> > MW>
MW> > MW> Happy Testing!
MW> > MW>
MW> > MW> - --
MW> > MW>
MW> > MW> +-----------------------+-------------------------------+
MW> > MW> | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de |
MW> > MW> | ICQ : 169139903 | Mail : miwi(at)FreeBSD.org |
MW> > MW> +-----------------------+-------------------------------+
MW> > MW> | Mess with the Best, Die like the
MW> > MW> Rest! |
MW> > MW> +-----------------------+-------------------------------+
MW> > MW> -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD)
MW> > MW>
MW> > MW> iEYEARECAAYFAkoSeCYACgkQdLJIhLHm/OkuOQCfVzr7yTxydbo6npBgO2LyZNk1
MW> > MW> RpUAnAmxjlHTBsM8pJ5SIiPIqQRCWElu
MW> > MW> =LoBM
MW> > MW> -----END PGP SIGNATURE-----
MW> >
MW> > --
MW> > wbr, tiger
MW> >
MW>
MW> - --
MW>
MW> +-----------------------+-------------------------------+
MW> | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de |
MW> | ICQ : 169139903 | Mail : miwi(at)FreeBSD.org |
MW> +-----------------------+-------------------------------+
MW> | Mess with the Best, Die like the Rest! |
MW> +-----------------------+-------------------------------+
MW> -----BEGIN PGP SIGNATURE-----
MW> Version: GnuPG v2.0.11 (FreeBSD)
MW>
MW> iEYEARECAAYFAkoSmkwACgkQdLJIhLHm/Ony5gCg4iWUTPqjrIJoY+hmLndSD5Ml
MW> d6kAoNIE/VCuRHnqShzuywsGOb9pKVcP
MW> =IRJZ
MW> -----END PGP SIGNATURE-----



--
wbr, tiger

[Martin Wilke]

? Tue, 19 May 2009 13:38:52 +0200
MW> -----BEGIN PGP SIGNED MESSAGE-----
MW> Hash: SHA1
MW>
MW> > ? Tue, 19 May 2009 11:13:10 +0200
MW> >
MW> > MW> -----BEGIN PGP SIGNED MESSAGE-----
MW> > MW> Hash: SHA1
MW> > MW>
MW> > MW> Howdy ..
MW> > MW>
MW> > MW> Next run,
MW> > MW>
MW> > MW> We updated the port to 2.2.2r19801.
MW> > MW> The Patch files/patch-amd64-r0-exec-alloc
MW> > MW> was removed in favor of a similar fix
MW> > MW> commited to upstream. Also was fixed a
MW> > MW> bug on HEAD which should be fix the Kernel
MW> > MW> crash. Please test test test .. :-)
MW> > Thanks,
MW> > after kldload vboxdrv start/stop vm (winxp) is work fine for me.
MW> > But...
MW> > kldunload vboxdrv - ok
MW> > kldload vboxdrv - system hungs. solution: hw reset:(
MW>
MW> How old is your src?
Fri May 8 15:32:29 EEST 2009
virtualbox is 2.2.2r19801

Ok, Can you please update your src/kernel after
that please rebuild vbox. That should be fix the crash.

- - Martin

- --

+-----------------------+-------------------------------+
| PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de |
| ICQ : 169139903 | Mail : miwi(at)FreeBSD.org |
+-----------------------+-------------------------------+
| Mess with the Best, Die like the Rest! |
+-----------------------+-------------------------------+

[Sergey V. Dyatko]

В Tue, 19 May 2009 13:49:09 +0200
Martin Wilke <***@FreeBSD.org> пишет:

MW> -----BEGIN PGP SIGNED MESSAGE-----
MW> Hash: SHA1
MW>
MW> On Tue, May 19, 2009 at 02:42:40PM +0300, Sergey V. Dyatko wrote:
MW> > ? Tue, 19 May 2009 13:38:52 +0200
MW> > Martin Wilke <***@FreeBSD.org> ?????:
MW> >
MW> > MW> -----BEGIN PGP SIGNED MESSAGE-----
MW> > MW> Hash: SHA1
MW> > MW>
MW> > MW> On Tue, May 19, 2009 at 02:34:51PM +0300, Sergey V. Dyatko
MW> > MW> wrote:
MW> > MW> > ? Tue, 19 May 2009 11:13:10 +0200
MW> > MW> > Martin Wilke <***@FreeBSD.org> ?????:
MW> > MW> >
MW> > MW> > MW> -----BEGIN PGP SIGNED MESSAGE-----
MW> > MW> > MW> Hash: SHA1
MW> > MW> > MW>
MW> > MW> > MW> Howdy ..
MW> > MW> > MW>
MW> > MW> > MW> Next run,
MW> > MW> > MW>
MW> > MW> > MW> We updated the port to 2.2.2r19801.
MW> > MW> > MW> The Patch files/patch-amd64-r0-exec-alloc
MW> > MW> > MW> was removed in favor of a similar fix
MW> > MW> > MW> commited to upstream. Also was fixed a
MW> > MW> > MW> bug on HEAD which should be fix the Kernel
MW> > MW> > MW> crash. Please test test test .. :-)
MW> > MW> > Thanks,
MW> > MW> > after kldload vboxdrv start/stop vm (winxp) is work fine
MW> > MW> > for me. But...
MW> > MW> > kldunload vboxdrv - ok
MW> > MW> > kldload vboxdrv - system hungs. solution: hw reset:(
MW> > MW>
MW> > MW> How old is your src?
MW> >
MW> > Fri May 8 15:32:29 EEST 2009
MW> >
MW> > virtualbox is 2.2.2r19801
MW> >
MW>
MW>
MW> Ok, Can you please update your src/kernel after
MW> that please rebuild vbox. That should be fix the crash.
MW>
Ok, I'll try
MW> - - Martin
MW>
MW> - --
MW>
MW> +-----------------------+-------------------------------+
MW> | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de |
MW> | ICQ : 169139903 | Mail : miwi(at)FreeBSD.org |
MW> +-----------------------+-------------------------------+
MW> | Mess with the Best, Die like the Rest! |
MW> +-----------------------+-------------------------------+
MW> -----BEGIN PGP SIGNATURE-----
MW> Version: GnuPG v2.0.11 (FreeBSD)
MW>
MW> iEYEARECAAYFAkoSnLUACgkQdLJIhLHm/OlnuwCfX1yGFsfMbxiluoDAx+1lDxuB
MW> uSEAn1lM2r4xjfJAa2GnJYUAI5nsLlCN
MW> =Rn5t
MW> -----END PGP SIGNATURE-----



--
wbr, tiger

[Sergey G Nasonov]

Post by Martin Wilke
Howdy ..
Next run,
We updated the port to 2.2.2r19801.
The Patch files/patch-amd64-r0-exec-alloc
was removed in favor of a similar fix
commited to upstream. Also was fixed a
bug on HEAD which should be fix the Kernel
crash. Please test test test .. :-)
PS: Yes this run is for AMD64 and HEAD
users!
http://people.freebsd.org/~miwi/vbox/virtualbox_3.tgz
Happy Testing!

FreeBSD snasonovnbwxp.bcc 8.0-CURRENT FreeBSD 8.0-CURRENT #23: Tue May 19
11:26:37 MSD 2009
***@snasonovnbwxp.bcc:/usr/obj/usr/current/src/sys/CUSTOM i386

With this version I can succesfuly run VM (now it Windows XP 32 bit). All
previous versions at VM start lead system to hang.

Thanks!

[subbsd]

Hello

Post by Martin Wilke
Howdy ..
Next run,
We updated the port to 2.2.2r19801.
The Patch files/patch-amd64-r0-exec-alloc
was removed in favor of a similar fix
commited to upstream. Also was fixed a
bug on HEAD which should be fix the Kernel
crash. Please test test test .. :-)
PS: Yes this run is for AMD64 and HEAD
users!
http://people.freebsd.org/~miwi/vbox/virtualbox_3.tgz
Happy Testing!

I've try to compile this port on i386/8-CURRENT ( kern.osreldate: 800087 ) and
job stops with last messages:
--
/* ... */
kBuild: xsltproc VBoxSVC -
/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/src/VBox/Main/idl/xpidl.xsl
kBuild: Compiling RuntimeR3 -
/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/src/VBox/Runtime/common/err/errmsg.cpp
kBuild: Compiling RuntimeR3 -
/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/src/VBox/Runtime/common/err/errmsgxpcom.cpp
kBuild: Linking RuntimeR0
kBuild: Linking RuntimeGC
kBuild: Linking RuntimeEFCPP
kBuild: Linking RuntimeR3NoCRTGCC
kBuild: Compiling RuntimeR0Drv -
/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/src/VBox/Runtime/common/alloc/alloc.cpp
kBuild: Linking VMMR3
kBuild: Compiling PcBiosBin -
/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/out/freebsd.x86/release/obj/PcBiosBin/_rombios_.c
/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/out/freebsd.x86/release/obj/PcBiosBin/_rombios_.c:471.66:
error: need ';'
/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/out/freebsd.x86/release/obj/PcBiosBin/_rombios_.c:471.66:
error: need variable name
kmk[2]: ***
[/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/out/freebsd.x86/release/obj/PcBiosBin/rombios0.s]
Error 1
kmk[2]: *** Deleting file
`/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/out/freebsd.x86/release/obj/PcBiosBin/rombios0.s'
kmk[2]: *** Waiting for unfinished jobs....
kmk[2]: Leaving directory
`/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801'
kmk[2]: Entering directory
`/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801'
kmk[2]: *** Exiting with status 2
kmk[1]: *** [pass_libraries_this] Error 2
kmk[1]: Leaving directory
`/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801'
kmk: *** [pass_libraries_order] Error 2
*** Error code 2

Stop in /usr/ports/emulators/virtualbox.

--

DISABLE_MAKE_JOBS=yes options is not influence
In the _rombios__c at 471 i see strings:

static char bios_cvs_version_string[] = "VirtualBox " "2.2.51_OSE";

but ';' symbol is presents.

[Martin Wilke]

Post by subbsd
Hello

Post by Martin Wilke
Howdy ..
Next run,
We updated the port to 2.2.2r19801.
The Patch files/patch-amd64-r0-exec-alloc
was removed in favor of a similar fix
commited to upstream. Also was fixed a
bug on HEAD which should be fix the Kernel
crash. Please test test test .. :-)
PS: Yes this run is for AMD64 and HEAD
users!
http://people.freebsd.org/~miwi/vbox/virtualbox_3.tgz
Happy Testing!

I've try to compile this port on i386/8-CURRENT ( kern.osreldate: 800087 ) and

please update your src/kernel and rebuild vbox

Post by subbsd
--
/* ... */
kBuild: xsltproc VBoxSVC -
/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/src/VBox/Main/idl/xpidl.xsl
kBuild: Compiling RuntimeR3 -
/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/src/VBox/Runtime/common/err/errmsg.cpp
kBuild: Compiling RuntimeR3 -
/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/src/VBox/Runtime/common/err/errmsgxpcom.cpp
kBuild: Linking RuntimeR0
kBuild: Linking RuntimeGC
kBuild: Linking RuntimeEFCPP
kBuild: Linking RuntimeR3NoCRTGCC
kBuild: Compiling RuntimeR0Drv -
/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/src/VBox/Runtime/common/alloc/alloc.cpp
kBuild: Linking VMMR3
kBuild: Compiling PcBiosBin -
/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/out/freebsd.x86/release/obj/PcBiosBin/_rombios_.c
error: need ';'
error: need variable name
kmk[2]: ***
[/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/out/freebsd.x86/release/obj/PcBiosBin/rombios0.s]
Error 1
kmk[2]: *** Deleting file
`/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/out/freebsd.x86/release/obj/PcBiosBin/rombios0.s'
kmk[2]: *** Waiting for unfinished jobs....
kmk[2]: Leaving directory
`/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801'
kmk[2]: Entering directory
`/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801'
kmk[2]: *** Exiting with status 2
kmk[1]: *** [pass_libraries_this] Error 2
kmk[1]: Leaving directory
`/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801'
kmk: *** [pass_libraries_order] Error 2
*** Error code 2
Stop in /usr/ports/emulators/virtualbox.
--
DISABLE_MAKE_JOBS=yes options is not influence
static char bios_cvs_version_string[] = "VirtualBox " "2.2.51_OSE";
but ';' symbol is presents.
_______________________________________________
http://lists.freebsd.org/mailman/listinfo/freebsd-current

- --

+-----------------------+-------------------------------+
| PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de |
| ICQ : 169139903 | Mail : miwi(at)FreeBSD.org |
+-----------------------+-------------------------------+
| Mess with the Best, Die like the Rest! |
+-----------------------+-------------------------------+

[Ismail YENIGUL]

Hello Martin,

I installed http://people.freebsd.org/~miwi/vbox/virtualbox_3.tgz on FreeBSD 8 snapshot-200905 amd64.
It compiled successfully, But When I create a virtual server (Redhat) and click on start,
FreeBSD 8 crashed. I am not in the office at the moment. I will check the error messages tomorrow.

Thaks.

Post by Sergey V. Dyatko
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Post by subbsd
Hello

Post by Martin Wilke
Howdy ..
Next run,
We updated the port to 2.2.2r19801.
The Patch files/patch-amd64-r0-exec-alloc
was removed in favor of a similar fix
commited to upstream. Also was fixed a
bug on HEAD which should be fix the Kernel
crash. Please test test test .. :-)
PS: Yes this run is for AMD64 and HEAD
users!
http://people.freebsd.org/~miwi/vbox/virtualbox_3.tgz
Happy Testing!

I've try to compile this port on i386/8-CURRENT ( kern.osreldate: 800087 ) and

please update your src/kernel and rebuild vbox

Post by subbsd
--
/* ... */
kBuild: xsltproc VBoxSVC -
/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/src/VBox/Main/idl/xpidl.xsl
kBuild: Compiling RuntimeR3 -
/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/src/VBox/Runtime/common/err/errmsg.cpp
kBuild: Compiling RuntimeR3 -
/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/src/VBox/Runtime/common/err/errmsgxpcom.cpp
kBuild: Linking RuntimeR0
kBuild: Linking RuntimeGC
kBuild: Linking RuntimeEFCPP
kBuild: Linking RuntimeR3NoCRTGCC
kBuild: Compiling RuntimeR0Drv -
/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/src/VBox/Runtime/common/alloc/alloc.cpp
kBuild: Linking VMMR3
kBuild: Compiling PcBiosBin -
/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/out/freebsd.x86/release/obj/PcBiosBin/_rombios_.c
error: need ';'
error: need variable name
kmk[2]: ***
[/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/out/freebsd.x86/release/obj/PcBiosBin/rombios0.s]
Error 1
kmk[2]: *** Deleting file
`/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/out/freebsd.x86/release/obj/PcBiosBin/rombios0.s'
kmk[2]: *** Waiting for unfinished jobs....
kmk[2]: Leaving directory
`/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801'
kmk[2]: Entering directory
`/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801'
kmk[2]: *** Exiting with status 2
kmk[1]: *** [pass_libraries_this] Error 2
kmk[1]: Leaving directory
`/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801'
kmk: *** [pass_libraries_order] Error 2
*** Error code 2
Stop in /usr/ports/emulators/virtualbox.
--
DISABLE_MAKE_JOBS=yes options is not influence
static char bios_cvs_version_string[] = "VirtualBox " "2.2.51_OSE";
but ';' symbol is presents.
_______________________________________________
http://lists.freebsd.org/mailman/listinfo/freebsd-current

[Ismail YENIGUL]

Hi,

Here is the error messages when I try to start a virtual server.

May 19 15:08:01 freebsd8 kernel: lock order reversal:
May 19 15:08:01 freebsd8 kernel: 1st 0xfffffffe69c94230 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:2555
May 19 15:08:01 freebsd8 kernel: 2nd 0xffffff00044d3c00 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhash.c:275
May 19 15:08:01 freebsd8 kernel: KDB: stack backtrace:
May 19 15:08:01 freebsd8 kernel: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a
May 19 15:08:01 freebsd8 kernel: _witness_debugger() at _witness_debugger+0x2e
May 19 15:08:01 freebsd8 kernel: witness_checkorder() at witness_checkorder+0x81e
May 19 15:08:01 freebsd8 kernel: _sx_xlock() at _sx_xlock+0x55
May 19 15:08:01 freebsd8 kernel: ufsdirhash_acquire() at ufsdirhash_acquire+0x33
May 19 15:08:01 freebsd8 kernel: ufsdirhash_add() at ufsdirhash_add+0x19
May 19 15:08:01 freebsd8 kernel: ufs_direnter() at ufs_direnter+0x88b
May 19 15:08:01 freebsd8 kernel: ufs_makeinode() at ufs_makeinode+0x31c
May 19 15:08:01 freebsd8 kernel: VOP_CREATE_APV() at VOP_CREATE_APV+0x8d
May 19 15:08:01 freebsd8 kernel: vn_open_cred() at vn_open_cred+0x3fd
May 19 15:08:01 freebsd8 kernel: kern_openat() at kern_openat+0x159
May 19 15:08:01 freebsd8 kernel: syscall() at syscall+0x1bf
May 19 15:08:01 freebsd8 kernel: Xfast_syscall() at Xfast_syscall+0xd0
May 19 15:08:01 freebsd8 kernel: --- syscall (5, FreeBSD ELF64, open), rip = 0x800e23e2c, rsp = 0x7fffffffe688, rbp = 0x124 ---
May 19 15:22:05 freebsd8 kernel: kldload: unexpected relocation type 10
May 19 15:22:05 freebsd8 last message repeated 11 times
May 19 15:22:05 freebsd8 kernel: vboxdrv: fAsync=0 offMin=0x1d8 offMax=0x950
May 20 08:56:26 freebsd8 syslogd: kernel boot file is /boot/kernel/kernel
May 20 08:56:26 freebsd8 kernel: Copyright (c) 1992-2009 The FreeBSD Project.
Ma

Post by Ismail YENIGUL
Hello Martin,
I installed http://people.freebsd.org/~miwi/vbox/virtualbox_3.tgz
on FreeBSD 8 snapshot-200905 amd64.
It compiled successfully, But When I create a virtual server (Redhat) and click on start,
FreeBSD 8 crashed. I am not in the office at the moment. I will
check the error messages tomorrow.
Thaks.

Post by Sergey V. Dyatko
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Post by subbsd
Hello

Post by Martin Wilke
Howdy ..
Next run,
We updated the port to 2.2.2r19801.
The Patch files/patch-amd64-r0-exec-alloc
was removed in favor of a similar fix
commited to upstream. Also was fixed a
bug on HEAD which should be fix the Kernel
crash. Please test test test .. :-)
PS: Yes this run is for AMD64 and HEAD
users!
http://people.freebsd.org/~miwi/vbox/virtualbox_3.tgz
Happy Testing!

I've try to compile this port on i386/8-CURRENT ( kern.osreldate: 800087 ) and

please update your src/kernel and rebuild vbox

Post by subbsd
--
/* ... */
kBuild: xsltproc VBoxSVC -
/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/src/VBox/Main/idl/xpidl.xsl
kBuild: Compiling RuntimeR3 -
/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/src/VBox/Runtime/common/err/errmsg.cpp
kBuild: Compiling RuntimeR3 -
/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/src/VBox/Runtime/common/err/errmsgxpcom.cpp
kBuild: Linking RuntimeR0
kBuild: Linking RuntimeGC
kBuild: Linking RuntimeEFCPP
kBuild: Linking RuntimeR3NoCRTGCC
kBuild: Compiling RuntimeR0Drv -
/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/src/VBox/Runtime/common/alloc/alloc.cpp
kBuild: Linking VMMR3
kBuild: Compiling PcBiosBin -
/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/out/freebsd.x86/release/obj/PcBiosBin/_rombios_.c
error: need ';'
error: need variable name
kmk[2]: ***
[/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/out/freebsd.x86/release/obj/PcBiosBin/rombios0.s]
Error 1
kmk[2]: *** Deleting file
`/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/out/freebsd.x86/release/obj/PcBiosBin/rombios0.s'
kmk[2]: *** Waiting for unfinished jobs....
kmk[2]: Leaving directory
`/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801'
kmk[2]: Entering directory
`/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801'
kmk[2]: *** Exiting with status 2
kmk[1]: *** [pass_libraries_this] Error 2
kmk[1]: Leaving directory
`/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801'
kmk: *** [pass_libraries_order] Error 2
*** Error code 2
Stop in /usr/ports/emulators/virtualbox.
--
DISABLE_MAKE_JOBS=yes options is not influence
static char bios_cvs_version_string[] = "VirtualBox " "2.2.51_OSE";
but ';' symbol is presents.
_______________________________________________
http://lists.freebsd.org/mailman/listinfo/freebsd-current

[Martin Wilke]

Post by Ismail YENIGUL
Hi,
Here is the error messages when I try to start a virtual server.
May 19 15:08:01 freebsd8 kernel: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a
May 19 15:08:01 freebsd8 kernel: _witness_debugger() at _witness_debugger+0x2e
May 19 15:08:01 freebsd8 kernel: witness_checkorder() at witness_checkorder+0x81e
May 19 15:08:01 freebsd8 kernel: _sx_xlock() at _sx_xlock+0x55
May 19 15:08:01 freebsd8 kernel: ufsdirhash_acquire() at ufsdirhash_acquire+0x33
May 19 15:08:01 freebsd8 kernel: ufsdirhash_add() at ufsdirhash_add+0x19
May 19 15:08:01 freebsd8 kernel: ufs_direnter() at ufs_direnter+0x88b
May 19 15:08:01 freebsd8 kernel: ufs_makeinode() at ufs_makeinode+0x31c
May 19 15:08:01 freebsd8 kernel: VOP_CREATE_APV() at VOP_CREATE_APV+0x8d
May 19 15:08:01 freebsd8 kernel: vn_open_cred() at vn_open_cred+0x3fd
May 19 15:08:01 freebsd8 kernel: kern_openat() at kern_openat+0x159
May 19 15:08:01 freebsd8 kernel: syscall() at syscall+0x1bf
May 19 15:08:01 freebsd8 kernel: Xfast_syscall() at Xfast_syscall+0xd0
May 19 15:08:01 freebsd8 kernel: --- syscall (5, FreeBSD ELF64, open), rip = 0x800e23e2c, rsp = 0x7fffffffe688, rbp = 0x124 ---
May 19 15:22:05 freebsd8 kernel: kldload: unexpected relocation type 10
May 19 15:22:05 freebsd8 last message repeated 11 times
May 19 15:22:05 freebsd8 kernel: vboxdrv: fAsync=0 offMin=0x1d8 offMax=0x950
May 20 08:56:26 freebsd8 syslogd: kernel boot file is /boot/kernel/kernel
May 20 08:56:26 freebsd8 kernel: Copyright (c) 1992-2009 The FreeBSD Project.
Ma

That is a FreeBSD LOR, that can you ignore :)

Post by Ismail YENIGUL

Post by Ismail YENIGUL
Hello Martin,
I installed http://people.freebsd.org/~miwi/vbox/virtualbox_3.tgz
on FreeBSD 8 snapshot-200905 amd64.
It compiled successfully, But When I create a virtual server (Redhat) and click on start,
FreeBSD 8 crashed. I am not in the office at the moment. I will
check the error messages tomorrow.
Thaks.

Post by Sergey V. Dyatko
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Post by subbsd
Hello

Post by Martin Wilke
Howdy ..
Next run,
We updated the port to 2.2.2r19801.
The Patch files/patch-amd64-r0-exec-alloc
was removed in favor of a similar fix
commited to upstream. Also was fixed a
bug on HEAD which should be fix the Kernel
crash. Please test test test .. :-)
PS: Yes this run is for AMD64 and HEAD
users!
http://people.freebsd.org/~miwi/vbox/virtualbox_3.tgz
Happy Testing!

I've try to compile this port on i386/8-CURRENT ( kern.osreldate: 800087 ) and

please update your src/kernel and rebuild vbox

Post by subbsd
--
/* ... */
kBuild: xsltproc VBoxSVC -
/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/src/VBox/Main/idl/xpidl.xsl
kBuild: Compiling RuntimeR3 -
/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/src/VBox/Runtime/common/err/errmsg.cpp
kBuild: Compiling RuntimeR3 -
/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/src/VBox/Runtime/common/err/errmsgxpcom.cpp
kBuild: Linking RuntimeR0
kBuild: Linking RuntimeGC
kBuild: Linking RuntimeEFCPP
kBuild: Linking RuntimeR3NoCRTGCC
kBuild: Compiling RuntimeR0Drv -
/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/src/VBox/Runtime/common/alloc/alloc.cpp
kBuild: Linking VMMR3
kBuild: Compiling PcBiosBin -
/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/out/freebsd.x86/release/obj/PcBiosBin/_rombios_.c
error: need ';'
error: need variable name
kmk[2]: ***
[/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/out/freebsd.x86/release/obj/PcBiosBin/rombios0.s]
Error 1
kmk[2]: *** Deleting file
`/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801/out/freebsd.x86/release/obj/PcBiosBin/rombios0.s'
kmk[2]: *** Waiting for unfinished jobs....
kmk[2]: Leaving directory
`/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801'
kmk[2]: Entering directory
`/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801'
kmk[2]: *** Exiting with status 2
kmk[1]: *** [pass_libraries_this] Error 2
kmk[1]: Leaving directory
`/usr/ports/emulators/virtualbox/work/virtualbox-2.2.2r19801'
kmk: *** [pass_libraries_order] Error 2
*** Error code 2
Stop in /usr/ports/emulators/virtualbox.
--
DISABLE_MAKE_JOBS=yes options is not influence
static char bios_cvs_version_string[] = "VirtualBox " "2.2.51_OSE";
but ';' symbol is presents.
_______________________________________________
http://lists.freebsd.org/mailman/listinfo/freebsd-current

--
Ismail YENIGUL
Endersys Ltd.
Genel Koordinatör / General Coordinator
Phone :[phone] | Mobile:[phone]
Fax :[phone] | web: http://www.endersys.com.tr
Endersys blog aç?ld?. http://blog.endersys.com

- --

+-----------------------+-------------------------------+
| PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de |
| ICQ : 169139903 | Mail : miwi(at)FreeBSD.org |
+-----------------------+-------------------------------+
| Mess with the Best, Die like the Rest! |
+-----------------------+-------------------------------+

[Ryan Stone]

unexpected relocation type 10 is the error that you'll get if you try to
load a kernel module with debug symbols into an amd64 kernel. You have to
load a stripped kernel module.

Ryan Stone

[Ismail YENIGUL]

Hello Ryan,

Thanks for the info.

Anyway, I would like to test virtualbox and give feedback.
FreeBSD crashes, when I start a guest operating system.


Thanks.

Post by Ryan Stone
unexpected relocation type 10 is the error that you'll get if you try to
load a kernel module with debug symbols into an amd64 kernel. You have to
load a stripped kernel module.
Ryan Stone
_______________________________________________
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to

[Olivier SMEDTS]

Post by Sergey V. Dyatko
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Howdy ..
Next run,
We updated the port to 2.2.2r19801.
The Patch files/patch-amd64-r0-exec-alloc
was removed in favor of a similar fix
commited to upstream. Also was fixed a
bug on HEAD which should be fix the Kernel
crash. Please test test test .. :-)
PS: Yes this run is for AMD64 and HEAD
   users!
http://people.freebsd.org/~miwi/vbox/virtualbox_3.tgz
Happy Testing!

Tested, installed fine but I can only run guests without VT (so only 32-bits).
I'm using latest -CURRENT on amd64 (Intel Core2 Quad Q9450).
Seems to work fine (but slowly) for 32-bit guests without VT.

Thanks !

Post by Sergey V. Dyatko
- --
+-----------------------+-------------------------------+
|  PGP    : 0xB1E6FCE9  |  Jabber : miwi(at)BSDCrew.de  |
|  ICQ    : 169139903   |  Mail   : miwi(at)FreeBSD.org |
+-----------------------+-------------------------------+
|       Mess with the Best, Die like the Rest!          |
+-----------------------+-------------------------------+
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (FreeBSD)
iEYEARECAAYFAkoSeCYACgkQdLJIhLHm/OkuOQCfVzr7yTxydbo6npBgO2LyZNk1
RpUAnAmxjlHTBsM8pJ5SIiPIqQRCWElu
=LoBM
-----END PGP SIGNATURE-----
_______________________________________________
http://lists.freebsd.org/mailman/listinfo/freebsd-current

[Harald Schmalzbauer]

Post by Martin Wilke
Howdy ..
Next run,
We updated the port to 2.2.2r19801.
The Patch files/patch-amd64-r0-exec-alloc
was removed in favor of a similar fix
commited to upstream. Also was fixed a
bug on HEAD which should be fix the Kernel
crash. Please test test test .. :-)
PS: Yes this run is for AMD64 and HEAD
users!
http://people.freebsd.org/~miwi/vbox/virtualbox_3.tgz
Happy Testing!

Howdy too :) And KUDOS to the VirtualBox porters and developers! I'm
impressed and I've been missing this way of realizing a
fashion-bits-laucher ;) (qemu is also very nice, but magnitudes slower)
One problem I recognized so far:
If I "enable additional controller", regardless which type (but I'd like
to have AHCI), the vbox doesn't start at all. Please find attached the
log file.

Of course I'd highly appreciate USB support :))

Best regards,

-Harry

[Guy Brand]

Post by Martin Wilke
We updated the port to 2.2.2r19801.

FreeBSD 8.0-CURRENT #12: Wed May 13 11:22:30 CEST 2009 amd64 +
virtualbox-2.2.2r19852 works like a charm. I only had to disable the
VT/AMD option from the setting as already pointed in this list.

Thank you for your work!

[Mickael Torres]

Post by Sergey V. Dyatko
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
We rolled a new tarball with the patch from Juergen Lock [1]
with a posible fix for AMD64 users, tested on 3 machines
which now works without problems. Many Thanks to him for
his nice work!
http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz
Martin

Tested on a 7-stable/amd64 from yesterday. Works great with VT with
win64 / openbsd64 guests. Thanks :)

Mike.

Post by Sergey V. Dyatko
- --
+-----------------------+-------------------------------+
| PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de |
| ICQ : 169139903 | Mail : miwi(at)FreeBSD.org |
+-----------------------+-------------------------------+
| Mess with the Best, Die like the Rest! |
+-----------------------+-------------------------------+
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (FreeBSD)
iEUEARECAAYFAkoQUtAACgkQdLJIhLHm/OlY2QCg1KZW2YCvE1VhqKgSQ/xhjKIx
U60Al2UMniKg+KvQ6m9RcP92eOMddfQ=
=kB6c
-----END PGP SIGNATURE-----
_______________________________________________
http://lists.freebsd.org/mailman/listinfo/freebsd-current
"

[Michael Butler]

Post by Martin Wilke
http://people.freebsd.org/~miwi/vbox/virtualbox_3.tgz

With the latest tarball, I still don't see my DVD in the drop-down list
even though I have tweaked the devd.conf file such that ..

***@toshi:/home/imb> ll /dev/*cd*
crw-rw-rw- 1 root operator 0, 97 May 19 10:55 /dev/acd0
crw-rw-rw- 1 root operator 0, 104 May 19 10:55 /dev/cd0
lrwxr-xr-x 1 root wheel 3 May 19 10:55 /dev/cdrom -> cd0

This is on a Toshiba Satellite with today's -current ..

***@toshi:/home/imb> uname -a
FreeBSD toshi.auburn.protected-networks.net 8.0-CURRENT FreeBSD
8.0-CURRENT #89: Tue May 19 07:29:32 EDT 2009
***@toshi.auburn.protected-networks.net:/usr/obj/usr/src/sys/TOSHI i386


Is this expected?

Michael

[Martin Wilke]

Post by Sergey V. Dyatko
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Post by Martin Wilke
http://people.freebsd.org/~miwi/vbox/virtualbox_3.tgz

With the latest tarball, I still don't see my DVD in the drop-down list
even though I have tweaked the devd.conf file such that ..
crw-rw-rw- 1 root operator 0, 97 May 19 10:55 /dev/acd0
crw-rw-rw- 1 root operator 0, 104 May 19 10:55 /dev/cd0
lrwxr-xr-x 1 root wheel 3 May 19 10:55 /dev/cdrom -> cd0
This is on a Toshiba Satellite with today's -current ..
FreeBSD toshi.auburn.protected-networks.net 8.0-CURRENT FreeBSD
8.0-CURRENT #89: Tue May 19 07:29:32 EDT 2009

at the moment a now issus we will take a look later.

All in one seems that by most peoples now vbox works \o/

Post by Sergey V. Dyatko
Is this expected?
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (FreeBSD)
iEYEARECAAYFAkoTCEIACgkQQv9rrgRC1JIsXACfQiATgNTSkjmrg1O/f5XMXXoc
gc8AoMBQARVPh9UNxetXuGHaMXkd3oL4
=tdVE
-----END PGP SIGNATURE-----

- --

+-----------------------+-------------------------------+
| PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de |
| ICQ : 169139903 | Mail : miwi(at)FreeBSD.org |
+-----------------------+-------------------------------+
| Mess with the Best, Die like the Rest! |
+-----------------------+-------------------------------+

[Gustau Pérez]

Post by Martin Wilke

Post by Sergey V. Dyatko
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Post by Martin Wilke
http://people.freebsd.org/~miwi/vbox/virtualbox_3.tgz

With the latest tarball, I still don't see my DVD in the drop-down list
even though I have tweaked the devd.conf file such that ..
crw-rw-rw- 1 root operator 0, 97 May 19 10:55 /dev/acd0
crw-rw-rw- 1 root operator 0, 104 May 19 10:55 /dev/cd0
lrwxr-xr-x 1 root wheel 3 May 19 10:55 /dev/cdrom -> cd0
This is on a Toshiba Satellite with today's -current ..
FreeBSD toshi.auburn.protected-networks.net 8.0-CURRENT FreeBSD
8.0-CURRENT #89: Tue May 19 07:29:32 EDT 2009

i386
at the moment a now issus we will take a look later.
All in one seems that by most peoples now vbox works \o/

Hi,

as I reported this morning, for me is not working. My system is a
DELL D630 laptop with 3Gb of RAM. i386/CURRENT update today :

FreeBSD gusiport 8.0-CURRENT FreeBSD 8.0-CURRENT #41: Tue May 19
14:24:05 CEST 2009
***@gusiport:/usr/obj/usr/src/sys/CUSTOM i386

Last version fixed the problem with the kernel module not being
detected the second time vbox is run, but I still have vbox booting the
virtual machine in wit a gray screen. I've observed the machine is
supposed to be running, but making top shows no activity. Also tried
VBoxSDL -startvm win (win is the id given to the vmachine, yes I know,
it took me little time to give it a name :) ) and the virtual machine
shows a black screen. No CPU activity at all. Tried disabling VT-x/AMD-v
extensions (the laptop supports VT-x) still no go.

Anything I can try ?

Thanks,

Gus

[Henri Hennebert]

Post by Gustau Pérez

Post by Martin Wilke

Post by Sergey V. Dyatko
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Post by Martin Wilke
http://people.freebsd.org/~miwi/vbox/virtualbox_3.tgz

With the latest tarball, I still don't see my DVD in the drop-down list
even though I have tweaked the devd.conf file such that ..
crw-rw-rw- 1 root operator 0, 97 May 19 10:55 /dev/acd0
crw-rw-rw- 1 root operator 0, 104 May 19 10:55 /dev/cd0
lrwxr-xr-x 1 root wheel 3 May 19 10:55 /dev/cdrom -> cd0
This is on a Toshiba Satellite with today's -current ..
FreeBSD toshi.auburn.protected-networks.net 8.0-CURRENT FreeBSD
8.0-CURRENT #89: Tue May 19 07:29:32 EDT 2009

i386
at the moment a now issus we will take a look later.
All in one seems that by most peoples now vbox works \o/

Hi,
as I reported this morning, for me is not working. My system is a
FreeBSD gusiport 8.0-CURRENT FreeBSD 8.0-CURRENT #41: Tue May 19
14:24:05 CEST 2009
Last version fixed the problem with the kernel module not being
detected the second time vbox is run, but I still have vbox booting the
virtual machine in wit a gray screen. I've observed the machine is
supposed to be running, but making top shows no activity. Also tried
VBoxSDL -startvm win (win is the id given to the vmachine, yes I know,
it took me little time to give it a name :) ) and the virtual machine
shows a black screen. No CPU activity at all. Tried disabling VT-x/AMD-v
extensions (the laptop supports VT-x) still no go.

Same problem here

FreeBSD chamonix.restart.bel 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Mon May
18 16:47:40 CEST 2009
***@chamonix.restart.bel:/usr/obj/usr/src/sys/CHAMONIX i386

I am using nvidia-driver-180.44

(II) LoadModule: "nvidia"
(II) Loading /usr/local/lib/xorg/modules/drivers//nvidia_drv.so
(II) Module nvidia: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Video Driver
(II) NVIDIA dlloader X Driver 180.44 Mon Mar 23 05:42:54 PST 2009
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
<clip>
(II) NVIDIA(0): NVIDIA GPU Quadro NVS 285 (NV44GL) at PCI:3:0:0 (GPU-0)
(--) NVIDIA(0): Memory: 131072 kBytes
(--) NVIDIA(0): VideoBIOS: 05.44.02.64.03
(II) NVIDIA(0): Detected PCI Express Link width: 1X
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(--) NVIDIA(0): Connected display device(s) on Quadro NVS 285 at PCI:3:0:0:
(--) NVIDIA(0): FUS P22W-5 ECO (CRT-0)
(--) NVIDIA(0): FUS P22W-5 ECO (CRT-0): 400.0 MHz maximum pixel clock
(II) NVIDIA(0): Assigned Display Device: CRT-0
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0): "1680x1050"
(II) NVIDIA(0): Virtual screen size determined to be 1680 x 1050
(--) NVIDIA(0): DPI set to (90, 88); computed from "UseEdidDpi" X config
(--) NVIDIA(0): option
(==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.

Henri

Post by Gustau Pérez
Anything I can try ?
Thanks,
Gus

[Gustau Pérez]

Post by Henri Hennebert

Post by Gustau Pérez
Last version fixed the problem with the kernel module not being
detected the second time vbox is run, but I still have vbox booting the
virtual machine in wit a gray screen. I've observed the machine is
supposed to be running, but making top shows no activity. Also tried
VBoxSDL -startvm win (win is the id given to the vmachine, yes I know,
it took me little time to give it a name :) ) and the virtual machine
shows a black screen. No CPU activity at all. Tried disabling
VT-x/AMD-v
extensions (the laptop supports VT-x) still no go.

Same problem here
FreeBSD chamonix.restart.bel 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Mon
May 18 16:47:40 CEST 2009
I am using nvidia-driver-180.44
(II) LoadModule: "nvidia"
(II) Loading /usr/local/lib/xorg/modules/drivers//nvidia_drv.so
(II) Module nvidia: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Video Driver
(II) NVIDIA dlloader X Driver 180.44 Mon Mar 23 05:42:54 PST 2009
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
<clip>
(II) NVIDIA(0): NVIDIA GPU Quadro NVS 285 (NV44GL) at PCI:3:0:0 (GPU-0)
(--) NVIDIA(0): Memory: 131072 kBytes
(--) NVIDIA(0): VideoBIOS: 05.44.02.64.03
(II) NVIDIA(0): Detected PCI Express Link width: 1X
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(--) NVIDIA(0): FUS P22W-5 ECO (CRT-0)
(--) NVIDIA(0): FUS P22W-5 ECO (CRT-0): 400.0 MHz maximum pixel clock
(II) NVIDIA(0): Assigned Display Device: CRT-0
(II) NVIDIA(0): "1680x1050"
(II) NVIDIA(0): Virtual screen size determined to be 1680 x 1050
(--) NVIDIA(0): DPI set to (90, 88); computed from "UseEdidDpi" X config
(--) NVIDIA(0): option
(==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
Henri

Hi,

I tried starting vbox with current with VBoxSDL --startvm win (win
is the id I gave to the virtual machine). With that, a black window
appears, but the "Press F12 ..." messages doesn't appear. I checked
with top, and vbox is doing nothing.

With the same machine (Dell D630) and using 7.2-RELEASE (with nvidia
driver loader, sound, etc ...) , it works (and it is pretty fast,
don't know how could I live with qemu).

So that makes me think either it is a problem with some config file
(/boot/loader.conf, /etc/syslog.conf, for tunning purposes) or maybe
my version of current. For /boot/loader.conf and /etc/syslog.conf, I
removed the changes I made related to kern.maxdsiz and others, left
kern.hz=100, removed kqemu and aio. I only have usb, ehci and friends,
linux, nvidia and other hardware modules that shouldn't be the source
of the problem.

Can anyone with current and vbox working tolds us when you guys
updated your sources ? Anyone has an idea what to check, hack ?

Regards and thanks,

Gusi


- --
PGP KEY : http://www-entel.upc.edu/gus/gus.asc

[Henri Hennebert]

Post by Henri Hennebert

Post by Gustau Pérez

Post by Martin Wilke

Post by Sergey V. Dyatko
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Post by Martin Wilke
http://people.freebsd.org/~miwi/vbox/virtualbox_3.tgz

With the latest tarball, I still don't see my DVD in the drop-down list
even though I have tweaked the devd.conf file such that ..
crw-rw-rw- 1 root operator 0, 97 May 19 10:55 /dev/acd0
crw-rw-rw- 1 root operator 0, 104 May 19 10:55 /dev/cd0
lrwxr-xr-x 1 root wheel 3 May 19 10:55 /dev/cdrom -> cd0
This is on a Toshiba Satellite with today's -current ..
FreeBSD toshi.auburn.protected-networks.net 8.0-CURRENT FreeBSD
8.0-CURRENT #89: Tue May 19 07:29:32 EDT 2009

i386
at the moment a now issus we will take a look later.
All in one seems that by most peoples now vbox works \o/

Hi,
as I reported this morning, for me is not working. My system is a
FreeBSD gusiport 8.0-CURRENT FreeBSD 8.0-CURRENT #41: Tue May 19
14:24:05 CEST 2009
Last version fixed the problem with the kernel module not being
detected the second time vbox is run, but I still have vbox booting the
virtual machine in wit a gray screen. I've observed the machine is
supposed to be running, but making top shows no activity. Also tried
VBoxSDL -startvm win (win is the id given to the vmachine, yes I know,
it took me little time to give it a name :) ) and the virtual machine
shows a black screen. No CPU activity at all. Tried disabling VT-x/AMD-v
extensions (the laptop supports VT-x) still no go.

Same problem here
FreeBSD chamonix.restart.bel 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Mon May
18 16:47:40 CEST 2009
I am using nvidia-driver-180.44
(II) LoadModule: "nvidia"
(II) Loading /usr/local/lib/xorg/modules/drivers//nvidia_drv.so
(II) Module nvidia: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Video Driver
(II) NVIDIA dlloader X Driver 180.44 Mon Mar 23 05:42:54 PST 2009
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
<clip>
(II) NVIDIA(0): NVIDIA GPU Quadro NVS 285 (NV44GL) at PCI:3:0:0 (GPU-0)
(--) NVIDIA(0): Memory: 131072 kBytes
(--) NVIDIA(0): VideoBIOS: 05.44.02.64.03
(II) NVIDIA(0): Detected PCI Express Link width: 1X
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(--) NVIDIA(0): FUS P22W-5 ECO (CRT-0)
(--) NVIDIA(0): FUS P22W-5 ECO (CRT-0): 400.0 MHz maximum pixel clock
(II) NVIDIA(0): Assigned Display Device: CRT-0
(II) NVIDIA(0): "1680x1050"
(II) NVIDIA(0): Virtual screen size determined to be 1680 x 1050
(--) NVIDIA(0): DPI set to (90, 88); computed from "UseEdidDpi" X config
(--) NVIDIA(0): option
(==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
Henri

I Try on FreeBSD-STABLE and get a black screen.

I reboot without nvidia driver and with vboxdrv loaded at boot.

I use vesa driver for xorg

no change, a black screen.

I try VirtualBox --startvm pcbsd --rmode image

And still got a black screen.

Henri

Post by Henri Hennebert

Post by Gustau Pérez
Anything I can try ?
Thanks,
Gus

_______________________________________________
http://lists.freebsd.org/mailman/listinfo/freebsd-current

[Paul Schenkeveld]

Post by Martin Wilke
Howdy Guys,
After the announcement from Alexander Eichner about
Virtualbox on FreeBSD, we started the work on a port
for FreeBSD. Now we think that we solved the most
problems and are ready for the first Call for Testing.

Many thanks!

So far I had a short ride but vbox fails every time after the first try.

If the following can help you debug/improve, read on, otherwise I'll just
wait for a more stable version. If you want me to test anything or send
crash dump, please let me know.

- Running 7.2-STABLE i386 as of Thu May 14 19:28:42 CEST 2009 on Dell
Precision M4300 notebook (Intel T7500 Core-2 Duo, 2.2GHz VT-x enabled,
3 GB RAM)
- /proc is mounted
- Downloaded vbox port yesterday evening (~ 18:50 UTC)
- make -s install clean (watch many qt4 dependencies, dev86 and vbox
install)
- kldload vboxdrv (OK, even with X running)
- $ VirtualBox
- Created a guest with 512MB RAM, 2GB IDE pri master disk
- Could not choose bridged network, so fell back to NAT
- Installed FreeBSD 7.1 from 7.1 release DVD iso, feels very good, nice
performance!
- Could not NFS mount anything, vbox NAT translates NFS client to
unprivileged port
- Wanted to add second virtual disk to hold /usr/src and /usr/obj so
stopped vbox, added virtual disk and tried to restart guest many
times, no luck
- Rebooted computer
- kldload vboxdrv (with X11 running), system panics
- Reboot and load vboxdrv from loader works
- Trying to start existing vbox guest always fails, sometimes with error
popup:
Unknown error creating VM (VERR_PDM_DEVICE_NOT_FOUND).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: Console
Interface: IConsole {a7f17a42-5b64-488d-977b-4b2c639ada27}
but mostly I only see the console window appear and disappear within
a second (/var/log/messages: pid 1283 (VirtualBox), uid 2506: exited
on signal 11
- Creating a new guest (in case disk image of old guest is damaged)
never starts (shows same symptoms as original guest)

Thanks again for all the good work!

-- Paul Schenkeveld

[Hyogeol Lee]

Post by Martin Wilke
Howdy ..
Next run,
We updated the port to 2.2.2r19801.
The Patch files/patch-amd64-r0-exec-
alloc
was removed in favor of a similar fix
commited to upstream. Also was fixed a
bug on HEAD which should be fix the Kernel
crash. Please test test test .. :-)
PS: Yes this run is for AMD64 and HEAD
users!
http://people.freebsd.org/~miwi/vbox/virtualbox_3.tgz
<http://people.freebsd.org/%7Emiwi/vbox/virtualbox_3.tgz>
Happy Testing!

Hi,

I'm using -current/amd64 and it works fine with new port.

But it is need to *turn off VT-x/AMD-V* to run VM.

I could not run VM when I turn on VT-x/AMD-V.
(I'm using VT-X supported processor, Q9450.)

Anyway, nice works!

Regards,
- ----
Hyogeol Lee
***@gmail.com