<?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>Jonathan Marrott's VM Scripting Blog</title>
    <link>http://communities.vmware.com/blogs/froboy</link>
    <description>A swell blog containing some of the scripts I have written for VM management.</description>
    <pubDate>Fri, 18 Jan 2008 18:32:21 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2008-01-18T18:32:21Z</dc:date>
    <item>
      <title>Enable VMotion on VMKernel port</title>
      <link>http://communities.vmware.com/blogs/froboy/2008/01/18/enable-vmotion-on-vmkernel-port</link>
      <description>This will enable VMotion on a VMKernel port. I am writing this one because it changed between verisons of ESX.  This command uses the very useful vimsh.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;ESX 3.0.x:&lt;/b&gt;&lt;br /&gt;
vimsh -n -e "/hostsvc/vmotion/vnic_set portgroup2"&lt;br /&gt;
portgroup# - Determined by the order of portgroup creation. The system automatically makes one to begin with.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;ESX 3.5:&lt;/b&gt;&lt;br /&gt;
vimsh -n -e "/hostsvc/vmotion/vnic_set vmk0"&lt;br /&gt;
vmk# - Determined by the order of the VMKernel port creation. The first one created is '0'.</description>
      <category domain="http://communities.vmware.com/blogs/froboy/tags">esx</category>
      <category domain="http://communities.vmware.com/blogs/froboy/tags">vimsh</category>
      <category domain="http://communities.vmware.com/blogs/froboy/tags">vmotion</category>
      <category domain="http://communities.vmware.com/blogs/froboy/tags">vmkernel</category>
      <category domain="http://communities.vmware.com/blogs/froboy/tags">script</category>
      <pubDate>Fri, 18 Jan 2008 18:32:00 GMT</pubDate>
      <author>froboy</author>
      <guid>http://communities.vmware.com/blogs/froboy/2008/01/18/enable-vmotion-on-vmkernel-port</guid>
      <dc:date>2008-01-18T18:32:00Z</dc:date>
      <clearspace:dateToText>1 year, 10 months ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
      <wfw:comment>http://communities.vmware.com/blogs/froboy/comment/enable-vmotion-on-vmkernel-port</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/froboy/feeds/comments?blogPostID=1405</wfw:commentRss>
    </item>
    <item>
      <title>DNS - Set Servers (Updated)</title>
      <link>http://communities.vmware.com/blogs/froboy/2008/01/18/dns-set-servers-updated</link>
      <description>Simple script to set DNS servers. This sets muplitle DNS servers while kickstart by default only sets one.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Set DNS servers using vimsh:&lt;/b&gt;&lt;br /&gt;
vimsh -n -e "/hostsvc/net/dns_set --dns-addresses=192.168.0.1,192.168.0.2 --dns-searchdomain=yourdomain.com"&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Set DNS servers by manually creating resolv.conf:&lt;/b&gt;&lt;br /&gt;
cat &amp;gt; /etc/resolv.conf &amp;lt;&amp;lt; EOF1&lt;br /&gt;
&lt;br /&gt;
search yourdomain.com&lt;br /&gt;
nameserver 192.168.0.4&lt;br /&gt;
nameserver 192.168.0.6&lt;br /&gt;
&lt;br /&gt;
EOF1</description>
      <category domain="http://communities.vmware.com/blogs/froboy/tags">vimsh</category>
      <category domain="http://communities.vmware.com/blogs/froboy/tags">dns</category>
      <category domain="http://communities.vmware.com/blogs/froboy/tags">esx</category>
      <category domain="http://communities.vmware.com/blogs/froboy/tags">install</category>
      <category domain="http://communities.vmware.com/blogs/froboy/tags">script</category>
      <pubDate>Fri, 18 Jan 2008 18:22:00 GMT</pubDate>
      <author>froboy</author>
      <guid>http://communities.vmware.com/blogs/froboy/2008/01/18/dns-set-servers-updated</guid>
      <dc:date>2008-01-18T18:22:00Z</dc:date>
      <clearspace:dateToText>2 years, 1 month ago</clearspace:dateToText>
      <wfw:comment>http://communities.vmware.com/blogs/froboy/comment/dns-set-servers-updated</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/froboy/feeds/comments?blogPostID=1055</wfw:commentRss>
    </item>
    <item>
      <title>Set Service Console Memory (Updated)</title>
      <link>http://communities.vmware.com/blogs/froboy/2008/01/18/set-service-console-memory-updated</link>
      <description>The service console memory should be increased if you are running apps other than the default install.  This includes management agents, backups, etc.  Here is a simple command that I ran across to accomplish this.  It requires a reboot to take effect.  I incorporate this in my kickstart script. Don't forget to set your swap partition to be 2x the Service Console memory.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;See Current Setting:&lt;/b&gt;&lt;br /&gt;
