<?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>mgorecki.net &#187; Ubuntu</title>
	<atom:link href="http://mgorecki.net/index.php/tag/ubuntu/feed/" rel="self" type="application/rss+xml" />
	<link>http://mgorecki.net</link>
	<description>Life, the Universe, Software and Everything</description>
	<lastBuildDate>Mon, 16 Aug 2010 12:31:53 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Disabling VT-x/AMD-v in VirtualBox on Ubuntu</title>
		<link>http://mgorecki.net/index.php/2010/01/15/disabling-vt-xamd-v-in-virtualbox-on-ubuntu/</link>
		<comments>http://mgorecki.net/index.php/2010/01/15/disabling-vt-xamd-v-in-virtualbox-on-ubuntu/#comments</comments>
		<pubDate>Fri, 15 Jan 2010 20:51:21 +0000</pubDate>
		<dc:creator>mgorecki</dc:creator>
				<category><![CDATA[Tips and tricks]]></category>
		<category><![CDATA[Ubuntu]]></category>
		<category><![CDATA[VirtualBox]]></category>

		<guid isPermaLink="false">http://mgorecki.net/?p=42</guid>
		<description><![CDATA[VirtualBox on Ubuntu has an issue preventing host waking up from suspend. This issue is marked as resolved, but unfortunately it&#8217;s still present in 3.1.2 r56127 running under control of Ubuntu x64. The workaround for this issue is well documented: disable VT-x/AMD-v support. Fine, but&#8230; the option is greyed out in the settings: To change [...]]]></description>
			<content:encoded><![CDATA[<p>VirtualBox on Ubuntu has an issue <a href="http://www.virtualbox.org/ticket/2023">preventing host waking up from suspend</a>. This issue is marked as resolved, but unfortunately it&#8217;s still present in 3.1.2 r56127 running under control of Ubuntu x64. The workaround for this issue is well documented: disable VT-x/AMD-v support. Fine, but&#8230; the option is greyed out in the settings:</p>
<p><a href="http://mgorecki.net/wp-content/uploads/2010/01/vt-x.png"><img class="alignnone size-full wp-image-43" title="vt-x" src="http://mgorecki.net/wp-content/uploads/2010/01/vt-x.png" alt="" width="665" height="533" /></a></p>
<p>To change it, you have to go directly to vm configuration file and change enabled attribute in HardwareVirtEx to false. After the change CPU node should look similar to:</p>
<pre>      &lt;CPU count="1"&gt;

        &lt;HardwareVirtEx enabled="false" exclusive="true"/&gt;

        &lt;HardwareVirtExNestedPaging enabled="false"/&gt;

        &lt;HardwareVirtExVPID enabled="false"/&gt;

        &lt;PAE enabled="true"/&gt;

      &lt;/CPU&gt;</pre>
<div id="_mcePaste">Now restart VirtualBox and you&#8217;re done!</div>
<p><a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save"><img src="http://mgorecki.net/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a> </p>]]></content:encoded>
			<wfw:commentRss>http://mgorecki.net/index.php/2010/01/15/disabling-vt-xamd-v-in-virtualbox-on-ubuntu/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
