glenngombert> I could not even get 'Current' to boot at all under
glenngombert> VMware 3.0 without applying the patch that was mentioned
glenngombert> a couple weeks ago under Win2K...
What goes wrong to you? Unable to boot with boot floppies?
-- -
Makoto `MAR' Matsushita
To Unsubscribe: send
iedowse> ... but only if you spend most of your time running CPU benchmarks :-)
That's right :-)
iedowse> On slower CPUs (I was using a 400MHz PII), the interrupts can
iedowse> soak up virtually all of the available processing capacity
iedowse> without the patch. I suspect this effect is respon
In message <[EMAIL PROTECTED]>, Makoto Matsushita writes:
>I really know I'm doing a stupid thing, but here is benchmark results
>of both "plain" and "patched" 5-current (as of Nov/26/2001). Patched
>FreeBSD is about 10% faster than before.
... but only if you spend most of your time running CPU
I could not even get 'Current' to boot at all under VMware 3.0 without
applying the patch that was mentioned a couple weeks ago under Win2K...
--
Glenn Gombert
[EMAIL PROTECTED] - email
(513) 587-2643 x2263 - voicemail/fax
Makoto Matsushita <[EMAIL PROTECTED]> wrote:
>
> iedowse> Some
I could not even get 'Currnet' to boot at all under VMware 3.0 without
applying the patch that was mentioned a couple weeks ago under Win2K...
--
Glenn Gombert
[EMAIL PROTECTED] - email
(513) 587-2643 x2263 - voicemail/fax
Makoto Matsushita <[EMAIL PROTECTED]> wrote:
>
> iedowse> Some
iedowse> Someone mentioned on a list somewhere that vmware takes forever to
iedowse> emulate the cmpxchg instruction, and that using the I386_CPU version
iedowse> of atomic_cmpset_int() helps a lot.
I really know I'm doing a stupid thing, but here is benchmark results
of both "plain" and "patche
At 7:35 AM -0800 11/15/01, John Baldwin wrote:
>On 15-Nov-01 Glenn Gombert wrote:
>>
>> Thanks for the tip Ian ...this works great! I have applied this patch
>> to my desktop system ...and the FreeBSD Current kernel with this patch
>> applied boots right up now...anyone else running Current un
On 15-Nov-01 Glenn Gombert wrote:
>
> Thanks for the tip Ian ...this works great! I have applied this patch
> to my desktop system ...and the FreeBSD Current kernel with this patch
> applied boots right up now...anyone else running Current under FreeBSD
> would fine it helpful to do as well
Thanks for the tip Ian ...this works great! I have applied this patch
to my desktop system ...and the FreeBSD Current kernel with this patch
applied boots right up now...anyone else running Current under FreeBSD
would fine it helpful to do as well
Glenn G.
Ian Dowse <[EMAIL PROTECTED
In message <[EMAIL PROTECTED]>, Robert Watson writ
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 spend a lot
>of time just spinning -- it's not clear to me what the cause is, and I
>haven't had time to deb
I now have 4.3 running under VMware on my laptop and main desktop machine
(Asus CVU4X-D) systemI am trying to recompile current on my desktop
system now (Current hangs badly on my laptop)I will try and investigate
the cause of this a little later tonight
--
Glenn Gombert
[EMAIL PR
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 spend a lot
of time just spinning -- it's not clear to me what the cause is, and I
haven't had time to debug.
Robert N M Watson FreeBSD Core Team, Trust
[ Picking any one to reply to... ]
>
> 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
>
Thanks to a
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,
>
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 he
On Mon, 12 Nov 2001, Koster, K.J. wrote:
> 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.
Yep; 4-stable with
I am running VMware on my Dell 5000e LapTop using Win2k right now and
4.3 seems to work fineI 'hang' badly when trying to run 'Current'
however ...and I am still trying to sort out why that is
Glenn G.
--
Glenn Gombert
[EMAIL PROTECTED] - email
(513) 587-2643 x2263 - voicemail/fax
-
raff> Yes, I am running FreeBSD 4.3 in a win2k vmware will everything
raff> working including the network (to outside world). No special
raff> configurations were required other than the obvious.
FreeBSD 5-current guest also works fine here (W2k host). I'm happy
with ports/emulators/vmware-tool
I am running FreeBSD 4.4 in a win2k vmware.
Everything seems to work without any perticoular configurations.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Yes, I am running FreeBSD 4.3 in a win2k vmware will everything working
including the network (to outside world). No special configurations were
required other than the obvious.
At 08:57 AM 11/12/2001, Koster, K.J. wrote:
>Just out of curiousity, are there any people who actually have FreeBSD
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 ke
21 matches
Mail list logo
