What kind of limitations are you looking for? That's a very broad question...
Here are a few per-VM limitations
\- 2 vCPUs
\- 3.6 GB RAM
\- 6 virtual PCI devices. One of those is a video card. SCSI cards, sound cards, and network cards also count against this. IDE, USB, etc., do not count.
Hey Nick, what do you mean by "2 vCpus"
And what is the 6 PCI virtual devices thingy?
What I mean by limitations is that just any in general
You REALLY should read the manuals
ERR, im just asking because I want peoples experiences..
Message was edited by:
Message was edited by:
2 vCPUs is two virtual CPUs. Your VMs can either have a single CPU or two CPUs assigned to them. VMware ESX VMs can have four CPUs assigned to each VM.
6 PCI devices is exactly what I described - you can have up to 6 virtual PCI devices - one PCI video card (mandatory), one sound card (optional), and any combination of SCSI cards and network cards. So, if you have 1 PCI video card, a sound card, and a SCSI card, you can have three network adapters in your VM. If you use IDE disks and don't have any sound you can add two more network cards to the VM.
You really should go read the manual...it will help quite a bit...
I'm sorry, let me clarify myself.
What I meant to ask is what are some of the known problems with VMWare regarding your own experiences. That is what I meant by limitations.
In response to your answer about reading the manual Oliver - The manual doesnt help me because it only puts FIXES, however, I'm looking for problems that are still there.
Thanks for the reply though Oliver.
You don't usually "bump" a thread unless it's gone unanswered for a while - since you just posted today, there's really no reason to bump the thread.
One problem that comes to mind is the "absolute pathname" bug.
Another one are some of the defaults used when creating VMs.
Yet another one is the "black screen" bug.
Nothing though that you can't fix.
Hey Oliver, what exactly do you mean by the absolute path name bug. How does it happen?
Also what is the black screen bug and how does it happen.
Thanks for your response!
if you search the forum for both of these questions you would find your answers without the above having to re-hash existing information.
Limitations and problems are different things - limitations are usually things designed into the software or things about the environment that you can't get around. For example, the 3.6GB limitation is due to the fact the VMware Server is written in a 32-bit environment. VMware Workstation overcomes this limitation in a 64-bit environment.
Bugs are a little different - bugs are things that are broken but not designed to be that way. For example, the absolute path bug that oreeh mentions is just that - a bug - it isn't designed that way, but it works that way.
Build_Interns.. .If you're looking for people's experiences, spend an hour or few hours reading the threads in the VMWare Server forum. You'll get alot more information by doing that and asking specific questions based on that information.
Most of the people here have learned what they have learned by installing, testing and deploying the product. If we run into a problem, search the forum, then ask qeustions.
The more specific your question, then better response you'll get from members of the community. Everyone is glad to help out, but vague questions will get at best vague answers (and sometimes nasty answers).
yep with him thats what I am doing every day.