<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.ihitc.net/mediawiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=ABorgert</id>
	<title>ITCwiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.ihitc.net/mediawiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=ABorgert"/>
	<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/w/Special:Contributions/ABorgert"/>
	<updated>2026-04-08T07:20:36Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.38.5</generator>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3577</id>
		<title>Converting VMWare .vmdk To VirtualBox .vdi Using Qemu+ and VBoxManage</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3577"/>
		<updated>2010-12-07T17:16:18Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If you want to switch to VirtualBox and have a Vmware Virtual Machine you want to use? You can convert a Vmware .vmdk file into a VirtualBox .vdi file that you can use on VirtualBox. &lt;br /&gt;
&lt;br /&gt;
First, download qemu, open a Console and execute: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo apt-get install qemu&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Next, open a console and go to your .vmdk virtual disc image folder and type this: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;qemu-img convert &amp;quot;harddrive-name&amp;quot;.vmdk /filelocation/&amp;quot;harddrive-name&amp;quot;.bin&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Change &amp;quot;harddrive-name&amp;quot; with the name of your .vmdk file and raw-file with the name of the new converted file you want to create. This takes a few minutes, After the conversion is completed. A raw hard disk image has been created. &lt;br /&gt;
&lt;br /&gt;
To convert a raw disk image to a VirtualBox Disk Image (.vdi) file use this command. &lt;br /&gt;
&lt;br /&gt;
The syntax is as follows:&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw /filelocation/&amp;quot;harddrive-name&amp;quot;.bin &amp;lt;outputfile&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo VBoxManage convertfromraw /home/tony/.VirtualBox/HardDisks/HardDisk1.bin /home/tony/.VirtualBox&#039;&#039;&#039; &lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD]&lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw stdin &amp;lt;outputfile&amp;gt; &amp;lt;bytes&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD] &lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
What the parameters mean:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;format&#039;&#039;&#039;  - Selects the disk image format to create. Default is .vdi. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;variant&#039;&#039;&#039;  - Allows to choose a file format variant for the output file. It is a comma-separated list of variant flags. Not all combinations are supported, and specifying inconsistent flags will result in an error message. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The second form forces VBoxManage to read the content for the disk image from standard input(useful for using that command in a pipe).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note: For compatibility with earlier versions of VirtualBox, the “convertdd” command is also supported and mapped internally to the “convertfromraw” command.&lt;br /&gt;
 &lt;br /&gt;
&#039;&#039;&#039;Here is a quick example of an actual conversion&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;tony@ubuntu:~$ sudo apt-get install qemu &lt;br /&gt;
   &#039;&#039;&#039;[sudo] password for tony:&lt;br /&gt;
   &#039;&#039;&#039;Reading package lists... Done&lt;br /&gt;
   &#039;&#039;&#039;Building dependency tree       &lt;br /&gt;
   &#039;&#039;&#039;Reading state information... Done&lt;br /&gt;
   &#039;&#039;&#039;The following packages were automatically installed and are no longer required:&lt;br /&gt;
   &#039;&#039;&#039;linux-headers-2.6.32-24 linux-headers-2.6.32-24-generic&lt;br /&gt;
   &#039;&#039;&#039;Use &#039;apt-get autoremove&#039; to remove them.&lt;br /&gt;
   &#039;&#039;&#039;The following extra packages will be installed:&lt;br /&gt;
   &#039;&#039;&#039;bridge-utils libaio1 qemu-common qemu-kvm seabios vgabios&lt;br /&gt;
   &#039;&#039;&#039;Suggested packages:&lt;br /&gt;
   &#039;&#039;&#039;mol-drivers-macosx openbios-sparc kvm-pxe ubuntu-vm-builder uml-utilities&lt;br /&gt;
   &#039;&#039;&#039;The following NEW packages will be installed:&lt;br /&gt;
   &#039;&#039;&#039;bridge-utils libaio1 qemu qemu-common qemu-kvm seabios vgabios&lt;br /&gt;
   &#039;&#039;&#039;0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded.&lt;br /&gt;
   &#039;&#039;&#039;Need to get 2,769kB of archives.&lt;br /&gt;
   &#039;&#039;&#039;After this operation, 8,192kB of additional disk space will be used.&lt;br /&gt;
   &#039;&#039;&#039;Do you want to continue [Y/n]? Y&lt;br /&gt;
   &#039;&#039;&#039;Get:1 http://us.archive.ubuntu.com/ubuntu/ lucid/main bridge-utils 1.4-5ubuntu2 [32.6kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:2 http://us.archive.ubuntu.com/ubuntu/ lucid/main libaio1 0.3.107-3ubuntu2 [9,512B]&lt;br /&gt;
   &#039;&#039;&#039;Get:3 http://us.archive.ubuntu.com/ubuntu/ lucid/main seabios 0.5.1-0ubuntu2 [48.2kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:4 http://us.archive.ubuntu.com/ubuntu/ lucid/main vgabios 0.6c-2ubuntu1 [78.5kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:5 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main qemu-common 0.12.3+noroms-0ubuntu9.2 [30.1kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:6 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main qemu-kvm 0.12.3+noroms-0ubuntu9.2 [2,556kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:7 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/universe qemu 0.12.3+noroms-0ubuntu9.2 [3.9kB]                     &lt;br /&gt;
   &#039;&#039;&#039;Fetched 2,769kB in 17s(156kB/s)                                                                                             &lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package bridge-utils.&lt;br /&gt;
   &#039;&#039;&#039;(Reading database ... 148121 files and directories currently installed.)&lt;br /&gt;
   &#039;&#039;&#039;Unpacking bridge-utils (from .../bridge-utils_1.4-5ubuntu2_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package libaio1.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking libaio1 (from .../libaio1_0.3.107-3ubuntu2_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package seabios.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking seabios (from .../seabios_0.5.1-0ubuntu2_all.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package vgabios.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking vgabios (from .../vgabios_0.6c-2ubuntu1_all.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package qemu-common.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking qemu-common (from .../qemu-common_0.12.3+noroms-0ubuntu9.2_all.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package qemu-kvm.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking qemu-kvm (from .../qemu-kvm_0.12.3+noroms-0ubuntu9.2_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package qemu.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking qemu (from .../qemu_0.12.3+noroms-0ubuntu9.2_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for ureadahead ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for man-db ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up bridge-utils (1.4-5ubuntu2) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up libaio1 (0.3.107-3ubuntu2) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up seabios (0.5.1-0ubuntu2) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up vgabios (0.6c-2ubuntu1) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up qemu-common (0.12.3+noroms-0ubuntu9.2) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up qemu-kvm (0.12.3+noroms-0ubuntu9.2) ...&lt;br /&gt;
   &#039;&#039;&#039;qemu-kvm start/running&lt;br /&gt;
   &#039;&#039;&#039;Setting up qemu (0.12.3+noroms-0ubuntu9.2) ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for libc-bin ...&lt;br /&gt;
   &#039;&#039;&#039;ldconfig deferred processing now taking place&lt;br /&gt;
   &#039;&#039;&#039;tony@ubuntu:~$ su&lt;br /&gt;
   &#039;&#039;&#039;Password: &lt;br /&gt;
   &#039;&#039;&#039;root@ubuntu:/home/tony# cd /tmp/Ubuntu_VMware&lt;br /&gt;
   &#039;&#039;&#039;root@ubuntu:/tmp/Ubuntu_VMware# qemu-img convert Ubuntu_VMware.vmdk /tmp/Ubuntu_VMware.bin&#039;&#039;&#039;&lt;br /&gt;
   &#039;&#039;&#039;root@ubuntu:/tmp/Ubuntu_VMware# VBoxManage convertfromraw /tmp/Ubuntu_VMware.bin /tmp/Ubuntu_VBox/Ubuntu_VBox.vdi&lt;br /&gt;
   &#039;&#039;&#039;The program &#039;VBoxManage&#039; is currently not installed.  You can install it by typing:&lt;br /&gt;
   &#039;&#039;&#039;apt-get install virtualbox-ose&lt;br /&gt;
   &#039;&#039;&#039;root@ubuntu:/tmp/Ubuntu_VMware# apt-get install virtualbox-ose&lt;br /&gt;
   &#039;&#039;&#039;Reading package lists... Done&lt;br /&gt;
   &#039;&#039;&#039;Building dependency tree       &lt;br /&gt;
   &#039;&#039;&#039;Reading state information... Done&lt;br /&gt;
   &#039;&#039;&#039;The following extra packages will be installed:&lt;br /&gt;
   &#039;&#039;&#039;dkms libaudio2 libmng1 libqt4-network libqt4-opengl libqtcore4 libqtgui4 virtualbox-ose-dkms virtualbox-ose-qt&lt;br /&gt;
   &#039;&#039;&#039;Suggested packages:&lt;br /&gt;
   &#039;&#039;&#039;nas qt4-qtconfig virtualbox-guest-additions&lt;br /&gt;
   &#039;&#039;&#039;The following NEW packages will be installed:&lt;br /&gt;
   &#039;&#039;&#039;dkms libaudio2 libmng1 libqt4-network libqt4-opengl libqtcore4 libqtgui4 virtualbox-ose virtualbox-ose-dkms&lt;br /&gt;
   &#039;&#039;&#039;virtualbox-ose-qt&lt;br /&gt;
   &#039;&#039;&#039;0 upgraded, 10 newly installed, 0 to remove and 0 not upgraded.&lt;br /&gt;
   &#039;&#039;&#039;Need to get 20.2MB of archives.&lt;br /&gt;
   &#039;&#039;&#039;After this operation, 70.4MB of additional disk space will be used.&lt;br /&gt;
   &#039;&#039;&#039;Do you want to continue [Y/n]? Y&lt;br /&gt;
   &#039;&#039;&#039;Get:1 http://us.archive.ubuntu.com/ubuntu/ lucid/main dkms 2.1.1.2-2fakesync1 [70.1kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:2 http://us.archive.ubuntu.com/ubuntu/ lucid/main libaudio2 1.9.2-3 [81.0kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:3 http://us.archive.ubuntu.com/ubuntu/ lucid/main libmng1 1.0.9-1ubuntu1 [209kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:4 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main libqtcore4 4:4.6.2-0ubuntu5.1 [1,722kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:5 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main libqt4-network 4:4.6.2-0ubuntu5.1 [444kB]                      &lt;br /&gt;
   &#039;&#039;&#039;Get:6 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main libqtgui4 4:4.6.2-0ubuntu5.1 [4,010kB]                         &lt;br /&gt;
   &#039;&#039;&#039;Get:7 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main libqt4-opengl 4:4.6.2-0ubuntu5.1 [265kB]                       &lt;br /&gt;
   &#039;&#039;&#039;Get:8 http://us.archive.ubuntu.com/ubuntu/ lucid/universe virtualbox-ose 3.1.6-dfsg-2ubuntu2 [8,265kB]                       &lt;br /&gt;
   &#039;&#039;&#039;Get:9 http://us.archive.ubuntu.com/ubuntu/ lucid/universe virtualbox-ose-dkms 3.1.6-dfsg-2ubuntu2 [501kB]                    &lt;br /&gt;
   &#039;&#039;&#039;Get:10 http://us.archive.ubuntu.com/ubuntu/ lucid/universe virtualbox-ose-qt 3.1.6-dfsg-2ubuntu2 [4,678kB]                   &lt;br /&gt;
   &#039;&#039;&#039;Fetched 20.2MB in 2min 3s (164kB/s)                                                                                          &lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package dkms.&lt;br /&gt;
   &#039;&#039;&#039;(Reading database ... 148269 files and directories currently installed.)&lt;br /&gt;
   &#039;&#039;&#039;Unpacking dkms (from .../dkms_2.1.1.2-2fakesync1_all.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package libaudio2.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking libaudio2 (from .../libaudio2_1.9.2-3_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package libmng1.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking libmng1 (from .../libmng1_1.0.9-1ubuntu1_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package libqtcore4.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking libqtcore4 (from .../libqtcore4_4%3a4.6.2-0ubuntu5.1_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package libqt4-network.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking libqt4-network (from .../libqt4-network_4%3a4.6.2-0ubuntu5.1_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package libqtgui4.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking libqtgui4 (from .../libqtgui4_4%3a4.6.2-0ubuntu5.1_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package libqt4-opengl.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking libqt4-opengl (from .../libqt4-opengl_4%3a4.6.2-0ubuntu5.1_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package virtualbox-ose.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking virtualbox-ose (from .../virtualbox-ose_3.1.6-dfsg-2ubuntu2_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package virtualbox-ose-dkms.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking virtualbox-ose-dkms (from .../virtualbox-ose-dkms_3.1.6-dfsg-2ubuntu2_all.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package virtualbox-ose-qt.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking virtualbox-ose-qt (from .../virtualbox-ose-qt_3.1.6-dfsg-2ubuntu2_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for man-db ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for ureadahead ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for desktop-file-utils ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for python-gmenu ... &lt;br /&gt;
   &#039;&#039;&#039;Rebuilding /usr/share/applications/desktop.en_US.utf8.cache...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for python-support ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up dkms (2.1.1.2-2fakesync1) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up libaudio2 (1.9.2-3) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up libmng1 (1.0.9-1ubuntu1) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up libqtcore4 (4:4.6.2-0ubuntu5.1) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up libqt4-network (4:4.6.2-0ubuntu5.1) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up libqtgui4 (4:4.6.2-0ubuntu5.1) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up libqt4-opengl (4:4.6.2-0ubuntu5.1) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up virtualbox-ose (3.1.6-dfsg-2ubuntu2) ...&lt;br /&gt;
   &#039;&#039;&#039; * Stopping VirtualBox kernel modules                                                                    [ OK ]&lt;br /&gt;
   &#039;&#039;&#039; * StartingVirtualBoxkernelModules                                                                                            &lt;br /&gt;
   &#039;&#039;&#039; * No suitable module for running kernel found                                                           [fail]&lt;br /&gt;
   &#039;&#039;&#039;invoke-rc.d: initscript virtualbox-ose, action &amp;quot;restart&amp;quot; failed.&lt;br /&gt;
   &#039;&#039;&#039;Setting up virtualbox-ose-dkms (3.1.6-dfsg-2ubuntu2) ...&lt;br /&gt;
   &#039;&#039;&#039;Loading new virtualbox-ose-3.1.6 DKMS files...&lt;br /&gt;
   &#039;&#039;&#039;First Installation: checking all kernels...&lt;br /&gt;
   &#039;&#039;&#039;Building only for 2.6.32-25-generic&lt;br /&gt;
   &#039;&#039;&#039;Building for architecture i686&lt;br /&gt;
   &#039;&#039;&#039;Building initial module for 2.6.32-25-generic Done.&lt;br /&gt;
   &#039;&#039;&#039;vboxdrv.ko: Running module version sanity check.&lt;br /&gt;
   &#039;&#039;&#039;- Original module&lt;br /&gt;
      &#039;&#039;&#039;- No original module exists within this kernel&lt;br /&gt;
    &#039;&#039;&#039;- Installation&lt;br /&gt;
      &#039;&#039;&#039;- Installing to /lib/modules/2.6.32-25-generic/updates/dkms/&lt;br /&gt;
   &#039;&#039;&#039;vboxnetadp.ko: Running module version sanity check.&lt;br /&gt;
    &#039;&#039;&#039;- Original module&lt;br /&gt;
      &#039;&#039;&#039;- No original module exists within this kernel&lt;br /&gt;
    &#039;&#039;&#039;- Installation&lt;br /&gt;
      &#039;&#039;&#039;- Installing to /lib/modules/2.6.32-25-generic/updates/dkms/&lt;br /&gt;
   &#039;&#039;&#039;vboxnetflt.ko: Running module version sanity check.&lt;br /&gt;
    &#039;&#039;&#039;- Original module&lt;br /&gt;
      &#039;&#039;&#039;- No original module exists within this kernel&lt;br /&gt;
    &#039;&#039;&#039;- Installation&lt;br /&gt;
      &#039;&#039;&#039;- Installing to /lib/modules/2.6.32-25-generic/updates/dkms/depmod..............&lt;br /&gt;
   &#039;&#039;&#039;DKMS: install Completed.&lt;br /&gt;
    &#039;&#039;&#039;* Stopping VirtualBox kernel modules                                                                                  [ OK ] &lt;br /&gt;
    &#039;&#039;&#039;* Starting VirtualBox kernel modules                                                                                  [ OK ] &lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for python-central ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up virtualbox-ose-qt (3.1.6-dfsg-2ubuntu2) ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for libc-bin ...&lt;br /&gt;
   &#039;&#039;&#039;ldconfig deferred processing now taking place&lt;br /&gt;
   &#039;&#039;&#039;root@ubuntu:/tmp/Ubuntu_VMware# VBoxManage convertfromraw /tmp/Ubuntu_VMware.bin /tmp/Ubuntu_VBox/Ubuntu_VBox.vdi&lt;br /&gt;
   &#039;&#039;&#039;Sun VirtualBox Command Line Management Interface Version 3.1.6_OSE(C) 2005-2010 Sun Microsystems, Inc. All rights reserved.&lt;br /&gt;
   &#039;&#039;&#039;Converting from raw image file=&amp;quot;/tmp/Ubuntu_VMware.bin&amp;quot; to file=&amp;quot;/tmp/Ubuntu_VBox/Ubuntu_VBox.vdi&amp;quot;...&lt;br /&gt;
   &#039;&#039;&#039;Creating dynamic image with size 17179869184 bytes (16384MB)...&lt;br /&gt;
   &#039;&#039;&#039;root@ubuntu:/tmp/Ubuntu_VMware# &lt;br /&gt;
&lt;br /&gt;
Run VirtualBox, use the (File Menu) Virtual Media Manager and &#039;Add&#039; the newly cloned drive. This makes Virtual Box &#039;aware&#039; of the drive. Then go though the normal creation steps and choose this as the drive to use for the virtual machine.&lt;br /&gt;
&lt;br /&gt;
You should be able to boot up the newly created virtual machine.&lt;br /&gt;
&lt;br /&gt;
Enjoy your migration to Virtual Box!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Refrences:&lt;br /&gt;
&lt;br /&gt;
http://thedarkmaster.wordpress.com/2007/03/12/vmware-virtual-machine-to-virtual-box-conversion-how-to/&lt;br /&gt;
&lt;br /&gt;
https://wiki.ubuntu.com/UbuntuMagazine/HowTo/Switching_From_VMWare_To_VirtualBox:_.vmdk_To_.vdi_Using_Qemu_+_VdiTool&lt;br /&gt;
&lt;br /&gt;
http://www.cyberciti.biz/tips/converting-from-vmware-images-to-virtualbox-images.html#comments&lt;br /&gt;
&lt;br /&gt;
http://download.virtualbox.org/virtualbox/UserManual.pdf&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3576</id>
		<title>Converting VMWare .vmdk To VirtualBox .vdi Using Qemu+ and VBoxManage</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3576"/>
		<updated>2010-12-07T17:09:58Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If you want to switch to VirtualBox and have a Vmware Virtual Machine you want to use? You can convert a Vmware .vmdk file into a VirtualBox .vdi file that you can use on VirtualBox. &lt;br /&gt;
&lt;br /&gt;
First, download qemu, open a Console and execute: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo apt-get install qemu&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Next, open a console and go to your .vmdk virtual disc image folder and type this: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;qemu-img convert &amp;quot;harddrive-name&amp;quot;.vmdk /filelocation/&amp;quot;harddrive-name&amp;quot;.bin&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Change &amp;quot;harddrive-name&amp;quot; with the name of your .vmdk file and raw-file with the name of the new converted file you want to create. This takes a few minutes, After the conversion is completed. A raw hard disk image has been created. &lt;br /&gt;
&lt;br /&gt;
To convert a raw disk image to a VirtualBox Disk Image (.vdi) file use this command. &lt;br /&gt;
&lt;br /&gt;
The syntax is as follows:&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw /filelocation/&amp;quot;harddrive-name&amp;quot;.bin &amp;lt;outputfile&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo VBoxManage convertfromraw /home/tony/.VirtualBox/HardDisks/HardDisk1.bin /home/tony/.VirtualBox&#039;&#039;&#039; &lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD]&lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw stdin &amp;lt;outputfile&amp;gt; &amp;lt;bytes&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD] &lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
What the parameters mean:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;format&#039;&#039;&#039;  - Selects the disk image format to create. Default is .vdi. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;variant&#039;&#039;&#039;  - Allows to choose a file format variant for the output file. It is a comma-separated list of variant flags. Not all combinations are supported, and specifying inconsistent flags will result in an error message. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The second form forces VBoxManage to read the content for the disk image from standard input(useful for using that command in a pipe).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note: For compatibility with earlier versions of VirtualBox, the “convertdd” command is also supported and mapped internally to the “convertfromraw” command.&lt;br /&gt;
 &lt;br /&gt;
&#039;&#039;&#039;Here is a quick example of an actual conversion&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;tony@ubuntu:~$ sudo apt-get install qemu &lt;br /&gt;
   &#039;&#039;&#039;[sudo] password for tony:&lt;br /&gt;
   &#039;&#039;&#039;Reading package lists... Done&lt;br /&gt;
   &#039;&#039;&#039;Building dependency tree       &lt;br /&gt;
   &#039;&#039;&#039;Reading state information... Done&lt;br /&gt;
   &#039;&#039;&#039;The following packages were automatically installed and are no longer required:&lt;br /&gt;
   &#039;&#039;&#039;linux-headers-2.6.32-24 linux-headers-2.6.32-24-generic&lt;br /&gt;
   &#039;&#039;&#039;Use &#039;apt-get autoremove&#039; to remove them.&lt;br /&gt;
   &#039;&#039;&#039;The following extra packages will be installed:&lt;br /&gt;
   &#039;&#039;&#039;bridge-utils libaio1 qemu-common qemu-kvm seabios vgabios&lt;br /&gt;
   &#039;&#039;&#039;Suggested packages:&lt;br /&gt;
   &#039;&#039;&#039;mol-drivers-macosx openbios-sparc kvm-pxe ubuntu-vm-builder uml-utilities&lt;br /&gt;
   &#039;&#039;&#039;The following NEW packages will be installed:&lt;br /&gt;
   &#039;&#039;&#039;bridge-utils libaio1 qemu qemu-common qemu-kvm seabios vgabios&lt;br /&gt;
   &#039;&#039;&#039;0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded.&lt;br /&gt;
   &#039;&#039;&#039;Need to get 2,769kB of archives.&lt;br /&gt;
   &#039;&#039;&#039;After this operation, 8,192kB of additional disk space will be used.&lt;br /&gt;
   &#039;&#039;&#039;Do you want to continue [Y/n]? Y&lt;br /&gt;
   &#039;&#039;&#039;Get:1 http://us.archive.ubuntu.com/ubuntu/ lucid/main bridge-utils 1.4-5ubuntu2 [32.6kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:2 http://us.archive.ubuntu.com/ubuntu/ lucid/main libaio1 0.3.107-3ubuntu2 [9,512B]&lt;br /&gt;
   &#039;&#039;&#039;Get:3 http://us.archive.ubuntu.com/ubuntu/ lucid/main seabios 0.5.1-0ubuntu2 [48.2kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:4 http://us.archive.ubuntu.com/ubuntu/ lucid/main vgabios 0.6c-2ubuntu1 [78.5kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:5 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main qemu-common 0.12.3+noroms-0ubuntu9.2 [30.1kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:6 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main qemu-kvm 0.12.3+noroms-0ubuntu9.2 [2,556kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:7 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/universe qemu 0.12.3+noroms-0ubuntu9.2 [3.9kB]                     &lt;br /&gt;
   &#039;&#039;&#039;Fetched 2,769kB in 17s(156kB/s)                                                                                             &lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package bridge-utils.&lt;br /&gt;
   &#039;&#039;&#039;(Reading database ... 148121 files and directories currently installed.)&lt;br /&gt;
   &#039;&#039;&#039;Unpacking bridge-utils (from .../bridge-utils_1.4-5ubuntu2_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package libaio1.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking libaio1 (from .../libaio1_0.3.107-3ubuntu2_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package seabios.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking seabios (from .../seabios_0.5.1-0ubuntu2_all.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package vgabios.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking vgabios (from .../vgabios_0.6c-2ubuntu1_all.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package qemu-common.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking qemu-common (from .../qemu-common_0.12.3+noroms-0ubuntu9.2_all.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package qemu-kvm.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking qemu-kvm (from .../qemu-kvm_0.12.3+noroms-0ubuntu9.2_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package qemu.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking qemu (from .../qemu_0.12.3+noroms-0ubuntu9.2_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for ureadahead ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for man-db ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up bridge-utils (1.4-5ubuntu2) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up libaio1 (0.3.107-3ubuntu2) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up seabios (0.5.1-0ubuntu2) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up vgabios (0.6c-2ubuntu1) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up qemu-common (0.12.3+noroms-0ubuntu9.2) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up qemu-kvm (0.12.3+noroms-0ubuntu9.2) ...&lt;br /&gt;
   &#039;&#039;&#039;qemu-kvm start/running&lt;br /&gt;
   &#039;&#039;&#039;Setting up qemu (0.12.3+noroms-0ubuntu9.2) ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for libc-bin ...&lt;br /&gt;
   &#039;&#039;&#039;ldconfig deferred processing now taking place&lt;br /&gt;
   &#039;&#039;&#039;tony@ubuntu:~$ su&lt;br /&gt;
   &#039;&#039;&#039;Password: &lt;br /&gt;
   &#039;&#039;&#039;root@ubuntu:/home/tony# cd /tmp/Ubuntu_VMware&lt;br /&gt;
   &#039;&#039;&#039;root@ubuntu:/tmp/Ubuntu_VMware# qemu-img convert Ubuntu_VMware.vmdk /tmp/Ubuntu_VMware.bin&#039;&#039;&#039;&lt;br /&gt;
   &#039;&#039;&#039;root@ubuntu:/tmp/Ubuntu_VMware# VBoxManage convertfromraw /tmp/Ubuntu_VMware.bin /tmp/Ubuntu_VBox/Ubuntu_VBox.vdi&lt;br /&gt;
   &#039;&#039;&#039;The program &#039;VBoxManage&#039; is currently not installed.  You can install it by typing:&lt;br /&gt;
   &#039;&#039;&#039;apt-get install virtualbox-ose&lt;br /&gt;
   &#039;&#039;&#039;root@ubuntu:/tmp/Ubuntu_VMware# apt-get install virtualbox-ose&lt;br /&gt;
   &#039;&#039;&#039;Reading package lists... Done&lt;br /&gt;
   &#039;&#039;&#039;Building dependency tree       &lt;br /&gt;
   &#039;&#039;&#039;Reading state information... Done&lt;br /&gt;
   &#039;&#039;&#039;The following extra packages will be installed:&lt;br /&gt;
   &#039;&#039;&#039;dkms libaudio2 libmng1 libqt4-network libqt4-opengl libqtcore4 libqtgui4 virtualbox-ose-dkms virtualbox-ose-qt&lt;br /&gt;
   &#039;&#039;&#039;Suggested packages:&lt;br /&gt;
   &#039;&#039;&#039;nas qt4-qtconfig virtualbox-guest-additions&lt;br /&gt;
   &#039;&#039;&#039;The following NEW packages will be installed:&lt;br /&gt;
   &#039;&#039;&#039;dkms libaudio2 libmng1 libqt4-network libqt4-opengl libqtcore4 libqtgui4 virtualbox-ose virtualbox-ose-dkms&lt;br /&gt;
   &#039;&#039;&#039;virtualbox-ose-qt&lt;br /&gt;
   &#039;&#039;&#039;0 upgraded, 10 newly installed, 0 to remove and 0 not upgraded.&lt;br /&gt;
   &#039;&#039;&#039;Need to get 20.2MB of archives.&lt;br /&gt;
   &#039;&#039;&#039;After this operation, 70.4MB of additional disk space will be used.&lt;br /&gt;
   &#039;&#039;&#039;Do you want to continue [Y/n]? Y&lt;br /&gt;
   &#039;&#039;&#039;Get:1 http://us.archive.ubuntu.com/ubuntu/ lucid/main dkms 2.1.1.2-2fakesync1 [70.1kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:2 http://us.archive.ubuntu.com/ubuntu/ lucid/main libaudio2 1.9.2-3 [81.0kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:3 http://us.archive.ubuntu.com/ubuntu/ lucid/main libmng1 1.0.9-1ubuntu1 [209kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:4 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main libqtcore4 4:4.6.2-0ubuntu5.1 [1,722kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:5 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main libqt4-network 4:4.6.2-0ubuntu5.1 [444kB]                      &lt;br /&gt;
   &#039;&#039;&#039;Get:6 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main libqtgui4 4:4.6.2-0ubuntu5.1 [4,010kB]                         &lt;br /&gt;
   &#039;&#039;&#039;Get:7 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main libqt4-opengl 4:4.6.2-0ubuntu5.1 [265kB]                       &lt;br /&gt;
   &#039;&#039;&#039;Get:8 http://us.archive.ubuntu.com/ubuntu/ lucid/universe virtualbox-ose 3.1.6-dfsg-2ubuntu2 [8,265kB]                       &lt;br /&gt;
   &#039;&#039;&#039;Get:9 http://us.archive.ubuntu.com/ubuntu/ lucid/universe virtualbox-ose-dkms 3.1.6-dfsg-2ubuntu2 [501kB]                    &lt;br /&gt;
   &#039;&#039;&#039;Get:10 http://us.archive.ubuntu.com/ubuntu/ lucid/universe virtualbox-ose-qt 3.1.6-dfsg-2ubuntu2 [4,678kB]                   &lt;br /&gt;
   &#039;&#039;&#039;Fetched 20.2MB in 2min 3s (164kB/s)                                                                                          &lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package dkms.&lt;br /&gt;
   &#039;&#039;&#039;(Reading database ... 148269 files and directories currently installed.)&lt;br /&gt;
   &#039;&#039;&#039;Unpacking dkms (from .../dkms_2.1.1.2-2fakesync1_all.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package libaudio2.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking libaudio2 (from .../libaudio2_1.9.2-3_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package libmng1.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking libmng1 (from .../libmng1_1.0.9-1ubuntu1_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package libqtcore4.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking libqtcore4 (from .../libqtcore4_4%3a4.6.2-0ubuntu5.1_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package libqt4-network.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking libqt4-network (from .../libqt4-network_4%3a4.6.2-0ubuntu5.1_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package libqtgui4.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking libqtgui4 (from .../libqtgui4_4%3a4.6.2-0ubuntu5.1_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package libqt4-opengl.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking libqt4-opengl (from .../libqt4-opengl_4%3a4.6.2-0ubuntu5.1_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package virtualbox-ose.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking virtualbox-ose (from .../virtualbox-ose_3.1.6-dfsg-2ubuntu2_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package virtualbox-ose-dkms.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking virtualbox-ose-dkms (from .../virtualbox-ose-dkms_3.1.6-dfsg-2ubuntu2_all.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package virtualbox-ose-qt.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking virtualbox-ose-qt (from .../virtualbox-ose-qt_3.1.6-dfsg-2ubuntu2_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for man-db ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for ureadahead ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for desktop-file-utils ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for python-gmenu ... &lt;br /&gt;
   &#039;&#039;&#039;Rebuilding /usr/share/applications/desktop.en_US.utf8.cache...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for python-support ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up dkms (2.1.1.2-2fakesync1) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up libaudio2 (1.9.2-3) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up libmng1 (1.0.9-1ubuntu1) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up libqtcore4 (4:4.6.2-0ubuntu5.1) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up libqt4-network (4:4.6.2-0ubuntu5.1) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up libqtgui4 (4:4.6.2-0ubuntu5.1) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up libqt4-opengl (4:4.6.2-0ubuntu5.1) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up virtualbox-ose (3.1.6-dfsg-2ubuntu2) ...&lt;br /&gt;
   &#039;&#039;&#039; * Stopping VirtualBox kernel modules                                                                    [ OK ]&lt;br /&gt;
   &#039;&#039;&#039; * StartingVirtualBoxkernelModules                                                                                            &lt;br /&gt;
   &#039;&#039;&#039; * No suitable module for running kernel found                                                           [fail]&lt;br /&gt;
   &#039;&#039;&#039;invoke-rc.d: initscript virtualbox-ose, action &amp;quot;restart&amp;quot; failed.&lt;br /&gt;
   &#039;&#039;&#039;Setting up virtualbox-ose-dkms (3.1.6-dfsg-2ubuntu2) ...&lt;br /&gt;
   &#039;&#039;&#039;Loading new virtualbox-ose-3.1.6 DKMS files...&lt;br /&gt;
   &#039;&#039;&#039;First Installation: checking all kernels...&lt;br /&gt;
   &#039;&#039;&#039;Building only for 2.6.32-25-generic&lt;br /&gt;
   &#039;&#039;&#039;Building for architecture i686&lt;br /&gt;
   &#039;&#039;&#039;Building initial module for 2.6.32-25-generic Done.&lt;br /&gt;
   &#039;&#039;&#039;vboxdrv.ko: Running module version sanity check.&lt;br /&gt;
   &#039;&#039;&#039;- Original module&lt;br /&gt;
      &#039;&#039;&#039;- No original module exists within this kernel&lt;br /&gt;
    &#039;&#039;&#039;- Installation&lt;br /&gt;
      &#039;&#039;&#039;- Installing to /lib/modules/2.6.32-25-generic/updates/dkms/&lt;br /&gt;
   &#039;&#039;&#039;vboxnetadp.ko:Running module version sanity check.&lt;br /&gt;
    &#039;&#039;&#039;- Original module&lt;br /&gt;
      &#039;&#039;&#039;- No original module exists within this kernel&lt;br /&gt;
    &#039;&#039;&#039;- Installation&lt;br /&gt;
      &#039;&#039;&#039;- Installing to /lib/modules/2.6.32-25-generic/updates/dkms/&lt;br /&gt;
   &#039;&#039;&#039;vboxnetflt.ko:&lt;br /&gt;
   &#039;&#039;&#039;Running module version sanity check.&lt;br /&gt;
    &#039;&#039;&#039;- Original module&lt;br /&gt;
      &#039;&#039;&#039;- No original module exists within this kernel&lt;br /&gt;
    &#039;&#039;&#039;- Installation&lt;br /&gt;
      &#039;&#039;&#039;- Installing to /lib/modules/2.6.32-25-generic/updates/dkms/depmod..............&lt;br /&gt;
   &#039;&#039;&#039;DKMS: install Completed.&lt;br /&gt;
    &#039;&#039;&#039;* Stopping VirtualBox kernel modules                                                                                  [ OK ] &lt;br /&gt;
    &#039;&#039;&#039;* Starting VirtualBox kernel modules                                                                                  [ OK ] &lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for python-central ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up virtualbox-ose-qt (3.1.6-dfsg-2ubuntu2) ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for libc-bin ...&lt;br /&gt;
   &#039;&#039;&#039;ldconfig deferred processing now taking place&lt;br /&gt;
   &#039;&#039;&#039;root@ubuntu:/tmp/Ubuntu_VMware# VBoxManage convertfromraw /tmp/Ubuntu_VMware.bin /tmp/Ubuntu_VBox/Ubuntu_VBox.vdi&lt;br /&gt;
   &#039;&#039;&#039;Sun VirtualBox Command Line Management Interface Version 3.1.6_OSE(C) 2005-2010 Sun Microsystems, Inc. All rights reserved.&lt;br /&gt;
   &#039;&#039;&#039;Converting from raw image file=&amp;quot;/tmp/Ubuntu_VMware.bin&amp;quot; to file=&amp;quot;/tmp/Ubuntu_VBox/Ubuntu_VBox.vdi&amp;quot;...&lt;br /&gt;
   &#039;&#039;&#039;Creating dynamic image with size 17179869184 bytes (16384MB)...&lt;br /&gt;
   &#039;&#039;&#039;root@ubuntu:/tmp/Ubuntu_VMware# &lt;br /&gt;
