On 9/22/2012 3:17 PM, David Froble wrote:
>
> My 2 most advanced PCs are AMD San Deigo chips, 90 nm single core. One
> using Windows 2000 Pro, and the other Windows XP. I do not have any
> experience with multi-core CPUs at this time. Some questions.
According to
http://en.wikipedia.org/wiki/X86_virtualization
You need a 64 bit AMD processor released after May 23, 2006. For Intel
you need a Pentium 4 released after November 2005.
The FreeAXP emulator requires dual processors at a minimum.
Basically I would not bother with emulation on CPUs that are more than a
few years old.
> Will any of the OSs, Weendoze, Linux, Unix, etc allow choices for what
> can use each core?
I have not looked into that.
> I see references to System CPU and User CPU. Is this user configurable?
> If so, what OS allow this?
System is CPU utilization by the operating systems and drivers.
User code is non-privileged code.
Some OSes like VMS allow quotas on a user CPU for a process.
And in some cases you can set priorities on the user mode CPU.
> My choice if I was to use a VM would be to have no underlaying OS, but,
> I'm getting the impression that such does not exist
Pretty much. Most systems add a Hypervisor with a specific Linux
distribution as the control VM.
Others add a hypervisor to a booted operating system.
The hypervisor timeshares the guest OSes, and can be an add-on to a
booted OS.
> If some
> underlaying OS is required, is there any that are superior for doing so?
My preference would be for Linux as it can easily be customized and I
can inspect the source.
> I'd think what would be desired would be something that provided
> minimal capabilities, and let the VM, and guest OSs, do as much of
> what's required as possible.
The problem is with that the privileged mode code must either be run by
the hypervisor or has to be simulated in user mode by the hypervisor.
So the hypervisor has to do as much of the basic IO and virtual memory
management as possible, as as simulation of that code uses most of the
resources.
For efficiency, you want the VM to do as little in privileged mode as
possible.
> What underlaying OS works well with a hypervisor and paravirtulized
> drivers? Or perhaps I should be asking what guest OS can work with the
> paravirtulized drivers?
Windows 7, 2008 have paravirtualized drivers available for them and now
recognize when they are running under many of the hypervisors.
Paravirtualized drivers are also there for Windows XP.
Now the paravirualized drivers have to be matched to the hypervisor, so
you need to check to see if they are available.
Most modern Linux distributions will also recognize when they are
running in a hypervisor.
> Basically I'm a novice at these concepts, and looking for advice to keep
> me from going down some dead end paths.
I would read the installation and configuration requirements for
VirtualBox and the guest OSes. And then look at the other Hypervisors.
VirtualBox is easy to install on Windows and Mac OS-X and provides a GUI
that is easy to use.
> What I'm considering is putting together a new system for this
> experimentation. Maybe a 4 core CPU, with plenty of memory. Not sure
> what effect and bonuses you get with multiple cores, and what might be a
> minimum number of cores, and what might be optimum.
FreeAXP requires 2 cores. More seem to be better. Check the prices of
8 core CPUs when you do your research.
I have not done the research to see if a newer 4 core processor would be
better than an older 8 core processor with the same clock speed.
> As to disk storage. Are virtual devices set up for the guest OSs? Is
> multiple disks or partitions advisable? Or just have one large disk
> that gets virtual devices created for the guests?
Some VMs or emulators require container files, others can access raw disks.
In general, you can use storage managers to combine and partition disks
many different ways.
For reliability, mirroring can be used.
For performance, solid state caches and separate physical disks.
For just playing, you can use one large disk.
> So, advice on:
>
> 1) Hardware
You need at a minimum the virtualization support, 2 Ghz CPU or better
and at least 4 GB of RAM would be the minium to play with.
Faster is better, more memory is better. Nothing that you do not
already know.
If you want to play with moving a VM from one host to another with out
shutting down the guest, then you need more than simple hardware.
> 2) Underlaying OS and configuration
Depends on below:
> 3) VM software
Pick the hypervisor(s) that you want to try.
Microsoft has Hyper-V.
Linux has Xen and KVM.
Oracle has VirtualBox that can use the KVM paravirtualized drivers.
VMware has their free player.
There are probably some others out there.
For when I do something similar, I would probably use either Xen or KVM,
depending on the guest OS support. I would probably use Scientific
Linux for as for $Dayjob related reasons I am using it.
For playing, I would also tend to open source.
As far as market share, VMware appears to have the largest commercial
market share. I do not know about the others.
When you do your research, you will find that there are some diverse
opinions, just like for operating system tuning. Some people are
against using paravirtualization for various reasons. My opinion is
paravirtualize as much as possible.
Some feel that RAM should be dedicated to the guest. Some
virtualization solutions map the guest memory to their own VM and take
over the paging. The load that you are running may be the key to the
right answer to that one.
I have been told by other experts, that if you use the ZFS file system,
you need to configure it to have a high speed write cache, such as using
solid state disks, or your VMs will have severe performance problems
every time that they do a disk write. Seems to be a common
configuration problem.
> 4) Guest OSs
Check which guest OSes have support for running in a hypervisor.
> 5) configuration, configuration, cofiguration ....
Test things and try things out. The worst that can happen is that you
have to reinstall everything.
Try out assigning different number of CPUs to guests to see what happens.