<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: VMware Server in Production</title>
	<atom:link href="http://www.briandowney.net/blog/2007/03/30/vmware-server-in-production/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.briandowney.net/blog/2007/03/30/vmware-server-in-production/</link>
	<description>Technical musings of an entrepreneur.</description>
	<lastBuildDate>Tue, 16 Feb 2010 10:53:34 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: conexiva.net &#187; VMware Server 2 en CentOS 5.3 con instalacion mínima</title>
		<link>http://www.briandowney.net/blog/2007/03/30/vmware-server-in-production/comment-page-1/#comment-361</link>
		<dc:creator>conexiva.net &#187; VMware Server 2 en CentOS 5.3 con instalacion mínima</dc:creator>
		<pubDate>Wed, 29 Jul 2009 02:52:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.briandowney.net/blog/2007/03/30/vmware-server-in-production/#comment-361</guid>
		<description>[...] Algunas recomendaciones para usar el  VMware Server 2 en una instalación mínima de CentOS: http://www.briandowney.net/blog/2007/03/30/vmware-server-in-production/ [...]</description>
		<content:encoded><![CDATA[<p>[...] Algunas recomendaciones para usar el  VMware Server 2 en una instalación mínima de CentOS: <a href="http://www.briandowney.net/blog/2007/03/30/vmware-server-in-production/" rel="nofollow">http://www.briandowney.net/blog/2007/03/30/vmware-server-in-production/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VMWare running on Linux CentOS 5.2 &#171; MJS1&#124;dotcom</title>
		<link>http://www.briandowney.net/blog/2007/03/30/vmware-server-in-production/comment-page-1/#comment-357</link>
		<dc:creator>VMWare running on Linux CentOS 5.2 &#171; MJS1&#124;dotcom</dc:creator>
		<pubDate>Tue, 12 May 2009 12:53:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.briandowney.net/blog/2007/03/30/vmware-server-in-production/#comment-357</guid>
		<description>[...] VMWare Server in Production by Brian Downey and [...]</description>
		<content:encoded><![CDATA[<p>[...] VMWare Server in Production by Brian Downey and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fusebox</title>
		<link>http://www.briandowney.net/blog/2007/03/30/vmware-server-in-production/comment-page-1/#comment-348</link>
		<dc:creator>fusebox</dc:creator>
		<pubDate>Fri, 09 Jan 2009 00:57:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.briandowney.net/blog/2007/03/30/vmware-server-in-production/#comment-348</guid>
		<description>Whoever says that,&quot;VMware Server is not fit for production&quot; has surely never ever worked with well enough to understand what is going on and last but not least,has no iota of what virtualization/vmware is all about and the way a virtualization solution is put in place.

I have been experimenting,designing &amp; implementing VMWare&#039;s ESX,ESXi &amp; Server editions for some major,small &amp; startup companies with real good results.Putting a virtualization or vmware solution in place is a whole different ball game.Its all about careful &amp; meticulous design keeping that various performance requirements,bottlenecks,purpose of the VMs,number of users,available hardware,bandwidth,etc,etc....Execution or deployment is just 15% and whereas design &amp; system planning phase is 85%.That says it all.I know a case of one huge financial institution which screwed up its virtualization project because of hurrying up the design/system planning phase and directly jumping into implementing it.Ultimately it found itself in a huge mess with huge performance issues and blaming it all on VMware,saying it was not yet ready for mainstream.Later some sense dawned on this company and realized it was their incapability and not VMWare&#039;s.Now,they are spending huge amounts on undoing everything,redoing the design and implementation all over again from square#1.

In short,what I am trying to say is either VMware Server or ESX/ESXi,they are all awesome technologies in their own sense.But,if you dont get the design&amp; system planning basics right while putting a Vmware Server or ESX server ,no matter how big or great hardware &amp; resources you have,they are all a huge waste and nothing more than a expensive 10k$ paperweight.

I have been personally running VMware Server 2.0 on CentOS 5.2(Final),patched and updated without any sort of issues,at my home.This has 6gb of RAM,2 x 640GB sata2 drives and a AMD Phenom Quad core CPU.In the Admin world,this machine would be compared to a midlevel gaming pc.But,you will be surprised to know that this is running 11 VMs at this point and all are up &amp; running without any performance issues.6 are linux,2 Solaris 10,1 Vista,1 Windows server 2008 enterprise and all are running 64bit OS,since this physical cpu has AMD-V enabled.I am also running SAP Netweaver 2004s in one of the linux machines and Oracle 10g RAC simulation on 2 of the VMs,10gR2 on Solaris 10.

Coming to the way,I setup the filesystems or drives or CentOS installation.Like, Brian rightly pointed out,I am running a minimal install(although I have GNOME installed)but running it in run level 3 and disabled un-needed services and only 3-4 services are running.I have no onboard hardware raid as this is not a high end pc or entry level server.So,I am using software raid available in Centos and setup the RAID partitions according to my performance or redundancy needs.For example,VMs which can afford to go down even if one of the datastore filesystem(s) goes down,but need speed over redundancy,I chose to use RAID 0 with an EXT2 formatting.For VMs,which need redundancy over speed and cannot afford to be lost for a filesystem corruption or disk crash,I chose to go with RAID1 with EXT3.My SAP and Win 2008 server have their own dedicated datastores/filesystems and I chose speed over redundancy in both their cases as SAP is pretty IO intensive.So,I used RAID 0 with EXT2 with a bigger chunk size on the RAID level &amp; bigger block sizes on the filesystem level.

Moreover,I make sure I allocate all the disk space upfront while I am creating a VM to give it a performance boost and at the same time avoid defragmentation,which indirectly results in inefficient IO seeks &amp; burden on the kernel ultimately affecting end performance which will have a domino effect on all the VMs in that filesystem.Before,I create my first VM,I make sure the kernel &amp; system parameters,swap ,shared mem params are tuned to requirements &amp; to optimal values to reduce the possibilities of any bottlenecks in the first place.In short,better to be PROACTIVE rather than be REACTIVE &amp; regret later.

This is just a tip of the iceberg,this small setup itself can be tuned,designed in multiple ways depending upon your needs and requirements.Its all about understanding the requirements clearly.That&#039;s the first step for a successful vmware solution.And,trust me VMWare Server 1.x/2.x is a peach of a product,especially when you see its capabilities with the right design/hardware and absolutely at no licensing cost.It may be free of licensing costs,but that doesnt mean its inferior or cannot handle production.One shouldnt compare it with ESX/ESXi server,as that a whole different ball game when you really get into it.You will obviously getfor a 15grand a cutting/bleeding edge technology which can run on bare metal hardware with absolutely negligible overhead &amp; footprint.Whereas,VMware server is running on top of a OS as an application.Now,the beauty is,inspite of that with careful but simple design ,one can churn out immense power,performance with it and can peacefully run handful of decent production VMs.So,compare apples to apples and not apples to oranges,which is not totally fair.

In the first place,the very reason vmware server is free with not licensing strings attached is,VMWARE wants people or companies(Big/Small) to have a taste of what it could achieve and the whole objective is to entice the companies to buy the REAL DEAL (ESX Server)  once they tasted the power of vmware server.Any company would think,&quot;If a free product like vmware server can give such a good server consolidation ratio &amp; performance,then imagine what ESX could do which was designed from group up keeping performance,availability,resource scheduling &amp; flexibility in mind&quot;....VMware server is just a starting point.....Sky is the limit from there on....

Hope this info has helped you folks!!

Do feel free to email me@(fuseboxvirt@gmail.com) for any queries,suggestions,ideas,assistance in setting up,designing,tuning VMware Server Or ESX at your homes or organizations.Would be glad to assist you.

Thanks.Adios!!</description>
		<content:encoded><![CDATA[<p>Whoever says that,&#8221;VMware Server is not fit for production&#8221; has surely never ever worked with well enough to understand what is going on and last but not least,has no iota of what virtualization/vmware is all about and the way a virtualization solution is put in place.</p>
<p>I have been experimenting,designing &amp; implementing VMWare&#8217;s ESX,ESXi &amp; Server editions for some major,small &amp; startup companies with real good results.Putting a virtualization or vmware solution in place is a whole different ball game.Its all about careful &amp; meticulous design keeping that various performance requirements,bottlenecks,purpose of the VMs,number of users,available hardware,bandwidth,etc,etc&#8230;.Execution or deployment is just 15% and whereas design &amp; system planning phase is 85%.That says it all.I know a case of one huge financial institution which screwed up its virtualization project because of hurrying up the design/system planning phase and directly jumping into implementing it.Ultimately it found itself in a huge mess with huge performance issues and blaming it all on VMware,saying it was not yet ready for mainstream.Later some sense dawned on this company and realized it was their incapability and not VMWare&#8217;s.Now,they are spending huge amounts on undoing everything,redoing the design and implementation all over again from square#1.</p>
<p>In short,what I am trying to say is either VMware Server or ESX/ESXi,they are all awesome technologies in their own sense.But,if you dont get the design&amp; system planning basics right while putting a Vmware Server or ESX server ,no matter how big or great hardware &amp; resources you have,they are all a huge waste and nothing more than a expensive 10k$ paperweight.</p>
<p>I have been personally running VMware Server 2.0 on CentOS 5.2(Final),patched and updated without any sort of issues,at my home.This has 6gb of RAM,2 x 640GB sata2 drives and a AMD Phenom Quad core CPU.In the Admin world,this machine would be compared to a midlevel gaming pc.But,you will be surprised to know that this is running 11 VMs at this point and all are up &amp; running without any performance issues.6 are linux,2 Solaris 10,1 Vista,1 Windows server 2008 enterprise and all are running 64bit OS,since this physical cpu has AMD-V enabled.I am also running SAP Netweaver 2004s in one of the linux machines and Oracle 10g RAC simulation on 2 of the VMs,10gR2 on Solaris 10.</p>
<p>Coming to the way,I setup the filesystems or drives or CentOS installation.Like, Brian rightly pointed out,I am running a minimal install(although I have GNOME installed)but running it in run level 3 and disabled un-needed services and only 3-4 services are running.I have no onboard hardware raid as this is not a high end pc or entry level server.So,I am using software raid available in Centos and setup the RAID partitions according to my performance or redundancy needs.For example,VMs which can afford to go down even if one of the datastore filesystem(s) goes down,but need speed over redundancy,I chose to use RAID 0 with an EXT2 formatting.For VMs,which need redundancy over speed and cannot afford to be lost for a filesystem corruption or disk crash,I chose to go with RAID1 with EXT3.My SAP and Win 2008 server have their own dedicated datastores/filesystems and I chose speed over redundancy in both their cases as SAP is pretty IO intensive.So,I used RAID 0 with EXT2 with a bigger chunk size on the RAID level &amp; bigger block sizes on the filesystem level.</p>
<p>Moreover,I make sure I allocate all the disk space upfront while I am creating a VM to give it a performance boost and at the same time avoid defragmentation,which indirectly results in inefficient IO seeks &amp; burden on the kernel ultimately affecting end performance which will have a domino effect on all the VMs in that filesystem.Before,I create my first VM,I make sure the kernel &amp; system parameters,swap ,shared mem params are tuned to requirements &amp; to optimal values to reduce the possibilities of any bottlenecks in the first place.In short,better to be PROACTIVE rather than be REACTIVE &amp; regret later.</p>
<p>This is just a tip of the iceberg,this small setup itself can be tuned,designed in multiple ways depending upon your needs and requirements.Its all about understanding the requirements clearly.That&#8217;s the first step for a successful vmware solution.And,trust me VMWare Server 1.x/2.x is a peach of a product,especially when you see its capabilities with the right design/hardware and absolutely at no licensing cost.It may be free of licensing costs,but that doesnt mean its inferior or cannot handle production.One shouldnt compare it with ESX/ESXi server,as that a whole different ball game when you really get into it.You will obviously getfor a 15grand a cutting/bleeding edge technology which can run on bare metal hardware with absolutely negligible overhead &amp; footprint.Whereas,VMware server is running on top of a OS as an application.Now,the beauty is,inspite of that with careful but simple design ,one can churn out immense power,performance with it and can peacefully run handful of decent production VMs.So,compare apples to apples and not apples to oranges,which is not totally fair.</p>
<p>In the first place,the very reason vmware server is free with not licensing strings attached is,VMWARE wants people or companies(Big/Small) to have a taste of what it could achieve and the whole objective is to entice the companies to buy the REAL DEAL (ESX Server)  once they tasted the power of vmware server.Any company would think,&#8221;If a free product like vmware server can give such a good server consolidation ratio &amp; performance,then imagine what ESX could do which was designed from group up keeping performance,availability,resource scheduling &amp; flexibility in mind&#8221;&#8230;.VMware server is just a starting point&#8230;..Sky is the limit from there on&#8230;.</p>
<p>Hope this info has helped you folks!!</p>
<p>Do feel free to email me@(fuseboxvirt@gmail.com) for any queries,suggestions,ideas,assistance in setting up,designing,tuning VMware Server Or ESX at your homes or organizations.Would be glad to assist you.</p>
<p>Thanks.Adios!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Randy Robertson</title>
		<link>http://www.briandowney.net/blog/2007/03/30/vmware-server-in-production/comment-page-1/#comment-338</link>
		<dc:creator>Randy Robertson</dc:creator>
		<pubDate>Wed, 06 Aug 2008 04:33:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.briandowney.net/blog/2007/03/30/vmware-server-in-production/#comment-338</guid>
		<description>To previous poster, yes I think you can do any arbitrary configuration using VMware Server, but ESXi is now free, so I would use that if your hardware supports if for lots of reasons.</description>
		<content:encoded><![CDATA[<p>To previous poster, yes I think you can do any arbitrary configuration using VMware Server, but ESXi is now free, so I would use that if your hardware supports if for lots of reasons.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David George</title>
		<link>http://www.briandowney.net/blog/2007/03/30/vmware-server-in-production/comment-page-1/#comment-335</link>
		<dc:creator>David George</dc:creator>
		<pubDate>Mon, 28 Jul 2008 22:09:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.briandowney.net/blog/2007/03/30/vmware-server-in-production/#comment-335</guid>
		<description>Brian,

Excellent article.  Thank you for sharing.
My experience: DOS 3.2 --&gt; Win2k3, the last 10 years as a server admin at the corporate enterprise level.  Beginner in Linux (very green)
My last two engagements were building large ESX farms attached to fiber and IP SANs.  I now find myself doing some work for a small company and I have little budget.  Thus I&#039;ve built the following:
- Dell PowerEdge R900, 32 Gig RAM, 8x 146 Gig SAS (all RAID 10, single container) purchased through Dell Outlet for under $7K (2K cheaper than a white box and half the cost of a &quot;new&quot; R900)
- Ubuntu 8.04.1 64 Server (free)
- VMware server 1.0.6.9 (free)
Never heard of CentOS until this post.
Here&#039;s my question: Within ESX I can trunk multiple ports and have my VMs run their own IPs (DHCP or static) accross this.  Can I do this within VMware Server?

Please reply to my email address as I rarely visit these posting boards.
Your time and effort are greatly appreciated.

Thanks,

David</description>
		<content:encoded><![CDATA[<p>Brian,</p>
<p>Excellent article.  Thank you for sharing.<br />
My experience: DOS 3.2 &#8211;&gt; Win2k3, the last 10 years as a server admin at the corporate enterprise level.  Beginner in Linux (very green)<br />
My last two engagements were building large ESX farms attached to fiber and IP SANs.  I now find myself doing some work for a small company and I have little budget.  Thus I&#8217;ve built the following:<br />
- Dell PowerEdge R900, 32 Gig RAM, 8x 146 Gig SAS (all RAID 10, single container) purchased through Dell Outlet for under $7K (2K cheaper than a white box and half the cost of a &#8220;new&#8221; R900)<br />
- Ubuntu 8.04.1 64 Server (free)<br />
- VMware server 1.0.6.9 (free)<br />
Never heard of CentOS until this post.<br />
Here&#8217;s my question: Within ESX I can trunk multiple ports and have my VMs run their own IPs (DHCP or static) accross this.  Can I do this within VMware Server?</p>
<p>Please reply to my email address as I rarely visit these posting boards.<br />
Your time and effort are greatly appreciated.</p>
<p>Thanks,</p>
<p>David</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: subramanian</title>
		<link>http://www.briandowney.net/blog/2007/03/30/vmware-server-in-production/comment-page-1/#comment-315</link>
		<dc:creator>subramanian</dc:creator>
		<pubDate>Wed, 23 Apr 2008 08:58:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.briandowney.net/blog/2007/03/30/vmware-server-in-production/#comment-315</guid>
		<description>Hi Brian

Can you please point me to an article on how to configure mainframe on vmware ?
My host operating system is windows XP Professional.</description>
		<content:encoded><![CDATA[<p>Hi Brian</p>
<p>Can you please point me to an article on how to configure mainframe on vmware ?<br />
My host operating system is windows XP Professional.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JR</title>
		<link>http://www.briandowney.net/blog/2007/03/30/vmware-server-in-production/comment-page-1/#comment-310</link>
		<dc:creator>JR</dc:creator>
		<pubDate>Fri, 04 Apr 2008 15:30:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.briandowney.net/blog/2007/03/30/vmware-server-in-production/#comment-310</guid>
		<description>Great article, Brian. That&#039;s the re-assurance I was looking for as I finish prepping a Dell PE2900 for VMware Server (with Ubuntu 6.06 as host OS, as opposed to CentOS) and a couple of slim virtual machines (primarily for ZCS, DNS, and Apache2). I was scouring blogs for some user-detailed examples of successful implementation and the TLF project sounded great! Much appreciated.</description>
		<content:encoded><![CDATA[<p>Great article, Brian. That&#8217;s the re-assurance I was looking for as I finish prepping a Dell PE2900 for VMware Server (with Ubuntu 6.06 as host OS, as opposed to CentOS) and a couple of slim virtual machines (primarily for ZCS, DNS, and Apache2). I was scouring blogs for some user-detailed examples of successful implementation and the TLF project sounded great! Much appreciated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aregnier42</title>
		<link>http://www.briandowney.net/blog/2007/03/30/vmware-server-in-production/comment-page-1/#comment-307</link>
		<dc:creator>aregnier42</dc:creator>
		<pubDate>Tue, 04 Mar 2008 08:48:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.briandowney.net/blog/2007/03/30/vmware-server-in-production/#comment-307</guid>
		<description>interesting article!

I&#039;ve been messing around a lot with vmware server and centos 5.1 over the last few days and I have a problem... Maybe you have ideas about it.

configuration is 
host: centos 5.1 64 bits on a dell 1950 (2 cpu with 2 core each)
guest: centos 5.1 64 bits smp (2 vcpu)


The bottom line is that I&#039;m able to get the load average very high inside the guest, but the the load average on the host doesn&#039;t go over 2... any idea why?

The real problem is that performance inside the vm are way lower than it would directly on the host... (like 10 times less work done) And this is not a memory issue.

thanks for any advice.</description>
		<content:encoded><![CDATA[<p>interesting article!</p>
<p>I&#8217;ve been messing around a lot with vmware server and centos 5.1 over the last few days and I have a problem&#8230; Maybe you have ideas about it.</p>
<p>configuration is<br />
host: centos 5.1 64 bits on a dell 1950 (2 cpu with 2 core each)<br />
guest: centos 5.1 64 bits smp (2 vcpu)</p>
<p>The bottom line is that I&#8217;m able to get the load average very high inside the guest, but the the load average on the host doesn&#8217;t go over 2&#8230; any idea why?</p>
<p>The real problem is that performance inside the vm are way lower than it would directly on the host&#8230; (like 10 times less work done) And this is not a memory issue.</p>
<p>thanks for any advice.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian</title>
		<link>http://www.briandowney.net/blog/2007/03/30/vmware-server-in-production/comment-page-1/#comment-304</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Thu, 14 Feb 2008 20:48:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.briandowney.net/blog/2007/03/30/vmware-server-in-production/#comment-304</guid>
		<description>Hi Rick.

First, a bit of a disclaimer--I&#039;ve never used Vmware Server on a Windows Host, only Linux ones.   So YMMV.

My instant guess based on what you told me is disk latency.  

But first of all, if you haven&#039;t already--install the Vmware Server MUI on your machine, and take a look at it.  You&#039;ll probably notice that the VM&#039;s that you&#039;ve allocated a full 512 megs to aren&#039;t actually using anything close to that.   I very rarely see a VM actually /need/ 512M of RAM allocated.  Adjust them accordingly.

Here&#039;s the reason this is important:  On Vmware (of any rendition), your single biggest performance hurdle will always be I/O wait on disk operations.  But on Vmware Server, tuning your VM&#039;s to allocate approximately the memory they&#039;re actually using allows your Host OS use more of that RAM for disk cache, which is a good thing considering the size of the .vmdk files usually involved.

That would be my initial suggestion--see how your RAM is allocated, and free up what you can back to the Host OS.  1GB free isn&#039;t a whole lot for both Windows and a disk cache.

Additionally, it would be helpful to know the setup on the 2900.  If you haven&#039;t already, mirror the drives and use a PERC that has built-in cache on it.  

But as far as Vmware Server not being used in production, it&#039;s hogwash.  We&#039;ve got 4 years of it under our belt at TLF--and *yet* have had it flake out.  But sure, ESX is preferable of course, if you can actually afford it.</description>
		<content:encoded><![CDATA[<p>Hi Rick.</p>
<p>First, a bit of a disclaimer&#8211;I&#8217;ve never used Vmware Server on a Windows Host, only Linux ones.   So YMMV.</p>
<p>My instant guess based on what you told me is disk latency.  </p>
<p>But first of all, if you haven&#8217;t already&#8211;install the Vmware Server MUI on your machine, and take a look at it.  You&#8217;ll probably notice that the VM&#8217;s that you&#8217;ve allocated a full 512 megs to aren&#8217;t actually using anything close to that.   I very rarely see a VM actually /need/ 512M of RAM allocated.  Adjust them accordingly.</p>
<p>Here&#8217;s the reason this is important:  On Vmware (of any rendition), your single biggest performance hurdle will always be I/O wait on disk operations.  But on Vmware Server, tuning your VM&#8217;s to allocate approximately the memory they&#8217;re actually using allows your Host OS use more of that RAM for disk cache, which is a good thing considering the size of the .vmdk files usually involved.</p>
<p>That would be my initial suggestion&#8211;see how your RAM is allocated, and free up what you can back to the Host OS.  1GB free isn&#8217;t a whole lot for both Windows and a disk cache.</p>
<p>Additionally, it would be helpful to know the setup on the 2900.  If you haven&#8217;t already, mirror the drives and use a PERC that has built-in cache on it.  </p>
<p>But as far as Vmware Server not being used in production, it&#8217;s hogwash.  We&#8217;ve got 4 years of it under our belt at TLF&#8211;and *yet* have had it flake out.  But sure, ESX is preferable of course, if you can actually afford it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick</title>
		<link>http://www.briandowney.net/blog/2007/03/30/vmware-server-in-production/comment-page-1/#comment-303</link>
		<dc:creator>Rick</dc:creator>
		<pubDate>Wed, 13 Feb 2008 17:26:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.briandowney.net/blog/2007/03/30/vmware-server-in-production/#comment-303</guid>
		<description>Hi Brian,
I am at my ropes end with an issue I am having hopefully you can help me with sort out the fact from fiction, and guide me in the right direction.

I am running VMware  Server 1.04 on a Dell Poweredge 2900 box with Win2K3 R2 Standard with 4Gb ram. I have Netware 6.5 with Groupwise7 running on one VM(1Gb mem assigned, SpamTitan on another VM(512Mb), and BES server running on another VM(512Mb).

My users are complaining of latency issues or hangs when opening emails in Outlook 2003. If they use the GW client, the emails open instaneously.

The bosses called in a consultant to look at the setup. He told them the setup of NW and GW is perfect. The only issue he has is with VMware.

He said this:
1)VMware server was never meant to be put in production. He recommends going to ESX.
2)There is not enough memory on the box, that we should add 4 to 8Gb more.

Can Vmware server be put in production? It replaced the GSX product and it WAS made to run in a production environment...

As for the memory, I would have to install the 64bit version of Windows to take advantage of the extra memory...

What are your thoughts or suggestions?

Any input is greatly appreciated. No one seems to be able to give me a straight answer. I spoke to 2 people at Vmware- one said yes, it could be run in production. Another said no, to go with ESX.

Thanks,
Rick</description>
		<content:encoded><![CDATA[<p>Hi Brian,<br />
I am at my ropes end with an issue I am having hopefully you can help me with sort out the fact from fiction, and guide me in the right direction.</p>
<p>I am running VMware  Server 1.04 on a Dell Poweredge 2900 box with Win2K3 R2 Standard with 4Gb ram. I have Netware 6.5 with Groupwise7 running on one VM(1Gb mem assigned, SpamTitan on another VM(512Mb), and BES server running on another VM(512Mb).</p>
<p>My users are complaining of latency issues or hangs when opening emails in Outlook 2003. If they use the GW client, the emails open instaneously.</p>
<p>The bosses called in a consultant to look at the setup. He told them the setup of NW and GW is perfect. The only issue he has is with VMware.</p>
<p>He said this:<br />
1)VMware server was never meant to be put in production. He recommends going to ESX.<br />
2)There is not enough memory on the box, that we should add 4 to 8Gb more.</p>
<p>Can Vmware server be put in production? It replaced the GSX product and it WAS made to run in a production environment&#8230;</p>
<p>As for the memory, I would have to install the 64bit version of Windows to take advantage of the extra memory&#8230;</p>
<p>What are your thoughts or suggestions?</p>
<p>Any input is greatly appreciated. No one seems to be able to give me a straight answer. I spoke to 2 people at Vmware- one said yes, it could be run in production. Another said no, to go with ESX.</p>
<p>Thanks,<br />
Rick</p>
]]></content:encoded>
	</item>
</channel>
</rss>
