<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Clearspace Server Syndication Feed</title>
    <link>http://communities.vmware.com/blogs</link>
    <description>A syndication feed of all the blogs on this system</description>
    <pubDate>Fri, 06 Nov 2009 20:40:33 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2009-11-06T20:40:33Z</dc:date>
    <item>
      <title>How to Reduce Replication Traffic in a VMware SRM Configuration</title>
      <link>http://communities.vmware.com/blogs/trevordavis/2009/11/06/how-to-reduce-replication-traffic-in-a-vmware-srm-configuration</link>
      <description>See Attached</description>
      <pubDate>Fri, 06 Nov 2009 20:40:33 GMT</pubDate>
      <author>Trevor Davis</author>
      <guid>http://communities.vmware.com/blogs/trevordavis/2009/11/06/how-to-reduce-replication-traffic-in-a-vmware-srm-configuration</guid>
      <dc:date>2009-11-06T20:40:33Z</dc:date>
      <wfw:comment>http://communities.vmware.com/blogs/trevordavis/comment/how-to-reduce-replication-traffic-in-a-vmware-srm-configuration</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/trevordavis/feeds/comments?blogPostID=5196</wfw:commentRss>
    </item>
    <item>
      <title>RVTools</title>
      <link>http://communities.vmware.com/blogs/cfo/2009/11/06/rvtools</link>
      <description>RVTools is a small .NET 2.0 application which uses the VI SDK to display information about your virtual machines. Interacting with VirtualCenter 2.x or ESX 3.x RVTools is able to list information about cpu, memory, disks, nics, cd-rom, floppy drives, snapshots, VMware tools, ESX hosts, datastores and health checks. With RVTools you can disconnect the cd-rom or floppy drives from the virtual machines and RVTools is able to list the current version of the VMware Tools installed inside each virtual machine. and update them to the latest version. &lt;br /&gt;
&lt;br /&gt;
&lt;a class="jive-link-external" href="http://rvtools.deveij.com/"&gt;http://rvtools.deveij.com/&lt;/a&gt;</description>
      <pubDate>Fri, 06 Nov 2009 14:25:38 GMT</pubDate>
      <author>cfo</author>
      <guid>http://communities.vmware.com/blogs/cfo/2009/11/06/rvtools</guid>
      <dc:date>2009-11-06T14:25:38Z</dc:date>
      <wfw:comment>http://communities.vmware.com/blogs/cfo/comment/rvtools</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/cfo/feeds/comments?blogPostID=5195</wfw:commentRss>
    </item>
    <item>
      <title>necklace for your Wedding Day</title>
      <link>http://communities.vmware.com/blogs/necklace/2009/11/05/necklace-for-your-wedding-day</link>
      <description>&lt;br /&gt;
