From owner-freebsd-emulation Sun Jan 28 20: 1:22 2001 Delivered-To: freebsd-emulation@freebsd.org Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246]) by hub.freebsd.org (Postfix) with ESMTP id BB84937B400 for ; Sun, 28 Jan 2001 20:01:05 -0800 (PST) Received: from delta.rc.ny.us (nyf-ny4-25.ix.netcom.com [198.211.16.217]) by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id XAA24732 for ; Sun, 28 Jan 2001 23:01:03 -0500 (EST) Received: (from vsilyaev@localhost) by delta.rc.ny.us (8.11.1/8.9.3) id f0T411R07383 for emulation@freebsd.org; Sun, 28 Jan 2001 23:01:01 -0500 (EST) (envelope-from vsilyaev) Date: Sun, 28 Jan 2001 23:01:01 -0500 From: Vladimir Silyaev To: emulation@freebsd.org Subject: New vmware experimental port Message-ID: <20010128230100.A5421@delta.rc.ny.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, New vmware port available at http://www.mindspring.com/~vsilyaev/vmware/vmware.tar.gz Major improvements: - support for multiple vmware sessions - fully functional bridge and host only networking, you have just select proper type from vmware network configuration menu To get it properly working with networking you have to apply patch from 'files/tap.diff'. Feedback would be very welcome. -- Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Jan 29 9:48: 3 2001 Delivered-To: freebsd-emulation@freebsd.org Received: from mail.utcorp.net (x-montana.utcorp.com [146.145.135.26]) by hub.freebsd.org (Postfix) with ESMTP id 5A71637B699 for ; Mon, 29 Jan 2001 09:47:46 -0800 (PST) Received: from [146.145.135.17] (helo=utcorp.com) by mail.utcorp.net with esmtp (Exim 3.03 #1) id 14NIJP-000JLX-00 for freebsd-emulation@FreeBSD.ORG; Mon, 29 Jan 2001 12:41:55 -0500 Message-ID: <3A75B346.CF1B867E@utcorp.com> Date: Mon, 29 Jan 2001 13:15:34 -0500 From: Kurt Seel X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.8-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-emulation@FreeBSD.ORG Subject: vmware video driver install problem Content-Type: multipart/alternative; boundary="------------3FCABDE7E055B59F7AD0CDA9" Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --------------3FCABDE7E055B59F7AD0CDA9 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I can't get the Vmware video drivers to install using the settings -> tools install menu options. I says that the a:\ drive is inaccessable (windows message). I _hate_ 640x480x16 ... -- In theory, there is no difference between theory and practice. In practice, however, there is. - Albert Einstein --------------3FCABDE7E055B59F7AD0CDA9 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit  
 I can't get the Vmware video drivers to install using the settings
-> tools install menu options. I says that the a:\ drive is inaccessable
(windows message).
 I _hate_ 640x480x16 ... 
-- 
 In theory, there is no difference between theory
