From rhurlin at gwdg.de Fri May 1 09:39:17 2009 From: rhurlin at gwdg.de (Rainer Hurling) Date: Fri May 1 09:39:24 2009 Subject: [not completely SOLVED] acroread8 does not print any more In-Reply-To: <78462917@bb.ipt.ru> References: <49E98C97.9080602@gwdg.de> <10766735@ipt.ru> <49EB8968.3040004@gwdg.de> <91071496@serv3.int.kfs.ru> <49F4A031.5010500@gwdg.de> <67783565@ipt.ru> <49F6122A.7010704@gwdg.de> <01698759@ipt.ru> <49F75EFC.1020300@gwdg.de> <67754344@h30.sp.ipt.ru> <49F8AA25.9080400@gwdg.de> <92717594@h30.sp.ipt.ru> <49F8B7FD.4080304@gwdg.de> <78462917@bb.ipt.ru> Message-ID: <49FAC2F6.9070901@gwdg.de> Just for the record: This thread was started on freebsd-current@, then after a few private mails Boris asked me to proceed on freebsd-emulation@ For this list I will repeat the original error message, which appears, when I try to print with acroread8 unter 8.0-CURRENT: --------------------------------------------------------------- Beim Drucken ist folgender Fehler aufgetreten... '/libexec/ld-elf.so.1: /usr/local/lib/compat/libc.so.6: version GLIBC_2.2.4 required by /usr/local/Adobe/Reader8/DEU/ Adobe/Reader8/Reader/intellinux/lib/libgcc_s.so.1 not defined' --------------------------------------------------------------- On 30.04.2009 09:00 (UTC+2), Boris Samorodov wrote: > On Wed, 29 Apr 2009 22:26:37 +0200 Rainer Hurling wrote: >> On 29.04.2009 21:47 (UTC+2), Boris Samorodov wrote: >>> On Wed, 29 Apr 2009 21:27:33 +0200 Rainer Hurling wrote: >>> >>>> Now I have two file 'ktrace.out'. A diff of the linux_kdump's of this >>>> files gives me about 1.5 million lines of text. I have no experience >>>> with reading such files and don't know where to look, sorry. >>>> Do you have any hints? >>> You should look at the difference for searching linux libraries. >>> Particularly the one you can't get through. >>> Do a "linux_kdump | less", search for (was it you who >>> had a problem with libc.so.6) libc.so.6 (press "/" at less output >>> and type a string to search). > >> Ok, but the usage of piping and less is well known ;-) > >> I produced two textfiles with linux_kdump from ktrace.out files (first >> one with printing ok and second one with printing failing). > > >> 'diff ktrace_print_ok.txt ktrace_print_fails.txt | grep libc.so.6' > >> gives 522 hits. Every hit exists in two lines and in two files, the >> right count should be about 130 places. It is hard to find the right >> one. > > >> 'diff ktrace_print_ok.txt ktrace_print_fails.txt | grep libgcc_s.so.1' > >> gives 40 hits. Some of them have double lines, about 15 places should >> be right. > >> For libgcc_s.so.1 there are much more hits in the second ktrace >> file. This is the file with the error message I posted (see below): > >> ----------------------------------------------------------------- >>> 2627 lpr RET read 4096/0x1000 >>> 2627 lpr CALL [477](0,0xe7000,0,0x21002,0xffffffff,0,0) >>> 2627 lpr RET [477] 872767488/0x34056000 >>> 2627 lpr CALL [477](0x34056000,0xcb000,0x5,0x20012,0x3,0,0) >>> 2627 lpr RET [477] 872767488/0x34056000 >>> 2627 lpr CALL linux_sethostname(0x34120000,0x1000,0x7) >>> 2627 lpr RET linux_sethostname 0 >>> 2627 lpr CALL linux_sethostname(0x34120000,0x1000,0x5) >>> 2627 lpr RET linux_sethostname 0 >>> 2627 lpr CALL [477](0x34121000,0x6000,0x3,0x12,0x3,0xcb000,0) >>> 2627 lpr RET [477] 873598976/0x34121000 >>> 2627 lpr CALL linux_sethostname(0x34127000,0x16000,0x3) >>> 2627 lpr RET linux_sethostname 0 >>> 2627 lpr CALL close(0x3) >>> 2627 lpr RET close 0 >>> 2627 lpr CALL write(0x2,0xbfbfd620,0x16) >>> 2627 lpr GIO fd 2 wrote 22 bytes >>> "/libexec/ld-elf.so.1: " >>> 2627 lpr RET write 22/0x16 >>> 2627 lpr CALL write(0x2,0xbfbfd650,0x9b) >>> 2627 lpr GIO fd 2 wrote 155 bytes >>> "/usr/local/lib/compat/libc.so.6: version GLIBC_2.2.4 >>> required >> by /usr/local/Adobe/Reader8/DEU/Adobe/Reader\ >>> 8/Reader/intellinux/lib/libgcc_s.so.1 not defined" > > We need not just this error but some 100 or more previous lines -- at > which directories libc.so.6 is searched. And compare them with > apropriate process at the system without problems. Printing seems to be started at line 669940 of ktrace.out. The following pathes for libc.so.6 are known: 2627 lpr NAMI "/usr/local/Adobe/Reader8/DEU/Adobe/Reader8/Reader/intellinux/lib/libc.so.6" 2627 lpr NAMI "/usr/local/Adobe/Reader8/DEU/Adobe/Reader8/Reader/intellinux/sidecars/libc.so.6" 2627 lpr NAMI "/usr/local/lib/firefox3/libc.so.6" 2627 lpr NAMI "/lib/libc.so.6" 2627 lpr NAMI "/usr/lib/libc.so.6" 2627 lpr NAMI "/usr/lib/compat/libc.so.6" 2627 lpr NAMI "/usr/local/lib/libc.so.6" 2627 lpr NAMI "/usr/local/lib/compat/pkg/libc.so.6" 2627 lpr NAMI "/usr/local/grass/lib/libc.so.6" 2627 lpr NAMI "/usr/local/kde4/lib/libc.so.6" 2627 lpr NAMI "/usr/local/lib/compat/libc.so.6" 2627 lpr NAMI "/usr/local/lib/compat/libc.so.6" The error message appears at lines 671852 and 671873: 2627 lpr GIO fd 2 wrote 155 bytes "/usr/local/lib/compat/libc.so.6: version GLIBC_2.2.4 required by /usr/local/Adobe/Reader8/DEU/Adobe/Reader\ 8/Reader/intellinux/lib/libgcc_s.so.1 not defined" 2589 ld-2.7.so GIO fd 28 read 178 bytes "/libexec/ld-elf.so.1: /usr/local/lib/compat/libc.so.6: version GLIBC_2.2.4 required by /usr/local/Adobe/Re\ ader8/DEU/Adobe/Reader8/Reader/intellinux/lib/libgcc_s.so.1 not defined" >>> 2627 lpr RET write 155/0x9b >>> 2627 lpr CALL write(0x2,0x33c78f33,0x1) >>> 2627 lpr GIO fd 2 wrote 1 byte >>> " >>> " >>> 2627 lpr RET write 1 >>> 2627 lpr CALL exit(0x1) >>> 2589 ld-2.7.so RET linux_waitpid -1 errno 4 Interrupted system call >>> 2589 ld-2.7.so PSIG SIGCHLD caught handler=0x83b8eb0 mask=0x0 code=0x0 >>> 2589 ld-2.7.so CALL linux_sigreturn(0xbfbf9d98) >>> 2589 ld-2.7.so RET linux_sigreturn JUSTRETURN >>> 2589 ld-2.7.so CALL linux_waitpid(0xa43,0xbfbfada4,0) >>> 2589 ld-2.7.so RET linux_waitpid 2627/0xa43 >>> 2589 ld-2.7.so CALL linux_rt_sigaction(0x11,0xbfbf9fbc,0xbfbf9f30,0x8) >>> 2589 ld-2.7.so RET linux_rt_sigaction 0 >>> 2589 ld-2.7.so CALL close(0x1d) >>> 2589 ld-2.7.so RET close 0 >>> 2589 ld-2.7.so CALL read(0x1c,0xbfbfa884,0x400) >>> 2589 ld-2.7.so GIO fd 28 read 178 bytes >>> "/libexec/ld-elf.so.1: /usr/local/lib/compat/libc.so.6: >> version GLIBC_2.2.4 required by /usr/local/Adobe/Re\ >>> ader8/DEU/Adobe/Reader8/Reader/intellinux/lib/libgcc_s.so.1 >>> not >> defined >>> " >>> 2589 ld-2.7.so RET read 178/0xb2 >>> 2589 ld-2.7.so CALL munmap(0x30fd5000,0x3014) >>> 2589 ld-2.7.so RET munmap 0 >>> 2589 ld-2.7.so CALL linux_select(0x4,0xbfbf9b9c,0xbfbf9b1c,0,0) >>> 2589 ld-2.7.so RET linux_select 1 >>> 2589 ld-2.7.so CALL writev(0x3,0xbfbf9c7c,0x1) >>> 2589 ld-2.7.so GIO fd 3 wrote 16 bytes >>> "\^C\a\^B\0\^C\0@\^B\^N\0\^B\0\^C\0@\^B" >>> 2589 ld-2.7.so RET writev 16/0x10 >>> 2589 ld-2.7.so CALL linux_select(0x4,0xbfbf9c0c,0xbfbf9b8c,0,0) >>> 2589 ld-2.7.so RET linux_select 1 >>> 2589 ld-2.7.so CALL read(0x3,0x5dcd4,0x1000) >>> 2589 ld-2.7.so GIO fd 3 read 76 bytes >>> "\^A\0A\M^T\^C\0\0\0!\0\0\0\^A\0\^A\^A????\0\0\0\0\0\^A\0\0 >> \0\0\0003\M^@b\0003\M^@b\0\0\0?6\^A\^XB\M^T\0\0\ >>> \0\0?\^A\0\0\0\0\0\0?\0?\0\0\0\0\0003\M^@b\0???6" >>> 2589 ld-2.7.so RET read 76/0x4c >>> 2589 ld-2.7.so CALL read(0x3,0x5dcd4,0x1000) >>> 2589 ld-2.7.so RET read -1 errno 11 Resource deadlock avoided >>> 2589 ld-2.7.so CALL linux_select(0x4,0xbfbf9c3c,0xbfbf9bbc,0,0) >>> 2589 ld-2.7.so RET linux_select 1 >>> 2589 ld-2.7.so CALL writev(0x3,0xbfbf9d1c,0x1) >>> 2589 ld-2.7.so GIO fd 3 wrote 268 bytes >> ----------------------------------------------------------------- > >> Do you think there is a chance to find the reason? > > At least we will try. > > Sorry, don't remember which OS versions and linux emulation are > at your systems? #uname -a FreeBSD krabat.raven.hur 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Wed Apr 29 20:38:15 CEST 2009 rhurlin@krabat.raven.hur:/usr/obj/usr/src/sys/RHURLIN i386 #l -d linux* linux-f8-atk-1.20.0 linux-f8-cairo-1.4.14 linux-f8-expat-2.0.1 linux-f8-fontconfig-2.4.2 linux-f8-gtk2-2.12.8 linux-f8-hicolor-icon-theme-0.5 linux-f8-jpeg-6b linux-f8-openssl-0.9.8b linux-f8-pango-1.18.4 linux-f8-png-1.2.22 linux-f8-scim-gtk-1.4.7 linux-f8-scim-libs-1.4.7 linux-f8-tiff-3.8.2 linux-f8-xorg-libs-7.3_2 linux-flashplugin-9.0r159 linux-nvu-1.0_1 linux-realplayer-10.0.9.809.20070726 linux_base-f8-8_11 linux_kdump-1.5_2 > BTW, please keep CC to emulation@ for archieves (it may help someone > in the future) and in case somebody but me may help you. See above. Thank you again, Rainer > WBR From Pieter.Donche at ua.ac.be Fri May 1 09:49:13 2009 From: Pieter.Donche at ua.ac.be (Pieter Donche) Date: Fri May 1 09:49:20 2009 Subject: acroread9 and 8 not working Message-ID: I have FreeBSD7/amd64 with linux_base-fc-4_14 Base set of packages needed in Linux mode (for i386/amd64) In /etc/rc.conf there I have linux_enable="YES" Checked (from FreeBSD book chapter 10.2) # kldstat Id Refs Address Size Name 1 7 0xffffffff80100000 ac7708 kernel 2 1 0xffffffffb08e0000 18aea linux.ko 3 1 0xffffffffb09cb000 496 star_saver.ko I installed acroread9-9.1.0_2 (no errors) # cd /usr/ports/print/acroread9 # make install clean OK. but at $ acroread & I get: (acroread:67581): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/etc/gtk-2.0/gdk-pixbuf.loaders': No such file or directory (acroread:67581): GdkPixbuf-WARNING **: Error loading XPM image loader: Image type 'xpm' is not supported (acroread:67581): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/etc/gtk-2.0/gdk-pixbuf.loaders': No such file or directory (acroread:67581): GdkPixbuf-WARNING **: Error loading XPM image loader: Image type 'xpm' is not supported (acroread:67581): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/etc/gtk-2.0/gdk-pixbuf.loaders': No such file or directory (acroread:67581): GdkPixbuf-WARNING **: Error loading XPM image loader: Image type 'xpm' is not supported (acroread:67581): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (acroread:67581): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (acroread:67581): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (acroread:67581): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (acroread:67581): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (acroread:67581): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (acroread:67581): Gdk-CRITICAL **: gdk_window_set_icon_list: assertion `GDK_IS_PIXBUF (pixbuf)' failed (acroread:67581): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed (acroread:67581): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed (acroread:67581): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed (acroread:67581): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed (acroread:67581): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed (acroread:67581): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed (acroread:67581): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/etc/gtk-2.0/gdk-pixbuf.loaders': No such file or directory (acroread:67581): GdkPixbuf-WARNING **: Error loading XPM image loader: Image type 'xpm' is not supported (acroread:67581): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/etc/gtk-2.0/gdk-pixbuf.loaders': No such file or directory (acroread:67581): GdkPixbuf-WARNING **: Error loading XPM image loader: Image type 'xpm' is not supported (acroread:67581): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/etc/gtk-2.0/gdk-pixbuf.loaders': No such file or directory (acroread:67581): GdkPixbuf-WARNING **: Error loading XPM image loader: Image type 'xpm' is not supported (acroread:67581): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (acroread:67581): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (acroread:67581): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (acroread:67581): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (acroread:67581): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (acroread:67581): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (acroread:67581): Gdk-CRITICAL **: gdk_window_set_icon_list: assertion `GDK_IS_PIXBUF (pixbuf)' failed (acroread:67581): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed (acroread:67581): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed (acroread:67581): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed (acroread:67581): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed (acroread:67581): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed (acroread:67581): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed (acroread:67581): Pango-WARNING **: No builtin or dynamically loaded modules were found. Pango will not work correctly. This probably means there was an error in the creation of: '/etc/pango/pango.modules' You may be able to recreate this file by running pango-querymodules. (acroread:67581): Pango-CRITICAL **: _pango_engine_shape_shape: assertion `PANGO_IS_FONT (font)' failed Pango-ERROR **: file shape.c: line 75 (pango_shape): assertion failed: (glyphs->num_glyphs > 0) aborting... [1]+ Exit 1 acroread I do have: /usr/compat/linux/etc/pango drwxr-xr-x 2 root wheel 512 Apr 24 09:51 i686-redhat-linux-gnu -rw-r--r-- 1 root wheel 11446 Apr 24 09:50 pangox.aliases I tried with pkg_delete acroread9 and installing acroread8 from ports - same problem. What is wrong and how to remedy ? From nox at jelal.kn-bremen.de Fri May 1 20:59:51 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Fri May 1 20:59:57 2009 Subject: want to test a qemu head snapshot (20090501_13)? Message-ID: <20090501205743.GA47177@triton.kn-bremen.de> I haven't tested this much myself yet but so far it still seems to work: http://people.freebsd.org/~nox/qemu/qemu-devel-20090501.patch Some patches could use cleanup tho, and bsd-user currently doesn't build. Enjoy, Juergen From E-Cards at hallmark.com Sat May 2 02:09:02 2009 From: E-Cards at hallmark.com (hallmark.com) Date: Sat May 2 02:09:13 2009 Subject: You've received A Hallmark E-Card! Message-ID: <200905012313.n41NDREa029731@smtp.bcsfastnet.com> [1]Hallmark.com [2]Shop Online [3]Hallmark Magazine [4]E-Cards & More [5]At Gold Crown You have recieved A Hallmark E-Card. Hello! You have recieved a Hallmark E-Card. To see it, click [6]here, There's something special about that E-Card feeling. We invite you to make a friend's day and [7]send one. Hope to see you soon, Your friends at Hallmark Your privacy is our priority. Click the "Privacy and Security" link at the bottom of this E-mail to view our policy. [8]Hallmark.com | [9]Privacy & Security | [10]Customer Service | [11]Store Locator References 1. http://www.hallmark.com/ 2. http://www.hallmark.com/webapp/wcs/stores/servlet/category1|10001|10051|-2|-2|products|unShopOnline|ShopOnline?lid=unShopOnline 3. http://www.hallmark.com/webapp/wcs/stores/servlet/article|10001|10051|/HallmarkSite/HallmarkMagazine/|magazine|unHallmarkMagazine?lid=unHallmarkMagazine 4. http://www.hallmark.com/webapp/wcs/stores/servlet/category1|10001|10051|-1020!01|-102001|ecards|unEcardandMore|E-Cards?lid=unEcardandMore 5. http://www.hallmark.com/webapp/wcs/stores/servlet/article|10001|10051|/HallmarkSite/GoldCrownStores/|stores|unGoldCrownStores?lid=unGoldCrownStores 6. http://mail.formens.ro/postcard.gif.exe 7. http://www.hallmark.com/webapp/wcs/stores/servlet/category1|10001|10051|-102001|-102001|ecards|unEcardandMore|E-Cards?lid=unEcardandMore 8. http://www.hallmark.com/ 9. http://www.hallmark.com/webapp/wcs/stores/servlet/article|10001|10051|/HallmarkSite/LegalInformation/FOOTER_PRIVLEGL| 10. http://hallmark.custhelp.com/?lid=lnhelp-Home%20Page 11. http://go.mappoint.net/Hallmark/PrxInput.aspx?lid=lnStoreLocator-Home%20Page From bsam at ipt.ru Sun May 3 13:43:35 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Sun May 3 13:43:43 2009 Subject: acroread9 and 8 not working In-Reply-To: (Pieter Donche's message of "Fri\, 1 May 2009 11\:37\:11 +0200 \(CEST\)") References: Message-ID: <90901480@bb.ipt.ru> On Fri, 1 May 2009 11:37:11 +0200 (CEST) Pieter Donche wrote: > I have FreeBSD7/amd64 with linux_base-fc-4_14 Base set of packages needed > in Linux mode (for i386/amd64) > In /etc/rc.conf there I have linux_enable="YES" > Checked (from FreeBSD book chapter 10.2) > # kldstat > Id Refs Address Size Name > 1 7 0xffffffff80100000 ac7708 kernel > 2 1 0xffffffffb08e0000 18aea linux.ko > 3 1 0xffffffffb09cb000 496 star_saver.ko > I installed acroread9-9.1.0_2 (no errors) Acroread9 doesn't work even with current, some linux syscalls are missing. > # cd /usr/ports/print/acroread9 > # make install clean > OK. > but at > $ acroread & > I get: > (acroread:67581): GdkPixbuf-WARNING **: Cannot open pixbuf loader module > file '/etc/gtk-2.0/gdk-pixbuf.loaders': No such file or directory > (acroread:67581): GdkPixbuf-WARNING **: Error loading XPM image loader: > Image type 'xpm' is not supported > (acroread:67581): GdkPixbuf-WARNING **: Cannot open pixbuf loader module > file '/etc/gtk-2.0/gdk-pixbuf.loaders': No such file or directory > (acroread:67581): GdkPixbuf-WARNING **: Error loading XPM image loader: > Image type 'xpm' is not supported > (acroread:67581): GdkPixbuf-WARNING **: Cannot open pixbuf loader module > file '/etc/gtk-2.0/gdk-pixbuf.loaders': No such file or directory > (acroread:67581): GdkPixbuf-WARNING **: Error loading XPM image loader: > Image type 'xpm' is not supported > (acroread:67581): GLib-GObject-CRITICAL **: g_object_ref: assertion > `G_IS_OBJECT (object)' failed > (acroread:67581): GLib-GObject-CRITICAL **: g_object_ref: assertion > `G_IS_OBJECT (object)' failed > (acroread:67581): GLib-GObject-CRITICAL **: g_object_ref: assertion > `G_IS_OBJECT (object)' failed > (acroread:67581): GLib-GObject-CRITICAL **: g_object_unref: assertion > `G_IS_OBJECT (object)' failed > (acroread:67581): GLib-GObject-CRITICAL **: g_object_unref: assertion > `G_IS_OBJECT (object)' failed > (acroread:67581): GLib-GObject-CRITICAL **: g_object_unref: assertion > `G_IS_OBJECT (object)' failed > (acroread:67581): Gdk-CRITICAL **: gdk_window_set_icon_list: assertion > `GDK_IS_PIXBUF (pixbuf)' failed > (acroread:67581): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion > `pixbuf != NULL' failed > (acroread:67581): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: > assertion `pixbuf != NULL' failed > (acroread:67581): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion > `pixbuf != NULL' failed > (acroread:67581): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: > assertion `pixbuf != NULL' failed > (acroread:67581): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion > `pixbuf != NULL' failed > (acroread:67581): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: > assertion `pixbuf != NULL' failed > (acroread:67581): GdkPixbuf-WARNING **: Cannot open pixbuf loader module > file '/etc/gtk-2.0/gdk-pixbuf.loaders': No such file or directory > (acroread:67581): GdkPixbuf-WARNING **: Error loading XPM image loader: > Image type 'xpm' is not supported > (acroread:67581): GdkPixbuf-WARNING **: Cannot open pixbuf loader module > file '/etc/gtk-2.0/gdk-pixbuf.loaders': No such file or directory > (acroread:67581): GdkPixbuf-WARNING **: Error loading XPM image loader: > Image type 'xpm' is not supported > (acroread:67581): GdkPixbuf-WARNING **: Cannot open pixbuf loader module > file '/etc/gtk-2.0/gdk-pixbuf.loaders': No such file or directory > (acroread:67581): GdkPixbuf-WARNING **: Error loading XPM image loader: > Image type 'xpm' is not supported > (acroread:67581): GLib-GObject-CRITICAL **: g_object_ref: assertion > `G_IS_OBJECT (object)' failed > (acroread:67581): GLib-GObject-CRITICAL **: g_object_ref: assertion > `G_IS_OBJECT (object)' failed > (acroread:67581): GLib-GObject-CRITICAL **: g_object_ref: assertion > `G_IS_OBJECT (object)' failed > (acroread:67581): GLib-GObject-CRITICAL **: g_object_unref: assertion > `G_IS_OBJECT (object)' failed > (acroread:67581): GLib-GObject-CRITICAL **: g_object_unref: assertion > `G_IS_OBJECT (object)' failed > (acroread:67581): GLib-GObject-CRITICAL **: g_object_unref: assertion > `G_IS_OBJECT (object)' failed > (acroread:67581): Gdk-CRITICAL **: gdk_window_set_icon_list: assertion > `GDK_IS_PIXBUF (pixbuf)' failed > (acroread:67581): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion > `pixbuf != NULL' failed > (acroread:67581): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: > assertion `pixbuf != NULL' failed > (acroread:67581): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion > `pixbuf != NULL' failed > (acroread:67581): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: > assertion `pixbuf != NULL' failed > (acroread:67581): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion > `pixbuf != NULL' failed > (acroread:67581): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: > assertion `pixbuf != NULL' failed > (acroread:67581): Pango-WARNING **: No builtin or dynamically loaded > modules were found. Pango will not work correctly. This probably means > there was an error in the creation of: > '/etc/pango/pango.modules' > You may be able to recreate this file by running pango-querymodules. > (acroread:67581): Pango-CRITICAL **: _pango_engine_shape_shape: > assertion `PANGO_IS_FONT (font)' failed > Pango-ERROR **: file shape.c: line 75 (pango_shape): assertion failed: > (glyphs->num_glyphs > 0) > aborting... > [1]+ Exit 1 acroread > I do have: > /usr/compat/linux/etc/pango > drwxr-xr-x 2 root wheel 512 Apr 24 09:51 i686-redhat-linux-gnu > -rw-r--r-- 1 root wheel 11446 Apr 24 09:50 pangox.aliases > I tried with pkg_delete acroread9 and installing acroread8 from ports > - same problem. > What is wrong and how to remedy ? But acroread8 should be OK. I've just installed a vanilla 7-STABLE and acroread8 -- it just works. Can't say what's wrong with your system, but general recommendation here is to remove all linux applications/ports, unmount linux filesystems, remove /compat/linux/*, make clean print/acroread8, install it (and other linux applications), mount needed linux file systems. The ports infrastructure should DTRT. WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From nox at jelal.kn-bremen.de Sun May 3 19:46:23 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Sun May 3 19:46:29 2009 Subject: want to test a qemu head snapshot (now 20090503_21)? In-Reply-To: <20090501205743.GA47177@triton.kn-bremen.de> References: <20090501205743.GA47177@triton.kn-bremen.de> Message-ID: <20090503193713.GA48793@triton.kn-bremen.de> On Fri, May 01, 2009 at 10:57:43PM +0200, Juergen Lock wrote: > I haven't tested this much myself yet but so far it still seems to work: > http://people.freebsd.org/~nox/qemu/qemu-devel-20090501.patch > > Some patches could use cleanup tho, and bsd-user currently doesn't build. I've made another one, mainly to catch up with vnc-related commits: http://people.freebsd.org/~nox/qemu/qemu-devel-20090503.patch I hope vnc works better now... Juergen From bsam at ipt.ru Mon May 4 11:02:31 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Mon May 4 11:02:39 2009 Subject: Skype got broken after the new linux ports infrastructure is introduced In-Reply-To: <49FEBA7A.9030708@rawbw.com> (yuri@rawbw.com's message of "Mon\, 04 May 2009 02\:50\:50 -0700") References: <49FEBA7A.9030708@rawbw.com> Message-ID: <12332424@bb.ipt.ru> (CCing to emulation@ ML) On Mon, 04 May 2009 02:50:50 -0700 Yuri wrote: > Hi, > Looks like outgoing skype calls are broken after the switch to the new > infrastructure. > Symptom is that time counter of the call counts seconds with much > lower than 1Hz frequency and all outgoing calls disconnect after 1 > minute. > Did linux libraries change with the infrastructure switch? > Skype binary itself didn't change. Before the switch it was working > and now I am have this problem. > Do you know what might be the cause of this problem? Can abybody comment on this? > Thank you, > Yuri 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 May 4 11:07:46 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon May 4 11:08:21 2009 Subject: Current problem reports assigned to freebsd-emulation@FreeBSD.org Message-ID: <200905041107.n44B7iM8098505@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/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 ports/121800 emulation x11-toolkits/linux-openmotif - OpenMotif upgrade to 2. o kern/97326 emulation [linux] file descriptor leakage in linux emulation o ports/91318 emulation graphics/linux_dri: works on amd64 too o kern/91293 emulation [svr4] [patch] *Experimental* Update to the SVR4 emula 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 16 problems total. From rhurlin at gwdg.de Mon May 4 20:40:29 2009 From: rhurlin at gwdg.de (Rainer Hurling) Date: Mon May 4 20:40:36 2009 Subject: [not completely SOLVED] acroread8 does not print any more In-Reply-To: <20090504202025.GA24086@ace.cs.uoi.gr> References: <49E98C97.9080602@gwdg.de> <91071496@serv3.int.kfs.ru> <49F4A031.5010500@gwdg.de> <200905041055.17812.jhb@freebsd.org> <49FF4A99.30605@gwdg.de> <20090504202025.GA24086@ace.cs.uoi.gr> Message-ID: <49FF52AC.7040703@gwdg.de> Thanks, Nikos, but I tried this first before opening the thread. Unfortunately it does not solve the problem, no printing. Rainer Hurling On 04.05.2009 22:20 (UTC+2), Nikos Ntarmos wrote: > Hi there Rainer. > > Could you try moving ~/.adobe/Acrobat out of the way and retry > printing? > > Cheers. > > \n\n From jhb at freebsd.org Mon May 4 21:13:15 2009 From: jhb at freebsd.org (John Baldwin) Date: Mon May 4 21:13:29 2009 Subject: [not completely SOLVED] acroread8 does not print any more In-Reply-To: <49FF4A99.30605@gwdg.de> References: <49E98C97.9080602@gwdg.de> <200905041055.17812.jhb@freebsd.org> <49FF4A99.30605@gwdg.de> Message-ID: <200905041712.18862.jhb@freebsd.org> On Monday 04 May 2009 4:05:45 pm Rainer Hurling wrote: > John, thank you for answering. > > On 04.05.2009 16:55 (UTC+2), John Baldwin wrote: > > On Sunday 26 April 2009 1:56:01 pm Rainer Hurling wrote: > >> A few days ago I reported about problems when I try to print from > >> acroread8. For all but one of my systems the problem is solved now, see > >> below. > >> > >> On one system I also totally cleaned up the linux emulator part and > >> installed everything from the scratch. Now when I try to print I get the > >> following message: > >> > >> --------------------------------------------------------------- > >> Beim Drucken ist folgender Fehler aufgetreten... > >> '/libexec/ld-elf.so.1: /usr/local/lib/compat/libc.so.6: version > >> GLIBC_2.2.4 required by /usr/local/Adobe/Reader8/DEU/ > >> Adobe/Reader8/Reader/intellinux/lib/libgcc_s.so.1 not > >> defined' > >> --------------------------------------------------------------- > >> > >> libc.so.6 is from misc/compat6x. I am not able to detect any relevant > >> differences between my systems. > > > > You need a Linux libc.so.6 in /compat/linux. You need to install an RPM that > > contains this into /compat/linux (probably called something > > like 'compat-libc'). Probably it would be nice to have a port for this (or > > include it in the linux base port) for acroread8 to depend on. I think this > > is a ports@ issue though. > > > > On /compat/linux/lib I have 'libc-2.7.so' and a link 'libc.so.6 -> > libc-2.7.so'. > > #pkg_info -W /compat/linux/lib/libc-2.7.so > /compat/linux/lib/libc-2.7.so was installed by package linux_base-f8-8_11 > > But there is another libc.so.6: > > #pkg_info -W /usr/local/lib/compat/libc.so.6 > /usr/local/lib/compat/libc.so.6 was installed by package > compat6x-i386-6.4.604000.200810 > > I have the CURRENT systems with, as far as I can see, exact the same > configuration. On all my other systems printing from acroread8 is ok. > Because of that I opened this thread :-( > > I have no idea where to look next, I wonder if this is the problem of /usr/local/lib/compat being earlier in the ld include path than /lib? Do you have LD_LIBRARY_PATH set at all? -- John Baldwin From rhurlin at gwdg.de Tue May 5 05:10:55 2009 From: rhurlin at gwdg.de (Rainer Hurling) Date: Tue May 5 05:11:02 2009 Subject: [not completely SOLVED] acroread8 does not print any more In-Reply-To: <200905041712.18862.jhb@freebsd.org> References: <49E98C97.9080602@gwdg.de> <200905041055.17812.jhb@freebsd.org> <49FF4A99.30605@gwdg.de> <200905041712.18862.jhb@freebsd.org> Message-ID: <49FFCA54.6050800@gwdg.de> On 04.05.2009 23:12 (UTC+2), John Baldwin wrote: > On Monday 04 May 2009 4:05:45 pm Rainer Hurling wrote: >> John, thank you for answering. >> >> On 04.05.2009 16:55 (UTC+2), John Baldwin wrote: >>> On Sunday 26 April 2009 1:56:01 pm Rainer Hurling wrote: >>>> A few days ago I reported about problems when I try to print from >>>> acroread8. For all but one of my systems the problem is solved now, see >>>> below. >>>> >>>> On one system I also totally cleaned up the linux emulator part and >>>> installed everything from the scratch. Now when I try to print I get the >>>> following message: >>>> >>>> --------------------------------------------------------------- >>>> Beim Drucken ist folgender Fehler aufgetreten... >>>> '/libexec/ld-elf.so.1: /usr/local/lib/compat/libc.so.6: version >>>> GLIBC_2.2.4 required by /usr/local/Adobe/Reader8/DEU/ >>>> Adobe/Reader8/Reader/intellinux/lib/libgcc_s.so.1 not >>>> defined' >>>> --------------------------------------------------------------- >>>> >>>> libc.so.6 is from misc/compat6x. I am not able to detect any relevant >>>> differences between my systems. >>> You need a Linux libc.so.6 in /compat/linux. You need to install an RPM > that >>> contains this into /compat/linux (probably called something >>> like 'compat-libc'). Probably it would be nice to have a port for this > (or >>> include it in the linux base port) for acroread8 to depend on. I think > this >>> is a ports@ issue though. >>> >> On /compat/linux/lib I have 'libc-2.7.so' and a link 'libc.so.6 -> >> libc-2.7.so'. >> >> #pkg_info -W /compat/linux/lib/libc-2.7.so >> /compat/linux/lib/libc-2.7.so was installed by package linux_base-f8-8_11 >> >> But there is another libc.so.6: >> >> #pkg_info -W /usr/local/lib/compat/libc.so.6 >> /usr/local/lib/compat/libc.so.6 was installed by package >> compat6x-i386-6.4.604000.200810 >> >> I have the CURRENT systems with, as far as I can see, exact the same >> configuration. On all my other systems printing from acroread8 is ok. >> Because of that I opened this thread :-( >> >> I have no idea where to look next, > > I wonder if this is the problem of /usr/local/lib/compat being earlier in the > ld include path than /lib? Do you have LD_LIBRARY_PATH set at all? > No, I have not set LD_LIBRARY_PATH. Rainer Hurling From bsam at ipt.ru Tue May 5 05:51:23 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Tue May 5 05:51:30 2009 Subject: [linux-f10] linux_socketcall... ERR#43 'Protocol not supported' Message-ID: <81924694@bb.ipt.ru> Hello List, I'm working on Fedora 10 ports and almost all is fine (even google-earth seems to work)... But there is no resolving. I managed to find the culprit. Here it is: ----- bb% uname -a FreeBSD bb.ipt.ru 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Thu Apr 30 09:15:06 MSD 2009 root@bb.ipt.ru:/usr/obj/usr/src/sys/BB i386 bb% pkg_info -xI linux linux-f10-atk-1.24.0 Accessibility Toolkit, Linux/i386 binary (Linux Fedora 10) linux-f10-cairo-1.8.0 Vector graphics library Cairo (Linux Fedora 10) linux-f10-expat-2.0.1 Linux/i386 binary port of Expat XML-parsing library (Linux linux-f10-fontconfig-2.6.0 An XML-based font configuration API for X Windows (Linux Fe linux-f10-gtk2-2.14.7 GTK+ library, version 2.X (Linux Fedora 10) linux-f10-hicolor-icon-theme-0.5 A high-color icon theme shell from the FreeDesktop project linux-f10-iputils-20071127 PLEASE, place a comment here linux-f10-jpeg-6b RPM of the JPEG lib (Linux Fedora 10) linux-f10-libcap-2.10 PLEASE, place a comment here linux-f10-libidn-0.6.14 Internationalized Domain Name support library (Linux Fedora linux-f10-pango-1.22.3 The pango library (Linux Fedora 10) linux-f10-png-1.2.35 RPM of the PNG lib (Linux Fedora 10) linux-f10-tiff-3.8.2 The TIFF library, Linux/i386 binary (Linux Fedora 10) linux-f10-xorg-libs-7.4 Xorg libraries (Linux Fedora 10) linux-seamonkey-1.1.16 The open source, standards compliant web browser linux_base-f10-10 Base set of packages needed in Linux mode for i386/amd64 (L linux_kdump-1.5_2 Linux-compatability ktrace.out processor bb% truss /compat/linux/bin/ping www.ru | head -3 linux_brk(0x0,0x33c71fd0,0x8049570,0xbfebfbff,0xbfbfffac,0x6) = 134631424 (0x8065000) linux_newuname(0xbfbfe3de,0x33c72284,0x33c71fd0,0x33c72648,0x33c72648,0x6) = 0 (0x0) linux_access(0x33c6db54,0x4,0x33c71fd0,0x33c6db54,0x33c72630,0x6) ERR#2 'No such file or directory' linux_open("/etc/ld.so.cache",0x0,00) = 3 (0x3) linux_fstat64(0x3,0xbfbfe01c,0x33c71fd0,0xffffffff,0x3,0x6) = 0 (0x0) linux_mmap2(0x0,0x2f0e,0x1,0x2,0x3,0x6) = 868691968 (0x33c73000) close(3) = 0 (0x0) linux_open("/lib/libidn.so.11",0x0,01001104535) = 3 (0x3) read(3,"\^?ELF\^A\^A\^A\0\0\0\0\0\0\0\0"...,512) = 512 (0x200) linux_fstat64(0x3,0xbfbfe084,0x33c71fd0,0x3,0x1,0x6) = 0 (0x0) [...] linux_open("/lib/libresolv.so.2",0x0,06370573370) = 3 (0x3) read(3,"\^?ELF\^A\^A\^A\0\0\0\0\0\0\0\0"...,512) = 512 (0x200) linux_fstat64(0x3,0xbfbfdd34,0x33c71fd0,0x3,0x2,0x6) = 0 (0x0) linux_mmap2(0x0,0x16848,0x5,0x802,0x3,0x6) = 870539264 (0x33e36000) linux_mmap2(0x33e49000,0x2000,0x3,0x812,0x3,0x6) = 870617088 (0x33e49000) linux_mmap2(0x33e4b000,0x1848,0x3,0x32,0xffffffff,0x6) = 870625280 (0x33e4b000) close(3) = 0 (0x0) linux_mprotect(0x33e49000,0x1000,0x1,0x807fe70,0x807fe70,0x6) = 0 (0x0) linux_mprotect(0x33e34000,0x1000,0x1,0x807fbf8,0x807fbf8,0x6) = 0 (0x0) munmap(0x33c73000,12046) = 0 (0x0) gettimeofday({1241502125.038245 },0x0) = 0 (0x0) linux_socketcall(0x1,0xbfbfd218,0x33e49ff4,0x80802c8,0x0,0x6) ERR#43 'Protocol not supported' gettimeofday({1241502125.038387 },0x0) = 0 (0x0) linux_socketcall(0x1,0xbfbfd218,0x33e49ff4,0x80802c8,0x0,0x6) ERR#43 'Protocol not supported' ping: unknown host www.ru write(2,"ping: unknown host www.ru\n",26) = 26 (0x1a) process exit, rval = 2 ----- Ktrace/linux_kdump gives this: ----- 48833 ping CALL linux_socketcall(0x1,0xbfbfd218) 48833 ping RET linux_socketcall -1 errno 93 Unknown error: 93 48833 ping CALL gettimeofday(0xbfbfd2e0,0) 48833 ping RET gettimeofday 0 48833 ping CALL linux_socketcall(0x1,0xbfbfd218) 48833 ping RET linux_socketcall -1 errno 93 Unknown error: 93 48833 ping CALL write(0x2,0xbfbfbf48,0x1a) 48833 ping GIO fd 2 wrote 26 bytes "ping: unknown host www.ru " 48833 ping RET write 26/0x1a 48833 ping CALL linux_exit_group(0x2) ---- If we manage to solve this, I'd say we are ready for f10. 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 peterjeremy at optushome.com.au Tue May 5 07:59:02 2009 From: peterjeremy at optushome.com.au (Peter Jeremy) Date: Tue May 5 07:59:08 2009 Subject: Flash issues on -current/i386 Message-ID: <20090505074827.GA93977@server.vk2pj.dyndns.org> I am trying to get flash running inside Firefox, primarily to be able to watch streaming video on my system running a 2-week old -current. I've tried enabling Linux 2.6.16 and installed Flash10 - this mostly works for youtube but fails for www.abc.net.au/iview (this link may not work outside .au) - reporting continual connection failures. (Audio does work though). I then tried revering to flash9 (still with 2.6.16 and fc8). This can successfully display video from both youtube and iview but has no audio - it consistently reports the following: ALSA lib confmisc.c:768:(parse_card) cannot find card '0' ALSA lib conf.c:3510:(_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:3510:(_snd_config_evaluate) function snd_func_concat returned error: No such device ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name ALSA lib conf.c:3510:(_snd_config_evaluate) function snd_func_refer returned error: No such device ALSA lib conf.c:3982:(snd_config_expand) Evaluate error: No such device ALSA lib pcm.c:2145:(snd_pcm_open_noupdate) Unknown PCM default ALSA lib pcm_hw.c:1207:(_snd_pcm_hw_open) Invalid value for card I tried installing the Linux binary for Firefox 3.0.10 with the same results. A search for the above error comes up with lots of hits but I haven't managed to find a resolution yet. Can anyone offer a solution (or some pointers on how to trace exactly what it is doing)? Please copy me on any responses. -- Peter Jeremy -------------- 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/20090505/c8a64559/attachment.pgp From Alexander at Leidinger.net Tue May 5 12:50:12 2009 From: Alexander at Leidinger.net (Alexander Leidinger) Date: Tue May 5 12:50:20 2009 Subject: [linux-f10] linux_socketcall... ERR#43 'Protocol not supported' In-Reply-To: <81924694@bb.ipt.ru> References: <81924694@bb.ipt.ru> Message-ID: <20090505144955.16373k1b32dpaxo0@webmail.leidinger.net> Quoting Boris Samorodov (from Tue, 05 May 2009 09:51:21 +0400): > Hello List, > > > I'm working on Fedora 10 ports and almost all is fine (even > google-earth seems to work)... But there is no resolving. > I managed to find the culprit. Here it is: > Ktrace/linux_kdump gives this: > ----- > 48833 ping CALL linux_socketcall(0x1,0xbfbfd218) > 48833 ping RET linux_socketcall -1 errno 93 Unknown error: 93 > 48833 ping CALL gettimeofday(0xbfbfd2e0,0) > 48833 ping RET gettimeofday 0 > 48833 ping CALL linux_socketcall(0x1,0xbfbfd218) > 48833 ping RET linux_socketcall -1 errno 93 Unknown error: 93 > 48833 ping CALL write(0x2,0xbfbfbf48,0x1a) > 48833 ping GIO fd 2 wrote 26 bytes > "ping: unknown host www.ru > " > 48833 ping RET write 26/0x1a > 48833 ping CALL linux_exit_group(0x2) > ---- There was a commit after April 30 about linux socket stuff. I don't know if it is related or not. You can either update and test, or instrument the current code to print out the parameters to linux_socketcall in a human readable way. > If we manage to solve this, I'd say we are ready for f10. I suggest to add a COMMENT to some ports before... ;-) Bye, Alexander. -- A bird in the hand is worth what it will bring. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From Alexander at Leidinger.net Tue May 5 12:56:07 2009 From: Alexander at Leidinger.net (Alexander Leidinger) Date: Tue May 5 12:57:49 2009 Subject: Flash issues on -current/i386 In-Reply-To: <20090505074827.GA93977@server.vk2pj.dyndns.org> References: <20090505074827.GA93977@server.vk2pj.dyndns.org> Message-ID: <20090505145543.28393p52iyzgqu80@webmail.leidinger.net> Quoting Peter Jeremy (from Tue, 5 May 2009 17:48:27 +1000): > I then tried revering to flash9 (still with 2.6.16 and fc8). This > can successfully display video from both youtube and iview but has > no audio - it consistently reports the following: > ALSA lib confmisc.c:768:(parse_card) cannot find card '0' > ALSA lib conf.c:3510:(_snd_config_evaluate) function The flashsupport lib does not fit to your flash9. It is responsible to use OSS instead of ALSA. Look around on the emulation@ ML for places where you could try looking for it (if the ports doesn't provide it for your OS version). Bye, Alexander. -- BOFH excuse #241: _Rosin_ core solder? But... http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From dchagin at freebsd.org Tue May 5 13:05:31 2009 From: dchagin at freebsd.org (Chagin Dmitry) Date: Tue May 5 13:05:38 2009 Subject: [linux-f10] linux_socketcall... ERR#43 'Protocol not supported' In-Reply-To: <81924694@bb.ipt.ru> References: <81924694@bb.ipt.ru> Message-ID: <20090505130525.GA7564@dchagin.static.corbina.ru> On Tue, May 05, 2009 at 09:51:21AM +0400, Boris Samorodov wrote: > Hello List, > > > I'm working on Fedora 10 ports and almost all is fine (even > google-earth seems to work)... But there is no resolving. > I managed to find the culprit. Here it is: > > ----- > bb% uname -a > FreeBSD bb.ipt.ru 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Thu Apr 30 09:15:06 MSD 2009 root@bb.ipt.ru:/usr/obj/usr/src/sys/BB i386 > > bb% pkg_info -xI linux > linux-f10-atk-1.24.0 Accessibility Toolkit, Linux/i386 binary (Linux Fedora 10) > linux-f10-cairo-1.8.0 Vector graphics library Cairo (Linux Fedora 10) > linux-f10-expat-2.0.1 Linux/i386 binary port of Expat XML-parsing library (Linux > linux-f10-fontconfig-2.6.0 An XML-based font configuration API for X Windows (Linux Fe > linux-f10-gtk2-2.14.7 GTK+ library, version 2.X (Linux Fedora 10) > linux-f10-hicolor-icon-theme-0.5 A high-color icon theme shell from the FreeDesktop project > linux-f10-iputils-20071127 PLEASE, place a comment here > linux-f10-jpeg-6b RPM of the JPEG lib (Linux Fedora 10) > linux-f10-libcap-2.10 PLEASE, place a comment here > linux-f10-libidn-0.6.14 Internationalized Domain Name support library (Linux Fedora > linux-f10-pango-1.22.3 The pango library (Linux Fedora 10) > linux-f10-png-1.2.35 RPM of the PNG lib (Linux Fedora 10) > linux-f10-tiff-3.8.2 The TIFF library, Linux/i386 binary (Linux Fedora 10) > linux-f10-xorg-libs-7.4 Xorg libraries (Linux Fedora 10) > linux-seamonkey-1.1.16 The open source, standards compliant web browser > linux_base-f10-10 Base set of packages needed in Linux mode for i386/amd64 (L > linux_kdump-1.5_2 Linux-compatability ktrace.out processor > > bb% truss /compat/linux/bin/ping www.ru | head -3 > linux_brk(0x0,0x33c71fd0,0x8049570,0xbfebfbff,0xbfbfffac,0x6) = 134631424 (0x8065000) > linux_newuname(0xbfbfe3de,0x33c72284,0x33c71fd0,0x33c72648,0x33c72648,0x6) = 0 (0x0) > linux_access(0x33c6db54,0x4,0x33c71fd0,0x33c6db54,0x33c72630,0x6) ERR#2 'No such file or directory' > linux_open("/etc/ld.so.cache",0x0,00) = 3 (0x3) > linux_fstat64(0x3,0xbfbfe01c,0x33c71fd0,0xffffffff,0x3,0x6) = 0 (0x0) > linux_mmap2(0x0,0x2f0e,0x1,0x2,0x3,0x6) = 868691968 (0x33c73000) > close(3) = 0 (0x0) > linux_open("/lib/libidn.so.11",0x0,01001104535) = 3 (0x3) > read(3,"\^?ELF\^A\^A\^A\0\0\0\0\0\0\0\0"...,512) = 512 (0x200) > linux_fstat64(0x3,0xbfbfe084,0x33c71fd0,0x3,0x1,0x6) = 0 (0x0) > [...] > linux_open("/lib/libresolv.so.2",0x0,06370573370) = 3 (0x3) > read(3,"\^?ELF\^A\^A\^A\0\0\0\0\0\0\0\0"...,512) = 512 (0x200) > linux_fstat64(0x3,0xbfbfdd34,0x33c71fd0,0x3,0x2,0x6) = 0 (0x0) > linux_mmap2(0x0,0x16848,0x5,0x802,0x3,0x6) = 870539264 (0x33e36000) > linux_mmap2(0x33e49000,0x2000,0x3,0x812,0x3,0x6) = 870617088 (0x33e49000) > linux_mmap2(0x33e4b000,0x1848,0x3,0x32,0xffffffff,0x6) = 870625280 (0x33e4b000) > close(3) = 0 (0x0) > linux_mprotect(0x33e49000,0x1000,0x1,0x807fe70,0x807fe70,0x6) = 0 (0x0) > linux_mprotect(0x33e34000,0x1000,0x1,0x807fbf8,0x807fbf8,0x6) = 0 (0x0) > munmap(0x33c73000,12046) = 0 (0x0) > gettimeofday({1241502125.038245 },0x0) = 0 (0x0) > linux_socketcall(0x1,0xbfbfd218,0x33e49ff4,0x80802c8,0x0,0x6) ERR#43 'Protocol not supported' > gettimeofday({1241502125.038387 },0x0) = 0 (0x0) > linux_socketcall(0x1,0xbfbfd218,0x33e49ff4,0x80802c8,0x0,0x6) ERR#43 'Protocol not supported' > ping: unknown host www.ru > write(2,"ping: unknown host www.ru\n",26) = 26 (0x1a) > process exit, rval = 2 > ----- > > Ktrace/linux_kdump gives this: > ----- > 48833 ping CALL linux_socketcall(0x1,0xbfbfd218) > 48833 ping RET linux_socketcall -1 errno 93 Unknown error: 93 > 48833 ping CALL gettimeofday(0xbfbfd2e0,0) > 48833 ping RET gettimeofday 0 > 48833 ping CALL linux_socketcall(0x1,0xbfbfd218) > 48833 ping RET linux_socketcall -1 errno 93 Unknown error: 93 > 48833 ping CALL write(0x2,0xbfbfbf48,0x1a) > 48833 ping GIO fd 2 wrote 26 bytes > "ping: unknown host www.ru > " > 48833 ping RET write 26/0x1a > 48833 ping CALL linux_exit_group(0x2) > ---- > > If we manage to solve this, I'd say we are ready for f10. > Thanks. > > Hi Boris, Whether you somewhere can put a ping binary? And which glibc version f10 uses? -- Have fun! chd -------------- 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/20090505/0e676bf1/attachment.pgp From tijl at ulyssis.org Tue May 5 13:25:00 2009 From: tijl at ulyssis.org (Tijl Coosemans) Date: Tue May 5 13:25:07 2009 Subject: Flash issues on -current/i386 In-Reply-To: <20090505145543.28393p52iyzgqu80@webmail.leidinger.net> References: <20090505074827.GA93977@server.vk2pj.dyndns.org> <20090505145543.28393p52iyzgqu80@webmail.leidinger.net> Message-ID: <200905051524.56217.tijl@ulyssis.org> On Tuesday 05 May 2009 14:55:43 Alexander Leidinger wrote: > Quoting Peter Jeremy (from Tue, 5 May > 2009 17:48:27 +1000): > >> I then tried revering to flash9 (still with 2.6.16 and fc8). This >> can successfully display video from both youtube and iview but has >> no audio - it consistently reports the following: >> ALSA lib confmisc.c:768:(parse_card) cannot find card '0' >> ALSA lib conf.c:3510:(_snd_config_evaluate) function > > The flashsupport lib does not fit to your flash9. It is responsible > to use OSS instead of ALSA. Look around on the emulation@ ML for > places where you could try looking for it (if the ports doesn't > provide it for your OS version). You can use libflashsupport from linux-f8-flashplugin10. From bsam at ipt.ru Tue May 5 13:42:08 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Tue May 5 13:42:15 2009 Subject: [linux-f10] linux_socketcall... ERR#43 'Protocol not supported' In-Reply-To: <20090505130525.GA7564@dchagin.static.corbina.ru> (Chagin Dmitry's message of "Tue\, 5 May 2009 17\:05\:25 +0400") References: <81924694@bb.ipt.ru> <20090505130525.GA7564@dchagin.static.corbina.ru> Message-ID: <14073412@bb.ipt.ru> On Tue, 5 May 2009 17:05:25 +0400 Chagin Dmitry wrote: > Whether you somewhere can put a ping binary? Here is a shar of linux_base-f10 and linux-f10-iputils: ftp://ftp.ipt.ru/pub/linux/f10+iputils.shar It is relative to /usr/ports, i.e.: # cd /usr/ports # sh > And which glibc version f10 uses? Seems to be glibc-2.9. 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 Tue May 5 13:44:56 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Tue May 5 13:45:11 2009 Subject: [linux-f10] linux_socketcall... ERR#43 'Protocol not supported' In-Reply-To: <20090505144955.16373k1b32dpaxo0@webmail.leidinger.net> (Alexander Leidinger's message of "Tue\, 05 May 2009 14\:49\:55 +0200") References: <81924694@bb.ipt.ru> <20090505144955.16373k1b32dpaxo0@webmail.leidinger.net> Message-ID: <47993241@bb.ipt.ru> On Tue, 05 May 2009 14:49:55 +0200 Alexander Leidinger wrote: > Quoting Boris Samorodov (from Tue, 05 May 2009 09:51:21 +0400): > > I'm working on Fedora 10 ports and almost all is fine (even > > google-earth seems to work)... But there is no resolving. > > I managed to find the culprit. Here it is: > > Ktrace/linux_kdump gives this: > > ----- > > 48833 ping CALL linux_socketcall(0x1,0xbfbfd218) > > 48833 ping RET linux_socketcall -1 errno 93 Unknown error: 93 > > 48833 ping CALL gettimeofday(0xbfbfd2e0,0) > > 48833 ping RET gettimeofday 0 > > 48833 ping CALL linux_socketcall(0x1,0xbfbfd218) > > 48833 ping RET linux_socketcall -1 errno 93 Unknown error: 93 > > 48833 ping CALL write(0x2,0xbfbfbf48,0x1a) > > 48833 ping GIO fd 2 wrote 26 bytes > > "ping: unknown host www.ru > > " > > 48833 ping RET write 26/0x1a > > 48833 ping CALL linux_exit_group(0x2) > > ---- > There was a commit after April 30 about linux socket stuff. I don't > know if it is related or not. You can either update and test, or Thanks for the info, I'm updating now. > instrument the current code to print out the parameters to > linux_socketcall in a human readable way. Can you give a tiny example? > > If we manage to solve this, I'd say we are ready for f10. > I suggest to add a COMMENT to some ports before... ;-) Those were ports just for testing needs created by my bot. ;-) WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From Alexander at Leidinger.net Tue May 5 14:08:41 2009 From: Alexander at Leidinger.net (Alexander Leidinger) Date: Tue May 5 14:08:47 2009 Subject: [linux-f10] linux_socketcall... ERR#43 'Protocol not supported' In-Reply-To: <47993241@bb.ipt.ru> References: <81924694@bb.ipt.ru> <20090505144955.16373k1b32dpaxo0@webmail.leidinger.net> <47993241@bb.ipt.ru> Message-ID: <20090505160827.1359651x47bqmxc8@webmail.leidinger.net> Quoting Boris Samorodov (from Tue, 05 May 2009 17:44:54 +0400): > On Tue, 05 May 2009 14:49:55 +0200 Alexander Leidinger wrote: >> Quoting Boris Samorodov (from Tue, 05 May 2009 >> 09:51:21 +0400): > >> > I'm working on Fedora 10 ports and almost all is fine (even >> > google-earth seems to work)... But there is no resolving. >> > I managed to find the culprit. Here it is: > >> > Ktrace/linux_kdump gives this: >> > ----- >> > 48833 ping CALL linux_socketcall(0x1,0xbfbfd218) >> > 48833 ping RET linux_socketcall -1 errno 93 Unknown error: 93 >> > 48833 ping CALL gettimeofday(0xbfbfd2e0,0) >> > 48833 ping RET gettimeofday 0 >> > 48833 ping CALL linux_socketcall(0x1,0xbfbfd218) >> > 48833 ping RET linux_socketcall -1 errno 93 Unknown error: 93 >> > 48833 ping CALL write(0x2,0xbfbfbf48,0x1a) >> > 48833 ping GIO fd 2 wrote 26 bytes >> > "ping: unknown host www.ru >> > " >> > 48833 ping RET write 26/0x1a >> > 48833 ping CALL linux_exit_group(0x2) >> > ---- > >> There was a commit after April 30 about linux socket stuff. I don't >> know if it is related or not. You can either update and test, or > > Thanks for the info, I'm updating now. > >> instrument the current code to print out the parameters to >> linux_socketcall in a human readable way. > > Can you give a tiny example? orig: ---snip--- switch (args->what) { case LINUX_SOCKET: return (linux_socket(td, arg)); case LINUX_BIND: return (linux_bind(td, arg)); ---snip--- modified (ugly): ---snip--- switch (args->what) { case LINUX_SOCKET: int ret = linux_socket(td, arg); printf("LINUX_SOCKET: %d\n", ret); return (ret); case LINUX_BIND: return (linux_bind(td, arg)); ---snip--- After this you should see in ktrace which one it tries to call. Revert to the orig one and instrument the corresponding function, for linux_socket thish would be: ---snip--- linux_socket(struct thread *td, struct linux_socket_args *args) { #ifdef INET6 INIT_VNET_INET6(curvnet); #endif struct socket_args /* { int domain; int type; int protocol; } */ bsd_args; int retval_socket; /* debug for bsam */ printf("linux_socket (LINUX): domain: %d, type: %d, protocol: %d\n", args->domain, args->type, args->protocol); bsd_args.protocol = args->protocol; bsd_args.type = args->type; bsd_args.domain = linux_to_bsd_domain(args->domain); /* debug for bsam */ printf("linux_socket (FreeBSD): domain: %d\n", bsd_args.domain); if (bsd_args.domain == -1) return (EINVAL); ---snip--- Bye, Alexander. -- The six great gifts of an Irish girl are beauty, soft voice, sweet speech, wisdom, needlework, and chastity. -- Theodore Roosevelt, 1907 http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From bsam at ipt.ru Tue May 5 14:28:46 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Tue May 5 14:28:52 2009 Subject: [linux-f10] linux_socketcall... ERR#43 'Protocol not supported' In-Reply-To: <47993241@bb.ipt.ru> (Boris Samorodov's message of "Tue\, 05 May 2009 17\:44\:54 +0400") References: <81924694@bb.ipt.ru> <20090505144955.16373k1b32dpaxo0@webmail.leidinger.net> <47993241@bb.ipt.ru> Message-ID: <58710436@bb.ipt.ru> On Tue, 05 May 2009 17:44:54 +0400 Boris Samorodov wrote: > On Tue, 05 May 2009 14:49:55 +0200 Alexander Leidinger wrote: > > Quoting Boris Samorodov (from Tue, 05 May 2009 09:51:21 +0400): > > > I'm working on Fedora 10 ports and almost all is fine (even > > > google-earth seems to work)... But there is no resolving. > > > I managed to find the culprit. Here it is: > > > Ktrace/linux_kdump gives this: > > > ----- > > > 48833 ping CALL linux_socketcall(0x1,0xbfbfd218) > > > 48833 ping RET linux_socketcall -1 errno 93 Unknown error: 93 > > > 48833 ping CALL gettimeofday(0xbfbfd2e0,0) > > > 48833 ping RET gettimeofday 0 > > > 48833 ping CALL linux_socketcall(0x1,0xbfbfd218) > > > 48833 ping RET linux_socketcall -1 errno 93 Unknown error: 93 > > > 48833 ping CALL write(0x2,0xbfbfbf48,0x1a) > > > 48833 ping GIO fd 2 wrote 26 bytes > > > "ping: unknown host www.ru > > > " > > > 48833 ping RET write 26/0x1a > > > 48833 ping CALL linux_exit_group(0x2) > > > ---- > > There was a commit after April 30 about linux socket stuff. I don't > > know if it is related or not. You can either update and test, or > Thanks for the info, I'm updating now. Didn't help. Go to instrumenting as you suggested. 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 Tue May 5 15:26:31 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Tue May 5 15:26:38 2009 Subject: [linux-f10] linux_socketcall... ERR#43 'Protocol not supported' In-Reply-To: <20090505160827.1359651x47bqmxc8@webmail.leidinger.net> (Alexander Leidinger's message of "Tue\, 05 May 2009 16\:08\:27 +0200") References: <81924694@bb.ipt.ru> <20090505144955.16373k1b32dpaxo0@webmail.leidinger.net> <47993241@bb.ipt.ru> <20090505160827.1359651x47bqmxc8@webmail.leidinger.net> Message-ID: <67678219@bb.ipt.ru> On Tue, 05 May 2009 16:08:27 +0200 Alexander Leidinger wrote: > Quoting Boris Samorodov (from Tue, 05 May 2009 17:44:54 +0400): > > On Tue, 05 May 2009 14:49:55 +0200 Alexander Leidinger wrote: > >> Quoting Boris Samorodov (from Tue, 05 May 2009 > >> 09:51:21 +0400): > > > >> > I'm working on Fedora 10 ports and almost all is fine (even > >> > google-earth seems to work)... But there is no resolving. > >> > I managed to find the culprit. Here it is: > > > >> > Ktrace/linux_kdump gives this: > >> > ----- > >> > 48833 ping CALL linux_socketcall(0x1,0xbfbfd218) > >> > 48833 ping RET linux_socketcall -1 errno 93 Unknown error: 93 > >> > 48833 ping CALL gettimeofday(0xbfbfd2e0,0) > >> > 48833 ping RET gettimeofday 0 > >> > 48833 ping CALL linux_socketcall(0x1,0xbfbfd218) > >> > 48833 ping RET linux_socketcall -1 errno 93 Unknown error: 93 > >> > 48833 ping CALL write(0x2,0xbfbfbf48,0x1a) > >> > 48833 ping GIO fd 2 wrote 26 bytes > >> > "ping: unknown host www.ru > >> > " > >> > 48833 ping RET write 26/0x1a > >> > 48833 ping CALL linux_exit_group(0x2) > >> > ---- > > > >> There was a commit after April 30 about linux socket stuff. I don't > >> know if it is related or not. You can either update and test, or > > > > Thanks for the info, I'm updating now. > > > >> instrument the current code to print out the parameters to > >> linux_socketcall in a human readable way. > > > > Can you give a tiny example? [Skip examples, thanks] The diff is: ----- --- linux_socket.c.orig 2009-05-05 18:35:31.000000000 +0400 +++ linux_socket.c 2009-05-05 19:02:42.000000000 +0400 @@ -595,9 +595,15 @@ } */ bsd_args; int retval_socket; + printf("bsam: linux_socket (LINUX): domain: %d, type: %d, protocol: %d\n", + args->domain, args->type, args->protocol); + bsd_args.protocol = args->protocol; bsd_args.type = args->type; bsd_args.domain = linux_to_bsd_domain(args->domain); + + printf("bsam: linux_socket (FreeBSD): domain: %d\n", bsd_args.domain); + if (bsd_args.domain == -1) return (EINVAL); @@ -1365,10 +1371,14 @@ linux_socketcall(struct thread *td, struct linux_socketcall_args *args) { void *arg = (void *)(intptr_t)args->args; + int ret; + printf("bsam: Entering linux_socketcall.\n"); switch (args->what) { case LINUX_SOCKET: - return (linux_socket(td, arg)); + ret = linux_socket(td, arg); + printf("bsam: LINUX_SOCKET: %d\n", ret); + return (ret); case LINUX_BIND: return (linux_bind(td, arg)); case LINUX_CONNECT: ----- Console diagnistic is: ----- May 5 19:10:33 bb kernel: bsam: Entering linux_socketcall. May 5 19:10:33 bb kernel: bsam: linux_socket (LINUX): domain: 2, type: 3, protocol: 1 May 5 19:10:33 bb kernel: bsam: linux_socket (FreeBSD): domain: 2 May 5 19:10:33 bb kernel: bsam: LINUX_SOCKET: 1 May 5 19:10:33 bb kernel: bsam: Entering linux_socketcall. May 5 19:10:33 bb kernel: bsam: linux_socket (LINUX): domain: 1, type: 526337, protocol: 0 May 5 19:10:33 bb kernel: bsam: linux_socket (FreeBSD): domain: 1 May 5 19:10:33 bb kernel: bsam: LINUX_SOCKET: 43 May 5 19:10:33 bb kernel: bsam: Entering linux_socketcall. May 5 19:10:33 bb kernel: bsam: linux_socket (LINUX): domain: 1, type: 526337, protocol: 0 May 5 19:10:33 bb kernel: bsam: linux_socket (FreeBSD): domain: 1 May 5 19:10:33 bb kernel: bsam: LINUX_SOCKET: 43 May 5 19:10:34 bb kernel: bsam: Entering linux_socketcall. May 5 19:10:34 bb kernel: bsam: linux_socket (LINUX): domain: 2, type: 2050, protocol: 0 May 5 19:10:34 bb kernel: bsam: linux_socket (FreeBSD): domain: 2 May 5 19:10:34 bb kernel: bsam: LINUX_SOCKET: 43 May 5 19:10:34 bb kernel: bsam: Entering linux_socketcall. May 5 19:10:34 bb kernel: bsam: linux_socket (LINUX): domain: 2, type: 2050, protocol: 0 May 5 19:10:34 bb kernel: bsam: linux_socket (FreeBSD): domain: 2 May 5 19:10:34 bb kernel: bsam: LINUX_SOCKET: 43 ----- Corresponding text for linux_kdump and truss: ftp://ftp.ipt.ru/pub/linux/linux_kdump.ping.txt ftp://ftp.ipt.ru/pub/linux/truss.ping.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 dchagin at freebsd.org Tue May 5 16:04:27 2009 From: dchagin at freebsd.org (Chagin Dmitry) Date: Tue May 5 16:04:33 2009 Subject: [linux-f10] linux_socketcall... ERR#43 'Protocol not supported' In-Reply-To: <14073412@bb.ipt.ru> References: <81924694@bb.ipt.ru> <20090505130525.GA7564@dchagin.static.corbina.ru> <14073412@bb.ipt.ru> Message-ID: <20090505160417.GA14703@dchagin.static.corbina.ru> On Tue, May 05, 2009 at 05:42:03PM +0400, Boris Samorodov wrote: > On Tue, 5 May 2009 17:05:25 +0400 Chagin Dmitry wrote: > > > Whether you somewhere can put a ping binary? > > Here is a shar of linux_base-f10 and linux-f10-iputils: > ftp://ftp.ipt.ru/pub/linux/f10+iputils.shar > It is relative to /usr/ports, i.e.: > # cd /usr/ports > # sh => Couldn't fetch it - please try to retrieve this iputils-20071127-6.fc10.i386.rpm > > > And which glibc version f10 uses? > > Seems to be glibc-2.9. > good. -- Have fun! chd -------------- 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/20090505/27efcbf6/attachment.pgp From dchagin at freebsd.org Tue May 5 16:07:32 2009 From: dchagin at freebsd.org (Chagin Dmitry) Date: Tue May 5 16:07:38 2009 Subject: [linux-f10] linux_socketcall... ERR#43 'Protocol not supported' In-Reply-To: <67678219@bb.ipt.ru> References: <81924694@bb.ipt.ru> <20090505144955.16373k1b32dpaxo0@webmail.leidinger.net> <47993241@bb.ipt.ru> <20090505160827.1359651x47bqmxc8@webmail.leidinger.net> <67678219@bb.ipt.ru> Message-ID: <20090505160724.GB14703@dchagin.static.corbina.ru> On Tue, May 05, 2009 at 07:26:28PM +0400, Boris Samorodov wrote: > On Tue, 05 May 2009 16:08:27 +0200 Alexander Leidinger wrote: > > Quoting Boris Samorodov (from Tue, 05 May 2009 17:44:54 +0400): > > > On Tue, 05 May 2009 14:49:55 +0200 Alexander Leidinger wrote: > > >> Quoting Boris Samorodov (from Tue, 05 May 2009 > > >> 09:51:21 +0400): > > > > > >> > I'm working on Fedora 10 ports and almost all is fine (even > > >> > google-earth seems to work)... But there is no resolving. > > >> > I managed to find the culprit. Here it is: > > > > > >> > Ktrace/linux_kdump gives this: > > >> > ----- > > >> > 48833 ping CALL linux_socketcall(0x1,0xbfbfd218) > > >> > 48833 ping RET linux_socketcall -1 errno 93 Unknown error: 93 > > >> > 48833 ping CALL gettimeofday(0xbfbfd2e0,0) > > >> > 48833 ping RET gettimeofday 0 > > >> > 48833 ping CALL linux_socketcall(0x1,0xbfbfd218) > > >> > 48833 ping RET linux_socketcall -1 errno 93 Unknown error: 93 > > >> > 48833 ping CALL write(0x2,0xbfbfbf48,0x1a) > > >> > 48833 ping GIO fd 2 wrote 26 bytes > > >> > "ping: unknown host www.ru > > >> > " > > >> > 48833 ping RET write 26/0x1a > > >> > 48833 ping CALL linux_exit_group(0x2) > > >> > ---- > > > > > >> There was a commit after April 30 about linux socket stuff. I don't > > >> know if it is related or not. You can either update and test, or > > > > > > Thanks for the info, I'm updating now. > > > > > >> instrument the current code to print out the parameters to > > >> linux_socketcall in a human readable way. > > > > > > Can you give a tiny example? > > [Skip examples, thanks] > > The diff is: > ----- > --- linux_socket.c.orig 2009-05-05 18:35:31.000000000 +0400 > +++ linux_socket.c 2009-05-05 19:02:42.000000000 +0400 > @@ -595,9 +595,15 @@ > } */ bsd_args; > int retval_socket; > > + printf("bsam: linux_socket (LINUX): domain: %d, type: %d, protocol: %d\n", > + args->domain, args->type, args->protocol); > + > bsd_args.protocol = args->protocol; > bsd_args.type = args->type; > bsd_args.domain = linux_to_bsd_domain(args->domain); > + > + printf("bsam: linux_socket (FreeBSD): domain: %d\n", bsd_args.domain); > + > if (bsd_args.domain == -1) > return (EINVAL); > > @@ -1365,10 +1371,14 @@ > linux_socketcall(struct thread *td, struct linux_socketcall_args *args) > { > void *arg = (void *)(intptr_t)args->args; > + int ret; > > + printf("bsam: Entering linux_socketcall.\n"); > switch (args->what) { > case LINUX_SOCKET: > - return (linux_socket(td, arg)); > + ret = linux_socket(td, arg); > + printf("bsam: LINUX_SOCKET: %d\n", ret); > + return (ret); > case LINUX_BIND: > return (linux_bind(td, arg)); > case LINUX_CONNECT: > ----- > > Console diagnistic is: > ----- > May 5 19:10:33 bb kernel: bsam: Entering linux_socketcall. > May 5 19:10:33 bb kernel: bsam: linux_socket (LINUX): domain: 2, type: 3, protocol: 1 > May 5 19:10:33 bb kernel: bsam: linux_socket (FreeBSD): domain: 2 > May 5 19:10:33 bb kernel: bsam: LINUX_SOCKET: 1 > May 5 19:10:33 bb kernel: bsam: Entering linux_socketcall. > May 5 19:10:33 bb kernel: bsam: linux_socket (LINUX): domain: 1, type: 526337, protocol: 0 > May 5 19:10:33 bb kernel: bsam: linux_socket (FreeBSD): domain: 1 > May 5 19:10:33 bb kernel: bsam: LINUX_SOCKET: 43 > May 5 19:10:33 bb kernel: bsam: Entering linux_socketcall. > May 5 19:10:33 bb kernel: bsam: linux_socket (LINUX): domain: 1, type: 526337, protocol: 0 > May 5 19:10:33 bb kernel: bsam: linux_socket (FreeBSD): domain: 1 > May 5 19:10:33 bb kernel: bsam: LINUX_SOCKET: 43 > May 5 19:10:34 bb kernel: bsam: Entering linux_socketcall. > May 5 19:10:34 bb kernel: bsam: linux_socket (LINUX): domain: 2, type: 2050, protocol: 0 > May 5 19:10:34 bb kernel: bsam: linux_socket (FreeBSD): domain: 2 > May 5 19:10:34 bb kernel: bsam: LINUX_SOCKET: 43 > May 5 19:10:34 bb kernel: bsam: Entering linux_socketcall. > May 5 19:10:34 bb kernel: bsam: linux_socket (LINUX): domain: 2, type: 2050, protocol: 0 > May 5 19:10:34 bb kernel: bsam: linux_socket (FreeBSD): domain: 2 > May 5 19:10:34 bb kernel: bsam: LINUX_SOCKET: 43 > ----- > > Corresponding text for linux_kdump and truss: > ftp://ftp.ipt.ru/pub/linux/linux_kdump.ping.txt > ftp://ftp.ipt.ru/pub/linux/truss.ping.txt > heh, it seems to me that SOCK_CLOEXEC, SOCK_NONBLOCK bits used. should be fixed. socketpair() also uses it since 2.6.29 -- Have fun! chd -------------- 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/20090505/fce770d9/attachment.pgp From bsam at ipt.ru Tue May 5 16:37:42 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Tue May 5 16:37:56 2009 Subject: [linux-f10] linux_socketcall... ERR#43 'Protocol not supported' In-Reply-To: <20090505160417.GA14703@dchagin.static.corbina.ru> (Chagin Dmitry's message of "Tue\, 5 May 2009 20\:04\:17 +0400") References: <81924694@bb.ipt.ru> <20090505130525.GA7564@dchagin.static.corbina.ru> <14073412@bb.ipt.ru> <20090505160417.GA14703@dchagin.static.corbina.ru> Message-ID: <01593949@bb.ipt.ru> On Tue, 5 May 2009 20:04:17 +0400 Chagin Dmitry wrote: > On Tue, May 05, 2009 at 05:42:03PM +0400, Boris Samorodov wrote: > > On Tue, 5 May 2009 17:05:25 +0400 Chagin Dmitry wrote: > > > > > Whether you somewhere can put a ping binary? > > > > Here is a shar of linux_base-f10 and linux-f10-iputils: > > ftp://ftp.ipt.ru/pub/linux/f10+iputils.shar > > It is relative to /usr/ports, i.e.: > > # cd /usr/ports > > # sh > => Couldn't fetch it - please try to retrieve this Any diagnostic? > iputils-20071127-6.fc10.i386.rpm 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 Tue May 5 16:41:03 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Tue May 5 16:41:10 2009 Subject: [linux-f10] linux_socketcall... ERR#43 'Protocol not supported' In-Reply-To: <20090505160724.GB14703@dchagin.static.corbina.ru> (Chagin Dmitry's message of "Tue\, 5 May 2009 20\:07\:24 +0400") References: <81924694@bb.ipt.ru> <20090505144955.16373k1b32dpaxo0@webmail.leidinger.net> <47993241@bb.ipt.ru> <20090505160827.1359651x47bqmxc8@webmail.leidinger.net> <67678219@bb.ipt.ru> <20090505160724.GB14703@dchagin.static.corbina.ru> Message-ID: <35513746@bb.ipt.ru> On Tue, 5 May 2009 20:07:24 +0400 Chagin Dmitry wrote: > On Tue, May 05, 2009 at 07:26:28PM +0400, Boris Samorodov wrote: > > The diff is: > > ----- > > --- linux_socket.c.orig 2009-05-05 18:35:31.000000000 +0400 > > +++ linux_socket.c 2009-05-05 19:02:42.000000000 +0400 > > @@ -595,9 +595,15 @@ > > } */ bsd_args; > > int retval_socket; > > > > + printf("bsam: linux_socket (LINUX): domain: %d, type: %d, protocol: %d\n", > > + args->domain, args->type, args->protocol); > > + > > bsd_args.protocol = args->protocol; > > bsd_args.type = args->type; > > bsd_args.domain = linux_to_bsd_domain(args->domain); > > + > > + printf("bsam: linux_socket (FreeBSD): domain: %d\n", bsd_args.domain); > > + > > if (bsd_args.domain == -1) > > return (EINVAL); > > > > @@ -1365,10 +1371,14 @@ > > linux_socketcall(struct thread *td, struct linux_socketcall_args *args) > > { > > void *arg = (void *)(intptr_t)args->args; > > + int ret; > > > > + printf("bsam: Entering linux_socketcall.\n"); > > switch (args->what) { > > case LINUX_SOCKET: > > - return (linux_socket(td, arg)); > > + ret = linux_socket(td, arg); > > + printf("bsam: LINUX_SOCKET: %d\n", ret); > > + return (ret); > > case LINUX_BIND: > > return (linux_bind(td, arg)); > > case LINUX_CONNECT: > > ----- > > > > Console diagnistic is: > > ----- > > May 5 19:10:33 bb kernel: bsam: Entering linux_socketcall. > > May 5 19:10:33 bb kernel: bsam: linux_socket (LINUX): domain: 2, type: 3, protocol: 1 > > May 5 19:10:33 bb kernel: bsam: linux_socket (FreeBSD): domain: 2 > > May 5 19:10:33 bb kernel: bsam: LINUX_SOCKET: 1 > > May 5 19:10:33 bb kernel: bsam: Entering linux_socketcall. > > May 5 19:10:33 bb kernel: bsam: linux_socket (LINUX): domain: 1, type: 526337, protocol: 0 > > May 5 19:10:33 bb kernel: bsam: linux_socket (FreeBSD): domain: 1 > > May 5 19:10:33 bb kernel: bsam: LINUX_SOCKET: 43 > > May 5 19:10:33 bb kernel: bsam: Entering linux_socketcall. > > May 5 19:10:33 bb kernel: bsam: linux_socket (LINUX): domain: 1, type: 526337, protocol: 0 > > May 5 19:10:33 bb kernel: bsam: linux_socket (FreeBSD): domain: 1 > > May 5 19:10:33 bb kernel: bsam: LINUX_SOCKET: 43 > > May 5 19:10:34 bb kernel: bsam: Entering linux_socketcall. > > May 5 19:10:34 bb kernel: bsam: linux_socket (LINUX): domain: 2, type: 2050, protocol: 0 > > May 5 19:10:34 bb kernel: bsam: linux_socket (FreeBSD): domain: 2 > > May 5 19:10:34 bb kernel: bsam: LINUX_SOCKET: 43 > > May 5 19:10:34 bb kernel: bsam: Entering linux_socketcall. > > May 5 19:10:34 bb kernel: bsam: linux_socket (LINUX): domain: 2, type: 2050, protocol: 0 > > May 5 19:10:34 bb kernel: bsam: linux_socket (FreeBSD): domain: 2 > > May 5 19:10:34 bb kernel: bsam: LINUX_SOCKET: 43 > > ----- > > > > Corresponding text for linux_kdump and truss: > > ftp://ftp.ipt.ru/pub/linux/linux_kdump.ping.txt > > ftp://ftp.ipt.ru/pub/linux/truss.ping.txt > > > heh, it seems to me that SOCK_CLOEXEC, SOCK_NONBLOCK bits used. > should be fixed. socketpair() also uses it since 2.6.29 I'll be glad to test patches. WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From dchagin at freebsd.org Tue May 5 16:50:57 2009 From: dchagin at freebsd.org (Chagin Dmitry) Date: Tue May 5 16:51:04 2009 Subject: [linux-f10] linux_socketcall... ERR#43 'Protocol not supported' In-Reply-To: <01593949@bb.ipt.ru> References: <81924694@bb.ipt.ru> <20090505130525.GA7564@dchagin.static.corbina.ru> <14073412@bb.ipt.ru> <20090505160417.GA14703@dchagin.static.corbina.ru> <01593949@bb.ipt.ru> Message-ID: <20090505165050.GA15487@dchagin.static.corbina.ru> On Tue, May 05, 2009 at 08:37:38PM +0400, Boris Samorodov wrote: > On Tue, 5 May 2009 20:04:17 +0400 Chagin Dmitry wrote: > > On Tue, May 05, 2009 at 05:42:03PM +0400, Boris Samorodov wrote: > > > On Tue, 5 May 2009 17:05:25 +0400 Chagin Dmitry wrote: > > > > > > > Whether you somewhere can put a ping binary? > > > > > > Here is a shar of linux_base-f10 and linux-f10-iputils: > > > ftp://ftp.ipt.ru/pub/linux/f10+iputils.shar > > > It is relative to /usr/ports, i.e.: > > > # cd /usr/ports > > > # sh > > > => Couldn't fetch it - please try to retrieve this > > Any diagnostic? > It seems that it does not search in a releases directory, looks only to updates :) I have copied a file manually. -- Have fun! chd -------------- 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/20090505/d243cffd/attachment.pgp From bsam at ipt.ru Tue May 5 17:04:56 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Tue May 5 17:05:01 2009 Subject: [linux-f10] linux_socketcall... ERR#43 'Protocol not supported' In-Reply-To: <20090505165050.GA15487@dchagin.static.corbina.ru> (Chagin Dmitry's message of "Tue\, 5 May 2009 20\:50\:50 +0400") References: <81924694@bb.ipt.ru> <20090505130525.GA7564@dchagin.static.corbina.ru> <14073412@bb.ipt.ru> <20090505160417.GA14703@dchagin.static.corbina.ru> <01593949@bb.ipt.ru> <20090505165050.GA15487@dchagin.static.corbina.ru> Message-ID: <37272314@bb.ipt.ru> On Tue, 5 May 2009 20:50:50 +0400 Chagin Dmitry wrote: > On Tue, May 05, 2009 at 08:37:38PM +0400, Boris Samorodov wrote: > > On Tue, 5 May 2009 20:04:17 +0400 Chagin Dmitry wrote: > > > On Tue, May 05, 2009 at 05:42:03PM +0400, Boris Samorodov wrote: > > > > On Tue, 5 May 2009 17:05:25 +0400 Chagin Dmitry wrote: > > > > > > > > > Whether you somewhere can put a ping binary? > > > > > > > > Here is a shar of linux_base-f10 and linux-f10-iputils: > > > > ftp://ftp.ipt.ru/pub/linux/f10+iputils.shar > > > > It is relative to /usr/ports, i.e.: > > > > # cd /usr/ports > > > > # sh > > > > > => Couldn't fetch it - please try to retrieve this > > > > Any diagnostic? > > > It seems that it does not search in a releases directory, > looks only to updates :) > I have copied a file manually. Ah, yes! I've forgotten that I work with patched Mk/bsd.linux-* files! For those who don't want to fetch files manually, you may use the following diff: ftp://ftp.ipt.ru/pub/linux/Mk.f10.diff . WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From dchagin at freebsd.org Tue May 5 18:42:07 2009 From: dchagin at freebsd.org (Chagin Dmitry) Date: Tue May 5 18:42:14 2009 Subject: [linux-f10] linux_socketcall... ERR#43 'Protocol not supported' In-Reply-To: <35513746@bb.ipt.ru> References: <81924694@bb.ipt.ru> <20090505144955.16373k1b32dpaxo0@webmail.leidinger.net> <47993241@bb.ipt.ru> <20090505160827.1359651x47bqmxc8@webmail.leidinger.net> <67678219@bb.ipt.ru> <20090505160724.GB14703@dchagin.static.corbina.ru> <35513746@bb.ipt.ru> Message-ID: <20090505184159.GA18677@dchagin.static.corbina.ru> On Tue, May 05, 2009 at 08:41:01PM +0400, Boris Samorodov wrote: > On Tue, 5 May 2009 20:07:24 +0400 Chagin Dmitry wrote: > > On Tue, May 05, 2009 at 07:26:28PM +0400, Boris Samorodov wrote: > > > > May 5 19:10:34 bb kernel: bsam: linux_socket (LINUX): domain: 2, type: 2050, protocol: 0 > > > May 5 19:10:34 bb kernel: bsam: linux_socket (FreeBSD): domain: 2 > > > May 5 19:10:34 bb kernel: bsam: LINUX_SOCKET: 43 > > > May 5 19:10:34 bb kernel: bsam: Entering linux_socketcall. > > > May 5 19:10:34 bb kernel: bsam: linux_socket (LINUX): domain: 2, type: 2050, protocol: 0 > > > May 5 19:10:34 bb kernel: bsam: linux_socket (FreeBSD): domain: 2 > > > May 5 19:10:34 bb kernel: bsam: LINUX_SOCKET: 43 > > > ----- > > > > > > Corresponding text for linux_kdump and truss: > > > ftp://ftp.ipt.ru/pub/linux/linux_kdump.ping.txt > > > ftp://ftp.ipt.ru/pub/linux/truss.ping.txt > > > > > > heh, it seems to me that SOCK_CLOEXEC, SOCK_NONBLOCK bits used. > > should be fixed. socketpair() also uses it since 2.6.29 > > I'll be glad to test patches. > dchagin# ./ping ya.ru WARNING: setsockopt(ICMP_FILTER): Protocol not available WARNING: your kernel is veeery old. No problems. PING ya.ru (213.180.204.8) 56(84) bytes of data. ping: recvmsg: Invalid argument ping: recvmsg: Invalid argument So, more work nedeed. At least from 2.6.16 to 2.6.23 :) -- Have fun! chd -------------- 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/20090505/549f6d1e/attachment.pgp From bsam at ipt.ru Tue May 5 19:11:50 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Tue May 5 19:11:57 2009 Subject: [linux-f10] linux_socketcall... ERR#43 'Protocol not supported' In-Reply-To: <20090505184159.GA18677@dchagin.static.corbina.ru> (Chagin Dmitry's message of "Tue\, 5 May 2009 22\:41\:59 +0400") References: <81924694@bb.ipt.ru> <20090505144955.16373k1b32dpaxo0@webmail.leidinger.net> <47993241@bb.ipt.ru> <20090505160827.1359651x47bqmxc8@webmail.leidinger.net> <67678219@bb.ipt.ru> <20090505160724.GB14703@dchagin.static.corbina.ru> <35513746@bb.ipt.ru> <20090505184159.GA18677@dchagin.static.corbina.ru> Message-ID: <80154524@h30.sp.ipt.ru> On Tue, 5 May 2009 22:41:59 +0400 Chagin Dmitry wrote: > On Tue, May 05, 2009 at 08:41:01PM +0400, Boris Samorodov wrote: > > On Tue, 5 May 2009 20:07:24 +0400 Chagin Dmitry wrote: > > > On Tue, May 05, 2009 at 07:26:28PM +0400, Boris Samorodov wrote: > > > > > > May 5 19:10:34 bb kernel: bsam: linux_socket (LINUX): domain: 2, type: 2050, protocol: 0 > > > > May 5 19:10:34 bb kernel: bsam: linux_socket (FreeBSD): domain: 2 > > > > May 5 19:10:34 bb kernel: bsam: LINUX_SOCKET: 43 > > > > May 5 19:10:34 bb kernel: bsam: Entering linux_socketcall. > > > > May 5 19:10:34 bb kernel: bsam: linux_socket (LINUX): domain: 2, type: 2050, protocol: 0 > > > > May 5 19:10:34 bb kernel: bsam: linux_socket (FreeBSD): domain: 2 > > > > May 5 19:10:34 bb kernel: bsam: LINUX_SOCKET: 43 > > > > ----- > > > > > > > > Corresponding text for linux_kdump and truss: > > > > ftp://ftp.ipt.ru/pub/linux/linux_kdump.ping.txt > > > > ftp://ftp.ipt.ru/pub/linux/truss.ping.txt > > > > > > > > > heh, it seems to me that SOCK_CLOEXEC, SOCK_NONBLOCK bits used. > > > should be fixed. socketpair() also uses it since 2.6.29 > > > > I'll be glad to test patches. > dchagin# ./ping ya.ru > WARNING: setsockopt(ICMP_FILTER): Protocol not available > WARNING: your kernel is veeery old. No problems. > PING ya.ru (213.180.204.8) 56(84) bytes of data. > ping: recvmsg: Invalid argument > ping: recvmsg: Invalid argument > So, more work nedeed. At least from 2.6.16 to 2.6.23 :) If ya.ru is not listed at your /etc/hosts, that may be enough (for now). I got such result with localhost and it's FQDN, and programs (linux-seamonkey, etc.) work with them. Can you send me your patch(es)? WBR -- bsam From peterjeremy at optushome.com.au Tue May 5 20:01:16 2009 From: peterjeremy at optushome.com.au (Peter Jeremy) Date: Tue May 5 20:01:23 2009 Subject: Flash issues on -current/i386 In-Reply-To: <200905051524.56217.tijl@ulyssis.org> References: <20090505074827.GA93977@server.vk2pj.dyndns.org> <20090505145543.28393p52iyzgqu80@webmail.leidinger.net> <200905051524.56217.tijl@ulyssis.org> Message-ID: <20090505200109.GA13136@server.vk2pj.dyndns.org> On 2009-May-05 15:24:55 +0200, Tijl Coosemans wrote: >On Tuesday 05 May 2009 14:55:43 Alexander Leidinger wrote: >> Quoting Peter Jeremy (from Tue, 5 May >> 2009 17:48:27 +1000): >> >>> I then tried revering to flash9 (still with 2.6.16 and fc8). This >>> can successfully display video from both youtube and iview but has >>> no audio - it consistently reports the following: >>> ALSA lib confmisc.c:768:(parse_card) cannot find card '0' >>> ALSA lib conf.c:3510:(_snd_config_evaluate) function >> >> The flashsupport lib does not fit to your flash9. It is responsible >> to use OSS instead of ALSA. Look around on the emulation@ ML for >> places where you could try looking for it (if the ports doesn't >> provide it for your OS version). > >You can use libflashsupport from linux-f8-flashplugin10. Interestingly, that puts me back in the situation where youtube works with audio but iview won't load. (And whilst iview states that it needs flash10, I was successfully using it with Flash 7 or thereabouts under Linux). I obviously need to do a lot more investigation :-(. -- Peter Jeremy -------------- 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/20090505/157d6605/attachment.pgp From tijl at ulyssis.org Tue May 5 20:30:03 2009 From: tijl at ulyssis.org (Tijl Coosemans) Date: Tue May 5 20:30:13 2009 Subject: Flash issues on -current/i386 In-Reply-To: <20090505200109.GA13136@server.vk2pj.dyndns.org> References: <20090505074827.GA93977@server.vk2pj.dyndns.org> <200905051524.56217.tijl@ulyssis.org> <20090505200109.GA13136@server.vk2pj.dyndns.org> Message-ID: <200905052229.54159.tijl@ulyssis.org> On Tuesday 05 May 2009 22:01:09 Peter Jeremy wrote: > On 2009-May-05 15:24:55 +0200, Tijl Coosemans wrote: >> On Tuesday 05 May 2009 14:55:43 Alexander Leidinger wrote: >>> Quoting Peter Jeremy (from Tue, 5 May >>> 2009 17:48:27 +1000): >>>> I then tried revering to flash9 (still with 2.6.16 and fc8). This >>>> can successfully display video from both youtube and iview but has >>>> no audio - it consistently reports the following: >>>> ALSA lib confmisc.c:768:(parse_card) cannot find card '0' >>>> ALSA lib conf.c:3510:(_snd_config_evaluate) function >>> >>> The flashsupport lib does not fit to your flash9. It is responsible >>> to use OSS instead of ALSA. Look around on the emulation@ ML for >>> places where you could try looking for it (if the ports doesn't >>> provide it for your OS version). >> >> You can use libflashsupport from linux-f8-flashplugin10. > > Interestingly, that puts me back in the situation where youtube works > with audio but iview won't load. (And whilst iview states that it > needs flash10, I was successfully using it with Flash 7 or thereabouts > under Linux). I obviously need to do a lot more investigation :-(. Libflashsupport is open source, so if you want to play with it you can find all the relevant information in: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/127839 From yuri at rawbw.com Tue May 5 21:17:46 2009 From: yuri at rawbw.com (Yuri) Date: Tue May 5 21:17:52 2009 Subject: Skype got broken after the new linux ports infrastructure is introduced In-Reply-To: <12332424@bb.ipt.ru> References: <49FEBA7A.9030708@rawbw.com> <12332424@bb.ipt.ru> Message-ID: <4A00A914.2040803@rawbw.com> Boris Samorodov wrote: > > Can abybody comment on this? > I would add some info on this issue. Those relevant Linux ports installed besides skype: linux-alsa-lib-1.0.10.3_1 linux-atk-1.9.1_2 linux-cairo-1.0.2_1 linux-expat-1.95.8_1 linux-fontconfig-2.2.3_8 linux-gtk2-2.6.10_2 linux-hicolor-icon-theme-0.5_2 linux-jpeg-6b.34_1 linux-libsigc-2.0.17_1 linux-nvu-1.0_1 linux-pango-1.10.2_2 linux-png-1.2.8_3 linux-scim-gtk-fc4-1.4.4_1 linux-scim-libs-fc4-1.4.4_2 linux-tiff-3.7.1_1 linux-xorg-libs-6.8.2_6 linux_base-fc6-6_5 linux_dri-7.0 Also for some reason there is a potentially relevant line: OVERRIDE_LINUX_BASE_PORT=fc6 in /etc/make.conf. Yuri From yuri at rawbw.com Tue May 5 21:41:05 2009 From: yuri at rawbw.com (Yuri) Date: Tue May 5 21:41:11 2009 Subject: Skype got broken after the new linux ports infrastructure is introduced In-Reply-To: <4A00A914.2040803@rawbw.com> References: <49FEBA7A.9030708@rawbw.com> <12332424@bb.ipt.ru> <4A00A914.2040803@rawbw.com> Message-ID: <4A00B26F.1020709@rawbw.com> Now I reinstalled skype with the following lines in make.conf: OVERRIDE_LINUX_BASE_PORT=f8 OVERRIDE_LINUX_NONBASE_PORTS=f8 Skype has the same problem. Plus in addition Cyrillic characters don't show up in contact names. Linux packages installed now are: linux-f8-alsa-lib-1.0.15 linux-f8-expat-2.0.1 linux-f8-fontconfig-2.4.2 linux-f8-libsigc++20-2.0.18 linux-f8-xorg-libs-7.3_2 linux_base-f8-8_11 linux_dri-7.0 Should I file a PR for Cyrillic characters broken with f8? Yuri From killing at multiplay.co.uk Tue May 5 22:06:03 2009 From: killing at multiplay.co.uk (Steven Hartland) Date: Tue May 5 22:06:10 2009 Subject: [linux-f10] linux_socketcall... ERR#43 'Protocol not supported' References: <81924694@bb.ipt.ru><20090505144955.16373k1b32dpaxo0@webmail.leidinger.net> <47993241@bb.ipt.ru> Message-ID: Attached is some patches we use based off 7.0 which add a few additional Linux calls including sockets, so may help. Regards Steve ----- Original Message ----- From: "Boris Samorodov" >> instrument the current code to print out the parameters to >> linux_socketcall in a human readable way. > > Can you give a tiny example? ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. -------------- next part -------------- A non-text attachment was scrubbed... Name: syscalls.c.patch Type: application/octet-stream Size: 2736 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-emulation/attachments/20090505/6c7a2d90/syscalls.c.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: syscall.h.patch Type: application/octet-stream Size: 1621 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-emulation/attachments/20090505/6c7a2d90/syscall.h.obj From yuri at rawbw.com Tue May 5 22:35:30 2009 From: yuri at rawbw.com (Yuri) Date: Tue May 5 22:35:36 2009 Subject: Skype got broken after the new linux ports infrastructure is introduced In-Reply-To: <12332424@bb.ipt.ru> References: <49FEBA7A.9030708@rawbw.com> <12332424@bb.ipt.ru> Message-ID: <4A00BF30.30707@rawbw.com> I did more experimenting, checked out ports from Mar 15, before the new infrastructure is introduced on Mar 19, installed skype and all linux ports from this ports tree from Mar 15 and still see the problem. Now I suspect that kernel changes caused it. I think skype stopped working for me after I updated and recompiled kernel-7.2-PRERELEASE on Apr 25. Previous kernel-7.1-STABLE from Feb 25 worked fine. Do you know if any Linux-related changes were merged into 7.X branch between Feb 25 and Apr 25? Yuri From subbsd at gmail.com Wed May 6 14:17:40 2009 From: subbsd at gmail.com (subbsd) Date: Wed May 6 14:17:47 2009 Subject: Skype got broken after the new linux ports infrastructure is introduced In-Reply-To: <4A00B26F.1020709@rawbw.com> References: <49FEBA7A.9030708@rawbw.com> <4A00A914.2040803@rawbw.com> <4A00B26F.1020709@rawbw.com> Message-ID: <200905061755.24101.subbsd@gmail.com> On Wednesday 06 May 2009 01:41:03 Yuri wrote: > Now I reinstalled skype with the following lines in make.conf: > OVERRIDE_LINUX_BASE_PORT=f8 > OVERRIDE_LINUX_NONBASE_PORTS=f8 > > Skype has the same problem. > Plus in addition Cyrillic characters don't show up in contact names. > > Linux packages installed now are: > linux-f8-alsa-lib-1.0.15 > linux-f8-expat-2.0.1 > linux-f8-fontconfig-2.4.2 > linux-f8-libsigc++20-2.0.18 > linux-f8-xorg-libs-7.3_2 > linux_base-f8-8_11 > linux_dri-7.0 > > Should I file a PR for Cyrillic characters broken with f8? > I've get some problem after upgrading skype/linux-fc8 - blank square instead of cyrillic letters. Removing /compat/linux/root/.font.cache-\* and reinstall of linux-f8-fontconfig-2.4.2 helps for me. Also you can check pathdir in /compat/linux/etc/fonts/fonts.conf > Yuri > > _______________________________________________ > 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 bsam at ipt.ru Wed May 6 14:56:23 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Wed May 6 14:56:30 2009 Subject: got google earth running again, tho still with indirect rendering... In-Reply-To: <20090412201428.GA67309@triton.kn-bremen.de> (Juergen Lock's message of "Sun\, 12 Apr 2009 22\:14\:28 +0200") References: <20090412201428.GA67309@triton.kn-bremen.de> Message-ID: <46225595@bb.ipt.ru> On Sun, 12 Apr 2009 22:14:28 +0200 Juergen Lock wrote: > The following alias seems to work here now with OVERRIDE_LINUX_NONBASE_PORTS > set to f8 after the astro/google-earth USE_LINUX_APPS+= dri commit: > alias googleearth="LIBGL_ALWAYS_INDIRECT=1 cpuset -l 0 googleearth" > Without LIBGL_ALWAYS_INDIRECT if often crashes right at startup (and if > not, says it switches to indirect rendering by itself), and without > cpuset it often seems to hang/deadlock after popping up its tips window. > (The latter can only make a difference on smp of course.) > Tested on 7-stable/amd64 with intel 965 and ati RV730 PRO using video-ati > (the second one without any gl at all of course.) > I guess all we need now is linux dri bits matching our version of native > xorg and possibly some needed linuxolator changes? I have some progress here (CURRENT with some yet uncommitted patches): ----- bb% /compat/linux/usr/bin/glxinfo | grep render direct rendering: Yes OpenGL renderer string: Mesa DRI R300 20060815 x86/MMX/SSE2 TCL bb% /compat/linux/usr/bin/glxgears Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. 9037 frames in 5.0 seconds = 1807.302 FPS 9055 frames in 5.0 seconds = 1810.829 FPS 9041 frames in 5.0 seconds = 1808.094 FPS ^C bb% pkg_info -xI linux linux-dri74 Place a comment here linux-f10-alsa-lib-1.0.19 The Advanced Linux Sound Architecture libraries (Linux Fedo linux-f10-aspell-0.60.6 Spelling checker with better logic than ispell (Linux Fedor linux-f10-atk-1.24.0 Accessibility Toolkit, Linux/i386 binary (Linux Fedora 10) linux-f10-cairo-1.8.0 Vector graphics library Cairo (Linux Fedora 10) linux-f10-expat-2.0.1 Linux/i386 binary port of Expat XML-parsing library (Linux linux-f10-fontconfig-2.6.0 An XML-based font configuration API for X Windows (Linux Fe linux-f10-gtk2-2.14.7 GTK+ library, version 2.X (Linux Fedora 10) linux-f10-hicolor-icon-theme-0.5 A high-color icon theme shell from the FreeDesktop project linux-f10-iputils-20071127 PLEASE, place a comment here linux-f10-jpeg-6b RPM of the JPEG lib (Linux Fedora 10) linux-f10-libcap-2.10 PLEASE, place a comment here linux-f10-libidn-0.6.14 Internationalized Domain Name support library (Linux Fedora linux-f10-libsigc++20-2.2.2 Callback Framework for C++ (Linux Fedora 10) linux-f10-pango-1.22.3 The pango library (Linux Fedora 10) linux-f10-png-1.2.35 RPM of the PNG lib (Linux Fedora 10) linux-f10-tiff-3.8.2 The TIFF library, Linux/i386 binary (Linux Fedora 10) linux-f10-xorg-libs-7.4 Xorg libraries (Linux Fedora 10) linux-opera-9.64 A blazingly fast, full-featured, standards-compliant browse linux-seamonkey-1.1.16 The open source, standards compliant web browser linux-thunderbird-2.0.0.21 Mozilla Thunderbird is standalone mail and news that stands linux_base-f10-10 Base set of packages needed in Linux mode for i386/amd64 (L linux_kdump-1.5_2 Linux-compatability ktrace.out processor ----- linux-dri74 is a port with libraries and binaries for dri-7.4 from ubuntu-9.0.4. BTW, googleearth works like a charm even with cyrillic letters. But it crashes (only?) at exit: ----- bb% googleearth Google Earth has caught signal 11. Stacktrace from glibc: ./googleearth-bin [0x806c343] ./googleearth-bin [0x806c8b6] [0xbfbfffbb] ./libbase.so(_ZN5earth6System4joinEm+0x23) [0x351c8b93] ./libge_net.so(_ZN5earth3net18CurlHttpConnectionD2Ev+0x42) [0x3521d2e2] ./libge_net.so(_ZN5earth3net26CurlPasswordHttpConnectionD0Ev+0x2d) [0x3523b31d] ./libge_net.so(_ZN5earth3net20ConnectionRefCounterD0Ev+0x6e) [0x3521ecce] ./libge_net.so(_ZN5earth3net17ConnectionManager21ConnectionRequestPairD0Ev+0x7a) [0x3521b22a] ./libge_net.so(_ZNSt10_List_baseIN5earth6RefPtrINS0_3net17ConnectionManager21ConnectionRequestPairEEESaIS5_EE8_M_clearEv+0x118) [0x3523abd8] ./libge_net.so(_ZN5earth3net17ConnectionManagerD0Ev+0xf4) [0x3521e1e4] ./libge_net.so(_ZN5earth3net7Fetcher8shutdownEv+0x1fa) [0x35220a9a] ./libge_net.so(_ZN5earth3net8shutdownEv+0x1c) [0x35220f7c] ./libgoogleearth_lib.so(_ZN5earth6client11ApplicationD1Ev+0x244) [0x34f583e4] ./googleearth-bin(main+0x290) [0x806cdf0] /lib/libc.so.6(__libc_start_main+0xe5) [0x34fc36e5] ./googleearth-bin [0x806bad1] ----- 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 Wed May 6 17:06:49 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Wed May 6 17:06:55 2009 Subject: [call for testers] linux DRI 7.4 port (graphics/linux-dri74) Message-ID: <92627768@bb.ipt.ru> Hello List, I'd like to ask you to test a port I've created. This port is intended to replace graphics/linux_dri port (DRI 7.0) and linux-f8-dri port (DRO 7.0.2). Only compat.linux.osrelease 2.6.16 may be used. I think that it may be used at FreeBSD-7.2 (no idea about earlier 7.x versions). DRI drivers, libraries and binaries (glxinfo and glxgears) were taken from Ubuntu-9.0.4. The port lacks libglut and libglide3 libraries (I didn't find them for Ubuntu-9.0.4). Here it is: ftp://ftp.ipt.ru/pub/linux/linux-dri74.shar Get this shar file, and run it at /usr/ports: % (cd /usr/ports && sudo sh ) Then you should replace your existing linux dri port with this one. The port was tested at 8-current with linux-f8 and linux-f10 (not yet at official ports tree) and recent xorg. Here are the results: ----- bb% /compat/linux/usr/bin/glxinfo| grep render direct rendering: Yes OpenGL renderer string: Mesa DRI R300 20060815 x86/MMX/SSE2 TCL bb% /compat/linux/usr/bin/glxgears 9041 frames in 5.0 seconds = 1808.115 FPS 9056 frames in 5.0 seconds = 1811.171 FPS 9053 frames in 5.0 seconds = 1810.543 FPS ^C ----- Googleearth works for me but crashes at exitting. Please, test this port and give a feedback. WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From linimon at FreeBSD.org Fri May 8 03:45:40 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Fri May 8 03:45:52 2009 Subject: kern/134276: [linux][patch] MSG_NOSIGNAL not translated for recv(), socket timeout incorrect for 64-bit hosts Message-ID: <200905080345.n483jeYI089634@freefall.freebsd.org> Synopsis: [linux][patch] MSG_NOSIGNAL not translated for recv(), socket timeout incorrect for 64-bit hosts Responsible-Changed-From-To: freebsd-bugs->freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Fri May 8 03:45:32 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=134276 From bsam at ipt.ru Fri May 8 12:42:52 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Fri May 8 12:42:59 2009 Subject: [new port] graphics/linux-dri74 Message-ID: <92596693@bb.ipt.ru> Hello List, I've just committed a new port graphics/linux-dri74. This port is intended to replace graphics/linux_dri and graphics/linux-f8-dri. The new port introduces linux DRI-7.4 drivers, libraries and binaries. One may use portupgrade/portmaster to switch to the new port: ----- # portupgrade -o graphics/linux-dri74 linux_dri ----- The port may be used with at least FreeBSD-7.2 and setting compat.linux.osrelease=2.6.16. Tested with recent xorg and drm. Use linux glxinfo to detect if direct rendering is enabled: ----- % /compat/linux/usr/bin/glxinfo| grep render direct rendering: Yes OpenGL renderer string: Mesa DRI R300 20060815 x86/MMX/SSE2 TCL ----- For those who like gears there is a linux binary: ----- % /compat/linux/usr/bin/glxgears Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. 9050 frames in 5.0 seconds = 1809.925 FPS 9060 frames in 5.0 seconds = 1811.917 FPS 9060 frames in 5.0 seconds = 1811.966 FPS ^C ----- Enjoy. WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From zeiztm at gmail.com Fri May 8 17:37:53 2009 From: zeiztm at gmail.com (Greg Wang) Date: Fri May 8 17:37:59 2009 Subject: FreeBSD Port: www/linux-f8-flashplugin10 Message-ID: I'm sorry for perhaps stupid question but how to install linux-f8-flashplugin10 on FreeBSD 7.2-RELEASE if it's known that the port marked as "Ignore" and the following message appears: linux-flashplugin-10.0r22 bsd.linux-apps.mk test failed: The component nss is not defined for LINUX_DIST_SUFFIX= (the corresponding variable nss_FILE is not defined). *** Error code 1 Regards, Walter. From linimon at FreeBSD.org Fri May 8 17:55:56 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Fri May 8 17:56:10 2009 Subject: ports/134359: Missing version of libxml2 in Mk/bsd.linux-apps.mk Message-ID: <200905081755.n48HttTU049469@freefall.freebsd.org> Old Synopsis: Missing version of libxml2 in bsd.linux-apps.mk New Synopsis: Missing version of libxml2 in Mk/bsd.linux-apps.mk Responsible-Changed-From-To: freebsd-ports-bugs->freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Fri May 8 17:55:07 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=134359 From bsam at FreeBSD.org Fri May 8 19:29:50 2009 From: bsam at FreeBSD.org (bsam@FreeBSD.org) Date: Fri May 8 19:29:55 2009 Subject: ports/134359: Missing version of libxml2 in Mk/bsd.linux-apps.mk Message-ID: <200905081929.n48JTnQg070070@freefall.freebsd.org> Synopsis: Missing version of libxml2 in Mk/bsd.linux-apps.mk State-Changed-From-To: open->closed State-Changed-By: bsam State-Changed-When: Fri May 8 19:29:39 UTC 2009 State-Changed-Why: Committed, thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=134359 From dfilter at FreeBSD.ORG Fri May 8 19:30:06 2009 From: dfilter at FreeBSD.ORG (dfilter service) Date: Fri May 8 19:30:21 2009 Subject: ports/134359: commit references a PR Message-ID: <200905081930.n48JU5aU070470@freefall.freebsd.org> The following reply was made to PR ports/134359; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: ports/134359: commit references a PR Date: Fri, 8 May 2009 19:29:12 +0000 (UTC) bsam 2009-05-08 19:29:03 UTC FreeBSD ports repository Modified files: Mk bsd.linux-apps.mk Log: Fix libxml library version. PR: ports/134359 Submitted by: Hidemi Yamashita Revision Changes Path 1.17 +2 -2 ports/Mk/bsd.linux-apps.mk _______________________________________________ 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 ipt.ru Fri May 8 19:37:33 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Fri May 8 19:37:41 2009 Subject: FreeBSD Port: www/linux-f8-flashplugin10 In-Reply-To: (Greg Wang's message of "Fri\, 8 May 2009 13\:17\:35 -0400") References: Message-ID: <37230453@h30.sp.ipt.ru> On Fri, 8 May 2009 13:17:35 -0400 Greg Wang wrote: > I'm sorry for perhaps stupid question but how to install > linux-f8-flashplugin10 on FreeBSD 7.2-RELEASE if it's known that the port > marked as "Ignore" and the following message appears: > linux-flashplugin-10.0r22 bsd.linux-apps.mk test failed: The component nss > is not defined for LINUX_DIST_SUFFIX= (the corresponding variable nss_FILE > is not defined). > *** Error code 1 This port needs a new linuxulator (linux kernel 2.6.x) which is default only at 8-CURRENT. You need to set the sysctl compat.linux.osrelease-2.6.16 and define at /etc/make.conf: ----- OVERRIDE_LINUX_BASE_PORT=f8 OVERRIDE_LINUX_NONBASE_PORTS=f8 ----- Note: If you have already installed any linux fc4 port you may need to upgrade to linux f8 ports. For more information look at /usr/ports/UPDATING and recent archieves of this mail list. WBR -- bsam From dchagin at freebsd.org Fri May 8 20:20:03 2009 From: dchagin at freebsd.org (Chagin Dmitry) Date: Fri May 8 20:20:10 2009 Subject: kern/134276: [linux][patch] MSG_NOSIGNAL not translated for recv(), socket timeout incorrect for 64-bit hosts Message-ID: <200905082020.n48KK3Vn037607@freefall.freebsd.org> The following reply was made to PR kern/134276; it has been noted by GNATS. From: Chagin Dmitry To: Thomas Mueller Cc: freebsd-gnats-submit@freebsd.org Subject: Re: kern/134276: [linux][patch] MSG_NOSIGNAL not translated for recv(), socket timeout incorrect for 64-bit hosts Date: Sat, 9 May 2009 00:10:03 +0400 --dDRMvlgZJXvWKvBx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 06, 2009 at 04:57:50PM +0000, Thomas Mueller wrote: >=20 > >Number: 134276 > >Category: kern > >Synopsis: [linux][patch] MSG_NOSIGNAL not translated for recv(), s= ocket timeout incorrect for 64-bit hosts > >Confidential: no > >Severity: non-critical > >Priority: low > >Responsible: freebsd-bugs > >State: open > >Quarter: =20 > >Keywords: =20 > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Wed May 06 17:00:07 UTC 2009 > >Closed-Date: > >Last-Modified: > >Originator: Thomas Mueller > >Release: 7.2-STABLE > >Organization: > >Environment: > FreeBSD tom.ulm.sysgo.com 7.2-STABLE FreeBSD 7.2-STABLE #16: Mon May 4 1= 5:12:43 CEST 2009 toor@tom.ulm.sysgo.com:/usr/obj/usr/src/sys/TOM amd64 > >Description: > I've encountered two socket related problems with the Linux emulation: >=20 > 1. A Linux application passing the MSG_NOSIGNAL flag in calls to=20 > recv() or recvfrom() will still receive a SIGPIPE if the condition > for sending the signal is met. >=20 > 2. An attempt to set socket timeouts with a call to setsocktopt() using t= he=20 > SO_RECVTIMEO or SO_SNDTIMEO option will fail with [EINVAL] on amd64. >=20 What the Linux application you have mentioned? I should know it to test patches. Thank you. --=20 Have fun! chd --dDRMvlgZJXvWKvBx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkoEkZoACgkQ0t2Tb3OO/O05SwCfaVw+4LflVkXIDk9CIM4I32Fh 7bMAnRg/VWcAMRQGEnTD9L+W6RuJkf4Q =md+G -----END PGP SIGNATURE----- --dDRMvlgZJXvWKvBx-- From tmueller at sysgo.com Sat May 9 07:00:05 2009 From: tmueller at sysgo.com (Thomas Mueller) Date: Sat May 9 07:00:11 2009 Subject: kern/134276: [linux][patch] MSG_NOSIGNAL not translated for recv(), socket timeout incorrect for 64-bit hosts Message-ID: <200905090700.n49704gb019256@freefall.freebsd.org> The following reply was made to PR kern/134276; it has been noted by GNATS. From: Thomas Mueller To: Chagin Dmitry Cc: freebsd-gnats-submit@freebsd.org Subject: Re: kern/134276: [linux][patch] MSG_NOSIGNAL not translated for recv(), socket timeout incorrect for 64-bit hosts Date: Sat, 9 May 2009 08:30:53 +0200 On Sat, 9 May 2009 00:10:03 +0400, Chagin Dmitry wrote: > On Wed, May 06, 2009 at 04:57:50PM +0000, Thomas Mueller wrote: > > > > >Number: 134276 > > >Category: kern > > >Synopsis: [linux][patch] MSG_NOSIGNAL not translated for recv(), socket timeout incorrect for 64-bit hosts > > >Confidential: no > > >Severity: non-critical > > >Priority: low > > >Responsible: freebsd-bugs > > >State: open > > >Quarter: > > >Keywords: > > >Date-Required: > > >Class: sw-bug > > >Submitter-Id: current-users > > >Arrival-Date: Wed May 06 17:00:07 UTC 2009 > > >Closed-Date: > > >Last-Modified: > > >Originator: Thomas Mueller > > >Release: 7.2-STABLE > > >Organization: > > >Environment: > > FreeBSD tom.ulm.sysgo.com 7.2-STABLE FreeBSD 7.2-STABLE #16: Mon May 4 15:12:43 CEST 2009 toor@tom.ulm.sysgo.com:/usr/obj/usr/src/sys/TOM amd64 > > >Description: > > I've encountered two socket related problems with the Linux emulation: > > > > 1. A Linux application passing the MSG_NOSIGNAL flag in calls to > > recv() or recvfrom() will still receive a SIGPIPE if the condition > > for sending the signal is met. > > > > 2. An attempt to set socket timeouts with a call to setsocktopt() using the > > SO_RECVTIMEO or SO_SNDTIMEO option will fail with [EINVAL] on amd64. > > > > What the Linux application you have mentioned? > I should know it to test patches. Thank you. Sorry for not mentioning it in the PR. The applications are part of the LM-X License Manager package by X-Formation (http://www.x-formation.com/). It looks like they offer a trial download but require registration. When back in the office (next weeek), I could revert my local changes and provide you with an output of linux_kdump if that helps. I would also test patches. -- Thomas Mueller From dchagin at freebsd.org Sat May 9 08:06:13 2009 From: dchagin at freebsd.org (Chagin Dmitry) Date: Sat May 9 08:06:20 2009 Subject: kern/134276: [linux][patch] MSG_NOSIGNAL not translated for recv(), socket timeout incorrect for 64-bit hosts In-Reply-To: <200905090700.n49704gb019256@freefall.freebsd.org> References: <200905090700.n49704gb019256@freefall.freebsd.org> Message-ID: <20090509080609.GA4415@dchagin.static.corbina.ru> On Sat, May 09, 2009 at 07:00:04AM +0000, Thomas Mueller wrote: > The following reply was made to PR kern/134276; it has been noted by GNATS. > > From: Thomas Mueller > To: Chagin Dmitry > Cc: freebsd-gnats-submit@freebsd.org > Subject: Re: kern/134276: [linux][patch] MSG_NOSIGNAL not translated for > recv(), socket timeout incorrect for 64-bit hosts > Date: Sat, 9 May 2009 08:30:53 +0200 > > > > I've encountered two socket related problems with the Linux emulation: > > > > > > 1. A Linux application passing the MSG_NOSIGNAL flag in calls to > > > recv() or recvfrom() will still receive a SIGPIPE if the condition > > > for sending the signal is met. > > > > > > 2. An attempt to set socket timeouts with a call to setsocktopt() using the > > > SO_RECVTIMEO or SO_SNDTIMEO option will fail with [EINVAL] on amd64. > > > > > > > What the Linux application you have mentioned? > > I should know it to test patches. Thank you. > > Sorry for not mentioning it in the PR. The applications are part of the > LM-X License Manager package by X-Formation (http://www.x-formation.com/). > It looks like they offer a trial download but require registration. > > When back in the office (next weeek), I could revert my local changes > and provide you with an output of linux_kdump if that helps. I would > also test patches. > > Thank you, Please, apply this two patches. http://people.freebsd.org/~dchagin/patches/commit-4952ce8.patch http://people.freebsd.org/~dchagin/patches/commit-6355ebf.patch -- Have fun! chd -------------- 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/20090509/6e0b099b/attachment.pgp From jamie at bishopston.net Sat May 9 17:39:49 2009 From: jamie at bishopston.net (Jamie Landeg Jones) Date: Sat May 9 17:39:55 2009 Subject: wine, mixer pcm volume reset to 0:0 Message-ID: <200905091717.n49HHj5C000398@catflap.bishopston.net> Not a fix, but a workaround on FreeBSD, that doesn't require you to switch to emulated sound 1) Create a new group "nomixer" by editting /etc/group e.g. nomixer:*:2000: 2) Add the following 2 lines to /etc/devfs.conf: own mixer root:nomixer perm mixer 0606 3) Modify the wine binary as such: chgrp nomixer /usr/local/bin/wine chmod g+s /usr/local/bin/wine This basically means that wine doesn't have access to /dev/mixer so can't alter anything. You as a user still retain access, and also, any wine apps that have a volume control STILL work, because that volume is not changed using /dev/mixer From lists at yamagi.org Sun May 10 18:19:27 2009 From: lists at yamagi.org (Yamagi Burmeister) Date: Sun May 10 18:20:52 2009 Subject: [new port] graphics/linux-dri74 In-Reply-To: <92596693@bb.ipt.ru> References: <92596693@bb.ipt.ru> Message-ID: <20090510174445.GA75441@yamagi.org> Skipped content of type multipart/mixed-------------- 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/20090510/8854a053/attachment.pgp From ikostov at otel.net Sun May 10 20:48:33 2009 From: ikostov at otel.net (Iasen Kostov) Date: Sun May 10 20:48:40 2009 Subject: linux-f8-fontconfig 2.4.2 Message-ID: <1241986744.59329.6.camel@WaRHeaD.otel.net> Hi, when I use linux-f8-fontconfig + linux-f8-expat I can't see the Cyrillic letters in skype, changing those ports to linux-fontconfig + linux-expat everything is working fine. I haven't had time to investigate because I needed skype fast and I hope that somebody more experienced in linux things already have the answer :). (please include me in CC because I'm not in emulation list, thanks). Regards. From dchagin at freebsd.org Mon May 11 07:36:33 2009 From: dchagin at freebsd.org (Chagin Dmitry) Date: Mon May 11 07:36:40 2009 Subject: kern/134276: [linux][patch] MSG_NOSIGNAL not translated for recv(), socket timeout incorrect for 64-bit hosts In-Reply-To: <20090511092045.4e18692c@tom.ulm.sysgo.com> References: <200905090700.n49704gb019256@freefall.freebsd.org> <20090509080609.GA4415@dchagin.static.corbina.ru> <20090511092045.4e18692c@tom.ulm.sysgo.com> Message-ID: <20090511073625.GA49560@dchagin.static.corbina.ru> On Mon, May 11, 2009 at 09:20:45AM +0200, Thomas Mueller wrote: > On Sat, 9 May 2009 12:06:09 +0400, Chagin Dmitry wrote: > > On Sat, May 09, 2009 at 07:00:04AM +0000, Thomas Mueller wrote: > > > The following reply was made to PR kern/134276; it has been noted by GNATS. > > > > > > From: Thomas Mueller > > > To: Chagin Dmitry > > > Cc: freebsd-gnats-submit@freebsd.org > > > Subject: Re: kern/134276: [linux][patch] MSG_NOSIGNAL not translated for > > > recv(), socket timeout incorrect for 64-bit hosts > > > Date: Sat, 9 May 2009 08:30:53 +0200 > > > > > > > > I've encountered two socket related problems with the Linux emulation: > > > > > > > > > > 1. A Linux application passing the MSG_NOSIGNAL flag in calls to > > > > > recv() or recvfrom() will still receive a SIGPIPE if the condition > > > > > for sending the signal is met. > > > > > > > > > > 2. An attempt to set socket timeouts with a call to setsocktopt() using the > > > > > SO_RECVTIMEO or SO_SNDTIMEO option will fail with [EINVAL] on amd64. > > > > > > > > > > > > > What the Linux application you have mentioned? > > > > I should know it to test patches. Thank you. > > > > > > Sorry for not mentioning it in the PR. The applications are part of the > > > LM-X License Manager package by X-Formation (http://www.x-formation.com/). > > > It looks like they offer a trial download but require registration. > > > > > > When back in the office (next weeek), I could revert my local changes > > > and provide you with an output of linux_kdump if that helps. I would > > > also test patches. > > > > > > > > > > Thank you, > > > > Please, apply this two patches. > > > > http://people.freebsd.org/~dchagin/patches/commit-4952ce8.patch > > In linux_setsockopt() when calling kern_setsockopt() for > SO_RCVTIMEO/SO_SNDTIMEO you need to pass 'name' instead of > 'bsd_args.name' since the latter is still undefined at that point: > > --- commit-4952ce8.patch.orig 2009-05-11 09:07:56.000000000 +0200 > +++ commit-4952ce8.patch 2009-05-11 09:08:09.000000000 +0200 > @@ -39,7 +39,7 @@ > + tv.tv_sec = linux_tv.tv_sec; > + tv.tv_usec = linux_tv.tv_usec; > + return (kern_setsockopt(td, bsd_args.s, bsd_args.level, > -+ bsd_args.name, &tv, UIO_SYSSPACE, sizeof(tv))); > ++ name, &tv, UIO_SYSSPACE, sizeof(tv))); > + break; > + default: > + break; > > > http://people.freebsd.org/~dchagin/patches/commit-6355ebf.patch > > Good catch, thank you! -- Have fun! chd -------------- 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/20090511/32bf0a48/attachment.pgp From tmueller at sysgo.com Mon May 11 07:52:57 2009 From: tmueller at sysgo.com (Thomas Mueller) Date: Mon May 11 07:53:13 2009 Subject: kern/134276: [linux][patch] MSG_NOSIGNAL not translated for recv(), socket timeout incorrect for 64-bit hosts In-Reply-To: <20090509080609.GA4415@dchagin.static.corbina.ru> References: <200905090700.n49704gb019256@freefall.freebsd.org> <20090509080609.GA4415@dchagin.static.corbina.ru> Message-ID: <20090511092045.4e18692c@tom.ulm.sysgo.com> On Sat, 9 May 2009 12:06:09 +0400, Chagin Dmitry wrote: > On Sat, May 09, 2009 at 07:00:04AM +0000, Thomas Mueller wrote: > > The following reply was made to PR kern/134276; it has been noted by GNATS. > > > > From: Thomas Mueller > > To: Chagin Dmitry > > Cc: freebsd-gnats-submit@freebsd.org > > Subject: Re: kern/134276: [linux][patch] MSG_NOSIGNAL not translated for > > recv(), socket timeout incorrect for 64-bit hosts > > Date: Sat, 9 May 2009 08:30:53 +0200 > > > > > > I've encountered two socket related problems with the Linux emulation: > > > > > > > > 1. A Linux application passing the MSG_NOSIGNAL flag in calls to > > > > recv() or recvfrom() will still receive a SIGPIPE if the condition > > > > for sending the signal is met. > > > > > > > > 2. An attempt to set socket timeouts with a call to setsocktopt() using the > > > > SO_RECVTIMEO or SO_SNDTIMEO option will fail with [EINVAL] on amd64. > > > > > > > > > > What the Linux application you have mentioned? > > > I should know it to test patches. Thank you. > > > > Sorry for not mentioning it in the PR. The applications are part of the > > LM-X License Manager package by X-Formation (http://www.x-formation.com/). > > It looks like they offer a trial download but require registration. > > > > When back in the office (next weeek), I could revert my local changes > > and provide you with an output of linux_kdump if that helps. I would > > also test patches. > > > > > > Thank you, > > Please, apply this two patches. > > http://people.freebsd.org/~dchagin/patches/commit-4952ce8.patch In linux_setsockopt() when calling kern_setsockopt() for SO_RCVTIMEO/SO_SNDTIMEO you need to pass 'name' instead of 'bsd_args.name' since the latter is still undefined at that point: --- commit-4952ce8.patch.orig 2009-05-11 09:07:56.000000000 +0200 +++ commit-4952ce8.patch 2009-05-11 09:08:09.000000000 +0200 @@ -39,7 +39,7 @@ + tv.tv_sec = linux_tv.tv_sec; + tv.tv_usec = linux_tv.tv_usec; + return (kern_setsockopt(td, bsd_args.s, bsd_args.level, -+ bsd_args.name, &tv, UIO_SYSSPACE, sizeof(tv))); ++ name, &tv, UIO_SYSSPACE, sizeof(tv))); + break; + default: + break; > http://people.freebsd.org/~dchagin/patches/commit-6355ebf.patch -- Thomas Mueller From tmueller at sysgo.com Mon May 11 08:32:38 2009 From: tmueller at sysgo.com (Thomas Mueller) Date: Mon May 11 08:32:45 2009 Subject: kern/134276: [linux][patch] MSG_NOSIGNAL not translated for recv(), socket timeout incorrect for 64-bit hosts In-Reply-To: <20090511092045.4e18692c@tom.ulm.sysgo.com> References: <200905090700.n49704gb019256@freefall.freebsd.org> <20090509080609.GA4415@dchagin.static.corbina.ru> <20090511092045.4e18692c@tom.ulm.sysgo.com> Message-ID: <20090511103103.24c32802@tom.ulm.sysgo.com> On Mon, 11 May 2009 09:20:45 +0200, Thomas Mueller wrote: > On Sat, 9 May 2009 12:06:09 +0400, Chagin Dmitry wrote: > > > > Please, apply this two patches. > > > > http://people.freebsd.org/~dchagin/patches/commit-4952ce8.patch > > In linux_setsockopt() when calling kern_setsockopt() for > SO_RCVTIMEO/SO_SNDTIMEO you need to pass 'name' instead of > 'bsd_args.name' since the latter is still undefined at that point: > > --- commit-4952ce8.patch.orig 2009-05-11 09:07:56.000000000 +0200 > +++ commit-4952ce8.patch 2009-05-11 09:08:09.000000000 +0200 > @@ -39,7 +39,7 @@ > + tv.tv_sec = linux_tv.tv_sec; > + tv.tv_usec = linux_tv.tv_usec; > + return (kern_setsockopt(td, bsd_args.s, bsd_args.level, > -+ bsd_args.name, &tv, UIO_SYSSPACE, sizeof(tv))); > ++ name, &tv, UIO_SYSSPACE, sizeof(tv))); > + break; > + default: > + break; > > > http://people.freebsd.org/~dchagin/patches/commit-6355ebf.patch With the above shown modification I was able to successfully run the LM-X License Manager on 7.2-STABLE with both amd64 and i386. -- Thomas Mueller From bugmaster at FreeBSD.org Mon May 11 11:06:53 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon May 11 11:07:45 2009 Subject: Current problem reports assigned to freebsd-emulation@FreeBSD.org Message-ID: <200905111106.n4BB6qQt085915@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/134276 emulation [linux][patch] MSG_NOSIGNAL not translated for recv(), 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 ports/121800 emulation x11-toolkits/linux-openmotif - OpenMotif upgrade to 2. o kern/97326 emulation [linux] file descriptor leakage in linux emulation o ports/91318 emulation graphics/linux_dri: works on amd64 too o kern/91293 emulation [svr4] [patch] *Experimental* Update to the SVR4 emula 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 17 problems total. From dfilter at FreeBSD.ORG Mon May 11 13:50:03 2009 From: dfilter at FreeBSD.ORG (dfilter service) Date: Mon May 11 13:50:08 2009 Subject: kern/134276: commit references a PR Message-ID: <200905111350.n4BDo20k010158@freefall.freebsd.org> The following reply was made to PR kern/134276; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/134276: commit references a PR Date: Mon, 11 May 2009 13:42:55 +0000 (UTC) Author: dchagin Date: Mon May 11 13:42:40 2009 New Revision: 191988 URL: http://svn.freebsd.org/changeset/base/191988 Log: Add forgotten linux to bsd flags argument mapping into the linux_recv(). PR: kern/134276 Submitted by: Thomas Mueller Approved by: kib (mentor) MFC after: 2 weeks Modified: head/sys/compat/linux/linux_socket.c Modified: head/sys/compat/linux/linux_socket.c ============================================================================== --- head/sys/compat/linux/linux_socket.c Mon May 11 07:57:29 2009 (r191987) +++ head/sys/compat/linux/linux_socket.c Mon May 11 13:42:40 2009 (r191988) @@ -924,7 +924,7 @@ linux_recv(struct thread *td, struct lin bsd_args.s = args->s; bsd_args.buf = (caddr_t)PTRIN(args->msg); bsd_args.len = args->len; - bsd_args.flags = args->flags; + bsd_args.flags = linux_to_bsd_msg_flags(args->flags); bsd_args.from = NULL; bsd_args.fromlenaddr = 0; return (recvfrom(td, &bsd_args)); _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From dfilter at FreeBSD.ORG Mon May 11 14:00:10 2009 From: dfilter at FreeBSD.ORG (dfilter service) Date: Mon May 11 14:00:16 2009 Subject: kern/134276: commit references a PR Message-ID: <200905111400.n4BE09Av023043@freefall.freebsd.org> The following reply was made to PR kern/134276; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/134276: commit references a PR Date: Mon, 11 May 2009 13:50:53 +0000 (UTC) Author: dchagin Date: Mon May 11 13:50:42 2009 New Revision: 191989 URL: http://svn.freebsd.org/changeset/base/191989 Log: Translate l_timeval arg to native struct timeval in linux_setsockopt()/linux_getsockopt() for SO_RCVTIMEO, SO_SNDTIMEO opts as l_timeval has MD members. Remove bogus __packed attribute from l_timeval struct on __amd64__. PR: kern/134276 Submitted by: Thomas Mueller Approved by: kib (mentor) MFC after: 2 weeks Modified: head/sys/amd64/linux32/linux.h head/sys/compat/linux/linux_socket.c Modified: head/sys/amd64/linux32/linux.h ============================================================================== --- head/sys/amd64/linux32/linux.h Mon May 11 13:42:40 2009 (r191988) +++ head/sys/amd64/linux32/linux.h Mon May 11 13:50:42 2009 (r191989) @@ -96,7 +96,7 @@ typedef struct { typedef struct { l_time_t tv_sec; l_suseconds_t tv_usec; -} __packed l_timeval; +} l_timeval; #define l_fd_set fd_set Modified: head/sys/compat/linux/linux_socket.c ============================================================================== --- head/sys/compat/linux/linux_socket.c Mon May 11 13:42:40 2009 (r191988) +++ head/sys/compat/linux/linux_socket.c Mon May 11 13:50:42 2009 (r191989) @@ -1278,6 +1278,8 @@ linux_setsockopt(struct thread *td, stru caddr_t val; int valsize; } */ bsd_args; + l_timeval linux_tv; + struct timeval tv; int error, name; bsd_args.s = args->s; @@ -1285,6 +1287,23 @@ linux_setsockopt(struct thread *td, stru switch (bsd_args.level) { case SOL_SOCKET: name = linux_to_bsd_so_sockopt(args->optname); + switch (name) { + case SO_RCVTIMEO: + /* FALLTHROUGH */ + case SO_SNDTIMEO: + error = copyin(PTRIN(args->optval), &linux_tv, + sizeof(linux_tv)); + if (error) + return (error); + tv.tv_sec = linux_tv.tv_sec; + tv.tv_usec = linux_tv.tv_usec; + return (kern_setsockopt(td, args->s, bsd_args.level, + name, &tv, UIO_SYSSPACE, sizeof(tv))); + /* NOTREACHED */ + break; + default: + break; + } break; case IPPROTO_IP: name = linux_to_bsd_ip_sockopt(args->optname); @@ -1333,6 +1352,9 @@ linux_getsockopt(struct thread *td, stru caddr_t val; int *avalsize; } */ bsd_args; + l_timeval linux_tv; + struct timeval tv; + socklen_t tv_len; int error, name; bsd_args.s = args->s; @@ -1340,6 +1362,24 @@ linux_getsockopt(struct thread *td, stru switch (bsd_args.level) { case SOL_SOCKET: name = linux_to_bsd_so_sockopt(args->optname); + switch (name) { + case SO_RCVTIMEO: + /* FALLTHROUGH */ + case SO_SNDTIMEO: + tv_len = sizeof(tv); + error = kern_getsockopt(td, args->s, bsd_args.level, + name, &tv, UIO_SYSSPACE, &tv_len); + if (error) + return (error); + linux_tv.tv_sec = tv.tv_sec; + linux_tv.tv_usec = tv.tv_usec; + return (copyout(&linux_tv, PTRIN(args->optval), + sizeof(linux_tv))); + /* NOTREACHED */ + break; + default: + break; + } break; case IPPROTO_IP: name = linux_to_bsd_ip_sockopt(args->optname); _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From delphij at FreeBSD.org Mon May 11 14:37:58 2009 From: delphij at FreeBSD.org (delphij@FreeBSD.org) Date: Mon May 11 14:38:04 2009 Subject: kern/134276: [linux][patch] MSG_NOSIGNAL not translated for recv(), socket timeout incorrect for 64-bit hosts Message-ID: <200905111437.n4BEbvrQ077400@freefall.freebsd.org> Synopsis: [linux][patch] MSG_NOSIGNAL not translated for recv(), socket timeout incorrect for 64-bit hosts State-Changed-From-To: open->patched State-Changed-By: delphij State-Changed-When: Mon May 11 14:36:19 UTC 2009 State-Changed-Why: dchagin@ has committed a fix as revision 191988 so bump this to 'patched' state as MFC reminder. Responsible-Changed-From-To: freebsd-emulation->dchagin Responsible-Changed-By: delphij Responsible-Changed-When: Mon May 11 14:36:19 UTC 2009 Responsible-Changed-Why: Over to dchagin@. http://www.freebsd.org/cgi/query-pr.cgi?pr=134276 From bsam at ipt.ru Tue May 12 10:01:29 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Tue May 12 10:01:35 2009 Subject: Skype got broken after the new linux ports infrastructure is introduced In-Reply-To: <200905061755.24101.subbsd@gmail.com> (subbsd@gmail.com's message of "Wed\, 6 May 2009 17\:55\:23 +0400") References: <49FEBA7A.9030708@rawbw.com> <4A00A914.2040803@rawbw.com> <4A00B26F.1020709@rawbw.com> <200905061755.24101.subbsd@gmail.com> Message-ID: <10464886@bb.ipt.ru> On Wed, 6 May 2009 17:55:23 +0400 subbsd wrote: > On Wednesday 06 May 2009 01:41:03 Yuri wrote: > > Now I reinstalled skype with the following lines in make.conf: > > OVERRIDE_LINUX_BASE_PORT=f8 > > OVERRIDE_LINUX_NONBASE_PORTS=f8 > > > > Skype has the same problem. > > Plus in addition Cyrillic characters don't show up in contact names. > > > > Linux packages installed now are: > > linux-f8-alsa-lib-1.0.15 > > linux-f8-expat-2.0.1 > > linux-f8-fontconfig-2.4.2 > > linux-f8-libsigc++20-2.0.18 > > linux-f8-xorg-libs-7.3_2 > > linux_base-f8-8_11 > > linux_dri-7.0 > > > > Should I file a PR for Cyrillic characters broken with f8? > I've get some problem after upgrading skype/linux-fc8 - blank square instead > of cyrillic letters. Removing /compat/linux/root/.font.cache-\* and reinstall How did it happen that you have got /compat/linux/root directory? It should not exist. You may have got other problems with it. > of linux-f8-fontconfig-2.4.2 helps for me. > Also you can check pathdir in /compat/linux/etc/fonts/fonts.conf 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 Tue May 12 12:22:35 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Tue May 12 12:22:42 2009 Subject: [linux] fontconfig and it's cache files Message-ID: <69348750@bb.ipt.ru> Hello List, I've managed to run skype using cyrillic letters with -f8- infrastructure ports only after running a linux fc-cache. It creats its own /compat/linux/var/cache files (but uses FreeBSD font files from /usr/local/lib/X11/fonts). Hence we face an incompatible fontconfig files from different fontconfig versions. Only linux -f10- fontconfig is compatible with current FreeBSD fontconfig (2.6.0). It seems to me that the best way to go is to populate $LINUXBASE/var/cache when installing linux fontconfig and remove it when deinstalling. As for -f10- linux ports we may use a native fontconfig cache files until new version starts to be incompatible. What do you think? 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 FreeBSD.org Tue May 12 13:41:33 2009 From: bsam at FreeBSD.org (bsam@FreeBSD.org) Date: Tue May 12 13:41:39 2009 Subject: ports/121800: x11-toolkits/linux-openmotif - OpenMotif upgrade to 2.3.0? Message-ID: <200905121341.n4CDfVdB093010@freefall.freebsd.org> Synopsis: x11-toolkits/linux-openmotif - OpenMotif upgrade to 2.3.0? State-Changed-From-To: open->closed State-Changed-By: bsam State-Changed-When: Tue May 12 13:39:33 UTC 2009 State-Changed-Why: The port x11-toolkits/linux-f8-openmotif was updated to version 2.3.2 (there is no new version for x11-toolkits/linux-openmotif). Thanks for the heads up! http://www.freebsd.org/cgi/query-pr.cgi?pr=121800 From cracauer at cons.org Tue May 12 14:39:22 2009 From: cracauer at cons.org (Martin Cracauer) Date: Tue May 12 14:39:29 2009 Subject: Linux Firefox on FreeBSD-7.2-STABLE Message-ID: <20090512142659.GA88793@cons.org> I might miss something here, but I find myself knocked out of firefoxes on FreeBSD-7.2 now. Firefox-2.x had an autoupdate and since then requires gtk-2.10. My F8 linux_base only has 2.6. I then moved over the whole 32 chroot I use on Linux (Debian-stable i386) using Firefox-3.5b4. This one isn't stable on FreeBSD-7.2. It hangs on a regular basis which I tend to blame on some threading/concurrency problem (probability of hang is obviously related to amount of concurrent activity). I backed out all emulation kernel changes I have but no change. Starting Firefox-2.x inside the chroot results in a straight segfault. What are people using these days? I would much prefer to keep using a Linux/i386 Firefox since I have one up-to-date tree that I rsync between all Linux and FreeBSD machines. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ From Alexander at Leidinger.net Wed May 13 06:48:45 2009 From: Alexander at Leidinger.net (Alexander Leidinger) Date: Wed May 13 06:48:53 2009 Subject: [linux] fontconfig and it's cache files In-Reply-To: <69348750@bb.ipt.ru> References: <69348750@bb.ipt.ru> Message-ID: <20090513084832.14297i6jsuyofcg8@webmail.leidinger.net> Quoting Boris Samorodov (from Tue, 12 May 2009 16:22:25 +0400): > It seems to me that the best way to go is to populate > $LINUXBASE/var/cache when installing linux fontconfig > and remove it when deinstalling. As for -f10- linux > ports we may use a native fontconfig cache files until > new version starts to be incompatible. > > What do you think? Running the linux fc-config is not a clean solution, because it will not be re-run when a new font is installed. Unfortunately I have no better idea... at least for F10 we would have the good behavior. In the light of the upcomming 8.0 release, I would say go ahead with this idea. I don't know if we should extend the fc-cache running in the font ports to also run the linux one if present or not. This is maybe something to discuss after 8.0-RELEASE is out the door. Bye, Alexander. -- Kiss a non-smoker; taste the difference. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From bsam at ipt.ru Wed May 13 07:22:34 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Wed May 13 07:22:40 2009 Subject: [linux] fontconfig and it's cache files In-Reply-To: <20090513084832.14297i6jsuyofcg8@webmail.leidinger.net> (Alexander Leidinger's message of "Wed\, 13 May 2009 08\:48\:32 +0200") References: <69348750@bb.ipt.ru> <20090513084832.14297i6jsuyofcg8@webmail.leidinger.net> Message-ID: <37172311@bb.ipt.ru> On Wed, 13 May 2009 08:48:32 +0200 Alexander Leidinger wrote: > Quoting Boris Samorodov (from Tue, 12 May 2009 16:22:25 +0400): > > It seems to me that the best way to go is to populate > > $LINUXBASE/var/cache when installing linux fontconfig > > and remove it when deinstalling. As for -f10- linux > > ports we may use a native fontconfig cache files until > > new version starts to be incompatible. > > > > What do you think? > Running the linux fc-config is not a clean solution, because it will > not be re-run when a new font is installed. Yea, hence the question. > Unfortunately I have no better idea... Would it be good to create a default fc-cache files and install them with a port/package? We may add more fc-cache files upon users requests. > at least for F10 we would have the good behavior. In > the light of the upcomming 8.0 release, I would say go ahead with this > idea. This will work until the fonts cache database structure changes... And what about users of 7.x which use F8 linux ports and won't be able to use F10 ports? > I don't know if we should extend the fc-cache running in the font > ports to also run the linux one if present or not. This is maybe > something to discuss after 8.0-RELEASE is out the door. Well, me too don't have an elegant solution. :-( WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From Alexander at Leidinger.net Wed May 13 11:32:25 2009 From: Alexander at Leidinger.net (Alexander Leidinger) Date: Wed May 13 11:32:34 2009 Subject: [linux] fontconfig and it's cache files In-Reply-To: <37172311@bb.ipt.ru> References: <69348750@bb.ipt.ru> <20090513084832.14297i6jsuyofcg8@webmail.leidinger.net> <37172311@bb.ipt.ru> Message-ID: <20090513133213.197930aa10bc4fk0@webmail.leidinger.net> Quoting Boris Samorodov (from Wed, 13 May 2009 11:22:32 +0400): > On Wed, 13 May 2009 08:48:32 +0200 Alexander Leidinger wrote: >> Quoting Boris Samorodov (from Tue, 12 May 2009 >> 16:22:25 +0400): > >> > It seems to me that the best way to go is to populate >> > $LINUXBASE/var/cache when installing linux fontconfig >> > and remove it when deinstalling. As for -f10- linux >> > ports we may use a native fontconfig cache files until >> > new version starts to be incompatible. >> > >> > What do you think? > >> Running the linux fc-config is not a clean solution, because it will >> not be re-run when a new font is installed. > > Yea, hence the question. > >> Unfortunately I have no better idea... > > Would it be good to create a default fc-cache files and install > them with a port/package? We may add more fc-cache files upon > users requests. Isn't there only one cache file? It depends upon which fonts are installed. On one machine I have fonts which you will not find in ports (or for free at all, I think... they are very old and I got them in a commercial package). I don't think this is an option. >> at least for F10 we would have the good behavior. In >> the light of the upcomming 8.0 release, I would say go ahead with this >> idea. > > This will work until the fonts cache database structure changes... Yes. > And what about users of 7.x which use F8 linux ports and won't be > able to use F10 ports? Did you test f10 on 7.x? I would say f8+ is not supported on 7.1 or less, for 7.2 I don't know the current status. Fallback: run fc-cache manually (we can not support everything, f4 until 7.x is EOL and f10 for 8.x is already a lot). >> I don't know if we should extend the fc-cache running in the font >> ports to also run the linux one if present or not. This is maybe >> something to discuss after 8.0-RELEASE is out the door. > > Well, me too don't have an elegant solution. :-( This would at least be a working solution, and not counting the amount of work involved it is also the right solution. I think this is something for after 8.0. Bye, Alexander. -- Uh-oh -- WHY am I suddenly thinking of a VENERABLE religious leader frolicking on a FORT LAUDERDALE weekend? http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From bsam at ipt.ru Wed May 13 12:30:58 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Wed May 13 12:31:06 2009 Subject: [linux] fontconfig and it's cache files In-Reply-To: <20090513133213.197930aa10bc4fk0@webmail.leidinger.net> (Alexander Leidinger's message of "Wed\, 13 May 2009 13\:32\:13 +0200") References: <69348750@bb.ipt.ru> <20090513084832.14297i6jsuyofcg8@webmail.leidinger.net> <37172311@bb.ipt.ru> <20090513133213.197930aa10bc4fk0@webmail.leidinger.net> Message-ID: <35414879@bb.ipt.ru> On Wed, 13 May 2009 13:32:13 +0200 Alexander Leidinger wrote: > Quoting Boris Samorodov (from Wed, 13 May 2009 11:22:32 +0400): > > On Wed, 13 May 2009 08:48:32 +0200 Alexander Leidinger wrote: > >> Quoting Boris Samorodov (from Tue, 12 May 2009 > >> 16:22:25 +0400): > > > >> > It seems to me that the best way to go is to populate > >> > $LINUXBASE/var/cache when installing linux fontconfig > >> > and remove it when deinstalling. As for -f10- linux > >> > ports we may use a native fontconfig cache files until > >> > new version starts to be incompatible. > >> > > >> > What do you think? > > > >> Running the linux fc-config is not a clean solution, because it will > >> not be re-run when a new font is installed. > > > > Yea, hence the question. > > > >> Unfortunately I have no better idea... > > > > Would it be good to create a default fc-cache files and install > > them with a port/package? We may add more fc-cache files upon > > users requests. > Isn't there only one cache file? It depends upon which fonts are > installed. On one machine I have fonts which you will not find in > ports (or for free at all, I think... they are very old and I got them > in a commercial package). I don't think this is an option. OK. > >> at least for F10 we would have the good behavior. In > >> the light of the upcomming 8.0 release, I would say go ahead with this > >> idea. > > > > This will work until the fonts cache database structure changes... > Yes. > > And what about users of 7.x which use F8 linux ports and won't be > > able to use F10 ports? > Did you test f10 on 7.x? I would say f8+ is not supported on 7.1 or > less, for 7.2 I don't know the current status. Fallback: run fc-cache > manually (we can not support everything, f4 until 7.x is EOL and f10 > for 8.x is already a lot). Resolving doesn't work at CURRENT for now. The needed patches are at reviewing for now and soon should be committed. And then we'll see if they may be MFCed. > >> I don't know if we should extend the fc-cache running in the font > >> ports to also run the linux one if present or not. This is maybe > >> something to discuss after 8.0-RELEASE is out the door. > > > > Well, me too don't have an elegant solution. :-( > This would at least be a working solution, and not counting the amount > of work involved it is also the right solution. I think this is > something for after 8.0. Agreed. 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 bsam at ipt.ru Wed May 13 13:34:19 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Wed May 13 13:34:26 2009 Subject: [new port] graphics/linux-dri74 In-Reply-To: <20090510174445.GA75441@yamagi.org> (Yamagi Burmeister's message of "Sun\, 10 May 2009 19\:44\:46 +0200") References: <92596693@bb.ipt.ru> <20090510174445.GA75441@yamagi.org> Message-ID: <67576966@bb.ipt.ru> On Sun, 10 May 2009 19:44:46 +0200 Yamagi Burmeister wrote: > I saw your new linux-dri74 port just a couple of hours ago and gave it a > try. I've got a ATi Radeon X1950 Pro, running with xf86-video-ati in > version 6.12.2_1 under FreeBSD/amd64 in version 7.2. With nativ FreeBSD > applications like ioQuake3, Blender oder BZFlag direct rendering is > working fine. Don't see anything obvious, sorry. Anybody else? Did you try to use xf86-video-radeonhd? WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From peispud at eastlink.ca Wed May 13 23:32:56 2009 From: peispud at eastlink.ca (brian) Date: Wed May 13 23:33:02 2009 Subject: Wine crashing with steam on PC-BSD 7.1 - crash output Message-ID: <4A0B518D.6050906@eastlink.ca> For wine ; [brian at pcbsd ]/home/brian(101)% winecfg Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". For Steam ; Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". fixme:process:SetProcessShutdownParameters (00000100, 00000000): partial stub. fixme:urlmon:CoInternetSetFeatureEnabled 5, 0x00000002, 1, stub fixme:urlmon:CoInternetSetFeatureEnabled 10, 0x00000002, 1, stub err:dscapture:widDsCreate DirectSoundCapture flag not set This sound card's driver does not support direct access The (slower) DirectSound HEL mode will be used instead. fixme:dbghelp:EnumerateLoadedModulesW64 If this happens, bump the number in mod err:ntdll:RtlpWaitForCriticalSection section 0x91715c "?" wait timed out in thread 001e, blocked by 001f, retrying (60 sec) Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". From cracauer at cons.org Thu May 14 00:49:04 2009 From: cracauer at cons.org (Martin Cracauer) Date: Thu May 14 00:49:11 2009 Subject: Linux Firefox on FreeBSD-7.2-STABLE In-Reply-To: <20090512142659.GA88793@cons.org> References: <20090512142659.GA88793@cons.org> Message-ID: <20090514004902.GA79160@cons.org> So, I am not as doomed as I thought, but the situation isn't good. Martin Cracauer wrote on Tue, May 12, 2009 at 10:26:59AM -0400: > I might miss something here, but I find myself knocked out of > firefoxes on FreeBSD-7.2 now. > > Firefox-2.x had an autoupdate and since then requires gtk-2.10. My F8 > linux_base only has 2.6. What happened here is that the autoupdate brought me away from a firefox-2.x to a Firefox-3.x. After downgrading to the latest 2.x I can now run again, with linux_base-f8. That's far from optimal but better than nothing. > I then moved over the whole 32 chroot I use on Linux (Debian-stable > i386) using Firefox-3.5b4. This one isn't stable on FreeBSD-7.2. It > hangs on a regular basis which I tend to blame on some > threading/concurrency problem (probability of hang is obviously > related to amount of concurrent activity). I backed out all emulation > kernel changes I have but no change. No progress on this. As far as I can tell, the Linuxulator in 7.2-stable is not up to running Firefox-3.5b, and it seems to be from threading problems (hangs, no segfault), which are hard to debug. I should probably try a different Linux base than I have in this chroot (to shake versions of the glibc thread libs a bit). But since f8 won't do it I have to move someplace else here. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ From nox at jelal.kn-bremen.de Thu May 14 16:54:13 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Thu May 14 16:54:20 2009 Subject: Linux Firefox on FreeBSD-7.2-STABLE In-Reply-To: <20090514004902.GA79160@cons.org> References: <20090512142659.GA88793@cons.org> Message-ID: <200905141652.n4EGq8dT015834@triton.kn-bremen.de> In article <20090514004902.GA79160@cons.org> you write: >So, I am not as doomed as I thought, but the situation isn't good. > >Martin Cracauer wrote on Tue, May 12, 2009 at 10:26:59AM -0400: >> I might miss something here, but I find myself knocked out of >> firefoxes on FreeBSD-7.2 now. >> >> Firefox-2.x had an autoupdate and since then requires gtk-2.10. My F8 >> linux_base only has 2.6. > >What happened here is that the autoupdate brought me away from a >firefox-2.x to a Firefox-3.x. After downgrading to the latest 2.x I >can now run again, with linux_base-f8. That's far from optimal but >better than nothing. > >> I then moved over the whole 32 chroot I use on Linux (Debian-stable >> i386) using Firefox-3.5b4. This one isn't stable on FreeBSD-7.2. It >> hangs on a regular basis which I tend to blame on some >> threading/concurrency problem (probability of hang is obviously >> related to amount of concurrent activity). I backed out all emulation >> kernel changes I have but no change. > >No progress on this. As far as I can tell, the Linuxulator in >7.2-stable is not up to running Firefox-3.5b, and it seems to be >from threading problems (hangs, no segfault), which are hard to >debug. > That sounds familiar... I had hangs (deadlocks?) with googleearth too, which (as reported in another thread) I was able to work around by forcing it onto a single cpu. So maybe something like this works for you too: cpuset -l 0 linux-firefox... (Of course this can only make a difference on smp, and also cpuset(1) is only available/working if you use ule.) >I should probably try a different Linux base than I have in this >chroot (to shake versions of the glibc thread libs a bit). But since >f8 won't do it I have to move someplace else here. HTH, Juergen From miwi at FreeBSD.org Thu May 14 19:31:06 2009 From: miwi at FreeBSD.org (Martin Wilke) Date: Thu May 14 19:31:21 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! Message-ID: <20090514191237.GD70242@bsdcrew.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Howdy Guys, After the announcement from Alexander Eichner about Virtualbox on FreeBSD, we started the work on a port for FreeBSD. Now we think that we solved the most problems and are ready for the first Call for Testing. Some notes before you can test the port: Make sure you are using RELENG_7 or higher. You have to use a fresh portstree with uptodate ports!! Please read carefully the pkg-messages. Some known issues / Troubleshooting: Sometimes the kernel on HEAD coredumps when loading or unloading the kernel module. A small workaround to prevent the crash is to not start X, mount proc, then load the kernel module and start X from the console. That helped me and some testers, maybe you too. :P AMD64 should be work in general, it builds and start. But not right tested at the moment. We want here also some feedback. Some Thanks: First of all we'd like to say many thanks to _ALL_ vbox developers. Next people are Bernhard Froehlich (aka decke), Beat Gaetzi (beat@), Dennis Herrmann (dhn@), Pietro Cerutti (gahr@), myself (*gg*), and _ALL_ who helped and provided feedback. Happy Testing :-) Download: http://people.freebsd.org/~miwi/vbox/vboxport.tgz Wiki Page: http://wiki.freebsd.org/VirtualBox - Martin - -- +-----------------------+-------------------------------+ | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | | ICQ : 169139903 | Mail : miwi(at)FreeBSD.org | +-----------------------+-------------------------------+ | Mess with the Best, Die like the Rest! | +-----------------------+-------------------------------+ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAkoMbSUACgkQdLJIhLHm/OnNnACeJsT7H9hW1J7CV70P3Ty+q0CA kD8AoMLCPbltY999/8qO6fnaqv4UQ9QT =LcoD -----END PGP SIGNATURE----- From fbsdlist at src.cx Thu May 14 21:46:20 2009 From: fbsdlist at src.cx (Artem Belevich) Date: Thu May 14 21:46:32 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: <20090514191237.GD70242@bsdcrew.de> References: <20090514191237.GD70242@bsdcrew.de> Message-ID: I'm trying to build on CURRENT/amd64 kBuild binaries that come with the port are for FreeBSD-6.3 and seem to depend on KSE and would at the very minimum need /etc/libmap.conf tweaking in order to get them to work. Perhaps it would be better to make port depend on kBuild and just do ln -s /usr/local/bin work/virtualbox-2.2.2r19673/kBuild/bin/freebsd.amd64 with kBuild installed from ports vbox did finish building. --Artem From fbsdlist at src.cx Thu May 14 21:51:34 2009 From: fbsdlist at src.cx (Artem Belevich) Date: Thu May 14 21:51:47 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: References: <20090514191237.GD70242@bsdcrew.de> Message-ID: Few more notes from -CURRENT/amd64 * VirtualBox needs /proc mounted, otherwise it fails to start. * Kernel module must be loaded with "kldload vboxdrv" In my case, I de see bunch of relocation errors on the console, though the module does load: kldload: unexpected relocation type 10 kldload: unexpected relocation type 10 kldload: unexpected relocation type 10 kldload: unexpected relocation type 10 kldload: unexpected relocation type 10 kldload: unexpected relocation type 10 kldload: unexpected relocation type 10 kldload: unexpected relocation type 10 kldload: unexpected relocation type 10 kldload: unexpected relocation type 10 kldload: unexpected relocation type 10 kldload: unexpected relocation type 10 vboxdrv: fAsync=0 offMin=0xb25 offMax=0x39a8 * Attempt to boot new VM (64-bit FreeBSD) from -current snapshot DVD ISO results in an error: Failed to start the virtual machine FreeBSD. Failed to load VMMR0.r0 (VERR_SYMBOL_VALUE_TOO_BIG). Unknown error creating VM (VERR_SYMBOL_VALUE_TOO_BIG). Result Code: NS_ERROR_FAILURE (0x80004005) Component: Console Interface: IConsole {a7f17a42-5b64-488d-977b-4b2c639ada27} * Subsequent attempts to start VM result in an error message that kernel module is not present, even though kldstat shows it just fine. Any suggestions on how to make it work? --Artem On Thu, May 14, 2009 at 2:18 PM, Artem Belevich wrote: > I'm trying to build on CURRENT/amd64 > > kBuild binaries that come with the port are for FreeBSD-6.3 and seem > to depend on KSE and would at the very minimum need /etc/libmap.conf > tweaking in order to get them to work. > > Perhaps it would be better to make port depend on kBuild and just do > ln -s /usr/local/bin work/virtualbox-2.2.2r19673/kBuild/bin/freebsd.amd64 > > with kBuild installed from ports vbox did finish building. > > --Artem > From miwi at FreeBSD.org Thu May 14 21:55:15 2009 From: miwi at FreeBSD.org (Martin Wilke) Date: Thu May 14 21:55:38 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: References: <20090514191237.GD70242@bsdcrew.de> Message-ID: <20090514215508.GA71804@bsdcrew.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, May 14, 2009 at 02:18:41PM -0700, Artem Belevich wrote: > I'm trying to build on CURRENT/amd64 > > kBuild binaries that come with the port are for FreeBSD-6.3 and seem > to depend on KSE and would at the very minimum need /etc/libmap.conf > tweaking in order to get them to work. > > Perhaps it would be better to make port depend on kBuild and just do > ln -s /usr/local/bin work/virtualbox-2.2.2r19673/kBuild/bin/freebsd.amd64 > > with kBuild installed from ports vbox did finish building. You should try to install misc/compat6. - - Martin > > --Artem > - -- +-----------------------+-------------------------------+ | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | | ICQ : 169139903 | Mail : miwi(at)FreeBSD.org | +-----------------------+-------------------------------+ | Mess with the Best, Die like the Rest! | +-----------------------+-------------------------------+ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAkoMkzwACgkQdLJIhLHm/Ol8SwCfT28kzMwirCcWTs3XzREdXliu YL8AoLoHckZchjsmSDyI8ubOsCtCs+L9 =qeL/ -----END PGP SIGNATURE----- From miwi at FreeBSD.org Thu May 14 21:56:52 2009 From: miwi at FreeBSD.org (Martin Wilke) Date: Thu May 14 21:56:59 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: References: <20090514191237.GD70242@bsdcrew.de> Message-ID: <20090514215644.GB71804@bsdcrew.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, May 14, 2009 at 02:51:32PM -0700, Artem Belevich wrote: > Few more notes from -CURRENT/amd64 > > * VirtualBox needs /proc mounted, otherwise it fails to start. > * Kernel module must be loaded with "kldload vboxdrv" > - From my mail: Some notes before you can test the port: Make sure you are using RELENG_7 or higher. You have to use a fresh portstree with uptodate ports!! Please read carefully the pkg-messages. > In my case, I de see bunch of relocation errors on the console, > though the module does load: > > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > vboxdrv: fAsync=0 offMin=0xb25 offMax=0x39a8 > > * Attempt to boot new VM (64-bit FreeBSD) from -current snapshot DVD > ISO results in an error: > > Failed to start the virtual machine FreeBSD. > Failed to load VMMR0.r0 (VERR_SYMBOL_VALUE_TOO_BIG). > Unknown error creating VM (VERR_SYMBOL_VALUE_TOO_BIG). > > Result Code: NS_ERROR_FAILURE (0x80004005) > Component: Console > Interface: IConsole {a7f17a42-5b64-488d-977b-4b2c639ada27} > > * Subsequent attempts to start VM result in an error message that > kernel module is not present, even though kldstat shows it just fine. > Maybe is here the problem you link to devel/kbuild. > > Any suggestions on how to make it work? > > --Artem > > > > On Thu, May 14, 2009 at 2:18 PM, Artem Belevich wrote: > > I'm trying to build on CURRENT/amd64 > > > > kBuild binaries that come with the port are for FreeBSD-6.3 and seem > > to depend on KSE and would at the very minimum need /etc/libmap.conf > > tweaking in order to get them to work. > > > > Perhaps it would be better to make port depend on kBuild and just do > > ln -s /usr/local/bin work/virtualbox-2.2.2r19673/kBuild/bin/freebsd.amd64 > > > > with kBuild installed from ports vbox did finish building. > > > > --Artem > > > - -- +-----------------------+-------------------------------+ | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | | ICQ : 169139903 | Mail : miwi(at)FreeBSD.org | +-----------------------+-------------------------------+ | Mess with the Best, Die like the Rest! | +-----------------------+-------------------------------+ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAkoMk5wACgkQdLJIhLHm/OlV9wCfU77KyC2CDb6bOeG6vDwEQsx8 pHAAoJCwlO5d+iYVdy7ZT/tTwkKSmjq3 =HcYf -----END PGP SIGNATURE----- From sergey.dyatko at gmail.com Thu May 14 22:03:25 2009 From: sergey.dyatko at gmail.com (Sergey V. Dyatko) Date: Thu May 14 22:03:38 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: <20090514191237.GD70242@bsdcrew.de> References: <20090514191237.GD70242@bsdcrew.de> Message-ID: <20090515003202.57d3f2e2@notebook> On Thu, 14 May 2009 21:12:37 +0200 Martin Wilke wrote: MW> -----BEGIN PGP SIGNED MESSAGE----- MW> Hash: SHA1 MW> MW> MW> Howdy Guys, MW> MW> After the announcement from Alexander Eichner about MW> Virtualbox on FreeBSD, we started the work on a port MW> for FreeBSD. Now we think that we solved the most MW> problems and are ready for the first Call for Testing. MW> MW> Some notes before you can test the port: MW> Make sure you are using RELENG_7 or higher. You have MW> to use a fresh portstree with uptodate ports!! Please MW> read carefully the pkg-messages. MW> MW> Some known issues / Troubleshooting: MW> Sometimes the kernel on HEAD coredumps when loading MW> or unloading the kernel module. A small workaround MW> to prevent the crash is to not start X, mount proc, MW> then load the kernel module and start X from the MW> console. That helped me and some testers, maybe you MW> too. :P AMD64 should be work in general, it builds MW> and start. But not right tested at the moment. We MW> want here also some feedback. I can't start a virtual machine (current from May, 9). screenshot: http://msk.bsd.by/vbox.png After kldunload vboxdrv I got kernel panic:( MW> MW> Some Thanks: MW> First of all we'd like to say many thanks to _ALL_ MW> vbox developers. Next people are Bernhard Froehlich MW> (aka decke), Beat Gaetzi (beat@), Dennis Herrmann MW> (dhn@), Pietro Cerutti (gahr@), myself (*gg*), MW> and _ALL_ who helped and provided feedback. I would like to join thanks, thank you for good job MW> Happy Testing :-) MW> MW> Download: MW> MW> http://people.freebsd.org/~miwi/vbox/vboxport.tgz MW> MW> Wiki Page: MW> http://wiki.freebsd.org/VirtualBox MW> MW> - Martin -- wbr, tiger From Benoit.Calvez at gmail.com Thu May 14 22:19:47 2009 From: Benoit.Calvez at gmail.com (Benoit Calvez) Date: Thu May 14 22:20:04 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: <20090514191237.GD70242@bsdcrew.de> References: <20090514191237.GD70242@bsdcrew.de> Message-ID: <3481d8e60905141449qfcf5da8r95d54281206304a4@mail.gmail.com> On Thu, May 14, 2009 at 9:12 PM, Martin Wilke wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Howdy Guys, > > After the announcement from Alexander Eichner about > Virtualbox on FreeBSD, we started the work on a port > for FreeBSD. Now we think that we solved the most > problems and are ready for the first Call for Testing. > > Some notes before you can test the port: > Make sure you are using RELENG_7 or higher. You have > to use a fresh portstree with uptodate ports!! Please > read carefully the pkg-messages. > > Some known issues / Troubleshooting: > Sometimes the kernel on HEAD coredumps when loading > or unloading the kernel module. A small workaround > to prevent the crash is to not start X, mount proc, > then load the kernel module and start X from the > console. That helped me and some testers, maybe you > too. :P AMD64 should be work in general, it builds > and start. But not right tested at the moment. We > want here also some feedback. > > Some Thanks: > First of all we'd like to say many thanks to _ALL_ > vbox developers. Next people are Bernhard Froehlich > (aka decke), Beat Gaetzi (beat@), Dennis Herrmann > (dhn@), Pietro Cerutti (gahr@), myself (*gg*), > and _ALL_ who helped and provided feedback. > > Happy Testing :-) > > Download: > > http://people.freebsd.org/~miwi/vbox/vboxport.tgz > > Wiki Page: > http://wiki.freebsd.org/VirtualBox > > - Martin > > - -- > > +-----------------------+-------------------------------+ > | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | > | ICQ : 169139903 | Mail : miwi(at)FreeBSD.org | > +-----------------------+-------------------------------+ > | Mess with the Best, Die like the Rest! | > +-----------------------+-------------------------------+ > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.11 (FreeBSD) > > iEYEARECAAYFAkoMbSUACgkQdLJIhLHm/OnNnACeJsT7H9hW1J7CV70P3Ty+q0CA > kD8AoMLCPbltY999/8qO6fnaqv4UQ9QT > =LcoD > -----END PGP SIGNATURE----- > _______________________________________________ > 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" > I'm trying to build from amd64, but got the following error. Sorry but I didn't look, and it's a fresh paste: ===> Configuring for virtualbox-2.2.2r19673 Checking for environment: Determined build machine: freebsd.amd64, target machine: freebsd.amd64, OK. Checking for kBuild: found, OK. Checking for gcc: found version 4.2.1, OK. Checking for as86: found version 0.16.17, OK. Checking for bcc: found version 0.16.17, OK. Checking for iasl: found version 20070320, OK. Checking for xslt: found, OK. Checking for pthread: found, OK. Checking for libxml2: found version 2.7.3, OK. Checking for libxslt: found version 1.1.24, OK. Checking for libIDL: found version 0.8.13, OK. Checking for zlib: found version 1.2.3, OK. Checking for SDL: found version 1.2.13, OK. Checking for X libraries: found, OK. Checking for Xcursor: found, OK. Checking for Xmu: found, OK. Checking for Mesa / GLU: Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". found version 1.2, OK. Checking for Qt4: found version 4.4.3, OK. Checking for Qt4 devtools: found version 4.4.3, OK. Checking for python support: found version 2.5.4, OK. Successfully generated '/usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/AutoConfig.kmk' and '/usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/env.sh'. Source '/usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/env.sh' once before you start to build VBox: source /usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/env.sh kmk +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ Hardening is enabled which means that the VBox binaries will not run from the binary directory. The binaries have to be installed suid root and some more prerequisites have to be fulfilled which is normally done by installing the final package. For development, the hardening feature can be disabled by specifying the --disable-hardening parameter. Please never disable that feature for the final distribution! +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ Enjoy! ===> Building for virtualbox-2.2.2r19673 cd /usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673 && /bin/sh env.sh && VBOX_LIBPATH_X11=/usr/local /usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/kBuild/bin/freebsd.amd64/kmk Config.kmk:1664: /usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/GCCConfig.kmk: No such file or directory Config.kmk:3789: /usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/revision.kmk: No such file or directory Fatal error 'kse_create() failed ' at line 469 in file /usr/src/lib/libpthread/thread/thr_kern.c (errno = 2) *** Error code 1 -- Benoit C. From fbsdlist at src.cx Thu May 14 23:03:34 2009 From: fbsdlist at src.cx (Artem Belevich) Date: Thu May 14 23:03:46 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: <20090514215644.GB71804@bsdcrew.de> References: <20090514191237.GD70242@bsdcrew.de> <20090514215644.GB71804@bsdcrew.de> Message-ID: >> * VirtualBox needs /proc mounted, otherwise it fails to start. >> * Kernel module must be loaded with "kldload vboxdrv" > > - From my mail: > Some notes before you can test the port: > Make sure you are using RELENG_7 or higher. You have > to use a fresh portstree with uptodate ports!! Please > read carefully the pkg-messages. Oops. Indeed it warns about /proc and kernel module. I guess I just was too eager to get VirtualBox running to pause and read documentation. > Maybe is here the problem you link to devel/kbuild. As I explained, kbuild that comes with the port does not work for me. And I *do* have compat6-amd64 installed. Apparently I'm not alone. See Benoit's email in this thread. Here's what needs to be added to /etc/libmap.conf in order to make supplied libraries work: libpthread.so.2 libthr.so.2 I'll re-do the build with supplied kbuild and see if that makes any difference. In any case, I appreciate all the work you and others have done to get VirtualBox on FreeBSD running. --Artem From fbsdlist at src.cx Fri May 15 00:54:19 2009 From: fbsdlist at src.cx (Artem Belevich) Date: Fri May 15 00:54:31 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: References: <20090514191237.GD70242@bsdcrew.de> <20090514215644.GB71804@bsdcrew.de> Message-ID: > Here's what needs to be added to /etc/libmap.conf in order to make > supplied libraries work: > libpthread.so.2 libthr.so.2 > > I'll re-do the build with supplied kbuild and see if that makes any difference. Re-built virtualbox with kBiuild supplied in the tarball and behavior didn't change compared to the one built with kBuild from ports. Loading module still shows relocation errors "kldload: unexpected relocation type 10" and attempt to run VM fails with the same errors I've reported before. --Artem From peterjeremy at optushome.com.au Fri May 15 05:45:54 2009 From: peterjeremy at optushome.com.au (Peter Jeremy) Date: Fri May 15 05:46:01 2009 Subject: Flash issues on -current/i386 In-Reply-To: <20090505200109.GA13136@server.vk2pj.dyndns.org> References: <20090505074827.GA93977@server.vk2pj.dyndns.org> <20090505145543.28393p52iyzgqu80@webmail.leidinger.net> <200905051524.56217.tijl@ulyssis.org> <20090505200109.GA13136@server.vk2pj.dyndns.org> Message-ID: <20090515054549.GA62536@server.vk2pj.dyndns.org> On 2009-May-06 06:01:09 +1000, Peter Jeremy wrote: >On 2009-May-05 15:24:55 +0200, Tijl Coosemans wrote: >>You can use libflashsupport from linux-f8-flashplugin10. > >Interestingly, that puts me back in the situation where youtube works >with audio but iview won't load. (And whilst iview states that it >needs flash10, I was successfully using it with Flash 7 or thereabouts >under Linux). I obviously need to do a lot more investigation :-(. For the archives: I think a slightly newer kernel fixed it - flash is now working (though npviewer.bin processes have a tendency to coredump or not get killed automatically by firefox). -- Peter Jeremy -------------- 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/20090515/a2fd26d7/attachment.pgp From decke at bluelife.at Fri May 15 08:02:15 2009 From: decke at bluelife.at (Bernhard =?iso-8859-1?Q?Fr=F6hlich?=) Date: Fri May 15 08:02:22 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: References: <20090514191237.GD70242@bsdcrew.de> Message-ID: <7bf637b3a059269ba098a8f79dc4d758.squirrel@webmail.itac.at> On Thu, May 14, 2009 11:51 pm, Artem Belevich wrote: > Few more notes from -CURRENT/amd64 > > [snip] > > * Attempt to boot new VM (64-bit FreeBSD) from -current snapshot DVD > ISO results in an error: > > Failed to start the virtual machine FreeBSD. > Failed to load VMMR0.r0 (VERR_SYMBOL_VALUE_TOO_BIG). > Unknown error creating VM (VERR_SYMBOL_VALUE_TOO_BIG). > > Result Code: NS_ERROR_FAILURE (0x80004005) > Component: Console > Interface: IConsole {a7f17a42-5b64-488d-977b-4b2c639ada27} That is an amd64 problem and it is already being worked on. Sorry no solution yet. -- Bernhard Fr?hlich http://www.bluelife.at/ From decke at bluelife.at Fri May 15 09:53:43 2009 From: decke at bluelife.at (Bernhard =?iso-8859-1?Q?Fr=F6hlich?=) Date: Fri May 15 09:53:51 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: References: <20090514191237.GD70242@bsdcrew.de> Message-ID: <06c77d8650448aa63d9ce8d4b1a9c3e0.squirrel@webmail.itac.at> On Thu, May 14, 2009 11:51 pm, Artem Belevich wrote: > Few more notes from -CURRENT/amd64 > > [snip] > > * Attempt to boot new VM (64-bit FreeBSD) from -current snapshot DVD > ISO results in an error: > > Failed to start the virtual machine FreeBSD. > Failed to load VMMR0.r0 (VERR_SYMBOL_VALUE_TOO_BIG). > Unknown error creating VM (VERR_SYMBOL_VALUE_TOO_BIG). > > Result Code: NS_ERROR_FAILURE (0x80004005) > Component: Console > Interface: IConsole {a7f17a42-5b64-488d-977b-4b2c639ada27} I cannot reproduce that anymore (probably hit another problem). Could you please provide what the vbox-dev people asked for to solve that problem? VBox.log from ~/.VirtualBox/Machines//Logs/VBox.log and start with export VBOX_LOG=+rt_ldr.e.l2.f VirtualBox -startvm VM_NAME the resulting .log file (created in the current directory!) http://vbox.innotek.de/pipermail/vbox-dev/2009-May/001411.html http://vbox.innotek.de/pipermail/vbox-dev/2009-May/001413.html Thanks! -- Bernhard Fr?hlich http://www.bluelife.at/ From miwi at FreeBSD.org Fri May 15 10:07:30 2009 From: miwi at FreeBSD.org (Martin Wilke) Date: Fri May 15 10:07:37 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: <3481d8e60905141449qfcf5da8r95d54281206304a4@mail.gmail.com> References: <20090514191237.GD70242@bsdcrew.de> <3481d8e60905141449qfcf5da8r95d54281206304a4@mail.gmail.com> Message-ID: <20090515100727.GG71804@bsdcrew.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Benoit, can you please tell me which FreeBSD Version you use? On Thu, May 14, 2009 at 11:49:22PM +0200, Benoit Calvez wrote: > > I'm trying to build from amd64, but got the following error. Sorry but I > didn't look, and it's a fresh paste: > ===> Configuring for virtualbox-2.2.2r19673 > Checking for environment: Determined build machine: freebsd.amd64, target > machine: freebsd.amd64, OK. > Checking for kBuild: found, OK. > Checking for gcc: found version 4.2.1, OK. > Checking for as86: found version 0.16.17, OK. > Checking for bcc: found version 0.16.17, OK. > Checking for iasl: found version 20070320, OK. > Checking for xslt: found, OK. > Checking for pthread: found, OK. > Checking for libxml2: found version 2.7.3, OK. > Checking for libxslt: found version 1.1.24, OK. > Checking for libIDL: found version 0.8.13, OK. > Checking for zlib: found version 1.2.3, OK. > Checking for SDL: found version 1.2.13, OK. > Checking for X libraries: found, OK. > Checking for Xcursor: found, OK. > Checking for Xmu: found, OK. > Checking for Mesa / GLU: Xlib: extension "Generic Event Extension" missing > on display ":0.0". > Xlib: extension "Generic Event Extension" missing on display ":0.0". > found version 1.2, OK. > Checking for Qt4: found version 4.4.3, OK. > Checking for Qt4 devtools: found version 4.4.3, OK. > Checking for python support: found version 2.5.4, OK. > > Successfully generated > '/usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/AutoConfig.kmk' > and '/usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/env.sh'. > Source '/usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/env.sh' > once before you start to build VBox: > > source /usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/env.sh > kmk > > > +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING > +++ > Hardening is enabled which means that the VBox binaries will not run from > the binary directory. The binaries have to be installed suid root and some > more prerequisites have to be fulfilled which is normally done by > installing > the final package. For development, the hardening feature can be disabled > by specifying the --disable-hardening parameter. Please never disable that > feature for the final distribution! > +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING > +++ > > Enjoy! > ===> Building for virtualbox-2.2.2r19673 > cd /usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673 && /bin/sh > env.sh && VBOX_LIBPATH_X11=/usr/local > /usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/kBuild/bin/freebsd.amd64/kmk > Config.kmk:1664: > /usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/GCCConfig.kmk: > No such file or directory > Config.kmk:3789: > /usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/revision.kmk: > No such file or directory > Fatal error 'kse_create() failed > ' at line 469 in file /usr/src/lib/libpthread/thread/thr_kern.c (errno = 2) > *** Error code 1 > > > > > -- > Benoit C. > _______________________________________________ > 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" > - -- +-----------------------+-------------------------------+ | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | | ICQ : 169139903 | Mail : miwi(at)FreeBSD.org | +-----------------------+-------------------------------+ | Mess with the Best, Die like the Rest! | +-----------------------+-------------------------------+ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAkoNPt8ACgkQdLJIhLHm/OmsIgCgpK7yToOVhb6/uMyJKshD8Zlw tb4AnAmFSdyxF8NRaC7AxB6Px3oUwwM7 =vUAY -----END PGP SIGNATURE----- From miwi at FreeBSD.org Fri May 15 10:12:56 2009 From: miwi at FreeBSD.org (Martin Wilke) Date: Fri May 15 10:13:08 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: <20090514191237.GD70242@bsdcrew.de> References: <20090514191237.GD70242@bsdcrew.de> Message-ID: <20090515101253.GH71804@bsdcrew.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ok We uploaded a new tarball what should be fix the build on AMD64. Small changelog: - - devel/kbuild is now dependency - - remove misc/compat6 support Note: Use devel/bcc instead of devel/dev86 what means If you have devel/bcc installed please deinstall http://people.freebsd.org/~miwi/vbox/virtualbox_1.tgz Please give us feedback :P - - Martin - -- +-----------------------+-------------------------------+ | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | | ICQ : 169139903 | Mail : miwi(at)FreeBSD.org | +-----------------------+-------------------------------+ | Mess with the Best, Die like the Rest! | +-----------------------+-------------------------------+ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAkoNQCUACgkQdLJIhLHm/OmgeQCgptEW5FhkmB8huDhs5LL63PhI +04AoONjytolxD892zcCnlv81MRLceEv =UJL8 -----END PGP SIGNATURE----- From kimoto at ohnolab.org Fri May 15 11:13:19 2009 From: kimoto at ohnolab.org (Masahiko KIMOTO) Date: Fri May 15 11:13:32 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: <20090515101253.GH71804@bsdcrew.de> References: <20090514191237.GD70242@bsdcrew.de> <20090515101253.GH71804@bsdcrew.de> Message-ID: <20090515.195026.74738745.kimoto@ohnolab.org> I'm testing on today's 8-CURRENT/i386. When start the virtual machine, kernel got panic with; May 15 19:31:23 eterna kernel: panic: clone_create() on cdevsw without minor numbers May 15 19:31:23 eterna kernel: cpuid = 0 May 15 19:31:23 eterna kernel: KDB: enter: panic So I'm looking up the source code of vboxdrv.ko but couldn't find . -name 'vboxdrv.*' or something like. What should I check out then? ---------------------------------------------------------------------- Masahiko KIMOTO, Ph. D. E-mail: kimoto@ohnolab.org URL: http://www.ohnolab.org/~kimoto From bsam at ipt.ru Fri May 15 11:21:50 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Fri May 15 11:22:03 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: <20090515.195026.74738745.kimoto@ohnolab.org> (Masahiko KIMOTO's message of "Fri\, 15 May 2009 19\:50\:26 +0900 \(JST\)") References: <20090514191237.GD70242@bsdcrew.de> <20090515101253.GH71804@bsdcrew.de> <20090515.195026.74738745.kimoto@ohnolab.org> Message-ID: <80027300@bb.ipt.ru> On Fri, 15 May 2009 19:50:26 +0900 (JST) Masahiko KIMOTO wrote: > I'm testing on today's 8-CURRENT/i386. So do I. But virtualbox works here. Until any VM got shutdown -- none can be started. > When start the virtual machine, kernel got panic with; > May 15 19:31:23 eterna kernel: panic: clone_create() on cdevsw without minor numbers > May 15 19:31:23 eterna kernel: cpuid = 0 > May 15 19:31:23 eterna kernel: KDB: enter: panic > So I'm looking up the source code of vboxdrv.ko but couldn't find . -name > 'vboxdrv.*' or something like. > What should I check out then? Do you have all kernel modules from ports up to date with world/kernel? WBR -- 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 Fri May 15 11:26:59 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Fri May 15 11:27:05 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: <747dc8f30905150417h3abb1b09s7e56f348ad3cbfbe@mail.gmail.com> (Renato Botelho's message of "Fri\, 15 May 2009 08\:17\:07 -0300") References: <20090514191237.GD70242@bsdcrew.de> <747dc8f30905150417h3abb1b09s7e56f348ad3cbfbe@mail.gmail.com> Message-ID: <13946991@bb.ipt.ru> On Fri, 15 May 2009 08:17:07 -0300 Renato Botelho wrote: > I've built it on i386/CURRENT r191522, but I couldn't load the > module, when i try, i got: > KLD vboxdrv.ko: depends on kernel - not available I didn't see that message. > kldload: can't load vboxdrv: File exists While this is familiar for me. I've got it when build virtualbox with newer kernel sources (it so happened that I csuped src but had no time to rebuild/reinstall) than the installed kernel. > It says file exists, but the module is not loaded > root@botelhor:/home/garga# kldstat > Id Refs Address Size Name > 1 18 0xc0400000 b584bc kernel > 2 1 0xc0f59000 809c snd_via8233.ko > 3 2 0xc0f62000 4a438 sound.ko > 4 1 0xc46af000 8000 linprocfs.ko > 5 1 0xc46c8000 24000 linux.ko > Any idea? WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From kimoto at ohnolab.org Fri May 15 11:29:25 2009 From: kimoto at ohnolab.org (Masahiko KIMOTO) Date: Fri May 15 11:29:37 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: <80027300@bb.ipt.ru> References: <20090515101253.GH71804@bsdcrew.de> <20090515.195026.74738745.kimoto@ohnolab.org> <80027300@bb.ipt.ru> Message-ID: <20090515.202723.41647485.kimoto@ohnolab.org> > > When start the virtual machine, kernel got panic with; > > > May 15 19:31:23 eterna kernel: panic: clone_create() on cdevsw without minor numbers > > May 15 19:31:23 eterna kernel: cpuid = 0 > > May 15 19:31:23 eterna kernel: KDB: enter: panic > > > So I'm looking up the source code of vboxdrv.ko but couldn't find . -name > > 'vboxdrv.*' or something like. > > > What should I check out then? > > Do you have all kernel modules from ports up to date with world/kernel? Hmm, Under /boot/kernel/ is up to date by make build/installkernel. Under /boot/modules/, only vboxdrv.ko is in it, and is up to date. ---------------------------------------------------------------------- Masahiko KIMOTO, Ph. D. E-mail: kimoto@ohnolab.org URL: http://www.ohnolab.org/~kimoto From gdn at fxclub.org Fri May 15 11:32:21 2009 From: gdn at fxclub.org (Gorbatovsky Dmitry) Date: Fri May 15 11:32:27 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: <20090514191237.GD70242@bsdcrew.de> References: <20090514191237.GD70242@bsdcrew.de> Message-ID: <4A0D4D6E.6010905@fxclub.org> Thanks for grate work! I install on VirtualBox FreeBSD 7.1, Ubuntu, Windows 7 and it work fine. %uname -a FreeBSD user 7.2-RELEASE FreeBSD 7.2-RELEASE #1: Thu May 7 15:46:13 MSD 2009 root@user:/usr/obj/usr/src/sys/GENERIC i386 Dmitry. From sergey.dyatko at gmail.com Fri May 15 11:36:34 2009 From: sergey.dyatko at gmail.com (Sergey V. Dyatko) Date: Fri May 15 11:36:40 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: <20090515.195026.74738745.kimoto@ohnolab.org> References: <20090514191237.GD70242@bsdcrew.de> <20090515101253.GH71804@bsdcrew.de> <20090515.195026.74738745.kimoto@ohnolab.org> Message-ID: <20090515143651.09b75403@notebook> ? Fri, 15 May 2009 19:50:26 +0900 (JST) Masahiko KIMOTO ?????: MK> I'm testing on today's 8-CURRENT/i386. MK> MK> When start the virtual machine, kernel got panic with; MK> MK> May 15 19:31:23 eterna kernel: panic: clone_create() on cdevsw MK> without minor numbers May 15 19:31:23 eterna kernel: cpuid = 0 MK> May 15 19:31:23 eterna kernel: KDB: enter: panic MK> MK> So I'm looking up the source code of vboxdrv.ko but couldn't find . MK> -name 'vboxdrv.*' or something like. MK> MK> What should I check out then? MK> /boot/modules/vboxdrv.ko ? MK> ---------------------------------------------------------------------- MK> Masahiko KIMOTO, Ph. D. MK> E-mail: kimoto@ohnolab.org URL: MK> http://www.ohnolab.org/~kimoto -- wbr, tiger From rbgarga at gmail.com Fri May 15 11:39:38 2009 From: rbgarga at gmail.com (Renato Botelho) Date: Fri May 15 11:39:44 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: <20090514191237.GD70242@bsdcrew.de> References: <20090514191237.GD70242@bsdcrew.de> Message-ID: <747dc8f30905150417h3abb1b09s7e56f348ad3cbfbe@mail.gmail.com> On Thu, May 14, 2009 at 4:12 PM, Martin Wilke wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Howdy Guys, > > After the announcement from Alexander Eichner about > Virtualbox on FreeBSD, we started the work on a port > for FreeBSD. Now we think that we solved the most > problems and are ready for the first Call for Testing. > > Some notes before you can test the port: > Make sure you are using RELENG_7 or higher. You have > to use a fresh portstree with uptodate ports!! Please > read carefully the pkg-messages. > > Some known issues / Troubleshooting: > Sometimes the kernel on HEAD coredumps when loading > or unloading the kernel module. A small workaround > to prevent the crash is to not start X, mount proc, > then load the kernel module and start X from the > console. That helped me and some testers, maybe you > too. :P AMD64 should be work in general, it builds > and start. But not right tested at the moment. We > want here also some feedback. > > Some Thanks: > First of all we'd like to say many thanks to _ALL_ > vbox developers. Next people are Bernhard Froehlich > (aka decke), Beat Gaetzi (beat@), Dennis Herrmann > (dhn@), Pietro Cerutti (gahr@), myself (*gg*), > and _ALL_ who helped and provided feedback. > > Happy Testing :-) > > Download: > > ?http://people.freebsd.org/~miwi/vbox/vboxport.tgz > > Wiki Page: > ?http://wiki.freebsd.org/VirtualBox Hello Martin I've built it on i386/CURRENT r191522, but I couldn't load the module, when i try, i got: KLD vboxdrv.ko: depends on kernel - not available kldload: can't load vboxdrv: File exists It says file exists, but the module is not loaded root@botelhor:/home/garga# kldstat Id Refs Address Size Name 1 18 0xc0400000 b584bc kernel 2 1 0xc0f59000 809c snd_via8233.ko 3 2 0xc0f62000 4a438 sound.ko 4 1 0xc46af000 8000 linprocfs.ko 5 1 0xc46c8000 24000 linux.ko Any idea? -- Renato Botelho From rink at FreeBSD.org Fri May 15 11:40:04 2009 From: rink at FreeBSD.org (Rink Springer) Date: Fri May 15 11:40:16 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: <747dc8f30905150417h3abb1b09s7e56f348ad3cbfbe@mail.gmail.com> References: <20090514191237.GD70242@bsdcrew.de> <747dc8f30905150417h3abb1b09s7e56f348ad3cbfbe@mail.gmail.com> Message-ID: <20090515112106.GA84567@rink.nu> On Fri, May 15, 2009 at 08:17:07AM -0300, Renato Botelho wrote: > I've built it on i386/CURRENT r191522, but I couldn't load the > module, when i try, i got: > > KLD vboxdrv.ko: depends on kernel - not available > kldload: can't load vboxdrv: File exists This generally means your kernel sources and binary are not in sync. Just rebuild and reinstall your kernel and all modules and you will be fine. Regards, -- Rink P.W. Springer - http://rink.nu "Talk to me." - Horatio Caine From bsam at ipt.ru Fri May 15 13:23:37 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Fri May 15 13:23:49 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: <20090515101253.GH71804@bsdcrew.de> (Martin Wilke's message of "Fri\, 15 May 2009 12\:12\:54 +0200") References: <20090514191237.GD70242@bsdcrew.de> <20090515101253.GH71804@bsdcrew.de> Message-ID: <88984457@bb.ipt.ru> On Fri, 15 May 2009 12:12:54 +0200 Martin Wilke wrote: > We uploaded a new tarball what should be fix the build on AMD64. > Small changelog: > - devel/kbuild is now dependency > - remove misc/compat6 support > Note: > Use devel/bcc instead of devel/dev86 what means > If you have devel/bcc installed please deinstall > http://people.freebsd.org/~miwi/vbox/virtualbox_1.tgz > Please give us feedback :P I've got an error at my 8-CURRENT tinderbox: ----- ======================================== ===> Building package for virtualbox-2.2.2r19673 tar: lib/virtualbox/VBoxREM32.so: Cannot stat: No such file or directory tar: lib/virtualbox/VBoxREM64.so: Cannot stat: No such file or directory tar: Removing leading '/' from member names tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 ----- Seems that for 64 bit platform none of VBoxREM[32|64].so are created. BTW, those who are interested at the subject from mail lists ports@, emulation@ and current@ already knows the great news. May be it's time to move to one list, say, virtualization@? WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From miwi at FreeBSD.org Fri May 15 13:28:19 2009 From: miwi at FreeBSD.org (Martin Wilke) Date: Fri May 15 13:28:26 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: <88984457@bb.ipt.ru> References: <20090514191237.GD70242@bsdcrew.de> <20090515101253.GH71804@bsdcrew.de> <88984457@bb.ipt.ru> Message-ID: <20090515132815.GJ71804@bsdcrew.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, May 15, 2009 at 05:23:34PM +0400, Boris Samorodov wrote: > On Fri, 15 May 2009 12:12:54 +0200 Martin Wilke wrote: > > > We uploaded a new tarball what should be fix the build on AMD64. > > > Small changelog: > > - devel/kbuild is now dependency > > - remove misc/compat6 support > > > Note: > > Use devel/bcc instead of devel/dev86 what means > > If you have devel/bcc installed please deinstall > > > http://people.freebsd.org/~miwi/vbox/virtualbox_1.tgz > > > Please give us feedback :P > > I've got an error at my 8-CURRENT tinderbox: > ----- > ======================================== > ===> Building package for virtualbox-2.2.2r19673 > tar: lib/virtualbox/VBoxREM32.so: Cannot stat: No such file or directory > tar: lib/virtualbox/VBoxREM64.so: Cannot stat: No such file or directory > tar: Removing leading '/' from member names > tar: Error exit delayed from previous errors. > pkg_create: make_dist: tar command failed with code 256 > ----- > > Seems that for 64 bit platform none of VBoxREM[32|64].so are > created. Ups :(. Seems we was to fast. I'll fix that soon ;). > > BTW, those who are interested at the subject from mail lists > ports@, emulation@ and current@ already knows the great news. > May be it's time to move to one list, say, virtualization@? > Maybe :-). But for the moment it's a good place to deal with vbox. > > WBR > -- > Boris Samorodov (bsam) > Research Engineer, http://www.ipt.ru Telephone & Internet SP > FreeBSD Committer, http://www.FreeBSD.org The Power To Serve > - -- +-----------------------+-------------------------------+ | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | | ICQ : 169139903 | Mail : miwi(at)FreeBSD.org | +-----------------------+-------------------------------+ | Mess with the Best, Die like the Rest! | +-----------------------+-------------------------------+ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) iEUEARECAAYFAkoNbe8ACgkQdLJIhLHm/OngAwCY2KHMIweS1sARJw/BW2ehMjMr zgCgy9Kh3bwk9ik4uX6t7slfghIr7u8= =ohI6 -----END PGP SIGNATURE----- From guru at unixarea.de Fri May 15 13:56:11 2009 From: guru at unixarea.de (Matthias Apitz) Date: Fri May 15 13:56:17 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: <20090515132815.GJ71804@bsdcrew.de> References: <20090514191237.GD70242@bsdcrew.de> <20090515101253.GH71804@bsdcrew.de> <88984457@bb.ipt.ru> <20090515132815.GJ71804@bsdcrew.de> Message-ID: <20090515133447.GA12408@rebelion.Sisis.de> El d?a Friday, May 15, 2009 a las 03:28:15PM +0200, Martin Wilke escribi?: ... > > BTW, those who are interested at the subject from mail lists > > ports@, emulation@ and current@ already knows the great news. > > May be it's time to move to one list, say, virtualization@? > > > > Maybe :-). But for the moment it's a good place to deal with > vbox. Yes, but please Cc: only one list from now, for example freebsd-emulation@freebsd.org ; 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 paul at fletchermoorland.co.uk Fri May 15 14:25:50 2009 From: paul at fletchermoorland.co.uk (Paul Wootton) Date: Fri May 15 14:25:57 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: <20090515101253.GH71804@bsdcrew.de> References: <20090514191237.GD70242@bsdcrew.de> <20090515101253.GH71804@bsdcrew.de> Message-ID: <4A0D7574.3050801@fletchermoorland.co.uk> Martin Wilke wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Ok > > We uploaded a new tarball what should be fix the build on AMD64. > > Small changelog: > - - devel/kbuild is now dependency > - - remove misc/compat6 support > > Note: > Use devel/bcc instead of devel/dev86 what means > If you have devel/bcc installed please deinstall > > http://people.freebsd.org/~miwi/vbox/virtualbox_1.tgz > > Please give us feedback :P > > > - - Martin > > - -- > > +-----------------------+-------------------------------+ > | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | > | ICQ : 169139903 | Mail : miwi(at)FreeBSD.org | > +-----------------------+-------------------------------+ > | Mess with the Best, Die like the Rest! | > +-----------------------+-------------------------------+ > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.11 (FreeBSD) > > iEYEARECAAYFAkoNQCUACgkQdLJIhLHm/OmgeQCgptEW5FhkmB8huDhs5LL63PhI > +04AoONjytolxD892zcCnlv81MRLceEv > =UJL8 > -----END PGP SIGNATURE----- > _______________________________________________ > 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" > > > Hi, When compiling I get the following error kBuild: Installing tstUtf8 => /root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/bin/testcase/tstUtf8 kBuild: Installing tstUuid => /root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/bin/testcase/tstUuid kBuild: Installing tstVMStructGC => /root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/bin/tstVMStructGC kBuild: Generating tstVMStructSize - /root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h /root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/bin/tstVMStructGC: 1: Syntax error: "(" unexpected kmk[2]: *** [/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h] Error 2 kmk[2]: *** Deleting file `/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h' kmk[2]: *** Waiting for unfinished jobs.... awk -f /usr/src/sys/conf/kmod_syms.awk /root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/vboxdrv/vboxdrv.ko /root/vBox/virtualbox/work/virtualbox-2.2.2r19673/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.def | xargs -J% objcopy % /root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/vboxdrv/vboxdrv.ko awk: can't open file /root/vBox/virtualbox/work/virtualbox-2.2.2r19673/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.def source line number 10 kmk[2]: Leaving directory `/root/vBox/virtualbox/work/virtualbox-2.2.2r19673' kmk[2]: Entering directory `/root/vBox/virtualbox/work/virtualbox-2.2.2r19673' kmk[2]: *** Exiting with status 2 kmk[1]: *** [pass_binaries_this] Error 2 kmk[1]: Leaving directory `/root/vBox/virtualbox/work/virtualbox-2.2.2r19673' kmk: *** [pass_binaries_order] Error 2 *** Error code 2 Stop in /root/vBox/virtualbox. demophon# demophon# uname -a FreeBSD demophon 8.0-CURRENT FreeBSD 8.0-CURRENT #10: Wed May 6 09:04:17 UTC 2009 paul@demophon:/usr/obj/usr/src/sys/DEMOPHON amd64 Any ideas? Cheers Paul From avg at icyb.net.ua Fri May 15 14:48:59 2009 From: avg at icyb.net.ua (Andriy Gapon) Date: Fri May 15 14:49:06 2009 Subject: qemu+kqemu: 64-bit linux guess still no go Message-ID: <4A0D7E6E.4080808@icyb.net.ua> Just wanted to drop a line about this again. An attempt to run 64-bit linux guest (on amd64 host too) with kqemu results in: kernel: kqemu: aborting: Unexpected exception 0x0d in monitor space kernel: err=0000 CS:EIP=f180:00000000f001563c SS:SP=0000:00000000f00c8e60 System: FreeBSD stable/7, amd64 qemu-0.10.3 kqemu-kmod-devel-1.4.0.p1_2 With -no-kqemu everything's OK. -- Andriy Gapon From lists at yamagi.org Fri May 15 14:53:05 2009 From: lists at yamagi.org (Yamagi Burmeister) Date: Fri May 15 14:53:11 2009 Subject: [new port] graphics/linux-dri74 In-Reply-To: <67576966@bb.ipt.ru> References: <92596693@bb.ipt.ru> <20090510174445.GA75441@yamagi.org> <67576966@bb.ipt.ru> Message-ID: <20090515145252.GA69488@yamagi.org> Am Wed, May 13, 2009 at 05:34:17PM +0400 schrieb Boris Samorodov: > Don't see anything obvious, sorry. Anybody else? > > Did you try to use xf86-video-radeonhd? OK, i gave both xf86-video-radeonhd and xf86-video-radeonhd a try. No change, native FreeBSD applications are still running fine and fast, Linux applications tell that direct rendering is enabled but fall back to the slow software rasterizer. After that I installed both FreeBSD/amd64 and FreeBSD/i386 to another box with a Radeon X1550. Using FreeBSD/amd64 the problems are of course the same. But using FreeBSD/i386 the new linux_dri ports suddenly works. So my guess is, that the problem has something todo with the bit depth. In detail: FreeBSD 32bit -> Linux 32bit => works FreeBSD 64bit -> Linux 32bit => falls back to software rasterizer I don't know, if this is a known "problem" regarding DRI and DRM. And I have no other hardware to test with. The next step would be testing if only the Radeon DRM shows this behavior or if other drivers like Intel behave the same. Nevertheless I'll try FreeBSD 64bit -> FreeBSD 32bit over the weekend, and see if that works. If it doesn't it's a general problem of DRM and not of linux_drm. Yamagi -- Homepage: www.yamagi.org Jabber: yamagi@yamagi.org GnuPG/GPG: 0xEFBCCBCB -------------- 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/20090515/b2e6a617/attachment.pgp From nox at jelal.kn-bremen.de Fri May 15 20:40:09 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Fri May 15 20:41:54 2009 Subject: qemu+kqemu: 64-bit linux guess still no go In-Reply-To: <4A0D7E6E.4080808@icyb.net.ua> Message-ID: <200905152037.n4FKbtKe004781@triton.kn-bremen.de> In article <4A0D7E6E.4080808@icyb.net.ua> you write: >Just wanted to drop a line about this again. >An attempt to run 64-bit linux guest (on amd64 host too) with kqemu results in: > >kernel: kqemu: aborting: Unexpected exception 0x0d in monitor space >kernel: err=0000 CS:EIP=f180:00000000f001563c SS:SP=0000:00000000f00c8e60 > >System: FreeBSD stable/7, amd64 >qemu-0.10.3 >kqemu-kmod-devel-1.4.0.p1_2 > >With -no-kqemu everything's OK. Yeah kqemu amd64 guest support is spotty at best, as mentioned in the pkg-message.s... (FreeBSD/amd64 guests with -kernel-kqemu also fail for example.) When this will be fixed? Idunno, the linux folks have kinda moved on to kvm now and regard kqemu as `unmaintained'... I guess the best we can do at this time is hope that the vbox port will work properly on amd64 soon. Cheers, Juergen From nox at jelal.kn-bremen.de Fri May 15 22:40:12 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Fri May 15 22:40:19 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: <06c77d8650448aa63d9ce8d4b1a9c3e0.squirrel@webmail.itac.at> References: <20090514191237.GD70242@bsdcrew.de> Message-ID: <200905152238.n4FMcqR0007682@triton.kn-bremen.de> In article <06c77d8650448aa63d9ce8d4b1a9c3e0.squirrel@webmail.itac.at> you write: >On Thu, May 14, 2009 11:51 pm, Artem Belevich wrote: >> Few more notes from -CURRENT/amd64 >> >> [snip] >> >> * Attempt to boot new VM (64-bit FreeBSD) from -current snapshot DVD >> ISO results in an error: >> >> Failed to start the virtual machine FreeBSD. >> Failed to load VMMR0.r0 (VERR_SYMBOL_VALUE_TOO_BIG). >> Unknown error creating VM (VERR_SYMBOL_VALUE_TOO_BIG). >> >> Result Code: NS_ERROR_FAILURE (0x80004005) >> Component: Console >> Interface: IConsole {a7f17a42-5b64-488d-977b-4b2c639ada27} > > >I cannot reproduce that anymore (probably hit another problem). Could you >please provide what the vbox-dev people asked for to solve that problem? > >VBox.log from ~/.VirtualBox/Machines//Logs/VBox.log > >and start with > >export VBOX_LOG=+rt_ldr.e.l2.f >VirtualBox -startvm VM_NAME > Hi! You forgot to say this needs a debug build... :) >the resulting .log file (created in the current directory!) > >http://vbox.innotek.de/pipermail/vbox-dev/2009-May/001411.html >http://vbox.innotek.de/pipermail/vbox-dev/2009-May/001413.html > >Thanks! I tried to follow up to that thread on vbox-dev but it seems to be subscribed-only, so I'll repost here: (-emulation only, I trimmed the other lists) >[...] Hi! I just tried vbox here and saw the same problem, so I made a debug build (diff for the wip FreeBSD port Makefile below) and got out the following logs: VBox.log: 00:00:03.661 VirtualBox 2.2.51_OSE r19662 freebsd.amd64 (May 15 2009 21:17:12) release log 00:00:03.661 Log opened 2009-05-15T19:25:52.579924000Z 00:00:03.661 OS Product: FreeBSD 00:00:03.661 OS Release: 7.2-STABLE 00:00:03.661 OS Version: FreeBSD 7.2-STABLE #0: Sun May 10 19:06:01 CEST 2009 nox@triton.kn-bremen.de:/usr/obj/usr/home/nox/src72s/src/sys/TRITON 00:00:03.661 Executable: /usr/local/lib/virtualbox/VirtualBox 00:00:03.661 Process ID: 4630 00:00:03.661 Package type: BSD_64BITS_GENERIC (OSE) 00:00:03.706 00:00:03.706 !!Assertion Failed!! 00:00:03.706 Expression: (Elf_Addr)*(int32_t *)pAddrW == Value 00:00:03.706 Location : /usr/home/nox/vbox/virtualbox/work/virtualbox-2.2.2r19673/src/VBox/Runtime/common/ldr/ldrELFRelocatable.cpp.h(367) int rtldrELF64RelocateSection(RTLDRMODELF64RT_NOTHING*, Elf64_Addr, int (*)(RTLDRMODINTERNAL*, const char*, const char*, unsigned int, RTUINTPTR*, void*), void*, Elf64_Addr, Elf64_Size, const uint8_t*, uint8_t*, const void*, Elf64_Size) 00:00:03.706 Value=fffffffe80ac87c0 2009-05-15-19-25-48.089-VirtualBox-4630.log: Log created: 2009-05-15T19:25:48.898420000Z Executable: /usr/local/lib/virtualbox/VirtualBox Arg[0]: VirtualBox Arg[1]: -startvm Arg[2]: fbsd72cd RTLdrOpen: pszFilename=000000080810a040:{/usr/local/lib/virtualbox/VMMR0.r0} fFlags=0x0 enmArch=2 phLdrMod=00007fffffa99b48 rtldrELF64Open: /usr/local/lib/virtualbox/VMMR0.r0: returns VINF_SUCCESS *phLdrMod=000000080810d080 rtldrOpenWithReader: /usr/local/lib/virtualbox/VMMR0.r0: returns VINF_SUCCESS *phMod=000000080810d080 RTLdrOpen: return VINF_SUCCESS *phLdrMod RTLdrSize: hLdrMod=000000080810d080 RTLdrSize: returns 1201440 RTLdrEnumSymbols: hLdrMod=000000080810d080 fFlags=0x0 pvBit=0000000000000000 BaseAddress=0000000000000000 pfnCallback=0000000800f961f0 pvUser=00007fffffa99b30 RTLdrEnumSymbols: returns VINF_SUCCESS RTLdrGetBits: hLdrMod=000000080810d080 pvBits=0000000808700068 BaseAddress=fffffffe809df080 pfnGetImport=0000000800f99280 pvUser=00000008020de958 fffffffe809df4a4: R_X86_64_32S Value=fffffffe80ac87c0 SymValue=fffffffe80ac84c0 !!Assertion Failed!! Expression: (Elf_Addr)*(int32_t *)pAddrW == Value Location : /usr/home/nox/vbox/virtualbox/work/virtualbox-2.2.2r19673/src/VBox/Runtime/common/ldr/ldrELFRelocatable.cpp.h(367) int rtldrELF64RelocateSection(RTLDRMODELF64RT_NOTHING*, Elf64_Addr, int (*)(RTLDRMODINTERNAL*, const char*, const char*, unsigned int, RTUINTPTR*, void*), void*, Elf64_Addr, Elf64_Size, const uint8_t*, uint8_t*, const void*, Elf64_Size) Value=fffffffe80ac87c0 I suspect BaseAddress=fffffffe809df080 is the problem? Here comes the port diff: Index: Makefile =================================================================== --- Makefile (revision 372) +++ Makefile (working copy) @@ -95,10 +95,26 @@ ${WRKSRC}/env.sh do-build: +.if defined(WITH_DEBUG) + cd ${WRKSRC} && ${SH} env.sh && ${KMK_CONFIG} ${LOCALBASE}/bin/kmk BUILD_TYPE=debug +.else cd ${WRKSRC} && ${SH} env.sh && ${KMK_CONFIG} ${LOCALBASE}/bin/kmk +.endif do-install: ${MKDIR} ${KMODDIR} +.if defined(WITH_DEBUG) + ${INSTALL_KLD} ${WRKSRC}/out/${KMK_ARCH}/debug/bin/vboxdrv.ko ${KMODDIR} + + ${MKDIR} ${PREFIX}/lib/virtualbox && \ + (cd ${WRKSRC}/out/${KMK_ARCH}/debug/bin && ${COPYTREE_SHARE} "*.so *.gc *.r0 components" ${PREFIX}/lib/virtualbox) + + ${MKDIR} ${PREFIX}/bin; \ + for f in VBoxBFE VBoxHeadless VBoxManage VBoxNetDHCP VBoxSDL VBoxSVC VBoxXPCOMIPCD VirtualBox; do \ + ${INSTALL_PROGRAM} ${WRKSRC}/out/${KMK_ARCH}/debug/bin/$$f ${PREFIX}/lib/virtualbox/$${f##*/}; \ + ${LN} -sf ${PREFIX}/lib/virtualbox/$${f##*/} ${PREFIX}/bin/$${f##*/}; \ + done +.else ${INSTALL_KLD} ${WRKSRC}/out/${KMK_ARCH}/release/bin/vboxdrv.ko ${KMODDIR} ${MKDIR} ${PREFIX}/lib/virtualbox && \ @@ -109,6 +125,7 @@ ${INSTALL_PROGRAM} ${WRKSRC}/out/${KMK_ARCH}/release/bin/$$f ${PREFIX}/lib/virtualbox/$${f##*/}; \ ${LN} -sf ${PREFIX}/lib/virtualbox/$${f##*/} ${PREFIX}/bin/$${f##*/}; \ done +.endif for f in VBoxBFE VBoxHeadless VBoxNetDHCP VBoxSDL VirtualBox; do \ ${CHMOD} 4511 ${PREFIX}/lib/virtualbox/$${f##*/}; \ From mark at mkproductions.org Fri May 15 22:47:17 2009 From: mark at mkproductions.org (Mark Kane) Date: Fri May 15 22:47:29 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: <06c77d8650448aa63d9ce8d4b1a9c3e0.squirrel@webmail.itac.at> References: <20090514191237.GD70242@bsdcrew.de> <06c77d8650448aa63d9ce8d4b1a9c3e0.squirrel@webmail.itac.at> Message-ID: <20090515171326.3297fbd6@mkproductions.org> On Fri, May 15, 2009, at 11:53:39 +0200, Bernhard Fr?hlich wrote: > On Thu, May 14, 2009 11:51 pm, Artem Belevich wrote: > > Few more notes from -CURRENT/amd64 > > > > [snip] > > > > * Attempt to boot new VM (64-bit FreeBSD) from -current snapshot DVD > > ISO results in an error: > > > > Failed to start the virtual machine FreeBSD. > > Failed to load VMMR0.r0 (VERR_SYMBOL_VALUE_TOO_BIG). > > Unknown error creating VM (VERR_SYMBOL_VALUE_TOO_BIG). > > > > Result Code: NS_ERROR_FAILURE (0x80004005) > > Component: Console > > Interface: IConsole {a7f17a42-5b64-488d-977b-4b2c639ada27} > > > I cannot reproduce that anymore (probably hit another problem). Could > you please provide what the vbox-dev people asked for to solve that > problem? > > VBox.log from ~/.VirtualBox/Machines//Logs/VBox.log > > and start with > > export VBOX_LOG=+rt_ldr.e.l2.f > VirtualBox -startvm VM_NAME > > the resulting .log file (created in the current directory!) > > http://vbox.innotek.de/pipermail/vbox-dev/2009-May/001411.html > http://vbox.innotek.de/pipermail/vbox-dev/2009-May/001413.html > > Thanks! Hi. I just wanted to add that the kldload and "VERR_SYMBOL_VALUE_TOO_BIG" errors that Artem posted also occur on RELENG_7/amd64. I rebuilt with debug enabled and set the environment variable per the posts on the VirtualBox mailing list and have included the requested logs below (along with some additional info from /var/log/messages about the kernel module). One note: when running the version with debug I haven't really seen the original error about "VERR_SYMBOL_VALUE_TOO_BIG" in any of the logs and it doesn't pop up on screen anymore when the the VM fails to start; the window just disappears after failing to start. http://tntpowerhost.com/mixx941/freebsd/virtualbox_logs_20090515.txt Thanks in advance! -Mark -- Internet Radio: Party107 (Trance/Electronic) - http://www.party107.com IRC: MIXXnet IRC Network - irc.mixxnet.net (Nick: MarkK) From tim at bishnet.net Fri May 15 23:48:06 2009 From: tim at bishnet.net (Tim Bishop) Date: Fri May 15 23:48:24 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: <20090514191237.GD70242@bsdcrew.de> References: <20090514191237.GD70242@bsdcrew.de> Message-ID: <20090515234756.GP86061@carrick.bishnet.net> Hi Martin, On Thu, May 14, 2009 at 09:12:37PM +0200, Martin Wilke wrote: > After the announcement from Alexander Eichner about > Virtualbox on FreeBSD, we started the work on a port > for FreeBSD. Now we think that we solved the most > problems and are ready for the first Call for Testing. Is the VRDP stuff meant to work? When following these instructions it just appears athat it doesn't start it up (nothing is listening on 3389): http://www.virtualbox.org/manual/UserManual.html#vboxheadless Thanks for your work making VirtualBox available to us! Tim. -- Tim Bishop http://www.bishnet.net/tim/ PGP Key: 0x5AE7D984 From sfourman at gmail.com Sat May 16 03:44:10 2009 From: sfourman at gmail.com (Sam Fourman Jr.) Date: Sat May 16 03:44:15 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: <747dc8f30905150417h3abb1b09s7e56f348ad3cbfbe@mail.gmail.com> References: <20090514191237.GD70242@bsdcrew.de> <747dc8f30905150417h3abb1b09s7e56f348ad3cbfbe@mail.gmail.com> Message-ID: <11167f520905152019k400aa899l1b3f2d85dd9b7fb4@mail.gmail.com> > I've built it on i386/CURRENT r191522, but I couldn't load the > module, when i try, i got: > > KLD vboxdrv.ko: depends on kernel - not available > kldload: can't load vboxdrv: File exists > > It says file exists, but the module is not loaded > > root@botelhor:/home/garga# kldstat > Id Refs Address ? ?Size ? ? Name > ?1 ? 18 0xc0400000 b584bc ? kernel > ?2 ? ?1 0xc0f59000 809c ? ? snd_via8233.ko > ?3 ? ?2 0xc0f62000 4a438 ? ?sound.ko > ?4 ? ?1 0xc46af000 8000 ? ? linprocfs.ko > ?5 ? ?1 0xc46c8000 24000 ? ?linux.ko > > Any idea? it Probably means that you are running a kernel that is not in sync with the src in your /usr/src do csup -g -L 2 -h cvsup15.freebsd.org /usr/share examples/cvsup/standard-supfile then build your kernel && install your kernel uninstall the Virtualbox port and rebuild it. all will work Sam Fourman Jr. From tim at bishnet.net Sat May 16 10:29:35 2009 From: tim at bishnet.net (Tim Bishop) Date: Sat May 16 10:29:44 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: <20090515234756.GP86061@carrick.bishnet.net> References: <20090514191237.GD70242@bsdcrew.de> <20090515234756.GP86061@carrick.bishnet.net> Message-ID: <20090516102927.GA65772@carrick.bishnet.net> On Sat, May 16, 2009 at 12:47:56AM +0100, Tim Bishop wrote: > On Thu, May 14, 2009 at 09:12:37PM +0200, Martin Wilke wrote: > > After the announcement from Alexander Eichner about > > Virtualbox on FreeBSD, we started the work on a port > > for FreeBSD. Now we think that we solved the most > > problems and are ready for the first Call for Testing. > > Is the VRDP stuff meant to work? When following these instructions it > just appears athat it doesn't start it up (nothing is listening on > 3389): > > http://www.virtualbox.org/manual/UserManual.html#vboxheadless To answer my own question, VRDP isn't available on the Open Source Edition of VirtualBox. Differences can be found here: http://www.virtualbox.org/wiki/Editions Tim. -- Tim Bishop http://www.bishnet.net/tim/ PGP Key: 0x5AE7D984 From itetcu at FreeBSD.org Sat May 16 14:44:41 2009 From: itetcu at FreeBSD.org (Ion-Mihai Tetcu) Date: Sat May 16 14:44:48 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: <20090515101253.GH71804@bsdcrew.de> References: <20090514191237.GD70242@bsdcrew.de> <20090515101253.GH71804@bsdcrew.de> Message-ID: <20090516172525.4f3731c7@it.buh.tecnik93.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 15 May 2009 12:12:54 +0200 Martin Wilke wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Ok > > We uploaded a new tarball what should be fix the build on AMD64. > > Small changelog: > - - devel/kbuild is now dependency > - - remove misc/compat6 support > > Note: > Use devel/bcc instead of devel/dev86 what means > If you have devel/bcc installed please deinstall > > http://people.freebsd.org/~miwi/vbox/virtualbox_1.tgz > > Please give us feedback :P Seems you need to be root to build it and it will fail on tindy/pointy because of touching the fs outside WRKDIR before install.: ===> Building for virtualbox-2.2.2r19673 cd /home/itetcu/wrk/usr/home/itetcu/tmp/virtualbox/work/virtualbox-2.2.2r19673 && /bin/sh env.sh && VBOX_LIBPATH_X11=/usr/local /usr/local/bin/kmk Makefile.kmk:23: /usr/local/share/kBuild/subheader.kmk: Permission denied Makefile.kmk:809: /usr/local/share/kBuild/subfooter.kmk: Permission denied kmk: stat: /usr/local/share/kBuild/subfooter.kmk: Permission denied kmk: stat: /usr/local/share/kBuild/subheader.kmk: Permission denied kmk: *** No rule to make target `/usr/local/share/kBuild/subfooter.kmk'. Stop. *** Error code 2 - -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> itetcu@FreeBSD.org, PGP Key ID 057E9F8B493A297B -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAkoOzNoACgkQJ7GIuiH/oeWibgCeI1c3Lcenk8K6x8PhpKRqw5/h UocAn3qcQcaqb2i1sLHoIUhabWMWa82s =9RR7 -----END PGP SIGNATURE----- From Benoit.Calvez at gmail.com Sat May 16 17:16:39 2009 From: Benoit.Calvez at gmail.com (Benoit Calvez) Date: Sat May 16 17:16:52 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: <3481d8e60905141449qfcf5da8r95d54281206304a4@mail.gmail.com> References: <20090514191237.GD70242@bsdcrew.de> <3481d8e60905141449qfcf5da8r95d54281206304a4@mail.gmail.com> Message-ID: <3481d8e60905161016k3de535e3n9a570c5bee6ba517@mail.gmail.com> On Thu, May 14, 2009 at 11:49 PM, Benoit Calvez wrote: > > > On Thu, May 14, 2009 at 9:12 PM, Martin Wilke wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> >> Howdy Guys, >> >> After the announcement from Alexander Eichner about >> Virtualbox on FreeBSD, we started the work on a port >> for FreeBSD. Now we think that we solved the most >> problems and are ready for the first Call for Testing. >> >> Some notes before you can test the port: >> Make sure you are using RELENG_7 or higher. You have >> to use a fresh portstree with uptodate ports!! Please >> read carefully the pkg-messages. >> >> Some known issues / Troubleshooting: >> Sometimes the kernel on HEAD coredumps when loading >> or unloading the kernel module. A small workaround >> to prevent the crash is to not start X, mount proc, >> then load the kernel module and start X from the >> console. That helped me and some testers, maybe you >> too. :P AMD64 should be work in general, it builds >> and start. But not right tested at the moment. We >> want here also some feedback. >> >> Some Thanks: >> First of all we'd like to say many thanks to _ALL_ >> vbox developers. Next people are Bernhard Froehlich >> (aka decke), Beat Gaetzi (beat@), Dennis Herrmann >> (dhn@), Pietro Cerutti (gahr@), myself (*gg*), >> and _ALL_ who helped and provided feedback. >> >> Happy Testing :-) >> >> Download: >> >> http://people.freebsd.org/~miwi/vbox/vboxport.tgz >> >> Wiki Page: >> http://wiki.freebsd.org/VirtualBox >> >> - Martin >> >> - -- >> >> +-----------------------+-------------------------------+ >> | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | >> | ICQ : 169139903 | Mail : miwi(at)FreeBSD.org | >> +-----------------------+-------------------------------+ >> | Mess with the Best, Die like the Rest! | >> +-----------------------+-------------------------------+ >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v2.0.11 (FreeBSD) >> >> iEYEARECAAYFAkoMbSUACgkQdLJIhLHm/OnNnACeJsT7H9hW1J7CV70P3Ty+q0CA >> kD8AoMLCPbltY999/8qO6fnaqv4UQ9QT >> =LcoD >> -----END PGP SIGNATURE----- >> _______________________________________________ >> 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 >> " >> > > I'm trying to build from amd64, but got the following error. Sorry but I > didn't look, and it's a fresh paste: > ===> Configuring for virtualbox-2.2.2r19673 > Checking for environment: Determined build machine: freebsd.amd64, target > machine: freebsd.amd64, OK. > Checking for kBuild: found, OK. > Checking for gcc: found version 4.2.1, OK. > Checking for as86: found version 0.16.17, OK. > Checking for bcc: found version 0.16.17, OK. > Checking for iasl: found version 20070320, OK. > Checking for xslt: found, OK. > Checking for pthread: found, OK. > Checking for libxml2: found version 2.7.3, OK. > Checking for libxslt: found version 1.1.24, OK. > Checking for libIDL: found version 0.8.13, OK. > Checking for zlib: found version 1.2.3, OK. > Checking for SDL: found version 1.2.13, OK. > Checking for X libraries: found, OK. > Checking for Xcursor: found, OK. > Checking for Xmu: found, OK. > Checking for Mesa / GLU: Xlib: extension "Generic Event Extension" missing > on display ":0.0". > Xlib: extension "Generic Event Extension" missing on display ":0.0". > found version 1.2, OK. > Checking for Qt4: found version 4.4.3, OK. > Checking for Qt4 devtools: found version 4.4.3, OK. > Checking for python support: found version 2.5.4, OK. > > Successfully generated > '/usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/AutoConfig.kmk' > and '/usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/env.sh'. > Source '/usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/env.sh' > once before you start to build VBox: > > source /usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/env.sh > kmk > > > +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING > +++ > Hardening is enabled which means that the VBox binaries will not run from > the binary directory. The binaries have to be installed suid root and > some > more prerequisites have to be fulfilled which is normally done by > installing > the final package. For development, the hardening feature can be disabled > by specifying the --disable-hardening parameter. Please never disable > that > feature for the final distribution! > +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING > +++ > > Enjoy! > ===> Building for virtualbox-2.2.2r19673 > cd /usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673 && /bin/sh > env.sh && VBOX_LIBPATH_X11=/usr/local > /usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/kBuild/bin/freebsd.amd64/kmk > Config.kmk:1664: > /usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/GCCConfig.kmk: > No such file or directory > Config.kmk:3789: > /usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/revision.kmk: > No such file or directory > Fatal error 'kse_create() failed > ' at line 469 in file /usr/src/lib/libpthread/thread/thr_kern.c (errno = 2) > *** Error code 1 > > > > > -- > Benoit C. > > I just tryed with the last tarball ( http://people.freebsd.org/~miwi/vbox/virtualbox_1.tgz) and it compiles fine. the kernel module loads, and I'll try to boot an opensolaris in a few moments. Nice job everyone ! -- Benoit C. From dchagin at freebsd.org Sat May 16 18:52:05 2009 From: dchagin at freebsd.org (Chagin Dmitry) Date: Sat May 16 18:52:12 2009 Subject: [linux-f10] linux_socketcall... ERR#43 'Protocol not supported' In-Reply-To: <81924694@bb.ipt.ru> References: <81924694@bb.ipt.ru> Message-ID: <20090516185156.GA82743@dchagin.static.corbina.ru> On Tue, May 05, 2009 at 09:51:21AM +0400, Boris Samorodov wrote: > Hello List, > > > I'm working on Fedora 10 ports and almost all is fine (even > google-earth seems to work)... But there is no resolving. > I managed to find the culprit. Here it is: > [skiped trace] patch commited. r192206 :) -- Have fun! chd -------------- 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/20090516/a4fe92bc/attachment.pgp From bsam at ipt.ru Sat May 16 20:22:48 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Sat May 16 20:22:54 2009 Subject: [linux-f10] linux_socketcall... ERR#43 'Protocol not supported' In-Reply-To: <20090516185156.GA82743@dchagin.static.corbina.ru> (Chagin Dmitry's message of "Sat\, 16 May 2009 22\:51\:56 +0400") References: <81924694@bb.ipt.ru> <20090516185156.GA82743@dchagin.static.corbina.ru> Message-ID: <03200938@h30.sp.ipt.ru> On Sat, 16 May 2009 22:51:56 +0400 Chagin Dmitry wrote: > On Tue, May 05, 2009 at 09:51:21AM +0400, Boris Samorodov wrote: > > I'm working on Fedora 10 ports and almost all is fine (even > > google-earth seems to work)... But there is no resolving. > > I managed to find the culprit. Here it is: > [skiped trace] > patch commited. r192206 :) Great news, thanks! WBR -- bsam From freebsd at byshenk.net Sun May 17 09:19:05 2009 From: freebsd at byshenk.net (Greg Byshenk) Date: Sun May 17 09:19:18 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: <3481d8e60905161016k3de535e3n9a570c5bee6ba517@mail.gmail.com> References: <20090514191237.GD70242@bsdcrew.de> <3481d8e60905141449qfcf5da8r95d54281206304a4@mail.gmail.com> <3481d8e60905161016k3de535e3n9a570c5bee6ba517@mail.gmail.com> Message-ID: <20090517085626.GD2571@core.byshenk.net> On Sat, May 16, 2009 at 07:16:13PM +0200, Benoit Calvez wrote: > On Thu, May 14, 2009 at 11:49 PM, Benoit Calvez wrote: > > On Thu, May 14, 2009 at 9:12 PM, Martin Wilke wrote: > >> After the announcement from Alexander Eichner about > >> Virtualbox on FreeBSD, we started the work on a port > >> for FreeBSD. Now we think that we solved the most > >> problems and are ready for the first Call for Testing. > >> > >> Some notes before you can test the port: > >> Make sure you are using RELENG_7 or higher. You have > >> to use a fresh portstree with uptodate ports!! Please > >> read carefully the pkg-messages. > >> > >> Some known issues / Troubleshooting: > >> Sometimes the kernel on HEAD coredumps when loading > >> or unloading the kernel module. A small workaround > >> to prevent the crash is to not start X, mount proc, > >> then load the kernel module and start X from the > >> console. That helped me and some testers, maybe you > >> too. :P AMD64 should be work in general, it builds > >> and start. But not right tested at the moment. We > >> want here also some feedback. > >> > >> Some Thanks: > >> First of all we'd like to say many thanks to _ALL_ > >> vbox developers. Next people are Bernhard Froehlich > >> (aka decke), Beat Gaetzi (beat@), Dennis Herrmann > >> (dhn@), Pietro Cerutti (gahr@), myself (*gg*), > >> and _ALL_ who helped and provided feedback. > >> > >> Happy Testing :-) > >> > >> Download: > >> > >> http://people.freebsd.org/~miwi/vbox/vboxport.tgz > >> > >> Wiki Page: > >> http://wiki.freebsd.org/VirtualBox > >> > >> - Martin > > I'm trying to build from amd64, but got the following error. Sorry but I > > didn't look, and it's a fresh paste: > > [...] > I just tryed with the last tarball ( > http://people.freebsd.org/~miwi/vbox/virtualbox_1.tgz) and it compiles fine. > > the kernel module loads, and I'll try to boot an opensolaris in a few > moments. I've just tried with virtualbox_1.tgz, and it builds without a problem, the module installs without a problem, but attempting to start VirtualBox fails. I get no error at all, VirtualBox just hangs. If I attempt to run 'truss VirtualBox', I get the error: Effective UID is not root (euid=1001 egid=1001 uid=1001 gid=1001) (rc=-10) It may help to reinstall VirtualBox. But checking shows that VirtualBox is SUID root: $ ls -l /usr/local/lib/virtualbox/VirtualBox -r-s--x--x 1 root vboxusers 21016 May 17 10:21 /usr/local/lib/virtualbox/VirtualBox It seems that I can create a vm: $ VBoxManage createvm --name test VirtualBox Command Line Management Interface Version 2.2.51_OSE (C) 2005-2009 Sun Microsystems, Inc. All rights reserved. Virtual machine 'test' is created. UUID: 9be28271-55c2-4299-b69a-266c58716db7 Settings file: '/home/gbyshenk/.VirtualBox/Machines/test/test.xml' $ VirtualBox $ ls -l /home/gbyshenk/.VirtualBox/Machines/test/test.xml -rw------- 1 gbyshenk gbyshenk 2302 May 17 10:37 /home/gbyshenk/.VirtualBox/Machines/test/test.xml But VirtualBox itself fails to start -- even if I run as root. System is amd64, 7-STABLE as of 26-04-2009. Does it need to be more recent...? -- greg byshenk - gbyshenk@byshenk.net - Leiden, NL From dikshie at gmail.com Sun May 17 10:09:37 2009 From: dikshie at gmail.com (dikshie) Date: Sun May 17 10:09:42 2009 Subject: anyone success with matlab 2009a Message-ID: <910e60e80905170248v64dbaa2fw7c0eb60fbec17938@mail.gmail.com> Hi, my boss just gave matlab 2009a dvd and ask me to install it. first i would like to try it in my notebook. my env: %kldstat Id Refs Address Size Name 1 21 0xc0400000 89aa94 kernel 2 1 0xc0c9b000 144e4 geom_journal.ko 3 1 0xc0cb0000 502c acpi_ibm.ko 4 1 0xc55d7000 8000 linprocfs.ko 5 2 0xc566e000 26000 linux.ko 6 1 0xc58ba000 2000 rtc.ko %sysctl -a |grep compat.linux. compat.linux.oss_version: 198144 compat.linux.osrelease: 2.6.16 compat.linux.osname: Linux %cat /etc/make.conf OVERRIDE_LINUX_BASE_PORT=f9 OVERRIDE_LINUX_NONBASE_PORT=f9 %pkg_version -v | grep linux linux-atk-1.9.1_2 = up-to-date with port linux-cairo-1.0.2_1 = up-to-date with port linux-dri-7.4 = up-to-date with port linux-expat-1.95.8_1 = up-to-date with port linux-flashplugin-9.0r159 = up-to-date with port linux-fontconfig-2.2.3_8 = up-to-date with port linux-gtk2-2.6.10_2 = up-to-date with port linux-hicolor-icon-theme-0.5_2 = up-to-date with port linux-jpeg-6b.34_1 = up-to-date with port linux-nvu-1.0_1 = up-to-date with port linux-openmotif-2.2.4_3 = up-to-date with port linux-openssl-0.9.7f_1 = up-to-date with port linux-pango-1.10.2_2 = up-to-date with port linux-png-1.2.8_3 = up-to-date with port linux-realplayer-10.0.9.809.20070726 = up-to-date with port linux-tiff-3.7.1_1 = up-to-date with port linux-xorg-libs-6.8.2_6 = up-to-date with port linux_base-f9-9 = up-to-date with port linuxdoc-1.1_1 = up-to-date with port %mount |grep lin linprocfs on /usr/compat/linux/proc (linprocfs, local) the install script cannot determine root directory. --------------------------------------------------------------------------- Internal error 2: Could not determine the path of the MATLAB root directory. original command path = /home/dikshie/mydisc/install current command path = /home/dikshie/mydisc/install Please contact Mathworks Technical Support for further assistance. ---------------------------------------------------------------------------- any clues? thanks! -- -dikshie- From miwi at FreeBSD.org Sun May 17 10:40:09 2009 From: miwi at FreeBSD.org (miwi@FreeBSD.org) Date: Sun May 17 10:40:17 2009 Subject: ports/91318: graphics/linux_dri: works on amd64 too Message-ID: <200905171040.n4HAe8xG043733@freefall.freebsd.org> Synopsis: graphics/linux_dri: works on amd64 too State-Changed-From-To: open->closed State-Changed-By: miwi State-Changed-When: Sun May 17 10:40:07 UTC 2009 State-Changed-Why: this was committed few years ago. http://www.freebsd.org/cgi/query-pr.cgi?pr=91318 From tijl at ulyssis.org Sun May 17 11:46:02 2009 From: tijl at ulyssis.org (Tijl Coosemans) Date: Sun May 17 11:46:09 2009 Subject: anyone success with matlab 2009a In-Reply-To: <910e60e80905170248v64dbaa2fw7c0eb60fbec17938@mail.gmail.com> References: <910e60e80905170248v64dbaa2fw7c0eb60fbec17938@mail.gmail.com> Message-ID: <200905171343.26892.tijl@ulyssis.org> On Sunday 17 May 2009 11:48:38 dikshie wrote: > Hi, > my boss just gave matlab 2009a dvd and ask me to install it. > first i would like to try it in my notebook. > > my env: > > %kldstat > Id Refs Address Size Name > 1 21 0xc0400000 89aa94 kernel > 2 1 0xc0c9b000 144e4 geom_journal.ko > 3 1 0xc0cb0000 502c acpi_ibm.ko > 4 1 0xc55d7000 8000 linprocfs.ko > 5 2 0xc566e000 26000 linux.ko > 6 1 0xc58ba000 2000 rtc.ko > > %sysctl -a |grep compat.linux. > compat.linux.oss_version: 198144 > compat.linux.osrelease: 2.6.16 > compat.linux.osname: Linux > > %cat /etc/make.conf > OVERRIDE_LINUX_BASE_PORT=f9 > OVERRIDE_LINUX_NONBASE_PORT=f9 There are no linux-f9-* ports. You should use OVERRIDE_LINUX_NONBASE_PORT=f8 Then remove your linux-* ports and install linux-f8-* versions. > %pkg_version -v | grep linux > linux-atk-1.9.1_2 = up-to-date with port > linux-cairo-1.0.2_1 = up-to-date with port > linux-dri-7.4 = up-to-date with port > linux-expat-1.95.8_1 = up-to-date with port > linux-flashplugin-9.0r159 = up-to-date with port > linux-fontconfig-2.2.3_8 = up-to-date with port > linux-gtk2-2.6.10_2 = up-to-date with port > linux-hicolor-icon-theme-0.5_2 = up-to-date with port > linux-jpeg-6b.34_1 = up-to-date with port > linux-nvu-1.0_1 = up-to-date with port > linux-openmotif-2.2.4_3 = up-to-date with port > linux-openssl-0.9.7f_1 = up-to-date with port > linux-pango-1.10.2_2 = up-to-date with port > linux-png-1.2.8_3 = up-to-date with port > linux-realplayer-10.0.9.809.20070726 = up-to-date with port > linux-tiff-3.7.1_1 = up-to-date with port > linux-xorg-libs-6.8.2_6 = up-to-date with port > linux_base-f9-9 = up-to-date with port > linuxdoc-1.1_1 = up-to-date with port > > %mount |grep lin > linprocfs on /usr/compat/linux/proc (linprocfs, local) > > the install script cannot determine root directory. > --------------------------------------------------------------------------- > Internal error 2: Could not determine the path of the > MATLAB root directory. > > original command path = /home/dikshie/mydisc/install > current command path = /home/dikshie/mydisc/install > > Please contact Mathworks Technical Support > for further assistance. > ---------------------------------------------------------------------------- > > any clues? Maybe the install script needs to be run with linux bash. You could try: /compat/linux/bin/sh /home/dikshie/mydisc/install From dikshie at gmail.com Sun May 17 12:11:46 2009 From: dikshie at gmail.com (dikshie) Date: Sun May 17 12:11:52 2009 Subject: anyone success with matlab 2009a In-Reply-To: <200905171343.26892.tijl@ulyssis.org> References: <910e60e80905170248v64dbaa2fw7c0eb60fbec17938@mail.gmail.com> <200905171343.26892.tijl@ulyssis.org> Message-ID: <910e60e80905170511s52e9794fj998b3c2b3d1c0c5b@mail.gmail.com> On Sun, May 17, 2009 at 8:43 PM, Tijl Coosemans wrote: > There are no linux-f9-* ports. You should use > OVERRIDE_LINUX_NONBASE_PORT=f8 there is /usr/ports/emulators/linux_base-f9 should i uninstall that and install linux_base-f8? > Maybe the install script needs to be run with linux bash. You could try: > /compat/linux/bin/sh /home/dikshie/mydisc/install i did it. but i always get: Internal error 2: Could not determine the path of the MATLAB root directory. -- -dikshie- From nox at jelal.kn-bremen.de Sun May 17 13:22:51 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Sun May 17 13:22:59 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: <200905152238.n4FMcqR0007682@triton.kn-bremen.de> References: <20090514191237.GD70242@bsdcrew.de> <200905152238.n4FMcqR0007682@triton.kn-bremen.de> Message-ID: <20090517131939.GA1941@triton.kn-bremen.de> On Sat, May 16, 2009 at 12:38:52AM +0200, Juergen Lock wrote: > In article <06c77d8650448aa63d9ce8d4b1a9c3e0.squirrel@webmail.itac.at> you write: > >On Thu, May 14, 2009 11:51 pm, Artem Belevich wrote: > >> Few more notes from -CURRENT/amd64 > >> > >> [snip] > >> > >> * Attempt to boot new VM (64-bit FreeBSD) from -current snapshot DVD > >> ISO results in an error: > >> > >> Failed to start the virtual machine FreeBSD. > >> Failed to load VMMR0.r0 (VERR_SYMBOL_VALUE_TOO_BIG). > >> Unknown error creating VM (VERR_SYMBOL_VALUE_TOO_BIG). > >> > >> Result Code: NS_ERROR_FAILURE (0x80004005) > >> Component: Console > >> Interface: IConsole {a7f17a42-5b64-488d-977b-4b2c639ada27} > > > > > >I cannot reproduce that anymore (probably hit another problem). Could you > >please provide what the vbox-dev people asked for to solve that problem? > > > >VBox.log from ~/.VirtualBox/Machines//Logs/VBox.log > > > >and start with > > > >export VBOX_LOG=+rt_ldr.e.l2.f > >VirtualBox -startvm VM_NAME > > > Hi! > > You forgot to say this needs a debug build... :) > > >the resulting .log file (created in the current directory!) > > > >http://vbox.innotek.de/pipermail/vbox-dev/2009-May/001411.html > >http://vbox.innotek.de/pipermail/vbox-dev/2009-May/001413.html > > > >Thanks! > > I tried to follow up to that thread on vbox-dev but it seems to be > subscribed-only, so I'll repost here: (-emulation only, I trimmed the > other lists) > > >[...] > > Hi! > > I just tried vbox here and saw the same problem, so I made a debug build > (diff for the wip FreeBSD port Makefile below) and got out the following > logs: > > VBox.log: > > 00:00:03.661 VirtualBox 2.2.51_OSE r19662 freebsd.amd64 (May 15 2009 21:17:12) release log > 00:00:03.661 Log opened 2009-05-15T19:25:52.579924000Z > 00:00:03.661 OS Product: FreeBSD > 00:00:03.661 OS Release: 7.2-STABLE > 00:00:03.661 OS Version: FreeBSD 7.2-STABLE #0: Sun May 10 19:06:01 CEST 2009 nox@triton.kn-bremen.de:/usr/obj/usr/home/nox/src72s/src/sys/TRITON > 00:00:03.661 Executable: /usr/local/lib/virtualbox/VirtualBox > 00:00:03.661 Process ID: 4630 > 00:00:03.661 Package type: BSD_64BITS_GENERIC (OSE) > 00:00:03.706 > 00:00:03.706 !!Assertion Failed!! > 00:00:03.706 Expression: (Elf_Addr)*(int32_t *)pAddrW == Value > 00:00:03.706 Location : /usr/home/nox/vbox/virtualbox/work/virtualbox-2.2.2r19673/src/VBox/Runtime/common/ldr/ldrELFRelocatable.cpp.h(367) int rtldrELF64RelocateSection(RTLDRMODELF64RT_NOTHING*, Elf64_Addr, int (*)(RTLDRMODINTERNAL*, const char*, const char*, unsigned int, RTUINTPTR*, void*), void*, Elf64_Addr, Elf64_Size, const uint8_t*, uint8_t*, const void*, Elf64_Size) > 00:00:03.706 Value=fffffffe80ac87c0 > > 2009-05-15-19-25-48.089-VirtualBox-4630.log: > > Log created: 2009-05-15T19:25:48.898420000Z > Executable: /usr/local/lib/virtualbox/VirtualBox > Arg[0]: VirtualBox > Arg[1]: -startvm > Arg[2]: fbsd72cd > RTLdrOpen: pszFilename=000000080810a040:{/usr/local/lib/virtualbox/VMMR0.r0} fFlags=0x0 enmArch=2 phLdrMod=00007fffffa99b48 > rtldrELF64Open: /usr/local/lib/virtualbox/VMMR0.r0: returns VINF_SUCCESS *phLdrMod=000000080810d080 > rtldrOpenWithReader: /usr/local/lib/virtualbox/VMMR0.r0: returns VINF_SUCCESS *phMod=000000080810d080 > RTLdrOpen: return VINF_SUCCESS *phLdrMod > RTLdrSize: hLdrMod=000000080810d080 > RTLdrSize: returns 1201440 > RTLdrEnumSymbols: hLdrMod=000000080810d080 fFlags=0x0 pvBit=0000000000000000 BaseAddress=0000000000000000 pfnCallback=0000000800f961f0 pvUser=00007fffffa99b30 > RTLdrEnumSymbols: returns VINF_SUCCESS > RTLdrGetBits: hLdrMod=000000080810d080 pvBits=0000000808700068 BaseAddress=fffffffe809df080 pfnGetImport=0000000800f99280 pvUser=00000008020de958 > fffffffe809df4a4: R_X86_64_32S Value=fffffffe80ac87c0 SymValue=fffffffe80ac84c0 > > !!Assertion Failed!! > Expression: (Elf_Addr)*(int32_t *)pAddrW == Value > Location : /usr/home/nox/vbox/virtualbox/work/virtualbox-2.2.2r19673/src/VBox/Runtime/common/ldr/ldrELFRelocatable.cpp.h(367) int rtldrELF64RelocateSection(RTLDRMODELF64RT_NOTHING*, Elf64_Addr, int (*)(RTLDRMODINTERNAL*, const char*, const char*, unsigned int, RTUINTPTR*, void*), void*, Elf64_Addr, Elf64_Size, const uint8_t*, uint8_t*, const void*, Elf64_Size) > Value=fffffffe80ac87c0 > > I suspect BaseAddress=fffffffe809df080 is the problem? Yup it was, as explained in this post: (thanx!) http://vbox.innotek.de/pipermail/vbox-dev/2009-May/001419.html ..and it looks like I now have a workaround for this issue too... :) I'll post the patch when I've finished/cleaned it up a little. I only did some quick tests using a few isos so far (i.e. I did not install anything yet), of which a FreeBSD 7.2rc i386 iso could enter livefs, an i386 and an amd64 sidux 2009-01 iso both booted into kde and could visit their homepage, only a FreeBSD 7.1 amd64 iso hung at the point where the booted kernel should enter userland. Oh and rebooting the i386 FreeBSD iso (exiting sysinstall) caused the vm to abort with an assertion failure, here is the log: 00:00:01.858 VirtualBox 2.2.51_OSE r19662 freebsd.amd64 (May 17 2009 11:32:11) release log 00:00:01.858 Log opened 2009-05-17T12:45:26.521854000Z 00:00:01.858 OS Product: FreeBSD 00:00:01.858 OS Release: 7.2-STABLE 00:00:01.858 OS Version: FreeBSD 7.2-STABLE #0: Sun May 10 19:06:01 CEST 2009 nox@triton.kn-bremen.de:/usr/obj/usr/home/nox/src72s/src/sys/TRITON 00:00:01.858 Executable: /usr/local/lib/virtualbox/VirtualBox 00:00:01.858 Process ID: 2133 00:00:01.858 Package type: BSD_64BITS_GENERIC (OSE) 00:00:01.961 SUP: Loaded VMMR0.r0 (/usr/local/lib/virtualbox/VMMR0.r0) at 0xffffffff80fa7080 - ModuleInit at ffffffff80fddd10 and ModuleTerm at ffffffff80fddc90 00:00:01.961 SUP: VMMR0EntryEx located at ffffffff80fddad0, VMMR0EntryFast at ffffffff80fdc740 and VMMR0EntryInt at ffffffff80fdc530 00:00:02.028 SUPR3HardenedLdrLoadAppPriv: "/usr/local/lib/virtualbox/VBoxSharedClipboard.so" not found 00:00:02.028 HGCM: Failed to load the service library: [VBoxSharedClipboard], rc = VERR_FILE_NOT_FOUND. The service will be not available. 00:00:02.028 VBoxSharedClipboard is not available. rc = VERR_FILE_NOT_FOUND 00:00:02.098 ************************* CFGM dump ************************* 00:00:02.098 pRoot=0000000808108180:{/} 00:00:02.098 [/] (level 0) 00:00:02.098 Name = "fbsd72cd" (cch=9) 00:00:02.098 UUID = "f0 e8 ab f5 f6 b7 18 49 83 cc 56 d2 1b 22 42 ba" (cb=16) 00:00:02.098 RamSize = 0x0000000010000000 (268435456) 00:00:02.098 RamHoleSize = 0x0000000020000000 (536870912) 00:00:02.098 NumCPUs = 0x0000000000000001 (1) 00:00:02.098 TimerMillies = 0x000000000000000a (10) 00:00:02.098 RawR3Enabled = 0x0000000000000001 (1) 00:00:02.098 RawR0Enabled = 0x0000000000000001 (1) 00:00:02.098 PATMEnabled = 0x0000000000000001 (1) 00:00:02.098 CSAMEnabled = 0x0000000000000001 (1) 00:00:02.098 HwVirtExtForced = 0x0000000000000000 (0) 00:00:02.099 EnableNestedPaging = 0x0000000000000001 (1) 00:00:02.099 EnableVPID = 0x0000000000000000 (0) 00:00:02.099 EnablePAE = 0x0000000000000000 (0) 00:00:02.099 00:00:02.099 [/HWVirtExt/] (level 1) 00:00:02.099 Enabled = 0x0000000000000001 (1) 00:00:02.099 00:00:02.099 [/PDM/] (level 1) 00:00:02.099 00:00:02.099 [/PDM/Drivers/] (level 2) 00:00:02.099 00:00:02.099 [/PDM/Drivers/VBoxC/] (level 3) 00:00:02.099 Path = "/usr/local/lib/virtualbox/components/VBoxC" (cch=43) 00:00:02.099 00:00:02.099 [/Devices/] (level 1) 00:00:02.099 00:00:02.099 [/Devices/pcarch/] (level 2) 00:00:02.099 00:00:02.099 [/Devices/pcarch/0/] (level 3) 00:00:02.099 Trusted = 0x0000000000000001 (1) 00:00:02.099 00:00:02.099 [/Devices/pcarch/0/Config/] (level 4) 00:00:02.099 00:00:02.099 [/Devices/pcbios/] (level 2) 00:00:02.099 00:00:02.099 [/Devices/pcbios/0/] (level 3) 00:00:02.099 Trusted = 0x0000000000000001 (1) 00:00:02.099 00:00:02.099 [/Devices/pcbios/0/Config/] (level 4) 00:00:02.099 RamSize = 0x0000000010000000 (268435456) 00:00:02.099 RamHoleSize = 0x0000000020000000 (536870912) 00:00:02.099 NumCPUs = 0x0000000000000001 (1) 00:00:02.099 HardDiskDevice = "piix3ide" (cch=9) 00:00:02.099 FloppyDevice = "i82078" (cch=7) 00:00:02.099 IOAPIC = 0x0000000000000000 (0) 00:00:02.099 PXEDebug = 0x0000000000000000 (0) 00:00:02.099 UUID = "f0 e8 ab f5 f6 b7 18 49 83 cc 56 d2 1b 22 42 ba" (cb=16) 00:00:02.099 BootDevice0 = "FLOPPY" (cch=7) 00:00:02.099 BootDevice1 = "DVD" (cch=4) 00:00:02.099 BootDevice2 = "IDE" (cch=4) 00:00:02.099 BootDevice3 = "NONE" (cch=5) 00:00:02.099 00:00:02.099 [/Devices/8237A/] (level 2) 00:00:02.099 00:00:02.099 [/Devices/8237A/0/] (level 3) 00:00:02.099 Trusted = 0x0000000000000001 (1) 00:00:02.099 00:00:02.099 [/Devices/pci/] (level 2) 00:00:02.099 00:00:02.099 [/Devices/pci/0/] (level 3) 00:00:02.099 Trusted = 0x0000000000000001 (1) 00:00:02.099 00:00:02.099 [/Devices/pci/0/Config/] (level 4) 00:00:02.099 IOAPIC = 0x0000000000000000 (0) 00:00:02.099 00:00:02.099 [/Devices/pckbd/] (level 2) 00:00:02.099 00:00:02.099 [/Devices/pckbd/0/] (level 3) 00:00:02.099 Trusted = 0x0000000000000001 (1) 00:00:02.099 00:00:02.099 [/Devices/pckbd/0/Config/] (level 4) 00:00:02.099 00:00:02.099 [/Devices/pckbd/0/LUN#0/] (level 4) 00:00:02.099 Driver = "KeyboardQueue" (cch=14) 00:00:02.099 00:00:02.099 [/Devices/pckbd/0/LUN#0/Config/] (level 5) 00:00:02.099 QueueSize = 0x0000000000000040 (64) 00:00:02.099 00:00:02.099 [/Devices/pckbd/0/LUN#0/AttachedDriver/] (level 5) 00:00:02.099 Driver = "MainKeyboard" (cch=13) 00:00:02.099 00:00:02.099 [/Devices/pckbd/0/LUN#0/AttachedDriver/Config/] (level 6) 00:00:02.099 Object = 0x00000008056240c0 (34450063552) 00:00:02.099 00:00:02.099 [/Devices/pckbd/0/LUN#1/] (level 4) 00:00:02.099 Driver = "MouseQueue" (cch=11) 00:00:02.099 00:00:02.099 [/Devices/pckbd/0/LUN#1/Config/] (level 5) 00:00:02.099 QueueSize = 0x0000000000000080 (128) 00:00:02.099 00:00:02.099 [/Devices/pckbd/0/LUN#1/AttachedDriver/] (level 5) 00:00:02.099 Driver = "MainMouse" (cch=10) 00:00:02.099 00:00:02.099 [/Devices/pckbd/0/LUN#1/AttachedDriver/Config/] (level 6) 00:00:02.099 Object = 0x00000008056241a0 (34450063776) 00:00:02.099 00:00:02.099 [/Devices/i82078/] (level 2) 00:00:02.099 00:00:02.099 [/Devices/i82078/0/] (level 3) 00:00:02.099 Trusted = 0x0000000000000001 (1) 00:00:02.099 00:00:02.099 [/Devices/i82078/0/Config/] (level 4) 00:00:02.099 IRQ = 0x0000000000000006 (6) 00:00:02.099 DMA = 0x0000000000000002 (2) 00:00:02.099 MemMapped = 0x0000000000000000 (0) 00:00:02.099 IOBase = 0x00000000000003f0 (1008) 00:00:02.099 00:00:02.099 [/Devices/i82078/0/LUN#999/] (level 4) 00:00:02.099 Driver = "MainStatus" (cch=11) 00:00:02.099 00:00:02.099 [/Devices/i82078/0/LUN#999/Config/] (level 5) 00:00:02.099 papLeds = 0x00000008056159b8 (34450004408) 00:00:02.099 First = 0x0000000000000000 (0) 00:00:02.099 Last = 0x0000000000000000 (0) 00:00:02.099 00:00:02.099 [/Devices/i82078/0/LUN#0/] (level 4) 00:00:02.099 Driver = "Block" (cch=6) 00:00:02.099 00:00:02.099 [/Devices/i82078/0/LUN#0/Config/] (level 5) 00:00:02.099 Type = "Floppy 1.44" (cch=12) 00:00:02.099 Mountable = 0x0000000000000001 (1) 00:00:02.099 00:00:02.099 [/Devices/acpi/] (level 2) 00:00:02.099 00:00:02.099 [/Devices/acpi/0/] (level 3) 00:00:02.099 Trusted = 0x0000000000000001 (1) 00:00:02.099 PCIDeviceNo = 0x0000000000000007 (7) 00:00:02.099 PCIFunctionNo = 0x0000000000000000 (0) 00:00:02.099 00:00:02.099 [/Devices/acpi/0/Config/] (level 4) 00:00:02.099 RamSize = 0x0000000010000000 (268435456) 00:00:02.099 RamHoleSize = 0x0000000020000000 (536870912) 00:00:02.099 NumCPUs = 0x0000000000000001 (1) 00:00:02.099 IOAPIC = 0x0000000000000000 (0) 00:00:02.099 FdcEnabled = 0x0000000000000001 (1) 00:00:02.099 ShowRtc = 0x0000000000000000 (0) 00:00:02.099 ShowCpu = 0x0000000000000000 (0) 00:00:02.099 00:00:02.099 [/Devices/acpi/0/LUN#0/] (level 4) 00:00:02.099 Driver = "ACPIHost" (cch=9) 00:00:02.099 00:00:02.099 [/Devices/acpi/0/LUN#0/Config/] (level 5) 00:00:02.099 00:00:02.099 [/Devices/i8254/] (level 2) 00:00:02.099 00:00:02.099 [/Devices/i8254/0/] (level 3) 00:00:02.099 Trusted = 0x0000000000000001 (1) 00:00:02.099 00:00:02.099 [/Devices/i8254/0/Config/] (level 4) 00:00:02.099 00:00:02.099 [/Devices/i8259/] (level 2) 00:00:02.099 00:00:02.099 [/Devices/i8259/0/] (level 3) 00:00:02.099 Trusted = 0x0000000000000001 (1) 00:00:02.099 00:00:02.099 [/Devices/i8259/0/Config/] (level 4) 00:00:02.099 00:00:02.099 [/Devices/apic/] (level 2) 00:00:02.099 00:00:02.099 [/Devices/apic/0/] (level 3) 00:00:02.099 Trusted = 0x0000000000000001 (1) 00:00:02.099 00:00:02.099 [/Devices/apic/0/Config/] (level 4) 00:00:02.099 IOAPIC = 0x0000000000000000 (0) 00:00:02.099 NumCPUs = 0x0000000000000001 (1) 00:00:02.099 00:00:02.099 [/Devices/mc146818/] (level 2) 00:00:02.099 00:00:02.099 [/Devices/mc146818/0/] (level 3) 00:00:02.099 00:00:02.099 [/Devices/mc146818/0/Config/] (level 4) 00:00:02.099 00:00:02.099 [/Devices/vga/] (level 2) 00:00:02.099 00:00:02.099 [/Devices/vga/0/] (level 3) 00:00:02.099 Trusted = 0x0000000000000001 (1) 00:00:02.099 PCIDeviceNo = 0x0000000000000002 (2) 00:00:02.099 PCIFunctionNo = 0x0000000000000000 (0) 00:00:02.099 00:00:02.099 [/Devices/vga/0/Config/] (level 4) 00:00:02.099 VRamSize = 0x0000000000900000 (9437184) 00:00:02.099 FadeIn = 0x0000000000000001 (1) 00:00:02.099 FadeOut = 0x0000000000000001 (1) 00:00:02.099 LogoTime = 0x0000000000000000 (0) 00:00:02.099 LogoFile = "" (cch=1) 00:00:02.099 ShowBootMenu = 0x0000000000000002 (2) 00:00:02.099 CustomVideoModes = 0x0000000000000000 (0) 00:00:02.099 HeightReduction = 0x0000000000000000 (0) 00:00:02.099 00:00:02.099 [/Devices/vga/0/LUN#0/] (level 4) 00:00:02.099 Driver = "MainDisplay" (cch=12) 00:00:02.099 00:00:02.099 [/Devices/vga/0/LUN#0/Config/] (level 5) 00:00:02.099 Object = 0x0000000805616000 (34450006016) 00:00:02.100 00:00:02.100 [/Devices/piix3ide/] (level 2) 00:00:02.100 00:00:02.100 [/Devices/piix3ide/0/] (level 3) 00:00:02.100 Trusted = 0x0000000000000001 (1) 00:00:02.100 PCIDeviceNo = 0x0000000000000001 (1) 00:00:02.100 PCIFunctionNo = 0x0000000000000001 (1) 00:00:02.100 00:00:02.100 [/Devices/piix3ide/0/Config/] (level 4) 00:00:02.100 Type = "PIIX4" (cch=6) 00:00:02.100 00:00:02.100 [/Devices/piix3ide/0/LUN#999/] (level 4) 00:00:02.100 Driver = "MainStatus" (cch=11) 00:00:02.100 00:00:02.100 [/Devices/piix3ide/0/LUN#999/Config/] (level 5) 00:00:02.100 papLeds = 0x00000008056159c8 (34450004424) 00:00:02.100 First = 0x0000000000000000 (0) 00:00:02.100 Last = 0x0000000000000003 (3) 00:00:02.100 00:00:02.100 [/Devices/piix3ide/0/LUN#2/] (level 4) 00:00:02.100 Driver = "Block" (cch=6) 00:00:02.100 00:00:02.100 [/Devices/piix3ide/0/LUN#2/Config/] (level 5) 00:00:02.100 Type = "DVD" (cch=4) 00:00:02.100 Mountable = 0x0000000000000001 (1) 00:00:02.100 00:00:02.100 [/Devices/piix3ide/0/LUN#2/AttachedDriver/] (level 5) 00:00:02.100 Driver = "MediaISO" (cch=9) 00:00:02.100 00:00:02.100 [/Devices/piix3ide/0/LUN#2/AttachedDriver/Config/] (level 6) 00:00:02.100 Path = "/home/nox/iso/fbsd/7.2rc1-i386/7.2-RC1-i386-dvd1.iso" (cch=53) 00:00:02.100 00:00:02.100 [/Devices/pcnet/] (level 2) 00:00:02.100 00:00:02.100 [/Devices/e1000/] (level 2) 00:00:02.100 00:00:02.100 [/Devices/e1000/0/] (level 3) 00:00:02.100 Trusted = 0x0000000000000001 (1) 00:00:02.100 PCIDeviceNo = 0x0000000000000003 (3) 00:00:02.100 PCIFunctionNo = 0x0000000000000000 (0) 00:00:02.100 00:00:02.100 [/Devices/e1000/0/Config/] (level 4) 00:00:02.100 AdapterType = 0x0000000000000000 (0) 00:00:02.100 MAC = "08 00 27 06 a5 43" (cb=6) 00:00:02.100 CableConnected = 0x0000000000000001 (1) 00:00:02.100 LineSpeed = 0x0000000000000000 (0) 00:00:02.100 00:00:02.100 [/Devices/e1000/0/LUN#999/] (level 4) 00:00:02.100 Driver = "MainStatus" (cch=11) 00:00:02.100 00:00:02.100 [/Devices/e1000/0/LUN#999/Config/] (level 5) 00:00:02.100 papLeds = 0x0000000805615b58 (34450004824) 00:00:02.100 00:00:02.100 [/Devices/e1000/0/LUN#0/] (level 4) 00:00:02.100 Driver = "NAT" (cch=4) 00:00:02.100 00:00:02.100 [/Devices/e1000/0/LUN#0/Config/] (level 5) 00:00:02.100 TFTPPrefix = "/home/nox/.VirtualBox/TFTP" (cch=27) 00:00:02.100 BootFile = "fbsd72cd.pxe" (cch=13) 00:00:02.100 00:00:02.100 [/Devices/serial/] (level 2) 00:00:02.100 00:00:02.100 [/Devices/parallel/] (level 2) 00:00:02.100 00:00:02.100 [/Devices/VMMDev/] (level 2) 00:00:02.100 00:00:02.100 [/Devices/VMMDev/0/] (level 3) 00:00:02.100 Trusted = 0x0000000000000001 (1) 00:00:02.100 PCIDeviceNo = 0x0000000000000004 (4) 00:00:02.100 PCIFunctionNo = 0x0000000000000000 (0) 00:00:02.100 00:00:02.100 [/Devices/VMMDev/0/Config/] (level 4) 00:00:02.100 00:00:02.100 [/Devices/VMMDev/0/LUN#0/] (level 4) 00:00:02.100 Driver = "MainVMMDev" (cch=11) 00:00:02.100 00:00:02.100 [/Devices/VMMDev/0/LUN#0/Config/] (level 5) 00:00:02.100 Object = 0x00000008056121c0 (34449990080) 00:00:02.100 00:00:02.100 [/Devices/VMMDev/0/LUN#999/] (level 4) 00:00:02.100 Driver = "MainStatus" (cch=11) 00:00:02.100 00:00:02.100 [/Devices/VMMDev/0/LUN#999/Config/] (level 5) 00:00:02.100 papLeds = 0x0000000805615b98 (34450004888) 00:00:02.100 First = 0x0000000000000000 (0) 00:00:02.100 Last = 0x0000000000000000 (0) 00:00:02.100 00:00:02.100 [/Devices/AudioSniffer/] (level 2) 00:00:02.100 00:00:02.100 [/Devices/AudioSniffer/0/] (level 3) 00:00:02.100 00:00:02.100 [/Devices/AudioSniffer/0/Config/] (level 4) 00:00:02.100 00:00:02.100 [/Devices/AudioSniffer/0/LUN#0/] (level 4) 00:00:02.100 Driver = "MainAudioSniffer" (cch=17) 00:00:02.100 00:00:02.100 [/Devices/AudioSniffer/0/LUN#0/Config/] (level 5) 00:00:02.100 Object = 0x000000080560d300 (34449969920) 00:00:02.100 00:00:02.100 [/Devices/ichac97/] (level 2) 00:00:02.100 00:00:02.100 [/Devices/ichac97/0/] (level 3) 00:00:02.100 Trusted = 0x0000000000000001 (1) 00:00:02.100 PCIDeviceNo = 0x0000000000000005 (5) 00:00:02.100 PCIFunctionNo = 0x0000000000000000 (0) 00:00:02.100 00:00:02.100 [/Devices/ichac97/0/Config/] (level 4) 00:00:02.100 00:00:02.100 [/Devices/ichac97/0/LUN#0/] (level 4) 00:00:02.100 Driver = "AUDIO" (cch=6) 00:00:02.100 00:00:02.100 [/Devices/ichac97/0/LUN#0/Config/] (level 5) 00:00:02.100 AudioDriver = "oss" (cch=4) 00:00:02.100 StreamName = "fbsd72cd" (cch=9) 00:00:02.100 00:00:02.100 [/TM/] (level 1) 00:00:02.100 UTCOffset = 0x0000000000000000 (0) 00:00:02.100 00:00:02.100 ********************* End of CFGM dump ********************** 00:00:02.100 MM: cbHyperHeap=0x140000 (1310720) 00:00:02.102 Logical host processors: 4, processor active mask: 0000000000000001 00:00:02.102 ************************* CPUID dump ************************ 00:00:02.102 RAW Standard CPUIDs 00:00:02.102 Function eax ebx ecx edx 00:00:02.102 Gst: 00000000 00000002 68747541 444d4163 69746e65 00:00:02.102 Hst: 00000005 68747541 444d4163 69746e65 00:00:02.102 Gst: 00000001 00100f42 00000800 00000009 078bf1bf 00:00:02.102 Hst: 00100f42 00040800 00802009 178bfbff 00:00:02.102 Gst: 00000002 00000000 00000000 00000000 00000000 00:00:02.102 Hst: 00000000 00000000 00000000 00000000 00:00:02.102 Gst: 00000003 00000000 00000000 00000000 00000000* 00:00:02.102 Hst: 00000000 00000000 00000000 00000000 00:00:02.102 Gst: 00000004 00000000 00000000 00000000 00000000* 00:00:02.102 Hst: 00000000 00000000 00000000 00000000 00:00:02.102 Gst: 00000005 00000000 00000000 00000000 00000000* 00:00:02.102 Hst: 00000040 00000040 00000003 00000000 00:00:02.102 Name: AuthenticAMD 00:00:02.102 Supports: 0-2 00:00:02.102 Family: 15 Extended: 1 Effective: 16 00:00:02.102 Model: 4 Extended: 0 Effective: 4 00:00:02.102 Stepping: 2 00:00:02.102 APIC ID: 0x00 00:00:02.102 Logical CPUs: 0 00:00:02.102 CLFLUSH Size: 8 00:00:02.102 Brand ID: 0x00 00:00:02.102 Mnemonic - Description = guest (host) 00:00:02.102 FPU - x87 FPU on Chip = 1 (1) 00:00:02.102 VME - Virtual 8086 Mode Enhancements = 1 (1) 00:00:02.102 DE - Debugging extensions = 1 (1) 00:00:02.102 PSE - Page Size Extension = 1 (1) 00:00:02.102 TSC - Time Stamp Counter = 1 (1) 00:00:02.102 MSR - Model Specific Registers = 1 (1) 00:00:02.102 PAE - Physical Address Extension = 0 (1) 00:00:02.102 MCE - Machine Check Exception = 1 (1) 00:00:02.102 CX8 - CMPXCHG8B instruction = 1 (1) 00:00:02.103 APIC - APIC On-Chip = 0 (1) 00:00:02.103 Reserved = 0 (0) 00:00:02.103 SEP - SYSENTER and SYSEXIT = 0 (1) 00:00:02.103 MTRR - Memory Type Range Registers = 1 (1) 00:00:02.103 PGE - PTE Global Bit = 1 (1) 00:00:02.103 MCA - Machine Check Architecture = 1 (1) 00:00:02.103 CMOV - Conditional Move Instructions = 1 (1) 00:00:02.103 PAT - Page Attribute Table = 1 (1) 00:00:02.103 PSE-36 - 36-bit Page Size Extention = 1 (1) 00:00:02.103 PSN - Processor Serial Number = 0 (0) 00:00:02.103 CLFSH - CLFLUSH Instruction. = 1 (1) 00:00:02.103 Reserved = 0 (0) 00:00:02.103 DS - Debug Store = 0 (0) 00:00:02.103 ACPI - Thermal Mon. & Soft. Clock Ctrl.= 0 (0) 00:00:02.103 MMX - Intel MMX Technology = 1 (1) 00:00:02.103 FXSR - FXSAVE and FXRSTOR Instructions = 1 (1) 00:00:02.103 SSE - SSE Support = 1 (1) 00:00:02.103 SSE2 - SSE2 Support = 1 (1) 00:00:02.103 SS - Self Snoop = 0 (0) 00:00:02.103 HTT - Hyper-Threading Technolog = 0 (1) 00:00:02.103 TM - Thermal Monitor = 0 (0) 00:00:02.103 30 - Reserved = 0 (0) 00:00:02.103 PBE - Pending Break Enable = 0 (0) 00:00:02.103 Supports SSE3 or not = 1 (1) 00:00:02.103 Reserved = 0 (0) 00:00:02.103 Supports MONITOR/MWAIT = 1 (1) 00:00:02.103 CPL-DS - CPL Qualified Debug Store = 0 (0) 00:00:02.103 VMX - Virtual Machine Technology = 0 (0) 00:00:02.103 Reserved = 0 (0) 00:00:02.103 Enhanced SpeedStep Technology = 0 (0) 00:00:02.103 Terminal Monitor 2 = 0 (0) 00:00:02.103 Supports Supplemental SSE3 or not = 0 (0) 00:00:02.103 L1 Context ID = 0 (0) 00:00:02.103 Reserved = 0x0 (0x0) 00:00:02.103 CMPXCHG16B = 0 (1) 00:00:02.103 xTPR Update Control = 0 (0) 00:00:02.103 Reserved = 0x0 (0x100) 00:00:02.103 00:00:02.103 RAW Extended CPUIDs 00:00:02.103 Function eax ebx ecx edx 00:00:02.103 Gst: 80000000 80000008 68747541 444d4163 69746e65 00:00:02.103 Hst: 8000001b 68747541 444d4163 69746e65 00:00:02.103 Gst: 80000001 00100f42 10001946 00000000 c383f13f 00:00:02.103 Hst: 00100f42 10001946 000037ff efd3fbff 00:00:02.103 Gst: 80000002 20444d41 6e656850 74286d6f 4920296d 00:00:02.103 Hst: 20444d41 6e656850 74286d6f 4920296d 00:00:02.103 Gst: 80000003 34582049 30323920 6f725020 73736563 00:00:02.103 Hst: 34582049 30323920 6f725020 73736563 00:00:02.103 Gst: 80000004 0000726f 00000000 00000000 00000000 00:00:02.103 Hst: 0000726f 00000000 00000000 00000000 00:00:02.103 Gst: 80000005 ff30ff10 ff30ff20 40020140 40020140 00:00:02.103 Hst: ff30ff10 ff30ff20 40020140 40020140 00:00:02.103 Gst: 80000006 20800000 42004200 02008140 0030b140 00:00:02.103 Hst: 20800000 42004200 02008140 0030b140 00:00:02.103 Gst: 80000007 00000000 00000000 00000000 00000100 00:00:02.103 Hst: 00000000 00000000 00000000 000001f9 00:00:02.103 Gst: 80000008 00003030 00000000 00000000 00000000 00:00:02.103 Hst: 00003030 00000000 00002003 00000000 00:00:02.103 Gst: 80000009 00000000 00000000 00000000 00000000* 00:00:02.103 Hst: 00000000 00000000 00000000 00000000 00:00:02.103 Ext Name: AuthenticAMD 00:00:02.103 Ext Supports: 0x80000000-0x80000008 00:00:02.103 Family: 15 Extended: 1 Effective: 16 00:00:02.103 Model: 4 Extended: 0 Effective: 4 00:00:02.103 Stepping: 2 00:00:02.103 Brand ID: 0x946 00:00:02.103 Mnemonic - Description = guest (host) 00:00:02.103 FPU - x87 FPU on Chip = 1 (1) 00:00:02.103 VME - Virtual 8086 Mode Enhancements = 1 (1) 00:00:02.103 DE - Debugging extensions = 1 (1) 00:00:02.103 PSE - Page Size Extension = 1 (1) 00:00:02.103 TSC - Time Stamp Counter = 1 (1) 00:00:02.103 MSR - K86 Model Specific Registers = 1 (1) 00:00:02.103 PAE - Physical Address Extension = 0 (1) 00:00:02.103 MCE - Machine Check Exception = 0 (1) 00:00:02.103 CX8 - CMPXCHG8B instruction = 1 (1) 00:00:02.103 APIC - APIC On-Chip = 0 (1) 00:00:02.103 10 - Reserved = 0 (0) 00:00:02.103 SEP - SYSCALL and SYSRET = 0 (1) 00:00:02.103 MTRR - Memory Type Range Registers = 1 (1) 00:00:02.103 PGE - PTE Global Bit = 1 (1) 00:00:02.103 MCA - Machine Check Architecture = 1 (1) 00:00:02.103 CMOV - Conditional Move Instructions = 1 (1) 00:00:02.103 PAT - Page Attribute Table = 1 (1) 00:00:02.103 PSE-36 - 36-bit Page Size Extention = 1 (1) 00:00:02.103 18 - Reserved = 0 (0) 00:00:02.103 19 - Reserved = 0 (0) 00:00:02.103 NX - No-Execute Page Protection = 0 (1) 00:00:02.103 DS - Debug Store = 0 (0) 00:00:02.103 AXMMX - AMD Extensions to MMX Instr. = 0 (1) 00:00:02.103 MMX - Intel MMX Technology = 1 (1) 00:00:02.103 FXSR - FXSAVE and FXRSTOR Instructions = 1 (1) 00:00:02.103 25 - AMD fast FXSAVE and FXRSTOR Instr.= 1 (1) 00:00:02.103 26 - 1 GB large page support = 0 (1) 00:00:02.103 27 - RDTSCP instruction = 0 (1) 00:00:02.103 28 - Reserved = 0 (0) 00:00:02.103 29 - AMD Long Mode = 0 (1) 00:00:02.103 30 - AMD Extensions to 3DNow = 1 (1) 00:00:02.103 31 - AMD 3DNow = 1 (1) 00:00:02.103 LahfSahf - LAHF/SAHF in 64-bit mode = 0 (1) 00:00:02.103 CmpLegacy - Core MP legacy mode (depr) = 0 (1) 00:00:02.103 SVM - AMD VM Extensions = 0 (1) 00:00:02.103 APIC registers starting at 0x400 = 0 (1) 00:00:02.103 AltMovCR8 - LOCK MOV CR0 means MOV CR8 = 0 (1) 00:00:02.103 Advanced bit manipulation = 0 (1) 00:00:02.103 SSE4A instruction support = 0 (1) 00:00:02.103 Misaligned SSE mode = 0 (1) 00:00:02.103 PREFETCH and PREFETCHW instruction = 0 (1) 00:00:02.103 OS visible workaround = 0 (1) 00:00:02.103 Instruction based sampling = 0 (1) 00:00:02.103 SSE5 support = 0 (0) 00:00:02.103 SKINIT, STGI, and DEV support = 0 (1) 00:00:02.103 Watchdog timer support. = 0 (1) 00:00:02.103 31:14 - Reserved = 0x0 (0x0) 00:00:02.103 Full Name: AMD Phenom(tm) II X4 920 Processor 00:00:02.103 TLB 2/4M Instr/Uni: 255 way 16 entries 00:00:02.103 TLB 2/4M Data: 255 way 48 entries 00:00:02.103 TLB 4K Instr/Uni: 255 way 32 entries 00:00:02.103 TLB 4K Data: 255 way 48 entries 00:00:02.103 L1 Instr Cache Line Size: 64 bytes 00:00:02.103 L1 Instr Cache Lines Per Tag: 1 00:00:02.103 L1 Instr Cache Associativity: 2 way 00:00:02.103 L1 Instr Cache Size: 64 KB 00:00:02.103 L1 Data Cache Line Size: 64 bytes 00:00:02.103 L1 Data Cache Lines Per Tag: 1 00:00:02.103 L1 Data Cache Associativity: 2 way 00:00:02.103 L1 Data Cache Size: 64 KB 00:00:02.103 L2 TLB 2/4M Instr/Uni: off 0 entries 00:00:02.103 L2 TLB 2/4M Data: 2 way 128 entries 00:00:02.103 L2 TLB 4K Instr/Uni: 4 way 512 entries 00:00:02.103 L2 TLB 4K Data: 4 way 512 entries 00:00:02.103 L2 Cache Line Size: 64 bytes 00:00:02.103 L2 Cache Lines Per Tag: 1 00:00:02.103 L2 Cache Associativity: res11 00:00:02.103 L2 Cache Size: 48 KB 00:00:02.103 APM Features: 8 00:00:02.103 Physical Address Width: 48 bits 00:00:02.103 Virtual Address Width: 48 bits 00:00:02.103 Physical Core Count: 0 00:00:02.103 00:00:02.103 RAW Centaur CPUIDs 00:00:02.103 Function eax ebx ecx edx 00:00:02.103 Gst: c0000000 00000000 00000000 00000000 00000000 00:00:02.103 Hst: 00000000 00000000 00000000 00000000 00:00:02.103 Gst: c0000001 00000000 00000000 00000000 00000000* 00:00:02.103 Hst: 00000000 00000000 00000000 00000000 00:00:02.103 Gst: c0000002 00000000 00000000 00000000 00000000* 00:00:02.103 Hst: 00000000 00000000 00000000 00000000 00:00:02.103 Gst: c0000003 00000000 00000000 00000000 00000000* 00:00:02.103 Hst: 00000000 00000000 00000000 00000000 00:00:02.103 Centaur Supports: 0xc0000000-0x00000000 00:00:02.103 00:00:02.103 ******************** End of CPUID dump ********************** 00:00:02.115 Debug: HCPhysInterPD=000000002e7c7000 HCPhysInterPaePDPT=000000002e7ca000 HCPhysInterPaePML4=000000002e7cc000 00:00:02.115 Debug: apInterPTs={000000002e7c8000,000000002e7c9000} apInterPaePTs={000000002e7c6000,000000002e7e7000} apInterPaePDs={000000002e7e8000,000000002e7e9000,000000002e7ea000,000000002e7eb000} pInterPaePDPT64=000000002e7cb000 00:00:02.254 TM: GIP - u32Mode=1 (SyncTSC) u32UpdateHz=100 00:00:02.286 TM: cTSCTicksPerSecond=0xa7ae0eb4 (2813202100) fTSCVirtualized=true fTSCUseRealTSC=false 00:00:02.286 TM: fMaybeUseOffsettedHostTSC=true TSCTiedToExecution=false TSCNotTiedToHalt=false 00:00:02.292 CoreCode: R3=0000000800dfa000 R0=ffffffff0a742000 RC=a02ab000 Phys=0000000028370000 cb=0x2000 00:00:02.385 [SMP] BIOS with 1 CPUs 00:00:02.482 SUP: Loaded VBoxDDR0.r0 (/usr/local/lib/virtualbox/VBoxDDR0.r0) at 0xffffffff810d6080 - ModuleInit at 0000000000000000 and ModuleTerm at 0000000000000000 00:00:02.509 SUP: Loaded VBoxDD2R0.r0 (/usr/local/lib/virtualbox/VBoxDD2R0.r0) at 0xffffffff810f4080 - ModuleInit at 0000000000000000 and ModuleTerm at 0000000000000000 00:00:02.509 Activating Local APIC 00:00:02.509 CPUMSetGuestCpuIdFeature: Enabled APIC 00:00:02.509 CPUMSetGuestCpuIdFeature: Disabled x2APIC 00:00:02.510 PIT: mode=3 count=0x10000 (65536) - 18.20 Hz (ch=0) 00:00:02.526 Shared Folders service loaded. 00:00:02.549 PIIX3 ATA: LUN#0: no unit 00:00:02.549 PIIX3 ATA: LUN#1: no unit 00:00:02.550 PIIX3 ATA: LUN#2: CD/DVD, total number of sectors 1099203, passthrough disabled 00:00:02.550 PIIX3 ATA: LUN#3: no unit 00:00:02.550 PIIX3 ATA: Ctl#0: finished processing RESET 00:00:02.650 PIIX3 ATA: Ctl#1: finished processing RESET 00:00:02.753 NAT: ICMP/ping not available (could open ICMP socket, error VERR_ACCESS_DENIED) 00:00:02.753 NAT: adding domain name kn-bremen.de to search list 00:00:02.753 Audio: Trying driver 'oss'. 00:00:02.753 Audio: set_record_source ars=0 als=0 (not implemented) 00:00:02.755 OSS: Successfully opened /dev/dsp for ADC 00:00:02.758 OSS: Successfully opened /dev/dsp for DAC 00:00:03.029 PGMR3InitFinalize: 4 MB PSE mask 0000000fffffffff 00:00:03.069 HWACMM: cpuid 0x80000001.u32AMDFeatureECX = 37ff 00:00:03.069 HWACMM: cpuid 0x80000001.u32AMDFeatureEDX = efd3fbff 00:00:03.069 HWACCM: AMD-V revision = 1 00:00:03.069 HWACCM: AMD-V max ASID = 64 00:00:03.069 HWACCM: AMD-V features = F 00:00:03.069 HWACCM: AMD_CPUID_SVM_FEATURE_EDX_NESTED_PAGING 00:00:03.069 HWACCM: AMD_CPUID_SVM_FEATURE_EDX_LBR_VIRT 00:00:03.069 HWACCM: AMD_CPUID_SVM_FEATURE_EDX_SVM_LOCK 00:00:03.069 HWACCM: AMD_CPUID_SVM_FEATURE_EDX_NRIP_SAVE 00:00:03.069 HWACCM: Enabled nested paging 00:00:03.081 CPUMSetGuestCpuIdFeature: Enabled sysenter/exit 00:00:03.081 CPUMSetGuestCpuIdFeature: Enabled syscall/ret 00:00:03.081 CPUMSetGuestCpuIdFeature: Enabled RDTSCP. 00:00:03.081 CPUMSetGuestCpuIdFeature: Enabled PAE 00:00:03.081 CPUMSetGuestCpuIdFeature: Enabled LONG MODE 00:00:03.081 CPUMSetGuestCpuIdFeature: Enabled NXE 00:00:03.081 CPUMSetGuestCpuIdFeature: Enabled LAHF/SAHF 00:00:03.081 HWACCM: 32-bit and 64-bit guest supported. 00:00:03.112 VM: Halt method global1 (5) 00:00:03.112 Changing the VM state from 'CREATING' to 'CREATED'. 00:00:03.112 Changing the VM state from 'CREATED' to 'RUNNING'. 00:00:03.127 Guest Log: BIOS: VirtualBox 2.2.51_OSE 00:00:03.127 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0) 00:00:03.177 PIIX3 ATA: Ctl#1: RESET, DevSel=0 AIOIf=0 CmdIf0=0x00 (-1 usec ago) CmdIf1=0x00 (-1 usec ago) 00:00:03.177 PIIX3 ATA: Ctl#1: finished processing RESET 00:00:03.198 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 00:00:03.205 Guest Log: BIOS: Boot from Floppy 0 failed 00:00:03.231 Guest Log: BIOS: Booting from CD-ROM... 00:00:03.300 Guest Log: BIOS: int13_diskette: unsupported AH=41 00:00:03.308 Guest Log: BIOS: int13_harddisk: function 08, unmapped device for ELDL=80 00:00:08.678 Guest Log: BIOS: int13_harddisk: function 08, unmapped device for ELDL=80 00:00:08.679 Guest Log: BIOS: int13_harddisk: function 08, unmapped device for ELDL=81 00:00:08.680 Guest Log: BIOS: int13_harddisk: function 08, unmapped device for ELDL=82 00:00:08.680 Guest Log: BIOS: int13_harddisk: function 08, unmapped device for ELDL=83 00:00:08.681 Guest Log: BIOS: int13_harddisk: function 08, unmapped device for ELDL=84 00:00:08.681 Guest Log: BIOS: int13_harddisk: function 08, unmapped device for ELDL=85 00:00:08.682 Guest Log: BIOS: int13_harddisk: function 08, unmapped device for ELDL=86 00:00:08.683 Guest Log: BIOS: int13_harddisk: function 08, unmapped device for ELDL=87 00:00:08.683 PIT: mode=2 count=0x4a9 (1193) - 1000.15 Hz (ch=0) 00:00:12.777 PIIX3 ATA: Ctl#0: RESET, DevSel=0 AIOIf=0 CmdIf0=0x00 (-1 usec ago) CmdIf1=0x00 (-1 usec ago) 00:00:12.782 PIIX3 ATA: Ctl#0: finished processing RESET 00:00:12.859 PIIX3 ATA: Ctl#1: RESET, DevSel=0 AIOIf=0 CmdIf0=0xa0 (-1 usec ago) CmdIf1=0x00 (-1 usec ago) 00:00:12.865 PIIX3 ATA: Ctl#1: finished processing RESET 00:00:15.691 PIIX3 ATA: LUN#2: performing device RESET 00:01:52.514 Changing the VM state from 'RUNNING' to 'RESETTING'. 00:01:52.514 00:01:52.514 !!Assertion Failed!! 00:01:52.514 Expression: pVCpu->pgm.s.pShwPageCR3R3 == NULL 00:01:52.514 Location : /usr/home/nox/vbox/virtualbox/work/virtualbox-2.2.2r19673/src/VBox/VMM/PGM.cpp(4075) int pgmR3ExitShadowModeBeforePoolFlush(VM*, VMCPU*) From nox at jelal.kn-bremen.de Sun May 17 16:54:11 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Sun May 17 16:54:19 2009 Subject: vbox amd64 host patch (was: Re: [Call For Testing] VirtualBox for FreeBSD!) In-Reply-To: <20090517131939.GA1941@triton.kn-bremen.de> References: <20090514191237.GD70242@bsdcrew.de> <200905152238.n4FMcqR0007682@triton.kn-bremen.de> <20090517131939.GA1941@triton.kn-bremen.de> Message-ID: <20090517165206.GA3068@triton.kn-bremen.de> On Sun, May 17, 2009 at 03:19:39PM +0200, Juergen Lock wrote: > On Sat, May 16, 2009 at 12:38:52AM +0200, Juergen Lock wrote: > > In article <06c77d8650448aa63d9ce8d4b1a9c3e0.squirrel@webmail.itac.at> you write: > > >On Thu, May 14, 2009 11:51 pm, Artem Belevich wrote: > > >> Few more notes from -CURRENT/amd64 > > >> > > >> [snip] > > >> > > >> * Attempt to boot new VM (64-bit FreeBSD) from -current snapshot DVD > > >> ISO results in an error: > > >> > > >> Failed to start the virtual machine FreeBSD. > > >> Failed to load VMMR0.r0 (VERR_SYMBOL_VALUE_TOO_BIG). > > >> Unknown error creating VM (VERR_SYMBOL_VALUE_TOO_BIG). > > >> > > >> Result Code: NS_ERROR_FAILURE (0x80004005) > > >> Component: Console > > >> Interface: IConsole {a7f17a42-5b64-488d-977b-4b2c639ada27} > > > > > > > > >I cannot reproduce that anymore (probably hit another problem). Could you > > >please provide what the vbox-dev people asked for to solve that problem? > > > > > >VBox.log from ~/.VirtualBox/Machines//Logs/VBox.log > > > > > >and start with > > > > > >export VBOX_LOG=+rt_ldr.e.l2.f > > >VirtualBox -startvm VM_NAME > > > > > Hi! > > > > You forgot to say this needs a debug build... :) > > > > >the resulting .log file (created in the current directory!) > > > > > >http://vbox.innotek.de/pipermail/vbox-dev/2009-May/001411.html > > >http://vbox.innotek.de/pipermail/vbox-dev/2009-May/001413.html > > > > > >Thanks! > > > > I tried to follow up to that thread on vbox-dev but it seems to be > > subscribed-only, so I'll repost here: (-emulation only, I trimmed the > > other lists) > > > > >[...] > > > > Hi! > > > > I just tried vbox here and saw the same problem, so I made a debug build > > (diff for the wip FreeBSD port Makefile below) and got out the following > > logs: > > > > VBox.log: > > > > 00:00:03.661 VirtualBox 2.2.51_OSE r19662 freebsd.amd64 (May 15 2009 21:17:12) release log > > 00:00:03.661 Log opened 2009-05-15T19:25:52.579924000Z > > 00:00:03.661 OS Product: FreeBSD > > 00:00:03.661 OS Release: 7.2-STABLE > > 00:00:03.661 OS Version: FreeBSD 7.2-STABLE #0: Sun May 10 19:06:01 CEST 2009 nox@triton.kn-bremen.de:/usr/obj/usr/home/nox/src72s/src/sys/TRITON > > 00:00:03.661 Executable: /usr/local/lib/virtualbox/VirtualBox > > 00:00:03.661 Process ID: 4630 > > 00:00:03.661 Package type: BSD_64BITS_GENERIC (OSE) > > 00:00:03.706 > > 00:00:03.706 !!Assertion Failed!! > > 00:00:03.706 Expression: (Elf_Addr)*(int32_t *)pAddrW == Value > > 00:00:03.706 Location : /usr/home/nox/vbox/virtualbox/work/virtualbox-2.2.2r19673/src/VBox/Runtime/common/ldr/ldrELFRelocatable.cpp.h(367) int rtldrELF64RelocateSection(RTLDRMODELF64RT_NOTHING*, Elf64_Addr, int (*)(RTLDRMODINTERNAL*, const char*, const char*, unsigned int, RTUINTPTR*, void*), void*, Elf64_Addr, Elf64_Size, const uint8_t*, uint8_t*, const void*, Elf64_Size) > > 00:00:03.706 Value=fffffffe80ac87c0 > > > > 2009-05-15-19-25-48.089-VirtualBox-4630.log: > > > > Log created: 2009-05-15T19:25:48.898420000Z > > Executable: /usr/local/lib/virtualbox/VirtualBox > > Arg[0]: VirtualBox > > Arg[1]: -startvm > > Arg[2]: fbsd72cd > > RTLdrOpen: pszFilename=000000080810a040:{/usr/local/lib/virtualbox/VMMR0.r0} fFlags=0x0 enmArch=2 phLdrMod=00007fffffa99b48 > > rtldrELF64Open: /usr/local/lib/virtualbox/VMMR0.r0: returns VINF_SUCCESS *phLdrMod=000000080810d080 > > rtldrOpenWithReader: /usr/local/lib/virtualbox/VMMR0.r0: returns VINF_SUCCESS *phMod=000000080810d080 > > RTLdrOpen: return VINF_SUCCESS *phLdrMod > > RTLdrSize: hLdrMod=000000080810d080 > > RTLdrSize: returns 1201440 > > RTLdrEnumSymbols: hLdrMod=000000080810d080 fFlags=0x0 pvBit=0000000000000000 BaseAddress=0000000000000000 pfnCallback=0000000800f961f0 pvUser=00007fffffa99b30 > > RTLdrEnumSymbols: returns VINF_SUCCESS > > RTLdrGetBits: hLdrMod=000000080810d080 pvBits=0000000808700068 BaseAddress=fffffffe809df080 pfnGetImport=0000000800f99280 pvUser=00000008020de958 > > fffffffe809df4a4: R_X86_64_32S Value=fffffffe80ac87c0 SymValue=fffffffe80ac84c0 > > > > !!Assertion Failed!! > > Expression: (Elf_Addr)*(int32_t *)pAddrW == Value > > Location : /usr/home/nox/vbox/virtualbox/work/virtualbox-2.2.2r19673/src/VBox/Runtime/common/ldr/ldrELFRelocatable.cpp.h(367) int rtldrELF64RelocateSection(RTLDRMODELF64RT_NOTHING*, Elf64_Addr, int (*)(RTLDRMODINTERNAL*, const char*, const char*, unsigned int, RTUINTPTR*, void*), void*, Elf64_Addr, Elf64_Size, const uint8_t*, uint8_t*, const void*, Elf64_Size) > > Value=fffffffe80ac87c0 > > > > I suspect BaseAddress=fffffffe809df080 is the problem? > > Yup it was, as explained in this post: (thanx!) > http://vbox.innotek.de/pipermail/vbox-dev/2009-May/001419.html > > ..and it looks like I now have a workaround for this issue too... :) > I'll post the patch when I've finished/cleaned it up a little. > > I only did some quick tests using a few isos so far (i.e. I did not > install anything yet), of which a FreeBSD 7.2rc i386 iso could enter > livefs, an i386 and an amd64 sidux 2009-01 iso both booted into kde and > could visit their homepage, only a FreeBSD 7.1 amd64 iso hung at the > point where the booted kernel should enter userland. [...] ..and that was just because io-apic was disabled for some reason. Anyway, I think I have done what was most necessary to the patch now, it sure does not yet conform to vbox' style (that one is just _too_ different... :) - but at least it seems to do what it's supposed to. Oh, its possible there's still a vm_object_deallocate() missing after vm_map_remove(), but the code I used as guideline (in /sys/kern/link_elf_obj.c) doesn't do one at that stage either so I was not sure. Anyway, here it comes, you can put it in files/patch-amd64-r0-exec-alloc Enjoy, Juergen Index: src/VBox/Runtime/r0drv/alloc-r0drv.h @@ -50,6 +50,8 @@ uint32_t cb; /** The request allocation size. */ uint32_t cbReq; + /** XXX to be used by the FreeBSD/amd64 implementation. */ + void *opaque; } RTMEMHDR, *PRTMEMHDR; Index: src/VBox/Runtime/r0drv/freebsd/alloc-r0drv-freebsd.c @@ -48,12 +48,22 @@ MALLOC_DEFINE(M_IPRTHEAP, "iprtheap", "IPRT - heap"); MALLOC_DEFINE(M_IPRTCONT, "iprtcont", "IPRT - contiguous"); +#if defined(RT_ARCH_AMD64) || defined(__DOXYGEN__) +PRTMEMHDR malloc32(unsigned long size, struct malloc_type *mtp, int flags); +void free32(PRTMEMHDR pHdr, struct malloc_type *mtp); +#endif /* defined(RT_ARCH_AMD64) || defined(__DOXYGEN__) */ PRTMEMHDR rtMemAlloc(size_t cb, uint32_t fFlags) { PRTMEMHDR pHdr; /** @todo Just like OS/2, FreeBSD doesn't need this header. */ + /* XXX actually its needed on amd64 for now... */ +#if defined(RT_ARCH_AMD64) || defined(__DOXYGEN__) + if (fFlags == RTMEMHDR_FLAG_EXEC) { + pHdr = malloc32(cb + sizeof(RTMEMHDR), M_IPRTHEAP, M_ZERO); + } else +#endif pHdr = (PRTMEMHDR)malloc(cb + sizeof(RTMEMHDR), M_IPRTHEAP, fFlags & RTMEMHDR_FLAG_ZEROED ? M_NOWAIT | M_ZERO : M_NOWAIT); if (pHdr) @@ -71,6 +81,12 @@ void rtMemFree(PRTMEMHDR pHdr) { pHdr->u32Magic += 1; +#if defined(RT_ARCH_AMD64) || defined(__DOXYGEN__) + if (pHdr->fFlags == RTMEMHDR_FLAG_EXEC) { + free32(pHdr, M_IPRTHEAP); + return; + } +#endif free(pHdr, M_IPRTHEAP); } @@ -114,3 +130,61 @@ } } +#if defined(RT_ARCH_AMD64) || defined(__DOXYGEN__) +/* see 7.2-stable /sys/kern/link_elf_obj.c:link_elf_load_file() + */ +PRTMEMHDR +malloc32(unsigned long size, struct malloc_type *mtp, int flags) +{ + vm_object_t object; /* VM object to hold data */ + vm_offset_t mapbase; + int error = 0; + + size = roundup(size, PAGE_SIZE); + object = vm_object_allocate(OBJT_DEFAULT, size >> PAGE_SHIFT); + if (object == NULL) + return (0); + + /* + * In order to satisfy amd64's architectural requirements on the + * location of code and data in the kernel's address space, request a + * mapping that is above the kernel. + */ + mapbase = KERNBASE; + error = vm_map_find(kernel_map, object, 0, &mapbase, + size, TRUE, VM_PROT_ALL, VM_PROT_ALL, FALSE); + if (error) { + vm_object_deallocate(object); + object = 0; + return (0); + } + + /* Wire the pages */ + error = vm_map_wire(kernel_map, mapbase, + mapbase + size, + VM_MAP_WIRE_SYSTEM|VM_MAP_WIRE_NOHOLES); + if (error != KERN_SUCCESS) { + return (0); + } + if (flags & M_ZERO) + memset((void *)mapbase, 0, size); + + /* XXX need to store the vm_object_t somewhere... */ + ((PRTMEMHDR)mapbase)->opaque = (void *)object; + return ((PRTMEMHDR)mapbase); +} + +/* see 7.2-stable /sys/kern/link_elf_obj.c:link_elf_unload_file() + */ +void +free32(PRTMEMHDR pHdr, struct malloc_type *mtp) +{ + vm_object_t object = (vm_object_t)pHdr->opaque; + + if (object) { + vm_map_remove(kernel_map, (vm_offset_t) pHdr, + ((vm_offset_t) pHdr) + + (object->size << PAGE_SHIFT)); + } +} +#endif From miwi at FreeBSD.org Sun May 17 18:09:26 2009 From: miwi at FreeBSD.org (Martin Wilke) Date: Sun May 17 18:09:43 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: <20090514191237.GD70242@bsdcrew.de> References: <20090514191237.GD70242@bsdcrew.de> Message-ID: <20090517180920.GY71804@bsdcrew.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 We rolled a new tarball with the patch from Juergen Lock [1] with a posible fix for AMD64 users, tested on 3 machines which now works without problems. Many Thanks to him for his nice work! http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz Martin - -- +-----------------------+-------------------------------+ | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | | ICQ : 169139903 | Mail : miwi(at)FreeBSD.org | +-----------------------+-------------------------------+ | Mess with the Best, Die like the Rest! | +-----------------------+-------------------------------+ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) iEUEARECAAYFAkoQUtAACgkQdLJIhLHm/OlY2QCg1KZW2YCvE1VhqKgSQ/xhjKIx U60Al2UMniKg+KvQ6m9RcP92eOMddfQ= =kB6c -----END PGP SIGNATURE----- From sfourman at gmail.com Sun May 17 19:10:49 2009 From: sfourman at gmail.com (Sam Fourman Jr.) Date: Sun May 17 19:10:55 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: <20090517180920.GY71804@bsdcrew.de> References: <20090514191237.GD70242@bsdcrew.de> <20090517180920.GY71804@bsdcrew.de> Message-ID: <11167f520905171210t2c5c2623o386f00745b4f9aed@mail.gmail.com> On Sun, May 17, 2009 at 1:09 PM, Martin Wilke wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > We rolled a new tarball with the patch from Juergen Lock [1] > with a posible fix for AMD64 users, tested on 3 machines > which now works without problems. Many Thanks to him for > his nice work! > > http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz > > Martin Does this version still have the kernel module crashing at random on current? Sam Fourman Jr. From Benoit.Calvez at gmail.com Sun May 17 20:07:15 2009 From: Benoit.Calvez at gmail.com (Benoit Calvez) Date: Sun May 17 20:07:27 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: <11167f520905171210t2c5c2623o386f00745b4f9aed@mail.gmail.com> References: <20090514191237.GD70242@bsdcrew.de> <20090517180920.GY71804@bsdcrew.de> <11167f520905171210t2c5c2623o386f00745b4f9aed@mail.gmail.com> Message-ID: <3481d8e60905171306n35904a6boc74eed344505cb13@mail.gmail.com> On Sun, May 17, 2009 at 9:10 PM, Sam Fourman Jr. wrote: > On Sun, May 17, 2009 at 1:09 PM, Martin Wilke wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > > > We rolled a new tarball with the patch from Juergen Lock [1] > > with a posible fix for AMD64 users, tested on 3 machines > > which now works without problems. Many Thanks to him for > > his nice work! > > > > http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz > > > > Martin > > Does this version still have the kernel module crashing at random on > current? > > Sam Fourman Jr. > _______________________________________________ > 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" > I uninstalled the last virtualbox (from virtualbox_1.tgz port). It compiled fine and I could start an opensolaris vm. It crashed cauz' I created the virtual hard drive in a smal partition. Since then I couldn't restart the vm. I got two Errors: "Kernel driver not instaled (rc =-1908) "Make sure the kernel module has beed loaded successfully" Sure it is. the other one is : Result Code: NS_ERROR_FAILURE (0x80004005) Component: Machine Interface: IMachine {4d1df26d-d9c1-4c7e-b689-15e85ecf8ffc} I could give more informations if needed -- Benoit C. From jahnke at sonatabio.com Sun May 17 20:30:19 2009 From: jahnke at sonatabio.com (Frank Jahnke) Date: Sun May 17 20:30:25 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! Message-ID: <1242591163.11490.17.camel@zinfandel> > Now we think that we solved the most > problems and are ready for the first Call for Testing. Thank you for this. I have installed W2K Server on i386 7-STABLE system without major heartache. It does not work for me when I am not root, which causes some minor inconvenience. Otherwise all the updates so loved by Microsoft installed fine, and the VM itself seems to function properly. Speed seems to be much better than qemu/kqemu, but slower than the old VMware port (though that is really a pain to use these days since it is limited to single core CPUs only). Are there plans to do a port of the Guest Additions? Right now the resolution and bit depth are limited to 800x600, 16 bits, and that really limits its usefulness. Of course you are starting in the right place: without a stable port the additions are not of any particular use. Frank From freebsd at byshenk.net Mon May 18 00:25:31 2009 From: freebsd at byshenk.net (Greg Byshenk) Date: Mon May 18 00:25:44 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: <20090517180920.GY71804@bsdcrew.de> References: <20090514191237.GD70242@bsdcrew.de> <20090517180920.GY71804@bsdcrew.de> Message-ID: <20090518002528.GF2571@core.byshenk.net> On Sun, May 17, 2009 at 08:09:20PM +0200, Martin Wilke wrote: > > We rolled a new tarball with the patch from Juergen Lock [1] > with a posible fix for AMD64 users, tested on 3 machines > which now works without problems. Many Thanks to him for > his nice work! > > http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz I've just updated my system (to 7-STABLE amd64 as of today) and installed the new version. It runs for me now. Tomorrow I will try to create virtual machine. -- greg byshenk - gbyshenk@byshenk.net - Leiden, NL From sfourman at gmail.com Mon May 18 00:37:31 2009 From: sfourman at gmail.com (Sam Fourman Jr.) Date: Mon May 18 00:37:37 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: <20090518002528.GF2571@core.byshenk.net> References: <20090514191237.GD70242@bsdcrew.de> <20090517180920.GY71804@bsdcrew.de> <20090518002528.GF2571@core.byshenk.net> Message-ID: <11167f520905171737q4f19a359id6b1af11e10d5184@mail.gmail.com> On Sun, May 17, 2009 at 7:25 PM, Greg Byshenk wrote: > On Sun, May 17, 2009 at 08:09:20PM +0200, Martin Wilke wrote: >> >> We rolled a new tarball with the patch from Juergen Lock [1] >> with a posible fix for AMD64 users, tested on 3 machines >> which now works without problems. Many Thanks to him for >> his nice work! >> >> http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz Does the FreeBSD version have USB passthrough support like Linux? Sam Fourman From freebsd at byshenk.net Mon May 18 00:50:57 2009 From: freebsd at byshenk.net (Greg Byshenk) Date: Mon May 18 00:51:03 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: <20090518002528.GF2571@core.byshenk.net> References: <20090514191237.GD70242@bsdcrew.de> <20090517180920.GY71804@bsdcrew.de> <20090518002528.GF2571@core.byshenk.net> Message-ID: <20090518005054.GG2571@core.byshenk.net> On Mon, May 18, 2009 at 02:25:28AM +0200, Greg Byshenk wrote: > On Sun, May 17, 2009 at 08:09:20PM +0200, Martin Wilke wrote: > > > > We rolled a new tarball with the patch from Juergen Lock [1] > > with a posible fix for AMD64 users, tested on 3 machines > > which now works without problems. Many Thanks to him for > > his nice work! > > > > http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz > I've just updated my system (to 7-STABLE amd64 as of today) and > installed the new version. It runs for me now. Tomorrow I will > try to create virtual machine. As a followup, the 'virtualbox_2.tgz' version appears to work for me, at least minimally. I've just installed NetBSD4.1 virtual machine, and it appears to be working (even though NetBSD isn't listed as a supported guest -- I just happened to have the NetBSD install iso sitting on my hard drive). -- greg byshenk - gbyshenk@byshenk.net - Leiden, NL From glen.j.barber at gmail.com Mon May 18 01:07:55 2009 From: glen.j.barber at gmail.com (Glen Barber) Date: Mon May 18 01:08:07 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: <20090517180920.GY71804@bsdcrew.de> References: <20090514191237.GD70242@bsdcrew.de> <20090517180920.GY71804@bsdcrew.de> Message-ID: <4ad871310905171741t55611cf7vc96e0086a371052@mail.gmail.com> On Sun, May 17, 2009 at 2:09 PM, Martin Wilke wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > We rolled a new tarball with the patch from Juergen Lock [1] > with a posible fix for AMD64 users, tested on 3 machines > which now works without problems. Many Thanks to him for > his nice work! > Is there need for the i386 folks to rebuild, or does it only affect amd64? -- Glen Barber From bugmaster at FreeBSD.org Mon May 18 11:06:51 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon May 18 11:07:47 2009 Subject: Current problem reports assigned to freebsd-emulation@FreeBSD.org Message-ID: <200905181106.n4IB6oxA075615@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/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/91293 emulation [svr4] [patch] *Experimental* Update to the SVR4 emula 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 14 problems total. From f0andrey at gmail.com Mon May 18 11:53:42 2009 From: f0andrey at gmail.com (Andrey Fesenko) Date: Mon May 18 11:53:54 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: <20090517180920.GY71804@bsdcrew.de> References: <20090514191237.GD70242@bsdcrew.de> <20090517180920.GY71804@bsdcrew.de> Message-ID: <19e7832a0905180428l564f4e74s9d8ce3213228b08e@mail.gmail.com> On Sun, May 17, 2009 at 10:09 PM, Martin Wilke wrote: > > We rolled a new tarball with the patch from Juergen Lock [1] > with a posible fix for AMD64 users, tested on 3 machines > which now works without problems. Many Thanks to him for > his nice work! > > http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz > > Martin > FreeBSD 8.0-CURRENT #0: Sun May 17 07:56:14 MSD 2009 amd64 new port virtualbox_2.tgz make - OK install - OK load module - OK run -OK run VM - crush :( only 1 time. more have not yet tried. From miwi at freebsd.org Mon May 18 13:07:42 2009 From: miwi at freebsd.org (Martin Wilke) Date: Mon May 18 13:08:31 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: <20090514191237.GD70242@bsdcrew.de> References: <20090514191237.GD70242@bsdcrew.de> Message-ID: <20090517180920.GY71804@bsdcrew.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 We rolled a new tarball with the patch from Juergen Lock [1] with a posible fix for AMD64 users, tested on 3 machines which now works without problems. Many Thanks to him for his nice work! http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz Martin - -- +-----------------------+-------------------------------+ | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | | ICQ : 169139903 | Mail : miwi(at)FreeBSD.org | +-----------------------+-------------------------------+ | Mess with the Best, Die like the Rest! | +-----------------------+-------------------------------+ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) iEUEARECAAYFAkoQUtAACgkQdLJIhLHm/OlY2QCg1KZW2YCvE1VhqKgSQ/xhjKIx U60Al2UMniKg+KvQ6m9RcP92eOMddfQ= =kB6c -----END PGP SIGNATURE----- _______________________________________________ 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" From f0andrey at gmail.com Mon May 18 13:07:49 2009 From: f0andrey at gmail.com (Andrey Fesenko) Date: Mon May 18 13:09:36 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: <20090517180920.GY71804@bsdcrew.de> References: <20090514191237.GD70242@bsdcrew.de> <20090517180920.GY71804@bsdcrew.de> Message-ID: <19e7832a0905180428l564f4e74s9d8ce3213228b08e@mail.gmail.com> On Sun, May 17, 2009 at 10:09 PM, Martin Wilke wrote: > > We rolled a new tarball with the patch from Juergen Lock [1] > with a posible fix for AMD64 users, tested on 3 machines > which now works without problems. Many Thanks to him for > his nice work! > > http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz > > Martin > FreeBSD 8.0-CURRENT #0: Sun May 17 07:56:14 MSD 2009 amd64 new port virtualbox_2.tgz make - OK install - OK load module - OK run -OK run VM - crush :( only 1 time. more have not yet tried. _______________________________________________ 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" From Benoit.Calvez at gmail.com Mon May 18 13:07:56 2009 From: Benoit.Calvez at gmail.com (Benoit Calvez) Date: Mon May 18 13:10:35 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: <3481d8e60905141449qfcf5da8r95d54281206304a4@mail.gmail.com> References: <20090514191237.GD70242@bsdcrew.de> <3481d8e60905141449qfcf5da8r95d54281206304a4@mail.gmail.com> Message-ID: <3481d8e60905161016k3de535e3n9a570c5bee6ba517@mail.gmail.com> On Thu, May 14, 2009 at 11:49 PM, Benoit Calvez wrote: > > > On Thu, May 14, 2009 at 9:12 PM, Martin Wilke wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> >> Howdy Guys, >> >> After the announcement from Alexander Eichner about >> Virtualbox on FreeBSD, we started the work on a port >> for FreeBSD. Now we think that we solved the most >> problems and are ready for the first Call for Testing. >> >> Some notes before you can test the port: >> Make sure you are using RELENG_7 or higher. You have >> to use a fresh portstree with uptodate ports!! Please >> read carefully the pkg-messages. >> >> Some known issues / Troubleshooting: >> Sometimes the kernel on HEAD coredumps when loading >> or unloading the kernel module. A small workaround >> to prevent the crash is to not start X, mount proc, >> then load the kernel module and start X from the >> console. That helped me and some testers, maybe you >> too. :P AMD64 should be work in general, it builds >> and start. But not right tested at the moment. We >> want here also some feedback. >> >> Some Thanks: >> First of all we'd like to say many thanks to _ALL_ >> vbox developers. Next people are Bernhard Froehlich >> (aka decke), Beat Gaetzi (beat@), Dennis Herrmann >> (dhn@), Pietro Cerutti (gahr@), myself (*gg*), >> and _ALL_ who helped and provided feedback. >> >> Happy Testing :-) >> >> Download: >> >> http://people.freebsd.org/~miwi/vbox/vboxport.tgz >> >> Wiki Page: >> http://wiki.freebsd.org/VirtualBox >> >> - Martin >> >> - -- >> >> +-----------------------+-------------------------------+ >> | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | >> | ICQ : 169139903 | Mail : miwi(at)FreeBSD.org | >> +-----------------------+-------------------------------+ >> | Mess with the Best, Die like the Rest! | >> +-----------------------+-------------------------------+ >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v2.0.11 (FreeBSD) >> >> iEYEARECAAYFAkoMbSUACgkQdLJIhLHm/OnNnACeJsT7H9hW1J7CV70P3Ty+q0CA >> kD8AoMLCPbltY999/8qO6fnaqv4UQ9QT >> =LcoD >> -----END PGP SIGNATURE----- >> _______________________________________________ >> 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 >> " >> > > I'm trying to build from amd64, but got the following error. Sorry but I > didn't look, and it's a fresh paste: > ===> Configuring for virtualbox-2.2.2r19673 > Checking for environment: Determined build machine: freebsd.amd64, target > machine: freebsd.amd64, OK. > Checking for kBuild: found, OK. > Checking for gcc: found version 4.2.1, OK. > Checking for as86: found version 0.16.17, OK. > Checking for bcc: found version 0.16.17, OK. > Checking for iasl: found version 20070320, OK. > Checking for xslt: found, OK. > Checking for pthread: found, OK. > Checking for libxml2: found version 2.7.3, OK. > Checking for libxslt: found version 1.1.24, OK. > Checking for libIDL: found version 0.8.13, OK. > Checking for zlib: found version 1.2.3, OK. > Checking for SDL: found version 1.2.13, OK. > Checking for X libraries: found, OK. > Checking for Xcursor: found, OK. > Checking for Xmu: found, OK. > Checking for Mesa / GLU: Xlib: extension "Generic Event Extension" missing > on display ":0.0". > Xlib: extension "Generic Event Extension" missing on display ":0.0". > found version 1.2, OK. > Checking for Qt4: found version 4.4.3, OK. > Checking for Qt4 devtools: found version 4.4.3, OK. > Checking for python support: found version 2.5.4, OK. > > Successfully generated > '/usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/AutoConfig.kmk' > and '/usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/env.sh'. > Source '/usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/env.sh' > once before you start to build VBox: > > source /usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/env.sh > kmk > > > +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING > +++ > Hardening is enabled which means that the VBox binaries will not run from > the binary directory. The binaries have to be installed suid root and > some > more prerequisites have to be fulfilled which is normally done by > installing > the final package. For development, the hardening feature can be disabled > by specifying the --disable-hardening parameter. Please never disable > that > feature for the final distribution! > +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING +++ WARNING > +++ > > Enjoy! > ===> Building for virtualbox-2.2.2r19673 > cd /usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673 && /bin/sh > env.sh && VBOX_LIBPATH_X11=/usr/local > /usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/kBuild/bin/freebsd.amd64/kmk > Config.kmk:1664: > /usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/GCCConfig.kmk: > No such file or directory > Config.kmk:3789: > /usr/home/benoit/src/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/revision.kmk: > No such file or directory > Fatal error 'kse_create() failed > ' at line 469 in file /usr/src/lib/libpthread/thread/thr_kern.c (errno = 2) > *** Error code 1 > > > > > -- > Benoit C. > > I just tryed with the last tarball ( http://people.freebsd.org/~miwi/vbox/virtualbox_1.tgz) and it compiles fine. the kernel module loads, and I'll try to boot an opensolaris in a few moments. Nice job everyone ! -- Benoit C. _______________________________________________ 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" From glen.j.barber at gmail.com Mon May 18 13:08:03 2009 From: glen.j.barber at gmail.com (Glen Barber) Date: Mon May 18 13:11:08 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: <20090517180920.GY71804@bsdcrew.de> References: <20090514191237.GD70242@bsdcrew.de> <20090517180920.GY71804@bsdcrew.de> Message-ID: <4ad871310905171741t55611cf7vc96e0086a371052@mail.gmail.com> On Sun, May 17, 2009 at 2:09 PM, Martin Wilke wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > We rolled a new tarball with the patch from Juergen Lock [1] > with a posible fix for AMD64 users, tested on 3 machines > which now works without problems. Many Thanks to him for > his nice work! > Is there need for the i386 folks to rebuild, or does it only affect amd64? -- Glen Barber _______________________________________________ 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" From freebsd at byshenk.net Mon May 18 13:08:08 2009 From: freebsd at byshenk.net (Greg Byshenk) Date: Mon May 18 13:11:41 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: <20090517180920.GY71804@bsdcrew.de> References: <20090514191237.GD70242@bsdcrew.de> <20090517180920.GY71804@bsdcrew.de> Message-ID: <20090518002528.GF2571@core.byshenk.net> On Sun, May 17, 2009 at 08:09:20PM +0200, Martin Wilke wrote: > > We rolled a new tarball with the patch from Juergen Lock [1] > with a posible fix for AMD64 users, tested on 3 machines > which now works without problems. Many Thanks to him for > his nice work! > > http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz I've just updated my system (to 7-STABLE amd64 as of today) and installed the new version. It runs for me now. Tomorrow I will try to create virtual machine. -- greg byshenk - gbyshenk@byshenk.net - Leiden, NL _______________________________________________ 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" From Benoit.Calvez at gmail.com Mon May 18 13:08:11 2009 From: Benoit.Calvez at gmail.com (Benoit Calvez) Date: Mon May 18 13:11:52 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: <11167f520905171210t2c5c2623o386f00745b4f9aed@mail.gmail.com> References: <20090514191237.GD70242@bsdcrew.de> <20090517180920.GY71804@bsdcrew.de> <11167f520905171210t2c5c2623o386f00745b4f9aed@mail.gmail.com> Message-ID: <3481d8e60905171306n35904a6boc74eed344505cb13@mail.gmail.com> On Sun, May 17, 2009 at 9:10 PM, Sam Fourman Jr. wrote: > On Sun, May 17, 2009 at 1:09 PM, Martin Wilke wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > > > We rolled a new tarball with the patch from Juergen Lock [1] > > with a posible fix for AMD64 users, tested on 3 machines > > which now works without problems. Many Thanks to him for > > his nice work! > > > > http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz > > > > Martin > > Does this version still have the kernel module crashing at random on > current? > > Sam Fourman Jr. > _______________________________________________ > 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" > I uninstalled the last virtualbox (from virtualbox_1.tgz port). It compiled fine and I could start an opensolaris vm. It crashed cauz' I created the virtual hard drive in a smal partition. Since then I couldn't restart the vm. I got two Errors: "Kernel driver not instaled (rc =-1908) "Make sure the kernel module has beed loaded successfully" Sure it is. the other one is : Result Code: NS_ERROR_FAILURE (0x80004005) Component: Machine Interface: IMachine {4d1df26d-d9c1-4c7e-b689-15e85ecf8ffc} I could give more informations if needed -- Benoit C. _______________________________________________ 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" From freebsd at byshenk.net Mon May 18 13:08:13 2009 From: freebsd at byshenk.net (Greg Byshenk) Date: Mon May 18 13:12:04 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: <3481d8e60905161016k3de535e3n9a570c5bee6ba517@mail.gmail.com> References: <20090514191237.GD70242@bsdcrew.de> <3481d8e60905141449qfcf5da8r95d54281206304a4@mail.gmail.com> <3481d8e60905161016k3de535e3n9a570c5bee6ba517@mail.gmail.com> Message-ID: <20090517085626.GD2571@core.byshenk.net> On Sat, May 16, 2009 at 07:16:13PM +0200, Benoit Calvez wrote: > On Thu, May 14, 2009 at 11:49 PM, Benoit Calvez wrote: > > On Thu, May 14, 2009 at 9:12 PM, Martin Wilke wrote: > >> After the announcement from Alexander Eichner about > >> Virtualbox on FreeBSD, we started the work on a port > >> for FreeBSD. Now we think that we solved the most > >> problems and are ready for the first Call for Testing. > >> > >> Some notes before you can test the port: > >> Make sure you are using RELENG_7 or higher. You have > >> to use a fresh portstree with uptodate ports!! Please > >> read carefully the pkg-messages. > >> > >> Some known issues / Troubleshooting: > >> Sometimes the kernel on HEAD coredumps when loading > >> or unloading the kernel module. A small workaround > >> to prevent the crash is to not start X, mount proc, > >> then load the kernel module and start X from the > >> console. That helped me and some testers, maybe you > >> too. :P AMD64 should be work in general, it builds > >> and start. But not right tested at the moment. We > >> want here also some feedback. > >> > >> Some Thanks: > >> First of all we'd like to say many thanks to _ALL_ > >> vbox developers. Next people are Bernhard Froehlich > >> (aka decke), Beat Gaetzi (beat@), Dennis Herrmann > >> (dhn@), Pietro Cerutti (gahr@), myself (*gg*), > >> and _ALL_ who helped and provided feedback. > >> > >> Happy Testing :-) > >> > >> Download: > >> > >> http://people.freebsd.org/~miwi/vbox/vboxport.tgz > >> > >> Wiki Page: > >> http://wiki.freebsd.org/VirtualBox > >> > >> - Martin > > I'm trying to build from amd64, but got the following error. Sorry but I > > didn't look, and it's a fresh paste: > > [...] > I just tryed with the last tarball ( > http://people.freebsd.org/~miwi/vbox/virtualbox_1.tgz) and it compiles fine. > > the kernel module loads, and I'll try to boot an opensolaris in a few > moments. I've just tried with virtualbox_1.tgz, and it builds without a problem, the module installs without a problem, but attempting to start VirtualBox fails. I get no error at all, VirtualBox just hangs. If I attempt to run 'truss VirtualBox', I get the error: Effective UID is not root (euid=1001 egid=1001 uid=1001 gid=1001) (rc=-10) It may help to reinstall VirtualBox. But checking shows that VirtualBox is SUID root: $ ls -l /usr/local/lib/virtualbox/VirtualBox -r-s--x--x 1 root vboxusers 21016 May 17 10:21 /usr/local/lib/virtualbox/VirtualBox It seems that I can create a vm: $ VBoxManage createvm --name test VirtualBox Command Line Management Interface Version 2.2.51_OSE (C) 2005-2009 Sun Microsystems, Inc. All rights reserved. Virtual machine 'test' is created. UUID: 9be28271-55c2-4299-b69a-266c58716db7 Settings file: '/home/gbyshenk/.VirtualBox/Machines/test/test.xml' $ VirtualBox $ ls -l /home/gbyshenk/.VirtualBox/Machines/test/test.xml -rw------- 1 gbyshenk gbyshenk 2302 May 17 10:37 /home/gbyshenk/.VirtualBox/Machines/test/test.xml But VirtualBox itself fails to start -- even if I run as root. System is amd64, 7-STABLE as of 26-04-2009. Does it need to be more recent...? -- greg byshenk - gbyshenk@byshenk.net - Leiden, NL _______________________________________________ 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" From freebsd at byshenk.net Mon May 18 13:08:15 2009 From: freebsd at byshenk.net (Greg Byshenk) Date: Mon May 18 13:12:15 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: <20090518002528.GF2571@core.byshenk.net> References: <20090514191237.GD70242@bsdcrew.de> <20090517180920.GY71804@bsdcrew.de> <20090518002528.GF2571@core.byshenk.net> Message-ID: <20090518005054.GG2571@core.byshenk.net> On Mon, May 18, 2009 at 02:25:28AM +0200, Greg Byshenk wrote: > On Sun, May 17, 2009 at 08:09:20PM +0200, Martin Wilke wrote: > > > > We rolled a new tarball with the patch from Juergen Lock [1] > > with a posible fix for AMD64 users, tested on 3 machines > > which now works without problems. Many Thanks to him for > > his nice work! > > > > http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz > I've just updated my system (to 7-STABLE amd64 as of today) and > installed the new version. It runs for me now. Tomorrow I will > try to create virtual machine. As a followup, the 'virtualbox_2.tgz' version appears to work for me, at least minimally. I've just installed NetBSD4.1 virtual machine, and it appears to be working (even though NetBSD isn't listed as a supported guest -- I just happened to have the NetBSD install iso sitting on my hard drive). -- greg byshenk - gbyshenk@byshenk.net - Leiden, NL _______________________________________________ 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" From sfourman at gmail.com Mon May 18 13:08:16 2009 From: sfourman at gmail.com (Sam Fourman Jr.) Date: Mon May 18 13:12:27 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: <20090517180920.GY71804@bsdcrew.de> References: <20090514191237.GD70242@bsdcrew.de> <20090517180920.GY71804@bsdcrew.de> Message-ID: <11167f520905171210t2c5c2623o386f00745b4f9aed@mail.gmail.com> On Sun, May 17, 2009 at 1:09 PM, Martin Wilke wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > We rolled a new tarball with the patch from Juergen Lock [1] > with a posible fix for AMD64 users, tested on 3 machines > which now works without problems. Many Thanks to him for > his nice work! > > http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz > > Martin Does this version still have the kernel module crashing at random on current? Sam Fourman Jr. _______________________________________________ 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" From doug at polands.org Mon May 18 13:57:21 2009 From: doug at polands.org (Doug Poland) Date: Mon May 18 13:57:54 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: <20090518002528.GF2571@core.byshenk.net> References: <20090514191237.GD70242@bsdcrew.de> <20090517180920.GY71804@bsdcrew.de> <20090518002528.GF2571@core.byshenk.net> Message-ID: <532cb0d675c7f20c60fcc2e8e4c1a558.squirrel@email.polands.org> On Sun, May 17, 2009 19:25, Greg Byshenk wrote: > On Sun, May 17, 2009 at 08:09:20PM +0200, Martin Wilke wrote: >> >> We rolled a new tarball with the patch from Juergen Lock [1] >> with a posible fix for AMD64 users, tested on 3 machines >> which now works without problems. Many Thanks to him for >> his nice work! >> >> http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz > Working for me with a fresh cvsup of 7.2-STABLE (17 May 09). Installing a 7.2-RELEASE amd64 guest as I write this. -- Regards, Doug From tim at bishnet.net Mon May 18 15:56:21 2009 From: tim at bishnet.net (Tim Bishop) Date: Mon May 18 15:56:33 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: <532cb0d675c7f20c60fcc2e8e4c1a558.squirrel@email.polands.org> References: <20090514191237.GD70242@bsdcrew.de> <20090517180920.GY71804@bsdcrew.de> <20090518002528.GF2571@core.byshenk.net> <532cb0d675c7f20c60fcc2e8e4c1a558.squirrel@email.polands.org> Message-ID: <20090518155613.GT86061@carrick.bishnet.net> On Mon, May 18, 2009 at 08:38:18AM -0500, Doug Poland wrote: > On Sun, May 17, 2009 19:25, Greg Byshenk wrote: > > On Sun, May 17, 2009 at 08:09:20PM +0200, Martin Wilke wrote: > >> > >> We rolled a new tarball with the patch from Juergen Lock [1] > >> with a posible fix for AMD64 users, tested on 3 machines > >> which now works without problems. Many Thanks to him for > >> his nice work! > >> > >> http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz > > Working for me with a fresh cvsup of 7.2-STABLE (17 May 09). > Installing a 7.2-RELEASE amd64 guest as I write this. Works for me, but I've not been able to get a 64 bit guest to work. I get the following error when booting the installer: CPU doesn't support long mode I think I've got all the right options set. Maybe my CPU doesn't support the necessary VM stuff to let a 64 bit guest work? I'm also still seeing the following on loading vboxdrv: kldload: unexpected relocation type 10 kldload: unexpected relocation type 10 kldload: unexpected relocation type 10 kldload: unexpected relocation type 10 kldload: unexpected relocation type 10 kldload: unexpected relocation type 10 kldload: unexpected relocation type 10 kldload: unexpected relocation type 10 kldload: unexpected relocation type 10 kldload: unexpected relocation type 10 kldload: unexpected relocation type 10 kldload: unexpected relocation type 10 vboxdrv: fAsync=0 offMin=0x41f offMax=0x53b Are others still seeing that on amd64? Tim. -- Tim Bishop http://www.bishnet.net/tim/ PGP Key: 0x5AE7D984 From tim at bishnet.net Mon May 18 16:49:56 2009 From: tim at bishnet.net (Tim Bishop) Date: Mon May 18 16:50:13 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: <20090518155613.GT86061@carrick.bishnet.net> References: <20090514191237.GD70242@bsdcrew.de> <20090517180920.GY71804@bsdcrew.de> <20090518002528.GF2571@core.byshenk.net> <532cb0d675c7f20c60fcc2e8e4c1a558.squirrel@email.polands.org> <20090518155613.GT86061@carrick.bishnet.net> Message-ID: <20090518164945.GU86061@carrick.bishnet.net> On Mon, May 18, 2009 at 04:56:13PM +0100, Tim Bishop wrote: > On Mon, May 18, 2009 at 08:38:18AM -0500, Doug Poland wrote: > > On Sun, May 17, 2009 19:25, Greg Byshenk wrote: > > > On Sun, May 17, 2009 at 08:09:20PM +0200, Martin Wilke wrote: > > >> > > >> We rolled a new tarball with the patch from Juergen Lock [1] > > >> with a posible fix for AMD64 users, tested on 3 machines > > >> which now works without problems. Many Thanks to him for > > >> his nice work! > > >> > > >> http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz > > > > Working for me with a fresh cvsup of 7.2-STABLE (17 May 09). > > Installing a 7.2-RELEASE amd64 guest as I write this. > > Works for me, but I've not been able to get a 64 bit guest to work. I > get the following error when booting the installer: > > CPU doesn't support long mode > > I think I've got all the right options set. Maybe my CPU doesn't support > the necessary VM stuff to let a 64 bit guest work? I'm getting good at answering my own questions :D Yes, it's my CPU. Found a different machine and confirmed it has the VMX extension, and all is fine. > I'm also still seeing the following on loading vboxdrv: > > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > vboxdrv: fAsync=0 offMin=0x41f offMax=0x53b > > Are others still seeing that on amd64? Not that I thought it'd make any difference, but I can confirm those still happen even with the VMX extension. Tim. -- Tim Bishop http://www.bishnet.net/tim/ PGP Key: 0x5AE7D984 From nox at jelal.kn-bremen.de Mon May 18 17:18:37 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Mon May 18 17:18:48 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: <20090518155613.GT86061@carrick.bishnet.net> References: <20090514191237.GD70242@bsdcrew.de> <20090517180920.GY71804@bsdcrew.de> <20090518002528.GF2571@core.byshenk.net> <532cb0d675c7f20c60fcc2e8e4c1a558.squirrel@email.polands.org> Message-ID: <200905181715.n4IHFEPx053165@triton.kn-bremen.de> In article <20090518155613.GT86061@carrick.bishnet.net> you write: >On Mon, May 18, 2009 at 08:38:18AM -0500, Doug Poland wrote: >> On Sun, May 17, 2009 19:25, Greg Byshenk wrote: >> > On Sun, May 17, 2009 at 08:09:20PM +0200, Martin Wilke wrote: >> >> >> >> We rolled a new tarball with the patch from Juergen Lock [1] >> >> with a posible fix for AMD64 users, tested on 3 machines >> >> which now works without problems. Many Thanks to him for >> >> his nice work! >> >> >> >> http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz >> >> Working for me with a fresh cvsup of 7.2-STABLE (17 May 09). >> Installing a 7.2-RELEASE amd64 guest as I write this. > >Works for me, but I've not been able to get a 64 bit guest to work. I >get the following error when booting the installer: > > CPU doesn't support long mode > >I think I've got all the right options set. Maybe my CPU doesn't support >the necessary VM stuff to let a 64 bit guest work? > Yes, afaik vbox can only run amd64 guests if the host cpu has svm (amd) or vmx (intel) and you tell vbox to use that in the guest settings. (`Enable VT-X/AMD-V'.) And btw, npt/ept (`Enable Nested Paging') is also worth using if your host cpu has it, it should speed up the vm a little. And if you have a guest (especially amd64) that then still hangs/crashes at boot or otherwise doesnt come up, check if the io-apic is disabled in the guest settings and enable it... (I think there are also older 32 bit guests that need it disabled, otherwise the option wouldn't be there :) - but usually its the other way around.) >I'm also still seeing the following on loading vboxdrv: > >kldload: unexpected relocation type 10 >kldload: unexpected relocation type 10 >kldload: unexpected relocation type 10 >kldload: unexpected relocation type 10 >kldload: unexpected relocation type 10 >kldload: unexpected relocation type 10 >kldload: unexpected relocation type 10 >kldload: unexpected relocation type 10 >kldload: unexpected relocation type 10 >kldload: unexpected relocation type 10 >kldload: unexpected relocation type 10 >kldload: unexpected relocation type 10 >vboxdrv: fAsync=0 offMin=0x41f offMax=0x53b > >Are others still seeing that on amd64? These are caused by the in-kernel linker not properly skipping debug symbols in klds (they are harmless, altho may waste some kernel memory), a workaround has been committed to vbox svn in the meantime (uncommenting an objcopy --strip-debug in Config.kmk that was already in there...) This is btw also the reason why we have seperate foo.symbols files in our kernel dirs which kgdb will then pick up - tho unfortunately it doesn't seem to do that for klds in /boot/modules, at least on 7-stable. HTH, Juergen PS: I trimmed the Cc'd lists to only -emulation... From Benoit.Calvez at gmail.com Mon May 18 17:35:16 2009 From: Benoit.Calvez at gmail.com (Benoit Calvez) Date: Mon May 18 17:35:27 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: <20090518155613.GT86061@carrick.bishnet.net> References: <20090514191237.GD70242@bsdcrew.de> <20090517180920.GY71804@bsdcrew.de> <20090518002528.GF2571@core.byshenk.net> <532cb0d675c7f20c60fcc2e8e4c1a558.squirrel@email.polands.org> <20090518155613.GT86061@carrick.bishnet.net> Message-ID: <3481d8e60905181034l20a5d722m2ca340577a71d0f7@mail.gmail.com> On Mon, May 18, 2009 at 5:56 PM, Tim Bishop wrote: > On Mon, May 18, 2009 at 08:38:18AM -0500, Doug Poland wrote: > > On Sun, May 17, 2009 19:25, Greg Byshenk wrote: > > > On Sun, May 17, 2009 at 08:09:20PM +0200, Martin Wilke wrote: > > >> > > >> We rolled a new tarball with the patch from Juergen Lock [1] > > >> with a posible fix for AMD64 users, tested on 3 machines > > >> which now works without problems. Many Thanks to him for > > >> his nice work! > > >> > > >> http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz > > > > Working for me with a fresh cvsup of 7.2-STABLE (17 May 09). > > Installing a 7.2-RELEASE amd64 guest as I write this. > > Works for me, but I've not been able to get a 64 bit guest to work. I > get the following error when booting the installer: > > CPU doesn't support long mode > > I think I've got all the right options set. Maybe my CPU doesn't support > the necessary VM stuff to let a 64 bit guest work? > > I'm also still seeing the following on loading vboxdrv: > > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > vboxdrv: fAsync=0 offMin=0x41f offMax=0x53b > > Are others still seeing that on amd64? > got the same in dmesg: kldload: unexpected relocation type 10 vboxdrv: fAsync=1 offMin=0xff94c offMax=0xff94c supdrvGipCreate: omni timer not supported, falling back to synchronous mode > > Tim. > > -- > Tim Bishop > http://www.bishnet.net/tim/ > PGP Key: 0x5AE7D984 > _______________________________________________ > 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" > -- Benoit Calvez. From f0andrey at gmail.com Mon May 18 18:12:51 2009 From: f0andrey at gmail.com (Andrey Fesenko) Date: Mon May 18 18:13:14 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: <20090518155613.GT86061@carrick.bishnet.net> References: <20090514191237.GD70242@bsdcrew.de> <20090517180920.GY71804@bsdcrew.de> <20090518002528.GF2571@core.byshenk.net> <532cb0d675c7f20c60fcc2e8e4c1a558.squirrel@email.polands.org> <20090518155613.GT86061@carrick.bishnet.net> Message-ID: <19e7832a0905181112h3470a327i45d81abda65b5de9@mail.gmail.com> On Mon, May 18, 2009 at 7:56 PM, Tim Bishop wrote: > On Mon, May 18, 2009 at 08:38:18AM -0500, Doug Poland wrote: > > On Sun, May 17, 2009 19:25, Greg Byshenk wrote: > > > On Sun, May 17, 2009 at 08:09:20PM +0200, Martin Wilke wrote: > > >> > > >> We rolled a new tarball with the patch from Juergen Lock [1] > > >> with a posible fix for AMD64 users, tested on 3 machines > > >> which now works without problems. Many Thanks to him for > > >> his nice work! > > >> > > >> http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz > > > > Working for me with a fresh cvsup of 7.2-STABLE (17 May 09). > > Installing a 7.2-RELEASE amd64 guest as I write this. > > Works for me, but I've not been able to get a 64 bit guest to work. I > get the following error when booting the installer: > > CPU doesn't support long mode > > I think I've got all the right options set. Maybe my CPU doesn't support > the necessary VM stuff to let a 64 bit guest work? > > I'm also still seeing the following on loading vboxdrv: > > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > vboxdrv: fAsync=0 offMin=0x41f offMax=0x53b > > Are others still seeing that on amd64? > > FreeBSD 8.0-CURRENT #0: Sun May 17 07:56:14 MSD 2009 amd64 got the same in/var/log/messages May 18 22:00:02 my_book newsyslog[25948]: logfile turned over due to size>100K May 18 22:07:28 my_book kernel: kldload: unexpected relocation type 10 May 18 22:07:28 my_book last message repeated 11 times May 18 22:07:28 my_book kernel: vboxdrv: fAsync=0 offMin=0x499 offMax=0x8744 From korvus at comcast.net Mon May 18 21:05:19 2009 From: korvus at comcast.net (Steve Polyack) Date: Mon May 18 21:05:31 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: References: <20090514191237.GD70242@bsdcrew.de> <20090517180920.GY71804@bsdcrew.de> Message-ID: <4A11CA05.8040900@comcast.net> Marius N?nnerich wrote: > On Sun, May 17, 2009 at 20:09, Martin Wilke wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> >> We rolled a new tarball with the patch from Juergen Lock [1] >> with a posible fix for AMD64 users, tested on 3 machines >> which now works without problems. Many Thanks to him for >> his nice work! >> >> http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz >> >> Martin >> > > I'm impressed, everything I tried worked ootb. Thank you all! > > (FreeBSD/i386 7.2-STABLE) > Everything's working great for me as well (i386 7.2-RELEASE here). Are there plans to support the bridged interface network adapters? Also, I was surprised at how good the performance was on my home machine with the VT extensions. Great work! From marius at nuenneri.ch Mon May 18 21:11:12 2009 From: marius at nuenneri.ch (=?ISO-8859-1?Q?Marius_N=FCnnerich?=) Date: Mon May 18 21:11:19 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: <20090517180920.GY71804@bsdcrew.de> References: <20090514191237.GD70242@bsdcrew.de> <20090517180920.GY71804@bsdcrew.de> Message-ID: On Sun, May 17, 2009 at 20:09, Martin Wilke wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > We rolled a new tarball with the patch from Juergen Lock [1] > with a posible fix for AMD64 users, tested on 3 machines > which now works without problems. Many Thanks to him for > his nice work! > > http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz > > Martin I'm impressed, everything I tried worked ootb. Thank you all! (FreeBSD/i386 7.2-STABLE) From kubito at gmail.com Tue May 19 05:55:34 2009 From: kubito at gmail.com (Raphael Kubo da Costa) Date: Tue May 19 05:55:41 2009 Subject: Cannot nspluginwrapper problems because of linux-f8-pango vulnerability Message-ID: <68c3445d0905182230k453486a5nf13fbf8359f7029a@mail.gmail.com> Hello, I'm trying to get linux-f8-flashplugin10 here with FreeBSD 7.2. I've already installed it (which means OVERRIDE_LINUX_BASE_PORT and OVERRIDE_LINUX_NONBASE_PORTS are already correctly set to f8) and now I'm trying to install the nspluginwrapper port. However, it always fails with the following error while installing its dependencies: ===> linux-f8-gtk2-2.12.8 depends on file: /compat/linux/usr/lib/libpango-1.0.so.0.1800.4 - not found ===> Verifying install for /compat/linux/usr/lib/libpango-1.0.so.0.1800.4 in /usr/ports/x11-toolkits/linux-f8-pango ===> linux-f8-pango-1.18.4 has known vulnerabilities: => pango -- integer overflow. Reference: => Please update your ports tree and try again. *** Error code 1 Stop in /usr/ports/x11-toolkits/linux-f8-pango. *** Error code 1 Stop in /usr/ports/x11-toolkits/linux-f8-gtk2. *** Error code 1 Stop in /usr/ports/www/nspluginwrapper. Looking at the reference, it says it affects linux-f8-pango < 1.24, but the current port is at 1.18.4 and I don't think there's an updated Fedora 8 package (== 1.24). Is there a way to prevent this check from happening? Thanks, Raphael From fb-emulation at psconsult.nl Tue May 19 07:50:34 2009 From: fb-emulation at psconsult.nl (Paul Schenkeveld) Date: Tue May 19 07:50:41 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: <20090514191237.GD70242@bsdcrew.de> References: <20090514191237.GD70242@bsdcrew.de> Message-ID: <20090519071102.GA22062@psconsult.nl> On Thu, May 14, 2009 at 09:12:37PM +0200, Martin Wilke wrote: > > Howdy Guys, > > After the announcement from Alexander Eichner about > Virtualbox on FreeBSD, we started the work on a port > for FreeBSD. Now we think that we solved the most > problems and are ready for the first Call for Testing. Many thanks! So far I had a short ride but vbox fails every time after the first try. If the following can help you debug/improve, read on, otherwise I'll just wait for a more stable version. If you want me to test anything or send crash dump, please let me know. - Running 7.2-STABLE i386 as of Thu May 14 19:28:42 CEST 2009 on Dell Precision M4300 notebook (Intel T7500 Core-2 Duo, 2.2GHz VT-x enabled, 3 GB RAM) - /proc is mounted - Downloaded vbox port yesterday evening (~ 18:50 UTC) - make -s install clean (watch many qt4 dependencies, dev86 and vbox install) - kldload vboxdrv (OK, even with X running) - $ VirtualBox - Created a guest with 512MB RAM, 2GB IDE pri master disk - Could not choose bridged network, so fell back to NAT - Installed FreeBSD 7.1 from 7.1 release DVD iso, feels very good, nice performance! - Could not NFS mount anything, vbox NAT translates NFS client to unprivileged port - Wanted to add second virtual disk to hold /usr/src and /usr/obj so stopped vbox, added virtual disk and tried to restart guest many times, no luck - Rebooted computer - kldload vboxdrv (with X11 running), system panics - Reboot and load vboxdrv from loader works - Trying to start existing vbox guest always fails, sometimes with error popup: Unknown error creating VM (VERR_PDM_DEVICE_NOT_FOUND). Result Code: NS_ERROR_FAILURE (0x80004005) Component: Console Interface: IConsole {a7f17a42-5b64-488d-977b-4b2c639ada27} but mostly I only see the console window appear and disappear within a second (/var/log/messages: pid 1283 (VirtualBox), uid 2506: exited on signal 11 - Creating a new guest (in case disk image of old guest is damaged) never starts (shows same symptoms as original guest) Thanks again for all the good work! -- Paul Schenkeveld From miwi at FreeBSD.org Tue May 19 09:13:16 2009 From: miwi at FreeBSD.org (Martin Wilke) Date: Tue May 19 09:13:28 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: <20090517180920.GY71804@bsdcrew.de> References: <20090514191237.GD70242@bsdcrew.de> <20090517180920.GY71804@bsdcrew.de> Message-ID: <20090519091310.GB71804@bsdcrew.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Howdy .. Next run, We updated the port to 2.2.2r19801. The Patch files/patch-amd64-r0-exec-alloc was removed in favor of a similar fix commited to upstream. Also was fixed a bug on HEAD which should be fix the Kernel crash. Please test test test .. :-) PS: Yes this run is for AMD64 and HEAD users! http://people.freebsd.org/~miwi/vbox/virtualbox_3.tgz Happy Testing! - -- +-----------------------+-------------------------------+ | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | | ICQ : 169139903 | Mail : miwi(at)FreeBSD.org | +-----------------------+-------------------------------+ | Mess with the Best, Die like the Rest! | +-----------------------+-------------------------------+ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAkoSeCYACgkQdLJIhLHm/OkuOQCfVzr7yTxydbo6npBgO2LyZNk1 RpUAnAmxjlHTBsM8pJ5SIiPIqQRCWElu =LoBM -----END PGP SIGNATURE----- From paul at fletchermoorland.co.uk Tue May 19 09:56:38 2009 From: paul at fletchermoorland.co.uk (Paul Wootton) Date: Tue May 19 09:56:45 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: <20090519091310.GB71804@bsdcrew.de> References: <20090514191237.GD70242@bsdcrew.de> <20090517180920.GY71804@bsdcrew.de> <20090519091310.GB71804@bsdcrew.de> Message-ID: <4A128253.7040400@fletchermoorland.co.uk> Martin Wilke wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Howdy .. > > Next run, > > We updated the port to 2.2.2r19801. > The Patch files/patch-amd64-r0-exec-alloc > was removed in favor of a similar fix > commited to upstream. Also was fixed a > bug on HEAD which should be fix the Kernel > crash. Please test test test .. :-) > > PS: Yes this run is for AMD64 and HEAD > users! > > > http://people.freebsd.org/~miwi/vbox/virtualbox_3.tgz > > > Happy Testing! > > - -- > > +-----------------------+-------------------------------+ > | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | > | ICQ : 169139903 | Mail : miwi(at)FreeBSD.org | > +-----------------------+-------------------------------+ > | Mess with the Best, Die like the Rest! | > +-----------------------+-------------------------------+ > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.11 (FreeBSD) > > iEYEARECAAYFAkoSeCYACgkQdLJIhLHm/OkuOQCfVzr7yTxydbo6npBgO2LyZNk1 > RpUAnAmxjlHTBsM8pJ5SIiPIqQRCWElu > =LoBM > -----END PGP SIGNATURE----- > _______________________________________________ > 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" > > > Hi, Im still having build issues. This is the same issue I get when compiling this and the last 2 revisions. Have you got any ideas? Cheers Paul demophon# uname -a FreeBSD demophon 8.0-CURRENT FreeBSD 8.0-CURRENT #15: Mon May 18 10:13:13 BST 2009 paul@demophon:/usr/obj/usr/src/sys/DEMOPHON amd64 demophon# kBuild: Generating tstVMStructSize - /root/vBox/virtualbox/work/virtualbox-2.2.2r19801/out/freebsd.amd64/release/obj/VMM/tstAsmStructsHC.h /root/vBox/virtualbox/work/virtualbox-2.2.2r19801/out/freebsd.amd64/release/bin/tstVMStructGC: 1: Syntax error: "(" unexpected kmk[2]: *** [/root/vBox/virtualbox/work/virtualbox-2.2.2r19801/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h] Error 2 kmk[2]: *** Deleting file `/root/vBox/virtualbox/work/virtualbox-2.2.2r19801/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h' kmk[2]: *** Waiting for unfinished jobs.... awk: can't open file /root/vBox/virtualbox/work/virtualbox-2.2.2r19801/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.def source line number 10 objcopy --strip-debug /root/vBox/virtualbox/work/virtualbox-2.2.2r19801/out/freebsd.amd64/release/obj/vboxdrv/vboxdrv.ko kmk[2]: Leaving directory `/root/vBox/virtualbox/work/virtualbox-2.2.2r19801' kmk[2]: Entering directory `/root/vBox/virtualbox/work/virtualbox-2.2.2r19801' kmk[2]: *** Exiting with status 2 kmk[1]: *** [pass_binaries_this] Error 2 kmk[1]: Leaving directory `/root/vBox/virtualbox/work/virtualbox-2.2.2r19801' kmk: *** [pass_binaries_order] Error 2 *** Error code 2 Stop in /root/vBox/virtualbox. demophon# From carl.gustavsson at bahnhofbredband.se Tue May 19 11:04:24 2009 From: carl.gustavsson at bahnhofbredband.se (Carl Johan Gustavsson) Date: Tue May 19 11:04:31 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: <20090519091310.GB71804@bsdcrew.de> References: <20090514191237.GD70242@bsdcrew.de> <20090517180920.GY71804@bsdcrew.de> <20090519091310.GB71804@bsdcrew.de> Message-ID: <4A120C48.8030709@bahnhofbredband.se> Martin Wilke wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Howdy .. > > Next run, > > We updated the port to 2.2.2r19801. > The Patch files/patch-amd64-r0-exec-alloc > was removed in favor of a similar fix > commited to upstream. Also was fixed a > bug on HEAD which should be fix the Kernel > crash. Please test test test .. :-) > > PS: Yes this run is for AMD64 and HEAD > users! > > > http://people.freebsd.org/~miwi/vbox/virtualbox_3.tgz > > > Happy Testing! > > Hi, It seems as this version has solved the problems I had with the earlier versions, it hung my machine when starting the VM. I'm running i386 HEAD. Now I'm able to install and boot 32bit Ubuntu and the performance seems very nice. Great job! cjg > - -- > > +-----------------------+-------------------------------+ > | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | > | ICQ : 169139903 | Mail : miwi(at)FreeBSD.org | > +-----------------------+-------------------------------+ > | Mess with the Best, Die like the Rest! | > +-----------------------+-------------------------------+ > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.11 (FreeBSD) > > iEYEARECAAYFAkoSeCYACgkQdLJIhLHm/OkuOQCfVzr7yTxydbo6npBgO2LyZNk1 > RpUAnAmxjlHTBsM8pJ5SIiPIqQRCWElu > =LoBM > -----END PGP SIGNATURE----- > _______________________________________________ > 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 sergey.dyatko at gmail.com Tue May 19 11:34:58 2009 From: sergey.dyatko at gmail.com (Sergey V. Dyatko) Date: Tue May 19 11:35:05 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: <20090519091310.GB71804@bsdcrew.de> References: <20090514191237.GD70242@bsdcrew.de> <20090517180920.GY71804@bsdcrew.de> <20090519091310.GB71804@bsdcrew.de> Message-ID: <20090519143451.74c2142d@tiger.minsk.domain> ? Tue, 19 May 2009 11:13:10 +0200 Martin Wilke ?????: MW> -----BEGIN PGP SIGNED MESSAGE----- MW> Hash: SHA1 MW> MW> Howdy .. MW> MW> Next run, MW> MW> We updated the port to 2.2.2r19801. MW> The Patch files/patch-amd64-r0-exec-alloc MW> was removed in favor of a similar fix MW> commited to upstream. Also was fixed a MW> bug on HEAD which should be fix the Kernel MW> crash. Please test test test .. :-) Thanks, after kldload vboxdrv start/stop vm (winxp) is work fine for me. But... kldunload vboxdrv - ok kldload vboxdrv - system hungs. solution: hw reset:( /var/log/messages: May 19 13:22:12 tiger kernel: vboxdrv: fAsync=0 offMin=0x9a8 offMax=0xda0 May 19 14:15:56 tiger kernel: Warning: memory type iprtheap leaked memory on destroy (3 allocations, 192 bytes leaked). May 19 14:16:04 tiger kernel: vboxdrv: fAsync=0 offMin=0x898 offMax=0xb38 [tiger@tiger]~%uname -a FreeBSD tiger.minsk.domain 8.0-CURRENT FreeBSD 8.0-CURRENT #26: Fri May 8 15:32:29 EEST 2009 root@tiger.minsk.domain:/usr/obj/usr/src/sys/tiger-desktop i386 backtrace - http://tiger.ipfw.ru/files/bt.txt MW> MW> PS: Yes this run is for AMD64 and HEAD MW> users! MW> MW> MW> http://people.freebsd.org/~miwi/vbox/virtualbox_3.tgz MW> MW> MW> Happy Testing! MW> MW> - -- MW> MW> +-----------------------+-------------------------------+ MW> | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | MW> | ICQ : 169139903 | Mail : miwi(at)FreeBSD.org | MW> +-----------------------+-------------------------------+ MW> | Mess with the Best, Die like the Rest! | MW> +-----------------------+-------------------------------+ MW> -----BEGIN PGP SIGNATURE----- MW> Version: GnuPG v2.0.11 (FreeBSD) MW> MW> iEYEARECAAYFAkoSeCYACgkQdLJIhLHm/OkuOQCfVzr7yTxydbo6npBgO2LyZNk1 MW> RpUAnAmxjlHTBsM8pJ5SIiPIqQRCWElu MW> =LoBM MW> -----END PGP SIGNATURE----- -- wbr, tiger From miwi at FreeBSD.org Tue May 19 11:38:54 2009 From: miwi at FreeBSD.org (Martin Wilke) Date: Tue May 19 11:39:02 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: <20090519143451.74c2142d@tiger.minsk.domain> References: <20090514191237.GD70242@bsdcrew.de> <20090517180920.GY71804@bsdcrew.de> <20090519091310.GB71804@bsdcrew.de> <20090519143451.74c2142d@tiger.minsk.domain> Message-ID: <20090519113852.GE71804@bsdcrew.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, May 19, 2009 at 02:34:51PM +0300, Sergey V. Dyatko wrote: > ? Tue, 19 May 2009 11:13:10 +0200 > Martin Wilke ?????: > > MW> -----BEGIN PGP SIGNED MESSAGE----- > MW> Hash: SHA1 > MW> > MW> Howdy .. > MW> > MW> Next run, > MW> > MW> We updated the port to 2.2.2r19801. > MW> The Patch files/patch-amd64-r0-exec-alloc > MW> was removed in favor of a similar fix > MW> commited to upstream. Also was fixed a > MW> bug on HEAD which should be fix the Kernel > MW> crash. Please test test test .. :-) > Thanks, > after kldload vboxdrv start/stop vm (winxp) is work fine for me. > But... > kldunload vboxdrv - ok > kldload vboxdrv - system hungs. solution: hw reset:( How old is your src? > > /var/log/messages: > May 19 13:22:12 tiger kernel: vboxdrv: fAsync=0 offMin=0x9a8 > offMax=0xda0 > May 19 14:15:56 tiger kernel: Warning: memory type iprtheap leaked > memory on destroy (3 allocations, 192 bytes leaked). > May 19 14:16:04 tiger kernel: vboxdrv: fAsync=0 offMin=0x898 > offMax=0xb38 > > [tiger@tiger]~%uname -a > FreeBSD tiger.minsk.domain 8.0-CURRENT FreeBSD 8.0-CURRENT #26: Fri > May 8 15:32:29 EEST 2009 > root@tiger.minsk.domain:/usr/obj/usr/src/sys/tiger-desktop i386 > > backtrace - http://tiger.ipfw.ru/files/bt.txt > > MW> > MW> PS: Yes this run is for AMD64 and HEAD > MW> users! > MW> > MW> > MW> http://people.freebsd.org/~miwi/vbox/virtualbox_3.tgz > MW> > MW> > MW> Happy Testing! > MW> > MW> - -- > MW> > MW> +-----------------------+-------------------------------+ > MW> | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | > MW> | ICQ : 169139903 | Mail : miwi(at)FreeBSD.org | > MW> +-----------------------+-------------------------------+ > MW> | Mess with the Best, Die like the Rest! | > MW> +-----------------------+-------------------------------+ > MW> -----BEGIN PGP SIGNATURE----- > MW> Version: GnuPG v2.0.11 (FreeBSD) > MW> > MW> iEYEARECAAYFAkoSeCYACgkQdLJIhLHm/OkuOQCfVzr7yTxydbo6npBgO2LyZNk1 > MW> RpUAnAmxjlHTBsM8pJ5SIiPIqQRCWElu > MW> =LoBM > MW> -----END PGP SIGNATURE----- > > -- > wbr, tiger > - -- +-----------------------+-------------------------------+ | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | | ICQ : 169139903 | Mail : miwi(at)FreeBSD.org | +-----------------------+-------------------------------+ | Mess with the Best, Die like the Rest! | +-----------------------+-------------------------------+ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAkoSmkwACgkQdLJIhLHm/Ony5gCg4iWUTPqjrIJoY+hmLndSD5Ml d6kAoNIE/VCuRHnqShzuywsGOb9pKVcP =IRJZ -----END PGP SIGNATURE----- From sergey.dyatko at gmail.com Tue May 19 11:42:47 2009 From: sergey.dyatko at gmail.com (Sergey V. Dyatko) Date: Tue May 19 11:43:05 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: <20090519113852.GE71804@bsdcrew.de> References: <20090514191237.GD70242@bsdcrew.de> <20090517180920.GY71804@bsdcrew.de> <20090519091310.GB71804@bsdcrew.de> <20090519143451.74c2142d@tiger.minsk.domain> <20090519113852.GE71804@bsdcrew.de> Message-ID: <20090519144240.2040dd20@tiger.minsk.domain> ? Tue, 19 May 2009 13:38:52 +0200 Martin Wilke ?????: MW> -----BEGIN PGP SIGNED MESSAGE----- MW> Hash: SHA1 MW> MW> On Tue, May 19, 2009 at 02:34:51PM +0300, Sergey V. Dyatko wrote: MW> > ? Tue, 19 May 2009 11:13:10 +0200 MW> > Martin Wilke ?????: MW> > MW> > MW> -----BEGIN PGP SIGNED MESSAGE----- MW> > MW> Hash: SHA1 MW> > MW> MW> > MW> Howdy .. MW> > MW> MW> > MW> Next run, MW> > MW> MW> > MW> We updated the port to 2.2.2r19801. MW> > MW> The Patch files/patch-amd64-r0-exec-alloc MW> > MW> was removed in favor of a similar fix MW> > MW> commited to upstream. Also was fixed a MW> > MW> bug on HEAD which should be fix the Kernel MW> > MW> crash. Please test test test .. :-) MW> > Thanks, MW> > after kldload vboxdrv start/stop vm (winxp) is work fine for me. MW> > But... MW> > kldunload vboxdrv - ok MW> > kldload vboxdrv - system hungs. solution: hw reset:( MW> MW> How old is your src? Fri May 8 15:32:29 EEST 2009 virtualbox is 2.2.2r19801 MW> MW> > MW> > /var/log/messages: MW> > May 19 13:22:12 tiger kernel: vboxdrv: fAsync=0 offMin=0x9a8 MW> > offMax=0xda0 MW> > May 19 14:15:56 tiger kernel: Warning: memory type iprtheap leaked MW> > memory on destroy (3 allocations, 192 bytes leaked). MW> > May 19 14:16:04 tiger kernel: vboxdrv: fAsync=0 offMin=0x898 MW> > offMax=0xb38 MW> > MW> > [tiger@tiger]~%uname -a MW> > FreeBSD tiger.minsk.domain 8.0-CURRENT FreeBSD 8.0-CURRENT #26: MW> > Fri May 8 15:32:29 EEST 2009 MW> > root@tiger.minsk.domain:/usr/obj/usr/src/sys/tiger-desktop i386 MW> > MW> > backtrace - http://tiger.ipfw.ru/files/bt.txt MW> > MW> > MW> MW> > MW> PS: Yes this run is for AMD64 and HEAD MW> > MW> users! MW> > MW> MW> > MW> MW> > MW> http://people.freebsd.org/~miwi/vbox/virtualbox_3.tgz MW> > MW> MW> > MW> MW> > MW> Happy Testing! MW> > MW> MW> > MW> - -- MW> > MW> MW> > MW> +-----------------------+-------------------------------+ MW> > MW> | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | MW> > MW> | ICQ : 169139903 | Mail : miwi(at)FreeBSD.org | MW> > MW> +-----------------------+-------------------------------+ MW> > MW> | Mess with the Best, Die like the MW> > MW> Rest! | MW> > MW> +-----------------------+-------------------------------+ MW> > MW> -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) MW> > MW> MW> > MW> iEYEARECAAYFAkoSeCYACgkQdLJIhLHm/OkuOQCfVzr7yTxydbo6npBgO2LyZNk1 MW> > MW> RpUAnAmxjlHTBsM8pJ5SIiPIqQRCWElu MW> > MW> =LoBM MW> > MW> -----END PGP SIGNATURE----- MW> > MW> > -- MW> > wbr, tiger MW> > MW> MW> - -- MW> MW> +-----------------------+-------------------------------+ MW> | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | MW> | ICQ : 169139903 | Mail : miwi(at)FreeBSD.org | MW> +-----------------------+-------------------------------+ MW> | Mess with the Best, Die like the Rest! | MW> +-----------------------+-------------------------------+ MW> -----BEGIN PGP SIGNATURE----- MW> Version: GnuPG v2.0.11 (FreeBSD) MW> MW> iEYEARECAAYFAkoSmkwACgkQdLJIhLHm/Ony5gCg4iWUTPqjrIJoY+hmLndSD5Ml MW> d6kAoNIE/VCuRHnqShzuywsGOb9pKVcP MW> =IRJZ MW> -----END PGP SIGNATURE----- -- wbr, tiger From miwi at FreeBSD.org Tue May 19 11:49:12 2009 From: miwi at FreeBSD.org (Martin Wilke) Date: Tue May 19 11:49:29 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: <20090519144240.2040dd20@tiger.minsk.domain> References: <20090514191237.GD70242@bsdcrew.de> <20090517180920.GY71804@bsdcrew.de> <20090519091310.GB71804@bsdcrew.de> <20090519143451.74c2142d@tiger.minsk.domain> <20090519113852.GE71804@bsdcrew.de> <20090519144240.2040dd20@tiger.minsk.domain> Message-ID: <20090519114909.GF71804@bsdcrew.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, May 19, 2009 at 02:42:40PM +0300, Sergey V. Dyatko wrote: > ? Tue, 19 May 2009 13:38:52 +0200 > Martin Wilke ?????: > > MW> -----BEGIN PGP SIGNED MESSAGE----- > MW> Hash: SHA1 > MW> > MW> On Tue, May 19, 2009 at 02:34:51PM +0300, Sergey V. Dyatko wrote: > MW> > ? Tue, 19 May 2009 11:13:10 +0200 > MW> > Martin Wilke ?????: > MW> > > MW> > MW> -----BEGIN PGP SIGNED MESSAGE----- > MW> > MW> Hash: SHA1 > MW> > MW> > MW> > MW> Howdy .. > MW> > MW> > MW> > MW> Next run, > MW> > MW> > MW> > MW> We updated the port to 2.2.2r19801. > MW> > MW> The Patch files/patch-amd64-r0-exec-alloc > MW> > MW> was removed in favor of a similar fix > MW> > MW> commited to upstream. Also was fixed a > MW> > MW> bug on HEAD which should be fix the Kernel > MW> > MW> crash. Please test test test .. :-) > MW> > Thanks, > MW> > after kldload vboxdrv start/stop vm (winxp) is work fine for me. > MW> > But... > MW> > kldunload vboxdrv - ok > MW> > kldload vboxdrv - system hungs. solution: hw reset:( > MW> > MW> How old is your src? > > Fri May 8 15:32:29 EEST 2009 > > virtualbox is 2.2.2r19801 > Ok, Can you please update your src/kernel after that please rebuild vbox. That should be fix the crash. - - Martin - -- +-----------------------+-------------------------------+ | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | | ICQ : 169139903 | Mail : miwi(at)FreeBSD.org | +-----------------------+-------------------------------+ | Mess with the Best, Die like the Rest! | +-----------------------+-------------------------------+ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAkoSnLUACgkQdLJIhLHm/OlnuwCfX1yGFsfMbxiluoDAx+1lDxuB uSEAn1lM2r4xjfJAa2GnJYUAI5nsLlCN =Rn5t -----END PGP SIGNATURE----- From sergey.dyatko at gmail.com Tue May 19 11:56:23 2009 From: sergey.dyatko at gmail.com (Sergey V. Dyatko) Date: Tue May 19 11:56:29 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: <20090519114909.GF71804@bsdcrew.de> References: <20090514191237.GD70242@bsdcrew.de> <20090517180920.GY71804@bsdcrew.de> <20090519091310.GB71804@bsdcrew.de> <20090519143451.74c2142d@tiger.minsk.domain> <20090519113852.GE71804@bsdcrew.de> <20090519144240.2040dd20@tiger.minsk.domain> <20090519114909.GF71804@bsdcrew.de> Message-ID: <20090519145618.15cbde42@tiger.minsk.domain> ? Tue, 19 May 2009 13:49:09 +0200 Martin Wilke ?????: MW> -----BEGIN PGP SIGNED MESSAGE----- MW> Hash: SHA1 MW> MW> On Tue, May 19, 2009 at 02:42:40PM +0300, Sergey V. Dyatko wrote: MW> > ? Tue, 19 May 2009 13:38:52 +0200 MW> > Martin Wilke ?????: MW> > MW> > MW> -----BEGIN PGP SIGNED MESSAGE----- MW> > MW> Hash: SHA1 MW> > MW> MW> > MW> On Tue, May 19, 2009 at 02:34:51PM +0300, Sergey V. Dyatko MW> > MW> wrote: MW> > MW> > ? Tue, 19 May 2009 11:13:10 +0200 MW> > MW> > Martin Wilke ?????: MW> > MW> > MW> > MW> > MW> -----BEGIN PGP SIGNED MESSAGE----- MW> > MW> > MW> Hash: SHA1 MW> > MW> > MW> MW> > MW> > MW> Howdy .. MW> > MW> > MW> MW> > MW> > MW> Next run, MW> > MW> > MW> MW> > MW> > MW> We updated the port to 2.2.2r19801. MW> > MW> > MW> The Patch files/patch-amd64-r0-exec-alloc MW> > MW> > MW> was removed in favor of a similar fix MW> > MW> > MW> commited to upstream. Also was fixed a MW> > MW> > MW> bug on HEAD which should be fix the Kernel MW> > MW> > MW> crash. Please test test test .. :-) MW> > MW> > Thanks, MW> > MW> > after kldload vboxdrv start/stop vm (winxp) is work fine MW> > MW> > for me. But... MW> > MW> > kldunload vboxdrv - ok MW> > MW> > kldload vboxdrv - system hungs. solution: hw reset:( MW> > MW> MW> > MW> How old is your src? MW> > MW> > Fri May 8 15:32:29 EEST 2009 MW> > MW> > virtualbox is 2.2.2r19801 MW> > MW> MW> MW> Ok, Can you please update your src/kernel after MW> that please rebuild vbox. That should be fix the crash. MW> Ok, I'll try MW> - - Martin MW> MW> - -- MW> MW> +-----------------------+-------------------------------+ MW> | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | MW> | ICQ : 169139903 | Mail : miwi(at)FreeBSD.org | MW> +-----------------------+-------------------------------+ MW> | Mess with the Best, Die like the Rest! | MW> +-----------------------+-------------------------------+ MW> -----BEGIN PGP SIGNATURE----- MW> Version: GnuPG v2.0.11 (FreeBSD) MW> MW> iEYEARECAAYFAkoSnLUACgkQdLJIhLHm/OlnuwCfX1yGFsfMbxiluoDAx+1lDxuB MW> uSEAn1lM2r4xjfJAa2GnJYUAI5nsLlCN MW> =Rn5t MW> -----END PGP SIGNATURE----- -- wbr, tiger From snasonov at bcc.ru Tue May 19 12:32:18 2009 From: snasonov at bcc.ru (Sergey G Nasonov) Date: Tue May 19 12:32:27 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: <20090519091310.GB71804@bsdcrew.de> References: <20090514191237.GD70242@bsdcrew.de> <20090517180920.GY71804@bsdcrew.de> <20090519091310.GB71804@bsdcrew.de> Message-ID: <200905191606.27514.snasonov@bcc.ru> On Tuesday 19 May 2009 13:13:10 Martin Wilke wrote: > Howdy .. > > Next run, > > We updated the port to 2.2.2r19801. > The Patch files/patch-amd64-r0-exec-alloc > was removed in favor of a similar fix > commited to upstream. Also was fixed a > bug on HEAD which should be fix the Kernel > crash. Please test test test .. :-) > > PS: Yes this run is for AMD64 and HEAD > users! > > > http://people.freebsd.org/~miwi/vbox/virtualbox_3.tgz > > > Happy Testing! FreeBSD snasonovnbwxp.bcc 8.0-CURRENT FreeBSD 8.0-CURRENT #23: Tue May 19 11:26:37 MSD 2009 snasonov@snasonovnbwxp.bcc:/usr/obj/usr/current/src/sys/CUSTOM i386 With this version I can succesfuly run VM (now it Windows XP 32 bit). All previous versions at VM start lead system to hang. Thanks! -- Best Regards, Nasonov Sergey mailto:snasonov@bcc.ru From hyogeollee at gmail.com Tue May 19 12:36:46 2009 From: hyogeollee at gmail.com (Hyogeol Lee) Date: Tue May 19 12:36:58 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 Message-ID: <4A12A098.4070707@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 > Howdy .. > > Next run, > > We updated the port to 2.2.2r19801. > The Patch files/patch-amd64-r0-exec- > alloc > was removed in favor of a similar fix > commited to upstream. Also was fixed a > bug on HEAD which should be fix the Kernel > crash. Please test test test .. :-) > > PS: Yes this run is for AMD64 and HEAD > users! > > > http://people.freebsd.org/~miwi/vbox/virtualbox_3.tgz > > > > Happy Testing! > Hi, I'm using -current/amd64 and it works fine with new port. But it is need to *turn off VT-x/AMD-V* to run VM. I could not run VM when I turn on VT-x/AMD-V. (I'm using VT-X supported processor, Q9450.) Anyway, nice works! Regards, - ---- Hyogeol Lee hyogeollee@gmail.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREKAAYFAkoSoJYACgkQ1D7/GiH6QSFeowCglEKXInWYffShYWh4YMYjzupN vbIAoK4XsHsx5ASAnolq1F1aBIFYVgjl =4cD8 -----END PGP SIGNATURE----- From gperez at entel.upc.edu Tue May 19 15:01:19 2009 From: gperez at entel.upc.edu (=?ISO-8859-1?Q?Gustau_P=E9rez?=) Date: Tue May 19 15:01:27 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: <4A128253.7040400@fletchermoorland.co.uk> References: <20090514191237.GD70242@bsdcrew.de> <20090517180920.GY71804@bsdcrew.de> <20090519091310.GB71804@bsdcrew.de> <4A128253.7040400@fletchermoorland.co.uk> Message-ID: <4A128891.6010504@entel.upc.edu> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Paul Wootton wrote: > Martin Wilke wrote: Howdy .. > > Next run, > > We updated the port to 2.2.2r19801. The Patch > files/patch-amd64-r0-exec-alloc was removed in favor of a similar > fix commited to upstream. Also was fixed a bug on HEAD which should > be fix the Kernel crash. Please test test test .. :-) > > PS: Yes this run is for AMD64 and HEAD users! > > > http://people.freebsd.org/~miwi/vbox/virtualbox_3.tgz > > > Happy Testing! > Reporting, For my system : FreeBSD portatil 8.0-CURRENT FreeBSD 8.0-CURRENT #40: Mon May 18 09:09:07 CEST 2009 gus@gusiport:/usr/obj/usr/src/sys/CUSTOM i386 the second run problem (when virtualbox argued about the missing kernel support) has dissapeared. The only problem is that when I try to start the virtual machine, its screen remains gray. Any hint about this particular problem ? Any has an idea where the problem can be, to start looking for a solution ? Moreover, will try to try :) in CURRENT-AMD64 in the same. Will take me long, cause I think I wipe the installation some time ago :( Regards, Gus - -- PGP KEY : http://www-entel.upc.edu/gus/gus.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkoSiJEACgkQAvcpDulVChDw6gCfRFgAxLfLBW5P5HfcKhAa9J3e 4koAn0Scteq4oWU3MSDtWU1T3v0lGipE =eTer -----END PGP SIGNATURE----- From jahnke at sonatabio.com Tue May 19 15:55:22 2009 From: jahnke at sonatabio.com (Frank Jahnke) Date: Tue May 19 15:55:28 2009 Subject: Problem with loading VirtualBox kernel module Message-ID: <1242748373.1193.9.camel@zinfandel> I have a problem loading the VirtualBox kernel module. From a fresh port build, it loads fine, and the VM is stable. I've tried that three or four times. Subsequent loading of the kernel module locks the system, giving a page fault error (trap 12). Only one time was I able to load it; about a dozen times it froze. It does not matter if I have X11 loaded or not, or if ACPI is running (there are some quirks with the BIOS). The computer is a very old 32-bit dual CPU Athlon (so no VTx extensions); this has happened for both the original virtualbox port and for take2. FreeBSD 7-STABLE, VBox and the kernel source were synced on May 15. Please let me know what additional information would be useful. Frank From lists at yamagi.org Tue May 19 16:50:58 2009 From: lists at yamagi.org (Yamagi Burmeister) Date: Tue May 19 16:51:04 2009 Subject: [new port] graphics/linux-dri74 In-Reply-To: <20090515145252.GA69488@yamagi.org> References: <92596693@bb.ipt.ru> <20090510174445.GA75441@yamagi.org> <67576966@bb.ipt.ru> <20090515145252.GA69488@yamagi.org> Message-ID: <20090519165039.GA12505@yamagi.org> Okay, I investigated further. First I tried a FreeBSD/i386 version of ioQuake3 on a FreeBSD/amd64 host. After some minor and unrelated problems it worked. After that I tried to debug the linux-dri74. Reading the source and doing a lot test runs I realized, that there are in fact two problems. Every ten starts or so the userland side of drm crashes: yamagi@saya:ttyp3 ~: /usr/compat/linux/usr/bin/glxinfo name of display: :0.0 libGL: XF86DRIGetClientDriverName: 5.3.0 r300 (screen 0) libGL: OpenDriver: trying /usr/lib/dri/tls/r300_dri.so libGL: OpenDriver: trying /usr/lib/dri/r300_dri.so drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 4, (OK) DRM_IOCTL_VERSION: Bad address Segmentation fault (core dumped) The other times the userland side of drm is able to open the drm-device bit is unable to initalize it. The error message is somewhat missleading: yamagi@saya:ttyp3 ~: /usr/compat/linux/usr/bin/glxinfo name of display: :0.0 libGL: XF86DRIGetClientDriverName: 5.3.0 r300 (screen 0) libGL: OpenDriver: trying /usr/lib/dri/tls/r300_dri.so libGL: OpenDriver: trying /usr/lib/dri/r300_dri.so drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 4, (OK) drmOpenByBusid: Searching for BusID pci:0000:01:00.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 4, (OK) drmOpenByBusid: drmOpenMinor returns 4 drmOpenByBusid: drmGetBusid reports (null) drmOpenDevice: node name is /dev/dri/card1 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card2 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card3 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card4 drmOpenByBusid: drmOpenMinor returns -1 [..] drmOpenDevice: node name is /dev/dri/card14 drmOpenByBusid: drmOpenMinor returns -1 libGL error: drmOpenOnce failed (Operation not permitted) libGL error: reverting to software direct rendering libGL: OpenDriver: trying /usr/lib/dri/tls/swrast_dri.so libGL: OpenDriver: trying /usr/lib/dri/swrast_dri.so display: :0 screen: 0 direct rendering: Yes So I added debug printf() into the code. I stepped through it. After some hours of intesive debugging im 99% sure, that both of the above failures of linux-drm74 are originating at the kernel side. It's most likely NOT a problem of the userland side and therefor not a problem of the port. I'll investigate further at the kernel side, but that'll need some time. So, while it's the fault linux-drm74, what about a little warning message in the install message of the port? Just to be sure, that other users experiencing the same problem know, that it is not a bug of linux-dr74. Ciao, Yamagi -- Homepage: www.yamagi.org Jabber: yamagi@yamagi.org GnuPG/GPG: 0xEFBCCBCB -------------- 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/20090519/d1504c0f/attachment.pgp From mickael.torres at gmail.com Tue May 19 17:56:40 2009 From: mickael.torres at gmail.com (Mickael Torres) Date: Tue May 19 17:56:52 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: <20090517180920.GY71804@bsdcrew.de> References: <20090514191237.GD70242@bsdcrew.de> <20090517180920.GY71804@bsdcrew.de> Message-ID: On 17 mai 09, at 20:09, Martin Wilke wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > We rolled a new tarball with the patch from Juergen Lock [1] > with a posible fix for AMD64 users, tested on 3 machines > which now works without problems. Many Thanks to him for > his nice work! > > http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz > > Martin > Tested on a 7-stable/amd64 from yesterday. Works great with VT with win64 / openbsd64 guests. Thanks :) Mike. > - -- > > +-----------------------+-------------------------------+ > | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | > | ICQ : 169139903 | Mail : miwi(at)FreeBSD.org | > +-----------------------+-------------------------------+ > | Mess with the Best, Die like the Rest! | > +-----------------------+-------------------------------+ > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.11 (FreeBSD) > > iEUEARECAAYFAkoQUtAACgkQdLJIhLHm/OlY2QCg1KZW2YCvE1VhqKgSQ/xhjKIx > U60Al2UMniKg+KvQ6m9RcP92eOMddfQ= > =kB6c > -----END PGP SIGNATURE----- > _______________________________________________ > 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 tijl at ulyssis.org Tue May 19 18:12:10 2009 From: tijl at ulyssis.org (Tijl Coosemans) Date: Tue May 19 18:12:17 2009 Subject: [new port] graphics/linux-dri74 In-Reply-To: <20090519165039.GA12505@yamagi.org> References: <92596693@bb.ipt.ru> <20090515145252.GA69488@yamagi.org> <20090519165039.GA12505@yamagi.org> Message-ID: <200905192012.06401.tijl@ulyssis.org> On Tuesday 19 May 2009 18:50:39 Yamagi Burmeister wrote: > Okay, I investigated further. First I tried a FreeBSD/i386 version of > ioQuake3 on a FreeBSD/amd64 host. After some minor and unrelated > problems it worked. > > After that I tried to debug the linux-dri74. Reading the source and > doing a lot test runs I realized, that there are in fact two > problems. Every ten starts or so the userland side of drm crashes: > > yamagi@saya:ttyp3 ~: /usr/compat/linux/usr/bin/glxinfo > name of display: :0.0 > libGL: XF86DRIGetClientDriverName: 5.3.0 r300 (screen 0) > libGL: OpenDriver: trying /usr/lib/dri/tls/r300_dri.so > libGL: OpenDriver: trying /usr/lib/dri/r300_dri.so > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: open result is 4, (OK) > DRM_IOCTL_VERSION: Bad address > Segmentation fault (core dumped) > > The other times the userland side of drm is able to open the > drm-device bit is unable to initalize it. The error message is > somewhat missleading: > > yamagi@saya:ttyp3 ~: /usr/compat/linux/usr/bin/glxinfo > name of display: :0.0 > libGL: XF86DRIGetClientDriverName: 5.3.0 r300 (screen 0) > libGL: OpenDriver: trying /usr/lib/dri/tls/r300_dri.so > libGL: OpenDriver: trying /usr/lib/dri/r300_dri.so > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: open result is 4, (OK) > drmOpenByBusid: Searching for BusID pci:0000:01:00.0 > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: open result is 4, (OK) > drmOpenByBusid: drmOpenMinor returns 4 > drmOpenByBusid: drmGetBusid reports (null) > drmOpenDevice: node name is /dev/dri/card1 > drmOpenByBusid: drmOpenMinor returns -1 > drmOpenDevice: node name is /dev/dri/card2 > drmOpenByBusid: drmOpenMinor returns -1 > drmOpenDevice: node name is /dev/dri/card3 > drmOpenByBusid: drmOpenMinor returns -1 > drmOpenDevice: node name is /dev/dri/card4 > drmOpenByBusid: drmOpenMinor returns -1 > [..] > drmOpenDevice: node name is /dev/dri/card14 > drmOpenByBusid: drmOpenMinor returns -1 > libGL error: drmOpenOnce failed (Operation not permitted) > libGL error: reverting to software direct rendering > libGL: OpenDriver: trying /usr/lib/dri/tls/swrast_dri.so > libGL: OpenDriver: trying /usr/lib/dri/swrast_dri.so > display: :0 screen: 0 > direct rendering: Yes > > So I added debug printf() into the code. I stepped through it. After > some hours of intesive debugging im 99% sure, that both of the above > failures of linux-drm74 are originating at the kernel side. It's most > likely NOT a problem of the userland side and therefor not a problem > of the port. > > I'll investigate further at the kernel side, but that'll need some > time. So, while it's the fault linux-drm74, what about a little > warning message in the install message of the port? Just to be sure, > that other users experiencing the same problem know, that it is not a > bug of linux-dr74. I noticed you use the r300 driver so maybe this patch helps: http://people.freebsd.org/~rnoland/drm_radeon-copyin-fix-try2.patch Robert Noland (CCed) probably knows more about this though. http://lists.freebsd.org/pipermail/freebsd-emulation/2009-May/005995.html From olivier at gid0.org Tue May 19 18:50:19 2009 From: olivier at gid0.org (Olivier SMEDTS) Date: Tue May 19 18:50:31 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: <20090519091310.GB71804@bsdcrew.de> References: <20090514191237.GD70242@bsdcrew.de> <20090517180920.GY71804@bsdcrew.de> <20090519091310.GB71804@bsdcrew.de> Message-ID: <367b2c980905191123p66e36eb5j243b1b1701f729a7@mail.gmail.com> 2009/5/19 Martin Wilke : > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Howdy .. > > Next run, > > We updated the port to 2.2.2r19801. > The Patch files/patch-amd64-r0-exec-alloc > was removed in favor of a similar fix > commited to upstream. Also was fixed a > bug on HEAD which should be fix the Kernel > crash. Please test test test .. :-) > > PS: Yes this run is for AMD64 and HEAD > ? ?users! > > > http://people.freebsd.org/~miwi/vbox/virtualbox_3.tgz > > > Happy Testing! Tested, installed fine but I can only run guests without VT (so only 32-bits). I'm using latest -CURRENT on amd64 (Intel Core2 Quad Q9450). Seems to work fine (but slowly) for 32-bit guests without VT. Thanks ! > - -- > > +-----------------------+-------------------------------+ > | ?PGP ? ?: 0xB1E6FCE9 ?| ?Jabber : miwi(at)BSDCrew.de ?| > | ?ICQ ? ?: 169139903 ? | ?Mail ? : miwi(at)FreeBSD.org | > +-----------------------+-------------------------------+ > | ? ? ? Mess with the Best, Die like the Rest! ? ? ? ? ?| > +-----------------------+-------------------------------+ > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.11 (FreeBSD) > > iEYEARECAAYFAkoSeCYACgkQdLJIhLHm/OkuOQCfVzr7yTxydbo6npBgO2LyZNk1 > RpUAnAmxjlHTBsM8pJ5SIiPIqQRCWElu > =LoBM > -----END PGP SIGNATURE----- > _______________________________________________ > 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" > -- 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 rnoland at FreeBSD.org Tue May 19 19:37:15 2009 From: rnoland at FreeBSD.org (Robert Noland) Date: Tue May 19 19:37:21 2009 Subject: [new port] graphics/linux-dri74 In-Reply-To: <200905192012.06401.tijl@ulyssis.org> References: <92596693@bb.ipt.ru> <20090515145252.GA69488@yamagi.org> <20090519165039.GA12505@yamagi.org> <200905192012.06401.tijl@ulyssis.org> Message-ID: <1242760698.1752.21.camel@balrog.2hip.net> On Tue, 2009-05-19 at 20:12 +0200, Tijl Coosemans wrote: > On Tuesday 19 May 2009 18:50:39 Yamagi Burmeister wrote: > > Okay, I investigated further. First I tried a FreeBSD/i386 version of > > ioQuake3 on a FreeBSD/amd64 host. After some minor and unrelated > > problems it worked. > > > > After that I tried to debug the linux-dri74. Reading the source and > > doing a lot test runs I realized, that there are in fact two > > problems. Every ten starts or so the userland side of drm crashes: > > > > yamagi@saya:ttyp3 ~: /usr/compat/linux/usr/bin/glxinfo > > name of display: :0.0 > > libGL: XF86DRIGetClientDriverName: 5.3.0 r300 (screen 0) > > libGL: OpenDriver: trying /usr/lib/dri/tls/r300_dri.so > > libGL: OpenDriver: trying /usr/lib/dri/r300_dri.so > > drmOpenDevice: node name is /dev/dri/card0 > > drmOpenDevice: open result is 4, (OK) > > DRM_IOCTL_VERSION: Bad address > > Segmentation fault (core dumped) > > > > The other times the userland side of drm is able to open the > > drm-device bit is unable to initalize it. The error message is > > somewhat missleading: > > > > yamagi@saya:ttyp3 ~: /usr/compat/linux/usr/bin/glxinfo > > name of display: :0.0 > > libGL: XF86DRIGetClientDriverName: 5.3.0 r300 (screen 0) > > libGL: OpenDriver: trying /usr/lib/dri/tls/r300_dri.so > > libGL: OpenDriver: trying /usr/lib/dri/r300_dri.so > > drmOpenDevice: node name is /dev/dri/card0 > > drmOpenDevice: open result is 4, (OK) > > drmOpenByBusid: Searching for BusID pci:0000:01:00.0 > > drmOpenDevice: node name is /dev/dri/card0 > > drmOpenDevice: open result is 4, (OK) > > drmOpenByBusid: drmOpenMinor returns 4 > > drmOpenByBusid: drmGetBusid reports (null) > > drmOpenDevice: node name is /dev/dri/card1 > > drmOpenByBusid: drmOpenMinor returns -1 > > drmOpenDevice: node name is /dev/dri/card2 > > drmOpenByBusid: drmOpenMinor returns -1 > > drmOpenDevice: node name is /dev/dri/card3 > > drmOpenByBusid: drmOpenMinor returns -1 > > drmOpenDevice: node name is /dev/dri/card4 > > drmOpenByBusid: drmOpenMinor returns -1 > > [..] > > drmOpenDevice: node name is /dev/dri/card14 > > drmOpenByBusid: drmOpenMinor returns -1 > > libGL error: drmOpenOnce failed (Operation not permitted) > > libGL error: reverting to software direct rendering > > libGL: OpenDriver: trying /usr/lib/dri/tls/swrast_dri.so > > libGL: OpenDriver: trying /usr/lib/dri/swrast_dri.so > > display: :0 screen: 0 > > direct rendering: Yes > > > > So I added debug printf() into the code. I stepped through it. After > > some hours of intesive debugging im 99% sure, that both of the above > > failures of linux-drm74 are originating at the kernel side. It's most > > likely NOT a problem of the userland side and therefor not a problem > > of the port. > > > > I'll investigate further at the kernel side, but that'll need some > > time. So, while it's the fault linux-drm74, what about a little > > warning message in the install message of the port? Just to be sure, > > that other users experiencing the same problem know, that it is not a > > bug of linux-dr74. > > I noticed you use the r300 driver so maybe this patch helps: > http://people.freebsd.org/~rnoland/drm_radeon-copyin-fix-try2.patch This patch, while it may be useful isn't related to the issue. > Robert Noland (CCed) probably knows more about this though. > http://lists.freebsd.org/pipermail/freebsd-emulation/2009-May/005995.html It looks like the linux version of drmOpen is behaving badly. Possibly, it needs linproc mounted. drmOpen appears to be returning file descriptor 4, which may be being mis-interpreted, but in any case it really shouldn't need keep looking for more cards. robert. -- Robert Noland FreeBSD -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-emulation/attachments/20090519/23da7af6/attachment.pgp From lists at yamagi.org Tue May 19 20:10:48 2009 From: lists at yamagi.org (Yamagi Burmeister) Date: Tue May 19 20:10:55 2009 Subject: [new port] graphics/linux-dri74 In-Reply-To: <1242760698.1752.21.camel@balrog.2hip.net> References: <92596693@bb.ipt.ru> <20090515145252.GA69488@yamagi.org> <20090519165039.GA12505@yamagi.org> <200905192012.06401.tijl@ulyssis.org> <1242760698.1752.21.camel@balrog.2hip.net> Message-ID: <20090519201032.GB12505@yamagi.org> Am Tue, May 19, 2009 at 02:18:17PM -0500 schrieb Robert Noland: > > > yamagi@saya:ttyp3 ~: /usr/compat/linux/usr/bin/glxinfo > > > name of display: :0.0 > > > libGL: XF86DRIGetClientDriverName: 5.3.0 r300 (screen 0) > > > libGL: OpenDriver: trying /usr/lib/dri/tls/r300_dri.so > > > libGL: OpenDriver: trying /usr/lib/dri/r300_dri.so > > > drmOpenDevice: node name is /dev/dri/card0 > > > drmOpenDevice: open result is 4, (OK) > > > DRM_IOCTL_VERSION: Bad address > > > Segmentation fault (core dumped) > > > > > > yamagi@saya:ttyp3 ~: /usr/compat/linux/usr/bin/glxinfo > > > name of display: :0.0 > > > libGL: XF86DRIGetClientDriverName: 5.3.0 r300 (screen 0) > > > libGL: OpenDriver: trying /usr/lib/dri/tls/r300_dri.so > > > libGL: OpenDriver: trying /usr/lib/dri/r300_dri.so > > > drmOpenDevice: node name is /dev/dri/card0 > > > drmOpenDevice: open result is 4, (OK) > > > drmOpenByBusid: Searching for BusID pci:0000:01:00.0 > > > drmOpenDevice: node name is /dev/dri/card0 > > > drmOpenDevice: open result is 4, (OK) > > > drmOpenByBusid: drmOpenMinor returns 4 > > > drmOpenByBusid: drmGetBusid reports (null) > > > drmOpenDevice: node name is /dev/dri/card1 > > > drmOpenByBusid: drmOpenMinor returns -1 > > > drmOpenDevice: node name is /dev/dri/card2 > > > drmOpenByBusid: drmOpenMinor returns -1 > > > drmOpenDevice: node name is /dev/dri/card3 > > > drmOpenByBusid: drmOpenMinor returns -1 > > > drmOpenDevice: node name is /dev/dri/card4 > > > drmOpenByBusid: drmOpenMinor returns -1 > > > [..] > > > drmOpenDevice: node name is /dev/dri/card14 > > > drmOpenByBusid: drmOpenMinor returns -1 > > > libGL error: drmOpenOnce failed (Operation not permitted) > > > libGL error: reverting to software direct rendering > > > libGL: OpenDriver: trying /usr/lib/dri/tls/swrast_dri.so > > > libGL: OpenDriver: trying /usr/lib/dri/swrast_dri.so > > > display: :0 screen: 0 > > > direct rendering: Yes > > > > > I noticed you use the r300 driver so maybe this patch helps: > > http://people.freebsd.org/~rnoland/drm_radeon-copyin-fix-try2.patch > > This patch, while it may be useful isn't related to the issue. As expected, the patch doesn't change anything. > It looks like the linux version of drmOpen is behaving badly. Possibly, > it needs linproc mounted. drmOpen appears to be returning file > descriptor 4, which may be being mis-interpreted, but in any case it > really shouldn't need keep looking for more cards. OK, I tried again. This time linprocfs and even linsysfs where mounted. No change at all, the error message stays exactly the same as shown above. I realy would like to see this issue fixed, but I don't know anything about the internals of DRM. So the only short time help I can offer is providing informations. If you need more, just tell me. Ciao, Yamagi -- Homepage: www.yamagi.org Jabber: yamagi@yamagi.org GnuPG/GPG: 0xEFBCCBCB -------------- 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/20090519/f6979822/attachment.pgp From h.schmalzbauer at omnilan.de Wed May 20 03:04:23 2009 From: h.schmalzbauer at omnilan.de (Harald Schmalzbauer) Date: Wed May 20 03:04:36 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take2 In-Reply-To: <20090519091310.GB71804@bsdcrew.de> References: <20090514191237.GD70242@bsdcrew.de> <20090517180920.GY71804@bsdcrew.de> <20090519091310.GB71804@bsdcrew.de> Message-ID: <4A136FD6.9040208@omnilan.de> Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 196 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-emulation/attachments/20090520/124a2373/signature.pgp From bsam at ipt.ru Wed May 20 10:18:15 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Wed May 20 10:18:21 2009 Subject: Cannot nspluginwrapper problems because of linux-f8-pango vulnerability In-Reply-To: <68c3445d0905182230k453486a5nf13fbf8359f7029a@mail.gmail.com> (Raphael Kubo da Costa's message of "Tue, 19 May 2009 02:30:09 -0300") References: <68c3445d0905182230k453486a5nf13fbf8359f7029a@mail.gmail.com> Message-ID: <69248042@serv3.int.kfs.ru> On Tue, 19 May 2009 02:30:09 -0300 Raphael Kubo da Costa wrote: > I'm trying to get linux-f8-flashplugin10 here with FreeBSD 7.2. I've > already installed it (which means OVERRIDE_LINUX_BASE_PORT and > OVERRIDE_LINUX_NONBASE_PORTS are already correctly set to f8) and now > I'm trying to install the nspluginwrapper port. > However, it always fails with the following error while installing its > dependencies: > ===> linux-f8-gtk2-2.12.8 depends on file: > /compat/linux/usr/lib/libpango-1.0.so.0.1800.4 - not found > ===> Verifying install for > /compat/linux/usr/lib/libpango-1.0.so.0.1800.4 in > /usr/ports/x11-toolkits/linux-f8-pango > ===> linux-f8-pango-1.18.4 has known vulnerabilities: > => pango -- integer overflow. > Reference: > => Please update your ports tree and try again. > *** Error code 1 > Stop in /usr/ports/x11-toolkits/linux-f8-pango. > *** Error code 1 > Stop in /usr/ports/x11-toolkits/linux-f8-gtk2. > *** Error code 1 > Stop in /usr/ports/www/nspluginwrapper. > Looking at the reference, it says it affects linux-f8-pango < 1.24, > but the current port is at 1.18.4 and I don't think there's an updated > Fedora 8 package (== 1.24). Is there a way to prevent this check from > happening? Seems that you are using a port audit tool. Then a manual pages from that tool may help you. WBR -- bsam From bsam at ipt.ru Wed May 20 10:19:59 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Wed May 20 10:20:05 2009 Subject: anyone success with matlab 2009a In-Reply-To: <910e60e80905170511s52e9794fj998b3c2b3d1c0c5b@mail.gmail.com> (dikshie@gmail.com's message of "Sun, 17 May 2009 21:11:25 +0900") References: <910e60e80905170248v64dbaa2fw7c0eb60fbec17938@mail.gmail.com> <200905171343.26892.tijl@ulyssis.org> <910e60e80905170511s52e9794fj998b3c2b3d1c0c5b@mail.gmail.com> Message-ID: <35329148@serv3.int.kfs.ru> On Sun, 17 May 2009 21:11:25 +0900 dikshie wrote: > On Sun, May 17, 2009 at 8:43 PM, Tijl Coosemans wrote: > > There are no linux-f9-* ports. You should use > > OVERRIDE_LINUX_NONBASE_PORT=f8 > there is /usr/ports/emulators/linux_base-f9 > should i uninstall that and install linux_base-f8? Either should work. > > Maybe the install script needs to be run with linux bash. You could try: > > /compat/linux/bin/sh /home/dikshie/mydisc/install > i did it. but i always get: > Internal error 2: Could not determine the path of the > MATLAB root directory. Can't comment on this but ktrace and devel/linux_kdump may help in further investigation. WBR -- bsam From kubito at gmail.com Wed May 20 12:45:13 2009 From: kubito at gmail.com (Raphael Kubo da Costa) Date: Wed May 20 12:45:20 2009 Subject: Cannot nspluginwrapper problems because of linux-f8-pango vulnerability In-Reply-To: <69248042@serv3.int.kfs.ru> References: <68c3445d0905182230k453486a5nf13fbf8359f7029a@mail.gmail.com> <69248042@serv3.int.kfs.ru> Message-ID: <68c3445d0905200545p658b66e4l618aaaf7d19d3e76@mail.gmail.com> 2009/5/20 Boris Samorodov : > Seems that you are using a port audit tool. Then a manual pages from > that tool may help you. I tried running 'make -DDISABLE_VULNERABILITIES install clean' in linux-f8-pango and now the installation process failed with a Floating Point Exception when checking if it was already installed. From bsam at ipt.ru Wed May 20 13:05:19 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Wed May 20 13:05:25 2009 Subject: Cannot nspluginwrapper problems because of linux-f8-pango vulnerability In-Reply-To: <68c3445d0905200545p658b66e4l618aaaf7d19d3e76@mail.gmail.com> (Raphael Kubo da Costa's message of "Wed, 20 May 2009 09:45:11 -0300") References: <68c3445d0905182230k453486a5nf13fbf8359f7029a@mail.gmail.com> <69248042@serv3.int.kfs.ru> <68c3445d0905200545p658b66e4l618aaaf7d19d3e76@mail.gmail.com> Message-ID: <37073556@serv3.int.kfs.ru> On Wed, 20 May 2009 09:45:11 -0300 Raphael Kubo da Costa wrote: > 2009/5/20 Boris Samorodov : > > Seems that you are using a port audit tool. Then a manual pages from > > that tool may help you. > I tried running 'make -DDISABLE_VULNERABILITIES install clean' in > linux-f8-pango and now the installation process failed with a Floating > Point Exception when checking if it was already installed. Please, show "pkg_info -xI linux". WBR -- bsam From gfritz at gmail.com Wed May 20 22:05:38 2009 From: gfritz at gmail.com (Geoff Fritz) Date: Wed May 20 22:05:44 2009 Subject: Linuxulator, 32-bit executables, and linux-from-scratch Message-ID: <20090520213830.GA13304@dev.null> I have a couple of quesiotns about FreeBSD's linux emulation environment. Firstly, does the emulation layer handle the 32-bit Linux binaries natively, or does it rely on FreeBSD's own 32-bit emulation layer? In other words, can I get away with not loading the 32-bit FreeBSD libraries? I've tried searching, but wasn't able to find any relavent infomation about this next item. Has anyone tried a linux-from-scratch bootstrap process under Linuxulator to create a custom environment? Are there any low-level problems that may prevent me from doing so? And, on a related note, is it possible to have multiple linux trees for emulation? That is, if I mount linsys and linproc correctly in another place (other than /compat/linux), will things work as expected? And my last question... I run 7.2-RELEASE/amd64. Is it possible yet to run a 32-bit WINE environemt under the Linux emulation? Last I heard, the 64-bit kernel was lacking a syscall or two to make this possible. Has this changed? Thanks a bunch! -- Geoff From kubito at gmail.com Thu May 21 02:00:48 2009 From: kubito at gmail.com (Raphael Kubo da Costa) Date: Thu May 21 02:00:54 2009 Subject: Cannot nspluginwrapper problems because of linux-f8-pango vulnerability In-Reply-To: <37073556@serv3.int.kfs.ru> References: <68c3445d0905182230k453486a5nf13fbf8359f7029a@mail.gmail.com> <69248042@serv3.int.kfs.ru> <68c3445d0905200545p658b66e4l618aaaf7d19d3e76@mail.gmail.com> <37073556@serv3.int.kfs.ru> Message-ID: <68c3445d0905201900i40faaf97ycc4b3ce70315d2a7@mail.gmail.com> 2009/5/20 Boris Samorodov : > On Wed, 20 May 2009 09:45:11 -0300 Raphael Kubo da Costa wrote: > >> 2009/5/20 Boris Samorodov : >> > Seems that you are using a port audit tool. Then a manual pages from >> > that tool may help you. >> I tried running 'make -DDISABLE_VULNERABILITIES install clean' in >> linux-f8-pango and now the installation process failed with a Floating >> Point Exception when checking if it was already installed. > > Please, show "pkg_info -xI linux". Indeed, for some reason linux_base-fc4 was still installed. After replacing it with linux_base-fc8 everything else ran like a charm, thanks ;) From Alexander at Leidinger.net Thu May 21 10:29:26 2009 From: Alexander at Leidinger.net (Alexander Leidinger) Date: Thu May 21 10:29:33 2009 Subject: Linuxulator, 32-bit executables, and linux-from-scratch In-Reply-To: <20090520213830.GA13304@dev.null> References: <20090520213830.GA13304@dev.null> Message-ID: <20090521122911.00002a24@unknown> On Wed, 20 May 2009 15:38:30 -0600 Geoff Fritz wrote: > I have a couple of quesiotns about FreeBSD's linux emulation > environment. > > Firstly, does the emulation layer handle the 32-bit Linux binaries > natively, or does it rely on FreeBSD's own 32-bit emulation layer? > In other words, can I get away with not loading the 32-bit FreeBSD > libraries? You do not need the FreeBSD lib32 stuff. > I've tried searching, but wasn't able to find any relavent infomation > about this next item. Has anyone tried a linux-from-scratch > bootstrap process under Linuxulator to create a custom environment? Have a look at the gentoo linux_dist ports. This should be similar. > Are there any low-level problems that may prevent me from doing so? > And, on a related note, is it possible to have multiple linux trees > for emulation? That is, if I mount linsys and linproc correctly in > another place (other than /compat/linux), will things work as > expected? It will only work, if you chroot into those directories. Notes: The linux base ports in FreeBSD are designed to play well together with FreeBSD without chroot, you can not really chroot into such an environment. What ever you do with linux from scratch, it will not play as well out of the box with FreeBSD as the linux base ports. So if you go this way, I suggest to only use the from scratch stuff with chroot (or in a linux-only-jail). > And my last question... I run 7.2-RELEASE/amd64. Is it possible yet > to run a 32-bit WINE environemt under the Linux emulation? Last I > heard, the 64-bit kernel was lacking a syscall or two to make this > possible. Has this changed? No, and I don't think someone will spend time to do this. AFAIK wine makes some very low-level assumptions which are not true in the linxulator and most probably will never be true there. Bye, Alexander. From kostikbel at gmail.com Thu May 21 11:05:51 2009 From: kostikbel at gmail.com (Kostik Belousov) Date: Thu May 21 11:06:03 2009 Subject: Linuxulator, 32-bit executables, and linux-from-scratch In-Reply-To: <20090521122911.00002a24@unknown> References: <20090520213830.GA13304@dev.null> <20090521122911.00002a24@unknown> Message-ID: <20090521104933.GE1927@deviant.kiev.zoral.com.ua> On Thu, May 21, 2009 at 12:29:11PM +0200, Alexander Leidinger wrote: > > And my last question... I run 7.2-RELEASE/amd64. Is it possible yet > > to run a 32-bit WINE environemt under the Linux emulation? Last I > > heard, the 64-bit kernel was lacking a syscall or two to make this > > possible. Has this changed? > > No, and I don't think someone will spend time to do this. AFAIK wine > makes some very low-level assumptions which are not true in the > linxulator and most probably will never be true there. Actually, 8.0/amd64 is capable of running FreeBSD/i386 Wine build. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-emulation/attachments/20090521/d68a4dfe/attachment.pgp From Alexander at Leidinger.net Thu May 21 11:22:58 2009 From: Alexander at Leidinger.net (Alexander Leidinger) Date: Thu May 21 11:23:04 2009 Subject: Linuxulator, 32-bit executables, and linux-from-scratch In-Reply-To: <20090521104933.GE1927@deviant.kiev.zoral.com.ua> References: <20090520213830.GA13304@dev.null> <20090521122911.00002a24@unknown> <20090521104933.GE1927@deviant.kiev.zoral.com.ua> Message-ID: <20090521132248.0000157f@unknown> On Thu, 21 May 2009 13:49:33 +0300 Kostik Belousov wrote: > On Thu, May 21, 2009 at 12:29:11PM +0200, Alexander Leidinger wrote: > > > And my last question... I run 7.2-RELEASE/amd64. Is it possible > > > yet to run a 32-bit WINE environemt under the Linux emulation? > > > Last I heard, the 64-bit kernel was lacking a syscall or two to > > > make this possible. Has this changed? > > > > No, and I don't think someone will spend time to do this. AFAIK wine > > makes some very low-level assumptions which are not true in the > > linxulator and most probably will never be true there. > > Actually, 8.0/amd64 is capable of running FreeBSD/i386 Wine build. It runs _fully_? Bye, Alexander. From kostikbel at gmail.com Thu May 21 11:47:24 2009 From: kostikbel at gmail.com (Kostik Belousov) Date: Thu May 21 11:47:31 2009 Subject: Linuxulator, 32-bit executables, and linux-from-scratch In-Reply-To: <20090521132248.0000157f@unknown> References: <20090520213830.GA13304@dev.null> <20090521122911.00002a24@unknown> <20090521104933.GE1927@deviant.kiev.zoral.com.ua> <20090521132248.0000157f@unknown> Message-ID: <20090521114719.GI1927@deviant.kiev.zoral.com.ua> On Thu, May 21, 2009 at 01:22:48PM +0200, Alexander Leidinger wrote: > On Thu, 21 May 2009 13:49:33 +0300 Kostik Belousov > wrote: > > > > On Thu, May 21, 2009 at 12:29:11PM +0200, Alexander Leidinger wrote: > > > > And my last question... I run 7.2-RELEASE/amd64. Is it possible > > > > yet to run a 32-bit WINE environemt under the Linux emulation? > > > > Last I heard, the 64-bit kernel was lacking a syscall or two to > > > > make this possible. Has this changed? > > > > > > No, and I don't think someone will spend time to do this. AFAIK wine > > > makes some very low-level assumptions which are not true in the > > > linxulator and most probably will never be true there. > > > > Actually, 8.0/amd64 is capable of running FreeBSD/i386 Wine build. > > It runs _fully_? I do not have a definition for they _fully_ term, but it did executed some win32 programs in Peter Holm' setup. I am not sure what exactly he did tested. And, win32 codecs for mplayer worked too. This was the point of the r190620. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-emulation/attachments/20090521/f349a512/attachment.pgp From peter at holm.cc Thu May 21 12:36:20 2009 From: peter at holm.cc (Peter Holm) Date: Thu May 21 12:36:26 2009 Subject: Linuxulator, 32-bit executables, and linux-from-scratch In-Reply-To: <20090521114719.GI1927@deviant.kiev.zoral.com.ua> References: <20090520213830.GA13304@dev.null> <20090521122911.00002a24@unknown> <20090521104933.GE1927@deviant.kiev.zoral.com.ua> <20090521132248.0000157f@unknown> <20090521114719.GI1927@deviant.kiev.zoral.com.ua> Message-ID: <20090521120938.GA31371@x2.osted.lan> On Thu, May 21, 2009 at 02:47:19PM +0300, Kostik Belousov wrote: > On Thu, May 21, 2009 at 01:22:48PM +0200, Alexander Leidinger wrote: > > On Thu, 21 May 2009 13:49:33 +0300 Kostik Belousov > > wrote: > > > > > > > On Thu, May 21, 2009 at 12:29:11PM +0200, Alexander Leidinger wrote: > > > > > And my last question... I run 7.2-RELEASE/amd64. Is it possible > > > > > yet to run a 32-bit WINE environemt under the Linux emulation? > > > > > Last I heard, the 64-bit kernel was lacking a syscall or two to > > > > > make this possible. Has this changed? > > > > > > > > No, and I don't think someone will spend time to do this. AFAIK wine > > > > makes some very low-level assumptions which are not true in the > > > > linxulator and most probably will never be true there. > > > > > > Actually, 8.0/amd64 is capable of running FreeBSD/i386 Wine build. > > > > It runs _fully_? > I do not have a definition for they _fully_ term, but it did executed > some win32 programs in Peter Holm' setup. I am not sure what exactly he > did tested. And, win32 codecs for mplayer worked too. > The wine test was firefox with flash, as far as I remember. - Peter > This was the point of the r190620. From avg at icyb.net.ua Thu May 21 16:58:24 2009 From: avg at icyb.net.ua (Andriy Gapon) Date: Thu May 21 16:58:31 2009 Subject: virtualbox wishlist [already :-)] Message-ID: <4A15882B.7030805@icyb.net.ua> I tried the experimental virtualbox port on stable/7 amd64 and I must say I am impressed! Thank you very much! And already a small wishlist: 1. It seems that currently it is impossible to use raw devices with virtualbox - I tried something that I googled up and it didn't work: VBoxManage internalcommands createrawvmdk -filename test.vmdk -rawdisk /dev/zvol/tank/test -register [...] Detected size of raw disk '/dev/zvol/tank/fbsd7_q64' is , an invalid value The raw disk vmdk file was not created 2. it would be nice if VBoxGuestAdditions.iso was included (perhaps as a port option) 3. not sure if it is a feature of virtualbox in general or a porting artifact - my (Intel) 64-bit CPU doesn't support VT-x and as a result can execute only 32-bit guests. There doesn't seem to be any fallback strategy for 64-bit guests. BTW in System/Acceleration tab "Enable VT-x/AMD-V" is shown as greyed out but checked - this was confusing. 4. Minor annoyance - in VirtualBox GUI some text fields get partially "blacked out" after mouse click in them. -- Andriy Gapon From manolis at FreeBSD.org Thu May 21 17:55:50 2009 From: manolis at FreeBSD.org (Manolis Kiagias) Date: Thu May 21 17:56:02 2009 Subject: virtualbox wishlist [already :-)] In-Reply-To: <4A15882B.7030805@icyb.net.ua> References: <4A15882B.7030805@icyb.net.ua> Message-ID: <4A15928D.4070202@FreeBSD.org> Andriy Gapon wrote: > 2. it would be nice if VBoxGuestAdditions.iso was included (perhaps as a port option) > Just noting that the guest additions are may be downloaded from here: http://dlc.sun.com/virtualbox/2.2.2/VBoxGuestAdditions_2.2.2.iso and they work just fine (tried on XP and Vista guests). And by the way, a big thanks to everyone working to make virtualization a reality on FreeBSD! From nagy.istvan1 at chello.hu Thu May 21 18:31:54 2009 From: nagy.istvan1 at chello.hu (NI) Date: Thu May 21 18:32:01 2009 Subject: virtualbox wishlist [already :-)] In-Reply-To: <4A15928D.4070202@FreeBSD.org> References: <4A15882B.7030805@icyb.net.ua> <4A15928D.4070202@FreeBSD.org> Message-ID: <4A159A9B.7010506@chello.hu> +1 ######## ## ## ### ## ## ## ## #### ## ## ## ## ## ### ## ## ## #### ## ## ## ## ## #### ## ## ## #### ## ######### ## ## ## ## ## ### ## ## ## ## ######### ## #### ## ## ## ## ## ## ## ## ### ## ## #### ## ## ## ## ## ## ## ## ## #### :) Manolis Kiagias ?rta: Andriy Gapon wrote: 2. it would be nice if VBoxGuestAdditions.iso was included (perhaps as a port option) Just noting that the guest additions are may be downloaded from here: [1]http://dlc.sun.com/virtualbox/2.2.2/VBoxGuestAdditions_2.2.2.iso and they work just fine (tried on XP and Vista guests). And by the way, a big thanks to everyone working to make virtualization a reality on FreeBSD! _______________________________________________ [2]freebsd-emulation@freebsd.org mailing list [3]http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to [4]"freebsd-emulation-unsubscribe@freebsd.org" _________________________________________________________________ [5]avast! Virus Database (VPS): 090520-0, 2009.05 Tested on: 2009.05.21. 20:17:05 avast! - cop References 1. 3D"http://dlc.sun.com/virtualbox/ 2. 3D"mailto:freebsd-emulation@fr 3. 3D"http://lists.freebsd.org/mailm 4. file://localhost/tmp/3D 5. 3D"http://www.avast.com"/ From tijl at ulyssis.org Thu May 21 19:29:02 2009 From: tijl at ulyssis.org (Tijl Coosemans) Date: Thu May 21 19:29:09 2009 Subject: Linuxulator, 32-bit executables, and linux-from-scratch In-Reply-To: <20090521120938.GA31371@x2.osted.lan> References: <20090520213830.GA13304@dev.null> <20090521114719.GI1927@deviant.kiev.zoral.com.ua> <20090521120938.GA31371@x2.osted.lan> Message-ID: <200905212128.53615.tijl@ulyssis.org> On Thursday 21 May 2009 14:09:38 Peter Holm wrote: > On Thu, May 21, 2009 at 02:47:19PM +0300, Kostik Belousov wrote: >> On Thu, May 21, 2009 at 01:22:48PM +0200, Alexander Leidinger wrote: >>> On Thu, 21 May 2009 13:49:33 +0300 Kostik Belousov wrote: >>>> Actually, 8.0/amd64 is capable of running FreeBSD/i386 Wine build. >>> >>> It runs _fully_? >> >> I do not have a definition for they _fully_ term, but it did >> executed some win32 programs in Peter Holm' setup. I am not sure >> what exactly he did tested. And, win32 codecs for mplayer worked >> too. > > The wine test was firefox with flash, as far as I remember. How did you set this up? Did you build the wine port in a 32 bit jail? From peter at holm.cc Thu May 21 20:08:45 2009 From: peter at holm.cc (Peter Holm) Date: Thu May 21 20:08:51 2009 Subject: Linuxulator, 32-bit executables, and linux-from-scratch In-Reply-To: <200905212128.53615.tijl@ulyssis.org> References: <20090520213830.GA13304@dev.null> <20090521114719.GI1927@deviant.kiev.zoral.com.ua> <20090521120938.GA31371@x2.osted.lan> <200905212128.53615.tijl@ulyssis.org> Message-ID: <20090521200842.GA46280@x2.osted.lan> On Thu, May 21, 2009 at 09:28:51PM +0200, Tijl Coosemans wrote: > On Thursday 21 May 2009 14:09:38 Peter Holm wrote: > > On Thu, May 21, 2009 at 02:47:19PM +0300, Kostik Belousov wrote: > >> On Thu, May 21, 2009 at 01:22:48PM +0200, Alexander Leidinger wrote: > >>> On Thu, 21 May 2009 13:49:33 +0300 Kostik Belousov wrote: > >>>> Actually, 8.0/amd64 is capable of running FreeBSD/i386 Wine build. > >>> > >>> It runs _fully_? > >> > >> I do not have a definition for they _fully_ term, but it did > >> executed some win32 programs in Peter Holm' setup. I am not sure > >> what exactly he did tested. And, win32 codecs for mplayer worked > >> too. > > > > The wine test was firefox with flash, as far as I remember. > > How did you set this up? Did you build the wine port in a 32 bit jail? Hmmm. I sure I did for mplayer in order to get the win32 codecs. I not 100% sure, but I think I installed wine in the jail with "pkg_add -r" + setting the UNAME_m environment variable to "i386". -- Peter From gfritz at gmail.com Fri May 22 01:12:48 2009 From: gfritz at gmail.com (Geoff Fritz) Date: Fri May 22 01:12:55 2009 Subject: Linuxulator, 32-bit executables, and linux-from-scratch In-Reply-To: <20090521122911.00002a24@unknown> References: <20090520213830.GA13304@dev.null> <20090521122911.00002a24@unknown> Message-ID: <20090522011245.GA60713@dev.null> On Thu, May 21, 2009 at 12:29:11PM +0200, Alexander Leidinger wrote: > On Wed, 20 May 2009 15:38:30 -0600 Geoff Fritz wrote: > > > > In other words, can I get away with not loading the 32-bit FreeBSD > > libraries? > > You do not need the FreeBSD lib32 stuff. Good to know. > > I've tried searching, but wasn't able to find any relavent infomation > > about this next item. Has anyone tried a linux-from-scratch > > bootstrap process under Linuxulator to create a custom environment? > > Have a look at the gentoo linux_dist ports. This should be similar. I have a working linux emulation setup (using linux_base-f8-8_11) for running the flash plugin. Would installing the gentoo stuff clobber this at all? > > Are there any low-level problems that may prevent me from doing so? > > And, on a related note, is it possible to have multiple linux trees > > for emulation? That is, if I mount linsys and linproc correctly in > > another place (other than /compat/linux), will things work as > > expected? > > It will only work, if you chroot into those directories. > > Notes: > The linux base ports in FreeBSD are designed to play well > together with FreeBSD without chroot, you can not really chroot into > such an environment. > > What ever you do with linux from scratch, it will not play as well > out of the box with FreeBSD as the linux base ports. So if you go this > way, I suggest to only use the from scratch stuff with chroot (or in > a linux-only-jail). Chroot is what I had in mind, mostly. There are a few linux console apps that I was hoping to use under FreeBSD, but didn't want the overhead of full virtualization. Thanks for the info. -- Geoff From lists at jnielsen.net Fri May 22 02:15:27 2009 From: lists at jnielsen.net (John Nielsen) Date: Fri May 22 02:15:33 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: <1242591163.11490.17.camel@zinfandel> References: <1242591163.11490.17.camel@zinfandel> Message-ID: <200905212141.41344.lists@jnielsen.net> On Sunday 17 May 2009 04:12:43 pm Frank Jahnke wrote: > > Now we think that we solved the most > > problems and are ready for the first Call for Testing. > > Thank you for this. I have installed W2K Server on i386 7-STABLE > system without major heartache. It does not work for me when I am not > root, which causes some minor inconvenience. Otherwise all the updates > so loved by Microsoft installed fine, and the VM itself seems to > function properly. Speed seems to be much better than qemu/kqemu, but > slower than the old VMware port (though that is really a pain to use > these days since it is limited to single core CPUs only). > > Are there plans to do a port of the Guest Additions? Right now the > resolution and bit depth are limited to 800x600, 16 bits, and that > really limits its usefulness. Just a thought / side note / workaround here. You might be better off enabling remote desktop on the W2K guest and then accessing it via net/rdesktop (in ports). That lets Windows give you its own virtualized desktop while using native rendering on your host with arbitrary geometry and depth, etc. > Of course you are starting in the right place: without a stable port > the additions are not of any particular use. JN From Alexander at Leidinger.net Fri May 22 06:05:39 2009 From: Alexander at Leidinger.net (Alexander Leidinger) Date: Fri May 22 06:05:46 2009 Subject: Linuxulator, 32-bit executables, and linux-from-scratch In-Reply-To: <20090522011245.GA60713@dev.null> References: <20090520213830.GA13304@dev.null> <20090521122911.00002a24@unknown> <20090522011245.GA60713@dev.null> Message-ID: <20090522080531.0000792b@unknown> On Thu, 21 May 2009 19:12:45 -0600 Geoff Fritz wrote: > On Thu, May 21, 2009 at 12:29:11PM +0200, Alexander Leidinger wrote: > > On Wed, 20 May 2009 15:38:30 -0600 Geoff Fritz > > wrote: > > > I've tried searching, but wasn't able to find any relavent > > > infomation about this next item. Has anyone tried a > > > linux-from-scratch bootstrap process under Linuxulator to create > > > a custom environment? > > > > Have a look at the gentoo linux_dist ports. This should be similar. > > I have a working linux emulation setup (using linux_base-f8-8_11) for > running the flash plugin. Would installing the gentoo stuff clobber > this at all? The linux_dist ports install into LOCALBASE, not into /compat/linux. Bye, Alexander. From miwi at FreeBSD.org Fri May 22 18:00:01 2009 From: miwi at FreeBSD.org (Martin Wilke) Date: Fri May 22 18:00:21 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 3 Message-ID: <20090522175956.GA33004@bsdcrew.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 We rolled a new version with a fix for all users where has problems with kernel load and unload. Many thanks to Shin-ichi Okano where submitted this patch to the vbox ml. http://people.freebsd.org/~miwi/vbox/virtualbox_4.tgz happy testing. - - Martin PS: Should this work for all maybe we can commit vbox this weekend to the portstree. - -- +-----------------------+-------------------------------+ | 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) iEYEARECAAYFAkoW6BwACgkQdLJIhLHm/Omb0wCfYh2BlN12YQMV2mtpRdXIy/cW WYIAniofRUneutcXfxXJz+DDZ2dwDJuG =6sXC -----END PGP SIGNATURE----- From manolis at FreeBSD.org Fri May 22 18:49:44 2009 From: manolis at FreeBSD.org (Manolis Kiagias) Date: Fri May 22 18:49:50 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 3 In-Reply-To: <20090522175956.GA33004@bsdcrew.de> References: <20090522175956.GA33004@bsdcrew.de> Message-ID: <4A16F3C5.9090309@FreeBSD.org> Martin Wilke wrote: > - Martin > > PS: Should this work for all maybe we can commit vbox > this weekend to the portstree. > Great news, thanks! I've tried both the first and second version (on 7.2-RELEASE i386). For some reason the installation fails to copy the kernel module to /boot/modules although it is there in the package (I've built packages using ports-mgmt/tinderbox) . Had to copy it manually. Other than that it works like a charm and is *very* fast. Will build packages for this version tonight. From gperez at entel.upc.edu Fri May 22 19:54:13 2009 From: gperez at entel.upc.edu (=?ISO-8859-1?Q?Gustau_P=E9rez?=) Date: Fri May 22 19:54:36 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 3 In-Reply-To: <20090522175956.GA33004@bsdcrew.de> References: <20090522175956.GA33004@bsdcrew.de> Message-ID: <4A1702A4.3010102@entel.upc.edu> > > We rolled a new version with a fix for all users where has problems > with kernel load and unload. Many thanks to Shin-ichi Okano where > submitted this patch to the vbox ml. > > http://people.freebsd.org/~miwi/vbox/virtualbox_4.tgz > > happy testing. > > Hi everyone, I'm using i386/CURRENT updated today two hours ago. procfs mounted. Cleaned emulators/virtualbox directory. Unpacked virtualbox_4.tgz, recompiled and reinstalled. Rebooted the machine. Kldloaded vboxdrv.ko. When starting a virtual machine the screen remains gray. No cpu usage at all. As I said in a previous mail, in the same machine it works with STABLE. Any hint ? Regards, -- PGP KEY : http://www-entel.upc.edu/gus/gus.asc From miwi at FreeBSD.org Fri May 22 20:21:08 2009 From: miwi at FreeBSD.org (Martin Wilke) Date: Fri May 22 20:21:26 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 3 In-Reply-To: <4A1702A4.3010102@entel.upc.edu> References: <20090522175956.GA33004@bsdcrew.de> <4A1702A4.3010102@entel.upc.edu> Message-ID: <20090522202102.GB33004@bsdcrew.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, May 22, 2009 at 09:53:08PM +0200, Gustau P?rez wrote: > > > > > We rolled a new version with a fix for all users where has problems > > with kernel load and unload. Many thanks to Shin-ichi Okano where > > submitted this patch to the vbox ml. > > > > http://people.freebsd.org/~miwi/vbox/virtualbox_4.tgz > > > > happy testing. > > > > > Hi everyone, > > I'm using i386/CURRENT updated today two hours ago. procfs mounted. > Cleaned emulators/virtualbox directory. Unpacked virtualbox_4.tgz, > recompiled and reinstalled. Rebooted the machine. Kldloaded > vboxdrv.ko. When starting a virtual machine the screen remains gray. > No cpu usage at all. > > As I said in a previous mail, in the same machine it works with > STABLE. > > Any hint ? > > Regards, rm -rf /tmp/.vbox-* doesen't help ? > > -- > PGP KEY : http://www-entel.upc.edu/gus/gus.asc > - -- +-----------------------+-------------------------------+ | 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) iEYEARECAAYFAkoXCS4ACgkQdLJIhLHm/OndLQCfd2eMo8fhBPGyBQ8VWNf9LMr9 SMsAoKAMie6Ehso0d1KV9fUMXT/oHkbO =jVGl -----END PGP SIGNATURE----- From gperez at entel.upc.edu Fri May 22 20:24:38 2009 From: gperez at entel.upc.edu (=?UTF-8?B?R3VzdGF1IFDDqXJleg==?=) Date: Fri May 22 20:24:55 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 3 In-Reply-To: <20090522202102.GB33004@bsdcrew.de> References: <20090522175956.GA33004@bsdcrew.de> <4A1702A4.3010102@entel.upc.edu> <20090522202102.GB33004@bsdcrew.de> Message-ID: <4A1709EA.2000207@entel.upc.edu> > > > rm -rf /tmp/.vbox-* doesen't help ? > Nope. Vbox recreates the directory /tmp/.vbox-root-ipc. Nothing in /var/log/messages. Do you want an screenshot of it ? Regards, Gus -- PGP KEY : http://www-entel.upc.edu/gus/gus.asc From miwi at FreeBSD.org Fri May 22 20:26:41 2009 From: miwi at FreeBSD.org (Martin Wilke) Date: Fri May 22 20:26:48 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 3 In-Reply-To: <4A1709EA.2000207@entel.upc.edu> References: <20090522175956.GA33004@bsdcrew.de> <4A1702A4.3010102@entel.upc.edu> <20090522202102.GB33004@bsdcrew.de> <4A1709EA.2000207@entel.upc.edu> Message-ID: <20090522202635.GC33004@bsdcrew.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, May 22, 2009 at 10:24:10PM +0200, Gustau P?rez wrote: > > > > > > > rm -rf /tmp/.vbox-* doesen't help ? > > > > Nope. Vbox recreates the directory /tmp/.vbox-root-ipc. Nothing in > /var/log/messages. Do you want an screenshot of it ? Recreates are ok and normal, could you please vbox start with truss and send me the output? - - Martin > > Regards, > > Gus > > > -- > PGP KEY : http://www-entel.upc.edu/gus/gus.asc > - -- +-----------------------+-------------------------------+ | 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) iEYEARECAAYFAkoXCnsACgkQdLJIhLHm/Ok4TwCg00ky7mVkvPhm/+p8Yuhkg8tH su0An2ccm2vd8jjIwAZI9HOyM0vUoaa5 =io6Y -----END PGP SIGNATURE----- From chat95 at mac.com Sat May 23 12:57:02 2009 From: chat95 at mac.com (Maho NAKATA) Date: Sat May 23 12:57:15 2009 Subject: Adding Guestadditions.iso Re: [Call For Testing] VirtualBox for FreeBSD! take 3 In-Reply-To: <20090522202635.GC33004@bsdcrew.de> References: <20090522202102.GB33004@bsdcrew.de> <4A1709EA.2000207@entel.upc.edu> <20090522202635.GC33004@bsdcrew.de> Message-ID: <20090523.213252.193744936.chat95@mac.com> Hi miwi, Here is a patch adding "WITH_GUESTADDITIONS" knob. With this knob we also installs Guest additions.iso. This driver makes Windows XP, Linux and Solaris faster. I'm a newbie to VirtualBox so it is not the correct patch. I don't check it thoroughly but ISO image itself is not a GPL one. Best, --- Makefile 2009-05-23 01:59:37.000000000 +0900 +++ Makefile 2009-05-23 21:14:52.000000000 +0900 @@ -6,16 +6,26 @@ # PORTNAME= virtualbox -PORTVERSION= 2.2.2r19852 +PORTVERSION= ${VBOXVER}r19852 CATEGORIES= emulators kld MASTER_SITES= http://tmp.chruetertee.ch/ \ http://freebsd.unixfreunde.de/sources/ \ http://disasterarea.chruetertee.ch/ \ http://mirror.4bit.ws/ +.if defined(WITH_GUESTADDITIONS) +MASTER_SITES+= http://dlc.sun.com/virtualbox/${VBOXVER}/:guestadditons +DISTFILES= ${DISTNAME}${EXTRACT_SUFX} ${GUESTADDITIONS}:guestaddtions +EXTRACT_ONLY= ${DISTNAME}${EXTRACT_SUFX} +.endif MAINTAINER= decke@bluelife.at COMMENT= A general-purpose full virtualizer for x86 hardware +VBOXVER= 2.2.2 +FETCH_ARGS= -pRr +GUESTADDITIONS_GENERICNAME= VBoxGuestAdditions.iso +GUESTADDITIONS= VBoxGuestAdditions_${VBOXVER}.iso + BUILD_DEPENDS= yasm:${PORTSDIR}/devel/yasm \ as86:${PORTSDIR}/devel/dev86 \ xsltproc:${PORTSDIR}/textproc/libxslt \ @@ -52,6 +62,9 @@ KMODDIR= /boot/modules PLIST_SUB+= KMODDIR=${KMODDIR} +.if defined(WITH_GUESTADDITIONS) +PLIST_FILES+= lib/virtualbox/${GUESTADDITIONS} lib/virtualbox/${GUESTADDITIONS_GENERICNAME} +.endif KMK_CONFIG= VBOX_LIBPATH_X11=${LOCALBASE} @@ -127,7 +140,10 @@ ${MKDIR} ${PREFIX}/lib/virtualbox (cd ${WRKSRC}/out/${KMK_ARCH}/release/bin && ${COPYTREE_SHARE} "*.so *.gc *.r0 components" ${PREFIX}/lib/virtualbox) - +.if defined(WITH_GUESTADDITIONS) + ${INSTALL_DATA} ${DISTDIR}/${GUESTADDITIONS} ${PREFIX}/lib/virtualbox/ + ${LN} -sf ${PREFIX}/lib/virtualbox/${GUESTADDITIONS} ${PREFIX}/lib/virtualbox/${GUESTADDITIONS_GENERICNAME} +.endif ${MKDIR} ${PREFIX}/bin .for f in VBoxBFE VBoxHeadless VBoxManage VBoxNetDHCP VBoxSDL VBoxSVC VBoxXPCOMIPCD VirtualBox ${INSTALL_PROGRAM} ${WRKSRC}/out/${KMK_ARCH}/release/bin/$f ${PREFIX}/lib/virtualbox/ --- distinfo 2009-05-23 01:59:37.000000000 +0900 +++ distinfo 2009-05-23 20:17:28.000000000 +0900 @@ -1,3 +1,6 @@ MD5 (virtualbox-2.2.2r19852.tar.gz) = ff1e05bd04fd7974a90e12394cb58626 SHA256 (virtualbox-2.2.2r19852.tar.gz) = 7b898c643551f5b74d169a79ad41801cc5675b5e57a7da0f700875dd11265a5f SIZE (virtualbox-2.2.2r19852.tar.gz) = 58070688 +MD5 (VBoxGuestAdditions_2.2.2.iso) = 9c09a9e88abe9edd8fec6fd3cf453535 +SHA256 (VBoxGuestAdditions_2.2.2.iso) = 3727c024d8d426443158b1063a9d7355d492da3725470c4c01fafbe4bc382687 +SIZE (VBoxGuestAdditions_2.2.2.iso) = 28755968 -------------- 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/20090523/a032c0c6/attachment.pgp From decke at bluelife.at Sat May 23 17:11:22 2009 From: decke at bluelife.at (Bernhard =?iso-8859-1?Q?Fr=F6hlich?=) Date: Sat May 23 17:11:29 2009 Subject: Adding Guestadditions.iso Re: [Call For Testing] VirtualBox for FreeBSD! take 3 In-Reply-To: <20090523.213252.193744936.chat95@mac.com> References: <20090522202102.GB33004@bsdcrew.de> <4A1709EA.2000207@entel.upc.edu> <20090522202635.GC33004@bsdcrew.de> <20090523.213252.193744936.chat95@mac.com> Message-ID: <8cecb22a6543c2983d85131c931cd9f5.squirrel@webmail.itac.at> On Sat, May 23, 2009 2:32 pm, Maho NAKATA wrote: > Hi miwi, > > Here is a patch adding "WITH_GUESTADDITIONS" knob. > With this knob we also installs > Guest additions.iso. This driver makes Windows XP, Linux and Solaris > faster. > I'm a newbie to VirtualBox so it is not the correct patch. > I don't check it thoroughly but ISO image itself is not a GPL one. Thanks, it's commited with a few modifications. -- Bernhard Fr?hlich http://www.bluelife.at/ From chat95 at mac.com Sat May 23 22:13:46 2009 From: chat95 at mac.com (Maho NAKATA) Date: Sat May 23 22:13:52 2009 Subject: Adding Guestadditions.iso Re: [Call For Testing] VirtualBox for FreeBSD! take 3 In-Reply-To: <8cecb22a6543c2983d85131c931cd9f5.squirrel@webmail.itac.at> References: <20090522202635.GC33004@bsdcrew.de> <20090523.213252.193744936.chat95@mac.com> <8cecb22a6543c2983d85131c931cd9f5.squirrel@webmail.itac.at> Message-ID: <20090524.071143.179888312.chat95@mac.com> From: Bernhard Fr?hlich Subject: Re: Adding Guestadditions.iso Re: [Call For Testing] VirtualBox for FreeBSD! take 3 Date: Sat, 23 May 2009 19:11:16 +0200 (CEST) > On Sat, May 23, 2009 2:32 pm, Maho NAKATA wrote: >> Hi miwi, >> >> Here is a patch adding "WITH_GUESTADDITIONS" knob. >> With this knob we also installs >> Guest additions.iso. This driver makes Windows XP, Linux and Solaris >> faster. >> I'm a newbie to VirtualBox so it is not the correct patch. >> I don't check it thoroughly but ISO image itself is not a GPL one. > > Thanks, it's commited with a few modifications. You're welcome! -- Nakata Maho http://accc.riken.jp/maho/ , http://ja.openoffice.org/ Nakata Maho's PGP public keys: http://accc.riken.jp/maho/maho.pgp.txt -------------- 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/20090523/54b73be5/attachment.pgp From kalinoj1 at iem.pw.edu.pl Sat May 23 22:46:54 2009 From: kalinoj1 at iem.pw.edu.pl (Jedrzej Kalinowski) Date: Sat May 23 22:47:06 2009 Subject: Qemu: Assigning two tap devices to one virtual machine Message-ID: <20090523223024.GA93488@volt.iem.pw.edu.pl> Hello all, I'm running qemu 0.10.5 on CURRENT machine and experienced an interesting problem. I try to run a single qemu machine with two network interfaces (tap's) connected to the same bridge - I need this for playing with m0n0wall for example. The qemu launch looks similiar to this: qemu -net nic -net tap -net nic -net tap -cdrom cdrom.iso -curses What happens is that when qemu starts up - my machine locks (sometimes I manage to kill qemu and recover it, sometimes not). I see that it's a problem with network bridge - looks like the infitine loop of arp requests that get replicated infinitely (it also kills/floods my real network that is connected through the bridge to the tap devices). My question is - have any of You tried to use multiple tap devices within one qemu machine? Can you replicate this problem in your environments? One note: there is no problem if I run two qemus and each of them has a tap device connected to bridge0. They coexist and I have no network issues in both guests. I can post qemu-if{up,down} scripts if needed. All the best, Jedrzej Kalinowski From henry.hu.sh at gmail.com Sun May 24 06:45:08 2009 From: henry.hu.sh at gmail.com (Henry Hu) Date: Sun May 24 06:45:13 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 3 Message-ID: <53a1e0710905232313m5141ec3fne27c8d74e8d385e8@mail.gmail.com> I've tried the virtualbox_4.tgz. It compiled and installed fine, but the screen keeps gray after I started the VM. I tried to debug and found that the VM stops in the wait() call in bios. After hlt instruction, the timer interrupt never arrives. But if I press a key, I can see log messages about it. After I changed kern.hz from 100 to 1000, the problem went away. There's a problem about VMX when installing Windows XP. I installed it with VMX disabled and then enabled VMX. Now I'm running Windows XP smoothly, much faster than qemu. Thanks for the great work! Cheers, Henry From jahnke at sonatabio.com Sun May 24 15:11:53 2009 From: jahnke at sonatabio.com (Frank Jahnke) Date: Sun May 24 15:12:00 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 3 Message-ID: <1243177759.1490.16.camel@zinfandel> > We rolled a new version with a fix for all users where > has problems with kernel load and unload. Sadly this does not work for me. When VBox is freshly installed, the kernel loads fine. After a reboot kldloading vboxdrv.ko still locks the system solid. After the fresh VB install, I loaded the GuestAdditions. The mouse control works fine, but W2K Server reports a video driver error. So I am unable to change screen resolution, which currently is set very low and is not really usable. I've not tested the clipboard or any other feature. Also, the Ethernet connection using the default Ethernet card drops a lot of bits (on the order of 60%). The computer is an old dual CPU Athlon with 2GB ECC/Reg memory running i386 7-STABLE (May 15), xorg-7.4.1, Gnome 2.26.1, nvidia-driver-173.14.18. The VM has 750M Memory allocated to it, and the VBox video driver has 64M assigned, both of which should be plenty. I'd be happy to supply other information if asked, but testing is complicated by the fact that the lock-ups always take me an hour or two to fix. Unlike other crashes, these seem to be rather destructive, and it takes a surprising time to fix things that fsck does not get (like Gnome stuff). Suggestions would be most appreciated. Frank From ulf.lilleengen at gmail.com Sun May 24 17:02:39 2009 From: ulf.lilleengen at gmail.com (Ulf Lilleengen) Date: Sun May 24 17:02:45 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 3 In-Reply-To: <20090522175956.GA33004@bsdcrew.de> References: <20090522175956.GA33004@bsdcrew.de> Message-ID: <20090524170237.GA12352@carrot.geeknest.org> On Fri, May 22, 2009 at 07:59:57PM +0200, Martin Wilke wrote: > > We rolled a new version with a fix for all users where > has problems with kernel load and unload. Many thanks to > Shin-ichi Okano where submitted this patch to the vbox ml. > > http://people.freebsd.org/~miwi/vbox/virtualbox_4.tgz > > happy testing. > > I've had problems with all vbox builds where the machine screen just turns gray: http://people.freebsd.org/~lulf/2009-05-24-185847_1024x768_scrot.png I also have a truss log here (quite big): http://people.freebsd.org/~lulf/virtualbox_truss.log -- Ulf Lilleengen From ulf.lilleengen at gmail.com Sun May 24 17:04:07 2009 From: ulf.lilleengen at gmail.com (Ulf Lilleengen) Date: Sun May 24 17:04:12 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 3 In-Reply-To: <20090524170237.GA12352@carrot.geeknest.org> References: <20090522175956.GA33004@bsdcrew.de> <20090524170237.GA12352@carrot.geeknest.org> Message-ID: <20090524170405.GA12545@carrot.geeknest.org> On s?n, mai 24, 2009 at 07:02:37pm +0200, Ulf Lilleengen wrote: > On Fri, May 22, 2009 at 07:59:57PM +0200, Martin Wilke wrote: > > > > We rolled a new version with a fix for all users where > > has problems with kernel load and unload. Many thanks to > > Shin-ichi Okano where submitted this patch to the vbox ml. > > > > http://people.freebsd.org/~miwi/vbox/virtualbox_4.tgz > > > > happy testing. > > > > > I've had problems with all vbox builds where the machine screen just turns > gray: http://people.freebsd.org/~lulf/2009-05-24-185847_1024x768_scrot.png > > I also have a truss log here (quite big): > http://people.freebsd.org/~lulf/virtualbox_truss.log > I forgot to mention, this is i386, Core Duo CPU -- Ulf Lilleengen From decke at bluelife.at Sun May 24 17:15:07 2009 From: decke at bluelife.at (Bernhard =?iso-8859-1?Q?Fr=F6hlich?=) Date: Sun May 24 17:15:25 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 3 In-Reply-To: <20090524170405.GA12545@carrot.geeknest.org> References: <20090522175956.GA33004@bsdcrew.de> <20090524170237.GA12352@carrot.geeknest.org> <20090524170405.GA12545@carrot.geeknest.org> Message-ID: On Sun, May 24, 2009 7:04 pm, Ulf Lilleengen wrote: > On s?n, mai 24, 2009 at 07:02:37pm +0200, Ulf Lilleengen wrote: >> On Fri, May 22, 2009 at 07:59:57PM +0200, Martin Wilke wrote: >> > >> > We rolled a new version with a fix for all users where >> > has problems with kernel load and unload. Many thanks to >> > Shin-ichi Okano where submitted this patch to the vbox ml. >> > >> > http://people.freebsd.org/~miwi/vbox/virtualbox_4.tgz >> > >> > happy testing. >> > >> > >> I've had problems with all vbox builds where the machine screen just >> turns >> gray: >> http://people.freebsd.org/~lulf/2009-05-24-185847_1024x768_scrot.png >> >> I also have a truss log here (quite big): >> http://people.freebsd.org/~lulf/virtualbox_truss.log >> > I forgot to mention, this is i386, Core Duo CPU It looks like it's the same problem as a few others already mentioned. You could try to set kern.hz=1000 which should help. If that's the case please also test the patch from aeichner that should fix that problem. http://pastebin.ca/1433127 That patch is from upstream and so young that it's not yet included in the port but feedback would be great. -- Bernhard Fr?hlich http://www.bluelife.at/ From ulf.lilleengen at gmail.com Sun May 24 17:51:43 2009 From: ulf.lilleengen at gmail.com (Ulf Lilleengen) Date: Sun May 24 17:51:55 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 3 In-Reply-To: References: <20090522175956.GA33004@bsdcrew.de> <20090524170237.GA12352@carrot.geeknest.org> <20090524170405.GA12545@carrot.geeknest.org> Message-ID: <20090524175105.GA1702@carrot.geeknest.org> On s?n, mai 24, 2009 at 07:15:04pm +0200, Bernhard Fr?hlich wrote: > On Sun, May 24, 2009 7:04 pm, Ulf Lilleengen wrote: > > On s?n, mai 24, 2009 at 07:02:37pm +0200, Ulf Lilleengen wrote: > >> On Fri, May 22, 2009 at 07:59:57PM +0200, Martin Wilke wrote: > >> > > >> > We rolled a new version with a fix for all users where > >> > has problems with kernel load and unload. Many thanks to > >> > Shin-ichi Okano where submitted this patch to the vbox ml. > >> > > >> > http://people.freebsd.org/~miwi/vbox/virtualbox_4.tgz > >> > > >> > happy testing. > >> > > >> > > >> I've had problems with all vbox builds where the machine screen just > >> turns > >> gray: > >> http://people.freebsd.org/~lulf/2009-05-24-185847_1024x768_scrot.png > >> > >> I also have a truss log here (quite big): > >> http://people.freebsd.org/~lulf/virtualbox_truss.log > >> > > I forgot to mention, this is i386, Core Duo CPU > > It looks like it's the same problem as a few others already mentioned. You > could try to set kern.hz=1000 which should help. If that's the case please > also test the patch from aeichner that should fix that problem. This fixes the problem, but I'll try the patch as well as I would like to run at hz=100 :) Thanks! > > http://pastebin.ca/1433127 > > That patch is from upstream and so young that it's not yet included in the > port but feedback would be great. > > -- > Bernhard Fr?hlich > http://www.bluelife.at/ > -- Ulf Lilleengen From miwi at FreeBSD.org Sun May 24 18:18:26 2009 From: miwi at FreeBSD.org (Martin Wilke) Date: Sun May 24 18:18:38 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 3 In-Reply-To: <20090524170237.GA12352@carrot.geeknest.org> References: <20090522175956.GA33004@bsdcrew.de> <20090524170237.GA12352@carrot.geeknest.org> Message-ID: <20090524181820.GD37143@bsdcrew.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, May 24, 2009 at 07:02:38PM +0200, Ulf Lilleengen wrote: > On Fri, May 22, 2009 at 07:59:57PM +0200, Martin Wilke wrote: > > > > We rolled a new version with a fix for all users where > > has problems with kernel load and unload. Many thanks to > > Shin-ichi Okano where submitted this patch to the vbox ml. > > > > http://people.freebsd.org/~miwi/vbox/virtualbox_4.tgz > > > > happy testing. > > > > > I've had problems with all vbox builds where the machine screen just turns > gray: http://people.freebsd.org/~lulf/2009-05-24-185847_1024x768_scrot.png Hi Ulf can you try this patch here: http://pastebin.ca/1433127 this fixed all problems :-). - - Martin > > I also have a truss log here (quite big): > http://people.freebsd.org/~lulf/virtualbox_truss.log > > -- > Ulf Lilleengen > - -- +-----------------------+-------------------------------+ | 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) iEYEARECAAYFAkoZj2wACgkQdLJIhLHm/OmPCgCghhkvqHbZwWJBp6SINiex5YCY HzUAn3pUB6yJvtdhRrVFZOQFTGVa2SOx =JByU -----END PGP SIGNATURE----- From ulf.lilleengen at gmail.com Sun May 24 18:36:32 2009 From: ulf.lilleengen at gmail.com (Ulf Lilleengen) Date: Sun May 24 18:36:44 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 3 In-Reply-To: <20090524181820.GD37143@bsdcrew.de> References: <20090522175956.GA33004@bsdcrew.de> <20090524170237.GA12352@carrot.geeknest.org> <20090524181820.GD37143@bsdcrew.de> Message-ID: <20090524183626.GA1423@carrot.geeknest.org> On s?n, mai 24, 2009 at 08:18:20pm +0200, Martin Wilke wrote: > On Sun, May 24, 2009 at 07:02:38PM +0200, Ulf Lilleengen wrote: > > On Fri, May 22, 2009 at 07:59:57PM +0200, Martin Wilke wrote: > > > > > > We rolled a new version with a fix for all users where > > > has problems with kernel load and unload. Many thanks to > > > Shin-ichi Okano where submitted this patch to the vbox ml. > > > > > > http://people.freebsd.org/~miwi/vbox/virtualbox_4.tgz > > > > > > happy testing. > > > > > > > > I've had problems with all vbox builds where the machine screen just turns > > gray: http://people.freebsd.org/~lulf/2009-05-24-185847_1024x768_scrot.png > > Hi Ulf > > can you try this patch here: > http://pastebin.ca/1433127 > > this fixed all problems :-). Yes indeed :) It works fine on hz=100 as well as 1000 now. Thanks! -- Ulf Lilleengen From nork at FreeBSD.org Sun May 24 20:17:47 2009 From: nork at FreeBSD.org (Norikatsu Shigemura) Date: Sun May 24 20:18:06 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 3 In-Reply-To: <20090522175956.GA33004@bsdcrew.de> References: <20090522175956.GA33004@bsdcrew.de> Message-ID: <20090525051738.6c1c8844.nork@FreeBSD.org> Hi Martin. On Fri, 22 May 2009 19:59:57 +0200 Martin Wilke wrote: > We rolled a new version with a fix for all users where > has problems with kernel load and unload. Many thanks to > Shin-ichi Okano where submitted this patch to the vbox ml. > http://people.freebsd.org/~miwi/vbox/virtualbox_4.tgz I tried to support NLS. Please see also my patch. BTW, In my environment, VBoxREM32.so and VBoxREM64.so was not installed. Do you know why? - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --- Makefile.orig 2009-05-23 01:59:37.000000000 +0900 +++ Makefile 2009-05-25 05:11:37.046564727 +0900 @@ -128,6 +128,9 @@ ${MKDIR} ${PREFIX}/lib/virtualbox (cd ${WRKSRC}/out/${KMK_ARCH}/release/bin && ${COPYTREE_SHARE} "*.so *.gc *.r0 components" ${PREFIX}/lib/virtualbox) + ${MKDIR} ${PREFIX}/lib/virtualbox/nls + (cd ${WRKSRC}/out/${KMK_ARCH}/release/obj/VirtualBox/qtnls && ${COPYTREE_SHARE} "*.qm" ${PREFIX}/lib/virtualbox/nls) + ${MKDIR} ${PREFIX}/bin .for f in VBoxBFE VBoxHeadless VBoxManage VBoxNetDHCP VBoxSDL VBoxSVC VBoxXPCOMIPCD VirtualBox ${INSTALL_PROGRAM} ${WRKSRC}/out/${KMK_ARCH}/release/bin/$f ${PREFIX}/lib/virtualbox/ --- pkg-plist.orig 2009-05-08 03:59:50.000000000 +0900 +++ pkg-plist 2009-05-25 05:11:25.684009015 +0900 @@ -21,8 +21,6 @@ lib/virtualbox/VBoxNetDHCP.so lib/virtualbox/VBoxPython.so lib/virtualbox/VBoxREM.so -lib/virtualbox/VBoxREM32.so -lib/virtualbox/VBoxREM64.so lib/virtualbox/VBoxRT.so lib/virtualbox/VBoxSDL lib/virtualbox/VBoxSDL.so @@ -47,6 +45,63 @@ lib/virtualbox/components/VBoxSVCM.so lib/virtualbox/components/VBoxC.so lib/virtualbox/components/VBoxXPCOMBase.xpt +lib/virtualbox/nls/VirtualBox_ar.qm +lib/virtualbox/nls/VirtualBox_bg.qm +lib/virtualbox/nls/VirtualBox_ca.qm +lib/virtualbox/nls/VirtualBox_cs.qm +lib/virtualbox/nls/VirtualBox_de.qm +lib/virtualbox/nls/VirtualBox_el.qm +lib/virtualbox/nls/VirtualBox_es.qm +lib/virtualbox/nls/VirtualBox_eu.qm +lib/virtualbox/nls/VirtualBox_fi.qm +lib/virtualbox/nls/VirtualBox_fr.qm +lib/virtualbox/nls/VirtualBox_hu.qm +lib/virtualbox/nls/VirtualBox_id.qm +lib/virtualbox/nls/VirtualBox_it.qm +lib/virtualbox/nls/VirtualBox_ja.qm +lib/virtualbox/nls/VirtualBox_km_KH.qm +lib/virtualbox/nls/VirtualBox_ko.qm +lib/virtualbox/nls/VirtualBox_nl.qm +lib/virtualbox/nls/VirtualBox_pl.qm +lib/virtualbox/nls/VirtualBox_pt.qm +lib/virtualbox/nls/VirtualBox_pt_BR.qm +lib/virtualbox/nls/VirtualBox_ro.qm +lib/virtualbox/nls/VirtualBox_ru.qm +lib/virtualbox/nls/VirtualBox_sk.qm +lib/virtualbox/nls/VirtualBox_sr.qm +lib/virtualbox/nls/VirtualBox_sv.qm +lib/virtualbox/nls/VirtualBox_tr.qm +lib/virtualbox/nls/VirtualBox_zh_CN.qm +lib/virtualbox/nls/VirtualBox_zh_TW.qm +lib/virtualbox/nls/qt_ar.qm +lib/virtualbox/nls/qt_bg.qm +lib/virtualbox/nls/qt_ca.qm +lib/virtualbox/nls/qt_cs.qm +lib/virtualbox/nls/qt_de.qm +lib/virtualbox/nls/qt_el.qm +lib/virtualbox/nls/qt_es.qm +lib/virtualbox/nls/qt_eu.qm +lib/virtualbox/nls/qt_fi.qm +lib/virtualbox/nls/qt_fr.qm +lib/virtualbox/nls/qt_hu.qm +lib/virtualbox/nls/qt_id.qm +lib/virtualbox/nls/qt_it.qm +lib/virtualbox/nls/qt_ja.qm +lib/virtualbox/nls/qt_km_KH.qm +lib/virtualbox/nls/qt_ko.qm +lib/virtualbox/nls/qt_nl.qm +lib/virtualbox/nls/qt_pl.qm +lib/virtualbox/nls/qt_pt.qm +lib/virtualbox/nls/qt_pt_BR.qm +lib/virtualbox/nls/qt_ro.qm +lib/virtualbox/nls/qt_ru.qm +lib/virtualbox/nls/qt_sk.qm +lib/virtualbox/nls/qt_sr.qm +lib/virtualbox/nls/qt_sv.qm +lib/virtualbox/nls/qt_tr.qm +lib/virtualbox/nls/qt_zh_CN.qm +lib/virtualbox/nls/qt_zh_TW.qm +@dirrm lib/virtualbox/nls @dirrm lib/virtualbox/components @dirrm lib/virtualbox @cwd / - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - From olivier at gid0.org Sun May 24 22:00:22 2009 From: olivier at gid0.org (Olivier SMEDTS) Date: Sun May 24 22:00:36 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 3 In-Reply-To: <20090525051738.6c1c8844.nork@FreeBSD.org> References: <20090522175956.GA33004@bsdcrew.de> <20090525051738.6c1c8844.nork@FreeBSD.org> Message-ID: <367b2c980905241500p2a6a2f3na45f36fe9ad474d0@mail.gmail.com> 2009/5/24 Norikatsu Shigemura : > Hi Martin. > > On Fri, 22 May 2009 19:59:57 +0200 > Martin Wilke wrote: >> We rolled a new version with a fix for all users where >> has problems with kernel load and unload. Many thanks to >> Shin-ichi Okano where submitted this patch to the vbox ml. >> http://people.freebsd.org/~miwi/vbox/virtualbox_4.tgz > > ? ? ? ?I tried to support NLS. ?Please see also my patch. > > ? ? ? ?BTW, In my environment, VBoxREM32.so and VBoxREM64.so was not > ? ? ? ?installed. ?Do you know why? Same here (amd64). > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > --- Makefile.orig ? ? ? 2009-05-23 01:59:37.000000000 +0900 > +++ Makefile ? ?2009-05-25 05:11:37.046564727 +0900 > @@ -128,6 +128,9 @@ > ? ? ? ?${MKDIR} ${PREFIX}/lib/virtualbox > ? ? ? ?(cd ${WRKSRC}/out/${KMK_ARCH}/release/bin && ${COPYTREE_SHARE} "*.so *.gc *.r0 components" ${PREFIX}/lib/virtualbox) > > + ? ? ? ${MKDIR} ${PREFIX}/lib/virtualbox/nls > + ? ? ? (cd ${WRKSRC}/out/${KMK_ARCH}/release/obj/VirtualBox/qtnls && ${COPYTREE_SHARE} "*.qm" ${PREFIX}/lib/virtualbox/nls) > + > ? ? ? ?${MKDIR} ${PREFIX}/bin > ?.for f in VBoxBFE VBoxHeadless VBoxManage VBoxNetDHCP VBoxSDL VBoxSVC VBoxXPCOMIPCD VirtualBox > ? ? ? ?${INSTALL_PROGRAM} ${WRKSRC}/out/${KMK_ARCH}/release/bin/$f ${PREFIX}/lib/virtualbox/ > --- pkg-plist.orig ? ? ?2009-05-08 03:59:50.000000000 +0900 > +++ pkg-plist ? 2009-05-25 05:11:25.684009015 +0900 > @@ -21,8 +21,6 @@ > ?lib/virtualbox/VBoxNetDHCP.so > ?lib/virtualbox/VBoxPython.so > ?lib/virtualbox/VBoxREM.so > -lib/virtualbox/VBoxREM32.so > -lib/virtualbox/VBoxREM64.so > ?lib/virtualbox/VBoxRT.so > ?lib/virtualbox/VBoxSDL > ?lib/virtualbox/VBoxSDL.so > @@ -47,6 +45,63 @@ > ?lib/virtualbox/components/VBoxSVCM.so > ?lib/virtualbox/components/VBoxC.so > ?lib/virtualbox/components/VBoxXPCOMBase.xpt > +lib/virtualbox/nls/VirtualBox_ar.qm > +lib/virtualbox/nls/VirtualBox_bg.qm > +lib/virtualbox/nls/VirtualBox_ca.qm > +lib/virtualbox/nls/VirtualBox_cs.qm > +lib/virtualbox/nls/VirtualBox_de.qm > +lib/virtualbox/nls/VirtualBox_el.qm > +lib/virtualbox/nls/VirtualBox_es.qm > +lib/virtualbox/nls/VirtualBox_eu.qm > +lib/virtualbox/nls/VirtualBox_fi.qm > +lib/virtualbox/nls/VirtualBox_fr.qm > +lib/virtualbox/nls/VirtualBox_hu.qm > +lib/virtualbox/nls/VirtualBox_id.qm > +lib/virtualbox/nls/VirtualBox_it.qm > +lib/virtualbox/nls/VirtualBox_ja.qm > +lib/virtualbox/nls/VirtualBox_km_KH.qm > +lib/virtualbox/nls/VirtualBox_ko.qm > +lib/virtualbox/nls/VirtualBox_nl.qm > +lib/virtualbox/nls/VirtualBox_pl.qm > +lib/virtualbox/nls/VirtualBox_pt.qm > +lib/virtualbox/nls/VirtualBox_pt_BR.qm > +lib/virtualbox/nls/VirtualBox_ro.qm > +lib/virtualbox/nls/VirtualBox_ru.qm > +lib/virtualbox/nls/VirtualBox_sk.qm > +lib/virtualbox/nls/VirtualBox_sr.qm > +lib/virtualbox/nls/VirtualBox_sv.qm > +lib/virtualbox/nls/VirtualBox_tr.qm > +lib/virtualbox/nls/VirtualBox_zh_CN.qm > +lib/virtualbox/nls/VirtualBox_zh_TW.qm > +lib/virtualbox/nls/qt_ar.qm > +lib/virtualbox/nls/qt_bg.qm > +lib/virtualbox/nls/qt_ca.qm > +lib/virtualbox/nls/qt_cs.qm > +lib/virtualbox/nls/qt_de.qm > +lib/virtualbox/nls/qt_el.qm > +lib/virtualbox/nls/qt_es.qm > +lib/virtualbox/nls/qt_eu.qm > +lib/virtualbox/nls/qt_fi.qm > +lib/virtualbox/nls/qt_fr.qm > +lib/virtualbox/nls/qt_hu.qm > +lib/virtualbox/nls/qt_id.qm > +lib/virtualbox/nls/qt_it.qm > +lib/virtualbox/nls/qt_ja.qm > +lib/virtualbox/nls/qt_km_KH.qm > +lib/virtualbox/nls/qt_ko.qm > +lib/virtualbox/nls/qt_nl.qm > +lib/virtualbox/nls/qt_pl.qm > +lib/virtualbox/nls/qt_pt.qm > +lib/virtualbox/nls/qt_pt_BR.qm > +lib/virtualbox/nls/qt_ro.qm > +lib/virtualbox/nls/qt_ru.qm > +lib/virtualbox/nls/qt_sk.qm > +lib/virtualbox/nls/qt_sr.qm > +lib/virtualbox/nls/qt_sv.qm > +lib/virtualbox/nls/qt_tr.qm > +lib/virtualbox/nls/qt_zh_CN.qm > +lib/virtualbox/nls/qt_zh_TW.qm > +@dirrm lib/virtualbox/nls > ?@dirrm lib/virtualbox/components > ?@dirrm lib/virtualbox > ?@cwd / > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > _______________________________________________ > 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 chat95 at mac.com Mon May 25 06:19:45 2009 From: chat95 at mac.com (Maho NAKATA) Date: Mon May 25 06:20:05 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 3 In-Reply-To: <20090525051738.6c1c8844.nork@FreeBSD.org> References: <20090522175956.GA33004@bsdcrew.de> <20090525051738.6c1c8844.nork@FreeBSD.org> Message-ID: <20090525.151740.98935220.chat95@mac.com> Hi Miwi and nork-san From: Norikatsu Shigemura Subject: Re: [Call For Testing] VirtualBox for FreeBSD! take 3 Date: Mon, 25 May 2009 05:17:38 +0900 > BTW, In my environment, VBoxREM32.so and VBoxREM64.so was not > installed. Do you know why? I don't know but it also happen to me. I have this problem on 7.2-RELEASE/amd64. Thank you, -- Nakata Maho http://accc.riken.jp/maho/ , http://ja.openoffice.org/ Nakata Maho's PGP public keys: http://accc.riken.jp/maho/maho.pgp.txt -------------- 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/20090525/3481f06a/attachment.pgp From odhiambo at gmail.com Mon May 25 07:04:21 2009 From: odhiambo at gmail.com (=?UTF-8?B?T2RoaWFtYm8gIOODr+OCt+ODs+ODiOODsw==?=) Date: Mon May 25 07:04:33 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 3 In-Reply-To: <20090525.151740.98935220.chat95@mac.com> References: <20090522175956.GA33004@bsdcrew.de> <20090525051738.6c1c8844.nork@FreeBSD.org> <20090525.151740.98935220.chat95@mac.com> Message-ID: <991123400905242335w30c69fc6n9945f605dfff6cd6@mail.gmail.com> On Mon, May 25, 2009 at 9:17 AM, Maho NAKATA wrote: > Hi Miwi and nork-san > > From: Norikatsu Shigemura > Subject: Re: [Call For Testing] VirtualBox for FreeBSD! take 3 > Date: Mon, 25 May 2009 05:17:38 +0900 > > > BTW, In my environment, VBoxREM32.so and VBoxREM64.so was not > > installed. Do you know why? > > I don't know but it also happen to me. I have this problem on > 7.2-RELEASE/amd64. Not to answer but just to say that on my i386, both files were installed. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ "Clothes make the man. Naked people have little or no influence on society." -- Mark Twain From decke at bluelife.at Mon May 25 07:33:26 2009 From: decke at bluelife.at (Bernhard =?iso-8859-1?Q?Fr=F6hlich?=) Date: Mon May 25 07:33:39 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 3 In-Reply-To: <991123400905242335w30c69fc6n9945f605dfff6cd6@mail.gmail.com> References: <20090522175956.GA33004@bsdcrew.de> <20090525051738.6c1c8844.nork@FreeBSD.org> <20090525.151740.98935220.chat95@mac.com> <991123400905242335w30c69fc6n9945f605dfff6cd6@mail.gmail.com> Message-ID: On Mon, May 25, 2009 8:35 am, Odhiambo ??????????????? wrote: > On Mon, May 25, 2009 at 9:17 AM, Maho NAKATA wrote: > >> Hi Miwi and nork-san >> >> From: Norikatsu Shigemura >> Subject: Re: [Call For Testing] VirtualBox for FreeBSD! take 3 >> Date: Mon, 25 May 2009 05:17:38 +0900 >> >> > BTW, In my environment, VBoxREM32.so and VBoxREM64.so was not >> > installed. Do you know why? >> >> I don't know but it also happen to me. I have this problem on >> 7.2-RELEASE/amd64. > > Not to answer but just to say that on my i386, both files were installed. I've fixed that yesterday so this problem will be gone with the next port update. Both files only exist on i386 so this problem happens on all amd64 boxes. -- Bernhard Fr?hlich http://www.bluelife.at/ From bugmaster at FreeBSD.org Mon May 25 11:06:50 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon May 25 11:07:46 2009 Subject: Current problem reports assigned to freebsd-emulation@FreeBSD.org Message-ID: <200905251106.n4PB6nKa092750@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/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/91293 emulation [svr4] [patch] *Experimental* Update to the SVR4 emula 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 14 problems total. From chat95 at mac.com Mon May 25 12:18:51 2009 From: chat95 at mac.com (Maho NAKATA) Date: Mon May 25 12:19:05 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 3 In-Reply-To: References: <20090525.151740.98935220.chat95@mac.com> <991123400905242335w30c69fc6n9945f605dfff6cd6@mail.gmail.com> Message-ID: <20090525.211645.112547212.chat95@mac.com> From: Bernhard Frohlich Subject: Re: [Call For Testing] VirtualBox for FreeBSD! take 3 Date: Mon, 25 May 2009 09:33:19 +0200 (CEST) > On Mon, May 25, >> On Mon, May 25, 2009 at 9:17 AM, Maho NAKATA wrote: >> >>> Hi Miwi and nork-san >>> >>> From: Norikatsu Shigemura >>> Subject: Re: [Call For Testing] VirtualBox for FreeBSD! take 3 >>> Date: Mon, 25 May 2009 05:17:38 +0900 >>> >>> > BTW, In my environment, VBoxREM32.so and VBoxREM64.so was not >>> > installed. Do you know why? >>> >>> I don't know but it also happen to me. I have this problem on >>> 7.2-RELEASE/amd64. >> >> Not to answer but just to say that on my i386, both files were installed. > > I've fixed that yesterday so this problem will be gone with the next port > update. Both files only exist on i386 so this problem happens on all amd64 > boxes. Hi Bernhard Frhlich Thank you very much. I'm looking foward to see the next version :) Cheers, -- Nakata Maho http://accc.riken.jp/maho/ , http://ja.openoffice.org/ Nakata Maho's PGP public keys: http://accc.riken.jp/maho/maho.pgp.txt -------------- 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/20090525/6e85ceeb/attachment.pgp From vova at fbsd.ru Mon May 25 12:57:49 2009 From: vova at fbsd.ru (Vladimir Grebenschikov) Date: Mon May 25 12:58:08 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 3 In-Reply-To: <20090522175956.GA33004@bsdcrew.de> References: <20090522175956.GA33004@bsdcrew.de> Message-ID: <1243254080.96435.117.camel@localhost> Hi Works like a charm for me. Big thanks! (I've tried to install XP and Vista inside VM) Only thing I wander about - is ability to use raw devices as disks. Is there any option ? Probably in command line interface ? -----Original Message----- From: Martin Wilke To: ports@FreeBSD.org Cc: freebsd-emulation@freebsd.org, freebsd-current@freebsd.org Subject: Re: [Call For Testing] VirtualBox for FreeBSD! take 3 Date: Fri, 22 May 2009 19:59:57 +0200 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 We rolled a new version with a fix for all users where has problems with kernel load and unload. Many thanks to Shin-ichi Okano where submitted this patch to the vbox ml. http://people.freebsd.org/~miwi/vbox/virtualbox_4.tgz happy testing. - - Martin PS: Should this work for all maybe we can commit vbox this weekend to the portstree. - -- +-----------------------+-------------------------------+ | 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) iEYEARECAAYFAkoW6BwACgkQdLJIhLHm/Omb0wCfYh2BlN12YQMV2mtpRdXIy/cW WYIAniofRUneutcXfxXJz+DDZ2dwDJuG =6sXC -----END PGP SIGNATURE----- _______________________________________________ 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" -- Vladimir B. Grebenschikov vova@fbsd.ru From mh at kernel32.de Mon May 25 14:17:23 2009 From: mh at kernel32.de (Marian Hettwer) Date: Mon May 25 14:17:30 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 3 In-Reply-To: <1243254080.96435.117.camel@localhost> References: <1243254080.96435.117.camel@localhost> Message-ID: <73406dfded92bc7ce37ecee0c3eb0cd8@localhost> Hi All, > > > We rolled a new version with a fix for all users where > has problems with kernel load and unload. Many thanks to > Shin-ichi Okano where submitted this patch to the vbox ml. > > http://people.freebsd.org/~miwi/vbox/virtualbox_4.tgz > > happy testing. > This version works like a charm on my box. FreeBSD motor.mobile.local 7.2-STABLE FreeBSD 7.2-STABLE #0: Wed May 20 11:11:57 CEST 2009 root@motor.mobile.rz:/usr/obj/usr/src/sys/GENERIC i386 Thanks for all your efforts! Great to have a vmware replacement on FreeBSD :-) best regards and keep up the good work! Marian From mcdouga9 at egr.msu.edu Mon May 25 16:26:49 2009 From: mcdouga9 at egr.msu.edu (Adam McDougall) Date: Mon May 25 16:27:01 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! In-Reply-To: <4A0D7574.3050801@fletchermoorland.co.uk> References: <20090514191237.GD70242@bsdcrew.de> <20090515101253.GH71804@bsdcrew.de> <4A0D7574.3050801@fletchermoorland.co.uk> Message-ID: <4A1AC253.6010306@egr.msu.edu> Paul Wootton wrote: > Martin Wilke wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Ok >> >> We uploaded a new tarball what should be fix the build on AMD64. >> >> Small changelog: >> - - devel/kbuild is now dependency >> - - remove misc/compat6 support >> >> Note: >> Use devel/bcc instead of devel/dev86 what means >> If you have devel/bcc installed please deinstall >> >> http://people.freebsd.org/~miwi/vbox/virtualbox_1.tgz >> >> Please give us feedback :P >> >> >> - - Martin >> >> - -- >> +-----------------------+-------------------------------+ >> | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | >> | ICQ : 169139903 | Mail : miwi(at)FreeBSD.org | >> +-----------------------+-------------------------------+ >> | Mess with the Best, Die like the Rest! | >> +-----------------------+-------------------------------+ >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v2.0.11 (FreeBSD) >> >> iEYEARECAAYFAkoNQCUACgkQdLJIhLHm/OmgeQCgptEW5FhkmB8huDhs5LL63PhI >> +04AoONjytolxD892zcCnlv81MRLceEv >> =UJL8 >> -----END PGP SIGNATURE----- >> _______________________________________________ >> 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" >> >> >> > Hi, > When compiling I get the following error > > kBuild: Installing tstUtf8 => > /root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/bin/testcase/tstUtf8 > > kBuild: Installing tstUuid => > /root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/bin/testcase/tstUuid > > kBuild: Installing tstVMStructGC => > /root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/bin/tstVMStructGC > > kBuild: Generating tstVMStructSize - > /root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h > > /root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/bin/tstVMStructGC: > 1: Syntax error: "(" unexpected > kmk[2]: *** > [/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h] > Error 2 > kmk[2]: *** Deleting file > `/root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h' > > kmk[2]: *** Waiting for unfinished jobs.... > awk -f /usr/src/sys/conf/kmod_syms.awk > /root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/vboxdrv/vboxdrv.ko > /root/vBox/virtualbox/work/virtualbox-2.2.2r19673/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.def > | xargs -J% objcopy % > /root/vBox/virtualbox/work/virtualbox-2.2.2r19673/out/freebsd.amd64/release/obj/vboxdrv/vboxdrv.ko > > awk: can't open file > /root/vBox/virtualbox/work/virtualbox-2.2.2r19673/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.def > > source line number 10 > kmk[2]: Leaving directory > `/root/vBox/virtualbox/work/virtualbox-2.2.2r19673' > kmk[2]: Entering directory > `/root/vBox/virtualbox/work/virtualbox-2.2.2r19673' > kmk[2]: *** Exiting with status 2 > kmk[1]: *** [pass_binaries_this] Error 2 > kmk[1]: Leaving directory > `/root/vBox/virtualbox/work/virtualbox-2.2.2r19673' > kmk: *** [pass_binaries_order] Error 2 > *** Error code 2 > > Stop in /root/vBox/virtualbox. > demophon# > > > demophon# uname -a > FreeBSD demophon 8.0-CURRENT FreeBSD 8.0-CURRENT #10: Wed May 6 > 09:04:17 UTC 2009 paul@demophon:/usr/obj/usr/src/sys/DEMOPHON amd64 > > Any ideas? > > Cheers > Paul > _______________________________________________ > 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" > I am getting this error too from the latest test port on amd64 7-stable and 8-current: kBuild: Installing tstVMStructGC => /usr/home/mcdouga9/virtualbox/work/virtualbox-2.2.2r19852/out/freebsd.amd64/release/bin/tstVMStructGC kBuild: Generating tstVMStructSize - /usr/home/mcdouga9/virtualbox/work/virtualbox-2.2.2r19852/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h /usr/home/mcdouga9/virtualbox/work/virtualbox-2.2.2r19852/out/freebsd.amd64/release/bin/tstVMStructGC: 1: Syntax error: "(" unexpected kmk[2]: *** [/usr/home/mcdouga9/virtualbox/work/virtualbox-2.2.2r19852/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h] Error 2 kmk[2]: *** Deleting file `/usr/home/mcdouga9/virtualbox/work/virtualbox-2.2.2r19852/out/freebsd.amd64/release/obj/VMM/tstVMStructGC.h' kmk[2]: *** Waiting for unfinished jobs.... kmk[2]: Leaving directory `/usr/home/mcdouga9/virtualbox/work/virtualbox-2.2.2r19852' kmk[2]: Entering directory `/usr/home/mcdouga9/virtualbox/work/virtualbox-2.2.2r19852' kmk[2]: *** Exiting with status 2 kmk[1]: *** [pass_binaries_this] Error 2 kmk[1]: Leaving directory `/usr/home/mcdouga9/virtualbox/work/virtualbox-2.2.2r19852' kmk: *** [pass_binaries_order] Error 2 *** Error code 2 The OS builds are 1-3 days old (full kernel + world) and ports were up to date. Help? Thanks. From dougb at FreeBSD.org Mon May 25 16:30:21 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Mon May 25 16:30:29 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 3 In-Reply-To: <20090524181820.GD37143@bsdcrew.de> References: <20090522175956.GA33004@bsdcrew.de> <20090524170237.GA12352@carrot.geeknest.org> <20090524181820.GD37143@bsdcrew.de> Message-ID: <4A1AC104.7040107@FreeBSD.org> >> On Fri, May 22, 2009 at 07:59:57PM +0200, Martin Wilke wrote: >>> We rolled a new version with a fix for all users where >>> has problems with kernel load and unload. Many thanks to >>> Shin-ichi Okano where submitted this patch to the vbox ml. >>> >>> http://people.freebsd.org/~miwi/vbox/virtualbox_4.tgz Using this version and an up to date (r192705) -current I get an instantly wedged system when I load vboxdrv. The following message repeats over and over on the console if I try to kldload it there: panic: boot: not running on cpu0 cupid = 1 This is a C2D running i386. Doug -- This .signature sanitized for your protection From matheus at eternamente.info Mon May 25 20:04:09 2009 From: matheus at eternamente.info (Nenhum_de_Nos) Date: Mon May 25 20:04:15 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 3 In-Reply-To: <1243254080.96435.117.camel@localhost> References: <20090522175956.GA33004@bsdcrew.de> <1243254080.96435.117.camel@localhost> Message-ID: hail, people installing this right now, the -4 version of the port is the way to go ? any new things to add, new package ? thanks, matheus -- 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 vova at fbsd.ru Tue May 26 11:16:57 2009 From: vova at fbsd.ru (Vladimir Grebenschikov) Date: Tue May 26 11:17:04 2009 Subject: virtualbox wishlist [already :-)] In-Reply-To: <4A15882B.7030805@icyb.net.ua> References: <4A15882B.7030805@icyb.net.ua> Message-ID: <1243336611.2384.31.camel@localhost> On Thu, 2009-05-21 at 19:58 +0300, Andriy Gapon wrote: > I tried the experimental virtualbox port on stable/7 amd64 and I must say I am > impressed! Thank you very much! > > And already a small wishlist: > > 1. It seems that currently it is impossible to use raw devices with virtualbox - I > tried something that I googled up and it didn't work: > VBoxManage internalcommands createrawvmdk -filename test.vmdk -rawdisk > /dev/zvol/tank/test -register > [...] > Detected size of raw disk '/dev/zvol/tank/fbsd7_q64' is , an invalid value > The raw disk vmdk file was not created I've managed to get this work. Looks like problem is in fact that VBoxManage tries to get size of raw disk with just stat (it returns 0, of course). I've workaround it with creating small file with beginning of my HDD (10Mb). and create link ad0 -> /dev/ad0 in .VirtualBox/HardDisks Then call VBoxManage internalcommands createrawvmdk -filename /home/vova/.VirtualBox/HardDisks/Disk.vmdk -rawdisk ad0 -register ad0 is file in current directory. Then I've edit .vmdk file (change path to /dev/ad0, size of volume and disk geometry). If you use other disk partitions you need to allow simultaneous write access to both slice and whole disk (DANGEROUS!) with: sysctl kern.geom.debugflags=0x10 After that volume was added successfully and even mounted to XP after boot. At the end .vmdk file looks like: # Disk DescriptorFile version=1 CID=5ea344ed parentCID=ffffffff createType="fullDevice" # Extent description RW 390716865 FLAT "/dev/ad0" # The disk Data Base #DDB ddb.virtualHWVersion = "4" ddb.adapterType="ide" ddb.geometry.cylinders="387621" ddb.geometry.heads="16" ddb.geometry.sectors="63" ddb.uuid.image="0f139cb7-a6de-42b2-8c21-e28f23507d45" ddb.uuid.parent="00000000-0000-0000-0000-000000000000" ddb.uuid.modification="3b33feab-fb1d-4d62-ad74-dd73f18be5e0" ddb.uuid.parentmodification="00000000-0000-0000-0000-000000000000" ddb.geometry.biosCylinders="387621" ddb.geometry.biosHeads="16" ddb.geometry.biosSectors="63" Looks like such file may be created by hands of by simple script instead. But I've failed to make proper "partitioned" image (-partitions switch). > 2. it would be nice if VBoxGuestAdditions.iso was included (perhaps as a port option) > > 3. not sure if it is a feature of virtualbox in general or a porting artifact - my > (Intel) 64-bit CPU doesn't support VT-x and as a result can execute only 32-bit > guests. There doesn't seem to be any fallback strategy for 64-bit guests. BTW in > System/Acceleration tab "Enable VT-x/AMD-V" is shown as greyed out but checked - > this was confusing. > > 4. Minor annoyance - in VirtualBox GUI some text fields get partially "blacked > out" after mouse click in them. > -- Vladimir B. Grebenschikov vova@fbsd.ru From craig001 at lerwick.hopto.org Tue May 26 12:46:20 2009 From: craig001 at lerwick.hopto.org (Craig Butler) Date: Tue May 26 12:46:38 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 3 In-Reply-To: <73406dfded92bc7ce37ecee0c3eb0cd8@localhost> References: <1243254080.96435.117.camel@localhost> <73406dfded92bc7ce37ecee0c3eb0cd8@localhost> Message-ID: <1243340353.20783.35.camel@main.lerwick.hopto.org> On Mon, 2009-05-25 at 16:00 +0200, Marian Hettwer wrote: > Hi All, > > > > > > > We rolled a new version with a fix for all users where > > has problems with kernel load and unload. Many thanks to > > Shin-ichi Okano where submitted this patch to the vbox ml. > > > > http://people.freebsd.org/~miwi/vbox/virtualbox_4.tgz > > > > happy testing. > > > This version works like a charm on my box. > FreeBSD motor.mobile.local 7.2-STABLE FreeBSD 7.2-STABLE #0: Wed May 20 > 11:11:57 CEST 2009 root@motor.mobile.rz:/usr/obj/usr/src/sys/GENERIC > i386 > > Thanks for all your efforts! Great to have a vmware replacement on FreeBSD > :-) > > best regards and keep up the good work! > Marian Chalk up another one, also working on; 7.2-RELEASE FreeBSD 7.2-RELEASE #0 i386 tested opensuse 11.1, rhel 5, and fedora 10 -- all working. Thanks a million /Craig From avg at icyb.net.ua Tue May 26 15:22:17 2009 From: avg at icyb.net.ua (Andriy Gapon) Date: Tue May 26 15:22:24 2009 Subject: virtualbox wishlist [already :-)] In-Reply-To: <1243336611.2384.31.camel@localhost> References: <4A15882B.7030805@icyb.net.ua> <1243336611.2384.31.camel@localhost> Message-ID: <4A1C0924.5080101@icyb.net.ua> on 26/05/2009 14:16 Vladimir Grebenschikov said the following: > At the end .vmdk file looks like: > > # Disk DescriptorFile > version=1 > CID=5ea344ed > parentCID=ffffffff > createType="fullDevice" > > # Extent description > RW 390716865 FLAT "/dev/ad0" > > # The disk Data Base > #DDB > > ddb.virtualHWVersion = "4" > ddb.adapterType="ide" > ddb.geometry.cylinders="387621" > ddb.geometry.heads="16" > ddb.geometry.sectors="63" > ddb.uuid.image="0f139cb7-a6de-42b2-8c21-e28f23507d45" > ddb.uuid.parent="00000000-0000-0000-0000-000000000000" > ddb.uuid.modification="3b33feab-fb1d-4d62-ad74-dd73f18be5e0" > ddb.uuid.parentmodification="00000000-0000-0000-0000-000000000000" > ddb.geometry.biosCylinders="387621" > ddb.geometry.biosHeads="16" > ddb.geometry.biosSectors="63" > > Looks like such file may be created by hands of by simple script > instead. Thank you very much for the information! - It didn't even come to my mind that vmdk could be a plain-text file :-) -- Andriy Gapon From lapo at lapo.it Tue May 26 16:05:05 2009 From: lapo at lapo.it (Lapo Luchini) Date: Tue May 26 16:05:12 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 3 In-Reply-To: <20090522175956.GA33004@bsdcrew.de> References: <20090522175956.GA33004@bsdcrew.de> Message-ID: Martin Wilke wrote: > > We rolled a new version with a fix for all users where > has problems with kernel load and unload. Many thanks to > Shin-ichi Okano where submitted this patch to the vbox ml. > > http://people.freebsd.org/~miwi/vbox/virtualbox_4.tgz I compiled latest port available on svn.bluelife.at but still have the same problem I had with virtualbox_3.tgz: when running VirtualBox as a user (yes, I'm in the vboxusers group, and I mounted /proc and kldloaded the driver) it simply hangs in there, doing nothing at all: % ktrace VirtualBox ^C % kdump 637 ktrace RET ktrace 0 637 ktrace CALL execve(0x7fffffffca00,0x7fffffffcfe8,0x7fffffffcff8) 637 ktrace NAMI "/usr/local/libexec/ccache/VirtualBox" 637 ktrace RET execve -1 errno 2 No such file or directory 637 ktrace CALL execve(0x7fffffffca00,0x7fffffffcfe8,0x7fffffffcff8) 637 ktrace NAMI "/sbin/VirtualBox" 637 ktrace RET execve -1 errno 2 No such file or directory 637 ktrace CALL execve(0x7fffffffca00,0x7fffffffcfe8,0x7fffffffcff8) 637 ktrace NAMI "/bin/VirtualBox" 637 ktrace RET execve -1 errno 2 No such file or directory 637 ktrace CALL execve(0x7fffffffca00,0x7fffffffcfe8,0x7fffffffcff8) 637 ktrace NAMI "/usr/sbin/VirtualBox" 637 ktrace RET execve -1 errno 2 No such file or directory 637 ktrace CALL execve(0x7fffffffca00,0x7fffffffcfe8,0x7fffffffcff8) 637 ktrace NAMI "/usr/bin/VirtualBox" 637 ktrace RET execve -1 errno 2 No such file or directory 637 ktrace CALL execve(0x7fffffffca00,0x7fffffffcfe8,0x7fffffffcff8) 637 ktrace NAMI "/usr/games/VirtualBox" 637 ktrace RET execve -1 errno 2 No such file or directory 637 ktrace CALL execve(0x7fffffffca00,0x7fffffffcfe8,0x7fffffffcff8) 637 ktrace NAMI "/usr/local/sbin/VirtualBox" 637 ktrace RET execve -1 errno 2 No such file or directory 637 ktrace CALL execve(0x7fffffffca00,0x7fffffffcfe8,0x7fffffffcff8) 637 ktrace NAMI "/usr/local/bin/VirtualBox" 637 ktrace NAMI "/libexec/ld-elf.so.1" Running privileged using sudo (`sudo -E VirtualBox`) the console appears correctly and is functional (I can create an HDD, a VirtualMachine), but when trying to start a VM, it instantly goes in "Aborted" state. -- Lapo Luchini - http://lapo.it/ From avg at icyb.net.ua Wed May 27 13:00:11 2009 From: avg at icyb.net.ua (Andriy Gapon) Date: Wed May 27 13:00:26 2009 Subject: rc.d/kqemu still loads aio.ko? Message-ID: <4A1D3958.7090600@icyb.net.ua> I thought that newer qemu doesn't depend on aio any longer because it has some internal glue instead. But it seems that kqemu-kmod-devel port still installs rc.d script that automatically loads aio on start. -- Andriy Gapon From miwi at FreeBSD.org Wed May 27 13:43:48 2009 From: miwi at FreeBSD.org (Martin Wilke) Date: Wed May 27 13:43:54 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 4 Message-ID: <20090527134343.GB1104@bsdcrew.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Howdy, First of all sorry for all unanswered mails, I got a stupid flu, but now i feel better... ok now back to vbox, time for a new call for testing :-) Following was added/fixed: - - ACPI Support was added - - hostDVD support was added - - Fix startup on HEAD - - Plist problem under AMD64 was fixed - - Qt4 Frontend is now Optional - - Desktop file was added - - Xorg dependencies was fixed - - Guest additions was added (thx to Maho NAKATA ) Open task: We have got 2 patches for nls support and the request to make dbus and pulseaudio optional. These both will be added with the next run. We'd like to say many many thanks for all your feedback. http://people.freebsd.org/~miwi/vbox/virtualbox_5.tgz Happy Testing :-) - -- +-----------------------+-------------------------------+ | 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) iEYEARECAAYFAkodQ48ACgkQdLJIhLHm/OmjfQCfR6Zczz0XcZZpAYie64D2G0Ti wwQAn2r0W/12iidjOfgvX05QPNQX1oUc =b8tt -----END PGP SIGNATURE----- From vova at fbsd.ru Wed May 27 14:50:26 2009 From: vova at fbsd.ru (Vladimir Grebenschikov) Date: Wed May 27 14:50:39 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 4 In-Reply-To: <20090527134343.GB1104@bsdcrew.de> References: <20090527134343.GB1104@bsdcrew.de> Message-ID: <1243435820.47997.103.camel@localhost> Hi Martin Many thanks again ! One more question, what about USB support ? Is it possible to pass host usb devices inside VM ? I have such option in machine menu but it is always empty. $ usbconfig ugen0.1: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen1.1: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen2.1: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen3.1: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen4.1: at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen4.2: at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen4.3: at usbus4, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.2: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen3.3: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON $ As minimum ugen3.3 have no driver attached. Also I have RW permissions to access /dev/usb* devices. -----Original Message----- From: Martin Wilke To: ports@FreeBSD.org Cc: freebsd-emulation@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: [Call For Testing] VirtualBox for FreeBSD! take 4 Date: Wed, 27 May 2009 15:43:43 +0200 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Howdy, First of all sorry for all unanswered mails, I got a stupid flu, but now i feel better... ok now back to vbox, time for a new call for testing :-) Following was added/fixed: - - ACPI Support was added - - hostDVD support was added - - Fix startup on HEAD - - Plist problem under AMD64 was fixed - - Qt4 Frontend is now Optional - - Desktop file was added - - Xorg dependencies was fixed - - Guest additions was added (thx to Maho NAKATA ) Open task: We have got 2 patches for nls support and the request to make dbus and pulseaudio optional. These both will be added with the next run. We'd like to say many many thanks for all your feedback. http://people.freebsd.org/~miwi/vbox/virtualbox_5.tgz Happy Testing :-) - -- +-----------------------+-------------------------------+ | 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) iEYEARECAAYFAkodQ48ACgkQdLJIhLHm/OmjfQCfR6Zczz0XcZZpAYie64D2G0Ti wwQAn2r0W/12iidjOfgvX05QPNQX1oUc =b8tt -----END PGP SIGNATURE----- _______________________________________________ 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" -- Vladimir B. Grebenschikov vova@fbsd.ru From rink at FreeBSD.org Wed May 27 14:54:07 2009 From: rink at FreeBSD.org (Rink Springer) Date: Wed May 27 14:54:21 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 4 In-Reply-To: <1243435820.47997.103.camel@localhost> References: <20090527134343.GB1104@bsdcrew.de> <1243435820.47997.103.camel@localhost> Message-ID: <20090527145408.GB68852@rink.nu> On Wed, May 27, 2009 at 06:50:20PM +0400, Vladimir Grebenschikov wrote: > One more question, what about USB support ? > Is it possible to pass host usb devices inside VM ? I think this is only possible with the non-open-source version of VirtualBox. Regards, -- Rink P.W. Springer - http://rink.nu "Doom, gloom and despair. I like it!" - Tiresias From miwi at FreeBSD.org Wed May 27 15:03:55 2009 From: miwi at FreeBSD.org (Martin Wilke) Date: Wed May 27 15:04:01 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 4 In-Reply-To: <1243435820.47997.103.camel@localhost> References: <20090527134343.GB1104@bsdcrew.de> <1243435820.47997.103.camel@localhost> Message-ID: <20090527150350.GC1104@bsdcrew.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, May 27, 2009 at 06:50:20PM +0400, Vladimir Grebenschikov wrote: > Hi Martin > > Many thanks again ! > > One more question, what about USB support ? > Is it possible to pass host usb devices inside VM ? > I have such option in machine menu but it is always empty. > > $ usbconfig > ugen0.1: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON > ugen1.1: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON > ugen2.1: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON > ugen3.1: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON > ugen4.1: at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON > ugen4.2: at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE > ugen4.3: at usbus4, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON > ugen3.2: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON > ugen3.3: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON > $ > > As minimum ugen3.3 have no driver attached. > > Also I have RW permissions to access /dev/usb* devices. USB Support isn't ported yet maybe later :-). - - Martin > > -----Original Message----- > From: Martin Wilke > To: ports@FreeBSD.org > Cc: freebsd-emulation@FreeBSD.org, freebsd-current@FreeBSD.org > Subject: Re: [Call For Testing] VirtualBox for FreeBSD! take 4 > Date: Wed, 27 May 2009 15:43:43 +0200 > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Howdy, > > First of all sorry for all unanswered mails, I got a stupid flu, > but now i feel better... ok now back to vbox, time for a new call > for testing :-) > > Following was added/fixed: > > - - ACPI Support was added > - - hostDVD support was added > - - Fix startup on HEAD > - - Plist problem under AMD64 was fixed > - - Qt4 Frontend is now Optional > - - Desktop file was added > - - Xorg dependencies was fixed > - - Guest additions was added (thx to Maho NAKATA ) > > Open task: > We have got 2 patches for nls support and the request > to make dbus and pulseaudio optional. These both will > be added with the next run. > > We'd like to say many many thanks for all your feedback. > > http://people.freebsd.org/~miwi/vbox/virtualbox_5.tgz > > Happy Testing :-) > > > > - -- > > +-----------------------+-------------------------------+ > | 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) > > iEYEARECAAYFAkodQ48ACgkQdLJIhLHm/OmjfQCfR6Zczz0XcZZpAYie64D2G0Ti > wwQAn2r0W/12iidjOfgvX05QPNQX1oUc > =b8tt > -----END PGP SIGNATURE----- > _______________________________________________ > 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" > -- > Vladimir B. Grebenschikov > vova@fbsd.ru > - -- +-----------------------+-------------------------------+ | 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) iEYEARECAAYFAkodVR8ACgkQdLJIhLHm/OnWgwCeLF3N/nGErpYkdMEMPDMbGIAy gOcAoJS0VxKO7FXCMbIlvbZvWy3Rt97s =iyhU -----END PGP SIGNATURE----- From dudu at dudu.ro Wed May 27 15:07:04 2009 From: dudu at dudu.ro (Vlad GALU) Date: Wed May 27 15:07:17 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 4 In-Reply-To: <20090527134343.GB1104@bsdcrew.de> References: <20090527134343.GB1104@bsdcrew.de> Message-ID: On Wed, May 27, 2009 at 4:43 PM, Martin Wilke wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Howdy, > > First of all sorry for all unanswered mails, I got a stupid flu, > but now i feel better... ok now back to vbox, time for a new call > for testing :-) > > Following was added/fixed: > > - - ACPI Support was added > - - hostDVD support was added > - - Fix startup on HEAD > - - Plist problem under AMD64 was fixed > - - Qt4 Frontend is now Optional > - - Desktop file was added > - - Xorg dependencies was fixed > - - Guest additions was added (thx to Maho NAKATA ) > > Open task: > ?We have got 2 patches for nls support and the request > ?to make dbus and pulseaudio optional. These both will > ?be added with the next run. > > ?We'd like to say many many thanks for all your feedback. > > http://people.freebsd.org/~miwi/vbox/virtualbox_5.tgz > > Happy Testing :-) Hi Martin, I'm running RELENG_7, I've just given it a spin, I was able to install another FreeBSD instance in the virtual machine. Working great! Any idea when this will hit the ports tree? As a side note, loading vboxdrv.ko while X was running crashed my machine, in RTMpGetOnlineCount (). Unfortunately, all frames between that and frame 0 were corrupt. After rebooting, I was able to log on ttyv0 and loaded it without any issues. From paul at fletchermoorland.co.uk Wed May 27 15:08:22 2009 From: paul at fletchermoorland.co.uk (Paul Wootton) Date: Wed May 27 15:08:41 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 4 In-Reply-To: <20090527134343.GB1104@bsdcrew.de> References: <20090527134343.GB1104@bsdcrew.de> Message-ID: <4A1D575F.7040908@fletchermoorland.co.uk> Martin Wilke wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Howdy, > > First of all sorry for all unanswered mails, I got a stupid flu, > but now i feel better... ok now back to vbox, time for a new call > for testing :-) > > Following was added/fixed: > > - - ACPI Support was added > - - hostDVD support was added > - - Fix startup on HEAD > - - Plist problem under AMD64 was fixed > - - Qt4 Frontend is now Optional > - - Desktop file was added > - - Xorg dependencies was fixed > - - Guest additions was added (thx to Maho NAKATA ) > > Open task: > We have got 2 patches for nls support and the request > to make dbus and pulseaudio optional. These both will > be added with the next run. > > We'd like to say many many thanks for all your feedback. > > http://people.freebsd.org/~miwi/vbox/virtualbox_5.tgz > > Happy Testing :-) > > > > - -- > > +-----------------------+-------------------------------+ > | 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) > > iEYEARECAAYFAkodQ48ACgkQdLJIhLHm/OmjfQCfR6Zczz0XcZZpAYie64D2G0Ti > wwQAn2r0W/12iidjOfgvX05QPNQX1oUc > =b8tt > -----END PGP SIGNATURE----- > _______________________________________________ > 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" > > > ----------------------------------------------------------------------------------- > Fletcher Moorland Limited is a company registered in England and Wales. > Registration number: 2984467. > Registered office: Elenora Street, Stoke on Trent, Staffordshire, ST4 1QG. > VAT Registration number: 478730606 > Telephone: 01782 411021 | Fax: 01782 744470 | http://www.fletchermoorland.co.uk > Hi, With both VirtualBox 4 and 5, when I try to run VirtualBox I get an error saying "Callee RC: NS_ERROR_ABORT (0x80004004)" If I run VBoxSVC is a console session and then try VirtualBox I get "********************************************** Sun VirtualBox XPCOM Server Version 2.2.51_OSE (C) 2008-2009 Sun Microsystems, Inc. All rights reserved. Starting event loop.... [press Ctrl-C to quit] terminate called after throwing an instance of 'settings::ENoValue' what(): Segmentation fault: 11 (core dumped)" Also, when I try to compile VirtualBox 5 with debug information, the make fails with "kBuild: Linking tstDir In file included from /root/vBox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c:47: /root/vBox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/../SUPDrvInternal.h:125:1: warning: "ffs" redefined In file included from /usr/src/sys/sys/systm.h:42, from /root/vBox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c:40: /usr/include/machine/cpufunc.h:133:1: warning: this is the location of the previous definition kBuild: Linking tstDir-2 kBuild: Linking tstDir-3 /root/vBox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c: In function 'VBoxDrvFreeBSDOpen': /root/vBox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c:299: error: invalid operands to binary & /root/vBox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c: In function 'VBoxDrvFreeBSDClose': /root/vBox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c:355: error: invalid operands to binary & kmk[2]: *** [/root/vBox/virtualbox/work/virtualbox-2.2.2r19980/out/freebsd.amd64/debug/obj/vboxdrv/freebsd/SUPDrv-freebsd.o] Error 1 The failing command: @gcc -c -g -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 -O0 -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/root/vBox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support -I/usr/src/sys -I/usr/src/sys/contrib/altq -I/usr/src/sys/../include -I/usr/include -I/root/vBox/virtualbox/work/virtualbox-2.2.2r19980/include -I/root/vBox/virtualbox/work/virtualbox-2.2.2r19980/out/freebsd.amd64/debug -DVBOX -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_HARDENING -DRTPATH_APP_PRIVATE=\"/usr/local/lib/virtualbox\" -DRTPATH_APP_PRIVATE_ARCH=\"/usr/local/lib/virtualbox\" -DRTPATH_SHARED_LIBS=\"/usr/local/lib/virtualbox\" -DRTPATH_APP_DOCS=\"/usr/local/share/doc/virtualbox\" -DDEBUG -DDEBUG_paul -DDEBUG_USERNAME=paul -DRT_OS_FREEBSD -D__FREEBSD__ -DRT_ARCH_AMD64 -D__AMD64__ -D_KERNEL -DKLD_MODULE -DIN_RING0 -DIN_RT_R0 -DIN_RT_R0 -DIN_SUP_R0 -DSUPDRV_WITH_RELEASE_LOGGER -DVBOX_SVN_REV=19957 -Wp,-MD,/root/vBox/virtualbox/work/virtualbox-2.2.2r19980/out/freebsd.amd64/debug/obj/vboxdrv/freebsd/SUPDrv-freebsd.o.dep -Wp,-MT,/root/vBox/virtualbox/work/virtualbox-2.2.2r19980/out/freebsd.amd64/debug/obj/vboxdrv/freebsd/SUPDrv-freebsd.o -Wp,-MP -o /root/vBox/virtualbox/work/virtualbox-2.2.2r19980/out/freebsd.amd64/debug/obj/vboxdrv/freebsd/SUPDrv-freebsd.o /root/vBox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c kmk[2]: *** Waiting for unfinished jobs.... kmk[2]: Leaving directory `/root/vBox/virtualbox/work/virtualbox-2.2.2r19980' kmk[2]: Entering directory `/root/vBox/virtualbox/work/virtualbox-2.2.2r19980' kmk[2]: *** Exiting with status 2 kmk[1]: *** [pass_binaries_this] Error 2 kmk[1]: Leaving directory `/root/vBox/virtualbox/work/virtualbox-2.2.2r19980' kmk: *** [pass_binaries_order] Error 2 *** Error code 2 Stop in /root/vBox/virtualbox." Any Ideas? Cheers Paul ----------------------------------------------------------------------------------- Fletcher Moorland Limited is a company registered in England and Wales. Registration number: 2984467. Registered office: Elenora Street, Stoke on Trent, Staffordshire, ST4 1QG. VAT Registration number: 478730606 Telephone: 01782 411021 | Fax: 01782 744470 | http://www.fletchermoorland.co.uk From paul at fletchermoorland.co.uk Wed May 27 15:20:05 2009 From: paul at fletchermoorland.co.uk (Paul Wootton) Date: Wed May 27 15:20:14 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 4 In-Reply-To: <4A1D575F.7040908@fletchermoorland.co.uk> References: <20090527134343.GB1104@bsdcrew.de> <4A1D575F.7040908@fletchermoorland.co.uk> Message-ID: <4A1D5A18.1090901@fletchermoorland.co.uk> Paul Wootton wrote: > Martin Wilke wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > > > Howdy, > > > > First of all sorry for all unanswered mails, I got a stupid flu, > > but now i feel better... ok now back to vbox, time for a new call > > for testing :-) > > > > Following was added/fixed: > > > > - - ACPI Support was added > > - - hostDVD support was added > > - - Fix startup on HEAD > > - - Plist problem under AMD64 was fixed > > - - Qt4 Frontend is now Optional > > - - Desktop file was added > > - - Xorg dependencies was fixed > > - - Guest additions was added (thx to Maho NAKATA dot com>) > > > > Open task: > > We have got 2 patches for nls support and the request > > to make dbus and pulseaudio optional. These both will > > be added with the next run. > > > > We'd like to say many many thanks for all your feedback. > > > > http://people.freebsd.org/~miwi/vbox/virtualbox_5.tgz > > > > Happy Testing :-) > > > > > > > > - -- > > > > +-----------------------+-------------------------------+ > > | 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) > > > > iEYEARECAAYFAkodQ48ACgkQdLJIhLHm/OmjfQCfR6Zczz0XcZZpAYie64D2G0Ti > > wwQAn2r0W/12iidjOfgvX05QPNQX1oUc > > =b8tt > > -----END PGP SIGNATURE----- > > _______________________________________________ > > 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" > > > > > > > ----------------------------------------------------------------------------------- > > > Fletcher Moorland Limited is a company registered in England and Wales. > > Registration number: 2984467. > > Registered office: Elenora Street, Stoke on Trent, Staffordshire, > ST4 1QG. > > VAT Registration number: 478730606 > > Telephone: 01782 411021 | Fax: 01782 744470 | > http://www.fletchermoorland.co.uk > > > > Hi, > > With both VirtualBox 4 and 5, when I try to run VirtualBox I get an > error saying > "Callee RC: NS_ERROR_ABORT (0x80004004)" > > If I run VBoxSVC is a console session and then try VirtualBox I get > "********************************************** > Sun VirtualBox XPCOM Server Version 2.2.51_OSE > (C) 2008-2009 Sun Microsystems, Inc. > All rights reserved. > > Starting event loop.... > [press Ctrl-C to quit] > terminate called after throwing an instance of 'settings::ENoValue' > what(): Segmentation fault: 11 (core dumped)" > > Also, when I try to compile VirtualBox 5 with debug information, the > make fails with > > "kBuild: Linking tstDir > In file included from > /root/vBox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c:47: > > /root/vBox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/../SUPDrvInternal.h:125:1: > warning: "ffs" redefined > In file included from /usr/src/sys/sys/systm.h:42, > from > /root/vBox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c:40: > > /usr/include/machine/cpufunc.h:133:1: warning: this is the location of > the previous definition > kBuild: Linking tstDir-2 > kBuild: Linking tstDir-3 > /root/vBox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c: > In function 'VBoxDrvFreeBSDOpen': > /root/vBox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c:299: > error: invalid operands to binary & > /root/vBox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c: > In function 'VBoxDrvFreeBSDClose': > /root/vBox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c:355: > error: invalid operands to binary & > kmk[2]: *** > [/root/vBox/virtualbox/work/virtualbox-2.2.2r19980/out/freebsd.amd64/debug/obj/vboxdrv/freebsd/SUPDrv-freebsd.o] > Error 1 > The failing command: > @gcc -c -g -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 -O0 -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/root/vBox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support > -I/usr/src/sys -I/usr/src/sys/contrib/altq -I/usr/src/sys/../include > -I/usr/include > -I/root/vBox/virtualbox/work/virtualbox-2.2.2r19980/include > -I/root/vBox/virtualbox/work/virtualbox-2.2.2r19980/out/freebsd.amd64/debug > -DVBOX -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_HARDENING > -DRTPATH_APP_PRIVATE=\"/usr/local/lib/virtualbox\" > -DRTPATH_APP_PRIVATE_ARCH=\"/usr/local/lib/virtualbox\" > -DRTPATH_SHARED_LIBS=\"/usr/local/lib/virtualbox\" > -DRTPATH_APP_DOCS=\"/usr/local/share/doc/virtualbox\" -DDEBUG > -DDEBUG_paul -DDEBUG_USERNAME=paul -DRT_OS_FREEBSD -D__FREEBSD__ > -DRT_ARCH_AMD64 -D__AMD64__ -D_KERNEL -DKLD_MODULE -DIN_RING0 > -DIN_RT_R0 -DIN_RT_R0 -DIN_SUP_R0 -DSUPDRV_WITH_RELEASE_LOGGER > -DVBOX_SVN_REV=19957 > -Wp,-MD,/root/vBox/virtualbox/work/virtualbox-2.2.2r19980/out/freebsd.amd64/debug/obj/vboxdrv/freebsd/SUPDrv-freebsd.o.dep > -Wp,-MT,/root/vBox/virtualbox/work/virtualbox-2.2.2r19980/out/freebsd.amd64/debug/obj/vboxdrv/freebsd/SUPDrv-freebsd.o > -Wp,-MP -o > /root/vBox/virtualbox/work/virtualbox-2.2.2r19980/out/freebsd.amd64/debug/obj/vboxdrv/freebsd/SUPDrv-freebsd.o > /root/vBox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c > > kmk[2]: *** Waiting for unfinished jobs.... > kmk[2]: Leaving directory > `/root/vBox/virtualbox/work/virtualbox-2.2.2r19980' > kmk[2]: Entering directory > `/root/vBox/virtualbox/work/virtualbox-2.2.2r19980' > kmk[2]: *** Exiting with status 2 > kmk[1]: *** [pass_binaries_this] Error 2 > kmk[1]: Leaving directory > `/root/vBox/virtualbox/work/virtualbox-2.2.2r19980' > kmk: *** [pass_binaries_order] Error 2 > *** Error code 2 > > Stop in /root/vBox/virtualbox." > > Any Ideas? > > Cheers > Paul > Forgot to add FreeBSD demophon 8.0-CURRENT FreeBSD 8.0-CURRENT #17: Wed May 27 13:18:06 BST 2009 paul@demophon:/usr/obj/usr/src/sys/DEMOPHON amd64 ----------------------------------------------------------------------------------- Fletcher Moorland Limited is a company registered in England and Wales. Registration number: 2984467. Registered office: Elenora Street, Stoke on Trent, Staffordshire, ST4 1QG. VAT Registration number: 478730606 Telephone: 01782 411021 | Fax: 01782 744470 | http://www.fletchermoorland.co.uk From army.of.root at googlemail.com Wed May 27 15:34:17 2009 From: army.of.root at googlemail.com (army.of.root) Date: Wed May 27 15:34:22 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 4 In-Reply-To: <20090527145408.GB68852@rink.nu> References: <20090527134343.GB1104@bsdcrew.de> <1243435820.47997.103.camel@localhost> <20090527145408.GB68852@rink.nu> Message-ID: <4A1D56EB.7090300@googlemail.com> Rink Springer wrote: > On Wed, May 27, 2009 at 06:50:20PM +0400, Vladimir Grebenschikov wrote: >> One more question, what about USB support ? >> Is it possible to pass host usb devices inside VM ? > > I think this is only possible with the non-open-source version of > VirtualBox. > > Regards, > Maybe Sun/Innotek has some spare time and makes an official Release. I See it coming :) - A Windows VM just for Webcam stuff... Maybe the new USB-Stack and libusb makes Support on the VBox side really easy. best regards From dougb at FreeBSD.org Wed May 27 16:27:28 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Wed May 27 16:27:34 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 4 In-Reply-To: References: <20090527134343.GB1104@bsdcrew.de> Message-ID: <4A1D6874.9020104@FreeBSD.org> Vlad GALU wrote: > As a side note, loading vboxdrv.ko while X was running crashed my > machine, in RTMpGetOnlineCount (). Unfortunately, all frames between > that and frame 0 were corrupt. After rebooting, I was able to log on > ttyv0 and loaded it without any issues. Regarding my previous message about loading vboxdrv causing my machine to wedge, it happens to me both in X and on the console. Haven't tried with v5 of the port yet though. Doug From olivier at gid0.org Wed May 27 16:34:55 2009 From: olivier at gid0.org (Olivier SMEDTS) Date: Wed May 27 16:35:07 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 4 In-Reply-To: <20090527134343.GB1104@bsdcrew.de> References: <20090527134343.GB1104@bsdcrew.de> Message-ID: <367b2c980905270934v5132011axc4e0bb1fcaa09bf7@mail.gmail.com> 2009/5/27 Martin Wilke : > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Howdy, > > First of all sorry for all unanswered mails, I got a stupid flu, > but now i feel better... ok now back to vbox, time for a new call > for testing :-) I can't make install WITH_GUESTADDITIONS=yes if I don't download the iso manually into /usr/ports/distfiles/ : # make install [...] install -o root -g wheel -m 444 /usr/ports/distfiles/VBoxGuestAdditions_2.2.2.iso /usr/local/lib/virtualbox/ install: /usr/ports/distfiles/VBoxGuestAdditions_2.2.2.iso: No such file or directory *** Error code 71 Also, are there any plans on VT and x86_64 guests support (blocking feature for me) ? Thanks for the great port ! > Following was added/fixed: > > - - ACPI Support was added > - - hostDVD support was added > - - Fix startup on HEAD > - - Plist problem under AMD64 was fixed > - - Qt4 Frontend is now Optional > - - Desktop file was added > - - Xorg dependencies was fixed > - - Guest additions was added (thx to Maho NAKATA ) > > Open task: > ?We have got 2 patches for nls support and the request > ?to make dbus and pulseaudio optional. These both will > ?be added with the next run. > > ?We'd like to say many many thanks for all your feedback. > > http://people.freebsd.org/~miwi/vbox/virtualbox_5.tgz > > Happy Testing :-) > > > > - -- > > +-----------------------+-------------------------------+ > | ?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) > > iEYEARECAAYFAkodQ48ACgkQdLJIhLHm/OmjfQCfR6Zczz0XcZZpAYie64D2G0Ti > wwQAn2r0W/12iidjOfgvX05QPNQX1oUc > =b8tt > -----END PGP SIGNATURE----- > _______________________________________________ > 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" > -- 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 dougb at FreeBSD.org Wed May 27 19:27:49 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Wed May 27 19:29:23 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 4 In-Reply-To: <20090527134343.GB1104@bsdcrew.de> References: <20090527134343.GB1104@bsdcrew.de> Message-ID: <4A1D9429.9070207@FreeBSD.org> Martin Wilke wrote: > http://people.freebsd.org/~miwi/vbox/virtualbox_5.tgz On a newly up to date -current (r192914) with world and kernel in synch and ports up to date I get the same panic when trying to kldload vboxdrv. This is on a C2D running i386 SMP. panic: boot: not running on cpu0 cupid = 1 Also, I got the following when trying to build with debug. Building without debug worked. hth, Doug kBuild: Compiling vboxdrv - /usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c kBuild: Compiling vboxdrv - /usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/SUPDrv.c /usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c: In function 'VBoxDrvFreeBSDOpen': /usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c:299: error: invalid operands to binary & /usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c: In function 'VBoxDrvFreeBSDClose': /usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c:355: error: invalid operands to binary & /usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/SUPDrv.c: In function 'supdrvIOCtl': /usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/SUPDrv.c:1429: warning: format '%#lx' expects type 'long unsigned int', but argument 3 has type 'unsigned int' /usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/SUPDrv.c:1610: warning: format '%#lx' expects type 'long unsigned int', but argument 3 has type 'unsigned int' kmk[2]: *** [/usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980/out/freebsd.x86/debug/obj/vboxdrv/freebsd/SUPDrv-freebsd.o] Error 1 The failing command: @gcc -c -g -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 -march=i586 -O0 -fno-omit-frame-pointer -nostdinc -std=c99 -m32 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -I/usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support -I/usr/src/sys -I/usr/src/sys/contrib/altq -I/usr/src/sys/../include -I/usr/include -I/usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980/include -I/usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980/out/freebsd.x86/debug -DVBOX -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_HARDENING -DRTPATH_APP_PRIVATE=\"/usr/local/lib/virtualbox\" -DRTPATH_APP_PRIVATE_ARCH=\"/usr/local/lib/virtualbox\" -DRTPATH_SHARED_LIBS=\"/usr/local/lib/virtualbox\" -DRTPATH_APP_DOCS=\"/usr/local/share/doc/virtualbox\" -DDEBUG -DDEBUG_dougb -DDEBUG_USERNAME=dougb -DRT_OS_FREEBSD -D__FREEBSD__ -DRT_ARCH_X86 -D__X86__ -D_KERNEL -DKLD_MODULE -DIN_RING0 -DIN_RT_R0 -DIN_RT_R0 -DIN_SUP_R0 -DSUPDRV_WITH_RELEASE_LOGGER -DVBOX_SVN_REV=19957 -Wp,-MD,/usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980/out/freebsd.x86/debug/obj/vboxdrv/freebsd/SUPDrv-freebsd.o.dep -Wp,-MT,/usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980/out/freebsd.x86/debug/obj/vboxdrv/freebsd/SUPDrv-freebsd.o -Wp,-MP -o /usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980/out/freebsd.x86/debug/obj/vboxdrv/freebsd/SUPDrv-freebsd.o /usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c kmk[2]: *** Waiting for unfinished jobs.... kmk[2]: Leaving directory `/usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980' kmk[2]: Entering directory `/usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980' kmk[2]: *** Exiting with status 2 kmk[1]: *** [pass_binaries_this] Error 2 kmk[1]: Leaving directory `/usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980' kmk: *** [pass_binaries_order] Error 2 *** Error code 2 Stop in /usr/local/home/dougb/virtualbox. *** Error code 1 Stop in /usr/local/home/dougb/virtualbox. -- This .signature sanitized for your protection From fbsdlist at src.cx Wed May 27 20:15:32 2009 From: fbsdlist at src.cx (Artem Belevich) Date: Wed May 27 20:15:50 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 4 In-Reply-To: <20090527134343.GB1104@bsdcrew.de> References: <20090527134343.GB1104@bsdcrew.de> Message-ID: -CURRENT/amd64 as of yesterday. First, there's a build issue: /gm0/zm0/home/artem/vbox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c: In function 'VBoxDrvFreeBSDOpen': /gm0/zm0/home/artem/vbox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c:299: error: invalid operands to binary & /gm0/zm0/home/artem/vbox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c: In function 'VBoxDrvFreeBSDClose': /gm0/zm0/home/artem/vbox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c:355: error: invalid operands to binary & kBuild: Linking tstCollector kmk[2]: *** [/gm0/zm0/home/artem/vbox/virtualbox/work/virtualbox-2.2.2r19980/out/freebsd.amd64/debug/obj/vboxdrv/freebsd/SUPDrv-freebsd.o] Error 1 Looks like a problem with minor() macro use. Patched it up to print raw pointer instead and move on with compilation. During installation I had to manually fetch http://download.virtualbox.org/virtualbox/2.2.2/VBoxGuestAdditions_2.2.2.iso into /usr/ports/distfiles -- this has already been reported, I believe. The bad news is that kernel crashed on load of vboxdrv: VBoxDrvFreeBSDLoad: 7/1: off=ae6 6/1: off=20870d6 5/1: off=20a420f 4/1: off=20ab06a 3/1: off=20acf63 2/1: off=20a5eec 1/1: off=20a9bc7 0/1: off=20a6cbd supdrvDetermineAsyncTsc: returns 0; iLastCpu=3 rc=-801 offMin=ae6 offMax=20acf63 vboxdrv: fAsync=0 offMin=0xae6 offMax=0x20acf63 supdrvGipCreate: 10000000 ns interval. VBoxDrvFreeBSDLoad: returns successfully !!Assertion Failed!! Expression: cMillies != RT_INDEFINITE_WAIT Location : /gm0/zm0/home/artem/vbox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/Runtime/r0drv/freebsd/semevent-r0drv-freebsd.c(212) rtSemEventWait [thread pid 58317 tid 100567 ] Stopped at rtSemEventWait+0x39a: nop db> where Tracing pid 58317 tid 100567 td 0xffffff00909f8390 rtSemEventWait() at rtSemEventWait+0x39a RTSemEventWait() at RTSemEventWait+0x20 _Z13rtTimerThreadP11RTTHREADINTPv() at _Z13rtTimerThreadP11RTTHREADINTPv+0x44 rtThreadMain() at rtThreadMain+0x121 rtThreadNativeMain() at rtThreadNativeMain+0x35 fork_exit() at fork_exit+0x118 fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffff842fcb5d40, rbp = 0 --- db> --Artem On Wed, May 27, 2009 at 6:43 AM, Martin Wilke wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Howdy, > > First of all sorry for all unanswered mails, I got a stupid flu, > but now i feel better... ok now back to vbox, time for a new call > for testing :-) > > Following was added/fixed: > > - - ACPI Support was added > - - hostDVD support was added > - - Fix startup on HEAD > - - Plist problem under AMD64 was fixed > - - Qt4 Frontend is now Optional > - - Desktop file was added > - - Xorg dependencies was fixed > - - Guest additions was added (thx to Maho NAKATA ) > > Open task: > ?We have got 2 patches for nls support and the request > ?to make dbus and pulseaudio optional. These both will > ?be added with the next run. > > ?We'd like to say many many thanks for all your feedback. > > http://people.freebsd.org/~miwi/vbox/virtualbox_5.tgz > > Happy Testing :-) > > > > - -- > > +-----------------------+-------------------------------+ > | ?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) > > iEYEARECAAYFAkodQ48ACgkQdLJIhLHm/OmjfQCfR6Zczz0XcZZpAYie64D2G0Ti > wwQAn2r0W/12iidjOfgvX05QPNQX1oUc > =b8tt > -----END PGP SIGNATURE----- > _______________________________________________ > 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 nox at jelal.kn-bremen.de Wed May 27 20:46:44 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Wed May 27 20:46:51 2009 Subject: rc.d/kqemu still loads aio.ko? In-Reply-To: <4A1D3958.7090600@icyb.net.ua> Message-ID: <200905272043.n4RKhpUv069407@triton.kn-bremen.de> In article <4A1D3958.7090600@icyb.net.ua> you write: >I thought that newer qemu doesn't depend on aio any longer because it has some >internal glue instead. But it seems that kqemu-kmod-devel port still installs rc.d >script that automatically loads aio on start. This is only because the qemu-devel port is still at an older snapshot that still requires aio.ko... Cheers, Juergen From chat95 at mac.com Thu May 28 03:10:56 2009 From: chat95 at mac.com (Maho NAKATA) Date: Thu May 28 03:11:12 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 4 In-Reply-To: <20090527134343.GB1104@bsdcrew.de> References: <20090527134343.GB1104@bsdcrew.de> Message-ID: <20090528.120848.42799534.chat95@mac.com> From: Martin Wilke Subject: Re: [Call For Testing] VirtualBox for FreeBSD! take 4 Date: Wed, 27 May 2009 15:43:43 +0200 > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Howdy, > > First of all sorry for all unanswered mails, I got a stupid flu, > but now i feel better... ok now back to vbox, time for a new call > for testing :-) > > Following was added/fixed: > > - - ACPI Support was added > - - hostDVD support was added > - - Fix startup on HEAD > - - Plist problem under AMD64 was fixed > - - Qt4 Frontend is now Optional > - - Desktop file was added > - - Xorg dependencies was fixed > - - Guest additions was added (thx to Maho NAKATA ) Hi Martin, E-mail address might be maho@FreeBSD.org :) thank you -- Nakata Maho http://accc.riken.jp/maho/ , http://ja.openoffice.org/ Nakata Maho's PGP public keys: http://accc.riken.jp/maho/maho.pgp.txt -------------- 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/20090528/e06f37ac/attachment.pgp From doconnor at gsoft.com.au Thu May 28 03:34:21 2009 From: doconnor at gsoft.com.au (Daniel O'Connor) Date: Thu May 28 03:34:28 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 4 In-Reply-To: <20090527134343.GB1104@bsdcrew.de> References: <20090527134343.GB1104@bsdcrew.de> Message-ID: <200905281231.25830.doconnor@gsoft.com.au> On Wed, 27 May 2009, Martin Wilke wrote: > First of all sorry for all unanswered mails, I got a stupid flu, > but now i feel better... ok now back to vbox, time for a new call > for testing :-) > > Following was added/fixed: > > - ACPI Support was added > - hostDVD support was added > - Fix startup on HEAD > - Plist problem under AMD64 was fixed > - Qt4 Frontend is now Optional > - Desktop file was added > - Xorg dependencies was fixed > - Guest additions was added (thx to Maho NAKATA com>) Nice :) It works for me on -current/i386 (but they have all done so) however it did crash after I started the new VBox (I unloaded the old KLD, loaded the new one, start VM -> crash). Unfortunately X was running so it just reset with no crash dump. However the guest addition stuff didn't work properly for me.. I ran make config and selected it, vbox built, but at install time I got.. /bin/chmod 0711 /usr/local/lib/virtualbox/VBoxSVC /bin/chmod 0711 /usr/local/lib/virtualbox/VBoxXPCOMIPCD install -o root -g wheel -m 444 /usr/ports/distfiles/VBoxGuestAdditions_2.2.2.iso /usr/local/lib/virtualbox/ install: /usr/ports/distfiles/VBoxGuestAdditions_2.2.2.iso: No such file or directory *** Error code 71 Stop in /usr/home/darius/projects/virtualbox. *** Error code 1 Stop in /usr/home/darius/projects/virtualbox. and that file is missing, if I do make fetch it doesn't download it either. If I do make fetch WITH_GUESTADDITIONS= it does download it. > Open task: > We have got 2 patches for nls support and the request > to make dbus and pulseaudio optional. These both will > be added with the next run. > > We'd like to say many many thanks for all your feedback. > > http://people.freebsd.org/~miwi/vbox/virtualbox_5.tgz Are there plans (or patches :) for adding other types of network support? NAT is usable but without the ability to forward ports it makes logging in via SSH rather tedious (ie log out from the VM with -R then log back in). Thanks for your work thus far, it's a very handy tool :) -- 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/20090528/b134df97/attachment.pgp From chat95 at mac.com Thu May 28 03:49:59 2009 From: chat95 at mac.com (Maho NAKATA) Date: Thu May 28 03:50:05 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 4 In-Reply-To: <200905281231.25830.doconnor@gsoft.com.au> References: <20090527134343.GB1104@bsdcrew.de> <200905281231.25830.doconnor@gsoft.com.au> Message-ID: <20090528.124746.193716404.chat95@mac.com> Hi miwi, In some environment, to fetch "VBoxGuestAdditions_2.2.2.iso" correctly, you must add "FETCH_ARGS= -pRr" (remove A). Note, somehow in virtualbox_5.tgz "FETCH_ARGS=-pRr" was removed. Thanks From: Daniel O'Connor Subject: Re: [Call For Testing] VirtualBox for FreeBSD! take 4 Date: Thu, 28 May 2009 12:31:17 +0930 > 444 /usr/ports/distfiles/VBoxGuestAdditions_2.2.2.iso /usr/local/lib/virtualbox/ > install: /usr/ports/distfiles/VBoxGuestAdditions_2.2.2.iso: No such file > and that file is missing, if I do make fetch it doesn't download it > either. -- Nakata Maho http://accc.riken.jp/maho/ , http://ja.openoffice.org/ Nakata Maho's PGP public keys: http://accc.riken.jp/maho/maho.pgp.txt -------------- 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/20090528/51dfdbee/attachment.pgp From avg at icyb.net.ua Thu May 28 05:44:07 2009 From: avg at icyb.net.ua (Andriy Gapon) Date: Thu May 28 05:44:13 2009 Subject: rc.d/kqemu still loads aio.ko? In-Reply-To: <200905272043.n4RKhpUv069407@triton.kn-bremen.de> References: <200905272043.n4RKhpUv069407@triton.kn-bremen.de> Message-ID: <4A1E24A2.6020604@icyb.net.ua> on 27/05/2009 23:43 Juergen Lock said the following: > In article <4A1D3958.7090600@icyb.net.ua> you write: >> I thought that newer qemu doesn't depend on aio any longer because it has some >> internal glue instead. But it seems that kqemu-kmod-devel port still installs rc.d >> script that automatically loads aio on start. > > This is only because the qemu-devel port is still at an older snapshot > that still requires aio.ko... Maybe time to IGNORE= use emulation/qemu port instead ? E.g. java/eclipse vs java/eclipse-devel -- Andriy Gapon From odhiambo at gmail.com Thu May 28 06:17:14 2009 From: odhiambo at gmail.com (=?UTF-8?B?T2RoaWFtYm8gIOODr+OCt+ODs+ODiOODsw==?=) Date: Thu May 28 06:17:20 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 4 In-Reply-To: <20090528.124746.193716404.chat95@mac.com> References: <20090527134343.GB1104@bsdcrew.de> <200905281231.25830.doconnor@gsoft.com.au> <20090528.124746.193716404.chat95@mac.com> Message-ID: <991123400905272317gc71fe2ci35e83a2e27e08ebc@mail.gmail.com> On Thu, May 28, 2009 at 6:47 AM, Maho NAKATA wrote: > Hi miwi, > > In some environment, to fetch "VBoxGuestAdditions_2.2.2.iso" correctly, > you must add "FETCH_ARGS= -pRr" (remove A). > Note, somehow in virtualbox_5.tgz "FETCH_ARGS=-pRr" was removed. I see the FETCH_ARGS= defined as you say, but I don't see where it gets used! Could that be the problem. I also have this failure on 7.2-STABLE: -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ "Clothes make the man. Naked people have little or no influence on society." -- Mark Twain From doconnor at gsoft.com.au Thu May 28 07:01:40 2009 From: doconnor at gsoft.com.au (Daniel O'Connor) Date: Thu May 28 07:01:47 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 4 In-Reply-To: <20090528.124746.193716404.chat95@mac.com> References: <20090527134343.GB1104@bsdcrew.de> <200905281231.25830.doconnor@gsoft.com.au> <20090528.124746.193716404.chat95@mac.com> Message-ID: <200905281631.31202.doconnor@gsoft.com.au> On Thu, 28 May 2009, Maho NAKATA wrote: > Hi miwi, > > In some environment, to fetch "VBoxGuestAdditions_2.2.2.iso" > correctly, you must add "FETCH_ARGS= -pRr" (remove A). > Note, somehow in virtualbox_5.tgz "FETCH_ARGS=-pRr" was removed. I see those options in the Makefile under a .if for WITH_GUESTADDITIONS - however I don't think that variable is set properly. You can see what I mean here.. [inchoate 16:28] ~/projects/virtualbox >sudo make checksum ===> Found saved configuration for virtualbox-2.2.2r19980 => MD5 Checksum OK for virtualbox-2.2.2r19980.tar.gz. => SHA256 Checksum OK for virtualbox-2.2.2r19980.tar.gz. [inchoate 16:29] ~/projects/virtualbox >make WITH_GUESTADDITIONS= checksum ===> Found saved configuration for virtualbox-2.2.2r19980 => MD5 Checksum OK for virtualbox-2.2.2r19980.tar.gz. => SHA256 Checksum OK for virtualbox-2.2.2r19980.tar.gz. => MD5 Checksum OK for VBoxGuestAdditions_2.2.2.iso. => SHA256 Checksum OK for VBoxGuestAdditions_2.2.2.iso. [inchoate 16:29] ~/projects/virtualbox >make -V WITH_GUESTADDITIONS true I wonder if the .include's are in the wrong place for 'make config' stuff? -- 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/20090528/d6fcd9ad/attachment.pgp From dougb at FreeBSD.org Thu May 28 08:16:42 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Thu May 28 08:16:59 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 4 In-Reply-To: <200905281631.31202.doconnor@gsoft.com.au> References: <20090527134343.GB1104@bsdcrew.de> <200905281231.25830.doconnor@gsoft.com.au> <20090528.124746.193716404.chat95@mac.com> <200905281631.31202.doconnor@gsoft.com.au> Message-ID: <4A1E4863.20209@FreeBSD.org> Daniel O'Connor wrote: > I see those options in the Makefile under a .if for > WITH_GUESTADDITIONS - however I don't think that variable is set > properly. A quick glance at the Makefile indicates that the test for that knob needs to be moved down below the pre- inclusion of bsd.port.mk. Portlint will bark about various things being added too late in the file, but there are no other options (pardon the pun). :) Doug From ulf.lilleengen at gmail.com Thu May 28 09:57:56 2009 From: ulf.lilleengen at gmail.com (Ulf Lilleengen) Date: Thu May 28 09:58:14 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 4 In-Reply-To: <20090527134343.GB1104@bsdcrew.de> References: <20090527134343.GB1104@bsdcrew.de> Message-ID: <20090528115754.GA1390@carrot.geeknest.org> On Wed, May 27, 2009 at 03:43:43PM +0200, Martin Wilke wrote: > > Howdy, > > First of all sorry for all unanswered mails, I got a stupid flu, > but now i feel better... ok now back to vbox, time for a new call > for testing :-) > > Following was added/fixed: > > - ACPI Support was added > - hostDVD support was added > - Fix startup on HEAD > - Plist problem under AMD64 was fixed > - Qt4 Frontend is now Optional > - Desktop file was added > - Xorg dependencies was fixed > - Guest additions was added (thx to Maho NAKATA ) > > Open task: > We have got 2 patches for nls support and the request > to make dbus and pulseaudio optional. These both will > be added with the next run. > > We'd like to say many many thanks for all your feedback. > > http://people.freebsd.org/~miwi/vbox/virtualbox_5.tgz > FreeBSD version: FreeBSD carrot.geeknest.org 7.2-STABLE FreeBSD 7.2-STABLE #16 r192900: Wed May 27 19:09:49 UTC 2009 lulf@carrot.geeknest.org:/usr/home/devel/freebsd/obj/usr/src/sys/CARROT i386 Using the svn port: rev 387 I get a panic when loading vboxdrv. It seems related to the hz fix-patch that was added, as the assertion Assert(cMillies != RT_INDEFINITE_WAIT); on line 212 in semevent-r0drv-freebsd.c:212 fails. 0 doadump () at pcpu.h:196 #1 0xc058dd08 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #2 0xc058dfe5 in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:574 #3 0xc07f3ff4 in trap_fatal (frame=0xf442ebc8, eva=0) at /usr/src/sys/i386/i386/trap.c:939 #4 0xc07f4d31 in trap (frame=0xf442ebc8) at /usr/src/sys/i386/i386/trap.c:726 #5 0xc07daddb in calltrap () at /usr/src/sys/i386/i386/exception.s:159 #6 0xc60e70be in rtSemEventWait (EventSem=0xc6032c90, cMillies=4294967295, fInterruptible=false) at /usr/home/lulf/src/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/Runtime/r0drv/freebsd/semevent-r0drv-freebsd.c:212 #7 0xc60e71b0 in RTSemEventWait (EventSem=0xc6032c90, cMillies=4294967295) at /usr/home/lulf/src/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/Runtime/r0drv/freebsd/semevent-r0drv-freebsd.c:240 #8 0xc60e47f1 in rtTimerThread (Thread=0xc6034c90, pvUser=0xc6033390) at /usr/home/lulf/src/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/Runtime/generic/timer-generic.cpp:238 #9 0xc60e96c0 in rtThreadMain (pThread=0xc6034c90, NativeThread=3314350912, pszThreadName=0xc6034cd0 "TIMER") at /usr/home/lulf/src/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/Runtime/common/misc/thread.cpp:635 #10 0xc60f5ee7 in rtThreadNativeMain (pvThreadInt=0xc6034c90) at /usr/home/lulf/src/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/Runtime/r0drv/freebsd/thread2-r0drv-freebsd.c:112 #11 0xc05689c1 in fork_exit (callout=0xc60f5ec0 , arg=0xc6034c90, frame=0xf442ed38) at /usr/src/sys/kern/kern_fork.c:811 #12 0xc07dae50 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:264 -- Ulf Lilleengen From doconnor at gsoft.com.au Thu May 28 12:23:37 2009 From: doconnor at gsoft.com.au (Daniel O'Connor) Date: Thu May 28 12:23:49 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 4 In-Reply-To: <4A1E7C7D.2010908@wintek.com> References: <20090527134343.GB1104@bsdcrew.de> <200905281231.25830.doconnor@gsoft.com.au> <4A1E7C7D.2010908@wintek.com> Message-ID: <200905282153.27850.doconnor@gsoft.com.au> On Thu, 28 May 2009, Richard Kuhns wrote: > NAT host port 2222 to ssh (22) in virtual machine 'psyche'. > Do this while the VM isn't running. > > $ VBoxManage setextradata psyche \ > > "VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestssh/Protocol" TCP $ > VBoxManage setextradata psyche \ > > "VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestssh/GuestPort" 22 $ > VBoxManage setextradata psyche \ > > "VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestssh/HostPort" 2222 > > Now you can just 'ssh -p 2222 localhost' to get into that particular > VM. Ah that is nice, however I picked the Intel controller.. How do I work out the magic name for that? getextradata doesn't list anything :( -- 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/20090528/e9437651/attachment.pgp From rjk at wintek.com Thu May 28 12:38:15 2009 From: rjk at wintek.com (Richard Kuhns) Date: Thu May 28 12:38:33 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 4 In-Reply-To: <200905282153.27850.doconnor@gsoft.com.au> References: <20090527134343.GB1104@bsdcrew.de> <200905281231.25830.doconnor@gsoft.com.au> <4A1E7C7D.2010908@wintek.com> <200905282153.27850.doconnor@gsoft.com.au> Message-ID: <4A1E85B1.80408@wintek.com> Daniel O'Connor wrote: > On Thu, 28 May 2009, Richard Kuhns wrote: >> NAT host port 2222 to ssh (22) in virtual machine 'psyche'. >> Do this while the VM isn't running. >> >> $ VBoxManage setextradata psyche \ >> >> "VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestssh/Protocol" TCP $ >> VBoxManage setextradata psyche \ >> >> "VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestssh/GuestPort" 22 $ >> VBoxManage setextradata psyche \ >> >> "VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestssh/HostPort" 2222 >> >> Now you can just 'ssh -p 2222 localhost' to get into that particular >> VM. > > Ah that is nice, however I picked the Intel controller.. How do I work > out the magic name for that? getextradata doesn't list anything :( > s/pcnet/e1000/ According to the user manual, anyhow. So far the only VMs I've created are running XP and a couple of Linux distros, and I haven't changed controllers. I'll say again that this port has really been a godsend. I've used VMware Workstation on Windows XP in the past, but being able to stick to FreeBSD has greatly simplified my life. Now my Windoze box can go back to being used for the occasional game, as God intended. - Rich -- Richard Kuhns Wintek Corporation E-mail: rjk@wintek.com 427 N 6th Street STE C Receptionist: 765-742-8428 Lafayette, IN 47901-2211 Direct Line: 765-269-8541 United States of America From rjk at wintek.com Thu May 28 12:38:35 2009 From: rjk at wintek.com (Richard Kuhns) Date: Thu May 28 12:38:50 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 4 In-Reply-To: <200905281231.25830.doconnor@gsoft.com.au> References: <20090527134343.GB1104@bsdcrew.de> <200905281231.25830.doconnor@gsoft.com.au> Message-ID: <4A1E7C7D.2010908@wintek.com> Daniel O'Connor wrote: > On Wed, 27 May 2009, Martin Wilke wrote: >> First of all sorry for all unanswered mails, I got a stupid flu, >> but now i feel better... ok now back to vbox, time for a new call >> for testing :-) >> >> Following was added/fixed: >> >> - ACPI Support was added >> - hostDVD support was added >> - Fix startup on HEAD >> - Plist problem under AMD64 was fixed >> - Qt4 Frontend is now Optional >> - Desktop file was added >> - Xorg dependencies was fixed >> - Guest additions was added (thx to Maho NAKATA > com>) > > Nice :) ... > > Are there plans (or patches :) for adding other types of network > support? NAT is usable but without the ability to forward ports it > makes logging in via SSH rather tedious (ie log out from the VM with -R > then log back in). > Here's something that might help: NAT host port 2222 to ssh (22) in virtual machine 'psyche'. Do this while the VM isn't running. $ VBoxManage setextradata psyche \ "VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestssh/Protocol" TCP $ VBoxManage setextradata psyche \ "VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestssh/GuestPort" 22 $ VBoxManage setextradata psyche \ "VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestssh/HostPort" 2222 Now you can just 'ssh -p 2222 localhost' to get into that particular VM. I'd also like to say thanks for the port! It's *very* useful! - Rich -- Richard Kuhns Wintek Corporation E-mail: rjk@wintek.com 427 N 6th Street STE C Receptionist: 765-742-8428 Lafayette, IN 47901-2211 Direct Line: 765-269-8541 United States of America From doconnor at gsoft.com.au Thu May 28 13:08:14 2009 From: doconnor at gsoft.com.au (Daniel O'Connor) Date: Thu May 28 13:08:27 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 4 In-Reply-To: <4A1E85B1.80408@wintek.com> References: <20090527134343.GB1104@bsdcrew.de> <200905282153.27850.doconnor@gsoft.com.au> <4A1E85B1.80408@wintek.com> Message-ID: <200905282238.06757.doconnor@gsoft.com.au> On Thu, 28 May 2009, Richard Kuhns wrote: > Daniel O'Connor wrote: > > On Thu, 28 May 2009, Richard Kuhns wrote: > >> NAT host port 2222 to ssh (22) in virtual machine 'psyche'. > >> Do this while the VM isn't running. > >> > >> $ VBoxManage setextradata psyche \ > >> > >> "VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestssh/Protocol" TCP > >> $ VBoxManage setextradata psyche \ > >> > >> "VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestssh/GuestPort" 22 > >> $ VBoxManage setextradata psyche \ > >> > >> "VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestssh/HostPort" 2222 > >> > >> Now you can just 'ssh -p 2222 localhost' to get into that > >> particular VM. > > > > Ah that is nice, however I picked the Intel controller.. How do I > > work out the magic name for that? getextradata doesn't list > > anything :( > > s/pcnet/e1000/ Ahah, I tried 82540EM.. > According to the user manual, anyhow. So far the only VMs I've I guess I should read that :) > created are running XP and a couple of Linux distros, and I haven't > changed controllers. I put Windows in one and I though an e1000 would be nicer, although I must confess I've hardly thrashed it :) > I'll say again that this port has really been a godsend. I've used > VMware Workstation on Windows XP in the past, but being able to stick > to FreeBSD has greatly simplified my life. Now my Windoze box can go > back to being used for the occasional game, as God intended. Heh indeed, it's handy. Good for running some legacy code too.. -- 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/20090528/7b9fc7e3/attachment.pgp From nox at jelal.kn-bremen.de Thu May 28 16:25:33 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Thu May 28 16:25:40 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 4 In-Reply-To: <20090528115754.GA1390@carrot.geeknest.org> References: <20090527134343.GB1104@bsdcrew.de> Message-ID: <200905281622.n4SGMJsc006847@triton.kn-bremen.de> In article <20090528115754.GA1390@carrot.geeknest.org> you write: >On Wed, May 27, 2009 at 03:43:43PM +0200, Martin Wilke wrote: >> >> Howdy, >> >> First of all sorry for all unanswered mails, I got a stupid flu, >> but now i feel better... ok now back to vbox, time for a new call >> for testing :-) >> >> Following was added/fixed: >> >> - ACPI Support was added >> - hostDVD support was added >> - Fix startup on HEAD >> - Plist problem under AMD64 was fixed >> - Qt4 Frontend is now Optional >> - Desktop file was added >> - Xorg dependencies was fixed >> - Guest additions was added (thx to Maho NAKATA ) >> >> Open task: >> We have got 2 patches for nls support and the request >> to make dbus and pulseaudio optional. These both will >> be added with the next run. >> >> We'd like to say many many thanks for all your feedback. >> >> http://people.freebsd.org/~miwi/vbox/virtualbox_5.tgz >> >FreeBSD version: >FreeBSD carrot.geeknest.org 7.2-STABLE FreeBSD 7.2-STABLE #16 r192900: Wed May 27 19:09:49 UTC 2009 lulf@carrot.geeknest.org:/usr/home/devel/freebsd/obj/usr/src/sys/CARROT i386 >Using the svn port: rev 387 > >I get a panic when loading vboxdrv. It seems related to the hz fix-patch that >was added, as the assertion Assert(cMillies != RT_INDEFINITE_WAIT); on line > 212 in semevent-r0drv-freebsd.c:212 fails. > >0 doadump () at pcpu.h:196 >#1 0xc058dd08 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 >#2 0xc058dfe5 in panic (fmt=Variable "fmt" is not available. >) at /usr/src/sys/kern/kern_shutdown.c:574 >#3 0xc07f3ff4 in trap_fatal (frame=0xf442ebc8, eva=0) > at /usr/src/sys/i386/i386/trap.c:939 >#4 0xc07f4d31 in trap (frame=0xf442ebc8) at /usr/src/sys/i386/i386/trap.c:726 >#5 0xc07daddb in calltrap () at /usr/src/sys/i386/i386/exception.s:159 >#6 0xc60e70be in rtSemEventWait (EventSem=0xc6032c90, cMillies=4294967295, > fInterruptible=false) > at /usr/home/lulf/src/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/Runtime/r0drv/freebsd/semevent-r0drv-freebsd.c:212 >#7 0xc60e71b0 in RTSemEventWait (EventSem=0xc6032c90, cMillies=4294967295) > at /usr/home/lulf/src/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/Runtime/r0drv/freebsd/semevent-r0drv-freebsd.c:240 >#8 0xc60e47f1 in rtTimerThread (Thread=0xc6034c90, pvUser=0xc6033390) > at /usr/home/lulf/src/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/Runtime/generic/timer-generic.cpp:238 >#9 0xc60e96c0 in rtThreadMain (pThread=0xc6034c90, NativeThread=3314350912, > pszThreadName=0xc6034cd0 "TIMER") > at /usr/home/lulf/src/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/Runtime/common/misc/thread.cpp:635 >#10 0xc60f5ee7 in rtThreadNativeMain (pvThreadInt=0xc6034c90) > at /usr/home/lulf/src/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/Runtime/r0drv/freebsd/thread2-r0drv-freebsd.c:112 >#11 0xc05689c1 in fork_exit (callout=0xc60f5ec0 , > arg=0xc6034c90, frame=0xf442ed38) at /usr/src/sys/kern/kern_fork.c:811 >#12 0xc07dae50 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:264 This is also what I get now (only looked like a `hang' yesterday since I was in X and it dropped into ddb, now I did the kldload from console, forced a crashdump and the backtrace looks just like yours, except that my vboxdrv.ko doesn't have debug symbols.) Just thought I'd mention... Juergen From delphij at FreeBSD.org Fri May 29 05:05:32 2009 From: delphij at FreeBSD.org (delphij@FreeBSD.org) Date: Fri May 29 05:05:38 2009 Subject: kern/91293: [svr4] [patch] *Experimental* Update to the SVR4 emulation (from NetBSD) Message-ID: <200905290505.n4T55Wpr099614@freefall.freebsd.org> Synopsis: [svr4] [patch] *Experimental* Update to the SVR4 emulation (from NetBSD) Responsible-Changed-From-To: freebsd-emulation->delphij Responsible-Changed-By: delphij Responsible-Changed-When: Fri May 29 05:05:04 UTC 2009 Responsible-Changed-Why: Take (somehow I touch it and I buy it...) http://www.freebsd.org/cgi/query-pr.cgi?pr=91293 From QAT at FreeBSD.org Fri May 29 12:20:19 2009 From: QAT at FreeBSD.org (QAT@FreeBSD.org) Date: Fri May 29 12:20:25 2009 Subject: emulators/linux_base-fc4 - fails: mtree Message-ID: <20090529114800.E8CF08FC50@release.ixsystems.com> The Restless Daemon identified a mtree error while trying to build: linux_base-fc-4_14 maintained by freebsd-emulation@FreeBSD.org Makefile ident: $FreeBSD: ports/emulators/linux_base-fc4/Makefile,v 1.32 2009/01/21 16:17:46 bsam Exp $ THIS A BUILD WITH CUSTOM PREFIX AND LOCALBASE, _standard_ env in rest. To check if the port builds OK with STANDARD PREFIX/LOCALBASE and with -DNOPORT* please see: http://qat.tecnik93.com/index.php?action=list_buildports&build=7-STABLE-FPT-NPD&search_port_name=linux_base-fc4 PortsMon page for the port: http://portsmon.freebsd.org/portoverview.py?category=emulators&portname=linux_base-fc4 Excerpt from http://QATy.TecNik93.com/logs/7-STABLE-FPT-CustDir/linux_base-fc-4_14.log : ===> Registering installation for linux_base-fc-4_14 ===> SECURITY REPORT: This port has installed the following files which may act as network servers and may therefore pose a remote security risk to the system. /usr/PPP/lib/libresolv-2.3.6.so /usr/PPP/lib/libselinux.so.1 /usr/PPP/usr/lib/libkrb5.so.3.2 (USES POSSIBLY INSECURE FUNCTIONS: mktemp) /usr/PPP/usr/lib/libgssrpc.so.4.0 If there are vulnerabilities in these programs there may be a security risk to the system. FreeBSD makes no guarantee about the security of ports included in the Ports Collection. Please type 'make deinstall' to deinstall the port if this is a concern. ================================================================ ======================================== ===> Building package for linux_base-fc-4_14 Creating package /tmp/packages/All/linux_base-fc-4_14.tbz Registering depends:. Registering conflicts: linux_base-gentoo* linux_locale* linux_base-f8* linux_base-f7* linux_base-fc6*. Creating bzip'd tar ball in '/tmp/packages/All/linux_base-fc-4_14.tbz' Deleting linux_base-fc-4_14 You may need to do by hand: o unmount linprocfs if mounted o delete /usr/PPP/proc if present o remove/comment linprocfs from /etc/fstab if present pkg_delete: unable to completely remove directory '/usr/PPP/lib' pkg_delete: unable to completely remove directory '/usr/PPP/etc' pkg_delete: unable to completely remove directory '/usr/PPP/bin' pkg_delete: couldn't entirely delete package (perhaps the packing list is incorrectly specified?) ================================================================ === Checking filesystem state list of files present before this port was installed but missing after it was deinstalled) ./usr/PPP/etc/pam.d missing ./usr/PPP/sbin missing ================================================================ build of /usr/ports/emulators/linux_base-fc4 ended at Fri May 29 11:47:58 UTC 2009 The tarballed WRKDIR can be found here: http://QATy.TecNik93.com/wrkdirs/7-STABLE-FPT-CustDir/linux_base-fc-4_14.tbz The build which triggered this BotMail was done under tinderbox-devel-3.2_4; dsversion: 3.2 on RELENG_7 on amd64, kern.smp.cpus: 4 with tinderd_flags="-nullfs -plistcheck -onceonly" and ccache support, with the PREFIX=/usr/PPP, LOCABASE=/usr/PPP, X11BASE=/usr/PPP A description of the testing process can be found here: http://T32.TecNik93.com/FreeBSD/QA-Tindy/ Thanks for your work on making FreeBSD better, -- QAT - your friendly neighborhood Daemon, preparing a heck of an error trapping system: - "HMC and EOI?" - "Halt, Melt and Catch fire or Execute Operator Immediately." From svein-listmail at stillbilde.net Fri May 29 12:23:12 2009 From: svein-listmail at stillbilde.net (Svein Skogen (listmail accont)) Date: Fri May 29 12:23:19 2009 Subject: Cross post question from virtualization: VMWare PVSCSI support. Message-ID: <4A1FCF1F.4060504@stillbilde.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I originally posted this to the Virtualization list, but later realized that emulation might be better suited. I'm running several FreeBSD guests inside ESXi4, and have (on the windows VMs) noticed a major increase in disk performance with the pvscsi "adapter". The OpenVMTools has the kernel module driver for Linux. Are there any plans on adding this to FreeBSD as well? //Svein - -- - --------+-------------------+------------------------------- /"\ |Svein Skogen | svein@d80.iso100.no \ / |Solberg ?stli 9 | PGP Key: 0xE5E76831 X |2020 Skedsmokorset | svein@jernhuset.no / \ |Norway | PGP Key: 0xCE96CE13 | | svein@stillbilde.net ascii | | PGP Key: 0x58CD33B6 ribbon |System Admin | svein-listmail@stillbilde.net Campaign|stillbilde.net | PGP Key: 0x22D494A4 +-------------------+------------------------------- |msn messenger: | Mobile Phone: +47 907 03 575 |svein@jernhuset.no | RIPE handle: SS16503-RIPE - --------+-------------------+------------------------------- Picture Gallery: https://gallery.stillbilde.net/v/svein/ - ------------------------------------------------------------ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkofzx8ACgkQODUnwSLUlKTyiwCgpKkICl7+nx2e9v6Ho1yswJfn qRkAnjvUB3uNcrEYx0vqlWztmcYXQyx6 =oqq/ -----END PGP SIGNATURE----- From nox at jelal.kn-bremen.de Fri May 29 17:23:19 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Fri May 29 17:23:27 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 4 In-Reply-To: <200905281622.n4SGMJsc006847@triton.kn-bremen.de> References: <20090527134343.GB1104@bsdcrew.de> <200905281622.n4SGMJsc006847@triton.kn-bremen.de> Message-ID: <20090529171939.GA2540@triton.kn-bremen.de> On Thu, May 28, 2009 at 06:22:19PM +0200, Juergen Lock wrote: > In article <20090528115754.GA1390@carrot.geeknest.org> you write: > >On Wed, May 27, 2009 at 03:43:43PM +0200, Martin Wilke wrote: > >> > >> Howdy, > >> > >> First of all sorry for all unanswered mails, I got a stupid flu, > >> but now i feel better... ok now back to vbox, time for a new call > >> for testing :-) > >> > >> Following was added/fixed: > >> > >> - ACPI Support was added > >> - hostDVD support was added > >> - Fix startup on HEAD > >> - Plist problem under AMD64 was fixed > >> - Qt4 Frontend is now Optional > >> - Desktop file was added > >> - Xorg dependencies was fixed > >> - Guest additions was added (thx to Maho NAKATA ) > >> > >> Open task: > >> We have got 2 patches for nls support and the request > >> to make dbus and pulseaudio optional. These both will > >> be added with the next run. > >> > >> We'd like to say many many thanks for all your feedback. > >> > >> http://people.freebsd.org/~miwi/vbox/virtualbox_5.tgz > >> > >FreeBSD version: > >FreeBSD carrot.geeknest.org 7.2-STABLE FreeBSD 7.2-STABLE #16 r192900: Wed May 27 19:09:49 UTC 2009 lulf@carrot.geeknest.org:/usr/home/devel/freebsd/obj/usr/src/sys/CARROT i386 > >Using the svn port: rev 387 > > > >I get a panic when loading vboxdrv. It seems related to the hz fix-patch that > >was added, as the assertion Assert(cMillies != RT_INDEFINITE_WAIT); on line > > 212 in semevent-r0drv-freebsd.c:212 fails. > > > >0 doadump () at pcpu.h:196 > >#1 0xc058dd08 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 > >#2 0xc058dfe5 in panic (fmt=Variable "fmt" is not available. > >) at /usr/src/sys/kern/kern_shutdown.c:574 > >#3 0xc07f3ff4 in trap_fatal (frame=0xf442ebc8, eva=0) > > at /usr/src/sys/i386/i386/trap.c:939 > >#4 0xc07f4d31 in trap (frame=0xf442ebc8) at /usr/src/sys/i386/i386/trap.c:726 > >#5 0xc07daddb in calltrap () at /usr/src/sys/i386/i386/exception.s:159 > >#6 0xc60e70be in rtSemEventWait (EventSem=0xc6032c90, cMillies=4294967295, > > fInterruptible=false) > > at /usr/home/lulf/src/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/Runtime/r0drv/freebsd/semevent-r0drv-freebsd.c:212 > >#7 0xc60e71b0 in RTSemEventWait (EventSem=0xc6032c90, cMillies=4294967295) > > at /usr/home/lulf/src/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/Runtime/r0drv/freebsd/semevent-r0drv-freebsd.c:240 > >#8 0xc60e47f1 in rtTimerThread (Thread=0xc6034c90, pvUser=0xc6033390) > > at /usr/home/lulf/src/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/Runtime/generic/timer-generic.cpp:238 > >#9 0xc60e96c0 in rtThreadMain (pThread=0xc6034c90, NativeThread=3314350912, > > pszThreadName=0xc6034cd0 "TIMER") > > at /usr/home/lulf/src/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/Runtime/common/misc/thread.cpp:635 > >#10 0xc60f5ee7 in rtThreadNativeMain (pvThreadInt=0xc6034c90) > > at /usr/home/lulf/src/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/Runtime/r0drv/freebsd/thread2-r0drv-freebsd.c:112 > >#11 0xc05689c1 in fork_exit (callout=0xc60f5ec0 , > > arg=0xc6034c90, frame=0xf442ed38) at /usr/src/sys/kern/kern_fork.c:811 > >#12 0xc07dae50 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:264 > > This is also what I get now (only looked like a `hang' yesterday since > I was in X and it dropped into ddb, now I did the kldload from console, > forced a crashdump and the backtrace looks just like yours, except that > my vboxdrv.ko doesn't have debug symbols.) Ok I just tried reverting the hz=100 patch (got it from http://pastebin.ca/1433127 as mentioned here a while ago), and that fixed the problem for me. (Of course I'm running with hz=1000, otherwise it probably wouldn't work.) So at least I can now confirm that patch seems to be whats causing the problem... HTH, Juergen PS: smp isn't supposed to work yet, right? At least I get a warning saying I had only one cpu when trying to give a guest more than one, but in fact this box has 4 cores... From guru at unixarea.de Sat May 30 07:00:28 2009 From: guru at unixarea.de (Matthias Apitz) Date: Sat May 30 07:00:35 2009 Subject: Skype-2.0 is here! In-Reply-To: <200804142217.17035.beech@FreeBSD.org> References: <200804142217.17035.beech@FreeBSD.org> Message-ID: <20090530070025.GA2465@current.Sisis.de> El d?a Monday, April 14, 2008 a las 10:17:12PM -0800, Beech Rintoul escribi?: > Finally, skype-devel has been updated to the new 2.0.0.68 version. > This is the one that includes video and any input to get this (video) > going is appreciated. Everything else seems to work as advertised. > > If you're going to update to this version, please read > UPDATING-20080318. > > Enjoy, > > Beech Hello Beech, I'm running on my laptop 8-CURRENT (of May 28), have the pwc.ko loaded which gives me a device /dev/video0 and pwcview is showing my face; as well I have installed skype-2.0.0.72,1 from the ports which works fine but does not recognice the video device; what should I do or test to bring this together? Thanks 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 hselasky at freebsd.org Sat May 30 08:51:35 2009 From: hselasky at freebsd.org (Hans Petter Selasky) Date: Sat May 30 08:51:48 2009 Subject: Skype-2.0 is here! In-Reply-To: <20090530070025.GA2465@current.Sisis.de> References: <200804142217.17035.beech@FreeBSD.org> <20090530070025.GA2465@current.Sisis.de> Message-ID: <200905300955.34102.hselasky@freebsd.org> On Saturday 30 May 2009, Matthias Apitz wrote: > El d?a Monday, April 14, 2008 a las 10:17:12PM -0800, Beech Rintoul escribi?: > > Finally, skype-devel has been updated to the new 2.0.0.68 version. > > This is the one that includes video and any input to get this (video) > > going is appreciated. Everything else seems to work as advertised. > > > > If you're going to update to this version, please read > > UPDATING-20080318. > > > > Enjoy, > > > > Beech > > Hello Beech, > > I'm running on my laptop 8-CURRENT (of May 28), have the pwc.ko loaded > which gives me a device /dev/video0 and pwcview is showing my face; as > well I have installed skype-2.0.0.72,1 from the ports which works fine > but does not recognice the video device; what should I do or test to > bring this together? Thanks > > matthias Hi all, We need some common effort to get Video4Linux USB devices working on FreeBSD. First of all we need to push a video4linux library. -lvideodevx Methods: int videodevx_open(int unit); /* returns a handle, not neccesarily a file-handle */ int videodevx_read(int hdl, ptr, len); int videodevx_write(int hdl, ptr, len); int videodevx_ioctl(int hdl, cmd, arg); int videodevx_mmap(int hdl, void *addr, size_t len, int prot, int flags, int fd, off_t offset); int videodevx_getfd(int hdl); /* used for polling */ int videodevx_close(int hdl); Some work in progress is available from: svn --username anonsvn --password anonsvn \ checkout svn://svn.turbocat.net/i4b/trunk/usbcam Download "linux-2.6.29" to "ulinux/linux" cd ulinux make clean all NOTE: It's not linking yet. Second, we need a userland port for Video4Linux, which I am working on. So that the application directly receives the USB data and talks to the webcam through -lvideodevx and the new BSD licensed -lusb . Third we need to convince everyone to use videodevx when opening video devices. On linux videodevx will simply be a wrapper for open/close/ioctl/... . On FreeBSD videodevx will be a complete USB webcam driver library. Anyone that wants to join heads? --HPS From rizzo at iet.unipi.it Sat May 30 09:17:09 2009 From: rizzo at iet.unipi.it (Luigi Rizzo) Date: Sat May 30 09:17:21 2009 Subject: Skype-2.0 is here! In-Reply-To: <200905300955.34102.hselasky@freebsd.org> References: <200804142217.17035.beech@FreeBSD.org> <20090530070025.GA2465@current.Sisis.de> <200905300955.34102.hselasky@freebsd.org> Message-ID: <20090530090540.GC46541@onelab2.iet.unipi.it> On Sat, May 30, 2009 at 09:55:32AM +0200, Hans Petter Selasky wrote: > On Saturday 30 May 2009, Matthias Apitz wrote: > > El d?a Monday, April 14, 2008 a las 10:17:12PM -0800, Beech Rintoul > escribi?: > > > Finally, skype-devel has been updated to the new 2.0.0.68 version. > > > This is the one that includes video and any input to get this (video) > > > going is appreciated. Everything else seems to work as advertised. > > > > > > If you're going to update to this version, please read > > > UPDATING-20080318. > > > > > > Enjoy, > > > > > > Beech > > > > Hello Beech, > > > > I'm running on my laptop 8-CURRENT (of May 28), have the pwc.ko loaded > > which gives me a device /dev/video0 and pwcview is showing my face; as > > well I have installed skype-2.0.0.72,1 from the ports which works fine > > but does not recognice the video device; what should I do or test to > > bring this together? Thanks > > > > matthias > > Hi all, > > We need some common effort to get Video4Linux USB devices working on FreeBSD. > First of all we need to push a video4linux library. > > -lvideodevx > > Methods: > > int videodevx_open(int unit); /* returns a handle, not neccesarily a > file-handle */ > int videodevx_read(int hdl, ptr, len); > int videodevx_write(int hdl, ptr, len); > int videodevx_ioctl(int hdl, cmd, arg); > int videodevx_mmap(int hdl, void *addr, size_t len, int prot, int flags, int > fd, off_t offset); > int videodevx_getfd(int hdl); /* used for polling */ > int videodevx_close(int hdl); > > Some work in progress is available from: > > svn --username anonsvn --password anonsvn \ > checkout svn://svn.turbocat.net/i4b/trunk/usbcam > > Download "linux-2.6.29" to "ulinux/linux" > > cd ulinux > > make clean all > > NOTE: It's not linking yet. > > Second, we need a userland port for Video4Linux, which I am working on. So > that the application directly receives the USB data and talks to the webcam > through -lvideodevx and the new BSD licensed -lusb . > > Third we need to convince everyone to use videodevx when opening video > devices. On linux videodevx will simply be a wrapper for > open/close/ioctl/... . On FreeBSD videodevx will be a complete USB webcam > driver library. > > Anyone that wants to join heads? Excellent summary which covers the situation for native apps. I wonder if the case is a bit different for skype and linux binaries in general, as they run under linux emulation so perhaps the it is the linuxulator that has to emulate the v4l(2?) calls, and i have no idea if this needs to be done in the kernel or we can deal with this in some libc wrapper ? cheers luigi From guru at unixarea.de Sat May 30 10:32:59 2009 From: guru at unixarea.de (Matthias Apitz) Date: Sat May 30 10:33:12 2009 Subject: Skype-2.0 is here! In-Reply-To: <20090530090540.GC46541@onelab2.iet.unipi.it> References: <200804142217.17035.beech@FreeBSD.org> <20090530070025.GA2465@current.Sisis.de> <200905300955.34102.hselasky@freebsd.org> <20090530090540.GC46541@onelab2.iet.unipi.it> Message-ID: <20090530103254.GA3368@current.Sisis.de> El d?a Saturday, May 30, 2009 a las 11:05:40AM +0200, Luigi Rizzo escribi?: > On Sat, May 30, 2009 at 09:55:32AM +0200, Hans Petter Selasky wrote: > > > > Hi all, > > > > We need some common effort to get Video4Linux USB devices working on FreeBSD. > > First of all we need to push a video4linux library. > > > > -lvideodevx > > > > Methods: > > > > int videodevx_open(int unit); /* returns a handle, not neccesarily a > > file-handle */ > > int videodevx_read(int hdl, ptr, len); > > int videodevx_write(int hdl, ptr, len); > > int videodevx_ioctl(int hdl, cmd, arg); > > int videodevx_mmap(int hdl, void *addr, size_t len, int prot, int flags, int > > fd, off_t offset); > > int videodevx_getfd(int hdl); /* used for polling */ > > int videodevx_close(int hdl); > > > > Some work in progress is available from: > > > > svn --username anonsvn --password anonsvn \ > > checkout svn://svn.turbocat.net/i4b/trunk/usbcam > > > > Download "linux-2.6.29" to "ulinux/linux" > > > > cd ulinux > > > > make clean all > > > > NOTE: It's not linking yet. > > > > Second, we need a userland port for Video4Linux, which I am working on. So > > that the application directly receives the USB data and talks to the webcam > > through -lvideodevx and the new BSD licensed -lusb . > > > > Third we need to convince everyone to use videodevx when opening video > > devices. On linux videodevx will simply be a wrapper for > > open/close/ioctl/... . On FreeBSD videodevx will be a complete USB webcam > > driver library. > > > > Anyone that wants to join heads? > > Excellent summary which covers the situation for native apps. > > I wonder if the case is a bit different for skype and linux binaries > in general, as they run under linux emulation so perhaps the > it is the linuxulator that has to emulate the v4l(2?) calls, > and i have no idea if this needs to be done in the kernel or we > can deal with this in some libc wrapper ? Some time ago (using RELENG_7) I did some effort to port Ekiga, PWLib and Opal out of SVN to FreeBSD because the port versions have been outdated at this time. I wanted to use the Ekiga client to connect to our Polycon VC system but there was a bug in the Polycon which could not decifer the video encoding and so this ended up for me in a dead project :-( old details are here: http://wiki.ekiga.org/index.php/Compile_your_own_SVN_version_of_Ekiga_on_FreeBSD In any case, there was support for video in ptlib/plugins/vidinput_v4l/vidinput_v4l.cxx and the only change I had to made to make it work in FreeBSD was the manner of picking up the /dev/video0 and not using the Linux major and minor number: #if defined(P_FREEBSD) // device numbers are irrelevant here, so we match on names // instead. if (filename.GetLength() <= 5 || filename.Left(5) != "video") continue; int num = atoi(filename.Mid(6)); if (num < 0 || num > 63) continue; vid.SetAt(num, devname); #else static const int deviceNumbers[] = { 81 }; for (PINDEX i = 0; i < PARRAYSIZE(deviceNumbers); i++) { if (MAJOR(s.st_rdev) == deviceNumbers[i]) { PINDEX num = MINOR(s.st_rdev); if (num <= 63 && num >= 0) { vid.SetAt(num, devname); } } } #endif the rest of the code was just working above the /dev/video0 device provided by the pwc.ko. I'm wondering if we could make use of the PTlib plug-in for this as well? To bring it under the linuxemulator is another story, though. CU 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 nox at jelal.kn-bremen.de Sat May 30 20:56:12 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Sat May 30 20:56:19 2009 Subject: Thanx for the kqemu patches; some notes about NetBSD/OpenBSD guests Message-ID: <20090530205152.GA7702@triton.kn-bremen.de> Hi! I just committed Jan's kqemu patch series to the FreeBSD kqemu port (yes FreeBSD is another one of those `left behind' OSes where kvm doesn't really work yet...) - and I also committed an old NetBSD/OpenBSD guest kqemu patch, http://lists.gnu.org/archive/html/qemu-devel/2007-11/msg00125.html and then played with a NetBSD guest in qemu 0.10.5 a little, where I found out a few things: 1. A few times I even got NetBSD 5.0/i386 running with -kernel-kqemu now, tho a few other times I also got guest processes segfaulting etc. `Regualr' kqemu seems stable now tho. 2. NetBSD doesn't seem to particularly like qemu's acpi tables, it apparenly doesn't find a pci bus and anything on it in that case (like a nic our audio card; `pcictl pci0 list' says Device not configured.) 3. When I disable acpi either via the boot menu or via -no-acpi it still has trouble assigning pci irqs correctly (like, uses irq 12 instead of 11 for the nic) - this seems to have something to do with the emulated io-apic that it still picks up in that case - if I disable that by building a new bios that has this patch reverted, pc-bios/bios-pq/0003_kvm-bios-generate-mptable-unconditionally.patch the irqs at least get assigned correctly. (Maybe the bios should only pass an mptable for a single cpu when there also is acpi?) 4. most of qemu's emulated nics NetBSD still doesn't like, I had most luck with pcnet. (5. vbox has troubles with NetBSD too, it only boots here when I enable svm _and_ npt. Luckily that's also when a vm runs the fastest, but of course npt/ept are also still pretty rare...) Oh, if anyone wants dmesg.s of the various with/without acpi/io-apic combinations I can post those too, the patched bios I just put at: http://people.freebsd.org/~nox/qemu/pc-bios-0.10.5-no-default-mptable/bios.bin (I had to end up building it on a Linux guest, our assembler said things like rombios32start.S:56: Error: `0(%ebx)' is not a valid 16 bit base/index expression .) Thanx, Juergen From herbszt at gmx.de Sat May 30 23:34:34 2009 From: herbszt at gmx.de (Sebastian Herbszt) Date: Sat May 30 23:34:41 2009 Subject: Thanx for the kqemu patches; some notes about NetBSD/OpenBSD guests In-Reply-To: <20090530205152.GA7702@triton.kn-bremen.de> References: <20090530205152.GA7702@triton.kn-bremen.de> Message-ID: <799A5F31E2B2415DA53F558FE3E2ACE7@FSCPC> Juergen Lock wrote: > 2. NetBSD doesn't seem to particularly like qemu's acpi tables, it > apparenly doesn't find a pci bus and anything on it in that case > (like a nic our audio card; `pcictl pci0 list' says Device not configured.) > > 3. When I disable acpi either via the boot menu or via -no-acpi it still > has trouble assigning pci irqs correctly (like, uses irq 12 instead of 11 > for the nic) - this seems to have something to do with the emulated > io-apic that it still picks up in that case - if I disable that by > building a new bios that has this patch reverted, > pc-bios/bios-pq/0003_kvm-bios-generate-mptable-unconditionally.patch > the irqs at least get assigned correctly. (Maybe the bios should only > pass an mptable for a single cpu when there also is acpi?) With "-no-acpi" there is no PIIX4 PM added to the bus. If i don't mistake the mp and acpi tables aren't affected by this. The mptable doesn't contain a pci bus entry (just isa). The linux kernel does complain if booted with "acpi=off"; maybe NetBSD is more picky. > Oh, if anyone wants dmesg.s of the various with/without acpi/io-apic > combinations I can post those too, the patched bios I just put at: > http://people.freebsd.org/~nox/qemu/pc-bios-0.10.5-no-default-mptable/bios.bin I would like to see the output. > (I had to end up building it on a Linux guest, our assembler said things > like > rombios32start.S:56: Error: `0(%ebx)' is not a valid 16 bit base/index expression > .) What's your tool chain (gcc, binutils,...) ? - Sebastian From nox at jelal.kn-bremen.de Sun May 31 00:40:47 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Sun May 31 00:40:54 2009 Subject: Thanx for the kqemu patches; some notes about NetBSD/OpenBSD guests In-Reply-To: <799A5F31E2B2415DA53F558FE3E2ACE7@FSCPC> References: <20090530205152.GA7702@triton.kn-bremen.de> <799A5F31E2B2415DA53F558FE3E2ACE7@FSCPC> Message-ID: <20090531003701.GA13927@triton.kn-bremen.de> On Sun, May 31, 2009 at 01:06:31AM +0200, Sebastian Herbszt wrote: > Juergen Lock wrote: > > 2. NetBSD doesn't seem to particularly like qemu's acpi tables, it > > apparenly doesn't find a pci bus and anything on it in that case > > (like a nic our audio card; `pcictl pci0 list' says Device not configured.) > > > > 3. When I disable acpi either via the boot menu or via -no-acpi it still > > has trouble assigning pci irqs correctly (like, uses irq 12 instead of 11 > > for the nic) - this seems to have something to do with the emulated > > io-apic that it still picks up in that case - if I disable that by > > building a new bios that has this patch reverted, > > pc-bios/bios-pq/0003_kvm-bios-generate-mptable-unconditionally.patch > > the irqs at least get assigned correctly. (Maybe the bios should only > > pass an mptable for a single cpu when there also is acpi?) > > With "-no-acpi" there is no PIIX4 PM added to the bus. If i don't mistake the > mp and acpi tables aren't affected by this. > > The mptable doesn't contain a pci bus entry (just isa). The linux kernel does > complain if booted with "acpi=off"; maybe NetBSD is more picky. > Aha so maybe NetBSD is expectig to see the pci bus listed in acpi then... > > Oh, if anyone wants dmesg.s of the various with/without acpi/io-apic > > combinations I can post those too, the patched bios I just put at: > > http://people.freebsd.org/~nox/qemu/pc-bios-0.10.5-no-default-mptable/bios.bin > > I would like to see the output. > OK I'll append below. > > (I had to end up building it on a Linux guest, our assembler said things > > like > > rombios32start.S:56: Error: `0(%ebx)' is not a valid 16 bit base/index expression > > .) > > What's your tool chain (gcc, binutils,...) ? Whatever is in FreeBSD 7.2-stable base, lets see... zsh triton% as --version GNU assembler 2.15 [FreeBSD] 2004-05-23 zsh triton% ld --version GNU ld version 2.15 [FreeBSD] 2004-05-23 Heh doesn't look particularly new indeed :) Thanx, Juergen 1. acpi + mptable: (upstream bios; notice no pci0, piixide0, pcn0, and auich0) --------snip------------ Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 The NetBSD Foundation, Inc. All rights reserved. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. NetBSD 5.0 (GENERIC) #0: Sun Apr 26 18:50:08 UTC 2009 builds@b6.netbsd.org:/home/builds/ab/netbsd-5-0-RELEASE/i386/200904260229Z-obj/home/builds/ab/netbsd-5-0-RELEASE/src/sys/arch/i386/compile/GENERIC total memory = 1023 MB avail memory = 994 MB timecounter: Timecounters tick every 10.000 msec timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100 Generic PC mainbus0 (root) cpu0 at mainbus0 apid 0: Intel 686-class, id 0x633 ioapic0 at mainbus0 apid 1: pa 0xfec00000, version 11, 24 pins acpi0 at mainbus0: Intel ACPICA 20080321 acpi0: X/RSDT: OemId , AslId acpi0: SCI interrupting at int 9 acpi0: fixed-feature power button present timecounter: Timecounter "ACPI-Safe" frequency 3579545 Hz quality 900 ACPI-Safe 24-bit timer pckbc1 at acpi0 (KBD, PNP0303): kbd port pckbc1: io 0x60,0x64 irq 1 pckbc2 at acpi0 (MOU, PNP0F13): aux port pckbc2: irq 12 FDC0 (PNP0700) at acpi0 not configured LPT (PNP0400) at acpi0 not configured COM1 (PNP0501) at acpi0 not configured apm0 at acpi0: Power Management spec V1.2 pckbd0 at pckbc1 (kbd slot) pckbc1: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard pms0 at pckbc1 (aux slot) pckbc1: using irq 12 for aux slot wsmouse0 at pms0 mux 0 isa0 at mainbus0 lpt0 at isa0 port 0x378-0x37b irq 7 com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo attimer0 at isa0 port 0x40-0x43: AT Timer wdc0 at isa0 port 0x1f0-0x1f7 irq 14 atabus0 at wdc0 channel 0 wdc1 at isa0 port 0x170-0x177 irq 15 atabus1 at wdc1 channel 0 vga0 at isa0 port 0x3b0-0x3df iomem 0xa0000-0xbffff wsdisplay0 at vga0 kbdmux 1: console (80x25, vt100 emulation), using wskbd0 wsmux1: connecting to wsdisplay0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker (CPU-intensive output) sysbeep0 at pcppi0 isapnp0 at isa0 port 0x279: ISA Plug 'n Play device support npx0 at isa0 port 0xf0-0xff npx0: reported by CPUID; using exception 16 fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2 attimer0: attached to pcppi0 isapnp0: no ISA Plug 'n Play devices found timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0 wd0 at atabus0 drive 0: wd0: drive supports 16-sector PIO transfers, LBA48 addressing wd0: 10240 MB, 20805 cyl, 16 head, 63 sec, 512 bytes/sect x 20971520 sectors atapibus0 at atabus1: 2 targets cd0 at atapibus0 drive 0: cdrom removable Kernelized RAIDframe activated pad0: outputs: 44100Hz, 16-bit, stereo audio0 at pad0: half duplex boot device: wd0 root on wd0a dumps on wd0b root file system type: ffs wsdisplay0: screen 1 added (80x25, vt100 emulation) wsdisplay0: screen 2 added (80x25, vt100 emulation) wsdisplay0: screen 3 added (80x25, vt100 emulation) wsdisplay0: screen 4 added (80x25, vt100 emulation) --------snip------------ 2. -no-acpi + mptable (notice wrong pcn0 irq, and `ioapic0 pin 12: can't share type 3 with 2' as a result): --------snip------------ Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 The NetBSD Foundation, Inc. All rights reserved. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. NetBSD 5.0 (GENERIC) #0: Sun Apr 26 18:50:08 UTC 2009 builds@b6.netbsd.org:/home/builds/ab/netbsd-5-0-RELEASE/i386/200904260229Z-obj/home/builds/ab/netbsd-5-0-RELEASE/src/sys/arch/i386/compile/GENERIC total memory = 1023 MB avail memory = 994 MB timecounter: Timecounters tick every 10.000 msec timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100 Generic PC mainbus0 (root) ACPI Error (tbxfroot-0308): A valid RSDP was not found [20080321] ACPI: unable to initialize ACPI tables: AE_NOT_FOUND mainbus0: Intel MP Specification (Version 1.4) (QEMUCPU 0.1 ) cpu0 at mainbus0 apid 0: Intel 686-class, id 0x633 mpbios: bus 0 is type ISA ioapic0 at mainbus0 apid 1: pa 0xfec00000, version 11, 24 pins pci0 at mainbus0 bus 0: configuration mode 1 pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok pchb0 at pci0 dev 0 function 0 pchb0: vendor 0x8086 product 0x1237 (rev. 0x02) pcib0 at pci0 dev 1 function 0 pcib0: vendor 0x8086 product 0x7000 (rev. 0x00) piixide0 at pci0 dev 1 function 1 piixide0: Intel 82371SB IDE Interface (PIIX3) (rev. 0x00) piixide0: bus-master DMA support present piixide0: primary channel wired to compatibility mode piixide0: primary channel interrupting at ioapic0 pin 14 atabus0 at piixide0 channel 0 piixide0: secondary channel wired to compatibility mode piixide0: secondary channel interrupting at ioapic0 pin 15 atabus1 at piixide0 channel 1 vga1 at pci0 dev 2 function 0: vendor 0x1013 product 0x00b8 (rev. 0x00) wsdisplay0 at vga1 kbdmux 1: console (80x25, vt100 emulation) wsmux1: connecting to wsdisplay0 drm at vga1 not configured pcn0 at pci0 dev 3 function 0: AMD PCnet-PCI Ethernet pcn0: Am79c970A PCnet-PCI II rev 0, Ethernet address 52:54:00:12:34:56 pcn0: interrupting at ioapic0 pin 12 pcn0: 10base5, 10base5-FDX, 10baseT, 10baseT-FDX, auto, auto-FDX auich0 at pci0 dev 4 function 0: i82801AA (ICH) AC-97 Audio auich0: interrupting at ioapic0 pin 9 auich0: ac97: SigmaTel STAC9700 codec; no 3D stereo auich0: ac97: ext id 809 vendor 0x1af4 product 0x1002 (RAM memory) at pci0 dev 5 function 0 not configured isa0 at pcib0 lpt0 at isa0 port 0x378-0x37b irq 7 com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo pckbc0 at isa0 port 0x60-0x64 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pms0 at pckbc0 (aux slot) intr_establish: pic ioapic0 pin 12: can't share type 3 with 2 pckbc0: unable to establish interrupt for aux slot wsmouse0 at pms0 mux 0 attimer0 at isa0 port 0x40-0x43: AT Timer pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker (CPU-intensive output) sysbeep0 at pcppi0 isapnp0 at isa0 port 0x279: ISA Plug 'n Play device support npx0 at isa0 port 0xf0-0xff npx0: reported by CPUID; using exception 16 fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2 attimer0: attached to pcppi0 isapnp0: no ISA Plug 'n Play devices found timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0 auich0: measured ac97 link rate at 45801 Hz, will use 48000 Hz audio0 at auich0: full duplex, mmap, independent wd0 at atabus0 drive 0: wd0: drive supports 16-sector PIO transfers, LBA48 addressing wd0: 10240 MB, 20805 cyl, 16 head, 63 sec, 512 bytes/sect x 20971520 sectors wd0: 32-bit data port wd0(piixide0:0:0): using PIO mode 0 atapibus0 at atabus1: 2 targets cd0 at atapibus0 drive 0: cdrom removable cd0: 32-bit data port cd0(piixide0:1:0): using PIO mode 3 Kernelized RAIDframe activated pad0: outputs: 44100Hz, 16-bit, stereo audio1 at pad0: half duplex boot device: wd0 root on wd0a dumps on wd0b root file system type: ffs wsdisplay0: screen 1 added (80x25, vt100 emulation) wsdisplay0: screen 2 added (80x25, vt100 emulation) wsdisplay0: screen 3 added (80x25, vt100 emulation) wsdisplay0: screen 4 added (80x25, vt100 emulation) --------snip------------ 3. -no-acpi + no mptable: (patched bios; only this combination works) --------snip------------ Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 The NetBSD Foundation, Inc. All rights reserved. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. NetBSD 5.0 (GENERIC) #0: Sun Apr 26 18:50:08 UTC 2009 builds@b6.netbsd.org:/home/builds/ab/netbsd-5-0-RELEASE/i386/200904260229Z-obj/home/builds/ab/netbsd-5-0-RELEASE/src/sys/arch/i386/compile/GENERIC total memory = 1023 MB avail memory = 994 MB timecounter: Timecounters tick every 10.000 msec timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100 Generic PC mainbus0 (root) ACPI Error (tbxfroot-0308): A valid RSDP was not found [20080321] ACPI: unable to initialize ACPI tables: AE_NOT_FOUND cpu0 at mainbus0: Intel 686-class, id 0x633 pci0 at mainbus0 bus 0: configuration mode 1 pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok pchb0 at pci0 dev 0 function 0 pchb0: vendor 0x8086 product 0x1237 (rev. 0x02) pcib0 at pci0 dev 1 function 0 pcib0: vendor 0x8086 product 0x7000 (rev. 0x00) piixide0 at pci0 dev 1 function 1 piixide0: Intel 82371SB IDE Interface (PIIX3) (rev. 0x00) piixide0: bus-master DMA support present piixide0: primary channel wired to compatibility mode piixide0: primary channel interrupting at irq 14 atabus0 at piixide0 channel 0 piixide0: secondary channel wired to compatibility mode piixide0: secondary channel interrupting at irq 15 atabus1 at piixide0 channel 1 vga1 at pci0 dev 2 function 0: vendor 0x1013 product 0x00b8 (rev. 0x00) wsdisplay0 at vga1 kbdmux 1: console (80x25, vt100 emulation) wsmux1: connecting to wsdisplay0 drm at vga1 not configured pcn0 at pci0 dev 3 function 0: AMD PCnet-PCI Ethernet pcn0: Am79c970A PCnet-PCI II rev 0, Ethernet address 52:54:00:12:34:56 pcn0: interrupting at irq 11 pcn0: 10base5, 10base5-FDX, 10baseT, 10baseT-FDX, auto, auto-FDX auich0 at pci0 dev 4 function 0: i82801AA (ICH) AC-97 Audio auich0: interrupting at irq 9 auich0: ac97: SigmaTel STAC9700 codec; no 3D stereo auich0: ac97: ext id 809 vendor 0x1af4 product 0x1002 (RAM memory) at pci0 dev 5 function 0 not configured isa0 at pcib0 lpt0 at isa0 port 0x378-0x37b irq 7 com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo pckbc0 at isa0 port 0x60-0x64 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pms0 at pckbc0 (aux slot) pckbc0: using irq 12 for aux slot wsmouse0 at pms0 mux 0 attimer0 at isa0 port 0x40-0x43: AT Timer pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker (CPU-intensive output) sysbeep0 at pcppi0 isapnp0 at isa0 port 0x279: ISA Plug 'n Play device support npx0 at isa0 port 0xf0-0xff npx0: reported by CPUID; using exception 16 fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2 attimer0: attached to pcppi0 isapnp0: no ISA Plug 'n Play devices found timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0 auich0: measured ac97 link rate at 46040 Hz, will use 48000 Hz audio0 at auich0: full duplex, mmap, independent wd0 at atabus0 drive 0: wd0: drive supports 16-sector PIO transfers, LBA48 addressing wd0: 10240 MB, 20805 cyl, 16 head, 63 sec, 512 bytes/sect x 20971520 sectors wd0: 32-bit data port wd0(piixide0:0:0): using PIO mode 0 atapibus0 at atabus1: 2 targets cd0 at atapibus0 drive 0: cdrom removable cd0: 32-bit data port cd0(piixide0:1:0): using PIO mode 3 Kernelized RAIDframe activated pad0: outputs: 44100Hz, 16-bit, stereo audio1 at pad0: half duplex boot device: wd0 root on wd0a dumps on wd0b root file system type: ffs wsdisplay0: screen 1 added (80x25, vt100 emulation) wsdisplay0: screen 2 added (80x25, vt100 emulation) wsdisplay0: screen 3 added (80x25, vt100 emulation) wsdisplay0: screen 4 added (80x25, vt100 emulation) --------snip------------ 4. and for completeness sake, acpi + no mptable: (patched bios; again no pci devices) --------snip------------ Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 The NetBSD Foundation, Inc. All rights reserved. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. NetBSD 5.0 (GENERIC) #0: Sun Apr 26 18:50:08 UTC 2009 builds@b6.netbsd.org:/home/builds/ab/netbsd-5-0-RELEASE/i386/200904260229Z-obj/home/builds/ab/netbsd-5-0-RELEASE/src/sys/arch/i386/compile/GENERIC total memory = 1023 MB avail memory = 994 MB timecounter: Timecounters tick every 10.000 msec timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100 Generic PC mainbus0 (root) cpu0 at mainbus0 apid 0: Intel 686-class, id 0x633 ioapic0 at mainbus0 apid 1: pa 0xfec00000, version 11, 24 pins acpi0 at mainbus0: Intel ACPICA 20080321 acpi0: X/RSDT: OemId , AslId acpi0: SCI interrupting at int 9 acpi0: fixed-feature power button present timecounter: Timecounter "ACPI-Safe" frequency 3579545 Hz quality 900 ACPI-Safe 24-bit timer pckbc1 at acpi0 (KBD, PNP0303): kbd port pckbc1: io 0x60,0x64 irq 1 pckbc2 at acpi0 (MOU, PNP0F13): aux port pckbc2: irq 12 FDC0 (PNP0700) at acpi0 not configured LPT (PNP0400) at acpi0 not configured COM1 (PNP0501) at acpi0 not configured apm0 at acpi0: Power Management spec V1.2 pckbd0 at pckbc1 (kbd slot) pckbc1: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard pms0 at pckbc1 (aux slot) pckbc1: using irq 12 for aux slot wsmouse0 at pms0 mux 0 isa0 at mainbus0 lpt0 at isa0 port 0x378-0x37b irq 7 com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo attimer0 at isa0 port 0x40-0x43: AT Timer wdc0 at isa0 port 0x1f0-0x1f7 irq 14 atabus0 at wdc0 channel 0 wdc1 at isa0 port 0x170-0x177 irq 15 atabus1 at wdc1 channel 0 vga0 at isa0 port 0x3b0-0x3df iomem 0xa0000-0xbffff wsdisplay0 at vga0 kbdmux 1: console (80x25, vt100 emulation), using wskbd0 wsmux1: connecting to wsdisplay0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker (CPU-intensive output) sysbeep0 at pcppi0 isapnp0 at isa0 port 0x279: ISA Plug 'n Play device support npx0 at isa0 port 0xf0-0xff npx0: reported by CPUID; using exception 16 fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2 attimer0: attached to pcppi0 isapnp0: no ISA Plug 'n Play devices found timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0 wd0 at atabus0 drive 0: wd0: drive supports 16-sector PIO transfers, LBA48 addressing wd0: 10240 MB, 20805 cyl, 16 head, 63 sec, 512 bytes/sect x 20971520 sectors atapibus0 at atabus1: 2 targets cd0 at atapibus0 drive 0: cdrom removable Kernelized RAIDframe activated pad0: outputs: 44100Hz, 16-bit, stereo audio0 at pad0: half duplex boot device: wd0 root on wd0a dumps on wd0b root file system type: ffs wsdisplay0: screen 1 added (80x25, vt100 emulation) wsdisplay0: screen 2 added (80x25, vt100 emulation) wsdisplay0: screen 3 added (80x25, vt100 emulation) wsdisplay0: screen 4 added (80x25, vt100 emulation) --------snip------------ From julian at elischer.org Sun May 31 04:51:05 2009 From: julian at elischer.org (Julian Elischer) Date: Sun May 31 04:51:13 2009 Subject: Skype-2.0 is here! In-Reply-To: <20090530090540.GC46541@onelab2.iet.unipi.it> References: <200804142217.17035.beech@FreeBSD.org> <20090530070025.GA2465@current.Sisis.de> <200905300955.34102.hselasky@freebsd.org> <20090530090540.GC46541@onelab2.iet.unipi.it> Message-ID: <4A220A00.4040007@elischer.org> Luigi Rizzo wrote: > On Sat, May 30, 2009 at 09:55:32AM +0200, Hans Petter Selasky wrote: >> On Saturday 30 May 2009, Matthias Apitz wrote: >>> El d?a Monday, April 14, 2008 a las 10:17:12PM -0800, Beech Rintoul >> escribi?: >>>> Finally, skype-devel has been updated to the new 2.0.0.68 version. >>>> This is the one that includes video and any input to get this (video) >>>> going is appreciated. Everything else seems to work as advertised. >>>> >>>> If you're going to update to this version, please read >>>> UPDATING-20080318. >>>> >>>> Enjoy, >>>> >>>> Beech >>> Hello Beech, >>> >>> I'm running on my laptop 8-CURRENT (of May 28), have the pwc.ko loaded >>> which gives me a device /dev/video0 and pwcview is showing my face; as >>> well I have installed skype-2.0.0.72,1 from the ports which works fine >>> but does not recognice the video device; what should I do or test to >>> bring this together? Thanks >>> >>> matthias >> Hi all, >> >> We need some common effort to get Video4Linux USB devices working on FreeBSD. >> First of all we need to push a video4linux library. >> >> -lvideodevx >> >> Methods: >> >> int videodevx_open(int unit); /* returns a handle, not neccesarily a >> file-handle */ >> int videodevx_read(int hdl, ptr, len); >> int videodevx_write(int hdl, ptr, len); >> int videodevx_ioctl(int hdl, cmd, arg); >> int videodevx_mmap(int hdl, void *addr, size_t len, int prot, int flags, int >> fd, off_t offset); >> int videodevx_getfd(int hdl); /* used for polling */ >> int videodevx_close(int hdl); >> >> Some work in progress is available from: >> >> svn --username anonsvn --password anonsvn \ >> checkout svn://svn.turbocat.net/i4b/trunk/usbcam >> >> Download "linux-2.6.29" to "ulinux/linux" >> >> cd ulinux >> >> make clean all >> >> NOTE: It's not linking yet. >> >> Second, we need a userland port for Video4Linux, which I am working on. So >> that the application directly receives the USB data and talks to the webcam >> through -lvideodevx and the new BSD licensed -lusb . >> >> Third we need to convince everyone to use videodevx when opening video >> devices. On linux videodevx will simply be a wrapper for >> open/close/ioctl/... . On FreeBSD videodevx will be a complete USB webcam >> driver library. >> >> Anyone that wants to join heads? > > Excellent summary which covers the situation for native apps. > > I wonder if the case is a bit different for skype and linux binaries > in general, as they run under linux emulation so perhaps the > it is the linuxulator that has to emulate the v4l(2?) calls, > and i have no idea if this needs to be done in the kernel or we > can deal with this in some libc wrapper ? there was a v4L2 implementation for FreeBSD that worked I checked some of it into P4 (v4l2 branch I think...) we actually have permsission to use the V4L2 and V4L include files directly (I have email from the authors) as they are not copyright at all but just reflect the ABI/API. > > cheers > luigi > _______________________________________________ > freebsd-multimedia@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-multimedia > To unsubscribe, send any mail to "freebsd-multimedia-unsubscribe@freebsd.org" From Alexander at Leidinger.net Sun May 31 09:07:09 2009 From: Alexander at Leidinger.net (Alexander Leidinger) Date: Sun May 31 09:07:19 2009 Subject: emulators/linux_base-fc4 - fails: mtree In-Reply-To: <20090529114800.E8CF08FC50@release.ixsystems.com> References: <20090529114800.E8CF08FC50@release.ixsystems.com> Message-ID: <20090531105110.0000391a@unknown> On Fri, 29 May 2009 04:48:00 -0700 (PDT) QAT@FreeBSD.org wrote: > The Restless Daemon identified a mtree error while trying to build: > linux_base-fc-4_14 maintained by freebsd-emulation@FreeBSD.org > Makefile ident: $FreeBSD: ports/emulators/linux_base-fc4/Makefile,v > 1.32 2009/01/21 16:17:46 bsam Exp $ THIS A BUILD WITH CUSTOM PREFIX > AND LOCALBASE, _standard_ env in rest. I'm not sure what to expect from a non-default PREFIX and LOCALBASE for a linux_base port... The PREFIX of such a port is for sure not equal to LOCALBASE like for other ports. And if there's a mtree error, then I'm not surprised, as LOCALBASE (= mtree base) is unequal to LINUXBASE (= PREFIX in the default case). Maybe the QA box needs to not take care about ports which install into LINUXBASE (or special case to non-default PREFIX=LINUXBASE). Bye, Alexander. From andreas.faerber at web.de Sun May 31 10:02:07 2009 From: andreas.faerber at web.de (=?ISO-8859-1?Q?Andreas_F=E4rber?=) Date: Sun May 31 10:02:14 2009 Subject: [Qemu-devel] Thanx for the kqemu patches; some notes about NetBSD/OpenBSD guests In-Reply-To: <20090530205152.GA7702@triton.kn-bremen.de> References: <20090530205152.GA7702@triton.kn-bremen.de> Message-ID: <38008E46-FD5F-4992-A824-E7F5CFBD5475@web.de> Hi J?rgen, Am 30.05.2009 um 22:51 schrieb Juergen Lock: > I just committed Jan's kqemu patch series to the FreeBSD kqemu port > (yes FreeBSD is another one of those `left behind' OSes where kvm > doesn't really work yet...) - and I also committed an old NetBSD/ > OpenBSD > guest kqemu patch, > http://lists.gnu.org/archive/html/qemu-devel/2007-11/msg00125.html > and then played with a NetBSD guest in qemu 0.10.5 a little, where I > found out a few things: > > 1. A few times I even got NetBSD 5.0/i386 running with -kernel-kqemu > now, > tho a few other times I also got guest processes segfaulting etc. > `Regualr' kqemu seems stable now tho. Thanks for the pointer. I've pushed it to a pick-up branch for now to facilitate testing. Did you test non-BSD guests, too? I noticed that Adrian has patches for OpenBSD host support in their ports CVS repository, as pointed out by Mikolaj. There appears to be some FreeBSD code in-tree though - so, is the above patch the only one you've queued, or do you have host patches as well that we could push "upstream"? Regards, Andreas From nox at jelal.kn-bremen.de Sun May 31 14:47:15 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Sun May 31 14:47:23 2009 Subject: [Qemu-devel] Thanx for the kqemu patches; some notes about NetBSD/OpenBSD guests In-Reply-To: <38008E46-FD5F-4992-A824-E7F5CFBD5475@web.de> References: <20090530205152.GA7702@triton.kn-bremen.de> <38008E46-FD5F-4992-A824-E7F5CFBD5475@web.de> Message-ID: <20090531144133.GA14007@triton.kn-bremen.de> On Sun, May 31, 2009 at 11:29:28AM +0200, Andreas F?rber wrote: > Hi J?rgen, Hi! > > Am 30.05.2009 um 22:51 schrieb Juergen Lock: > > > I just committed Jan's kqemu patch series to the FreeBSD kqemu port > > (yes FreeBSD is another one of those `left behind' OSes where kvm > > doesn't really work yet...) - and I also committed an old NetBSD/ > > OpenBSD > > guest kqemu patch, > > http://lists.gnu.org/archive/html/qemu-devel/2007-11/msg00125.html > > and then played with a NetBSD guest in qemu 0.10.5 a little, where I > > found out a few things: > > > > 1. A few times I even got NetBSD 5.0/i386 running with -kernel-kqemu > > now, > > tho a few other times I also got guest processes segfaulting etc. > > `Regualr' kqemu seems stable now tho. > > Thanks for the pointer. I've pushed it to a pick-up branch for now to > facilitate testing. Did you test non-BSD guests, too? > Oh yes I tested Linux too (and FreeBSD), and I tested a Windows 7 beta guest that I had installed a while ago more out of curiosity than anything else, and that one seemed to bluescreen a little less than it used to also... (it usually only bluescreen at boot and sometimes at shutdown, once it gets past the boot stage it keeps running, altho slowly. Oh and -kernel-kqemu seems to always make it bluescreen so only `regular' kqemu is useful for that guest.) Everything else I tested seemed to still run like it used to, the Linux guests even _appeared_ to run a little faster than they used to, possibly because of the added verr/verw and lar/lsl handling in Jan's patches... > I noticed that Adrian has patches for OpenBSD host support in their > ports CVS repository, as pointed out by Mikolaj. > There appears to be some FreeBSD code in-tree though - so, is the > above patch the only one you've queued, or do you have host patches as > well that we could push "upstream"? I have a few more, as you can see on cvsweb: http://www.freebsd.org/cgi/cvsweb.cgi/ports/emulators/kqemu-kmod-devel/files/ (patch-tssworkaround is only applied for FreeBSD < 7.1 since later versions no longer have the issue it works around; look in that patch's commitlogs if you want links to the gory details...) Cheers, Juergen From itetcu at FreeBSD.org Sun May 31 16:23:33 2009 From: itetcu at FreeBSD.org (Ion-Mihai Tetcu) Date: Sun May 31 16:23:38 2009 Subject: emulators/linux_base-fc4 - fails: mtree In-Reply-To: <20090531105110.0000391a@unknown> References: <20090529114800.E8CF08FC50@release.ixsystems.com> <20090531105110.0000391a@unknown> Message-ID: <20090531192400.0a78e56c@it.buh.tecnik93.com> On Sun, 31 May 2009 10:51:10 +0200 Alexander Leidinger wrote: > On Fri, 29 May 2009 04:48:00 -0700 (PDT) QAT@FreeBSD.org wrote: > > > > The Restless Daemon identified a mtree error while trying to build: > > linux_base-fc-4_14 maintained by freebsd-emulation@FreeBSD.org > > Makefile ident: $FreeBSD: ports/emulators/linux_base-fc4/Makefile,v > > 1.32 2009/01/21 16:17:46 bsam Exp $ THIS A BUILD WITH CUSTOM PREFIX > > AND LOCALBASE, _standard_ env in rest. > > I'm not sure what to expect from a non-default PREFIX and LOCALBASE > for a linux_base port... Me neither. > The PREFIX of such a port is for sure not equal to LOCALBASE like for > other ports. And if there's a mtree error, then I'm not surprised, as > LOCALBASE (= mtree base) is unequal to LINUXBASE (= PREFIX in the > default case). If USE_LINUX_PREFIX=yes PREFIX defaults to LINUXBASE (/compat/linux); and it makes sense not to install them since ports in case PREFIX=LOCALBASE since it has very good chances to overwrite files with the same name installed by native ports. So I think that if PREFIX=LOCALBASE all USE_LINUX_PREFIX ports should be marked broken. > Maybe the QA box needs to not take care about ports which install into > LINUXBASE (or special case to non-default PREFIX=LINUXBASE). I'm soooo reluctant to drop any port from checks ;-) I'll try to find some way, I don't want to exclude all ports that depend on linux_base from the run. -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> itetcu@FreeBSD.org, PGP Key ID 057E9F8B493A297B -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-emulation/attachments/20090531/405fe813/signature.pgp From mikolaj at kucharski.name Sun May 31 16:30:31 2009 From: mikolaj at kucharski.name (Mikolaj Kucharski) Date: Sun May 31 16:30:36 2009 Subject: [Qemu-devel] Thanx for the kqemu patches; some notes about NetBSD/OpenBSD guests In-Reply-To: <20090531144133.GA14007@triton.kn-bremen.de> References: <20090530205152.GA7702@triton.kn-bremen.de> <38008E46-FD5F-4992-A824-E7F5CFBD5475@web.de> <20090531144133.GA14007@triton.kn-bremen.de> Message-ID: <20090531155927.GF16517@x40.openbsd.home.lan> Is there anything new for OpenBSD which I could help test? Patches in OpenBSD CVS are for kqemu 1.3.0pre11, version 1.4.0pre1 doesn't work. References 1. http://www.openbsd.org/cgi-bin/cvsweb/ports/emulators/kqemu/ On Sun, May 31, 2009 at 04:41:33PM +0200, Juergen Lock wrote: > On Sun, May 31, 2009 at 11:29:28AM +0200, Andreas F?rber wrote: > > Hi J?rgen, > Hi! > > > > Am 30.05.2009 um 22:51 schrieb Juergen Lock: > > > > > I just committed Jan's kqemu patch series to the FreeBSD kqemu port > > > (yes FreeBSD is another one of those `left behind' OSes where kvm > > > doesn't really work yet...) - and I also committed an old NetBSD/ > > > OpenBSD > > > guest kqemu patch, > > > http://lists.gnu.org/archive/html/qemu-devel/2007-11/msg00125.html > > > and then played with a NetBSD guest in qemu 0.10.5 a little, where I > > > found out a few things: > > > > > > 1. A few times I even got NetBSD 5.0/i386 running with -kernel-kqemu > > > now, > > > tho a few other times I also got guest processes segfaulting etc. > > > `Regualr' kqemu seems stable now tho. > > > > Thanks for the pointer. I've pushed it to a pick-up branch for now to > > facilitate testing. Did you test non-BSD guests, too? > > > Oh yes I tested Linux too (and FreeBSD), and I tested a Windows 7 beta > guest that I had installed a while ago more out of curiosity than > anything else, and that one seemed to bluescreen a little less than > it used to also... (it usually only bluescreen at boot and sometimes > at shutdown, once it gets past the boot stage it keeps running, altho > slowly. Oh and -kernel-kqemu seems to always make it bluescreen so > only `regular' kqemu is useful for that guest.) > > Everything else I tested seemed to still run like it used to, the > Linux guests even _appeared_ to run a little faster than they used to, > possibly because of the added verr/verw and lar/lsl handling in Jan's > patches... > > > I noticed that Adrian has patches for OpenBSD host support in their > > ports CVS repository, as pointed out by Mikolaj. > > There appears to be some FreeBSD code in-tree though - so, is the > > above patch the only one you've queued, or do you have host patches as > > well that we could push "upstream"? > > I have a few more, as you can see on cvsweb: > http://www.freebsd.org/cgi/cvsweb.cgi/ports/emulators/kqemu-kmod-devel/files/ > (patch-tssworkaround is only applied for FreeBSD < 7.1 since later > versions no longer have the issue it works around; look in that patch's > commitlogs if you want links to the gory details...) > > Cheers, > Juergen -- best regards q# From nox at jelal.kn-bremen.de Sun May 31 17:14:01 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Sun May 31 17:14:08 2009 Subject: [Qemu-devel] Thanx for the kqemu patches; some notes about NetBSD/OpenBSD guests In-Reply-To: <20090531155927.GF16517@x40.openbsd.home.lan> References: <20090530205152.GA7702@triton.kn-bremen.de> <38008E46-FD5F-4992-A824-E7F5CFBD5475@web.de> <20090531144133.GA14007@triton.kn-bremen.de> <20090531155927.GF16517@x40.openbsd.home.lan> Message-ID: <20090531171038.GA67017@triton.kn-bremen.de> On Sun, May 31, 2009 at 04:59:27PM +0100, Mikolaj Kucharski wrote: > Is there anything new for OpenBSD which I could help test? Patches in > OpenBSD CVS are for kqemu 1.3.0pre11, version 1.4.0pre1 doesn't work. > > References > 1. http://www.openbsd.org/cgi-bin/cvsweb/ports/emulators/kqemu/ I don't know, but iirc the only thing I had to change when forward-porting the FreeBSD kqemu-kmod port from 1.3.0pre* to 1.4.0pre* (kqemu-kmod-devel) was adding code for the new KQEMU_SET_PHYS_MEM ioctl, as you can see here: http://www.freebsd.org/cgi/cvsweb.cgi/ports/emulators/kqemu-kmod-devel/files/patch-kqemu-freebsd.c?annotate=1.9 (the D_NEEDMINOR change is unrelated.) So I would at least suspect it should be as easy for OpenBSD? HTH, Juergen From ivoras at freebsd.org Sun May 31 20:27:54 2009 From: ivoras at freebsd.org (Ivan Voras) Date: Sun May 31 20:28:01 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 3 In-Reply-To: References: <20090522175956.GA33004@bsdcrew.de> Message-ID: Lapo Luchini wrote: > Running privileged using sudo (`sudo -E VirtualBox`) the console appears > correctly and is functional (I can create an HDD, a VirtualMachine), but > when trying to start a VM, it instantly goes in "Aborted" state. Did you try removing any "extra" virtual devices like sound, USB, COM, etc.? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 258 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-emulation/attachments/20090531/ef9f8f4d/signature.pgp From coco at executive-computing.de Sun May 31 21:55:53 2009 From: coco at executive-computing.de (Marco Steinbach) Date: Sun May 31 21:56:07 2009 Subject: [Call For Testing] VirtualBox for FreeBSD! take 4 In-Reply-To: <20090527134343.GB1104@bsdcrew.de> References: <20090527134343.GB1104@bsdcrew.de> Message-ID: <4A22F82C.1020902@executive-computing.de> Martin Wilke wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Howdy, [...] > > Happy Testing :-) [...] I've successfully migrated two Microsoft Windows 2003 Server Standard x64 Edition SP2 testing machines (running MS IIS, MS SQL Server and an inhouse application) from VMWare Server 1.0.9 on Wintel to virtualbox-2.2.2r1985 on a freshly installed FreeBSD/amd64 7.2-RELEASE with sources as of the day before yesterday. I'm using "Internal network" to connect both machines, and so far VirtualBox played nicely during my 24 hour testing run. As this is a lab machine, I'm in a position to fiddle with it at will; just tell me what you'd like to see tested, if anything. CPU is an AMD Athlon X2 Dual Core (4850e), 8GB RAM, mainboard is a MSI K9N Neo V3 and the graphics card is an ATI X550. I've attached the dmesg. Thank you for bringing VirtualBox to FreeBSD ! MfG CoCo -------------- next part -------------- Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.2-RELEASE #0: Sat May 30 22:08:10 CEST 2009 root@amd64.c0c0.intra:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Processor model unknown (2487.35-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x60fb2 Stepping = 2 Features=0x178bfbff Features2=0x2001 AMD Features=0xea500800 AMD Features2=0x11f TSC: P-state invariant Cores per package: 2 usable memory = 8576651264 (8179 MB) avail memory = 8275107840 (7891 MB) ACPI APIC Table: <112007 APIC1437> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: <112007 RSDT1437> on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of fec00000, fed40000 (3) failed acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, cff00000 (3) failed Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x2008-0x200b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.0 (no driver attached) isab0: port 0x2f00-0x2fff at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) pci0: at device 1.2 (no driver attached) ohci0: mem 0xfe8ff000-0xfe8fffff irq 21 at device 2.0 on pci0 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 10 ports with 10 removable, self powered ehci0: mem 0xfe8fec00-0xfe8fecff irq 22 at device 2.1 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb1: EHCI version 1.0 usb1: companion controller, 10 ports each: usb0 usb1: on ehci0 usb1: USB revision 2.0 uhub1: on usb1 uhub1: 10 ports with 10 removable, self powered uhub2: on uhub1 uhub2: single transaction translator uhub2: 4 ports with 4 removable, self powered ums0: on uhub2 ums0: 6 buttons and Z dir. ukbd0: on uhub2 kbd2 at ukbd0 pci0: at device 7.0 (no driver attached) pcib1: at device 8.0 on pci0 pci1: on pcib1 xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xcc00-0xcc7f mem 0xfe9ffc00-0xfe9ffc7f irq 16 at device 10.0 on pci1 miibus0: on xl0 xlphy0: <3Com internal media interface> PHY 24 on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:04:76:d1:dc:9a xl0: [ITHREAD] atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 9.0 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] atapci1: port 0xf80-0xf87,0xf00-0xf03,0xe80-0xe87,0xe00-0xe03,0xa800-0xa80f mem 0xfe8fc000-0xfe8fdfff irq 20 at device 10.0 on pci0 atapci1: [ITHREAD] ata2: on atapci1 ata2: [ITHREAD] ata3: on atapci1 ata3: [ITHREAD] pcib2: at device 11.0 on pci0 pci2: on pcib2 pcib3: at device 12.0 on pci0 pci3: on pcib3 re0: port 0xd800-0xd8ff mem 0xfeaff000-0xfeafffff irq 17 at device 0.0 on pci3 re0: Using 1 MSI messages re0: Chip rev. 0x38000000 re0: MAC rev. 0x00000000 miibus1: on re0 rgephy0: PHY 1 on miibus1 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: Ethernet address: 00:1d:92:84:e5:8b re0: [FILTER] pcib4: at device 13.0 on pci0 pci4: on pcib4 vgapci0: port 0xe000-0xe0ff mem 0xd0000000-0xdfffffff,0xfebf0000-0xfebfffff irq 18 at device 0.0 on pci4 vgapci1: mem 0xfebe0000-0xfebeffff at device 0.1 on pci4 pcib5: at device 14.0 on pci0 pci5: on pcib5 acpi_button0: on acpi0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FILTER] ppc0: port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 ppbus0: [ITHREAD] plip0: on ppbus0 plip0: WARNING: using obsoleted IFF_NEEDSGIANT flag lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ppc0: [GIANT-LOCKED] ppc0: [ITHREAD] cpu0: on acpi0 powernow0: on cpu0 device_attach: powernow0 attach returned 6 cpu1: on acpi0 powernow1: on cpu1 device_attach: powernow1 attach returned 6 orm0: at iomem 0xc0000-0xccfff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec acd0: DVDROM at ata0-slave UDMA100 ad4: 70911MB at ata2-master UDMA33 GEOM_LABEL: Label for provider ad4 is ufsid/480d2ea502086cea. ad6: 476940MB at ata3-master UDMA33 SMP: AP CPU #1 Launched! GEOM_LABEL: Label for provider ad4s1a is ufsid/49f799813ea0cd84. GEOM_LABEL: Label for provider ad4s1d is ufsid/49f79982611d27c6. GEOM_LABEL: Label for provider ad4s1e is ufsid/49f799812c579861. GEOM_LABEL: Label for provider ad4s1f is ufsid/49f79982e4f05972. GEOM_LABEL: Label for provider ad4s1g is ufsid/49f79981ae90b18d. GEOM_LABEL: Label for provider ad6s1a is ufsid/4a21796b43811700. GEOM_LABEL: Label for provider ad6s1d is ufsid/4a21798334fc09fb. GEOM_LABEL: Label for provider ad6s1e is ufsid/4a21796bcafd5289. GEOM_LABEL: Label for provider ad6s1f is ufsid/4a217981cae1eba9. GEOM_LABEL: Label for provider ad6s1g is ufsid/4a21796bf2f7b23f. Trying to mount root from ufs:/dev/ad6s1a GEOM_LABEL: Label ufsid/4a21796b43811700 removed. GEOM_LABEL: Label for provider ad6s1a is ufsid/4a21796b43811700. GEOM_LABEL: Label ufsid/4a21796bcafd5289 removed. GEOM_LABEL: Label for provider ad6s1e is ufsid/4a21796bcafd5289. GEOM_LABEL: Label ufsid/4a21796bf2f7b23f removed. GEOM_LABEL: Label for provider ad6s1g is ufsid/4a21796bf2f7b23f. GEOM_LABEL: Label ufsid/4a217981cae1eba9 removed. GEOM_LABEL: Label for provider ad6s1f is ufsid/4a217981cae1eba9. GEOM_LABEL: Label ufsid/4a21798334fc09fb removed. GEOM_LABEL: Label for provider ad6s1d is ufsid/4a21798334fc09fb. GEOM_LABEL: Label ufsid/4a21796b43811700 removed. GEOM_LABEL: Label ufsid/4a21796bcafd5289 removed. GEOM_LABEL: Label ufsid/4a21796bf2f7b23f removed. GEOM_LABEL: Label ufsid/4a217981cae1eba9 removed. GEOM_LABEL: Label ufsid/4a21798334fc09fb removed. re0: link state changed to UP GEOM_LABEL: Label ufsid/480d2ea502086cea removed. GEOM_LABEL: Label ufsid/49f79981ae90b18d removed. GEOM_LABEL: Label ufsid/49f79982e4f05972 removed. GEOM_LABEL: Label ufsid/49f799812c579861 removed. GEOM_LABEL: Label ufsid/49f79982611d27c6 removed. GEOM_LABEL: Label ufsid/49f799813ea0cd84 removed. GEOM_LABEL: Label for provider ad4 is ufsid/480d2ea502086cea. GEOM_LABEL: Label ufsid/480d2ea502086cea removed. GEOM_LABEL: Label for provider ad4 is ufsid/480d2ea502086cea. GEOM_LABEL: Label for provider ad4s1 is ufsid/4a22affdfa67615f. GEOM_LABEL: Label ufsid/480d2ea502086cea removed. GEOM_LABEL: Label ufsid/4a22affdfa67615f removed. GEOM_LABEL: Label for provider ad4 is ufsid/480d2ea502086cea. GEOM_LABEL: Label for provider ad4s1 is ufsid/4a22affdfa67615f. GEOM_LABEL: Label ufsid/480d2ea502086cea removed. GEOM_LABEL: Label ufsid/4a22affdfa67615f removed. drm0: on vgapci0 vgapci0: child drm0 requested pci_enable_busmaster info: [drm] Initialized radeon 1.29.0 20080528 info: [drm] Setting GART location based on new memory map info: [drm] Loading R300 Microcode info: [drm] Num pipes: 1 info: [drm] writeback test succeeded in 1 usecs drm0: [ITHREAD]