So your big day is approaching and you would like to present either&lt;br /&gt;
your future spouse or your wedding party with a stunning piece of&lt;br /&gt;
jewelry as a wedding gift.Preparations often seem to focus around the&lt;br /&gt;
dress, but there are many other elements of your look to&lt;br /&gt;
consider.Purchase identical gifts, but in varying colors, for your&lt;br /&gt;
bridesmaids. Tennis &lt;a class="jive-link-external" href="http://community.wgntv.com/service/linkOut.kickAction?as=101892&amp;#38;url=http%3A%2F%2Fcommunity2.myfoxaustin.com%2Fservice%2FlinkOut.kickAction%3Fas%3D82263%26amp%3Burl%3Dhttp%253A%252F%252Fwww.bjbead.com%252Fnecklace%252F%26amp%3Bh%3D6bf7ce86516af59cbcd57652c418b355&amp;#38;h=2c7cbbe1528dc2edd4112592fbac3d1"&gt;necklace&lt;/a&gt; in each of their birthstones, or perhaps stones that match their dress colors, make perfect reminders of the day.&lt;br /&gt;
&lt;p /&gt;
Although all eyes will be glued to the beauty and symbolism of your&lt;br /&gt;
wedding ring, other jewelry will round out your bridal look. Depending&lt;br /&gt;
on your personal preferences, the cut of your dress and the style of&lt;br /&gt;
your hair, you may opt for a necklace, bracelet or earrings.&lt;br /&gt;
Coordination of gemstones is key, as are the jewel tones you choose.&lt;br /&gt;
&lt;p /&gt;
Pearls are a traditional &lt;b&gt;wedding jewelry&lt;/b&gt;  for both brides and bridesmaids. Pearls are available in all forms, but necklaces and &lt;a class="jive-link-external" href="http://community.wgntv.com/service/linkOut.kickAction?as=101892&amp;#38;url=http%3A%2F%2Fcommunity2.myfoxaustin.com%2Fservice%2FlinkOut.kickAction%3Fas%3D82263%26amp%3Burl%3Dhttp%253A%252F%252Fwww.bjbead.com%252Fearrings%252F%26amp%3Bh%3Dbdf5d58e9b97676a61b314a34cc54cf3&amp;#38;h=618e3850fbc21cce36a1b438ef181d7"&gt;earrings&lt;/a&gt;&lt;br /&gt;
are the more popular options.Giving jewelry such as a necklace is a&lt;br /&gt;
tradition when it comes to wedding presents. The bride&amp;rsquo;s mother or the&lt;br /&gt;
groom may give her something special, or she may give jewelry to her&lt;br /&gt;
bridesmaids.&lt;br /&gt;
&lt;p /&gt;
&lt;img src="http://www.bjbead.com/pic1/new_jewelry/D1192_2.jpg" alt="http://www.bjbead.com/pic1/new_jewelry/D1192_2.jpg" class="jive-image"  /&gt;&lt;br /&gt;
&lt;p /&gt;
Opt for a necklace that complements the cut of your dress. A pearl&lt;br /&gt;
or rhinestone choker works well with a strapless bodice, whereas a&lt;br /&gt;
diamond solitaire will look stunning with a V or sweetheart neckline.&lt;br /&gt;
&lt;p /&gt;
Let your hairstyle, necklace dictate the earrings you choose.&lt;br /&gt;
Harmonize the gemstones found in your dress or headpiece with those in&lt;br /&gt;
your jewelry. Pearls will complement beading, whereas diamonds or&lt;br /&gt;
zirconia go well with sequins or crystals.&lt;br /&gt;
&lt;p /&gt;
Bridal necklaces are as important as your wedding gown and your&lt;br /&gt;
wedding shoes because they add beauty and elegance to whatever wedding&lt;br /&gt;
dress you plan to pick for your wedding day.</description>
      <category domain="http://communities.vmware.com/blogs/tags">necklace</category>
      <category domain="http://communities.vmware.com/blogs/tags">fashion</category>
      <pubDate>Fri, 06 Nov 2009 01:37:57 GMT</pubDate>
      <author>Briace</author>
      <guid>http://communities.vmware.com/blogs/necklace/2009/11/05/necklace-for-your-wedding-day</guid>
      <dc:date>2009-11-06T01:37:57Z</dc:date>
      <wfw:comment>http://communities.vmware.com/blogs/necklace/comment/necklace-for-your-wedding-day</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/necklace/feeds/comments?blogPostID=5194</wfw:commentRss>
    </item>
    <item>
      <title>Top things you MUST do after 9.10 upgrade or install</title>
      <link>http://communities.vmware.com/blogs/ecrossley/2009/11/05/top-things-you-must-do-after-910-upgrade-or-install</link>
      <description>Great read over here:  &lt;a class="jive-link-external" href="http://blog.thesilentnumber.me/2009/09/top-things-to-do-after-installing.html"&gt;http://blog.thesilentnumber.me/2009/09/top-things-to-do-after-installing.html&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
Check out some of the key things you must do once you upgrade your system to 9.10 (or rebuild it from scratch).</description>
      <category domain="http://communities.vmware.com/blogs/tags">64bit</category>
      <category domain="http://communities.vmware.com/blogs/tags">laptop</category>
      <category domain="http://communities.vmware.com/blogs/tags">linux</category>
      <category domain="http://communities.vmware.com/blogs/tags">ubuntu</category>
      <pubDate>Thu, 05 Nov 2009 18:51:12 GMT</pubDate>
      <author>ecrossley</author>
      <guid>http://communities.vmware.com/blogs/ecrossley/2009/11/05/top-things-you-must-do-after-910-upgrade-or-install</guid>
      <dc:date>2009-11-05T18:51:12Z</dc:date>
      <wfw:comment>http://communities.vmware.com/blogs/ecrossley/comment/top-things-you-must-do-after-910-upgrade-or-install</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/ecrossley/feeds/comments?blogPostID=5192</wfw:commentRss>
    </item>
    <item>
      <title>VMware Workstation 7 on Ubuntu 64</title>
      <link>http://communities.vmware.com/blogs/ecrossley/2009/11/05/vmware-workstation-7-on-ubuntu-64</link>
      <description>Workstation 7 is FANTASTIC on Ubuntu 64.  I'm so excited about this new workstation release as it provides many additional features over WS 6.5.&lt;br /&gt;
