[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: debian-user] Re: AMD vs Intel and the Debian kernel



Hi Ted,

Thanks for clarifying -- hopefully that'll give the wiser heads around
here a bit more of a lead on how to help you.

I've done a little bit of research into virtualization, but only just
scratching the surface, and nothing on the level that you're
describing--it sounds like you'll have a lot of research to do before
you can put it together, but no reason that should stop you!  I'll
just throw in a few points.

Here's some links on virtualization in Debian:

https://penta.debconf.org/~joerg/attachments/16-qdebconf2007_virtualization_in_debian
http://wiki.debian.org/Xen (wiki on using Xen under Debian)
http://en.wikipedia.org/wiki/Comparison_of_virtual_machines (decent
comparison of what your options are for virtualization)

Maybe you know these things already, but it can't hurt to provide some links.


> Gb divided by 8.  At this time I haven't got a clue whether the virtual
> system should be single core or multi core

As for multi-core vs. single-core, I can't really imagine that you'd
be better served running several virtual machines on a single-core
processor than you would a multi-core one.  (Do they even sell
single-core server-grade processors any more?)  Obviously your
different virtual machines will have to share whatever hardware
resources are available, so I'd imagine there might be a lot of
bottlenecks to doing this, not just the processor (disk I/O speed is
likely to be another one, for instance).

I personally don't have the experience to give any pragmatic advice on
what you might need for this.  Maybe somebody else on this list can
help more, or you could consider checking out some of the Xen mailing
lists:
http://lists.xensource.com/

Good luck!


> Thanks Jeff.
>
> What I want to do is acquire a fast quad core CPU board and associated chip
> set (either Intel or AMD) manufactured.  The purpose is to establish a
> virtual enviornment with a Linux host as the basis for that computing
> environment.  Over the last 2 years there have been many changes regarding
> how a virtual computing environment can come together.  First I encountered
> Xen and then became aware of several existing Linux approaches.  I followed
> the lists the best I could and started to wonder which would be the optimal
> approach.  I decided that Debian would be my best bet but I was unsure of
> what virtualisation technique would be best.
> I want to run server applications on this Debian host with that host
> virtualizing the servers.  I need each server to be capable of networking
> into my LAN as well as into the INTERNET.  I need the networking between
> servers on the LAN and well as the INTERNET to be easily connected and
> understood preferably by means of a GUI.  But I want the entire networking
> effort OPEN SOURCE so I don't want a GUI that is non Debian.  The networking
> of virtualised servers -- let's say 10 -- has me worried as I want to assign
> static LAN based IP address (192.168.x.x) and name
> (server-apache.network.com) and SAMBA connection protocal for every server.
>  In other words I want the servers to be able to interconnect with each
> other using shares.
>
> Also, recently, I discovered that  a dual or quad  CPU board only provides
>  load balancing and not greater speed.  If for example the CPU speed is
> given as 3 Gb and there are numerous servers on that machine the speed of
> each of the two (dual core) or 4 (quad core) or 8 core components is reduced
> thus reducing the speed of each process so the total processing of core
> elements is 3 Gb.  This means for an 8 core unit the speed is reduced to 3
> Gb divided by 8.  At this time I haven't got a clue whether the virtual
> system should be single core or multi core as there could be speed
> advantages and perhaps the manner of virtualising might work best by using
> some kind of quota control???
>
> Maybe you or someone else reading this response (or possibly a Debian
> mentor) could help me with this objective.
>
> Anyway, thanks -- Ted


Reply to: