From owner-freebsd-emulation@FreeBSD.ORG Mon Feb 2 12:18:20 2004 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 54D5A16A4CE for ; Mon, 2 Feb 2004 12:18:20 -0800 (PST) Received: from smtp804.mail.sc5.yahoo.com (smtp804.mail.sc5.yahoo.com [66.163.168.183]) by mx1.FreeBSD.org (Postfix) with SMTP id A0C7C43D3F for ; Mon, 2 Feb 2004 12:18:14 -0800 (PST) (envelope-from zenin@rhps.org) Received: from unknown (HELO rhps.org) (zenin@sbcglobal.net@68.122.34.146 with plain) by smtp804.mail.sc5.yahoo.com with SMTP; 2 Feb 2004 20:18:14 -0000 Message-ID: <401EB119.4060201@rhps.org> Date: Mon, 02 Feb 2004 12:20:41 -0800 From: Zenin User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: en-us, en, ja MIME-Version: 1.0 To: emulation@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: VMWare2 / 4.9-STABLE networking oddness (RTC related?) X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2004 20:18:20 -0000 I've got an updated 4.9-STABLE setup running VMWare 2 (W2k SP4, etc) with the latest RTC driver (major improvement btw, thanks!) and my kernel built with HZ=10000, which has done wonders to improve my VMWare performance across the board. -With the default HZ=100 VMWare is basically unusable, this is on a P4/2.4ghz box with 1GB RAM and very little other load. I've tried both bridged and host-only (with bimap NAT via IPNat) and both have the same problems. Now the W2k VMWare client seems to work well for most things, and even ping flooding it over my DSL line 400 miles away I get a solid 15ms ping response and zero packet loss. However...the point of this VMWare client is to run a Windows-only game server (MS's "Allegiance"). It looks like everything is fine until one actually tries to use the server... The game client is reporting 40ms pings but yet has unplayable lag issues (not being able to "zone" or do much of anything). The client's TCP and UDP layers seem solid, but it seems like the client is running completely off its "prediction" code and not actually getting any real information back from the server at all. Normally the symptoms shown by this setup are from someone trying to run this server over a low-bandwidth connection like DSL with 128kb max upload and have too many clients attached, but this setup is hosted at a colo on multi-homed 100Mbs connections with only two test players on the server. Is there anything more extensive I can do to debug the networking systems of this beast? Of course I'm also assuming it's a networking problem, but perhaps it's something more with the server app not getting interrupts correctly and thus just "not responding" to client events because it's not seeing them? The server's networking is based on DirectPlay 7 if it helps. TIA! -Zenin