Date: Tue, 5 Dec 2000 23:44:30 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: barry@lustig.com, stable@FreeBSD.ORG, Matt Dillon <dillon@earth.backplane.com> Subject: Re: VMware hanging Message-ID: <p04330104b6537116c9da@[128.113.24.47]> In-Reply-To: <20001205232913.15317.qmail@devious.lustig.com> References: <20001118231633.A85206@evilcode.com> <200011190635.eAJ6ZRS94516@grumpy.dyndns.org> <20001118230305.A83848@evilcode.com> <20001119151138.A7434@bsdvm.jtjang.idv.tw> <200011192202.eAJM2cG03593@billy-club.village.org> <200011192239.eAJMdDa90818@earth.backplane.com> <200011192308.eAJN8q714360@whizzo.transsys.com> <200011192324.eAJNO1891133@earth.backplane.com> <20001205232913.15317.qmail@devious.lustig.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 6:29 PM -0500 12/5/00, Barry Lustig wrote: >VMware is hanging the system in certain cases with 4.2-STABLE >kernels, but works with 4.2-RELEASE. If I config the memory >in vmware to 64MB the client os runs properly. If I set it >higher, I get a hung system. When the system is hung >everything seems to lock up except for the mouse. As another (probably useless) datapoint, I also recently upgraded to 4.2-stable. I upgraded all out-of-date ports at the time, except I did NOT try to upgrade the vmware- related ports. Vmware seems to still be working for me, unless I try to do a 'suspend' (the VMWARE option to suspend the running virtual system), and then try to switch to a different system while that first one is suspended. In my case the X-terminal session is locked up, except that the mouse can still move. I *think* I could still switch consoles via 'alt-opt-F1', but I did not have any sessions in those other console windows so I couldn't do anything. It would not even echo letters I was typing on the keyboard. I did happen to have three remote sessions going via ssh at the time, and those sessions could do some commands. Once I typed in a "bad command", that session was hung. Trying to pull myself out of this nosedive, in the last session (which happened to be root), I tried to do a 'shutdown -r now'. That session hung too. In the end, I had to turn off power to the machine to get it's attention, after which it booted up fine. Also, in my case the virtual machines are 96meg, and the real machine is a dual-processor P3 system with 256meg of RAM. It is definitely NOT running into a low-memory situation... I don't really have any time to help debug this right now, but I'll be following it. Maybe in a week or two I should once again have some time. -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p04330104b6537116c9da>