&lt;br /&gt;
1) Sockets / Core selection - You can now set number of sockets and cores per socket to your individual workstation vm's.&lt;br /&gt;
2) Compacting of VM disk files can be done from workstation.&lt;br /&gt;
3) Encryption of Workstation VM's can now be done preventing access into VM's without proper credentials.&lt;br /&gt;
4) Windows 7 support&lt;br /&gt;
&lt;br /&gt;
These are just a few of the options that are available, as well as, the ability to run nested ESX environments inside of Workstation 7.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;If you are installing workstation for the first time on Ubuntu 64, you MUST execute the vmnetset script (&lt;a class="jive-link-external" href="http://communities.vmware.com/blogs/ecrossley/2009/06/29/ubuntu-and-vmware-workstation-networking"&gt;http://communities.vmware.com/blogs/ecrossley/2009/06/29/ubuntu-and-vmware-workstation-networking&lt;/a&gt;) from this blog in order to allow promiscuous mode for your ethernet adapters&lt;/b&gt;</description>
      <category domain="http://communities.vmware.com/blogs/tags">vmnet</category>
      <category domain="http://communities.vmware.com/blogs/tags">laptop</category>
      <category domain="http://communities.vmware.com/blogs/tags">linux</category>
      <category domain="http://communities.vmware.com/blogs/tags">ubuntu</category>
      <category domain="http://communities.vmware.com/blogs/tags">workstation</category>
      <pubDate>Thu, 05 Nov 2009 17:41:34 GMT</pubDate>
      <author>ecrossley</author>
      <guid>http://communities.vmware.com/blogs/ecrossley/2009/11/05/vmware-workstation-7-on-ubuntu-64</guid>
      <dc:date>2009-11-05T17:41:34Z</dc:date>
      <wfw:comment>http://communities.vmware.com/blogs/ecrossley/comment/vmware-workstation-7-on-ubuntu-64</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/ecrossley/feeds/comments?blogPostID=5191</wfw:commentRss>
    </item>
    <item>
      <title>VMware View Open Client on 64 bit</title>
      <link>http://communities.vmware.com/blogs/ecrossley/2009/11/05/vmware-view-open-client-on-64-bit</link>
      <description>Great article over at Cosmic Egg about open source view client on 64 bit linux.  I've been slacking on the blog, so enjoy the read.&lt;br /&gt;
&lt;br /&gt;
&lt;a class="jive-link-external" href="http://blog.cosmicegg.net/2009/10/vmware-view-open-client-on-64-bit.html"&gt;http://blog.cosmicegg.net/2009/10/vmware-view-open-client-on-64-bit.html&lt;/a&gt;</description>
      <category domain="http://communities.vmware.com/blogs/tags">view</category>
      <category domain="http://communities.vmware.com/blogs/tags">linux</category>
      <category domain="http://communities.vmware.com/blogs/tags">ubuntu</category>
      <category domain="http://communities.vmware.com/blogs/tags">64bit</category>
      <pubDate>Thu, 05 Nov 2009 17:39:51 GMT</pubDate>
      <author>ecrossley</author>
      <guid>http://communities.vmware.com/blogs/ecrossley/2009/11/05/vmware-view-open-client-on-64-bit</guid>
      <dc:date>2009-11-05T17:39:51Z</dc:date>
      <wfw:comment>http://communities.vmware.com/blogs/ecrossley/comment/vmware-view-open-client-on-64-bit</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/ecrossley/feeds/comments?blogPostID=5189</wfw:commentRss>
    </item>
    <item>
      <title>Discuss "SAP on VMware" at SAP Community Network</title>
      <link>http://communities.vmware.com/blogs/SAPsolutions/2009/11/05/discuss-sap-on-vmware-at-sap-community-network</link>
      <description>If you are a user of SAP Community Network, then you might have already seen the new forum about "&lt;a class="jive-link-external" href="http://forums.sdn.sap.com/forum.jspa?forumID=471"&gt;SAP on VMware&lt;/a&gt;" which is live since Oct 21. The forum creates a platform for customers where answers to minor technical questions can be adressed or discussions about best practices, configurations, etc. can take place. You can find the forum right &lt;a class="jive-link-external" href="http://forums.sdn.sap.com/forum.jspa?forumID=471"&gt;here&lt;/a&gt;: &lt;br /&gt;
&lt;br /&gt;
&lt;span style="font-size:10pt"&gt;&lt;a class="jive-link-external" href="http://forums.sdn.sap.com/forum.jspa?forumID=471"&gt;http://forums.sdn.sap.com/forum.jspa?forumID=471&lt;/a&gt;&lt;/span&gt;</description>
      <category domain="http://communities.vmware.com/blogs/tags">sap_community_network</category>
      <category domain="http://communities.vmware.com/blogs/tags">sdn</category>
      <category domain="http://communities.vmware.com/blogs/tags">scn</category>
      <category domain="http://communities.vmware.com/blogs/tags">sap_on_vmware</category>
      <pubDate>Thu, 05 Nov 2009 11:24:41 GMT</pubDate>
      <author>m@t</author>
      <guid>http://communities.vmware.com/blogs/SAPsolutions/2009/11/05/discuss-sap-on-vmware-at-sap-community-network</guid>
      <dc:date>2009-11-05T11:24:41Z</dc:date>
      <wfw:comment>http://communities.vmware.com/blogs/SAPsolutions/comment/discuss-sap-on-vmware-at-sap-community-network</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/SAPsolutions/feeds/comments?blogPostID=5188</wfw:commentRss>
    </item>
    <item>
      <title>We want VMWare on Linux!</title>
      <link>http://communities.vmware.com/blogs/simoncpu/2009/11/05/we-want-vmware-on-linux</link>
      <description>&lt;img src="http://i33.tinypic.com/2qdptfd.jpg" alt="http://i33.tinypic.com/2qdptfd.jpg" class="jive-image"  /&gt;</description>
      <category domain="http://communities.vmware.com/blogs/tags">linux</category>
      <category domain="http://communities.vmware.com/blogs/tags">tux</category>
      <category domain="http://communities.vmware.com/blogs/tags">rants</category>
      <pubDate>Thu, 05 Nov 2009 08:02:39 GMT</pubDate>
      <author>simoncpu</author>
      <guid>http://communities.vmware.com/blogs/simoncpu/2009/11/05/we-want-vmware-on-linux</guid>
      <dc:date>2009-11-05T08:02:39Z</dc:date>
      <wfw:comment>http://communities.vmware.com/blogs/simoncpu/comment/we-want-vmware-on-linux</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/simoncpu/feeds/comments?blogPostID=5187</wfw:commentRss>
    </item>
    <item>
      <title>"Allowing for Future Growth" has reached End-of-life</title>
      <link>http://communities.vmware.com/blogs/vmroyale/2009/11/04/allowing-for-future-growth-has-reached-endoflife</link>
      <description>I was recently involved in a situation where a development group at a SMB was tasked with consolidating two SQL servers into one.  These SQL servers were physical servers running old versions of Windows, with equally old versions of SQL Server, on some pretty old hardware.  The situation became interesting, when the development group put in the specifications request for the new virtual machine. The request was for a 64-bit Windows 2008 server with 8 GB of RAM, 4 vCPUs and over half a TB of FC SAN disk for storage.&lt;br /&gt;
&lt;br /&gt;
This seemed like a bit of a tall order, so the first thing I did was to compare the specifications in the request with the specifications of the current physical servers. Server 1 had two Pentium III 1.2 GHz processors with 512 MB of RAM and 90 GB of used disk space.  Server 2 had two Pentium III 1.0 GHz processors with 2 GB of RAM and 16 GB of used disk space.  Even after ignoring the massive storage difference, the requested numbers didn't match up with the 4 vCPUs and 8 GB RAM specified in the request.  Next I went to the system baselines, thinking that the systems might be overburdened.  The baselines actually revealed that the systems weren't doing much work - 3% CPU average utilization, low disk IOPs, and very low network utilization.  Using the perfmon SQLServer:Memory Manager -&amp;gt; Total Server Memory counter did reveal that the SQL servers were actually using the memory they were allocated. The numbers in the request still didn't add up though, and now with data in-hand, it was time to go talk to the requestors.  &lt;br /&gt;
&lt;br /&gt;
Ultimately it was discovered that this request was submitted this way to "allow for future growth." Many years ago this may have been standard practice with physical hardware, but in today's virtual environments it just no longer makes any sense.  Based on the baseline data, the requested virtual machine could be built with 1 vCPU, 3 GB of memory and less than 100 GB of SATA disk space.  If it turns out that the server actually needs more resources in the future, then these resources may be very quickly added with minimal or even no downtime.  Gone are the days of provisioning everything up front while allowing room for future growth, hoping the server makes it to the next refresh cycle and then repeating the same process over again. To complement the virtual infrastructure, there must be an awareness of the way this technology fundamentally changes how systems are now provisioned. &lt;br /&gt;
&lt;br /&gt;
Thanks for reading!</description>
      <pubDate>Wed, 04 Nov 2009 20:36:23 GMT</pubDate>
      <author>vmroyale</author>
      <guid>http://communities.vmware.com/blogs/vmroyale/2009/11/04/allowing-for-future-growth-has-reached-endoflife</guid>
      <dc:date>2009-11-04T20:36:23Z</dc:date>
      <wfw:comment>http://communities.vmware.com/blogs/vmroyale/comment/allowing-for-future-growth-has-reached-endoflife</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/vmroyale/feeds/comments?blogPostID=5184</wfw:commentRss>
    </item>
  </channel>
</rss>

