Date: Mon, 4 Dec 2000 12:47:51 -0800 (PST) From: Doug Ambrisko <ambrisko@whistle.com> To: barry@lustig.com Cc: emulation@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: VMware hanging -- Memory deadlock? Message-ID: <200012042047.MAA03339@whistle.com> In-Reply-To: <20001203180054.10355.qmail@devious.lustig.com> from Barry Lustig at "Dec 3, 2000 01:00:54 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Barry Lustig writes: | I have a vaio z505le with 192MB running 4.2-STABLE (cvsupped today). I've | been trying to get vmware running properly on it. I first configured vmware | on the vaio, created a win2k type virtual disk, set ram in the VM to 80M, | and copied a happily working win2k virtual disk from another system over the | skeleton one that the config wizard created. I'm running the latest port of | XFree86 4.0.1. | | Each time I start vmware the system gets part of the way through the VM | boot process and then hangs. The only thing that still responds is the | mouse. A top process running in an xterm locks up, as does the getty on the | serial console. I can break into ddb from the serial console. I've found | that dropping the memory size for the VM down to 64MB works (68MB doesn't). | When running the 64MB VM top shows: | | 70M Active, 34M Inactive, 75M Wired, ~9M Cache, 29M Buf, ~6M Free | | Does anyone have any suggestions on how to debug this? No, but going back to 4.2 RELEASE kernel fixed it for me. Start from there and move forward until you find out which commit broke it. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200012042047.MAA03339>