&lt;br /&gt;
Run VirtualBox, use the (File Menu) Virtual Media Manager and &#039;Add&#039; the newly cloned drive. This makes Virtual Box &#039;aware&#039; of the drive. Then go though the normal creation steps and choose this as the drive to use for the virtual machine.&lt;br /&gt;
&lt;br /&gt;
You should be able to boot up the newly created virtual machine.&lt;br /&gt;
&lt;br /&gt;
Enjoy your migration to Virtual Box!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Refrences:&lt;br /&gt;
&lt;br /&gt;
http://thedarkmaster.wordpress.com/2007/03/12/vmware-virtual-machine-to-virtual-box-conversion-how-to/&lt;br /&gt;
&lt;br /&gt;
https://wiki.ubuntu.com/UbuntuMagazine/HowTo/Switching_From_VMWare_To_VirtualBox:_.vmdk_To_.vdi_Using_Qemu_+_VdiTool&lt;br /&gt;
&lt;br /&gt;
http://www.cyberciti.biz/tips/converting-from-vmware-images-to-virtualbox-images.html#comments&lt;br /&gt;
&lt;br /&gt;
http://download.virtualbox.org/virtualbox/UserManual.pdf&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3575</id>
		<title>Converting VMWare .vmdk To VirtualBox .vdi Using Qemu+ and VBoxManage</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3575"/>
		<updated>2010-12-07T17:01:35Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If you want to switch to VirtualBox and have a Vmware Virtual Machine you want to use? You can convert a Vmware .vmdk file into a VirtualBox .vdi file that you can use on VirtualBox. &lt;br /&gt;
&lt;br /&gt;
First, download qemu, open a Console and execute: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo apt-get install qemu&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Next, open a console and go to your .vmdk virtual disc image folder and type this: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;qemu-img convert &amp;quot;harddrive-name&amp;quot;.vmdk /filelocation/&amp;quot;harddrive-name&amp;quot;.bin&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Change &amp;quot;harddrive-name&amp;quot; with the name of your .vmdk file and raw-file with the name of the new converted file you want to create. This takes a few minutes, After the conversion is completed. A raw hard disk image has been created. &lt;br /&gt;
&lt;br /&gt;
To convert a raw disk image to a VirtualBox Disk Image (.vdi) file use this command. &lt;br /&gt;
&lt;br /&gt;
The syntax is as follows:&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw /filelocation/&amp;quot;harddrive-name&amp;quot;.bin &amp;lt;outputfile&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo VBoxManage convertfromraw /home/tony/.VirtualBox/HardDisks/HardDisk1.bin /home/tony/.VirtualBox&#039;&#039;&#039; &lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD]&lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw stdin &amp;lt;outputfile&amp;gt; &amp;lt;bytes&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD] &lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
What the parameters mean:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;format&#039;&#039;&#039;  - Selects the disk image format to create. Default is .vdi. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;variant&#039;&#039;&#039;  - Allows to choose a file format variant for the output file. It is a comma-separated list of variant flags. Not all combinations are supported, and specifying inconsistent flags will result in an error message. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The second form forces VBoxManage to read the content for the disk image from standard input(useful for using that command in a pipe).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note: For compatibility with earlier versions of VirtualBox, the “convertdd” command is also supported and mapped internally to the “convertfromraw” command.&lt;br /&gt;
 &lt;br /&gt;
&#039;&#039;&#039;Here is a quick example of an actual conversion&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;tony@ubuntu:~$ sudo apt-get install qemu &lt;br /&gt;
   &#039;&#039;&#039;[sudo] password for tony:&lt;br /&gt;
   &#039;&#039;&#039;Reading package lists... Done&lt;br /&gt;
   &#039;&#039;&#039;Building dependency tree       &lt;br /&gt;
   &#039;&#039;&#039;Reading state information... Done&lt;br /&gt;
   &#039;&#039;&#039;The following packages were automatically installed and are no longer required:&lt;br /&gt;
   &#039;&#039;&#039;linux-headers-2.6.32-24 linux-headers-2.6.32-24-generic&lt;br /&gt;
   &#039;&#039;&#039;Use &#039;apt-get autoremove&#039; to remove them.&lt;br /&gt;
   &#039;&#039;&#039;The following extra packages will be installed:&lt;br /&gt;
   &#039;&#039;&#039;bridge-utils libaio1 qemu-common qemu-kvm seabios vgabios&lt;br /&gt;
   &#039;&#039;&#039;Suggested packages:&lt;br /&gt;
   &#039;&#039;&#039;mol-drivers-macosx openbios-sparc kvm-pxe ubuntu-vm-builder uml-utilities&lt;br /&gt;
   &#039;&#039;&#039;The following NEW packages will be installed:&lt;br /&gt;
   &#039;&#039;&#039;bridge-utils libaio1 qemu qemu-common qemu-kvm seabios vgabios&lt;br /&gt;
   &#039;&#039;&#039;0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded.&lt;br /&gt;
   &#039;&#039;&#039;Need to get 2,769kB of archives.&lt;br /&gt;
   &#039;&#039;&#039;After this operation, 8,192kB of additional disk space will be used.&lt;br /&gt;
   &#039;&#039;&#039;Do you want to continue [Y/n]? Y&lt;br /&gt;
   &#039;&#039;&#039;Get:1 http://us.archive.ubuntu.com/ubuntu/ lucid/main bridge-utils 1.4-5ubuntu2 [32.6kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:2 http://us.archive.ubuntu.com/ubuntu/ lucid/main libaio1 0.3.107-3ubuntu2 [9,512B]&lt;br /&gt;
   &#039;&#039;&#039;Get:3 http://us.archive.ubuntu.com/ubuntu/ lucid/main seabios 0.5.1-0ubuntu2 [48.2kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:4 http://us.archive.ubuntu.com/ubuntu/ lucid/main vgabios 0.6c-2ubuntu1 [78.5kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:5 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main qemu-common 0.12.3+noroms-0ubuntu9.2 [30.1kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:6 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main qemu-kvm 0.12.3+noroms-0ubuntu9.2 [2,556kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:7 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/universe qemu 0.12.3+noroms-0ubuntu9.2 [3.9kB]                     &lt;br /&gt;
   &#039;&#039;&#039;Fetched 2,769kB in 17s(156kB/s)                                                                                             &lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package bridge-utils.&lt;br /&gt;
   &#039;&#039;&#039;(Reading database ... 148121 files and directories currently installed.)&lt;br /&gt;
   &#039;&#039;&#039;Unpacking bridge-utils (from .../bridge-utils_1.4-5ubuntu2_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package libaio1.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking libaio1 (from .../libaio1_0.3.107-3ubuntu2_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package seabios.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking seabios (from .../seabios_0.5.1-0ubuntu2_all.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package vgabios.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking vgabios (from .../vgabios_0.6c-2ubuntu1_all.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package qemu-common.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking qemu-common (from .../qemu-common_0.12.3+noroms-0ubuntu9.2_all.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package qemu-kvm.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking qemu-kvm (from .../qemu-kvm_0.12.3+noroms-0ubuntu9.2_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package qemu.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking qemu (from .../qemu_0.12.3+noroms-0ubuntu9.2_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for ureadahead ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for man-db ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up bridge-utils (1.4-5ubuntu2) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up libaio1 (0.3.107-3ubuntu2) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up seabios (0.5.1-0ubuntu2) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up vgabios (0.6c-2ubuntu1) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up qemu-common (0.12.3+noroms-0ubuntu9.2) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up qemu-kvm (0.12.3+noroms-0ubuntu9.2) ...&lt;br /&gt;
   &#039;&#039;&#039;qemu-kvm start/running&lt;br /&gt;
   &#039;&#039;&#039;Setting up qemu (0.12.3+noroms-0ubuntu9.2) ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for libc-bin ...&lt;br /&gt;
   &#039;&#039;&#039;ldconfig deferred processing now taking place&lt;br /&gt;
   &#039;&#039;&#039;tony@ubuntu:~$ su&lt;br /&gt;
   &#039;&#039;&#039;Password: &lt;br /&gt;
   &#039;&#039;&#039;root@ubuntu:/home/tony# cd /tmp/Ubuntu_VMware&lt;br /&gt;
   &#039;&#039;&#039;root@ubuntu:/tmp/Ubuntu_VMware# qemu-img convert Ubuntu_VMware.vmdk /tmp/Ubuntu_VMware.bin&#039;&#039;&#039;&lt;br /&gt;
   &#039;&#039;&#039;root@ubuntu:/tmp/Ubuntu_VMware# VBoxManage convertfromraw /tmp/Ubuntu_VMware.bin /tmp/Ubuntu_VBox/Ubuntu_VBox.vdi&lt;br /&gt;
   &#039;&#039;&#039;The program &#039;VBoxManage&#039; is currently not installed.  You can install it by typing:&lt;br /&gt;
   &#039;&#039;&#039;apt-get install virtualbox-ose&lt;br /&gt;
   &#039;&#039;&#039;root@ubuntu:/tmp/Ubuntu_VMware# apt-get install virtualbox-ose&lt;br /&gt;
   &#039;&#039;&#039;Reading package lists... Done&lt;br /&gt;
   &#039;&#039;&#039;Building dependency tree       &lt;br /&gt;
   &#039;&#039;&#039;Reading state information... Done&lt;br /&gt;
   &#039;&#039;&#039;The following extra packages will be installed:&lt;br /&gt;
   &#039;&#039;&#039;dkms libaudio2 libmng1 libqt4-network libqt4-opengl libqtcore4 libqtgui4 virtualbox-ose-dkms virtualbox-ose-qt&lt;br /&gt;
   &#039;&#039;&#039;Suggested packages:&lt;br /&gt;
   &#039;&#039;&#039;nas qt4-qtconfig virtualbox-guest-additions&lt;br /&gt;
   &#039;&#039;&#039;The following NEW packages will be installed:&lt;br /&gt;
   &#039;&#039;&#039;dkms libaudio2 libmng1 libqt4-network libqt4-opengl libqtcore4 libqtgui4 virtualbox-ose virtualbox-ose-dkms&lt;br /&gt;
   &#039;&#039;&#039;virtualbox-ose-qt&lt;br /&gt;
   &#039;&#039;&#039;0 upgraded, 10 newly installed, 0 to remove and 0 not upgraded.&lt;br /&gt;
   &#039;&#039;&#039;Need to get 20.2MB of archives.&lt;br /&gt;
   &#039;&#039;&#039;After this operation, 70.4MB of additional disk space will be used.&lt;br /&gt;
   &#039;&#039;&#039;Do you want to continue [Y/n]? Y&lt;br /&gt;
   &#039;&#039;&#039;Get:1 http://us.archive.ubuntu.com/ubuntu/ lucid/main dkms 2.1.1.2-2fakesync1 [70.1kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:2 http://us.archive.ubuntu.com/ubuntu/ lucid/main libaudio2 1.9.2-3 [81.0kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:3 http://us.archive.ubuntu.com/ubuntu/ lucid/main libmng1 1.0.9-1ubuntu1 [209kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:4 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main libqtcore4 4:4.6.2-0ubuntu5.1 [1,722kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:5 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main libqt4-network 4:4.6.2-0ubuntu5.1 [444kB]                      &lt;br /&gt;
   &#039;&#039;&#039;Get:6 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main libqtgui4 4:4.6.2-0ubuntu5.1 [4,010kB]                         &lt;br /&gt;
   &#039;&#039;&#039;Get:7 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main libqt4-opengl 4:4.6.2-0ubuntu5.1 [265kB]                       &lt;br /&gt;
   &#039;&#039;&#039;Get:8 http://us.archive.ubuntu.com/ubuntu/ lucid/universe virtualbox-ose 3.1.6-dfsg-2ubuntu2 [8,265kB]                       &lt;br /&gt;
   &#039;&#039;&#039;Get:9 http://us.archive.ubuntu.com/ubuntu/ lucid/universe virtualbox-ose-dkms 3.1.6-dfsg-2ubuntu2 [501kB]                    &lt;br /&gt;
   &#039;&#039;&#039;Get:10 http://us.archive.ubuntu.com/ubuntu/ lucid/universe virtualbox-ose-qt 3.1.6-dfsg-2ubuntu2 [4,678kB]                   &lt;br /&gt;
   &#039;&#039;&#039;Fetched 20.2MB in 2min 3s (164kB/s)                                                                                          &lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package dkms.&lt;br /&gt;
   &#039;&#039;&#039;(Reading database ... 148269 files and directories currently installed.)&lt;br /&gt;
   &#039;&#039;&#039;Unpacking dkms (from .../dkms_2.1.1.2-2fakesync1_all.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package libaudio2.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking libaudio2 (from .../libaudio2_1.9.2-3_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package libmng1.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking libmng1 (from .../libmng1_1.0.9-1ubuntu1_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package libqtcore4.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking libqtcore4 (from .../libqtcore4_4%3a4.6.2-0ubuntu5.1_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package libqt4-network.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking libqt4-network (from .../libqt4-network_4%3a4.6.2-0ubuntu5.1_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package libqtgui4.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking libqtgui4 (from .../libqtgui4_4%3a4.6.2-0ubuntu5.1_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package libqt4-opengl.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking libqt4-opengl (from .../libqt4-opengl_4%3a4.6.2-0ubuntu5.1_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package virtualbox-ose.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking virtualbox-ose (from .../virtualbox-ose_3.1.6-dfsg-2ubuntu2_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package virtualbox-ose-dkms.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking virtualbox-ose-dkms (from .../virtualbox-ose-dkms_3.1.6-dfsg-2ubuntu2_all.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package virtualbox-ose-qt.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking virtualbox-ose-qt (from .../virtualbox-ose-qt_3.1.6-dfsg-2ubuntu2_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for man-db ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for ureadahead ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for desktop-file-utils ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for python-gmenu ... &lt;br /&gt;
   &#039;&#039;&#039;Rebuilding /usr/share/applications/desktop.en_US.utf8.cache...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for python-support ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up dkms (2.1.1.2-2fakesync1) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up libaudio2 (1.9.2-3) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up libmng1 (1.0.9-1ubuntu1) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up libqtcore4 (4:4.6.2-0ubuntu5.1) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up libqt4-network (4:4.6.2-0ubuntu5.1) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up libqtgui4 (4:4.6.2-0ubuntu5.1) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up libqt4-opengl (4:4.6.2-0ubuntu5.1) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up virtualbox-ose (3.1.6-dfsg-2ubuntu2) ...&lt;br /&gt;
   &#039;&#039;&#039; * Stopping VirtualBox kernel modules                                                                    [ OK ]&lt;br /&gt;
   &#039;&#039;&#039; * StartingVirtualBoxkernelModules                                                                                            &lt;br /&gt;
   &#039;&#039;&#039; * No suitable module for running kernel found                                                           [fail]&lt;br /&gt;
invoke-rc.d: initscript virtualbox-ose, action &amp;quot;restart&amp;quot; failed.&lt;br /&gt;
&lt;br /&gt;
Setting up virtualbox-ose-dkms (3.1.6-dfsg-2ubuntu2) ...&lt;br /&gt;
Loading new virtualbox-ose-3.1.6 DKMS files...&lt;br /&gt;
First Installation: checking all kernels...&lt;br /&gt;
Building only for 2.6.32-25-generic&lt;br /&gt;
Building for architecture i686&lt;br /&gt;
Building initial module for 2.6.32-25-generic&lt;br /&gt;
Done.&lt;br /&gt;
&lt;br /&gt;
vboxdrv.ko:&lt;br /&gt;
Running module version sanity check.&lt;br /&gt;
 - Original module&lt;br /&gt;
   - No original module exists within this kernel&lt;br /&gt;
 - Installation&lt;br /&gt;
   - Installing to /lib/modules/2.6.32-25-generic/updates/dkms/&lt;br /&gt;
&lt;br /&gt;
vboxnetadp.ko:&lt;br /&gt;
Running module version sanity check.&lt;br /&gt;
 - Original module&lt;br /&gt;
   - No original module exists within this kernel&lt;br /&gt;
 - Installation&lt;br /&gt;
   - Installing to /lib/modules/2.6.32-25-generic/updates/dkms/&lt;br /&gt;
&lt;br /&gt;
vboxnetflt.ko:&lt;br /&gt;
Running module version sanity check.&lt;br /&gt;
 - Original module&lt;br /&gt;
   - No original module exists within this kernel&lt;br /&gt;
 - Installation&lt;br /&gt;
   - Installing to /lib/modules/2.6.32-25-generic/updates/dkms/&lt;br /&gt;
&lt;br /&gt;
depmod..............&lt;br /&gt;
&lt;br /&gt;
DKMS: install Completed.&lt;br /&gt;
 * Stopping VirtualBox kernel modules                                                                                  [ OK ] &lt;br /&gt;
 * Starting VirtualBox kernel modules                                                                                  [ OK ] &lt;br /&gt;
&lt;br /&gt;
Processing triggers for python-central ...&lt;br /&gt;
Setting up virtualbox-ose-qt (3.1.6-dfsg-2ubuntu2) ...&lt;br /&gt;
&lt;br /&gt;
Processing triggers for libc-bin ...&lt;br /&gt;
ldconfig deferred processing now taking place&lt;br /&gt;
root@ubuntu:/tmp/Ubuntu_VMware# VBoxManage convertfromraw /tmp/Ubuntu_VMware.bin /tmp/Ubuntu_VBox/Ubuntu_VBox.vdi&lt;br /&gt;
Sun VirtualBox Command Line Management Interface Version 3.1.6_OSE&lt;br /&gt;
(C) 2005-2010 Sun Microsystems, Inc.&lt;br /&gt;
All rights reserved.&lt;br /&gt;
&lt;br /&gt;
Converting from raw image file=&amp;quot;/tmp/Ubuntu_VMware.bin&amp;quot; to file=&amp;quot;/tmp/Ubuntu_VBox/Ubuntu_VBox.vdi&amp;quot;...&lt;br /&gt;
Creating dynamic image with size 17179869184 bytes (16384MB)...&lt;br /&gt;
root@ubuntu:/tmp/Ubuntu_VMware# &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Run VirtualBox, use the (File Menu) Virtual Media Manager and &#039;Add&#039; the newly cloned drive. This makes Virtual Box &#039;aware&#039; of the drive. Then go though the normal creation steps and choose this as the drive to use for the virtual machine.&lt;br /&gt;
&lt;br /&gt;
You should be able to boot up the newly created virtual machine.&lt;br /&gt;
&lt;br /&gt;
Enjoy your migration to Virtual Box!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Refrences:&lt;br /&gt;
&lt;br /&gt;
http://thedarkmaster.wordpress.com/2007/03/12/vmware-virtual-machine-to-virtual-box-conversion-how-to/&lt;br /&gt;
&lt;br /&gt;
https://wiki.ubuntu.com/UbuntuMagazine/HowTo/Switching_From_VMWare_To_VirtualBox:_.vmdk_To_.vdi_Using_Qemu_+_VdiTool&lt;br /&gt;
&lt;br /&gt;
http://www.cyberciti.biz/tips/converting-from-vmware-images-to-virtualbox-images.html#comments&lt;br /&gt;
&lt;br /&gt;
http://download.virtualbox.org/virtualbox/UserManual.pdf&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3555</id>
		<title>Converting VMWare .vmdk To VirtualBox .vdi Using Qemu+ and VBoxManage</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3555"/>
		<updated>2010-11-24T00:37:21Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If you want to switch to VirtualBox and have a Vmware Virtual Machine you want to use? You can convert a Vmware .vmdk file into a VirtualBox .vdi file that you can use on VirtualBox. &lt;br /&gt;
&lt;br /&gt;
First, download qemu, open a Console and execute: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo apt-get install qemu&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Next, open a console and go to your .vmdk virtual disc image folder and type this: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;qemu-img convert &amp;quot;harddrive-name&amp;quot;.vmdk /filelocation/&amp;quot;harddrive-name&amp;quot;.bin&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Change &amp;quot;harddrive-name&amp;quot; with the name of your .vmdk file and raw-file with the name of the new converted file you want to create. This takes a few minutes, After the conversion is completed. A raw hard disk image has been created. &lt;br /&gt;
&lt;br /&gt;
To convert a raw disk image to a VirtualBox Disk Image (.vdi) file use this command. &lt;br /&gt;
&lt;br /&gt;
The syntax is as follows:&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw /filelocation/&amp;quot;harddrive-name&amp;quot;.bin &amp;lt;outputfile&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo VBoxManage convertfromraw /home/tony/.VirtualBox/HardDisks/HardDisk1.bin /home/tony/.VirtualBox&#039;&#039;&#039; &lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD]&lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw stdin &amp;lt;outputfile&amp;gt; &amp;lt;bytes&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD] &lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
What the parameters mean:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;format&#039;&#039;&#039;  - Selects the disk image format to create. Default is .vdi. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;variant&#039;&#039;&#039;  - Allows to choose a file format variant for the output file. It is a comma-separated list of variant flags. Not all combinations are supported, and specifying inconsistent flags will result in an error message. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The second form forces VBoxManage to read the content for the disk image from standard input(useful for using that command in a pipe).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note: For compatibility with earlier versions of VirtualBox, the “convertdd” command is also supported and mapped internally to the “convertfromraw” command.&lt;br /&gt;
 &lt;br /&gt;
&#039;&#039;&#039;Here is a quick example of an actual conversion&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;tony@ubuntu:~$ sudo apt-get install qemu &lt;br /&gt;
   &#039;&#039;&#039;[sudo] password for tony:&lt;br /&gt;
   &#039;&#039;&#039;Reading package lists... Done&lt;br /&gt;
   &#039;&#039;&#039;Building dependency tree       &lt;br /&gt;
   &#039;&#039;&#039;Reading state information... Done&lt;br /&gt;
   &#039;&#039;&#039;The following packages were automatically installed and are no longer required:&lt;br /&gt;
   &#039;&#039;&#039;linux-headers-2.6.32-24 linux-headers-2.6.32-24-generic&lt;br /&gt;
   &#039;&#039;&#039;Use &#039;apt-get autoremove&#039; to remove them.&lt;br /&gt;
   &#039;&#039;&#039;The following extra packages will be installed:&lt;br /&gt;
   &#039;&#039;&#039;bridge-utils libaio1 qemu-common qemu-kvm seabios vgabios&lt;br /&gt;
   &#039;&#039;&#039;Suggested packages:&lt;br /&gt;
   &#039;&#039;&#039;mol-drivers-macosx openbios-sparc kvm-pxe ubuntu-vm-builder uml-utilities&lt;br /&gt;
   &#039;&#039;&#039;The following NEW packages will be installed:&lt;br /&gt;
   &#039;&#039;&#039;bridge-utils libaio1 qemu qemu-common qemu-kvm seabios vgabios&lt;br /&gt;
   &#039;&#039;&#039;0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded.&lt;br /&gt;
   &#039;&#039;&#039;Need to get 2,769kB of archives.&lt;br /&gt;
   &#039;&#039;&#039;After this operation, 8,192kB of additional disk space will be used.&lt;br /&gt;
   &#039;&#039;&#039;Do you want to continue [Y/n]? Y&lt;br /&gt;
   &#039;&#039;&#039;Get:1 http://us.archive.ubuntu.com/ubuntu/ lucid/main bridge-utils 1.4-5ubuntu2 [32.6kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:2 http://us.archive.ubuntu.com/ubuntu/ lucid/main libaio1 0.3.107-3ubuntu2 [9,512B]&lt;br /&gt;
   &#039;&#039;&#039;Get:3 http://us.archive.ubuntu.com/ubuntu/ lucid/main seabios 0.5.1-0ubuntu2 [48.2kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:4 http://us.archive.ubuntu.com/ubuntu/ lucid/main vgabios 0.6c-2ubuntu1 [78.5kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:5 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main qemu-common 0.12.3+noroms-0ubuntu9.2 [30.1kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:6 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main qemu-kvm 0.12.3+noroms-0ubuntu9.2 [2,556kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:7 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/universe qemu 0.12.3+noroms-0ubuntu9.2 [3.9kB]                     &lt;br /&gt;
   &#039;&#039;&#039;Fetched 2,769kB in 17s(156kB/s)                                                                                             &lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package bridge-utils.&lt;br /&gt;
   &#039;&#039;&#039;(Reading database ... 148121 files and directories currently installed.)&lt;br /&gt;
   &#039;&#039;&#039;Unpacking bridge-utils (from .../bridge-utils_1.4-5ubuntu2_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package libaio1.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking libaio1 (from .../libaio1_0.3.107-3ubuntu2_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package seabios.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking seabios (from .../seabios_0.5.1-0ubuntu2_all.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package vgabios.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking vgabios (from .../vgabios_0.6c-2ubuntu1_all.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package qemu-common.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking qemu-common (from .../qemu-common_0.12.3+noroms-0ubuntu9.2_all.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package qemu-kvm.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking qemu-kvm (from .../qemu-kvm_0.12.3+noroms-0ubuntu9.2_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package qemu.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking qemu (from .../qemu_0.12.3+noroms-0ubuntu9.2_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for ureadahead ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for man-db ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up bridge-utils (1.4-5ubuntu2) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up libaio1 (0.3.107-3ubuntu2) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up seabios (0.5.1-0ubuntu2) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up vgabios (0.6c-2ubuntu1) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up qemu-common (0.12.3+noroms-0ubuntu9.2) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up qemu-kvm (0.12.3+noroms-0ubuntu9.2) ...&lt;br /&gt;
   &#039;&#039;&#039;qemu-kvm start/running&lt;br /&gt;
   &#039;&#039;&#039;Setting up qemu (0.12.3+noroms-0ubuntu9.2) ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for libc-bin ...&lt;br /&gt;
   &#039;&#039;&#039;ldconfig deferred processing now taking place&lt;br /&gt;
   &#039;&#039;&#039;tony@ubuntu:~$ su&lt;br /&gt;
   &#039;&#039;&#039;Password: &lt;br /&gt;
   &#039;&#039;&#039;root@ubuntu:/home/tony# cd /tmp/Ubuntu_VMware&lt;br /&gt;
   &#039;&#039;&#039;root@ubuntu:/tmp/Ubuntu_VMware# qemu-img convert Ubuntu_VMware.vmdk /tmp/Ubuntu_VMware.bin&#039;&#039;&#039;&lt;br /&gt;
   &#039;&#039;&#039;root@ubuntu:/tmp/Ubuntu_VMware# VBoxManage convertfromraw /tmp/Ubuntu_VMware.bin /tmp/Ubuntu_VBox/Ubuntu_VBox.vdi&lt;br /&gt;
   &#039;&#039;&#039;The program &#039;VBoxManage&#039; is currently not installed.  You can install it by typing:&lt;br /&gt;
   &#039;&#039;&#039;apt-get install virtualbox-ose&lt;br /&gt;
   &#039;&#039;&#039;root@ubuntu:/tmp/Ubuntu_VMware# apt-get install virtualbox-ose&lt;br /&gt;
   &#039;&#039;&#039;Reading package lists... Done&lt;br /&gt;
   &#039;&#039;&#039;Building dependency tree       &lt;br /&gt;
   &#039;&#039;&#039;Reading state information... Done&lt;br /&gt;
   &#039;&#039;&#039;The following extra packages will be installed:&lt;br /&gt;
   &#039;&#039;&#039;dkms libaudio2 libmng1 libqt4-network libqt4-opengl libqtcore4 libqtgui4 virtualbox-ose-dkms virtualbox-ose-qt&lt;br /&gt;
   &#039;&#039;&#039;Suggested packages:&lt;br /&gt;
   &#039;&#039;&#039;nas qt4-qtconfig virtualbox-guest-additions&lt;br /&gt;
   &#039;&#039;&#039;The following NEW packages will be installed:&lt;br /&gt;
   &#039;&#039;&#039;dkms libaudio2 libmng1 libqt4-network libqt4-opengl libqtcore4 libqtgui4 virtualbox-ose virtualbox-ose-dkms&lt;br /&gt;
   &#039;&#039;&#039;virtualbox-ose-qt&lt;br /&gt;
   &#039;&#039;&#039;0 upgraded, 10 newly installed, 0 to remove and 0 not upgraded.&lt;br /&gt;
   &#039;&#039;&#039;Need to get 20.2MB of archives.&lt;br /&gt;
   &#039;&#039;&#039;After this operation, 70.4MB of additional disk space will be used.&lt;br /&gt;
   &#039;&#039;&#039;Do you want to continue [Y/n]? Y&lt;br /&gt;
   &#039;&#039;&#039;Get:1 http://us.archive.ubuntu.com/ubuntu/ lucid/main dkms 2.1.1.2-2fakesync1 [70.1kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:2 http://us.archive.ubuntu.com/ubuntu/ lucid/main libaudio2 1.9.2-3 [81.0kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:3 http://us.archive.ubuntu.com/ubuntu/ lucid/main libmng1 1.0.9-1ubuntu1 [209kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:4 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main libqtcore4 4:4.6.2-0ubuntu5.1 [1,722kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:5 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main libqt4-network 4:4.6.2-0ubuntu5.1 [444kB]                      &lt;br /&gt;
   &#039;&#039;&#039;Get:6 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main libqtgui4 4:4.6.2-0ubuntu5.1 [4,010kB]                         &lt;br /&gt;
   &#039;&#039;&#039;Get:7 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main libqt4-opengl 4:4.6.2-0ubuntu5.1 [265kB]                       &lt;br /&gt;
   &#039;&#039;&#039;Get:8 http://us.archive.ubuntu.com/ubuntu/ lucid/universe virtualbox-ose 3.1.6-dfsg-2ubuntu2 [8,265kB]                       &lt;br /&gt;
   &#039;&#039;&#039;Get:9 http://us.archive.ubuntu.com/ubuntu/ lucid/universe virtualbox-ose-dkms 3.1.6-dfsg-2ubuntu2 [501kB]                    &lt;br /&gt;
   &#039;&#039;&#039;Get:10 http://us.archive.ubuntu.com/ubuntu/ lucid/universe virtualbox-ose-qt 3.1.6-dfsg-2ubuntu2 [4,678kB]                   &lt;br /&gt;
   &#039;&#039;&#039;Fetched 20.2MB in 2min 3s (164kB/s)                                                                                          &lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package dkms.&lt;br /&gt;
   &#039;&#039;&#039;(Reading database ... 148269 files and directories currently installed.)&lt;br /&gt;
   &#039;&#039;&#039;Unpacking dkms (from .../dkms_2.1.1.2-2fakesync1_all.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package libaudio2.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking libaudio2 (from .../libaudio2_1.9.2-3_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package libmng1.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking libmng1 (from .../libmng1_1.0.9-1ubuntu1_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package libqtcore4.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking libqtcore4 (from .../libqtcore4_4%3a4.6.2-0ubuntu5.1_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package libqt4-network.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking libqt4-network (from .../libqt4-network_4%3a4.6.2-0ubuntu5.1_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package libqtgui4.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking libqtgui4 (from .../libqtgui4_4%3a4.6.2-0ubuntu5.1_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package libqt4-opengl.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking libqt4-opengl (from .../libqt4-opengl_4%3a4.6.2-0ubuntu5.1_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package virtualbox-ose.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking virtualbox-ose (from .../virtualbox-ose_3.1.6-dfsg-2ubuntu2_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package virtualbox-ose-dkms.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking virtualbox-ose-dkms (from .../virtualbox-ose-dkms_3.1.6-dfsg-2ubuntu2_all.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package virtualbox-ose-qt.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking virtualbox-ose-qt (from .../virtualbox-ose-qt_3.1.6-dfsg-2ubuntu2_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for man-db ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for ureadahead ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for desktop-file-utils ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for python-gmenu ... &lt;br /&gt;
   &#039;&#039;&#039;Rebuilding /usr/share/applications/desktop.en_US.utf8.cache...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for python-support ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up dkms (2.1.1.2-2fakesync1) ...&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;Setting up libaudio2 (1.9.2-3) ...&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;Setting up libmng1 (1.0.9-1ubuntu1) ...&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;Setting up libqtcore4 (4:4.6.2-0ubuntu5.1) ...&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;Setting up libqt4-network (4:4.6.2-0ubuntu5.1) ...&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;Setting up libqtgui4 (4:4.6.2-0ubuntu5.1) ...&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;Setting up libqt4-opengl (4:4.6.2-0ubuntu5.1) ...&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;Setting up virtualbox-ose (3.1.6-dfsg-2ubuntu2) ...&lt;br /&gt;
   &#039;&#039;&#039; * Stopping VirtualBox kernel modules                                                                    [ OK ]&lt;br /&gt;
   &#039;&#039;&#039; * Starting VirtualBox kernel Modules                                                                                            &lt;br /&gt;
   &#039;&#039;&#039; * No suitable module for running kernel   found                                                                                                                        [fail]&lt;br /&gt;
invoke-rc.d: initscript virtualbox-ose, action &amp;quot;restart&amp;quot; failed.&lt;br /&gt;
&lt;br /&gt;
Setting up virtualbox-ose-dkms (3.1.6-dfsg-2ubuntu2) ...&lt;br /&gt;
Loading new virtualbox-ose-3.1.6 DKMS files...&lt;br /&gt;
First Installation: checking all kernels...&lt;br /&gt;
Building only for 2.6.32-25-generic&lt;br /&gt;
Building for architecture i686&lt;br /&gt;
Building initial module for 2.6.32-25-generic&lt;br /&gt;
Done.&lt;br /&gt;
&lt;br /&gt;
vboxdrv.ko:&lt;br /&gt;
Running module version sanity check.&lt;br /&gt;
 - Original module&lt;br /&gt;
   - No original module exists within this kernel&lt;br /&gt;
 - Installation&lt;br /&gt;
   - Installing to /lib/modules/2.6.32-25-generic/updates/dkms/&lt;br /&gt;
