<?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: Installing VMware tools without a reboot?</title>
	<atom:link href="http://www.yellow-bricks.com/2008/11/27/installing-vmware-tools-without-a-reboot/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.yellow-bricks.com/2008/11/27/installing-vmware-tools-without-a-reboot/</link>
	<description>Building blocks for virtualization...</description>
	<lastBuildDate>Fri, 19 Mar 2010 14:22:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: halr9000</title>
		<link>http://www.yellow-bricks.com/2008/11/27/installing-vmware-tools-without-a-reboot/comment-page-1/#comment-1846</link>
		<dc:creator>halr9000</dc:creator>
		<pubDate>Thu, 27 Nov 2008 18:30:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.yellow-bricks.com/?p=1065#comment-1846</guid>
		<description>Well to me the point of the script was never in question.  I, as a the system administrator, want to control when a system is rebooted.  A software install should always provide options to suppress reboots during unattended installs.  Why?  Because I would want to bundle multiple installs (more than one of which could require a reboot) into one batch job--and then reboot when complete.

As to the other point about whether a reboot  is truly required, that is very often...due to software vendors being (overly) conservative. You see, they have to make an install as robust as possible so as to prevent as many tech support calls as possible. 

So anyway, I&#039;m not saying that the VM Tools do not require a reboot, but just that I want to have that control. That was the point all along as far as I&#039;m concerned.</description>
		<content:encoded><![CDATA[<p>Well to me the point of the script was never in question.  I, as a the system administrator, want to control when a system is rebooted.  A software install should always provide options to suppress reboots during unattended installs.  Why?  Because I would want to bundle multiple installs (more than one of which could require a reboot) into one batch job&#8211;and then reboot when complete.</p>
<p>As to the other point about whether a reboot  is truly required, that is very often&#8230;due to software vendors being (overly) conservative. You see, they have to make an install as robust as possible so as to prevent as many tech support calls as possible. </p>
<p>So anyway, I&#8217;m not saying that the VM Tools do not require a reboot, but just that I want to have that control. That was the point all along as far as I&#8217;m concerned.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: moosethumbs</title>
		<link>http://www.yellow-bricks.com/2008/11/27/installing-vmware-tools-without-a-reboot/comment-page-1/#comment-1845</link>
		<dc:creator>moosethumbs</dc:creator>
		<pubDate>Thu, 27 Nov 2008 15:45:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.yellow-bricks.com/?p=1065#comment-1845</guid>
		<description>I&#039;ve been trying to get this script to work myself, so I&#039;m happy to see it updated!  Here are my personal reasons for wanting to do this...  We have 1600 VMs or so, and we need to update tools on basically all of them.  The problem with letting them reboot is that all the VMs have a reboot/maint window once per month, otherwise I have to coordinate with all the server owners for the downtime, and then create change requests and get approval for them.  Also, my team doesn&#039;t have an easy way of tracking down the window for each VM because that is managed by a different team!  If I can upgrade tools without rebooting, I&#039;m hoping I can do 1 change request, fire off the script and let the monthly reboot do the dirty work.

I did not think about the network connections dropping though, so that may throw a kink in my plans anyway.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been trying to get this script to work myself, so I&#8217;m happy to see it updated!  Here are my personal reasons for wanting to do this&#8230;  We have 1600 VMs or so, and we need to update tools on basically all of them.  The problem with letting them reboot is that all the VMs have a reboot/maint window once per month, otherwise I have to coordinate with all the server owners for the downtime, and then create change requests and get approval for them.  Also, my team doesn&#8217;t have an easy way of tracking down the window for each VM because that is managed by a different team!  If I can upgrade tools without rebooting, I&#8217;m hoping I can do 1 change request, fire off the script and let the monthly reboot do the dirty work.</p>
<p>I did not think about the network connections dropping though, so that may throw a kink in my plans anyway.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Jacobs</title>
		<link>http://www.yellow-bricks.com/2008/11/27/installing-vmware-tools-without-a-reboot/comment-page-1/#comment-1844</link>
		<dc:creator>Tim Jacobs</dc:creator>
		<pubDate>Thu, 27 Nov 2008 14:51:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.yellow-bricks.com/?p=1065#comment-1844</guid>
		<description>Hi Duncan,

I was also under the impression that installing device drivers automatically requires a reboot of your virtual machine. Apparently this is not true and only a very specific type of device drivers actually require a reboot to be properly reloaded (amongst others if you update the storage driver that is used by your boot device). I&#039;ve recently written some thoughts about the VMware Tools upgrade (see my blog). 

Nevertheless, I totally agree with your suspicion regarding these suppress-reboot scripts.</description>
		<content:encoded><![CDATA[<p>Hi Duncan,</p>
<p>I was also under the impression that installing device drivers automatically requires a reboot of your virtual machine. Apparently this is not true and only a very specific type of device drivers actually require a reboot to be properly reloaded (amongst others if you update the storage driver that is used by your boot device). I&#8217;ve recently written some thoughts about the VMware Tools upgrade (see my blog). </p>
<p>Nevertheless, I totally agree with your suspicion regarding these suppress-reboot scripts.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