and practice. In practice, however, there is.
 - Albert Einstein
  --------------3FCABDE7E055B59F7AD0CDA9-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Jan 29 11:15:21 2001 Delivered-To: freebsd-emulation@freebsd.org Received: from fsmail.net (mail.fsmail.net [216.200.119.37]) by hub.freebsd.org (Postfix) with SMTP id 8262837B698 for ; Mon, 29 Jan 2001 11:14:55 -0800 (PST) Received: (qmail 3216 invoked by uid 1120); 29 Jan 2001 17:36:45 -0000 Message-ID: <20010129173644.3215.qmail@fsmail.net> From: Ericka Rivera Subject: alianza estrategica To: ek5_76@yahoo.com Cc: Date: Mon, 29 Jan 2001 17:36:44 +0000 (GMT+00:00) MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hola! Recientemente visite su sitio en internet y creo que talvez ud. se encuentre interesado en formar una alianza estrategica. Nuestra compaņia es dueņa y opera varios casinos en linea con todas las licencias. Tenemos mas de 30,000 clientes y 8,500 sitios asociados. La industria de juegos en linea es la mas explosiva en la red, con cerca de $10 billones proyectados para el para el ano 2002. Nos gustaria ofrecerle la siguiente propuesta: Quest Global Entretenimiento provee: * Casino / Casa de Apuestas, diseņo completo (por ejemplo, vaya a www.getyourcasino.com/spanish) *Todo los programas del juego, servicio al cliente, procesamiento de tarjetas de credito, y apollo logistico *Mas de 50% de ganancias netas del casino, (hechas en tiempo real). *Los Cheques de las ganancias seran enviados por correo cada viernes, llueva o truene!. Ud. nos dara: *Promocion del Casino, por medio de banners, correo electronico o ubicacion en los buscadores. Sin tomar ningun riesgo, ud llevara trafico a su casino personal en Internet, e inmediatamente aumentara los ingresos brutos de su compania. Lo invito a observar nuestro sitio corporativo en la siguiente direccion: http://www.getyourcasino.com/spanish Esperamos llegar a saber de ud. muy pronto! Cordialmente Ericka Rivera Directora Latinoamerica socio@getyourcasino.com _______________________________________________________________________ FSmail - Get your free web-based email from Freeserve: www.fsmail.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Jan 29 21:35:55 2001 Delivered-To: freebsd-emulation@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id 229EC37B698 for ; Mon, 29 Jan 2001 21:35:36 -0800 (PST) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id A7E0D815; Mon, 29 Jan 2001 21:35:35 -0800 (PST) Received: from cup.hp.com (p1000181.nsr.hp.com [15.109.0.181]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id VAA03962; Mon, 29 Jan 2001 21:35:33 -0800 (PST) Message-ID: <3A7652A0.BF5F7DB8@cup.hp.com> Date: Mon, 29 Jan 2001 21:35:28 -0800 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Martin Blapp Cc: freebsd-emulation@FreeBSD.ORG Subject: Re: [PATCH] Staroffice Network Problem solved References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Martin Blapp wrote: > > Can you review this and commit it to STABLE and CURRENT ? This > unbreaks the staroffice network code. :-)))) > > --- linux_socket.c Sat Jan 20 20:54:47 2001 > +++ linux_socket.c.new Sun Jan 21 02:59:44 2001 > @@ -454,7 +454,7 @@ > return (error); > > p->p_retval[0] = stat; > - return (0); > + return (EISCONN); > } > } This code is executes when the native connect(2) returns EISCONN. Can you test the following patch. It removes the special handling when connect(2) returns EISCONN. Index: linux_socket.c =================================================================== RCS file: /home/ncvs/src/sys/compat/linux/linux_socket.c,v retrieving revision 1.25 diff -u -r1.25 linux_socket.c --- linux_socket.c 2000/12/19 00:24:25 1.25 +++ linux_socket.c 2001/01/30 05:30:56 @@ -404,61 +404,7 @@ bsd_args.s = linux_args.s; bsd_args.name = (caddr_t)linux_args.name; bsd_args.namelen = linux_args.namelen; - error = connect(p, &bsd_args); - if (error == EISCONN) { - /* - * Linux doesn't return EISCONN the first time it occurs, - * when on a non-blocking socket. Instead it returns the - * error getsockopt(SOL_SOCKET, SO_ERROR) would return on BSD. - */ - struct fcntl_args /* { - int fd; - int cmd; - int arg; - } */ bsd_fcntl_args; - struct getsockopt_args /* { - int s; - int level; - int name; - caddr_t val; - int *avalsize; - } */ bsd_getsockopt_args; - void *status, *statusl; - int stat, statl = sizeof stat; - caddr_t sg; - - /* Check for non-blocking */ - bsd_fcntl_args.fd = linux_args.s; - bsd_fcntl_args.cmd = F_GETFL; - bsd_fcntl_args.arg = 0; - error = fcntl(p, &bsd_fcntl_args); - if (error == 0 && (p->p_retval[0] & O_NONBLOCK)) { - sg = stackgap_init(); - status = stackgap_alloc(&sg, sizeof stat); - statusl = stackgap_alloc(&sg, sizeof statusl); - - if ((error = copyout(&statl, statusl, sizeof statl))) - return (error); - - bsd_getsockopt_args.s = linux_args.s; - bsd_getsockopt_args.level = SOL_SOCKET; - bsd_getsockopt_args.name = SO_ERROR; - bsd_getsockopt_args.val = status; - bsd_getsockopt_args.avalsize = statusl; - - error = getsockopt(p, &bsd_getsockopt_args); - if (error) - return (error); - - if ((error = copyin(status, &stat, sizeof stat))) - return (error); - - p->p_retval[0] = stat; - return (0); - } - } - - return (error); + return (connect(p, &bsd_args)); } #ifndef __alpha__ -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Jan 30 23:32:26 2001 Delivered-To: freebsd-emulation@freebsd.org Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by hub.freebsd.org (Postfix) with ESMTP id 8492937B6C4 for ; Tue, 30 Jan 2001 23:32:09 -0800 (PST) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.9.3/8.9.3) id IAA64969 for emulation@freebsd.org; Wed, 31 Jan 2001 08:32:08 +0100 (CET) (envelope-from kuku) Date: Wed, 31 Jan 2001 08:32:08 +0100 From: Christoph Kukulies To: emulation@freebsd.org Subject: Realplay - linux Message-ID: <20010131083208.B64860@gil.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This was in my security logs last night: cmd realplay pid 57558 tried to use non-present sched_yield Is this a matter of linux emulation? -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Wed Jan 31 12:11:21 2001 Delivered-To: freebsd-emulation@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id DEA1137B503 for ; Wed, 31 Jan 2001 12:11:03 -0800 (PST) Received: (from dan@localhost) by dan.emsphone.com (8.11.1/8.11.1) id f0VKAqk29607; Wed, 31 Jan 2001 14:10:52 -0600 (CST) (envelope-from dan) Date: Wed, 31 Jan 2001 14:10:51 -0600 From: Dan Nelson To: Christoph Kukulies Cc: emulation@FreeBSD.ORG Subject: Re: Realplay - linux Message-ID: <20010131141051.A23635@dan.emsphone.com> References: <20010131083208.B64860@gil.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.14i In-Reply-To: <20010131083208.B64860@gil.physik.rwth-aachen.de>; from "Christoph Kukulies" on Wed Jan 31 08:32:08 GMT 2001 X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In the last episode (Jan 31), Christoph Kukulies said: > This was in my security logs last night: > > cmd realplay pid 57558 tried to use non-present sched_yield > > Is this a matter of linux emulation? I think sched_yield is part of the Posix realtime extensions. Try adding options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L to your kernel and recompiling. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Wed Jan 31 18:43:37 2001 Delivered-To: freebsd-emulation@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 829EB37B69F for ; Wed, 31 Jan 2001 18:43:19 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id VAA05196; Wed, 31 Jan 2001 21:43:14 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id f112hE438248; Wed, 31 Jan 2001 21:43:14 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 31 Jan 2001 21:43:13 -0500 (EST) To: freebsd-emulation@freebsd.org Cc: becker@cs.duke.edu Subject: experiences running vmware w/freebsd 5.0-current as guest X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14968.51758.59870.15884@grasshopper.cs.duke.edu> Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just a heads up so this makes it into the archives: When running FreeBSD-current as a guest in vmware (VMX86: version='unreleased' build='$Name: build-570 $' option=Release2.0.1) I ran into 2 problems: a) VMware crashes when the pcn driver probes the AMD PCInet card. This is indicated by a "NOT_IMPLEMENTED F(562):1654" message shortly after FreeBSD probes the PCI bus, right after message pci0: at 15.0 (no driver attached). Switching to a kernel without the pcn driver driver works around this. The lnc driver mostly still works, but is unable to correctly determine the card's mac address. This doesn't seem to matter for running host-only networking. b) 5.0-current is _slow_. Mounting root takes upwards of 30 seconds on a 400MHz mobile PII. Going multi-user takes over 10 minutes. This is compared to near-native perf. with a 4.2-RELEASE kernel. Taking the i386 version of the atomic_cmpset_int() inline in sys/i386/include/atomic.h is an effective workaround for this. Note that it is apparently not sufficient to build an I386_CPU kernel - I had trouble booting this. Taking just the i386 version of atomic_cmpset_int() seems to work just fine, though. My theory is that the cmpxchgl instruction causes some sort of trap to software emulation, but I have not verified it. Hope this helps somebody. Cheers, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Thu Feb 1 2:14: 0 2001 Delivered-To: freebsd-emulation@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 6F8F037B503 for ; Thu, 1 Feb 2001 02:13:42 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id LAA29803; Thu, 1 Feb 2001 11:13:34 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Dan Nelson Cc: Christoph Kukulies , emulation@FreeBSD.ORG Subject: Re: Realplay - linux References: <20010131083208.B64860@gil.physik.rwth-aachen.de> <20010131141051.A23635@dan.emsphone.com> From: Dag-Erling Smorgrav Date: 01 Feb 2001 11:13:33 +0100 In-Reply-To: Dan Nelson's message of "Wed, 31 Jan 2001 14:10:51 -0600" Message-ID: Lines: 10 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dan Nelson writes: > options P1003_1B > options _KPOSIX_PRIORITY_SCHEDULING > options _KPOSIX_VERSION=199309L Does anybody know of a reason why this shouldn't be standard? DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Thu Feb 1 9:13:46 2001 Delivered-To: freebsd-emulation@freebsd.org Received: from gw.errno.com (node-d1d4bd7a.powerinter.net [209.212.189.122]) by hub.freebsd.org (Postfix) with ESMTP id C086137B6A2 for ; Thu, 1 Feb 2001 09:13:27 -0800 (PST) Received: from melange (melange.errno.com [209.212.166.36]) by gw.errno.com (8.9.0/8.9.0) with SMTP id JAA14083; Thu, 1 Feb 2001 09:13:25 -0800 (PST) Message-ID: <06d701c08c72$49a9d080$24a6d4d1@melange> From: "Sam Leffler" To: "Andrew Gallatin" , Cc: References: <14968.51758.59870.15884@grasshopper.cs.duke.edu> Subject: Re: experiences running vmware w/freebsd 5.0-current as guest Date: Thu, 1 Feb 2001 09:13:25 -0800 Organization: Errno Consulting MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.3018.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ----- Original Message ----- From: "Andrew Gallatin" To: Cc: Sent: Wednesday, January 31, 2001 6:43 PM Subject: experiences running vmware w/freebsd 5.0-current as guest > > Just a heads up so this makes it into the archives: > > When running FreeBSD-current as a guest in vmware (VMX86: > version='unreleased' build='$Name: build-570 $' option=Release2.0.1) I > ran into 2 problems: > > a) VMware crashes when the pcn driver probes the AMD PCInet card. > This is indicated by a "NOT_IMPLEMENTED F(562):1654" message > shortly after FreeBSD probes the PCI bus, right after > message pci0: at 15.0 (no driver attached). > This assertion is caused by the pcn driver doing 32-bit ins and outs to 16-bit registers (the upper 16 bits are reserved). > Switching to a kernel without the pcn driver driver works around this. > The lnc driver mostly still works, but is unable to correctly > determine the card's mac address. This doesn't seem to matter for > running host-only networking. > > b) 5.0-current is _slow_. Mounting root takes upwards of 30 seconds > on a 400MHz mobile PII. Going multi-user takes over 10 minutes. > This is compared to near-native perf. with a 4.2-RELEASE kernel. > > Taking the i386 version of the atomic_cmpset_int() inline in > sys/i386/include/atomic.h is an effective workaround for this. Note > that it is apparently not sufficient to build an I386_CPU kernel - I > had trouble booting this. Taking just the i386 version of > atomic_cmpset_int() seems to work just fine, though. > > My theory is that the cmpxchgl instruction causes some sort of trap to > software emulation, but I have not verified it. > It could be that the use of the cmpxchgl instruction is finding a slow path through the runtime; if you have the code fragment handy I can forward it to the appropriate VMware folks. Sam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Thu Feb 1 10:49: 5 2001 Delivered-To: freebsd-emulation@freebsd.org Received: from syncopation-01.iinet.net.au (syncopation-01.iinet.net.au [203.59.24.37]) by hub.freebsd.org (Postfix) with SMTP id 1E9B137B4EC for ; Thu, 1 Feb 2001 10:48:46 -0800 (PST) Received: (qmail 12162 invoked by uid 666); 1 Feb 2001 18:56:03 -0000 Received: from reggae-03-33.nv.iinet.net.au (HELO elischer.org) (203.59.78.33) by mail.m.iinet.net.au with SMTP; 1 Feb 2001 18:56:03 -0000 Message-ID: <3A79AF6F.49EB8685@elischer.org> Date: Thu, 01 Feb 2001 10:48:15 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Sam Leffler Cc: Andrew Gallatin , freebsd-emulation@FreeBSD.ORG, becker@cs.duke.edu Subject: Re: experiences running vmware w/freebsd 5.0-current as guest References: <14968.51758.59870.15884@grasshopper.cs.duke.edu> <06d701c08c72$49a9d080$24a6d4d1@melange> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sam Leffler wrote: > > > When running FreeBSD-current as a guest in vmware (VMX86: > > version='unreleased' build='$Name: build-570 $' option=Release2.0.1) I > > ran into 2 problems: > > > > a) VMware crashes when the pcn driver probes the AMD PCInet card. > > This is indicated by a "NOT_IMPLEMENTED F(562):1654" message > > shortly after FreeBSD probes the PCI bus, right after > > message pci0: at 15.0 (no driver attached). I used to get something very similar to this on vmware 1.0.2 but it seems to work fine now. I use the lnc driver and it works fine (except for the wierd MAC address, but who cares about that.. I do all my kernel debugging with a vmware machine with its com2 port (sio1) redirected to gdb so I can single step it etc.. When running I have /usr/src NFS mounted from the host so "cd /usr/src/sys/compile/MUMBLE; make install" installs the latest compiled kernel and then I reboot and proceed to debug.. works great but a bit slow.. I haven't seen the 30 secs to mount root, but I'm using a virtual disk (not soft updates ether) .. > > > > This assertion is caused by the pcn driver doing 32-bit ins and outs to > 16-bit registers (the upper 16 bits are reserved). > > > Switching to a kernel without the pcn driver driver works around this. > > The lnc driver mostly still works, but is unable to correctly > > determine the card's mac address. This doesn't seem to matter for > > running host-only networking. > > > > b) 5.0-current is _slow_. Mounting root takes upwards of 30 seconds > > on a 400MHz mobile PII. Going multi-user takes over 10 minutes. > > This is compared to near-native perf. with a 4.2-RELEASE kernel. As I said.. I reboot to multiuser in about 50 seconds from poweron using a PIII-500. > > > > Taking the i386 version of the atomic_cmpset_int() inline in > > sys/i386/include/atomic.h is an effective workaround for this. Note > > that it is apparently not sufficient to build an I386_CPU kernel - I > > had trouble booting this. Taking just the i386 version of > > atomic_cmpset_int() seems to work just fine, though. hmm maybe I'm a couple of days out of date, but I'm sure I've rebooted since then and not seen it.. maybe it's because I'm using the older vmware? > > > > My theory is that the cmpxchgl instruction causes some sort of trap to > > software emulation, but I have not verified it. > > > > It could be that the use of the cmpxchgl instruction is finding a slow path > through the runtime; if you have the code fragment handy I can forward it to > the appropriate VMware folks. > > Sam > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-emulation" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Thu Feb 1 10:59:28 2001 Delivered-To: freebsd-emulation@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 7383337B65D for ; Thu, 1 Feb 2001 10:59:06 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id NAA20277; Thu, 1 Feb 2001 13:59:06 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id f11Ix5W40021; Thu, 1 Feb 2001 13:59:05 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 1 Feb 2001 13:59:05 -0500 (EST) To: "Sam Leffler" Cc: Subject: Re: experiences running vmware w/freebsd 5.0-current as guest In-Reply-To: <06d701c08c72$49a9d080$24a6d4d1@melange> References: <14968.51758.59870.15884@grasshopper.cs.duke.edu> <06d701c08c72$49a9d080$24a6d4d1@melange> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14969.39659.18817.437539@grasshopper.cs.duke.edu> Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sam Leffler writes: <...> > > a) VMware crashes when the pcn driver probes the AMD PCInet card. > > This is indicated by a "NOT_IMPLEMENTED F(562):1654" message > > shortly after FreeBSD probes the PCI bus, right after > > message pci0: at 15.0 (no driver attached). > > > > This assertion is caused by the pcn driver doing 32-bit ins and outs to > 16-bit registers (the upper 16 bits are reserved). OK. Cool. So this should be fixable. I don't know anything about the PCInet's registers, though. Perhaps we should get the driver's author involved. <...> > > It could be that the use of the cmpxchgl instruction is finding a slow path > through the runtime; if you have the code fragment handy I can forward it to > the appropriate VMware folks. > The I386_CPU path is the "fast path" under vmware, the #else clause is the slow path under vmware: #if defined(I386_CPU) static __inline int atomic_cmpset_int(volatile u_int *dst, u_int exp, u_int src) { int res = exp; __asm __volatile( " pushfl ; " " cli ; " " cmpl %1,%3 ; " " jne 1f ; " " movl %2,%3 ; " "1: " " sete %%al; " " movzbl %%al,%0 ; " " popfl ; " "# atomic_cmpset_int" : "=a" (res) /* 0 (result) */ : "0" (exp), /* 1 */ "r" (src), /* 2 */ "m" (*(dst)) /* 3 */ : "memory"); return (res); } #else /* defined(I386_CPU) */ static __inline int atomic_cmpset_int(volatile u_int *dst, u_int exp, u_int src) { int res = exp; __asm __volatile ( " " MPLOCKED " " " cmpxchgl %2,%3 ; " " setz %%al ; " " movzbl %%al,%0 ; " "1: " "# atomic_cmpset_int" : "=a" (res) /* 0 (result) */ : "0" (exp), /* 1 */ "r" (src), /* 2 */ "m" (*(dst)) /* 3 */ : "memory"); return (res); } #endif /* defined(I386_CPU) */ Thanks! Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Thu Feb 1 13:40:10 2001 Delivered-To: freebsd-emulation@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 8FB3637B491; Thu, 1 Feb 2001 13:39:47 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.1/8.11.1) with SMTP id f11Ldkh20304; Thu, 1 Feb 2001 16:39:46 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Thu, 1 Feb 2001 16:39:45 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: mdillon@FreeBSD.org Cc: emulation@FreeBSD.org Subject: long hangs running vmware -- vm system interactions? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matt, I don't know if you've ever spent much time running vmware, but I've noticed that it appears to bring out the worst in FreeBSD, especially when it comes to mapped memory regions. I have two scenarios in mind, and this is using the vmware2 port, if you want to give it a try. The first is during the initial startup of a virtual machine with a guest operating system. Their emulated BIOS spends some time touching each page of memory during the boot process, which apparently involves creating a huge file on /var/tmp (or where-ever), mmap'ing it, and then touching the pages. I'm not sure what the sequence of events for creating the file is, but one suspects they seek to create a sparse file, and then the touching of pages causes the pages/blocks to be allocated sequentially. During this procedure, other processes that attempt to touch the disk generally hang, presumably waiting on a lock, or just the opportunity to perform disk I/O. It seems like the long hanging should be avoidable... The second scenario occurs when vmware runs out of disk space for its paging file during the previously described procedure. I lost control of the system for around ten minutes, and observed a lot of the following messages appearing in dmesg: ... pid 5 (syncer), uid 0 on /var: file system full vnode_pager_putpages: I/O error 28 vnode_pager_putpages: residual I/O 65536 at 6942 pid 5 (syncer), uid 0 on /var: file system full vnode_pager_putpages: I/O error 28 vnode_pager_putpages: residual I/O 65536 at 6943 pid 5 (syncer), uid 0 on /var: file system full vnode_pager_putpages: I/O error 28 vnode_pager_putpages: residual I/O 65536 at 6944 pid 5 (syncer), uid 0 on /var: file system full vnode_pager_putpages: I/O error 28 vnode_pager_putpages: residual I/O 65536 at 6945 pid 5 (syncer), uid 0 on /var: file system full vnode_pager_putpages: I/O error 28 ... Now, I understand that fundamentally life sucks when you over-commit and find out the hard way that you don't have the resources, but the fact that fairly regularly used applications have this problem due to poor disk layout and use strategies suggests we could be handling it better. Interestingly, VMware even notices it has run out of room, but that doesn't seem to save you from suffering through this anyway. I did recover control of the system eventually, but it took a long time, and at the very least, it would be nice if the recovery time was faster. Some of the problem may have been the printf'ing, which in turn spewed log messages to syslogd, which then wanted to write to /var, feeding back. In any case, if you haven't had the opportunity to explore how VMware stresses FreeBSD, you might give it a spin sometime... :-) Thanks, Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Thu Feb 1 19: 7:53 2001 Delivered-To: freebsd-emulation@freebsd.org Received: from blount.mail.mindspring.net (blount.mail.mindspring.net [207.69.200.226]) by hub.freebsd.org (Postfix) with ESMTP id 37D1A37B65D; Thu, 1 Feb 2001 19:07:34 -0800 (PST) Received: from delta.rc.ny.us (nyf-ny3-29.ix.netcom.com [198.211.16.157]) by blount.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id WAA14652; Thu, 1 Feb 2001 22:07:31 -0500 (EST) Received: (from vsilyaev@localhost) by delta.rc.ny.us (8.11.1/8.9.3) id f1237Tn00673; Thu, 1 Feb 2001 22:07:29 -0500 (EST) (envelope-from vsilyaev) Date: Thu, 1 Feb 2001 22:07:28 -0500 From: Vladimir Silyaev To: Robert Watson Cc: emulation@FreeBSD.org, mdillon@FreeBSD.org Subject: Re: long hangs running vmware -- vm system interactions? Message-ID: <20010201220728.A653@delta.rc.ny.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >/var/tmp (or where-ever), mmap'ing it, and then touching the pages. I'm >not sure what the sequence of events for creating the file is, but one >suspects they seek to create a sparse file, and then the touching of pages >causes the pages/blocks to be allocated sequentially. It just create file, mmaped it, unlink it and seek at the end. The big difference with comparsion with normal operation, that vmware mmaped pages are not just touching, but also being 'wired'. Just my five cents ;) -- Vladimir P.S. You shouldn't run/connect rtc if you are not really need it. It just eating CPU as a dog. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Fri Feb 2 7:59:15 2001 Delivered-To: freebsd-emulation@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id E3EFD37B699; Fri, 2 Feb 2001 07:58:57 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.1/8.11.1) with SMTP id f12Fwuh30285; Fri, 2 Feb 2001 10:58:57 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Fri, 2 Feb 2001 10:58:56 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: dillon@FreeBSD.org Cc: emulation@FreeBSD.org, sos@FreeBSD.org Subject: Re: long hangs running vmware -- vm system interactions? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've also noticed that I get messages like these during the startup of windows under VMware (possibly a property of the wiring behavior previously described): Feb 2 10:58:21 curry /boot/kernel/kernel: swap_pager: indefinite wait buffer: device: ad0s1b, blkno: 288, size: 4096 Feb 2 10:58:22 curry /boot/kernel/kernel: swap_pager: indefinite wait buffer: device: ad0s1b, blkno: 376, size: 4096 Feb 2 10:58:22 curry /boot/kernel/kernel: swap_pager: indefinite wait buffer: device: ad0s1b, blkno: 1536, size: 16384 Normally I'd think this was an impending IDE drive failure, only a number of others have reported seeing this behavior under -CURRENT also. Don't know if it's a product of VMWare, the VM system, or the ATA driver... Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Fri Feb 2 10: 7:16 2001 Delivered-To: freebsd-emulation@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 74B6837B503; Fri, 2 Feb 2001 10:06:59 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f12I6x556847; Fri, 2 Feb 2001 10:06:59 -0800 (PST) (envelope-from dillon) Date: Fri, 2 Feb 2001 10:06:59 -0800 (PST) From: Matt Dillon Message-Id: <200102021806.f12I6x556847@earth.backplane.com> To: Robert Watson Cc: emulation@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: long hangs running vmware -- vm system interactions? References: Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org :I've also noticed that I get messages like these during the startup of :windows under VMware (possibly a property of the wiring behavior :previously described): : :Feb 2 10:58:21 curry /boot/kernel/kernel: swap_pager: indefinite wait buffer: device: ad0s1b, blkno: 288, size: 4096 :Feb 2 10:58:22 curry /boot/kernel/kernel: swap_pager: indefinite wait buffer: device: ad0s1b, blkno: 376, size: 4096 :Feb 2 10:58:22 curry /boot/kernel/kernel: swap_pager: indefinite wait buffer: device: ad0s1b, blkno: 1536, size: 16384 : :Normally I'd think this was an impending IDE drive failure, only a number :of others have reported seeing this behavior under -CURRENT also. Don't :know if it's a product of VMWare, the VM system, or the ATA driver... : :Robert N M Watson FreeBSD Core Team, TrustedBSD Project This message occurs when the system is trying to swap pages in and I/O queued to the swap device (aka hard drive) does not complete after 20 seconds. The swapper will still wait until the I/O completes. So something is tying up your IDE bus for 20+ seconds. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Sat Feb 3 18:41:16 2001 Delivered-To: freebsd-emulation@freebsd.org Received: from hj.egroups.com (hj.egroups.com [208.50.99.212]) by hub.freebsd.org (Postfix) with SMTP id 13F6237B6A0 for ; Sat, 3 Feb 2001 18:40:59 -0800 (PST) X-eGroups-Return: supermanlinux@yahoo.com Received: from [10.1.2.48] by hj.egroups.com with NNFMP; 04 Feb 2001 02:40:58 -0000 Date: Sun, 04 Feb 2001 02:40:55 -0000 From: supermanlinux@yahoo.com To: freebsd-emulation@freebsd.org Subject: SuperMan Message-ID: <95iffn+k5vo@eGroups.com> User-Agent: eGroups-EW/0.82 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Length: 1310 X-Mailer: eGroups Message Poster X-Originating-IP: 209.128.133.240 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello , My name is Joshua Abbott and I wanted to email you (sorry I don't know your name) about an open source project that we need help with. Here are the details: The open source project is Code-named "SuperMan Linux" and will be create for all of those linux geeks that want more from their regular linux distribution. SuperMan Linux will also be a robust linux server and since it is open source it will be free! Please note that details are at the end of this email to join the open source project. O/S TYPE: Unix Derivitive UNIX TYPE: Linux O/S NAME: Superman Linux PLATFORM TARGET: x86 computers and all others DESCRIPTION: This o/s will be centered around making linux better and this o/s will be a robust server for anyone's needs. NOTES: o/s needs to have the following: 1. update in all existing linux software that is standard for a linux distribution 2. update in the kernel 3. an easy installation program 4. New features END EXPLANATION Other notes of interest: Do you have anyone who would be interested in joining this team or do you want to join? If so please email me with a short little note telling me you want to join. Send the email to supermanlinux@yahoo.com and then CC it to admin@server-space.net . Thanks Joshua Abbott P.S. Thank you ahead of time for joining! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message