&lt;br /&gt;
vboxnetadp.ko:&lt;br /&gt;
Running module version sanity check.&lt;br /&gt;
 - Original module&lt;br /&gt;
   - No original module exists within this kernel&lt;br /&gt;
 - Installation&lt;br /&gt;
   - Installing to /lib/modules/2.6.32-25-generic/updates/dkms/&lt;br /&gt;
&lt;br /&gt;
vboxnetflt.ko:&lt;br /&gt;
Running module version sanity check.&lt;br /&gt;
 - Original module&lt;br /&gt;
   - No original module exists within this kernel&lt;br /&gt;
 - Installation&lt;br /&gt;
   - Installing to /lib/modules/2.6.32-25-generic/updates/dkms/&lt;br /&gt;
&lt;br /&gt;
depmod..............&lt;br /&gt;
&lt;br /&gt;
DKMS: install Completed.&lt;br /&gt;
 * Stopping VirtualBox kernel modules                                                                                  [ OK ] &lt;br /&gt;
 * Starting VirtualBox kernel modules                                                                                  [ OK ] &lt;br /&gt;
&lt;br /&gt;
Processing triggers for python-central ...&lt;br /&gt;
Setting up virtualbox-ose-qt (3.1.6-dfsg-2ubuntu2) ...&lt;br /&gt;
&lt;br /&gt;
Processing triggers for libc-bin ...&lt;br /&gt;
ldconfig deferred processing now taking place&lt;br /&gt;
root@ubuntu:/tmp/Ubuntu_VMware# VBoxManage convertfromraw /tmp/Ubuntu_VMware.bin /tmp/Ubuntu_VBox/Ubuntu_VBox.vdi&lt;br /&gt;
Sun VirtualBox Command Line Management Interface Version 3.1.6_OSE&lt;br /&gt;
(C) 2005-2010 Sun Microsystems, Inc.&lt;br /&gt;
All rights reserved.&lt;br /&gt;
&lt;br /&gt;
Converting from raw image file=&amp;quot;/tmp/Ubuntu_VMware.bin&amp;quot; to file=&amp;quot;/tmp/Ubuntu_VBox/Ubuntu_VBox.vdi&amp;quot;...&lt;br /&gt;
Creating dynamic image with size 17179869184 bytes (16384MB)...&lt;br /&gt;
root@ubuntu:/tmp/Ubuntu_VMware# &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Run VirtualBox, use the (File Menu) Virtual Media Manager and &#039;Add&#039; the newly cloned drive. This makes Virtual Box &#039;aware&#039; of the drive. Then go though the normal creation steps and choose this as the drive to use for the virtual machine.&lt;br /&gt;
&lt;br /&gt;
You should be able to boot up the newly created virtual machine.&lt;br /&gt;
&lt;br /&gt;
Enjoy your migration to Virtual Box!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Refrences:&lt;br /&gt;
&lt;br /&gt;
http://thedarkmaster.wordpress.com/2007/03/12/vmware-virtual-machine-to-virtual-box-conversion-how-to/&lt;br /&gt;
&lt;br /&gt;
https://wiki.ubuntu.com/UbuntuMagazine/HowTo/Switching_From_VMWare_To_VirtualBox:_.vmdk_To_.vdi_Using_Qemu_+_VdiTool&lt;br /&gt;
&lt;br /&gt;
http://www.cyberciti.biz/tips/converting-from-vmware-images-to-virtualbox-images.html#comments&lt;br /&gt;
&lt;br /&gt;
http://download.virtualbox.org/virtualbox/UserManual.pdf&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3554</id>
		<title>Converting VMWare .vmdk To VirtualBox .vdi Using Qemu+ and VBoxManage</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3554"/>
		<updated>2010-11-23T02:50:06Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If you want to switch to VirtualBox and have a Vmware Virtual Machine you want to use? You can convert a Vmware .vmdk file into a VirtualBox .vdi file that you can use on VirtualBox. &lt;br /&gt;
&lt;br /&gt;
First, download qemu, open a Console and execute: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo apt-get install qemu&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Next, open a console and go to your .vmdk virtual disc image folder and type this: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;qemu-img convert &amp;quot;harddrive-name&amp;quot;.vmdk /filelocation/&amp;quot;harddrive-name&amp;quot;.bin&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Change &amp;quot;harddrive-name&amp;quot; with the name of your .vmdk file and raw-file with the name of the new converted file you want to create. This takes a few minutes, After the conversion is completed. A raw hard disk image has been created. &lt;br /&gt;
&lt;br /&gt;
To convert a raw disk image to a VirtualBox Disk Image (.vdi) file use this command. &lt;br /&gt;
&lt;br /&gt;
The syntax is as follows:&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw /filelocation/&amp;quot;harddrive-name&amp;quot;.bin &amp;lt;outputfile&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo VBoxManage convertfromraw /home/tony/.VirtualBox/HardDisks/HardDisk1.bin /home/tony/.VirtualBox&#039;&#039;&#039; &lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD]&lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw stdin &amp;lt;outputfile&amp;gt; &amp;lt;bytes&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD] &lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
What the parameters mean:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;format&#039;&#039;&#039;  - Selects the disk image format to create. Default is .vdi. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;variant&#039;&#039;&#039;  - Allows to choose a file format variant for the output file. It is a comma-separated list of variant flags. Not all combinations are supported, and specifying inconsistent flags will result in an error message. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The second form forces VBoxManage to read the content for the disk image from standard input(useful for using that command in a pipe).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note: For compatibility with earlier versions of VirtualBox, the “convertdd” command is also supported and mapped internally to the “convertfromraw” command.&lt;br /&gt;
 &lt;br /&gt;
&#039;&#039;&#039;Here is a quick example of an actual conversion&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;tony@ubuntu:~$ sudo apt-get install qemu &lt;br /&gt;
   &#039;&#039;&#039;[sudo] password for tony:&lt;br /&gt;
   &#039;&#039;&#039;Reading package lists... Done&lt;br /&gt;
   &#039;&#039;&#039;Building dependency tree       &lt;br /&gt;
   &#039;&#039;&#039;Reading state information... Done&lt;br /&gt;
   &#039;&#039;&#039;The following packages were automatically installed and are no longer required:&lt;br /&gt;
   &#039;&#039;&#039;linux-headers-2.6.32-24 linux-headers-2.6.32-24-generic&lt;br /&gt;
   &#039;&#039;&#039;Use &#039;apt-get autoremove&#039; to remove them.&lt;br /&gt;
   &#039;&#039;&#039;The following extra packages will be installed:&lt;br /&gt;
   &#039;&#039;&#039;bridge-utils libaio1 qemu-common qemu-kvm seabios vgabios&lt;br /&gt;
   &#039;&#039;&#039;Suggested packages:&lt;br /&gt;
   &#039;&#039;&#039;mol-drivers-macosx openbios-sparc kvm-pxe ubuntu-vm-builder uml-utilities&lt;br /&gt;
   &#039;&#039;&#039;The following NEW packages will be installed:&lt;br /&gt;
   &#039;&#039;&#039;bridge-utils libaio1 qemu qemu-common qemu-kvm seabios vgabios&lt;br /&gt;
   &#039;&#039;&#039;0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded.&lt;br /&gt;
   &#039;&#039;&#039;Need to get 2,769kB of archives.&lt;br /&gt;
   &#039;&#039;&#039;After this operation, 8,192kB of additional disk space will be used.&lt;br /&gt;
   &#039;&#039;&#039;Do you want to continue [Y/n]? Y&lt;br /&gt;
   &#039;&#039;&#039;Get:1 http://us.archive.ubuntu.com/ubuntu/ lucid/main bridge-utils 1.4-5ubuntu2 [32.6kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:2 http://us.archive.ubuntu.com/ubuntu/ lucid/main libaio1 0.3.107-3ubuntu2 [9,512B]&lt;br /&gt;
   &#039;&#039;&#039;Get:3 http://us.archive.ubuntu.com/ubuntu/ lucid/main seabios 0.5.1-0ubuntu2 [48.2kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:4 http://us.archive.ubuntu.com/ubuntu/ lucid/main vgabios 0.6c-2ubuntu1 [78.5kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:5 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main qemu-common 0.12.3+noroms-0ubuntu9.2 [30.1kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:6 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main qemu-kvm 0.12.3+noroms-0ubuntu9.2 [2,556kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:7 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/universe qemu 0.12.3+noroms-0ubuntu9.2 [3.9kB]                     &lt;br /&gt;
   &#039;&#039;&#039;Fetched 2,769kB in 17s(156kB/s)                                                                                             &lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package bridge-utils.&lt;br /&gt;
   &#039;&#039;&#039;(Reading database ... 148121 files and directories currently installed.)&lt;br /&gt;
   &#039;&#039;&#039;Unpacking bridge-utils (from .../bridge-utils_1.4-5ubuntu2_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package libaio1.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking libaio1 (from .../libaio1_0.3.107-3ubuntu2_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package seabios.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking seabios (from .../seabios_0.5.1-0ubuntu2_all.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package vgabios.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking vgabios (from .../vgabios_0.6c-2ubuntu1_all.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package qemu-common.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking qemu-common (from .../qemu-common_0.12.3+noroms-0ubuntu9.2_all.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package qemu-kvm.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking qemu-kvm (from .../qemu-kvm_0.12.3+noroms-0ubuntu9.2_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package qemu.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking qemu (from .../qemu_0.12.3+noroms-0ubuntu9.2_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for ureadahead ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for man-db ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up bridge-utils (1.4-5ubuntu2) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up libaio1 (0.3.107-3ubuntu2) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up seabios (0.5.1-0ubuntu2) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up vgabios (0.6c-2ubuntu1) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up qemu-common (0.12.3+noroms-0ubuntu9.2) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up qemu-kvm (0.12.3+noroms-0ubuntu9.2) ...&lt;br /&gt;
   &#039;&#039;&#039;qemu-kvm start/running&lt;br /&gt;
   &#039;&#039;&#039;Setting up qemu (0.12.3+noroms-0ubuntu9.2) ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for libc-bin ...&lt;br /&gt;
   &#039;&#039;&#039;ldconfig deferred processing now taking place&lt;br /&gt;
   &#039;&#039;&#039;tony@ubuntu:~$ su&lt;br /&gt;
   &#039;&#039;&#039;Password: &lt;br /&gt;
   &#039;&#039;&#039;root@ubuntu:/home/tony# cd /tmp/Ubuntu_VMware&lt;br /&gt;
   &#039;&#039;&#039;root@ubuntu:/tmp/Ubuntu_VMware# qemu-img convert Ubuntu_VMware.vmdk /tmp/Ubuntu_VMware.bin&#039;&#039;&#039;&lt;br /&gt;
   &#039;&#039;&#039;root@ubuntu:/tmp/Ubuntu_VMware# VBoxManage convertfromraw /tmp/Ubuntu_VMware.bin /tmp/Ubuntu_VBox/Ubuntu_VBox.vdi&lt;br /&gt;
   &#039;&#039;&#039;The program &#039;VBoxManage&#039; is currently not installed.  You can install it by typing:&lt;br /&gt;
   &#039;&#039;&#039;apt-get install virtualbox-ose&lt;br /&gt;
   &#039;&#039;&#039;root@ubuntu:/tmp/Ubuntu_VMware# apt-get install virtualbox-ose&lt;br /&gt;
Reading package lists... Done&lt;br /&gt;
Building dependency tree       &lt;br /&gt;
Reading state information... Done&lt;br /&gt;
The following extra packages will be installed:&lt;br /&gt;
  dkms libaudio2 libmng1 libqt4-network libqt4-opengl libqtcore4 libqtgui4 virtualbox-ose-dkms virtualbox-ose-qt&lt;br /&gt;
Suggested packages:&lt;br /&gt;
  nas qt4-qtconfig virtualbox-guest-additions&lt;br /&gt;
The following NEW packages will be installed:&lt;br /&gt;
  dkms libaudio2 libmng1 libqt4-network libqt4-opengl libqtcore4 libqtgui4 virtualbox-ose virtualbox-ose-dkms&lt;br /&gt;
  virtualbox-ose-qt&lt;br /&gt;
0 upgraded, 10 newly installed, 0 to remove and 0 not upgraded.&lt;br /&gt;
Need to get 20.2MB of archives.&lt;br /&gt;
After this operation, 70.4MB of additional disk space will be used.&lt;br /&gt;
Do you want to continue [Y/n]? Y&lt;br /&gt;
Get:1 http://us.archive.ubuntu.com/ubuntu/ lucid/main dkms 2.1.1.2-2fakesync1 [70.1kB]&lt;br /&gt;
Get:2 http://us.archive.ubuntu.com/ubuntu/ lucid/main libaudio2 1.9.2-3 [81.0kB]&lt;br /&gt;
Get:3 http://us.archive.ubuntu.com/ubuntu/ lucid/main libmng1 1.0.9-1ubuntu1 [209kB]&lt;br /&gt;
Get:4 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main libqtcore4 4:4.6.2-0ubuntu5.1 [1,722kB]&lt;br /&gt;
Get:5 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main libqt4-network 4:4.6.2-0ubuntu5.1 [444kB]                      &lt;br /&gt;
Get:6 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main libqtgui4 4:4.6.2-0ubuntu5.1 [4,010kB]                         &lt;br /&gt;
Get:7 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main libqt4-opengl 4:4.6.2-0ubuntu5.1 [265kB]                       &lt;br /&gt;
Get:8 http://us.archive.ubuntu.com/ubuntu/ lucid/universe virtualbox-ose 3.1.6-dfsg-2ubuntu2 [8,265kB]                       &lt;br /&gt;
Get:9 http://us.archive.ubuntu.com/ubuntu/ lucid/universe virtualbox-ose-dkms 3.1.6-dfsg-2ubuntu2 [501kB]                    &lt;br /&gt;
Get:10 http://us.archive.ubuntu.com/ubuntu/ lucid/universe virtualbox-ose-qt 3.1.6-dfsg-2ubuntu2 [4,678kB]                   &lt;br /&gt;
Fetched 20.2MB in 2min 3s (164kB/s)                                                                                          &lt;br /&gt;
Selecting previously deselected package dkms.&lt;br /&gt;
(Reading database ... 148269 files and directories currently installed.)&lt;br /&gt;
Unpacking dkms (from .../dkms_2.1.1.2-2fakesync1_all.deb) ...&lt;br /&gt;
Selecting previously deselected package libaudio2.&lt;br /&gt;
Unpacking libaudio2 (from .../libaudio2_1.9.2-3_i386.deb) ...&lt;br /&gt;
Selecting previously deselected package libmng1.&lt;br /&gt;
Unpacking libmng1 (from .../libmng1_1.0.9-1ubuntu1_i386.deb) ...&lt;br /&gt;
Selecting previously deselected package libqtcore4.&lt;br /&gt;
Unpacking libqtcore4 (from .../libqtcore4_4%3a4.6.2-0ubuntu5.1_i386.deb) ...&lt;br /&gt;
Selecting previously deselected package libqt4-network.&lt;br /&gt;
Unpacking libqt4-network (from .../libqt4-network_4%3a4.6.2-0ubuntu5.1_i386.deb) ...&lt;br /&gt;
Selecting previously deselected package libqtgui4.&lt;br /&gt;
Unpacking libqtgui4 (from .../libqtgui4_4%3a4.6.2-0ubuntu5.1_i386.deb) ...&lt;br /&gt;
Selecting previously deselected package libqt4-opengl.&lt;br /&gt;
Unpacking libqt4-opengl (from .../libqt4-opengl_4%3a4.6.2-0ubuntu5.1_i386.deb) ...&lt;br /&gt;
Selecting previously deselected package virtualbox-ose.&lt;br /&gt;
Unpacking virtualbox-ose (from .../virtualbox-ose_3.1.6-dfsg-2ubuntu2_i386.deb) ...&lt;br /&gt;
Selecting previously deselected package virtualbox-ose-dkms.&lt;br /&gt;
Unpacking virtualbox-ose-dkms (from .../virtualbox-ose-dkms_3.1.6-dfsg-2ubuntu2_all.deb) ...&lt;br /&gt;
Selecting previously deselected package virtualbox-ose-qt.&lt;br /&gt;
Unpacking virtualbox-ose-qt (from .../virtualbox-ose-qt_3.1.6-dfsg-2ubuntu2_i386.deb) ...&lt;br /&gt;
Processing triggers for man-db ...&lt;br /&gt;
Processing triggers for ureadahead ...&lt;br /&gt;
Processing triggers for desktop-file-utils ...&lt;br /&gt;
Processing triggers for python-gmenu ...&lt;br /&gt;
Rebuilding /usr/share/applications/desktop.en_US.utf8.cache...&lt;br /&gt;
Processing triggers for python-support ...&lt;br /&gt;
Setting up dkms (2.1.1.2-2fakesync1) ...&lt;br /&gt;
&lt;br /&gt;
Setting up libaudio2 (1.9.2-3) ...&lt;br /&gt;
&lt;br /&gt;
Setting up libmng1 (1.0.9-1ubuntu1) ...&lt;br /&gt;
&lt;br /&gt;
Setting up libqtcore4 (4:4.6.2-0ubuntu5.1) ...&lt;br /&gt;
&lt;br /&gt;
Setting up libqt4-network (4:4.6.2-0ubuntu5.1) ...&lt;br /&gt;
&lt;br /&gt;
Setting up libqtgui4 (4:4.6.2-0ubuntu5.1) ...&lt;br /&gt;
&lt;br /&gt;
Setting up libqt4-opengl (4:4.6.2-0ubuntu5.1) ...&lt;br /&gt;
&lt;br /&gt;
Setting up virtualbox-ose (3.1.6-dfsg-2ubuntu2) ...&lt;br /&gt;
 * Stopping VirtualBox kernel modules                                                                                  [ OK ] &lt;br /&gt;
 * Starting VirtualBox kernel modules                                                                                          * No suitable module for running kernel found&lt;br /&gt;
                                                                                                                       [fail]&lt;br /&gt;
invoke-rc.d: initscript virtualbox-ose, action &amp;quot;restart&amp;quot; failed.&lt;br /&gt;
&lt;br /&gt;
Setting up virtualbox-ose-dkms (3.1.6-dfsg-2ubuntu2) ...&lt;br /&gt;
Loading new virtualbox-ose-3.1.6 DKMS files...&lt;br /&gt;
First Installation: checking all kernels...&lt;br /&gt;
Building only for 2.6.32-25-generic&lt;br /&gt;
Building for architecture i686&lt;br /&gt;
Building initial module for 2.6.32-25-generic&lt;br /&gt;
Done.&lt;br /&gt;
&lt;br /&gt;
vboxdrv.ko:&lt;br /&gt;
Running module version sanity check.&lt;br /&gt;
 - Original module&lt;br /&gt;
   - No original module exists within this kernel&lt;br /&gt;
 - Installation&lt;br /&gt;
   - Installing to /lib/modules/2.6.32-25-generic/updates/dkms/&lt;br /&gt;
&lt;br /&gt;
vboxnetadp.ko:&lt;br /&gt;
Running module version sanity check.&lt;br /&gt;
 - Original module&lt;br /&gt;
   - No original module exists within this kernel&lt;br /&gt;
 - Installation&lt;br /&gt;
   - Installing to /lib/modules/2.6.32-25-generic/updates/dkms/&lt;br /&gt;
&lt;br /&gt;
vboxnetflt.ko:&lt;br /&gt;
Running module version sanity check.&lt;br /&gt;
 - Original module&lt;br /&gt;
   - No original module exists within this kernel&lt;br /&gt;
 - Installation&lt;br /&gt;
   - Installing to /lib/modules/2.6.32-25-generic/updates/dkms/&lt;br /&gt;
&lt;br /&gt;
depmod..............&lt;br /&gt;
&lt;br /&gt;
DKMS: install Completed.&lt;br /&gt;
 * Stopping VirtualBox kernel modules                                                                                  [ OK ] &lt;br /&gt;
 * Starting VirtualBox kernel modules                                                                                  [ OK ] &lt;br /&gt;
&lt;br /&gt;
Processing triggers for python-central ...&lt;br /&gt;
Setting up virtualbox-ose-qt (3.1.6-dfsg-2ubuntu2) ...&lt;br /&gt;
&lt;br /&gt;
Processing triggers for libc-bin ...&lt;br /&gt;
ldconfig deferred processing now taking place&lt;br /&gt;
root@ubuntu:/tmp/Ubuntu_VMware# VBoxManage convertfromraw /tmp/Ubuntu_VMware.bin /tmp/Ubuntu_VBox/Ubuntu_VBox.vdi&lt;br /&gt;
Sun VirtualBox Command Line Management Interface Version 3.1.6_OSE&lt;br /&gt;
(C) 2005-2010 Sun Microsystems, Inc.&lt;br /&gt;
All rights reserved.&lt;br /&gt;
&lt;br /&gt;
Converting from raw image file=&amp;quot;/tmp/Ubuntu_VMware.bin&amp;quot; to file=&amp;quot;/tmp/Ubuntu_VBox/Ubuntu_VBox.vdi&amp;quot;...&lt;br /&gt;
Creating dynamic image with size 17179869184 bytes (16384MB)...&lt;br /&gt;
root@ubuntu:/tmp/Ubuntu_VMware# &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Run VirtualBox, use the (File Menu) Virtual Media Manager and &#039;Add&#039; the newly cloned drive. This makes Virtual Box &#039;aware&#039; of the drive. Then go though the normal creation steps and choose this as the drive to use for the virtual machine.&lt;br /&gt;
&lt;br /&gt;
You should be able to boot up the newly created virtual machine.&lt;br /&gt;
&lt;br /&gt;
Enjoy your migration to Virtual Box!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Refrences:&lt;br /&gt;
&lt;br /&gt;
http://thedarkmaster.wordpress.com/2007/03/12/vmware-virtual-machine-to-virtual-box-conversion-how-to/&lt;br /&gt;
&lt;br /&gt;
https://wiki.ubuntu.com/UbuntuMagazine/HowTo/Switching_From_VMWare_To_VirtualBox:_.vmdk_To_.vdi_Using_Qemu_+_VdiTool&lt;br /&gt;
&lt;br /&gt;
http://www.cyberciti.biz/tips/converting-from-vmware-images-to-virtualbox-images.html#comments&lt;br /&gt;
&lt;br /&gt;
http://download.virtualbox.org/virtualbox/UserManual.pdf&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3553</id>
		<title>Converting VMWare .vmdk To VirtualBox .vdi Using Qemu+ and VBoxManage</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3553"/>
		<updated>2010-11-22T21:44:38Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If you want to switch to VirtualBox and have a Vmware Virtual Machine you want to use? You can convert a Vmware .vmdk file into a VirtualBox .vdi file that you can use on VirtualBox. &lt;br /&gt;
&lt;br /&gt;
First, download qemu, open a Console and execute: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo apt-get install qemu&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Next, open a console and go to your .vmdk virtual disc image folder and type this: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;qemu-img convert &amp;quot;harddrive-name&amp;quot;.vmdk /filelocation/&amp;quot;harddrive-name&amp;quot;.bin&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Change &amp;quot;harddrive-name&amp;quot; with the name of your .vmdk file and raw-file with the name of the new converted file you want to create. This takes a few minutes, After the conversion is completed. A raw hard disk image has been created. &lt;br /&gt;
&lt;br /&gt;
To convert a raw disk image to a VirtualBox Disk Image (.vdi) file use this command. &lt;br /&gt;
&lt;br /&gt;
The syntax is as follows:&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw /filelocation/&amp;quot;harddrive-name&amp;quot;.bin &amp;lt;outputfile&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo VBoxManage convertfromraw /home/tony/.VirtualBox/HardDisks/HardDisk1.bin /home/tony/.VirtualBox&#039;&#039;&#039; &lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD]&lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw stdin &amp;lt;outputfile&amp;gt; &amp;lt;bytes&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD] &lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
What the parameters mean:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;format&#039;&#039;&#039;  - Selects the disk image format to create. Default is .vdi. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;variant&#039;&#039;&#039;  - Allows to choose a file format variant for the output file. It is a comma-separated list of variant flags. Not all combinations are supported, and specifying inconsistent flags will result in an error message. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The second form forces VBoxManage to read the content for the disk image from standard input(useful for using that command in a pipe).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note: For compatibility with earlier versions of VirtualBox, the “convertdd” command is also supported and mapped internally to the “convertfromraw” command.&lt;br /&gt;
 &lt;br /&gt;
&#039;&#039;&#039;Here is a quick example of an actual conversion&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;tony@ubuntu:~$ sudo apt-get install qemu &lt;br /&gt;
   &#039;&#039;&#039;[sudo] password for tony:&lt;br /&gt;
   &#039;&#039;&#039;Reading package lists... Done&lt;br /&gt;
   &#039;&#039;&#039;Building dependency tree       &lt;br /&gt;
   &#039;&#039;&#039;Reading state information... Done&lt;br /&gt;
   &#039;&#039;&#039;The following packages were automatically installed and are no longer required:&lt;br /&gt;
   &#039;&#039;&#039;linux-headers-2.6.32-24 linux-headers-2.6.32-24-generic&lt;br /&gt;
   &#039;&#039;&#039;Use &#039;apt-get autoremove&#039; to remove them.&lt;br /&gt;
   &#039;&#039;&#039;The following extra packages will be installed:&lt;br /&gt;
   &#039;&#039;&#039;bridge-utils libaio1 qemu-common qemu-kvm seabios vgabios&lt;br /&gt;
   &#039;&#039;&#039;Suggested packages:&lt;br /&gt;
   &#039;&#039;&#039;mol-drivers-macosx openbios-sparc kvm-pxe ubuntu-vm-builder uml-utilities&lt;br /&gt;
   &#039;&#039;&#039;The following NEW packages will be installed:&lt;br /&gt;
   &#039;&#039;&#039;bridge-utils libaio1 qemu qemu-common qemu-kvm seabios vgabios&lt;br /&gt;
   &#039;&#039;&#039;0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded.&lt;br /&gt;
   &#039;&#039;&#039;Need to get 2,769kB of archives.&lt;br /&gt;
   &#039;&#039;&#039;After this operation, 8,192kB of additional disk space will be used.&lt;br /&gt;
   &#039;&#039;&#039;Do you want to continue [Y/n]? Y&lt;br /&gt;
   &#039;&#039;&#039;Get:1 http://us.archive.ubuntu.com/ubuntu/ lucid/main bridge-utils 1.4-5ubuntu2 [32.6kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:2 http://us.archive.ubuntu.com/ubuntu/ lucid/main libaio1 0.3.107-3ubuntu2 [9,512B]&lt;br /&gt;
   &#039;&#039;&#039;Get:3 http://us.archive.ubuntu.com/ubuntu/ lucid/main seabios 0.5.1-0ubuntu2 [48.2kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:4 http://us.archive.ubuntu.com/ubuntu/ lucid/main vgabios 0.6c-2ubuntu1 [78.5kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:5 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main qemu-common 0.12.3+noroms-0ubuntu9.2 [30.1kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:6 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main qemu-kvm 0.12.3+noroms-0ubuntu9.2 [2,556kB]&lt;br /&gt;
   &#039;&#039;&#039;Get:7 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/universe qemu 0.12.3+noroms-0ubuntu9.2 [3.9kB]                     &lt;br /&gt;
   &#039;&#039;&#039;Fetched 2,769kB in 17s(156kB/s)                                                                                             &lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package bridge-utils.&lt;br /&gt;
   &#039;&#039;&#039;(Reading database ... 148121 files and directories currently installed.)&lt;br /&gt;
   &#039;&#039;&#039;Unpacking bridge-utils (from .../bridge-utils_1.4-5ubuntu2_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package libaio1.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking libaio1 (from .../libaio1_0.3.107-3ubuntu2_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package seabios.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking seabios (from .../seabios_0.5.1-0ubuntu2_all.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package vgabios.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking vgabios (from .../vgabios_0.6c-2ubuntu1_all.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package qemu-common.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking qemu-common (from .../qemu-common_0.12.3+noroms-0ubuntu9.2_all.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package qemu-kvm.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking qemu-kvm (from .../qemu-kvm_0.12.3+noroms-0ubuntu9.2_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Selecting previously deselected package qemu.&lt;br /&gt;
   &#039;&#039;&#039;Unpacking qemu (from .../qemu_0.12.3+noroms-0ubuntu9.2_i386.deb) ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for ureadahead ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for man-db ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up bridge-utils (1.4-5ubuntu2) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up libaio1 (0.3.107-3ubuntu2) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up seabios (0.5.1-0ubuntu2) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up vgabios (0.6c-2ubuntu1) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up qemu-common (0.12.3+noroms-0ubuntu9.2) ...&lt;br /&gt;
   &#039;&#039;&#039;Setting up qemu-kvm (0.12.3+noroms-0ubuntu9.2) ...&lt;br /&gt;
   &#039;&#039;&#039;qemu-kvm start/running&lt;br /&gt;
   &#039;&#039;&#039;Setting up qemu (0.12.3+noroms-0ubuntu9.2) ...&lt;br /&gt;
   &#039;&#039;&#039;Processing triggers for libc-bin ...&lt;br /&gt;
   &#039;&#039;&#039;ldconfig deferred processing now taking place&lt;br /&gt;
   &#039;&#039;&#039;tony@ubuntu:~$ su&lt;br /&gt;
   &#039;&#039;&#039;Password: &lt;br /&gt;
   &#039;&#039;&#039;root@ubuntu:/home/tony# cd /tmp/Ubuntu_VMware&lt;br /&gt;
   &#039;&#039;&#039;root@ubuntu:/tmp/Ubuntu_VMware# qemu-img convert Ubuntu_VMware.vmdk /tmp/Ubuntu_VMware.bin&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Run VirtualBox, use the (File Menu) Virtual Media Manager and &#039;Add&#039; the newly cloned drive. This makes Virtual Box &#039;aware&#039; of the drive. Then go though the normal creation steps and choose this as the drive to use for the virtual machine.&lt;br /&gt;
&lt;br /&gt;
You should be able to boot up the newly created virtual machine.&lt;br /&gt;
&lt;br /&gt;
Enjoy your migration to Virtual Box!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Refrences:&lt;br /&gt;
&lt;br /&gt;
http://thedarkmaster.wordpress.com/2007/03/12/vmware-virtual-machine-to-virtual-box-conversion-how-to/&lt;br /&gt;
&lt;br /&gt;
https://wiki.ubuntu.com/UbuntuMagazine/HowTo/Switching_From_VMWare_To_VirtualBox:_.vmdk_To_.vdi_Using_Qemu_+_VdiTool&lt;br /&gt;
&lt;br /&gt;
http://www.cyberciti.biz/tips/converting-from-vmware-images-to-virtualbox-images.html#comments&lt;br /&gt;
&lt;br /&gt;
http://download.virtualbox.org/virtualbox/UserManual.pdf&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3552</id>
		<title>Converting VMWare .vmdk To VirtualBox .vdi Using Qemu+ and VBoxManage</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3552"/>
		<updated>2010-11-22T21:36:19Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If you want to switch to VirtualBox and have a Vmware Virtual Machine you want to use? You can convert a Vmware .vmdk file into a VirtualBox .vdi file that you can use on VirtualBox. &lt;br /&gt;
&lt;br /&gt;
First, download qemu, open a Console and execute: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo apt-get install qemu&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Next, open a console and go to your .vmdk virtual disc image folder and type this: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;qemu-img convert &amp;quot;harddrive-name&amp;quot;.vmdk /filelocation/&amp;quot;harddrive-name&amp;quot;.bin&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Change &amp;quot;harddrive-name&amp;quot; with the name of your .vmdk file and raw-file with the name of the new converted file you want to create. This takes a few minutes, After the conversion is completed. A raw hard disk image has been created. &lt;br /&gt;
&lt;br /&gt;
To convert a raw disk image to a VirtualBox Disk Image (.vdi) file use this command. &lt;br /&gt;
&lt;br /&gt;
The syntax is as follows:&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw /filelocation/&amp;quot;harddrive-name&amp;quot;.bin &amp;lt;outputfile&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo VBoxManage convertfromraw /home/tony/.VirtualBox/HardDisks/HardDisk1.bin /home/tony/.VirtualBox&#039;&#039;&#039; &lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD]&lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw stdin &amp;lt;outputfile&amp;gt; &amp;lt;bytes&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD] &lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
What the parameters mean:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;format&#039;&#039;&#039;  - Selects the disk image format to create. Default is .vdi. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;variant&#039;&#039;&#039;  - Allows to choose a file format variant for the output file. It is a comma-separated list of variant flags. Not all combinations are supported, and specifying inconsistent flags will result in an error message. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The second form forces VBoxManage to read the content for the disk image from standard input(useful for using that command in a pipe).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note: For compatibility with earlier versions of VirtualBox, the “convertdd” command is also supported and mapped internally to the “convertfromraw” command.&lt;br /&gt;
 &lt;br /&gt;
&#039;&#039;&#039;Here is a quick example of an actual conversion&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;tony@ubuntu:~$ sudo apt-get install qemu &lt;br /&gt;
   &#039;&#039;&#039;[sudo] password for tony:&lt;br /&gt;
 &lt;br /&gt;
Reading package lists... Done&lt;br /&gt;
Building dependency tree       &lt;br /&gt;
Reading state information... Done&lt;br /&gt;
The following packages were automatically installed and are no longer required:&lt;br /&gt;
  linux-headers-2.6.32-24 linux-headers-2.6.32-24-generic&lt;br /&gt;
Use &#039;apt-get autoremove&#039; to remove them.&lt;br /&gt;
The following extra packages will be installed:&lt;br /&gt;
  bridge-utils libaio1 qemu-common qemu-kvm seabios vgabios&lt;br /&gt;
Suggested packages:&lt;br /&gt;
  mol-drivers-macosx openbios-sparc kvm-pxe ubuntu-vm-builder uml-utilities&lt;br /&gt;
The following NEW packages will be installed:&lt;br /&gt;
  bridge-utils libaio1 qemu qemu-common qemu-kvm seabios vgabios&lt;br /&gt;
