
<?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: Taming Windows 7 in a VirtualBox VM Using Raw Disk Access</title>
	<atom:link href="http://www.rajatarya.com/website/taming-windows-virtualbox-vm/feed" rel="self" type="application/rss+xml" />
	<link>http://www.rajatarya.com/website/taming-windows-virtualbox-vm</link>
	<description>glimpses of sanity on technology and productivity by rajat arya</description>
	<lastBuildDate>Sat, 21 Jan 2012 04:39:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: banavara</title>
		<link>http://www.rajatarya.com/website/taming-windows-virtualbox-vm/comment-page-1#comment-393</link>
		<dc:creator>banavara</dc:creator>
		<pubDate>Sat, 21 Jan 2012 04:39:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.rajatarya.com/?p=644#comment-393</guid>
		<description>You can&#039;t mount a partition in both the guest and host. But there is a workaround using shared folder. Mount the partition in host OS (oreferably) and use it as shared folder in guest OS.</description>
		<content:encoded><![CDATA[<p>You can&#8217;t mount a partition in both the guest and host. But there is a workaround using shared folder. Mount the partition in host OS (oreferably) and use it as shared folder in guest OS.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fixion</title>
		<link>http://www.rajatarya.com/website/taming-windows-virtualbox-vm/comment-page-1#comment-388</link>
		<dc:creator>Fixion</dc:creator>
		<pubDate>Sat, 26 Nov 2011 21:40:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.rajatarya.com/?p=644#comment-388</guid>
		<description>Can both your main OS and the virtual machine both access your data partition (partition 3) at the same time? If so how? This is exactly what I&#039;ve been looking for.</description>
		<content:encoded><![CDATA[<p>Can both your main OS and the virtual machine both access your data partition (partition 3) at the same time? If so how? This is exactly what I&#8217;ve been looking for.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carl Nobile</title>
		<link>http://www.rajatarya.com/website/taming-windows-virtualbox-vm/comment-page-1#comment-381</link>
		<dc:creator>Carl Nobile</dc:creator>
		<pubDate>Sun, 23 Oct 2011 05:36:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.rajatarya.com/?p=644#comment-381</guid>
		<description>I am getting errors when I run your 5th step. It says that -register is an invalid argument. I&#039;m using Ubuntu 11.10 and VB 4.1.4, so I&#039;m guessing the -register argument has been deprecated. </description>
		<content:encoded><![CDATA[<p>I am getting errors when I run your 5th step. It says that -register is an invalid argument. I&#8217;m using Ubuntu 11.10 and VB 4.1.4, so I&#8217;m guessing the -register argument has been deprecated. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geekfault &#187; Lancer votre dual-booting Windows dans une VirtualBox</title>
		<link>http://www.rajatarya.com/website/taming-windows-virtualbox-vm/comment-page-1#comment-380</link>
		<dc:creator>Geekfault &#187; Lancer votre dual-booting Windows dans une VirtualBox</dc:creator>
		<pubDate>Fri, 14 Oct 2011 17:49:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.rajatarya.com/?p=644#comment-380</guid>
		<description>[...] Taming Windows 7 in a VM [...]</description>
		<content:encoded><![CDATA[<p>[...] Taming Windows 7 in a VM [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: N Milyaev</title>
		<link>http://www.rajatarya.com/website/taming-windows-virtualbox-vm/comment-page-1#comment-379</link>
		<dc:creator>N Milyaev</dc:creator>
		<pubDate>Thu, 08 Sep 2011 15:56:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.rajatarya.com/?p=644#comment-379</guid>
		<description>Great Post, many thanks.
I did it all step-by-step and all went smooth up to the point 6.
When trying to create a new virtual machine in the VB it refuses to pick up the created win7.vmdk file with the following error/.

Any idea what I&#039;m doing wrong?


p, li { white-space: pre-wrap; }



p, li { white-space: pre-wrap; 
Failed to open the hard disk /home/xxx/win7.vmdk.
The medium &#039;/home/xxx/win7.vmdk&#039; can&#039;t be used as the requested device type.Deatails show the following:
p, li { white-space: pre-wrap; }

Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
Medium
Interface: 
IMedium {53f9cc0c-e0fd-40a5-a404-a7a5272082cd}
Callee: 
IVirtualBox {c28be65f-1a8f-43b4-81f1-eb60cb516e66}

</description>
		<content:encoded><![CDATA[<p>Great Post, many thanks.<br />
I did it all step-by-step and all went smooth up to the point 6.<br />
When trying to create a new virtual machine in the VB it refuses to pick up the created win7.vmdk file with the following error/.</p>
<p>Any idea what I&#8217;m doing wrong?</p>
<p>p, li { white-space: pre-wrap; }</p>
<p>p, li { white-space: pre-wrap;<br />
Failed to open the hard disk /home/xxx/win7.vmdk.<br />
The medium &#8216;/home/xxx/win7.vmdk&#8217; can&#8217;t be used as the requested device type.Deatails show the following:<br />
p, li { white-space: pre-wrap; }</p>
<p>Result Code:<br />
NS_ERROR_FAILURE (0&#215;80004005)<br />
Component:<br />
Medium<br />
Interface:<br />
IMedium {53f9cc0c-e0fd-40a5-a404-a7a5272082cd}<br />
Callee:<br />
IVirtualBox {c28be65f-1a8f-43b4-81f1-eb60cb516e66}</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://www.rajatarya.com/website/taming-windows-virtualbox-vm/comment-page-1#comment-378</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Mon, 29 Aug 2011 04:01:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.rajatarya.com/?p=644#comment-378</guid>
		<description>It is a BAD BAD idea to add yourself to group disk.  Many bad things can happen and it would be a great vector for viruses.  Create a new user, add them to the group disk and then run the vm as that user.  Here is my script (based on another found on virtualbox) that automates this.  Just create the user virtualbox and use this script.

#! /bin/bash
# Windows 7 VM boot script for VirtualBox 4.x-- you&#039;ll have to always use it instead of running VirtualBox
VBUSER=virtualbox          # name of custom account created (which is a member of disk group)
VM_NAME=Win7           # name of virtual machine

wait_for_closing_machines() {
RUNNING_MACHINES=`sudo -u $VBUSER VBoxManage list runningvms &#124; wc -l`
if [ $RUNNING_MACHINES != 0 ]; then
sleep 5
wait_for_closing_machines
fi
}

sudo chown -R $USER:users /home/$USER/.VirtualBox    # make sure $VBUSER will be able to access VirtualBox settings etc.
                                                     # we use sudo because $VBUSER creates files with its ownership on previous runs
sudo chmod -R g=u /home/$USER/.VirtualBox                 # $VBOXUSER permissions should be the same as ours
sudo chown -R $USER:users /home/$USER/VirtualBox VMs/$VM_NAME    # ditto for VirtualBox VMs directory.
sudo chmod -R g=u /home/$USER/VirtualBox VMs/$VM_NAME

xauth extract /home/$USER/cookieTmp $DISPLAY

chmod g+r /home/$USER/cookieTmp
sudo chmod g+x /home/$USER/

sudo -u $VBUSER XAUTHORITY=/tmp/.Xauthority_$VBUSER xauth merge /home/$USER/cookieTmp
rm /home/$USER/cookieTmp

sudo -u $VBUSER DISPLAY=:0 XAUTHORITY=/tmp/.Xauthority_$VBUSER VBOX_USER_HOME=/home/$USER/.VirtualBox VBoxManage startvm $VM_NAME
#sudo -u $VBUSER DISPLAY=:0 XAUTHORITY=/tmp/.Xauthority_$VBUSER VBOX_USER_HOME=/home/$USER/.VirtualBox virtualbox

echo &quot;Waiting for shutdown of $VM_NAME&quot;
wait_for_closing_machines
echo &quot;$VM_NAME shutdown. Resetting permissions.&quot;
sudo chown -R $USER:users /home/$USER/.VirtualBox    # make sure $VBUSER will be able to access VirtualBox settings etc.
                                                     # we use sudo because $VBUSER creates files with its ownership on previous runs
sudo chmod -R g-rw /home/$USER/.VirtualBox/*                 # $VBOXUSER permissions should be the same as ours
sudo chown -R $USER:users /home/$USER/VirtualBox VMs/$VM_NAME    # ditto for VirtualBox VMs directory.
sudo chmod -R g-rw /home/$USER/VirtualBox VMs/$VM_NAME
</description>
		<content:encoded><![CDATA[<p>It is a BAD BAD idea to add yourself to group disk.  Many bad things can happen and it would be a great vector for viruses.  Create a new user, add them to the group disk and then run the vm as that user.  Here is my script (based on another found on virtualbox) that automates this.  Just create the user virtualbox and use this script.</p>
<p>#! /bin/bash<br />
# Windows 7 VM boot script for VirtualBox 4.x&#8211; you&#8217;ll have to always use it instead of running VirtualBox<br />
VBUSER=virtualbox          # name of custom account created (which is a member of disk group)<br />
VM_NAME=Win7           # name of virtual machine</p>
<p>wait_for_closing_machines() {<br />
RUNNING_MACHINES=`sudo -u $VBUSER VBoxManage list runningvms | wc -l`<br />
if [ $RUNNING_MACHINES != 0 ]; then<br />
sleep 5<br />
wait_for_closing_machines<br />
fi<br />
}</p>
<p>sudo chown -R $USER:users /home/$USER/.VirtualBox    # make sure $VBUSER will be able to access VirtualBox settings etc.<br />
                                                     # we use sudo because $VBUSER creates files with its ownership on previous runs<br />
sudo chmod -R g=u /home/$USER/.VirtualBox                 # $VBOXUSER permissions should be the same as ours<br />
sudo chown -R $USER:users /home/$USER/VirtualBox VMs/$VM_NAME    # ditto for VirtualBox VMs directory.<br />
sudo chmod -R g=u /home/$USER/VirtualBox VMs/$VM_NAME</p>
<p>xauth extract /home/$USER/cookieTmp $DISPLAY</p>
<p>chmod g+r /home/$USER/cookieTmp<br />
sudo chmod g+x /home/$USER/</p>
<p>sudo -u $VBUSER XAUTHORITY=/tmp/.Xauthority_$VBUSER xauth merge /home/$USER/cookieTmp<br />
rm /home/$USER/cookieTmp</p>
<p>sudo -u $VBUSER DISPLAY=:0 XAUTHORITY=/tmp/.Xauthority_$VBUSER VBOX_USER_HOME=/home/$USER/.VirtualBox VBoxManage startvm $VM_NAME<br />
#sudo -u $VBUSER DISPLAY=:0 XAUTHORITY=/tmp/.Xauthority_$VBUSER VBOX_USER_HOME=/home/$USER/.VirtualBox virtualbox</p>
<p>echo &#8220;Waiting for shutdown of $VM_NAME&#8221;<br />
wait_for_closing_machines<br />
echo &#8220;$VM_NAME shutdown. Resetting permissions.&#8221;<br />
sudo chown -R $USER:users /home/$USER/.VirtualBox    # make sure $VBUSER will be able to access VirtualBox settings etc.<br />
                                                     # we use sudo because $VBUSER creates files with its ownership on previous runs<br />
sudo chmod -R g-rw /home/$USER/.VirtualBox/*                 # $VBOXUSER permissions should be the same as ours<br />
sudo chown -R $USER:users /home/$USER/VirtualBox VMs/$VM_NAME    # ditto for VirtualBox VMs directory.<br />
sudo chmod -R g-rw /home/$USER/VirtualBox VMs/$VM_NAME</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Xerebus</title>
		<link>http://www.rajatarya.com/website/taming-windows-virtualbox-vm/comment-page-1#comment-377</link>
		<dc:creator>Xerebus</dc:creator>
		<pubDate>Sat, 27 Aug 2011 03:04:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.rajatarya.com/?p=644#comment-377</guid>
		<description>I&#039;d really love to try this, but before I do - how much of this might be different in VirtualBox 4.1.2 (it&#039;s been a while)?</description>
		<content:encoded><![CDATA[<p>I&#8217;d really love to try this, but before I do &#8211; how much of this might be different in VirtualBox 4.1.2 (it&#8217;s been a while)?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JD Trout</title>
		<link>http://www.rajatarya.com/website/taming-windows-virtualbox-vm/comment-page-1#comment-376</link>
		<dc:creator>JD Trout</dc:creator>
		<pubDate>Mon, 18 Jul 2011 14:58:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.rajatarya.com/?p=644#comment-376</guid>
		<description>I have been having the same issues as apmsylvain - blue screens when trying to boot windows- but am not able to resolve it.  I tried the repair route, but receive the message &quot;Startup Repair cannot repair this computer automatically&quot;. I tried changing the controller from SATA to IDE, but had no luck with that either.

The host is Ubuntu 11.04 running Vbox 4.0.12 and the windows version that I am trying to do the raw device map from is Windows 7 64bit.

Any suggestions would be appreciated. </description>
		<content:encoded><![CDATA[<p>I have been having the same issues as apmsylvain &#8211; blue screens when trying to boot windows- but am not able to resolve it.  I tried the repair route, but receive the message &#8220;Startup Repair cannot repair this computer automatically&#8221;. I tried changing the controller from SATA to IDE, but had no luck with that either.</p>
<p>The host is Ubuntu 11.04 running Vbox 4.0.12 and the windows version that I am trying to do the raw device map from is Windows 7 64bit.</p>
<p>Any suggestions would be appreciated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Priest</title>
		<link>http://www.rajatarya.com/website/taming-windows-virtualbox-vm/comment-page-1#comment-374</link>
		<dc:creator>Priest</dc:creator>
		<pubDate>Mon, 20 Jun 2011 16:37:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.rajatarya.com/?p=644#comment-374</guid>
		<description>Doesn&#039;t matter which one you use tbh, the point is to run the startup repair option which simply overwrites the mbr with a vista/win7 compatible bootloader. Both vista and win7 install / repair disks will work fine.
</description>
		<content:encoded><![CDATA[<p>Doesn&#8217;t matter which one you use tbh, the point is to run the startup repair option which simply overwrites the mbr with a vista/win7 compatible bootloader. Both vista and win7 install / repair disks will work fine.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Csaba Toth</title>
		<link>http://www.rajatarya.com/website/taming-windows-virtualbox-vm/comment-page-1#comment-371</link>
		<dc:creator>Csaba Toth</dc:creator>
		<pubDate>Fri, 13 May 2011 18:24:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.rajatarya.com/?p=644#comment-371</guid>
		<description>Thanks for your help, other guides didn&#039;t mention the trick of creating an MBR file. Now I managed to boot (this way I bypass GRUB and don&#039;t get an error. I&#039;m at the 7th step. I have Win 7 x64. Why do you mention Vista DVD? You seem to have also a Win7. I don&#039;t have an installation CD, how can I overcome this step?</description>
		<content:encoded><![CDATA[<p>Thanks for your help, other guides didn&#8217;t mention the trick of creating an MBR file. Now I managed to boot (this way I bypass GRUB and don&#8217;t get an error. I&#8217;m at the 7th step. I have Win 7 x64. Why do you mention Vista DVD? You seem to have also a Win7. I don&#8217;t have an installation CD, how can I overcome this step?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.663 seconds -->

