<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: splunk in virtual machine in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/splunk-in-virtual-machine/m-p/104285#M183159</link>
    <description>&lt;P&gt;As long as you can give Splunk the disk IO and memory it needs it runs just fine in a VM. Perfect for Dev system.&lt;/P&gt;</description>
    <pubDate>Thu, 29 Mar 2012 13:58:55 GMT</pubDate>
    <dc:creator>ftk</dc:creator>
    <dc:date>2012-03-29T13:58:55Z</dc:date>
    <item>
      <title>splunk in virtual machine</title>
      <link>https://community.splunk.com/t5/Splunk-Search/splunk-in-virtual-machine/m-p/104283#M183157</link>
      <description>&lt;P&gt;I read in splunk doc that we should not use splunk in virtual machine because splunk require more input and outpur.&lt;BR /&gt;
But still can we use virtual machine for splunk for any task?&lt;/P&gt;</description>
      <pubDate>Thu, 29 Mar 2012 13:41:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/splunk-in-virtual-machine/m-p/104283#M183157</guid>
      <dc:creator>kml_uvce</dc:creator>
      <dc:date>2012-03-29T13:41:41Z</dc:date>
    </item>
    <item>
      <title>Re: splunk in virtual machine</title>
      <link>https://community.splunk.com/t5/Splunk-Search/splunk-in-virtual-machine/m-p/104284#M183158</link>
      <description>&lt;P&gt;I don't know where it says that you shouldn't use Splunk in a VM at all? While it's true that there are considerations to make when deploying Splunk on virtual machines, there's nothing stopping you from taking that route. Splunk (the company) themselves even run their main Splunk (the product) installation in VMs (see &lt;A href="http://blogs.splunk.com/2012/02/28/splunkx-splunking-the-enterprise/"&gt;http://blogs.splunk.com/2012/02/28/splunkx-splunking-the-enterprise/&lt;/A&gt; and &lt;A href="http://blogs.splunk.com/2012/03/14/the-splunkx-environment/"&gt;http://blogs.splunk.com/2012/03/14/the-splunkx-environment/&lt;/A&gt; ).&lt;/P&gt;

&lt;P&gt;More information on things to consider when deploying Splunk in virtual machines: &lt;A href="http://www.splunk.com/web_assets/pdfs/secure/Splunk_and_VMware_VMs_Tech_Brief.pdf"&gt;http://www.splunk.com/web_assets/pdfs/secure/Splunk_and_VMware_VMs_Tech_Brief.pdf&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 29 Mar 2012 13:55:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/splunk-in-virtual-machine/m-p/104284#M183158</guid>
      <dc:creator>Ayn</dc:creator>
      <dc:date>2012-03-29T13:55:57Z</dc:date>
    </item>
    <item>
      <title>Re: splunk in virtual machine</title>
      <link>https://community.splunk.com/t5/Splunk-Search/splunk-in-virtual-machine/m-p/104285#M183159</link>
      <description>&lt;P&gt;As long as you can give Splunk the disk IO and memory it needs it runs just fine in a VM. Perfect for Dev system.&lt;/P&gt;</description>
      <pubDate>Thu, 29 Mar 2012 13:58:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/splunk-in-virtual-machine/m-p/104285#M183159</guid>
      <dc:creator>ftk</dc:creator>
      <dc:date>2012-03-29T13:58:55Z</dc:date>
    </item>
    <item>
      <title>Re: splunk in virtual machine</title>
      <link>https://community.splunk.com/t5/Splunk-Search/splunk-in-virtual-machine/m-p/104286#M183160</link>
      <description>&lt;P&gt;Echoing Ayn's advice - it's all about scale and sizing.  Most people oversubscribe their VM estate - especially with the number of network / disk I/O paths per guest.   Splunk (like any other I/O intensive application) can suffer poor performance when the VM environment isn't sized properly or to too far oversubscribed.&lt;/P&gt;</description>
      <pubDate>Thu, 29 Mar 2012 13:59:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/splunk-in-virtual-machine/m-p/104286#M183160</guid>
      <dc:creator>dwaddle</dc:creator>
      <dc:date>2012-03-29T13:59:18Z</dc:date>
    </item>
    <item>
      <title>Re: splunk in virtual machine</title>
      <link>https://community.splunk.com/t5/Splunk-Search/splunk-in-virtual-machine/m-p/104287#M183161</link>
      <description>&lt;P&gt;All about size and scale..&lt;/P&gt;</description>
      <pubDate>Thu, 29 Mar 2012 14:00:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/splunk-in-virtual-machine/m-p/104287#M183161</guid>
      <dc:creator>Drainy</dc:creator>
      <dc:date>2012-03-29T14:00:18Z</dc:date>
    </item>
    <item>
      <title>Re: splunk in virtual machine</title>
      <link>https://community.splunk.com/t5/Splunk-Search/splunk-in-virtual-machine/m-p/104288#M183162</link>
      <description>&lt;P&gt;Also, there is a big difference between installing a full Splunk server on a VM (for the reasons mentioned above), and installing a forwarder on a virtual host sending the logs elsewhere, which is perfectly fine under almost any circumstance.&lt;/P&gt;

&lt;P&gt;/k&lt;/P&gt;</description>
      <pubDate>Mon, 02 Apr 2012 20:54:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/splunk-in-virtual-machine/m-p/104288#M183162</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2012-04-02T20:54:28Z</dc:date>
    </item>
  </channel>
</rss>