0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded.&lt;br /&gt;
Need to get 2,769kB of archives.&lt;br /&gt;
After this operation, 8,192kB of additional disk space will be used.&lt;br /&gt;
Do you want to continue [Y/n]? Y&lt;br /&gt;
Get:1 http://us.archive.ubuntu.com/ubuntu/ lucid/main bridge-utils 1.4-5ubuntu2 [32.6kB]&lt;br /&gt;
Get:2 http://us.archive.ubuntu.com/ubuntu/ lucid/main libaio1 0.3.107-3ubuntu2 [9,512B]&lt;br /&gt;
Get:3 http://us.archive.ubuntu.com/ubuntu/ lucid/main seabios 0.5.1-0ubuntu2 [48.2kB]&lt;br /&gt;
Get:4 http://us.archive.ubuntu.com/ubuntu/ lucid/main vgabios 0.6c-2ubuntu1 [78.5kB]&lt;br /&gt;
Get:5 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main qemu-common 0.12.3+noroms-0ubuntu9.2 [30.1kB]&lt;br /&gt;
Get:6 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main qemu-kvm 0.12.3+noroms-0ubuntu9.2 [2,556kB]&lt;br /&gt;
Get:7 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/universe qemu 0.12.3+noroms-0ubuntu9.2 [13.9kB]                     &lt;br /&gt;
Fetched 2,769kB in 17s (156kB/s)                                                                                             &lt;br /&gt;
Selecting previously deselected package bridge-utils.&lt;br /&gt;
(Reading database ... 148121 files and directories currently installed.)&lt;br /&gt;
Unpacking bridge-utils (from .../bridge-utils_1.4-5ubuntu2_i386.deb) ...&lt;br /&gt;
Selecting previously deselected package libaio1.&lt;br /&gt;
Unpacking libaio1 (from .../libaio1_0.3.107-3ubuntu2_i386.deb) ...&lt;br /&gt;
Selecting previously deselected package seabios.&lt;br /&gt;
Unpacking seabios (from .../seabios_0.5.1-0ubuntu2_all.deb) ...&lt;br /&gt;
Selecting previously deselected package vgabios.&lt;br /&gt;
Unpacking vgabios (from .../vgabios_0.6c-2ubuntu1_all.deb) ...&lt;br /&gt;
Selecting previously deselected package qemu-common.&lt;br /&gt;
Unpacking qemu-common (from .../qemu-common_0.12.3+noroms-0ubuntu9.2_all.deb) ...&lt;br /&gt;
Selecting previously deselected package qemu-kvm.&lt;br /&gt;
Unpacking qemu-kvm (from .../qemu-kvm_0.12.3+noroms-0ubuntu9.2_i386.deb) ...&lt;br /&gt;
Selecting previously deselected package qemu.&lt;br /&gt;
Unpacking qemu (from .../qemu_0.12.3+noroms-0ubuntu9.2_i386.deb) ...&lt;br /&gt;
Processing triggers for ureadahead ...&lt;br /&gt;
Processing triggers for man-db ...&lt;br /&gt;
Setting up bridge-utils (1.4-5ubuntu2) ...&lt;br /&gt;
&lt;br /&gt;
Setting up libaio1 (0.3.107-3ubuntu2) ...&lt;br /&gt;
&lt;br /&gt;
Setting up seabios (0.5.1-0ubuntu2) ...&lt;br /&gt;
Setting up vgabios (0.6c-2ubuntu1) ...&lt;br /&gt;
Setting up qemu-common (0.12.3+noroms-0ubuntu9.2) ...&lt;br /&gt;
Setting up qemu-kvm (0.12.3+noroms-0ubuntu9.2) ...&lt;br /&gt;
qemu-kvm start/running&lt;br /&gt;
&lt;br /&gt;
Setting up qemu (0.12.3+noroms-0ubuntu9.2) ...&lt;br /&gt;
Processing triggers for libc-bin ...&lt;br /&gt;
ldconfig deferred processing now taking place&lt;br /&gt;
tony@ubuntu:~$ su&lt;br /&gt;
Password: &lt;br /&gt;
root@ubuntu:/home/tony# cd /tmp/Ubuntu VMware&lt;br /&gt;
bash: cd: /tmp/Ubuntu: No such file or directory&lt;br /&gt;
root@ubuntu:/home/tony# cd /tmp/Ubuntu VMware&lt;br /&gt;
bash: cd: /tmp/Ubuntu: No such file or directory&lt;br /&gt;
root@ubuntu:/home/tony# cd /tmp/Ubuntu_VMware&lt;br /&gt;
root@ubuntu:/tmp/Ubuntu_VMware# qemu-img convert Ubuntu_VMware.vmdk /tmp/Ubuntu_VMware.bin&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Run VirtualBox, use the (File Menu) Virtual Media Manager and &#039;Add&#039; the newly cloned drive. This makes Virtual Box &#039;aware&#039; of the drive. Then go though the normal creation steps and choose this as the drive to use for the virtual machine.&lt;br /&gt;
&lt;br /&gt;
You should be able to boot up the newly created virtual machine.&lt;br /&gt;
&lt;br /&gt;
Enjoy your migration to Virtual Box!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Refrences:&lt;br /&gt;
&lt;br /&gt;
http://thedarkmaster.wordpress.com/2007/03/12/vmware-virtual-machine-to-virtual-box-conversion-how-to/&lt;br /&gt;
&lt;br /&gt;
https://wiki.ubuntu.com/UbuntuMagazine/HowTo/Switching_From_VMWare_To_VirtualBox:_.vmdk_To_.vdi_Using_Qemu_+_VdiTool&lt;br /&gt;
&lt;br /&gt;
http://www.cyberciti.biz/tips/converting-from-vmware-images-to-virtualbox-images.html#comments&lt;br /&gt;
&lt;br /&gt;
http://download.virtualbox.org/virtualbox/UserManual.pdf&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3551</id>
		<title>Converting VMWare .vmdk To VirtualBox .vdi Using Qemu+ and VBoxManage</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3551"/>
		<updated>2010-11-22T21:33:25Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If you want to switch to VirtualBox and have a Vmware Virtual Machine you want to use? You can convert a Vmware .vmdk file into a VirtualBox .vdi file that you can use on VirtualBox. &lt;br /&gt;
&lt;br /&gt;
First, download qemu, open a Console and execute: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo apt-get install qemu&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Next, open a console and go to your .vmdk virtual disc image folder and type this: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;qemu-img convert &amp;quot;harddrive-name&amp;quot;.vmdk /filelocation/&amp;quot;harddrive-name&amp;quot;.bin&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Change &amp;quot;harddrive-name&amp;quot; with the name of your .vmdk file and raw-file with the name of the new converted file you want to create. This takes a few minutes, After the conversion is completed. A raw hard disk image has been created. &lt;br /&gt;
&lt;br /&gt;
To convert a raw disk image to a VirtualBox Disk Image (.vdi) file use this command. &lt;br /&gt;
&lt;br /&gt;
The syntax is as follows:&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw /filelocation/&amp;quot;harddrive-name&amp;quot;.bin &amp;lt;outputfile&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo VBoxManage convertfromraw /home/tony/.VirtualBox/HardDisks/HardDisk1.bin /home/tony/.VirtualBox&#039;&#039;&#039; &lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD]&lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw stdin &amp;lt;outputfile&amp;gt; &amp;lt;bytes&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD] &lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
What the parameters mean:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;format&#039;&#039;&#039;  - Selects the disk image format to create. Default is .vdi. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;variant&#039;&#039;&#039;  - Allows to choose a file format variant for the output file. It is a comma-separated list of variant flags. Not all combinations are supported, and specifying inconsistent flags will result in an error message. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The second form forces VBoxManage to read the content for the disk image from standard input(useful for using that command in a pipe).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note: For compatibility with earlier versions of VirtualBox, the “convertdd” command is also supported and mapped internally to the “convertfromraw” command.&lt;br /&gt;
 &lt;br /&gt;
&#039;&#039;&#039;Here is a quick example of an actual conversion&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;tony@ubuntu:~$ sudo apt-get install qemu &lt;br /&gt;
[sudo] password for tony: &lt;br /&gt;
Reading package lists... Done&lt;br /&gt;
Building dependency tree       &lt;br /&gt;
Reading state information... Done&lt;br /&gt;
The following packages were automatically installed and are no longer required:&lt;br /&gt;
  linux-headers-2.6.32-24 linux-headers-2.6.32-24-generic&lt;br /&gt;
Use &#039;apt-get autoremove&#039; to remove them.&lt;br /&gt;
The following extra packages will be installed:&lt;br /&gt;
  bridge-utils libaio1 qemu-common qemu-kvm seabios vgabios&lt;br /&gt;
Suggested packages:&lt;br /&gt;
  mol-drivers-macosx openbios-sparc kvm-pxe ubuntu-vm-builder uml-utilities&lt;br /&gt;
The following NEW packages will be installed:&lt;br /&gt;
  bridge-utils libaio1 qemu qemu-common qemu-kvm seabios vgabios&lt;br /&gt;
0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded.&lt;br /&gt;
Need to get 2,769kB of archives.&lt;br /&gt;
After this operation, 8,192kB of additional disk space will be used.&lt;br /&gt;
Do you want to continue [Y/n]? Y&lt;br /&gt;
Get:1 http://us.archive.ubuntu.com/ubuntu/ lucid/main bridge-utils 1.4-5ubuntu2 [32.6kB]&lt;br /&gt;
Get:2 http://us.archive.ubuntu.com/ubuntu/ lucid/main libaio1 0.3.107-3ubuntu2 [9,512B]&lt;br /&gt;
Get:3 http://us.archive.ubuntu.com/ubuntu/ lucid/main seabios 0.5.1-0ubuntu2 [48.2kB]&lt;br /&gt;
Get:4 http://us.archive.ubuntu.com/ubuntu/ lucid/main vgabios 0.6c-2ubuntu1 [78.5kB]&lt;br /&gt;
Get:5 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main qemu-common 0.12.3+noroms-0ubuntu9.2 [30.1kB]&lt;br /&gt;
Get:6 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main qemu-kvm 0.12.3+noroms-0ubuntu9.2 [2,556kB]&lt;br /&gt;
Get:7 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/universe qemu 0.12.3+noroms-0ubuntu9.2 [13.9kB]                     &lt;br /&gt;
Fetched 2,769kB in 17s (156kB/s)                                                                                             &lt;br /&gt;
Selecting previously deselected package bridge-utils.&lt;br /&gt;
(Reading database ... 148121 files and directories currently installed.)&lt;br /&gt;
Unpacking bridge-utils (from .../bridge-utils_1.4-5ubuntu2_i386.deb) ...&lt;br /&gt;
Selecting previously deselected package libaio1.&lt;br /&gt;
Unpacking libaio1 (from .../libaio1_0.3.107-3ubuntu2_i386.deb) ...&lt;br /&gt;
Selecting previously deselected package seabios.&lt;br /&gt;
Unpacking seabios (from .../seabios_0.5.1-0ubuntu2_all.deb) ...&lt;br /&gt;
Selecting previously deselected package vgabios.&lt;br /&gt;
Unpacking vgabios (from .../vgabios_0.6c-2ubuntu1_all.deb) ...&lt;br /&gt;
Selecting previously deselected package qemu-common.&lt;br /&gt;
Unpacking qemu-common (from .../qemu-common_0.12.3+noroms-0ubuntu9.2_all.deb) ...&lt;br /&gt;
Selecting previously deselected package qemu-kvm.&lt;br /&gt;
Unpacking qemu-kvm (from .../qemu-kvm_0.12.3+noroms-0ubuntu9.2_i386.deb) ...&lt;br /&gt;
Selecting previously deselected package qemu.&lt;br /&gt;
Unpacking qemu (from .../qemu_0.12.3+noroms-0ubuntu9.2_i386.deb) ...&lt;br /&gt;
Processing triggers for ureadahead ...&lt;br /&gt;
Processing triggers for man-db ...&lt;br /&gt;
Setting up bridge-utils (1.4-5ubuntu2) ...&lt;br /&gt;
&lt;br /&gt;
Setting up libaio1 (0.3.107-3ubuntu2) ...&lt;br /&gt;
&lt;br /&gt;
Setting up seabios (0.5.1-0ubuntu2) ...&lt;br /&gt;
Setting up vgabios (0.6c-2ubuntu1) ...&lt;br /&gt;
Setting up qemu-common (0.12.3+noroms-0ubuntu9.2) ...&lt;br /&gt;
Setting up qemu-kvm (0.12.3+noroms-0ubuntu9.2) ...&lt;br /&gt;
qemu-kvm start/running&lt;br /&gt;
&lt;br /&gt;
Setting up qemu (0.12.3+noroms-0ubuntu9.2) ...&lt;br /&gt;
Processing triggers for libc-bin ...&lt;br /&gt;
ldconfig deferred processing now taking place&lt;br /&gt;
tony@ubuntu:~$ su&lt;br /&gt;
Password: &lt;br /&gt;
root@ubuntu:/home/tony# cd /tmp/Ubuntu VMware&lt;br /&gt;
bash: cd: /tmp/Ubuntu: No such file or directory&lt;br /&gt;
root@ubuntu:/home/tony# cd /tmp/Ubuntu VMware&lt;br /&gt;
bash: cd: /tmp/Ubuntu: No such file or directory&lt;br /&gt;
root@ubuntu:/home/tony# cd /tmp/Ubuntu_VMware&lt;br /&gt;
root@ubuntu:/tmp/Ubuntu_VMware# qemu-img convert Ubuntu_VMware.vmdk /tmp/Ubuntu_VMware.bin&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Run VirtualBox, use the (File Menu) Virtual Media Manager and &#039;Add&#039; the newly cloned drive. This makes Virtual Box &#039;aware&#039; of the drive. Then go though the normal creation steps and choose this as the drive to use for the virtual machine.&lt;br /&gt;
&lt;br /&gt;
You should be able to boot up the newly created virtual machine.&lt;br /&gt;
&lt;br /&gt;
Enjoy your migration to Virtual Box!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Refrences:&lt;br /&gt;
&lt;br /&gt;
http://thedarkmaster.wordpress.com/2007/03/12/vmware-virtual-machine-to-virtual-box-conversion-how-to/&lt;br /&gt;
&lt;br /&gt;
https://wiki.ubuntu.com/UbuntuMagazine/HowTo/Switching_From_VMWare_To_VirtualBox:_.vmdk_To_.vdi_Using_Qemu_+_VdiTool&lt;br /&gt;
&lt;br /&gt;
http://www.cyberciti.biz/tips/converting-from-vmware-images-to-virtualbox-images.html#comments&lt;br /&gt;
&lt;br /&gt;
http://download.virtualbox.org/virtualbox/UserManual.pdf&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3550</id>
		<title>Converting VMWare .vmdk To VirtualBox .vdi Using Qemu+ and VBoxManage</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3550"/>
		<updated>2010-11-22T21:26:48Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If you want to switch to VirtualBox and have a Vmware Virtual Machine you want to use? You can convert a Vmware .vmdk file into a VirtualBox .vdi file that you can use on VirtualBox. &lt;br /&gt;
&lt;br /&gt;
First, download qemu, open a Console and execute: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo apt-get install qemu&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Next, open a console and go to your .vmdk virtual disc image folder and type this: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;qemu-img convert &amp;quot;harddrive-name&amp;quot;.vmdk /filelocation/&amp;quot;harddrive-name&amp;quot;.bin&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Change &amp;quot;harddrive-name&amp;quot; with the name of your .vmdk file and raw-file with the name of the new converted file you want to create. This takes a few minutes, After the conversion is completed. A raw hard disk image has been created. &lt;br /&gt;
&lt;br /&gt;
To convert a raw disk image to a VirtualBox Disk Image (.vdi) file use this command. &lt;br /&gt;
&lt;br /&gt;
The syntax is as follows:&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw /filelocation/&amp;quot;harddrive-name&amp;quot;.bin &amp;lt;outputfile&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo VBoxManage convertfromraw /home/tony/.VirtualBox/HardDisks/HardDisk1.bin /home/tony/.VirtualBox&#039;&#039;&#039; &lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD]&lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw stdin &amp;lt;outputfile&amp;gt; &amp;lt;bytes&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD] &lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
What the parameters mean:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;format&#039;&#039;&#039;  - Selects the disk image format to create. Default is .vdi. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;variant&#039;&#039;&#039;  - Allows to choose a file format variant for the output file. It is a comma-separated list of variant flags. Not all combinations are supported, and specifying inconsistent flags will result in an error message. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The second form forces VBoxManage to read the content for the disk image from standard input(useful for using that command in a pipe).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note: For compatibility with earlier versions of VirtualBox, the “convertdd” command is also supported and mapped internally to the “convertfromraw” command.&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
Run VirtualBox, use the (File Menu) Virtual Media Manager and &#039;Add&#039; the newly cloned drive. This makes Virtual Box &#039;aware&#039; of the drive. Then go though the normal creation steps and choose this as the drive to use for the virtual machine.&lt;br /&gt;
&lt;br /&gt;
You should be able to boot up the newly created virtual machine.&lt;br /&gt;
&lt;br /&gt;
Enjoy your migration to Virtual Box!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Refrences:&lt;br /&gt;
&lt;br /&gt;
http://thedarkmaster.wordpress.com/2007/03/12/vmware-virtual-machine-to-virtual-box-conversion-how-to/&lt;br /&gt;
&lt;br /&gt;
https://wiki.ubuntu.com/UbuntuMagazine/HowTo/Switching_From_VMWare_To_VirtualBox:_.vmdk_To_.vdi_Using_Qemu_+_VdiTool&lt;br /&gt;
&lt;br /&gt;
http://www.cyberciti.biz/tips/converting-from-vmware-images-to-virtualbox-images.html#comments&lt;br /&gt;
&lt;br /&gt;
http://download.virtualbox.org/virtualbox/UserManual.pdf&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3549</id>
		<title>Converting VMWare .vmdk To VirtualBox .vdi Using Qemu+ and VBoxManage</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3549"/>
		<updated>2010-11-22T21:22:31Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If you want to switch to VirtualBox and have a Vmware Virtual Machine you want to use? You can convert a Vmware .vmdk file into a VirtualBox .vdi file that you can use on VirtualBox. &lt;br /&gt;
&lt;br /&gt;
First, download qemu, open a Console and execute: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo apt-get install qemu&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Next, open a console and go to your .vmdk virtual disc image folder and type this: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;qemu-img convert Ubuntu_VMware.vmdk /filelocation/Ubuntu_VMware.bin&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Change &amp;quot;harddrive-name&amp;quot; with the name of your .vmdk file and raw-file with the name of the new converted file you want to create. This takes a few minutes, After the conversion is completed. A raw hard disk image has been created. &lt;br /&gt;
&lt;br /&gt;
To convert a raw disk image to a VirtualBox Disk Image (.vdi) file use this command. &lt;br /&gt;
&lt;br /&gt;
The syntax is as follows:&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw /filelocation/&amp;quot;harddrive-name&amp;quot;.bin &amp;lt;outputfile&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo VBoxManage convertfromraw /home/tony/.VirtualBox/HardDisks/HardDisk1.bin /home/tony/.VirtualBox&#039;&#039;&#039; &lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD]&lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw stdin &amp;lt;outputfile&amp;gt; &amp;lt;bytes&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD] &lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
What the parameters mean:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;format&#039;&#039;&#039;  - Selects the disk image format to create. Default is .vdi. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;variant&#039;&#039;&#039;  - Allows to choose a file format variant for the output file. It is a comma-separated list of variant flags. Not all combinations are supported, and specifying inconsistent flags will result in an error message. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The second form forces VBoxManage to read the content for the disk image from standard input(useful for using that command in a pipe).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note: For compatibility with earlier versions of VirtualBox, the “convertdd” command is also supported and mapped internally to the “convertfromraw” command.&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
Run VirtualBox, use the (File Menu) Virtual Media Manager and &#039;Add&#039; the newly cloned drive. This makes Virtual Box &#039;aware&#039; of the drive. Then go though the normal creation steps and choose this as the drive to use for the virtual machine.&lt;br /&gt;
&lt;br /&gt;
You should be able to boot up the newly created virtual machine.&lt;br /&gt;
&lt;br /&gt;
Enjoy your migration to Virtual Box!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Refrences:&lt;br /&gt;
&lt;br /&gt;
http://thedarkmaster.wordpress.com/2007/03/12/vmware-virtual-machine-to-virtual-box-conversion-how-to/&lt;br /&gt;
&lt;br /&gt;
https://wiki.ubuntu.com/UbuntuMagazine/HowTo/Switching_From_VMWare_To_VirtualBox:_.vmdk_To_.vdi_Using_Qemu_+_VdiTool&lt;br /&gt;
&lt;br /&gt;
http://www.cyberciti.biz/tips/converting-from-vmware-images-to-virtualbox-images.html#comments&lt;br /&gt;
&lt;br /&gt;
http://download.virtualbox.org/virtualbox/UserManual.pdf&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3535</id>
		<title>Converting VMWare .vmdk To VirtualBox .vdi Using Qemu+ and VBoxManage</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3535"/>
		<updated>2010-11-16T21:29:43Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If you want to switch to VirtualBox and have a Vmware Virtual Machine you want to use? You can convert a Vmware .vmdk file into a VirtualBox .vdi file that you can use on VirtualBox. &lt;br /&gt;
&lt;br /&gt;
First, download qemu, open a Console and execute: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo apt-get install qemu&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Next, open a console and go to your .vmdk virtual disc image folder and type this: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;qemu-img convert &amp;quot;harddrive-name&amp;quot;.vmdk /filelocation/&amp;quot;harddrive-name&amp;quot;.bin&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Change &amp;quot;harddrive-name&amp;quot; with the name of your .vmdk file and raw-file with the name of the new converted file you want to create. This takes a few minutes, After the conversion is completed. A raw hard disk image has been created. &lt;br /&gt;
&lt;br /&gt;
To convert a raw disk image to a VirtualBox Disk Image (.vdi) file use this command. &lt;br /&gt;
&lt;br /&gt;
The syntax is as follows:&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw /filelocation/&amp;quot;harddrive-name&amp;quot;.bin &amp;lt;outputfile&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo VBoxManage convertfromraw /home/tony/.VirtualBox/HardDisks/HardDisk1.bin /home/tony/.VirtualBox&#039;&#039;&#039; &lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD]&lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw stdin &amp;lt;outputfile&amp;gt; &amp;lt;bytes&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD] &lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
What the parameters mean:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;format&#039;&#039;&#039;  - Selects the disk image format to create. Default is .vdi. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;variant&#039;&#039;&#039;  - Allows to choose a file format variant for the output file. It is a comma-separated list of variant flags. Not all combinations are supported, and specifying inconsistent flags will result in an error message. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The second form forces VBoxManage to read the content for the disk image from standard input(useful for using that command in a pipe).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note: For compatibility with earlier versions of VirtualBox, the “convertdd” command is also supported and mapped internally to the “convertfromraw” command.&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
Run VirtualBox, use the (File Menu) Virtual Media Manager and &#039;Add&#039; the newly cloned drive. This makes Virtual Box &#039;aware&#039; of the drive. Then go though the normal creation steps and choose this as the drive to use for the virtual machine.&lt;br /&gt;
&lt;br /&gt;
You should be able to boot up the newly created virtual machine.&lt;br /&gt;
&lt;br /&gt;
Enjoy your migration to Virtual Box!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Refrences:&lt;br /&gt;
&lt;br /&gt;
http://thedarkmaster.wordpress.com/2007/03/12/vmware-virtual-machine-to-virtual-box-conversion-how-to/&lt;br /&gt;
&lt;br /&gt;
https://wiki.ubuntu.com/UbuntuMagazine/HowTo/Switching_From_VMWare_To_VirtualBox:_.vmdk_To_.vdi_Using_Qemu_+_VdiTool&lt;br /&gt;
&lt;br /&gt;
http://www.cyberciti.biz/tips/converting-from-vmware-images-to-virtualbox-images.html#comments&lt;br /&gt;
&lt;br /&gt;
http://download.virtualbox.org/virtualbox/UserManual.pdf&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3534</id>
		<title>Converting VMWare .vmdk To VirtualBox .vdi Using Qemu+ and VBoxManage</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3534"/>
		<updated>2010-11-16T21:14:55Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If you want to switch to VirtualBox and have a Vmware Virtual Machine you want to use? You can convert a Vmware .vmdk file into a VirtualBox .vdi file that you can use on VirtualBox. &lt;br /&gt;
&lt;br /&gt;
First, download qemu, open a Console and execute: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo apt-get install qemu&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Next, open a console and go to your .vmdk virtual disc image folder and type this: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;qemu-img convert &amp;quot;harddrive-name&amp;quot;.vmdk /filelocation/&amp;quot;harddrive-name&amp;quot;.bin&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Change &amp;quot;harddrive-name&amp;quot; with the name of your .vmdk file and raw-file with the name of the new converted file you want to create. This takes a few minutes, After the conversion is completed. A raw hard disk image has been created. &lt;br /&gt;
&lt;br /&gt;
To convert a raw disk image to a VirtualBox Disk Image (.vdi) file use this command. &lt;br /&gt;
&lt;br /&gt;
The syntax is as follows:&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw /filelocation/&amp;quot;harddrive-name&amp;quot;.bin &amp;lt;outputfile&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo VBoxManage convertfromraw /home/tony/.VirtualBox/HardDisks/HardDisk1.bin /home/tony/.VirtualBox&#039;&#039;&#039; &lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD]&lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw stdin &amp;lt;outputfile&amp;gt; &amp;lt;bytes&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD] &lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
What the parameters mean:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;format&#039;&#039;&#039;  - Selects the disk image format to create. Default is .vdi. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;variant&#039;&#039;&#039;  - Allows to choose a file format variant for the output file. It is a comma-separated list of variant flags. Not all combinations are supported, and specifying inconsistent flags will result in an error message. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The second form forces VBoxManage to read the content for the disk image from standard input(useful for using that command in a pipe).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note: For compatibility with earlier versions of VirtualBox, the “convertdd” command is also supported and mapped internally to the “convertfromraw” command.&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
Run VirtualBox, use the (File Menu) Virtual Media Manager and &#039;Add&#039; the newly cloned drive. This makes Virtual Box &#039;aware&#039; of the drive. Then go though the normal creation steps and choose this as the drive to use for the virtual machine.&lt;br /&gt;
&lt;br /&gt;
You should be able to boot up the newly created virtual machine.&lt;br /&gt;
&lt;br /&gt;
Enjoy your migration to Virtual Box!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Refrences:&lt;br /&gt;
&lt;br /&gt;
http://thedarkmaster.wordpress.com/2007/03/12/vmware-virtual-machine-to-virtual-box-conversion-how-to/&lt;br /&gt;
&lt;br /&gt;
https://wiki.ubuntu.com/UbuntuMagazine/HowTo/Switching_From_VMWare_To_VirtualBox:_.vmdk_To_.vdi_Using_Qemu_+_VdiTool&lt;br /&gt;
&lt;br /&gt;
http://www.cyberciti.biz/tips/converting-from-vmware-images-to-virtualbox-images.html#comments&lt;br /&gt;
&lt;br /&gt;
Oracle VM VirtualBox User Manual.pdf&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3533</id>
		<title>Converting VMWare .vmdk To VirtualBox .vdi Using Qemu+ and VBoxManage</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3533"/>
		<updated>2010-11-16T21:13:38Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If you want to switch to VirtualBox and have a Vmware Virtual Machine you want to use? You can convert a Vmware .vmdk file into a VirtualBox .vdi file that you can use on VirtualBox. &lt;br /&gt;
&lt;br /&gt;
First, download qemu, open a Console and execute: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo apt-get install qemu&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Next, open a console and go to your .vmdk virtual disc image folder and type this: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;qemu-img convert &amp;quot;harddrive-name&amp;quot;.vmdk /filelocation/&amp;quot;harddrive-name&amp;quot;.bin&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Change &amp;quot;harddrive-name&amp;quot; with the name of your .vmdk file and raw-file with the name of the new converted file you want to create. This takes a few minutes, After the conversion is completed. A raw hard disk image has been created. &lt;br /&gt;
&lt;br /&gt;
To convert a raw disk image to a VirtualBox Disk Image (.vdi) file use this command. &lt;br /&gt;
&lt;br /&gt;
The syntax is as follows:&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw /filelocation/&amp;quot;harddrive-name&amp;quot;.bin &amp;lt;outputfile&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo VBoxManage convertfromraw /home/tony/.VirtualBox/HardDisks/HardDisk1.bin /home/tony/.VirtualBox&#039;&#039;&#039; &lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD]&lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw stdin &amp;lt;outputfile&amp;gt; &amp;lt;bytes&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD] &lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
What the parameters mean:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;format&#039;&#039;&#039;  - Selects the disk image format to create. Default is .vdi. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;variant&#039;&#039;&#039;  - Allows to choose a file format variant for the output file. It is a comma-separated list of variant flags. Not all combinations are supported, and specifying inconsistent flags will result in an error message. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The second form forces VBoxManage to read the content for the disk image from standard input(useful for using that command in a pipe).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note: For compatibility with earlier versions of VirtualBox, the “convertdd” command is also supported and mapped internally to the “convertfromraw” command.&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
Run VirtualBox, use the (File Menu) Virtual Media Manager and &#039;Add&#039; the newly cloned drive. This makes Virtual Box &#039;aware&#039; of the drive. Then go though the normal creation steps and choose this as the drive to use for the virtual machine.&lt;br /&gt;
&lt;br /&gt;
You should be able to boot up the newly created virtual machine.&lt;br /&gt;
&lt;br /&gt;
Enjoy your migration to Virtual Box!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Refrences:&lt;br /&gt;
&lt;br /&gt;
http://thedarkmaster.wordpress.com/2007/03/12/vmware-virtual-machine-to-virtual-box-conversion-how-to/&lt;br /&gt;
&lt;br /&gt;
https://wiki.ubuntu.com/UbuntuMagazine/HowTo/Switching_From_VMWare_To_VirtualBox:_.vmdk_To_.vdi_Using_Qemu_+_VdiTool&lt;br /&gt;
&lt;br /&gt;
http://www.cyberciti.biz/tips/converting-from-vmware-images-to-virtualbox-images.html#comments&lt;br /&gt;
&lt;br /&gt;
Oracle VM VirtualBox User Manual.pdf&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3532</id>
		<title>Converting VMWare .vmdk To VirtualBox .vdi Using Qemu+ and VBoxManage</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3532"/>
		<updated>2010-11-16T21:11:09Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If you want to switch to VirtualBox and have a Vmware Virtual Machine you want to use? You can convert a Vmware .vmdk file into a VirtualBox .vdi file that you can use on VirtualBox. &lt;br /&gt;
&lt;br /&gt;
First, download qemu, open a Console and execute: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo apt-get install qemu&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Next, open a console and go to your .vmdk virtual disc image folder and type this: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;qemu-img convert &amp;quot;harddrive-name&amp;quot;.vmdk /filelocation/&amp;quot;harddrive-name&amp;quot;.bin&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Change &amp;quot;harddrive-name&amp;quot; with the name of your .vmdk file and raw-file with the name of the new converted file you want to create. This takes a few minutes, After the conversion is completed. A raw hard disk image has been created. &lt;br /&gt;
&lt;br /&gt;
To convert a raw disk image to a VirtualBox Disk Image (.vdi) file use this command. &lt;br /&gt;
&lt;br /&gt;
The syntax is as follows:&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw &amp;lt;filelocation/filename.bin&amp;gt; &amp;lt;outputfile&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo VBoxManage convertfromraw /home/tony/.VirtualBox/HardDisks/HardDisk1.bin /home/tony/.VirtualBox&#039;&#039;&#039; &lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD]&lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw stdin &amp;lt;outputfile&amp;gt; &amp;lt;bytes&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD] &lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
What the parameters mean:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;format&#039;&#039;&#039;  - Selects the disk image format to create. Default is .vdi. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;variant&#039;&#039;&#039;  - Allows to choose a file format variant for the output file. It is a comma-separated list of variant flags. Not all combinations are supported, and specifying inconsistent flags will result in an error message. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The second form forces VBoxManage to read the content for the disk image from standard input(useful for using that command in a pipe).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note: For compatibility with earlier versions of VirtualBox, the “convertdd” command is also supported and mapped internally to the “convertfromraw” command.&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
Run VirtualBox, use the (File Menu) Virtual Media Manager and &#039;Add&#039; the newly cloned drive. This makes Virtual Box &#039;aware&#039; of the drive. Then go though the normal creation steps and choose this as the drive to use for the virtual machine.&lt;br /&gt;
&lt;br /&gt;
You should be able to boot up the newly created virtual machine.&lt;br /&gt;
&lt;br /&gt;
Enjoy your migration to Virtual Box!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Refrences:&lt;br /&gt;
&lt;br /&gt;
http://thedarkmaster.wordpress.com/2007/03/12/vmware-virtual-machine-to-virtual-box-conversion-how-to/&lt;br /&gt;
&lt;br /&gt;
https://wiki.ubuntu.com/UbuntuMagazine/HowTo/Switching_From_VMWare_To_VirtualBox:_.vmdk_To_.vdi_Using_Qemu_+_VdiTool&lt;br /&gt;
&lt;br /&gt;
http://www.cyberciti.biz/tips/converting-from-vmware-images-to-virtualbox-images.html#comments&lt;br /&gt;
&lt;br /&gt;
Oracle VM VirtualBox User Manual.pdf&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3531</id>
		<title>Converting VMWare .vmdk To VirtualBox .vdi Using Qemu+ and VBoxManage</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3531"/>
		<updated>2010-11-16T21:03:55Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If you want to switch to VirtualBox and have a Vmware Virtual Machine you want to use? You can convert a Vmware .vmdk file into a VirtualBox .vdi file that you can use on VirtualBox. &lt;br /&gt;
