From mezz7 at cox.net Tue Sep 1 00:22:34 2009 From: mezz7 at cox.net (Jeremy Messenger) Date: Tue Sep 1 00:22:40 2009 Subject: linux-opera 10.x needs linux-nas-libs, anyone want to create port? Message-ID: Hello all, The linux-opera (well, actually, it's QT4 that came in bundle tarball) needs libaudio.so.2 that is in nas-libs rpm file. I am deaf, so it is impossible for me to test linux-nas-libs. Also I am pretty very behind with new linux ports stuff. It will be great if anyone can create linux-nas-libs port for all version of what we have linux_base*. Thanks! Cheers, Mezz -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org From mezz7 at cox.net Tue Sep 1 00:23:17 2009 From: mezz7 at cox.net (Jeremy Messenger) Date: Tue Sep 1 00:23:24 2009 Subject: linux-opera 10.x needs linux-nas-libs, anyone want to create port? In-Reply-To: References: Message-ID: On Mon, 31 Aug 2009 19:23:47 -0500, Jeremy Messenger wrote: > Hello all, > > The linux-opera (well, actually, it's QT4 that came in bundle tarball) > needs libaudio.so.2 that is in nas-libs rpm file. I am deaf, so it is > impossible for me to test linux-nas-libs. Also I am pretty very behind > with new linux ports stuff. It will be great if anyone can create > linux-nas-libs port for all version of what we have linux_base*. Thanks! By the way, please add me in CC. > Cheers, > Mezz -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org From fernando.apesteguia at gmail.com Tue Sep 1 06:30:07 2009 From: fernando.apesteguia at gmail.com (=?ISO-8859-1?Q?Fernando_Apestegu=EDa?=) Date: Tue Sep 1 06:30:14 2009 Subject: Thanks to wine developers/porters In-Reply-To: <20090831211217.GR50352@acme.spoerlein.net> References: <20090831211217.GR50352@acme.spoerlein.net> Message-ID: <1bd550a00908312300v4e5bef8dnbe3b82a2fc54fe0a@mail.gmail.com> On Mon, Aug 31, 2009 at 11:12 PM, Ulrich Sp?rlein wrote: > Hi, just wanted to thank those who made it possible to run an i386 wine > binary on amd64 and have it just work. > > I wrote the steps down in the wiki wine article, for those to whom they > are not obvious. Could you please post the exact link as a reference? Thanks. > > Again, thanks! > Uli > _______________________________________________ > freebsd-emulation@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-emulation > To unsubscribe, send any mail to "freebsd-emulation-unsubscribe@freebsd.org" > From tijl at ulyssis.org Tue Sep 1 11:13:06 2009 From: tijl at ulyssis.org (Tijl Coosemans) Date: Tue Sep 1 11:13:18 2009 Subject: Is ALSA support working in 72? In-Reply-To: <4A9C2B02.8010001@rawbw.com> References: <4A9C2B02.8010001@rawbw.com> Message-ID: <200909011310.32746.tijl@ulyssis.org> On Monday 31 August 2009 21:56:50 Yuri wrote: > I tried new skype-2.1.0.47 on FreBSD-72. (I have > linux-alsa-lib-1.0.10.3_2 installed.) > > Skype starts but gives the errors below when I try to make a voice call. > Previous versions of Skype came in OSS flavor but now it seems to be > dropped and it's only available for ALSA. > > Why would ALSA library fail? > > ----- errrors ----- > > ALSA lib confmisc.c:672:(snd_func_card_driver) cannot find card '0' > ALSA lib conf.c:3493:(_snd_config_evaluate) function > snd_func_card_driver returned error: No such device > ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings > ALSA lib conf.c:3493:(_snd_config_evaluate) function snd_func_concat > returned error: No such device > ALSA lib confmisc.c:1072:(snd_func_refer) error evaluating name > ALSA lib conf.c:3493:(_snd_config_evaluate) function snd_func_refer > returned error: No such device > ALSA lib conf.c:3962:(snd_config_expand) Evaluate error: No such device > ALSA lib pcm.c:2099:(snd_pcm_open_noupdate) Unknown PCM default > ALSA lib confmisc.c:672:(snd_func_card_driver) cannot find card '0' > ALSA lib conf.c:3493:(_snd_config_evaluate) function > snd_func_card_driver returned error: No such device > ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings > ALSA lib conf.c:3493:(_snd_config_evaluate) function snd_func_concat > returned error: No such device > ALSA lib confmisc.c:1072:(snd_func_refer) error evaluating name > ALSA lib conf.c:3493:(_snd_config_evaluate) function snd_func_refer > returned error: No such device > ALSA lib conf.c:3962:(snd_config_expand) Evaluate error: No such device > ALSA lib pcm.c:2099:(snd_pcm_open_noupdate) Unknown PCM default > /usr/ports/distfiles/skype_static-2.1.0.47/skype: relocation error: > /usr/ports/distfiles/skype_static-2.1.0.47/skype: symbol > snd_device_name_hint, version ALSA_0.9 not defined in file > libasound.so.2 with link time reference ALSA has never worked AFAIK. The library is only there for applications that link to it, but don't actually use it. It might be worth a try to install the alsa-plugins-oss RPM and then configure ALSA lib to use the FreeBSD OSS device. From bsam at ipt.ru Tue Sep 1 11:45:40 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Tue Sep 1 11:46:48 2009 Subject: linux-opera 10.x needs linux-nas-libs, anyone want to create port? In-Reply-To: (Jeremy Messenger's message of "Mon, 31 Aug 2009 19:23:47 -0500") References: Message-ID: <21460986@bb.ipt.ru> On Mon, 31 Aug 2009 19:23:47 -0500 Jeremy Messenger wrote: > The linux-opera (well, actually, it's QT4 that came in bundle tarball) > needs libaudio.so.2 that is in nas-libs rpm file. I am deaf, so it is > impossible for me to test linux-nas-libs. Also I am pretty very behind > with new linux ports stuff. It will be great if anyone can create > linux-nas-libs port for all version of what we have > linux_base*. Thanks! Done. Enjoy. ;-) BTW, don't forget to add to opera Makefile: ----- -------------- next part -------------- A non-text attachment was scrubbed... Name: linux-opera.diff Type: text/x-patch Size: 500 bytes Desc: add naslibs as a dependency Url : http://lists.freebsd.org/pipermail/freebsd-emulation/attachments/20090901/a0e9e459/linux-opera.bin -------------- next part -------------- ----- -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From bazerka at beardz.net Tue Sep 1 16:18:05 2009 From: bazerka at beardz.net (Jase Thew) Date: Tue Sep 1 16:18:12 2009 Subject: Thanks to wine developers/porters In-Reply-To: <1bd550a00908312300v4e5bef8dnbe3b82a2fc54fe0a@mail.gmail.com> References: <20090831211217.GR50352@acme.spoerlein.net> <1bd550a00908312300v4e5bef8dnbe3b82a2fc54fe0a@mail.gmail.com> Message-ID: <4A9D44D9.10102@beardz.net> On 01/09/2009 07:00, Fernando Apestegu?a wrote: > On Mon, Aug 31, 2009 at 11:12 PM, Ulrich Sp?rlein wrote: > >> Hi, just wanted to thank those who made it possible to run an i386 wine >> binary on amd64 and have it just work. >> >> I wrote the steps down in the wiki wine article, for those to whom they >> are not obvious. >> > Could you please post the exact link as a reference? > > Thanks. > http://wiki.freebsd.org/Wine#head-6963d527c173e57b1567e881305b544d33435b6d Regards, Jase. From mezz7 at cox.net Tue Sep 1 23:18:16 2009 From: mezz7 at cox.net (Jeremy Messenger) Date: Tue Sep 1 23:18:22 2009 Subject: linux-opera 10.x needs linux-nas-libs, anyone want to create port? In-Reply-To: <21460986@bb.ipt.ru> References: <21460986@bb.ipt.ru> Message-ID: On Tue, 01 Sep 2009 06:45:41 -0500, Boris Samorodov wrote: >> The linux-opera (well, actually, it's QT4 that came in bundle tarball) >> needs libaudio.so.2 that is in nas-libs rpm file. I am deaf, so it is >> impossible for me to test linux-nas-libs. Also I am pretty very behind >> with new linux ports stuff. It will be great if anyone can create >> linux-nas-libs port for all version of what we have >> linux_base*. Thanks! > > Done. Enjoy. ;-) Thanks! I owe you a beer. ;-) The linux-opera 10.00 works great with no issue as I am writing on this right now (Opera M2 email client) so far. I am going to post patch of update linux-opera in a separate email for I can get more tests from the others before I commit it. Because I will be out of town for a few days without access to FreeBSD boxes, only netbook with Linux (yes, I know and will be MacOS X soon anyway). Cheers, Mezz > BTW, don't forget to add to opera Makefile: > ----- -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org From mezz7 at cox.net Wed Sep 2 02:48:01 2009 From: mezz7 at cox.net (Jeremy Messenger) Date: Wed Sep 2 02:48:21 2009 Subject: Testers: Here's a patch to update linux-opera to 10.00. Message-ID: Hello all, Here is a patch to update linux-opera to 10.00. It works great with old ~/.linux-opera so far, I haven't seen any problem. I will be out of town for a few days. I need someone to test it more and report any bug if there is any. When I commit it, I am planning to note in the UPDATING about make the back up of ~/.linux-opera and turn the auto-update off. Also, I am planning to make a request to the Opera developer for allow us to tweak the path of /etc instead of hardcore that way I can put operaprefs_fixed.ini and put in ${PREFIX}/etc/ to force disable auto-update. Patch: http://people.freebsd.org/~mezz/diff/linux-opera.diff Couldn't have done without bsam. He has created linux-nas-lib for all linux_base*. The linux-opera (well, it's QT libraries that came in its tarball) needs it, so be sure to have your ports tree and installed ports up to date. Cheers, Mezz -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org From gary.jennejohn at freenet.de Wed Sep 2 09:07:51 2009 From: gary.jennejohn at freenet.de (Gary Jennejohn) Date: Wed Sep 2 09:08:21 2009 Subject: Testers: Here's a patch to update linux-opera to 10.00. In-Reply-To: References: Message-ID: <20090902110749.243fe108@ernst.jennejohn.org> On Tue, 01 Sep 2009 21:49:20 -0500 "Jeremy Messenger" wrote: > Here is a patch to update linux-opera to 10.00. It works great with old > ~/.linux-opera so far, I haven't seen any problem. I will be out of town > for a few days. I need someone to test it more and report any bug if there > is any. > Works extremely well so far, even flash works without any complications. I'm using linux_base-f10-10_1. uname -a (sanitized): FreeBSD 9.0-CURRENT FreeBSD 9.0-CURRENT #35: Sat Aug 29 18:30:32 CEST 2009 amd64 --- Gary Jennejohn From fli at shapeshifter.se Wed Sep 2 12:26:48 2009 From: fli at shapeshifter.se (Fredrik Lindberg) Date: Wed Sep 2 12:26:55 2009 Subject: VirtualBox bridged adapter (vboxnetflt) In-Reply-To: <4A8EB3D2.7010109@shapeshifter.se> References: <4A8EB3D2.7010109@shapeshifter.se> Message-ID: <4A9E6481.9070200@shapeshifter.se> Okay, so this past weekend I re-wrote the vboxnetflt driver using netgraph (as suggested by Julian Elischer). It's now an netgraph node and automatically attaches to ng_ether. This is probably the best solution that also works properly on FreeBSD 7. One minor thing, one do I manually generate opt_netgraph.h on FreeBSD 7 without using bsd.kmod.mk? Currently I just create an empty file. Also changed it to the MIT license to keep the Vbox guys happy (in reality a NOP as the MIT and 2-clause BSD licenses are essentially equal). This version has been tested on FreeBSD 7.2/i386 and FreeBSD 8/i386-SMP. Patches are at http://www.shapeshifter.se/pub/patches/vbox-freebsd-netif-20090831.patch http://www.shapeshifter.se/pub/patches/vbox-freebsd-vboxnetflt-20090831.patch http://www.shapeshifter.se/pub/patches/virtualbox-port.patch Apply/compile with cd /usr/ports/emulators/virtualbox make clean patch mkdir work/virtualbox-3.0.51r22226/src/VBox/HostDrivers/VBoxNetFlt/freebsd patch -d work/virtualbox-3.0.51r22226 < vbox-freebsd-netif-20090831.patch patch -d work/virtualbox-3.0.51r22226 < vbox-freebsd-vboxnetflt-20090831.patch patch < virtualbox-port.patch make install Test if you're interested and report failures/successes. Fredrik From avg at icyb.net.ua Wed Sep 2 14:48:36 2009 From: avg at icyb.net.ua (Andriy Gapon) Date: Wed Sep 2 14:48:43 2009 Subject: virtualbox 3.0.51r22226: some quirks Message-ID: <4A9E85C1.1090605@icyb.net.ua> Just to check if the following issues are mine local or if they are known ones. 1. Host+Del combination doesn't sent Ctrl+Alt+Del to a guest, this used to work correctly before. 2. Permanent shared directories disappear after VirtualBox restart. 3. VirtualBox guest clipboard driver freezes on attempts to copy something from host to guest; guest to host works OK. Otherwise, VirtualBox works great for me. Thank you! -- Andriy Gapon From nox at jelal.kn-bremen.de Wed Sep 2 18:01:08 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Wed Sep 2 18:01:15 2009 Subject: experimental FreeBSD qemu-devel git head port update for testing In-Reply-To: <20090829222339.GA93608@triton8.kn-bremen.de> References: <20090829222339.GA93608@triton8.kn-bremen.de> Message-ID: <20090902175621.GA63905@triton8.kn-bremen.de> On Sun, Aug 30, 2009 at 12:23:39AM +0200, Juergen Lock wrote: > Hi! > > Jan Kiszka asked me if the unstable guest timer irq problem still > exists on qemu git head, so I made an update for that today: > http://people.freebsd.org/~nox/qemu/qemu-devel-20090829.patch > (and found out it does.) > > The bad news (for FreeBSD users anyway) is kqemu support has now been > removed as `promised' (by the upstream qemu developers), so testing this > version is probably less interesting for many FreeBSD users than the > qemu 0.11 stable branch snapshot I posted about here, > http://lists.freebsd.org/pipermail/freebsd-emulation/2009-August/006646.html > but e.g. users of non-x86 targets probably will still be interested. > > Also the pcap patch stopped working in this snapshot and I don't yet > know why. (I think the original version of that patch was submitted by > Jung-uk Kim, maybe he has an idea; Cc'd.) > [...] Jung-uk Kim sent me a new pcap patch (thanx! :), and I have just included it in the mentioned update at http://people.freebsd.org/~nox/qemu/qemu-devel-20090829.patch Enjoy, Juergen From avg at icyb.net.ua Wed Sep 2 18:27:44 2009 From: avg at icyb.net.ua (Andriy Gapon) Date: Wed Sep 2 18:27:51 2009 Subject: skype 2.1 beta for linux Message-ID: <4A9EB91C.4060203@icyb.net.ua> Just noticed this: http://www.skype.com/intl/en/download/skype/linux/ -- Andriy Gapon From miwi at FreeBSD.org Wed Sep 2 22:42:08 2009 From: miwi at FreeBSD.org (Martin Wilke) Date: Wed Sep 2 22:42:30 2009 Subject: skype 2.1 beta for linux In-Reply-To: <4A9EB91C.4060203@icyb.net.ua> References: <4A9EB91C.4060203@icyb.net.ua> Message-ID: <20090902222407.GF82548@bsdcrew.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, Sep 02, 2009 at 09:27:40PM +0300, Andriy Gapon wrote: > > Just noticed this: > http://www.skype.com/intl/en/download/skype/linux/ > It doesn't work, this version missing the OSS support, I talked to the guys we get later a oss version! - - Martin > -- > Andriy Gapon > _______________________________________________ > freebsd-emulation@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-emulation > To unsubscribe, send any mail to "freebsd-emulation-unsubscribe@freebsd.org" > - -- +-----------------------+-------------------------------+ | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | | Skype : splash_111 | Mail : miwi(at)FreeBSD.org | +-----------------------+-------------------------------+ | Mess with the Best, Die like the Rest! | +-----------------------+-------------------------------+ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAkqe8IcACgkQdLJIhLHm/OmkxACg00eR6eTBtWR6EbFPaEuciVRy AgwAoNUiEBM3ZnDzFkIx52dBPQsqEaPk =BS/5 -----END PGP SIGNATURE----- From npapke at acm.org Thu Sep 3 07:14:53 2009 From: npapke at acm.org (Norbert Papke) Date: Thu Sep 3 07:14:59 2009 Subject: VirtualBox bridged adapter (vboxnetflt) In-Reply-To: <4A9E6481.9070200@shapeshifter.se> References: <4A8EB3D2.7010109@shapeshifter.se> <4A9E6481.9070200@shapeshifter.se> Message-ID: <200909030014.51466.npapke@acm.org> Hi Frederik, On September 2, 2009, Fredrik Lindberg wrote: > Okay, so this past weekend I re-wrote the vboxnetflt driver using > netgraph (as suggested by Julian Elischer). > > [...] > > Test if you're interested and report failures/successes. I just built and installed on 7.2/amd64 without any problems. I didn't even have to think, your instructions were spot-on. :) First impressions are good. I have not yet encountered any problems. I will continue to test. Thank you very much for your hard work. -- Norbert Papke. npapke@acm.org http://saveournet.ca Protecting your Internet's level playing field From fli at shapeshifter.se Thu Sep 3 07:42:16 2009 From: fli at shapeshifter.se (Fredrik Lindberg) Date: Thu Sep 3 07:42:22 2009 Subject: VirtualBox bridged adapter (vboxnetflt) In-Reply-To: <4A9F8AE6.1000001@entel.upc.edu> References: <4A8EB3D2.7010109@shapeshifter.se> <4A9E6481.9070200@shapeshifter.se> <4A9F8AE6.1000001@entel.upc.edu> Message-ID: <4A9F7353.3020106@shapeshifter.se> Gustau P?rez wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Fredrik Lindberg wrote: >> Test if you're interested and report failures/successes. > > Hi, > > tried your patches against FreeBSD 8.0BETA3/i386-SMP. When selecting > an interface and configuring it as a bridged one, it finds all my host > interfaces. I can select one of them (in my case bge0), but when I try > to start the > vm it gives me the following error : > > ******************* > > p, li { white-space: pre-wrap; } > > Failed to open/create the internal network > 'HostInterfaceNetworking-bge0' (VERR_SUPDRV_COMPONENT_NOT_FOUND). > > Unknown error creating VM (VERR_SUPDRV_COMPONENT_NOT_FOUND). > Did you by any chance forget to do a kldload /boot/modules/vboxnetflt.ko ? Fredrik From guru at unixarea.de Thu Sep 3 08:27:05 2009 From: guru at unixarea.de (Matthias Apitz) Date: Thu Sep 3 08:27:17 2009 Subject: skype 2.1 beta for linux In-Reply-To: <20090902222407.GF82548@bsdcrew.de> References: <4A9EB91C.4060203@icyb.net.ua> <20090902222407.GF82548@bsdcrew.de> Message-ID: <20090903081015.GA2343@current.Sisis.de> El d?a Thursday, September 03, 2009 a las 12:24:07AM +0200, Martin Wilke escribi?: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Wed, Sep 02, 2009 at 09:27:40PM +0300, Andriy Gapon wrote: > > > > Just noticed this: > > http://www.skype.com/intl/en/download/skype/linux/ > > > > It doesn't work, this version missing the OSS support, > I talked to the guys we get later a oss version! > > - - Martin I'm using 2.0.0.72-oss in 8-CURRENT which works fine for me. I don't need a better Skype version, what I would like to see is that also the video would work in Skype for us in FBSD. Just my opinion about a newer Skype. Thx matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ People who hate Microsoft Windows use Linux but people who love UNIX use FreeBSD. From miwi at FreeBSD.org Thu Sep 3 08:54:52 2009 From: miwi at FreeBSD.org (Martin Wilke) Date: Thu Sep 3 08:54:59 2009 Subject: skype 2.1 beta for linux In-Reply-To: <20090903081015.GA2343@current.Sisis.de> References: <4A9EB91C.4060203@icyb.net.ua> <20090902222407.GF82548@bsdcrew.de> <20090903081015.GA2343@current.Sisis.de> Message-ID: <20090903085446.GG82548@bsdcrew.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, Sep 03, 2009 at 10:10:15AM +0200, Matthias Apitz wrote: > El d?a Thursday, September 03, 2009 a las 12:24:07AM +0200, Martin Wilke escribi?: > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > On Wed, Sep 02, 2009 at 09:27:40PM +0300, Andriy Gapon wrote: > > > > > > Just noticed this: > > > http://www.skype.com/intl/en/download/skype/linux/ > > > > > > > It doesn't work, this version missing the OSS support, > > I talked to the guys we get later a oss version! > > > > - - Martin > > I'm using 2.0.0.72-oss in 8-CURRENT which works fine for me. I don't > need a better Skype version, what I would like to see is that also the > video would work in Skype for us in FBSD. Just my opinion about a newer > Skype. Also that's not a problem from Skype, FreeBSD need a v4l(v4bsd)... - - Martin > > Thx > > matthias > -- > Matthias Apitz > t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 > e - w http://www.unixarea.de/ > People who hate Microsoft Windows use Linux but people who love UNIX use FreeBSD. > - -- +-----------------------+-------------------------------+ | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | | Skype : splash_111 | Mail : miwi(at)FreeBSD.org | +-----------------------+-------------------------------+ | Mess with the Best, Die like the Rest! | +-----------------------+-------------------------------+ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAkqfhFYACgkQdLJIhLHm/Ol3OACg4vV9WkjBjm498ika1lktUZ/7 kCsAn2n82QxvTS+lC8werC+9mSzXlLeY =u/yO -----END PGP SIGNATURE----- From gperez at entel.upc.edu Thu Sep 3 10:44:03 2009 From: gperez at entel.upc.edu (=?ISO-8859-1?Q?Gustau_P=E9rez?=) Date: Thu Sep 3 10:44:10 2009 Subject: VirtualBox bridged adapter (vboxnetflt) In-Reply-To: <4A9E6481.9070200@shapeshifter.se> References: <4A8EB3D2.7010109@shapeshifter.se> <4A9E6481.9070200@shapeshifter.se> Message-ID: <4A9F8AE6.1000001@entel.upc.edu> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Fredrik Lindberg wrote: > > Test if you're interested and report failures/successes. Hi, tried your patches against FreeBSD 8.0BETA3/i386-SMP. When selecting an interface and configuring it as a bridged one, it finds all my host interfaces. I can select one of them (in my case bge0), but when I try to start the vm it gives me the following error : ******************* p, li { white-space: pre-wrap; } Failed to open/create the internal network 'HostInterfaceNetworking-bge0' (VERR_SUPDRV_COMPONENT_NOT_FOUND). Unknown error creating VM (VERR_SUPDRV_COMPONENT_NOT_FOUND). Details Result Code : NS_ERROR_FAILURE (0x80004005) Component : Console Interface : IConsole {0a51994b-cbc6-4686-94eb-d4e4023280e2} li { white-space: pre-wrap; } ******************* Your previous set of patches worked fine. I'll try in a 7.2-STABLE in a while a let you know my results. Greets, Gus - -- PGP KEY : http://www-entel.upc.edu/gus/gus.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkqfiuYACgkQKk3pq6YadNvFCgCfXGwbcbaOeeAhRtKiy3SHFrep 79gAoK22jdIHrKE5OXkY+oldtWtlM3XD =hxob -----END PGP SIGNATURE----- From gustau.perez at gmail.com Thu Sep 3 10:55:28 2009 From: gustau.perez at gmail.com (Gustau Perez) Date: Thu Sep 3 10:55:35 2009 Subject: VirtualBox bridged adapter (vboxnetflt) In-Reply-To: <4A9E6481.9070200@shapeshifter.se> References: <4A8EB3D2.7010109@shapeshifter.se> <4A9E6481.9070200@shapeshifter.se> Message-ID: <4A9F8E66.7020408@gmail.com> Fredrik Lindberg wrote: > > Test if you're interested and report failures/successes. Hi, tried your patches against FreeBSD 8.0BETA3/i386-SMP. When selecting an interface and configuring it as a bridged one, it finds all my host interfaces. I can select one of them (in my case bge0), but when I try to start the vm it gives me the following error : ******************* Failed to open/create the internal network 'HostInterfaceNetworking-bge0' (VERR_SUPDRV_COMPONENT_NOT_FOUND). Unknown error creating VM (VERR_SUPDRV_COMPONENT_NOT_FOUND). Details Result Code : NS_ERROR_FAILURE (0x80004005) Component : Console Interface : IConsole {0a51994b-cbc6-4686-94eb-d4e4023280e2} ******************* Your previous set of patches worked fine. I'll try in a 7.2-STABLE in a while a let you know my results. Greets, Gus From guru at unixarea.de Thu Sep 3 11:35:33 2009 From: guru at unixarea.de (Matthias Apitz) Date: Thu Sep 3 11:35:45 2009 Subject: skype 2.1 beta for linux In-Reply-To: <20090903085446.GG82548@bsdcrew.de> References: <4A9EB91C.4060203@icyb.net.ua> <20090902222407.GF82548@bsdcrew.de> <20090903081015.GA2343@current.Sisis.de> <20090903085446.GG82548@bsdcrew.de> Message-ID: <20090903113534.GA1984@current.Sisis.de> El d?a Thursday, September 03, 2009 a las 10:54:46AM +0200, Martin Wilke escribi?: > > I'm using 2.0.0.72-oss in 8-CURRENT which works fine for me. I don't > > need a better Skype version, what I would like to see is that also the > > video would work in Skype for us in FBSD. Just my opinion about a newer > > Skype. > > Also that's not a problem from Skype, FreeBSD need a v4l(v4bsd)... I know. Even better would be that Skype.com provides a native FreeBSD port of Skype. matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ People who hate Microsoft Windows use Linux but people who love UNIX use FreeBSD. From gperez at entel.upc.edu Thu Sep 3 17:44:18 2009 From: gperez at entel.upc.edu (=?ISO-8859-1?Q?Gustau_P=E9rez?=) Date: Thu Sep 3 17:44:26 2009 Subject: VirtualBox bridged adapter (vboxnetflt) In-Reply-To: <4A9F7353.3020106@shapeshifter.se> References: <4A8EB3D2.7010109@shapeshifter.se> <4A9E6481.9070200@shapeshifter.se> <4A9F8AE6.1000001@entel.upc.edu> <4A9F7353.3020106@shapeshifter.se> Message-ID: <4AA01C01.6030000@entel.upc.edu> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Fredrik Lindberg wrote: >> >> Hi, >> >> tried your patches against FreeBSD 8.0BETA3/i386-SMP. When selecting >> an interface and configuring it as a bridged one, it finds all my host >> interfaces. I can select one of them (in my case bge0), but when I try >> to start the >> vm it gives me the following error : >> >> ******************* >> >> p, li { white-space: pre-wrap; } >> >> Failed to open/create the internal network >> 'HostInterfaceNetworking-bge0' >> (VERR_SUPDRV_COMPONENT_NOT_FOUND). >> >> Unknown error creating VM (VERR_SUPDRV_COMPONENT_NOT_FOUND). >> > > Did you by any chance forget to do a kldload > /boot/modules/vboxnetflt.ko ? > > Fredrik I cleaned emulators/virtualbox, cvsup'ed it (to make sure it is clean). Then I reapplied the patches following the instructions. Both vboxdrv.ko and vboxnetflt.ko are in the kernel and I made sure they were the new ones. With 8.0-BETA3/i386-SMP it still fails. I checked dmesg, but nothing special there. What else can I try ? It worked fine with your previou set of patches. Gus - -- PGP KEY : http://www-entel.upc.edu/gus/gus.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkqgHAAACgkQKk3pq6YadNuHigCfaN9expfLR0TdxnbgNdA+MGNP igEAnjkvmPNl1KPkewdoBbtUAzzHDCLC =VH7P -----END PGP SIGNATURE----- From lapo at lapo.it Thu Sep 3 19:37:21 2009 From: lapo at lapo.it (Lapo Luchini) Date: Thu Sep 3 19:37:34 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 4 In-Reply-To: <20090527163952.GI1104@bsdcrew.de> References: <20090527134343.GB1104@bsdcrew.de> <85d001330905270909jde4d723s65e8708a8b498c29@mail.gmail.com> <20090527163952.GI1104@bsdcrew.de> Message-ID: <4AA0149E.30209@lapo.it> Martin Wilke wrote: >> /usr/ports/devel/kBuild/work/kBuild-0.1.5-p1/kBuild/footer.kmk:2304: *** >> target file `virtualbox' has both : and :: entries. >> Stop . >> kmk: Leaving directory `/usr/ports/devel/kBuild/work/kBuild-0.1.5-p1' >> gmake: *** >> [/usr/ports/devel/kBuild/work/kBuild-0.1.5-p1/out/freebsd.amd64/release/bootstrap/ts-stage2-build] >> Error 2 >> ./kBuild/env.sh: info: rc=2: gmake -f bootstrap.gmk >> *** Error code 2 > >> Stop in /usr/ports/devel/kBuild. >> " > > Please update to 7.2 or higher Errr, and what if I have that in a FreeBSD 7.2-STABLE? Any other ideas? (both on my i386 laptop and amd64 home-server) Strangely I can find nothing on Google for that, which seems to indicate very little people is trying VirtualBox on FreeBSD or both my unrelated and different boxes have got a "rare" bug =) (but of course they got more or less the same mix of ports installed, so they're not really unrelated one another) -- Lapo Luchini - http://lapo.it/ ??one of the main causes of the fall of the Roman Empire was that, lacking zero, they had no way to indicate successful termination of their C programs.? (Robert Firth) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 896 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-emulation/attachments/20090903/8db22d63/signature.pgp From amvandemore at gmail.com Thu Sep 3 20:14:48 2009 From: amvandemore at gmail.com (Adam Vande More) Date: Thu Sep 3 20:14:54 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 4 In-Reply-To: <4AA0149E.30209@lapo.it> References: <20090527134343.GB1104@bsdcrew.de> <85d001330905270909jde4d723s65e8708a8b498c29@mail.gmail.com> <20090527163952.GI1104@bsdcrew.de> <4AA0149E.30209@lapo.it> Message-ID: <6201873e0909031252r41bced2eqe1784a17214f1cd1@mail.gmail.com> On Thu, Sep 3, 2009 at 2:10 PM, Lapo Luchini wrote: > Martin Wilke wrote: > >> /usr/ports/devel/kBuild/work/kBuild-0.1.5-p1/kBuild/footer.kmk:2304: *** > >> target file `virtualbox' has both : and :: entries. > >> Stop . > >> kmk: Leaving directory `/usr/ports/devel/kBuild/work/kBuild-0.1.5-p1' > >> gmake: *** > >> > [/usr/ports/devel/kBuild/work/kBuild-0.1.5-p1/out/freebsd.amd64/release/bootstrap/ts-stage2-build] > >> Error 2 > >> ./kBuild/env.sh: info: rc=2: gmake -f bootstrap.gmk > >> *** Error code 2 > > > >> Stop in /usr/ports/devel/kBuild. > >> " > > > > Please update to 7.2 or higher > > Errr, and what if I have that in a FreeBSD 7.2-STABLE? > Any other ideas? (both on my i386 laptop and amd64 home-server) > > Strangely I can find nothing on Google for that, which seems to indicate > very little people is trying VirtualBox on FreeBSD or both my unrelated > and different boxes have got a "rare" bug =) > > (but of course they got more or less the same mix of ports installed, so > they're not really unrelated one another) > > -- > Lapo Luchini - http://lapo.it/ > > ??one of the main causes of the fall of the Roman Empire was that, > lacking zero, they had no way to indicate successful termination of > their C programs.? (Robert Firth) > > Are you using portmaster to build virtualbox? -- Adam Vande More From lapo at lapo.it Fri Sep 4 04:14:22 2009 From: lapo at lapo.it (Lapo Luchini) Date: Fri Sep 4 04:14:29 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 4 In-Reply-To: <6201873e0909031252r41bced2eqe1784a17214f1cd1@mail.gmail.com> References: <20090527134343.GB1104@bsdcrew.de> <85d001330905270909jde4d723s65e8708a8b498c29@mail.gmail.com> <20090527163952.GI1104@bsdcrew.de> <4AA0149E.30209@lapo.it> <6201873e0909031252r41bced2eqe1784a17214f1cd1@mail.gmail.com> Message-ID: <4AA09410.8020302@lapo.it> Adam Vande More wrote: >>>/usr/ports/devel/kBuild/work/kBuild-0.1.5-p1/kBuild/footer.kmk:2304: *** >>> target file `virtualbox' has both : and :: entries. >>> >>> Please update to 7.2 or higher >> >> Errr, and what if I have that in a FreeBSD 7.2-STABLE? > > Are you using portmaster to build virtualbox? Yes indeed... and now that you say it, I tried a simple "cd emulators/virtualbox ; make install" and it worked! I wonder what does portmaster different to break only that specific port... -- Lapo Luchini - http://lapo.it/ ?Any sufficiently advanced technology is indistinguishable from magic.? (Arthur C. Clarke) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 896 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-emulation/attachments/20090904/e19b8583/signature.pgp From amvandemore at gmail.com Fri Sep 4 12:36:50 2009 From: amvandemore at gmail.com (Adam Vande More) Date: Fri Sep 4 12:38:28 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 4 In-Reply-To: <4AA09410.8020302@lapo.it> References: <20090527134343.GB1104@bsdcrew.de> <85d001330905270909jde4d723s65e8708a8b498c29@mail.gmail.com> <20090527163952.GI1104@bsdcrew.de> <4AA0149E.30209@lapo.it> <6201873e0909031252r41bced2eqe1784a17214f1cd1@mail.gmail.com> <4AA09410.8020302@lapo.it> Message-ID: <6201873e0909040536y2a2c7a22t30247d61adc26318@mail.gmail.com> On Thu, Sep 3, 2009 at 11:14 PM, Lapo Luchini wrote: > Adam Vande More wrote: > >>>/usr/ports/devel/kBuild/work/kBuild-0.1.5-p1/kBuild/footer.kmk:2304: *** > >>> target file `virtualbox' has both : and :: entries. > >>> > >>> Please update to 7.2 or higher > >> > >> Errr, and what if I have that in a FreeBSD 7.2-STABLE? > > > > Are you using portmaster to build virtualbox? > > Yes indeed... and now that you say it, I tried a simple > "cd emulators/virtualbox ; make install" > and it worked! > > I wonder what does portmaster different to break only that specific port... > > -- > Lapo Luchini - http://lapo.it/ > > ?Any sufficiently advanced technology is indistinguishable from magic.? > (Arthur C. Clarke) > > I believe portmaster uses a lot environmental variables, and kBuild does something funky with them. So technically, the issue lies w/ kBuild, not portmaster. At least that's what I read. -- Adam Vande More From julian at elischer.org Fri Sep 4 16:37:52 2009 From: julian at elischer.org (Julian Elischer) Date: Fri Sep 4 16:37:59 2009 Subject: problem with virtualbox bridge.. Message-ID: <4AA1425F.5030701@elischer.org> The new bridge code used netgraph so make sure you have netgraph and ng_ether nodes loaded..... I think. From avg at freebsd.org Fri Sep 4 17:15:17 2009 From: avg at freebsd.org (Andriy Gapon) Date: Fri Sep 4 17:15:28 2009 Subject: virtualbox 3.0.51r22226: some quirks In-Reply-To: <4A9E85C1.1090605@icyb.net.ua> References: <4A9E85C1.1090605@icyb.net.ua> Message-ID: <4AA146A2.1000007@freebsd.org> on 02/09/2009 17:48 Andriy Gapon said the following: > 2. Permanent shared directories disappear after VirtualBox restart. It seems that the following line always stays unchanged: I manually replaced it with the following: But when I started VirtualBox it immediately magically went back to the previous state. Although VirtualBox itself showed that share as configured and permanent. Seems like a bug in some configuration saving logic. -- Andriy Gapon From nox at jelal.kn-bremen.de Fri Sep 4 20:18:22 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Fri Sep 4 20:18:35 2009 Subject: experimental FreeBSD qemu-devel git head port update for testing In-Reply-To: <20090902175621.GA63905@triton8.kn-bremen.de> References: <20090829222339.GA93608@triton8.kn-bremen.de> <20090902175621.GA63905@triton8.kn-bremen.de> Message-ID: <20090904193435.GA77708@triton8.kn-bremen.de> On Wed, Sep 02, 2009 at 07:56:21PM +0200, Juergen Lock wrote: > On Sun, Aug 30, 2009 at 12:23:39AM +0200, Juergen Lock wrote: > > Hi! > > > > Jan Kiszka asked me if the unstable guest timer irq problem still > > exists on qemu git head, so I made an update for that today: > > http://people.freebsd.org/~nox/qemu/qemu-devel-20090829.patch > > (and found out it does.) > > > > The bad news (for FreeBSD users anyway) is kqemu support has now been > > removed as `promised' (by the upstream qemu developers), so testing this > > version is probably less interesting for many FreeBSD users than the > > qemu 0.11 stable branch snapshot I posted about here, > > http://lists.freebsd.org/pipermail/freebsd-emulation/2009-August/006646.html > > but e.g. users of non-x86 targets probably will still be interested. > > > > Also the pcap patch stopped working in this snapshot and I don't yet > > know why. (I think the original version of that patch was submitted by > > Jung-uk Kim, maybe he has an idea; Cc'd.) > > [...] > > Jung-uk Kim sent me a new pcap patch (thanx! :), and I have just included > it in the mentioned update at > http://people.freebsd.org/~nox/qemu/qemu-devel-20090829.patch New update at the same place, Jung-uk Kim sent me another version of the pcap patch and while I was at it I added the tap close patch and removed the dynticks patch since it seems to perform even worse than -clock unix on FreeBSD. :( Happy testing... Juergen From nox at jelal.kn-bremen.de Fri Sep 4 20:18:23 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Fri Sep 4 20:18:35 2009 Subject: [Qemu-devel] ANNOUNCE: Release 0.11.0-rc2 of QEMU In-Reply-To: <4AA11B9F.9050101@codemonkey.ws> References: <4AA11B9F.9050101@codemonkey.ws> Message-ID: <20090904201347.GA77929@triton8.kn-bremen.de> On Fri, Sep 04, 2009 at 08:52:31AM -0500, Anthony Liguori wrote: > The QEMU team is pleased to announce the availability of the 0.11.0-rc2 > release. This is the second release candidate for the 0.11.0 release. > This release contains only bug fixes since 0.11.0-rc1. > > Any bugs can be reported at http://bugs.launchpad.net/qemu/+bugs > > It can be downloaded from Savannah at: > > http://download.savannah.gnu.org/releases/qemu/qemu-0.11.0-rc2.tar.gz > Since I already made an experimental FreeBSD qemu-devel port update for 0.11.0 rc1 updating that to 0.11.0 rc2 was easy: http://people.freebsd.org/~nox/qemu/qemu-devel-0.11.0r2.patch (I changed two things tho, see below.) > The following fixes have been added since qemu-0.11.0-rc1: > > - mips: fix conditional move off fp conditions codes (Nath Froyd) > - fix migration to obey -S (Paolo Bonzini) > - remove pc-0-10 machine type (Mark McLoughlin) > - vnc: fix copyrect screen corruption (Gerd Hoffman) > - fix vm state change handlers running order (Markus Armbruster) > - e1000: fix eerc and ics emulation (Bill Paul) > - fix sdl zooming with pl110 (Blue Swirl) > - sparc64: flush pending conditional evaluations (Igor Kovalenko) > - esp: fix interrupt register read (Blue Swirl) > - option rom makefile fixes (Paul Brook) > - fix sparse warnings (Blue Swirl) > - fix symfind (Laurent Desnogues) > - win32: fix default prefix (Stefan Weil) > - fix checksum writing in signboot (Alex Graf) > - fix sdl window resize (Stefano Stabellini) > - do not resize the screen on hw_invalidate (Stefano Stabellini) > - Add checks for -smbios option (Beth Kon) > - fix do_set_link (Luiz Capitulino) > - fix do_commit behavior (Luiz Capitulino) > - make windows notice media change (Gleb Natapov) > - check for PR_SET_NAME being defined (Nathan Froyd) > - fix migration for ide devices (Anthony Liguori) > - Use correct depth in vmware vga (Reimar Doffiner) This seems to work well, I now can run a Linux iso with -vga vmware and vmmouse and set all kinds of resolutions in the guest using xrandr. Thanx! > - support 32bpp cursors in sdl (Reimar Doffinger) > - fix device name completion for eject (Blue Swirl) > - make screendump use DisplayState properly (Stefano Stabellini) > - fix autostart with live migration (Avi Kivity) > - fix detached migration with exec (Chris Lalancette) > - fix segv when changing vnc password in sdl (Zach Amsden) > - fix vnc password clearing with stdio monitor (Zach Amsden) > - clean up VGA type selection (Zach Amsden) > - add missing linefeed in error message (Stefan Weil) Ok now what I changed: I removed the dynticks patch since it seems to perform even worse than -clock unix on FreeBSD (does this count as a qemu bug? The problem seems to be that FreeBSD's POSIX `realtime' timers still only count in increments of HZ, and then seem to always round up too.) And -clock unix is only marginally better, see my post here: http://lists.gnu.org/archive/html/qemu-devel/2009-09/msg00049.html (well at least its good enough that Linux guest kernels don't fail to boot like with -clock dynticks.) The second change is a small patch to tap_cleanup that makes it close the tap fd before calling the ifdown script instead of after, otherwise FreeBSD's tap driver may hit a KASSERT in case the ifdown script does something like an `ifconfig tap0 destroy'... Index: qemu/net.c @@ -1643,12 +1643,13 @@ static void tap_cleanup(VLANClientState qemu_purge_queued_packets(vc); - if (s->down_script[0]) - launch_script(s->down_script, s->down_script_arg, s->fd); - tap_read_poll(s, 0); tap_write_poll(s, 0); close(s->fd); + + if (s->down_script[0]) + launch_script(s->down_script, s->down_script_arg, -1); + qemu_free(s); } I don't know if there are use cases where the ifdown script needs the tap fd still open, otherwise I guess this can also be committed upstream. And in case you want to: :) Signed-off-by: Juergen Lock From rondzierwa at comcast.net Fri Sep 4 22:23:08 2009 From: rondzierwa at comcast.net (rondzierwa@comcast.net) Date: Fri Sep 4 22:23:15 2009 Subject: VirtualBox bridged adapter (vboxnetflt) Message-ID: <1636246179.7585961252102987506.JavaMail.root@sz0128a.westchester.pa.mail.comcast.net> I am running FreeBSD 7.2-RELEASE-p2 on i386. I fetched the virtualbox-3.0.51r22226 port and followed your directions in your posting to the emulators mailing list i found on 22-aug. i did a "make clean patch", then applied the two patches http://www.shapeshifter.se/pub/patches/vbox-freebsd-network.patch http://www.shapeshifter.se/pub/patches/virtualbox-Makefile.patch did a make install and got compile errors: kBuild: Compiling vboxdrv - /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/HostDrivers/Suppor t/freebsd/SUPDrv-freebsd.c /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/HostDrivers/VBoxNetFlt/freebsd/VBoxNetFlt-free bsd.c: In function 'vboxNetFltOsInitInstance': /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/HostDrivers/VBoxNetFlt/freebsd/VBoxNetFlt-free bsd.c:330: warning: implicit declaration of function 'ifunit_ref' /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/HostDrivers/VBoxNetFlt/freebsd/VBoxNetFlt-free bsd.c:330: warning: nested extern declaration of 'ifunit_ref' /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/HostDrivers/VBoxNetFlt/freebsd/VBoxNetFlt-free bsd.c:330: warning: assignment makes pointer from integer without a cast /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/HostDrivers/VBoxNetFlt/freebsd/VBoxNetFlt-free bsd.c:337: error: 'struct ifnet' has no member named 'if_transmit' /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/HostDrivers/VBoxNetFlt/freebsd/VBoxNetFlt-free bsd.c: In function 'vboxNetFltOsMaybeRediscovered': /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/HostDrivers/VBoxNetFlt/freebsd/VBoxNetFlt-free bsd.c:357: error: 'struct ifnet' has no member named 'if_transmit' /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/HostDrivers/VBoxNetFlt/freebsd/VBoxNetFlt-free bsd.c:359: warning: implicit declaration of function 'if_rele' /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/HostDrivers/VBoxNetFlt/freebsd/VBoxNetFlt-free bsd.c:359: warning: nested extern declaration of 'if_rele' /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/HostDrivers/VBoxNetFlt/freebsd/VBoxNetFlt-free bsd.c: In function 'vboxNetFltOsDeleteInstance': /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/HostDrivers/VBoxNetFlt/freebsd/VBoxNetFlt-free bsd.c:374: error: 'struct ifnet' has no member named 'if_transmit' /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/HostDrivers/VBoxNetFlt/freebsd/VBoxNetFlt-free bsd.c: In function 'vboxNetFltPortOsSetActive': /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/HostDrivers/VBoxNetFlt/freebsd/VBoxNetFlt-free bsd.c:402: error: 'struct ifnet' has no member named 'if_transmit' /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/HostDrivers/VBoxNetFlt/freebsd/VBoxNetFlt-free bsd.c:410: error: 'struct ifnet' has no member named 'if_transmit' which version do these patches work with? thanks, ron. From fli at shapeshifter.se Sat Sep 5 07:44:00 2009 From: fli at shapeshifter.se (Fredrik Lindberg) Date: Sat Sep 5 07:44:07 2009 Subject: VirtualBox bridged adapter (vboxnetflt) In-Reply-To: <1636246179.7585961252102987506.JavaMail.root@sz0128a.westchester.pa.mail.comcast.net> References: <1636246179.7585961252102987506.JavaMail.root@sz0128a.westchester.pa.mail.comcast.net> Message-ID: <4AA216BB.6000609@shapeshifter.se> rondzierwa@comcast.net wrote: > I am running FreeBSD 7.2-RELEASE-p2 on i386. I fetched the virtualbox-3.0.51r22226 port and > followed your directions in your posting to the emulators mailing list i found on 22-aug. > > i did a "make clean patch", then applied the two patches > http://www.shapeshifter.se/pub/patches/vbox-freebsd-network.patch > http://www.shapeshifter.se/pub/patches/virtualbox-Makefile.patch > > did a make install and got compile errors: > > which version do these patches work with? > The first set of patches only worked on 8.0, I posted a set of new patches a few days ago, please take a look at http://lists.freebsd.org/pipermail/freebsd-emulation/2009-September/006740.html Fredrik From edwin at FreeBSD.org Sat Sep 5 12:00:29 2009 From: edwin at FreeBSD.org (edwin@FreeBSD.org) Date: Sat Sep 5 12:00:41 2009 Subject: ports/138545: Update request for audio/linux-f10-alsa-lib Message-ID: <200909051200.n85C0TmU093421@freefall.freebsd.org> Synopsis: Update request for audio/linux-f10-alsa-lib Responsible-Changed-From-To: freebsd-ports-bugs->emulation Responsible-Changed-By: edwin Responsible-Changed-When: Sat Sep 5 12:00:28 UTC 2009 Responsible-Changed-Why: Over to maintainer (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=138545 From edwin at FreeBSD.org Sat Sep 5 12:10:13 2009 From: edwin at FreeBSD.org (edwin@FreeBSD.org) Date: Sat Sep 5 12:10:24 2009 Subject: ports/138546: Update request for x11/linux-f10-xorg-libs Message-ID: <200909051210.n85CADpC003651@freefall.freebsd.org> Synopsis: Update request for x11/linux-f10-xorg-libs Responsible-Changed-From-To: freebsd-ports-bugs->freebsd-emulation Responsible-Changed-By: edwin Responsible-Changed-When: Sat Sep 5 12:10:12 UTC 2009 Responsible-Changed-Why: Over to maintainer (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=138546 From nox at jelal.kn-bremen.de Sat Sep 5 15:06:16 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Sat Sep 5 15:06:22 2009 Subject: experimental FreeBSD qemu-devel git head port update for testing In-Reply-To: <20090904193435.GA77708@triton8.kn-bremen.de> References: <20090829222339.GA93608@triton8.kn-bremen.de> <20090902175621.GA63905@triton8.kn-bremen.de> <20090904193435.GA77708@triton8.kn-bremen.de> Message-ID: <20090905150334.GA55989@triton8.kn-bremen.de> On Fri, Sep 04, 2009 at 09:34:35PM +0200, Juergen Lock wrote: > On Wed, Sep 02, 2009 at 07:56:21PM +0200, Juergen Lock wrote: > > On Sun, Aug 30, 2009 at 12:23:39AM +0200, Juergen Lock wrote: > > > Hi! > > > > > > Jan Kiszka asked me if the unstable guest timer irq problem still > > > exists on qemu git head, so I made an update for that today: > > > http://people.freebsd.org/~nox/qemu/qemu-devel-20090829.patch > > > (and found out it does.) > > > > > > The bad news (for FreeBSD users anyway) is kqemu support has now been > > > removed as `promised' (by the upstream qemu developers), so testing this > > > version is probably less interesting for many FreeBSD users than the > > > qemu 0.11 stable branch snapshot I posted about here, > > > http://lists.freebsd.org/pipermail/freebsd-emulation/2009-August/006646.html > > > but e.g. users of non-x86 targets probably will still be interested. > > > > > > Also the pcap patch stopped working in this snapshot and I don't yet > > > know why. (I think the original version of that patch was submitted by > > > Jung-uk Kim, maybe he has an idea; Cc'd.) > > > [...] > > > > Jung-uk Kim sent me a new pcap patch (thanx! :), and I have just included > > it in the mentioned update at > > http://people.freebsd.org/~nox/qemu/qemu-devel-20090829.patch > > New update at the same place, Jung-uk Kim sent me another version of the > pcap patch and while I was at it I added the tap close patch and removed > the dynticks patch since it seems to perform even worse than -clock unix > on FreeBSD. :( I forgot to mention this update also fixes the build on FreeBSD 7 (libmath didn't get built properly), apologies if you were affected... Juergen From dougb at FreeBSD.org Sat Sep 5 20:13:27 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Sat Sep 5 20:13:38 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 4 In-Reply-To: <6201873e0909040536y2a2c7a22t30247d61adc26318@mail.gmail.com> References: <20090527134343.GB1104@bsdcrew.de> <85d001330905270909jde4d723s65e8708a8b498c29@mail.gmail.com> <20090527163952.GI1104@bsdcrew.de> <4AA0149E.30209@lapo.it> <6201873e0909031252r41bced2eqe1784a17214f1cd1@mail.gmail.com> <4AA09410.8020302@lapo.it> <6201873e0909040536y2a2c7a22t30247d61adc26318@mail.gmail.com> Message-ID: <4AA2C659.8050800@FreeBSD.org> Adam Vande More wrote: > I believe portmaster uses a lot environmental variables, and kBuild does > something funky with them. So technically, the issue lies w/ kBuild, not > portmaster. At least that's what I read. Yes, that's correct. Doug From gulanito at gmail.com Sat Sep 5 21:17:31 2009 From: gulanito at gmail.com (gula nito) Date: Sat Sep 5 21:17:37 2009 Subject: linux-nero no device detected Message-ID: Hi. I install linux-nero from ports today. The program runs well but at the begin it says two warnings: Code: Your /proc directory not seems to be mounted Please check your linux installation And Code: No device detected. Nero Linux was not able to acces any physical device. Please check your system configuration. I have linux proc mounted (linproc /usr/compat/linux/proc linprocfs rw 0 0 in /etc/fstab) And I have linux_enable="YES" in rc.conf. Thanks for help. From danny at cs.huji.ac.il Sun Sep 6 11:07:38 2009 From: danny at cs.huji.ac.il (Danny Braniss) Date: Sun Sep 6 11:07:44 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 6 In-Reply-To: <20090611194557.GC98175@bsdcrew.de> References: <20090611194557.GC98175@bsdcrew.de> Message-ID: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Huhu, > > Yes we life and that's good :-). > Changes: > > - Fix build error when compiling in debug mode on FreeBSD HEAD > - SemEvent?-r0drv/FreeBSD: Don't use tvtohz for an infinite timeout. > - Some FreeBSD relate typos > - Enable shared OpenGL service. Completely untested due to lack of > appropriate hardware but it compiles at least > - Add support for shared clipboards. Requires libXt > - FreeBSD: Implement preemption API for guest SMP and enable > it (slightly tested). Add neccessary RTMP* methods in userspace > for the frontends to detect the number of CPUs > - Runtime/semevent-r0drv-freebsd: Use a sleeping mutex > instead of a spinlock to fix the problems users are seeing > (assertions with debugging enabled) while still being able > to run on 100Hz hosts. No problems detected so far and Solaris > doesn't use a spin mutex in this code too so it shouldn't do > any harm (keeping fingers crossed)space for the frontends to > detect the number of CPUs > - Add support for curl > - Add VBoxSharedClipboard > > Ports Changes; > - Force guestadditions version to 2.2.4 > - Removed Qt3 include replacements (already upstream) > - Removed cosmetic X11 include path patch > > Please make SURE, your world and kernel is in sync and you've read > the pkg-messages. Also please unload the kernel module before > you update the port ;-). > > Many thx to all Vbox Devs, All supporters, my nice team! :-) > > http://people.freebsd.org/~miwi/vbox/virtualbox_6.tgz > > Happy Testing! > ok, so some time has passed, but virtualbox-2.2.51r20457.tar.gz is no longer available, there is a ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/virtualbox-2.2.51r20457.tar.bz2 then again in ports/emulatores/virtualbox the version is 3.0.51r22226, can someone please explain? danny From markmc at redhat.com Sun Sep 6 12:51:28 2009 From: markmc at redhat.com (Mark McLoughlin) Date: Sun Sep 6 12:51:34 2009 Subject: close tapfd before running down_script [was Re: [Qemu-devel] ANNOUNCE: Release 0.11.0-rc2 of QEMU] In-Reply-To: <20090904201347.GA77929@triton8.kn-bremen.de> References: <4AA11B9F.9050101@codemonkey.ws> <20090904201347.GA77929@triton8.kn-bremen.de> Message-ID: <1252241425.3191.81.camel@blaa> On Fri, 2009-09-04 at 22:13 +0200, Juergen Lock wrote: > The second change is a small patch to tap_cleanup that makes it close > the tap fd before calling the ifdown script instead of after, otherwise > FreeBSD's tap driver may hit a KASSERT in case the ifdown script does > something like an `ifconfig tap0 destroy'... > > Index: qemu/net.c > @@ -1643,12 +1643,13 @@ static void tap_cleanup(VLANClientState > > qemu_purge_queued_packets(vc); > > - if (s->down_script[0]) > - launch_script(s->down_script, s->down_script_arg, s->fd); > - > tap_read_poll(s, 0); > tap_write_poll(s, 0); > close(s->fd); > + > + if (s->down_script[0]) > + launch_script(s->down_script, s->down_script_arg, -1); > + > qemu_free(s); > } > > I don't know if there are use cases where the ifdown script needs the > tap fd still open, otherwise I guess this can also be committed upstream. > And in case you want to: :) > > Signed-off-by: Juergen Lock I don't ever use the the down script myself, but a couple of things to bear in mind: a) 0.9.1 never actually closed the tap fd and since 0.10.0 we've been closing the fd after calling the script b) where qemu creates the tap interface, by closing the tap fd before the script we'd be destroying the interface before passing the interface name to the script The current behaviour seems right to me. Could you explain your use case a bit more? Maybe post the up and down scripts? Cheers, Mark. From bsam at FreeBSD.org Sun Sep 6 14:25:24 2009 From: bsam at FreeBSD.org (bsam@FreeBSD.org) Date: Sun Sep 6 14:25:30 2009 Subject: ports/138545: Update request for audio/linux-f10-alsa-lib Message-ID: <200909061425.n86EPNYQ017515@freefall.freebsd.org> Synopsis: Update request for audio/linux-f10-alsa-lib State-Changed-From-To: open->closed State-Changed-By: bsam State-Changed-When: Sun Sep 6 14:25:03 UTC 2009 State-Changed-Why: The port is fixed. Thanks for the PR. http://www.freebsd.org/cgi/query-pr.cgi?pr=138545 From dfilter at FreeBSD.ORG Sun Sep 6 14:30:10 2009 From: dfilter at FreeBSD.ORG (dfilter service) Date: Sun Sep 6 14:30:18 2009 Subject: ports/138545: commit references a PR Message-ID: <200909061430.n86EUA8r017904@freefall.freebsd.org> The following reply was made to PR ports/138545; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: ports/138545: commit references a PR Date: Sun, 6 Sep 2009 14:24:47 +0000 (UTC) bsam 2009-09-06 14:24:39 UTC FreeBSD ports repository Modified files: audio/linux-f10-alsa-lib Makefile distinfo.i386 pkg-plist Log: Update to version 1.0.21. PR: ports/138545 Requested by: Grzegorz Blach Revision Changes Path 1.14 +1 -1 ports/audio/linux-f10-alsa-lib/Makefile 1.9 +6 -6 ports/audio/linux-f10-alsa-lib/distinfo.i386 1.5 +6 -5 ports/audio/linux-f10-alsa-lib/pkg-plist _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org" From bsam at FreeBSD.org Sun Sep 6 14:31:30 2009 From: bsam at FreeBSD.org (bsam@FreeBSD.org) Date: Sun Sep 6 14:31:36 2009 Subject: ports/138546: Update request for x11/linux-f10-xorg-libs Message-ID: <200909061431.n86EVUJM028084@freefall.freebsd.org> Synopsis: Update request for x11/linux-f10-xorg-libs State-Changed-From-To: open->closed State-Changed-By: bsam State-Changed-When: Sun Sep 6 14:31:15 UTC 2009 State-Changed-Why: The port is fixed. Thanks for the PR. http://www.freebsd.org/cgi/query-pr.cgi?pr=138546 From dfilter at FreeBSD.ORG Sun Sep 6 14:40:05 2009 From: dfilter at FreeBSD.ORG (dfilter service) Date: Sun Sep 6 14:40:11 2009 Subject: ports/138546: commit references a PR Message-ID: <200909061440.n86Ee5ue029045@freefall.freebsd.org> The following reply was made to PR ports/138546; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: ports/138546: commit references a PR Date: Sun, 6 Sep 2009 14:31:07 +0000 (UTC) bsam 2009-09-06 14:30:58 UTC FreeBSD ports repository Modified files: x11/linux-f10-xorg-libs Makefile distinfo.i386 Log: Update libX11 to version 1.1.5-4.fc10. PR: ports/138546 Requested by: Grzegorz Blach Revision Changes Path 1.15 +2 -2 ports/x11/linux-f10-xorg-libs/Makefile 1.10 +6 -6 ports/x11/linux-f10-xorg-libs/distinfo.i386 _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org" From odhiambo at gmail.com Sun Sep 6 15:35:08 2009 From: odhiambo at gmail.com (Odhiambo Washington) Date: Sun Sep 6 15:35:26 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 6 In-Reply-To: References: <20090611194557.GC98175@bsdcrew.de> Message-ID: <991123400909060811u9bea4d9rdbf453dfaae7c185@mail.gmail.com> On Sun, Sep 6, 2009 at 1:40 PM, Danny Braniss wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Huhu, > > > > Yes we life and that's good :-). > > Changes: > > > > - Fix build error when compiling in debug mode on FreeBSD HEAD > > - SemEvent?-r0drv/FreeBSD: Don't use tvtohz for an infinite timeout. > > - Some FreeBSD relate typos > > - Enable shared OpenGL service. Completely untested due to lack of > > appropriate hardware but it compiles at least > > - Add support for shared clipboards. Requires libXt > > - FreeBSD: Implement preemption API for guest SMP and enable > > it (slightly tested). Add neccessary RTMP* methods in userspace > > for the frontends to detect the number of CPUs > > - Runtime/semevent-r0drv-freebsd: Use a sleeping mutex > > instead of a spinlock to fix the problems users are seeing > > (assertions with debugging enabled) while still being able > > to run on 100Hz hosts. No problems detected so far and Solaris > > doesn't use a spin mutex in this code too so it shouldn't do > > any harm (keeping fingers crossed)space for the frontends to > > detect the number of CPUs > > - Add support for curl > > - Add VBoxSharedClipboard > > > > Ports Changes; > > - Force guestadditions version to 2.2.4 > > - Removed Qt3 include replacements (already upstream) > > - Removed cosmetic X11 include path patch > > > > Please make SURE, your world and kernel is in sync and you've read > > the pkg-messages. Also please unload the kernel module before > > you update the port ;-). > > > > Many thx to all Vbox Devs, All supporters, my nice team! :-) > > > > http://people.freebsd.org/~miwi/vbox/virtualbox_6.tgz > > > > Happy Testing! > > > ok, so some time has passed, but virtualbox-2.2.51r20457.tar.gz is no > longer available, there is a > ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/virtualbox-2.2.51r20457.tar.bz2 > then again in ports/emulatores/virtualbox the version is 3.0.51r22226, > > can someone please explain? > > And on my FreeBSD 7.2-STABLE, compiling virtualbox fails as follows: kBuild: Linking VBoxREM64 kBuild: Installing VBoxREM64 => /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/out/freebsd.x86/release/bin/VBox REM64.so kmk[2]: Leaving directory `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226' kmk[1]: Leaving directory `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226' kBuild: Pass - Programs kmk[1]: Entering directory `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226' kmk[2]: Entering directory `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226' kBuild: Compiling tstAPI - /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/Main/testcase/tstAPI.cpp kBuild: Linking tstAPI /usr/local/lib/libssl.so.5: undefined reference to `d2i_X509_EXTENSIONS' /usr/local/lib/libssl.so.5: undefined reference to `ENGINE_get_ssl_client_cert_function' /usr/local/lib/libssl.so.5: undefined reference to `HMAC_CTX_set_flags' /usr/local/lib/libssl.so.5: undefined reference to `i2d_X509_EXTENSIONS' /usr/local/lib/libssl.so.5: undefined reference to `ENGINE_load_ssl_client_cert' /usr/local/lib/libssl.so.5: undefined reference to `pqueue_size' /usr/local/lib/libssl.so.5: undefined reference to `EVP_idea_cbc' kmk[2]: *** [/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/out/freebsd.x86/release/obj/tstAPI/tstAPI] Error 1 The failing command: @g++ '-Wl,-rpath,/usr/local/lib/virtualbox' -m32 -o /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r 22226/out/freebsd.x86/release/obj/tstAPI/tstAPI /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/out/freebsd.x86/ release/obj/tstAPI/tstAPI.o -L/usr/lib -L/usr/X11R6/lib -L/usr/local/lib /usr/ports/emulators/virtualbox/work/virtualbo x-3.0.51r22226/out/freebsd.x86/release/bin/VBoxRT.so /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/out/freeb sd.x86/release/lib/VBoxCOM.a /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/out/freebsd.x86/release/bin/VBoxX PCOM.so kmk[2]: Leaving directory `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226' kmk[1]: *** [pass_binaries_this] Error 2 kmk[1]: Leaving directory `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226' kmk: *** [pass_binaries_order] Error 2 *** Error code 2 Stop in /usr/ports/emulators/virtualbox. I hope someone can advise on what is needed. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ "If you have nothing good to say about someone, just shut up!." -- Lucky Dube From nox at jelal.kn-bremen.de Sun Sep 6 15:46:35 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Sun Sep 6 15:46:42 2009 Subject: close tapfd before running down_script [was Re: [Qemu-devel] ANNOUNCE: Release 0.11.0-rc2 of QEMU] In-Reply-To: <1252241425.3191.81.camel@blaa> References: <4AA11B9F.9050101@codemonkey.ws> <20090904201347.GA77929@triton8.kn-bremen.de> <1252241425.3191.81.camel@blaa> Message-ID: <20090906154315.GA88187@triton8.kn-bremen.de> On Sun, Sep 06, 2009 at 01:50:25PM +0100, Mark McLoughlin wrote: > On Fri, 2009-09-04 at 22:13 +0200, Juergen Lock wrote: > > > The second change is a small patch to tap_cleanup that makes it close > > the tap fd before calling the ifdown script instead of after, otherwise > > FreeBSD's tap driver may hit a KASSERT in case the ifdown script does > > something like an `ifconfig tap0 destroy'... > > > > Index: qemu/net.c > > @@ -1643,12 +1643,13 @@ static void tap_cleanup(VLANClientState > > > > qemu_purge_queued_packets(vc); > > > > - if (s->down_script[0]) > > - launch_script(s->down_script, s->down_script_arg, s->fd); > > - > > tap_read_poll(s, 0); > > tap_write_poll(s, 0); > > close(s->fd); > > + > > + if (s->down_script[0]) > > + launch_script(s->down_script, s->down_script_arg, -1); > > + > > qemu_free(s); > > } > > > > I don't know if there are use cases where the ifdown script needs the > > tap fd still open, otherwise I guess this can also be committed upstream. > > And in case you want to: :) > > > > Signed-off-by: Juergen Lock > > I don't ever use the the down script myself, but a couple of things to > bear in mind: > > a) 0.9.1 never actually closed the tap fd and since 0.10.0 we've > been closing the fd after calling the script > > b) where qemu creates the tap interface, by closing the tap fd before > the script we'd be destroying the interface before passing the > interface name to the script > Ah, then that sounds like a difference between Linux and FreeBSD, on FreeBSD the tap interface continues to exist after closing the fd... (which is why these scripts call `ifconfig tapX destroy' in the first place.) > The current behaviour seems right to me. Could you explain your use case > a bit more? Maybe post the up and down scripts? Here's the thread that started this: http://lists.freebsd.org/pipermail/freebsd-emulation/2009-August/006700.html And here is FreeBSD's tap_destroy() fn with the mentioned KASSERT: http://fxr.watson.org/fxr/source/net/if_tap.c#L213 Anyway, sounds like the patch is the wrong thing to do on Linux hosts so I guess I'll just keep it private to the FreeBSD port(s)... (Or should I repost it with an #ifdef __FreeBSD__ etc?) Thanx, Juergen From miwi at FreeBSD.org Sun Sep 6 16:25:49 2009 From: miwi at FreeBSD.org (Martin Wilke) Date: Sun Sep 6 16:26:03 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 6 In-Reply-To: <991123400909060811u9bea4d9rdbf453dfaae7c185@mail.gmail.com> References: <20090611194557.GC98175@bsdcrew.de> <991123400909060811u9bea4d9rdbf453dfaae7c185@mail.gmail.com> Message-ID: <20090906162544.GA39448@bsdcrew.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, Sep 06, 2009 at 06:11:48PM +0300, Odhiambo Washington wrote: > On Sun, Sep 6, 2009 at 1:40 PM, Danny Braniss wrote: > > > > -----BEGIN PGP SIGNED MESSAGE----- > > > Hash: SHA1 > > > > > > Huhu, > > > > > > Yes we life and that's good :-). > > > Changes: > > > > > > - Fix build error when compiling in debug mode on FreeBSD HEAD > > > - SemEvent?-r0drv/FreeBSD: Don't use tvtohz for an infinite timeout. > > > - Some FreeBSD relate typos > > > - Enable shared OpenGL service. Completely untested due to lack of > > > appropriate hardware but it compiles at least > > > - Add support for shared clipboards. Requires libXt > > > - FreeBSD: Implement preemption API for guest SMP and enable > > > it (slightly tested). Add neccessary RTMP* methods in userspace > > > for the frontends to detect the number of CPUs > > > - Runtime/semevent-r0drv-freebsd: Use a sleeping mutex > > > instead of a spinlock to fix the problems users are seeing > > > (assertions with debugging enabled) while still being able > > > to run on 100Hz hosts. No problems detected so far and Solaris > > > doesn't use a spin mutex in this code too so it shouldn't do > > > any harm (keeping fingers crossed)space for the frontends to > > > detect the number of CPUs > > > - Add support for curl > > > - Add VBoxSharedClipboard > > > > > > Ports Changes; > > > - Force guestadditions version to 2.2.4 > > > - Removed Qt3 include replacements (already upstream) > > > - Removed cosmetic X11 include path patch > > > > > > Please make SURE, your world and kernel is in sync and you've read > > > the pkg-messages. Also please unload the kernel module before > > > you update the port ;-). > > > > > > Many thx to all Vbox Devs, All supporters, my nice team! :-) > > > > > > http://people.freebsd.org/~miwi/vbox/virtualbox_6.tgz > > > > > > Happy Testing! > > > > > ok, so some time has passed, but virtualbox-2.2.51r20457.tar.gz is no > > longer available, there is a > > ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/virtualbox-2.2.51r20457.tar.bz2 > > then again in ports/emulatores/virtualbox the version is 3.0.51r22226, > > > > can someone please explain? > > > > > > > And on my FreeBSD 7.2-STABLE, compiling virtualbox fails as follows: > > > > kBuild: Linking VBoxREM64 > kBuild: Installing VBoxREM64 => > /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/out/freebsd.x86/release/bin/VBox > REM64.so > kmk[2]: Leaving directory > `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226' > kmk[1]: Leaving directory > `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226' > kBuild: Pass - Programs > kmk[1]: Entering directory > `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226' > kmk[2]: Entering directory > `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226' > kBuild: Compiling tstAPI - > /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/Main/testcase/tstAPI.cpp > kBuild: Linking tstAPI > /usr/local/lib/libssl.so.5: undefined reference to `d2i_X509_EXTENSIONS' > /usr/local/lib/libssl.so.5: undefined reference to > `ENGINE_get_ssl_client_cert_function' > /usr/local/lib/libssl.so.5: undefined reference to `HMAC_CTX_set_flags' > /usr/local/lib/libssl.so.5: undefined reference to `i2d_X509_EXTENSIONS' > /usr/local/lib/libssl.so.5: undefined reference to > `ENGINE_load_ssl_client_cert' > /usr/local/lib/libssl.so.5: undefined reference to `pqueue_size' > /usr/local/lib/libssl.so.5: undefined reference to `EVP_idea_cbc' > kmk[2]: *** > [/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/out/freebsd.x86/release/obj/tstAPI/tstAPI] > Error 1 > The failing command: > @g++ '-Wl,-rpath,/usr/local/lib/virtualbox' -m32 -o > /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r > 22226/out/freebsd.x86/release/obj/tstAPI/tstAPI > /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/out/freebsd.x86/ > release/obj/tstAPI/tstAPI.o -L/usr/lib -L/usr/X11R6/lib > -L/usr/local/lib > /usr/ports/emulators/virtualbox/work/virtualbo > x-3.0.51r22226/out/freebsd.x86/release/bin/VBoxRT.so > /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/out/freeb > sd.x86/release/lib/VBoxCOM.a > /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/out/freebsd.x86/release/bin/VBoxX > PCOM.so > kmk[2]: Leaving directory > `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226' > kmk[1]: *** [pass_binaries_this] Error 2 > kmk[1]: Leaving directory > `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226' > kmk: *** [pass_binaries_order] Error 2 > *** Error code 2 > > Stop in /usr/ports/emulators/virtualbox. > > > I hope someone can advise on what is needed. > deinstall openssl from ports and try again :) > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254733744121/+254722743223 > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > "If you have nothing good to say about someone, just shut up!." > -- Lucky Dube - -- +-----------------------+-------------------------------+ | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | | Skype : splash_111 | Mail : miwi(at)FreeBSD.org | +-----------------------+-------------------------------+ | Mess with the Best, Die like the Rest! | +-----------------------+-------------------------------+ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iEYEARECAAYFAkqj4ogACgkQdLJIhLHm/OlShwCeJRqpqaBYbehqpKKfugxWD0PD OdEAmQFSfdfWNXvO/vTRLj5vxIsD5EwP =gbCY -----END PGP SIGNATURE----- From odhiambo at gmail.com Sun Sep 6 18:50:45 2009 From: odhiambo at gmail.com (Odhiambo Washington) Date: Sun Sep 6 18:50:58 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 6 In-Reply-To: <20090906162544.GA39448@bsdcrew.de> References: <20090611194557.GC98175@bsdcrew.de> <991123400909060811u9bea4d9rdbf453dfaae7c185@mail.gmail.com> <20090906162544.GA39448@bsdcrew.de> Message-ID: <991123400909061150h56dc6e07uf8d8e721f6c923bf@mail.gmail.com> On Sun, Sep 6, 2009 at 7:25 PM, Martin Wilke wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Sun, Sep 06, 2009 at 06:11:48PM +0300, Odhiambo Washington wrote: > > On Sun, Sep 6, 2009 at 1:40 PM, Danny Braniss > wrote: > > > > > > -----BEGIN PGP SIGNED MESSAGE----- > > > > Hash: SHA1 > > > > > > > > Huhu, > > > > > > > > Yes we life and that's good :-). > > > > Changes: > > > > > > > > - Fix build error when compiling in debug mode on FreeBSD HEAD > > > > - SemEvent?-r0drv/FreeBSD: Don't use tvtohz for an infinite > timeout. > > > > - Some FreeBSD relate typos > > > > - Enable shared OpenGL service. Completely untested due to lack of > > > > appropriate hardware but it compiles at least > > > > - Add support for shared clipboards. Requires libXt > > > > - FreeBSD: Implement preemption API for guest SMP and enable > > > > it (slightly tested). Add neccessary RTMP* methods in userspace > > > > for the frontends to detect the number of CPUs > > > > - Runtime/semevent-r0drv-freebsd: Use a sleeping mutex > > > > instead of a spinlock to fix the problems users are seeing > > > > (assertions with debugging enabled) while still being able > > > > to run on 100Hz hosts. No problems detected so far and Solaris > > > > doesn't use a spin mutex in this code too so it shouldn't do > > > > any harm (keeping fingers crossed)space for the frontends to > > > > detect the number of CPUs > > > > - Add support for curl > > > > - Add VBoxSharedClipboard > > > > > > > > Ports Changes; > > > > - Force guestadditions version to 2.2.4 > > > > - Removed Qt3 include replacements (already upstream) > > > > - Removed cosmetic X11 include path patch > > > > > > > > Please make SURE, your world and kernel is in sync and you've read > > > > the pkg-messages. Also please unload the kernel module before > > > > you update the port ;-). > > > > > > > > Many thx to all Vbox Devs, All supporters, my nice team! :-) > > > > > > > > http://people.freebsd.org/~miwi/vbox/virtualbox_6.tgz > > > > > > > > > Happy Testing! > > > > > > > ok, so some time has passed, but virtualbox-2.2.51r20457.tar.gz is no > > > longer available, there is a > > > > ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/virtualbox-2.2.51r20457.tar.bz2 > > > then again in ports/emulatores/virtualbox the version is 3.0.51r22226, > > > > > > can someone please explain? > > > > > > > > > > > > And on my FreeBSD 7.2-STABLE, compiling virtualbox fails as follows: > > > > > > > > kBuild: Linking VBoxREM64 > > kBuild: Installing VBoxREM64 => > > > /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/out/freebsd.x86/release/bin/VBox > > REM64.so > > kmk[2]: Leaving directory > > `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226' > > kmk[1]: Leaving directory > > `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226' > > kBuild: Pass - Programs > > kmk[1]: Entering directory > > `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226' > > kmk[2]: Entering directory > > `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226' > > kBuild: Compiling tstAPI - > > > /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/Main/testcase/tstAPI.cpp > > kBuild: Linking tstAPI > > /usr/local/lib/libssl.so.5: undefined reference to `d2i_X509_EXTENSIONS' > > /usr/local/lib/libssl.so.5: undefined reference to > > `ENGINE_get_ssl_client_cert_function' > > /usr/local/lib/libssl.so.5: undefined reference to `HMAC_CTX_set_flags' > > /usr/local/lib/libssl.so.5: undefined reference to `i2d_X509_EXTENSIONS' > > /usr/local/lib/libssl.so.5: undefined reference to > > `ENGINE_load_ssl_client_cert' > > /usr/local/lib/libssl.so.5: undefined reference to `pqueue_size' > > /usr/local/lib/libssl.so.5: undefined reference to `EVP_idea_cbc' > > kmk[2]: *** > > > [/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/out/freebsd.x86/release/obj/tstAPI/tstAPI] > > Error 1 > > The failing command: > > @g++ '-Wl,-rpath,/usr/local/lib/virtualbox' -m32 -o > > /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r > > 22226/out/freebsd.x86/release/obj/tstAPI/tstAPI > > > /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/out/freebsd.x86/ > > release/obj/tstAPI/tstAPI.o -L/usr/lib -L/usr/X11R6/lib > > -L/usr/local/lib > > /usr/ports/emulators/virtualbox/work/virtualbo > > x-3.0.51r22226/out/freebsd.x86/release/bin/VBoxRT.so > > /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/out/freeb > > sd.x86/release/lib/VBoxCOM.a > > > /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/out/freebsd.x86/release/bin/VBoxX > > PCOM.so > > kmk[2]: Leaving directory > > `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226' > > kmk[1]: *** [pass_binaries_this] Error 2 > > kmk[1]: Leaving directory > > `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226' > > kmk: *** [pass_binaries_order] Error 2 > > *** Error code 2 > > > > Stop in /usr/ports/emulators/virtualbox. > > > > > > I hope someone can advise on what is needed. > > > > deinstall openssl from ports and try again :) > > I remember we had this suggestion before, and either you (or someone else) was going to look into the use of openssl from the ports:-) Looks like I will have to recompile most apps that have linked against openssl, no? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ "If you have nothing good to say about someone, just shut up!." -- Lucky Dube From mezz7 at cox.net Sun Sep 6 22:42:31 2009 From: mezz7 at cox.net (Jeremy Messenger) Date: Sun Sep 6 22:42:38 2009 Subject: Testers: Here's a patch to update linux-opera to 10.00. In-Reply-To: <20090902110749.243fe108@ernst.jennejohn.org> References: <20090902110749.243fe108@ernst.jennejohn.org> Message-ID: On Wed, 02 Sep 2009 04:07:49 -0500, Gary Jennejohn wrote: > On Tue, 01 Sep 2009 21:49:20 -0500 > "Jeremy Messenger" wrote: > >> Here is a patch to update linux-opera to 10.00. It works great with old >> ~/.linux-opera so far, I haven't seen any problem. I will be out of town >> for a few days. I need someone to test it more and report any bug if >> there >> is any. >> > > Works extremely well so far, even flash works without any complications. > > I'm using linux_base-f10-10_1. > > uname -a (sanitized): > > FreeBSD 9.0-CURRENT FreeBSD 9.0-CURRENT #35: Sat Aug 29 18:30:32 CEST > 2009 amd64 Thanks for test it, I have committed it. I didn't add anything UPDATING since it seems run very stable with old ~/.linux-opera. Cheers, Mezz > --- > Gary Jennejohn -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org From danny at cs.huji.ac.il Mon Sep 7 05:41:38 2009 From: danny at cs.huji.ac.il (Danny Braniss) Date: Mon Sep 7 05:41:52 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 6 In-Reply-To: <20090906162544.GA39448@bsdcrew.de> References: <20090611194557.GC98175@bsdcrew.de> <991123400909060811u9bea4d9rdbf453dfaae7c185@mail.gmail.com> <20090906162544.GA39448@bsdcrew.de> Message-ID: [...] > > > > > > > ok, so some time has passed, but virtualbox-2.2.51r20457.tar.gz is no > > > longer available, there is a > > > ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/virtualbox-2.2.51r20457.tar.bz2 > > > then again in ports/emulatores/virtualbox the version is 3.0.51r22226, > > > > > > can someone please explain? hi, the above was my question, which was totally ignored, not nice. I will try and refrase it: the call for testing is for a version (2.2.51r20457) which is not available, while the ports is 3.0.51r22226, so while I managed to compile it, it complains that COM is not running, all this under 8BETA-3, both under 32 and 64 bit. thnaks, danny From doconnor at gsoft.com.au Mon Sep 7 07:07:08 2009 From: doconnor at gsoft.com.au (Daniel O'Connor) Date: Mon Sep 7 07:07:16 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 6 In-Reply-To: References: <20090611194557.GC98175@bsdcrew.de> <20090906162544.GA39448@bsdcrew.de> Message-ID: <200909071615.06146.doconnor@gsoft.com.au> On Mon, 7 Sep 2009, Danny Braniss wrote: > [...] > > > > > ok, so some time has passed, but virtualbox-2.2.51r20457.tar.gz > > > > is no longer available, there is a > > > > ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/virtualbox-2. > > > >2.51r20457.tar.bz2 then again in ports/emulatores/virtualbox the > > > > version is 3.0.51r22226, > > > > > > > > can someone please explain? > > hi, the above was my question, which was totally ignored, not nice. It wasn't a very politely worded question. You've also crossed posted to 3 lists which is not a good thing. > I will try and refrase it: > the call for testing is for a version (2.2.51r20457) which is not > available, while the ports is 3.0.51r22226, so while I managed to > compile it, it complains that COM is not running, all this under > 8BETA-3, both under 32 and 64 bit. thnaks, Are you using the emulators/virtualbox port? If not, try it, if you are, please make sure you're up to date and try again. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 188 bytes Desc: This is a digitally signed message part. Url : http://lists.freebsd.org/pipermail/freebsd-emulation/attachments/20090907/c180c5cf/attachment.pgp From decke at bluelife.at Mon Sep 7 07:36:06 2009 From: decke at bluelife.at (Bernhard =?iso-8859-1?Q?Fr=F6hlich?=) Date: Mon Sep 7 07:36:20 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 6 In-Reply-To: References: <20090611194557.GC98175@bsdcrew.de> <991123400909060811u9bea4d9rdbf453dfaae7c185@mail.gmail.com> <20090906162544.GA39448@bsdcrew.de> Message-ID: <50e4b96fb035ba5eaf5e30fbf12bf9f2.squirrel@webmail.itac.at> On Mon, September 7, 2009 7:41 am, Danny Braniss wrote: > > [...] >> > > > >> > > ok, so some time has passed, but virtualbox-2.2.51r20457.tar.gz is >> no >> > > longer available, there is a >> > > ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/virtualbox-2.2.51r20457.tar.bz2 >> > > then again in ports/emulatores/virtualbox the version is >> 3.0.51r22226, >> > > >> > > can someone please explain? > > hi, the above was my question, which was totally ignored, not nice. > I will try and refrase it: > the call for testing is for a version (2.2.51r20457) which is not > available, while > the ports is 3.0.51r22226, so while I managed to compile it, it complains > that COM > is not running, all this under 8BETA-3, both under 32 and 64 bit. I'll try to be nice but it is still unclear to me what you want. The file is available on all 4 master sites that are listed in the ports Makefile. The virtualbox port is still in heavy development so it is strongly recommended that you use the latest version that is in the ports. If that also does not work you could give our svn version a try but be careful with it because it can break in strange ways or destroy your virtual machines. svn co http://svn.bluelife.at/projects/packages/blueports/emulators/virtualbox/ -- Bernhard Fr?hlich http://www.bluelife.at/ From bsam at ipt.ru Mon Sep 7 08:19:03 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Mon Sep 7 08:19:09 2009 Subject: linux-nero no device detected In-Reply-To: (gula nito's message of "Sat, 5 Sep 2009 17:56:03 -0300") References: Message-ID: <99959451@bb.ipt.ru> On Sat, 5 Sep 2009 17:56:03 -0300 gula nito wrote: > Hi. > I install linux-nero from ports today. > The program runs well but at the begin it says two warnings: > Code: > Your /proc directory not seems to be mounted > Please check your linux installation > And > Code: > No device detected. > Nero Linux was not able to acces any physical device. Please check > your system configuration. I don't have a key, so can't be helpful, but I created a patch to upgrade linux-nero to the newest version. Please give it a try: ----- Index: Makefile =================================================================== RCS file: /home/pcvs/ports/sysutils/linux-nero/Makefile,v retrieving revision 1.4 diff -u -r1.4 Makefile --- Makefile 19 Mar 2009 17:28:48 -0000 1.4 +++ Makefile 7 Sep 2009 07:19:44 -0000 @@ -6,7 +6,7 @@ # PORTNAME= nero -PORTVERSION= 3.5.0.1 +PORTVERSION= 3.5.3.1 CATEGORIES= sysutils emulators MASTER_SITES= http://ftp6.usw.nero.com/software/NeroLINUX/ \ ftp://ftp6.usw.nero.com/software/NeroLINUX/ Index: distinfo.i386 =================================================================== RCS file: /home/pcvs/ports/sysutils/linux-nero/distinfo.i386,v retrieving revision 1.2 diff -u -r1.2 distinfo.i386 --- distinfo.i386 11 Apr 2008 10:40:41 -0000 1.2 +++ distinfo.i386 7 Sep 2009 07:19:44 -0000 @@ -1,3 +1,3 @@ -MD5 (rpm/nerolinux-3.5.0.1-x86.rpm) = f0d71dc8a0dd5213ac0be2a799d95e3a -SHA256 (rpm/nerolinux-3.5.0.1-x86.rpm) = fd5b2d8be64e8c5ab981191972403915b0d21a7fc1050df293f3a58a94d7f0e1 -SIZE (rpm/nerolinux-3.5.0.1-x86.rpm) = 17582671 +MD5 (rpm/nerolinux-3.5.3.1-x86.rpm) = 73c1090e85fbf7c1df130374117ce93b +SHA256 (rpm/nerolinux-3.5.3.1-x86.rpm) = fd4067306ea330361de4e5ee899dadbdd6d77301d112effcb1c18ab79960bfce +SIZE (rpm/nerolinux-3.5.3.1-x86.rpm) = 17673697 Index: pkg-plist =================================================================== RCS file: /home/pcvs/ports/sysutils/linux-nero/pkg-plist,v retrieving revision 1.2 diff -u -r1.2 pkg-plist --- pkg-plist 11 Apr 2008 10:40:41 -0000 1.2 +++ pkg-plist 7 Sep 2009 07:19:44 -0000 @@ -29,6 +29,7 @@ usr/lib/nero/plug-ins/libWav.so usr/share/applications/nerolinux.desktop usr/share/doc/nero/EULA-DE.txt +usr/share/doc/nero/EULA-ES.txt usr/share/doc/nero/EULA-EU.txt usr/share/doc/nero/EULA-FR.txt usr/share/doc/nero/EULA-JP.txt @@ -174,6 +175,7 @@ usr/share/nero/NeroTha.txt usr/share/nero/NeroTrk.txt usr/share/nero/eula/EULA-DE.txt +usr/share/nero/eula/EULA-ES.txt usr/share/nero/eula/EULA-EU.txt usr/share/nero/eula/EULA-FR.txt usr/share/nero/eula/EULA-JP.txt ----- -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From bugmaster at FreeBSD.org Mon Sep 7 11:06:57 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Sep 7 11:07:41 2009 Subject: Current problem reports assigned to freebsd-emulation@FreeBSD.org Message-ID: <200909071106.n87B6uRL010185@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/137332 emulation add caution messages to some adobe products f ports/136321 emulation x11-toolkits/linux-pango: please update linux based po o ports/136229 emulation [linux] certain linux apps look for libraries using a o ports/135337 emulation [PATCH] emulators/linux_base-f10: incorrect bash usage o ports/135322 emulation Port graphics/linux_dri has incorrect packaging list c o kern/130724 emulation [linprocfs] [patch] cpuinfo in linprocfs is dated, cau o kern/129169 emulation [linux] [patch] Linux Emulation ENOTCONN error using n f ports/127018 emulation Linuxulator incapable of using FreeBSD's LDAP environm o kern/126232 emulation [linux] Linux ioctl TCGETS (0x5401) always fails o kern/97326 emulation [linux] file descriptor leakage in linux emulation o kern/73777 emulation [linux] [patch] linux emulation: root dir special hand a kern/72920 emulation [linux]: path "prefixing" is not done on unix domain s o kern/56451 emulation [linprocfs] /compat/linux/proc/cpuinfo gives wrong CPU o kern/41543 emulation [patch] [request] easier wine/w23 support o kern/39201 emulation [linux] [patch] ptrace(2) and rfork(RFLINUXTHPN) confu o kern/29698 emulation [linux] [patch] linux ipcs doesn'work o kern/21463 emulation [linux] Linux compatability mode should not allow setu o kern/11165 emulation [ibcs2] IBCS2 doesn't work correctly with PID_MAX 9999 18 problems total. From cmdlnkid at gmail.com Mon Sep 7 17:08:44 2009 From: cmdlnkid at gmail.com (CmdLnKid) Date: Mon Sep 7 17:08:57 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 6 In-Reply-To: <991123400909061150h56dc6e07uf8d8e721f6c923bf@mail.gmail.com> References: <20090611194557.GC98175@bsdcrew.de> <991123400909060811u9bea4d9rdbf453dfaae7c185@mail.gmail.com> <20090906162544.GA39448@bsdcrew.de> <991123400909061150h56dc6e07uf8d8e721f6c923bf@mail.gmail.com> Message-ID: On Sun, 6 Sep 2009 14:50 -0000, odhiambo wrote: > On Sun, Sep 6, 2009 at 7:25 PM, Martin Wilke wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On Sun, Sep 06, 2009 at 06:11:48PM +0300, Odhiambo Washington wrote: >>> On Sun, Sep 6, 2009 at 1:40 PM, Danny Braniss >> wrote: >>> >>>>> -----BEGIN PGP SIGNED MESSAGE----- >>>>> Hash: SHA1 >>>>> >>>>> Huhu, >>>>> >>>>> Yes we life and that's good :-). >>>>> Changes: >>>>> >>>>> - Fix build error when compiling in debug mode on FreeBSD HEAD >>>>> - SemEvent?-r0drv/FreeBSD: Don't use tvtohz for an infinite >> timeout. >>>>> - Some FreeBSD relate typos >>>>> - Enable shared OpenGL service. Completely untested due to lack of >>>>> appropriate hardware but it compiles at least >>>>> - Add support for shared clipboards. Requires libXt >>>>> - FreeBSD: Implement preemption API for guest SMP and enable >>>>> it (slightly tested). Add neccessary RTMP* methods in userspace >>>>> for the frontends to detect the number of CPUs >>>>> - Runtime/semevent-r0drv-freebsd: Use a sleeping mutex >>>>> instead of a spinlock to fix the problems users are seeing >>>>> (assertions with debugging enabled) while still being able >>>>> to run on 100Hz hosts. No problems detected so far and Solaris >>>>> doesn't use a spin mutex in this code too so it shouldn't do >>>>> any harm (keeping fingers crossed)space for the frontends to >>>>> detect the number of CPUs >>>>> - Add support for curl >>>>> - Add VBoxSharedClipboard >>>>> >>>>> Ports Changes; >>>>> - Force guestadditions version to 2.2.4 >>>>> - Removed Qt3 include replacements (already upstream) >>>>> - Removed cosmetic X11 include path patch >>>>> >>>>> Please make SURE, your world and kernel is in sync and you've read >>>>> the pkg-messages. Also please unload the kernel module before >>>>> you update the port ;-). >>>>> >>>>> Many thx to all Vbox Devs, All supporters, my nice team! :-) >>>>> >>>>> http://people.freebsd.org/~miwi/vbox/virtualbox_6.tgz >> >>>>> >>>>> Happy Testing! >>>>> >>>> ok, so some time has passed, but virtualbox-2.2.51r20457.tar.gz is no >>>> longer available, there is a >>>> >> ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/virtualbox-2.2.51r20457.tar.bz2 >>>> then again in ports/emulatores/virtualbox the version is 3.0.51r22226, >>>> >>>> can someone please explain? >>>> >>>> >>> >>> >>> And on my FreeBSD 7.2-STABLE, compiling virtualbox fails as follows: >>> >>> >>> >>> kBuild: Linking VBoxREM64 >>> kBuild: Installing VBoxREM64 => >>> >> /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/out/freebsd.x86/release/bin/VBox >>> REM64.so >>> kmk[2]: Leaving directory >>> `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226' >>> kmk[1]: Leaving directory >>> `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226' >>> kBuild: Pass - Programs >>> kmk[1]: Entering directory >>> `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226' >>> kmk[2]: Entering directory >>> `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226' >>> kBuild: Compiling tstAPI - >>> >> /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/Main/testcase/tstAPI.cpp >>> kBuild: Linking tstAPI >>> /usr/local/lib/libssl.so.5: undefined reference to `d2i_X509_EXTENSIONS' >>> /usr/local/lib/libssl.so.5: undefined reference to >>> `ENGINE_get_ssl_client_cert_function' >>> /usr/local/lib/libssl.so.5: undefined reference to `HMAC_CTX_set_flags' >>> /usr/local/lib/libssl.so.5: undefined reference to `i2d_X509_EXTENSIONS' >>> /usr/local/lib/libssl.so.5: undefined reference to >>> `ENGINE_load_ssl_client_cert' >>> /usr/local/lib/libssl.so.5: undefined reference to `pqueue_size' >>> /usr/local/lib/libssl.so.5: undefined reference to `EVP_idea_cbc' >>> kmk[2]: *** >>> >> [/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/out/freebsd.x86/release/obj/tstAPI/tstAPI] >>> Error 1 >>> The failing command: >>> @g++ '-Wl,-rpath,/usr/local/lib/virtualbox' -m32 -o >>> /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r >>> 22226/out/freebsd.x86/release/obj/tstAPI/tstAPI >>> >> /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/out/freebsd.x86/ >>> release/obj/tstAPI/tstAPI.o -L/usr/lib -L/usr/X11R6/lib >>> -L/usr/local/lib >>> /usr/ports/emulators/virtualbox/work/virtualbo >>> x-3.0.51r22226/out/freebsd.x86/release/bin/VBoxRT.so >>> /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/out/freeb >>> sd.x86/release/lib/VBoxCOM.a >>> >> /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/out/freebsd.x86/release/bin/VBoxX >>> PCOM.so >>> kmk[2]: Leaving directory >>> `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226' >>> kmk[1]: *** [pass_binaries_this] Error 2 >>> kmk[1]: Leaving directory >>> `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226' >>> kmk: *** [pass_binaries_order] Error 2 >>> *** Error code 2 >>> >>> Stop in /usr/ports/emulators/virtualbox. >>> >>> >>> I hope someone can advise on what is needed. >>> >> >> deinstall openssl from ports and try again :) >> >> > I remember we had this suggestion before, and either you (or someone else) > was going to look into the use of openssl from the ports:-) > Looks like I will have to recompile most apps that have linked against > openssl, no? > Just create a backup package of your openssl port with ( pkg_create -b ) then uninstall the port, rebuild the port in question and ( pkg_add ) the openssl port again. This will at least get the port out of the way for you to complete the build and will let you determine further action. Best regards. -- - (2^(N-1)) From edwin at FreeBSD.org Mon Sep 7 18:00:19 2009 From: edwin at FreeBSD.org (edwin@FreeBSD.org) Date: Mon Sep 7 18:00:28 2009 Subject: ports/138616: [patch] graphics/linux-f10-png: update to latest version Message-ID: <200909071800.n87I0IoT038726@freefall.freebsd.org> Synopsis: [patch] graphics/linux-f10-png: update to latest version Responsible-Changed-From-To: freebsd-ports-bugs->freebsd-emulation Responsible-Changed-By: edwin Responsible-Changed-When: Mon Sep 7 18:00:18 UTC 2009 Responsible-Changed-Why: Over to maintainer (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=138616 From pluknet at gmail.com Mon Sep 7 18:15:55 2009 From: pluknet at gmail.com (pluknet) Date: Mon Sep 7 18:16:07 2009 Subject: acquiring duplicate lock of same type: "ftlk" In-Reply-To: References: Message-ID: 2009/8/27 pluknet : > Hi. > > Got it on FreeBSD 9.0-CURRENT while been running in Xorg, don't know > where exactly. > > Acquiring duplicate lock of same type: "ftlk" > ?1st ftlk @ /usr/src/sys/modules/linux/../../compat/linux/linux_futex.c:177 > ?2nd ftlk @ /usr/src/sys/modules/linux/../../compat/linux/linux_futex.c:203 > KDB: stack backtrace: > db_trace_self_wrapper(c07fd8ea,ea393b58,c060a145,c05fac1b,c08007b2,...) > at db_trace_self_wrapper+0x26 > kdb_backtrace(c05fac1b,c08007b2,c0b49757,c58ead20,ea393bb4,...) at > kdb_backtrace+0x29 > _witness_debugger(c08007b2,c0b49793,c0b49757,cb,0,...) at _witness_debugger+0x25 > witness_checkorder(c9bba780,9,c0b49757,cb,0,...) at witness_checkorder+0x469 > _sx_xlock(c9bba780,0,c0b49757,cb,0,...) at _sx_xlock+0x85 > futex_get0(c0609f8c,c09cc7a8,c9ac7764,c09cc7a8,c084df3c,...) at futex_get0+0x116 > linux_sys_futex(c9ac76c0,ea393cf8,ea393d18,ea393d1c,c0b4cf40,...) at > linux_sys_futex+0x6f > syscall(ea393d38) at syscall+0x2b4 > Xint0x80_syscall() at Xint0x80_syscall+0x20 > --- syscall (240, Linux ELF, linux_sys_futex), eip = 0x28799533, esp = > 0xbfbfc0cc, ebp = 0x4000001 --- > > This time seeing this LOR again but with another one just before. lock order reversal: 1st 0xc75365b8 pseudofs (pseudofs) @ /usr/src/sys/kern/vfs_lookup.c:497 2nd 0xc088ea3c allproc (allproc) @ /usr/src/sys/kern/kern_proc.c:292 KDB: stack backtrace: db_trace_self_wrapper(c07fd8ea,e82148e4,c060a145,c05fac1b,c08008bf,...) at db_trace_self_wrapper+0x26 kdb_backtrace(c05fac1b,c08008bf,c58eabe8,c58e30d0,e8214940,...) at kdb_backtrace+0x29 _witness_debugger(c08008bf,c088ea3c,c07f981d,c58e30d0,c07f96f0,...) at _witness_debugger+0x25 witness_checkorder(c088ea3c,1,c07f96f0,124,0,...) at witness_checkorder+0x839 _sx_slock(c088ea3c,0,c07f96f0,124,c73c4980,...) at _sx_slock+0x85 pfind(514,c72ba1a0,4,c07f8d78,c5fe1b40,...) at pfind+0x2f pfs_visible(0,0,c07f042d,7c,c7536560,...) at pfs_visible+0x3a pfs_lookup(e8214a40,c082715e,c7536560,c7536560,e8214bf8,...) at pfs_lookup+0x3dd VOP_CACHEDLOOKUP_APV(c0843960,e8214a40,e8214bf8,e8214be4,c73c4e80,...) at VOP_CACHEDLOOKUP_APV+0xc5 vfs_cache_lookup(e8214acc,c08087d0,c0875a00,200000,e8214bcc,...) at vfs_cache_lookup+0xd6 VOP_LOOKUP_APV(c0843960,e8214acc,e8214bf8,1f1,e8214be4,...) at VOP_LOOKUP_APV+0xe5 lookup(e8214bcc,c5fd1800,0,c5,c5ef77f8,...) at lookup+0x63b namei(e8214bcc,c5c1500d,3f3,e8214c20,c5c1500d,...) at namei+0x57f kern_alternate_path(c5fe1b40,c0b4921c,2879f478,0,e8214c74,...) at kern_alternate _path+0x1cd linux_emul_convpath(c5fe1b40,2879f478,0,e8214c74,0,...) at linux_emul_convpath+0x3c linux_open(c5fe1b40,e8214cf8,e8214d18,e8214d1c,c0b4b58c,...) at linux_open+0x41 syscall(e8214d38) at syscall+0x2b4 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (5, Linux ELF, linux_open), eip = 0x2889115e, esp = 0xbfbfbd1c, ebp = 0xbfbfbd6c --- acquiring duplicate lock of same type: "ftlk" [...] I'm running head from 08/26. There were recent changes in pseudofs. Could it be fixed? Looks like it's connected to running firefox3 with linprocfs (for adobe flash). -- wbr, pluknet From olivier at gid0.org Mon Sep 7 18:18:41 2009 From: olivier at gid0.org (Olivier Smedts) Date: Mon Sep 7 18:18:49 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 6 In-Reply-To: <50e4b96fb035ba5eaf5e30fbf12bf9f2.squirrel@webmail.itac.at> References: <20090611194557.GC98175@bsdcrew.de> <991123400909060811u9bea4d9rdbf453dfaae7c185@mail.gmail.com> <20090906162544.GA39448@bsdcrew.de> <50e4b96fb035ba5eaf5e30fbf12bf9f2.squirrel@webmail.itac.at> Message-ID: <367b2c980909071048j79b28babwcc9d59488d1de3ef@mail.gmail.com> 2009/9/7 Bernhard Fr?hlich : > On Mon, September 7, 2009 7:41 am, Danny Braniss wrote: >> >> [...] >>> > > > >>> > > ok, so some time has passed, but virtualbox-2.2.51r20457.tar.gz is >>> no >>> > > longer available, there is a >>> > > ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/virtualbox-2.2.51r20457.tar.bz2 >>> > > then again in ports/emulatores/virtualbox the version is >>> 3.0.51r22226, >>> > > >>> > > can someone please explain? >> >> hi, the above was my question, which was totally ignored, not nice. >> I will try and refrase it: >> the call for testing is for a version (2.2.51r20457) which is not >> available, while >> the ports is 3.0.51r22226, so while I managed to compile it, it complains >> that COM >> is not running, all this under 8BETA-3, both under 32 and 64 bit. > > I'll try to be nice but it is still unclear to me what you want. The file > is available on all 4 master sites that are listed in the ports Makefile. > > The virtualbox port is still in heavy development so it is strongly > recommended that you use the latest version that is in the ports. If that > also does not work you could give our svn version a try but be careful > with it because it can break in strange ways or destroy your virtual > machines. > > svn co > http://svn.bluelife.at/projects/packages/blueports/emulators/virtualbox/ Wow... the SVN version works great for me with VT extensions ! I just tried a 64 bits 2 processors guest :) Thanks ! > > -- > Bernhard Fr?hlich > http://www.bluelife.at/ > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: olivier@gid0.org - against HTML email & vCards X www: http://www.gid0.org - against proprietary attachments / \ "Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas." From glen.j.barber at gmail.com Mon Sep 7 18:40:02 2009 From: glen.j.barber at gmail.com (Glen Barber) Date: Mon Sep 7 18:40:08 2009 Subject: ports/138616: [patch] graphics/linux-f10-png: update to latest version Message-ID: <200909071840.n87Ie2YM078376@freefall.freebsd.org> The following reply was made to PR ports/138616; it has been noted by GNATS. From: "Glen Barber" To: bug-followup@FreeBSD.org, freebsd-ports-bugs@FreeBSD.org Cc: Subject: Re: ports/138616: [patch] graphics/linux-f10-png: update to latest version Date: Mon, 7 Sep 2009 14:30:36 -0400 --yrj/dFKFPuw6o+aM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I missed a few lines in the origninal patch. A corrected version is attached. --yrj/dFKFPuw6o+aM Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="graphics.linux-f10-png.patch.txt" diff -ruN /usr/ports/graphics/linux-f10-png.orig/Makefile /usr/ports/graphics/linux-f10-png/Makefile --- /usr/ports/graphics/linux-f10-png.orig/Makefile 2009-06-01 13:26:17.000000000 -0400 +++ /usr/ports/graphics/linux-f10-png/Makefile 2009-09-07 14:24:38.000000000 -0400 @@ -6,7 +6,7 @@ # PORTNAME= png -PORTVERSION= 1.2.35 +PORTVERSION= 1.2.37 CATEGORIES= graphics linux PKGNAMEPREFIX= linux-f10- DISTNAME= ${LINUX_NAME}-${PORTVERSION}-${RPMVERSION} @@ -24,12 +24,12 @@ USE_LDCONFIG= yes PLIST_FILES= usr/lib/libpng.so.3 \ - usr/lib/libpng.so.3.35.0 \ + usr/lib/libpng.so.3.37.0 \ usr/lib/libpng12.so.0 \ - usr/lib/libpng12.so.0.35.0 \ + usr/lib/libpng12.so.0.37.0 \ usr/share/man/man5/png.5.gz DOCSDIR= ${PREFIX}/usr/share/doc/libpng-${PORTVERSION} -PORTDOCS= CHANGES LICENSE README TODO example.c libpng-1.2.35.txt +PORTDOCS= CHANGES LICENSE README TODO example.c libpng-1.2.37.txt DESCR= ${.CURDIR}/../${PORTNAME}/pkg-descr .include diff -ruN /usr/ports/graphics/linux-f10-png.orig/distinfo.i386 /usr/ports/graphics/linux-f10-png/distinfo.i386 --- /usr/ports/graphics/linux-f10-png.orig/distinfo.i386 2009-06-01 13:26:17.000000000 -0400 +++ /usr/ports/graphics/linux-f10-png/distinfo.i386 2009-09-07 13:52:04.000000000 -0400 @@ -1,6 +1,3 @@ -MD5 (rpm/i386/fedora/10/libpng-1.2.35-1.fc10.i386.rpm) = 2c5fd1b1991e519efbaba45a4b5ead7b -SHA256 (rpm/i386/fedora/10/libpng-1.2.35-1.fc10.i386.rpm) = 0cafa0d6770824d1e5d0e24f07b723423ed926d02eeeed4e5e30dc2cadf1e020 -SIZE (rpm/i386/fedora/10/libpng-1.2.35-1.fc10.i386.rpm) = 257935 -MD5 (rpm/i386/fedora/10/libpng-1.2.35-1.fc10.src.rpm) = a85adf5ad0cb0953b7c05e57c21c8793 -SHA256 (rpm/i386/fedora/10/libpng-1.2.35-1.fc10.src.rpm) = 1288a6764bf2496413198b13ca0552a9f3a8969f8d0d928faeea9790affd81eb -SIZE (rpm/i386/fedora/10/libpng-1.2.35-1.fc10.src.rpm) = 666421 +MD5 (rpm/i386/fedora/10/libpng-1.2.37-1.fc10.i386.rpm) = d1d6047bdd669cd0eb9bb4ce50fa31ca +SHA256 (rpm/i386/fedora/10/libpng-1.2.37-1.fc10.i386.rpm) = 632d685a9d3328d77f96d5c8beb8f8d927b7e35d3ab92f460b6656624055bdf3 +SIZE (rpm/i386/fedora/10/libpng-1.2.37-1.fc10.i386.rpm) = 261212 --yrj/dFKFPuw6o+aM-- From odhiambo at gmail.com Mon Sep 7 19:18:23 2009 From: odhiambo at gmail.com (Odhiambo Washington) Date: Mon Sep 7 19:18:36 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 6 In-Reply-To: References: <20090611194557.GC98175@bsdcrew.de> <991123400909060811u9bea4d9rdbf453dfaae7c185@mail.gmail.com> <20090906162544.GA39448@bsdcrew.de> <991123400909061150h56dc6e07uf8d8e721f6c923bf@mail.gmail.com> Message-ID: <991123400909071218s2af7a76ybcac8702d697362f@mail.gmail.com> On Mon, Sep 7, 2009 at 7:45 PM, CmdLnKid wrote: > On Sun, 6 Sep 2009 14:50 -0000, odhiambo wrote: > > On Sun, Sep 6, 2009 at 7:25 PM, Martin Wilke wrote: >> >> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> On Sun, Sep 06, 2009 at 06:11:48PM +0300, Odhiambo Washington wrote: >>> >>>> On Sun, Sep 6, 2009 at 1:40 PM, Danny Braniss >>>> >>> wrote: >>> >>>> >>>> -----BEGIN PGP SIGNED MESSAGE----- >>>>>> Hash: SHA1 >>>>>> >>>>>> Huhu, >>>>>> >>>>>> Yes we life and that's good :-). >>>>>> Changes: >>>>>> >>>>>> - Fix build error when compiling in debug mode on FreeBSD HEAD >>>>>> - SemEvent?-r0drv/FreeBSD: Don't use tvtohz for an infinite >>>>>> >>>>> timeout. >>> >>>> - Some FreeBSD relate typos >>>>>> - Enable shared OpenGL service. Completely untested due to lack of >>>>>> appropriate hardware but it compiles at least >>>>>> - Add support for shared clipboards. Requires libXt >>>>>> - FreeBSD: Implement preemption API for guest SMP and enable >>>>>> it (slightly tested). Add neccessary RTMP* methods in userspace >>>>>> for the frontends to detect the number of CPUs >>>>>> - Runtime/semevent-r0drv-freebsd: Use a sleeping mutex >>>>>> instead of a spinlock to fix the problems users are seeing >>>>>> (assertions with debugging enabled) while still being able >>>>>> to run on 100Hz hosts. No problems detected so far and Solaris >>>>>> doesn't use a spin mutex in this code too so it shouldn't do >>>>>> any harm (keeping fingers crossed)space for the frontends to >>>>>> detect the number of CPUs >>>>>> - Add support for curl >>>>>> - Add VBoxSharedClipboard >>>>>> >>>>>> Ports Changes; >>>>>> - Force guestadditions version to 2.2.4 >>>>>> - Removed Qt3 include replacements (already upstream) >>>>>> - Removed cosmetic X11 include path patch >>>>>> >>>>>> Please make SURE, your world and kernel is in sync and you've read >>>>>> the pkg-messages. Also please unload the kernel module before >>>>>> you update the port ;-). >>>>>> >>>>>> Many thx to all Vbox Devs, All supporters, my nice team! :-) >>>>>> >>>>>> http://people.freebsd.org/~miwi/vbox/virtualbox_6.tgz >>>>>> >>>>>> >>>>> >>> >>>> >>>>>> Happy Testing! >>>>>> >>>>>> ok, so some time has passed, but virtualbox-2.2.51r20457.tar.gz is no >>>>> longer available, there is a >>>>> >>>>> >>> ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/virtualbox-2.2.51r20457.tar.bz2 >>> >>>> then again in ports/emulatores/virtualbox the version is 3.0.51r22226, >>>>> >>>>> can someone please explain? >>>>> >>>>> >>>>> >>>> >>>> And on my FreeBSD 7.2-STABLE, compiling virtualbox fails as follows: >>>> >>>> >>>> >>>> kBuild: Linking VBoxREM64 >>>> kBuild: Installing VBoxREM64 => >>>> >>>> /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/out/freebsd.x86/release/bin/VBox >>> >>>> REM64.so >>>> kmk[2]: Leaving directory >>>> `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226' >>>> kmk[1]: Leaving directory >>>> `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226' >>>> kBuild: Pass - Programs >>>> kmk[1]: Entering directory >>>> `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226' >>>> kmk[2]: Entering directory >>>> `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226' >>>> kBuild: Compiling tstAPI - >>>> >>>> /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/Main/testcase/tstAPI.cpp >>> >>>> kBuild: Linking tstAPI >>>> /usr/local/lib/libssl.so.5: undefined reference to `d2i_X509_EXTENSIONS' >>>> /usr/local/lib/libssl.so.5: undefined reference to >>>> `ENGINE_get_ssl_client_cert_function' >>>> /usr/local/lib/libssl.so.5: undefined reference to `HMAC_CTX_set_flags' >>>> /usr/local/lib/libssl.so.5: undefined reference to `i2d_X509_EXTENSIONS' >>>> /usr/local/lib/libssl.so.5: undefined reference to >>>> `ENGINE_load_ssl_client_cert' >>>> /usr/local/lib/libssl.so.5: undefined reference to `pqueue_size' >>>> /usr/local/lib/libssl.so.5: undefined reference to `EVP_idea_cbc' >>>> kmk[2]: *** >>>> >>>> [/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/out/freebsd.x86/release/obj/tstAPI/tstAPI] >>> >>>> Error 1 >>>> The failing command: >>>> @g++ '-Wl,-rpath,/usr/local/lib/virtualbox' -m32 -o >>>> /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r >>>> 22226/out/freebsd.x86/release/obj/tstAPI/tstAPI >>>> >>>> /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/out/freebsd.x86/ >>> >>>> release/obj/tstAPI/tstAPI.o -L/usr/lib -L/usr/X11R6/lib >>>> -L/usr/local/lib >>>> /usr/ports/emulators/virtualbox/work/virtualbo >>>> x-3.0.51r22226/out/freebsd.x86/release/bin/VBoxRT.so >>>> /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/out/freeb >>>> sd.x86/release/lib/VBoxCOM.a >>>> >>>> /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/out/freebsd.x86/release/bin/VBoxX >>> >>>> PCOM.so >>>> kmk[2]: Leaving directory >>>> `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226' >>>> kmk[1]: *** [pass_binaries_this] Error 2 >>>> kmk[1]: Leaving directory >>>> `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226' >>>> kmk: *** [pass_binaries_order] Error 2 >>>> *** Error code 2 >>>> >>>> Stop in /usr/ports/emulators/virtualbox. >>>> >>>> >>>> I hope someone can advise on what is needed. >>>> >>>> >>> deinstall openssl from ports and try again :) >>> >>> >>> I remember we had this suggestion before, and either you (or someone >> else) >> was going to look into the use of openssl from the ports:-) >> Looks like I will have to recompile most apps that have linked against >> openssl, no? >> >> > Just create a backup package of your openssl port with ( pkg_create -b ) > then uninstall the port, rebuild the port in question and ( pkg_add ) the > openssl port again. This will at least get the port out of the way for you > to complete the build and will let you determine further action. > > It's not such a critical box. It's a testbed nyway so I did not bother backing up anything since I will be able to fix any broken packages. Let me see how it goes. So far so good.... the build process is running... -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ "If you have nothing good to say about someone, just shut up!." -- Lucky Dube From decke at bluelife.at Mon Sep 7 19:56:00 2009 From: decke at bluelife.at (Bernhard =?iso-8859-1?Q?Fr=F6hlich?=) Date: Mon Sep 7 19:56:19 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 6 In-Reply-To: <367b2c980909071048j79b28babwcc9d59488d1de3ef@mail.gmail.com> References: <20090611194557.GC98175@bsdcrew.de> <991123400909060811u9bea4d9rdbf453dfaae7c185@mail.gmail.com> <20090906162544.GA39448@bsdcrew.de> <50e4b96fb035ba5eaf5e30fbf12bf9f2.squirrel@webmail.itac.at> <367b2c980909071048j79b28babwcc9d59488d1de3ef@mail.gmail.com> Message-ID: On Mon, September 7, 2009 7:48 pm, Olivier Smedts wrote: > 2009/9/7 Bernhard Fr?hlich : >> On Mon, September 7, 2009 7:41 am, Danny Braniss wrote: >>> >>> [...] >>>> > > > >>>> > > ok, so some time has passed, but virtualbox-2.2.51r20457.tar.gz is >>>> no >>>> > > longer available, there is a >>>> > > ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/virtualbox-2.2.51r20457.tar.bz2 >>>> > > then again in ports/emulatores/virtualbox the version is >>>> 3.0.51r22226, >>>> > > >>>> > > can someone please explain? >>> >>> hi, the above was my question, which was totally ignored, not nice. >>> I will try and refrase it: >>> the call for testing is for a version (2.2.51r20457) which is not >>> available, while >>> the ports is 3.0.51r22226, so while I managed to compile it, it >>> complains >>> that COM >>> is not running, all this under 8BETA-3, both under 32 and 64 bit. >> >> I'll try to be nice but it is still unclear to me what you want. The >> file >> is available on all 4 master sites that are listed in the ports >> Makefile. >> >> The virtualbox port is still in heavy development so it is strongly >> recommended that you use the latest version that is in the ports. If >> that >> also does not work you could give our svn version a try but be careful >> with it because it can break in strange ways or destroy your virtual >> machines. >> >> svn co >> http://svn.bluelife.at/projects/packages/blueports/emulators/virtualbox/ > > Wow... the SVN version works great for me with VT extensions ! I just > tried a 64 bits 2 processors guest :) > > Thanks ! According to Alexander Eichner VT-x should work now with the latest vbox code. So everybody who is using our svn port should already have working VT-x. We plan to update the virtualbox port in the next few days to get that version in the tree before the ports freeze. -- Bernhard Fr?hlich http://www.bluelife.at/ From bsam at FreeBSD.org Mon Sep 7 20:09:32 2009 From: bsam at FreeBSD.org (bsam@FreeBSD.org) Date: Mon Sep 7 20:09:39 2009 Subject: ports/138616: [patch] graphics/linux-f10-png: update to latest version Message-ID: <200909072009.n87K9Woa066266@freefall.freebsd.org> Synopsis: [patch] graphics/linux-f10-png: update to latest version State-Changed-From-To: open->closed State-Changed-By: bsam State-Changed-When: Mon Sep 7 20:08:52 UTC 2009 State-Changed-Why: Committed, thanks! Two notes: 1. For linux ports one should fetch and makesum with the option "PACKAGE_BUILDING=YES". 2. If library version changes then one should take a look at Mk/bsd.linux-apps.mk file. That library might be presented there. http://www.freebsd.org/cgi/query-pr.cgi?pr=138616 From dfilter at FreeBSD.ORG Mon Sep 7 20:10:03 2009 From: dfilter at FreeBSD.ORG (dfilter service) Date: Mon Sep 7 20:10:13 2009 Subject: ports/138616: commit references a PR Message-ID: <200909072010.n87KA3Vk066396@freefall.freebsd.org> The following reply was made to PR ports/138616; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: ports/138616: commit references a PR Date: Mon, 7 Sep 2009 20:08:45 +0000 (UTC) bsam 2009-09-07 20:08:37 UTC FreeBSD ports repository Modified files: Mk bsd.linux-apps.mk graphics/linux-f10-png Makefile distinfo.i386 Log: . update graphics/linux-f10-png to version 1.2.37-1.fc10; [1] . update distinfo for sources; . update the library version at Mk/bsd.linux-apps.mk. PR: ports/138616 [1] Submitted by: Glen Barber [1] Revision Changes Path 1.32 +2 -2 ports/Mk/bsd.linux-apps.mk 1.29 +4 -4 ports/graphics/linux-f10-png/Makefile 1.15 +6 -6 ports/graphics/linux-f10-png/distinfo.i386 _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org" From kostikbel at gmail.com Tue Sep 8 09:11:20 2009 From: kostikbel at gmail.com (Kostik Belousov) Date: Tue Sep 8 09:11:32 2009 Subject: acquiring duplicate lock of same type: "ftlk" In-Reply-To: References: Message-ID: <20090908091114.GH47688@deviant.kiev.zoral.com.ua> On Mon, Sep 07, 2009 at 10:15:48PM +0400, pluknet wrote: > 2009/8/27 pluknet : > > Hi. > > > > Got it on FreeBSD 9.0-CURRENT while been running in Xorg, don't know > > where exactly. > > > > Acquiring duplicate lock of same type: "ftlk" > > ?1st ftlk @ /usr/src/sys/modules/linux/../../compat/linux/linux_futex.c:177 > > ?2nd ftlk @ /usr/src/sys/modules/linux/../../compat/linux/linux_futex.c:203 > > KDB: stack backtrace: > > db_trace_self_wrapper(c07fd8ea,ea393b58,c060a145,c05fac1b,c08007b2,...) > > at db_trace_self_wrapper+0x26 > > kdb_backtrace(c05fac1b,c08007b2,c0b49757,c58ead20,ea393bb4,...) at > > kdb_backtrace+0x29 > > _witness_debugger(c08007b2,c0b49793,c0b49757,cb,0,...) at _witness_debugger+0x25 > > witness_checkorder(c9bba780,9,c0b49757,cb,0,...) at witness_checkorder+0x469 > > _sx_xlock(c9bba780,0,c0b49757,cb,0,...) at _sx_xlock+0x85 > > futex_get0(c0609f8c,c09cc7a8,c9ac7764,c09cc7a8,c084df3c,...) at futex_get0+0x116 > > linux_sys_futex(c9ac76c0,ea393cf8,ea393d18,ea393d1c,c0b4cf40,...) at > > linux_sys_futex+0x6f > > syscall(ea393d38) at syscall+0x2b4 > > Xint0x80_syscall() at Xint0x80_syscall+0x20 > > --- syscall (240, Linux ELF, linux_sys_futex), eip = 0x28799533, esp = > > 0xbfbfc0cc, ebp = 0x4000001 --- > > > > From what dchagin@ told me, the LOR is unavoidable since he has to acquire two sx locks of the same name. On the other hand, second sx lock is not visible to any thread except the current one, so the LOR should be innocent. > > This time seeing this LOR again but with another one just before. > lock order reversal: > 1st 0xc75365b8 pseudofs (pseudofs) @ /usr/src/sys/kern/vfs_lookup.c:497 > 2nd 0xc088ea3c allproc (allproc) @ /usr/src/sys/kern/kern_proc.c:292 > KDB: stack backtrace: > db_trace_self_wrapper(c07fd8ea,e82148e4,c060a145,c05fac1b,c08008bf,...) > at db_trace_self_wrapper+0x26 > kdb_backtrace(c05fac1b,c08008bf,c58eabe8,c58e30d0,e8214940,...) at > kdb_backtrace+0x29 > _witness_debugger(c08008bf,c088ea3c,c07f981d,c58e30d0,c07f96f0,...) at > _witness_debugger+0x25 > witness_checkorder(c088ea3c,1,c07f96f0,124,0,...) at witness_checkorder+0x839 > _sx_slock(c088ea3c,0,c07f96f0,124,c73c4980,...) at _sx_slock+0x85 > pfind(514,c72ba1a0,4,c07f8d78,c5fe1b40,...) at pfind+0x2f > pfs_visible(0,0,c07f042d,7c,c7536560,...) at pfs_visible+0x3a > pfs_lookup(e8214a40,c082715e,c7536560,c7536560,e8214bf8,...) at pfs_lookup+0x3dd > VOP_CACHEDLOOKUP_APV(c0843960,e8214a40,e8214bf8,e8214be4,c73c4e80,...) > at VOP_CACHEDLOOKUP_APV+0xc5 > vfs_cache_lookup(e8214acc,c08087d0,c0875a00,200000,e8214bcc,...) at > vfs_cache_lookup+0xd6 > VOP_LOOKUP_APV(c0843960,e8214acc,e8214bf8,1f1,e8214be4,...) at > VOP_LOOKUP_APV+0xe5 > lookup(e8214bcc,c5fd1800,0,c5,c5ef77f8,...) at lookup+0x63b > namei(e8214bcc,c5c1500d,3f3,e8214c20,c5c1500d,...) at namei+0x57f > kern_alternate_path(c5fe1b40,c0b4921c,2879f478,0,e8214c74,...) at kern_alternate > _path+0x1cd > linux_emul_convpath(c5fe1b40,2879f478,0,e8214c74,0,...) at > linux_emul_convpath+0x3c > linux_open(c5fe1b40,e8214cf8,e8214d18,e8214d1c,c0b4b58c,...) at linux_open+0x41 > syscall(e8214d38) at syscall+0x2b4 > Xint0x80_syscall() at Xint0x80_syscall+0x20 > --- syscall (5, Linux ELF, linux_open), eip = 0x2889115e, esp = > 0xbfbfbd1c, ebp = 0xbfbfbd6c --- > acquiring duplicate lock of same type: "ftlk" > [...] > > I'm running head from 08/26. > There were recent changes in pseudofs. Could it be fixed? > Looks like it's connected to running firefox3 with linprocfs (for adobe flash). The second LOR actually exposes the right order. It would be interesting to look up the point where the other order is established. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-emulation/attachments/20090908/6946fce0/attachment.pgp From attilio at freebsd.org Tue Sep 8 09:43:09 2009 From: attilio at freebsd.org (Attilio Rao) Date: Tue Sep 8 09:43:15 2009 Subject: acquiring duplicate lock of same type: "ftlk" In-Reply-To: <20090908091114.GH47688@deviant.kiev.zoral.com.ua> References: <20090908091114.GH47688@deviant.kiev.zoral.com.ua> Message-ID: <3bbf2fe10909080213i588493darf8dd1e1ff768cb0a@mail.gmail.com> 2009/9/8 Kostik Belousov : > On Mon, Sep 07, 2009 at 10:15:48PM +0400, pluknet wrote: >> 2009/8/27 pluknet : >> > Hi. >> > >> > Got it on FreeBSD 9.0-CURRENT while been running in Xorg, don't know >> > where exactly. >> > >> > Acquiring duplicate lock of same type: "ftlk" >> > 1st ftlk @ /usr/src/sys/modules/linux/../../compat/linux/linux_futex.c:177 >> > 2nd ftlk @ /usr/src/sys/modules/linux/../../compat/linux/linux_futex.c:203 >> > KDB: stack backtrace: >> > db_trace_self_wrapper(c07fd8ea,ea393b58,c060a145,c05fac1b,c08007b2,...) >> > at db_trace_self_wrapper+0x26 >> > kdb_backtrace(c05fac1b,c08007b2,c0b49757,c58ead20,ea393bb4,...) at >> > kdb_backtrace+0x29 >> > _witness_debugger(c08007b2,c0b49793,c0b49757,cb,0,...) at _witness_debugger+0x25 >> > witness_checkorder(c9bba780,9,c0b49757,cb,0,...) at witness_checkorder+0x469 >> > _sx_xlock(c9bba780,0,c0b49757,cb,0,...) at _sx_xlock+0x85 >> > futex_get0(c0609f8c,c09cc7a8,c9ac7764,c09cc7a8,c084df3c,...) at futex_get0+0x116 >> > linux_sys_futex(c9ac76c0,ea393cf8,ea393d18,ea393d1c,c0b4cf40,...) at >> > linux_sys_futex+0x6f >> > syscall(ea393d38) at syscall+0x2b4 >> > Xint0x80_syscall() at Xint0x80_syscall+0x20 >> > --- syscall (240, Linux ELF, linux_sys_futex), eip = 0x28799533, esp = >> > 0xbfbfc0cc, ebp = 0x4000001 --- >> > >> > > From what dchagin@ told me, the LOR is unavoidable since he has to > acquire two sx locks of the same name. On the other hand, second sx lock > is not visible to any thread except the current one, so the LOR should > be innocent. > >> >> This time seeing this LOR again but with another one just before. >> lock order reversal: >> 1st 0xc75365b8 pseudofs (pseudofs) @ /usr/src/sys/kern/vfs_lookup.c:497 >> 2nd 0xc088ea3c allproc (allproc) @ /usr/src/sys/kern/kern_proc.c:292 >> KDB: stack backtrace: >> db_trace_self_wrapper(c07fd8ea,e82148e4,c060a145,c05fac1b,c08008bf,...) >> at db_trace_self_wrapper+0x26 >> kdb_backtrace(c05fac1b,c08008bf,c58eabe8,c58e30d0,e8214940,...) at >> kdb_backtrace+0x29 >> _witness_debugger(c08008bf,c088ea3c,c07f981d,c58e30d0,c07f96f0,...) at >> _witness_debugger+0x25 >> witness_checkorder(c088ea3c,1,c07f96f0,124,0,...) at witness_checkorder+0x839 >> _sx_slock(c088ea3c,0,c07f96f0,124,c73c4980,...) at _sx_slock+0x85 >> pfind(514,c72ba1a0,4,c07f8d78,c5fe1b40,...) at pfind+0x2f >> pfs_visible(0,0,c07f042d,7c,c7536560,...) at pfs_visible+0x3a >> pfs_lookup(e8214a40,c082715e,c7536560,c7536560,e8214bf8,...) at pfs_lookup+0x3dd >> VOP_CACHEDLOOKUP_APV(c0843960,e8214a40,e8214bf8,e8214be4,c73c4e80,...) >> at VOP_CACHEDLOOKUP_APV+0xc5 >> vfs_cache_lookup(e8214acc,c08087d0,c0875a00,200000,e8214bcc,...) at >> vfs_cache_lookup+0xd6 >> VOP_LOOKUP_APV(c0843960,e8214acc,e8214bf8,1f1,e8214be4,...) at >> VOP_LOOKUP_APV+0xe5 >> lookup(e8214bcc,c5fd1800,0,c5,c5ef77f8,...) at lookup+0x63b >> namei(e8214bcc,c5c1500d,3f3,e8214c20,c5c1500d,...) at namei+0x57f >> kern_alternate_path(c5fe1b40,c0b4921c,2879f478,0,e8214c74,...) at kern_alternate >> _path+0x1cd >> linux_emul_convpath(c5fe1b40,2879f478,0,e8214c74,0,...) at >> linux_emul_convpath+0x3c >> linux_open(c5fe1b40,e8214cf8,e8214d18,e8214d1c,c0b4b58c,...) at linux_open+0x41 >> syscall(e8214d38) at syscall+0x2b4 >> Xint0x80_syscall() at Xint0x80_syscall+0x20 >> --- syscall (5, Linux ELF, linux_open), eip = 0x2889115e, esp = >> 0xbfbfbd1c, ebp = 0xbfbfbd6c --- >> acquiring duplicate lock of same type: "ftlk" >> [...] >> >> I'm running head from 08/26. >> There were recent changes in pseudofs. Could it be fixed? >> Looks like it's connected to running firefox3 with linprocfs (for adobe flash). > > The second LOR actually exposes the right order. It would be interesting > to look up the point where the other order is established. You would manually patch the witness static table with this order and the opposite will show, when happening. Attilio -- Peace can only be achieved by understanding - A. Einstein From borisbsd at googlemail.com Tue Sep 8 10:00:54 2009 From: borisbsd at googlemail.com (Boris) Date: Tue Sep 8 10:01:01 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 6 In-Reply-To: References: <20090611194557.GC98175@bsdcrew.de> <991123400909060811u9bea4d9rdbf453dfaae7c185@mail.gmail.com> <20090906162544.GA39448@bsdcrew.de> <50e4b96fb035ba5eaf5e30fbf12bf9f2.squirrel@webmail.itac.at> <367b2c980909071048j79b28babwcc9d59488d1de3ef@mail.gmail.com> Message-ID: Hi Bernhard, I confirm VT-x is now working. It used to fail on my system with previous release from the time I launched the VM. I am using amd64-8-BETA4 and rev 456. I have experienced a crash of the VM in the middle of the installation of a Debian64 so I will try again and report if it's reproducible. I used an existing virtual disk so I'll try again from scratch. Could you confirm if the patch from Fredrik Lindberg is going to be integrate to a next revision before port freeze? http://lists.freebsd.org/pipermail/freebsd-emulation/2009-September/006740.html Thanks a lot to all people involved ! Boris 2009/9/7 Bernhard Fr?hlich > On Mon, September 7, 2009 7:48 pm, Olivier Smedts wrote: > > 2009/9/7 Bernhard Fr?hlich : > >> On Mon, September 7, 2009 7:41 am, Danny Braniss wrote: > >>> > >>> [...] > >>>> > > > > >>>> > > ok, so some time has passed, but virtualbox-2.2.51r20457.tar.gz is > >>>> no > >>>> > > longer available, there is a > >>>> > > > ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/virtualbox-2.2.51r20457.tar.bz2 > >>>> > > then again in ports/emulatores/virtualbox the version is > >>>> 3.0.51r22226, > >>>> > > > >>>> > > can someone please explain? > >>> > >>> hi, the above was my question, which was totally ignored, not nice. > >>> I will try and refrase it: > >>> the call for testing is for a version (2.2.51r20457) which is not > >>> available, while > >>> the ports is 3.0.51r22226, so while I managed to compile it, it > >>> complains > >>> that COM > >>> is not running, all this under 8BETA-3, both under 32 and 64 bit. > >> > >> I'll try to be nice but it is still unclear to me what you want. The > >> file > >> is available on all 4 master sites that are listed in the ports > >> Makefile. > >> > >> The virtualbox port is still in heavy development so it is strongly > >> recommended that you use the latest version that is in the ports. If > >> that > >> also does not work you could give our svn version a try but be careful > >> with it because it can break in strange ways or destroy your virtual > >> machines. > >> > >> svn co > >> > http://svn.bluelife.at/projects/packages/blueports/emulators/virtualbox/ > > > > Wow... the SVN version works great for me with VT extensions ! I just > > tried a 64 bits 2 processors guest :) > > > > Thanks ! > > According to Alexander Eichner VT-x should work now with the latest vbox > code. So everybody who is using our svn port should already have working > VT-x. We plan to update the virtualbox port in the next few days to get > that version in the tree before the ports freeze. > > -- > Bernhard Fr?hlich > 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-unsubscribe@freebsd.org" > From decke at bluelife.at Tue Sep 8 11:45:38 2009 From: decke at bluelife.at (Bernhard =?iso-8859-1?Q?Fr=F6hlich?=) Date: Tue Sep 8 11:45:44 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 6 In-Reply-To: References: <20090611194557.GC98175@bsdcrew.de> <991123400909060811u9bea4d9rdbf453dfaae7c185@mail.gmail.com> <20090906162544.GA39448@bsdcrew.de> <50e4b96fb035ba5eaf5e30fbf12bf9f2.squirrel@webmail.itac.at> <367b2c980909071048j79b28babwcc9d59488d1de3ef@mail.gmail.com> Message-ID: <5effc292d4e1b51c1b33e8a1f987ccbc.squirrel@webmail.itac.at> On Tue, September 8, 2009 12:00 pm, Boris wrote: > Hi Bernhard, > > I confirm VT-x is now working. It used to fail on my system with previous > release from the time I launched the VM. Good to hear that! Thanks for testing it. > I am using amd64-8-BETA4 and rev 456. > I have experienced a crash of the VM in the middle of the installation of > a > Debian64 so I will try again and report if it's reproducible. I used an > existing virtual disk so I'll try again from scratch. I've seen something similar but haven't found out yet where the problem is. > Could you confirm if the patch from Fredrik Lindberg is going to be > integrate to a next revision before port freeze? > > http://lists.freebsd.org/pipermail/freebsd-emulation/2009-September/006740.html The short answer is no. That patch will not be included in the vbox update. We try to stay as close to the official code as possible and instead send all patches upstream to get them included. So if that patch is stable it should be send to vbox-dev@ and i'm sure aeichner will be glad to have a look at it. I will talk to Fredrik if we can help in any way. -- Bernhard Fr?hlich http://www.bluelife.at/ > 2009/9/7 Bernhard Fr?hlich > >> On Mon, September 7, 2009 7:48 pm, Olivier Smedts wrote: >> > 2009/9/7 Bernhard Fr?hlich : >> >> On Mon, September 7, 2009 7:41 am, Danny Braniss wrote: >> >>> >> >>> [...] >> >>>> > > > >> >>>> > > ok, so some time has passed, but virtualbox-2.2.51r20457.tar.gz >> is >> >>>> no >> >>>> > > longer available, there is a >> >>>> > > >> ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/virtualbox-2.2.51r20457.tar.bz2 >> >>>> > > then again in ports/emulatores/virtualbox the version is >> >>>> 3.0.51r22226, >> >>>> > > >> >>>> > > can someone please explain? >> >>> >> >>> hi, the above was my question, which was totally ignored, not nice. >> >>> I will try and refrase it: >> >>> the call for testing is for a version (2.2.51r20457) which is not >> >>> available, while >> >>> the ports is 3.0.51r22226, so while I managed to compile it, it >> >>> complains >> >>> that COM >> >>> is not running, all this under 8BETA-3, both under 32 and 64 bit. >> >> >> >> I'll try to be nice but it is still unclear to me what you want. The >> >> file >> >> is available on all 4 master sites that are listed in the ports >> >> Makefile. >> >> >> >> The virtualbox port is still in heavy development so it is strongly >> >> recommended that you use the latest version that is in the ports. If >> >> that >> >> also does not work you could give our svn version a try but be >> careful >> >> with it because it can break in strange ways or destroy your virtual >> >> machines. >> >> >> >> svn co >> >> >> http://svn.bluelife.at/projects/packages/blueports/emulators/virtualbox/ >> > >> > Wow... the SVN version works great for me with VT extensions ! I just >> > tried a 64 bits 2 processors guest :) >> > >> > Thanks ! >> >> According to Alexander Eichner VT-x should work now with the latest vbox >> code. So everybody who is using our svn port should already have working >> VT-x. We plan to update the virtualbox port in the next few days to get >> that version in the tree before the ports freeze. >> >> -- >> Bernhard Fr?hlich >> 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-unsubscribe@freebsd.org" >> > From vince at unsane.co.uk Tue Sep 8 12:03:51 2009 From: vince at unsane.co.uk (Vincent Hoffman) Date: Tue Sep 8 12:03:57 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 6 In-Reply-To: References: <20090611194557.GC98175@bsdcrew.de> <991123400909060811u9bea4d9rdbf453dfaae7c185@mail.gmail.com> <20090906162544.GA39448@bsdcrew.de> Message-ID: <4AA64808.4030105@unsane.co.uk> Danny Braniss wrote: > [...] > >>>> ok, so some time has passed, but virtualbox-2.2.51r20457.tar.gz is no >>>> longer available, there is a >>>> ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/virtualbox-2.2.51r20457.tar.bz2 >>>> then again in ports/emulatores/virtualbox the version is 3.0.51r22226, >>>> >>>> can someone please explain? >>>> > > hi, the above was my question, which was totally ignored, not nice. > I will try and refrase it: > the call for testing is for a version (2.2.51r20457) which is not available, while > the ports is 3.0.51r22226, so while I managed to compile it, it complains that COM > is not running, all this under 8BETA-3, both under 32 and 64 bit. > thnaks, > danny > > The call for testing went out on 11th june (http://lists.freebsd.org/pipermail/freebsd-current/2009-June/008061.html) I can only assume it was considered tested and working as the port was committed on 15th june (http://www.freebsd.org/cgi/cvsweb.cgi/ports/emulators/virtualbox/Makefile?rev=1.1;content-type=text%2Fplain) Since then there have been 4 updates to the port. The last of which updated it to 3.0.51r22226 on august 14th. I would say the call for testing is no longer valid, please use the version in ports. Vince > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From bsam at ipt.ru Tue Sep 8 12:09:41 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Tue Sep 8 12:09:49 2009 Subject: deprecate some linux ports Message-ID: <12416892@bb.ipt.ru> Hello List, there are too many linux_base ports at the ports tree now. I'm going to deprecate and remove in three months some of them (those that don't have infrastructure ports): . linux_base-fc6; . linux_base-f7; . linux_base-f9. That will leave: . linux fc4 ports (defaults at 6.x, 7.x); . linux f8 ports (non-defaults for 7.x); . linux f10 ports (defaults for 9.x, 8.x and non-defaults for 7.x). Actually I'd like to deprecate all linux f8 ports (say, for 12 months). Seems like f10 ports is a way to go for 7.x. Opinions, suggestions and thoughts are welcome. Thanks. -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From danny at cs.huji.ac.il Tue Sep 8 14:09:07 2009 From: danny at cs.huji.ac.il (Danny Braniss) Date: Tue Sep 8 14:09:19 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 6 In-Reply-To: <4AA64808.4030105@unsane.co.uk> References: <20090611194557.GC98175@bsdcrew.de> <991123400909060811u9bea4d9rdbf453dfaae7c185@mail.gmail.com> <20090906162544.GA39448@bsdcrew.de> <4AA64808.4030105@unsane.co.uk> Message-ID: > Danny Braniss wrote: > > [...] > > > >>>> ok, so some time has passed, but virtualbox-2.2.51r20457.tar.gz is no > >>>> longer available, there is a > >>>> ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/virtualbox-2.2.51r20457.tar.bz2 > >>>> then again in ports/emulatores/virtualbox the version is 3.0.51r22226, > >>>> > >>>> can someone please explain? > >>>> > > > > hi, the above was my question, which was totally ignored, not nice. > > I will try and refrase it: > > the call for testing is for a version (2.2.51r20457) which is not available, while > > the ports is 3.0.51r22226, so while I managed to compile it, it complains that COM > > is not running, all this under 8BETA-3, both under 32 and 64 bit. > > thnaks, > > danny > > > > > The call for testing went out on 11th june > (http://lists.freebsd.org/pipermail/freebsd-current/2009-June/008061.html) > I can only assume it was considered tested and working as the port was > committed on 15th june > (http://www.freebsd.org/cgi/cvsweb.cgi/ports/emulators/virtualbox/Makefile?rev=1.1;content-type=text%2Fplain) > > Since then there have been 4 updates to the port. The last of which > updated it to 3.0.51r22226 on august 14th. > > I would say the call for testing is no longer valid, please use the > version in ports. thank you, and all those involved! danny From pluknet at gmail.com Tue Sep 8 19:42:15 2009 From: pluknet at gmail.com (pluknet) Date: Tue Sep 8 19:42:27 2009 Subject: acquiring duplicate lock of same type: "ftlk" In-Reply-To: <3bbf2fe10909080213i588493darf8dd1e1ff768cb0a@mail.gmail.com> References: <20090908091114.GH47688@deviant.kiev.zoral.com.ua> <3bbf2fe10909080213i588493darf8dd1e1ff768cb0a@mail.gmail.com> Message-ID: 2009/9/8 Attilio Rao : > 2009/9/8 Kostik Belousov : >> On Mon, Sep 07, 2009 at 10:15:48PM +0400, pluknet wrote: >>> lock order reversal: >>> ?1st 0xc75365b8 pseudofs (pseudofs) @ /usr/src/sys/kern/vfs_lookup.c:497 >>> ?2nd 0xc088ea3c allproc (allproc) @ /usr/src/sys/kern/kern_proc.c:292 >>> KDB: stack backtrace: >>> db_trace_self_wrapper(c07fd8ea,e82148e4,c060a145,c05fac1b,c08008bf,...) >>> at db_trace_self_wrapper+0x26 >>> kdb_backtrace(c05fac1b,c08008bf,c58eabe8,c58e30d0,e8214940,...) at >>> kdb_backtrace+0x29 >>> _witness_debugger(c08008bf,c088ea3c,c07f981d,c58e30d0,c07f96f0,...) at >>> _witness_debugger+0x25 >>> witness_checkorder(c088ea3c,1,c07f96f0,124,0,...) at witness_checkorder+0x839 >>> _sx_slock(c088ea3c,0,c07f96f0,124,c73c4980,...) at _sx_slock+0x85 >>> pfind(514,c72ba1a0,4,c07f8d78,c5fe1b40,...) at pfind+0x2f >>> pfs_visible(0,0,c07f042d,7c,c7536560,...) at pfs_visible+0x3a >>> pfs_lookup(e8214a40,c082715e,c7536560,c7536560,e8214bf8,...) at pfs_lookup+0x3dd >>> VOP_CACHEDLOOKUP_APV(c0843960,e8214a40,e8214bf8,e8214be4,c73c4e80,...) >>> at VOP_CACHEDLOOKUP_APV+0xc5 >>> vfs_cache_lookup(e8214acc,c08087d0,c0875a00,200000,e8214bcc,...) at >>> vfs_cache_lookup+0xd6 >>> VOP_LOOKUP_APV(c0843960,e8214acc,e8214bf8,1f1,e8214be4,...) at >>> VOP_LOOKUP_APV+0xe5 >>> lookup(e8214bcc,c5fd1800,0,c5,c5ef77f8,...) at lookup+0x63b >>> namei(e8214bcc,c5c1500d,3f3,e8214c20,c5c1500d,...) at namei+0x57f >>> kern_alternate_path(c5fe1b40,c0b4921c,2879f478,0,e8214c74,...) at kern_alternate >>> _path+0x1cd >>> linux_emul_convpath(c5fe1b40,2879f478,0,e8214c74,0,...) at >>> linux_emul_convpath+0x3c >>> linux_open(c5fe1b40,e8214cf8,e8214d18,e8214d1c,c0b4b58c,...) at linux_open+0x41 >>> syscall(e8214d38) at syscall+0x2b4 >>> Xint0x80_syscall() at Xint0x80_syscall+0x20 >>> --- syscall (5, Linux ELF, linux_open), eip = 0x2889115e, esp = >>> 0xbfbfbd1c, ebp = 0xbfbfbd6c --- >>> acquiring duplicate lock of same type: "ftlk" >>> [...] >> >> The second LOR actually exposes the right order. It would be interesting >> to look up the point where the other order is established. > > You would manually patch the witness static table with this order and > the opposite will show, when happening. > I've patched witness order table, and still no opposite case, nor any pseudofs related LORs at all. { "pseudofs", &lock_class_lockmgr }, { "allproc", &lock_class_sx }, { NULL, NULL }, Seen orders with pseudofs: "ufs","pseudofs" "pseudofs","allproc" "pseudofs","process lock" "pseudofs","vnode interlock" "pseudofs","struct mount mtx" "pseudofs","UMA zone" "pseudofs","sleep mtxpool" "pseudofs","Name Cache" "pseudofs","vnode_free_list" "pseudofs","pfs_node" "pseudofs","pfs_vncache" Something else? -- wbr, pluknet From attilio at freebsd.org Tue Sep 8 19:48:39 2009 From: attilio at freebsd.org (Attilio Rao) Date: Tue Sep 8 19:48:50 2009 Subject: acquiring duplicate lock of same type: "ftlk" In-Reply-To: References: <20090908091114.GH47688@deviant.kiev.zoral.com.ua> <3bbf2fe10909080213i588493darf8dd1e1ff768cb0a@mail.gmail.com> Message-ID: <3bbf2fe10909081248w3a09c9a8ge3b6fa9de8b2d3e9@mail.gmail.com> 2009/9/8 pluknet : > 2009/9/8 Attilio Rao : >> 2009/9/8 Kostik Belousov : >>> On Mon, Sep 07, 2009 at 10:15:48PM +0400, pluknet wrote: >>>> lock order reversal: >>>> 1st 0xc75365b8 pseudofs (pseudofs) @ /usr/src/sys/kern/vfs_lookup.c:497 >>>> 2nd 0xc088ea3c allproc (allproc) @ /usr/src/sys/kern/kern_proc.c:292 >>>> KDB: stack backtrace: >>>> db_trace_self_wrapper(c07fd8ea,e82148e4,c060a145,c05fac1b,c08008bf,...) >>>> at db_trace_self_wrapper+0x26 >>>> kdb_backtrace(c05fac1b,c08008bf,c58eabe8,c58e30d0,e8214940,...) at >>>> kdb_backtrace+0x29 >>>> _witness_debugger(c08008bf,c088ea3c,c07f981d,c58e30d0,c07f96f0,...) at >>>> _witness_debugger+0x25 >>>> witness_checkorder(c088ea3c,1,c07f96f0,124,0,...) at witness_checkorder+0x839 >>>> _sx_slock(c088ea3c,0,c07f96f0,124,c73c4980,...) at _sx_slock+0x85 >>>> pfind(514,c72ba1a0,4,c07f8d78,c5fe1b40,...) at pfind+0x2f >>>> pfs_visible(0,0,c07f042d,7c,c7536560,...) at pfs_visible+0x3a >>>> pfs_lookup(e8214a40,c082715e,c7536560,c7536560,e8214bf8,...) at pfs_lookup+0x3dd >>>> VOP_CACHEDLOOKUP_APV(c0843960,e8214a40,e8214bf8,e8214be4,c73c4e80,...) >>>> at VOP_CACHEDLOOKUP_APV+0xc5 >>>> vfs_cache_lookup(e8214acc,c08087d0,c0875a00,200000,e8214bcc,...) at >>>> vfs_cache_lookup+0xd6 >>>> VOP_LOOKUP_APV(c0843960,e8214acc,e8214bf8,1f1,e8214be4,...) at >>>> VOP_LOOKUP_APV+0xe5 >>>> lookup(e8214bcc,c5fd1800,0,c5,c5ef77f8,...) at lookup+0x63b >>>> namei(e8214bcc,c5c1500d,3f3,e8214c20,c5c1500d,...) at namei+0x57f >>>> kern_alternate_path(c5fe1b40,c0b4921c,2879f478,0,e8214c74,...) at kern_alternate >>>> _path+0x1cd >>>> linux_emul_convpath(c5fe1b40,2879f478,0,e8214c74,0,...) at >>>> linux_emul_convpath+0x3c >>>> linux_open(c5fe1b40,e8214cf8,e8214d18,e8214d1c,c0b4b58c,...) at linux_open+0x41 >>>> syscall(e8214d38) at syscall+0x2b4 >>>> Xint0x80_syscall() at Xint0x80_syscall+0x20 >>>> --- syscall (5, Linux ELF, linux_open), eip = 0x2889115e, esp = >>>> 0xbfbfbd1c, ebp = 0xbfbfbd6c --- >>>> acquiring duplicate lock of same type: "ftlk" >>>> [...] >>> >>> The second LOR actually exposes the right order. It would be interesting >>> to look up the point where the other order is established. >> >> You would manually patch the witness static table with this order and >> the opposite will show, when happening. >> > > I've patched witness order table, and still no opposite case, > nor any pseudofs related LORs at all. > { "pseudofs", &lock_class_lockmgr }, > { "allproc", &lock_class_sx }, > { NULL, NULL }, > > Seen orders with pseudofs: > "ufs","pseudofs" > "pseudofs","allproc" > "pseudofs","process lock" > "pseudofs","vnode interlock" > "pseudofs","struct mount mtx" > "pseudofs","UMA zone" > "pseudofs","sleep mtxpool" > "pseudofs","Name Cache" > "pseudofs","vnode_free_list" > "pseudofs","pfs_node" > "pseudofs","pfs_vncache" > > Something else? Probabilly it just takes time. You should try to recreate conditions you did before to get this LOR. Attilio -- Peace can only be achieved by understanding - A. Einstein From miwi at FreeBSD.org Wed Sep 9 08:51:09 2009 From: miwi at FreeBSD.org (Martin Wilke) Date: Wed Sep 9 08:51:16 2009 Subject: [ports-i386@FreeBSD.org: linux_base-f9-10 failed on i386 7] Message-ID: <20090909085104.GI98067@bsdcrew.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - ----- Forwarded message from User Ports-i386 ----- Date: Wed, 9 Sep 2009 08:40:31 GMT From: User Ports-i386 To: erwin@FreeBSD.org, miwi@FreeBSD.org, linimon@FreeBSD.org Subject: linux_base-f9-10 failed on i386 7 You can also find this build log at http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/a.7.20090908204253/linux_base-f9-10.log building linux_base-f9-10 on gohan48.freebsd.org in directory /x/tmp/7/20090908204253/chroot/15 building for: 7.2-STABLE i386 maintained by: emulation@FreeBSD.org port directory: /usr/ports/emulators/linux_base-f9 Makefile ident: $FreeBSD: ports/emulators/linux_base-f9/Makefile,v 1.55 2009/09/08 09:16:27 bsam Exp $ build started at Wed Sep 9 08:40:21 UTC 2009 FETCH_DEPENDS= PATCH_DEPENDS= EXTRACT_DEPENDS=gettext-0.17_1.tbz libiconv-1.13.1.tbz popt-1.14.tbz rpm-3.0.6_14.tbz BUILD_DEPENDS= RUN_DEPENDS= prefixes: LOCALBASE=usr/local X11BASE=usr/local add_pkg ================================================================ ======================================== => basesystem-8.1-1.noarch.rpm is not in /a/ports/emulators/linux_base-f9/distinfo.i386. => Either /a/ports/emulators/linux_base-f9/distinfo.i386 is out of date, or => basesystem-8.1-1.noarch.rpm is spelled incorrectly. *** Error code 1 Stop in /a/ports/emulators/linux_base-f9. ================================================================ build of /usr/ports/emulators/linux_base-f9 ended at Wed Sep 9 08:40:26 UTC 2009 - ----- End forwarded message ----- - -- +-----------------------+-------------------------------+ | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | | Skype : splash_111 | Mail : miwi(at)FreeBSD.org | +-----------------------+-------------------------------+ | Mess with the Best, Die like the Rest! | +-----------------------+-------------------------------+ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iEYEARECAAYFAkqnbHcACgkQdLJIhLHm/OmkLQCguk53gMHPKyzZGuk1Gr0torDu YcwAnjbs3ZWmNhIdw1elYaOvmkQHckEh =k+sm -----END PGP SIGNATURE----- From bsam at ipt.ru Wed Sep 9 09:40:59 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Wed Sep 9 09:41:06 2009 Subject: [ports-i386@FreeBSD.org: linux_base-f9-10 failed on i386 7] In-Reply-To: <20090909085104.GI98067@bsdcrew.de> (Martin Wilke's message of "Wed, 9 Sep 2009 10:51:04 +0200") References: <20090909085104.GI98067@bsdcrew.de> Message-ID: <01684949@bb.ipt.ru> On Wed, 9 Sep 2009 10:51:04 +0200 Martin Wilke wrote: > Date: Wed, 9 Sep 2009 08:40:31 GMT > From: User Ports-i386 > To: erwin@FreeBSD.org, miwi@FreeBSD.org, linimon@FreeBSD.org > Subject: linux_base-f9-10 failed on i386 7 The port is fixed, thanks! -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From fli at shapeshifter.se Wed Sep 9 10:35:11 2009 From: fli at shapeshifter.se (Fredrik Lindberg) Date: Wed Sep 9 10:35:18 2009 Subject: VirtualBox network patches for FreeBSD (vboxnetflt + vboxnetadp) Message-ID: <4AA784D9.80405@shapeshifter.se> Hi These patches implement bridge and host only networking on FreeBSD, they have been tested on FreeBSD 7 and 8 by a few different people. The only known issue is that they might not work with wireless cards. At least it didn't work on my iwi-backed wlan0 interface on FreeBSD 8. The patches are split into different files for easier overview http://www.shapeshifter.se/pub/patches/virtualbox/vbox-freebsd-netif-20090908.patch http://www.shapeshifter.se/pub/patches/virtualbox/vbox-freebsd-vboxnetadp-20090908.patch http://www.shapeshifter.se/pub/patches/virtualbox/vbox-freebsd-vboxnetflt-20090908.patch http://www.shapeshifter.se/pub/patches/virtualbox/Config.kmk-20090908.patch http://www.shapeshifter.se/pub/patches/virtualbox/src-VBox-HostDrivers-Makefile.kmk-20090908.patch Original code is under the MIT license, patches to Makefiles, etc are under whatever license you want (I don't claim any copyright over these). People running FreeBSD and want to test this with the vbox version 3.0.51.r22226 that currently is in the ports tree needs the following additional patches. http://www.shapeshifter.se/pub/patches/virtualbox/Config.kmk-r22226-20090908.patch http://www.shapeshifter.se/pub/patches/virtualbox/virtualbox-port-20090907.patch http://www.shapeshifter.se/pub/patches/virtualbox/ConsoleImpl2.cpp.patch Apply/compile with cd /usr/ports/emulators/virtualbox make clean patch mkdir work/virtualbox-3.0.51r22226/src/VBox/HostDrivers/VBoxNetFlt/freebsd mkdir work/virtualbox-3.0.51r22226/src/VBox/HostDrivers/VBoxNetAdp/freebsd patch < virtualbox-port-20090907.patch patch -d work/virtualbox-3.0.51r22226/Config.kmk-r22226-20090908.patch patch -d work/virtualbox-3.0.51r22226/ConsoleImpl2.cpp.patch patch -d work/virtualbox-3.0.51r22226/src-VBox-HostDrivers-Makefile.kmk-20090908.patch patch -d work/virtualbox-3.0.51r22226/vbox-freebsd-netif-20090908.patch patch -d work/virtualbox-3.0.51r22226/vbox-freebsd-vboxnetadp-20090908.patch patch -d work/virtualbox-3.0.51r22226/vbox-freebsd-vboxnetflt-20090908.patch make install Fredrik From danny at cs.huji.ac.il Wed Sep 9 13:11:07 2009 From: danny at cs.huji.ac.il (Danny Braniss) Date: Wed Sep 9 13:11:15 2009 Subject: VirtualBox network patches for FreeBSD (vboxnetflt + vboxnetadp) In-Reply-To: <4AA784D9.80405@shapeshifter.se> References: <4AA784D9.80405@shapeshifter.se> Message-ID: > Hi > > These patches implement bridge and host only networking on FreeBSD, they > have been tested on FreeBSD 7 and 8 by a few different people. The only > known issue is that they might not work with wireless cards. At least > it didn't work on my iwi-backed wlan0 interface on FreeBSD 8. > > The patches are split into different files for easier overview > > http://www.shapeshifter.se/pub/patches/virtualbox/vbox-freebsd-netif-20090908.patch > http://www.shapeshifter.se/pub/patches/virtualbox/vbox-freebsd-vboxnetadp-20090908.patch > http://www.shapeshifter.se/pub/patches/virtualbox/vbox-freebsd-vboxnetflt-20090908.patch > http://www.shapeshifter.se/pub/patches/virtualbox/Config.kmk-20090908.patch > http://www.shapeshifter.se/pub/patches/virtualbox/src-VBox-HostDrivers-Makefile.kmk-20090908.patch > > Original code is under the MIT license, patches to Makefiles, etc are > under whatever license you want (I don't claim any copyright over > these). > > > People running FreeBSD and want to test this with the vbox version > 3.0.51.r22226 that currently is in the ports tree needs the following > additional patches. > > http://www.shapeshifter.se/pub/patches/virtualbox/Config.kmk-r22226-20090908.patch > http://www.shapeshifter.se/pub/patches/virtualbox/virtualbox-port-20090907.patch > http://www.shapeshifter.se/pub/patches/virtualbox/ConsoleImpl2.cpp.patch > > Apply/compile with > cd /usr/ports/emulators/virtualbox > make clean patch > mkdir work/virtualbox-3.0.51r22226/src/VBox/HostDrivers/VBoxNetFlt/freebsd > mkdir work/virtualbox-3.0.51r22226/src/VBox/HostDrivers/VBoxNetAdp/freebsd > patch < virtualbox-port-20090907.patch > patch -d work/virtualbox-3.0.51r22226/Config.kmk-r22226-20090908.patch > patch -d work/virtualbox-3.0.51r22226/ConsoleImpl2.cpp.patch > patch -d > work/virtualbox-3.0.51r22226/src-VBox-HostDrivers-Makefile.kmk-20090908.patch > patch -d work/virtualbox-3.0.51r22226/vbox-freebsd-netif-20090908.patch > patch -d work/virtualbox-3.0.51r22226/vbox-freebsd-vboxnetadp-20090908.patch > patch -d work/virtualbox-3.0.51r22226/vbox-freebsd-vboxnetflt-20090908.patch > make install > great work! any chance it will support PXE? what about throughput, at the moment iperf timet it at 120Mbits/sec but the host is connected at 1G. danny From fli at shapeshifter.se Wed Sep 9 13:31:41 2009 From: fli at shapeshifter.se (Fredrik Lindberg) Date: Wed Sep 9 13:31:47 2009 Subject: VirtualBox network patches for FreeBSD (vboxnetflt + vboxnetadp) In-Reply-To: References: <4AA784D9.80405@shapeshifter.se> Message-ID: <4AA7AE3B.9050705@shapeshifter.se> Danny Braniss wrote: > > great work! > any chance it will support PXE? > what about throughput, at the moment iperf timet it at 120Mbits/sec > but the host is connected at 1G. > > danny > It supports PXE. However the OSE version of VirtualBox does only have PXE booting on the PCnet interfaces not the Intel ones. Also, if you're going to boot a FreeBSD kernel you'll need to patch the etherboot code in virtualbox, otherwise it will abort with "Unable to load file". I don't know whether it's FreeBSDs pxeboot or etherboot that is the offender here. See, for more info http://lists.freebsd.org/pipermail/freebsd-emulation/2007-April/003503.html Throughput is not something I have actively looked at, there might be something that can be optimized regarding mbuf to SG-convertion. One source is most likely due to its dependency on the netgraph system which causes an additional packet detour. It uses netgraph because it's the only reliable way to hook into the input/output path of ethernet interfaces, and that also works properly on FreeBSD 7 and higher. Fredrik From danny at cs.huji.ac.il Wed Sep 9 13:56:53 2009 From: danny at cs.huji.ac.il (Danny Braniss) Date: Wed Sep 9 14:51:08 2009 Subject: VirtualBox network patches for FreeBSD (vboxnetflt + vboxnetadp) In-Reply-To: Your message of Wed, 09 Sep 2009 15:31:39 +0200 . Message-ID: > It supports PXE. However the OSE version of VirtualBox does only have > PXE booting on the PCnet interfaces not the Intel ones. > Also, if you're going to boot a FreeBSD kernel you'll need to patch > the etherboot code in virtualbox, otherwise it will abort with > "Unable to load file". i just tried, the pxeboot is loaded, but then it starts complaining: 132.65.16.80 is not in my arp table! ... this is the nfs server, which is differnet from the tftp server. the error seems to come from the pxe code? > I don't know whether it's FreeBSDs pxeboot or etherboot that is the > offender here. > > See, for more info > http://lists.freebsd.org/pipermail/freebsd-emulation/2007-April/003503.html > > > Throughput is not something I have actively looked at, there might be > something that can be optimized regarding mbuf to SG-convertion. > One source is most likely due to its dependency on the netgraph > system which causes an additional packet detour. > It uses netgraph because it's the only reliable way to hook > into the input/output path of ethernet interfaces, and > that also works properly on FreeBSD 7 and higher. > > Fredrik I'll try and install vbox on an apple server, which is connected at 1g, and see what speeds i get there, maybe that will shed some light. cheers, danny From alexbestms at math.uni-muenster.de Wed Sep 9 16:40:30 2009 From: alexbestms at math.uni-muenster.de (Alexander Best) Date: Wed Sep 9 16:40:36 2009 Subject: deprecate some linux ports Message-ID: seems like a good idea. especially for people new to freebsd the different linux base versions are confusing. the only linux-f8-* port i'm running atm is graphics/linux-f8-libGLU since there's no linux-f10-libGLU port available. using graphics/linux-f10-dri instead isn't an option for me since the port shares some files with the nvidia freebsd binary graphic drivers. cheers. alex From alexbestms at math.uni-muenster.de Wed Sep 9 18:26:17 2009 From: alexbestms at math.uni-muenster.de (Alexander Best) Date: Wed Sep 9 18:26:22 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 6 Message-ID: just updated to virtualbox-3.0.51.r22683. all my virtual machines are now marked as "inaccessable". all machines have the same problem. here's an example: Error reading /home/arundel/.VirtualBox/Machines/slackware/slackware.xml (line 23) -- Invalid value '0' in Boot/Order/@position: must be greater than 0 and less than 5. /usr/local/src/virtualbox/work/virtualbox-3.0.51r22683/src/VBox/Main/MachineImpl.cpp[4810] (nsresult Machine::loadSettings(bool)). Result Code: NS_ERROR_FAILURE (0x80004005) Component: VirtualBox Interface: IVirtualBox {3f4ab53a-199b-4526-a91a-93ff62e456b8} i'm running 9.0-CURRENT (r196879). cheers. alex From scf at FreeBSD.org Wed Sep 9 19:03:54 2009 From: scf at FreeBSD.org (Sean C. Farley) Date: Wed Sep 9 19:04:00 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 6 In-Reply-To: References: Message-ID: On Wed, 9 Sep 2009, Alexander Best wrote: > just updated to virtualbox-3.0.51.r22683. all my virtual machines are > now marked as "inaccessable". all machines have the same problem. > here's an example: > > Error reading /home/arundel/.VirtualBox/Machines/slackware/slackware.xml (line > 23) -- Invalid value '0' in Boot/Order/@position: must be greater than 0 and > less than 5. > /usr/local/src/virtualbox/work/virtualbox-3.0.51r22683/src/VBox/Main/MachineImpl.cpp[4810] > (nsresult Machine::loadSettings(bool)). > Result Code: > NS_ERROR_FAILURE (0x80004005) > Component: > VirtualBox > Interface: > IVirtualBox {3f4ab53a-199b-4526-a91a-93ff62e456b8} > > i'm running 9.0-CURRENT (r196879). I had that with a few machines, but I thought I had done something wrong since I had been hand editing them. The fix is easy: edit the machine's XML file and renumber the elements under the Boot element to have positions greater than zero. Also, for each snapshot in the XML file, there will be a separate Boot element to fix. Sean -- scf@FreeBSD.org From jhb at freebsd.org Wed Sep 9 19:08:57 2009 From: jhb at freebsd.org (John Baldwin) Date: Wed Sep 9 19:09:13 2009 Subject: acquiring duplicate lock of same type: "ftlk" In-Reply-To: References: <3bbf2fe10909080213i588493darf8dd1e1ff768cb0a@mail.gmail.com> Message-ID: <200909091455.42039.jhb@freebsd.org> On Tuesday 08 September 2009 3:42:13 pm pluknet wrote: > 2009/9/8 Attilio Rao : > > 2009/9/8 Kostik Belousov : > >> On Mon, Sep 07, 2009 at 10:15:48PM +0400, pluknet wrote: > >>> lock order reversal: > >>> ?1st 0xc75365b8 pseudofs (pseudofs) @ /usr/src/sys/kern/vfs_lookup.c:497 > >>> ?2nd 0xc088ea3c allproc (allproc) @ /usr/src/sys/kern/kern_proc.c:292 > >>> KDB: stack backtrace: > >>> db_trace_self_wrapper(c07fd8ea,e82148e4,c060a145,c05fac1b,c08008bf,...) > >>> at db_trace_self_wrapper+0x26 > >>> kdb_backtrace(c05fac1b,c08008bf,c58eabe8,c58e30d0,e8214940,...) at > >>> kdb_backtrace+0x29 > >>> _witness_debugger(c08008bf,c088ea3c,c07f981d,c58e30d0,c07f96f0,...) at > >>> _witness_debugger+0x25 > >>> witness_checkorder(c088ea3c,1,c07f96f0,124,0,...) at witness_checkorder+0x839 > >>> _sx_slock(c088ea3c,0,c07f96f0,124,c73c4980,...) at _sx_slock+0x85 > >>> pfind(514,c72ba1a0,4,c07f8d78,c5fe1b40,...) at pfind+0x2f > >>> pfs_visible(0,0,c07f042d,7c,c7536560,...) at pfs_visible+0x3a > >>> pfs_lookup(e8214a40,c082715e,c7536560,c7536560,e8214bf8,...) at pfs_lookup+0x3dd > >>> VOP_CACHEDLOOKUP_APV(c0843960,e8214a40,e8214bf8,e8214be4,c73c4e80,...) > >>> at VOP_CACHEDLOOKUP_APV+0xc5 > >>> vfs_cache_lookup(e8214acc,c08087d0,c0875a00,200000,e8214bcc,...) at > >>> vfs_cache_lookup+0xd6 > >>> VOP_LOOKUP_APV(c0843960,e8214acc,e8214bf8,1f1,e8214be4,...) at > >>> VOP_LOOKUP_APV+0xe5 > >>> lookup(e8214bcc,c5fd1800,0,c5,c5ef77f8,...) at lookup+0x63b > >>> namei(e8214bcc,c5c1500d,3f3,e8214c20,c5c1500d,...) at namei+0x57f > >>> kern_alternate_path(c5fe1b40,c0b4921c,2879f478,0,e8214c74,...) at kern_alternate > >>> _path+0x1cd > >>> linux_emul_convpath(c5fe1b40,2879f478,0,e8214c74,0,...) at > >>> linux_emul_convpath+0x3c > >>> linux_open(c5fe1b40,e8214cf8,e8214d18,e8214d1c,c0b4b58c,...) at linux_open+0x41 > >>> syscall(e8214d38) at syscall+0x2b4 > >>> Xint0x80_syscall() at Xint0x80_syscall+0x20 > >>> --- syscall (5, Linux ELF, linux_open), eip = 0x2889115e, esp = > >>> 0xbfbfbd1c, ebp = 0xbfbfbd6c --- > >>> acquiring duplicate lock of same type: "ftlk" > >>> [...] > >> > >> The second LOR actually exposes the right order. It would be interesting > >> to look up the point where the other order is established. > > > > You would manually patch the witness static table with this order and > > the opposite will show, when happening. > > > > I've patched witness order table, and still no opposite case, > nor any pseudofs related LORs at all. > { "pseudofs", &lock_class_lockmgr }, > { "allproc", &lock_class_sx }, > { NULL, NULL }, > > Seen orders with pseudofs: > "ufs","pseudofs" > "pseudofs","allproc" > "pseudofs","process lock" > "pseudofs","vnode interlock" > "pseudofs","struct mount mtx" > "pseudofs","UMA zone" > "pseudofs","sleep mtxpool" > "pseudofs","Name Cache" > "pseudofs","vnode_free_list" > "pseudofs","pfs_node" > "pseudofs","pfs_vncache" > > Something else? What are the seen orders with "allproc"? -- John Baldwin From alexbestms at math.uni-muenster.de Wed Sep 9 19:11:31 2009 From: alexbestms at math.uni-muenster.de (Alexander Best) Date: Wed Sep 9 19:11:38 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 6 In-Reply-To: Message-ID: thanks for the hint. all machines are now valid again. would be great to have a script doing this automatically. cheers. alex Sean C. Farley schrieb am 2009-09-09: > On Wed, 9 Sep 2009, Alexander Best wrote: > >just updated to virtualbox-3.0.51.r22683. all my virtual machines > >are now marked as "inaccessable". all machines have the same > >problem. here's an example: > >Error reading > >/home/arundel/.VirtualBox/Machines/slackware/slackware.xml (line > >23) -- Invalid value '0' in Boot/Order/@position: must be greater > >than 0 and > >less than 5. > >/usr/local/src/virtualbox/work/virtualbox-3.0.51r22683/src/VBox/Main > >/MachineImpl.cpp[4810] > >(nsresult Machine::loadSettings(bool)). > >Result Code: > >NS_ERROR_FAILURE (0x80004005) > >Component: > >VirtualBox > >Interface: > >IVirtualBox {3f4ab53a-199b-4526-a91a-93ff62e456b8} > >i'm running 9.0-CURRENT (r196879). > I had that with a few machines, but I thought I had done something > wrong since I had been hand editing them. The fix is easy: edit > the machine's XML file and renumber the elements under the Boot > element to have positions greater than zero. Also, for each > snapshot in the XML file, there will be a separate Boot element to > fix. > Sean > -- > scf@FreeBSD.org From fli at shapeshifter.se Wed Sep 9 19:24:18 2009 From: fli at shapeshifter.se (Fredrik Lindberg) Date: Wed Sep 9 19:24:31 2009 Subject: Enable DrvHostSerial on FreeBSD Message-ID: <4AA800DF.2090904@shapeshifter.se> The existing code for the host serial device (DrvHostSerial.cpp) works on FreeBSD, it's just disabled by ifdefs. Attached is a patch to enable it, MIT license or whatever you want. Compile-tested on FreeBSD 7 and 8, runtime tested on FreeBSD 8. I've tested it with a cross-over serial cable (null modem) connected between two (physical) machines. Used cu and minicom inside guest to connect to another cu/minicom-instance running on the second machine. My testing has been limited to this as I really don't have any other fancy serial equipment :) Notes to people trying this with the ports version, the patch does not apply cleanly and you'll have to modify src/VBox/Devices/Makefile.kmk by hand. Fredrik -------------- next part -------------- Index: src/VBox/Devices/Builtins.cpp =================================================================== --- src/VBox/Devices/Builtins.cpp (revision 22813) +++ src/VBox/Devices/Builtins.cpp (working copy) @@ -269,7 +269,7 @@ return rc; #endif -#if defined(RT_OS_DARWIN) || defined(RT_OS_LINUX) || defined(RT_OS_SOLARIS) || defined(RT_OS_WINDOWS) +#if defined(RT_OS_DARWIN) || defined(RT_OS_LINUX) || defined(RT_OS_SOLARIS) || defined(RT_OS_WINDOWS) || defined(RT_OS_FREEBSD) rc = pCallbacks->pfnRegister(pCallbacks, &g_DrvHostSerial); if (RT_FAILURE(rc)) return rc; Index: src/VBox/Devices/Serial/DrvHostSerial.cpp =================================================================== --- src/VBox/Devices/Serial/DrvHostSerial.cpp (revision 22864) +++ src/VBox/Devices/Serial/DrvHostSerial.cpp (working copy) @@ -37,7 +37,7 @@ #include #include -#if defined(RT_OS_LINUX) || defined(RT_OS_DARWIN) || defined(RT_OS_SOLARIS) +#if defined(RT_OS_LINUX) || defined(RT_OS_DARWIN) || defined(RT_OS_SOLARIS) || defined(RT_OS_FREEBSD) # include # ifdef RT_OS_SOLARIS # include @@ -113,7 +113,7 @@ /** the device path */ char *pszDevicePath; -#if defined(RT_OS_LINUX) || defined(RT_OS_DARWIN) || defined(RT_OS_SOLARIS) +#if defined(RT_OS_LINUX) || defined(RT_OS_DARWIN) || defined(RT_OS_SOLARIS) || defined(RT_OS_FREEBSD) /** the device handle */ RTFILE DeviceFile; # ifdef RT_OS_DARWIN @@ -244,7 +244,7 @@ static DECLCALLBACK(int) drvHostSerialSetParameters(PPDMICHAR pInterface, unsigned Bps, char chParity, unsigned cDataBits, unsigned cStopBits) { PDRVHOSTSERIAL pThis = PDMICHAR_2_DRVHOSTSERIAL(pInterface); -#if defined(RT_OS_LINUX) || defined(RT_OS_DARWIN) || defined(RT_OS_SOLARIS) +#if defined(RT_OS_LINUX) || defined(RT_OS_DARWIN) || defined(RT_OS_SOLARIS) || defined(RT_OS_FREEBSD) struct termios *termiosSetup; int baud_rate; #elif defined(RT_OS_WINDOWS) @@ -253,7 +253,7 @@ LogFlow(("%s: Bps=%u chParity=%c cDataBits=%u cStopBits=%u\n", __FUNCTION__, Bps, chParity, cDataBits, cStopBits)); -#if defined(RT_OS_LINUX) || defined(RT_OS_DARWIN) || defined(RT_OS_SOLARIS) +#if defined(RT_OS_LINUX) || defined(RT_OS_DARWIN) || defined(RT_OS_SOLARIS) || defined(RT_OS_FREEBSD) termiosSetup = (struct termios *)RTMemTmpAllocZ(sizeof(struct termios)); /* Enable receiver */ @@ -517,7 +517,7 @@ #ifdef DEBUG uint64_t volatile u64Now = RTTimeNanoTS(); NOREF(u64Now); #endif -#if defined(RT_OS_LINUX) || defined(RT_OS_DARWIN) || defined(RT_OS_SOLARIS) +#if defined(RT_OS_LINUX) || defined(RT_OS_DARWIN) || defined(RT_OS_SOLARIS) || defined(RT_OS_FREEBSD) size_t cbWritten; rc = RTFileWrite(pThis->DeviceFile, abBuf, cb, &cbWritten); @@ -598,7 +598,7 @@ uint8_t abBuf[1]; abBuf[0] = pThis->aSendQueue[iTail]; -#if defined(RT_OS_LINUX) || defined(RT_OS_DARWIN) || defined(RT_OS_SOLARIS) +#if defined(RT_OS_LINUX) || defined(RT_OS_DARWIN) || defined(RT_OS_SOLARIS) || defined(RT_OS_FREEBSD) rc = RTFileWrite(pThis->DeviceFile, abBuf, cbProcessed, NULL); @@ -763,7 +763,7 @@ } cbRemaining = cbRead; -#elif defined(RT_OS_LINUX) || defined(RT_OS_SOLARIS) +#elif defined(RT_OS_LINUX) || defined(RT_OS_SOLARIS) || defined(RT_OS_FREEBSD) size_t cbRead; struct pollfd aFDs[2]; @@ -923,7 +923,7 @@ static DECLCALLBACK(int) drvHostSerialWakeupRecvThread(PPDMDRVINS pDrvIns, PPDMTHREAD pThread) { PDRVHOSTSERIAL pThis = PDMINS_2_DATA(pDrvIns, PDRVHOSTSERIAL); -#if defined(RT_OS_LINUX) || defined(RT_OS_DARWIN) || defined(RT_OS_SOLARIS) +#if defined(RT_OS_LINUX) || defined(RT_OS_DARWIN) || defined(RT_OS_SOLARIS) || defined(RT_OS_FREEBSD) return RTFileWrite(pThis->WakeupPipeW, "", 1, NULL); #elif defined(RT_OS_WINDOWS) if (!SetEvent(pThis->hHaltEventSem)) @@ -934,7 +934,7 @@ #endif } -#if defined(RT_OS_LINUX) || defined(RT_OS_DARWIN) || defined(RT_OS_SOLARIS) +#if defined(RT_OS_LINUX) || defined(RT_OS_DARWIN) || defined(RT_OS_SOLARIS) || defined(RT_OS_FREEBSD) /* -=-=-=-=- Monitor thread -=-=-=-=- */ /** @@ -1139,7 +1139,7 @@ { PDRVHOSTSERIAL pThis = PDMICHAR_2_DRVHOSTSERIAL(pInterface); -#if defined(RT_OS_LINUX) || defined(RT_OS_DARWIN) || defined(RT_OS_SOLARIS) +#if defined(RT_OS_LINUX) || defined(RT_OS_DARWIN) || defined(RT_OS_SOLARIS) || defined(RT_OS_FREEBSD) int modemStateSet = 0; int modemStateClear = 0; @@ -1188,7 +1188,7 @@ /* * Init basic data members and interfaces. */ -#if defined(RT_OS_LINUX) || defined(RT_OS_DARWIN) || defined(RT_OS_SOLARIS) +#if defined(RT_OS_LINUX) || defined(RT_OS_DARWIN) || defined(RT_OS_SOLARIS) || defined(RT_OS_FREEBSD) pThis->DeviceFile = NIL_RTFILE; # ifdef RT_OS_DARWIN pThis->DeviceFileR = NIL_RTFILE; @@ -1269,7 +1269,7 @@ { case VERR_ACCESS_DENIED: return PDMDrvHlpVMSetError(pDrvIns, rc, RT_SRC_POS, -#if defined(RT_OS_LINUX) || defined(RT_OS_DARWIN) || defined(RT_OS_SOLARIS) +#if defined(RT_OS_LINUX) || defined(RT_OS_DARWIN) || defined(RT_OS_SOLARIS) || defined(RT_OS_FREEBSD) N_("Cannot open host device '%s' for read/write access. Check the permissions " "of that device ('/bin/ls -l %s'): Most probably you need to be member " "of the device group. Make sure that you logout/login after changing " @@ -1287,7 +1287,7 @@ } /* Set to non blocking I/O */ -#if defined(RT_OS_LINUX) || defined(RT_OS_DARWIN) || defined(RT_OS_SOLARIS) +#if defined(RT_OS_LINUX) || defined(RT_OS_DARWIN) || defined(RT_OS_SOLARIS) || defined(RT_OS_FREEBSD) fcntl(pThis->DeviceFile, F_SETFL, O_NONBLOCK); # ifdef RT_OS_DARWIN @@ -1339,7 +1339,7 @@ if (RT_FAILURE(rc)) return PDMDrvHlpVMSetError(pDrvIns, rc, RT_SRC_POS, N_("HostSerial#%d cannot create send thread"), pDrvIns->iInstance); -#if defined(RT_OS_LINUX) || defined(RT_OS_DARWIN) || defined(RT_OS_SOLARIS) +#if defined(RT_OS_LINUX) || defined(RT_OS_DARWIN) || defined(RT_OS_SOLARIS) || defined(RT_OS_FREEBSD) /* Linux & darwin needs a separate thread which monitors the status lines. */ # ifndef RT_OS_LINUX ioctl(pThis->DeviceFile, TIOCMGET, &pThis->fStatusLines); @@ -1382,7 +1382,7 @@ RTSemEventDestroy(pThis->SendSem); pThis->SendSem = NIL_RTSEMEVENT; -#if defined(RT_OS_LINUX) || defined(RT_OS_DARWIN) || defined(RT_OS_SOLARIS) +#if defined(RT_OS_LINUX) || defined(RT_OS_DARWIN) || defined(RT_OS_SOLARIS) || defined(RT_OS_FREEBSD) if (pThis->WakeupPipeW != NIL_RTFILE) { Index: src/VBox/Devices/Makefile.kmk =================================================================== --- src/VBox/Devices/Makefile.kmk (revision 22813) +++ src/VBox/Devices/Makefile.kmk (working copy) @@ -803,7 +803,8 @@ , $(Drivers_SOURCES)) \ Audio/ossaudio.c Drivers_SOURCES.freebsd = \ - Network/DrvTAP.cpp + Network/DrvTAP.cpp \ + Serial/DrvHostSerial.cpp endif # freebsd From pluknet at gmail.com Wed Sep 9 19:25:52 2009 From: pluknet at gmail.com (pluknet) Date: Wed Sep 9 19:26:42 2009 Subject: acquiring duplicate lock of same type: "ftlk" In-Reply-To: <200909091455.42039.jhb@freebsd.org> References: <3bbf2fe10909080213i588493darf8dd1e1ff768cb0a@mail.gmail.com> <200909091455.42039.jhb@freebsd.org> Message-ID: 2009/9/9 John Baldwin : > On Tuesday 08 September 2009 3:42:13 pm pluknet wrote: >> 2009/9/8 Attilio Rao : >> > 2009/9/8 Kostik Belousov : >> >> On Mon, Sep 07, 2009 at 10:15:48PM +0400, pluknet wrote: >> >>> lock order reversal: >> >>> ?1st 0xc75365b8 pseudofs (pseudofs) @ /usr/src/sys/kern/vfs_lookup.c:497 >> >>> ?2nd 0xc088ea3c allproc (allproc) @ /usr/src/sys/kern/kern_proc.c:292 >> >>> KDB: stack backtrace: >> >>> db_trace_self_wrapper(c07fd8ea,e82148e4,c060a145,c05fac1b,c08008bf,...) >> >>> at db_trace_self_wrapper+0x26 >> >>> kdb_backtrace(c05fac1b,c08008bf,c58eabe8,c58e30d0,e8214940,...) at >> >>> kdb_backtrace+0x29 >> >>> _witness_debugger(c08008bf,c088ea3c,c07f981d,c58e30d0,c07f96f0,...) at >> >>> _witness_debugger+0x25 >> >>> witness_checkorder(c088ea3c,1,c07f96f0,124,0,...) at > witness_checkorder+0x839 >> >>> _sx_slock(c088ea3c,0,c07f96f0,124,c73c4980,...) at _sx_slock+0x85 >> >>> pfind(514,c72ba1a0,4,c07f8d78,c5fe1b40,...) at pfind+0x2f >> >>> pfs_visible(0,0,c07f042d,7c,c7536560,...) at pfs_visible+0x3a >> >>> pfs_lookup(e8214a40,c082715e,c7536560,c7536560,e8214bf8,...) at > pfs_lookup+0x3dd >> >>> VOP_CACHEDLOOKUP_APV(c0843960,e8214a40,e8214bf8,e8214be4,c73c4e80,...) >> >>> at VOP_CACHEDLOOKUP_APV+0xc5 >> >>> vfs_cache_lookup(e8214acc,c08087d0,c0875a00,200000,e8214bcc,...) at >> >>> vfs_cache_lookup+0xd6 >> >>> VOP_LOOKUP_APV(c0843960,e8214acc,e8214bf8,1f1,e8214be4,...) at >> >>> VOP_LOOKUP_APV+0xe5 >> >>> lookup(e8214bcc,c5fd1800,0,c5,c5ef77f8,...) at lookup+0x63b >> >>> namei(e8214bcc,c5c1500d,3f3,e8214c20,c5c1500d,...) at namei+0x57f >> >>> kern_alternate_path(c5fe1b40,c0b4921c,2879f478,0,e8214c74,...) at > kern_alternate >> >>> _path+0x1cd >> >>> linux_emul_convpath(c5fe1b40,2879f478,0,e8214c74,0,...) at >> >>> linux_emul_convpath+0x3c >> >>> linux_open(c5fe1b40,e8214cf8,e8214d18,e8214d1c,c0b4b58c,...) at > linux_open+0x41 >> >>> syscall(e8214d38) at syscall+0x2b4 >> >>> Xint0x80_syscall() at Xint0x80_syscall+0x20 >> >>> --- syscall (5, Linux ELF, linux_open), eip = 0x2889115e, esp = >> >>> 0xbfbfbd1c, ebp = 0xbfbfbd6c --- >> >>> acquiring duplicate lock of same type: "ftlk" >> >>> [...] >> >> >> >> The second LOR actually exposes the right order. It would be interesting >> >> to look up the point where the other order is established. >> > >> > You would manually patch the witness static table with this order and >> > the opposite will show, when happening. >> > >> >> I've patched witness order table, and still no opposite case, >> nor any pseudofs related LORs at all. >> ? ? ? ? { "pseudofs", &lock_class_lockmgr }, >> ? ? ? ? { "allproc", &lock_class_sx }, >> ? ? ? ? { NULL, NULL }, >> >> Seen orders with pseudofs: >> "ufs","pseudofs" >> "pseudofs","allproc" >> "pseudofs","process lock" >> "pseudofs","vnode interlock" >> "pseudofs","struct mount mtx" >> "pseudofs","UMA zone" >> "pseudofs","sleep mtxpool" >> "pseudofs","Name Cache" >> "pseudofs","vnode_free_list" >> "pseudofs","pfs_node" >> "pseudofs","pfs_vncache" >> >> Something else? > > What are the seen orders with "allproc"? > sysctl debug.witness.fullgraph | grep allproc "proctree","allproc" "allproc","allprison" "allproc","process lock" "allproc","user map" "allproc","fdesc" "allproc","filedesc structure" "sysctl lock","allproc" "pseudofs","allproc" Also, if it matters, I saw this LOR today: lock order reversal: 1st 0xc7f01164 ufs (ufs) @ /usr/RELENG_8/src/sys/kern/vfs_mount.c:1054 2nd 0xc7fb5058 pseudofs (pseudofs) @ /usr/RELENG_8/src/sys/fs/pseudofs/pseudofs_vncache.c:193 KDB: stack backtrace: db_trace_self_wrapper(c0c7545b,eab2c850,c08c0f75,c08b1cfb,c0c783a3,...) at db_trace_self_wrapper+0x26 kdb_backtrace(c08b1cfb,c0c783a3,c612fbe8,c61281a0,eab2c8ac,...) at kdb_backtrace+0x29 _witness_debugger(c0c783a3,c7fb5058,c0c679b8,c61281a0,c0c6803f,...) at _witness_debugger+0x25 witness_checkorder(c7fb5058,9,c0c6803f,c1,c7fb5074,...) at witness_checkorder+0x839 __lockmgr_args(c7fb5058,80400,c7fb5074,0,0,...) at __lockmgr_args+0x7a7 vop_stdlock(eab2c9b4,c087030a,c7fb50a8,80400,c7fb5000,...) at vop_stdlock+0x62 VOP_LOCK1_APV(c0d55580,eab2c9b4,c0911dcf,c0d92080,c7fb5000,...) at VOP_LOCK1_APV+0xb5 _vn_lock(c7fb5000,80400,c0c6803f,c1,c0f3339c,...) at _vn_lock+0x5e pfs_vncache_alloc(c6764c94,eab2cc30,c7d1cb00,186a0,eab2cc60,...) at pfs_vncache_alloc+0x232 pfs_root(c6764c94,80000,eab2cc30,42c,0,...) at pfs_root+0x2d vfs_donmount(c7ba76c0,0,c6b66500,c6b66500,bfbfdc89,...) at vfs_donmount+0x14c2 nmount(c7ba76c0,eab2ccf8,c,c7ba76c0,c0d5a638,...) at nmount+0x75 syscall(eab2cd38) at syscall+0x2a3 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (378, FreeBSD ELF32, nmount), eip = 0x280e876b, esp = 0xbfbfdc5c, ebp = 0xbfbfe1b8 --- -- wbr, pluknet From Alexander.Eichner at Sun.COM Wed Sep 9 19:32:20 2009 From: Alexander.Eichner at Sun.COM (Alexander Eichner) Date: Wed Sep 9 19:32:27 2009 Subject: [vbox-dev] VirtualBox network patches for FreeBSD (vboxnetflt + vboxnetadp) In-Reply-To: <4AA7AE3B.9050705@shapeshifter.se> References: <4AA784D9.80405@shapeshifter.se> <4AA7AE3B.9050705@shapeshifter.se> Message-ID: <1252524723.6080.2.camel@Prometheus> Hi Fredrik, thanks a lot for these patches. You did a great job. Everything works without problems here so far. I committed the patches to our repository with minor modifications (mostly coding style :) ). It should appear in our public svn soon. Thanks again. Regards, Alexander Eichner Am Mittwoch, den 09.09.2009, 15:31 +0200 schrieb Fredrik Lindberg: > Danny Braniss wrote: > > > > great work! > > any chance it will support PXE? > > what about throughput, at the moment iperf timet it at 120Mbits/sec > > but the host is connected at 1G. > > > > danny > > > > It supports PXE. However the OSE version of VirtualBox does only have > PXE booting on the PCnet interfaces not the Intel ones. > Also, if you're going to boot a FreeBSD kernel you'll need to patch > the etherboot code in virtualbox, otherwise it will abort with > "Unable to load file". > I don't know whether it's FreeBSDs pxeboot or etherboot that is the > offender here. > > See, for more info > http://lists.freebsd.org/pipermail/freebsd-emulation/2007-April/003503.html > > > Throughput is not something I have actively looked at, there might be > something that can be optimized regarding mbuf to SG-convertion. > One source is most likely due to its dependency on the netgraph > system which causes an additional packet detour. > It uses netgraph because it's the only reliable way to hook > into the input/output path of ethernet interfaces, and > that also works properly on FreeBSD 7 and higher. > > Fredrik > > _______________________________________________ > vbox-dev mailing list > vbox-dev@virtualbox.org > http://vbox.innotek.de/mailman/listinfo/vbox-dev From jhb at freebsd.org Wed Sep 9 19:41:04 2009 From: jhb at freebsd.org (John Baldwin) Date: Wed Sep 9 19:41:33 2009 Subject: acquiring duplicate lock of same type: "ftlk" In-Reply-To: References: <200909091455.42039.jhb@freebsd.org> Message-ID: <200909091540.57890.jhb@freebsd.org> On Wednesday 09 September 2009 3:25:50 pm pluknet wrote: > 2009/9/9 John Baldwin : > > On Tuesday 08 September 2009 3:42:13 pm pluknet wrote: > >> 2009/9/8 Attilio Rao : > >> > 2009/9/8 Kostik Belousov : > >> >> On Mon, Sep 07, 2009 at 10:15:48PM +0400, pluknet wrote: > >> >>> lock order reversal: > >> >>> ?1st 0xc75365b8 pseudofs (pseudofs) @ /usr/src/sys/kern/vfs_lookup.c:497 > >> >>> ?2nd 0xc088ea3c allproc (allproc) @ /usr/src/sys/kern/kern_proc.c:292 > >> >>> KDB: stack backtrace: > >> >>> db_trace_self_wrapper(c07fd8ea,e82148e4,c060a145,c05fac1b,c08008bf,...) > >> >>> at db_trace_self_wrapper+0x26 > >> >>> kdb_backtrace(c05fac1b,c08008bf,c58eabe8,c58e30d0,e8214940,...) at > >> >>> kdb_backtrace+0x29 > >> >>> _witness_debugger(c08008bf,c088ea3c,c07f981d,c58e30d0,c07f96f0,...) at > >> >>> _witness_debugger+0x25 > >> >>> witness_checkorder(c088ea3c,1,c07f96f0,124,0,...) at > > witness_checkorder+0x839 > >> >>> _sx_slock(c088ea3c,0,c07f96f0,124,c73c4980,...) at _sx_slock+0x85 > >> >>> pfind(514,c72ba1a0,4,c07f8d78,c5fe1b40,...) at pfind+0x2f > >> >>> pfs_visible(0,0,c07f042d,7c,c7536560,...) at pfs_visible+0x3a > >> >>> pfs_lookup(e8214a40,c082715e,c7536560,c7536560,e8214bf8,...) at > > pfs_lookup+0x3dd > >> >>> VOP_CACHEDLOOKUP_APV(c0843960,e8214a40,e8214bf8,e8214be4,c73c4e80,...) > >> >>> at VOP_CACHEDLOOKUP_APV+0xc5 > >> >>> vfs_cache_lookup(e8214acc,c08087d0,c0875a00,200000,e8214bcc,...) at > >> >>> vfs_cache_lookup+0xd6 > >> >>> VOP_LOOKUP_APV(c0843960,e8214acc,e8214bf8,1f1,e8214be4,...) at > >> >>> VOP_LOOKUP_APV+0xe5 > >> >>> lookup(e8214bcc,c5fd1800,0,c5,c5ef77f8,...) at lookup+0x63b > >> >>> namei(e8214bcc,c5c1500d,3f3,e8214c20,c5c1500d,...) at namei+0x57f > >> >>> kern_alternate_path(c5fe1b40,c0b4921c,2879f478,0,e8214c74,...) at > > kern_alternate > >> >>> _path+0x1cd > >> >>> linux_emul_convpath(c5fe1b40,2879f478,0,e8214c74,0,...) at > >> >>> linux_emul_convpath+0x3c > >> >>> linux_open(c5fe1b40,e8214cf8,e8214d18,e8214d1c,c0b4b58c,...) at > > linux_open+0x41 > >> >>> syscall(e8214d38) at syscall+0x2b4 > >> >>> Xint0x80_syscall() at Xint0x80_syscall+0x20 > >> >>> --- syscall (5, Linux ELF, linux_open), eip = 0x2889115e, esp = > >> >>> 0xbfbfbd1c, ebp = 0xbfbfbd6c --- > >> >>> acquiring duplicate lock of same type: "ftlk" > >> >>> [...] > >> >> > >> >> The second LOR actually exposes the right order. It would be interesting > >> >> to look up the point where the other order is established. > >> > > >> > You would manually patch the witness static table with this order and > >> > the opposite will show, when happening. > >> > > >> > >> I've patched witness order table, and still no opposite case, > >> nor any pseudofs related LORs at all. > >> ? ? ? ? { "pseudofs", &lock_class_lockmgr }, > >> ? ? ? ? { "allproc", &lock_class_sx }, > >> ? ? ? ? { NULL, NULL }, > >> > >> Seen orders with pseudofs: > >> "ufs","pseudofs" > >> "pseudofs","allproc" > >> "pseudofs","process lock" > >> "pseudofs","vnode interlock" > >> "pseudofs","struct mount mtx" > >> "pseudofs","UMA zone" > >> "pseudofs","sleep mtxpool" > >> "pseudofs","Name Cache" > >> "pseudofs","vnode_free_list" > >> "pseudofs","pfs_node" > >> "pseudofs","pfs_vncache" > >> > >> Something else? > > > > What are the seen orders with "allproc"? > > > > sysctl debug.witness.fullgraph | grep allproc > "proctree","allproc" > "allproc","allprison" > "allproc","process lock" > "allproc","user map" > "allproc","fdesc" > "allproc","filedesc structure" > "sysctl lock","allproc" > "pseudofs","allproc" Ok, there is probably an order of "allproc" -> "filedesc" -> "ufs" -> "psuedofs". There might even be a "filedesc" -> "psuedofs" that could cause this. > Also, if it matters, I saw this LOR today: > > lock order reversal: > 1st 0xc7f01164 ufs (ufs) @ /usr/RELENG_8/src/sys/kern/vfs_mount.c:1054 > 2nd 0xc7fb5058 pseudofs (pseudofs) @ > /usr/RELENG_8/src/sys/fs/pseudofs/pseudofs_vncache.c:193 I think this backs up my theory. I think the LOR is probably harmless, but there's not an easy way to shut it up I believe. -- John Baldwin From Alexander.Eichner at Sun.COM Wed Sep 9 20:12:38 2009 From: Alexander.Eichner at Sun.COM (Alexander Eichner) Date: Wed Sep 9 20:12:45 2009 Subject: [vbox-dev] Enable DrvHostSerial on FreeBSD In-Reply-To: <4AA800DF.2090904@shapeshifter.se> References: <4AA800DF.2090904@shapeshifter.se> Message-ID: <1252527149.6080.4.camel@Prometheus> Hi, already committed before I got your mail. But good to know that nothing special is required to get this working because I couldn't test it here :) Regards, Alexander Eichner Am Mittwoch, den 09.09.2009, 21:24 +0200 schrieb Fredrik Lindberg: > The existing code for the host serial device (DrvHostSerial.cpp) > works on FreeBSD, it's just disabled by ifdefs. > > Attached is a patch to enable it, MIT license or whatever you want. > Compile-tested on FreeBSD 7 and 8, runtime tested on FreeBSD 8. > > I've tested it with a cross-over serial cable (null modem) connected > between two (physical) machines. Used cu and minicom inside guest > to connect to another cu/minicom-instance running on the second > machine. > My testing has been limited to this as I really don't have any other > fancy serial equipment :) > > Notes to people trying this with the ports version, the patch > does not apply cleanly and you'll have to modify > src/VBox/Devices/Makefile.kmk by hand. > > Fredrik From oberman at es.net Wed Sep 9 22:32:20 2009 From: oberman at es.net (Kevin Oberman) Date: Wed Sep 9 22:32:26 2009 Subject: Shared folders with Window 7 Ultimate Release Message-ID: <20090909223218.BF9271CC39@ptavv.es.net> I have installed VB on my laptop and installed the RTM of Windows7. It went very smoothly! I have now added Office and Visio, but I have run into a major problem...shared folders (or the lack of them). I installed the guest additions. Since no 3.0.51 set was available, I used 3.0.6. Then I set up a folder as shared. It shows up in the bar at the bottom of the VB window, but I have been unable to map it or access it in Windows. I have opened the network and the only things there are my computer and "media devices". No VirtualBox share. If I "Map Network Drive" and click "Browse", I also don't see the VB share folder. Am I missing something or is there a problem with shared folders on Windows 7 Release? (I searched the list archives and found nothing on this. I apologize if I missed it.) -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 From danny at cs.huji.ac.il Thu Sep 10 06:44:10 2009 From: danny at cs.huji.ac.il (Daniel Braniss) Date: Thu Sep 10 06:44:16 2009 Subject: vbox & network boot(pxe) Message-ID: Hi, The etherboot/pxe code works only if all the servers involved are the same, or in simple english, only one server :-) I can try and fix this, but even after my morning coffee, I'm at lost in trying to compile it, pcnet32.zrom is distributed in binary. Any hint would be greatly appreciated, danny From bsam at ipt.ru Thu Sep 10 06:47:47 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Thu Sep 10 06:47:54 2009 Subject: linux GL libraries and nvidia drivers (was: Re: deprecate some linux ports) In-Reply-To: (Alexander Best's message of "Wed, 09 Sep 2009 18:40:08 +0200 (CEST)") References: Message-ID: <90953406@bb.ipt.ru> On Wed, 09 Sep 2009 18:40:08 +0200 (CEST) Alexander Best wrote: > seems like a good idea. especially for people new to freebsd the different > linux base versions are confusing. > the only linux-f8-* port i'm running atm is graphics/linux-f8-libGLU since > there's no linux-f10-libGLU port available. using graphics/linux-f10-dri > instead isn't an option for me since the port shares some files with the > nvidia freebsd binary graphic drivers. Which dri graphics port are you using now? Seems that it already has some shared files with nvidia driver. The default for -f10- ports is linux-dri74. But it has just the same pkg-plist as linux-f10-dri. BTW, I can create a linux-f10-libGLU port if it is needed. But I'm not sure if it is needed. If I understand the problem with nvidia driver correctly it installs (and uses) its own linux libGL.so. Hence the problem is not with libGLU.so but with libGL.so. Correct me if I'm wrong. What if I create a new (say) linux--libGL port with only libGL libraries and remove them from linux--dri port? The latter will depend on linux--libGL port. In other words: . create a new linux-libGL74 with libGL libraries; . remove libGL libraries from linux-dri74 and add a dependecy upon the new linux-libGL74 port. Note: I use a "74" suffix here because I've taken those libraries from a Ubuntu distribution which had drivers for xorg-7.4. -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From bsam at ipt.ru Thu Sep 10 07:33:25 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Thu Sep 10 07:33:31 2009 Subject: linux GL libraries and nvidia drivers In-Reply-To: <90953406@bb.ipt.ru> (Boris Samorodov's message of "Thu, 10 Sep 2009 10:47:45 +0400") References: <90953406@bb.ipt.ru> Message-ID: <08875131@bb.ipt.ru> On Thu, 10 Sep 2009 10:47:45 +0400 Boris Samorodov wrote: > BTW, I can create a linux-f10-libGLU port if it is needed. But I'm > not sure if it is needed. After a better look at ports which use nvidia drivers I stand corrected. Seems that the best way is to create a new linux libGLU port and patch bsd.linux-apps.mk. Then ports which use nvidia drivers should use a patch like: ----- --- Makefile.orig 2009-06-07 19:23:52.000000000 +0400 +++ Makefile 2009-09-10 11:26:00.000000000 +0400 @@ -31,8 +31,8 @@ .include .if defined(WITH_NVIDIA) -RUN_DEPENDS+= ${LINUXBASE}/usr/lib/libGL.so.1:${PORTSDIR}/x11/nvidia-driver \ - ${LINUXBASE}/usr/X11R6/lib/libGLU.so.1:${PORTSDIR}/graphics/linux-libGLU +RUN_DEPENDS+= ${LINUXBASE}/usr/lib/libGL.so.1:${PORTSDIR}/x11/nvidia-driver +USE_LINUX_APPS+=libGLU .else USE_LINUX_APPS+=dri .endif ----- -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From edwin at FreeBSD.org Thu Sep 10 08:10:14 2009 From: edwin at FreeBSD.org (edwin@FreeBSD.org) Date: Thu Sep 10 08:10:22 2009 Subject: ports/138697: [repocopy] graphics/linux-f8-libGLU -> graphics/linux-f10-libGLU Message-ID: <200909100810.n8A8AERf023567@freefall.freebsd.org> Synopsis: [repocopy] graphics/linux-f8-libGLU -> graphics/linux-f10-libGLU Responsible-Changed-From-To: freebsd-ports-bugs->emulation Responsible-Changed-By: edwin Responsible-Changed-When: Thu Sep 10 08:10:13 UTC 2009 Responsible-Changed-Why: Over to maintainer (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=138697 From alexbestms at math.uni-muenster.de Thu Sep 10 08:21:02 2009 From: alexbestms at math.uni-muenster.de (Alexander Best) Date: Thu Sep 10 08:21:09 2009 Subject: linux GL libraries and nvidia drivers (was: Re: deprecate some linux ports) Message-ID: i'm not running any linux-dri* port at all since all of them come with their own libGL which i don't need because the nvidia driver provides that library. all i need is libGLU.so (linux version) because the nvidia driver doesn't supply that library. funny thing is that only the linux-dri* ports come with libGL.so. the native dri-* port doesn't include libGL.so and thus isn't colliding with the nvidia drivers. your suggestion sounds good. if i understood you correctly you want to change the ports like this: - have a linux_dri port without libGL* - create a linux_libGL port - remove the linux-libGLU* ports it would be nice if the linux_dri would feature some options which let's you chose which files you want to have installed. i personally don't need the Xorg modules or the binaries which come with the port. only libGLU.so. so how about the following options: xorg graphic card modules libglut libglade libexpat libdrm libGLU binaries cheers. From bsam at FreeBSD.org Thu Sep 10 08:31:18 2009 From: bsam at FreeBSD.org (bsam@FreeBSD.org) Date: Thu Sep 10 08:31:25 2009 Subject: ports/138697: [repocopy] graphics/linux-f8-libGLU -> graphics/linux-f10-libGLU Message-ID: <200909100831.n8A8VIHV055308@freefall.freebsd.org> Synopsis: [repocopy] graphics/linux-f8-libGLU -> graphics/linux-f10-libGLU State-Changed-From-To: open->repocopy State-Changed-By: bsam State-Changed-When: Thu Sep 10 08:29:50 UTC 2009 State-Changed-Why: Repocopy is a portmgr territory. Responsible-Changed-From-To: emulation->portmgr Responsible-Changed-By: bsam Responsible-Changed-When: Thu Sep 10 08:29:50 UTC 2009 Responsible-Changed-Why: Repocopy is a portmgr territory. http://www.freebsd.org/cgi/query-pr.cgi?pr=138697 From gary.jennejohn at freenet.de Thu Sep 10 09:13:02 2009 From: gary.jennejohn at freenet.de (Gary Jennejohn) Date: Thu Sep 10 09:13:09 2009 Subject: Shared folders with Window 7 Ultimate Release In-Reply-To: <20090909223218.BF9271CC39@ptavv.es.net> References: <20090909223218.BF9271CC39@ptavv.es.net> Message-ID: <20090910111259.501db589@ernst.jennejohn.org> On Wed, 09 Sep 2009 15:32:18 -0700 "Kevin Oberman" wrote: [snip tales of woe] > Am I missing something or is there a problem with shared folders on > Windows 7 Release? > > (I searched the list archives and found nothing on this. I apologize if > I missed it.) > Works for me. In the explorer click on Map network drive and enter \\vboxsvr\share-name into the appropriate box in the popup. You should consider downloading the VirtualBopx documentation fron SUN. Everything is explained in it. --- Gary Jennejohn From bsam at ipt.ru Thu Sep 10 09:39:40 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Thu Sep 10 09:39:46 2009 Subject: linux GL libraries and nvidia drivers In-Reply-To: (Alexander Best's message of "Thu, 10 Sep 2009 10:20:57 +0200 (CEST)") References: Message-ID: <32077556@bb.ipt.ru> On Thu, 10 Sep 2009 10:20:57 +0200 (CEST) Alexander Best wrote: > i'm not running any linux-dri* port at all since all of them come with their > own libGL which i don't need because the nvidia driver provides that library. > all i need is libGLU.so (linux version) because the nvidia driver doesn't > supply that library. OK. That was my misunderstanding. I thought that nvidia driver uses its own libGL but needs other dri-* stuff. I have a look at some ports which use nvidia driver and understand that nvidia driver needs _only_ libGLU (better to say that those applications need only libGLU along with nvidia driver). That's why I changed my mind about linux libGLU port. It will be created. > funny thing is that only the linux-dri* ports come with libGL.so. the native > dri-* port doesn't include libGL.so and thus isn't colliding with the nvidia > drivers. Someone with better (then mine) uderstanding of dri* and GL* may inverstigate current ports infrastructure and give a suggestion on a better structure. > your suggestion sounds good. if i understood you correctly you want to change > the ports like this: > - have a linux_dri port without libGL* > - create a linux_libGL port > - remove the linux-libGLU* ports At least for now (before FreeBSD-8.0 release) I'll leave it as is. With one exception: a new linux-f10-libGLU port (with apropriate infrastructure) will be added. > it would be nice if the linux_dri would feature some options which let's you > chose which files you want to have installed. i personally don't need the Xorg > modules or the binaries which come with the port. only libGLU.so. > so how about the following options: > xorg graphic card modules > libglut > libglade > libexpat > libdrm > libGLU > binaries Good suggestion but I have no much time to do it. -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From fli at shapeshifter.se Thu Sep 10 10:53:39 2009 From: fli at shapeshifter.se (Fredrik Lindberg) Date: Thu Sep 10 10:53:44 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 6 In-Reply-To: <5effc292d4e1b51c1b33e8a1f987ccbc.squirrel@webmail.itac.at> References: <20090611194557.GC98175@bsdcrew.de> <991123400909060811u9bea4d9rdbf453dfaae7c185@mail.gmail.com> <20090906162544.GA39448@bsdcrew.de> <50e4b96fb035ba5eaf5e30fbf12bf9f2.squirrel@webmail.itac.at> <367b2c980909071048j79b28babwcc9d59488d1de3ef@mail.gmail.com> <5effc292d4e1b51c1b33e8a1f987ccbc.squirrel@webmail.itac.at> Message-ID: <4AA8DAAF.3010507@shapeshifter.se> Bernhard Fr?hlich wrote: > On Tue, September 8, 2009 12:00 pm, Boris wrote: >> Hi Bernhard, >> >> I confirm VT-x is now working. It used to fail on my system with previous >> release from the time I launched the VM. > > Good to hear that! Thanks for testing it. > >> I am using amd64-8-BETA4 and rev 456. >> I have experienced a crash of the VM in the middle of the installation of >> a >> Debian64 so I will try again and report if it's reproducible. I used an >> existing virtual disk so I'll try again from scratch. > > I've seen something similar but haven't found out yet where the problem is. > >> Could you confirm if the patch from Fredrik Lindberg is going to be >> integrate to a next revision before port freeze? >> >> http://lists.freebsd.org/pipermail/freebsd-emulation/2009-September/006740.html > > The short answer is no. That patch will not be included in the vbox update. > > We try to stay as close to the official code as possible and instead send > all patches upstream to get them included. So if that patch is stable it > should be send to vbox-dev@ and i'm sure aeichner will be glad to have a > look at it. I will talk to Fredrik if we can help in any way. > > The network patches have been included in the upstream VirtualBox source as of revision 22899. Fredrik From alexbestms at math.uni-muenster.de Thu Sep 10 12:13:27 2009 From: alexbestms at math.uni-muenster.de (Alexander Best) Date: Thu Sep 10 12:13:34 2009 Subject: linux GL libraries and nvidia drivers Message-ID: thanks a lot for the linux-f10-libGLU port. no need to hurry. the other changes discussed aren't critical. cheers. alex From decke at bluelife.at Thu Sep 10 13:27:03 2009 From: decke at bluelife.at (Bernhard Froehlich) Date: Thu Sep 10 13:27:09 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 6 In-Reply-To: <4AA8DAAF.3010507@shapeshifter.se> References: <20090611194557.GC98175@bsdcrew.de> <991123400909060811u9bea4d9rdbf453dfaae7c185@mail.gmail.com> <20090906162544.GA39448@bsdcrew.de> <50e4b96fb035ba5eaf5e30fbf12bf9f2.squirrel@webmail.itac.at> <367b2c980909071048j79b28babwcc9d59488d1de3ef@mail.gmail.com> <5effc292d4e1b51c1b33e8a1f987ccbc.squirrel@webmail.itac.at> <4AA8DAAF.3010507@shapeshifter.se> Message-ID: On Thu, September 10, 2009 12:53 pm, Fredrik Lindberg wrote: > Bernhard Fr?hlich wrote: >> On Tue, September 8, 2009 12:00 pm, Boris wrote: >>> Hi Bernhard, >>> >>> I confirm VT-x is now working. It used to fail on my system with >>> previous >>> release from the time I launched the VM. >> >> Good to hear that! Thanks for testing it. >> >>> I am using amd64-8-BETA4 and rev 456. >>> I have experienced a crash of the VM in the middle of the installation >>> of >>> a >>> Debian64 so I will try again and report if it's reproducible. I used an >>> existing virtual disk so I'll try again from scratch. >> >> I've seen something similar but haven't found out yet where the problem >> is. >> >>> Could you confirm if the patch from Fredrik Lindberg is going to be >>> integrate to a next revision before port freeze? >>> >>> http://lists.freebsd.org/pipermail/freebsd-emulation/2009-September/006740.html >> >> The short answer is no. That patch will not be included in the vbox >> update. >> >> We try to stay as close to the official code as possible and instead >> send >> all patches upstream to get them included. So if that patch is stable it >> should be send to vbox-dev@ and i'm sure aeichner will be glad to have a >> look at it. I will talk to Fredrik if we can help in any way. >> >> > > The network patches have been included in the upstream VirtualBox source > as of revision 22899. Yes, we've seen that. Thanks again for your work and for sending it upstream. Inclusion within one day is really fast :o) We plan to update the FreeBSD port today with r22683 which will then be shipped with 8.0. After that we will update our svn port to the latest code so people can start testing it. -- Bernhard Fr?hlich http://www.bluelife.at/ From mailing at ekomedya.com Thu Sep 10 15:18:28 2009 From: mailing at ekomedya.com (=?utf-8?Q?Eko_Bilgisayar_ve_=C4=B0leti=C5=9Fim_Hizmetleri_Ltd=2E_=C5=9Eti?=) Date: Thu Sep 10 15:18:40 2009 Subject: Turkey Calling You To Visit - The Trade SHOW- In Las Vegas Message-ID: <66a0eb9ea92a2d0d7f4f9f08a9a5048b@localhost.localdomain> [http://www.turkeycalling.us] [http://www.turkeycalling.us] [http://www.turkeycalling.us] [http://www.turkeycalling.us/turkey-fam/turkeyfam.htm] Global Access Travel invites you to the Tradeshow in Las Vegas on September 13-15, 2009. Please visit us to get more information about our organization and services at our booth. If you fill the registration form or leave the business card when you visit us at our booth, you might be lucky visitor who is going to win our daily draw prize; Free inspection trip to Turkey. Yasal Uyar?; Bu e-posta, sadece adreste belirtilen kisi veya kurulusun kullanimini hedeflemekte olup,mesajda yer alan bilgiler kisiye ozel ve gizli olabilir, yasalar ya da anlasmalar geregi ?c?nc? kisiler ile paylasilmasi m?mk?n olmayabilir.Mesaji alan kisi, mesajin g?nderilmek istendigi kisi veya kurulus degilse,bu mesaji yaymak,dagitmak veya kopyalamak yasaktir Mesaj tarafiniza yanlislikla ulasmissa l?tfen mesaji geri g?nderiniz ve sisteminizden siliniz. Global Access Travel bu mesajin icerigi ile ilgili olarak hicbir hukuksal sorumlulugu kabul etmez Disclaimer This e-mail communication is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and that may not be made public by law or agreement. If the recipient of this message is not the intended recipient or entity, you are hereby notified that any further dissemination, distribution or copying of this information is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete it from your system. The Global Access Traveldoes not accept legal responsibility for the contents of this message. Yasal Uyar?; Bu e-posta, sadece adreste belirtilen kisi veya kurulusun kullanimini hedeflemekte olup,mesajda yer alan bilgiler kisiye ozel ve gizli olabilir, yasalar ya da anlasmalar geregi ?c?nc? kisiler ile paylasilmasi m?mk?n olmayabilir.Mesaji alan kisi, mesajin g?nderilmek istendigi kisi veya kurulus degilse,bu mesaji yaymak,dagitmak veya kopyalamak yasaktir Mesaj tarafiniza yanlislikla ulasmissa l?tfen mesaji geri g?nderiniz ve sisteminizden siliniz. Global Access Travel bu mesajin icerigi ile ilgili olarak hicbir hukuksal sorumlulugu kabul etmez Disclaimer This e-mail communication is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and that may not be made public by law or agreement. If the recipient of this message is not the intended recipient or entity, you are hereby notified that any further dissemination, distribution or copying of this information is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete it from your system. The Global Access Traveldoes not accept legal responsibility for the contents of this message. Yasal Uyar?; Bu e-posta, sadece adreste belirtilen kisi veya kurulusun kullanimini hedeflemekte olup,mesajda yer alan bilgiler kisiye ozel ve gizli olabilir, yasalar ya da anlasmalar geregi ?c?nc? kisiler ile paylasilmasi m?mk?n olmayabilir.Mesaji alan kisi, mesajin g?nderilmek istendigi kisi veya kurulus degilse,bu mesaji yaymak,dagitmak veya kopyalamak yasaktir Mesaj tarafiniza yanlislikla ulasmissa l?tfen mesaji geri g?nderiniz ve sisteminizden siliniz. Global Access Travel bu mesajin icerigi ile ilgili olarak hicbir hukuksal sorumlulugu kabul etmez Disclaimer This e-mail communication is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and that may not be made public by law or agreement. If the recipient of this message is not the intended recipient or entity, you are hereby notified that any further dissemination, distribution or copying of this information is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete it from your system. The Global Access Traveldoes not accept legal responsibility for the contents of this message. This message was sent by: TURKEY CALLING YOU TO VISIT "THE TRADE SHOW" IN LAS VEGAS, N?zhetiye Cad, istanbul, Besiktas 34357, Turkey Manage your subscription: http://app.icontact.com/icp/mmail-mprofile.pl?r=47622548&l=82253&s=5CJA&m=587775&c=305227 From oberman at es.net Thu Sep 10 17:32:43 2009 From: oberman at es.net (Kevin Oberman) Date: Thu Sep 10 17:32:50 2009 Subject: Shared folders with Window 7 Ultimate Release In-Reply-To: Your message of "Thu, 10 Sep 2009 11:12:59 +0200." <20090910111259.501db589@ernst.jennejohn.org> Message-ID: <20090910173240.669491CC39@ptavv.es.net> > Date: Thu, 10 Sep 2009 11:12:59 +0200 > From: Gary Jennejohn > > On Wed, 09 Sep 2009 15:32:18 -0700 > "Kevin Oberman" wrote: > > [snip tales of woe] > > Am I missing something or is there a problem with shared folders on > > Windows 7 Release? > > > > (I searched the list archives and found nothing on this. I apologize if > > I missed it.) > > > > Works for me. > > In the explorer click on Map network drive and enter \\vboxsvr\share-name > into the appropriate box in the popup. > > You should consider downloading the VirtualBopx documentation fron SUN. > Everything is explained in it. Thanks, Gary. First, I have downloaded the VirtualBox User Manual 3.0.4 and read it (or at least the relevant chapters) before installing VB, Windows 7, or the User Additions. But vboxsvr was not one of the options listed. After reading your response and re-reading the sub-chapter I realized that I should not assume that vboxsvr would show up and I did as you suggested. (What a strange thing to do.) Worked like a champ. My share is now available. Thanks so much for dragging me to the obvious destination. It's great. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 From ivoras at freebsd.org Fri Sep 11 14:07:30 2009 From: ivoras at freebsd.org (Ivan Voras) Date: Fri Sep 11 14:07:37 2009 Subject: New Virtualbox port (from today) Message-ID: Hi, VirtualBox now works with VT and I'm able to run SMP guests! But apparently it's not very stable (got two boot crashes) and something is wrong with timers: Example 1: host HZ=250, guest HZ=1000, - guest time apparently speeds up more than it should Example 2: same host, guest HZ=100 - guest time apparently goes 5x slower than real (wall) time. Example 3: same host, guest HZ=25, guest time apparently 2x slower than real (wall) time. In the examples, host is amd64 8-BETA2, 4CPU, guest is 7.2-RELEASE i386, 2CPU. Internally the time is always consistent - for example in the second case "time sleep 2" says the guest slept 2 seconds, while in real time, 10 seconds have passed. Time apparently goes normal when the guest is configured with only one CPU (and VT is still active). From matheus at eternamente.info Fri Sep 11 22:10:06 2009 From: matheus at eternamente.info (Nenhum_de_Nos) Date: Fri Sep 11 22:10:12 2009 Subject: New Virtualbox port (from today) In-Reply-To: References: Message-ID: On Fri, September 11, 2009 11:07, Ivan Voras wrote: > Hi, > > VirtualBox now works with VT and I'm able to run SMP guests! > > But apparently it's not very stable (got two boot crashes) and something > is wrong with timers: in my testes, I never got so far as a boot when using any 8.x > Example 1: host HZ=250, guest HZ=1000, - guest time apparently speeds up > more than it should > > Example 2: same host, guest HZ=100 - guest time apparently goes 5x > slower than real (wall) time. > > Example 3: same host, guest HZ=25, guest time apparently 2x slower than > real (wall) time. > > In the examples, host is amd64 8-BETA2, 4CPU, guest is 7.2-RELEASE i386, > 2CPU. I tried on a quite close system. intel or amd yours ? maybe its time to try again. my system was built from scratch. any particular tip ? matheus > Internally the time is always consistent - for example in the second > case "time sleep 2" says the guest slept 2 seconds, while in real time, > 10 seconds have passed. > > Time apparently goes normal when the guest is configured with only one > CPU (and VT is still active). > > _______________________________________________ > freebsd-emulation@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-emulation > To unsubscribe, send any mail to > "freebsd-emulation-unsubscribe@freebsd.org" > -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style From herbszt at gmx.de Fri Sep 11 22:34:53 2009 From: herbszt at gmx.de (Sebastian Herbszt) Date: Fri Sep 11 22:35:00 2009 Subject: experimental FreeBSD qemu-devel git head port update for testing In-Reply-To: <20090904193435.GA77708@triton8.kn-bremen.de> References: <20090829222339.GA93608@triton8.kn-bremen.de><20090902175621.GA63905@triton8.kn-bremen.de> <20090904193435.GA77708@triton8.kn-bremen.de> Message-ID: <2E5888455DA643CEB3960168C1AAB4E0@FSCPC> Juergen Lock wrote: > On Wed, Sep 02, 2009 at 07:56:21PM +0200, Juergen Lock wrote: >> On Sun, Aug 30, 2009 at 12:23:39AM +0200, Juergen Lock wrote: >> > Also the pcap patch stopped working in this snapshot and I don't yet >> > know why. (I think the original version of that patch was submitted by >> > Jung-uk Kim, maybe he has an idea; Cc'd.) >> > [...] >> >> Jung-uk Kim sent me a new pcap patch (thanx! :), and I have just included >> it in the mentioned update at >> http://people.freebsd.org/~nox/qemu/qemu-devel-20090829.patch > > New update at the same place, Jung-uk Kim sent me another version of the > pcap patch configure changes the LIBS variable (LIBS="$libpcap $LIBS"), which is not only used for the qemu binary, but also for qemu-nbd, qemu-io and qemu-img. Linking those with libpcap should not be required. Consider changing LIBS="$libpcap $LIBS" to libs_softmmu="$libpcap $libs_softmmu" which seems to fix this. - Sebastian From borisbsd at googlemail.com Fri Sep 11 22:45:50 2009 From: borisbsd at googlemail.com (Boris) Date: Fri Sep 11 22:45:56 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 6 In-Reply-To: References: <20090611194557.GC98175@bsdcrew.de> <20090906162544.GA39448@bsdcrew.de> <50e4b96fb035ba5eaf5e30fbf12bf9f2.squirrel@webmail.itac.at> <367b2c980909071048j79b28babwcc9d59488d1de3ef@mail.gmail.com> <5effc292d4e1b51c1b33e8a1f987ccbc.squirrel@webmail.itac.at> <4AA8DAAF.3010507@shapeshifter.se> Message-ID: Thanks all I got the latest revision (461) from your repository Bernhard and Fredrik's feature compiles correctly. I got a Debian64 VM with 4GB running on BETA4 amd64 with bridge interface working well. I just got a problem after installing the VBoxGuestAdditions-amd64. I rebooted, got on login screen (graphical) in the VM, issued user/pass and the VM aborts. As I noticed VBoxGuestAdditions-amd64 require 2.6.27 and I am running 2.6.26-2, I will align. VBoxGuestAdditions-amd64 installed successfully on 2.6.26-2 though. I will let you know if I still get the same behaviour after Linux kernel upgrade in the VM. Anyway I think I will go for proper CLI access now it is reachable through the bridged interface :-) Thanks again for all contributors ! Boris On Thu, Sep 10, 2009 at 2:26 PM, Bernhard Froehlich wrote: > On Thu, September 10, 2009 12:53 pm, Fredrik Lindberg wrote: > > Bernhard Fr?hlich wrote: > >> On Tue, September 8, 2009 12:00 pm, Boris wrote: > >>> Hi Bernhard, > >>> > >>> I confirm VT-x is now working. It used to fail on my system with > >>> previous > >>> release from the time I launched the VM. > >> > >> Good to hear that! Thanks for testing it. > >> > >>> I am using amd64-8-BETA4 and rev 456. > >>> I have experienced a crash of the VM in the middle of the installation > >>> of > >>> a > >>> Debian64 so I will try again and report if it's reproducible. I used an > >>> existing virtual disk so I'll try again from scratch. > >> > >> I've seen something similar but haven't found out yet where the problem > >> is. > >> > >>> Could you confirm if the patch from Fredrik Lindberg is going to be > >>> integrate to a next revision before port freeze? > >>> > >>> > http://lists.freebsd.org/pipermail/freebsd-emulation/2009-September/006740.html > >> > >> The short answer is no. That patch will not be included in the vbox > >> update. > >> > >> We try to stay as close to the official code as possible and instead > >> send > >> all patches upstream to get them included. So if that patch is stable it > >> should be send to vbox-dev@ and i'm sure aeichner will be glad to have > a > >> look at it. I will talk to Fredrik if we can help in any way. > >> > >> > > > > The network patches have been included in the upstream VirtualBox source > > as of revision 22899. > > Yes, we've seen that. Thanks again for your work and for sending it > upstream. Inclusion within one day is really fast :o) > > We plan to update the FreeBSD port today with r22683 which will then be > shipped with 8.0. After that we will update our svn port to the latest > code so people can start testing it. > > -- > Bernhard Fr?hlich > http://www.bluelife.at/ > > From avg at icyb.net.ua Sat Sep 12 09:51:32 2009 From: avg at icyb.net.ua (Andriy Gapon) Date: Sat Sep 12 09:51:39 2009 Subject: virtualbox 3.0.51r22226: some quirks In-Reply-To: <4A9E85C1.1090605@icyb.net.ua> References: <4A9E85C1.1090605@icyb.net.ua> Message-ID: <4AAB6F20.8000202@icyb.net.ua> on 02/09/2009 17:48 Andriy Gapon said the following: > Just to check if the following issues are mine local or if they are known ones. So, I upgraded to virtualbox-3.0.51.r22683. Updates: > 1. Host+Del combination doesn't sent Ctrl+Alt+Del to a guest, this used to work > correctly before. This still didn't work, but see below for a twist :) > 2. Permanent shared directories disappear after VirtualBox restart. This is fixed! > 3. VirtualBox guest clipboard driver freezes on attempts to copy something from > host to guest; guest to host works OK. This is fixed! > Otherwise, VirtualBox works great for me. It keeps on working great and now even much faster. Now about the Host key issue. It is working for me when I change it something more "normal "than before :) I set it to Super_L and it works. KDE calls this key "Meta" and VirtualBox calls it "Left WinKey". When the Host Key didn't work it was set to Hyper_R. KDE didn't recognize that key properly and VirtulBox called it "Hyper", but didn't like it. But what's interesting is that this Hyper key used to work in 2.X releases of VB. Some technical details for the curios (if any): $ xmodmap xmodmap: up to 3 keys per modifier, (keycodes in parentheses): shift Shift_L (0x32), Shift_R (0x3e) lock Caps_Lock (0x42) control Control_L (0x25), Control_R (0x6d) mod1 Alt_L (0x40), Alt_R (0x71), Meta_L (0x9c) mod2 Num_Lock (0x4d) mod3 Hyper_R (0x74), Hyper_L (0x80) mod4 Super_L (0x73), Super_L (0x7f), Hyper_L (0x80) mod5 Mode_switch (0x5d), ISO_Level3_Shift (0x75), ISO_Level3_Shift (0x7c) Output of xev when I press and release my Hyper_R key: KeyPress event, serial 34, synthetic NO, window 0x5200001, root 0x6e, subw 0x0, time 79762548, (416,266), root:(418,327), state 0x10, keycode 116 (keysym 0xffee, Hyper_R), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 34, synthetic NO, window 0x5200001, root 0x6e, subw 0x0, time 79762565, (416,266), root:(418,327), state 0x30, keycode 116 (keysym 0xffee, Hyper_R), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False So Super is mod4 and Hyper is mod3 modifiers, but somehow applications are confused by Hyper. -- Andriy Gapon From nox at jelal.kn-bremen.de Sat Sep 12 18:36:31 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Sat Sep 12 18:36:37 2009 Subject: experimental FreeBSD qemu-devel git head port update for testing In-Reply-To: <2E5888455DA643CEB3960168C1AAB4E0@FSCPC> References: <20090829222339.GA93608@triton8.kn-bremen.de> <20090902175621.GA63905@triton8.kn-bremen.de> <20090904193435.GA77708@triton8.kn-bremen.de> <2E5888455DA643CEB3960168C1AAB4E0@FSCPC> Message-ID: <20090912183516.GA65678@triton8.kn-bremen.de> On Sat, Sep 12, 2009 at 12:04:11AM +0200, Sebastian Herbszt wrote: > Juergen Lock wrote: > > On Wed, Sep 02, 2009 at 07:56:21PM +0200, Juergen Lock wrote: > >> On Sun, Aug 30, 2009 at 12:23:39AM +0200, Juergen Lock wrote: > >> > Also the pcap patch stopped working in this snapshot and I don't yet > >> > know why. (I think the original version of that patch was submitted by > >> > Jung-uk Kim, maybe he has an idea; Cc'd.) > >> > [...] > >> > >> Jung-uk Kim sent me a new pcap patch (thanx! :), and I have just included > >> it in the mentioned update at > >> http://people.freebsd.org/~nox/qemu/qemu-devel-20090829.patch > > > > New update at the same place, Jung-uk Kim sent me another version of the > > pcap patch > > configure changes the LIBS variable (LIBS="$libpcap $LIBS"), which is not only used > for the qemu binary, but also for qemu-nbd, qemu-io and qemu-img. Linking those with > libpcap should not be required. Consider changing > > LIBS="$libpcap $LIBS" > > to > > libs_softmmu="$libpcap $libs_softmmu" > > which seems to fix this. Thanx, seems to work, applied. Juergen From mezz7 at cox.net Sat Sep 12 22:32:17 2009 From: mezz7 at cox.net (Jeremy Messenger) Date: Sat Sep 12 22:32:23 2009 Subject: ports/138752: www/linux-opera does not start In-Reply-To: <86iqfn6gfz.fsf@ahab.tihnet> References: <86iqfn6gfz.fsf@ahab.tihnet> Message-ID: On Sat, 12 Sep 2009 15:44:48 -0500, Heino Tiedemann wrote: > "Jeremy Messenger" wrote: > >> Can you show me the output of 'pkg_info -IX linux' and 'sysctl >> compat.linux'? > > > yes, of course.. Thanks. > ,----[ pkg_info -IX linux ] > | linux_base-fc-4_15 Base set of packages needed in Linux mode (for > i386/amd64) > `---- I have linux_base-f8-8_10 installed here. It looks like Opera now required glibc 2.4, which is available in f8 but dunno about f6. I will have to uninstall all of my linux_* ports and test it with linux_base-f6 to see if it will working. For I can edit the USE_LINUX in the Makefile by change from 'yes' to '6', '7' or else what it required. I think the emulation@ team said that it's recommend to have f8 or above. Not sure, need to check w/ them. > ,----[ sysctl compat.linux ] > | compat.linux.oss_version: 198144 > | compat.linux.osrelease: 2.4.2 > | compat.linux.osname: Linux > `---- Since linux-opera now requires newer linux_base than f4, so it is going to force you to set compat.linux.osrelease=2.6.16 in your /etc/sysctl.conf before you can upgrade your linux_base. The compat.linux.osrelease only exists in FreeBSD 7.x and above. The FreeBSD 8.x sets to 2.6.16 by default. BTW: Add emulation@ in the CC for they can correct me if I said anything wrong with Linux emulation stuff related. Cheers, Mezz -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org From dnaeon at gmail.com Sun Sep 13 05:45:06 2009 From: dnaeon at gmail.com (Marin Atanasov) Date: Sun Sep 13 05:45:13 2009 Subject: VirtualBox network patches for FreeBSD (vboxnetflt + vboxnetadp) In-Reply-To: <4AA784D9.80405@shapeshifter.se> References: <4AA784D9.80405@shapeshifter.se> Message-ID: <717f7a3e0909122245r75f7d205j19507593c209a4ab@mail.gmail.com> Hi, Yesterday I did an upgrade of the Virtualbox port from 3.0.51.r22226 to 3.0.51.r22683. However I tried changing the network settings to Bridge mode and Host only networking, but that doesn't seem to work for me. Are Fredrik's patches included in the latest port of Virtualbox or I still need to apply them manually? Also one more question about the patches - are they supposed to create the bridge interfaces automatically or I need to create them manually first before using them? Regards, Marin On Wed, Sep 9, 2009 at 1:35 PM, Fredrik Lindberg wrote: > Hi > > These patches implement bridge and host only networking on FreeBSD, they > have been tested on FreeBSD 7 and 8 by a few different people. The only > known issue is that they might not work with wireless cards. At least > it didn't work on my iwi-backed wlan0 interface on FreeBSD 8. > > The patches are split into different files for easier overview > > > http://www.shapeshifter.se/pub/patches/virtualbox/vbox-freebsd-netif-20090908.patch > > http://www.shapeshifter.se/pub/patches/virtualbox/vbox-freebsd-vboxnetadp-20090908.patch > > http://www.shapeshifter.se/pub/patches/virtualbox/vbox-freebsd-vboxnetflt-20090908.patch > http://www.shapeshifter.se/pub/patches/virtualbox/Config.kmk-20090908.patch > > http://www.shapeshifter.se/pub/patches/virtualbox/src-VBox-HostDrivers-Makefile.kmk-20090908.patch > > Original code is under the MIT license, patches to Makefiles, etc are > under whatever license you want (I don't claim any copyright over > these). > > > People running FreeBSD and want to test this with the vbox version > 3.0.51.r22226 that currently is in the ports tree needs the following > additional patches. > > > http://www.shapeshifter.se/pub/patches/virtualbox/Config.kmk-r22226-20090908.patch > > http://www.shapeshifter.se/pub/patches/virtualbox/virtualbox-port-20090907.patch > http://www.shapeshifter.se/pub/patches/virtualbox/ConsoleImpl2.cpp.patch > > Apply/compile with > cd /usr/ports/emulators/virtualbox > make clean patch > mkdir work/virtualbox-3.0.51r22226/src/VBox/HostDrivers/VBoxNetFlt/freebsd > mkdir work/virtualbox-3.0.51r22226/src/VBox/HostDrivers/VBoxNetAdp/freebsd > patch < virtualbox-port-20090907.patch > patch -d work/virtualbox-3.0.51r22226/Config.kmk-r22226-20090908.patch > patch -d work/virtualbox-3.0.51r22226/ConsoleImpl2.cpp.patch > patch -d > work/virtualbox-3.0.51r22226/src-VBox-HostDrivers-Makefile.kmk-20090908.patch > patch -d work/virtualbox-3.0.51r22226/vbox-freebsd-netif-20090908.patch > patch -d > work/virtualbox-3.0.51r22226/vbox-freebsd-vboxnetadp-20090908.patch > patch -d > work/virtualbox-3.0.51r22226/vbox-freebsd-vboxnetflt-20090908.patch > make install > > > Fredrik > _______________________________________________ > freebsd-emulation@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-emulation > To unsubscribe, send any mail to " > freebsd-emulation-unsubscribe@freebsd.org" > -- Marin Atanasov dnaeon AT gmail DOT com daemon AT unix-heaven DOT org From fli at shapeshifter.se Sun Sep 13 07:56:01 2009 From: fli at shapeshifter.se (Fredrik Lindberg) Date: Sun Sep 13 07:56:08 2009 Subject: VirtualBox network patches for FreeBSD (vboxnetflt + vboxnetadp) In-Reply-To: <717f7a3e0909122245r75f7d205j19507593c209a4ab@mail.gmail.com> References: <4AA784D9.80405@shapeshifter.se> <717f7a3e0909122245r75f7d205j19507593c209a4ab@mail.gmail.com> Message-ID: <4AACA589.9080102@shapeshifter.se> Marin Atanasov wrote: > Hi, > > Yesterday I did an upgrade of the Virtualbox port from 3.0.51.r22226 to > 3.0.51.r22683. > > However I tried changing the network settings to Bridge mode and Host only > networking, but that doesn't seem to work for me. > > Are Fredrik's patches included in the latest port of Virtualbox or I still > need to apply them manually? > Also one more question about the patches - are they supposed to create the > bridge interfaces automatically or I need to create them manually first > before using them? > > Regards, > Marin > No they are not included in the latest version of the port. They are however include in the upstream sources so future version of the VirtualBox port will include them. If you're using bridged mode everything *should* work automatically, you won't however see any "bridge interface" with ifconfig or similar, everything is done internally. Fredrik From rotkap at gmx.de Sun Sep 13 11:00:43 2009 From: rotkap at gmx.de (Heino Tiedemann) Date: Sun Sep 13 11:00:50 2009 Subject: ports/138752: www/linux-opera does not start In-Reply-To: (Jeremy Messenger's message of "Sat\, 12 Sep 2009 17\:34\:27 -0500") References: <86iqfn6gfz.fsf@ahab.tihnet> Message-ID: <86eiqb2kx4.fsf@ahab.tihnet> "Jeremy Messenger" wrote: > On Sat, 12 Sep 2009 15:44:48 -0500, Heino Tiedemann wrote: > >> "Jeremy Messenger" wrote: >> >>> Can you show me the output of 'pkg_info -IX linux' and 'sysctl >>> compat.linux'? >> >> >> yes, of course.. > > Thanks. > >> ,----[ pkg_info -IX linux ] > >> | linux_base-fc-4_15 Base set of packages needed in Linux mode (for >> i386/amd64) >> `---- > > I have linux_base-f8-8_10 installed here. If Opera needs that vesion, why is the opera port not depending on that version? can I just switch from fc-4_15 to f8-8_10? Are there reasons against switching? I am using portupgrade, this should do it: portupgrade -o emulators/linux_base-f8 emulators/linux_base-fc4 Is that right? Heino From herbszt at gmx.de Sun Sep 13 14:40:34 2009 From: herbszt at gmx.de (Sebastian Herbszt) Date: Sun Sep 13 14:40:41 2009 Subject: experimental FreeBSD qemu-devel git head port update for testing In-Reply-To: <20090912183516.GA65678@triton8.kn-bremen.de> References: <20090829222339.GA93608@triton8.kn-bremen.de> <20090902175621.GA63905@triton8.kn-bremen.de> <20090904193435.GA77708@triton8.kn-bremen.de> <2E5888455DA643CEB3960168C1AAB4E0@FSCPC> <20090912183516.GA65678@triton8.kn-bremen.de> Message-ID: Replace own invokation of $cc with compile_prog (patch will likely not apply). - Sebastian @@ -37,7 +37,7 @@ + else + libpcap=-lwpcap + fi -+ if ! $cc $ARCH_CFLAGS -o $TMPE $libpcap $TMPC 2> /dev/null ; then ++ if ! compile_prog "" "$libpcap" ; then + echo + echo "Error: Could not find pcap" + echo "Make sure to have the pcap libs and headers installed." @@ -52,7 +52,7 @@ + return (pcap_create("foo", errbuf) == (pcap_t *)0 ? 1 : 0); +} +EOF -+ if $cc $ARCH_CFLAGS -o $TMPE $libpcap $TMPC 2> /dev/null ; then ++ if compile_prog "" "$libpcap" ; then + pcap_create="yes" + fi + cat > $TMPC << EOF @@ -61,10 +61,9 @@ +#include +int main(void) { return (BPF_MAJOR_VERSION); } +EOF -+ if $cc $ARCH_CFLAGS -o $TMPE $TMPC 2> /dev/null ; then ++ if compile_prog "" "" ; then + bpf="yes" + fi -+# LIBS="$libpcap $LIBS" + libs_softmmu="$libpcap $libs_softmmu" +fi # test "$pcap" + @@ -72,7 +71,7 @@ From herbszt at gmx.de Sun Sep 13 14:57:05 2009 From: herbszt at gmx.de (Sebastian Herbszt) Date: Sun Sep 13 14:57:12 2009 Subject: experimental FreeBSD qemu-devel git head port update for testing In-Reply-To: <20090912183516.GA65678@triton8.kn-bremen.de> References: <20090829222339.GA93608@triton8.kn-bremen.de> <20090902175621.GA63905@triton8.kn-bremen.de> <20090904193435.GA77708@triton8.kn-bremen.de> <2E5888455DA643CEB3960168C1AAB4E0@FSCPC> <20090912183516.GA65678@triton8.kn-bremen.de> Message-ID: <5ED063C575C64A60B1E1B5CEE2591D11@FSCPC> This change seems wrong: + if (ifname == NULL && (ifname = pcap_lookupdev(errbuf)) == NULL) { -+ fprintf(stderr, "qemu: pcap_lookupdev: %s\n", errbuf); ++ fprintf(stderr, "qemu: pcap_create: %s\n", errbuf); + goto fail; + } - Sebastian From mezz7 at cox.net Sun Sep 13 15:01:17 2009 From: mezz7 at cox.net (Jeremy Messenger) Date: Sun Sep 13 15:01:24 2009 Subject: ports/138752: www/linux-opera does not start In-Reply-To: <86eiqb2kx4.fsf@ahab.tihnet> References: <86iqfn6gfz.fsf@ahab.tihnet> <86eiqb2kx4.fsf@ahab.tihnet> Message-ID: On Sun, 13 Sep 2009 05:40:07 -0500, Heino Tiedemann wrote: > The following reply was made to PR ports/138752; it has been noted by > GNATS. > > From: Heino Tiedemann > To: "Jeremy Messenger" > Cc: bug-followup@freebsd.org, emulation@freebsd.org > Subject: Re: ports/138752: www/linux-opera does not start > Date: Sun, 13 Sep 2009 12:33:59 +0200 > > "Jeremy Messenger" wrote: > > On Sat, 12 Sep 2009 15:44:48 -0500, Heino Tiedemann > wrote: > > > >> "Jeremy Messenger" wrote: > >> > >>> Can you show me the output of 'pkg_info -IX linux' and 'sysctl > >>> compat.linux'? > >> > >> > >> yes, of course.. > > > > Thanks. > > > >> ,----[ pkg_info -IX linux ] > > > >> | linux_base-fc-4_15 Base set of packages needed in Linux mode (for > >> i386/amd64) > >> `---- > > > > I have linux_base-f8-8_10 installed here. > > If Opera needs that vesion, why is the opera port not depending on > that version? You have snipped out my previous comment. I said: ------------------------ It looks like Opera now required glibc 2.4, which is available in f8 but dunno about f6. I will have to uninstall all of my linux_* ports and test it with linux_base-f6 to see if it will working. For I can edit the USE_LINUX in the Makefile by change from 'yes' to '6', '7' or else what it required. ------------------------ It means: I just found out linux-opera now required glibc 2.4, so I am working on it to make the change of version requirement correct. > can I just switch from fc-4_15 to f8-8_10? Yes, since you have FreeBSD 7.2-STABLE. > Are there reasons against switching? Not that I know of. > I am using portupgrade, this should do it: > portupgrade -o emulators/linux_base-f8 emulators/linux_base-fc4 > Is that right? See in the /usr/ports/UPDATING at 20090401 and 20070327 sections for how to upgrade. Cheers, Mezz > Heino -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org From rotkap at gmx.de Sun Sep 13 15:32:19 2009 From: rotkap at gmx.de (Heino Tiedemann) Date: Sun Sep 13 15:32:25 2009 Subject: ports/138752: www/linux-opera does not start In-Reply-To: (Jeremy Messenger's message of "Sun\, 13 Sep 2009 10\:03\:32 -0500") References: <86iqfn6gfz.fsf@ahab.tihnet> <86eiqb2kx4.fsf@ahab.tihnet> Message-ID: <86r5uavp1d.fsf@ahab.tihnet> "Jeremy Messenger" wrote: > You have snipped out my previous comment. I said: > > ------------------------ > It looks like Opera now required glibc 2.4, which is available in f8 > but dunno about f6. I will have to uninstall all of my linux_* ports > and test it with linux_base-f6 to see if it will working. For I can > edit the USE_LINUX in the Makefile by change from 'yes' to '6', '7' > or else what it required. > ------------------------ > > It means: I just found out linux-opera now required glibc 2.4, so I am > working on it to make the change of version requirement correct. Oh - I'm sorry, for my misunderstanding. >> can I just switch from fc-4_15 to f8-8_10? > > Yes, since you have FreeBSD 7.2-STABLE. > >> Are there reasons against switching? > > Not that I know of. > >> I am using portupgrade, this should do it: >> portupgrade -o emulators/linux_base-f8 emulators/linux_base-fc4 >> Is that right? > > See in the /usr/ports/UPDATING at 20090401 and 20070327 sections for > how to upgrade. Thank you! works fine! my problem is solved with this answer. see you Heino From oberman at es.net Sun Sep 13 15:43:56 2009 From: oberman at es.net (Kevin Oberman) Date: Sun Sep 13 15:44:02 2009 Subject: ports/138752: www/linux-opera does not start In-Reply-To: Your message of "Sun, 13 Sep 2009 10:03:32 CDT." Message-ID: <20090913154337.D5E0A1CC37@ptavv.es.net> > Date: Sun, 13 Sep 2009 10:03:32 -0500 > From: "Jeremy Messenger" > Sender: owner-freebsd-emulation@freebsd.org > > On Sun, 13 Sep 2009 05:40:07 -0500, Heino Tiedemann wrote: > > > The following reply was made to PR ports/138752; it has been noted by > > GNATS. > > > > From: Heino Tiedemann > > To: "Jeremy Messenger" > > Cc: bug-followup@freebsd.org, emulation@freebsd.org > > Subject: Re: ports/138752: www/linux-opera does not start > > Date: Sun, 13 Sep 2009 12:33:59 +0200 > > > > "Jeremy Messenger" wrote: > > > On Sat, 12 Sep 2009 15:44:48 -0500, Heino Tiedemann > > wrote: > > > > > >> "Jeremy Messenger" wrote: > > >> > > >>> Can you show me the output of 'pkg_info -IX linux' and 'sysctl > > >>> compat.linux'? > > >> > > >> > > >> yes, of course.. > > > > > > Thanks. > > > > > >> ,----[ pkg_info -IX linux ] > > > > > >> | linux_base-fc-4_15 Base set of packages needed in Linux mode (for > > >> i386/amd64) > > >> `---- > > > > > > I have linux_base-f8-8_10 installed here. > > > > If Opera needs that vesion, why is the opera port not depending on > > that version? > > You have snipped out my previous comment. I said: > > ------------------------ > It looks like Opera now required glibc 2.4, which is available in f8 but > dunno about f6. I will have to uninstall all of my linux_* ports and test > it with linux_base-f6 to see if it will working. For I can edit the > USE_LINUX in the Makefile by change from 'yes' to '6', '7' or else what it > required. > ------------------------ > > It means: I just found out linux-opera now required glibc 2.4, so I am > working on it to make the change of version requirement correct. > > > can I just switch from fc-4_15 to f8-8_10? > > Yes, since you have FreeBSD 7.2-STABLE. > > > Are there reasons against switching? > > Not that I know of. > > > I am using portupgrade, this should do it: > > portupgrade -o emulators/linux_base-f8 emulators/linux_base-fc4 > > Is that right? I'd recommend emulators/linux_base-f10. That is the default in V8.0 and Flash10 will work with it on 7.2. Older versions all have issues with sound with older versions and none are being updated, so security vulnerabilities don't get fixed. I am running f10 on my one remaining 7.2 system and everything seems to be working fine. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 From dnaeon at gmail.com Sun Sep 13 16:06:51 2009 From: dnaeon at gmail.com (Marin Atanasov) Date: Sun Sep 13 16:06:57 2009 Subject: VirtualBox network patches for FreeBSD (vboxnetflt + vboxnetadp) In-Reply-To: <4AACA589.9080102@shapeshifter.se> References: <4AA784D9.80405@shapeshifter.se> <717f7a3e0909122245r75f7d205j19507593c209a4ab@mail.gmail.com> <4AACA589.9080102@shapeshifter.se> Message-ID: <717f7a3e0909130906w521257e9g34b8b3a61d828430@mail.gmail.com> Hi, I just tried to apply the patches on the new Virtualbox port ( 3.0.51.r22683 ) and then did a make install, but I got this error during the install process: ===> Installing for virtualbox-3.0.51.r22683 ===> virtualbox-3.0.51.r22683 depends on file: /usr/local/bin/easy_install-2.6 - found ===> virtualbox-3.0.51.r22683 depends on file: /usr/local/bin/python2.6 - found ===> virtualbox-3.0.51.r22683 depends on file: /usr/local/libdata/pkgconfig/xcursor.pc - found ===> virtualbox-3.0.51.r22683 depends on file: /usr/local/libdata/pkgconfig/xmu.pc - found ===> virtualbox-3.0.51.r22683 depends on package: qt4-gui>=4.5.2 - found ===> virtualbox-3.0.51.r22683 depends on package: qt4-network>=4.5.2 - found ===> virtualbox-3.0.51.r22683 depends on package: qt4-linguist>=4.5.2 - found ===> virtualbox-3.0.51.r22683 depends on executable: pkg-config - found ===> virtualbox-3.0.51.r22683 depends on file: /usr/local/lib/gio/modules/libgiofam.so - found ===> virtualbox-3.0.51.r22683 depends on executable: cdrecord - found ===> Generating temporary packing list ===> Checking if emulators/virtualbox already installed /bin/mkdir -p /boot/modules install -o root -g wheel -m 555 /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22683/out/freebsd.x86/debug/bin/vboxdrv.ko /boot/modules install -o root -g wheel -m 555 /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22683/out/freebsd.x86/debug/bin/vboxnetadp.ko /boot/modules install: /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22683/out/freebsd.x86/debug/bin/vboxnetadp.ko: No such file or directory *** Error code 71 Stop in /usr/ports/emulators/virtualbox. *** Error code 1 Stop in /usr/ports/emulators/virtualbox. Are the patches supposed to work with new Virtualbox port? Regards, Marin On Sun, Sep 13, 2009 at 10:55 AM, Fredrik Lindberg wrote: > Marin Atanasov wrote: > >> Hi, >> >> Yesterday I did an upgrade of the Virtualbox port from 3.0.51.r22226 to >> 3.0.51.r22683. >> >> However I tried changing the network settings to Bridge mode and Host only >> networking, but that doesn't seem to work for me. >> >> Are Fredrik's patches included in the latest port of Virtualbox or I still >> need to apply them manually? >> Also one more question about the patches - are they supposed to create the >> bridge interfaces automatically or I need to create them manually first >> before using them? >> >> Regards, >> Marin >> >> > No they are not included in the latest version of the port. They > are however include in the upstream sources so future version > of the VirtualBox port will include them. > > If you're using bridged mode everything *should* work automatically, > you won't however see any "bridge interface" with ifconfig or similar, > everything is done internally. > > Fredrik > > -- Marin Atanasov dnaeon AT gmail DOT com daemon AT unix-heaven DOT org From rotkap at gmx.de Sun Sep 13 17:05:47 2009 From: rotkap at gmx.de (Heino Tiedemann) Date: Sun Sep 13 17:05:53 2009 Subject: ports/138752: www/linux-opera does not start In-Reply-To: <20090913154337.D5E0A1CC37@ptavv.es.net> (Kevin Oberman's message of "Sun\, 13 Sep 2009 08\:43\:37 -0700") References: <20090913154337.D5E0A1CC37@ptavv.es.net> Message-ID: <86iqfmvkpn.fsf@ahab.tihnet> "Kevin Oberman" wrote: >> Date: Sun, 13 Sep 2009 10:03:32 -0500 >> From: "Jeremy Messenger" >> Sender: owner-freebsd-emulation@freebsd.org >> >> On Sun, 13 Sep 2009 05:40:07 -0500, Heino Tiedemann wrote: >> >> > The following reply was made to PR ports/138752; it has been noted by >> > GNATS. >> > >> > From: Heino Tiedemann >> > To: "Jeremy Messenger" >> > Cc: bug-followup@freebsd.org, emulation@freebsd.org >> > Subject: Re: ports/138752: www/linux-opera does not start >> > Date: Sun, 13 Sep 2009 12:33:59 +0200 >> > >> > "Jeremy Messenger" wrote: >> > > On Sat, 12 Sep 2009 15:44:48 -0500, Heino Tiedemann >> > wrote: >> > > >> > >> "Jeremy Messenger" wrote: >> > >> >> > >>> Can you show me the output of 'pkg_info -IX linux' and 'sysctl >> > >>> compat.linux'? >> > >> >> > >> >> > >> yes, of course.. >> > > >> > > Thanks. >> > > >> > >> ,----[ pkg_info -IX linux ] >> > > >> > >> | linux_base-fc-4_15 Base set of packages needed in Linux mode (for >> > >> i386/amd64) >> > >> `---- >> > > >> > > I have linux_base-f8-8_10 installed here. >> > >> > If Opera needs that vesion, why is the opera port not depending on >> > that version? >> >> You have snipped out my previous comment. I said: >> >> ------------------------ >> It looks like Opera now required glibc 2.4, which is available in f8 but >> dunno about f6. I will have to uninstall all of my linux_* ports and test >> it with linux_base-f6 to see if it will working. For I can edit the >> USE_LINUX in the Makefile by change from 'yes' to '6', '7' or else what it >> required. >> ------------------------ >> >> It means: I just found out linux-opera now required glibc 2.4, so I am >> working on it to make the change of version requirement correct. >> >> > can I just switch from fc-4_15 to f8-8_10? >> >> Yes, since you have FreeBSD 7.2-STABLE. >> >> > Are there reasons against switching? >> >> Not that I know of. >> >> > I am using portupgrade, this should do it: >> > portupgrade -o emulators/linux_base-f8 emulators/linux_base-fc4 >> > Is that right? > > I'd recommend emulators/linux_base-f10. That is the default in V8.0 and > Flash10 will work with it on 7.2. Older versions all have issues with > sound with older versions and none are being updated, so security > vulnerabilities don't get fixed. > > I am running f10 on my one remaining 7.2 system and everything seems to > be working fine. thank you. I did a "make fetch" in emulators/linux_base-f10 - wow there comes a lot.. I'll think about linux_base-f10 - for that moment my linux-opera runs perfekt with flashplugin 7 From decke at bluelife.at Sun Sep 13 17:26:17 2009 From: decke at bluelife.at (Bernhard Froehlich) Date: Sun Sep 13 17:26:24 2009 Subject: VirtualBox network patches for FreeBSD (vboxnetflt + vboxnetadp) In-Reply-To: <717f7a3e0909130906w521257e9g34b8b3a61d828430@mail.gmail.com> References: <4AA784D9.80405@shapeshifter.se> <717f7a3e0909122245r75f7d205j19507593c209a4ab@mail.gmail.com> <4AACA589.9080102@shapeshifter.se> <717f7a3e0909130906w521257e9g34b8b3a61d828430@mail.gmail.com> Message-ID: On Sun, September 13, 2009 6:06 pm, Marin Atanasov wrote: > Hi, > > I just tried to apply the patches on the new Virtualbox port ( > 3.0.51.r22683 > ) and then did a make install, but I got this error during the install > process: > > ===> Installing for virtualbox-3.0.51.r22683 > ===> virtualbox-3.0.51.r22683 depends on file: > /usr/local/bin/easy_install-2.6 - found > ===> virtualbox-3.0.51.r22683 depends on file: /usr/local/bin/python2.6 > - > found > ===> virtualbox-3.0.51.r22683 depends on file: > /usr/local/libdata/pkgconfig/xcursor.pc - found > ===> virtualbox-3.0.51.r22683 depends on file: > /usr/local/libdata/pkgconfig/xmu.pc - found > ===> virtualbox-3.0.51.r22683 depends on package: qt4-gui>=4.5.2 - found > ===> virtualbox-3.0.51.r22683 depends on package: qt4-network>=4.5.2 - > found > ===> virtualbox-3.0.51.r22683 depends on package: qt4-linguist>=4.5.2 - > found > ===> virtualbox-3.0.51.r22683 depends on executable: pkg-config - found > ===> virtualbox-3.0.51.r22683 depends on file: > /usr/local/lib/gio/modules/libgiofam.so - found > ===> virtualbox-3.0.51.r22683 depends on executable: cdrecord - found > ===> Generating temporary packing list > ===> Checking if emulators/virtualbox already installed > /bin/mkdir -p /boot/modules > install -o root -g wheel -m 555 > /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22683/out/freebsd.x86/debug/bin/vboxdrv.ko > /boot/modules > install -o root -g wheel -m 555 > /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22683/out/freebsd.x86/debug/bin/vboxnetadp.ko > /boot/modules > install: > /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22683/out/freebsd.x86/debug/bin/vboxnetadp.ko: > No such file or directory > *** Error code 71 > > Stop in /usr/ports/emulators/virtualbox. > *** Error code 1 > > Stop in /usr/ports/emulators/virtualbox. > > Are the patches supposed to work with new Virtualbox port? > > Regards, > Marin > > > On Sun, Sep 13, 2009 at 10:55 AM, Fredrik Lindberg > wrote: > >> Marin Atanasov wrote: >> >>> Hi, >>> >>> Yesterday I did an upgrade of the Virtualbox port from 3.0.51.r22226 to >>> 3.0.51.r22683. >>> >>> However I tried changing the network settings to Bridge mode and Host >>> only >>> networking, but that doesn't seem to work for me. >>> >>> Are Fredrik's patches included in the latest port of Virtualbox or I >>> still >>> need to apply them manually? >>> Also one more question about the patches - are they supposed to create >>> the >>> bridge interfaces automatically or I need to create them manually first >>> before using them? You can just try our testing port which is based on the latest vbox code and already includes Fredriks patches. svn co http://svn.bluelife.at/projects/packages/blueports/emulators/virtualbox/ -- Bernhard Fr?hlich http://www.bluelife.at/ From jonathan at kc8onw.net Mon Sep 14 01:20:05 2009 From: jonathan at kc8onw.net (Jonathan) Date: Mon Sep 14 01:20:10 2009 Subject: Virtualbox and VRDP Message-ID: <4AAD95C2.7040907@kc8onw.net> I just installed virtualbox on my server without X11 support intending to run it headless and now I find that the Virtual Remote Display Protocol support is only available in the closed source version. The virtualbox Editions page says that some of the closed source features may eventually become available in the open source version as well, has anyone heard anything about this happening for VRDP? Are there any other options that would allow me to set up a VM remotely without installing X? I suppose I could set up a VM locally and then copy it to my server once it's configured for remote ssh access but that would involve copying several GB over the internet, a rather slow process on my connection. Thanks, Jonathan P.S. Thank you very much to all who have helped bring VirtualBox to FreeBSD! From dnaeon at gmail.com Mon Sep 14 05:25:27 2009 From: dnaeon at gmail.com (Marin Atanasov) Date: Mon Sep 14 05:25:33 2009 Subject: VirtualBox network patches for FreeBSD (vboxnetflt + vboxnetadp) In-Reply-To: References: <4AA784D9.80405@shapeshifter.se> <717f7a3e0909122245r75f7d205j19507593c209a4ab@mail.gmail.com> <4AACA589.9080102@shapeshifter.se> <717f7a3e0909130906w521257e9g34b8b3a61d828430@mail.gmail.com> Message-ID: <4AADD393.4080305@gmail.com> Hi, I've installed virtualbox from the svn repo and I must say it works great! Great job! Btw, I see that you have updated the port as well, so now it's in the FreeBSD ports collection too - one more great news! :) Thanks, Marin Bernhard Froehlich wrote: > You can just try our testing port which is based on the latest vbox code > and already includes Fredriks patches. > > svn co > http://svn.bluelife.at/projects/packages/blueports/emulators/virtualbox/ > > From xorquewasp at googlemail.com Mon Sep 14 05:38:56 2009 From: xorquewasp at googlemail.com (xorquewasp@googlemail.com) Date: Mon Sep 14 05:39:02 2009 Subject: Problems with qemu networking on 7.2-RELEASE-amd64? Message-ID: <20090914051402.GB44046@logik.internal.network> Hello. I'm having horrendous trouble getting qemu to do networking on 7.2-RELEASE-amd64. I've not had any trouble on previous versions of FreeBSD and qemu so this comes as a bit of a surprise. The setup is a simple bridge between my main physical NIC (re0) and a tap device (tap0). I use PF to filter on the bridge for basic access control. # ifconfig bridge0 create # ifconfig tap0 create # ifconfig bridge0 addm tap0 # ifconfig bridge0 addm re0 # chmod 660 /dev/tap0 # chown root:devel /dev/tap0 # sysctl net.link.tap.up_on_open=1 # sysctl net.link.tap.user_open=1 $ cat if-up #!/bin/sh info() { echo "if-up: info: $1" 1>&2 } info "bringing up $1" sudo /sbin/ifconfig $1 0.0.0.0 promisc up exit 0 $ ifconfig bridge0 bridge0: flags=8802 metric 0 mtu 1500 ether de:38:3c:f6:8a:a9 id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200 root id 00:00:00:00:00:00 priority 0 ifcost 0 port 0 member: re0 flags=143 ifmaxaddr 0 port 1 priority 128 path cost 200000 member: tap0 flags=143 ifmaxaddr 0 port 9 priority 128 path cost 2000000 $ ifconfig re0 re0: flags=8943 metric 0 mtu 1500 options=3898 ether 00:e0:4d:b3:5b:bd inet 10.1.3.1 netmask 0xffff0000 broadcast 10.1.255.255 inet 10.1.3.2 netmask 0xffff0000 broadcast 10.1.255.255 inet 10.1.3.3 netmask 0xffff0000 broadcast 10.1.255.255 inet 10.1.3.4 netmask 0xffff0000 broadcast 10.1.255.255 inet 10.1.3.5 netmask 0xffff0000 broadcast 10.1.255.255 inet 10.1.3.6 netmask 0xffff0000 broadcast 10.1.255.255 inet 10.1.3.7 netmask 0xffff0000 broadcast 10.1.255.255 inet 10.1.3.8 netmask 0xffff0000 broadcast 10.1.255.255 inet 10.1.3.9 netmask 0xffff0000 broadcast 10.1.255.255 inet 10.1.3.10 netmask 0xffff0000 broadcast 10.1.255.255 inet 10.1.3.11 netmask 0xffff0000 broadcast 10.1.255.255 media: Ethernet autoselect (100baseTX ) status: active $ qemu -snapshot -hda image -net nic -net tap,ifname=tap0,script=if-up $ ifconfig tap0 tap0: flags=28943 metric 0 mtu 1500 ether 00:bd:bd:41:18:00 inet 0.0.0.0 netmask 0xff000000 broadcast 0.255.255.255 Opened by PID 21860 At this point, the guest in the qemu VM has the correct TCP/IP settings: host: 10.1.3.12 mask: 255.255.0.0 dns: 10.2.1.7 gate: 10.1.0.1 The ability for various guests to see the network interface is varied. NetBSD 5.0.1 x86 sees no network interface at all (nothing in dmesg). OpenBSD 4.5 x86 sees a network interface but at some point during boot, it'll state something along the lines of "ne3: device timeout" and networking doesn't work. Windows XP x86 seems to be able to see a network interface and can apparently send outgoing packets for DNS resolution but appears to never receive any data in return. NetBSD 5.0.1 SPARC can see an interface and can apparently send packets and not receive. I've intermittently been able to connect in via SSH, however. Currently, as I write, the NetBSD SPARC guest can neither send nor receive any data on the network interface (watching the bridge, tap and pflog devices shows no connections being made). Is anyone else having trouble? xw PS: Please CC as I'm not subscribed. From bsam at ipt.ru Mon Sep 14 06:56:37 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Mon Sep 14 06:56:44 2009 Subject: ports/138752: www/linux-opera does not start In-Reply-To: (Jeremy Messenger's message of "Sat, 12 Sep 2009 17:34:27 -0500") References: <86iqfn6gfz.fsf@ahab.tihnet> Message-ID: <76660667@bb.ipt.ru> On Sat, 12 Sep 2009 17:34:27 -0500 Jeremy Messenger wrote: > BTW: Add emulation@ in the CC for they can correct me if I said > anything wrong with Linux emulation stuff related. Jeremy, you are perfectly correct. However, I'll advise against other linux base ports than -fc4, -f8 and -f10. The latter ports have all needed linux infrastructure ports. A note: I'll commit the last one for -f10- soon as it has been just repocopied (it's a graphics/linux-f10-libGLU port). -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From decke at bluelife.at Mon Sep 14 07:33:17 2009 From: decke at bluelife.at (Bernhard Froehlich) Date: Mon Sep 14 07:33:24 2009 Subject: Virtualbox and VRDP In-Reply-To: <4AAD95C2.7040907@kc8onw.net> References: <4AAD95C2.7040907@kc8onw.net> Message-ID: <29e884c4b57123a181fb162710e6d1d0.squirrel@webmail.itac.at> On Mon, September 14, 2009 3:00 am, Jonathan wrote: > I just installed virtualbox on my server without X11 support intending > to run it headless and now I find that the Virtual Remote Display > Protocol support is only available in the closed source version. The > virtualbox Editions page says that some of the closed source features > may eventually become available in the open source version as well, has > anyone heard anything about this happening for VRDP? > > Are there any other options that would allow me to set up a VM remotely > without installing X? I suppose I could set up a VM locally and then > copy it to my server once it's configured for remote ssh access but that > would involve copying several GB over the internet, a rather slow > process on my connection. You can setup your virtual machine with VBoxManage but installing a system in it is rather painful without GUI. The way you described is my preferred at the moment but you could also install with X11 and use VBoxSDL and X11 forwarding. I've talked to the vbox developers and they don't think that the RDP code will be put opensource in the foreseeable future. That's a pity because in combination with vboxweb [0] which is a python web interface to vbox that includes a Flash based RDP client this would be a great headless solution. [0] http://code.google.com/p/vboxweb/ -- Bernhard Fr?hlich http://www.bluelife.at/ From Gabor at Zahemszky.HU Mon Sep 14 09:48:53 2009 From: Gabor at Zahemszky.HU (Zahemszky =?ISO-8859-2?Q?G=E1bor?=) Date: Mon Sep 14 09:48:59 2009 Subject: virtualbox cannot compile Message-ID: <20090914094805.47a01eab@Picasso.Zahemszky.HU> Hi! I've got a problem with the (last two) recent version(s) of the emulators/virtualbox port, as I cannot compile it. It fails with a: 02/src/VBox/Runtime/r0drv/freebsd/alloc-r0drv-freebsd.c:34: /sys/vm/vm.h:64:24: error: machine/vm.h: No such file or directory error message. The previous version failed with the same problem. The configuration is: $ make showconfig ===> The following configuration options are available for virtualbox-3.0.51.r22902: QT4=off "Build with QT4 Frontend" DEBUG=off "Build with debugging symbols" GUESTADDITIONS=on "Build with Guest Additions" DBUS=on "Build with D-Bus and HAL support" PULSEAUDIO=off "Build with PulseAudio" X11=on "Build with X11 support" NLS=on "Native language support" ===> Use 'make config' to modify these settings $ The full error log (generated after a failed compile, with a script make) is attached. Zahy < Gabor at Zahemszky dot HU > -- #!/bin/ksh Z='21N16I25C25E30, 40M30E33E25T15U!'; IFS=' ABCDEFGHIJKLMNOPQRSTUVWXYZ '; set -- $Z;for i;{ [[ $i = ? ]]&&print $i&&break; [[ $i = ??? ]]&&j=$i&&i=${i%?}; typeset -i40 i=8#$i;print -n ${i#???}; [[ "$j" = ??? ]]&&print -n "${j#??} "&&j=;typeset +i i;}; IFS=' 0123456789 ';set -- $Z;for i;{ [[ $i = , ]]&&i=2; [[ $i = ?? ]]||typeset -l i;j="$j $i";typeset +l i;};print "$j" -------------- next part -------------- A non-text attachment was scrubbed... Name: typescript Type: application/octet-stream Size: 8356 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-emulation/attachments/20090914/ebb80a8c/typescript.obj From bsam at ipt.ru Mon Sep 14 10:20:43 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Mon Sep 14 10:20:50 2009 Subject: changes in linux ports infrastructure Message-ID: <80173957@bb.ipt.ru> Dear linux ports maintainers, I've just committed a new graphics/linux-f10-libGLU port and apropriate changes to linux ports infrastructure. I'm going to commit the following patch which uses the new port and its infrastructure. The main goal is to give users of linux nvidia drivers to use more recent libGLU packages. Those changes do not touch default packages but imho it will be good to commit the patch before 8.0-RELEASE. Please, give it a try and submit a followup. Thanks! ----- Index: games/linux-coldwar-demo/Makefile =================================================================== RCS file: /home/pcvs/ports/games/linux-coldwar-demo/Makefile,v retrieving revision 1.4 diff -u -r1.4 Makefile --- games/linux-coldwar-demo/Makefile 7 Jun 2009 15:23:52 -0000 1.4 +++ games/linux-coldwar-demo/Makefile 14 Sep 2009 09:42:24 -0000 @@ -31,8 +31,8 @@ .include .if defined(WITH_NVIDIA) -RUN_DEPENDS+= ${LINUXBASE}/usr/lib/libGL.so.1:${PORTSDIR}/x11/nvidia-driver \ - ${LINUXBASE}/usr/X11R6/lib/libGLU.so.1:${PORTSDIR}/graphics/linux-libGLU +RUN_DEPENDS+= ${LINUXBASE}/usr/lib/libGL.so.1:${PORTSDIR}/x11/nvidia-driver +USE_LINUX_APPS+=libglu .else USE_LINUX_APPS+=dri .endif Index: games/linux-darwinia-demo/Makefile =================================================================== RCS file: /home/pcvs/ports/games/linux-darwinia-demo/Makefile,v retrieving revision 1.5 diff -u -r1.5 Makefile --- games/linux-darwinia-demo/Makefile 7 Jun 2009 15:23:52 -0000 1.5 +++ games/linux-darwinia-demo/Makefile 14 Sep 2009 09:42:24 -0000 @@ -31,8 +31,8 @@ .include .if defined(WITH_NVIDIA) -RUN_DEPENDS+= ${LINUXBASE}/usr/lib/libGL.so.1:${PORTSDIR}/x11/nvidia-driver \ - ${LINUXBASE}/usr/X11R6/lib/libGLU.so.1:${PORTSDIR}/graphics/linux-libGLU +RUN_DEPENDS+= ${LINUXBASE}/usr/lib/libGL.so.1:${PORTSDIR}/x11/nvidia-driver +USE_LINUX_APPS+=libglu .else USE_LINUX_APPS+=dri .endif Index: games/linux-defcon/Makefile =================================================================== RCS file: /home/pcvs/ports/games/linux-defcon/Makefile,v retrieving revision 1.4 diff -u -r1.4 Makefile --- games/linux-defcon/Makefile 7 Jun 2009 15:23:52 -0000 1.4 +++ games/linux-defcon/Makefile 14 Sep 2009 09:42:24 -0000 @@ -29,8 +29,8 @@ .include .if defined(WITH_NVIDIA) -RUN_DEPENDS+= ${LINUXBASE}/usr/lib/libGL.so.1:${PORTSDIR}/x11/nvidia-driver \ - ${LINUXBASE}/usr/X11R6/lib/libGLU.so.1:${PORTSDIR}/graphics/linux-libGLU +RUN_DEPENDS+= ${LINUXBASE}/usr/lib/libGL.so.1:${PORTSDIR}/x11/nvidia-driver +USE_LINUX_APPS+=libglu .else USE_LINUX_APPS+=dri .endif Index: games/linux-gorky17-demo/Makefile =================================================================== RCS file: /home/pcvs/ports/games/linux-gorky17-demo/Makefile,v retrieving revision 1.4 diff -u -r1.4 Makefile --- games/linux-gorky17-demo/Makefile 7 Jun 2009 15:23:53 -0000 1.4 +++ games/linux-gorky17-demo/Makefile 14 Sep 2009 09:42:24 -0000 @@ -32,8 +32,8 @@ .include .if defined(WITH_NVIDIA) -RUN_DEPENDS+= ${LINUXBASE}/usr/lib/libGL.so.1:${PORTSDIR}/x11/nvidia-driver \ - ${LINUXBASE}/usr/X11R6/lib/libGLU.so.1:${PORTSDIR}/graphics/linux-libGLU +RUN_DEPENDS+= ${LINUXBASE}/usr/lib/libGL.so.1:${PORTSDIR}/x11/nvidia-driver +USE_LINUX_APPS+=libglu .else USE_LINUX_APPS+=dri .endif Index: games/linux-nwnclient/Makefile =================================================================== RCS file: /home/pcvs/ports/games/linux-nwnclient/Makefile,v retrieving revision 1.18 diff -u -r1.18 Makefile --- games/linux-nwnclient/Makefile 7 Jun 2009 15:23:53 -0000 1.18 +++ games/linux-nwnclient/Makefile 14 Sep 2009 09:42:24 -0000 @@ -20,8 +20,8 @@ RUN_DEPENDS= ${LOCALBASE}/share/nwndata/NWNv129.txt:${PORTSDIR}/games/nwndata .ifdef WITH_NVIDIA_GL -RUN_DEPENDS+= ${LINUXBASE}/usr/lib/libGL.so.1:${PORTSDIR}/x11/nvidia-driver \ - ${LINUXBASE}/usr/X11R6/lib/libGLU.so.1:${PORTSDIR}/graphics/linux-libGLU +RUN_DEPENDS+= ${LINUXBASE}/usr/lib/libGL.so.1:${PORTSDIR}/x11/nvidia-driver +USE_LINUX_APPS+=libglu .else USE_LINUX_APPS+=dri .endif Index: games/linux-savage/Makefile =================================================================== RCS file: /home/pcvs/ports/games/linux-savage/Makefile,v retrieving revision 1.9 diff -u -r1.9 Makefile --- games/linux-savage/Makefile 7 Jun 2009 15:23:53 -0000 1.9 +++ games/linux-savage/Makefile 14 Sep 2009 09:42:24 -0000 @@ -40,8 +40,8 @@ .if defined(WITH_NVIDIA_GL) . if !exists(${LINUXBASE}/usr/X11R6/lib/libGL.so.1) -RUN_DEPENDS+= ${LINUXBASE}/usr/lib/libGL.so.1:${PORTSDIR}/x11/nvidia-driver \ - ${LINUXBASE}/usr/X11R6/lib/libGLU.so.1:${PORTSDIR}/graphics/linux-libGLU +RUN_DEPENDS+= ${LINUXBASE}/usr/lib/libGL.so.1:${PORTSDIR}/x11/nvidia-driver +USE_LINUX_APPS+=libglu . endif .else USE_LINUX_APPS+=dri Index: games/linux-savage-samuraiwars/Makefile =================================================================== RCS file: /home/pcvs/ports/games/linux-savage-samuraiwars/Makefile,v retrieving revision 1.3 diff -u -r1.3 Makefile --- games/linux-savage-samuraiwars/Makefile 7 Jun 2009 15:23:53 -0000 1.3 +++ games/linux-savage-samuraiwars/Makefile 14 Sep 2009 09:42:24 -0000 @@ -39,8 +39,8 @@ .if defined(WITH_NVIDIA_GL) . if !exists(${LINUXBASE}/usr/X11R6/lib/libGL.so.1) -RUN_DEPENDS+= ${LINUXBASE}/usr/lib/libGL.so.1:${PORTSDIR}/x11/nvidia-driver \ - ${LINUXBASE}/usr/X11R6/lib/libGLU.so.1:${PORTSDIR}/graphics/linux-libGLU +RUN_DEPENDS+= ${LINUXBASE}/usr/lib/libGL.so.1:${PORTSDIR}/x11/nvidia-driver +USE_LINUX_APPS+=libglu . endif .else USE_LINUX_APPS+=dri Index: games/linux-uplink-demo/Makefile =================================================================== RCS file: /home/pcvs/ports/games/linux-uplink-demo/Makefile,v retrieving revision 1.5 diff -u -r1.5 Makefile --- games/linux-uplink-demo/Makefile 7 Jun 2009 15:23:54 -0000 1.5 +++ games/linux-uplink-demo/Makefile 14 Sep 2009 09:42:24 -0000 @@ -34,8 +34,8 @@ .include .if defined(WITH_NVIDIA) -RUN_DEPENDS+= ${LINUXBASE}/usr/lib/libGL.so.1:${PORTSDIR}/x11/nvidia-driver \ - ${LINUXBASE}/usr/X11R6/lib/libGLU.so.1:${PORTSDIR}/graphics/linux-libGLU +RUN_DEPENDS+= ${LINUXBASE}/usr/lib/libGL.so.1:${PORTSDIR}/x11/nvidia-driver +USE_LINUX_APPS+=libglu .else USE_LINUX_APPS+=dri .endif Index: graphics/linux-ac3d/Makefile =================================================================== RCS file: /home/pcvs/ports/graphics/linux-ac3d/Makefile,v retrieving revision 1.25 diff -u -r1.25 Makefile --- graphics/linux-ac3d/Makefile 7 Jun 2009 15:23:54 -0000 1.25 +++ graphics/linux-ac3d/Makefile 14 Sep 2009 09:42:24 -0000 @@ -19,8 +19,8 @@ COMMENT= Easy to use and powerful 3D graphics modeller (trial version) .ifdef(WITH_NVIDIA_GL) -RUN_DEPENDS+= ${LINUXBASE}/usr/lib/libGL.so.1:${PORTSDIR}/x11/nvidia-driver \ - ${LINUXBASE}/usr/X11R6/lib/libGLU.so.1:${PORTSDIR}/graphics/linux-libGLU +RUN_DEPENDS+= ${LINUXBASE}/usr/lib/libGL.so.1:${PORTSDIR}/x11/nvidia-driver +USE_LINUX_APPS+=libglu .else USE_LINUX_APPS+=dri .endif ----- -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From ivoras at freebsd.org Mon Sep 14 10:30:06 2009 From: ivoras at freebsd.org (Ivan Voras) Date: Mon Sep 14 10:30:13 2009 Subject: New Virtualbox port (from today) In-Reply-To: References: Message-ID: Nenhum_de_Nos wrote: > On Fri, September 11, 2009 11:07, Ivan Voras wrote: >> Hi, >> >> VirtualBox now works with VT and I'm able to run SMP guests! >> >> But apparently it's not very stable (got two boot crashes) and something >> is wrong with timers: > > in my testes, I never got so far as a boot when using any 8.x > >> Example 1: host HZ=250, guest HZ=1000, - guest time apparently speeds up >> more than it should >> >> Example 2: same host, guest HZ=100 - guest time apparently goes 5x >> slower than real (wall) time. >> >> Example 3: same host, guest HZ=25, guest time apparently 2x slower than >> real (wall) time. >> >> In the examples, host is amd64 8-BETA2, 4CPU, guest is 7.2-RELEASE i386, >> 2CPU. > > I tried on a quite close system. intel or amd yours ? Intel. > maybe its time to try again. my system was built from scratch. any > particular tip ? No, nothing unusual or specially configured, except HZ. From ivoras at freebsd.org Mon Sep 14 10:42:20 2009 From: ivoras at freebsd.org (Ivan Voras) Date: Mon Sep 14 10:42:25 2009 Subject: Virtualbox and VRDP In-Reply-To: <4AAD95C2.7040907@kc8onw.net> References: <4AAD95C2.7040907@kc8onw.net> Message-ID: Hi, The last build (virtualbox-3.0.51.r22902) apparently doesn't allow me to start two VMs - the second one always fails with "out of memory". From bugmaster at FreeBSD.org Mon Sep 14 11:06:57 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Sep 14 11:07:49 2009 Subject: Current problem reports assigned to freebsd-emulation@FreeBSD.org Message-ID: <200909141106.n8EB6vXc072286@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/137332 emulation add caution messages to some adobe products f ports/136321 emulation x11-toolkits/linux-pango: please update linux based po o ports/136229 emulation [linux] certain linux apps look for libraries using a o ports/135337 emulation [PATCH] emulators/linux_base-f10: incorrect bash usage o ports/135322 emulation Port graphics/linux_dri has incorrect packaging list c o kern/130724 emulation [linprocfs] [patch] cpuinfo in linprocfs is dated, cau o kern/129169 emulation [linux] [patch] Linux Emulation ENOTCONN error using n f ports/127018 emulation Linuxulator incapable of using FreeBSD's LDAP environm o kern/126232 emulation [linux] Linux ioctl TCGETS (0x5401) always fails o kern/97326 emulation [linux] file descriptor leakage in linux emulation o kern/73777 emulation [linux] [patch] linux emulation: root dir special hand a kern/72920 emulation [linux]: path "prefixing" is not done on unix domain s o kern/56451 emulation [linprocfs] /compat/linux/proc/cpuinfo gives wrong CPU o kern/41543 emulation [patch] [request] easier wine/w23 support o kern/39201 emulation [linux] [patch] ptrace(2) and rfork(RFLINUXTHPN) confu o kern/29698 emulation [linux] [patch] linux ipcs doesn'work o kern/21463 emulation [linux] Linux compatability mode should not allow setu o kern/11165 emulation [ibcs2] IBCS2 doesn't work correctly with PID_MAX 9999 18 problems total. From ivoras at freebsd.org Mon Sep 14 12:08:24 2009 From: ivoras at freebsd.org (Ivan Voras) Date: Mon Sep 14 12:08:31 2009 Subject: Virtualbox and VRDP In-Reply-To: References: <4AAD95C2.7040907@kc8onw.net> Message-ID: Ivan Voras wrote: > Hi, > > The last build (virtualbox-3.0.51.r22902) apparently doesn't allow me to > start two VMs - the second one always fails with "out of memory". Sorry, responded to the wrong post :( From mezz7 at cox.net Mon Sep 14 12:21:26 2009 From: mezz7 at cox.net (Jeremy Messenger) Date: Mon Sep 14 12:21:32 2009 Subject: ports/138752: www/linux-opera does not start In-Reply-To: <76660667@bb.ipt.ru> References: <86iqfn6gfz.fsf@ahab.tihnet> <76660667@bb.ipt.ru> Message-ID: On Mon, 14 Sep 2009 01:56:36 -0500, Boris Samorodov wrote: > On Sat, 12 Sep 2009 17:34:27 -0500 Jeremy Messenger wrote: > >> BTW: Add emulation@ in the CC for they can correct me if I said >> anything wrong with Linux emulation stuff related. > > Jeremy, you are perfectly correct. > > However, I'll advise against other linux base ports than -fc4, > -f8 and -f10. The latter ports have all needed linux infrastructure > ports. Ok, it means that it's best for me to put USE_LINUX=f8 in there instead of f6 or f7. Will it still be able to use f10 if user wants it to be? I don't see anything to add '+' in the document something like USE_LINUX=f8+. > A note: I'll commit the last one for -f10- soon as it has been > just repocopied (it's a graphics/linux-f10-libGLU port). Sounds good. Cheers, Mezz -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org From Gabor at Zahemszky.HU Mon Sep 14 12:30:59 2009 From: Gabor at Zahemszky.HU (Zahemszky =?ISO-8859-2?Q?G=E1bor?=) Date: Mon Sep 14 12:31:05 2009 Subject: virtualbox cannot compile Message-ID: <20090914143057.49808881@Picasso.Zahemszky.HU> Mon, 14 Sep 2009 13:26:02 +0200 -n Gary Jennejohn ?rta: > On Mon, 14 Sep 2009 09:48:05 +0200 > Zahemszky G__bor (by way of Zahemszky G__bor > ) wrote: > > > I've got a problem with the (last two) recent version(s) of the > > emulators/virtualbox port, as I cannot compile it. It fails with a: > > > > 02/src/VBox/Runtime/r0drv/freebsd/alloc-r0drv-freebsd.c:34: > > /sys/vm/vm.h:64:24: error: machine/vm.h: No such file or directory > > > > error message. The previous version failed with the same problem. > > > > Have you generated a kernel lately? I believe machine is a symbolic > link which is created when you make a kernel, but I might be wrong. > > Om my box I > have: /usr/obj/usr/src/sys/amd64/machine > -> /usr/src/sys/amd64/include Hm. Interesting: I've generated kernels in the not too past. But. I use i386, and not amd64, and GENERIC kernel on it. I have /usr/obj/usr/src/sys/ and in it, GENERIC and boot directory. And I have GENERIC/machine/vm.h in it. So I think, some configuration steps have some problems. Zahy < Gabor at Zahemszky dot HU > -- #!/bin/ksh Z='21N16I25C25E30, 40M30E33E25T15U!'; IFS=' ABCDEFGHIJKLMNOPQRSTUVWXYZ '; set -- $Z;for i;{ [[ $i = ? ]]&&print $i&&break; [[ $i = ??? ]]&&j=$i&&i=${i%?}; typeset -i40 i=8#$i;print -n ${i#???}; [[ "$j" = ??? ]]&&print -n "${j#??} "&&j=;typeset +i i;}; IFS=' 0123456789 ';set -- $Z;for i;{ [[ $i = , ]]&&i=2; [[ $i = ?? ]]||typeset -l i;j="$j $i";typeset +l i;};print "$j" From danfe at FreeBSD.org Mon Sep 14 13:29:04 2009 From: danfe at FreeBSD.org (Alexey Dokuchaev) Date: Mon Sep 14 13:29:15 2009 Subject: linux GL libraries and nvidia drivers (was: Re: deprecate some linux ports) In-Reply-To: <90953406@bb.ipt.ru> References: <90953406@bb.ipt.ru> Message-ID: <20090914132904.GA78522@FreeBSD.org> On Thu, Sep 10, 2009 at 10:47:45AM +0400, Boris Samorodov wrote: > BTW, I can create a linux-f10-libGLU port if it is needed. But I'm > not sure if it is needed. > > If I understand the problem with nvidia driver correctly it > installs (and uses) its own linux libGL.so. Hence the problem is > not with libGLU.so but with libGL.so. Correct me if I'm wrong. You're right. > > What if I create a new (say) linux--libGL port with only > libGL libraries and remove them from linux--dri port? > The latter will depend on linux--libGL port. That would probably be ideal. I've seen you committed f10-libGL so I'll play with it and get back to you soon. Thanks! ./danfe From gary.jennejohn at freenet.de Mon Sep 14 13:38:04 2009 From: gary.jennejohn at freenet.de (Gary Jennejohn) Date: Mon Sep 14 13:38:11 2009 Subject: virtualbox cannot compile In-Reply-To: <20090914142916.31e69226@Picasso.Zahemszky.HU> References: <20090914094805.47a01eab@Picasso.Zahemszky.HU> <20090914132602.79faca57@ernst.jennejohn.org> <20090914142916.31e69226@Picasso.Zahemszky.HU> Message-ID: <20090914153800.38fb8e7a@ernst.jennejohn.org> On Mon, 14 Sep 2009 14:29:16 +0200 Zahemszky G__bor wrote: > Mon, 14 Sep 2009 13:26:02 +0200 -n > Gary Jennejohn __rta: > > > On Mon, 14 Sep 2009 09:48:05 +0200 > > Zahemszky G__bor (by way of Zahemszky G__bor > > ) wrote: > > > > > I've got a problem with the (last two) recent version(s) of the > > > emulators/virtualbox port, as I cannot compile it. It fails with a: > > > > > > 02/src/VBox/Runtime/r0drv/freebsd/alloc-r0drv-freebsd.c:34: > > > /sys/vm/vm.h:64:24: error: machine/vm.h: No such file or directory > > > > > > error message. The previous version failed with the same problem. > > > > > > > Have you generated a kernel lately? I believe machine is a symbolic > > link which is created when you make a kernel, but I might be wrong. > > > > Om my box I > > have: /usr/obj/usr/src/sys/amd64/machine > > -> /usr/src/sys/amd64/include > > Hm. Interesting: I've generated kernels in the not too past. But. I use > i386, and not amd64, and GENERIC kernel on it. I > have /usr/obj/usr/src/sys/ and in it, GENERIC and boot directory. And I > have GENERIC/machine/vm.h in it. So I think, some configuration steps > have some problems. > I just compiled the latest svn stuff and it also fails (copy&paste => long lines): kBuild: Compiling vboxnetflt - /oldzfs/virtualbox/work/virtualbox-3.0.51r22902/src/VBox/HostDrivers/VBoxNetFlt/freebsd/VBoxNetFlt-freebsd.c In file included from /oldzfs/virtualbox/work/virtualbox-3.0.51r22902/src/VBox/HostDrivers/VBoxNetFlt/freebsd/VBoxNetFlt-freebsd.c:43: /sys/sys/socket.h:39:28: error: machine/_align.h: No such file or directory kmk[2]: *** [/oldzfs/virtualbox/work/virtualbox-3.0.51r22902/out/freebsd.amd64/release/obj/vboxnetflt/freebsd/VBoxNetFlt-freebsd.o] Error 1 The failing command: @cc -c -O2 -Wall -Wextra -Wno-missing-field-initializers -Wno-unused -Wno-trigraphs -Wpointer-arith -Winline -Wno-pointer-sign -Wstrict-prototypes -Wmissing-prototypes -Wstrict-prototypes -Wnested-externs -O2 -fformat-extensions -ffreestanding -fno-strict-aliasing -fno-common -finline-limit=8000 -fno-stack-protector -O2 -mtune=generic -fno-omit-frame-pointer -nostdinc -std=c99 -m64 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -Wundef -I/oldzfs/virtualbox/work/virtualbox-3.0.51r22902/src/VBox/HostDrivers/VBoxNetFlt -I/sys -I/sys/contrib/altq -I/sys/../include -I/usr/include -I/oldzfs/virtualbox/work/virtualbox-3.0.51r22902/include -I/oldzfs/virtualbox/work/virtualbox-3.0.51r22902/out/freebsd.amd64/release -DVBOX -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_HARDENING -DRTPATH_APP_PRIVATE=\"/usr/local/share/virtualbox\" -DRTPATH_APP_PRIVATE_ARCH=\"/usr/local/lib/virtualbox\" -DRTPATH_SHARED_LIBS=\"/usr/local/lib/virtualbox\" -DRTPATH_APP_DOCS=\"/usr/local/share/doc/virtualbox\" -DRT_OS_FREEBSD -D__FREEBSD__ -DRT_ARCH_AMD64 -D__AMD64__ -D_KERNEL -DKLD_MODULE -DIN_RING0 -DIN_RT_R0 -DIN_RT_R0 -Wp,-MD,/oldzfs/virtualbox/work/virtualbox-3.0.51r22902/out/freebsd.amd64/release/obj/vboxnetflt/freebsd/VBoxNetFlt-freebsd.o.dep -Wp,-MT,/oldzfs/virtualbox/work/virtualbox-3.0.51r22902/out/freebsd.amd64/release/obj/vboxnetflt/freebsd/VBoxNetFlt-freebsd.o -Wp,-MP -o /oldzfs/virtualbox/work/virtualbox-3.0.51r22902/out/freebsd.amd64/release/obj/vboxnetflt/freebsd/VBoxNetFlt-freebsd.o /oldzfs/virtualbox/work/virtualbox-3.0.51r22902/src/VBox/HostDrivers/VBoxNetFlt/freebsd/VBoxNetFlt-freebsd.c Definitely looks like there's a bug in the new networking stuff. --- Gary Jennejohn From ivoras at freebsd.org Mon Sep 14 14:21:13 2009 From: ivoras at freebsd.org (Ivan Voras) Date: Mon Sep 14 14:21:21 2009 Subject: New Virtualbox port (from today) In-Reply-To: References: Message-ID: Hi, It looks like the timer problem is solved with the recent port (virtualbox-3.0.51.r22902) but now I cannot start more than one VM - the error is VERR_NO_MEMORY (there certainly is enough free memory). From bsam at ipt.ru Mon Sep 14 14:50:21 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Mon Sep 14 14:50:29 2009 Subject: ports/138752: www/linux-opera does not start In-Reply-To: (Jeremy Messenger's message of "Mon, 14 Sep 2009 07:23:45 -0500") References: <86iqfn6gfz.fsf@ahab.tihnet> <76660667@bb.ipt.ru> Message-ID: <80174211@bb.ipt.ru> On Mon, 14 Sep 2009 07:23:45 -0500 Jeremy Messenger wrote: > On Mon, 14 Sep 2009 01:56:36 -0500, Boris Samorodov wrote: > > On Sat, 12 Sep 2009 17:34:27 -0500 Jeremy Messenger wrote: > > > >> BTW: Add emulation@ in the CC for they can correct me if I said > >> anything wrong with Linux emulation stuff related. > > > > Jeremy, you are perfectly correct. > > > > However, I'll advise against other linux base ports than -fc4, > > -f8 and -f10. The latter ports have all needed linux infrastructure > > ports. > Ok, it means that it's best for me to put USE_LINUX=f8 in there > instead of f6 or f7. USE_LINUX does nor support it. I mean there is no possibility to define a linux distro ATM. The only option is to use USE_LINUX=yes. The only way is to check for OSVERSION and if OVERRIDE_LINUX_NONBASE_PORTS is defined. You may look at emulators/linux-systemsimcell for an examples. > Will it still be able to use f10 if user wants it > to be? I don't see anything to add '+' in the document something like > USE_LINUX=f8+. Yes, no one including me have written such support so far. -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From bsam at ipt.ru Mon Sep 14 14:53:24 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Mon Sep 14 14:53:30 2009 Subject: linux GL libraries and nvidia drivers In-Reply-To: <20090914132904.GA78522@FreeBSD.org> (Alexey Dokuchaev's message of "Mon, 14 Sep 2009 13:29:04 +0000") References: <90953406@bb.ipt.ru> <20090914132904.GA78522@FreeBSD.org> Message-ID: <98098491@bb.ipt.ru> On Mon, 14 Sep 2009 13:29:04 +0000 Alexey Dokuchaev wrote: > On Thu, Sep 10, 2009 at 10:47:45AM +0400, Boris Samorodov wrote: > > What if I create a new (say) linux--libGL port with only > > libGL libraries and remove them from linux--dri port? > > The latter will depend on linux--libGL port. > That would probably be ideal. I've seen you committed f10-libGL so I'll > play with it and get back to you soon. I didn't remove libGL, just mark those ports CONFLICTS. Seems that it is a best choice just before a release. -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From dnelson at allantgroup.com Mon Sep 14 15:55:45 2009 From: dnelson at allantgroup.com (Dan Nelson) Date: Mon Sep 14 15:55:52 2009 Subject: Virtualbox and VRDP In-Reply-To: <29e884c4b57123a181fb162710e6d1d0.squirrel@webmail.itac.at> References: <4AAD95C2.7040907@kc8onw.net> <29e884c4b57123a181fb162710e6d1d0.squirrel@webmail.itac.at> Message-ID: <20090914155543.GA40881@dan.emsphone.com> In the last episode (Sep 14), Bernhard Froehlich said: > On Mon, September 14, 2009 3:00 am, Jonathan wrote: > > I just installed virtualbox on my server without X11 support intending > > to run it headless and now I find that the Virtual Remote Display > > Protocol support is only available in the closed source version. The > > virtualbox Editions page says that some of the closed source features > > may eventually become available in the open source version as well, has > > anyone heard anything about this happening for VRDP? > > > > Are there any other options that would allow me to set up a VM remotely > > without installing X? I suppose I could set up a VM locally and then > > copy it to my server once it's configured for remote ssh access but that > > would involve copying several GB over the internet, a rather slow > > process on my connection. > > You can setup your virtual machine with VBoxManage but installing a system > in it is rather painful without GUI. The way you described is my > preferred at the moment but you could also install with X11 and use > VBoxSDL and X11 forwarding. > > I've talked to the vbox developers and they don't think that the RDP code > will be put opensource in the foreseeable future. That's a pity because > in combination with vboxweb [0] which is a python web interface to vbox > that includes a Flash based RDP client this would be a great headless > solution. What I do is run vncserver, VNC to that virtual X11 session, then run my VirtualBox sessions under there. Maybe someone could add VNC support to vbox using libvncserver? http://sourceforge.net/projects/libvncserver/ -- Dan Nelson dnelson@allantgroup.com From oberman at es.net Mon Sep 14 15:58:13 2009 From: oberman at es.net (Kevin Oberman) Date: Mon Sep 14 15:58:21 2009 Subject: New network capabilities? Message-ID: <20090914155807.5ED7B1CC37@ptavv.es.net> I see that the new port of VB seems to have added a couple of kernel modules that are probably network related: vboxnetadp.ko and vboxnetflt.ko. Do these provide new networking options? I have seen quite a bit of discussion of new network code on this list, but I am not sure exactly what they cover or how to use them and I don't see much on the wiki, but it looks like TAP is now available. Any clues for the clueless? -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 From avg at icyb.net.ua Mon Sep 14 16:01:56 2009 From: avg at icyb.net.ua (Andriy Gapon) Date: Mon Sep 14 16:02:02 2009 Subject: New Virtualbox port (from today) In-Reply-To: References: Message-ID: <4AAE68F1.3010709@icyb.net.ua> on 14/09/2009 17:21 Ivan Voras said the following: > Hi, > > It looks like the timer problem is solved with the recent port > (virtualbox-3.0.51.r22902) but now I cannot start more than one VM - the > error is VERR_NO_MEMORY (there certainly is enough free memory). Could this be related to a similar issue that I reported on -current? Or something too different? -- Andriy Gapon From fli at shapeshifter.se Mon Sep 14 16:12:01 2009 From: fli at shapeshifter.se (Fredrik Lindberg) Date: Mon Sep 14 16:12:06 2009 Subject: New network capabilities? In-Reply-To: <20090914155807.5ED7B1CC37@ptavv.es.net> References: <20090914155807.5ED7B1CC37@ptavv.es.net> Message-ID: <4AAE6B4A.8090905@shapeshifter.se> Kevin Oberman wrote: > I see that the new port of VB seems to have added a couple of kernel > modules that are probably network related: vboxnetadp.ko and > vboxnetflt.ko. > > Do these provide new networking options? I have seen quite a bit of > discussion of new network code on this list, but I am not sure exactly > what they cover or how to use them and I don't see much on the wiki, but > it looks like TAP is now available. > > Any clues for the clueless? They implement "Bridge Adapter" (vboxnetflt) and "Host-only Adapter" (vboxnetadp). Bridge is what it sounds like, it will bridge the guest interface with a physical interface. So, if you want your guest to be a part of your network, select "Bridge Adapter" and the select your physical ethernet interface in the drop-down list. Host-only adapter can be used to create a virtual network among guests and the physical machine. It creates a vboxnetX interface that acts like it's connected to a separate ethernet segment to which the guests are connected. I don't know how the TAP stuff works. Fredrik From fli at shapeshifter.se Mon Sep 14 16:42:05 2009 From: fli at shapeshifter.se (Fredrik Lindberg) Date: Mon Sep 14 16:42:11 2009 Subject: virtualbox cannot compile In-Reply-To: <20090914153800.38fb8e7a@ernst.jennejohn.org> References: <20090914094805.47a01eab@Picasso.Zahemszky.HU> <20090914132602.79faca57@ernst.jennejohn.org> <20090914142916.31e69226@Picasso.Zahemszky.HU> <20090914153800.38fb8e7a@ernst.jennejohn.org> Message-ID: <4AAE7259.80200@shapeshifter.se> Gary Jennejohn wrote: > On Mon, 14 Sep 2009 14:29:16 +0200 > Zahemszky G__bor wrote: > >> Mon, 14 Sep 2009 13:26:02 +0200 -n >> Gary Jennejohn __rta: >> >>> On Mon, 14 Sep 2009 09:48:05 +0200 >>> Zahemszky G__bor (by way of Zahemszky G__bor >>> ) wrote: >>> >>>> I've got a problem with the (last two) recent version(s) of the >>>> emulators/virtualbox port, as I cannot compile it. It fails with a: >>>> >>>> 02/src/VBox/Runtime/r0drv/freebsd/alloc-r0drv-freebsd.c:34: >>>> /sys/vm/vm.h:64:24: error: machine/vm.h: No such file or directory >>>> >>>> error message. The previous version failed with the same problem. >>>> >>> Have you generated a kernel lately? I believe machine is a symbolic >>> link which is created when you make a kernel, but I might be wrong. >>> >>> Om my box I >>> have: /usr/obj/usr/src/sys/amd64/machine >>> -> /usr/src/sys/amd64/include >> Hm. Interesting: I've generated kernels in the not too past. But. I use >> i386, and not amd64, and GENERIC kernel on it. I >> have /usr/obj/usr/src/sys/ and in it, GENERIC and boot directory. And I >> have GENERIC/machine/vm.h in it. So I think, some configuration steps >> have some problems. >> > > I just compiled the latest svn stuff and it also fails (copy&paste => long lines): > > kBuild: Compiling vboxnetflt - /oldzfs/virtualbox/work/virtualbox-3.0.51r22902/src/VBox/HostDrivers/VBoxNetFlt/freebsd/VBoxNetFlt-freebsd.c > In file included from /oldzfs/virtualbox/work/virtualbox-3.0.51r22902/src/VBox/HostDrivers/VBoxNetFlt/freebsd/VBoxNetFlt-freebsd.c:43: > /sys/sys/socket.h:39:28: error: machine/_align.h: No such file or directory > kmk[2]: *** [/oldzfs/virtualbox/work/virtualbox-3.0.51r22902/out/freebsd.amd64/release/obj/vboxnetflt/freebsd/VBoxNetFlt-freebsd.o] Error 1 > The failing command: > @cc -c -O2 -Wall -Wextra -Wno-missing-field-initializers -Wno-unused > -Wno-trigraphs -Wpointer-arith -Winline -Wno-pointer-sign -Wstrict-prototypes > -Wmissing-prototypes -Wstrict-prototypes -Wnested-externs -O2 > -fformat-extensions -ffreestanding -fno-strict-aliasing -fno-common > -finline-limit=8000 -fno-stack-protector -O2 -mtune=generic > -fno-omit-frame-pointer -nostdinc -std=c99 -m64 --param inline-unit-growth=100 > --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel > -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float > -fno-asynchronous-unwind-tables -Wundef > -I/oldzfs/virtualbox/work/virtualbox-3.0.51r22902/src/VBox/HostDrivers/VBoxNetFlt > -I/sys -I/sys/contrib/altq -I/sys/../include -I/usr/include > -I/oldzfs/virtualbox/work/virtualbox-3.0.51r22902/include > -I/oldzfs/virtualbox/work/virtualbox-3.0.51r22902/out/freebsd.amd64/release > -DVBOX -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_HARDENING > -DRTPATH_APP_PRIVATE=\"/usr/local/share/virtualbox\" > -DRTPATH_APP_PRIVATE_ARCH=\"/usr/local/lib/virtualbox\" > -DRTPATH_SHARED_LIBS=\"/usr/local/lib/virtualbox\" > -DRTPATH_APP_DOCS=\"/usr/local/share/doc/virtualbox\" -DRT_OS_FREEBSD > -D__FREEBSD__ -DRT_ARCH_AMD64 -D__AMD64__ -D_KERNEL -DKLD_MODULE -DIN_RING0 > -DIN_RT_R0 -DIN_RT_R0 > -Wp,-MD,/oldzfs/virtualbox/work/virtualbox-3.0.51r22902/out/freebsd.amd64/release/obj/vboxnetflt/freebsd/VBoxNetFlt-freebsd.o.dep > -Wp,-MT,/oldzfs/virtualbox/work/virtualbox-3.0.51r22902/out/freebsd.amd64/release/obj/vboxnetflt/freebsd/VBoxNetFlt-freebsd.o > -Wp,-MP > -o /oldzfs/virtualbox/work/virtualbox-3.0.51r22902/out/freebsd.amd64/release/obj/vboxnetflt/freebsd/VBoxNetFlt-freebsd.o /oldzfs/virtualbox/work/virtualbox-3.0.51r22902/src/VBox/HostDrivers/VBoxNetFlt/freebsd/VBoxNetFlt-freebsd.c > > Definitely looks like there's a bug in the new networking stuff. It compiles fine for me on FreeBSD 7.2-amd64 using the latest version in ports, builds both vboxnetflt.ko and vboxnetadp.ko. Have you tried the one in ports (although I can't imagine why the svn-version wouldn't work)? What version of FreeBSD are you using ? Fredrik From gary.jennejohn at freenet.de Mon Sep 14 17:01:39 2009 From: gary.jennejohn at freenet.de (Gary Jennejohn) Date: Mon Sep 14 17:01:46 2009 Subject: virtualbox cannot compile In-Reply-To: <4AAE7259.80200@shapeshifter.se> References: <20090914094805.47a01eab@Picasso.Zahemszky.HU> <20090914132602.79faca57@ernst.jennejohn.org> <20090914142916.31e69226@Picasso.Zahemszky.HU> <20090914153800.38fb8e7a@ernst.jennejohn.org> <4AAE7259.80200@shapeshifter.se> Message-ID: <20090914190136.773147aa@ernst.jennejohn.org> On Mon, 14 Sep 2009 18:42:01 +0200 Fredrik Lindberg wrote: [big snip] Gary Jennejohn wrote: > > Definitely looks like there's a bug in the new networking stuff. > > It compiles fine for me on FreeBSD 7.2-amd64 using the latest version > in ports, builds both vboxnetflt.ko and vboxnetadp.ko. Have you > tried the one in ports (although I can't imagine why the svn-version > wouldn't work)? What version of FreeBSD are you using ? > 9-current amd64. I didn't try the port. Hmm. My sources are newer than the kernel I'm using. Don't know whether that is a factor or not. --- Gary Jennejohn From mlobo at digiart.art.br Mon Sep 14 17:35:17 2009 From: mlobo at digiart.art.br (Mario Lobo) Date: Mon Sep 14 17:35:24 2009 Subject: virtualbox cannot compile In-Reply-To: <20090914190136.773147aa@ernst.jennejohn.org> References: <20090914094805.47a01eab@Picasso.Zahemszky.HU> <20090914132602.79faca57@ernst.jennejohn.org> <20090914142916.31e69226@Picasso.Zahemszky.HU> <20090914153800.38fb8e7a@ernst.jennejohn.org> <4AAE7259.80200@shapeshifter.se> <20090914190136.773147aa@ernst.jennejohn.org> Message-ID: <29199.200.249.56.17.1252949706.squirrel@squirrel.sv4.hmnoc.net> > On Mon, 14 Sep 2009 18:42:01 +0200 > Fredrik Lindberg wrote: > > [big snip] > Gary Jennejohn wrote: >> > Definitely looks like there's a bug in the new networking stuff. >> >> It compiles fine for me on FreeBSD 7.2-amd64 using the latest version >> in ports, builds both vboxnetflt.ko and vboxnetadp.ko. Have you >> tried the one in ports (although I can't imagine why the svn-version >> wouldn't work)? What version of FreeBSD are you using ? >> > > 9-current amd64. > > I didn't try the port. > > Hmm. My sources are newer than the kernel I'm using. Don't know whether > that is a factor or not. > > --- That was definetly a factor for me. I had a backup I made of /usr/src just before csuping a new source tree, which issued the same error you are getting. As soon as I restored to the old /usr/src, Vbox compiled without errors. The error I kept getting was machine/vm.h: No such file or directory On my new /usr/src, /usr/src/sys/vm/vm.h has a # include directive which the old source does not. Mario Lobo From jonathan at kc8onw.net Mon Sep 14 17:53:42 2009 From: jonathan at kc8onw.net (Jonathan) Date: Mon Sep 14 17:53:49 2009 Subject: Virtualbox and VRDP In-Reply-To: <20090914155543.GA40881@dan.emsphone.com> References: <4AAD95C2.7040907@kc8onw.net> <29e884c4b57123a181fb162710e6d1d0.squirrel@webmail.itac.at> <20090914155543.GA40881@dan.emsphone.com> Message-ID: <4AAE8324.6020803@kc8onw.net> On 9/14/2009 11:55 AM, Dan Nelson wrote: > In the last episode (Sep 14), Bernhard Froehlich said: >> On Mon, September 14, 2009 3:00 am, Jonathan wrote: >>> I just installed virtualbox on my server without X11 support >>> intending to run it headless and now I find that the Virtual >>> Remote Display Protocol support is only available in the closed >>> source version. The virtualbox Editions page says that some of >>> the closed source features may eventually become available in the >>> open source version as well, has anyone heard anything about this >>> happening for VRDP? >>> >>> Are there any other options that would allow me to set up a VM >>> remotely without installing X? I suppose I could set up a VM >>> locally and then copy it to my server once it's configured for >>> remote ssh access but that would involve copying several GB over >>> the internet, a rather slow process on my connection. >> >> You can setup your virtual machine with VBoxManage but installing a >> system in it is rather painful without GUI. The way you described >> is my preferred at the moment but you could also install with X11 >> and use VBoxSDL and X11 forwarding. >> >> I've talked to the vbox developers and they don't think that the >> RDP code will be put opensource in the foreseeable future. That's >> a pity because in combination with vboxweb [0] which is a python >> web interface to vbox that includes a Flash based RDP client this >> would be a great headless solution. > > What I do is run vncserver, VNC to that virtual X11 session, then run > my VirtualBox sessions under there. I'm trying to avoid installing X on the server at all or this would be an option. > Maybe someone could add VNC support to vbox using libvncserver? > http://sourceforge.net/projects/libvncserver/ It's a good idea but I personally don't have the time :( Jonathan From mezz7 at cox.net Mon Sep 14 18:17:00 2009 From: mezz7 at cox.net (Jeremy Messenger) Date: Mon Sep 14 18:17:06 2009 Subject: ports/138752: www/linux-opera does not start In-Reply-To: <80174211@bb.ipt.ru> References: <86iqfn6gfz.fsf@ahab.tihnet> <76660667@bb.ipt.ru> <80174211@bb.ipt.ru> Message-ID: On Mon, 14 Sep 2009 09:50:20 -0500, Boris Samorodov wrote: > On Mon, 14 Sep 2009 07:23:45 -0500 Jeremy Messenger wrote: >> On Mon, 14 Sep 2009 01:56:36 -0500, Boris Samorodov wrote: >> > On Sat, 12 Sep 2009 17:34:27 -0500 Jeremy Messenger wrote: >> > >> >> BTW: Add emulation@ in the CC for they can correct me if I said >> >> anything wrong with Linux emulation stuff related. >> > >> > Jeremy, you are perfectly correct. >> > >> > However, I'll advise against other linux base ports than -fc4, >> > -f8 and -f10. The latter ports have all needed linux infrastructure >> > ports. > >> Ok, it means that it's best for me to put USE_LINUX=f8 in there >> instead of f6 or f7. > > USE_LINUX does nor support it. I mean there is no possibility to > define a linux distro ATM. The only option is to use USE_LINUX=yes. > The only way is to check for OSVERSION and if > OVERRIDE_LINUX_NONBASE_PORTS is defined. You may look at > emulators/linux-systemsimcell for an examples. See in the Mk/bsd.port.mk: =================================== # USE_LINUX - Set to yes to say the port needs the default linux base port. # Set to value , if the port needs emulators/linux_base-. # If set to "7", a dependency is registered to emulators/linux_base. ------------------------------------ With USE_LINUX=yes: ------------------------------------ # make all-depends-list | grep base /usr/ports/emulators/linux_base-fc4 ------------------------------------ With USE_LINUX=f8: ------------------------------------ # make all-depends-list | grep base /usr/ports/emulators/linux_base-f8 /usr/ports/emulators/linux_base-fc4 ------------------------------------ Looks like it's a bug. Also the document needs to be update if it doesn't support. >> Will it still be able to use f10 if user wants it >> to be? I don't see anything to add '+' in the document something like >> USE_LINUX=f8+. > > Yes, no one including me have written such support so far. Ok thanks, I shall check in emulators/linux-systemsimcell. Cheers, Mezz -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org From Alexander at Leidinger.net Tue Sep 15 09:08:18 2009 From: Alexander at Leidinger.net (Alexander Leidinger) Date: Tue Sep 15 09:08:28 2009 Subject: Buffer overflow detected by REDZONE with linuxulator In-Reply-To: References: Message-ID: <20090915110806.13816i8eowbecwkc@webmail.leidinger.net> Quoting Alexander Best (from Wed, 09 Sep 2009 19:01:31 +0200 (CEST)): > hi there, CCing emulation@, this is better suited there. Full quote for the benefit of the emulation@ readers. Please drop hackers@ on reply. Thanks. > i've installed emulators/linux_dist-gentoo-stage3 and grabbed a snapshot from > the ltp git repository (http://ltp.sourceforge.net/). as expected some tests > failed because i'm using compat.linux.osrelease: 2.6.16 which is > still missing > a few linux syscalls, ipcs and ioctls. Are you interested to help update the corresponding FreeBSD wiki page? If yes, register there and we can hand out write access. > however i also noticed REDZONE reporting buffer overflows. i'm only > a user and > not a developer so i don't know if the ltp is to be blamed or if the problem > lies within the linuxulator. Probably the later... > i'm running 9.0-CURRENT (r196879). as i mentioned before i'm using 2.6 linux > kernel emulation. here are the buffer overflow reports: Is your system running in 32bit or 64bit mode? Do you know which ltp-tests cause those messages to appear? Bye, Alexander. > Sep 9 14:12:42 otaku kernel: REDZONE: Buffer overflow detected. 9 bytes > corrupted after 0xcc28c483 (3 bytes allocated). > Sep 9 14:12:42 otaku kernel: Allocation backtrace: > Sep 9 14:12:42 otaku kernel: #0 0xc0709aaa at redzone_setup+0x3a > Sep 9 14:12:42 otaku kernel: #1 0xc05bc673 at malloc+0x1c3 > Sep 9 14:12:42 otaku kernel: #2 0xc07428b8 at linux_getsockaddr+0x48 > Sep 9 14:12:42 otaku kernel: #3 0xc0742eb8 at linux_socketcall+0x178 > Sep 9 14:12:42 otaku kernel: #4 0xc0772f56 at syscall+0x2a6 > Sep 9 14:12:42 otaku kernel: #5 0xc07568b0 at Xint0x80_syscall+0x20 > Sep 9 14:12:42 otaku kernel: Free backtrace: > Sep 9 14:12:42 otaku kernel: #0 0xc0709a3a at redzone_check+0x17a > Sep 9 14:12:42 otaku kernel: #1 0xc05bc32d at free+0x5d > Sep 9 14:12:42 otaku kernel: #2 0xc0742ef0 at linux_socketcall+0x1b0 > Sep 9 14:12:42 otaku kernel: #3 0xc0772f56 at syscall+0x2a6 > Sep 9 14:12:42 otaku kernel: #4 0xc07568b0 at Xint0x80_syscall+0x20 > Sep 9 14:20:08 otaku kernel: REDZONE: Buffer overflow detected. 4 bytes > corrupted after 0xcc2538ea (106 bytes allocated). > Sep 9 14:20:08 otaku kernel: Allocation backtrace: > Sep 9 14:20:08 otaku kernel: #0 0xc0709aaa at redzone_setup+0x3a > Sep 9 14:20:08 otaku kernel: #1 0xc05bc673 at malloc+0x1c3 > Sep 9 14:20:08 otaku kernel: #2 0xc063a902 at unp_connect+0x162 > Sep 9 14:20:08 otaku kernel: #3 0xc063d6c9 at uipc_connect+0x49 > Sep 9 14:20:08 otaku kernel: #4 0xc062fde2 at soconnect+0x52 > Sep 9 14:20:08 otaku kernel: #5 0xc0638eb6 at kern_connect+0x96 > Sep 9 14:20:08 otaku kernel: #6 0xc0742c7b at linux_connect+0x3b > Sep 9 14:20:08 otaku kernel: #7 0xc0742f22 at linux_socketcall+0x1e2 > Sep 9 14:20:08 otaku kernel: #8 0xc0772f56 at syscall+0x2a6 > Sep 9 14:20:08 otaku kernel: #9 0xc07568b0 at Xint0x80_syscall+0x20 > Sep 9 14:20:08 otaku kernel: Free backtrace: > Sep 9 14:20:08 otaku kernel: #0 0xc0709a3a at redzone_check+0x17a > Sep 9 14:20:08 otaku kernel: #1 0xc05bc32d at free+0x5d > Sep 9 14:20:08 otaku kernel: #2 0xc063bfb2 at uipc_detach+0x242 > Sep 9 14:20:08 otaku kernel: #3 0xc0632a7e at sofree+0x22e > Sep 9 14:20:08 otaku kernel: #4 0xc0632f26 at soclose+0x386 > Sep 9 14:20:08 otaku kernel: #5 0xc0617c49 at soo_close+0x29 > Sep 9 14:20:08 otaku kernel: #6 0xc0598b13 at _fdrop+0x43 > Sep 9 14:20:08 otaku kernel: #7 0xc059ab90 at closef+0x290 > Sep 9 14:20:08 otaku kernel: #8 0xc059af22 at kern_close+0x102 > Sep 9 14:20:08 otaku kernel: #9 0xc059b09a at close+0x1a > Sep 9 14:20:08 otaku kernel: #10 0xc0772f56 at syscall+0x2a6 > Sep 9 14:20:08 otaku kernel: #11 0xc07568b0 at Xint0x80_syscall+0x20 > Sep 9 14:20:09 otaku kernel: REDZONE: Buffer overflow detected. 4 bytes > corrupted after 0xccc653ea (106 bytes allocated). > Sep 9 14:20:09 otaku kernel: Allocation backtrace: > Sep 9 14:20:09 otaku kernel: #0 0xc0709aaa at redzone_setup+0x3a > Sep 9 14:20:09 otaku kernel: #1 0xc05bc673 at malloc+0x1c3 > Sep 9 14:20:09 otaku kernel: #2 0xc063a902 at unp_connect+0x162 > Sep 9 14:20:09 otaku kernel: #3 0xc063d6c9 at uipc_connect+0x49 > Sep 9 14:20:09 otaku kernel: #4 0xc062fde2 at soconnect+0x52 > Sep 9 14:20:09 otaku kernel: #5 0xc0638eb6 at kern_connect+0x96 > Sep 9 14:20:09 otaku kernel: #6 0xc0742c7b at linux_connect+0x3b > Sep 9 14:20:09 otaku kernel: #7 0xc0742f22 at linux_socketcall+0x1e2 > Sep 9 14:20:09 otaku kernel: #8 0xc0772f56 at syscall+0x2a6 > Sep 9 14:20:09 otaku kernel: #9 0xc07568b0 at Xint0x80_syscall+0x20 > Sep 9 14:20:09 otaku kernel: Free backtrace: > Sep 9 14:20:09 otaku kernel: #0 0xc0709a3a at redzone_check+0x17a > Sep 9 14:20:09 otaku kernel: #1 0xc05bc32d at free+0x5d > Sep 9 14:20:09 otaku kernel: #2 0xc063bfb2 at uipc_detach+0x242 > Sep 9 14:20:09 otaku kernel: #3 0xc0632a7e at sofree+0x22e > Sep 9 14:20:09 otaku kernel: #4 0xc0632f26 at soclose+0x386 > Sep 9 14:20:09 otaku kernel: #5 0xc0617c49 at soo_close+0x29 > Sep 9 14:20:09 otaku kernel: #6 0xc0598b13 at _fdrop+0x43 > Sep 9 14:20:09 otaku kernel: #7 0xc059ab90 at closef+0x290 > Sep 9 14:20:09 otaku kernel: #8 0xc059af22 at kern_close+0x102 > Sep 9 14:20:09 otaku kernel: #9 0xc059b09a at close+0x1a > Sep 9 14:20:09 otaku kernel: #10 0xc0772f56 at syscall+0x2a6 > Sep 9 14:20:09 otaku kernel: #11 0xc07568b0 at Xint0x80_syscall+0x20 > Sep 9 14:20:09 otaku kernel: REDZONE: Buffer overflow detected. 4 bytes > corrupted after 0xcf45a9ea (106 bytes allocated). > Sep 9 14:20:09 otaku kernel: Allocation backtrace: > Sep 9 14:20:09 otaku kernel: #0 0xc0709aaa at redzone_setup+0x3a > Sep 9 14:20:09 otaku kernel: #1 0xc05bc673 at malloc+0x1c3 > Sep 9 14:20:09 otaku kernel: #2 0xc063a902 at unp_connect+0x162 > Sep 9 14:20:09 otaku kernel: #3 0xc063d6c9 at uipc_connect+0x49 > Sep 9 14:20:09 otaku kernel: #4 0xc062fde2 at soconnect+0x52 > Sep 9 14:20:09 otaku kernel: #5 0xc0638eb6 at kern_connect+0x96 > Sep 9 14:20:09 otaku kernel: #6 0xc0742c7b at linux_connect+0x3b > Sep 9 14:20:09 otaku kernel: #7 0xc0742f22 at linux_socketcall+0x1e2 > Sep 9 14:20:09 otaku kernel: #8 0xc0772f56 at syscall+0x2a6 > Sep 9 14:20:09 otaku kernel: #9 0xc07568b0 at Xint0x80_syscall+0x20 > Sep 9 14:20:09 otaku kernel: Free backtrace: > Sep 9 14:20:09 otaku kernel: #0 0xc0709a3a at redzone_check+0x17a > Sep 9 14:20:09 otaku kernel: #1 0xc05bc32d at free+0x5d > Sep 9 14:20:09 otaku kernel: #2 0xc063bfb2 at uipc_detach+0x242 > Sep 9 14:20:09 otaku kernel: #3 0xc0632a7e at sofree+0x22e > Sep 9 14:20:09 otaku kernel: #4 0xc0632f26 at soclose+0x386 > Sep 9 14:20:09 otaku kernel: #5 0xc0617c49 at soo_close+0x29 > Sep 9 14:20:09 otaku kernel: #6 0xc0598b13 at _fdrop+0x43 > Sep 9 14:20:09 otaku kernel: #7 0xc059ab90 at closef+0x290 > Sep 9 14:20:09 otaku kernel: #8 0xc059b55a at fdfree+0x3ea > Sep 9 14:20:09 otaku kernel: #9 0xc05a57b3 at exit1+0x513 > Sep 9 14:20:09 otaku kernel: #10 0xc05d17f4 at sigexit+0xa14 > Sep 9 14:20:09 otaku kernel: #11 0xc05d19fd at postsig+0x1dd > Sep 9 14:20:09 otaku kernel: #12 0xc0608fca at ast+0x35a > Sep 9 14:20:09 otaku kernel: #13 0xc0757174 at doreti_ast+0x17 > > cheers. > alex -- Fifth Law of Procrastination: Procrastination avoids boredom; one never has the feeling that there is nothing important to do. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From ivoras at freebsd.org Tue Sep 15 09:19:52 2009 From: ivoras at freebsd.org (Ivan Voras) Date: Tue Sep 15 09:19:59 2009 Subject: New Virtualbox port (from today) In-Reply-To: <4AAE68F1.3010709@icyb.net.ua> References: <4AAE68F1.3010709@icyb.net.ua> Message-ID: Andriy Gapon wrote: > on 14/09/2009 17:21 Ivan Voras said the following: >> Hi, >> >> It looks like the timer problem is solved with the recent port >> (virtualbox-3.0.51.r22902) but now I cannot start more than one VM - the >> error is VERR_NO_MEMORY (there certainly is enough free memory). > > Could this be related to a similar issue that I reported on -current? > Or something too different? It looks almost exactly the same as your issue except that I really do have enough memory: 00:00:00.681 VirtualBox 3.0.51_OSE r22900 freebsd.amd64 (Sep 14 2009 12:31:13) release log 00:00:00.681 Log opened 2009-09-14T14:20:25.014346000Z 00:00:00.681 OS Product: FreeBSD 00:00:00.681 OS Release: 8.0-BETA2 00:00:00.681 OS Version: FreeBSD 8.0-BETA2 #5: Mon Aug 17 11:29:21 CEST 2009 ivoras@lara.cc.fer.hr:/usr/obj/usr/src/sys/LARA !!! 00:00:00.681 Host RAM: 3823MB RAM, available: 508MB !!! 00:00:00.681 Executable: /usr/local/lib/virtualbox/VirtualBox 00:00:00.681 Process ID: 1217 00:00:00.681 Package type: BSD_64BITS_GENERIC (OSE) 00:00:00.685 SUP: Opened VMMR0.r0 (/usr/local/lib/virtualbox/VMMR0.r0) at 0xffffffff81062080. 00:00:00.686 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={0a51994b-cbc6-4686-94eb-d4e4023280e2} aComponent={Console} aText={VM creation failed (GVMM) (VERR_NO_MEMORY). 00:00:00.686 Unknown error creating VM (VERR_NO_MEMORY)} aWarning=false, preserve=false 00:00:00.688 Power up failed (vrc=VERR_NO_MEMORY, rc=NS_ERROR_FAILURE (0X80004005)) The VM is configured as 128 MB memory. From alexbestms at math.uni-muenster.de Tue Sep 15 12:03:50 2009 From: alexbestms at math.uni-muenster.de (Alexander Best) Date: Tue Sep 15 12:03:56 2009 Subject: Buffer overflow detected by REDZONE with linuxulator In-Reply-To: <20090915110806.13816i8eowbecwkc@webmail.leidinger.net> Message-ID: Alexander Leidinger schrieb am 2009-09-15: > Are you interested to help update the corresponding FreeBSD wiki > page? If yes, register there and we can hand out write access. that's a coincidence. i mailed Simon L. Nielsen a few days ago asking him if he could give me write permission so i could add some info to the linux-kernel wiki page. my wikiname is "AlexanderBest". > Is your system running in 32bit or 64bit mode? Do you know which > ltp-tests cause those messages to appear? i'm running the 32bit version of freebsd. i'll try to find out which tests exactly are causing the overflow. cheers. alex From Alexander at Leidinger.net Tue Sep 15 12:04:55 2009 From: Alexander at Leidinger.net (Alexander Leidinger) Date: Tue Sep 15 12:05:02 2009 Subject: Buffer overflow detected by REDZONE with linuxulator In-Reply-To: References: Message-ID: <20090915140444.11146ndqvz52wn40@webmail.leidinger.net> Quoting Alexander Best (from Tue, 15 Sep 2009 13:33:55 +0200 (CEST)): > Alexander Leidinger schrieb am 2009-09-15: >> Are you interested to help update the corresponding FreeBSD wiki >> page? If yes, register there and we can hand out write access. > > that's a coincidence. i mailed Simon L. Nielsen a few days ago asking him if > he could give me write permission so i could add some info to the > linux-kernel > wiki page. my wikiname is "AlexanderBest". The write access is granted now. >> Is your system running in 32bit or 64bit mode? Do you know which >> ltp-tests cause those messages to appear? > > i'm running the 32bit version of freebsd. i'll try to find out which tests > exactly are causing the overflow. If you want you can add the error messages you get to the wiki page in a sensible place... Bye, Alexander. -- The two things that can get you into trouble quicker than anything else are fast women and slow horses. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From gary.jennejohn at freenet.de Tue Sep 15 13:07:42 2009 From: gary.jennejohn at freenet.de (Gary Jennejohn) Date: Tue Sep 15 13:07:52 2009 Subject: virtualbox cannot compile In-Reply-To: <20090914190136.773147aa@ernst.jennejohn.org> References: <20090914094805.47a01eab@Picasso.Zahemszky.HU> <20090914132602.79faca57@ernst.jennejohn.org> <20090914142916.31e69226@Picasso.Zahemszky.HU> <20090914153800.38fb8e7a@ernst.jennejohn.org> <4AAE7259.80200@shapeshifter.se> <20090914190136.773147aa@ernst.jennejohn.org> Message-ID: <20090915150740.71c10b45@ernst.jennejohn.org> On Mon, 14 Sep 2009 19:01:36 +0200 Gary Jennejohn wrote: > Hmm. My sources are newer than the kernel I'm using. Don't know whether > that is a factor or not. > Well, I did a "make buildkernel" before trying to build the port. It still fails because it can't find machine/_align.h. The symbolic link "machine" only exists under /usr/obj/sys/amd64 (my KERNCONF is amd64). The only way I can get the port to build is by creating work/virtualbox-3.0.51r22902/include/machine -> /sys/amd64/include by hand. There definitely seems to be a bug somewhere here. Building the port worked in older versions before the new networking stuff was added. --- Gary Jennejohn From xorquewasp at googlemail.com Tue Sep 15 17:39:40 2009 From: xorquewasp at googlemail.com (xorquewasp@googlemail.com) Date: Tue Sep 15 17:39:46 2009 Subject: Problems with qemu networking on 7.2-RELEASE-amd64? In-Reply-To: <20090914051402.GB44046@logik.internal.network> References: <20090914051402.GB44046@logik.internal.network> Message-ID: <20090915173935.GA34173@logik.internal.network> On 2009-09-14 06:14:02, xorquewasp@googlemail.com wrote: > Hello. > > I'm having horrendous trouble getting qemu to do networking > on 7.2-RELEASE-amd64. I've not had any trouble on previous > versions of FreeBSD and qemu so this comes as a bit of a surprise. So, er, nobody's using this rather common setup on 7.2-RELEASE-amd64? I don't know if this is a problem with qemu or a problem with if_bridge.ko. Again: NetBSD x86 sees no NIC at all. OpenBSD x86 sees a NIC but it doesn't work ("ne3: device timeout"). Windows XP sees a NIC, can do DNS resolution but no outgoing TCP connection works. NetBSD SPARC sees a NIC, can do DNS resolution but no outgoing TCP connection works. I can connect into the guest via SSH. This isn't a firewall issue: I can watch the pflog0, re0 and tap0 devices with tcpdump and clearly see that nothing is being blocked. The TCP outbound connections simply pass into the tap device and then apparently don't even get as far as the bridge: Working DNS resolution: 133779 rule 22/0(match): pass in on tap0: 10.1.3.12.65529 > 10.2.1.7.53: UDP, length 32 000006 rule 23/0(match): pass out on bridge0: 10.1.3.12.65529 > 10.2.1.7.53: UDP, length 32 Apparently broken TCP/IP to google.com: 189768 rule 24/0(match): pass in on tap0: 10.1.3.12.65534 > 216.239.59.147.80: tcp 0 There's no "pass out on bridge0" or "pass out on re0" as expected. I've tried the recent qemu-devel patch but it's so unstable that it seems nearly any execution path results in a segmentation fault. Any help would be appreciated - I have work to do that requires access to these VMs and having no outgoing network connectivity is crippling. From amvandemore at gmail.com Tue Sep 15 17:44:09 2009 From: amvandemore at gmail.com (Adam Vande More) Date: Tue Sep 15 17:44:19 2009 Subject: Problems with qemu networking on 7.2-RELEASE-amd64? In-Reply-To: <20090915173935.GA34173@logik.internal.network> References: <20090914051402.GB44046@logik.internal.network> <20090915173935.GA34173@logik.internal.network> Message-ID: <6201873e0909151044o1331009rf62dba1912cf17eb@mail.gmail.com> On Tue, Sep 15, 2009 at 12:39 PM, wrote: > On 2009-09-14 06:14:02, xorquewasp@googlemail.com wrote: > > Hello. > > > > I'm having horrendous trouble getting qemu to do networking > > on 7.2-RELEASE-amd64. I've not had any trouble on previous > > versions of FreeBSD and qemu so this comes as a bit of a surprise. > > So, er, nobody's using this rather common setup on 7.2-RELEASE-amd64? > > I don't know if this is a problem with qemu or a problem with if_bridge.ko. > > Again: > > NetBSD x86 sees no NIC at all. > > OpenBSD x86 sees a NIC but it doesn't work ("ne3: device timeout"). > > Windows XP sees a NIC, can do DNS resolution but no outgoing TCP > connection > works. > > NetBSD SPARC sees a NIC, can do DNS resolution but no outgoing TCP > connection > works. I can connect into the guest via SSH. > > This isn't a firewall issue: I can watch the pflog0, re0 and tap0 devices > with tcpdump and clearly see that nothing is being blocked. > > The TCP outbound connections simply pass into the tap device and then > apparently > don't even get as far as the bridge: > > Working DNS resolution: > 133779 rule 22/0(match): pass in on tap0: 10.1.3.12.65529 > 10.2.1.7.53: > UDP, length 32 > 000006 rule 23/0(match): pass out on bridge0: 10.1.3.12.65529 > > 10.2.1.7.53: UDP, length 32 > > Apparently broken TCP/IP to google.com: > 189768 rule 24/0(match): pass in on tap0: 10.1.3.12.65534 > > 216.239.59.147.80: tcp 0 > > There's no "pass out on bridge0" or "pass out on re0" as expected. > > I've tried the recent qemu-devel patch but it's so unstable that it seems > nearly any execution path results in a segmentation fault. > > Any help would be appreciated - I have work to do that requires access > to these VMs and having no outgoing network connectivity is crippling. > > I don't know anything about your particular issue, but VirtualBox should be able to run those qemu images, and it's bridged networking is now working in addition to the previously working nat. IME, VBox is significantly faster and more robust than qemu, especially in the network realm. -- Adam Vande More From xorquewasp at googlemail.com Tue Sep 15 17:50:18 2009 From: xorquewasp at googlemail.com (xorquewasp@googlemail.com) Date: Tue Sep 15 17:50:25 2009 Subject: Problems with qemu networking on 7.2-RELEASE-amd64? In-Reply-To: <20090915173935.GA34173@logik.internal.network> References: <20090914051402.GB44046@logik.internal.network> <20090915173935.GA34173@logik.internal.network> Message-ID: <20090915175013.GA76444@logik.internal.network> > I don't know anything about your particular issue, but VirtualBox should be > able to run those qemu images, and it's bridged networking is now working in > addition to the previously working nat. IME, VBox is significantly faster > and more robust than qemu, especially in the network realm. Indeed. It still seems quite immature on FreeBSD, though. I can't tolerate unstable code in the kernel on this particular machine. I imagine practically anything is more robust than qemu, but at least a crash in qemu just requires running the program again... From fli at shapeshifter.se Tue Sep 15 19:28:20 2009 From: fli at shapeshifter.se (Fredrik Lindberg) Date: Tue Sep 15 19:28:31 2009 Subject: virtualbox cannot compile In-Reply-To: <20090915150740.71c10b45@ernst.jennejohn.org> References: <20090914094805.47a01eab@Picasso.Zahemszky.HU> <20090914132602.79faca57@ernst.jennejohn.org> <20090914142916.31e69226@Picasso.Zahemszky.HU> <20090914153800.38fb8e7a@ernst.jennejohn.org> <4AAE7259.80200@shapeshifter.se> <20090914190136.773147aa@ernst.jennejohn.org> <20090915150740.71c10b45@ernst.jennejohn.org> Message-ID: <4AAFEACA.20109@shapeshifter.se> Gary Jennejohn wrote: > On Mon, 14 Sep 2009 19:01:36 +0200 > Gary Jennejohn wrote: > >> Hmm. My sources are newer than the kernel I'm using. Don't know whether >> that is a factor or not. >> > > Well, I did a "make buildkernel" before trying to build the port. > > It still fails because it can't find machine/_align.h. > > The symbolic link "machine" only exists under /usr/obj/sys/amd64 (my > KERNCONF is amd64). > > The only way I can get the port to build is by creating > work/virtualbox-3.0.51r22902/include/machine -> /sys/amd64/include > by hand. > > There definitely seems to be a bug somewhere here. Building the port > worked in older versions before the new networking stuff was added. > Does your installed world (particularly your installed header files) match your current sources? If they don't I suggest you do a {build,install}world and see if that solves it. As a data point, I successfully compiled the vbox modules on an i386 9-current (from today) machine using the virtualbox version in ports. Fredrik From alexbestms at math.uni-muenster.de Tue Sep 15 21:35:48 2009 From: alexbestms at math.uni-muenster.de (Alexander Best) Date: Tue Sep 15 21:35:54 2009 Subject: Buffer overflow detected by REDZONE with linuxulator In-Reply-To: <20090915140444.11146ndqvz52wn40@webmail.leidinger.net> Message-ID: Alexander Leidinger schrieb am 2009-09-15: > Quoting Alexander Best (from Tue, > 15 Sep 2009 13:33:55 +0200 (CEST)): > >Alexander Leidinger schrieb am 2009-09-15: > >>Are you interested to help update the corresponding FreeBSD wiki > >>page? If yes, register there and we can hand out write access. > >that's a coincidence. i mailed Simon L. Nielsen a few days ago > >asking him if > >he could give me write permission so i could add some info to the > >linux-kernel > >wiki page. my wikiname is "AlexanderBest". > The write access is granted now. > >>Is your system running in 32bit or 64bit mode? Do you know which > >>ltp-tests cause those messages to appear? > >i'm running the 32bit version of freebsd. i'll try to find out > >which tests > >exactly are causing the overflow. > If you want you can add the error messages you get to the wiki page > in a sensible place... thanks. i've just submitted a PR describing the problem in detail. here it is: http://www.freebsd.org/cgi/query-pr.cgi?pr=138860 i'll add a note of it to the linux-kernel wiki page and see if i can provide some more updates to the site. cheers. alex > Bye, > Alexander. > -- > The two things that can get you into trouble > quicker than anything else are fast women and slow horses. > http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = > B0063FE7 > http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = > 72077137 From nox at jelal.kn-bremen.de Tue Sep 15 22:33:00 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Tue Sep 15 22:33:06 2009 Subject: Problems with qemu networking on 7.2-RELEASE-amd64? In-Reply-To: <20090915173935.GA34173@logik.internal.network> References: <20090914051402.GB44046@logik.internal.network> <20090915173935.GA34173@logik.internal.network> Message-ID: <20090915223039.GA46462@triton8.kn-bremen.de> On Tue, Sep 15, 2009 at 06:39:35PM +0100, xorquewasp@googlemail.com wrote: > On 2009-09-14 06:14:02, xorquewasp@googlemail.com wrote: > > Hello. Hi! > > > > I'm having horrendous trouble getting qemu to do networking > > on 7.2-RELEASE-amd64. I've not had any trouble on previous > > versions of FreeBSD and qemu so this comes as a bit of a surprise. > > So, er, nobody's using this rather common setup on 7.2-RELEASE-amd64? > > I don't know if this is a problem with qemu or a problem with if_bridge.ko. > > Again: > > NetBSD x86 sees no NIC at all. > > OpenBSD x86 sees a NIC but it doesn't work ("ne3: device timeout"). > Well thats unrelated, I'd say these guests just don't like most of qemu's emulated nic choices. I don't remember about OpenBSD, but NetBSD seemed to only really like the `pcnet' one, and that only after I patched qemu's bios, see this thread: http://lists.freebsd.org/pipermail/freebsd-emulation/2009-May/006207.html > Windows XP sees a NIC, can do DNS resolution but no outgoing TCP connection > works. > > NetBSD SPARC sees a NIC, can do DNS resolution but no outgoing TCP connection > works. I can connect into the guest via SSH. > Well if the guest's packets reach the tap interface and come back I'd say that mostly rules out qemu to be the cause of the problem, and also this works just fine for me on stable/7 and stable/8, and I guess I did it on 7.2 as well... > This isn't a firewall issue: I can watch the pflog0, re0 and tap0 devices > with tcpdump and clearly see that nothing is being blocked. > > The TCP outbound connections simply pass into the tap device and then apparently > don't even get as far as the bridge: > > Working DNS resolution: > 133779 rule 22/0(match): pass in on tap0: 10.1.3.12.65529 > 10.2.1.7.53: UDP, length 32 > 000006 rule 23/0(match): pass out on bridge0: 10.1.3.12.65529 > 10.2.1.7.53: UDP, length 32 > > Apparently broken TCP/IP to google.com: > 189768 rule 24/0(match): pass in on tap0: 10.1.3.12.65534 > 216.239.59.147.80: tcp 0 > > There's no "pass out on bridge0" or "pass out on re0" as expected. > Hmm have you tried disabling pf to completely rule out any issues with it? Also you may need to enable ip forwarding (net.inet.ip.forwarding sysctl, also settable via gateway_enable in rc.conf) and/or play with the net.link.bridge.pfil_* sysctls. (see the if_bridge manpage.) > I've tried the recent qemu-devel patch but it's so unstable that it seems > nearly any execution path results in a segmentation fault. > Oops :) Backtraces may be interesting there. Also which one you tried, the 0.11 rc2 one or the git head snapshot? > Any help would be appreciated - I have work to do that requires access > to these VMs and having no outgoing network connectivity is crippling. Oh and you could also try -net pcap... Or of course vbox too. HTH, Juergen From alexbestms at math.uni-muenster.de Tue Sep 15 23:00:18 2009 From: alexbestms at math.uni-muenster.de (Alexander Best) Date: Tue Sep 15 23:00:24 2009 Subject: kern/56451: [linprocfs] /compat/linux/proc/cpuinfo gives wrong CPU model Message-ID: <200909152300.n8FN0Hh3081804@freefall.freebsd.org> The following reply was made to PR kern/56451; it has been noted by GNATS. From: Alexander Best To: Cc: Subject: Re: kern/56451: [linprocfs] /compat/linux/proc/cpuinfo gives wrong CPU model Date: Wed, 16 Sep 2009 00:50:15 +0200 (CEST) i can confirm that this problem still exists in 9.0-CURRENT (FreeBSD otaku 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r197043: Sat Sep 12 01:07:56 CEST 2009 root@otaku:/usr/obj/usr/src/sys/ARUNDEL i386). from `dmesg`: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) Dual CPU E2160 @ 1.80GHz (1800.01-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6fd Stepping = 13 Features=0xbfebfbff Features2=0xe39d AMD Features=0x20100000 AMD Features2=0x1 TSC: P-state invariant from `cat /compat/linux/proc/cpuinfo`: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 7 model name : Intel(R) Pentium(R) Dual CPU E2160 @ 1.80GHz stepping : 13 processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 7 model name : Intel(R) Pentium(R) Dual CPU E2160 @ 1.80GHz stepping : 13 flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 b19 b21 mmxext mmx fxsr xmm sse2 b27 b28 b29 3dnow cpu MHz : 1800.01 bogomips : 1800.01 cheers. alex From alexbestms at math.uni-muenster.de Tue Sep 15 23:40:09 2009 From: alexbestms at math.uni-muenster.de (Alexander Best) Date: Tue Sep 15 23:40:20 2009 Subject: ports/135337: [PATCH] emulators/linux_base-f10: incorrect bash usage Message-ID: <200909152340.n8FNe7Ll022425@freefall.freebsd.org> The following reply was made to PR ports/135337; it has been noted by GNATS. From: Alexander Best To: Cc: Subject: Re: ports/135337: [PATCH] emulators/linux_base-f10: incorrect bash usage Date: Wed, 16 Sep 2009 01:39:33 +0200 (CEST) did anybody ever try the patch enclosed in this PR ? http://www.freebsd.org/cgi/query-pr.cgi?pr=36952 does it fix the issue? cheers. alex From alexbestms at math.uni-muenster.de Wed Sep 16 01:10:04 2009 From: alexbestms at math.uni-muenster.de (Alexander Best) Date: Wed Sep 16 01:10:14 2009 Subject: kern/29698: [linux] [patch] linux ipcs doesn'work Message-ID: <200909160110.n8G1A32T011855@freefall.freebsd.org> The following reply was made to PR kern/29698; it has been noted by GNATS. From: Alexander Best To: Cc: Subject: Re: kern/29698: [linux] [patch] linux ipcs doesn'work Date: Wed, 16 Sep 2009 03:02:25 +0200 (CEST) emulators/linux_dist-gentoo-stage3 comes with `ipcs` and `ipcrm`. running ipcs [-s|-a] works without any problems. `/usr/local/gentoo-stage3/usr/bin/ipcs -a`: ------ Shared Memory Segments -------- key shmid owner perms bytes nattch status ------ Semaphore Arrays -------- key semid owner perms nsems 0x74738b52 65536 arundel 600 1 ------ Message Queues -------- key msqid owner perms used-bytes messages `/usr/local/gentoo-stage3/usr/bin/ipcs -s`: ------ Semaphore Arrays -------- key semid owner perms nsems 0x74738b52 65536 arundel 600 1 ` /usr/local/gentoo-stage3/usr/bin/ipcrm -s 65536` `/usr/local/gentoo-stage3/usr/bin/ipcs -s`: ------ Semaphore Arrays -------- key semid owner perms nsems question is if `ipcs`/`ipcrm` is needed in emulators/linux_base-f*. cheers. alex p.s.: i'm running - FreeBSD otaku 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r197234: Wed Sep 16 01:10:00 CEST 2009 root@otaku:/usr/obj/usr/src/sys/ARUNDEL i386 From xorquewasp at googlemail.com Wed Sep 16 06:19:03 2009 From: xorquewasp at googlemail.com (xorquewasp@googlemail.com) Date: Wed Sep 16 06:19:10 2009 Subject: Problems with qemu networking on 7.2-RELEASE-amd64? In-Reply-To: <20090915223039.GA46462@triton8.kn-bremen.de> References: <20090914051402.GB44046@logik.internal.network> <20090915173935.GA34173@logik.internal.network> <20090915223039.GA46462@triton8.kn-bremen.de> Message-ID: <20090916061858.GA70047@logik.internal.network> On 2009-09-16 00:30:39, Juergen Lock wrote: > Hi! 'Lo. > > Again: > > > > NetBSD x86 sees no NIC at all. > > > > OpenBSD x86 sees a NIC but it doesn't work ("ne3: device timeout"). > > > Well thats unrelated, I'd say these guests just don't like most of qemu's > emulated nic choices. I don't remember about OpenBSD, but NetBSD seemed > to only really like the `pcnet' one, and that only after I patched qemu's > bios, see this thread: > http://lists.freebsd.org/pipermail/freebsd-emulation/2009-May/006207.html > That's good to know at least... if you can call it that. I'll try the new BIOS. > Well if the guest's packets reach the tap interface and come back I'd > say that mostly rules out qemu to be the cause of the problem, and also > this works just fine for me on stable/7 and stable/8, and I guess I did > it on 7.2 as well... > Hmm have you tried disabling pf to completely rule out any issues with > it? Also you may need to enable ip forwarding (net.inet.ip.forwarding > sysctl, also settable via gateway_enable in rc.conf) and/or play with > the net.link.bridge.pfil_* sysctls. (see the if_bridge manpage.) Hm! Some quite disturbing results with the various sysctls. I tried different combinations of the net.link.bridge.pfil_* controls and got some strange results. All of the results below are the output of tcpdump watching pflog0 when I execute 'telnet www.google.com 80' in the guest VM (NetBSD SPARC): net.link.bridge.ipfw: 0 net.link.bridge.log_stp: 0 net.link.bridge.pfil_local_phys: 0 net.link.bridge.pfil_member: 0 net.link.bridge.pfil_bridge: 1 net.link.bridge.ipfw_arp: 0 net.link.bridge.pfil_onlyip: 0 Connection does appear to work. Note the strange 'block in on bridge0' at the end... 000009 rule 23/0(match): pass out on bridge0: 10.1.3.12.65531 > 10.2.1.7.53: UDP, length 32 004923 rule 23/0(match): pass in on bridge0: 10.1.3.12.65530 > 10.2.1.7.53: UDP, length 32 000004 rule 23/0(match): pass out on bridge0: 10.1.3.12.65530 > 10.2.1.7.53: UDP, length 32 004191 rule 25/0(match): pass in on bridge0: 10.1.3.12.65533 > 216.239.59.99.80: tcp 0 000008 rule 25/0(match): pass out on bridge0: 10.1.3.12.65533 > 216.239.59.99.80: tcp 0 6. 193397 rule 0/0(match): block in on bridge0: 10.1.3.12.65534 > 216.239.59.99.80: tcp 0 ---------------------------------------------------------------------- net.link.bridge.ipfw: 0 net.link.bridge.log_stp: 0 net.link.bridge.pfil_local_phys: 0 net.link.bridge.pfil_member: 1 net.link.bridge.pfil_bridge: 0 net.link.bridge.ipfw_arp: 0 net.link.bridge.pfil_onlyip: 0 Connection doesn't work but is correctly blocked by pf, anyway. 38. 968850 rule 22/0(match): pass in on tap0: 10.1.3.12.65529 > 10.2.1.7.53: UDP, length 32 000008 rule 1/0(match): block out on re0: 10.1.3.12.65529 > 10.2.1.7.53: UDP, length 32 5. 001455 rule 1/0(match): block out on re0: 10.1.3.12.65529 > 10.2.1.7.53: UDP, length 32 ---------------------------------------------------------------------- net.link.bridge.ipfw: 0 net.link.bridge.log_stp: 0 net.link.bridge.pfil_local_phys: 1 net.link.bridge.pfil_member: 0 net.link.bridge.pfil_bridge: 0 net.link.bridge.ipfw_arp: 0 net.link.bridge.pfil_onlyip: 0 (works, no log) ---------------------------------------------------------------------- net.link.bridge.ipfw: 0 net.link.bridge.log_stp: 0 net.link.bridge.pfil_local_phys: 1 net.link.bridge.pfil_member: 0 net.link.bridge.pfil_bridge: 1 net.link.bridge.ipfw_arp: 0 net.link.bridge.pfil_onlyip: 0 Works (explicitly allowed by pf rules). 408422 rule 23/0(match): pass in on bridge0: 10.1.3.12.65525 > 10.2.1.7.53: UDP, length 32 000007 rule 23/0(match): pass out on bridge0: 10.1.3.12.65525 > 10.2.1.7.53: UDP, length 32 003908 rule 23/0(match): pass in on bridge0: 10.1.3.12.65524 > 10.2.1.7.53: UDP, length 32 000005 rule 23/0(match): pass out on bridge0: 10.1.3.12.65524 > 10.2.1.7.53: UDP, length 32 004390 rule 25/0(match): pass in on bridge0: 10.1.3.12.65531 > 216.239.59.99.80: tcp 0 000008 rule 25/0(match): pass out on bridge0: 10.1.3.12.65531 > 216.239.59.99.80: tcp 0 ---------------------------------------------------------------------- net.link.bridge.ipfw: 0 net.link.bridge.log_stp: 0 net.link.bridge.pfil_local_phys: 1 net.link.bridge.pfil_member: 1 net.link.bridge.pfil_bridge: 1 net.link.bridge.ipfw_arp: 0 net.link.bridge.pfil_onlyip: 0 Note that suddenly, outbound TCP no longer works (but isn't blocked, according to pf) and seems to go no further than the tap0 device: 18. 884422 rule 22/0(match): pass in on tap0: 10.1.3.12.65523 > 10.2.1.7.53: UDP, length 32 000008 rule 23/0(match): pass out on bridge0: 10.1.3.12.65523 > 10.2.1.7.53: UDP, length 32 003237 rule 22/0(match): pass in on tap0: 10.1.3.12.65522 > 10.2.1.7.53: UDP, length 32 000005 rule 23/0(match): pass out on bridge0: 10.1.3.12.65522 > 10.2.1.7.53: UDP, length 32 187188 rule 24/0(match): pass in on tap0: 10.1.3.12.65530 > 216.239.59.147.80: tcp 0 This suggests there's some sort of spooky interaction between pf and bridge when those three sysctls are all enabled - connections are apparently dropped and not logged. That said, I can get something that works and is correctly filtered with pfil_local_phys and pfil_bridge enabled. > > I've tried the recent qemu-devel patch but it's so unstable that it seems > > nearly any execution path results in a segmentation fault. > > > Oops :) Backtraces may be interesting there. Also which one you tried, > the 0.11 rc2 one or the git head snapshot? I will get to the backtraces. The version I used was the patched port in your other thread: http://lists.freebsd.org/pipermail/freebsd-emulation/2009-September/006760.html Thanks for the minor enlightenment so far! xw From gary.jennejohn at freenet.de Wed Sep 16 07:34:44 2009 From: gary.jennejohn at freenet.de (Gary Jennejohn) Date: Wed Sep 16 07:34:50 2009 Subject: virtualbox cannot compile In-Reply-To: <4AAFEACA.20109@shapeshifter.se> References: <20090914094805.47a01eab@Picasso.Zahemszky.HU> <20090914132602.79faca57@ernst.jennejohn.org> <20090914142916.31e69226@Picasso.Zahemszky.HU> <20090914153800.38fb8e7a@ernst.jennejohn.org> <4AAE7259.80200@shapeshifter.se> <20090914190136.773147aa@ernst.jennejohn.org> <20090915150740.71c10b45@ernst.jennejohn.org> <4AAFEACA.20109@shapeshifter.se> Message-ID: <20090916093441.0a0ede25@ernst.jennejohn.org> On Tue, 15 Sep 2009 21:28:10 +0200 Fredrik Lindberg wrote: > Does your installed world (particularly your installed header files) > match your current sources? If they don't I suggest you do a > {build,install}world and see if that solves it. > Ah yes, how stupid of me. I haven't done an installworld for a week or so. OK, that explains everything. --- Gary Jennejohn From scf at FreeBSD.org Wed Sep 16 13:40:52 2009 From: scf at FreeBSD.org (Sean C. Farley) Date: Wed Sep 16 13:40:58 2009 Subject: changes in linux ports infrastructure In-Reply-To: <80173957@bb.ipt.ru> References: <80173957@bb.ipt.ru> Message-ID: On Mon, 14 Sep 2009, Boris Samorodov wrote: > Dear linux ports maintainers, > > I've just committed a new graphics/linux-f10-libGLU port and > apropriate changes to linux ports infrastructure. I'm going to commit > the following patch which uses the new port and its infrastructure. > > The main goal is to give users of linux nvidia drivers to use more > recent libGLU packages. > > Those changes do not touch default packages but imho it will be good > to commit the patch before 8.0-RELEASE. Please, give it a try and > submit a followup. Thanks! The patch to games/linux-nwnclient does work. When you commit it, would you also apply the following patch which helps a bit? :) I think it has been broken since March, but I just noticed. Two things I have noticed in regard to this port, the Nvidia driver and Fedora 8 or 10 as base: 1. Performance is poor until you change the resolution. It does not matter what the starting resolution or the changed resolution is. Changing back to the starting resolution keeps the good performance. This is very odd. 2. The game core dumps upon exit, but I have not had time to look into this. ---------------------------------------- --- Makefile.orig 2009-09-14 22:36:27.000000000 -0500 +++ Makefile 2009-09-14 22:36:27.000000000 -0500 @@ -29,7 +29,7 @@ NO_BUILD= yes ONLY_FOR_ARCHS= i386 USE_LINUX= yes -USE_LINUX_APPS= sdl12 xorglibs +USE_LINUX_APPS+=sdl12 xorglibs NWNDATADIR= ${LOCALBASE}/share/nwndata PLIST_SUB+= NWNVERSION="${PORTVERSION:S/.//}" ---------------------------------------- Sean -- scf@FreeBSD.org From bsam at ipt.ru Wed Sep 16 14:42:24 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Wed Sep 16 14:42:30 2009 Subject: changes in linux ports infrastructure In-Reply-To: (Sean C. Farley's message of "Wed\, 16 Sep 2009 08\:40\:49 -0500 \(CDT\)") References: <80173957@bb.ipt.ru> Message-ID: <23039453@ipt.ru> "Sean C. Farley" writes: > On Mon, 14 Sep 2009, Boris Samorodov wrote: > >> Dear linux ports maintainers, >> >> I've just committed a new graphics/linux-f10-libGLU port and >> apropriate changes to linux ports infrastructure. I'm going to >> commit the following patch which uses the new port and its >> infrastructure. >> >> The main goal is to give users of linux nvidia drivers to use more >> recent libGLU packages. >> >> Those changes do not touch default packages but imho it will be good >> to commit the patch before 8.0-RELEASE. Please, give it a try and >> submit a followup. Thanks! > > The patch to games/linux-nwnclient does work. When you commit it, > would you also apply the following patch which helps a bit? :) I > think it has been broken since March, but I just noticed. Hm, yes, I see it. I'll move the NVIDIA test down, just before PLIST_SUB, if you don't mind (as it is done at other ports). > Two things I have noticed in regard to this port, the Nvidia driver > and Fedora 8 or 10 as base: > 1. Performance is poor until you change the resolution. It does not > matter what the starting resolution or the changed resolution is. > Changing back to the starting resolution keeps the good performance. > This is very odd. Which video card/driver/dri/linux-dri port are you using? > 2. The game core dumps upon exit, but I have not had time to look into > this. Can't say anything about this case. -- WBR, bsam From scf at FreeBSD.org Wed Sep 16 14:58:32 2009 From: scf at FreeBSD.org (Sean C. Farley) Date: Wed Sep 16 14:58:42 2009 Subject: changes in linux ports infrastructure In-Reply-To: <23039453@ipt.ru> References: <80173957@bb.ipt.ru> <23039453@ipt.ru> Message-ID: On Wed, 16 Sep 2009, Boris Samorodov wrote: > "Sean C. Farley" writes: >> On Mon, 14 Sep 2009, Boris Samorodov wrote: >> >>> Dear linux ports maintainers, >>> >>> I've just committed a new graphics/linux-f10-libGLU port and >>> apropriate changes to linux ports infrastructure. I'm going to >>> commit the following patch which uses the new port and its >>> infrastructure. >>> >>> The main goal is to give users of linux nvidia drivers to use more >>> recent libGLU packages. >>> >>> Those changes do not touch default packages but imho it will be good >>> to commit the patch before 8.0-RELEASE. Please, give it a try and >>> submit a followup. Thanks! >> >> The patch to games/linux-nwnclient does work. When you commit it, >> would you also apply the following patch which helps a bit? :) I >> think it has been broken since March, but I just noticed. > > Hm, yes, I see it. I'll move the NVIDIA test down, just before > PLIST_SUB, if you don't mind (as it is done at other ports). I do not mind. Thank you. >> Two things I have noticed in regard to this port, the Nvidia driver >> and Fedora 8 or 10 as base: >> 1. Performance is poor until you change the resolution. It does not >> matter what the starting resolution or the changed resolution is. >> Changing back to the starting resolution keeps the good >> performance. This is very odd. > > Which video card/driver/dri/linux-dri port are you using? Nvidia 8800 GTS, nvidia-driver-185.18.31 (same issue with some previous drivers) and linux-f10-libGLU-7.2. linux-ut (does not use libGLU) does not have this issue nor does sauerbraten. >> 2. The game core dumps upon exit, but I have not had time to look >> into this. > > Can't say anything about this case. No problem. When I get more time, I will try examine it in more detail. The game plays fine; it is just when exiting. Same as above where linux-ut and sauerbraten do not have this issue. Sean -- scf@FreeBSD.org From swhetzel at gmail.com Wed Sep 16 15:14:34 2009 From: swhetzel at gmail.com (Scot Hetzel) Date: Wed Sep 16 15:14:40 2009 Subject: Fwd: linuxolator: proc/filesystems and sysfs function implementations In-Reply-To: <790a9fff0701261550n5982c0chea94dbfa208439da@mail.gmail.com> References: <790a9fff0701060012x40063f48pc842510b082df5a5@mail.gmail.com> <20070106130830.3c2e6d98@Magellan.Leidinger.net> <790a9fff0701132017g6c081567la4a759cea4618535@mail.gmail.com> <20070114105239.GA6955@stud.fit.vutbr.cz> <790a9fff0701141254s2c92b10ag6b042a019bc283c@mail.gmail.com> <20070115105921.wbv2yrd4bkgokcko@webmail.leidinger.net> <790a9fff0701252321x2c7bea62od928766849e32c68@mail.gmail.com> <790a9fff0701261550n5982c0chea94dbfa208439da@mail.gmail.com> Message-ID: <790a9fff0909160742p1043e643i69febf5a7e88a97e@mail.gmail.com> I see that Alexander Best had added sysfs to the linux-kernel wiki. Attached is the sysfs implementation that I had created back in 2007, and was reviewed on this list. Could someone commit this implentation to P4 or at least put it up some where so others can improve on it. Thanks, Scot -------------- next part -------------- A non-text attachment was scrubbed... Name: sysfs4.patch Type: text/x-diff Size: 7125 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-emulation/attachments/20090916/7281851c/sysfs4.bin From delphij at delphij.net Wed Sep 16 20:16:19 2009 From: delphij at delphij.net (Xin LI) Date: Wed Sep 16 20:16:26 2009 Subject: Fwd: linuxolator: proc/filesystems and sysfs function implementations In-Reply-To: <790a9fff0909160742p1043e643i69febf5a7e88a97e@mail.gmail.com> References: <790a9fff0701060012x40063f48pc842510b082df5a5@mail.gmail.com> <20070106130830.3c2e6d98@Magellan.Leidinger.net> <790a9fff0701132017g6c081567la4a759cea4618535@mail.gmail.com> <20070114105239.GA6955@stud.fit.vutbr.cz> <790a9fff0701141254s2c92b10ag6b042a019bc283c@mail.gmail.com> <20070115105921.wbv2yrd4bkgokcko@webmail.leidinger.net> <790a9fff0701252321x2c7bea62od928766849e32c68@mail.gmail.com> <790a9fff0701261550n5982c0chea94dbfa208439da@mail.gmail.com> <790a9fff0909160742p1043e643i69febf5a7e88a97e@mail.gmail.com> Message-ID: <4AB14786.1010202@delphij.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Scot Hetzel wrote: > I see that Alexander Best had added sysfs to the linux-kernel wiki. > > Attached is the sysfs implementation that I had created back in 2007, > and was reviewed on this list. > > Could someone commit this implentation to P4 or at least put it up > some where so others can improve on it. Em... Is there any reason this is not ready for -HEAD? (There is a minor information disclosure issue, though, but that can be easily fixed). Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iEYEARECAAYFAkqxR4YACgkQi+vbBBjt66CzuACbBb96TwldoUZ0wMKpf6FV0C+K KKUAnjHMafVuvdvMM0g/2HvcAXM0P5g7 =Igxx -----END PGP SIGNATURE----- From linimon at FreeBSD.org Wed Sep 16 21:55:07 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Wed Sep 16 21:55:13 2009 Subject: kern/138880: [linux] munmap segfaults after linux_mmap2 stresstest Message-ID: <200909162155.n8GLt7RI006456@freefall.freebsd.org> Synopsis: [linux] munmap segfaults after linux_mmap2 stresstest Responsible-Changed-From-To: freebsd-bugs->freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Wed Sep 16 21:54:34 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=138880 From mlobo at digiart.art.br Thu Sep 17 00:44:13 2009 From: mlobo at digiart.art.br (Mario Lobo) Date: Thu Sep 17 00:44:19 2009 Subject: New network capabilities? In-Reply-To: <20090914155807.5ED7B1CC37@ptavv.es.net> References: <20090914155807.5ED7B1CC37@ptavv.es.net> Message-ID: <51072.200.249.56.17.1252948486.squirrel@squirrel.sv4.hmnoc.net> > I see that the new port of VB seems to have added a couple of kernel > modules that are probably network related: vboxnetadp.ko and > vboxnetflt.ko. > > Do these provide new networking options? I have seen quite a bit of > discussion of new network code on this list, but I am not sure exactly > what they cover or how to use them and I don't see much on the wiki, > but it looks like TAP is now available. > They provide host and bridge networking respectively. The TAP device (a great patch provided by Juergen Lock) is still in the code (I think) but Juergen designed it to be used while the networking bridge was not avaliable. I think that you can still use the TAP patch at the cost of disabling the bridge code. Mario Lobo From swhetzel at gmail.com Fri Sep 18 02:07:14 2009 From: swhetzel at gmail.com (Scot Hetzel) Date: Fri Sep 18 02:07:21 2009 Subject: Fwd: linuxolator: proc/filesystems and sysfs function implementations In-Reply-To: <4AB14786.1010202@delphij.net> References: <790a9fff0701060012x40063f48pc842510b082df5a5@mail.gmail.com> <20070106130830.3c2e6d98@Magellan.Leidinger.net> <790a9fff0701132017g6c081567la4a759cea4618535@mail.gmail.com> <20070114105239.GA6955@stud.fit.vutbr.cz> <790a9fff0701141254s2c92b10ag6b042a019bc283c@mail.gmail.com> <20070115105921.wbv2yrd4bkgokcko@webmail.leidinger.net> <790a9fff0701252321x2c7bea62od928766849e32c68@mail.gmail.com> <790a9fff0701261550n5982c0chea94dbfa208439da@mail.gmail.com> <790a9fff0909160742p1043e643i69febf5a7e88a97e@mail.gmail.com> <4AB14786.1010202@delphij.net> Message-ID: <790a9fff0909171907i296e65a0gbc7fefa255b70c65@mail.gmail.com> On Wed, Sep 16, 2009 at 3:16 PM, Xin LI wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Scot Hetzel wrote: >> I see that Alexander Best had added sysfs to the linux-kernel wiki. >> >> Attached is the sysfs implementation that I had created back in 2007, >> and was reviewed on this list. >> >> Could someone commit this implentation to P4 or at least put it up >> some where so others can improve on it. > > Em... ?Is there any reason this is not ready for -HEAD? > None that I can think of, it could be committed to -HEAD. Just needs someone to commit it. > (There is a minor information disclosure issue, though, but that can be > easily fixed). > Scot From alexbestms at math.uni-muenster.de Fri Sep 18 13:08:35 2009 From: alexbestms at math.uni-muenster.de (Alexander Best) Date: Fri Sep 18 13:08:42 2009 Subject: compat.linux.osrelease behavior Message-ID: hi there, i have a question regarding the behavior of compat.linux.osrelease. setting it to 2.4.2 sets linuxulator into 2.4 kernel-emulation and 2.6.16 sets it into 2.6 kernel-emulation right? but what happens when compat.linux.osrelease gets set to a different value? ports/Updating entry 20071101 e.g. advises skype users to set compat.linux.osrelease to 2.4.20. does this trigger 2.6 kernel-emulation because 2.4.20 > 2.4.2 or are there more than two kernel-emulation layers inside the linuxulator?? cheers. alex From yurtesen at ispro.net Fri Sep 18 22:07:46 2009 From: yurtesen at ispro.net (Evren Yurtesen) Date: Fri Sep 18 22:07:53 2009 Subject: E:Attach to pid 54301 failed: Function not implemented In-Reply-To: <4AB4016D.5070508@ispro.net> References: <4AB4016D.5070508@ispro.net> Message-ID: <4AB4035E.2030907@ispro.net> Evren Yurtesen wrote: > Hello, > > I am trying to use the Intel Software Development Emulator on FreeBSD 8 > > http://software.intel.com/en-us/articles/intel-software-development-emulator/ > > > with the linux_base-f10 port however I am getting the following error: > > # ./sde -- /bin/csh > E:Attach to pid 54304 failed: Function not implemented > > Is this something which can be fixed or should I forget about it? > > Thanks, > Evren > I just realized this in logs also: linux: pid 54303 (pinbin): syscall ptrace not implemented From yurtesen at ispro.net Fri Sep 18 22:19:36 2009 From: yurtesen at ispro.net (Evren Yurtesen) Date: Fri Sep 18 22:19:43 2009 Subject: E:Attach to pid 54301 failed: Function not implemented Message-ID: <4AB4016D.5070508@ispro.net> Hello, I am trying to use the Intel Software Development Emulator on FreeBSD 8 http://software.intel.com/en-us/articles/intel-software-development-emulator/ with the linux_base-f10 port however I am getting the following error: # ./sde -- /bin/csh E:Attach to pid 54304 failed: Function not implemented Is this something which can be fixed or should I forget about it? Thanks, Evren From gary.jennejohn at freenet.de Sat Sep 19 08:07:29 2009 From: gary.jennejohn at freenet.de (Gary Jennejohn) Date: Sat Sep 19 08:07:36 2009 Subject: E:Attach to pid 54301 failed: Function not implemented In-Reply-To: <4AB4035E.2030907@ispro.net> References: <4AB4016D.5070508@ispro.net> <4AB4035E.2030907@ispro.net> Message-ID: <20090919100724.1165f685@ernst.jennejohn.org> On Sat, 19 Sep 2009 01:02:06 +0300 Evren Yurtesen wrote: > Evren Yurtesen wrote: > > Hello, > > > > I am trying to use the Intel Software Development Emulator on FreeBSD 8 > > > > http://software.intel.com/en-us/articles/intel-software-development-emulator/ > > > > > > with the linux_base-f10 port however I am getting the following error: > > > > # ./sde -- /bin/csh > > E:Attach to pid 54304 failed: Function not implemented > > > > Is this something which can be fixed or should I forget about it? > > > It could probably be fixed, but it may require lots of effort. The arguments to the Linux ptrace(2) are different (some are pointers instead of ints) and it wouldn't surprise me in the least to find that ptrace(2) in Linux behaves differently than under FreeBSD. > I just realized this in logs also: > > linux: pid 54303 (pinbin): syscall ptrace not implemented --- Gary Jennejohn From Alexander at Leidinger.net Sat Sep 19 20:36:40 2009 From: Alexander at Leidinger.net (Alexander Leidinger) Date: Sat Sep 19 20:36:47 2009 Subject: compat.linux.osrelease behavior In-Reply-To: References: Message-ID: <20090919223624.00004f42@unknown> On Fri, 18 Sep 2009 15:08:31 +0200 (CEST) Alexander Best wrote: > hi there, > > i have a question regarding the behavior of compat.linux.osrelease. > setting it to 2.4.2 sets linuxulator into 2.4 kernel-emulation and > 2.6.16 sets it into 2.6 kernel-emulation right? Sort of. 2.6.x set's 2.6 mode, and everything else is 2.4 mode. But this is AFAIK only a semantic change of some functions. This does not disable syscalls which are in 2.6 but not in 2.4. > but what happens when compat.linux.osrelease gets set to a different > value? ports/Updating entry 20071101 e.g. advises skype users to set > compat.linux.osrelease to 2.4.20. does this trigger 2.6 > kernel-emulation because 2.4.20 > 2.4.2 or are there more than two > kernel-emulation layers inside the linuxulator?? It does not affect the kernel emulation. But the glibc will try to use new syscalls. Bye, Alexander. From kabaev at gmail.com Sat Sep 19 23:28:33 2009 From: kabaev at gmail.com (Alexander Kabaev) Date: Sat Sep 19 23:28:39 2009 Subject: E:Attach to pid 54301 failed: Function not implemented In-Reply-To: <20090919100724.1165f685@ernst.jennejohn.org> References: <4AB4016D.5070508@ispro.net> <4AB4035E.2030907@ispro.net> <20090919100724.1165f685@ernst.jennejohn.org> Message-ID: <20090919190022.3b046b1a@kan.dnsalias.net> On Sat, 19 Sep 2009 10:07:24 +0200 Gary Jennejohn wrote: > On Sat, 19 Sep 2009 01:02:06 +0300 > Evren Yurtesen wrote: > > > Evren Yurtesen wrote: > > > Hello, > > > > > > I am trying to use the Intel Software Development Emulator on > > > FreeBSD 8 > > > > > > http://software.intel.com/en-us/articles/intel-software-development-emulator/ > > > > > > > > > with the linux_base-f10 port however I am getting the following > > > error: > > > > > > # ./sde -- /bin/csh > > > E:Attach to pid 54304 failed: Function not implemented > > > > > > Is this something which can be fixed or should I forget about it? > > > > > > > It could probably be fixed, but it may require lots of effort. > > The arguments to the Linux ptrace(2) are different (some are pointers > instead of ints) and it wouldn't surprise me in the least to find that > ptrace(2) in Linux behaves differently than under FreeBSD. > > > I just realized this in logs also: > > > > linux: pid 54303 (pinbin): syscall ptrace not implemented > ptrace _was_ implemented for Linux at some point. See sys/i386/linux/linux_ptrace.c. -- Alexander Kabaev -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 188 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-emulation/attachments/20090919/95d279d4/signature.pgp From rdivacky at freebsd.org Sun Sep 20 06:33:46 2009 From: rdivacky at freebsd.org (Roman Divacky) Date: Sun Sep 20 06:33:53 2009 Subject: compat.linux.osrelease behavior In-Reply-To: <20090919223624.00004f42@unknown> References: <20090919223624.00004f42@unknown> Message-ID: <20090920063017.GA12687@freebsd.org> On Sat, Sep 19, 2009 at 10:36:24PM +0200, Alexander Leidinger wrote: > On Fri, 18 Sep 2009 15:08:31 +0200 (CEST) Alexander Best > wrote: > > > > hi there, > > > > i have a question regarding the behavior of compat.linux.osrelease. > > setting it to 2.4.2 sets linuxulator into 2.4 kernel-emulation and > > 2.6.16 sets it into 2.6 kernel-emulation right? > > Sort of. 2.6.x set's 2.6 mode, and everything else is 2.4 mode. But > this is AFAIK only a semantic change of some functions. This does not > disable syscalls which are in 2.6 but not in 2.4. > > > but what happens when compat.linux.osrelease gets set to a different > > value? ports/Updating entry 20071101 e.g. advises skype users to set > > compat.linux.osrelease to 2.4.20. does this trigger 2.6 > > kernel-emulation because 2.4.20 > 2.4.2 or are there more than two > > kernel-emulation layers inside the linuxulator?? > > It does not affect the kernel emulation. But the glibc will try to use > new syscalls. actually it does change how the kernel emulation works. grep for linux_use26() From yurtesen at ispro.net Sun Sep 20 08:50:06 2009 From: yurtesen at ispro.net (Evren Yurtesen) Date: Sun Sep 20 08:50:14 2009 Subject: E:Attach to pid 54301 failed: Function not implemented In-Reply-To: <20090919190022.3b046b1a@kan.dnsalias.net> References: <4AB4016D.5070508@ispro.net> <4AB4035E.2030907@ispro.net> <20090919100724.1165f685@ernst.jennejohn.org> <20090919190022.3b046b1a@kan.dnsalias.net> Message-ID: <4AB5ECF3.3020404@ispro.net> Alexander Kabaev wrote: > On Sat, 19 Sep 2009 10:07:24 +0200 > Gary Jennejohn wrote: > >> On Sat, 19 Sep 2009 01:02:06 +0300 >> Evren Yurtesen wrote: >> >>> Evren Yurtesen wrote: >>>> Hello, >>>> >>>> I am trying to use the Intel Software Development Emulator on >>>> FreeBSD 8 >>>> >>>> http://software.intel.com/en-us/articles/intel-software-development-emulator/ >>>> >>>> >>>> with the linux_base-f10 port however I am getting the following >>>> error: >>>> >>>> # ./sde -- /bin/csh >>>> E:Attach to pid 54304 failed: Function not implemented >>>> >>>> Is this something which can be fixed or should I forget about it? >>>> >> It could probably be fixed, but it may require lots of effort. >> >> The arguments to the Linux ptrace(2) are different (some are pointers >> instead of ints) and it wouldn't surprise me in the least to find that >> ptrace(2) in Linux behaves differently than under FreeBSD. >> >>> I just realized this in logs also: >>> >>> linux: pid 54303 (pinbin): syscall ptrace not implemented > ptrace _was_ implemented for Linux at some point. See > sys/i386/linux/linux_ptrace.c. > linux_ptrace.c doesnt appear at the amd64 side in /usr/src/sys/amd64/linux32 ? (I forgot to mention that I was using amd64). It would be nice if I could get the Intel's software working but if not, I can use Linux instead. Thanks for the information. Thanks, Evren From gary.jennejohn at freenet.de Sun Sep 20 17:15:04 2009 From: gary.jennejohn at freenet.de (Gary Jennejohn) Date: Sun Sep 20 17:15:11 2009 Subject: VirtualBox/kernel broken? Message-ID: <20090920191501.3d4d2c8a@ernst.jennejohn.org> So, I have a problem with VirtualBox and can't say whether it's a problem with VirtualBox itself or something which has changed in the kernel. I'm running FreeBSD 9.0-CURRENT Wed Sep 16 11:40:19 CEST 2009 amd64. I installed both the port and the latest stuff from svn. The problem is with an installation of Windows 7 RC which was working fine with an older version of the port (can't say from when, though) AND of the kernel. Today I decided to try the latest version of VirtualBox and the W7RC fails upon booting with an internal VirtualBox error. Strangely enough, if I start W7RC in repair mode it happily runs to completion, but then the boot fails with the above mentioned error. Booting from the ISO also fails. I have all kinds of log files from VirtualBox which I can't parse. Interestingly enough, the two Linux installations, which are from about the same time as the W7RC installation, still run flawlessly. Has anyone else seen any strangeness with the newer versions of VirtualBox and a fairly recent 9.0-CURRENT? --- Gary Jennejohn From Alexander at Leidinger.net Sun Sep 20 18:44:18 2009 From: Alexander at Leidinger.net (Alexander Leidinger) Date: Sun Sep 20 18:44:25 2009 Subject: compat.linux.osrelease behavior In-Reply-To: <20090920063017.GA12687@freebsd.org> References: <20090919223624.00004f42@unknown> <20090920063017.GA12687@freebsd.org> Message-ID: <20090920204407.0000383a@unknown> On Sun, 20 Sep 2009 08:30:17 +0200 Roman Divacky wrote: > On Sat, Sep 19, 2009 at 10:36:24PM +0200, Alexander Leidinger wrote: > > On Fri, 18 Sep 2009 15:08:31 +0200 (CEST) Alexander Best > > wrote: > > > > > > > hi there, > > > > > > i have a question regarding the behavior of > > > compat.linux.osrelease. setting it to 2.4.2 sets linuxulator into > > > 2.4 kernel-emulation and 2.6.16 sets it into 2.6 kernel-emulation > > > right? > > > > Sort of. 2.6.x set's 2.6 mode, and everything else is 2.4 mode. But > > this is AFAIK only a semantic change of some functions. This does > > not disable syscalls which are in 2.6 but not in 2.4. > > > > > but what happens when compat.linux.osrelease gets set to a > > > different value? ports/Updating entry 20071101 e.g. advises skype > > > users to set compat.linux.osrelease to 2.4.20. does this trigger > > > 2.6 kernel-emulation because 2.4.20 > 2.4.2 or are there more > > > than two kernel-emulation layers inside the linuxulator?? > > > > It does not affect the kernel emulation. But the glibc will try to > > use new syscalls. > > actually it does change how the kernel emulation works. grep for > linux_use26() I don't find the place where the behavior is changed when 2.4.20 is set... I only see a change when it is set to 2.6.x. Bye, Alexander. From rdivacky at freebsd.org Sun Sep 20 20:12:13 2009 From: rdivacky at freebsd.org (Roman Divacky) Date: Sun Sep 20 20:12:19 2009 Subject: compat.linux.osrelease behavior In-Reply-To: <20090920204407.0000383a@unknown> References: <20090919223624.00004f42@unknown> <20090920063017.GA12687@freebsd.org> <20090920204407.0000383a@unknown> Message-ID: <20090920200843.GA36192@freebsd.org> On Sun, Sep 20, 2009 at 08:44:07PM +0200, Alexander Leidinger wrote: > On Sun, 20 Sep 2009 08:30:17 +0200 Roman Divacky > wrote: > > > > On Sat, Sep 19, 2009 at 10:36:24PM +0200, Alexander Leidinger wrote: > > > On Fri, 18 Sep 2009 15:08:31 +0200 (CEST) Alexander Best > > > wrote: > > > > > > > > > > hi there, > > > > > > > > i have a question regarding the behavior of > > > > compat.linux.osrelease. setting it to 2.4.2 sets linuxulator into > > > > 2.4 kernel-emulation and 2.6.16 sets it into 2.6 kernel-emulation > > > > right? > > > > > > Sort of. 2.6.x set's 2.6 mode, and everything else is 2.4 mode. But > > > this is AFAIK only a semantic change of some functions. This does > > > not disable syscalls which are in 2.6 but not in 2.4. > > > > > > > but what happens when compat.linux.osrelease gets set to a > > > > different value? ports/Updating entry 20071101 e.g. advises skype > > > > users to set compat.linux.osrelease to 2.4.20. does this trigger > > > > 2.6 kernel-emulation because 2.4.20 > 2.4.2 or are there more > > > > than two kernel-emulation layers inside the linuxulator?? > > > > > > It does not affect the kernel emulation. But the glibc will try to > > > use new syscalls. > > > > actually it does change how the kernel emulation works. grep for > > linux_use26() > > I don't find the place where the behavior is changed when 2.4.20 is > set... I only see a change when it is set to 2.6.x. the thing with 2.4.20 is that red hat backported NPTL to 2.4.20 kernel. so the userland expects NTPL but we dont provide it. I dont think it's worth solving... the default is 2.6.16 and I dont see much reason why anyone would need 2.4.20... From linimon at FreeBSD.org Mon Sep 21 04:27:42 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Mon Sep 21 04:27:50 2009 Subject: kern/138944: [parallels] [regression] Parallels no longer works in FreeBSD 8 Beta Message-ID: <200909210427.n8L4RgkS088284@freefall.freebsd.org> Old Synopsis: Cannot update to FreeBSD 8 Beta from FreeBSD 7 New Synopsis: [parallels] [regression] Parallels no longer works in FreeBSD 8 Beta Responsible-Changed-From-To: freebsd-i386->freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Mon Sep 21 04:26:08 UTC 2009 Responsible-Changed-Why: Make a guess and assign this to the emulation mailing list. http://www.freebsd.org/cgi/query-pr.cgi?pr=138944 From bsam at ipt.ru Mon Sep 21 09:25:35 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Mon Sep 21 09:25:41 2009 Subject: compat.linux.osrelease behavior In-Reply-To: <20090920200843.GA36192@freebsd.org> (Roman Divacky's message of "Sun\, 20 Sep 2009 22\:08\:43 +0200") References: <20090919223624.00004f42@unknown> <20090920063017.GA12687@freebsd.org> <20090920204407.0000383a@unknown> <20090920200843.GA36192@freebsd.org> Message-ID: <78325388@ipt.ru> Roman Divacky writes: R> ... the default is 2.6.16 and I dont see much reason > why anyone would need 2.4.20... +1 -- WBR, bsam From bugmaster at FreeBSD.org Mon Sep 21 11:06:53 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Sep 21 11:07:52 2009 Subject: Current problem reports assigned to freebsd-emulation@FreeBSD.org Message-ID: <200909211106.n8LB6qj5030207@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/138944 emulation [parallels] [regression] Parallels no longer works in o kern/138880 emulation [linux] munmap segfaults after linux_mmap2 stresstest o ports/137332 emulation add caution messages to some adobe products f ports/136321 emulation x11-toolkits/linux-pango: please update linux based po o ports/136229 emulation [linux] certain linux apps look for libraries using a o ports/135337 emulation [PATCH] emulators/linux_base-f10: incorrect bash usage o ports/135322 emulation Port graphics/linux_dri has incorrect packaging list c o kern/130724 emulation [linprocfs] [patch] cpuinfo in linprocfs is dated, cau o kern/129169 emulation [linux] [patch] Linux Emulation ENOTCONN error using n f ports/127018 emulation Linuxulator incapable of using FreeBSD's LDAP environm o kern/126232 emulation [linux] Linux ioctl TCGETS (0x5401) always fails o kern/97326 emulation [linux] file descriptor leakage in linux emulation o kern/73777 emulation [linux] [patch] linux emulation: root dir special hand a kern/72920 emulation [linux]: path "prefixing" is not done on unix domain s o kern/56451 emulation [linprocfs] /compat/linux/proc/cpuinfo gives wrong CPU o kern/41543 emulation [patch] [request] easier wine/w23 support o kern/39201 emulation [linux] [patch] ptrace(2) and rfork(RFLINUXTHPN) confu o kern/29698 emulation [linux] [patch] linux ipcs doesn'work o kern/21463 emulation [linux] Linux compatability mode should not allow setu o kern/11165 emulation [ibcs2] IBCS2 doesn't work correctly with PID_MAX 9999 20 problems total. From Alexander at Leidinger.net Mon Sep 21 12:21:28 2009 From: Alexander at Leidinger.net (Alexander Leidinger) Date: Mon Sep 21 12:21:35 2009 Subject: compat.linux.osrelease behavior In-Reply-To: <20090920200843.GA36192@freebsd.org> References: <20090919223624.00004f42@unknown> <20090920063017.GA12687@freebsd.org> <20090920204407.0000383a@unknown> <20090920200843.GA36192@freebsd.org> Message-ID: <20090921142116.934965dwi9evrvok@webmail.leidinger.net> Quoting Roman Divacky (from Sun, 20 Sep 2009 22:08:43 +0200): > On Sun, Sep 20, 2009 at 08:44:07PM +0200, Alexander Leidinger wrote: >> On Sun, 20 Sep 2009 08:30:17 +0200 Roman Divacky >> wrote: >> >> >> > On Sat, Sep 19, 2009 at 10:36:24PM +0200, Alexander Leidinger wrote: >> > > On Fri, 18 Sep 2009 15:08:31 +0200 (CEST) Alexander Best >> > > wrote: >> > > >> > > >> > > > hi there, >> > > > >> > > > i have a question regarding the behavior of >> > > > compat.linux.osrelease. setting it to 2.4.2 sets linuxulator into >> > > > 2.4 kernel-emulation and 2.6.16 sets it into 2.6 kernel-emulation >> > > > right? >> > > >> > > Sort of. 2.6.x set's 2.6 mode, and everything else is 2.4 mode. But >> > > this is AFAIK only a semantic change of some functions. This does >> > > not disable syscalls which are in 2.6 but not in 2.4. >> > > >> > > > but what happens when compat.linux.osrelease gets set to a >> > > > different value? ports/Updating entry 20071101 e.g. advises skype >> > > > users to set compat.linux.osrelease to 2.4.20. does this trigger >> > > > 2.6 kernel-emulation because 2.4.20 > 2.4.2 or are there more >> > > > than two kernel-emulation layers inside the linuxulator?? >> > > >> > > It does not affect the kernel emulation. But the glibc will try to >> > > use new syscalls. >> > >> > actually it does change how the kernel emulation works. grep for >> > linux_use26() >> >> I don't find the place where the behavior is changed when 2.4.20 is >> set... I only see a change when it is set to 2.6.x. > > the thing with 2.4.20 is that red hat backported NPTL to 2.4.20 kernel. > so the userland expects NTPL but we dont provide it. I dont think it's > worth solving... the default is 2.6.16 and I dont see much reason > why anyone would need 2.4.20... I agree, but this was not the question of the initial post. So it seems we are back to my initial response, 2.4.20 does not change the emulation in the kernel, but it changes the behavior of glibc. Bye, Alexander. -- One man's constant is another man's variable. -- A. J. Perlis http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From gary.jennejohn at freenet.de Tue Sep 22 10:46:08 2009 From: gary.jennejohn at freenet.de (Gary Jennejohn) Date: Tue Sep 22 10:46:15 2009 Subject: VirtualBox/kernel broken? In-Reply-To: <20090920191501.3d4d2c8a@ernst.jennejohn.org> References: <20090920191501.3d4d2c8a@ernst.jennejohn.org> Message-ID: <20090922124606.0a9aee4d@ernst.jennejohn.org> On Sun, 20 Sep 2009 19:15:01 +0200 Gary Jennejohn wrote: > So, I have a problem with VirtualBox and can't say whether it's a problem > with VirtualBox itself or something which has changed in the kernel. > > I'm running FreeBSD 9.0-CURRENT Wed Sep 16 11:40:19 CEST 2009 amd64. > > I installed both the port and the latest stuff from svn. > > The problem is with an installation of Windows 7 RC which was working > fine with an older version of the port (can't say from when, though) > AND of the kernel. > > Today I decided to try the latest version of VirtualBox and the W7RC > fails upon booting with an internal VirtualBox error. > > Strangely enough, if I start W7RC in repair mode it happily runs to > completion, but then the boot fails with the above mentioned error. > > Booting from the ISO also fails. > > I have all kinds of log files from VirtualBox which I can't parse. > > Interestingly enough, the two Linux installations, which are from > about the same time as the W7RC installation, still run flawlessly. > > Has anyone else seen any strangeness with the newer versions of VirtualBox > and a fairly recent 9.0-CURRENT? > Since I never got any response to this, I'll relate what I've found out. If I turn off acceleration in Settings->System->Acceleration W7RC runs, although it's very slow. Something broke somewhere, but I can't say whether in VirtualBox or the kernel. --- Gary Jennejohn From scf at FreeBSD.org Tue Sep 22 18:46:55 2009 From: scf at FreeBSD.org (Sean C. Farley) Date: Tue Sep 22 18:47:02 2009 Subject: Panic with vboxnet drivers Message-ID: While I have had no trouble with two systems running with the tap patch, I am experiencing some lockups when using the vboxnet* drivers. I have five witness logs (attached): 1. The first one appeared when I tried to run VirtualBox with vboxnetadp loaded via loader.conf. VirtualBox will not be able to find the VirtualBox network drivers this way, so I unloaded and loaded vboxnetadp from the command line for the following logs. 2. The next three logs are LOR's (sleepable after non-sleepable) concerning VirtualBox's "IPRT Fast Mutex Semaphore" which is an sx. I am not sure I am reading the backtrace correctly. It looks like the call to RTSemFastMutexRequest(), which calls sx_xlock(), is the effect. I just do not know where the cause, i.e., RTSemFastMutexRequest(), is being called. 3. The last log is a LOR, but it may not be related to VirtualBox. Does _end() represent a special function called after any function returns? The easiest way to induce a panic is to scp a large file into a VM and then start a download of a file over the same network device of the host that vboxnet0 is bridged. It usually takes a few seconds. This occurs on two different systems running 7-STABLE (r196739): 1. i386, em0, gmirror 2. amd64, em0, no gmirror Here is the only panic that ever made it to the disk. Most of the time it just locks the system. Unread portion of the kernel message buffer: Sleeping thread (tid 100048, pid 48) owns a non-sleepable lock panic: sleeping thread cpuid = 0 Sleeping thread (tid 100048, pid 48) owns a non-sleepable lock panic: sleeping thread cpuid = 0 Uptime: 27m12s Physical memory: 3306 MB Dumping 236 MB: 221 205 189 173 157 141 125 109 93 77 61 45 29 13 #0 doadump () at pcpu.h:196 #1 0xc057bf87 in boot (howto=260) at /usr/FreeBSD/RELENG_7/src/sys/kern/kern_shutdown.c:418 #2 0xc057c259 in panic (fmt=Variable "fmt" is not available.) at /usr/FreeBSD/RELENG_7/src/sys/kern/kern_shutdown.c:574 #3 0xc05b3a7e in propagate_priority (td=0xc71b8b40) at /usr/FreeBSD/RELENG_7/src/sys/kern/subr_turnstile.c:222 #4 0xc05b3b89 in turnstile_adjust (td=0xc7638b40, oldpri=128 '\200') at /usr/FreeBSD/RELENG_7/src/sys/kern/subr_turnstile.c:442 #5 0xc059d6fb in sched_prio (td=0xc7638b40, prio=76 'L') at /usr/FreeBSD/RELENG_7/src/sys/kern/sched_ule.c:1726 #6 0xc058444d in _sleep (ident=0xc7486870, lock=0x0, priority=76, wmesg=0xc09ab880 "m:destroy", timo=200) at /usr/FreeBSD/RELENG_7/src/sys/kern/kern_synch.c:219 #7 0xc09a5441 in g_mirror_destroy (sc=0xc7486800, how=1) at /usr/FreeBSD/RELENG_7/src/sys/modules/geom/geom_mirror/../../../geom/mirror/g_mirror.c:2975 #8 0xc09a57e7 in g_mirror_shutdown_pre_sync (arg=0xc09ad3e0, howto=260) at /usr/FreeBSD/RELENG_7/src/sys/modules/geom/geom_mirror/../../../geom/mirror/g_mirror.c:3235 #9 0xc057b9f3 in boot (howto=260) at /usr/FreeBSD/RELENG_7/src/sys/kern/kern_shutdown.c:296 #10 0xc057c259 in panic (fmt=Variable "fmt" is not available.) at /usr/FreeBSD/RELENG_7/src/sys/kern/kern_shutdown.c:574 #11 0xc05b3a7e in propagate_priority (td=0xc71b8b40) at /usr/FreeBSD/RELENG_7/src/sys/kern/subr_turnstile.c:222 #12 0xc05b4948 in turnstile_wait (ts=0xc763a4b0, owner=0xc71b8b40, queue=Variable "queue" is not available.) at /usr/FreeBSD/RELENG_7/src/sys/kern/subr_turnstile.c:740 #13 0xc057aa88 in _rw_wlock_hard (rw=0xc7a9f36c, tid=3345189696, file=0x0, line=0) at /usr/FreeBSD/RELENG_7/src/sys/kern/kern_rwlock.c:686 #14 0xc06aaadb in tcp_usr_rcvd (so=0xc7a16000, flags=0) at /usr/FreeBSD/RELENG_7/src/sys/netinet/tcp_usrreq.c:707 #15 0xc05d8f93 in soreceive_generic (so=0xc7a16000, psa=0xe9bafbe8, uio=0xe9bafbf4, mp0=0x0, controlp=0x0, flagsp=0xe9bafc78) at /usr/FreeBSD/RELENG_7/src/sys/kern/uipc_socket.c:1828 #16 0xc05d3788 in soreceive (so=0xc7a16000, psa=0xe9bafbe8, uio=0xe9bafbf4, mp0=0x0, controlp=0x0, flagsp=0xe9bafc78) at /usr/FreeBSD/RELENG_7/src/sys/kern/uipc_socket.c:2032 #17 0xc05da5a5 in kern_recvit (td=0xc7638b40, s=3, mp=0xe9bafc60, fromseg=UIO_USERSPACE, controlp=0x0) at /usr/FreeBSD/RELENG_7/src/sys/kern/uipc_syscalls.c:1002 #18 0xc05da7b1 in recvit (td=Variable "td" is not available.) at /usr/FreeBSD/RELENG_7/src/sys/kern/uipc_syscalls.c:1113 #19 0xc05da926 in recvfrom (td=0xc7638b40, uap=0xe9bafcfc) at /usr/FreeBSD/RELENG_7/src/sys/kern/uipc_syscalls.c:1157 #20 0xc07cb085 in syscall (frame=0xe9bafd38) at /usr/FreeBSD/RELENG_7/src/sys/i386/i386/trap.c:1094 #21 0xc07b0c80 in Xint0x80_syscall () at /usr/FreeBSD/RELENG_7/src/sys/i386/i386/exception.s:262 #22 0x00000033 in ?? () Previous frame inner to this frame (corrupt stack?) Here is the output from the sleeping thread: #0 sched_switch (td=0xc71b8b40, newtd=Variable "newtd" is not available.) at /usr/FreeBSD/RELENG_7/src/sys/kern/sched_ule.c:1944 #1 0xc0584046 in mi_switch (flags=Variable "flags" is not available.) at /usr/FreeBSD/RELENG_7/src/sys/kern/kern_synch.c:444 #2 0xc05b080b in sleepq_switch (wchan=Variable "wchan" is not available.) at /usr/FreeBSD/RELENG_7/src/sys/kern/subr_sleepqueue.c:497 #3 0xc05b0e56 in sleepq_wait (wchan=0xc7be02d4) at /usr/FreeBSD/RELENG_7/src/sys/kern/subr_sleepqueue.c:580 #4 0xc058388e in _sx_xlock_hard (sx=0xc7be02d4, tid=3340471104, opts=0, file=0xc0acb042 "/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22902/src/VBox/Runtime/r0drv/freebsd/semfastmutex-r0drv-freebsd.c", line=103) at /usr/FreeBSD/RELENG_7/src/sys/kern/kern_sx.c:560 #5 0xc0583c28 in _sx_xlock (sx=0xc7be02d4, opts=0, file=0xc0acb042 "/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22902/src/VBox/Runtime/r0drv/freebsd/semfastmutex-r0drv-freebsd.c", line=103) at sx.h:154 #6 0xc0ab8351 in RTSemFastMutexRequest () from /boot/modules/vboxdrv.ko #7 0xc7f3d82a in ?? () #8 0xc7be02d0 in ?? () #9 0xc85b6c00 in ?? () #10 0x00000000 in ?? () #11 0xc8338a90 in ?? () #12 0xc8338a90 in ?? () #13 0xc85b6c00 in ?? () #14 0xe788f6e4 in ?? () #15 0xc7ee10bb in ng_vboxnetflt_rcvdata () from /boot/modules/vboxnetflt.ko The thread itself is: 49 Thread 100048 (PID=48: em0 taskq) sched_switch (td=0xc71b8b40, newtd=Variable "newtd" is not available.) at /usr/FreeBSD/RELENG_7/src/sys/kern/sched_ule.c:1944 While em0 taskq is the thread, is it really the em driver's fault or vboxnetflt? Does the panic message mean that the priority was changed while holding a spinlock? Sean -- scf@FreeBSD.org From jhs at berklix.com Tue Sep 22 22:12:04 2009 From: jhs at berklix.com (Julian H. Stacey) Date: Tue Sep 22 22:12:30 2009 Subject: VirtualBox/kernel broken? In-Reply-To: Your message "Tue, 22 Sep 2009 12:46:06 +0200." <20090922124606.0a9aee4d@ernst.jennejohn.org> Message-ID: <200909222143.n8MLhWa8065001@fire.js.berklix.net> Gary Jennejohn wrote: > On Sun, 20 Sep 2009 19:15:01 +0200 > Gary Jennejohn wrote: > > > So, I have a problem with VirtualBox and can't say whether it's a problem > > with VirtualBox itself or something which has changed in the kernel. > > > > I'm running FreeBSD 9.0-CURRENT Wed Sep 16 11:40:19 CEST 2009 amd64. > > > > I installed both the port and the latest stuff from svn. > > > > The problem is with an installation of Windows 7 RC which was working > > fine with an older version of the port (can't say from when, though) > > AND of the kernel. > > > > Today I decided to try the latest version of VirtualBox and the W7RC > > fails upon booting with an internal VirtualBox error. > > > > Strangely enough, if I start W7RC in repair mode it happily runs to > > completion, but then the boot fails with the above mentioned error. > > > > Booting from the ISO also fails. > > > > I have all kinds of log files from VirtualBox which I can't parse. > > > > Interestingly enough, the two Linux installations, which are from > > about the same time as the W7RC installation, still run flawlessly. > > > > Has anyone else seen any strangeness with the newer versions of VirtualBox > > and a fairly recent 9.0-CURRENT? > > > > Since I never got any response to this, I'll relate what I've found out. > > If I turn off acceleration in Settings->System->Acceleration W7RC runs, > although it's very slow. > > Something broke somewhere, but I can't say whether in VirtualBox or the > kernel. Hi Gary, cc list. I tried to see if I could cast light on the above, using my 7.2-RELEASE kernel, + current/ports/emulators/virtualbox sources as of yesterday, built yesterday. I did dd bs=2k of my genuine Toshiba XP cdrom, tried to install it, & got an error from Tosh/Mickeysoft "Wrong machine This software is designed for TOSHIBA Personal Computers" As suspected, the XP that Toshiba sold bundled with my laptop is a crippled version, looking for Toshiba hardware warts. I assume Virtualbox is providing a nice generic environment without Tosh warts. (The above both running Virtualbox as normal user & root, from a .iso file, I tried running VirtualBox from original cdrom in drive, but failed, likely my user error). I hope someone else can give you a more useful response. Cheers, Julian -- Julian Stacey: BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Mail ASCII plain text not HTML & Base64. http://asciiribbon.org Virused Microsoft PCs cause spam. http://berklix.com/free/ From nox at jelal.kn-bremen.de Wed Sep 23 18:33:47 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Wed Sep 23 18:33:59 2009 Subject: Panic with vboxnet drivers In-Reply-To: Message-ID: <200909231832.n8NIWNVw002447@triton8.kn-bremen.de> In article you write: >While I have had no trouble with two systems running with the tap patch, >I am experiencing some lockups when using the vboxnet* drivers. > >I have five witness logs (attached): >1. The first one appeared when I tried to run VirtualBox with vboxnetadp > loaded via loader.conf. VirtualBox will not be able to find the > VirtualBox network drivers this way, so I unloaded and loaded > vboxnetadp from the command line for the following logs. >2. The next three logs are LOR's (sleepable after non-sleepable) > concerning VirtualBox's "IPRT Fast Mutex Semaphore" which is an sx. > I am not sure I am reading the backtrace correctly. It looks like > the call to RTSemFastMutexRequest(), which calls sx_xlock(), is the > effect. I just do not know where the cause, i.e., > RTSemFastMutexRequest(), is being called. >3. The last log is a LOR, but it may not be related to VirtualBox. >[...] It seems the attachments got stripped... Juergen From scf at FreeBSD.org Wed Sep 23 18:41:39 2009 From: scf at FreeBSD.org (Sean C. Farley) Date: Wed Sep 23 18:41:45 2009 Subject: Panic with vboxnet drivers In-Reply-To: <200909231832.n8NIWNVw002447@triton8.kn-bremen.de> References: <200909231832.n8NIWNVw002447@triton8.kn-bremen.de> Message-ID: On Wed, 23 Sep 2009, Juergen Lock wrote: > In article you write: >> While I have had no trouble with two systems running with the tap >> patch, I am experiencing some lockups when using the vboxnet* >> drivers. >> >> I have five witness logs (attached): >> 1. The first one appeared when I tried to run VirtualBox with >> vboxnetadp loaded via loader.conf. VirtualBox will not be able to >> find the VirtualBox network drivers this way, so I unloaded and >> loaded vboxnetadp from the command line for the following logs. >> 2. The next three logs are LOR's (sleepable after non-sleepable) >> concerning VirtualBox's "IPRT Fast Mutex Semaphore" which is an >> sx. I am not sure I am reading the backtrace correctly. It looks >> like the call to RTSemFastMutexRequest(), which calls sx_xlock(), >> is the effect. I just do not know where the cause, i.e., >> RTSemFastMutexRequest(), is being called. >> 3. The last log is a LOR, but it may not be related to VirtualBox. >> [...] > > It seems the attachments got stripped... Oops. I think I forgot to attach them. :) Here they are now: http://people.freebsd.org/~scf/vb-witness.log Sean -- scf@FreeBSD.org From dougb at FreeBSD.org Thu Sep 24 21:19:18 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Thu Sep 24 21:19:25 2009 Subject: Does vbox have support for cd-rom or usb in winxp guest? Message-ID: <4ABBE24E.3090306@FreeBSD.org> The 2 most recent versions of vbox have been stable enough for me to start using them for real work, so congrats to those working on the port! So naturally, now I want more. :) Specifically I'm curious about cd-rom and usb support. When I start the gui and go to settings for my existing winxp guest my cd-rom drive is not available on the spinner for "Host CD/DVD Drive." Is that expected? Is there something I need to do differently to make that available? I'm also curious about access to USB devices. I don't even see options for that, so is it just not possible? Thanks, Doug -- This .signature sanitized for your protection From oberman at es.net Thu Sep 24 21:30:53 2009 From: oberman at es.net (Kevin Oberman) Date: Thu Sep 24 21:31:00 2009 Subject: Does vbox have support for cd-rom or usb in winxp guest? In-Reply-To: Your message of "Thu, 24 Sep 2009 14:19:10 PDT." <4ABBE24E.3090306@FreeBSD.org> Message-ID: <20090924213052.6BF031CC39@ptavv.es.net> > Date: Thu, 24 Sep 2009 14:19:10 -0700 > From: Doug Barton > Sender: owner-freebsd-emulation@freebsd.org > > The 2 most recent versions of vbox have been stable enough for me to > start using them for real work, so congrats to those working on the > port! So naturally, now I want more. :) > > Specifically I'm curious about cd-rom and usb support. When I start > the gui and go to settings for my existing winxp guest my cd-rom drive > is not available on the spinner for "Host CD/DVD Drive." Is that > expected? Is there something I need to do differently to make that > available? > > I'm also curious about access to USB devices. I don't even see options > for that, so is it just not possible? > > > Thanks, > > Doug > > -- > > This .signature sanitized for your protection > > _______________________________________________ > freebsd-emulation@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-emulation > To unsubscribe, send any mail to "freebsd-emulation-unsubscribe@freebsd.org" > Doug, I am NOT involved with VirtualBox porting, but I suggest that you see the VB wiki page . It is kept pretty current. It does have information on making the CD/DVD work. (Mostly protection issues.) It also lists the last two features not yet supported by the port...USB and OpenGL. :-( I really need USB, as well, as I need to sync my phone (Treo) regularly to our calendar. Other than the USB, everything seems to work great for a Windows 7 guest. I just need a bit more memory so I don't spend so much time paging. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 From amvandemore at gmail.com Thu Sep 24 21:31:23 2009 From: amvandemore at gmail.com (Adam Vande More) Date: Thu Sep 24 21:31:30 2009 Subject: Does vbox have support for cd-rom or usb in winxp guest? In-Reply-To: <4ABBE24E.3090306@FreeBSD.org> References: <4ABBE24E.3090306@FreeBSD.org> Message-ID: <6201873e0909241431h4df17f6fv8c8a8b5f594503d2@mail.gmail.com> On Thu, Sep 24, 2009 at 4:19 PM, Doug Barton wrote: > The 2 most recent versions of vbox have been stable enough for me to > start using them for real work, so congrats to those working on the > port! So naturally, now I want more. :) > > Specifically I'm curious about cd-rom and usb support. When I start > the gui and go to settings for my existing winxp guest my cd-rom drive > is not available on the spinner for "Host CD/DVD Drive." Is that > expected? Is there something I need to do differently to make that > available? > > I'm also curious about access to USB devices. I don't even see options > for that, so is it just not possible? > > > Thanks, > > Doug > I'm not sure, but I think atapicam is required for cdrom access. -- Adam Vande More From dougb at FreeBSD.org Thu Sep 24 21:42:24 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Thu Sep 24 21:42:31 2009 Subject: Does vbox have support for cd-rom or usb in winxp guest? In-Reply-To: <20090924213052.6BF031CC39@ptavv.es.net> References: <20090924213052.6BF031CC39@ptavv.es.net> Message-ID: <4ABBE7B8.6070205@FreeBSD.org> Kevin Oberman wrote: > Doug, > > I am NOT involved with VirtualBox porting, but I suggest that you see > the VB wiki page . It is kept pretty > current. > > It does have information on making the CD/DVD work. Thanks! I'm trying to avoid running HAL so unless my needs become much greater I'll stick with mounting ISOs for now. > (Mostly protection > issues.) It also lists the last two features not yet supported by the > port...USB and OpenGL. :-( I really need USB, as well, as I need to > sync my phone (Treo) regularly to our calendar. Yeah, I'd like to be able to sync my iPhone. That's the last thing I know for sure I need at the moment. Doug -- This .signature sanitized for your protection From fli at shapeshifter.se Thu Sep 24 21:54:57 2009 From: fli at shapeshifter.se (Fredrik Lindberg) Date: Thu Sep 24 21:55:03 2009 Subject: Does vbox have support for cd-rom or usb in winxp guest? In-Reply-To: <4ABBE24E.3090306@FreeBSD.org> References: <4ABBE24E.3090306@FreeBSD.org> Message-ID: <4ABBEAAF.9020409@shapeshifter.se> Doug Barton wrote: > > I'm also curious about access to USB devices. I don't even see options > for that, so is it just not possible? > The open source edition of VirtualBox doesn't include any USB support nor the virtual USB controller, it's a closed source component. Details at http://www.virtualbox.org/wiki/Editions Fredrik From dougb at FreeBSD.org Thu Sep 24 23:50:49 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Thu Sep 24 23:50:55 2009 Subject: Does vbox have support for cd-rom or usb in winxp guest? In-Reply-To: <4ABBEAAF.9020409@shapeshifter.se> References: <4ABBE24E.3090306@FreeBSD.org> <4ABBEAAF.9020409@shapeshifter.se> Message-ID: <4ABC05CD.6090108@FreeBSD.org> Fredrik Lindberg wrote: > Doug Barton wrote: >> >> I'm also curious about access to USB devices. I don't even see options >> for that, so is it just not possible? >> > > The open source edition of VirtualBox doesn't include any USB support > nor the virtual USB controller, it's a closed source component. > > Details at http://www.virtualbox.org/wiki/Editions Wow, what a bad web site! :) Where would I go to buy the closed source version, and could I run it on FreeBSD if I did? Doug -- This .signature sanitized for your protection From fli at shapeshifter.se Fri Sep 25 08:29:04 2009 From: fli at shapeshifter.se (Fredrik Lindberg) Date: Fri Sep 25 08:29:10 2009 Subject: Does vbox have support for cd-rom or usb in winxp guest? In-Reply-To: <4ABC05CD.6090108@FreeBSD.org> References: <4ABBE24E.3090306@FreeBSD.org> <4ABBEAAF.9020409@shapeshifter.se> <4ABC05CD.6090108@FreeBSD.org> Message-ID: <4ABC7F49.2060809@shapeshifter.se> Doug Barton wrote: > Fredrik Lindberg wrote: >> Doug Barton wrote: >>> I'm also curious about access to USB devices. I don't even see options >>> for that, so is it just not possible? >>> >> The open source edition of VirtualBox doesn't include any USB support >> nor the virtual USB controller, it's a closed source component. >> >> Details at http://www.virtualbox.org/wiki/Editions > > Wow, what a bad web site! :) Where would I go to buy the closed > source version, and could I run it on FreeBSD if I did? > The closed source version is free (as in beer) for personal use but as far as I know they don't have any binaries for FreeBSD. Fredrik From gary.jennejohn at freenet.de Fri Sep 25 09:38:37 2009 From: gary.jennejohn at freenet.de (Gary Jennejohn) Date: Fri Sep 25 09:38:44 2009 Subject: Does vbox have support for cd-rom or usb in winxp guest? In-Reply-To: <20090924213052.6BF031CC39@ptavv.es.net> References: <4ABBE24E.3090306@FreeBSD.org> <20090924213052.6BF031CC39@ptavv.es.net> Message-ID: <20090925113834.09dad3e2@ernst.jennejohn.org> On Thu, 24 Sep 2009 14:30:52 -0700 "Kevin Oberman" wrote: > Other than the USB, everything seems to work great for a Windows 7 > guest. I just need a bit more memory so I don't spend so much time > paging. > This statement interests me because, as I've posted several times, I can't even start W7RC with acceleration turned on (running a recent 9-CURRENT). Everything worked with older versions of the kernel and port. What version of FreeBSD and of the port are you using? --- Gary Jennejohn From oberman at es.net Fri Sep 25 16:17:44 2009 From: oberman at es.net (Kevin Oberman) Date: Fri Sep 25 16:17:50 2009 Subject: Does vbox have support for cd-rom or usb in winxp guest? In-Reply-To: Your message of "Fri, 25 Sep 2009 11:38:34 +0200." <20090925113834.09dad3e2@ernst.jennejohn.org> Message-ID: <20090925161738.403D41CC13@ptavv.es.net> > Date: Fri, 25 Sep 2009 11:38:34 +0200 > From: Gary Jennejohn > > On Thu, 24 Sep 2009 14:30:52 -0700 > "Kevin Oberman" wrote: > > > Other than the USB, everything seems to work great for a Windows 7 > > guest. I just need a bit more memory so I don't spend so much time > > paging. > > > > This statement interests me because, as I've posted several times, I can't > even start W7RC with acceleration turned on (running a recent 9-CURRENT). > Everything worked with older versions of the kernel and port. > > What version of FreeBSD and of the port are you using? Yes, I have seen your reports and I don't see anything like it. I'm running FreeBSD 8.0-RC1 and have been using VB running Windows 7 Release (not RC) since 8.0-BETA1. I have used both NAT and bridged networking and both work fine for me. No problems encountered at all other than that memory utilization tends to sit at 85% or more and paging and swapping on the Windows system makes it very slow and makes running more than one app at a time impractical. W7 simply can't run well with 512 MB of memory. I ordered memory for my ThinkPad yesterday, so I hope that I'll have double the memory next week. If it would work for FreeBSD, I would be quite willing to buy a commercial version to get the USB to work! Of course, neither the VB nor the Sun Microsystems web sites provide any clue as to how to buy it, even if it could work. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 From gary.jennejohn at freenet.de Fri Sep 25 16:31:30 2009 From: gary.jennejohn at freenet.de (Gary Jennejohn) Date: Fri Sep 25 16:31:37 2009 Subject: Does vbox have support for cd-rom or usb in winxp guest? In-Reply-To: <20090925161738.403D41CC13@ptavv.es.net> References: <20090925113834.09dad3e2@ernst.jennejohn.org> <20090925161738.403D41CC13@ptavv.es.net> Message-ID: <20090925183126.361f54aa@ernst.jennejohn.org> On Fri, 25 Sep 2009 09:17:38 -0700 "Kevin Oberman" wrote: > > Date: Fri, 25 Sep 2009 11:38:34 +0200 > > From: Gary Jennejohn > > > > On Thu, 24 Sep 2009 14:30:52 -0700 > > "Kevin Oberman" wrote: > > > > > Other than the USB, everything seems to work great for a Windows 7 > > > guest. I just need a bit more memory so I don't spend so much time > > > paging. > > > > > > > This statement interests me because, as I've posted several times, I can't > > even start W7RC with acceleration turned on (running a recent 9-CURRENT). > > Everything worked with older versions of the kernel and port. > > > > What version of FreeBSD and of the port are you using? > > Yes, I have seen your reports and I don't see anything like it. > > I'm running FreeBSD 8.0-RC1 and have been using VB running Windows 7 > Release (not RC) since 8.0-BETA1. > This sort of confirms my suspicion that something has changed in the 9-CURRENT kernel to break VirtualBox. It worked just fine until I installed a new kernel at the beginning of last week :( Hmm, you're running an Intel box? I run AMD64. Might also be a factor. > networking and both work fine for me. No problems encountered at all > other than that memory utilization tends to sit at 85% or more and > paging and swapping on the Windows system makes it very slow and makes > running more than one app at a time impractical. W7 simply can't run > well with 512 MB of memory. > > I ordered memory for my ThinkPad yesterday, so I hope that I'll have > double the memory next week. > More memory definitely helps. I allocated 1GB to W7RC and it runs OK with that. But then, I have 4GB in my box. --- Gary Jennejohn From oberman at es.net Fri Sep 25 16:46:02 2009 From: oberman at es.net (Kevin Oberman) Date: Fri Sep 25 16:46:14 2009 Subject: Does vbox have support for cd-rom or usb in winxp guest? In-Reply-To: Your message of "Fri, 25 Sep 2009 18:31:26 +0200." <20090925183126.361f54aa@ernst.jennejohn.org> Message-ID: <20090925164557.52BA41CC0E@ptavv.es.net> > Date: Fri, 25 Sep 2009 18:31:26 +0200 > From: Gary Jennejohn > > On Fri, 25 Sep 2009 09:17:38 -0700 > "Kevin Oberman" wrote: > > > > Date: Fri, 25 Sep 2009 11:38:34 +0200 > > > From: Gary Jennejohn > > > > > > On Thu, 24 Sep 2009 14:30:52 -0700 > > > "Kevin Oberman" wrote: > > > > > > > Other than the USB, everything seems to work great for a Windows 7 > > > > guest. I just need a bit more memory so I don't spend so much time > > > > paging. > > > > > > > > > > This statement interests me because, as I've posted several times, I can't > > > even start W7RC with acceleration turned on (running a recent 9-CURRENT). > > > Everything worked with older versions of the kernel and port. > > > > > > What version of FreeBSD and of the port are you using? > > > > Yes, I have seen your reports and I don't see anything like it. > > > > I'm running FreeBSD 8.0-RC1 and have been using VB running Windows 7 > > Release (not RC) since 8.0-BETA1. > > > > This sort of confirms my suspicion that something has changed in the > 9-CURRENT kernel to break VirtualBox. It worked just fine until I > installed a new kernel at the beginning of last week :( > > Hmm, you're running an Intel box? I run AMD64. Might also be a factor. Yes, it is a 4 year old 2 GHz Pentium-M, so AMD64 is not available. > > > networking and both work fine for me. No problems encountered at all > > other than that memory utilization tends to sit at 85% or more and > > paging and swapping on the Windows system makes it very slow and makes > > running more than one app at a time impractical. W7 simply can't run > > well with 512 MB of memory. > > > > I ordered memory for my ThinkPad yesterday, so I hope that I'll have > > double the memory next week. > > > > More memory definitely helps. I allocated 1GB to W7RC and it runs OK > with that. But then, I have 4GB in my box. Due to the Intel 915 chip, my system is restricted to 2 GB, but that will let me run a 1G guest. The VB is on a USB disk, too, which does not help performance, but lets me move the guest system from host to host which is proving very handy! -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 From dougb at FreeBSD.org Fri Sep 25 17:24:12 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Fri Sep 25 17:24:18 2009 Subject: Does vbox have support for cd-rom or usb in winxp guest? In-Reply-To: <20090925183126.361f54aa@ernst.jennejohn.org> References: <20090925113834.09dad3e2@ernst.jennejohn.org> <20090925161738.403D41CC13@ptavv.es.net> <20090925183126.361f54aa@ernst.jennejohn.org> Message-ID: <4ABCFCAF.30807@FreeBSD.org> Gary Jennejohn wrote: > This sort of confirms my suspicion that something has changed in the > 9-CURRENT kernel to break VirtualBox. It worked just fine until I > installed a new kernel at the beginning of last week :( I'm using 9-current and I update just about every day, so it's not universal. Did you rebuild your virtualbox port after updating your kernel? And did you do a complete buildworld and installworld? Doug -- This .signature sanitized for your protection From nox at jelal.kn-bremen.de Fri Sep 25 23:14:31 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Fri Sep 25 23:14:37 2009 Subject: qemu 0.11.0 on FreeBSD - port update for testing Message-ID: <20090925230920.GA46757@triton8.kn-bremen.de> Hi! So qemu 0.11.0 is out, the first version off the new stable branch, and I've now made an update for (for the moment) the emulators/qemu-devel port, http://people.freebsd.org/~nox/qemu/qemu-devel-0.11.0.patch that could use some testing before I commit it as emulators/qemu, especially because its a new branch... I have added the serial emulation fix again (which has been committed to the stable branch now too but after 0.11.0 was tagged; the only other fix committed since then - MAX_OP_PER_INSTR - has already been in the FreeBSD ports since back when I first reported it - only that I used an even higher value now that I look, I'll lower it later.) I already noticed one thing tho: I have updated the pcap patch to (mostly) the code Jung-uk Kim sent me for the git snapshot, and now packets especially from the host seem to be received late i.e. I see ping times of ~1000ms and ssh'ing to the host is laggy too - maybe setting BIOCIMMEDIATE doesn't work properly anymore with the new code? (Btw the git snapshot is affected too, I just didn't notice before.) Enjoy, Juergen From gary.jennejohn at freenet.de Sat Sep 26 09:11:03 2009 From: gary.jennejohn at freenet.de (Gary Jennejohn) Date: Sat Sep 26 09:11:10 2009 Subject: Does vbox have support for cd-rom or usb in winxp guest? In-Reply-To: <4ABCFCAF.30807@FreeBSD.org> References: <20090925113834.09dad3e2@ernst.jennejohn.org> <20090925161738.403D41CC13@ptavv.es.net> <20090925183126.361f54aa@ernst.jennejohn.org> <4ABCFCAF.30807@FreeBSD.org> Message-ID: <20090926111101.0176d5b4@ernst.jennejohn.org> On Fri, 25 Sep 2009 10:23:59 -0700 Doug Barton wrote: > Gary Jennejohn wrote: > > This sort of confirms my suspicion that something has changed in the > > 9-CURRENT kernel to break VirtualBox. It worked just fine until I > > installed a new kernel at the beginning of last week :( > > I'm using 9-current and I update just about every day, so it's not > universal. > Acceleration works with Linux, but not with Windows 7 RC. So, it's not really universal for me either. But it _did_ work with W7RC about 2 weeks ago. > Did you rebuild your virtualbox port after updating your kernel? And > did you do a complete buildworld and installworld? > Yes and yes. I've tried both the port and svn for VirtualBox. --- Gary Jennejohn From danny at cs.huji.ac.il Sun Sep 27 09:29:56 2009 From: danny at cs.huji.ac.il (Daniel Braniss) Date: Sun Sep 27 09:30:04 2009 Subject: Vbox/PXE booting works Message-ID: hi, the works should be 'works sometimes', but it's a great! take a look at: http://www.etherboot.org/wiki/romburning/vbox (thanks to "Miller, Shao" for pointing it out to me) the gPXE compiles under linux, but if anyone is interested, i've placed the 1022200.rom in: ftp://ftp.cs.huji.ac.il/users/danny/freebsd/vbox/1022200.rom I'm using the svn version, and PCnet-FAST II (the III booted, but then hung) danny From linimon at FreeBSD.org Sun Sep 27 16:06:08 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Sun Sep 27 16:06:20 2009 Subject: ports/139188: [panic] emulators/virtualbox: When "kldload vboxdrv.ko" is done, kernel panics Message-ID: <200909271606.n8RG68JQ051524@freefall.freebsd.org> Old Synopsis: When "kldload vboxdrv.ko" is done, panic kernel is done. New Synopsis: [panic] emulators/virtualbox: When "kldload vboxdrv.ko" is done, kernel panics Responsible-Changed-From-To: freebsd-ports-bugs->freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Sun Sep 27 16:04:13 UTC 2009 Responsible-Changed-Why: Not really sure if this should be assigned as kern or ports, but have to pick one anyways. http://www.freebsd.org/cgi/query-pr.cgi?pr=139188 From linimon at FreeBSD.org Sun Sep 27 16:06:31 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Sun Sep 27 16:06:37 2009 Subject: ports/139188: [panic] emulators/virtualbox: When "kldload vboxdrv.ko" is done, kernel panics Message-ID: <200909271606.n8RG6VZN051576@freefall.freebsd.org> Synopsis: [panic] emulators/virtualbox: When "kldload vboxdrv.ko" is done, kernel panics Responsible-Changed-From-To: freebsd-emulation->vbox Responsible-Changed-By: linimon Responsible-Changed-When: Sun Sep 27 16:06:13 UTC 2009 Responsible-Changed-Why: Over to correct mailing list. http://www.freebsd.org/cgi/query-pr.cgi?pr=139188 From bugmaster at FreeBSD.org Mon Sep 28 11:06:52 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Sep 28 11:07:46 2009 Subject: Current problem reports assigned to freebsd-emulation@FreeBSD.org Message-ID: <200909281106.n8SB6qLG063965@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/138944 emulation [parallels] [regression] Parallels no longer works in o kern/138880 emulation [linux] munmap segfaults after linux_mmap2 stresstest o ports/137332 emulation add caution messages to some adobe products f ports/136321 emulation x11-toolkits/linux-pango: please update linux based po o ports/136229 emulation [linux] certain linux apps look for libraries using a o ports/135337 emulation [PATCH] emulators/linux_base-f10: incorrect bash usage o ports/135322 emulation Port graphics/linux_dri has incorrect packaging list c o kern/130724 emulation [linprocfs] [patch] cpuinfo in linprocfs is dated, cau o kern/129169 emulation [linux] [patch] Linux Emulation ENOTCONN error using n f ports/127018 emulation Linuxulator incapable of using FreeBSD's LDAP environm o kern/126232 emulation [linux] Linux ioctl TCGETS (0x5401) always fails o kern/97326 emulation [linux] file descriptor leakage in linux emulation o kern/73777 emulation [linux] [patch] linux emulation: root dir special hand a kern/72920 emulation [linux]: path "prefixing" is not done on unix domain s o kern/56451 emulation [linprocfs] /compat/linux/proc/cpuinfo gives wrong CPU o kern/41543 emulation [patch] [request] easier wine/w23 support o kern/39201 emulation [linux] [patch] ptrace(2) and rfork(RFLINUXTHPN) confu o kern/29698 emulation [linux] [patch] linux ipcs doesn'work o kern/21463 emulation [linux] Linux compatability mode should not allow setu o kern/11165 emulation [ibcs2] IBCS2 doesn't work correctly with PID_MAX 9999 20 problems total. From fli at shapeshifter.se Mon Sep 28 20:48:04 2009 From: fli at shapeshifter.se (Fredrik Lindberg) Date: Mon Sep 28 20:48:11 2009 Subject: Panic with vboxnet drivers In-Reply-To: References: Message-ID: <4AC120F6.7090701@shapeshifter.se> Sean C. Farley wrote: > While I have had no trouble with two systems running with the tap patch, > I am experiencing some lockups when using the vboxnet* drivers. > Sorry about the late response. > I have five witness logs (attached): > 1. The first one appeared when I tried to run VirtualBox with vboxnetadp > loaded via loader.conf. VirtualBox will not be able to find the > VirtualBox network drivers this way, so I unloaded and loaded > vboxnetadp from the command line for the following logs. Need to look a bit more on this one. > 2. The next three logs are LOR's (sleepable after non-sleepable) > concerning VirtualBox's "IPRT Fast Mutex Semaphore" which is an sx. > I am not sure I am reading the backtrace correctly. It looks like > the call to RTSemFastMutexRequest(), which calls sx_xlock(), is the > effect. I just do not know where the cause, i.e., > RTSemFastMutexRequest(), is being called. Yeah, this was a real one. The call to RTSemFastMutexRequest is inside the virtual ethernet switch. I've attached a patch that defers processing to avoid the sleepable after non-sleepable case. Hopefully this fixes the panic you're seeing as well. Fredrik -------------- next part -------------- Index: src/VBox/HostDrivers/VBoxNetFlt/freebsd/VBoxNetFlt-freebsd.c =================================================================== --- src/VBox/HostDrivers/VBoxNetFlt/freebsd/VBoxNetFlt-freebsd.c (revision 23391) +++ src/VBox/HostDrivers/VBoxNetFlt/freebsd/VBoxNetFlt-freebsd.c (working copy) @@ -43,6 +43,8 @@ #include #include #include +#include +#include #include #include @@ -78,8 +80,6 @@ static ng_rcvdata_t ng_vboxnetflt_rcvdata; static ng_disconnect_t ng_vboxnetflt_disconnect; static int ng_vboxnetflt_mod_event(module_t mod, int event, void *data); -static int ng_vboxnetflt_rcv_in(hook_p node, item_p item); -static int ng_vboxnetflt_rcv_out(hook_p node, item_p item); /** Netgraph node type */ #define NG_VBOXNETFLT_NODE_TYPE "vboxnetflt" @@ -112,8 +112,8 @@ { .version = NG_ABI_VERSION, .name = NG_VBOXNETFLT_NODE_TYPE, - .mod_event = vboxnetflt_modevent, - .constructor = ng_vboxnetflt_constructor, + .mod_event = vboxnetflt_modevent, + .constructor = ng_vboxnetflt_constructor, .rcvmsg = ng_vboxnetflt_rcvmsg, .shutdown = ng_vboxnetflt_shutdown, .newhook = ng_vboxnetflt_newhook, @@ -267,16 +267,12 @@ if (strcmp(name, NG_VBOXNETFLT_HOOK_IN) == 0) { #if __FreeBSD_version >= 800000 - NG_HOOK_SET_RCVDATA(hook, ng_vboxnetflt_rcv_in); NG_HOOK_SET_TO_INBOUND(hook); #endif pThis->u.s.input = hook; } else if (strcmp(name, NG_VBOXNETFLT_HOOK_OUT) == 0) { -#if __FreeBSD_version >= 800000 - NG_HOOK_SET_RCVDATA(hook, ng_vboxnetflt_rcv_out); -#endif pThis->u.s.output = hook; } else @@ -310,161 +306,171 @@ /** * Handle data on netgraph hooks. + * Frames processing is deferred to a taskqueue because this might + * be called with non-sleepable locks held and code paths inside + * the virtual switch might sleep. */ static int ng_vboxnetflt_rcvdata(hook_p hook, item_p item) { const node_p node = NG_HOOK_NODE(hook); PVBOXNETFLTINS pThis = NG_NODE_PRIVATE(node); + struct ifnet *ifp = pThis->u.s.ifp; struct mbuf *m; + struct m_tag *mtag; + bool fActive; + fActive = ASMAtomicUoReadBool(&pThis->fActive); + + NGI_GET_M(item, m); + NG_FREE_ITEM(item); + + /* Locate tag to see if processing should be skipped for this frame */ + mtag = m_tag_locate(m, MTAG_VBOX, PACKET_TAG_VBOX, NULL); + if (mtag != NULL) + { + m_tag_unlink(m, mtag); + m_tag_free(mtag); + } + + /* + * Handle incoming hook. This is connected to the + * input path of the interface, thus handling incoming frames. + */ if (pThis->u.s.input == hook) - return ng_vboxnetflt_rcv_in(hook, item); + { + if (mtag != NULL || !fActive) + { + ether_demux(ifp, m); + return (0); + } + mtx_lock_spin(&pThis->u.s.inq.ifq_mtx); + _IF_ENQUEUE(&pThis->u.s.inq, m); + mtx_unlock_spin(&pThis->u.s.inq.ifq_mtx); + taskqueue_enqueue_fast(taskqueue_fast, &pThis->u.s.tskin); + } + /** + * Handle mbufs on the outgoing hook, frames going to the interface + */ else if (pThis->u.s.output == hook) - return ng_vboxnetflt_rcv_out(hook, item); + { + if (mtag != NULL || !fActive) + return ether_output_frame(ifp, m); + mtx_lock_spin(&pThis->u.s.outq.ifq_mtx); + _IF_ENQUEUE(&pThis->u.s.outq, m); + mtx_unlock_spin(&pThis->u.s.outq.ifq_mtx); + taskqueue_enqueue_fast(taskqueue_fast, &pThis->u.s.tskout); + } else { - NGI_GET_M(item, m); - NG_FREE_ITEM(item); + m_freem(m); } return (0); } +static int ng_vboxnetflt_shutdown(node_p node) +{ + PVBOXNETFLTINS pThis = NG_NODE_PRIVATE(node); + bool fActive; + + /* Prevent node shutdown if we're active */ + fActive = ASMAtomicUoReadBool(&pThis->fActive); + if (fActive) + return (EBUSY); + NG_NODE_UNREF(node); + return (0); +} + +static int ng_vboxnetflt_disconnect(hook_p hook) +{ + return (0); +} + /** - * Handle incoming hook. This is connected to the - * input path of the interface, thus handling incoming frames. + * Input processing task, handles incoming frames */ -static int ng_vboxnetflt_rcv_in(hook_p hook, item_p item) +static void vboxNetFltFreeBSDinput(void *arg, int pending) { + PVBOXNETFLTINS pThis = (PVBOXNETFLTINS)arg; struct mbuf *m, *m0; - struct m_tag *mtag; - const node_p node = NG_HOOK_NODE(hook); - PVBOXNETFLTINS pThis = NG_NODE_PRIVATE(node); struct ifnet *ifp = pThis->u.s.ifp; - bool fActive, fDropIt = false; unsigned int cSegs = 0; + bool fDropIt = false, fActive; PINTNETSG pSG; - NGI_GET_M(item, m); - NG_FREE_ITEM(item); - - fActive = ASMAtomicUoReadBool(&pThis->fActive); - if (!fActive) - goto out; - - mtag = m_tag_locate(m, MTAG_VBOX, PACKET_TAG_VBOX, NULL); - if (mtag != NULL) - { - m_tag_unlink(m, mtag); - m_tag_free(mtag); - goto out; - } vboxNetFltRetain(pThis, true /* fBusy */); - - for (m0 = m; m0 != NULL; m0 = m0->m_next) + for (;;) { - if (m0->m_len > 0) - cSegs++; - } + mtx_lock_spin(&pThis->u.s.inq.ifq_mtx); + _IF_DEQUEUE(&pThis->u.s.inq, m); + mtx_unlock_spin(&pThis->u.s.inq.ifq_mtx); + if (m == NULL) + break; + for (m0 = m; m0 != NULL; m0 = m0->m_next) + if (m0->m_len > 0) + cSegs++; + #ifdef PADD_RUNT_FRAMES_FROM_HOST - if (m_length(m, NULL) < 60) - cSegs++; + if (m_length(m, NULL) < 60) + cSegs++; #endif - /* Create a copy of the mbuf and hand it to the virtual switch */ - pSG = RTMemTmpAlloc(RT_OFFSETOF(INTNETSG, aSegs[cSegs])); - vboxNetFltFreeBSDMBufToSG(pThis, m, pSG, cSegs, 0); - fDropIt = pThis->pSwitchPort->pfnRecv(pThis->pSwitchPort, pSG, INTNETTRUNKDIR_WIRE); - RTMemTmpFree(pSG); + /* Create a copy and deliver to the virtual switch */ + pSG = RTMemTmpAlloc(RT_OFFSETOF(INTNETSG, aSegs[cSegs])); + vboxNetFltFreeBSDMBufToSG(pThis, m, pSG, cSegs, 0); + fDropIt = pThis->pSwitchPort->pfnRecv(pThis->pSwitchPort, pSG, INTNETTRUNKDIR_HOST); + RTMemTmpFree(pSG); + if (fDropIt) + m_freem(m); + else + ether_demux(ifp, m); + } vboxNetFltRelease(pThis, true /* fBusy */); - -out: - /* Only deliver it to the host stack if the destination weren't a guest */ - if (fDropIt) - { - m_freem(m); - return (0); - } - ether_demux(ifp, m); - return (0); } /** - * Handle mbufs on the outgoing hook, frames going to the interface + * Output processing task, handles outgoing frames */ -static int ng_vboxnetflt_rcv_out(hook_p hook, item_p item) +static void vboxNetFltFreeBSDoutput(void *arg, int pending) { + PVBOXNETFLTINS pThis = (PVBOXNETFLTINS)arg; struct mbuf *m, *m0; - struct m_tag *mtag; - const node_p node = NG_HOOK_NODE(hook); - PVBOXNETFLTINS pThis = NG_NODE_PRIVATE(node); struct ifnet *ifp = pThis->u.s.ifp; unsigned int cSegs = 0; bool fDropIt = false, fActive; PINTNETSG pSG; - NGI_GET_M(item, m); - NG_FREE_ITEM(item); - - fActive = ASMAtomicUoReadBool(&pThis->fActive); - if (!fActive) - return ether_output_frame(ifp, m); - vboxNetFltRetain(pThis, true /* fBusy */); - /* Pass directly to interface if the packet originated from us */ - mtag = m_tag_locate(m, MTAG_VBOX, PACKET_TAG_VBOX, NULL); - if (mtag != NULL) + for (;;) { - m_tag_unlink(m, mtag); - m_tag_free(mtag); - goto out; - } + mtx_lock_spin(&pThis->u.s.outq.ifq_mtx); + _IF_DEQUEUE(&pThis->u.s.outq, m); + mtx_unlock_spin(&pThis->u.s.outq.ifq_mtx); + if (m == NULL) + break; - for (m0 = m; m0 != NULL; m0 = m0->m_next) - { - if (m0->m_len > 0) - cSegs++; - } + for (m0 = m; m0 != NULL; m0 = m0->m_next) + if (m0->m_len > 0) + cSegs++; #ifdef PADD_RUNT_FRAMES_FROM_HOST - if (m_length(m, NULL) < 60) - cSegs++; + if (m_length(m, NULL) < 60) + cSegs++; #endif - /* Create a copy and deliver to the virtual switch */ - pSG = RTMemTmpAlloc(RT_OFFSETOF(INTNETSG, aSegs[cSegs])); - vboxNetFltFreeBSDMBufToSG(pThis, m, pSG, cSegs, 0); - fDropIt = pThis->pSwitchPort->pfnRecv(pThis->pSwitchPort, pSG, INTNETTRUNKDIR_HOST); - RTMemTmpFree(pSG); + /* Create a copy and deliver to the virtual switch */ + pSG = RTMemTmpAlloc(RT_OFFSETOF(INTNETSG, aSegs[cSegs])); + vboxNetFltFreeBSDMBufToSG(pThis, m, pSG, cSegs, 0); + fDropIt = pThis->pSwitchPort->pfnRecv(pThis->pSwitchPort, pSG, INTNETTRUNKDIR_HOST); + RTMemTmpFree(pSG); -out: + if (fDropIt) + m_freem(m); + else + ether_output_frame(ifp, m); + } vboxNetFltRelease(pThis, true /* fBusy */); - if (fDropIt) - { - m_freem(m); - return (0); - } - - return ether_output_frame(ifp, m); } -static int ng_vboxnetflt_shutdown(node_p node) -{ - PVBOXNETFLTINS pThis = NG_NODE_PRIVATE(node); - bool fActive; - - /* Prevent node shutdown if we're active */ - fActive = ASMAtomicUoReadBool(&pThis->fActive); - if (fActive) - return (EBUSY); - NG_NODE_UNREF(node); - return (0); -} - -static int ng_vboxnetflt_disconnect(hook_p hook) -{ - return (0); -} - /** * Called to deliver a frame to either the host, the wire or both. */ @@ -536,13 +542,23 @@ /* Create a new netgraph node for this instance */ if (ng_make_node_common(&ng_vboxnetflt_typestruct, &node) != 0) - return VERR_INTERNAL_ERROR; + return VERR_INTERNAL_ERROR; RTSpinlockAcquire(pThis->hSpinlock, &Tmp); ASMAtomicUoWritePtr((void * volatile *)&pThis->u.s.ifp, ifp); pThis->u.s.node = node; bcopy(IF_LLADDR(ifp), &pThis->u.s.Mac, ETHER_ADDR_LEN); ASMAtomicUoWriteBool(&pThis->fDisconnectedFromHost, false); + /* Initialize deferred input queue */ + bzero(&pThis->u.s.inq, sizeof(struct ifqueue)); + mtx_init(&pThis->u.s.inq.ifq_mtx, "vboxnetflt inq", NULL, MTX_SPIN); + TASK_INIT(&pThis->u.s.tskin, 0, vboxNetFltFreeBSDinput, pThis); + + /* Initialize deferred output queue */ + bzero(&pThis->u.s.outq, sizeof(struct ifqueue)); + mtx_init(&pThis->u.s.outq.ifq_mtx, "vboxnetflt outq", NULL, MTX_SPIN); + TASK_INIT(&pThis->u.s.tskout, 0, vboxNetFltFreeBSDoutput, pThis); + RTSpinlockRelease(pThis->hSpinlock, &Tmp); NG_NODE_SET_PRIVATE(node, pThis); @@ -571,7 +587,10 @@ } if (ifp0 != NULL) + { + vboxNetFltOsDeleteInstance(pThis); vboxNetFltOsInitInstance(pThis, NULL); + } return !ASMAtomicUoReadBool(&pThis->fDisconnectedFromHost); } @@ -579,6 +598,12 @@ void vboxNetFltOsDeleteInstance(PVBOXNETFLTINS pThis) { + taskqueue_drain(taskqueue_fast, &pThis->u.s.tskin); + taskqueue_drain(taskqueue_fast, &pThis->u.s.tskout); + + mtx_destroy(&pThis->u.s.inq.ifq_mtx); + mtx_destroy(&pThis->u.s.outq.ifq_mtx); + if (pThis->u.s.node != NULL) ng_rmnode_self(pThis->u.s.node); pThis->u.s.node = NULL; Index: src/VBox/HostDrivers/VBoxNetFlt/VBoxNetFltInternal.h =================================================================== --- src/VBox/HostDrivers/VBoxNetFlt/VBoxNetFltInternal.h (revision 23391) +++ src/VBox/HostDrivers/VBoxNetFlt/VBoxNetFltInternal.h (working copy) @@ -206,6 +206,14 @@ hook_p output; /** Original interface flags */ unsigned int flags; + /** Input queue */ + struct ifqueue inq; + /** Output queue */ + struct ifqueue outq; + /** Input task */ + struct task tskin; + /** Output task */ + struct task tskout; /** The MAC address of the interface. */ RTMAC Mac; /** @} */ @@ -241,6 +249,8 @@ # endif #elif defined(RT_OS_LINUX) uint8_t abPadding[320]; +#elif defined(RT_OS_FREEBSD) + uint8_t abPadding[256]; #else uint8_t abPadding[128]; #endif From scf at FreeBSD.org Tue Sep 29 01:39:57 2009 From: scf at FreeBSD.org (Sean C. Farley) Date: Tue Sep 29 01:40:03 2009 Subject: Panic with vboxnet drivers In-Reply-To: <4AC120F6.7090701@shapeshifter.se> References: <4AC120F6.7090701@shapeshifter.se> Message-ID: On Mon, 28 Sep 2009, Fredrik Lindberg wrote: > Sean C. Farley wrote: >> I have five witness logs (attached): >> 1. The first one appeared when I tried to run VirtualBox with >> vboxnetadp loaded via loader.conf. VirtualBox will not be able to >> find the VirtualBox network drivers this way, so I unloaded and >> loaded vboxnetadp from the command line for the following logs. > > Need to look a bit more on this one. Thank you. >> 2. The next three logs are LOR's (sleepable after non-sleepable) >> concerning VirtualBox's "IPRT Fast Mutex Semaphore" which is an >> sx. I am not sure I am reading the backtrace correctly. It looks >> like the call to RTSemFastMutexRequest(), which calls sx_xlock(), >> is the effect. I just do not know where the cause, i.e., >> RTSemFastMutexRequest(), is being called. > > Yeah, this was a real one. The call to RTSemFastMutexRequest is inside > the virtual ethernet switch. I've attached a patch that defers > processing to avoid the sleepable after non-sleepable case. Hopefully > this fixes the panic you're seeing as well. Thank you! :) This does fix the panic. Sean -- scf@FreeBSD.org From fli at shapeshifter.se Wed Sep 30 07:36:50 2009 From: fli at shapeshifter.se (Fredrik Lindberg) Date: Wed Sep 30 07:36:56 2009 Subject: Panic with vboxnet drivers In-Reply-To: References: <4AC120F6.7090701@shapeshifter.se> Message-ID: <4AC2EE77.4090509@shapeshifter.se> Sean C. Farley wrote: >>> 2. The next three logs are LOR's (sleepable after non-sleepable) >>> concerning VirtualBox's "IPRT Fast Mutex Semaphore" which is an >>> sx. I am not sure I am reading the backtrace correctly. It looks >>> like the call to RTSemFastMutexRequest(), which calls sx_xlock(), >>> is the effect. I just do not know where the cause, i.e., >>> RTSemFastMutexRequest(), is being called. >> >> Yeah, this was a real one. The call to RTSemFastMutexRequest is inside >> the virtual ethernet switch. I've attached a patch that defers >> processing to avoid the sleepable after non-sleepable case. Hopefully >> this fixes the panic you're seeing as well. > > Thank you! :) This does fix the panic. > Great, I'll submit it upstreams as soon as possible. Fredrik From beat at FreeBSD.org Wed Sep 30 08:19:56 2009 From: beat at FreeBSD.org (Beat Gaetzi) Date: Wed Sep 30 08:20:29 2009 Subject: Panic with vboxnet drivers In-Reply-To: <4AC2EE77.4090509@shapeshifter.se> References: <4AC120F6.7090701@shapeshifter.se> <4AC2EE77.4090509@shapeshifter.se> Message-ID: <4AC31533.2070702@FreeBSD.org> Hi Fredrik, Fredrik Lindberg wrote: > Sean C. Farley wrote: >>>> 2. The next three logs are LOR's (sleepable after non-sleepable) >>>> concerning VirtualBox's "IPRT Fast Mutex Semaphore" which is an >>>> sx. I am not sure I am reading the backtrace correctly. It looks >>>> like the call to RTSemFastMutexRequest(), which calls sx_xlock(), >>>> is the effect. I just do not know where the cause, i.e., >>>> RTSemFastMutexRequest(), is being called. >>> >>> Yeah, this was a real one. The call to RTSemFastMutexRequest is >>> inside the virtual ethernet switch. I've attached a patch that >>> defers processing to avoid the sleepable after non-sleepable case. >>> Hopefully this fixes the panic you're seeing as well. >> >> Thank you! :) This does fix the panic. >> > > Great, I'll submit it upstreams as soon as possible. Thanks for this patch. We already added the patch to the port. To fix a build failure on FreeBSD 7/amd64 we had to increase abPadding[] size in patch-src-VBox-HostDrivers-VBoxNetFlt-VBoxNetFltInternal.h: http://tmp.chruetertee.ch/virtualbox-amd64-build-fix.patch Beat From dog at virtual.org.ua Wed Sep 30 15:06:48 2009 From: dog at virtual.org.ua (Pavel Greenberg) Date: Wed Sep 30 15:06:56 2009 Subject: wine && serial port. Message-ID: Hello all! On my system: dog@dog:~> uname -a FreeBSD dog.ic.kharkov.ua 7.2-STABLE FreeBSD 7.2-STABLE #0: Tue Sep 22 15:59:09 EEST 2009 root@dog.ic.kharkov.ua:/usr/obj/usr/src/sys/DOG_KERNEL i386 I have installed wine-1.1.30,1 from ports. I have some window$ software, which is required com-port. My user is in dialer group, in /dev/ I have cuad0 device, which is work fine natively (with cu(1)) and have "666" permissions, in ~/.wine/dosdevices I have symlinks com1 -> /dev/cuad0 and COM1 -> /dev/cuad0 - but it's not work, software don't see com-port. I tried to install some other software (for example, hyperterminal), bat have the same picture. When I tried to set WINEDEBUG=+comm,+ntdll,+file and run this, in log I've seen: ... trace:file:wine_nt_to_unix_file_name L"\\??\\C:\\Program Files\\TMA\\config\\Cms2Serv.ini" -> "/usr/home/dog/.wine/dosdevices/c:/Program Files/ TMA/config/Cms2Serv.ini" trace:file:CreateFileW returning 0x6c trace:ntdll:NtQueryInformationFile (0x6c,0x34f5d8,0x34f5b0,0x00000028,0x00000004) trace:file:CreateFileW L"COM1" GENERIC_READ GENERIC_WRITE creation 3 attributes 0x40000000 trace:file:RtlDosPathNameToNtPathName_U (L"COM1",0x34fc00,0x0,0x0) trace:file:RtlGetFullPathName_U (L"COM1" 520 0x34f944 0x0) trace:ntdll:NtCreateFile handle=0x34fc08 access=c0000000 name=L"\\??\\COM1" objattr=00000040 root=0x0 sec=0x0 io=0x34fbf8 alloc_size=0x0 attr=00000000 sharing=00000000 disp=1 options=00000040 ea=0x0.0x00000000 trace:file:get_dos_device L"COM1" -> "/usr/home/dog/.wine/dosdevices/com1" trace:file:CreateFileW returning 0x6c trace:ntdll:NtDeviceIoControlFile (0x6c,0x0,0x0,0x0,0x34fc00,0x001b0008,0x34fc48,0x00000008,0x0,0x00000000) trace:comm:io_control 0x6c IOCTL_SERIAL_SET_QUEUE_SIZE 0x34fc48 8 0x0 0 0x34fc00 fixme:comm:set_queue_size insize 2000 outsize 1000 unimplemented stub trace:comm:BuildCommDCBAndTimeoutsA (COM1:9600,N,8,1,0x543a84,0x0) trace:comm:BuildCommDCBAndTimeoutsW (L"COM1:9600,N,8,1",0x543a84,0x0) trace:file:RtlGetFullPathName_U (L"C:\\Program Files\\TMA\\config\\Cms2Serv.ini" 520 0x34f634 0x34fa54) trace:file:CreateFileW L"C:\\Program Files\\TMA\\config\\Cms2Serv.ini" GENERIC_READ FILE_SHARE_READ FILE_SHARE_WRITE FILE_SHARE_DELETE creatio n 3 attributes 0x80 ... I tried to do the same on my Acer Aspire One netbook with usb-com device on uplcom (4) chipset and the same OS version - it doesn't work too. Is there any way to make the program have see com-port under the wine?