<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Migrating from VirtualBox to VMware</title>
	<atom:link href="http://dossy.org/2008/05/migrating-from-virtualbox-to-vmware/feed/" rel="self" type="application/rss+xml" />
	<link>http://dossy.org/2008/05/migrating-from-virtualbox-to-vmware/</link>
	<description>Everything that comes out of Dossy, from the strange to the banal.</description>
	<lastBuildDate>Fri, 27 Jan 2012 14:30:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Mhamed</title>
		<link>http://dossy.org/2008/05/migrating-from-virtualbox-to-vmware/comment-page-1/#comment-199381</link>
		<dc:creator>Mhamed</dc:creator>
		<pubDate>Mon, 19 Apr 2010 11:31:49 +0000</pubDate>
		<guid isPermaLink="false">http://dossy.org/archives/000629.html#comment-199381</guid>
		<description>@Kane Freehold
For converting VirtualBox Windows machines to VMware, VMware’s Converter (http://www.vmware.com/products/converter/ )

this do not support vdi files !!!</description>
		<content:encoded><![CDATA[<p>@Kane Freehold<br />
For converting VirtualBox Windows machines to VMware, VMware’s Converter (<a href="http://www.vmware.com/products/converter/" rel="nofollow">http://www.vmware.com/products/converter/</a> )</p>
<p>this do not support vdi files !!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Seth-Smith</title>
		<link>http://dossy.org/2008/05/migrating-from-virtualbox-to-vmware/comment-page-1/#comment-171908</link>
		<dc:creator>Nick Seth-Smith</dc:creator>
		<pubDate>Sun, 27 Dec 2009 19:59:23 +0000</pubDate>
		<guid isPermaLink="false">http://dossy.org/archives/000629.html#comment-171908</guid>
		<description>Thanks for the great instructions - worked like a champ for me.  I was migrating a WIndows XP Pro guest OS and made one small change -  disk adaptor type of ide instead of buslogic.  As a result I was able to boot the OS under VMWare immediately; albeit it went through several boot cycles installing drivers for the new hardware and also required re-activation at M$ due to significant hardware change.

I booted the new OS using the free VMWare Player.  Having created an empty VMWare image I edited the .vmx definition file to point to my freshly minted copy of the VirtualBox image and away we went.</description>
		<content:encoded><![CDATA[<p>Thanks for the great instructions &#8211; worked like a champ for me.  I was migrating a WIndows XP Pro guest OS and made one small change &#8211;  disk adaptor type of ide instead of buslogic.  As a result I was able to boot the OS under VMWare immediately; albeit it went through several boot cycles installing drivers for the new hardware and also required re-activation at M$ due to significant hardware change.</p>
<p>I booted the new OS using the free VMWare Player.  Having created an empty VMWare image I edited the .vmx definition file to point to my freshly minted copy of the VirtualBox image and away we went.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kane Freehold</title>
		<link>http://dossy.org/2008/05/migrating-from-virtualbox-to-vmware/comment-page-1/#comment-83428</link>
		<dc:creator>Kane Freehold</dc:creator>
		<pubDate>Sat, 11 Apr 2009 20:56:19 +0000</pubDate>
		<guid isPermaLink="false">http://dossy.org/archives/000629.html#comment-83428</guid>
		<description>For converting VirtualBox Windows machines to VMware, VMware&#039;s Converter (http://www.vmware.com/products/converter/ ) has worked seamlessly for me.  I have used it to convert both physical PCs and VirtualBox PCs to VMware VMDK.  By default it also makes all the changes needed to boot right up in a new VMware guest machine.  Only additional work was to install VMware tools, and reboot.  No need for a Windows reinstall or update.

Current version of VMware Converter Standalone is 4.0.0 .  I am using VMware Fusion 2.0 on Mac OS X 10.5.6.  My converted guests were all WinXP, SP3.  They were converted from VirtualBox 2.1.4 on Mac OS X 10.5.6.

Note that the converter only works on Windows OS, though, so if you&#039;re converting a Linux or other OS, it won&#039;t help.</description>
		<content:encoded><![CDATA[<p>For converting VirtualBox Windows machines to VMware, VMware&#8217;s Converter (<a href="http://www.vmware.com/products/converter/" rel="nofollow">http://www.vmware.com/products/converter/</a> ) has worked seamlessly for me.  I have used it to convert both physical PCs and VirtualBox PCs to VMware VMDK.  By default it also makes all the changes needed to boot right up in a new VMware guest machine.  Only additional work was to install VMware tools, and reboot.  No need for a Windows reinstall or update.</p>
<p>Current version of VMware Converter Standalone is 4.0.0 .  I am using VMware Fusion 2.0 on Mac OS X 10.5.6.  My converted guests were all WinXP, SP3.  They were converted from VirtualBox 2.1.4 on Mac OS X 10.5.6.</p>
<p>Note that the converter only works on Windows OS, though, so if you&#8217;re converting a Linux or other OS, it won&#8217;t help.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anatoli Arkhipenko</title>
		<link>http://dossy.org/2008/05/migrating-from-virtualbox-to-vmware/comment-page-1/#comment-79859</link>
		<dc:creator>Anatoli Arkhipenko</dc:creator>
		<pubDate>Fri, 03 Apr 2009 16:55:38 +0000</pubDate>
		<guid isPermaLink="false">http://dossy.org/archives/000629.html#comment-79859</guid>
		<description>and now without lees-than and more-than brackets:

1. Convert VDI to VMDK using: VBoxManage clonehd vdi_file vmdk_file -formal VMDK
2. Create a VM in VMServer similar to the the settings of your VirtualBox one, but without HDD
Unfortunately in may case the VMDK disk created by VBox did not work, BUT! 
3. Convert VBox VMDK file to VMSeerver VMDK file: vmware-vdiskmanager -r vbox_vmdk_file -t 0 new_vmdk_file
4. Put the new_vmdk_file into the VMWare directory and add HDD to your newly created VM using existing image.</description>
		<content:encoded><![CDATA[<p>and now without lees-than and more-than brackets:</p>
<p>1. Convert VDI to VMDK using: VBoxManage clonehd vdi_file vmdk_file -formal VMDK<br />
2. Create a VM in VMServer similar to the the settings of your VirtualBox one, but without HDD<br />
Unfortunately in may case the VMDK disk created by VBox did not work, BUT!<br />
3. Convert VBox VMDK file to VMSeerver VMDK file: vmware-vdiskmanager -r vbox_vmdk_file -t 0 new_vmdk_file<br />
4. Put the new_vmdk_file into the VMWare directory and add HDD to your newly created VM using existing image.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anatoli Arkhipenko</title>
		<link>http://dossy.org/2008/05/migrating-from-virtualbox-to-vmware/comment-page-1/#comment-79857</link>
		<dc:creator>Anatoli Arkhipenko</dc:creator>
		<pubDate>Fri, 03 Apr 2009 16:52:58 +0000</pubDate>
		<guid isPermaLink="false">http://dossy.org/archives/000629.html#comment-79857</guid>
		<description>Hi,
I was trying to do the same migration from VBox 2.1.6 to VMServer 2.0.
vditool is no longer included into VBox distro, BUT! there is even easier way now:

1. Convert VDI to VMDK using: VBoxManage clonehd   -formal VMDK
2. Create a VM in VMServer similar to the the settings of your VirtualBox one, but without HDD
Unfortunately in may case the VMDK disk created by VBox did not work, BUT! 
3. Convert VBox VMDK file to VMSeerver VMDK file: vmware-vdiskmanager -r  -t 0 
4. Put the  into the VMWare directory and add HDD to your newly created VM using existing image. 

Worked like charm for both Ubuntu and Win XP images. Win XP started without repair install, found a s...load of new hardware and works after a reboot!
Dont&#039; forget to install VMware tools, of course!

Happy Virtualization!</description>
		<content:encoded><![CDATA[<p>Hi,<br />
I was trying to do the same migration from VBox 2.1.6 to VMServer 2.0.<br />
vditool is no longer included into VBox distro, BUT! there is even easier way now:</p>
<p>1. Convert VDI to VMDK using: VBoxManage clonehd   -formal VMDK<br />
2. Create a VM in VMServer similar to the the settings of your VirtualBox one, but without HDD<br />
Unfortunately in may case the VMDK disk created by VBox did not work, BUT!<br />
3. Convert VBox VMDK file to VMSeerver VMDK file: vmware-vdiskmanager -r  -t 0<br />
4. Put the  into the VMWare directory and add HDD to your newly created VM using existing image. </p>
<p>Worked like charm for both Ubuntu and Win XP images. Win XP started without repair install, found a s&#8230;load of new hardware and works after a reboot!<br />
Dont&#8217; forget to install VMware tools, of course!</p>
<p>Happy Virtualization!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marcelo Oliveira</title>
		<link>http://dossy.org/2008/05/migrating-from-virtualbox-to-vmware/comment-page-1/#comment-74027</link>
		<dc:creator>Marcelo Oliveira</dc:creator>
		<pubDate>Fri, 20 Mar 2009 20:23:14 +0000</pubDate>
		<guid isPermaLink="false">http://dossy.org/archives/000629.html#comment-74027</guid>
		<description>Tks.

I didn&#039;t try any of this. (I&#039;m searching how to migrate a virtualbox VM to another pc)... But according to http://www.xgrr.de/wordpress/2008/02/25/convert-virtualbox-vdi-to-vmware-vmdk  the second part colud be easier...using qemu.

Cheers.</description>
		<content:encoded><![CDATA[<p>Tks.</p>
<p>I didn&#8217;t try any of this. (I&#8217;m searching how to migrate a virtualbox VM to another pc)&#8230; But according to <a href="http://www.xgrr.de/wordpress/2008/02/25/convert-virtualbox-vdi-to-vmware-vmdk" rel="nofollow">http://www.xgrr.de/wordpress/2008/02/25/convert-virtualbox-vdi-to-vmware-vmdk</a>  the second part colud be easier&#8230;using qemu.</p>
<p>Cheers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frank N</title>
		<link>http://dossy.org/2008/05/migrating-from-virtualbox-to-vmware/comment-page-1/#comment-61770</link>
		<dc:creator>Frank N</dc:creator>
		<pubDate>Wed, 25 Feb 2009 02:59:20 +0000</pubDate>
		<guid isPermaLink="false">http://dossy.org/archives/000629.html#comment-61770</guid>
		<description>Found your blog helpful and well thought out - so I figured I should share. I might be missing something - as I&#039;m only a VirtualBox user and not an expert:
Although I could install XP64 on VirtualBox 2.1.4, I&#039;m limited to only running one 64bit VirtualBox at a time... Once I launch a 64bit VirtualBox any additional attempts to run ANY VirtualBox results in a dialog box that &#039;VT-x&#039; is already in use and stops the second instance - even regular 32-bit VirtualBox&#039;s cannot run if 64 is running.  I have VT-x disabled in the 32-bit boxes - and can run several of those at a time. And 64 wont run if a 32 is running. I&#039;m now in the process of installing VMWare yet again.</description>
		<content:encoded><![CDATA[<p>Found your blog helpful and well thought out &#8211; so I figured I should share. I might be missing something &#8211; as I&#8217;m only a VirtualBox user and not an expert:<br />
Although I could install XP64 on VirtualBox 2.1.4, I&#8217;m limited to only running one 64bit VirtualBox at a time&#8230; Once I launch a 64bit VirtualBox any additional attempts to run ANY VirtualBox results in a dialog box that &#8216;VT-x&#8217; is already in use and stops the second instance &#8211; even regular 32-bit VirtualBox&#8217;s cannot run if 64 is running.  I have VT-x disabled in the 32-bit boxes &#8211; and can run several of those at a time. And 64 wont run if a 32 is running. I&#8217;m now in the process of installing VMWare yet again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dossy Shiobara</title>
		<link>http://dossy.org/2008/05/migrating-from-virtualbox-to-vmware/comment-page-1/#comment-17739</link>
		<dc:creator>Dossy Shiobara</dc:creator>
		<pubDate>Thu, 18 Dec 2008 22:09:13 +0000</pubDate>
		<guid isPermaLink="false">http://dossy.org/archives/000629.html#comment-17739</guid>
		<description>Kenneth: Thanks for the update!  Indeed, VirtualBox 2.1 looks really promising and I might give it a try.  Gotta love The Inquirer: &quot;[...] the open sauce VirtualBox project [...]&quot;  LOL!</description>
		<content:encoded><![CDATA[<p>Kenneth: Thanks for the update!  Indeed, VirtualBox 2.1 looks really promising and I might give it a try.  Gotta love The Inquirer: &#8220;[...] the open sauce VirtualBox project [...]&#8221;  LOL!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dr. Kenneth Noisewater</title>
		<link>http://dossy.org/2008/05/migrating-from-virtualbox-to-vmware/comment-page-1/#comment-17736</link>
		<dc:creator>Dr. Kenneth Noisewater</dc:creator>
		<pubDate>Thu, 18 Dec 2008 20:25:05 +0000</pubDate>
		<guid isPermaLink="false">http://dossy.org/archives/000629.html#comment-17736</guid>
		<description>According to &lt;a href=&quot;http://www.sun.com/software/products/virtualbox/features.jsp&quot; rel=&quot;nofollow&quot;&gt;Sun&lt;/a&gt; and &lt;a href=&quot;http://www.theinquirer.net/inquirer/news/103/1050103/sun-releases-virtualbox-2-1&quot; rel=&quot;nofollow&quot;&gt;The Inq&lt;/a&gt;, VBox supports 32 and 64-bit guests?  Apparently it also supports 64-bit guests on 32-bit hosts as well as OpenGL acceleration and VMDK/VHD support..  Actually, at least according to the changelog, they&#039;ve pretty much closed the gap on VMware...</description>
		<content:encoded><![CDATA[<p>According to <a href="http://www.sun.com/software/products/virtualbox/features.jsp" rel="nofollow">Sun</a> and <a href="http://www.theinquirer.net/inquirer/news/103/1050103/sun-releases-virtualbox-2-1" rel="nofollow">The Inq</a>, VBox supports 32 and 64-bit guests?  Apparently it also supports 64-bit guests on 32-bit hosts as well as OpenGL acceleration and VMDK/VHD support..  Actually, at least according to the changelog, they&#8217;ve pretty much closed the gap on VMware&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dossy Shiobara</title>
		<link>http://dossy.org/2008/05/migrating-from-virtualbox-to-vmware/comment-page-1/#comment-3169</link>
		<dc:creator>Dossy Shiobara</dc:creator>
		<pubDate>Sun, 02 Nov 2008 05:14:17 +0000</pubDate>
		<guid isPermaLink="false">http://dossy.org/archives/000629.html#comment-3169</guid>
		<description>Adam: Great question - from what I recall having done something similar, deleting all snapshots will leave the current state, not revert you to the pre-snapshots state.  However, if you&#039;re paranoid, make a duplicate of your guest VM and delete the snapshot in that copy and see what happens.  In other words: make a backup of your guest before deleting the snapshot.  :-)</description>
		<content:encoded><![CDATA[<p>Adam: Great question &#8211; from what I recall having done something similar, deleting all snapshots will leave the current state, not revert you to the pre-snapshots state.  However, if you&#8217;re paranoid, make a duplicate of your guest VM and delete the snapshot in that copy and see what happens.  In other words: make a backup of your guest before deleting the snapshot.  <img src='http://dossy.org/wp/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using apc
Database Caching using apc
Object Caching 387/391 objects using apc

Served from: dossy.org @ 2012-02-09 05:27:25 -->