&lt;br /&gt;
First, download qemu, open a Console and execute: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo apt-get install qemu&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Next, open a console and go to your .vmdk virtual disc image folder and type this: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;qemu-img convert &amp;quot;harddrive-name&amp;quot;.vmdk -O raw-file.bin&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Change &amp;quot;harddrive-name&amp;quot; with the name of your .vmdk file and raw-file with the name of the new converted file you want to create. This takes a few minutes, After the conversion is completed. A raw hard disk image has been created. &lt;br /&gt;
&lt;br /&gt;
To convert a raw disk image to a VirtualBox Disk Image (.vdi) file use this command. &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
The syntax is as follows:&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw &amp;lt;filelocation/filename.bin&amp;gt; &amp;lt;outputfile&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo VBoxManage convertfromraw /home/tony/.VirtualBox/HardDisks/HardDisk1.bin /home/tony/.VirtualBox&#039;&#039;&#039; &lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD]&lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw stdin &amp;lt;outputfile&amp;gt; &amp;lt;bytes&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD] &lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
What the parameters mean:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;format&#039;&#039;&#039;  - Selects the disk image format to create. Default is .vdi. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;variant&#039;&#039;&#039;  - Allows to choose a file format variant for the output file. It is a comma-separated list of variant flags. Not all combinations are supported, and specifying inconsistent flags will result in an error message. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The second form forces VBoxManage to read the content for the disk image from standard input(useful for using that command in a pipe).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note: For compatibility with earlier versions of VirtualBox, the “convertdd” command is also supported and mapped internally to the “convertfromraw” command.&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
Run VirtualBox, use the (File Menu) Virtual Media Manager and &#039;Add&#039; the newly cloned drive. This makes Virtual Box &#039;aware&#039; of the drive. Then go though the normal creation steps and choose this as the drive to use for the virtual machine.&lt;br /&gt;
&lt;br /&gt;
You should be able to boot up the newly created virtual machine.&lt;br /&gt;
&lt;br /&gt;
Enjoy your migration to Virtual Box!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Refrences:&lt;br /&gt;
&lt;br /&gt;
http://thedarkmaster.wordpress.com/2007/03/12/vmware-virtual-machine-to-virtual-box-conversion-how-to/&lt;br /&gt;
&lt;br /&gt;
https://wiki.ubuntu.com/UbuntuMagazine/HowTo/Switching_From_VMWare_To_VirtualBox:_.vmdk_To_.vdi_Using_Qemu_+_VdiTool&lt;br /&gt;
&lt;br /&gt;
http://www.cyberciti.biz/tips/converting-from-vmware-images-to-virtualbox-images.html#comments&lt;br /&gt;
&lt;br /&gt;
Oracle VM VirtualBox User Manual.pdf&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3530</id>
		<title>Converting VMWare .vmdk To VirtualBox .vdi Using Qemu+ and VBoxManage</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3530"/>
		<updated>2010-11-16T20:59:35Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If you want to switch to VirtualBox and have a Vmware Virtual Machine you want to use? You can convert a Vmware .vmdk file into a VirtualBox .vdi file that you can use on VirtualBox. &lt;br /&gt;
&lt;br /&gt;
First, download qemu, open a Console and execute: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo apt-get install qemu&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Next, open a console and go to your .vmdk virtual disc image folder and type this: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;qemu-img convert &amp;quot;harddrive-name&amp;quot;.vmdk -O raw-file.bin&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Change &amp;quot;harddrive-name&amp;quot; with the name of your .vmdk file and raw-file with the name of the new converted file you want to create. This takes a few minutes, After the conversion is completed. A raw hard disk image has been created. &lt;br /&gt;
&lt;br /&gt;
To convert a raw disk image to a VirtualBox Disk Image (.vdi) file use this command. &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
The syntax is as follows:&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw &amp;lt;filelocation/filename.bin&amp;gt; &amp;lt;outputfile&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo VBoxManage convertfromraw /home/tony/.VirtualBox/HardDisks/HardDisk1.bin /home/tony/.VirtualBox&#039;&#039;&#039; &lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD]&lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw stdin &amp;lt;outputfile&amp;gt; &amp;lt;bytes&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD] &lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
What the parameters mean:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;format&#039;&#039;&#039;  - Selects the disk image format to create. Default is .vdi. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;variant&#039;&#039;&#039;  - Allows to choose a file format variant for the output file. It is a comma-separated list of variant flags. Not all combinations are supported, and specifying inconsistent flags will result in an error message. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The second form forces VBoxManage to read the content for the disk image from standard input(useful for using that command in a pipe).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note: For compatibility with earlier versions of VirtualBox, the “convertdd” command is also supported and mapped internally to the “convertfromraw” command.&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
Run VirtualBox, use the (File Menu) Virtual Media Manager and &#039;Add&#039; the newly cloned drive. This makes Virtual Box &#039;aware&#039; of the drive. Then go though the normal creation steps and choose this as the drive to use for the virtual machine.&lt;br /&gt;
&lt;br /&gt;
You should be able to boot up the newly created virtual machine.&lt;br /&gt;
&lt;br /&gt;
Enjoy your migration to Virtual Box!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Refrences:&lt;br /&gt;
&lt;br /&gt;
http://thedarkmaster.wordpress.com/2007/03/12/vmware-virtual-machine-to-virtual-box-conversion-how-to/&lt;br /&gt;
&lt;br /&gt;
https://wiki.ubuntu.com/UbuntuMagazine/HowTo/Switching_From_VMWare_To_VirtualBox:_.vmdk_To_.vdi_Using_Qemu_+_VdiTool&lt;br /&gt;
&lt;br /&gt;
Oracle VM VirtualBox User Manual.pdf&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3529</id>
		<title>Converting VMWare .vmdk To VirtualBox .vdi Using Qemu+ and VBoxManage</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3529"/>
		<updated>2010-11-16T20:58:06Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If you want to switch to VirtualBox and have a Vmware Virtual Machine you want to use? You can convert a Vmware .vmdk file into a VirtualBox .vdi file that you can use on VirtualBox. &lt;br /&gt;
&lt;br /&gt;
First, download qemu, open a Console and execute: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo apt-get install qemu&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Next, open a console and go to your .vmdk virtual disc image folder and type this: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;qemu-img convert &amp;quot;harddrive-name&amp;quot;.vmdk -O raw-file.bin&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Change &amp;quot;harddrive-name&amp;quot; with the name of your .vmdk file and raw-file with the name of the new converted file you want to create. This takes a few minutes, After the conversion is completed. A raw hard disk image has been created. &lt;br /&gt;
&lt;br /&gt;
To convert a raw disk image to a VirtualBox Disk Image (.vdi) file use this command. &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
The syntax is as follows:&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw &amp;lt;filelocation/filename.bin&amp;gt; &amp;lt;outputfile&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo VBoxManage convertfromraw /home/tony/.VirtualBox/HardDisks/HardDisk1.bin /home/tony/.VirtualBox&#039;&#039;&#039; &lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD]&lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw stdin &amp;lt;outputfile&amp;gt; &amp;lt;bytes&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD] &lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
What the parameters mean:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;format&#039;&#039;&#039; Selects the disk image format to create. Default is .vdi. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;variant&#039;&#039;&#039; Allows to choose a file format variant for the output file. It is a comma-separated list of variant flags. Not all combinations are supported, and specifying inconsistent flags will result in an error message. &lt;br /&gt;
&lt;br /&gt;
The second form forces VBoxManage to read the content for the disk image from standard input(useful for using that command in a pipe).&lt;br /&gt;
&lt;br /&gt;
Note: For compatibility with earlier versions of VirtualBox, the “convertdd” command is also supported and mapped internally to the “convertfromraw” command.&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
Run VirtualBox, use the (File Menu) Virtual Media Manager and &#039;Add&#039; the newly cloned drive. This makes Virtual Box &#039;aware&#039; of the drive. Then go though the normal creation steps and choose this as the drive to use for the virtual machine.&lt;br /&gt;
&lt;br /&gt;
You should be able to boot up the newly created virtual machine.&lt;br /&gt;
&lt;br /&gt;
Enjoy your migration to Virtual Box!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Refrences:&lt;br /&gt;
&lt;br /&gt;
http://thedarkmaster.wordpress.com/2007/03/12/vmware-virtual-machine-to-virtual-box-conversion-how-to/&lt;br /&gt;
&lt;br /&gt;
https://wiki.ubuntu.com/UbuntuMagazine/HowTo/Switching_From_VMWare_To_VirtualBox:_.vmdk_To_.vdi_Using_Qemu_+_VdiTool&lt;br /&gt;
&lt;br /&gt;
Oracle VM VirtualBox User Manual.pdf&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Franske_CNT-2311&amp;diff=3528</id>
		<title>Franske CNT-2311</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Franske_CNT-2311&amp;diff=3528"/>
		<updated>2010-11-16T20:49:28Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: /* Projects */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This is the homepage for the CNT-2311 classes taught by Dr. Ben Franske.&lt;br /&gt;
&lt;br /&gt;
== General Course Information ==&lt;br /&gt;
* [[Franske CNT-2311 Syllabus|Course Syllabus]]&lt;br /&gt;
* [[Franske CNT-2311 FA10 Schedule|Fall 2010 Course Schedule]]&lt;br /&gt;
* [[Franske CNT-2311 Labs|Lab List]]&lt;br /&gt;
* [[Franske CNT Service Project Assignment|Service Project Assignment]]&lt;br /&gt;
* [[Franske Lab Report Format|Lab Report Format]]&lt;br /&gt;
&lt;br /&gt;
== Projects ==&lt;br /&gt;
&lt;br /&gt;
* [[Dual Booting Ubuntu and Windows 7]]&lt;br /&gt;
* [[GUID Partiton Table]]&lt;br /&gt;
* [[Linux VLAN Trunking]]&lt;br /&gt;
* [[Installing Webmin]]&lt;br /&gt;
* [[Nat Masquerading and Firewall]]&lt;br /&gt;
* [[Control Web Access With Squid]]&lt;br /&gt;
* [[Installing MyBB Forum]]&lt;br /&gt;
* [[openvpn]]&lt;br /&gt;
* [[Zoneminder]]&lt;br /&gt;
* [[Understanding Linux Permission Sets]]&lt;br /&gt;
* [[Franske CNT-2311 SP10 Commands|Spring 2010 Commands by Session]]&lt;br /&gt;
* [[Converting VMWare .vmdk To VirtualBox .vdi Using Qemu+ and VBoxManage]]&lt;br /&gt;
&lt;br /&gt;
== Resources ==&lt;br /&gt;
* [[Writing Moodle Questions]]&lt;br /&gt;
=== Software ===&lt;br /&gt;
* [http://www.virtualbox.org Virtualbox]&lt;br /&gt;
** [[VirtualBox Startup Script]]&lt;br /&gt;
=== Major Linux Distributions ===&lt;br /&gt;
* [http://www.debian.org Debian]&lt;br /&gt;
** [http://www.ubuntu.com Ubuntu]&lt;br /&gt;
* [http://www.redhat.com Redhat Enterprise Linux (RHEL)]&lt;br /&gt;
** [http://centos.org CentOS]&lt;br /&gt;
** [http://fedoraproject.org Fedora]&lt;br /&gt;
* [http://www.gentoo.org Gentoo]&lt;br /&gt;
* [http://www.opensuse.org OpenSUSE (Novell)]&lt;br /&gt;
=== Online Linux Tutuorials ===&lt;br /&gt;
* [http://www.linux.org/lessons/beginner Beginning Linux from Linux.org]&lt;br /&gt;
* [https://help.ubuntu.com/community/PostfixBasicSetupHowto Postfix Basic Setup]&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3527</id>
		<title>Converting VMWare .vmdk To VirtualBox .vdi Using Qemu+ and VBoxManage</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3527"/>
		<updated>2010-11-16T20:40:38Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If you want to switch to VirtualBox and have a Vmware Virtual Machine you want to use? You can convert a Vmware .vmdk file into a VirtualBox .vdi file that you can use on VirtualBox. &lt;br /&gt;
&lt;br /&gt;
First, download qemu, open a Console and execute: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo apt-get install qemu&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Next, open a console and go to your .vmdk virtual disc image folder and type this: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;qemu-img convert &amp;quot;harddrive-name&amp;quot;.vmdk -O raw-file.bin&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Change &amp;quot;harddrive-name&amp;quot; with the name of your .vmdk file and raw-file with the name of the new converted file you want to create. This takes a few minutes, After the conversion is completed. A raw hard disk image has been created. &lt;br /&gt;
&lt;br /&gt;
To convert a raw disk image to a VirtualBox Disk Image (.vdi) file use this command. &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
The syntax is as follows:&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw &amp;lt;filelocation/filename.bin&amp;gt; &amp;lt;outputfile&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo VBoxManage convertfromraw /home/tony/.VirtualBox/HardDisks/HardDisk1.bin /home/tony/.VirtualBox&#039;&#039;&#039; &lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD]&lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw stdin &amp;lt;outputfile&amp;gt; &amp;lt;bytes&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD] &lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
What the parameters mean:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;format&#039;&#039;&#039; Selects the disk image format to create. Default is .vdi. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;variant&#039;&#039;&#039; Allows to choose a file format variant for the output file. It is a comma-separated list of variant flags. Not all combinations are supported, and specifying inconsistent flags will result in an error message. &lt;br /&gt;
&lt;br /&gt;
The second form forces VBoxManage to read the content for the disk image from standard input(useful for using that command in a pipe). &lt;br /&gt;
&lt;br /&gt;
Run VirtualBox, use the (File Menu) Virtual Media Manager and &#039;Add&#039; the newly cloned drive. This makes Virtual Box &#039;aware&#039; of the drive. Then go though the normal creation steps and choose this as the drive to use for the virtual machine.&lt;br /&gt;
&lt;br /&gt;
You should be able to boot up the newly created virtual machine.&lt;br /&gt;
&lt;br /&gt;
Enjoy your migration to Virtual Box!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Refrences:&lt;br /&gt;
&lt;br /&gt;
http://thedarkmaster.wordpress.com/2007/03/12/vmware-virtual-machine-to-virtual-box-conversion-how-to/&lt;br /&gt;
&lt;br /&gt;
https://wiki.ubuntu.com/UbuntuMagazine/HowTo/Switching_From_VMWare_To_VirtualBox:_.vmdk_To_.vdi_Using_Qemu_+_VdiTool&lt;br /&gt;
&lt;br /&gt;
Oracle VM VirtualBox User Manual.pdf&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3526</id>
		<title>Converting VMWare .vmdk To VirtualBox .vdi Using Qemu+ and VBoxManage</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3526"/>
		<updated>2010-11-16T20:35:29Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If you want to switch to VirtualBox and have a Vmware Virtual Machine you want to use? You can convert a Vmware .vmdk file into a VirtualBox .vdi file that you can use on VirtualBox. &lt;br /&gt;
&lt;br /&gt;
First, download qemu, open a Console and execute: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo apt-get install qemu&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Next, open a console and go to your .vmdk virtual disc image folder and type this: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;qemu-img convert &amp;quot;harddrive-name&amp;quot;.vmdk -O raw-file.bin&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Change &amp;quot;harddrive-name&amp;quot; with the name of your .vmdk file and raw-file with the name of the new converted file you want to create. This takes a few minutes, After the conversion is completed. A raw hard disk image has been created. &lt;br /&gt;
&lt;br /&gt;
To convert a raw disk image to a VirtualBox Disk Image (.vdi) file use this command. &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
The syntax is as follows:&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw &amp;lt;filelocation/filename.bin&amp;gt; &amp;lt;outputfile&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo VBoxManage convertfromraw /home/tony/.VirtualBox/HardDisks/HardDisk1.bin /home/tony/.VirtualBox&#039;&#039;&#039; &lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD]&lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw stdin &amp;lt;outputfile&amp;gt; &amp;lt;bytes&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD] &lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
What the parameters mean:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;format&#039;&#039;&#039; Selects the disk image format to create. Default is .vdi. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;variant&#039;&#039;&#039; Allows to choose a file format variant for the output file. It is a comma-separated list of variant flags. Not all combinations are supported, and specifying inconsistent flags will result in an error message. &lt;br /&gt;
&lt;br /&gt;
The second form forces VBoxManage to read the content for the disk image from standard input(useful for using that command in a pipe). &lt;br /&gt;
&lt;br /&gt;
Run VirtualBox, use the (File Menu) Virtual Media Manager and &#039;Add&#039; the newly cloned drive. This makes Virtual Box &#039;aware&#039; of the drive. Then go though the normal creation steps and choose this as the drive to use for the virtual machine.&lt;br /&gt;
&lt;br /&gt;
You should be able to boot up the newly created virtual machine.&lt;br /&gt;
&lt;br /&gt;
Enjoy your migration to Virtual Box!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Refrences:&lt;br /&gt;
Oracle VM VirtualBox User Manual.pdf&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3525</id>
		<title>Converting VMWare .vmdk To VirtualBox .vdi Using Qemu+ and VBoxManage</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3525"/>
		<updated>2010-11-16T20:24:21Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If you want to switch to VirtualBox and have a Vmware Virtual Machine you want to use? You can convert a Vmware .vmdk file into a VirtualBox .vdi file that you can use on VirtualBox. &lt;br /&gt;
&lt;br /&gt;
First, download qemu, open a Console and execute: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo apt-get install qemu&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Next, open a console and go to your .vmdk virtual disc image folder and type this: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;qemu-img convert &amp;quot;harddrive-name&amp;quot;.vmdk -O raw-file.bin&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Change &amp;quot;harddrive-name&amp;quot; with the name of your .vmdk file and raw-file with the name of the new converted file you want to create. This takes a few minutes, After the conversion is completed. A raw hard disk image has been created. &lt;br /&gt;
&lt;br /&gt;
To convert a raw disk image to a VirtualBox Disk Image (.vdi) file use this command. &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
The syntax is as follows:&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw &amp;lt;filelocation/filename.bin&amp;gt; &amp;lt;outputfile&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo VBoxManage convertfromraw /home/tony/.VirtualBox/HardDisks/HardDisk1.bin /home/tony/.VirtualBox&#039;&#039;&#039; &lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD]&lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw stdin &amp;lt;outputfile&amp;gt; &amp;lt;bytes&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD] &lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX] &lt;br /&gt;
&lt;br /&gt;
What the parameters mean:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;format&#039;&#039;&#039; Selects the disk image format to create. Default is .vdi. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;variant&#039;&#039;&#039; Allows to choose a file format variant for the output file. It is a comma-separated list of variant flags. Not all combinations are supported, and specifying inconsistent flags will result in an error message. &lt;br /&gt;
&lt;br /&gt;
The second form forces VBoxManage to read the content for the disk image from standard input(useful for using that command in a pipe). &lt;br /&gt;
&lt;br /&gt;
Run VirtualBox, use the (File Menu) Virtual Media Manager and &#039;Add&#039; the newly cloned drive. This makes Virtual Box &#039;aware&#039; of the drive. Then go though the normal creation steps and choose this as the drive to use for the virtual machine.&lt;br /&gt;
&lt;br /&gt;
You should be able to boot up the newly created virtual machine.&lt;br /&gt;
&lt;br /&gt;
Enjoy your migration to Virtual Box!&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3524</id>
		<title>Converting VMWare .vmdk To VirtualBox .vdi Using Qemu+ and VBoxManage</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3524"/>
		<updated>2010-11-16T20:23:47Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If you want to switch to VirtualBox and have a Vmware Virtual Machine you want to use? You can convert a Vmware .vmdk file into a VirtualBox .vdi file that you can use on VirtualBox. &lt;br /&gt;
&lt;br /&gt;
First, download qemu, open a Console and execute: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo apt-get install qemu&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Next, open a console and go to your .vmdk virtual disc image folder and type this: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;qemu-img convert &amp;quot;harddrive-name&amp;quot;.vmdk -O raw-file.bin&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Change &amp;quot;harddrive-name&amp;quot; with the name of your .vmdk file and raw-file with the name of the new converted file you want to create. This takes a few minutes, After the conversion is completed. A raw hard disk image has been created. &lt;br /&gt;
&lt;br /&gt;
To convert a raw disk image to a VirtualBox Disk Image (.vdi) file use this command. &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
The syntax is as follows:&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw &amp;lt;filelocation/filename.bin&amp;gt; &amp;lt;outputfile&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo VBoxManage convertfromraw /home/tony/.VirtualBox/HardDisks/HardDisk1.bin /home/tony/.VirtualBox&#039;&#039;&#039; &lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD]&lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw stdin &amp;lt;outputfile&amp;gt; &amp;lt;bytes&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD] &lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX] &lt;br /&gt;
&lt;br /&gt;
what the parameters mean:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;format&#039;&#039;&#039; Selects the disk image format to create. Default is .vdi. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;variant&#039;&#039;&#039; Allows to choose a file format variant for the output file. It is a comma-separated list of variant flags. Not all combinations are supported, and specifying inconsistent flags will result in an error message. &lt;br /&gt;
&lt;br /&gt;
The second form forces VBoxManage to read the content for the disk image from standard input(useful for using that command in a pipe). &lt;br /&gt;
&lt;br /&gt;
Run VirtualBox, use the (File Menu) Virtual Media Manager and &#039;Add&#039; the newly cloned drive. This makes Virtual Box &#039;aware&#039; of the drive. Then go though the normal creation steps and choose this as the drive to use for the virtual machine.&lt;br /&gt;
&lt;br /&gt;
You should be able to boot up the newly created virtual machine.&lt;br /&gt;
&lt;br /&gt;
Enjoy your migration to Virtual Box!&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3523</id>
		<title>Converting VMWare .vmdk To VirtualBox .vdi Using Qemu+ and VBoxManage</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3523"/>
		<updated>2010-11-16T20:21:47Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If you want to switch to VirtualBox and have a Vmware Virtual Machine you want to use? You can convert a Vmware .vmdk file into a VirtualBox .vdi file that you can use on VirtualBox. &lt;br /&gt;
&lt;br /&gt;
First, download qemu, open a Console and execute: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo apt-get install qemu&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Next, open a console and go to your .vmdk virtual disc image folder and type this: &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;qemu-img convert &amp;quot;harddrive-name&amp;quot;.vmdk -O raw-file.bin&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Change &amp;quot;harddrive-name&amp;quot; with the name of your .vmdk file and raw-file with the name of the new converted file you want to create. This takes a few minutes, After the conversion is completed. A raw hard disk image has been created. &lt;br /&gt;
&lt;br /&gt;
To convert a raw disk image to a VirtualBox Disk Image (.vdi) file use this command. &lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
The syntax is as follows:&lt;br /&gt;
 &lt;br /&gt;
   &#039;&#039;&#039;VBoxManage convertfromraw &amp;lt;filelocation/filename.bin&amp;gt; &amp;lt;outputfile&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
   &#039;&#039;&#039;sudo VBoxManage convertfromraw /home/tony/.VirtualBox/HardDisks/HardDisk1.bin /home/tony/.VirtualBox&#039;&#039;&#039; &lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD]&lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
VBoxManage convertfromraw stdin &amp;lt;outputfile&amp;gt; &amp;lt;bytes&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD] &lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX] &lt;br /&gt;
&lt;br /&gt;
what the parameters mean:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;format&#039;&#039;&#039; Selects the disk image format to create. Default is .vdi. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;variant&#039;&#039;&#039; Allows to choose a file format variant for the output file. It is a comma-separated list of variant flags. Not all combinations are supported, and specifying inconsistent flags will result in an error message. &lt;br /&gt;
&lt;br /&gt;
The second form forces VBoxManage to read the content for the disk image from standard input(useful for using that command in a pipe). &lt;br /&gt;
&lt;br /&gt;
Run VirtualBox, use the (File Menu) Virtual Media Manager and &#039;Add&#039; the newly cloned drive. This makes Virtual Box &#039;aware&#039; of the drive. Then go though the normal creation steps and choose this as the drive to use for the virtual machine.&lt;br /&gt;
&lt;br /&gt;
You should be able to boot up the newly created virtual machine.&lt;br /&gt;
&lt;br /&gt;
Enjoy your migration to Virtual Box!&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3522</id>
		<title>Converting VMWare .vmdk To VirtualBox .vdi Using Qemu+ and VBoxManage</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3522"/>
		<updated>2010-11-16T20:20:43Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If you want to switch to VirtualBox and have a Vmware Virtual Machine you want to use? You can convert a Vmware .vmdk file into a VirtualBox .vdi file that you can use on VirtualBox. &lt;br /&gt;
&lt;br /&gt;
First, download qemu, open a Console and execute: &lt;br /&gt;
&lt;br /&gt;
-&#039;&#039;&#039;sudo apt-get install qemu&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Next, open a console and go to your .vmdk virtual disc image folder and type this: &lt;br /&gt;
&lt;br /&gt;
-&#039;&#039;&#039;qemu-img convert &amp;quot;harddrive-name&amp;quot;.vmdk -O raw-file.bin&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Change &amp;quot;harddrive-name&amp;quot; with the name of your .vmdk file and raw-file with the name of the new converted file you want to create. This takes a few minutes, After the conversion is completed. A raw hard disk image has been created. &lt;br /&gt;
&lt;br /&gt;
To convert a raw disk image to a VirtualBox Disk Image (.vdi) file use this command. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;VBoxManage convertfromraw&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
The syntax is as follows:&lt;br /&gt;
 &lt;br /&gt;
-&#039;&#039;&#039;VBoxManage convertfromraw &amp;lt;filelocation/filename.bin&amp;gt; &amp;lt;outputfile&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
-&#039;&#039;&#039;sudo VBoxManage convertfromraw /home/tony/.VirtualBox/HardDisks/HardDisk1.bin /home/tony/.VirtualBox&#039;&#039;&#039; &lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD]&lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
VBoxManage convertfromraw stdin &amp;lt;outputfile&amp;gt; &amp;lt;bytes&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD] &lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX] &lt;br /&gt;
&lt;br /&gt;
what the parameters mean:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;format&#039;&#039;&#039; Selects the disk image format to create. Default is .vdi. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;variant&#039;&#039;&#039; Allows to choose a file format variant for the output file. It is a comma-separated list of variant flags. Not all combinations are supported, and specifying inconsistent flags will result in an error message. &lt;br /&gt;
&lt;br /&gt;
The second form forces VBoxManage to read the content for the disk image from standard input(useful for using that command in a pipe). &lt;br /&gt;
&lt;br /&gt;
Run VirtualBox, use the (File Menu) Virtual Media Manager and &#039;Add&#039; the newly cloned drive. This makes Virtual Box &#039;aware&#039; of the drive. Then go though the normal creation steps and choose this as the drive to use for the virtual machine.&lt;br /&gt;
&lt;br /&gt;
You should be able to boot up the newly created virtual machine.&lt;br /&gt;
&lt;br /&gt;
Enjoy your migration to Virtual Box!&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3521</id>
		<title>Converting VMWare .vmdk To VirtualBox .vdi Using Qemu+ and VBoxManage</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3521"/>
		<updated>2010-11-16T20:18:12Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If you want to switch to VirtualBox and have a Vmware Virtual Machine you want to use? You can convert a Vmware .vmdk file into a VirtualBox .vdi file that you can use on VirtualBox. &lt;br /&gt;
&lt;br /&gt;
First, download qemu, open a Console and execute: &lt;br /&gt;
&lt;br /&gt;
sudo apt-get install qemu &lt;br /&gt;
&lt;br /&gt;
Next, open a console and go to your .vmdk virtual disc image folder and type this: &lt;br /&gt;
&lt;br /&gt;
qemu-img convert &amp;quot;harddrive-name&amp;quot;.vmdk -O raw-file.bin &lt;br /&gt;
&lt;br /&gt;
Change &amp;quot;harddrive-name&amp;quot; with the name of your .vmdk file and raw-file with the name of the new converted file you want to create. This takes a few minutes, After the conversion is completed. A raw hard disk image has been created. &lt;br /&gt;
&lt;br /&gt;
To convert a raw disk image to a VirtualBox Disk Image (.vdi) file use this command. &lt;br /&gt;
&lt;br /&gt;
VBoxManage convertfromraw &lt;br /&gt;
&lt;br /&gt;
The syntax is as follows:&lt;br /&gt;
 &lt;br /&gt;
VBoxManage convertfromraw &amp;lt;filelocation/filename.bin&amp;gt; &amp;lt;outputfile&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
sudo VBoxManage convertfromraw /home/tony/.VirtualBox/HardDisks/HardDisk1.bin /home/tony/.VirtualBox &lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD]&lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
VBoxManage convertfromraw stdin &amp;lt;outputfile&amp;gt; &amp;lt;bytes&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD] &lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX] &lt;br /&gt;
&lt;br /&gt;
what the parameters mean:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;format&#039;&#039;&#039; Selects the disk image format to create. Default is .vdi. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;variant&#039;&#039;&#039; Allows to choose a file format variant for the output file. It is a comma-separated list of variant flags. Not all combinations are supported, and specifying inconsistent flags will result in an error message. &lt;br /&gt;
&lt;br /&gt;
The second form forces VBoxManage to read the content for the disk image from standard input(useful for using that command in a pipe). &lt;br /&gt;
&lt;br /&gt;
Run VirtualBox, use the (File Menu) Virtual Media Manager and &#039;Add&#039; the newly cloned drive. This makes Virtual Box &#039;aware&#039; of the drive. Then go though the normal creation steps and choose this as the drive to use for the virtual machine.&lt;br /&gt;
&lt;br /&gt;
You should be able to boot up the newly created virtual machine.&lt;br /&gt;
&lt;br /&gt;
Enjoy your migration to Virtual Box!&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3520</id>
		<title>Converting VMWare .vmdk To VirtualBox .vdi Using Qemu+ and VBoxManage</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3520"/>
		<updated>2010-11-16T20:10:01Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If you want to switch to VirtualBox and have a Vmware Virtual Machine you want to use? You can convert a Vmware .vmdk file into a VirtualBox .vdi file that you can use on VirtualBox. &lt;br /&gt;
&lt;br /&gt;
First, download qemu, open a Console and execute: &lt;br /&gt;
&lt;br /&gt;
sudo apt-get install qemu &lt;br /&gt;
&lt;br /&gt;
Next, open a console and go to your .vmdk virtual disc image folder and type this: &lt;br /&gt;
&lt;br /&gt;
qemu-img convert &amp;quot;harddrive-name&amp;quot;.vmdk -O raw-file.bin &lt;br /&gt;
&lt;br /&gt;
Change &amp;quot;harddrive-name&amp;quot; with the name of your .vmdk file and raw-file with the name of the new converted file you want to create. This takes a few minutes, After the conversion is completed. A raw hard disk image has been created. &lt;br /&gt;
&lt;br /&gt;
To convert a raw disk image to a VirtualBox Disk Image (.vdi) file use this command. &lt;br /&gt;
&lt;br /&gt;
VBoxManage convertfromraw &lt;br /&gt;
&lt;br /&gt;
The syntax is as follows:&lt;br /&gt;
 &lt;br /&gt;
VBoxManage convertfromraw &amp;lt;filelocation/filename.bin&amp;gt; &amp;lt;outputfile&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
sudo VBoxManage convertfromraw /home/tony/.VirtualBox/HardDisks/HardDisk1.bin /home/tony/.VirtualBox &lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD]&lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
VBoxManage convertfromraw stdin &amp;lt;outputfile&amp;gt; &amp;lt;bytes&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD] &lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX] &lt;br /&gt;
&lt;br /&gt;
what the parameters mean:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;format&#039;&#039;&#039; Selects the disk image format to create. Default is .vdi. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;variant&#039;&#039;&#039; Allows to choose a file format variant for the output file. It is a comma-separated list of variant flags. Not all combinations are supported, and specifying inconsistent flags will result in an error message. &lt;br /&gt;
&lt;br /&gt;
The second form forces VBoxManage to read the content for the disk image from standard input(useful for using that command in a pipe). &lt;br /&gt;
&lt;br /&gt;
Run VirtualBox, use the (File Menu) Virtual Media Manager and &#039;Add&#039; the newly cloned drive. This makes Virtual Box &#039;aware&#039; of the drive. Then go though the normal creation steps and choose this as the drive to use for the virtual machine.&lt;br /&gt;
&lt;br /&gt;
You should be able to boot up the newly created virtual machine.&lt;br /&gt;
&lt;br /&gt;
Now we’re all setted up. Let’s run Virtual Box. At this point, you have to create a new Virtual Machine, set it up as you like and choose the new-file.vdi as disc image. If everything is okay, the machine will run, even if it will have to be settep up again a bit from inside the OS you’re using. For example, Windows has got a lot of problems in this part. &lt;br /&gt;
&lt;br /&gt;
When I started my old disc image converted into a new compressed .vdi file inside a new Virtual Machine created with VBox, WinXP refused to start. I had to insert in the CD-Rom my original WinXP Cd to boot from cd and restore the windows installation! Windows, this way, reconfigured and installed each new virtual peripheral so that at reboot everything was okay and all my programs where left installed where they were. &lt;br /&gt;
&lt;br /&gt;
Enjoy your migration to Virtual Box!&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3519</id>
		<title>Converting VMWare .vmdk To VirtualBox .vdi Using Qemu+ and VBoxManage</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3519"/>
		<updated>2010-11-16T20:07:13Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If you want to switch to VirtualBox and have a Vmware Virtual Machine you want to use? You can convert a Vmware .vmdk file into a VirtualBox .vdi file that you can use on VirtualBox. &lt;br /&gt;
&lt;br /&gt;
First, download qemu, open a Console and execute: &lt;br /&gt;
&lt;br /&gt;
sudo apt-get install qemu &lt;br /&gt;
&lt;br /&gt;
Next, open a console and go to your .vmdk virtual disc image folder and type this: &lt;br /&gt;
&lt;br /&gt;
qemu-img convert &amp;quot;harddrive-name&amp;quot;.vmdk -O raw-file.bin &lt;br /&gt;
&lt;br /&gt;
Change &amp;quot;harddrive-name&amp;quot; with the name of your .vmdk file and raw-file with the name of the new converted file you want to create. This takes a few minutes, After the conversion is completed. A raw hard disk image has been created. &lt;br /&gt;
&lt;br /&gt;
To convert a raw disk image to a VirtualBox Disk Image (.vdi) file use this command. &lt;br /&gt;
&lt;br /&gt;
VBoxManage convertfromraw &lt;br /&gt;
&lt;br /&gt;
The syntax is as follows:&lt;br /&gt;
 &lt;br /&gt;
