<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="http://feeds.feedburner.com/~d/styles/rss2full.xsl" type="text/xsl" media="screen"?><?xml-stylesheet href="http://feeds.feedburner.com/~d/styles/itemcontent.css" type="text/css" media="screen"?><rss 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" version="2.0">
<channel>
	<title>Comments for Far Fewer Toes</title>
	
	<link>http://farfewertoes.com</link>
	<description>Ten toes is overrated</description>
	<pubDate>Sat, 11 Oct 2008 01:46:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/farfewertoescomments" type="application/rss+xml" /><item>
		<title>Comment on Start VirtualBox virtual machines on boot by Jochem</title>
		<link>http://farfewertoes.com/stories/2008-03-09-start-virtualbox-virtual-machines-on-boot/#comment-68</link>
		<dc:creator>Jochem</dc:creator>
		<pubDate>Fri, 10 Oct 2008 19:19:28 +0000</pubDate>
		<guid isPermaLink="false">http://farfewertoes.com/stories/2008-03-09-start-virtualbox-virtual-machines-on-boot/#comment-68</guid>
		<description>Hi robp2175, you can remove the script with:
update-rc.d -f vboxcontrol remove

(see man update-rc.d)</description>
		<content:encoded><![CDATA[<p>Hi robp2175, you can remove the script with:<br />
update-rc.d -f vboxcontrol remove</p>
<p>(see man update-rc.d)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Start VirtualBox virtual machines on boot by robp2175</title>
		<link>http://farfewertoes.com/stories/2008-03-09-start-virtualbox-virtual-machines-on-boot/#comment-66</link>
		<dc:creator>robp2175</dc:creator>
		<pubDate>Mon, 29 Sep 2008 18:59:58 +0000</pubDate>
		<guid isPermaLink="false">http://farfewertoes.com/stories/2008-03-09-start-virtualbox-virtual-machines-on-boot/#comment-66</guid>
		<description>How do I remove this script "update-rc.d vboxcontrol defaults 99 10"   .
It did not work for me and I want to make sure it does not try to run every time I boot.</description>
		<content:encoded><![CDATA[<p>How do I remove this script &#8220;update-rc.d vboxcontrol defaults 99 10&#8243;   .<br />
It did not work for me and I want to make sure it does not try to run every time I boot.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Start VirtualBox virtual machines on boot by timbophillips</title>
		<link>http://farfewertoes.com/stories/2008-03-09-start-virtualbox-virtual-machines-on-boot/#comment-65</link>
		<dc:creator>timbophillips</dc:creator>
		<pubDate>Sun, 14 Sep 2008 10:27:23 +0000</pubDate>
		<guid isPermaLink="false">http://farfewertoes.com/stories/2008-03-09-start-virtualbox-virtual-machines-on-boot/#comment-65</guid>
		<description>great work jochem, that solved a problem i was having with a server running several virtualbox VMs. two extra bits that have helped me...

i add the lines
  bridge_fd 0
  bridge_stp on
in the br0 section of /etc/network/interfaces
on big networks this avoids the situation where the bridge isn't in listening mode by the time virtualbox is plugging its VMs onto the taps

in your vboxcontrol script (fantastic script by the way) i added a few lines to the waiting_for_closing_machines() method to give the VMs a minute or so to close themselves in response to the ACPI powerbutton... if a minute goes by and they haven't closed I assume they've hung and use 'poweroff' to pull the plug on them. 

code below....

wait_for_closing_machines() {
    RUNNING_MACHINES=`$SU "$VBOXMANAGE list runningvms" | wc -l`
	if [ $RUNNING_MACHINES != 0 ]; then
        sleep 5

	# =========================================================
	# added by Tim; give them a few cycles to shutdown then kill them
	# =========================================================
	x=$(expr $x + 1)
	log_action_msg "waiting for them to shut-down as instructed - $x"
	if [ $x = 10 ]; then
	   log_action_msg "$RUNNING_MACHINES VM(s) seem to be hung..."
           $SU "$VBOXMANAGE list runningvms" | while read HUNGVM; do
	       log_action_msg "Powering off VM: $HUNGVM ..."
      	       $SU "$VBOXMANAGE controlvm \"$HUNGVM\" poweroff"
		done
        fi
	#========================================================

        wait_for_closing_machines
        fi
        }</description>
		<content:encoded><![CDATA[<p>great work jochem, that solved a problem i was having with a server running several virtualbox VMs. two extra bits that have helped me&#8230;</p>
<p>i add the lines<br />
  bridge_fd 0<br />
  bridge_stp on<br />
in the br0 section of /etc/network/interfaces<br />
on big networks this avoids the situation where the bridge isn&#8217;t in listening mode by the time virtualbox is plugging its VMs onto the taps</p>
<p>in your vboxcontrol script (fantastic script by the way) i added a few lines to the waiting_for_closing_machines() method to give the VMs a minute or so to close themselves in response to the ACPI powerbutton&#8230; if a minute goes by and they haven&#8217;t closed I assume they&#8217;ve hung and use &#8216;poweroff&#8217; to pull the plug on them. </p>
<p>code below&#8230;.</p>
<p>wait_for_closing_machines() {<br />
    RUNNING_MACHINES=`$SU &#8220;$VBOXMANAGE list runningvms&#8221; | wc -l`<br />
	if [ $RUNNING_MACHINES != 0 ]; then<br />
        sleep 5</p>
<p>	# =========================================================<br />
	# added by Tim; give them a few cycles to shutdown then kill them<br />
	# =========================================================<br />
	x=$(expr $x + 1)<br />
	log_action_msg &#8220;waiting for them to shut-down as instructed - $x&#8221;<br />
	if [ $x = 10 ]; then<br />
	   log_action_msg &#8220;$RUNNING_MACHINES VM(s) seem to be hung&#8230;&#8221;<br />
           $SU &#8220;$VBOXMANAGE list runningvms&#8221; | while read HUNGVM; do<br />
	       log_action_msg &#8220;Powering off VM: $HUNGVM &#8230;&#8221;<br />
      	       $SU &#8220;$VBOXMANAGE controlvm \&#8221;$HUNGVM\&#8221; poweroff&#8221;<br />
		done<br />
        fi<br />
	#========================================================</p>
<p>        wait_for_closing_machines<br />
        fi<br />
        }</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Start VirtualBox virtual machines on boot by Lei</title>
		<link>http://farfewertoes.com/stories/2008-03-09-start-virtualbox-virtual-machines-on-boot/#comment-56</link>
		<dc:creator>Lei</dc:creator>
		<pubDate>Sun, 15 Jun 2008 11:39:44 +0000</pubDate>
		<guid isPermaLink="false">http://farfewertoes.com/stories/2008-03-09-start-virtualbox-virtual-machines-on-boot/#comment-56</guid>
		<description>It's a great script I have been looking for.

The version 2008051100 by  Jochem does not work for my setup:

   Sun xVM 1.6.2 under Ubuntu Server 8.04

so that I have adapted it and named version 20080615-1915. It is sent to Jochen to post in the hope that it may be useful for some people. It was just tested in my abovementioned setup and I am not sure if it would work on Ubuntu Desktop or any other Linux distributions, which I am not using and unable to test with.</description>
		<content:encoded><![CDATA[<p>It&#8217;s a great script I have been looking for.</p>
<p>The version 2008051100 by  Jochem does not work for my setup:</p>
<p>   Sun xVM 1.6.2 under Ubuntu Server 8.04</p>
<p>so that I have adapted it and named version 20080615-1915. It is sent to Jochen to post in the hope that it may be useful for some people. It was just tested in my abovementioned setup and I am not sure if it would work on Ubuntu Desktop or any other Linux distributions, which I am not using and unable to test with.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Start VirtualBox virtual machines on boot by Jochem</title>
		<link>http://farfewertoes.com/stories/2008-03-09-start-virtualbox-virtual-machines-on-boot/#comment-55</link>
		<dc:creator>Jochem</dc:creator>
		<pubDate>Sun, 01 Jun 2008 11:19:11 +0000</pubDate>
		<guid isPermaLink="false">http://farfewertoes.com/stories/2008-03-09-start-virtualbox-virtual-machines-on-boot/#comment-55</guid>
		<description>Thanks esoco, you're right. It's fixed in the &lt;a href="http://farfewertoes.com/code/vboxcontrol/" rel="nofollow"&gt;vboxcontrol section&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Thanks esoco, you&#8217;re right. It&#8217;s fixed in the <a href="http://farfewertoes.com/code/vboxcontrol/" rel="nofollow">vboxcontrol section</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Start VirtualBox virtual machines on boot by esoco</title>
		<link>http://farfewertoes.com/stories/2008-03-09-start-virtualbox-virtual-machines-on-boot/#comment-54</link>
		<dc:creator>esoco</dc:creator>
		<pubDate>Sun, 01 Jun 2008 10:14:55 +0000</pubDate>
		<guid isPermaLink="false">http://farfewertoes.com/stories/2008-03-09-start-virtualbox-virtual-machines-on-boot/#comment-54</guid>
		<description>Thanks for this helpful script, it works without problems on Ubuntu 8.04 for me. I only noticed a small typo in the instructions: the entry in interfaces mentioned here
* If you use 'Host interface' networking, put a br0 entry in /etc/network/interfaces: inet br0 inet dhcp

must instead be "iface br0 inet dhcp".</description>
		<content:encoded><![CDATA[<p>Thanks for this helpful script, it works without problems on Ubuntu 8.04 for me. I only noticed a small typo in the instructions: the entry in interfaces mentioned here<br />
* If you use &#8216;Host interface&#8217; networking, put a br0 entry in /etc/network/interfaces: inet br0 inet dhcp</p>
<p>must instead be &#8220;iface br0 inet dhcp&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Start VirtualBox virtual machines on boot by vboxcontrol 2008051100 | Far Fewer Toes</title>
		<link>http://farfewertoes.com/stories/2008-03-09-start-virtualbox-virtual-machines-on-boot/#comment-48</link>
		<dc:creator>vboxcontrol 2008051100 | Far Fewer Toes</dc:creator>
		<pubDate>Sun, 11 May 2008 20:08:14 +0000</pubDate>
		<guid isPermaLink="false">http://farfewertoes.com/stories/2008-03-09-start-virtualbox-virtual-machines-on-boot/#comment-48</guid>
		<description>[...] A while ago i wrote a script for starting up VirtualBox machines at system boot of the host. This script was called VirtualBoxMachines. I received some comments about it, and today I took the time to clean up the script, rename it to vboxcontrol, and put it with a proper README and ChangeLog file in a tarball. [...]</description>
		<content:encoded><![CDATA[<p>[...] A while ago i wrote a script for starting up VirtualBox machines at system boot of the host. This script was called VirtualBoxMachines. I received some comments about it, and today I took the time to clean up the script, rename it to vboxcontrol, and put it with a proper README and ChangeLog file in a tarball. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Start VirtualBox virtual machines on boot by raymond</title>
		<link>http://farfewertoes.com/stories/2008-03-09-start-virtualbox-virtual-machines-on-boot/#comment-46</link>
		<dc:creator>raymond</dc:creator>
		<pubDate>Fri, 02 May 2008 11:42:08 +0000</pubDate>
		<guid isPermaLink="false">http://farfewertoes.com/stories/2008-03-09-start-virtualbox-virtual-machines-on-boot/#comment-46</guid>
		<description>Hi Jochem,

Thanks for the quick response.

The only difference with using VBoxRDP for starting the VM is that it will show up in the log if there are any problems when starting it.

I'm looking forward to your updated script. 

PS. I believe you should post a link inside the VirtualBox forum for other s to find this wonderful script of yours. Believe you me there are many others who would like to be able to do this on their linux box but don't know how to code the script.</description>
		<content:encoded><![CDATA[<p>Hi Jochem,</p>
<p>Thanks for the quick response.</p>
<p>The only difference with using VBoxRDP for starting the VM is that it will show up in the log if there are any problems when starting it.</p>
<p>I&#8217;m looking forward to your updated script. </p>
<p>PS. I believe you should post a link inside the VirtualBox forum for other s to find this wonderful script of yours. Believe you me there are many others who would like to be able to do this on their linux box but don&#8217;t know how to code the script.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Start VirtualBox virtual machines on boot by Jochem</title>
		<link>http://farfewertoes.com/stories/2008-03-09-start-virtualbox-virtual-machines-on-boot/#comment-45</link>
		<dc:creator>Jochem</dc:creator>
		<pubDate>Fri, 02 May 2008 08:04:23 +0000</pubDate>
		<guid isPermaLink="false">http://farfewertoes.com/stories/2008-03-09-start-virtualbox-virtual-machines-on-boot/#comment-45</guid>
		<description>Hi Raymond, thanks for the compliment.

Right now the script only works with tap interfaces, since I didn't have a need for non-tap based VM's. Adding an option for that would be easy though, I guess. If so, I'll post a new version soonish with the option in it.

I use the VBoxManage command since that can do all actions to a VM needed, like shutting down (VBoxRDP can't do this afaik), listing running VM's etc. I don't think there's any advantage of running VBoxRDP for just starting the VM's.</description>
		<content:encoded><![CDATA[<p>Hi Raymond, thanks for the compliment.</p>
<p>Right now the script only works with tap interfaces, since I didn&#8217;t have a need for non-tap based VM&#8217;s. Adding an option for that would be easy though, I guess. If so, I&#8217;ll post a new version soonish with the option in it.</p>
<p>I use the VBoxManage command since that can do all actions to a VM needed, like shutting down (VBoxRDP can&#8217;t do this afaik), listing running VM&#8217;s etc. I don&#8217;t think there&#8217;s any advantage of running VBoxRDP for just starting the VM&#8217;s.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Start VirtualBox virtual machines on boot by raymond</title>
		<link>http://farfewertoes.com/stories/2008-03-09-start-virtualbox-virtual-machines-on-boot/#comment-44</link>
		<dc:creator>raymond</dc:creator>
		<pubDate>Fri, 02 May 2008 00:54:00 +0000</pubDate>
		<guid isPermaLink="false">http://farfewertoes.com/stories/2008-03-09-start-virtualbox-virtual-machines-on-boot/#comment-44</guid>
		<description>This is a great soluton! I have been looking for something like this for a long time.

What if I'm not using a tap interface will this script still work? Is there an option to disable the loading of the tap interface?

Why not use the VBoxRDP command to start the VMs?</description>
		<content:encoded><![CDATA[<p>This is a great soluton! I have been looking for something like this for a long time.</p>
<p>What if I&#8217;m not using a tap interface will this script still work? Is there an option to disable the loading of the tap interface?</p>
<p>Why not use the VBoxRDP command to start the VMs?</p>
]]></content:encoded>
	</item>
</channel>
</rss><!-- Dynamic Page Served (once) in 0.731 seconds -->
