Re: [Fwd: [Bug 817] New: DMX includes <linux/input.h> onnon-Linuxplatforms]

On Wed, Jul 07, 2004 at 05:16:30AM +0200, Roland Mainz wrote:
> Daniel Stone wrote:
> > > For x86 platforms I may have a better solution: We could simply fetch a
> > > x86 machine with >=1GHz, >=1GB memory, install VMware on it and then can
> > > run MANY MANY VMware VMs on it, - one for Solaris2.8/x86, one for
> > > Solaris 2.9/x86, one for SuSE Linux, one for Debian Linux, one for
> > > NetBSD, one for FreeBSD and there is still memory left for more VMs.
> > > And we would be able to use the same machine for building binaries for
> > > these platforms, too... :)
> > 
> > I have an AthlonXP 2400+ (raw clock 2GHz), and VMware is really quite
> > slow on it - my Windows sessions crawl.
> 
> Please check your configuration. We are running VMware "servers" here
> (to be exact: VMware Workstation on headless AMD Athlon machines) with
> up to 8 VMs (we could do more per server - but the network is usually
> the bottleneck since we don't have everywhere 1Gbit and if four users
> share one 100baseT pipe it may quickly get saturated if everyone runs
> realplayer) in parallel which provide windows services (e.g. WinNT4.0,
> Win2000, WinXP) and various other OSes (Solaris x86, Linux/x86 etc.) to
> our Sun machines. Works perfectly.
> 
> BTW: Win95/Win98/WinME and MS-DOS applications are slow as snails
> because the underlying "OS" doesn't call "HLT" when being idle. And
> don't forget to install the Vmware Tools and VMWare VGA driver on the
> Windows OSes.

I don't remember the configuration, but it was pretty slow, no matter
what I did. It certainly wasn't *faster* than under the host OS - I'll
tell you that now.

> > I wouldn't want to be trying to
> > build the monolithic tree under that, really.
> 
> I am doing this already with SuSE 8.2 as host OS and SuSE9.1/Solaris9 as
> guest OSes and don't have performace problems on my laptop. Mozilla
> debug builds within the VM may even be faster than running natively on
> the host OS (because they are I/O-bound, not CPU-bound - the VMware VM
> caches disk I/O which boots performace in such scenarios a lot (WARNING:
> If the host crashes or gets turned OFF a logging filesystem within the
> guest OS is of little use... in cases where it is important to gurantee
> filesystem consistency it is better to run the critical stuff on a NFS
> filesystem)) ... :)

I've actually found that NFS is probably the best way to throw data away
... but there you go.

-- 
Daniel Stone                                            <[email protected]>
freedesktop.org: powering your desktop                http://www.freedesktop.org

_______________________________________________
release-wranglers mailing list
[email protected]
http://freedesktop.org/mailman/listinfo/release-wranglers

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFA63M/cPClnTztfv0RAuBCAKCHVg6gx30jnslO+nvsAH7fEBXxXwCeJofv
fwNjbMDhac2oXX7PhPYRXmg=
=RR6n
-----END PGP SIGNATURE-----