From owner-freebsd-emulation Tue Dec 12 21:15:48 2000 From owner-freebsd-emulation@FreeBSD.ORG Tue Dec 12 21:15:46 2000 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from granger.mail.mindspring.net (granger.mail.mindspring.net [207.69.200.148]) by hub.freebsd.org (Postfix) with ESMTP id 4EFBA37B400 for ; Tue, 12 Dec 2000 21:15:45 -0800 (PST) Received: from jupiter.delta.ny.us (nyf-ny7-39.ix.netcom.com [198.211.17.167]) by granger.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id AAA31751; Wed, 13 Dec 2000 00:15:36 -0500 (EST) Received: (from vsilyaev@localhost) by jupiter.delta.ny.us (8.9.3/8.9.3) id AAA00406; Wed, 13 Dec 2000 00:15:32 -0500 (EST) (envelope-from vns) Date: Wed, 13 Dec 2000 00:15:32 -0500 (EST) From: "Vladimir N.Silyaev" Message-Id: <200012130515.AAA00406@jupiter.delta.ny.us> To: nsayer@kfu.com Cc: barry@lustig.com, emulation@freebsd.org Subject: Re: VMWare performance when returning from suspend to disk In-Reply-To: <3A369583.A8F6236B@sftw.com> References: <20001211003601.B937@gblx.net> <3A369583.A8F6236B@sftw.com> Reply-To: vns@delta.odessa.ua Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In muc.lists.freebsd.emulation, you wrote: >> VMWare running on dual 800Mhz with 512MB RAM runs great, except when I >> suspend to disk and then restore that image. When the restored image starts >> running, the mouse will move for a few moments and then freeze and then start >> moving again. The same behavior happens to window input. During the >> freezes, VMWare seems to be doing a lot of I/O. Any thoughts on where to >> look? > >I see this same symptom. My guest is win2k with 64M of RAM on a machine >with 192M. I can only suspect that it's some part of the guest >initialization that doesn't get run when you resume that does get run >when you boot, and that doesn't matter on Linux (since presumably one >doesn't see this when the host is a Linux box). This implies that it's a >bug in vmmon, but I don't know enough about that code to make coherent >suggestions. :-) Not likely. Actualy vmmon module it's very simple - it just has functionality to allocate fixed memory pages and make context switch back and forward to huge piece of code executed at RING 0. This code doesn't make any OS interaction, so fortunatly, this binary image executed on Linux also runned on FreeBSD (I think the same code used in VMware/NT). Returning to mentioned problem, my guess is it's a differencies it the VM implementation between FreeBSD and Linux. But unfortunatly we don't have any ability to traceback that. -- Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message