Re: VirtualBox kernel modules
On Thu, Jan 10, 2013 at 10:31 PM, Warren Block wbl...@wonkity.com wrote: On Thu, 10 Jan 2013, Ryan Stone wrote: As I recall, a make installkernel will first mv /boot/kernel /boot/kernel.old Should ports put modules in /boot/modules to avoid this kind of thing? I thought so, but the Porter's Handbook doesn't say anything about it. multimedia/cuse4bsd-kmod installs a module there. The previous versions of this port did indeed install the modules into /boot/modules; only with the most recent version (4.2.6) has this changed. For example: $ tar tvf /usr/ports/packages/All/virtualbox-ose-kmod-4.1.22.txz [...] -r-xr-xr-x 0 root wheel 297288 Sep 19 09:19 /boot/modules/vboxdrv.ko -r-xr-xr-x 0 root wheel9544 Sep 19 09:19 /boot/modules/vboxnetadp.ko -r-xr-xr-x 0 root wheel 26648 Sep 19 09:19 /boot/modules/vboxnetflt.ko [...] $ tar tvf /usr/ports/packages/All/virtualbox-ose-kmod-4.2.6.txz [...] -r-xr-xr-x 0 root wheel 337912 Jan 6 13:13 /boot/kernel/vboxdrv.ko -r-xr-xr-x 0 root wheel9696 Jan 6 13:13 /boot/kernel/vboxnetadp.ko -r-xr-xr-x 0 root wheel 26808 Jan 6 13:13 /boot/kernel/vboxnetflt.ko [...] I don't know WHY this changed, or if it was just an oversight during the update -- perhaps it by (re)design... -Brandon ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: [Call for Testers] VirtualBox 4.2.4
On Thu, Nov 8, 2012 at 8:12 AM, Bernhard Fröhlich de...@freebsd.org wrote: On Wed, Nov 7, 2012 at 4:21 AM, Brandon Gooch jamesbrandongo...@gmail.com wrote: On Tue, Oct 30, 2012 at 2:16 AM, Bernhard Fröhlich de...@freebsd.org wrote: Hi virtualbox users! This is again a call for testers to get some feedback before we commit VirtualBox 4.2 to the portstree. If you already run VirtualBox 4.2.0 you should definitely update to 4.2.4 because they fixed quite a few serious bugs upstream. Our plan is still to commit 4.2 to the portstree as soon as FreeBSD 9.1 is out the door. If you are interested in helping with virtualbox maintenance and development or have noticed a bug you can easily find us on IRC. Please update devel/kBuild-devel before updating any of the virtualbox ports and ensure that your Kernel sources match your running kernel before building the virtualbox-ose-kmod port. Changes since VirtualBox 4.1: https://www.virtualbox.org/wiki/Changelog VirtualBox 4.2.4 and 4.1.22 (legacy) Ports: http://people.freebsd.org/~decke/virtualbox/virtualbox-cft-4.2.4-20121030.tar.gz IRC: #freebsd-vbox on Freenode Bernhard on behalf of the new VirtualBox on FreeBSD Team! -- Bernhard Froehlich http://www.bluelife.at/ I've updated to 4.2.4 on my system running HEAD. I've hit one annoying issue. I've been running the 4.2.0 Call for Testing for a while now, and it worked very well. After updating to 4.2.4 and updating the guest additions on several Linux guests, I've found that 3D acceleration is broken. The guest on which I didn't update the guest additions (so it's still running version 4.2.0 guest additions), 3D acceleration works great. This is a nuisance on systems which had some form of compositing enabled (e.g. compiz) because the login process (GDM in this case) just spins indefinitely waiting on (I presume) the window manager to fire up. Anyone else seeing this? Hm haven't checked that recently. The only thing that changed between 4.2.0 and 4.2.2 from FreeBSD side was that we have enabled DRM in the additions for FreeBSD guests but that should not affect Linux guests at all. I will check if I can reproduce that. -- Bernhard Froehlich http://www.bluelife.at/ I downgraded the guest additions from 4.2.4 to 4.2.0 and functionality is restored. This seems to be an issue with other host environments as well. Here's an example: https://forums.virtualbox.org/viewtopic.php?f=3t=52215 -Brandon ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: Virtualbox 4.2?
On Sat, Sep 22, 2012 at 3:54 PM, Mike Manilone crtm...@gmx.us wrote: Hi, all! I found that VirtualBox in ports is only at version 4.1.x. I'm using RemoteBox (here's already a port in PR) which requires VirtualBox 4.2. Then all the menus/buttons turn grey and disabled. I'm just wondering how soon 4.2 will arrive in FreeBSD. Any plans? Sincerely, Mike Manilone Bernhard just sent out the Call for Testing: http://lists.freebsd.org/pipermail/freebsd-emulation/2012-September/010010.html I've been running it for a few days, so far, so good! -Brandon ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
VirtualBox 4.1.16 on 10-CURRENT: /usr/X11R6/lib/libGL.so: undefined reference
I'm having issues compiling VirtualBox 4.1.16; here is the relevant
snip from the configure.log file:
$ cat /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.16/configure.log
[SNIP]
* Checking Mesa / GLU *
compiling the following source file:
#include cstdio
#include X11/Xlib.h
#include GL/glx.h
#include GL/glu.h
extern C int main(void)
{
Display *dpy;
int major, minor;
dpy = XOpenDisplay(NULL);
if (dpy)
{
Bool glx_version = glXQueryVersion(dpy, major, minor);
XCloseDisplay(dpy);
if (glx_version)
{
printf(found version %u.%u, OK.\n, major, minor);
return 0;
}
}
printf(found (inactive), OK.\n);
return 0;
}
using the following command line:
c++ -g -O -Wall -o
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.16/.tmp_out
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.16/.tmp_src.cc
-L/usr/X11R6/lib -L/usr/X11R6/lib64 -L/usr/local/lib -lXext -lX11
-lGL -I/usr/local/include
/usr/X11R6/lib/libGL.so: undefined reference to `_nv017tls'
/usr/X11R6/lib/libGL.so: undefined reference to `_nv014tls'
I running:
FreeBSD m6500.local 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r236044: Sat
May 26 03:04:16 CDT 2012
root@m6500.local:/usr/obj/usr/src/sys/DELL_M6500 amd64
xorg-7.5.2
xorg-server-1.7.7_5,1
nvidia-driver-295.49
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: [PATCH] VirtualBox 4.1.8 kmod panic with VIMAGE kernel
On Sat, Mar 10, 2012 at 3:00 AM, Bernhard Froehlich de...@freebsd.org wrote:
On 10.03.2012 05:42, Brandon Gooch wrote:
It's my guess that not many people are running VirtualBox on a
VIMAGE-enabled kernel. However, for those of us who do (just me?),
the attached patch is required to prevent a panic when running
VirtualBox in such an environment. The patch belongs to the
emulators/virtualbox-ose-kmod port.
--- src/VBox/HostDrivers/VBoxNetAdp/VBoxNetAdp.c.orig 2011-12-19
07:01:06.0 -0600
+++ src/VBox/HostDrivers/VBoxNetAdp/VBoxNetAdp.c 2011-12-26
14:54:27.0 -0600
@@ -1189,6 +1189,7 @@
int vboxNetAdpInit(void)
{
unsigned i;
+ PVBOXNETADP pVboxnet0;
/*
* Init common members and call OS-specific init.
*/
@@ -1201,7 +1202,8 @@
vboxNetAdpOsInit(g_aAdapters[i]);
}
- return VINF_SUCCESS;
+ /* Create vboxnet0 */
+ return vboxNetAdpCreate(pVboxnet0, NULL);
}
/**
If there is a more appropriate fix, please help me find it, otherwise,
it would be great to have this committed!
Sorry, that I haven't committed the patch until now. Do you agree that
this patch is licensed under MIT License so I can send it upstream?
Yes, absolutely. Do with it as you please...
What I found when tracking this down led to this commit:
https://www.virtualbox.org/changeset/35785/vbox
https://www.virtualbox.org/browser/vbox/trunk/src/VBox/HostDrivers/VBoxNetAdp/VBoxNetAdp.c?rev=35785
I'm not sure how the initial VBox network adapter is supposed to be
created; maybe it should be deferred to the OS-specific init process
(in VBoxNetAdp-freebsd.c)? Trouble is, not sure how to do that
exactly, but anyway it seems more like a bug that was introduced.
Attempting to push this upstream will reveal something I imagine :)
Current VIMAGE support is only for vboxnetflt and you are touching
vboxnetadp so that is probably why nobody used it before. Have you
tested it with a non VIMAGE kernel?
I tested it with GENERIC, a custom kernel WITHOUT VIMAGE, and a custom
kernel WITH VIMAGE. I tested on 9-STABLE (from this month) and now
10-CURRENT.
--
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: [PATCH] VirtualBox 4.1.8 kmod panic with VIMAGE kernel
On Sat, Mar 10, 2012 at 9:50 AM, Brandon Gooch
jamesbrandongo...@gmail.com wrote:
On Sat, Mar 10, 2012 at 3:00 AM, Bernhard Froehlich de...@freebsd.org wrote:
On 10.03.2012 05:42, Brandon Gooch wrote:
It's my guess that not many people are running VirtualBox on a
VIMAGE-enabled kernel. However, for those of us who do (just me?),
the attached patch is required to prevent a panic when running
VirtualBox in such an environment. The patch belongs to the
emulators/virtualbox-ose-kmod port.
--- src/VBox/HostDrivers/VBoxNetAdp/VBoxNetAdp.c.orig 2011-12-19
07:01:06.0 -0600
+++ src/VBox/HostDrivers/VBoxNetAdp/VBoxNetAdp.c 2011-12-26
14:54:27.0 -0600
@@ -1189,6 +1189,7 @@
int vboxNetAdpInit(void)
{
unsigned i;
+ PVBOXNETADP pVboxnet0;
/*
* Init common members and call OS-specific init.
*/
@@ -1201,7 +1202,8 @@
vboxNetAdpOsInit(g_aAdapters[i]);
}
- return VINF_SUCCESS;
+ /* Create vboxnet0 */
+ return vboxNetAdpCreate(pVboxnet0, NULL);
}
/**
If there is a more appropriate fix, please help me find it, otherwise,
it would be great to have this committed!
Sorry, that I haven't committed the patch until now. Do you agree that
this patch is licensed under MIT License so I can send it upstream?
Yes, absolutely. Do with it as you please...
What I found when tracking this down led to this commit:
https://www.virtualbox.org/changeset/35785/vbox
https://www.virtualbox.org/browser/vbox/trunk/src/VBox/HostDrivers/VBoxNetAdp/VBoxNetAdp.c?rev=35785
I'm not sure how the initial VBox network adapter is supposed to be
created; maybe it should be deferred to the OS-specific init process
(in VBoxNetAdp-freebsd.c)? Trouble is, not sure how to do that
exactly, but anyway it seems more like a bug that was introduced.
Attempting to push this upstream will reveal something I imagine :)
Current VIMAGE support is only for vboxnetflt and you are touching
vboxnetadp so that is probably why nobody used it before. Have you
tested it with a non VIMAGE kernel?
I tested it with GENERIC, a custom kernel WITHOUT VIMAGE, and a custom
kernel WITH VIMAGE. I tested on 9-STABLE (from this month) and now
10-CURRENT.
--
Bernhard Froehlich
http://www.bluelife.at/
Y'know, I think the real problem is that a VIMAGE-enabled kernel
doesn't allow for the creation of new interfaces after boot.
At least it was that way back in late 2010 when I was using a USB
network device...
So this is at BEST an attempt at a work-around, which I suspect will
fail in any case more complicated than VirtualBox running in vnet0
with 1 network interface -- but I'm not totally sure I even understand
the way the VBoxNetFlt and VBoxNetAdp drivers work!
-Brandon
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: VirtualBox blueports repository moved to redports.org
On Tue, Dec 20, 2011 at 6:42 AM, Bernhard Froehlich de...@freebsd.org wrote: Hi VirtualBox Testers! I think it's the right time now to announce that the virtualbox blueports repository that a few of you were using moved to a new location. That is because in the last few months I was heavily working on a new FreeBSD port building cluster called redports.org which is also the new environment where I usually build test all virtualbox versions and the new home of VirtualBox for FreeBSD. redports.org is the successor of the blueports repository but the history was migrated so nothing is lost. Since last week I am back to my usual virtualbox work and have already pushed a few very interesting patches from Andriy Gapon and Ed Schouten upstream. All ports are at their latest available versions now so we are _not_ lagging behind in the development repository. I just do not want to push those versions in the tree before 9.0-RELEASE is out the door. So I am currently waiting for 9.0 to be released and then I will update our virtualbox-ose ports to 4.1.8 and virtualbox-ose-legacy to 4.0.14. If you want to test the latest versions have a look at the new repository: - virtualbox-ose 4.1.8 (0 days old) - virtualbox-ose-devel 4.1.51r39575 (10 days old) - virtualbox-ose-legacy 4.0.14 (2 months old) - phpvirtualbox 4.1-5 (1 month old) Keep in mind that you need to update devel/kBuild first to compile the newer virtualbox versions. Latest kBuild is also included in the repository. For support the IRC channel and mailinglist are still the same :o) Support: IRC: #fbsd-mentors on irc.unixfreunde.de irc://irc.unixfreunde.de/fbsd-mentors Mailinglist: freebsd-emulation (at) FreeBSD.org EMail: vbox (at) FreeBSD.org Development Repository: === Browseable: http://redports.org/browser/virtualbox SVN Checkout: svn co http://svn.redports.org/virtualbox/ tar Archive of repository: http://redports.org/~virtualbox/svn.tar.bz2 RSS Feed: http://redports.org/log/virtualbox?format=rsslimit=25 -- Bernhard Froehlich http://www.bluelife.at/ First off, thank you for the tremendous quality and quantity of work you (all) are doing with VirtualBox, and the new redports.org infrastructure. The work is truly exemplary and is an awesome example of the type of dedication required for a healthy, successful open source community effort. Secondly, I did run into one issue with VirtualBox 4.1.8 and VIMAGE, which required the attached patch to function properly. I'm not sure of the implications of this apparent reversion in the vboxNetAdpInit() function, but it seems to work for me. The patch in this form or any other is of course free to use in what ever way one would please :) Thanks! ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: VirtualBox blueports repository moved to redports.org
On Mon, Dec 26, 2011 at 4:40 PM, Kevin Oberman kob6...@gmail.com wrote:
On Mon, Dec 26, 2011 at 1:30 PM, Brandon Gooch
jamesbrandongo...@gmail.com wrote:
On Tue, Dec 20, 2011 at 6:42 AM, Bernhard Froehlich de...@freebsd.org
wrote:
Hi VirtualBox Testers!
I think it's the right time now to announce that the virtualbox blueports
repository that a few of you were using moved to a new location.
That is because in the last few months I was heavily working on a new
FreeBSD port building cluster called redports.org which is also the
new environment where I usually build test all virtualbox versions and
the new home of VirtualBox for FreeBSD. redports.org is the successor
of the blueports repository but the history was migrated so nothing is
lost.
Since last week I am back to my usual virtualbox work and have already
pushed a few very interesting patches from Andriy Gapon and Ed Schouten
upstream. All ports are at their latest available versions now so we
are _not_ lagging behind in the development repository. I just do not
want to push those versions in the tree before 9.0-RELEASE is out the
door. So I am currently waiting for 9.0 to be released and then I will
update our virtualbox-ose ports to 4.1.8 and virtualbox-ose-legacy to
4.0.14.
If you want to test the latest versions have a look at the new repository:
- virtualbox-ose 4.1.8 (0 days old)
- virtualbox-ose-devel 4.1.51r39575 (10 days old)
- virtualbox-ose-legacy 4.0.14 (2 months old)
- phpvirtualbox 4.1-5 (1 month old)
Keep in mind that you need to update devel/kBuild first to compile the
newer virtualbox versions. Latest kBuild is also included in the
repository.
For support the IRC channel and mailinglist are still the same :o)
Support:
IRC: #fbsd-mentors on irc.unixfreunde.de
irc://irc.unixfreunde.de/fbsd-mentors
Mailinglist:
freebsd-emulation (at) FreeBSD.org
EMail:
vbox (at) FreeBSD.org
Development Repository:
===
Browseable:
http://redports.org/browser/virtualbox
SVN Checkout:
svn co http://svn.redports.org/virtualbox/
tar Archive of repository:
http://redports.org/~virtualbox/svn.tar.bz2
RSS Feed:
http://redports.org/log/virtualbox?format=rsslimit=25
--
Bernhard Froehlich
http://www.bluelife.at/
First off, thank you for the tremendous quality and quantity of work
you (all) are doing with VirtualBox, and the new redports.org
infrastructure. The work is truly exemplary and is an awesome example
of the type of dedication required for a healthy, successful open
source community effort.
Secondly, I did run into one issue with VirtualBox 4.1.8 and VIMAGE,
which required the attached patch to function properly. I'm not sure
of the implications of this apparent reversion in the vboxNetAdpInit()
function, but it seems to work for me.
The patch in this form or any other is of course free to use in what
ever way one would please :)
Thanks!
The patch seems to have been eaten by the mail systems. Can you either
put it in-line in a message or make sure that the attachment is
text/plain? Probably text/*, but application and most (all?) other
MIME types won't make it.
--
R. Kevin Oberman, Network Engineer
E-mail: kob6...@gmail.com
No problem:
--- src/VBox/HostDrivers/VBoxNetAdp/VBoxNetAdp.c.orig 2011-12-19
07:01:06.0 -0600
+++ src/VBox/HostDrivers/VBoxNetAdp/VBoxNetAdp.c2011-12-26
14:54:27.0 -0600
@@ -1189,6 +1189,7 @@
int vboxNetAdpInit(void)
{
unsigned i;
+PVBOXNETADP pVboxnet0;
/*
* Init common members and call OS-specific init.
*/
@@ -1201,7 +1202,8 @@
vboxNetAdpOsInit(g_aAdapters[i]);
}
-return VINF_SUCCESS;
+/* Create vboxnet0 */
+return vboxNetAdpCreate(pVboxnet0, NULL);
}
/**
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Flash Player and nspluginwrapper instability
Recently (in the last few weeks), I've lost the ability to use Flash in the browser on 9-CURRENT. Details: FreeBSD m6500.local 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r223911: Sun Jul 10 14:53:05 CDT 2011 firefox-5.0,1 nspluginwrapper-1.4.4 linux-f10-flashplugin-10.3r181.34 When a Hulu or YouTube video freezes, the audio still plays on for a while (buffered I guess), but the Flash plugin eventually crashes, leaving a gray box where the video once was. I've also tried updating the NVIDIA driver to 275.09.07, to no avail. I've tried with and without acceleration, I've built the driver with and without Linux support -- same symptoms no matter. I also tried a trick I read about in another thread, creating the file /etc/adobe/mms.cfg and setting various options off/on... Below is the console output I see when I run Firefox and I experience the issue (though I suspect the output itself is more a symptom than a diagnostic): brandon@m6500:~$ firefox *** NSPlugin Wrapper *** WARNING: browser requested NP_GetValue variable via NPP_GetValue. *** NSPlugin Wrapper *** WARNING: browser requested NP_GetValue variable via NPP_GetValue. *** NSPlugin Wrapper *** WARNING: browser requested NP_GetValue variable via NPP_GetValue. *** NSPlugin Wrapper *** WARNING: browser requested NP_GetValue variable via NPP_GetValue. *** NSPlugin Wrapper *** WARNING: browser requested NP_GetValue variable via NPP_GetValue. *** NSPlugin Wrapper *** WARNING: browser requested NP_GetValue variable via NPP_GetValue. *** NSPlugin Wrapper *** WARNING: browser requested NP_GetValue variable via NPP_GetValue. *** NSPlugin Wrapper *** WARNING: browser requested NP_GetValue variable via NPP_GetValue. *** NSPlugin Wrapper *** WARNING: browser requested NP_GetValue variable via NPP_GetValue. *** NSPlugin Wrapper *** WARNING: browser requested NP_GetValue variable via NPP_GetValue. *** NSPlugin Wrapper *** WARNING: browser requested NP_GetValue variable via NPP_GetValue. *** NSPlugin Wrapper *** WARNING: browser requested NP_GetValue variable via NPP_GetValue. *** NSPlugin Wrapper *** WARNING: browser requested NP_GetValue variable via NPP_GetValue. *** NSPlugin Wrapper *** WARNING: browser requested NP_GetValue variable via NPP_GetValue. *** NSPlugin Wrapper *** WARNING: browser requested NP_GetValue variable via NPP_GetValue. *** NSPlugin Wrapper *** WARNING: browser requested NP_GetValue variable via NPP_GetValue. *** NSPlugin Wrapper *** WARNING: browser requested NP_GetValue variable via NPP_GetValue. *** NSPlugin Wrapper *** WARNING: browser requested NP_GetValue variable via NPP_GetValue. *** NSPlugin Wrapper *** WARNING: browser requested NP_GetValue variable via NPP_GetValue. *** NSPlugin Wrapper *** WARNING: browser requested NP_GetValue variable via NPP_GetValue. *** NSPlugin Wrapper *** WARNING: browser requested NP_GetValue variable via NPP_GetValue. *** NSPlugin Wrapper *** WARNING: browser requested NP_GetValue variable via NPP_GetValue. *** NSPlugin Wrapper *** WARNING: browser requested NP_GetValue variable via NPP_GetValue. *** NSPlugin Wrapper *** WARNING: browser requested NP_GetValue variable via NPP_GetValue. *** NSPlugin Wrapper *** WARNING: browser requested NP_GetValue variable via NPP_GetValue. *** NSPlugin Wrapper *** WARNING: browser requested NP_GetValue variable via NPP_GetValue. *** NSPlugin Wrapper *** WARNING: browser requested NP_GetValue variable via NPP_GetValue. *** NSPlugin Wrapper *** WARNING: browser requested NP_GetValue variable via NPP_GetValue. *** NSPlugin Wrapper *** ERROR: NPP_WriteReady() wait for reply: Message type invalid *** NSPlugin Wrapper *** WARNING:(/usr/ports/www/nspluginwrapper/work/nspluginwrapper-1.4.4/src/npw-wrapper.c:2705):invoke_NPP_Write: assertion failed: (rpc_method_invoke_possible(plugin-connection)) *** NSPlugin Wrapper *** WARNING:(/usr/ports/www/nspluginwrapper/work/nspluginwrapper-1.4.4/src/npw-wrapper.c:2550):invoke_NPP_DestroyStream: assertion failed: (rpc_method_invoke_possible(plugin-connection)) *** NSPlugin Wrapper *** WARNING:(/usr/ports/www/nspluginwrapper/work/nspluginwrapper-1.4.4/src/npw-wrapper.c:2434):invoke_NPP_URLNotify: assertion failed: (rpc_method_invoke_possible(plugin-connection)) *** NSPlugin Wrapper *** WARNING:(/usr/ports/www/nspluginwrapper/work/nspluginwrapper-1.4.4/src/npw-wrapper.c:2478):invoke_NPP_NewStream: assertion failed: (rpc_method_invoke_possible(plugin-connection)) *** NSPlugin Wrapper *** WARNING:(/usr/ports/www/nspluginwrapper/work/nspluginwrapper-1.4.4/src/npw-wrapper.c:2434):invoke_NPP_URLNotify: assertion failed: (rpc_method_invoke_possible(plugin-connection)) Any tips on debugging this? -Brandon ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: VirtualBox + VIMAGE
On Wed, Jan 26, 2011 at 5:19 PM, Bernhard Froehlich de...@freebsd.org wrote: On Wed, 26 Jan 2011 16:25:28 +0200, Mikolaj Golub wrote: On Wed, 26 Jan 2011 10:22:40 +0100 Bernhard Froehlich wrote: BF Sounds like it's my turn now. Which FreeBSD version is required to be BF able to use it? As Bjoern noted it is for __FreeBSD_version = 800500. BF Is VIMAGE enabled per default and what happens if VIMAGE is disabled - BF does it at least build fine with that patch? We have VIMAGE disabled by default. I have added to src/VBox/HostDrivers/VBoxNetFlt/freebsd/Makefile: .if defined(VIMAGE) CFLAGS += -DVIMAGE .endif So to build the driver for VIMAGE enabled kernel one should run VIMAGE=1 make If VIMAGE variable is not defined the module for VIMAGE disabled kernel will be built. http://home.bluelife.at/patches/virtualbox-ose-kmod-devel-VIMAGE.diff I've integrated it a bit better into the VirtualBox build system, added the ports stuff and updated the patch for VirtualBox 4.0.2. It is currently unclear to me why you add VIMAGE to CFLAGS but nowhere check for VIMAGE in VBoxNetFlt-freebsd.c. Shouldn't we add a check for VIMAGE in the #if defined line or is this already done somewhere deep in the included headers? -- Bernhard Froehlich http://www.bluelife.at/ I managed to completely miss your patch posted this thread, so I just gave it a try on bluelife's virtualbox-ose-kmod svn r1239; it's working well. I've started each of my guests with bridged networking to be sure, and I see no panic (or any other anomaly) during boot or normal operation. Do you have plans on merging the patch soon? -Brandon ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: VirtualBox + VIMAGE
On Wed, Mar 2, 2011 at 2:52 PM, Bernhard Froehlich de...@bluelife.at wrote: On Wed, 02 Mar 2011 21:31:45 +0100, Bernhard Froehlich wrote: On Wed, 2 Mar 2011 08:30:01 -0600, Brandon Gooch wrote: On Wed, Jan 26, 2011 at 5:19 PM, Bernhard Froehlich de...@freebsd.org wrote: On Wed, 26 Jan 2011 16:25:28 +0200, Mikolaj Golub wrote: On Wed, 26 Jan 2011 10:22:40 +0100 Bernhard Froehlich wrote: BF Sounds like it's my turn now. Which FreeBSD version is required to be BF able to use it? As Bjoern noted it is for __FreeBSD_version = 800500. BF Is VIMAGE enabled per default and what happens if VIMAGE is disabled - BF does it at least build fine with that patch? We have VIMAGE disabled by default. I have added to src/VBox/HostDrivers/VBoxNetFlt/freebsd/Makefile: .if defined(VIMAGE) CFLAGS += -DVIMAGE .endif So to build the driver for VIMAGE enabled kernel one should run VIMAGE=1 make If VIMAGE variable is not defined the module for VIMAGE disabled kernel will be built. http://home.bluelife.at/patches/virtualbox-ose-kmod-devel-VIMAGE.diff I've integrated it a bit better into the VirtualBox build system, added the ports stuff and updated the patch for VirtualBox 4.0.2. It is currently unclear to me why you add VIMAGE to CFLAGS but nowhere check for VIMAGE in VBoxNetFlt-freebsd.c. Shouldn't we add a check for VIMAGE in the #if defined line or is this already done somewhere deep in the included headers? -- Bernhard Froehlich http://www.bluelife.at/ I managed to completely miss your patch posted this thread, so I just gave it a try on bluelife's virtualbox-ose-kmod svn r1239; it's working well. I've started each of my guests with bridged networking to be sure, and I see no panic (or any other anomaly) during boot or normal operation. Do you have plans on merging the patch soon? It's not committed because it doesn't work. What i have tested so far is with stock 8.2-REL so without VIMAGE. enabled VIMAGE option on stock 8.2-REL: bridging works fine disabled VIMAGE option on stock 8.2-REL: crashes vm with an assert Expression: !pPatchToGuestRec Location : /usr/home/decke/blueports/emulators/virtualbox-ose/work/VirtualBox-4.0.4_OSE/src/VBox/VMM/VMMR3/PATM.cpp(116 6) void patmr3AddP2GLookupRecord(VM*, _PATCHINFO*, uint8_t*, RTRCPTR, PATM_LOOKUP_TYPE, bool) It looks like that assert is not related to the VIMAGE patch. Works fine now since half an hour. Could someone with an VIMAGE kernel please test the patch? Just configure a VM with bridging and let it transfer a few bytes. Once with the option enabled and once disabled. I've had a machine running a linux guest for almost a day, bridging with a VIMAGE kernel, while capturing traffic on the virtual interface (and performing a few other tasks) -- so far, so good. No panics, and no anomalies. I surely don't know what the above mentioned assert is about; I haven't seen such a panic myself. -Brandon ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: VirtualBox + VIMAGE
On Sat, Jan 29, 2011 at 6:25 AM, Bernhard Froehlich de...@freebsd.org wrote: On Wed, 26 Jan 2011 18:23:26 -0600, Brandon Gooch wrote: On Jan 26, 2011, at 5:33 PM, Bernhard Froehlich de...@freebsd.org wrote: On Wed, 26 Jan 2011 23:27:27 +0200, Mikolaj Golub wrote: On Wed, 26 Jan 2011 14:18:03 + (UTC) Bjoern A. Zeeb wrote: BAZ On Wed, 26 Jan 2011, Mikolaj Golub wrote: On Wed, 26 Jan 2011 09:15:46 + (UTC) Bjoern A. Zeeb wrote: BAZ I think you should wrap the CURVNET changes in __FreeBSD_version BAZ checks so that the port, should it run elsewhere or on older FreeBSDs BAZ (if it runs there) not trouble people having to patch it away. BAZ #if defined(__FreeBSD_version) __FreeBSD_version = 800500 BAZ #endif BAZ might be a save bet. Thanks. Something like in the patch below? Note, I have not run this version yet. Will test it tonight or tomorrow. BAZ Well, you will need to include sys/param.h as well, and that only if BAZ you are on FreeBSD so you'll need an extra check for just that I BAZ guess. Not sure how vbox handles the all this in their guts. The file has already had '#include sys/param.h' among other includes. It just is not seen in the patch. The file is used only for FreeBSD driver so there is no need in extra check I think. I have tested this latest version of the patch. It works for me. Could someone with a vimage enabled kernel please test bridging with a stock emulators/virtualbox-ose-kmod port? There was a report that this causes a crash and it would be good to verify if that is still valid: http://lists.freebsd.org/pipermail/freebsd-emulation/2009-November/007055.html -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org It still crashes. -Brandon Thanks for testing that. Does vbox crash or the kernel? Is it possible to get a backtrace? We could try to detect if the kernel has vimage enabled (sysctl?) and also enable the vimage option per default in the port in that case. -- Bernhard Froehlich http://www.bluelife.at/ Sorry for the late reply. I think I misrepresented the situation in my previous message in this thread. I didn't have Mikolaj's patch applied when I stated virtualbox is still crashing. My bad. However, I've moved on to testing vbox from the bluelife svn repo: $ VBoxManage --version 4.0.4_OSEr70112 $ svn info Path: . URL: http://svn.bluelife.at/projects/blueports/emulators/virtualbox-ose Repository Root: http://svn.bluelife.at/projects/blueports Repository UUID: 1a7a46e7-033b-dd11-8caa-001a92771ec2 Revision: 1237 Node Kind: directory Schedule: normal Last Changed Author: decke Last Changed Rev: 1237 Last Changed Date: 2011-02-28 03:43:36 -0600 (Mon, 28 Feb 2011) The VIMAGE-enabled kernel still crashes: x300.flick.local dumped core - see /var/crash/vmcore.3 Tue Mar 1 09:07:43 CST 2011 FreeBSD x300.flick.local 9.0-CURRENT FreeBSD 9.0-CURRENT #5 r218907M: Tue Mar 1 08:32:39 CST 2011 root@x300.flick.local:/usr/obj/usr/src/sys/X300 amd64 panic: 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... Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x28 fault code = supervisor read data, page not present instruction pointer = 0x20:0x8047fcfa stack pointer = 0x28:0xff809318c650 frame pointer = 0x28:0xff809318c670 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 3064 (VBoxHeadless) Physical memory: 2007 MB Dumping 133 MB: 118 102 86 70 54 38 22 6 Reading symbols from /boot/kernel/if_em.ko...Reading symbols from /boot/kernel/if_em.ko.symbols...done. done. Loaded symbols for /boot/kernel/if_em.ko Reading symbols from /boot/kernel/if_iwn.ko...Reading symbols from /boot/kernel/if_iwn.ko.symbols...done. done. Loaded symbols for /boot/kernel/if_iwn.ko Reading symbols from /boot/kernel/snd_hda.ko...Reading symbols from /boot/kernel/snd_hda.ko.symbols...done. done. Loaded symbols for /boot/kernel/snd_hda.ko Reading symbols from /boot/kernel/sound.ko...Reading symbols from /boot/kernel/sound.ko.symbols...done. done. Loaded symbols for /boot/kernel/sound.ko Reading symbols from /boot/kernel/usb.ko...Reading symbols from /boot/kernel/usb.ko.symbols...done. done
Re: Call for Testers: VirtualBox 4.0.4
On Fri, Feb 18, 2011 at 8:17 AM, Bernhard Froehlich de...@freebsd.org wrote: Hi Testers. A few of you have probably wondered what happened to our VirtualBox efforts for FreeBSD. Well it took a bit longer then expected and a few problems were found that needed to be resolved first but most of the things are looking fine now and almost all patches have been pushed upstream with 4.0.4 so here we are now. We will continue to work on VirtualBox for FreeBSD and upstream is also very helpful to us but we could need a few more hands to better keep up with the work and especially improve and fix the Guest Additions. So if you want to help please contact us or have a look at our Todo list. This result wouldn't have been possible without the continuous help of the VirtualBox Developers and a lot of people from the FreeBSD community! (names in alphabetical order and probably missed a few, sorry for that!) - Alexander Eichner - Anonymous - Beat Gätzi - Bernhard Fröhlich - crsd - DomiX - Doug Barton - Grzegorz Blach - Hans Petter Selasky - Julian Stacey - Jung-uk Kim - Jürgen Lock - Klaus Espenlaub - Martin Wilke - Mattia Rossi - Michael Butler - Sean C. Farley - Steve Wills - tombsd - Vivek Khera - well-wisher - Wietse Venema - Yuri - many more from emulation@ Please when testing this ports backup all your virtual machines first. Also please build the port with DEBUG option enabled and send us the logfile when any VM crashes. Without them it's very hard to figure out what went wrong. Highlights with 4.0: - USB support (by Hans Petter Selasky) - Asynchronous I/O - Guest additions got startscripts and a integration into the desktop environments - www/phpvirtualbox updated to 4.0-3 Changelog for 4.0: - http://www.virtualbox.org/wiki/Changelog Short configuration help: - http://wiki.freebsd.org/VirtualBox Todo List: - http://wiki.freebsd.org/VirtualBox/ToDo http://home.bluelife.at/ports/virtualbox-cft-20110218.tar.gz Thanks and good luck, Bernhard, on behalf of the FreeBSD Vbox Team I've been testing on 8.2-RELEASE and 9-CURRENT (r218907). For the most part, it's running well. Occasionally however, my guest(s) will eat up 100% of a CPU core (or two if the guest has been configured with multiple processors). Xorg (7.5 on 8.2 and 7.5.1 Testing on -CURRENT) will be completely unresponsive as well, but I can switch to a vty and kill the VBox process (VirtualBox or VBoxSDL, whichever way I've launched it). I also have an issue on -CURRENT where I have to disable 3d acceleration for the guests to boot. I didn't capture the error, sorry about that. The entire system, world, kernel, and all ports, have been rebuilt for the -CURRENT system. The 8.2-RELEASE was built on Feb. 16, at r218738. This happens with Ubuntu 10.10 and Windows 7 guests, both newly created with version 4 and with VMs migrated from 3.12. I've rebuilt with debugging, and I'll send logs when I have 'em. Meanwhile, here's some procstat output from one of my 100% cpu-bound Ubuntu 10.10 sessions: # procstat -kk 17903 PIDTID COMM TDNAME KSTACK 17903 100152 VBoxSDL initial thread mi_switch+0x174 sleepq_catch_signals+0x2f4 sleepq_wait_sig+0x16 _sleep+0x269 do_wait+0x688 __umtx_op_wait_uint_private+0x64 syscallenter+0x331 syscall+0x4b Xfast_syscall+0xdd 17903 100356 VBoxSDL -mi_switch+0x174 sleepq_catch_signals+0x2f4 sleepq_wait_sig+0x16 _cv_wait_sig+0x128 seltdwait+0x110 poll+0x478 syscallenter+0x331 syscall+0x4b Xfast_syscall+0xdd 17903 100357 VBoxSDL -mi_switch+0x174 sleepq_catch_signals+0x2f4 sleepq_wait_sig+0x16 _sleep+0x269 do_wait+0x688 __umtx_op_wait_uint_private+0x64 syscallenter+0x331 syscall+0x4b Xfast_syscall+0xdd 17903 100365 VBoxSDL -mi_switch+0x174 sleepq_catch_signals+0x2f4 sleepq_timedwait_sig+0x19 _sleep+0x1b1 do_wait+0x591 __umtx_op_wait_uint_private+0x64 syscallenter+0x331 syscall+0x4b Xfast_syscall+0xdd 17903 100367 VBoxSDL -mi_switch+0x174 sleepq_catch_signals+0x2f4 sleepq_timedwait_sig+0x19 _sleep+0x1b1 kern_nanosleep+0x118 nanosleep+0x6e syscallenter+0x331 syscall+0x4b Xfast_syscall+0xdd 17903 100369 VBoxSDL -mi_switch+0x174 sleepq_catch_signals+0x2f4 sleepq_timedwait_sig+0x19 _sleep+0x1b1 do_wait+0x591 __umtx_op_wait_uint_private+0x64 syscallenter+0x331 syscall+0x4b Xfast_syscall+0xdd 17903 100370 VBoxSDL -mi_switch+0x174 sleepq_catch_signals+0x2f4 sleepq_wait_sig+0x16 _sleep+0x269 do_wait+0x688 __umtx_op_wait_uint_private+0x64 syscallenter+0x331 syscall+0x4b Xfast_syscall+0xdd 17903 100371 VBoxSDL -running 17903 100372 VBoxSDL -mi_switch+0x174 sleepq_catch_signals+0x2f4 sleepq_wait_sig+0x16 _sleep+0x269 do_wait+0x688 __umtx_op_wait_uint_private+0x64 syscallenter+0x331 syscall+0x4b Xfast_syscall+0xdd 17903 100373 VBoxSDL -
Re: VirtualBox + VIMAGE
On Jan 26, 2011, at 5:33 PM, Bernhard Froehlich de...@freebsd.org wrote: On Wed, 26 Jan 2011 23:27:27 +0200, Mikolaj Golub wrote: On Wed, 26 Jan 2011 14:18:03 + (UTC) Bjoern A. Zeeb wrote: BAZ On Wed, 26 Jan 2011, Mikolaj Golub wrote: On Wed, 26 Jan 2011 09:15:46 + (UTC) Bjoern A. Zeeb wrote: BAZ I think you should wrap the CURVNET changes in __FreeBSD_version BAZ checks so that the port, should it run elsewhere or on older FreeBSDs BAZ (if it runs there) not trouble people having to patch it away. BAZ #if defined(__FreeBSD_version) __FreeBSD_version = 800500 BAZ #endif BAZ might be a save bet. Thanks. Something like in the patch below? Note, I have not run this version yet. Will test it tonight or tomorrow. BAZ Well, you will need to include sys/param.h as well, and that only if BAZ you are on FreeBSD so you'll need an extra check for just that I BAZ guess. Not sure how vbox handles the all this in their guts. The file has already had '#include sys/param.h' among other includes. It just is not seen in the patch. The file is used only for FreeBSD driver so there is no need in extra check I think. I have tested this latest version of the patch. It works for me. Could someone with a vimage enabled kernel please test bridging with a stock emulators/virtualbox-ose-kmod port? There was a report that this causes a crash and it would be good to verify if that is still valid: http://lists.freebsd.org/pipermail/freebsd-emulation/2009-November/007055.html -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org It still crashes. -Brandon___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: Testing Luvalley with FreeBSD as dom0
On Sun, Jan 9, 2011 at 12:01 AM, Xiaodong Yi xdong...@gmail.com wrote: Hi, I confirm that I no longer have time for Luvalley. However, I will be extreemly happy if anybody is willing to take over from me. Especially, I quite agree to customize Luvalley for FreeBSD, through it supports all kinds of Dom0 OSes. Howerver, I hope that the LIGHT architecture of Luvalley could be kept. Maybe it is useful to patch dom0 FreeBSD kernel (especially for interrupt handling), but it should not be very complex. Part of the code comes from KVM, and I suggest to keep flying with KVM to make sure that guest VMs work well. I believe that if serious effort were to be put forward by the FreeBSD developers to further develop the code, the result would need to be GPL and Linux free (or VERY close to it). This is an area of contention within the FreeBSD developer and user community, so it would need to be addressed. As the developer of Luvalley, do you have the ability to re-license the code using a BSD license? Are there too many technical issues with the code to do this? Juergen mentioned that bits of the code are based on (or pulled directly from?) Linux KVM. That probably wouldn't fly here... Luvalley does boot and run on bare hardware. But it does not taint dom0 FreeBSD. Although the `non-root' mode dom0 FreeBSD kernel has direct access to BIOS and hardware, Luvalley tries hard to coordinate with it. For example, Luvalley traps the BIOS calls from the FreeBSD kernel to report the modified E820 table. Another example is that Luvalley uses NMI as the IPI interrupt to avoid conflict with BSD kernel. And I also believe that simple patches could work if some corners of FreeBSD kernel are tainted. Regards, and looking forward to the following news ... Xiaodong As am I... Thanks for chiming in Xiaodong! -Brandon ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: question about virtualbox and windows.
On Sun, Oct 24, 2010 at 2:26 PM, Julian Elischer jul...@freebsd.org wrote: If I have a FreeBSD 8 machine with a windows partition that currently works. is there a way to boot FreeBSD, start virtualbox and run windows from the current functional windows partition.. basically I want to switch over to using dual-boot on this machine to permanently running BSD with windows as a VM when needed. Julian (I did this many years ago with vmware 1.x but not since). Though I've not tried any of the setups, there are several how-tos in the VirtualBox forums explaining how to do just that sort of thing: http://forums.virtualbox.org/viewforum.php?f=28 I'm preparing to do essentially the same thing with several machines at work, so I've looked through the Windows 7 and XP instructions; doesn't seem too difficult, but good luck nevertheless... -Brandon ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: Hope for USB support?
On Wed, Oct 13, 2010 at 10:04 AM, Hans Petter Selasky hsela...@freebsd.org wrote: On Mon, Oct 11, 2010 at 11:29 AM, Kevin Oberman wrote: I could use this as well, and I know of at least 2 others. I guess a good starting point would be to ask, what is the scope of work that needs to be done to add USB support to Virtual box in FreeBSD Hi, I've looked at the VirtualBox USB layer, and adding FreeBSD USB support should not require too much work. Is anyone interested in paying for this work? --HPS I'm very reliant on VirtualBox, I suspect many on this list are (or eventually will be), so I'm interested in having this support. Hans, would this be better handled by the FreeBSD Foundation, or would a pool of interested users be an appropriate vessel for the funds (assuming it is financially viable -- how much are we talking? ;) ). ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: Hope for USB support?
On Wed, Oct 13, 2010 at 11:13 AM, Hans Petter Selasky hsela...@freebsd.org wrote: On Wednesday 13 October 2010 17:40:47 Brandon Gooch wrote: On Wed, Oct 13, 2010 at 10:04 AM, Hans Petter Selasky hsela...@freebsd.org wrote: On Mon, Oct 11, 2010 at 11:29 AM, Kevin Oberman wrote: I could use this as well, and I know of at least 2 others. I guess a good starting point would be to ask, what is the scope of work that needs to be done to add USB support to Virtual box in FreeBSD Hi, I've looked at the VirtualBox USB layer, and adding FreeBSD USB support should not require too much work. Is anyone interested in paying for this work? --HPS I'm very reliant on VirtualBox, I suspect many on this list are (or eventually will be), so I'm interested in having this support. Hans, would this be better handled by the FreeBSD Foundation, or would a pool of interested users be an appropriate vessel for the funds (assuming it is financially viable -- how much are we talking? ;) ). Hi, I was thinking about something like $500-$1000 for adding USB support to VirtualBox through LibUSB. Probably you are right that it would be better to go through the FreeBSD Foundation, but I would also be fine getting paid directly through paypal for example. Woah. That seems awfully cheap for something that would be so incredibly useful to have :) I'm not a person of means, but I can surely come up with something -- I was actually hoping to make my first contribution to the Foundation this year; I may have to make a tough decision :( (Like you) I was hoping for a much greater response to your question; surely we have a few more opinionated -emulation-ers out there? -Brandon ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: Flash Player Square Preview Release - a new hope
On Wed, Sep 29, 2010 at 7:53 PM, Alexander Best arun...@freebsd.org wrote: hi there, i just sumbled upon this new flash player release by adobe: http://labs.adobe.com/downloads/flashplayer10.html i might be making an idiot out of myself, because this might have been discussed beforehand, but oh well... ;) i went for the 32-bit Content Debugger Players Linux version and after throwing it at nspluginwrapper everything works fine so far. i haven't experienced any segfaults (i'm sure anybody running flash 8-10 knows what I'm talking about ;)). anybody else tried it yet? i'm running chromium 5.0.375.127 btw (built with base gcc (4.2.x)). cheers. alex Firefox 3.6.10 here (on 8-STABLE amd64 and 8.1-RELEASE-p1 i386). I'm using the Linux version found under 32-bit Release Players. The 32-bit Content Debugger Player was wreaking serious havok :( With the Release player, it's still dumping core randomly, although much less often than usual. Very cool :) So, what's really going on with the npviewer.bin dumps? Is FreeBSD missing some magic from the linuxulator code, or is the Flash plugin really just THAT crappy? I don't recall that it was any better on Ubuntu to be honest... Thanks for the link Alexander! -Brandon ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: CFT: VirtualBox 3.2.0
On Sat, May 29, 2010 at 8:22 AM, Beat Gaetzi b...@freebsd.org wrote: Hi, The vbox@ team is happy to announce a call for tester for VirtualBox 3.2.0. The VirtualBox 3.2.0 changelog is available here: http://www.virtualbox.org/wiki/Changelog Changes to the port: - VirtualBox and the guest additions have been updated to 3.2.0. - Add option to build with VNC support (Disabled by default) - Add option to build with VDE support (Disabled by default) - Add option to build webservice (Disabled by default) - Fix build with QT4 support disabled and X11 support enabled. - Replace custom pkg-install.in script with GROUPS framework. - Do not build Guest Additions in virtualbox-ose port. - Add patch to implement locking/unlocking of host DVD drive. You will find a tarball with the latest port version here: https://svn.bluelife.at/nightlies/virtualbox-port.tar.gz Please check the wiki page for known problems: http://wiki.freebsd.org/VirtualBox Please backup your virtual machines before upgrading and report any functionality which was working with previous versions of VirtualBox and no longer working with 3.2.0, any build failures or problems with the newly added port options. Many thanks to the VirtualBox developers (especially Alexander Eichner for all his work and help), all tester and patch submitter and the whole vbox@ team especially de...@. Beat, on behalf of vbox@ Built and running on: FreeBSD adamo 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r208608: Fri May 28 04:21:49 CDT 2010 r...@adamo:/usr/obj/usr/src/sys/ADAMO amd64 Ubuntu 10.04 LTS 32-bit installed and running great, 3D video not working in full-screen with the Intel GM45 in this laptop, but so far, so GOOD :) -Brandon ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: VirtualBox 3.2.0-beta-1 fails to compile on -current
On Wed, May 26, 2010 at 1:45 AM, Beat Gaetzi b...@freebsd.org wrote:
On 05/26/10 08:27, Brandon Gooch wrote:
On Fri, Apr 30, 2010 at 1:05 PM, Jung-uk Kim j...@freebsd.org wrote:
On Thursday 29 April 2010 09:02 pm, Michael Butler wrote:
On 04/29/10 19:23, Jung-uk Kim wrote:
I read the source again and I found it is not patched by the
emulator itself. It's done from usual _CRS method. Please try
the attached patch instead.
Now I get ..
kBuild: iasl DevicesR3 -
/usr/home/imb/svn/virtualbox-ose/work/VirtualBox-3.2.0_OSE/src/VBox
/Devices/PC/vbox-cpuhotplug.dsl
/usr/home/imb/svn/virtualbox-ose/work/VirtualBox-3.2.0_OSE/out/free
bsd.x86/release/obj/DevicesR3/vboxssdt-cpuhotplug.hex.pre 14:
Device (SCK0) { Name (_HID, ACPI0004) Name (_UID, SCKCPU0)
Processor (CPU0, 0x00, 0x0, 0x0 ) { Name (_HID, ACPI0007) Name
(_UID, SCK0-CPU0) Name (_PXM, 0x00) Method(_MAT, 0) { IF
(CPCK(0x00)) { Name (APIC, Buffer (8) {0x00, 0x08, 0x00, 0x00,
0x01}) Return(APIC) } Else { Return (0x00) } } Method(_STA) { IF
(CPCK(0x00)) { Return (0xF) } Else { Return (0x0) } } Method(_EJ0,
1) { Store(0x00, \_SB.CPUL) Return } } }
Error 4080 -
Invalid object type for reserved
name ^ (found INTEGER, requires Buffer)
.. where the Return(0x00) as the alternate result to
Result(APIC) is causing an issue,
Sigh... A new file, a new bug. :-(
Try the attached patch.
It seems this patch has been committed to the 'virtualbox-ose-devel'
port, but your previous patch (attached to an earlier message in this
thread) did not. Will you submit the original patch to the
freebsd-vbox crew as well?
I forgot to commit this patch to the virtualbox-ose-devel port as our
main focus is on the 3.2.0 port at the moment with already includes this
patch. I will commit the patch in a few minutes to the -devel port.
I see... Well, as it stands, both of my laptops, one running CURRENT,
the other running 8.1-PRERELEASE, panic when loading the vboxdrv
module right now (on 3.2.1 at least), so I'm looking to rollback to
3.1.8 -- or test 3.2.0 :)
Will you announce to the list when we VirtualBox users should begin
testing 3.2.0? Or did I already miss that?
Thanks for the reminder!
Beat
Thank you!
-Brandon
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: VirtualBox 3.2.0-beta-1 fails to compile on -current
On Wed, May 26, 2010 at 11:45 AM, Sean C. Farley s...@freebsd.org wrote: On Wed, 26 May 2010, Beat Gaetzi wrote: We received a few reports from users that 3.2.0 panics the host when loading the kernel module. This is the reason why we haven't announced a CFT for 3.2.0 yet. On those hosts, did /boot/modules/linker.hints get generated correctly/completely? I have seen, at least from the subversion tree, a very small linker.hints file where I need to rerun kldxref on /boot/modules else a panic may occur. I can check this on my 3.2.x systems in a little bit (the panic occurs loading the vboxdrv for 3.2.0 or 3.2.1, 8.1-PRE and 9-CURRRENT both amd64). I personally get panics on my FreeBSD 8 amd64 host running the Nvidia driver (currently v195.36.24 but occurred with earlier drivers too). This is with a non-X FreeBSD 8 amd64 guest and using ssh to the guest. I think it is panic'ing when transferring some files to it from the host. Unfortunately, the system locks up completely, so there is no core saved. I'm preparing to test the Nvidia 195.36.24 amd64 driver on my primary system. I haven't had but one or two lockups using VirtualBox since installing the 195.36.15 driver, so I'm leery of change ATM -- but we need to make progress so... I would have reported both earlier but life has been very busy. Sean -- s...@freebsd.org ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: qemu git head 20100323 on FreeBSD - qemu-devel port update for testing
On Thu, Mar 25, 2010 at 8:44 PM, Juergen Lock n...@jelal.kn-bremen.de wrote: Hi! Now that qemu git head works again (thanx Aurelien! :) I've finished the FreeBSD qemu-devel port update patch/shar that made me uncover the bug: http://people.freebsd.org/~nox/qemu/qemu-devel-20100323.patch resp. http://people.freebsd.org/~nox/qemu/qemu-devel-20100323.shar This also adds a few misc fixes (that I'll submit on the qemu list seperately), I have... . Fixed the FreeBSD executable path detection to work without /proc mounted (it usually isn't on FreeBSD), so you now no longer have to pass the path to the pc-bios dir with -L if you run qemu out of the build dir when another version is installed, like, work/qemu-snapshot-20100323_20/i386-softmmu/qemu ... (files/patch-vl.c in the shar/patch) . Fixed some more bsd-user bugs so all of i386-bsd-user, x86_64-bsd-user, and sparc64-bsd-user now run for me again on FreeBSD stable/8 amd64. (I didn't test sparc-bsd-user as I only tried -bsd freebsd and FreeBSD doesn't run on 32bit sparc.) - Yes bsd-user still needs more work but at least simple exectuables run. (files/patch-bsd-user-mmap.c, files/patch-exec.c) . Fixed the bsd-user host page protection code for FreeBSD hosts (using kinfo_getvmmap(3) on FeeBSD = 7.x and /compat/linux/proc on older FreeBSD.) (files/patch-bsd-user-linproc) . Fixed some compilation warnings and a missing #include. (files/patch-qemu-char.c, files/patch-qemu-timer.c) Enjoy, :) Juergen ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org Thanks Juergen for all of your hard work on this! -Brandon ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: Flash sometimes freezes firefox, also many npviewer.bin processes left running around
On Fri, Mar 19, 2010 at 1:47 AM, Yuri y...@rawbw.com wrote: Sometimes after some flash object is displayed firefox gets frozen for many few seconds,maybe ~20sec. Do you see the same? Is there anyfix for this? In additions I have 54 processes like this one 50006 ?? I 0:00.00 /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin --plugin /usr/local/lib/linux-mozilla/plugins/libflashplayer.so --connection hanging around even after firefox process exits. linux-f10-flashplugin-10.0r45 nspluginwrapper-1.2.2_5 firefox-3.5.8,1 Yuri ___ freebsd-questi...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org I map a key to `killall npviewer.bin` -- crude and hack-ish, but it's all that seems to work. I just refresh the browser page(s) containing any other flash objects that I WANT to use or view (sometimes the refresh happens automagically). -Brandon ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
