Date: Mon, 12 Nov 2001 08:41:22 -0800 (PST) From: Julian Elischer <julian@elischer.org> To: "Koster, K.J." <K.J.Koster@kpn.com> Cc: "'Rohit Grover'" <rgrover@panasas.com>, "FreeBSD Hackers mailing list (E-mail)" <freebsd-hackers@FreeBSD.ORG>, "Bruin, M.L. de" <M.L.deBruin@kpn.com> Subject: RE: FreeBSD on vmware Message-ID: <Pine.BSF.4.21.0111120839010.93993-100000@InterJet.elischer.org> In-Reply-To: <59063B5B4D98D311BC0D0001FA7E452205FDA091@l04.research.kpn.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I have been running -current under vmware 2.x up until about August.. (it didn't stop working, but I vmware stopped running on -current due to KSE changes (patches now available I believe)).. i.e I was running -current under -current 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0111120839010.93993-100000>