VBoxManage convertfromraw &amp;lt;filelocation/filename.bin&amp;gt; &amp;lt;outputfile&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
sudo VBoxManage convertfromraw /home/tony/.VirtualBox/HardDisks/HardDisk1.bin /home/tony/.VirtualBox &lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD]&lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
VBoxManage convertfromraw stdin &amp;lt;outputfile&amp;gt; &amp;lt;bytes&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD] &lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX] &lt;br /&gt;
&lt;br /&gt;
what the parameters mean:&lt;br /&gt;
&lt;br /&gt;
format Select the disk image format to create. Default is VDI. &lt;br /&gt;
&lt;br /&gt;
variant Allow to choose a file format variant for the output file. It is a comma-separated list of variant flags. Not all combinations are supported, and specifying inconsistent flags will result in an error message. &lt;br /&gt;
&lt;br /&gt;
The second form forces VBoxManage to read the content for the disk image from standard input(useful for using that command in a pipe). &lt;br /&gt;
&lt;br /&gt;
Run VirtualBox, use the (File Menu) Virtual Media Manager and &#039;Add&#039; the newly cloned drive. This makes Virtual Box &#039;aware&#039; of the drive. Then go though the normal creation steps and choose this as the drive to use for the virtual machine.&lt;br /&gt;
&lt;br /&gt;
You should be able to boot up the newly created virtual machine.&lt;br /&gt;
&lt;br /&gt;
Now we’re all setted up. Let’s run Virtual Box. At this point, you have to create a new Virtual Machine, set it up as you like and choose the new-file.vdi as disc image. If everything is okay, the machine will run, even if it will have to be settep up again a bit from inside the OS you’re using. For example, Windows has got a lot of problems in this part. &lt;br /&gt;
&lt;br /&gt;
When I started my old disc image converted into a new compressed .vdi file inside a new Virtual Machine created with VBox, WinXP refused to start. I had to insert in the CD-Rom my original WinXP Cd to boot from cd and restore the windows installation! Windows, this way, reconfigured and installed each new virtual peripheral so that at reboot everything was okay and all my programs where left installed where they were. &lt;br /&gt;
&lt;br /&gt;
Enjoy your migration to Virtual Box!&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3518</id>
		<title>Converting VMWare .vmdk To VirtualBox .vdi Using Qemu+ and VBoxManage</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3518"/>
		<updated>2010-11-16T19:57:16Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If you want to switch to VirtualBox and have a Vmware Virtual Machine you want to use? You can convert a Vmware .vmdk file into a VirtualBox .vdi file that you can use on VirtualBox. &lt;br /&gt;
&lt;br /&gt;
First, download qemu, open a Console and execute: &lt;br /&gt;
&lt;br /&gt;
sudo apt-get install qemu &lt;br /&gt;
&lt;br /&gt;
Next, open a console and go to your .vmdk virtual disc image folder and type this: &lt;br /&gt;
&lt;br /&gt;
qemu-img convert &amp;quot;harddrive-name&amp;quot;.vmdk -O raw-file.bin &lt;br /&gt;
&lt;br /&gt;
Change &amp;quot;harddrive-name&amp;quot; with the name of your .vmdk file and raw-file with the name of the new converted file you want to create. This takes a few minutes, After the conversion is completed. A raw hard disk image has been created. &lt;br /&gt;
&lt;br /&gt;
To convert a raw disk image to a VirtualBox Disk Image (VDI) file use this command. &lt;br /&gt;
&lt;br /&gt;
VBoxManage convertfromraw &lt;br /&gt;
&lt;br /&gt;
The syntax is as follows: sudo VBoxManage clonehd /home/edwardss/.VirtualBox/HardDisks/XPHardDisk1.vdi /home/edwardss/.VirtualBox &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
VBoxManage convertfromraw &amp;lt;filename&amp;gt; &amp;lt;outputfile&amp;gt; &lt;br /&gt;
[--format VDI|VMDK|VHD]&lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
VBoxManage convertfromraw stdin &amp;lt;outputfile&amp;gt; &amp;lt;bytes&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD] &lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX] &lt;br /&gt;
&lt;br /&gt;
where the parameters mean: format Select the disk image format to create. Default is VDI. &lt;br /&gt;
&lt;br /&gt;
variant Allow to choose a file format variant for the output file. It is a comma-separated list of variant flags. Not all combinations are supported, and specifying inconsistent flags will result in an error message. &lt;br /&gt;
&lt;br /&gt;
The second form forces VBoxManage to read the content for the disk image from standard input(useful for using that command in a pipe). &lt;br /&gt;
&lt;br /&gt;
Run VirtualBox, use the (File Menu) Virtual Media Manager and &#039;Add&#039; the newly cloned drive. This makes Virtual Box &#039;aware&#039; of the drive. Then go though the normal creation steps and choose this as the drive to use for the virtual machine.&lt;br /&gt;
&lt;br /&gt;
You should be able to boot up the newly created virtual machine.&lt;br /&gt;
&lt;br /&gt;
Now we’re all setted up. Let’s run Virtual Box. At this point, you have to create a new Virtual Machine, set it up as you like and choose the new-file.vdi as disc image. If everything is okay, the machine will run, even if it will have to be settep up again a bit from inside the OS you’re using. For example, Windows has got a lot of problems in this part. &lt;br /&gt;
&lt;br /&gt;
When I started my old disc image converted into a new compressed .vdi file inside a new Virtual Machine created with VBox, WinXP refused to start. I had to insert in the CD-Rom my original WinXP Cd to boot from cd and restore the windows installation! Windows, this way, reconfigured and installed each new virtual peripheral so that at reboot everything was okay and all my programs where left installed where they were. &lt;br /&gt;
&lt;br /&gt;
Enjoy your migration to Virtual Box!&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3517</id>
		<title>Converting VMWare .vmdk To VirtualBox .vdi Using Qemu+ and VBoxManage</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3517"/>
		<updated>2010-11-16T19:49:51Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If you want to switch to VirtualBox and have a Vmware Virtual Machine you want to use? You can convert a Vmware .vmdk file into a VirtualBox .vdi file that you can use on VirtualBox. &lt;br /&gt;
&lt;br /&gt;
First, download qemu, open a Console and execute: &lt;br /&gt;
&lt;br /&gt;
sudo apt-get install qemu &lt;br /&gt;
&lt;br /&gt;
Next, open a console and go to your .vmdk virtual disc image folder and type this: &lt;br /&gt;
&lt;br /&gt;
qemu-img convert &amp;quot;harddrive-name&amp;quot;.vmdk -O raw-file.bin &lt;br /&gt;
&lt;br /&gt;
Change &amp;quot;harddrive-name&amp;quot; with the name of your .vmdk file and raw-file with the name of the new converted file you want to create. This takes a few minutes, After the conversion is completed. A raw hard disk image has been created. &lt;br /&gt;
&lt;br /&gt;
To convert a raw disk image to a VirtualBox Disk Image (VDI) file use this command. &lt;br /&gt;
&lt;br /&gt;
VBoxManage convertfromraw &lt;br /&gt;
&lt;br /&gt;
The syntax is as follows: sudo VBoxManage clonehd /home/edwardss/.VirtualBox/HardDisks/XPHardDisk1.vdi /home/edwardss/.VirtualBox &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
VBoxManage convertfromraw &amp;lt;filename&amp;gt; &amp;lt;outputfile&amp;gt; &lt;br /&gt;
[--format VDI|VMDK|VHD]&lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX]&lt;br /&gt;
 &lt;br /&gt;
VBoxManage convertfromraw stdin &amp;lt;outputfile&amp;gt; &amp;lt;bytes&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
[--format VDI|VMDK|VHD] &lt;br /&gt;
&lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX] &lt;br /&gt;
&lt;br /&gt;
where the parameters mean: format Select the disk image format to create. Default is VDI. &lt;br /&gt;
&lt;br /&gt;
variant Allow to choose a file format variant for the output file. It is a comma-separated list of variant flags. Not all combinations are supported, and specifying inconsistent flags will result in an error message. &lt;br /&gt;
&lt;br /&gt;
The second form forces VBoxManage to read the content for the disk image from standard input(useful for using that command in a pipe). &lt;br /&gt;
&lt;br /&gt;
Run VirtualBox, use the (File Menu) Virtual Media Manager and &#039;Add&#039; the newly cloned drive. This makes Virtual Box &#039;aware&#039; of the drive. Then go though the normal creation steps and choose this as the drive to use for the virtual machine. &lt;br /&gt;
&lt;br /&gt;
Downloading that vditool file is not the simplest thing in the world. If you try and open it with Firefox, for page with weird code in it will appear. To save this vditool file, right click on the link and choose to save the file. You can also tell a download manager to download this file for you. I suggest you the download manager: Aria. It is into Ubuntu repositoryes. &lt;br /&gt;
&lt;br /&gt;
Now that we’ve got vditool, we need to make it executable. Right click on the file, open its propertyes and set the “Executable” permission option. In Gnome, go into the Permission tag and activate the “Let this program be executed” or something like that option (Remember, my Ubuntu is Italian, dunno what’s your exact translation). &lt;br /&gt;
&lt;br /&gt;
At that point, we’ll need the console again, from the same dir where you’ve stored dvitool and the .bin raw file. Run this from console into the interested dir: &lt;br /&gt;
&lt;br /&gt;
LD_LIBRARY_PATH=/opt/VirtualBox* ./vditool DD new-file.vdi old-file.bin &lt;br /&gt;
&lt;br /&gt;
Where new-file.vdi is the file that will be outputted by vdi tool and must be the first to appear in the command. The second filename, old-file.bin, is the name of the raw disc image we converted the .vmdk image to. Naturally, change this invented names with real ones. &lt;br /&gt;
&lt;br /&gt;
If you wish, remember that you can run vditool for other tasks too. Now we’ll run it to optimize the filesize of the .vdi image file, for example. For a list of all commands, you’ve just got to execute vditool without any other option. &lt;br /&gt;
&lt;br /&gt;
Now we’re going to optimize the filesize of the newly converted .dvi file, let’s call it new-file.dvi and fromth console in the dir where you’ve got this file, run: &lt;br /&gt;
&lt;br /&gt;
LD_LIBRARY_PATH=/opt/VirtualBox* ./vditool SHRINK new-file.vdi &lt;br /&gt;
&lt;br /&gt;
Now we’re all setted up. Let’s run Virtual Box. At this point, you have to create a new Virtual Machine, set it up as you like and choose the new-file.dvi as disc image. If everything is okay, the machine will run, even if it will have to be settep up again a bit from inside the OS you’re using. For example, Windows has got a lot of problems in this part. &lt;br /&gt;
&lt;br /&gt;
When I started my old disc image converte into a new compressed .vdi file inside a new Virtual Machine created with VBox, WinXP refused to start. I had to insert in the CD-Rom my original WinXP Cd to boot from cd and restore the windows installation! Windows, this way, reconfigured and installed each new virtual peripheral so that at reboot everything was okay and all my programs where left installed where they were. &lt;br /&gt;
&lt;br /&gt;
Multiple vmdk files to vdi &lt;br /&gt;
&lt;br /&gt;
A lot of people have been asking me about this. I sincerely didn’t have a clue on how to convert multiple vmdk vmware virtual disc images into a vdi VB virtual disc image. Luckily, Leonardo Cosmai just provided us with a solution in one of the comments on this post! You can see that post for yourself. &lt;br /&gt;
&lt;br /&gt;
What you have to do is: &lt;br /&gt;
&lt;br /&gt;
1) Downloading and installing VMWare Server for your platform, it is freeware but proprietay software, it is opensourced but you’ll need to subscribe for a license to use it. We’ll just use this to convert multiplevmdk images into a single one. You can find VMWare Server here. &lt;br /&gt;
&lt;br /&gt;
2) Run a terminal, move in the dir where you store your multiple vmdk disc images and run: &lt;br /&gt;
&lt;br /&gt;
vmware-vdiskmanager -r source_multiples.vmdk -t 2 single_file.vmdk &lt;br /&gt;
&lt;br /&gt;
And that’s all! The multiple vmdk images will be converted into one single vmdk image file. At that point you’ll be able to normally use this guide to convert the newly obtained vmdk disc image into a single .vdi file! &lt;br /&gt;
&lt;br /&gt;
I sincerely hope this helped a lot of people out there. It is almost impossible to find a way to use vditool in Google for now. No matter how much you google, I spent the all day trying to find something. Thanks to the guys from the VBox IRC Channel for helping me out, I wasn’t going to get out from this problem alone. And a lot of people in Ubuntu Forum where in my same conditions, so…. Enjoy your migration to Virtual Box!&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3516</id>
		<title>Converting VMWare .vmdk To VirtualBox .vdi Using Qemu+ and VBoxManage</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3516"/>
		<updated>2010-11-16T19:48:45Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If you want to switch to VirtualBox and have a Vmware Virtual Machine you want to use? You can convert a Vmware .vmdk file into a VirtualBox .vdi file that you can use on VirtualBox. &lt;br /&gt;
&lt;br /&gt;
First, download qemu, open a Console and execute: &lt;br /&gt;
&lt;br /&gt;
sudo apt-get install qemu &lt;br /&gt;
&lt;br /&gt;
Next, open a console and go to your .vmdk virtual disc image folder and type this: &lt;br /&gt;
&lt;br /&gt;
qemu-img convert &amp;quot;harddrive-name&amp;quot;.vmdk -O raw-file.bin &lt;br /&gt;
&lt;br /&gt;
Change &amp;quot;harddrive-name&amp;quot; with the name of your .vmdk file and raw-file with the name of the new converted file you want to create. This takes a few minutes, After the conversion is completed. A raw hard disk image has been created. &lt;br /&gt;
&lt;br /&gt;
To convert a raw disk image to a VirtualBox Disk Image (VDI) file use this command. &lt;br /&gt;
&lt;br /&gt;
VBoxManage convertfromraw &lt;br /&gt;
&lt;br /&gt;
The syntax is as follows: sudo VBoxManage clonehd /home/edwardss/.VirtualBox/HardDisks/XPHardDisk1.vdi /home/edwardss/.VirtualBox &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
VBoxManage convertfromraw &amp;lt;filename&amp;gt; &amp;lt;outputfile&amp;gt; &lt;br /&gt;
[--format VDI|VMDK|VHD] &lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX] &lt;br /&gt;
VBoxManage convertfromraw stdin &amp;lt;outputfile&amp;gt; &amp;lt;bytes&amp;gt; &lt;br /&gt;
[--format VDI|VMDK|VHD] &lt;br /&gt;
[--variant Standard,Fixed,Split2G,Stream,ESX] &lt;br /&gt;
&lt;br /&gt;
where the parameters mean: format Select the disk image format to create. Default is VDI. &lt;br /&gt;
&lt;br /&gt;
variant Allow to choose a file format variant for the output file. It is a comma-separated list of variant flags. Not all combinations are supported, and specifying inconsistent flags will result in an error message. &lt;br /&gt;
&lt;br /&gt;
The second form forces VBoxManage to read the content for the disk image from standard input(useful for using that command in a pipe). &lt;br /&gt;
&lt;br /&gt;
Run VirtualBox, use the (File Menu) Virtual Media Manager and &#039;Add&#039; the newly cloned drive. This makes Virtual Box &#039;aware&#039; of the drive. Then go though the normal creation steps and choose this as the drive to use for the virtual machine. &lt;br /&gt;
&lt;br /&gt;
Downloading that vditool file is not the simplest thing in the world. If you try and open it with Firefox, for page with weird code in it will appear. To save this vditool file, right click on the link and choose to save the file. You can also tell a download manager to download this file for you. I suggest you the download manager: Aria. It is into Ubuntu repositoryes. &lt;br /&gt;
&lt;br /&gt;
Now that we’ve got vditool, we need to make it executable. Right click on the file, open its propertyes and set the “Executable” permission option. In Gnome, go into the Permission tag and activate the “Let this program be executed” or something like that option (Remember, my Ubuntu is Italian, dunno what’s your exact translation). &lt;br /&gt;
&lt;br /&gt;
At that point, we’ll need the console again, from the same dir where you’ve stored dvitool and the .bin raw file. Run this from console into the interested dir: &lt;br /&gt;
&lt;br /&gt;
LD_LIBRARY_PATH=/opt/VirtualBox* ./vditool DD new-file.vdi old-file.bin &lt;br /&gt;
&lt;br /&gt;
Where new-file.vdi is the file that will be outputted by vdi tool and must be the first to appear in the command. The second filename, old-file.bin, is the name of the raw disc image we converted the .vmdk image to. Naturally, change this invented names with real ones. &lt;br /&gt;
&lt;br /&gt;
If you wish, remember that you can run vditool for other tasks too. Now we’ll run it to optimize the filesize of the .vdi image file, for example. For a list of all commands, you’ve just got to execute vditool without any other option. &lt;br /&gt;
&lt;br /&gt;
Now we’re going to optimize the filesize of the newly converted .dvi file, let’s call it new-file.dvi and fromth console in the dir where you’ve got this file, run: &lt;br /&gt;
&lt;br /&gt;
LD_LIBRARY_PATH=/opt/VirtualBox* ./vditool SHRINK new-file.vdi &lt;br /&gt;
&lt;br /&gt;
Now we’re all setted up. Let’s run Virtual Box. At this point, you have to create a new Virtual Machine, set it up as you like and choose the new-file.dvi as disc image. If everything is okay, the machine will run, even if it will have to be settep up again a bit from inside the OS you’re using. For example, Windows has got a lot of problems in this part. &lt;br /&gt;
&lt;br /&gt;
When I started my old disc image converte into a new compressed .vdi file inside a new Virtual Machine created with VBox, WinXP refused to start. I had to insert in the CD-Rom my original WinXP Cd to boot from cd and restore the windows installation! Windows, this way, reconfigured and installed each new virtual peripheral so that at reboot everything was okay and all my programs where left installed where they were. &lt;br /&gt;
&lt;br /&gt;
Multiple vmdk files to vdi &lt;br /&gt;
&lt;br /&gt;
A lot of people have been asking me about this. I sincerely didn’t have a clue on how to convert multiple vmdk vmware virtual disc images into a vdi VB virtual disc image. Luckily, Leonardo Cosmai just provided us with a solution in one of the comments on this post! You can see that post for yourself. &lt;br /&gt;
&lt;br /&gt;
What you have to do is: &lt;br /&gt;
&lt;br /&gt;
1) Downloading and installing VMWare Server for your platform, it is freeware but proprietay software, it is opensourced but you’ll need to subscribe for a license to use it. We’ll just use this to convert multiplevmdk images into a single one. You can find VMWare Server here. &lt;br /&gt;
&lt;br /&gt;
2) Run a terminal, move in the dir where you store your multiple vmdk disc images and run: &lt;br /&gt;
&lt;br /&gt;
vmware-vdiskmanager -r source_multiples.vmdk -t 2 single_file.vmdk &lt;br /&gt;
&lt;br /&gt;
And that’s all! The multiple vmdk images will be converted into one single vmdk image file. At that point you’ll be able to normally use this guide to convert the newly obtained vmdk disc image into a single .vdi file! &lt;br /&gt;
&lt;br /&gt;
I sincerely hope this helped a lot of people out there. It is almost impossible to find a way to use vditool in Google for now. No matter how much you google, I spent the all day trying to find something. Thanks to the guys from the VBox IRC Channel for helping me out, I wasn’t going to get out from this problem alone. And a lot of people in Ubuntu Forum where in my same conditions, so…. Enjoy your migration to Virtual Box!&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3515</id>
		<title>Converting VMWare .vmdk To VirtualBox .vdi Using Qemu+ and VBoxManage</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu%2B_and_VBoxManage&amp;diff=3515"/>
		<updated>2010-11-16T19:47:31Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: Created page with &amp;#039;If you want to switch to VirtualBox and have a Vmware Virtual Machine you want to use? You can convert a Vmware .vmdk file into a VirtualBox .vdi file that you can use on Virtual…&amp;#039;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If you want to switch to VirtualBox and have a Vmware Virtual Machine you want to use? You can convert a Vmware .vmdk file into a VirtualBox .vdi file that you can use on VirtualBox. &lt;br /&gt;
&lt;br /&gt;
First, download qemu, open a Console and execute: &lt;br /&gt;
&lt;br /&gt;
sudo apt-get install qemu &lt;br /&gt;
&lt;br /&gt;
Next, open a console and go to your .vmdk virtual disc image folder and type this: &lt;br /&gt;
&lt;br /&gt;
qemu-img convert &amp;quot;harddrive-name&amp;quot;.vmdk -O raw-file.bin &lt;br /&gt;
&lt;br /&gt;
Change &amp;quot;harddrive-name&amp;quot; with the name of your .vmdk file and raw-file with the name of the new converted file you want to create. This takes a few minutes, After the conversion is completed. A raw hard disk image has been created. &lt;br /&gt;
&lt;br /&gt;
To convert a raw disk image to a VirtualBox Disk Image (VDI) file use this command. &lt;br /&gt;
&lt;br /&gt;
VBoxManage convertfromraw &lt;br /&gt;
&lt;br /&gt;
The syntax is as follows: sudo VBoxManage clonehd /home/edwardss/.VirtualBox/HardDisks/XPHardDisk1.vdi /home/edwardss/.VirtualBox &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
VBoxManage convertfromraw &amp;lt;filename&amp;gt; &amp;lt;outputfile&amp;gt; [--format VDI|VMDK|VHD] [--variant Standard,Fixed,Split2G,Stream,ESX] VBoxManage convertfromraw stdin &amp;lt;outputfile&amp;gt; &amp;lt;bytes&amp;gt; [--format VDI|VMDK|VHD] [--variant Standard,Fixed,Split2G,Stream,ESX] &lt;br /&gt;
&lt;br /&gt;
where the parameters mean: format Select the disk image format to create. Default is VDI. &lt;br /&gt;
&lt;br /&gt;
variant Allow to choose a file format variant for the output file. It is a comma-separated list of variant flags. Not all combinations are supported, and specifying inconsistent flags will result in an error message. &lt;br /&gt;
&lt;br /&gt;
The second form forces VBoxManage to read the content for the disk image from standard input(useful for using that command in a pipe). &lt;br /&gt;
&lt;br /&gt;
Run VirtualBox, use the (File Menu) Virtual Media Manager and &#039;Add&#039; the newly cloned drive. This makes Virtual Box &#039;aware&#039; of the drive. Then go though the normal creation steps and choose this as the drive to use for the virtual machine. &lt;br /&gt;
&lt;br /&gt;
Downloading that vditool file is not the simplest thing in the world. If you try and open it with Firefox, for page with weird code in it will appear. To save this vditool file, right click on the link and choose to save the file. You can also tell a download manager to download this file for you. I suggest you the download manager: Aria. It is into Ubuntu repositoryes. &lt;br /&gt;
&lt;br /&gt;
Now that we’ve got vditool, we need to make it executable. Right click on the file, open its propertyes and set the “Executable” permission option. In Gnome, go into the Permission tag and activate the “Let this program be executed” or something like that option (Remember, my Ubuntu is Italian, dunno what’s your exact translation). &lt;br /&gt;
&lt;br /&gt;
At that point, we’ll need the console again, from the same dir where you’ve stored dvitool and the .bin raw file. Run this from console into the interested dir: &lt;br /&gt;
&lt;br /&gt;
LD_LIBRARY_PATH=/opt/VirtualBox* ./vditool DD new-file.vdi old-file.bin &lt;br /&gt;
&lt;br /&gt;
Where new-file.vdi is the file that will be outputted by vdi tool and must be the first to appear in the command. The second filename, old-file.bin, is the name of the raw disc image we converted the .vmdk image to. Naturally, change this invented names with real ones. &lt;br /&gt;
&lt;br /&gt;
If you wish, remember that you can run vditool for other tasks too. Now we’ll run it to optimize the filesize of the .vdi image file, for example. For a list of all commands, you’ve just got to execute vditool without any other option. &lt;br /&gt;
&lt;br /&gt;
Now we’re going to optimize the filesize of the newly converted .dvi file, let’s call it new-file.dvi and fromth console in the dir where you’ve got this file, run: &lt;br /&gt;
&lt;br /&gt;
LD_LIBRARY_PATH=/opt/VirtualBox* ./vditool SHRINK new-file.vdi &lt;br /&gt;
&lt;br /&gt;
Now we’re all setted up. Let’s run Virtual Box. At this point, you have to create a new Virtual Machine, set it up as you like and choose the new-file.dvi as disc image. If everything is okay, the machine will run, even if it will have to be settep up again a bit from inside the OS you’re using. For example, Windows has got a lot of problems in this part. &lt;br /&gt;
&lt;br /&gt;
When I started my old disc image converte into a new compressed .vdi file inside a new Virtual Machine created with VBox, WinXP refused to start. I had to insert in the CD-Rom my original WinXP Cd to boot from cd and restore the windows installation! Windows, this way, reconfigured and installed each new virtual peripheral so that at reboot everything was okay and all my programs where left installed where they were. &lt;br /&gt;
&lt;br /&gt;
Multiple vmdk files to vdi &lt;br /&gt;
&lt;br /&gt;
A lot of people have been asking me about this. I sincerely didn’t have a clue on how to convert multiple vmdk vmware virtual disc images into a vdi VB virtual disc image. Luckily, Leonardo Cosmai just provided us with a solution in one of the comments on this post! You can see that post for yourself. &lt;br /&gt;
&lt;br /&gt;
What you have to do is: &lt;br /&gt;
&lt;br /&gt;
1) Downloading and installing VMWare Server for your platform, it is freeware but proprietay software, it is opensourced but you’ll need to subscribe for a license to use it. We’ll just use this to convert multiplevmdk images into a single one. You can find VMWare Server here. &lt;br /&gt;
&lt;br /&gt;
2) Run a terminal, move in the dir where you store your multiple vmdk disc images and run: &lt;br /&gt;
&lt;br /&gt;
vmware-vdiskmanager -r source_multiples.vmdk -t 2 single_file.vmdk &lt;br /&gt;
&lt;br /&gt;
And that’s all! The multiple vmdk images will be converted into one single vmdk image file. At that point you’ll be able to normally use this guide to convert the newly obtained vmdk disc image into a single .vdi file! &lt;br /&gt;
&lt;br /&gt;
I sincerely hope this helped a lot of people out there. It is almost impossible to find a way to use vditool in Google for now. No matter how much you google, I spent the all day trying to find something. Thanks to the guys from the VBox IRC Channel for helping me out, I wasn’t going to get out from this problem alone. And a lot of people in Ubuntu Forum where in my same conditions, so…. Enjoy your migration to Virtual Box!&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=User:ABorgert&amp;diff=3514</id>
		<title>User:ABorgert</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=User:ABorgert&amp;diff=3514"/>
		<updated>2010-11-16T19:47:03Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: /* Anthony Borgert&amp;#039;s CNT 2311-91 Linux Project */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Anthony Borgert&#039;s CNT 2453-01 Project ==&lt;br /&gt;
http://cnt.lextron.net/Intro_to_IPv6&lt;br /&gt;
&lt;br /&gt;
== Anthony Borgert&#039;s CNT 2311-91 Linux Project ==&lt;br /&gt;
http://cnt.lextron.net/Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu+_and_VBoxManage&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=User:ABorgert&amp;diff=3507</id>
		<title>User:ABorgert</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=User:ABorgert&amp;diff=3507"/>
		<updated>2010-11-16T18:16:34Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: /* Anthony Borgert&amp;#039;s CNT 2311-91 Linux Project */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Anthony Borgert&#039;s CNT 2453-01 Project ==&lt;br /&gt;
http://cnt.lextron.net/Intro_to_IPv6&lt;br /&gt;
&lt;br /&gt;
== Anthony Borgert&#039;s CNT 2311-91 Linux Project ==&lt;br /&gt;
http://cnt.lextron.net/Converting_VMWare_.vmdk_To_VirtualBox_.vdi_Using_Qemu+_VdiTool&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=User:ABorgert&amp;diff=3506</id>
		<title>User:ABorgert</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=User:ABorgert&amp;diff=3506"/>
		<updated>2010-11-16T18:13:53Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: /* Anthony Borgert&amp;#039;s CNT 2311-91 Linux Project */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Anthony Borgert&#039;s CNT 2453-01 Project ==&lt;br /&gt;
http://cnt.lextron.net/Intro_to_IPv6&lt;br /&gt;
&lt;br /&gt;
== Anthony Borgert&#039;s CNT 2311-91 Linux Project ==&lt;br /&gt;
http://cnt.lextron.net/Converting Virtual Hard drives Using Qemu+ VdiTool&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=User:ABorgert&amp;diff=3504</id>
		<title>User:ABorgert</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=User:ABorgert&amp;diff=3504"/>
		<updated>2010-11-16T18:09:23Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: /* Anthony Borgert&amp;#039;s CNT 2311-91 Linux Project */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Anthony Borgert&#039;s CNT 2453-01 Project ==&lt;br /&gt;
http://cnt.lextron.net/Intro_to_IPv6&lt;br /&gt;
&lt;br /&gt;
== Anthony Borgert&#039;s CNT 2311-91 Linux Project ==&lt;br /&gt;
http://cnt.lextron.net/Converting VMWare .vmdk To VirtualBox .vdi Using Qemu + VdiTool&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=User:ABorgert&amp;diff=3503</id>
		<title>User:ABorgert</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=User:ABorgert&amp;diff=3503"/>
		<updated>2010-11-16T18:05:43Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: /* Anthony Borgert&amp;#039;s CNT 2311 Linux Project */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Anthony Borgert&#039;s CNT 2453-01 Project ==&lt;br /&gt;
http://cnt.lextron.net/Intro_to_IPv6&lt;br /&gt;
&lt;br /&gt;
== Anthony Borgert&#039;s CNT 2311-91 Linux Project ==&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=User:ABorgert&amp;diff=3502</id>
		<title>User:ABorgert</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=User:ABorgert&amp;diff=3502"/>
		<updated>2010-11-16T18:04:12Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: /* Anthony Borgert&amp;#039;s CNT-2311 Linux Project */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Anthony Borgert&#039;s CNT 2453-01 Project ==&lt;br /&gt;
http://cnt.lextron.net/Intro_to_IPv6&lt;br /&gt;
&lt;br /&gt;
== Anthony Borgert&#039;s CNT 2311 Linux Project ==&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=User:ABorgert&amp;diff=3501</id>
		<title>User:ABorgert</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=User:ABorgert&amp;diff=3501"/>
		<updated>2010-11-16T18:03:58Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: /* Anthony Borgert&amp;#039;s CNT-2311 FA 10 Linux Project */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Anthony Borgert&#039;s CNT 2453-01 Project ==&lt;br /&gt;
http://cnt.lextron.net/Intro_to_IPv6&lt;br /&gt;
&lt;br /&gt;
== Anthony Borgert&#039;s CNT-2311 Linux Project ==&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=User:ABorgert&amp;diff=3500</id>
		<title>User:ABorgert</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=User:ABorgert&amp;diff=3500"/>
		<updated>2010-11-16T18:03:32Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: /* Anthony Borgert&amp;#039;s CNT Linux Project */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Anthony Borgert&#039;s CNT 2453-01 Project ==&lt;br /&gt;
