From owner-freebsd-hackers Mon Nov 12 9: 0:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 80DC037B405 for ; Mon, 12 Nov 2001 09:00:28 -0800 (PST) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id IAA94066; Mon, 12 Nov 2001 08:42:38 -0800 (PST) Date: Mon, 12 Nov 2001 08:42:38 -0800 (PST) From: Julian Elischer To: "Koster, K.J." Cc: "'Rohit Grover'" , "FreeBSD Hackers mailing list (E-mail)" , "Bruin, M.L. de" Subject: RE: FreeBSD on vmware In-Reply-To: <59063B5B4D98D311BC0D0001FA7E452205FDA091@l04.research.kpn.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG oh yeah there was a period where the lnc driver caused a crash of vmware. leave it out and try again.... On Mon, 12 Nov 2001, Koster, K.J. wrote: > Dear Rohit, > > Thanks for the response and your suggestion. > > > > > > Fatal trap 12: page fault in vm86 mode > > > > The following change helped me get rid of a similar panic. > > > > - device atkbd0 at atkbdc? irq 1 > > + device atkbd0 at atkbdc? irq 1 flags 0x1 > > > When I look at the keyboard in the visual kernel configuration this flag is > already set. > > Just out of curiousity, are there any people who actually have FreeBSD > running inside a vmware VM? Evidence from the mailing list archives seems to > suggest that it worked up to FreeBSD 3.2 and then stopped, never to work > again. > > Kees Jan > > ================================================ > You are only young once, > but you can stay immature all your life. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message