<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.7.2" -->
<rss version="2.0">
	<channel>
		<title>VMware vs. VirtualBox Part 2</title>
		<description>Comments for VMware vs. VirtualBox Part 2 at http://marsbox.com , comment 1 to 7 out of 7 comments</description>
		<link>http://marsbox.com</link>
		<lastBuildDate>Thu, 29 Jul 2010 22:56:32 +0100</lastBuildDate>
		<generator>FeedCreator 1.7.2</generator>
		<item>
			<title>...</title>
			<link>http://marsbox.com/blog/reviews/vmware-vs-virtualbox-part-2/#comment-277</link>
			<description>FWIW, I have been using VB 3.1.x on my Ubuntu box (AMD 9850 / 8G DDR2 / 7200RPM SATA) to host a Win7 VM and was pretty disappointed.  CPU usage in the guest was always &gt;20% and it seemed that things took forever to launch and were agonizingly sluggish in use.  I just switched to VMWare (3.0.x Player) and the difference is amazing.  The guest is actually usable now.  I see in one of the comments to your original article that setting VB to emulate SATA drives makes a big difference; I don't know what my current setting is,  I'll try that and see if if the performance improves.  Thanks for the article! - Random Coolzip</description>
			<pubDate>Thu, 20 May 2010 08:53:28 +0100</pubDate>
		</item>
		<item>
			<title>...</title>
			<link>http://marsbox.com/blog/reviews/vmware-vs-virtualbox-part-2/#comment-240</link>
			<description>I have both VMWare Fusion and VirtualBox on my MacBook Pro.  I also have VirtualBox on both of my Windows 7 machines.  The biggest VirtualBox  advantage to me is that it operates the same across all of the major operating systems.  I am can't afford to purchase VMWare Workstation for so much more $$ when I already purchased Fusion.  It is also nice to be able to just run my VMs on my desktop when I get home. - DJara</description>
			<pubDate>Wed, 17 Feb 2010 16:28:54 +0100</pubDate>
		</item>
		<item>
			<title>...</title>
			<link>http://marsbox.com/blog/reviews/vmware-vs-virtualbox-part-2/#comment-218</link>
			<description>Was looking for benchmarks of vmware vs virtualbox and finally found yours! Had almost decided against virtualbox based on older diskspeed issues but given the new benchmarks, am going for virtualbox now!
Thanks! - Aditya Gilra</description>
			<pubDate>Tue, 29 Dec 2009 03:52:44 +0100</pubDate>
		</item>
		<item>
			<title>...</title>
			<link>http://marsbox.com/blog/reviews/vmware-vs-virtualbox-part-2/#comment-201</link>
			<description>I think it is the most useful material for comparison between  the 2 VM giants I have seen so far! thanks! - sxathk</description>
			<pubDate>Thu, 19 Nov 2009 22:49:40 +0100</pubDate>
		</item>
		<item>
			<title>...</title>
			<link>http://marsbox.com/blog/reviews/vmware-vs-virtualbox-part-2/#comment-200</link>
			<description>Thanks for the update,

If possible I'd really like to see a feature comparison between VB and VMware WS, say about snapshots, network user interface, etc ... on both apps.

I like the tests graphics. - mb</description>
			<pubDate>Thu, 19 Nov 2009 10:14:17 +0100</pubDate>
		</item>
		<item>
			<title>...</title>
			<link>http://marsbox.com/blog/reviews/vmware-vs-virtualbox-part-2/#comment-137</link>
			<description>Hey,
looks like you compared performance of physical disks and forgot to take into account that VmWare is constantly updating the snapshot. To avoid this (useful) overhead, you may want to add an additioanl disk and check &quot;Independent&quot; checkbox. In this case disk won't be covered by snapshot.
I'd expect significant performance boost in this case.
-dda - dda</description>
			<pubDate>Thu, 23 Apr 2009 17:29:45 +0100</pubDate>
		</item>
		<item>
			<title>...</title>
			<link>http://marsbox.com/blog/reviews/vmware-vs-virtualbox-part-2/#comment-125</link>
			<description>Hey, thanks for writing this up.  I came upon your old review through 4sysops and saw your update.  I've been looking for a helpful substantiated summary between these two for a while now.

Thanks again! - Paul</description>
			<pubDate>Sun, 05 Apr 2009 10:17:08 +0100</pubDate>
		</item>
	</channel>
</rss>