http://cnt.lextron.net/Intro_to_IPv6&lt;br /&gt;
&lt;br /&gt;
== Anthony Borgert&#039;s CNT-2311 FA 10 Linux Project ==&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=User:ABorgert&amp;diff=3499</id>
		<title>User:ABorgert</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=User:ABorgert&amp;diff=3499"/>
		<updated>2010-11-16T18:02:05Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: /* Anthony Borgert&amp;#039;s Summer Project CNT 2453-01 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Anthony Borgert&#039;s CNT 2453-01 Project ==&lt;br /&gt;
http://cnt.lextron.net/Intro_to_IPv6&lt;br /&gt;
&lt;br /&gt;
== Anthony Borgert&#039;s CNT Linux Project ==&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=User:ABorgert&amp;diff=3498</id>
		<title>User:ABorgert</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=User:ABorgert&amp;diff=3498"/>
		<updated>2010-11-16T17:59:51Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: /* Anthony Borgert&amp;#039;s Summer Project CNT 2453-01 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Anthony Borgert&#039;s Summer Project CNT 2453-01 ==&lt;br /&gt;
http://cnt.lextron.net/Intro_to_IPv6&lt;br /&gt;
&lt;br /&gt;
== Anthony Borgert&#039;s CNT Linux Project ==&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Intro_to_IPv6&amp;diff=3170</id>
		<title>Intro to IPv6</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Intro_to_IPv6&amp;diff=3170"/>
		<updated>2010-08-05T23:56:17Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;&#039;By ABorgert CNT-2453-01 Summer Class&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
This tutorial is aimed at developing a basic understanding of IPv6 for the new user. The reason IPv6 was created was because of an explosive increase in the number of devices requiring an IP address to communicate on a network and the depleting resources of IPv4 address space. Current estimates suggest that by 2011, all of the left over addresses will be used up; meaning anyone not already connected to the Internet risks being left behind. Born out of necessity IPv6 is a solution to this problem, made up of a suite of protocols and standards that where developed by the Internet Engineering Task Force (IETF). Not only does IPv6 increase address space but it also solves problems discovered with IPv4 that became evident over the years. Deploying IPv6 on a global scale is vital to the Internet industry.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===General IPv6===&lt;br /&gt;
&lt;br /&gt;
The main difference between IPv4 and IPv6 is where IPv4 addresses consist of 32 bits, IPv6 addresses consist of eight blocks of 4 hexadecimal digits each.&lt;br /&gt;
Four hexadecimal digits are equal to 16 bits, so an IPv6 address has 8*16 = 128 bits.&lt;br /&gt;
&lt;br /&gt;
*An example of an IPv6 address looks like this:  2001:4CEA:8D8C:0000:0000:0000:00D2:7A4B&lt;br /&gt;
&lt;br /&gt;
From this example it is apparent to anyone that IPv6 addresses are more complex to remember than IPv4 addresses.&lt;br /&gt;
Therefore two rules have been developed to shorten addresses to something more manageable.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Address Structure Rules&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
1. Any leading digit of Zero can be dropped from any group&lt;br /&gt;
&lt;br /&gt;
* The example above will look like this with this rule:  2001:4CEA:8D8C:0:0:0:D2:7A4B&lt;br /&gt;
&lt;br /&gt;
2. Two or more groups of zeros can be replaced by two colons, (But only once per address).&lt;br /&gt;
&lt;br /&gt;
* Then it looks like this: 2001:4CEA:8D8C::D2:7A4B&lt;br /&gt;
&lt;br /&gt;
This is much simpler :)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Types of IPv6 addresses&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There are three main types of IPv4 addresses (APIPA, Private, and Public)? The same is true for IPv6, only they have different names:&lt;br /&gt;
&lt;br /&gt;
*Global Address (GA): this is the equivalent of IPv4’s (public address). These addresses start with a first block in the 2000-3FFF range.&lt;br /&gt;
&lt;br /&gt;
*Link-Local Address (LLA): this is the equivalent of the IPv4 (APIPA address). These addresses always start with &amp;quot;fe80&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
*Unique Local Address (ULA): also known as a Site-Local address this is the equivalent of IPv4’s (private address). Where IPv4 private addresses fall within three ranges, ULA’s always start with &amp;quot;fd&amp;quot;&lt;br /&gt;
&lt;br /&gt;
There are two more that have more specific uses:&lt;br /&gt;
&lt;br /&gt;
*Multicast address: Allows communication between one host and many receivers. These packets are sent out to all the interfaces that are identified by that address. Multicast addresses always begin with &amp;quot;ff&amp;quot;&lt;br /&gt;
      &lt;br /&gt;
*Special addresses: There are two special addresses. One is called the Loopback address and it looks like this 0:0:0:0:0:0:0:1 (or ::1). It is the same as the IPv4 address 127.0.0.1 and used for the same purpose; to identify a loopback interface. The other special address is called the Unspecified address and it looks like this 0:0:0:0:0:0:0:0 (or simply written ::). It is equivalent to the IPv4 address 0.0.0.0 and is also used for the same purpose; it is commonly used as the source address that packets use to confirm if a tentative address is unique.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Some features that are available only in IPv6&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Stateless address autoconfiguration - lets hosts configure themselves automatically.&lt;br /&gt;
&lt;br /&gt;
*Multicast - allows single packets to be sent to multiple destinations.&lt;br /&gt;
&lt;br /&gt;
*Mandatory network layer security - integrated Internet Protocol Security (IPsec).&lt;br /&gt;
&lt;br /&gt;
*Simpler router processing - Routing in IPv6 is almost identical to IPv4 routing under CIDR except that the addresses are 128- bit IPv6 addresses instead of 32-bit IPv4 addresses. With very straightforward extensions, IPv4&#039;s routing algorithms (OSPF, RIP, IDRP, ISIS, etc.) can be used to route IPv6.&lt;br /&gt;
&lt;br /&gt;
*Mobility – This means that a mobile device is not constrained by location and has an “always on” IP connectivity to its home agent via a bidirectional tunnel.  In other words, if there is a network that the mobile device can connect. Then it can communicate on its own home network with its own IP address, as if it was directly connected.&lt;br /&gt;
&lt;br /&gt;
*Extension Header Mechanism - The extension header mechanism makes it easy to &#039;extend&#039; the packet header to support future services for [http://en.wikipedia.org/wiki/Quality_of_service QoS], [http://en.wikipedia.org/wiki/IPsec IPsec], [http://en.wikipedia.org/wiki/Mobile_IP Mobile IP], etc. without a redesign of the basic protocol.  Extension headers do this by carrying options that are used for special packet treatment along its route or at its destination, routing, fragmenting, and for security using the IPsec framework.&lt;br /&gt;
&lt;br /&gt;
*Jumbo Payload Option header – Also known as a [http://en.wikipedia.org/wiki/Jumbogram Jumbogram] allows an IPv6 packet to carry a payload larger than the standard mode size of one byte less than 64 Kilobytes or 65,535 (2*16 - 1) octets of payload. A jumbo payload can be almost 4GB or 4,294,967,295 (2*32 - 1) octets of payload.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IPv6 Packet Format&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The IPv6 packet has three main parts:&lt;br /&gt;
&lt;br /&gt;
*Fixed Header: The first 40 octets (320 bits) of an IPv6 data packet makes up the fixed header. The format of the fixed header is presented in the table above.&lt;br /&gt;
&lt;br /&gt;
*Extension Headers (Optional): The extension headers encode the optional Internet-layer information between the fixed header and the upper-layer protocol header in a packet. The headers form a chain, using the Next Header fields.	&lt;br /&gt;
&lt;br /&gt;
*Payload (Optional): The payload can have a size of up to 64 KB in standard mode, or with the Hop-By-Hop Options extension header it can carry the larger &amp;quot;jumbo payload&amp;quot; option.&lt;br /&gt;
&lt;br /&gt;
The fixed and optional IPv6 extension headers are followed with the upper-layer payload and the data provided by the transport layer. The Next Header field of the last IPv6 header is what indicates the type of payload that is in this packet.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:Header.jpg|frame|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*Version (4 bits):   This Indicates the IP version.&lt;br /&gt;
&lt;br /&gt;
*Traffic Class (8 bits):   The traffic class field defines the priority of the packet. There are two values held by the bits of this field. The 6 most-significant bits are used to classify packets. The two bits left are used for congestion control.&lt;br /&gt;
 &lt;br /&gt;
*Flow Label (20 bits):   The flow label identifies all packets belonging to a specific Class of Service or “flow”.  These packets can be Identified by routers and handle them all according to their class of service. &lt;br /&gt;
&lt;br /&gt;
*Payload Length (16 bits):   The payload length field shows the size of the payload.  The payload length includes the size of any extension headers.  The field length is set to zero whenever an extension header carries a Jumbo Payload option. &lt;br /&gt;
&lt;br /&gt;
*Next Header (8 bits):   The next header field shows the Transport Layer Protocol that is used by the payload. When there is extension headers in the packet, this field shows which extension header will follow.&lt;br /&gt;
&lt;br /&gt;
*Hop Limit (8 bits):   The hop limit shows the maximum number of hops allowed. This value is decreased by one at every hop in the packets route. The packet is discarded when the counter reaches 0. &lt;br /&gt;
&lt;br /&gt;
*Source Address (128 bits):  This identifies the IPv6 address of the source sending the packet. The source is also known as the “The Sending Node”.&lt;br /&gt;
&lt;br /&gt;
*Destination Address (128 bits):   This identifies IPv6 address of the destination receiving the packet or “The Destination Node”.&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Intro_to_IPv6&amp;diff=3169</id>
		<title>Intro to IPv6</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Intro_to_IPv6&amp;diff=3169"/>
		<updated>2010-08-05T23:55:33Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;-By ABorgert CNT-2453-01 Summer Class-&lt;br /&gt;
&lt;br /&gt;
This tutorial is aimed at developing a basic understanding of IPv6 for the new user. The reason IPv6 was created was because of an explosive increase in the number of devices requiring an IP address to communicate on a network and the depleting resources of IPv4 address space. Current estimates suggest that by 2011, all of the left over addresses will be used up; meaning anyone not already connected to the Internet risks being left behind. Born out of necessity IPv6 is a solution to this problem, made up of a suite of protocols and standards that where developed by the Internet Engineering Task Force (IETF). Not only does IPv6 increase address space but it also solves problems discovered with IPv4 that became evident over the years. Deploying IPv6 on a global scale is vital to the Internet industry.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===General IPv6===&lt;br /&gt;
&lt;br /&gt;
The main difference between IPv4 and IPv6 is where IPv4 addresses consist of 32 bits, IPv6 addresses consist of eight blocks of 4 hexadecimal digits each.&lt;br /&gt;
Four hexadecimal digits are equal to 16 bits, so an IPv6 address has 8*16 = 128 bits.&lt;br /&gt;
&lt;br /&gt;
*An example of an IPv6 address looks like this:  2001:4CEA:8D8C:0000:0000:0000:00D2:7A4B&lt;br /&gt;
&lt;br /&gt;
From this example it is apparent to anyone that IPv6 addresses are more complex to remember than IPv4 addresses.&lt;br /&gt;
Therefore two rules have been developed to shorten addresses to something more manageable.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Address Structure Rules&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
1. Any leading digit of Zero can be dropped from any group&lt;br /&gt;
&lt;br /&gt;
* The example above will look like this with this rule:  2001:4CEA:8D8C:0:0:0:D2:7A4B&lt;br /&gt;
&lt;br /&gt;
2. Two or more groups of zeros can be replaced by two colons, (But only once per address).&lt;br /&gt;
&lt;br /&gt;
* Then it looks like this: 2001:4CEA:8D8C::D2:7A4B&lt;br /&gt;
&lt;br /&gt;
This is much simpler :)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Types of IPv6 addresses&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There are three main types of IPv4 addresses (APIPA, Private, and Public)? The same is true for IPv6, only they have different names:&lt;br /&gt;
&lt;br /&gt;
*Global Address (GA): this is the equivalent of IPv4’s (public address). These addresses start with a first block in the 2000-3FFF range.&lt;br /&gt;
&lt;br /&gt;
*Link-Local Address (LLA): this is the equivalent of the IPv4 (APIPA address). These addresses always start with &amp;quot;fe80&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
*Unique Local Address (ULA): also known as a Site-Local address this is the equivalent of IPv4’s (private address). Where IPv4 private addresses fall within three ranges, ULA’s always start with &amp;quot;fd&amp;quot;&lt;br /&gt;
&lt;br /&gt;
There are two more that have more specific uses:&lt;br /&gt;
&lt;br /&gt;
*Multicast address: Allows communication between one host and many receivers. These packets are sent out to all the interfaces that are identified by that address. Multicast addresses always begin with &amp;quot;ff&amp;quot;&lt;br /&gt;
      &lt;br /&gt;
*Special addresses: There are two special addresses. One is called the Loopback address and it looks like this 0:0:0:0:0:0:0:1 (or ::1). It is the same as the IPv4 address 127.0.0.1 and used for the same purpose; to identify a loopback interface. The other special address is called the Unspecified address and it looks like this 0:0:0:0:0:0:0:0 (or simply written ::). It is equivalent to the IPv4 address 0.0.0.0 and is also used for the same purpose; it is commonly used as the source address that packets use to confirm if a tentative address is unique.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Some features that are available only in IPv6&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Stateless address autoconfiguration - lets hosts configure themselves automatically.&lt;br /&gt;
&lt;br /&gt;
*Multicast - allows single packets to be sent to multiple destinations.&lt;br /&gt;
&lt;br /&gt;
*Mandatory network layer security - integrated Internet Protocol Security (IPsec).&lt;br /&gt;
&lt;br /&gt;
*Simpler router processing - Routing in IPv6 is almost identical to IPv4 routing under CIDR except that the addresses are 128- bit IPv6 addresses instead of 32-bit IPv4 addresses. With very straightforward extensions, IPv4&#039;s routing algorithms (OSPF, RIP, IDRP, ISIS, etc.) can be used to route IPv6.&lt;br /&gt;
&lt;br /&gt;
*Mobility – This means that a mobile device is not constrained by location and has an “always on” IP connectivity to its home agent via a bidirectional tunnel.  In other words, if there is a network that the mobile device can connect. Then it can communicate on its own home network with its own IP address, as if it was directly connected.&lt;br /&gt;
&lt;br /&gt;
*Extension Header Mechanism - The extension header mechanism makes it easy to &#039;extend&#039; the packet header to support future services for [http://en.wikipedia.org/wiki/Quality_of_service QoS], [http://en.wikipedia.org/wiki/IPsec IPsec], [http://en.wikipedia.org/wiki/Mobile_IP Mobile IP], etc. without a redesign of the basic protocol.  Extension headers do this by carrying options that are used for special packet treatment along its route or at its destination, routing, fragmenting, and for security using the IPsec framework.&lt;br /&gt;
&lt;br /&gt;
*Jumbo Payload Option header – Also known as a [http://en.wikipedia.org/wiki/Jumbogram Jumbogram] allows an IPv6 packet to carry a payload larger than the standard mode size of one byte less than 64 Kilobytes or 65,535 (2*16 - 1) octets of payload. A jumbo payload can be almost 4GB or 4,294,967,295 (2*32 - 1) octets of payload.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IPv6 Packet Format&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The IPv6 packet has three main parts:&lt;br /&gt;
&lt;br /&gt;
*Fixed Header: The first 40 octets (320 bits) of an IPv6 data packet makes up the fixed header. The format of the fixed header is presented in the table above.&lt;br /&gt;
&lt;br /&gt;
*Extension Headers (Optional): The extension headers encode the optional Internet-layer information between the fixed header and the upper-layer protocol header in a packet. The headers form a chain, using the Next Header fields.	&lt;br /&gt;
&lt;br /&gt;
*Payload (Optional): The payload can have a size of up to 64 KB in standard mode, or with the Hop-By-Hop Options extension header it can carry the larger &amp;quot;jumbo payload&amp;quot; option.&lt;br /&gt;
&lt;br /&gt;
The fixed and optional IPv6 extension headers are followed with the upper-layer payload and the data provided by the transport layer. The Next Header field of the last IPv6 header is what indicates the type of payload that is in this packet.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:Header.jpg|frame|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*Version (4 bits):   This Indicates the IP version.&lt;br /&gt;
&lt;br /&gt;
*Traffic Class (8 bits):   The traffic class field defines the priority of the packet. There are two values held by the bits of this field. The 6 most-significant bits are used to classify packets. The two bits left are used for congestion control.&lt;br /&gt;
 &lt;br /&gt;
*Flow Label (20 bits):   The flow label identifies all packets belonging to a specific Class of Service or “flow”.  These packets can be Identified by routers and handle them all according to their class of service. &lt;br /&gt;
&lt;br /&gt;
*Payload Length (16 bits):   The payload length field shows the size of the payload.  The payload length includes the size of any extension headers.  The field length is set to zero whenever an extension header carries a Jumbo Payload option. &lt;br /&gt;
&lt;br /&gt;
*Next Header (8 bits):   The next header field shows the Transport Layer Protocol that is used by the payload. When there is extension headers in the packet, this field shows which extension header will follow.&lt;br /&gt;
&lt;br /&gt;
*Hop Limit (8 bits):   The hop limit shows the maximum number of hops allowed. This value is decreased by one at every hop in the packets route. The packet is discarded when the counter reaches 0. &lt;br /&gt;
&lt;br /&gt;
*Source Address (128 bits):  This identifies the IPv6 address of the source sending the packet. The source is also known as the “The Sending Node”.&lt;br /&gt;
&lt;br /&gt;
*Destination Address (128 bits):   This identifies IPv6 address of the destination receiving the packet or “The Destination Node”.&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Intro_to_IPv6&amp;diff=3168</id>
		<title>Intro to IPv6</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Intro_to_IPv6&amp;diff=3168"/>
		<updated>2010-08-05T23:55:00Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=By ABorgert CNT-2453-01 Summer=&lt;br /&gt;
&lt;br /&gt;
This tutorial is aimed at developing a basic understanding of IPv6 for the new user. The reason IPv6 was created was because of an explosive increase in the number of devices requiring an IP address to communicate on a network and the depleting resources of IPv4 address space. Current estimates suggest that by 2011, all of the left over addresses will be used up; meaning anyone not already connected to the Internet risks being left behind. Born out of necessity IPv6 is a solution to this problem, made up of a suite of protocols and standards that where developed by the Internet Engineering Task Force (IETF). Not only does IPv6 increase address space but it also solves problems discovered with IPv4 that became evident over the years. Deploying IPv6 on a global scale is vital to the Internet industry.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===General IPv6===&lt;br /&gt;
&lt;br /&gt;
The main difference between IPv4 and IPv6 is where IPv4 addresses consist of 32 bits, IPv6 addresses consist of eight blocks of 4 hexadecimal digits each.&lt;br /&gt;
Four hexadecimal digits are equal to 16 bits, so an IPv6 address has 8*16 = 128 bits.&lt;br /&gt;
&lt;br /&gt;
*An example of an IPv6 address looks like this:  2001:4CEA:8D8C:0000:0000:0000:00D2:7A4B&lt;br /&gt;
&lt;br /&gt;
From this example it is apparent to anyone that IPv6 addresses are more complex to remember than IPv4 addresses.&lt;br /&gt;
Therefore two rules have been developed to shorten addresses to something more manageable.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Address Structure Rules&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
1. Any leading digit of Zero can be dropped from any group&lt;br /&gt;
&lt;br /&gt;
* The example above will look like this with this rule:  2001:4CEA:8D8C:0:0:0:D2:7A4B&lt;br /&gt;
&lt;br /&gt;
2. Two or more groups of zeros can be replaced by two colons, (But only once per address).&lt;br /&gt;
&lt;br /&gt;
* Then it looks like this: 2001:4CEA:8D8C::D2:7A4B&lt;br /&gt;
&lt;br /&gt;
This is much simpler :)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Types of IPv6 addresses&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There are three main types of IPv4 addresses (APIPA, Private, and Public)? The same is true for IPv6, only they have different names:&lt;br /&gt;
&lt;br /&gt;
*Global Address (GA): this is the equivalent of IPv4’s (public address). These addresses start with a first block in the 2000-3FFF range.&lt;br /&gt;
&lt;br /&gt;
*Link-Local Address (LLA): this is the equivalent of the IPv4 (APIPA address). These addresses always start with &amp;quot;fe80&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
*Unique Local Address (ULA): also known as a Site-Local address this is the equivalent of IPv4’s (private address). Where IPv4 private addresses fall within three ranges, ULA’s always start with &amp;quot;fd&amp;quot;&lt;br /&gt;
&lt;br /&gt;
There are two more that have more specific uses:&lt;br /&gt;
&lt;br /&gt;
*Multicast address: Allows communication between one host and many receivers. These packets are sent out to all the interfaces that are identified by that address. Multicast addresses always begin with &amp;quot;ff&amp;quot;&lt;br /&gt;
      &lt;br /&gt;
*Special addresses: There are two special addresses. One is called the Loopback address and it looks like this 0:0:0:0:0:0:0:1 (or ::1). It is the same as the IPv4 address 127.0.0.1 and used for the same purpose; to identify a loopback interface. The other special address is called the Unspecified address and it looks like this 0:0:0:0:0:0:0:0 (or simply written ::). It is equivalent to the IPv4 address 0.0.0.0 and is also used for the same purpose; it is commonly used as the source address that packets use to confirm if a tentative address is unique.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Some features that are available only in IPv6&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Stateless address autoconfiguration - lets hosts configure themselves automatically.&lt;br /&gt;
&lt;br /&gt;
*Multicast - allows single packets to be sent to multiple destinations.&lt;br /&gt;
&lt;br /&gt;
*Mandatory network layer security - integrated Internet Protocol Security (IPsec).&lt;br /&gt;
&lt;br /&gt;
*Simpler router processing - Routing in IPv6 is almost identical to IPv4 routing under CIDR except that the addresses are 128- bit IPv6 addresses instead of 32-bit IPv4 addresses. With very straightforward extensions, IPv4&#039;s routing algorithms (OSPF, RIP, IDRP, ISIS, etc.) can be used to route IPv6.&lt;br /&gt;
&lt;br /&gt;
*Mobility – This means that a mobile device is not constrained by location and has an “always on” IP connectivity to its home agent via a bidirectional tunnel.  In other words, if there is a network that the mobile device can connect. Then it can communicate on its own home network with its own IP address, as if it was directly connected.&lt;br /&gt;
&lt;br /&gt;
*Extension Header Mechanism - The extension header mechanism makes it easy to &#039;extend&#039; the packet header to support future services for [http://en.wikipedia.org/wiki/Quality_of_service QoS], [http://en.wikipedia.org/wiki/IPsec IPsec], [http://en.wikipedia.org/wiki/Mobile_IP Mobile IP], etc. without a redesign of the basic protocol.  Extension headers do this by carrying options that are used for special packet treatment along its route or at its destination, routing, fragmenting, and for security using the IPsec framework.&lt;br /&gt;
&lt;br /&gt;
*Jumbo Payload Option header – Also known as a [http://en.wikipedia.org/wiki/Jumbogram Jumbogram] allows an IPv6 packet to carry a payload larger than the standard mode size of one byte less than 64 Kilobytes or 65,535 (2*16 - 1) octets of payload. A jumbo payload can be almost 4GB or 4,294,967,295 (2*32 - 1) octets of payload.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IPv6 Packet Format&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The IPv6 packet has three main parts:&lt;br /&gt;
&lt;br /&gt;
*Fixed Header: The first 40 octets (320 bits) of an IPv6 data packet makes up the fixed header. The format of the fixed header is presented in the table above.&lt;br /&gt;
&lt;br /&gt;
*Extension Headers (Optional): The extension headers encode the optional Internet-layer information between the fixed header and the upper-layer protocol header in a packet. The headers form a chain, using the Next Header fields.	&lt;br /&gt;
&lt;br /&gt;
*Payload (Optional): The payload can have a size of up to 64 KB in standard mode, or with the Hop-By-Hop Options extension header it can carry the larger &amp;quot;jumbo payload&amp;quot; option.&lt;br /&gt;
&lt;br /&gt;
The fixed and optional IPv6 extension headers are followed with the upper-layer payload and the data provided by the transport layer. The Next Header field of the last IPv6 header is what indicates the type of payload that is in this packet.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:Header.jpg|frame|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*Version (4 bits):   This Indicates the IP version.&lt;br /&gt;
&lt;br /&gt;
*Traffic Class (8 bits):   The traffic class field defines the priority of the packet. There are two values held by the bits of this field. The 6 most-significant bits are used to classify packets. The two bits left are used for congestion control.&lt;br /&gt;
 &lt;br /&gt;
*Flow Label (20 bits):   The flow label identifies all packets belonging to a specific Class of Service or “flow”.  These packets can be Identified by routers and handle them all according to their class of service. &lt;br /&gt;
&lt;br /&gt;
*Payload Length (16 bits):   The payload length field shows the size of the payload.  The payload length includes the size of any extension headers.  The field length is set to zero whenever an extension header carries a Jumbo Payload option. &lt;br /&gt;
&lt;br /&gt;
*Next Header (8 bits):   The next header field shows the Transport Layer Protocol that is used by the payload. When there is extension headers in the packet, this field shows which extension header will follow.&lt;br /&gt;
&lt;br /&gt;
*Hop Limit (8 bits):   The hop limit shows the maximum number of hops allowed. This value is decreased by one at every hop in the packets route. The packet is discarded when the counter reaches 0. &lt;br /&gt;
&lt;br /&gt;
*Source Address (128 bits):  This identifies the IPv6 address of the source sending the packet. The source is also known as the “The Sending Node”.&lt;br /&gt;
&lt;br /&gt;
*Destination Address (128 bits):   This identifies IPv6 address of the destination receiving the packet or “The Destination Node”.&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Intro_to_IPv6&amp;diff=2799</id>
		<title>Intro to IPv6</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Intro_to_IPv6&amp;diff=2799"/>
		<updated>2010-07-27T04:23:26Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This tutorial is aimed at developing a basic understanding of IPv6 for the new user. The reason IPv6 was created was because of an explosive increase in the number of devices requiring an IP address to communicate on a network and the depleting resources of IPv4 address space. Current estimates suggest that by 2011, all of the left over addresses will be used up; meaning anyone not already connected to the Internet risks being left behind. Born out of necessity IPv6 is a solution to this problem, made up of a suite of protocols and standards that where developed by the Internet Engineering Task Force (IETF). Not only does IPv6 increase address space but it also solves problems discovered with IPv4 that became evident over the years. Deploying IPv6 on a global scale is vital to the Internet industry.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===General IPv6===&lt;br /&gt;
&lt;br /&gt;
The main difference between IPv4 and IPv6 is where IPv4 addresses consist of 32 bits, IPv6 addresses consist of eight blocks of 4 hexadecimal digits each.&lt;br /&gt;
Four hexadecimal digits are equal to 16 bits, so an IPv6 address has 8*16 = 128 bits.&lt;br /&gt;
&lt;br /&gt;
*An example of an IPv6 address looks like this:  2001:4CEA:8D8C:0000:0000:0000:00D2:7A4B&lt;br /&gt;
&lt;br /&gt;
From this example it is apparent to anyone that IPv6 addresses are more complex to remember than IPv4 addresses.&lt;br /&gt;
Therefore two rules have been developed to shorten addresses to something more manageable.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Address Structure Rules&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
1. Any leading digit of Zero can be dropped from any group&lt;br /&gt;
&lt;br /&gt;
* The example above will look like this with this rule:  2001:4CEA:8D8C:0:0:0:D2:7A4B&lt;br /&gt;
&lt;br /&gt;
2. Two or more groups of zeros can be replaced by two colons, (But only once per address).&lt;br /&gt;
&lt;br /&gt;
* Then it looks like this: 2001:4CEA:8D8C::D2:7A4B&lt;br /&gt;
&lt;br /&gt;
This is much simpler :)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Types of IPv6 addresses&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There are three main types of IPv4 addresses (APIPA, Private, and Public)? The same is true for IPv6, only they have different names:&lt;br /&gt;
&lt;br /&gt;
*Global Address (GA): this is the equivalent of IPv4’s (public address). These addresses start with a first block in the 2000-3FFF range.&lt;br /&gt;
&lt;br /&gt;
*Link-Local Address (LLA): this is the equivalent of the IPv4 (APIPA address). These addresses always start with &amp;quot;fe80&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
*Unique Local Address (ULA): also known as a Site-Local address this is the equivalent of IPv4’s (private address). Where IPv4 private addresses fall within three ranges, ULA’s always start with &amp;quot;fd&amp;quot;&lt;br /&gt;
&lt;br /&gt;
There are two more that have more specific uses:&lt;br /&gt;
&lt;br /&gt;
*Multicast address: Allows communication between one host and many receivers. These packets are sent out to all the interfaces that are identified by that address. Multicast addresses always begin with &amp;quot;ff&amp;quot;&lt;br /&gt;
      &lt;br /&gt;
*Special addresses: There are two special addresses. One is called the Loopback address and it looks like this 0:0:0:0:0:0:0:1 (or ::1). It is the same as the IPv4 address 127.0.0.1 and used for the same purpose; to identify a loopback interface. The other special address is called the Unspecified address and it looks like this 0:0:0:0:0:0:0:0 (or simply written ::). It is equivalent to the IPv4 address 0.0.0.0 and is also used for the same purpose; it is commonly used as the source address that packets use to confirm if a tentative address is unique.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Some features that are available only in IPv6&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Stateless address autoconfiguration - lets hosts configure themselves automatically.&lt;br /&gt;
&lt;br /&gt;
*Multicast - allows single packets to be sent to multiple destinations.&lt;br /&gt;
&lt;br /&gt;
*Mandatory network layer security - integrated Internet Protocol Security (IPsec).&lt;br /&gt;
&lt;br /&gt;
*Simpler router processing - Routing in IPv6 is almost identical to IPv4 routing under CIDR except that the addresses are 128- bit IPv6 addresses instead of 32-bit IPv4 addresses. With very straightforward extensions, IPv4&#039;s routing algorithms (OSPF, RIP, IDRP, ISIS, etc.) can be used to route IPv6.&lt;br /&gt;
&lt;br /&gt;
*Mobility – This means that a mobile device is not constrained by location and has an “always on” IP connectivity to its home agent via a bidirectional tunnel.  In other words, if there is a network that the mobile device can connect. Then it can communicate on its own home network with its own IP address, as if it was directly connected.&lt;br /&gt;
&lt;br /&gt;
*Extension Header Mechanism - The extension header mechanism makes it easy to &#039;extend&#039; the packet header to support future services for [http://en.wikipedia.org/wiki/Quality_of_service QoS], [http://en.wikipedia.org/wiki/IPsec IPsec], [http://en.wikipedia.org/wiki/Mobile_IP Mobile IP], etc. without a redesign of the basic protocol.  Extension headers do this by carrying options that are used for special packet treatment along its route or at its destination, routing, fragmenting, and for security using the IPsec framework.&lt;br /&gt;
&lt;br /&gt;
*Jumbo Payload Option header – Also known as a [http://en.wikipedia.org/wiki/Jumbogram Jumbogram] allows an IPv6 packet to carry a payload larger than the standard mode size of one byte less than 64 Kilobytes or 65,535 (2*16 - 1) octets of payload. A jumbo payload can be almost 4GB or 4,294,967,295 (2*32 - 1) octets of payload.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IPv6 Packet Format&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The IPv6 packet has three main parts:&lt;br /&gt;
&lt;br /&gt;
*Fixed Header: The first 40 octets (320 bits) of an IPv6 data packet makes up the fixed header. The format of the fixed header is presented in the table above.&lt;br /&gt;
&lt;br /&gt;
*Extension Headers (Optional): The extension headers encode the optional Internet-layer information between the fixed header and the upper-layer protocol header in a packet. The headers form a chain, using the Next Header fields.	&lt;br /&gt;
&lt;br /&gt;
*Payload (Optional): The payload can have a size of up to 64 KB in standard mode, or with the Hop-By-Hop Options extension header it can carry the larger &amp;quot;jumbo payload&amp;quot; option.&lt;br /&gt;
&lt;br /&gt;
The fixed and optional IPv6 extension headers are followed with the upper-layer payload and the data provided by the transport layer. The Next Header field of the last IPv6 header is what indicates the type of payload that is in this packet.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:Header.jpg|frame|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*Version (4 bits):   This Indicates the IP version.&lt;br /&gt;
&lt;br /&gt;
*Traffic Class (8 bits):   The traffic class field defines the priority of the packet. There are two values held by the bits of this field. The 6 most-significant bits are used to classify packets. The two bits left are used for congestion control.&lt;br /&gt;
 &lt;br /&gt;
*Flow Label (20 bits):   The flow label identifies all packets belonging to a specific Class of Service or “flow”.  These packets can be Identified by routers and handle them all according to their class of service. &lt;br /&gt;
&lt;br /&gt;
*Payload Length (16 bits):   The payload length field shows the size of the payload.  The payload length includes the size of any extension headers.  The field length is set to zero whenever an extension header carries a Jumbo Payload option. &lt;br /&gt;
&lt;br /&gt;
*Next Header (8 bits):   The next header field shows the Transport Layer Protocol that is used by the payload. When there is extension headers in the packet, this field shows which extension header will follow.&lt;br /&gt;
&lt;br /&gt;
*Hop Limit (8 bits):   The hop limit shows the maximum number of hops allowed. This value is decreased by one at every hop in the packets route. The packet is discarded when the counter reaches 0. &lt;br /&gt;
&lt;br /&gt;
*Source Address (128 bits):  This identifies the IPv6 address of the source sending the packet. The source is also known as the “The Sending Node”.&lt;br /&gt;
&lt;br /&gt;
*Destination Address (128 bits):   This identifies IPv6 address of the destination receiving the packet or “The Destination Node”.&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Intro_to_IPv6&amp;diff=2798</id>
		<title>Intro to IPv6</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Intro_to_IPv6&amp;diff=2798"/>
		<updated>2010-07-27T04:20:09Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This tutorial is aimed at developing a basic understanding of IPv6 for the new user. The reason IPv6 was created was because of an explosive increase in the number of devices requiring an IP address to communicate on a network and the depleting resources of IPv4 address space. Current estimates suggest that by 2011, all of the left over addresses will be used up; meaning anyone not already connected to the Internet risks being left behind. Born out of necessity IPv6 is a solution to this problem, made up of a suite of protocols and standards that where developed by the Internet Engineering Task Force (IETF). Not only does IPv6 increase address space but it also solves problems discovered with IPv4 that became evident over the years. Deploying IPv6 on a global scale is vital to the Internet industry.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===General IPv6===&lt;br /&gt;
&lt;br /&gt;
The main difference between IPv4 and IPv6 is where IPv4 addresses consist of 32 bits, IPv6 addresses consist of eight blocks of 4 hexadecimal digits each.&lt;br /&gt;
Four hexadecimal digits are equal to 16 bits, so an IPv6 address has 8*16 = 128 bits.&lt;br /&gt;
&lt;br /&gt;
*An example of an IPv6 address looks like this:  2001:4CEA:8D8C:0000:0000:0000:00D2:7A4B&lt;br /&gt;
&lt;br /&gt;
From this example it is apparent to anyone that IPv6 addresses are more complex to remember than IPv4 addresses.&lt;br /&gt;
Therefore two rules have been developed to shorten addresses to something more manageable.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Address Structure Rules&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
1. Any leading digit of Zero can be dropped from any group&lt;br /&gt;
&lt;br /&gt;
* The example above will look like this with this rule:  2001:4CEA:8D8C:0:0:0:D2:7A4B&lt;br /&gt;
&lt;br /&gt;
2. Two or more groups of zeros can be replaced by two colons, (But only once per address).&lt;br /&gt;
&lt;br /&gt;
* Then it looks like this: 2001:4CEA:8D8C::D2:7A4B&lt;br /&gt;
&lt;br /&gt;
This is much simpler :)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Types of IPv6 addresses&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There are three main types of IPv4 addresses (APIPA, Private, and Public)? The same is true for IPv6, only they have different names:&lt;br /&gt;
&lt;br /&gt;
*Global Address (GA): this is the equivalent of IPv4’s (public address). These addresses start with a first block in the 2000-3FFF range.&lt;br /&gt;
&lt;br /&gt;
*Link-Local Address (LLA): this is the equivalent of the IPv4 (APIPA address). These addresses always start with &amp;quot;fe80&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
*Unique Local Address (ULA): also known as a Site-Local address this is the equivalent of IPv4’s (private address). Where IPv4 private addresses fall within three ranges, ULA’s always start with &amp;quot;fd&amp;quot;&lt;br /&gt;
&lt;br /&gt;
There are two more that have more specific uses:&lt;br /&gt;
&lt;br /&gt;
*Multicast address: Allows communication between one host and many receivers. These packets are sent out to all the interfaces that are identified by that address. Multicast addresses always begin with &amp;quot;ff&amp;quot;&lt;br /&gt;
      &lt;br /&gt;
*Special addresses: There are two special addresses. One is called the Loopback address and it looks like this 0:0:0:0:0:0:0:1 (or ::1). It is the same as the IPv4 address 127.0.0.1 and used for the same purpose; to identify a loopback interface. The other special address is called the Unspecified address and it looks like this 0:0:0:0:0:0:0:0 (or simply written ::). It is equivalent to the IPv4 address 0.0.0.0 and is also used for the same purpose; it is commonly used as the source address that packets use to confirm if a tentative address is unique.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Some features that are available only in IPv6&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Stateless address autoconfiguration - lets hosts configure themselves automatically.&lt;br /&gt;
&lt;br /&gt;
*Multicast - allows single packets to be sent to multiple destinations.&lt;br /&gt;
&lt;br /&gt;
*Mandatory network layer security - integrated Internet Protocol Security (IPsec).&lt;br /&gt;
&lt;br /&gt;
*Simpler router processing - Routing in IPv6 is almost identical to IPv4 routing under CIDR except that the addresses are 128- bit IPv6 addresses instead of 32-bit IPv4 addresses. With very straightforward extensions, IPv4&#039;s routing algorithms (OSPF, RIP, IDRP, ISIS, etc.) can be used to route IPv6.&lt;br /&gt;
&lt;br /&gt;
*Mobility – This means that a mobile device is not constrained by location and has an “always on” IP connectivity to its home agent via a bidirectional tunnel.  In other words, if there is a network that the mobile device can connect. Then it can communicate on its own home network with its own IP address, as if it was directly connected.&lt;br /&gt;
&lt;br /&gt;
*Extension Header Mechanism - The extension header mechanism makes it easy to &#039;extend&#039; the packet header to support future services for [http://en.wikipedia.org/wiki/Quality_of_service QoS], [http://en.wikipedia.org/wiki/IPsec IPsec], [http://en.wikipedia.org/wiki/Mobile_IP Mobile IP], etc. without a redesign of the basic protocol.  Extension headers do this by carrying options that are used for special packet treatment along its route or at its destination, routing, fragmenting, and for security using the IPsec framework.&lt;br /&gt;
&lt;br /&gt;
*Jumbo Payload Option header – Also known as a [http://en.wikipedia.org/wiki/Jumbogram Jumbogram] allows an IPv6 packet to carry a payload larger than the standard mode size of one byte less than 64 Kilobytes or 65,535 (2*16 - 1) octets of payload. A jumbo payload can be almost 4GB or 4,294,967,295 (2*32 - 1) octets of payload.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IPv6 Packet Format&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The IPv6 packet has three main parts:&lt;br /&gt;
&lt;br /&gt;
*Fixed Header: The first 40 octets (320 bits) of an IPv6 data packet makes up the fixed header. The format of the fixed header is presented in the table above.&lt;br /&gt;
&lt;br /&gt;
*Extension Headers (Optional): The extension headers encode the optional Internet-layer information between the fixed header and the upper-layer protocol header in a packet. The headers form a chain, using the Next Header fields.	&lt;br /&gt;
&lt;br /&gt;
*Payload (Optional): The payload can have a size of up to 64 KB in standard mode, or with the Hop-By-Hop Options extension header it can carry the larger &amp;quot;jumbo payload&amp;quot; option.&lt;br /&gt;
&lt;br /&gt;
The fixed and optional IPv6 extension headers are followed with the upper-layer payload and the data provided by the transport layer. The Next Header field of the last IPv6 header shows what type of payload is in this packet.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:Header.jpg|frame|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*Version (4 bits):   This Indicates the IP version.&lt;br /&gt;
&lt;br /&gt;
*Traffic Class (8 bits):   The traffic class field defines the priority of the packet. There are two values held by the bits of this field. The 6 most-significant bits are used to classify packets. The two bits left are used for congestion control.&lt;br /&gt;
 &lt;br /&gt;
*Flow Label (20 bits):   The flow label identifies all packets belonging to a specific Class of Service or “flow”.  These packets can be Identified by routers and handle them all according to their class of service. &lt;br /&gt;
&lt;br /&gt;
*Payload Length (16 bits):   The payload length field shows the size of the payload.  The payload length includes the size of any extension headers.  The field length is set to zero whenever an extension header carries a Jumbo Payload option. &lt;br /&gt;
&lt;br /&gt;
*Next Header (8 bits):   The next header field shows the Transport Layer Protocol that is used by the payload. When there is extension headers in the packet, this field shows which extension header will follow.&lt;br /&gt;
&lt;br /&gt;
*Hop Limit (8 bits):   The hop limit shows the maximum number of hops allowed. This value is decreased by one at every hop in the packets route. The packet is discarded when the counter reaches 0. &lt;br /&gt;
&lt;br /&gt;
*Source Address (128 bits):  This identifies the IPv6 address of the source sending the packet. The source is also known as the “The Sending Node”.&lt;br /&gt;
&lt;br /&gt;
*Destination Address (128 bits):   This identifies IPv6 address of the destination receiving the packet or “The Destination Node”.&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Intro_to_IPv6&amp;diff=2797</id>
		<title>Intro to IPv6</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Intro_to_IPv6&amp;diff=2797"/>
		<updated>2010-07-27T04:15:00Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This tutorial is aimed at developing a basic understanding of IPv6 for the new user. The reason IPv6 was created was because of an explosive increase in the number of devices requiring an IP address to communicate on a network and the depleting resources of IPv4 address space. Current estimates suggest that by 2011, all of the left over addresses will be used up; meaning anyone not already connected to the Internet risks being left behind. Born out of necessity IPv6 is a solution to this problem, made up of a suite of protocols and standards that where developed by the Internet Engineering Task Force (IETF). Not only does IPv6 increase address space but it also solves problems discovered with IPv4 that became evident over the years. Deploying IPv6 on a global scale is vital to the Internet industry.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===General IPv6===&lt;br /&gt;
&lt;br /&gt;
The main difference between IPv4 and IPv6 is where IPv4 addresses consist of 32 bits, IPv6 addresses consist of eight blocks of 4 hexadecimal digits each.&lt;br /&gt;
Four hexadecimal digits are equal to 16 bits, so an IPv6 address has 8*16 = 128 bits.&lt;br /&gt;
&lt;br /&gt;
*An example of an IPv6 address looks like this:  2001:4CEA:8D8C:0000:0000:0000:00D2:7A4B&lt;br /&gt;
&lt;br /&gt;
From this example it is apparent to anyone that IPv6 addresses are more complex to remember than IPv4 addresses.&lt;br /&gt;
Therefore two rules have been developed to shorten addresses to something more manageable.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Address Structure Rules&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
1. Any leading digit of Zero can be dropped from any group&lt;br /&gt;
&lt;br /&gt;
* The example above will look like this with this rule:  2001:4CEA:8D8C:0:0:0:D2:7A4B&lt;br /&gt;
&lt;br /&gt;
2. Two or more groups of zeros can be replaced by two colons, (But only once per address).&lt;br /&gt;
&lt;br /&gt;
* Then it looks like this: 2001:4CEA:8D8C::D2:7A4B&lt;br /&gt;
&lt;br /&gt;
This is much simpler :)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Types of IPv6 addresses&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There are three main types of IPv4 addresses (APIPA, Private, and Public)? The same is true for IPv6, only they have different names:&lt;br /&gt;
&lt;br /&gt;
*Global Address (GA): this is the equivalent of IPv4’s (public address). These addresses start with a first block in the 2000-3FFF range.&lt;br /&gt;
&lt;br /&gt;
*Link-Local Address (LLA): this is the equivalent of the IPv4 (APIPA address). These addresses always start with &amp;quot;fe80&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
*Unique Local Address (ULA): also known as a Site-Local address this is the equivalent of IPv4’s (private address). Where IPv4 private addresses fall within three ranges, ULA’s always start with &amp;quot;fd&amp;quot;&lt;br /&gt;
&lt;br /&gt;
There are two more that have more specific uses:&lt;br /&gt;
&lt;br /&gt;
*Multicast address: Allows communication between one host and many receivers. These packets are sent out to all the interfaces that are identified by that address. Multicast addresses always begin with &amp;quot;ff&amp;quot;&lt;br /&gt;
      &lt;br /&gt;
*Special addresses: There are two special addresses. One is called the Loopback address and it looks like this 0:0:0:0:0:0:0:1 (or ::1). It is the same as the IPv4 address 127.0.0.1 and used for the same purpose; to identify a loopback interface. The other special address is called the Unspecified address and it looks like this 0:0:0:0:0:0:0:0 (or simply written ::). It is equivalent to the IPv4 address 0.0.0.0 and is also used for the same purpose; it is commonly used as the source address that packets use to confirm if a tentative address is unique.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Some features that are available only in IPv6&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Stateless address autoconfiguration - lets hosts configure themselves automatically.&lt;br /&gt;
&lt;br /&gt;
*Multicast - allows single packets to be sent to multiple destinations.&lt;br /&gt;
&lt;br /&gt;
*Mandatory network layer security - integrated Internet Protocol Security (IPsec).&lt;br /&gt;
&lt;br /&gt;
*Simpler router processing - Routing in IPv6 is almost identical to IPv4 routing under CIDR except that the addresses are 128- bit IPv6 addresses instead of 32-bit IPv4 addresses. With very straightforward extensions, IPv4&#039;s routing algorithms (OSPF, RIP, IDRP, ISIS, etc.) can be used to route IPv6.&lt;br /&gt;
&lt;br /&gt;
*Mobility – This means that a mobile device is not constrained by location and has an “always on” IP connectivity to its home agent via a bidirectional tunnel.  In other words, if there is a network that the mobile device can connect. Then it can communicate on its own home network with its own IP address, as if it was directly connected.&lt;br /&gt;
&lt;br /&gt;
*Extension Header Mechanism - The extension header mechanism makes it easy to &#039;extend&#039; the packet header to support future services for [http://en.wikipedia.org/wiki/Quality_of_service QoS], [http://en.wikipedia.org/wiki/IPsec IPsec], [http://en.wikipedia.org/wiki/Mobile_IP Mobile IP], etc. without a redesign of the basic protocol.  Extension headers do this by carrying options that are used for special packet treatment along its route or at its destination, routing, fragmenting, and for security using the IPsec framework.&lt;br /&gt;
&lt;br /&gt;
*Jumbo Payload Option header – Also known as a [http://en.wikipedia.org/wiki/Jumbogram Jumbogram] allows an IPv6 packet to carry a payload larger than the standard mode size of one byte less than 64 Kilobytes or 65,535 (2*16 - 1) octets of payload. A jumbo payload can be almost 4GB or 4,294,967,295 (2*32 - 1) octets of payload.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IPv6 Packet Format&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The IPv6 packet has three main parts:&lt;br /&gt;
&lt;br /&gt;
*Fixed Header: The first 40 octets (320 bits) of an IPv6 data packet makes up the fixed header. The format of the fixed header is presented in the table above.&lt;br /&gt;
&lt;br /&gt;
*Extension Headers (Optional): The extension headers encode the optional Internet-layer information between the fixed header and the upper-layer protocol header in a packet. The headers form a chain, using the Next Header fields.	&lt;br /&gt;
&lt;br /&gt;
*Payload (Optional): The payload can have a size of up to 64 KB in standard mode, or with the Hop-By-Hop Options extension header it can carry the larger &amp;quot;jumbo payload&amp;quot; option.&lt;br /&gt;
&lt;br /&gt;
The fixed and optional IPv6 extension headers are followed with the upper-layer payload, the data provided by the transport layer, for example a TCP segment or a UDP datagram. The Next Header field of the last IPv6 header indicates what type of payload is contained in this packet.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:Header.jpg|frame|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*Version (4 bits):   This Indicates the IP version.&lt;br /&gt;
&lt;br /&gt;
*Traffic Class (8 bits):   The traffic class field defines the priority of the packet. There are two values held by the bits of this field. The 6 most-significant bits are used to classify packets. The two bits left are used for congestion control.&lt;br /&gt;
 &lt;br /&gt;
*Flow Label (20 bits):   The flow label identifies all packets belonging to a specific Class of Service or “flow”.  These packets can be Identified by routers and handle them all according to their class of service. &lt;br /&gt;
&lt;br /&gt;
*Payload Length (16 bits):   The payload length field shows the size of the payload.  The payload length includes the size of any extension headers.  The field length is set to zero whenever an extension header carries a Jumbo Payload option. &lt;br /&gt;
&lt;br /&gt;
*Next Header (8 bits):   The next header field shows the Transport Layer Protocol that is used by the payload. When there is extension headers in the packet, this field shows which extension header will follow.&lt;br /&gt;
&lt;br /&gt;
*Hop Limit (8 bits):   The hop limit shows the maximum number of hops allowed. This value is decreased by one at every hop in the packets route. The packet is discarded when the counter reaches 0. &lt;br /&gt;
&lt;br /&gt;
*Source Address (128 bits):  This identifies the IPv6 address of the source sending the packet. The source is also known as the “The Sending Node”.&lt;br /&gt;
&lt;br /&gt;
*Destination Address (128 bits):   This identifies IPv6 address of the destination receiving the packet or “The Destination Node”.&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Intro_to_IPv6&amp;diff=2796</id>
		<title>Intro to IPv6</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Intro_to_IPv6&amp;diff=2796"/>
		<updated>2010-07-27T03:58:05Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This tutorial is aimed at developing a basic understanding of IPv6 for the new user. The reason IPv6 was created was because of an explosive increase in the number of devices requiring an IP address to communicate on a network and the depleting resources of IPv4 address space. Current estimates suggest that by 2011, all of the left over addresses will be used up; meaning anyone not already connected to the Internet risks being left behind. Born out of necessity IPv6 is a solution to this problem, made up of a suite of protocols and standards that where developed by the Internet Engineering Task Force (IETF). Not only does IPv6 increase address space but it also solves problems discovered with IPv4 that became evident over the years. Deploying IPv6 on a global scale is vital to the Internet industry.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===General IPv6===&lt;br /&gt;
&lt;br /&gt;
The main difference between IPv4 and IPv6 is where IPv4 addresses consist of 32 bits, IPv6 addresses consist of eight blocks of 4 hexadecimal digits each.&lt;br /&gt;
Four hexadecimal digits are equal to 16 bits, so an IPv6 address has 8*16 = 128 bits.&lt;br /&gt;
&lt;br /&gt;
*An example of an IPv6 address looks like this:  2001:4CEA:8D8C:0000:0000:0000:00D2:7A4B&lt;br /&gt;
&lt;br /&gt;
From this example it is apparent to anyone that IPv6 addresses are more complex to remember than IPv4 addresses.&lt;br /&gt;
Therefore two rules have been developed to shorten addresses to something more manageable.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Address Structure Rules&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
1. Any leading digit of Zero can be dropped from any group&lt;br /&gt;
&lt;br /&gt;
* The example above will look like this with this rule:  2001:4CEA:8D8C:0:0:0:D2:7A4B&lt;br /&gt;
&lt;br /&gt;
2. Two or more groups of zeros can be replaced by two colons, (But only once per address).&lt;br /&gt;
&lt;br /&gt;
* Then it looks like this: 2001:4CEA:8D8C::D2:7A4B&lt;br /&gt;
&lt;br /&gt;
This is much simpler :)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Types of IPv6 addresses&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There are three main types of IPv4 addresses (APIPA, Private, and Public)? The same is true for IPv6, only they have different names:&lt;br /&gt;
&lt;br /&gt;
*Global Address (GA): this is the equivalent of IPv4’s (public address). These addresses start with a first block in the 2000-3FFF range.&lt;br /&gt;
&lt;br /&gt;
*Link-Local Address (LLA): this is the equivalent of the IPv4 (APIPA address). These addresses always start with &amp;quot;fe80&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
*Unique Local Address (ULA): also known as a Site-Local address this is the equivalent of IPv4’s (private address). Where IPv4 private addresses fall within three ranges, ULA’s always start with &amp;quot;fd&amp;quot;&lt;br /&gt;
&lt;br /&gt;
There are two more that have more specific uses:&lt;br /&gt;
&lt;br /&gt;
*Multicast address: Allows communication between one host and many receivers. These packets are sent out to all the interfaces that are identified by that address. Multicast addresses always begin with &amp;quot;ff&amp;quot;&lt;br /&gt;
      &lt;br /&gt;
*Special addresses: There are two special addresses. One is called the Loopback address and it looks like this 0:0:0:0:0:0:0:1 (or ::1). It is the same as the IPv4 address 127.0.0.1 and used for the same purpose; to identify a loopback interface. The other special address is called the Unspecified address and it looks like this 0:0:0:0:0:0:0:0 (or simply written ::). It is equivalent to the IPv4 address 0.0.0.0 and is also used for the same purpose; it is commonly used as the source address that packets use to confirm if a tentative address is unique.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Some features that are available only in IPv6&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Stateless address autoconfiguration - lets hosts configure themselves automatically.&lt;br /&gt;
&lt;br /&gt;
*Multicast - allows single packets to be sent to multiple destinations.&lt;br /&gt;
&lt;br /&gt;
*Mandatory network layer security - integrated Internet Protocol Security (IPsec).&lt;br /&gt;
&lt;br /&gt;
*Simpler router processing - Routing in IPv6 is almost identical to IPv4 routing under CIDR except that the addresses are 128- bit IPv6 addresses instead of 32-bit IPv4 addresses. With very straightforward extensions, IPv4&#039;s routing algorithms (OSPF, RIP, IDRP, ISIS, etc.) can be used to route IPv6.&lt;br /&gt;
&lt;br /&gt;
*Mobility – This means that a mobile device is not constrained by location and has an “always on” IP connectivity to its home agent via a bidirectional tunnel.  In other words, if there is a network that the mobile device can connect. Then it can communicate on its own home network with its own IP address, as if it was directly connected.&lt;br /&gt;
&lt;br /&gt;
*Extension Header Mechanism - The extension header mechanism makes it easy to &#039;extend&#039; the packet header to support future services for [http://en.wikipedia.org/wiki/Quality_of_service QoS], [http://en.wikipedia.org/wiki/IPsec IPsec], [http://en.wikipedia.org/wiki/Mobile_IP Mobile IP], etc. without a redesign of the basic protocol.  Extension headers do this by carrying options that are used for special packet treatment along its route or at its destination, routing, fragmenting, and for security using the IPsec framework.&lt;br /&gt;
&lt;br /&gt;
*Jumbo Payload Option header – Also known as a [http://en.wikipedia.org/wiki/Jumbogram Jumbogram] allows an IPv6 packet to carry a payload larger than the standard mode size of one byte less than 64 Kilobytes or 65,535 (2*16 - 1) octets of payload. A jumbo payload can be almost 4GB or 4,294,967,295 (2*32 - 1) octets of payload.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IPv6 Packet Format&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The IPv6 packet has three main parts:&lt;br /&gt;
&lt;br /&gt;
*Fixed Header: The first 40 octets (320 bits) of an IPv6 data packet makes up the fixed header. The format of the fixed header is presented in the table above.&lt;br /&gt;
&lt;br /&gt;
*Extension Headers (Optional): The extension headers encode the optional Internet-layer information between the fixed header and the upper-layer protocol header in a packet. The headers form a chain, using the Next Header fields.	&lt;br /&gt;
&lt;br /&gt;
*Payload (Optional): The fixed and optional IPv6 extension headers are followed with the upper-layer payload, the data provided by the transport layer, for example a TCP segment or a UDP datagram. The Next Header field of the last IPv6 header indicates what type of payload is contained in this packet.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:Header.jpg|frame|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*Version (4 bits):   This Indicates the IP version.&lt;br /&gt;
&lt;br /&gt;
*Traffic Class (8 bits):   The traffic class field defines the priority of the packet. There are two values held by the bits of this field. The 6 most-significant bits are used to classify packets. The two bits left are used for congestion control.&lt;br /&gt;
 &lt;br /&gt;
*Flow Label (20 bits):   The flow label identifies all packets belonging to a specific Class of Service or “flow”.  These packets can be Identified by routers and handle them all according to their class of service. &lt;br /&gt;
&lt;br /&gt;
*Payload Length (16 bits):   The payload length field shows the size of the payload.  The payload length includes the size of any extension headers.  The field length is set to zero whenever an extension header carries a Jumbo Payload option. &lt;br /&gt;
&lt;br /&gt;
*Next Header (8 bits):   The next header field shows the Transport Layer Protocol that is used by the payload. When there is extension headers in the packet, this field shows which extension header will follow.&lt;br /&gt;
&lt;br /&gt;
*Hop Limit (8 bits):   The hop limit shows the maximum number of hops allowed. This value is decreased by one at every hop in the packets route. The packet is discarded when the counter reaches 0. &lt;br /&gt;
&lt;br /&gt;
*Source Address (128 bits):  This identifies the IPv6 address of the source sending the packet. The source is also known as the “The Sending Node”.&lt;br /&gt;
&lt;br /&gt;
*Destination Address (128 bits):   This identifies IPv6 address of the destination receiving the packet or “The Destination Node”.&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Intro_to_IPv6&amp;diff=2795</id>
		<title>Intro to IPv6</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Intro_to_IPv6&amp;diff=2795"/>
		<updated>2010-07-27T03:55:39Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This tutorial is aimed at developing a basic understanding of IPv6 for the new user. The reason IPv6 was created was because of an explosive increase in the number of devices requiring an IP address to communicate on a network and the depleting resources of IPv4 address space. Current estimates suggest that by 2011, all of the left over addresses will be used up; meaning anyone not already connected to the Internet risks being left behind. Born out of necessity IPv6 is a solution to this problem, made up of a suite of protocols and standards that where developed by the Internet Engineering Task Force (IETF). Not only does IPv6 increase address space but it also solves problems discovered with IPv4 that became evident over the years. Deploying IPv6 on a global scale is vital to the Internet industry.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===General IPv6===&lt;br /&gt;
&lt;br /&gt;
The main difference between IPv4 and IPv6 is where IPv4 addresses consist of 32 bits, IPv6 addresses consist of eight blocks of 4 hexadecimal digits each.&lt;br /&gt;
Four hexadecimal digits are equal to 16 bits, so an IPv6 address has 8*16 = 128 bits.&lt;br /&gt;
&lt;br /&gt;
*An example of an IPv6 address looks like this:  2001:4CEA:8D8C:0000:0000:0000:00D2:7A4B&lt;br /&gt;
&lt;br /&gt;
From this example it is apparent to anyone that IPv6 addresses are more complex to remember than IPv4 addresses.&lt;br /&gt;
Therefore two rules have been developed to shorten addresses to something more manageable.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Address Structure Rules&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
1. Any leading digit of Zero can be dropped from any group&lt;br /&gt;
&lt;br /&gt;
* The example above will look like this with this rule:  2001:4CEA:8D8C:0:0:0:D2:7A4B&lt;br /&gt;
&lt;br /&gt;
2. Two or more groups of zeros can be replaced by two colons, (But only once per address).&lt;br /&gt;
&lt;br /&gt;
* Then it looks like this: 2001:4CEA:8D8C::D2:7A4B&lt;br /&gt;
&lt;br /&gt;
This is much simpler :)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Types of IPv6 addresses&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There are three main types of IPv4 addresses (APIPA, Private, and Public)? The same is true for IPv6, only they have different names:&lt;br /&gt;
&lt;br /&gt;
*Global Address (GA): this is the equivalent of IPv4’s (public address). These addresses start with a first block in the 2000-3FFF range.&lt;br /&gt;
&lt;br /&gt;
*Link-Local Address (LLA): this is the equivalent of the IPv4 (APIPA address). These addresses always start with &amp;quot;fe80&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
*Unique Local Address (ULA): also known as a Site-Local address this is the equivalent of IPv4’s (private address). Where IPv4 private addresses fall within three ranges, ULA’s always start with &amp;quot;fd&amp;quot;&lt;br /&gt;
&lt;br /&gt;
There are two more that have more specific uses:&lt;br /&gt;
&lt;br /&gt;
*Multicast address: Allows communication between one host and many receivers. These packets are sent out to all the interfaces that are identified by that address. Multicast addresses always begin with &amp;quot;ff&amp;quot;&lt;br /&gt;
      &lt;br /&gt;
*Special addresses: There are two special addresses. One is called the Loopback address and it looks like this 0:0:0:0:0:0:0:1 (or ::1). It is the same as the IPv4 address 127.0.0.1 and used for the same purpose; to identify a loopback interface. The other special address is called the Unspecified address and it looks like this 0:0:0:0:0:0:0:0 (or simply written ::). It is equivalent to the IPv4 address 0.0.0.0 and is also used for the same purpose; it is commonly used as the source address that packets use to confirm if a tentative address is unique.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Some features that are available only in IPv6&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Stateless address autoconfiguration - lets hosts configure themselves automatically.&lt;br /&gt;
&lt;br /&gt;
*Multicast - allows single packets to be sent to multiple destinations.&lt;br /&gt;
&lt;br /&gt;
*Mandatory network layer security - integrated Internet Protocol Security (IPsec).&lt;br /&gt;
&lt;br /&gt;
*Simpler router processing - Routing in IPv6 is almost identical to IPv4 routing under CIDR except that the addresses are 128- bit IPv6 addresses instead of 32-bit IPv4 addresses. With very straightforward extensions, IPv4&#039;s routing algorithms (OSPF, RIP, IDRP, ISIS, etc.) can be used to route IPv6.&lt;br /&gt;
&lt;br /&gt;
*Mobility – This means that a mobile device is not constrained by location and has an “always on” IP connectivity to its home agent via a bidirectional tunnel.  In other words, if there is a network that the mobile device can connect. Then it can communicate on its own home network with its own IP address, as if it was directly connected.&lt;br /&gt;
&lt;br /&gt;
*Extension Header Mechanism - The extension header mechanism makes it easy to &#039;extend&#039; the packet header to support future services for [http://en.wikipedia.org/wiki/Quality_of_service QoS], [http://en.wikipedia.org/wiki/IPsec IPsec], [http://en.wikipedia.org/wiki/Mobile_IP Mobile IP], etc. without a redesign of the basic protocol.  Extension headers do this by carrying options that are used for special packet treatment along its route or at its destination, routing, fragmenting, and for security using the IPsec framework.&lt;br /&gt;
&lt;br /&gt;
*Jumbo Payload Option header – Also known as a [http://en.wikipedia.org/wiki/Jumbogram Jumbogram] allows an IPv6 packet to carry a payload larger than the standard mode size of one byte less than 64 Kilobytes or 65,535 (2*16 - 1) octets of payload. A jumbo payload can be almost 4GB or 4,294,967,295 (2*32 - 1) octets of payload.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IPv6 Packet Format&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The IPv6 packet has three main parts:&lt;br /&gt;
&lt;br /&gt;
*Fixed Header: The first 40 octets (320 bits) of an IPv6 data packet makes up the fixed header. The format of the fixed header is presented in the table above.&lt;br /&gt;
&lt;br /&gt;
*Extension Headers (Optional): The extension headers encode the optional Internet-layer information between the fixed header and the upper-layer protocol header in a packet. The headers form a chain, using the Next Header fields.	&lt;br /&gt;
&lt;br /&gt;
*Payload Extension Headers (Optional): The fixed and optional IPv6 extension headers are followed with the upper-layer payload, the data provided by the transport layer, for example a TCP segment or a UDP datagram. The Next Header field of the last IPv6 header indicates what type of payload is contained in this packet.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:Header.jpg|frame|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*Version (4 bits):   This Indicates the IP version.&lt;br /&gt;
&lt;br /&gt;
*Traffic Class (8 bits):   The traffic class field defines the priority of the packet. There are two values held by the bits of this field. The 6 most-significant bits are used to classify packets. The two bits left are used for congestion control.&lt;br /&gt;
 &lt;br /&gt;
*Flow Label (20 bits):   The flow label identifies all packets belonging to a specific Class of Service or “flow”.  These packets can be Identified by routers and handle them all according to their class of service. &lt;br /&gt;
&lt;br /&gt;
*Payload Length (16 bits):   The payload length field shows the size of the payload.  The payload length includes the size of any extension headers.  The field length is set to zero whenever an extension header carries a Jumbo Payload option. &lt;br /&gt;
&lt;br /&gt;
*Next Header (8 bits):   The next header field shows the Transport Layer Protocol that is used by the payload. When there is extension headers in the packet, this field shows which extension header will follow.&lt;br /&gt;
&lt;br /&gt;
*Hop Limit (8 bits):   The hop limit shows the maximum number of hops allowed. This value is decreased by one at every hop in the packets route. The packet is discarded when the counter reaches 0. &lt;br /&gt;
&lt;br /&gt;
*Source Address (128 bits):  This identifies the IPv6 address of the source sending the packet. The source is also known as the “The Sending Node”.&lt;br /&gt;
&lt;br /&gt;
*Destination Address (128 bits):   This identifies IPv6 address of the destination receiving the packet or “The Destination Node”.&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
	<entry>
		<id>https://wiki.ihitc.net/mediawiki/index.php?title=Intro_to_IPv6&amp;diff=2760</id>
		<title>Intro to IPv6</title>
		<link rel="alternate" type="text/html" href="https://wiki.ihitc.net/mediawiki/index.php?title=Intro_to_IPv6&amp;diff=2760"/>
		<updated>2010-07-27T02:13:06Z</updated>

		<summary type="html">&lt;p&gt;ABorgert: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This tutorial is aimed at developing a basic understanding of IPv6 for the new user. The reason IPv6 was created was because of an explosive increase in the number of devices requiring an IP address to communicate on a network and the depleting resources of IPv4 address space. Current estimates suggest that by 2011, all of the left over addresses will be used up; meaning anyone not already connected to the Internet risks being left behind. Born out of necessity IPv6 is a solution to this problem, made up of a suite of protocols and standards that where developed by the Internet Engineering Task Force (IETF). Not only does IPv6 increase address space but it also solves problems discovered with IPv4 that became evident over the years. Deploying IPv6 on a global scale is vital to the Internet industry.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===General IPv6===&lt;br /&gt;
&lt;br /&gt;
The main difference between IPv4 and IPv6 is where IPv4 addresses consist of 32 bits, IPv6 addresses consist of eight blocks of 4 hexadecimal digits each.&lt;br /&gt;
Four hexadecimal digits are equal to 16 bits, so an IPv6 address has 8*16 = 128 bits.&lt;br /&gt;
&lt;br /&gt;
*An example of an IPv6 address looks like this:  2001:4CEA:8D8C:0000:0000:0000:00D2:7A4B&lt;br /&gt;
&lt;br /&gt;
From this example it is apparent to anyone that IPv6 addresses are more complex to remember than IPv4 addresses.&lt;br /&gt;
Therefore two rules have been developed to shorten addresses to something more manageable.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Address Structure Rules&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
1. Any leading digit of Zero can be dropped from any group&lt;br /&gt;
&lt;br /&gt;
* The example above will look like this with this rule:  2001:4CEA:8D8C:0:0:0:D2:7A4B&lt;br /&gt;
&lt;br /&gt;
2. Two or more groups of zeros can be replaced by two colons, (But only once per address).&lt;br /&gt;
&lt;br /&gt;
* Then it looks like this: 2001:4CEA:8D8C::D2:7A4B&lt;br /&gt;
&lt;br /&gt;
This is much simpler :)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Types of IPv6 addresses&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There are three main types of IPv4 addresses (APIPA, Private, and Public)? The same is true for IPv6, only they have different names:&lt;br /&gt;
&lt;br /&gt;
*Global Address (GA): this is the equivalent of IPv4’s (public address). These addresses start with a first block in the 2000-3FFF range.&lt;br /&gt;
&lt;br /&gt;
*Link-Local Address (LLA): this is the equivalent of the IPv4 (APIPA address). These addresses always start with &amp;quot;fe80&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
*Unique Local Address (ULA): also known as a Site-Local address this is the equivalent of IPv4’s (private address). Where IPv4 private addresses fall within three ranges, ULA’s always start with &amp;quot;fd&amp;quot;&lt;br /&gt;
&lt;br /&gt;
There are two more that have more specific uses:&lt;br /&gt;
&lt;br /&gt;
*Multicast address: Allows communication between one host and many receivers. These packets are sent out to all the interfaces that are identified by that address. Multicast addresses always begin with &amp;quot;ff&amp;quot;&lt;br /&gt;
      &lt;br /&gt;
*Special addresses: There are two special addresses. One is called the Loopback address and it looks like this 0:0:0:0:0:0:0:1 (or ::1). It is the same as the IPv4 address 127.0.0.1 and used for the same purpose; to identify a loopback interface. The other special address is called the Unspecified address and it looks like this 0:0:0:0:0:0:0:0 (or simply written ::). It is equivalent to the IPv4 address 0.0.0.0 and is also used for the same purpose; it is commonly used as the source address that packets use to confirm if a tentative address is unique.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Some features that are available only in IPv6&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Stateless address autoconfiguration - lets hosts configure themselves automatically.&lt;br /&gt;
&lt;br /&gt;
*Multicast - allows single packets to be sent to multiple destinations.&lt;br /&gt;
&lt;br /&gt;
*Mandatory network layer security - integrated Internet Protocol Security (IPsec).&lt;br /&gt;
&lt;br /&gt;
*Simpler router processing - Routing in IPv6 is almost identical to IPv4 routing under CIDR except that the addresses are 128- bit IPv6 addresses instead of 32-bit IPv4 addresses. With very straightforward extensions, IPv4&#039;s routing algorithms (OSPF, RIP, IDRP, ISIS, etc.) can be used to route IPv6.&lt;br /&gt;
&lt;br /&gt;
*Mobility – This means that a mobile device is not constrained by location and has an “always on” IP connectivity to its home agent via a bidirectional tunnel.  In other words, if there is a network that the mobile device can connect. Then it can communicate on its own home network with its own IP address, as if it was directly connected.&lt;br /&gt;
&lt;br /&gt;
*Extension Header Mechanism - The extension header mechanism makes it easy to &#039;extend&#039; the packet header to support future services for [http://en.wikipedia.org/wiki/Quality_of_service QoS], [http://en.wikipedia.org/wiki/IPsec IPsec], [http://en.wikipedia.org/wiki/Mobile_IP Mobile IP], etc. without a redesign of the basic protocol.  Extension headers do this by carrying options that are used for special packet treatment along its route or at its destination, routing, fragmenting, and for security using the IPsec framework.&lt;br /&gt;
&lt;br /&gt;
*Jumbo Payload Option header – Also known as a [http://en.wikipedia.org/wiki/Jumbogram Jumbogram] allows an IPv6 packet to carry a payload larger than the standard mode size of one byte less than 64 Kilobytes or 65,535 (2*16 - 1) octets of payload. A jumbo payload can be almost 4GB or 4,294,967,295 (2*32 - 1) octets of payload.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IPv6 Packet Format&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The IPv6 packet has three main parts:&lt;br /&gt;
&lt;br /&gt;
*Fixed Header: The first 40 octets (320 bits) of an IPv6 data packet makes up the fixed header. The format of the fixed header is presented in the table above.&lt;br /&gt;
&lt;br /&gt;
*Extension Headers (Optional)&lt;br /&gt;
&lt;br /&gt;
*Payload Extension Headers (Optional)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:Header.jpg|frame|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*Version (4 bits):   This Indicates the IP version.&lt;br /&gt;
&lt;br /&gt;
*Traffic Class (8 bits):   The traffic class field defines the priority of the packet. There are two values held by the bits of this field. The 6 most-significant bits are used to classify packets. The two bits left are used for congestion control.&lt;br /&gt;
 &lt;br /&gt;
*Flow Label (20 bits):   The flow label identifies all packets belonging to a specific Class of Service or “flow”.  These packets can be Identified by routers and handle them all according to their class of service. &lt;br /&gt;
&lt;br /&gt;
*Payload Length (16 bits):   The payload length field shows the size of the payload.  The payload length includes the size of any extension headers.  The field length is set to zero whenever an extension header carries a Jumbo Payload option. &lt;br /&gt;
&lt;br /&gt;
*Next Header (8 bits):   The next header field shows the Transport Layer Protocol that is used by the payload. When there is extension headers in the packet, this field shows which extension header will follow.&lt;br /&gt;
&lt;br /&gt;
*Hop Limit (8 bits):   The hop limit shows the maximum number of hops allowed. This value is decreased by one at every hop in the packets route. The packet is discarded when the counter reaches 0. &lt;br /&gt;
&lt;br /&gt;
*Source Address (128 bits):  This identifies the IPv6 address of the source sending the packet. The source is also known as the “The Sending Node”.&lt;br /&gt;
&lt;br /&gt;
*Destination Address (128 bits):   This identifies IPv6 address of the destination receiving the packet or “The Destination Node”.&lt;/div&gt;</summary>
		<author><name>ABorgert</name></author>
	</entry>
</feed>