<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>VirtualBox &#8211; Blog of Kliment Andreev &#8211; A place so I won&#039;t forget things</title>
	<atom:link href="https://blog.andreev.it/tag/virtualbox/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.andreev.it</link>
	<description></description>
	<lastBuildDate>Sat, 17 Oct 2020 13:55:50 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>Azure: Vagrant and VirtualBox</title>
		<link>https://blog.andreev.it/2018/01/120-azure-vagrant-virtualbox/</link>
					<comments>https://blog.andreev.it/2018/01/120-azure-vagrant-virtualbox/#respond</comments>
		
		<dc:creator><![CDATA[Kliment Andreev]]></dc:creator>
		<pubDate>Mon, 22 Jan 2018 17:52:11 +0000</pubDate>
				<category><![CDATA[Azure]]></category>
		<category><![CDATA[Vagrant]]></category>
		<category><![CDATA[VirtualBox]]></category>
		<guid isPermaLink="false">http://blog.iandreev.com/?p=3550</guid>

					<description><![CDATA[Vagrant helps developers building and maintaining portable virtual software development environments under VirtualBox, Hyper-V,&#8230;]]></description>
										<content:encoded><![CDATA[<div id="bsf_rt_marker"></div><p>Vagrant helps developers building and maintaining portable virtual software development environments under VirtualBox, Hyper-V, Docker, VMWare etc..Vagrant uses pre-made boxes as VMs managed with <strong>Vagrantfile </strong>config file. By default, Vagrant is tied with VirtualBox to run the VMs, but VirtualBox requires to run on a physical box with VT enabled in BIOS. Not anymore. Azure supports VMs that can run Hyper-V on Windows 2016 if the VMs are Dv3 and Ev3 Azure Virtual Machines. So, all we have to do is deploy a Dv3 or Ev3 Azure Windows 2016 server and install VirtualBox. This is a good solution if you don&#8217;t have a physical server available and want to use Chef and Test Kitchen.</p>
<h1>Provision Windows 2016</h1>
<p>Create a new Windows 2016 datacenter and click <strong>Create</strong>.<br />
<a href="https://blog.andreev.it/wp-content/uploads/2018/01/P097-01.png"><img fetchpriority="high" decoding="async" src="https://blog.andreev.it/wp-content/uploads/2018/01/P097-01.png" alt="" width="662" height="524" class="aligncenter size-full wp-image-7812" srcset="https://blog.andreev.it/wp-content/uploads/2018/01/P097-01.png 662w, https://blog.andreev.it/wp-content/uploads/2018/01/P097-01-300x237.png 300w, https://blog.andreev.it/wp-content/uploads/2018/01/P097-01-585x463.png 585w" sizes="(max-width: 662px) 100vw, 662px" /></a><br />
Choose the basics (username, password, disk, location etc).<br />
<a href="https://blog.andreev.it/wp-content/uploads/2018/01/P097-02.png"><img decoding="async" src="https://blog.andreev.it/wp-content/uploads/2018/01/P097-02.png" alt="" width="315" height="481" class="aligncenter size-full wp-image-7813" srcset="https://blog.andreev.it/wp-content/uploads/2018/01/P097-02.png 315w, https://blog.andreev.it/wp-content/uploads/2018/01/P097-02-196x300.png 196w" sizes="(max-width: 315px) 100vw, 315px" /></a><br />
I&#8217;ll go with E2S_V3 because it&#8217;s the cheapest. DS1_V2 doesn&#8217;t support virtualization.<br />
<a href="https://blog.andreev.it/wp-content/uploads/2018/01/P097-03.png"><img decoding="async" src="https://blog.andreev.it/wp-content/uploads/2018/01/P097-03.png" alt="" width="586" height="523" class="aligncenter size-full wp-image-7814" srcset="https://blog.andreev.it/wp-content/uploads/2018/01/P097-03.png 586w, https://blog.andreev.it/wp-content/uploads/2018/01/P097-03-300x268.png 300w" sizes="(max-width: 586px) 100vw, 586px" /></a><br />
Choose the settings and finish the deployment.<br />
<a href="https://blog.andreev.it/wp-content/uploads/2018/01/P097-04.png"><img loading="lazy" decoding="async" src="https://blog.andreev.it/wp-content/uploads/2018/01/P097-04.png" alt="" width="374" height="554" class="aligncenter size-full wp-image-7815" srcset="https://blog.andreev.it/wp-content/uploads/2018/01/P097-04.png 374w, https://blog.andreev.it/wp-content/uploads/2018/01/P097-04-203x300.png 203w" sizes="(max-width: 374px) 100vw, 374px" /></a><br />
Once completed, go to the <strong>All Resources</strong> on the left and click on the <strong>Network Security Group</strong>.<br />
<a href="https://blog.andreev.it/wp-content/uploads/2018/01/P097-05.png"><img loading="lazy" decoding="async" src="https://blog.andreev.it/wp-content/uploads/2018/01/P097-05.png" alt="" width="634" height="111" class="aligncenter size-full wp-image-7816" srcset="https://blog.andreev.it/wp-content/uploads/2018/01/P097-05.png 634w, https://blog.andreev.it/wp-content/uploads/2018/01/P097-05-300x53.png 300w, https://blog.andreev.it/wp-content/uploads/2018/01/P097-05-585x102.png 585w" sizes="(max-width: 634px) 100vw, 634px" /></a><br />
Click on <strong>Inbound Security Rules</strong> and then click <strong>Add</strong>.<br />
<a href="https://blog.andreev.it/wp-content/uploads/2018/01/P097-06.png"><img loading="lazy" decoding="async" src="https://blog.andreev.it/wp-content/uploads/2018/01/P097-06.png" alt="" width="1085" height="397" class="aligncenter size-full wp-image-7817" srcset="https://blog.andreev.it/wp-content/uploads/2018/01/P097-06.png 1085w, https://blog.andreev.it/wp-content/uploads/2018/01/P097-06-300x110.png 300w, https://blog.andreev.it/wp-content/uploads/2018/01/P097-06-1024x375.png 1024w, https://blog.andreev.it/wp-content/uploads/2018/01/P097-06-768x281.png 768w, https://blog.andreev.it/wp-content/uploads/2018/01/P097-06-585x214.png 585w" sizes="(max-width: 1085px) 100vw, 1085px" /></a></p>
<p>Add port 2222 TCP. This will be used for SSH on the virtual machines running on VirtualBox.<br />
<a href="https://blog.andreev.it/wp-content/uploads/2018/01/P097-07.png"><img loading="lazy" decoding="async" src="https://blog.andreev.it/wp-content/uploads/2018/01/P097-07.png" alt="" width="400" height="578" class="aligncenter size-full wp-image-7818" srcset="https://blog.andreev.it/wp-content/uploads/2018/01/P097-07.png 400w, https://blog.andreev.it/wp-content/uploads/2018/01/P097-07-208x300.png 208w" sizes="(max-width: 400px) 100vw, 400px" /></a></p>
<h1>Vagrant/VirtualBox install</h1>
<p>Download and install Vagrant and VirtualBox from <a href="https://www.vagrantup.com/downloads.html">here </a>and <a href="https://www.virtualbox.org/wiki/Downloads">here</a>.</p>
<h1>Provision and access a test VM</h1>
<p>Open up the command prompt and type:</p>
<pre class="brush: bash; title: ; notranslate">
vagrant init bento/centos-7.4
</pre>
<p>Depending on what folder are you in, use some editor and edit the <strong>Vagrant </strong>file that was just created. Un comment the line that looks similar to this and change ports 80 and 8080 with 22 and 2222. This will allow port 22 to be forwarded to 2222 and make it publicly available.<br />
<a href="https://blog.andreev.it/wp-content/uploads/2018/01/P097-08.png"><img loading="lazy" decoding="async" src="https://blog.andreev.it/wp-content/uploads/2018/01/P097-08.png" alt="" width="560" height="109" class="aligncenter size-full wp-image-7819" srcset="https://blog.andreev.it/wp-content/uploads/2018/01/P097-08.png 560w, https://blog.andreev.it/wp-content/uploads/2018/01/P097-08-300x58.png 300w" sizes="(max-width: 560px) 100vw, 560px" /></a><br />
Power up the VM.</p>
<pre class="brush: bash; title: ; notranslate">
vagrant up
</pre>
<p>Finally, allow port 2222 on the Azure OS VM (we already took care of Azure firewall). Go to <strong>Control Panel</strong>, click on <strong>Windows Firewall</strong> and then <strong>Advanced Settings</strong>.<br />
<a href="https://blog.andreev.it/wp-content/uploads/2018/01/P097-09.png"><img loading="lazy" decoding="async" src="https://blog.andreev.it/wp-content/uploads/2018/01/P097-09.png" alt="" width="764" height="363" class="aligncenter size-full wp-image-7820" srcset="https://blog.andreev.it/wp-content/uploads/2018/01/P097-09.png 764w, https://blog.andreev.it/wp-content/uploads/2018/01/P097-09-300x143.png 300w, https://blog.andreev.it/wp-content/uploads/2018/01/P097-09-585x278.png 585w" sizes="(max-width: 764px) 100vw, 764px" /></a><br />
On the left side, click <strong>Inbound Rules</strong>, right-click it, then select <strong>New Rule</strong>. Select <strong>Port</strong>, then <strong>TCP</strong>, port <strong>2222</strong>, <strong>Allow </strong>and select <strong>All Profiles</strong>. The VM should be accessible from the outside now. Open up <strong>putty </strong>or any other SSH client and access the instance over port <strong>2222</strong>. Use <strong>vagrant/vagrant</strong> as username and password.</p>
<p><a href="https://blog.andreev.it/wp-content/uploads/2018/01/P097-10.png"><img loading="lazy" decoding="async" src="https://blog.andreev.it/wp-content/uploads/2018/01/P097-10.png" alt="" width="295" height="134" class="aligncenter size-full wp-image-7821" /></a></p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.andreev.it/2018/01/120-azure-vagrant-virtualbox/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
