Date: Tue, 20 Nov 2001 08:28:33 -0500 From: Sergey Babkin <babkin@bellatlantic.net> To: Glenn Gombert <glenngombert@onebox.com> Cc: "Bill G." <billg@cyberwar.com>, hackers@freebsd.org Subject: Re: vmware boot problem (xp host, freebsd guest) Message-ID: <3BFA5A81.1A7CDC96@bellatlantic.net> References: <20011120125602.INJT26106.mta07.onebox.com@onebox.com>
index | next in thread | previous in thread | raw e-mail
Glenn Gombert wrote:
>
> Here is a patch that was posted to the list a couple weeks ago, that
> needs to be applied to make FreeBSD uner vmware work reliably..
>
> In message <20011113165944.G52323-100000@fledge.watson.org>, Robert Watsonwrit
> es:
> >I've had -STABLE run fine, but of late have had a lot of trouble with
> >-current. Userland processes during the boot sequence seem to spenda
> lot
> >of time just spinning -- it's not clear to me what the cause is, andI
> >haven't had time to debug.
>
> Someone mentioned on a list somewhere that vmware takes forever to
> emulate the cmpxchg instruction, and that using the I386_CPU version
> of atomic_cmpset_int() helps a lot. I noticed a major vmware slowdown
> with -current sometime in September, so I tried avoiding the
> cmpxchg's and things got much faster. Below is the patch I use
> (using this outside vmware on SMP hardware is a bad idea :-).
Is there any reason why don't you just define I386_CPU instead
of modifying the header file ? This is done by the line
cpu I386_CPU
in the config file. Or has the full i386 support been already dropped
from the kernel by now (I remember such a discussion on
-developers) ? Hm, maybe we should add "VMWARE_CPU" then for
inclusion of any Vmware-related optimisations.
-SB
>
> Ian
>
> Index: atomic.h
> ===================================================================
> RCS file: /dump/FreeBSD-CVS/src/sys/i386/include/atomic.h,v
> retrieving revision 1.21
> diff -u -r1.21 atomic.h
> --- atomic.h 2001/10/08 20:58:24 1.21
> +++ atomic.h 2001/10/09 18:35:25
> @@ -111,7 +111,7 @@
> * Returns 0 on failure, non-zero on success
> */
>
> -#if defined(I386_CPU)
> +#if defined(I386_CPU) || 1
> static __inline int
> atomic_cmpset_int(volatile u_int *dst, u_int exp, u_int src)
> {
>
> ---- "Bill G." <billg@cyberwar.com> wrote:
> >
> > I am having trouble getting FreeBSD 4.4-RELEASE to run in
> > vmware. I am using Windows XP Pro as the host os, vmware
> > version 3, and FreeBSD as the guest os. I tried searching
> > the mailing lists, but was unsuccessful in finding the
> > answer to this problem.
> >
> > FreeBSD installs, but will not boot - it just hangs, with
> > no errors.
> >
> > All suggestions / solutions appreciated. Thanks,
> >
> > Bill
> >
> >
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-hackers" in the body of the message
> >
>
> __________________________________________________
> FREE voicemail, email, and fax...all in one place.
> Sign Up Now! http://www.onebox.com
>
> 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
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3BFA5A81.1A7CDC96>
