As far as I can tell, the extremely slow boot problem is specific to
VMWare for WindowsNT when running on the latest Athlon processors.
VMWare for Linux, running under FreeBSD host of the same Athlon
processor using the same guest image, does not have any problem.

If host Windows 2K is a Petium II or III, then it runs with no problem. I
VMWare should fix this for Athlon for its Window version of VMWare.
I say this because its Linux version works fine on an Athlon host.

There may be a quick fix on the FreeBSD side. I have a GENERIC FreeBSD
kernel built off CURRENT tree around March 2, 2001 that actually boots on
the Athlon host without problem. Unfortunately I didn't keep the version of
the source tree. Maybe someone on FreeBSD lists can tell what is causing
this problem (some code triggered a VMWare slow path on Athlon
processor ???)

Steve Neuharth wrote:

> I have no problem running freebsd... 4.3 and 4.4
> "Ian Jenkinson" <[EMAIL PROTECTED]> wrote in message
> > Ladies and Gentlemen of this newsgroup,
> >     I sent this one to genereal, but unfortunately nobody answer so I
> > was wondering if this group could be in a position
> > to help me
> >     Thanks
> >     Ian Jenkinson
> >
> > Subject: Windows 2000 Host running FreeBSD 4.2-RELEASE guest
> > Date: Mon, 08 Oct 2001 15:43:46 +0100
> > From: Ian Jenkinson <[EMAIL PROTECTED]>
> > Organization: VMware, Inc.
> > Newsgroups: vmware.for-windowsnt.general
> >
> > Ladies and Gentlemen,
> >     I am having a lot of difficulty in running FreeBSD 4.2-RELEASE as a
> > guest OS on my Windows 2000 (SP2) workstation. I have
> > installed Linux RedHat 6.1 and Linux SuSe 7.1 VMs and they work just
> > fine. The install process of the two boot floppies for FreeBSD passed
> > off without great event, except for ftp timeouts and retries. However it
> >
> > takes well over 30 minutes to boot the installed
> > FreeBSD and burns the host CPU to the ground (an Athlon 1.3Ghz with
> > 512MB)!
> >     If anyone has any thoughts or guidance on what's happening I would
> > be delighted to hear them.
> >     Yours
> >     Ian
> >

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to