&lt;i&gt;The setting shown is in bytes (MB * 1024 * 1024)&lt;/i&gt;&lt;br /&gt;
vimsh -n -e "/hostsvc/memoryinfo"&lt;br /&gt;
serviceConsoleReserved - Current setting&lt;br /&gt;
serviceConsoleReservedCfg - Setting after next reboot&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Set to 800MB with vimsh:&lt;/b&gt;&lt;br /&gt;
vimsh -n -e "/hostsvc/memoryinfo 838860800"&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Set by manual edit of files:&lt;/b&gt;&lt;br /&gt;
mv -f /etc/vmware/esx.conf /tmp/esx.conf.bak&lt;br /&gt;
sed -e 's/boot\/memSize = \"272\"/boot\/memSize = \"512\"/g' /tmp/esx.conf.bak &amp;gt;&amp;gt; /etc/vmware/esx.conf&lt;br /&gt;
&lt;br /&gt;
mv -f /boot/grub/grub.conf /tmp/grub.conf.bak&lt;br /&gt;
sed -e 's/uppermem 277504/uppermem 523264/g' -e 's/mem=272M/mem=512M/g' /tmp/grub.conf.bak &amp;gt;&amp;gt; /boot/grub/grub.conf&lt;br /&gt;
&lt;br /&gt;
If you feel like setting it to the maximum of 800 MB.&lt;br /&gt;
&lt;br /&gt;
mv -f /etc/vmware/esx.conf /tmp/esx.conf.bak&lt;br /&gt;
sed -e 's/boot\/memSize = \"272\"/boot\/memSize = \"800\"/g' /tmp/esx.conf.bak &amp;gt;&amp;gt; /etc/vmware/esx.conf&lt;br /&gt;
&lt;br /&gt;
mv -f /boot/grub/grub.conf /tmp/grub.conf.bak&lt;br /&gt;
sed -e 's/uppermem 277504/uppermem 818176/g' -e 's/mem=272M/mem=800M/g' /tmp/grub.conf.bak &amp;gt;&amp;gt; /boot/grub/grub.conf</description>
      <category domain="http://communities.vmware.com/blogs/froboy/tags">vimsh</category>
      <category domain="http://communities.vmware.com/blogs/froboy/tags">esx</category>
      <category domain="http://communities.vmware.com/blogs/froboy/tags">script</category>
      <category domain="http://communities.vmware.com/blogs/froboy/tags">memory</category>
      <pubDate>Fri, 18 Jan 2008 17:09:00 GMT</pubDate>
      <author>froboy</author>
      <guid>http://communities.vmware.com/blogs/froboy/2008/01/18/set-service-console-memory-updated</guid>
      <dc:date>2008-01-18T17:09:00Z</dc:date>
      <clearspace:dateToText>2 years, 1 month ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
      <wfw:comment>http://communities.vmware.com/blogs/froboy/comment/set-service-console-memory-updated</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/froboy/feeds/comments?blogPostID=1053</wfw:commentRss>
    </item>
  </channel>
</rss>

