<?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 for Securlogic Blog</title>
	<atom:link href="http://blog.securlogic.com/?feed=comments-rss2" rel="self" type="application/rss+xml" />
	<link>http://blog.securlogic.com</link>
	<description>Tech bites with an Asian touch.</description>
	<pubDate>Thu, 09 Sep 2010 09:33:37 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on VMware ESX 3i, VMware Server 2.0, Citrix XenServer or Sun xVM VirtualBox? by Ranxerox</title>
		<link>http://blog.securlogic.com/?p=28&#038;cpage=1#comment-107</link>
		<dc:creator>Ranxerox</dc:creator>
		<pubDate>Thu, 18 Mar 2010 21:50:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.securlogic.com/?p=28#comment-107</guid>
		<description>I can only chime in on my experience with VMware server 2.0 and VirtualBox but I'm getting ready to test VMW 2.0, ESXi, and VirtualBox for a multi-site server virtualization scheme proposal to the company I'm consulting for.
I have set up virtual hosts before with VM Server 1.02/2.0 (Quad - dual core opterons, 32Gb RAM, 9Tb iSCSI SAN), but my comparative experiences with both are on a Dual core AMD64 4800+, 4Gb DDR2, 750Gb SATA2, ASUS A8N-SLI MB.
VMware Server (and ESXi) have the advantages of good industry recognition, hardware built with it in mind, and it's so "popular" its name is almost layman recognizable making it easier to "sell". 
VMware detracting factors are the web only console (slow and twitchy), that the freeware demo is speed crippled vs. ESX(i), that ESXi is not console manageable, and the Windows only administration client is HUGE (although i haven't tried it yet as I can't see shelling out the cash for the rather slim "approved hardware" list to build a server from). The speed crippling of the freeware versions is the biggest detractor as it makes production emulation testing cost prohibitive, or very slow.
VirtualBox (which I have been using for approx. 3 months) has a small disk and resources impact, is snappy quick (compared to VMware), and can import a variety of VM disk types (vmware migration caveat that the disk image must be a monolithic .vmdk and not chopped into 2Gb chunks. If it is in 2Gb .vmdk chunks you must convert them into 1 file via VMware 1st before importing into VB).Once imported the guest OS' run fine.
VB's detractor situations are not quite enterprise level in features (yet), no remote virtual machine management app (although VNC is acceptable), and it seems to grab host memory and not give back all of it (this needs more thorough testing). 
I'll have more definite data and experiences by mid-summer, but right now I'm leaning towards VB with a custom kernel on the host.
The versatility of a type II vs. a type I host is very appealing.</description>
		<content:encoded><![CDATA[<p>I can only chime in on my experience with VMware server 2.0 and VirtualBox but I&#8217;m getting ready to test VMW 2.0, ESXi, and VirtualBox for a multi-site server virtualization scheme proposal to the company I&#8217;m consulting for.<br />
I have set up virtual hosts before with VM Server 1.02/2.0 (Quad - dual core opterons, 32Gb RAM, 9Tb iSCSI SAN), but my comparative experiences with both are on a Dual core AMD64 4800+, 4Gb DDR2, 750Gb SATA2, ASUS A8N-SLI MB.<br />
VMware Server (and ESXi) have the advantages of good industry recognition, hardware built with it in mind, and it&#8217;s so &#8220;popular&#8221; its name is almost layman recognizable making it easier to &#8220;sell&#8221;.<br />
VMware detracting factors are the web only console (slow and twitchy), that the freeware demo is speed crippled vs. ESX(i), that ESXi is not console manageable, and the Windows only administration client is HUGE (although i haven&#8217;t tried it yet as I can&#8217;t see shelling out the cash for the rather slim &#8220;approved hardware&#8221; list to build a server from). The speed crippling of the freeware versions is the biggest detractor as it makes production emulation testing cost prohibitive, or very slow.<br />
VirtualBox (which I have been using for approx. 3 months) has a small disk and resources impact, is snappy quick (compared to VMware), and can import a variety of VM disk types (vmware migration caveat that the disk image must be a monolithic .vmdk and not chopped into 2Gb chunks. If it is in 2Gb .vmdk chunks you must convert them into 1 file via VMware 1st before importing into VB).Once imported the guest OS&#8217; run fine.<br />
VB&#8217;s detractor situations are not quite enterprise level in features (yet), no remote virtual machine management app (although VNC is acceptable), and it seems to grab host memory and not give back all of it (this needs more thorough testing).<br />
I&#8217;ll have more definite data and experiences by mid-summer, but right now I&#8217;m leaning towards VB with a custom kernel on the host.<br />
The versatility of a type II vs. a type I host is very appealing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on VMware ESX 3i, VMware Server 2.0, Citrix XenServer or Sun xVM VirtualBox? by David</title>
		<link>http://blog.securlogic.com/?p=28&#038;cpage=1#comment-106</link>
		<dc:creator>David</dc:creator>
		<pubDate>Sat, 16 Jan 2010 17:08:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.securlogic.com/?p=28#comment-106</guid>
		<description>We use VMWare server just about everywhere because it works really well on commodity hardware.  We use inexpensive refurb optiplex machines with a beefy NAS over NFS.  The biggest reason we like VMWare server is because we have control over the base operating system which is 90% Ubuntu server and 10% CentOS 5.  We use scripts to shutdown the VMs, copy the vm files to the NAS and start the VMs backup.  On a stand-alone machine without a NAS, the same scripts copy the vm files to esata or usb hard drives.  A lot of our scripting is centralized from a linux script host that uses rsa certificates to ssh to the vmware hosts.  That way we can centralize our backup schedules and log files are copied to a single repository where we use Splunk to monitor for failure conditions.

None of that is possible in the other offerings.  However, XenServer 5.5.0 is a VERY VERY close second as it has a documented and supported base operating system loosely based on CentOS 5 that we are currently testing our scripts on.  

Thanks for the post.  I found it very informative.</description>
		<content:encoded><![CDATA[<p>We use VMWare server just about everywhere because it works really well on commodity hardware.  We use inexpensive refurb optiplex machines with a beefy NAS over NFS.  The biggest reason we like VMWare server is because we have control over the base operating system which is 90% Ubuntu server and 10% CentOS 5.  We use scripts to shutdown the VMs, copy the vm files to the NAS and start the VMs backup.  On a stand-alone machine without a NAS, the same scripts copy the vm files to esata or usb hard drives.  A lot of our scripting is centralized from a linux script host that uses rsa certificates to ssh to the vmware hosts.  That way we can centralize our backup schedules and log files are copied to a single repository where we use Splunk to monitor for failure conditions.</p>
<p>None of that is possible in the other offerings.  However, XenServer 5.5.0 is a VERY VERY close second as it has a documented and supported base operating system loosely based on CentOS 5 that we are currently testing our scripts on.  </p>
<p>Thanks for the post.  I found it very informative.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on VMware ESX 3i, VMware Server 2.0, Citrix XenServer or Sun xVM VirtualBox? by Phillip Chee</title>
		<link>http://blog.securlogic.com/?p=28&#038;cpage=1#comment-67</link>
		<dc:creator>Phillip Chee</dc:creator>
		<pubDate>Sat, 11 Jul 2009 17:15:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.securlogic.com/?p=28#comment-67</guid>
		<description>With respect to Sun's VirtualBox I think you're comparing apples to oranges when put up against Xenserver and VMware ESXi. Xenserver and ESXi are bare-metal Type I hypervisors while VirtualBox is a Type II hosted hypervisor. VMware Server is also a Type II hypervisor but features the remote web-based management of a Type I hypervisor. VirtualBox should be compared to VMware Workstation and Microsoft VirtualPC or Parallels Workstation to make any comparison meaningful and fair.</description>
		<content:encoded><![CDATA[<p>With respect to Sun&#8217;s VirtualBox I think you&#8217;re comparing apples to oranges when put up against Xenserver and VMware ESXi. Xenserver and ESXi are bare-metal Type I hypervisors while VirtualBox is a Type II hosted hypervisor. VMware Server is also a Type II hypervisor but features the remote web-based management of a Type I hypervisor. VirtualBox should be compared to VMware Workstation and Microsoft VirtualPC or Parallels Workstation to make any comparison meaningful and fair.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Public or Private? IPv6 must lead the way. by pradeep</title>
		<link>http://blog.securlogic.com/?p=59&#038;cpage=1#comment-58</link>
		<dc:creator>pradeep</dc:creator>
		<pubDate>Wed, 01 Jul 2009 11:39:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.securlogic.com/?p=59#comment-58</guid>
		<description>Its already implemented.. check this soft http://www.lanoninternet.com 
which uses windows teredo with ipv6 address to connect two m/c over internet. no more port forwarding...</description>
		<content:encoded><![CDATA[<p>Its already implemented.. check this soft <a href="http://www.lanoninternet.com" rel="nofollow">http://www.lanoninternet.com</a><br />
which uses windows teredo with ipv6 address to connect two m/c over internet. no more port forwarding&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Public or Private? IPv6 must lead the way. by Hanz</title>
		<link>http://blog.securlogic.com/?p=59&#038;cpage=1#comment-57</link>
		<dc:creator>Hanz</dc:creator>
		<pubDate>Wed, 01 Jul 2009 07:34:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.securlogic.com/?p=59#comment-57</guid>
		<description>the last i heard, the japanese are going to migrate everything to IPv6 by latest 1st quarter of next year but what about S'pore ? Other than FTTH, does we have plans for migrating to IPv6 yet ??</description>
		<content:encoded><![CDATA[<p>the last i heard, the japanese are going to migrate everything to IPv6 by latest 1st quarter of next year but what about S&#8217;pore ? Other than FTTH, does we have plans for migrating to IPv6 yet ??</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on VMware ESX 3i, VMware Server 2.0, Citrix XenServer or Sun xVM VirtualBox? by justin.lee</title>
		<link>http://blog.securlogic.com/?p=28&#038;cpage=1#comment-4</link>
		<dc:creator>justin.lee</dc:creator>
		<pubDate>Mon, 23 Mar 2009 03:34:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.securlogic.com/?p=28#comment-4</guid>
		<description>It's not the console management tool I'm referring to. It's the ability to fully manage the VM (add disk, change RAM settings, allocate CPU resources, migrate to another host, backup, etc.) from a single tool. VirtualBox lacks this ability.</description>
		<content:encoded><![CDATA[<p>It&#8217;s not the console management tool I&#8217;m referring to. It&#8217;s the ability to fully manage the VM (add disk, change RAM settings, allocate CPU resources, migrate to another host, backup, etc.) from a single tool. VirtualBox lacks this ability.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on VMware ESX 3i, VMware Server 2.0, Citrix XenServer or Sun xVM VirtualBox? by Hanz</title>
		<link>http://blog.securlogic.com/?p=28&#038;cpage=1#comment-2</link>
		<dc:creator>Hanz</dc:creator>
		<pubDate>Fri, 20 Mar 2009 09:13:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.securlogic.com/?p=28#comment-2</guid>
		<description>hi,

in regards to this below,

" xVM VirtualBox does not have the remote management capabilities of VMware ESX 3i or VMware Server 2.0. It works more like a client app and requires that your server runs a GUI (X11), somewhat like VMware Player. "

Ever heard of VBoxHeadless ?? it isa tool that comes with Virtual Box  that allows you to connect to the virtual machines over a remote desktop connection, so there's no need for the VirtualBox GUI.

Link : http://www.howtoforge.com/vboxheadless-running-virtual-machines-with-virtualbox-2.0-on-a-headless-ubuntu-8.04-server

Best Regards</description>
		<content:encoded><![CDATA[<p>hi,</p>
<p>in regards to this below,</p>
<p>&#8221; xVM VirtualBox does not have the remote management capabilities of VMware ESX 3i or VMware Server 2.0. It works more like a client app and requires that your server runs a GUI (X11), somewhat like VMware Player. &#8221;</p>
<p>Ever heard of VBoxHeadless ?? it isa tool that comes with Virtual Box  that allows you to connect to the virtual machines over a remote desktop connection, so there&#8217;s no need for the VirtualBox GUI.</p>
<p>Link : <a href="http://www.howtoforge.com/vboxheadless-running-virtual-machines-with-virtualbox-2.0-on-a-headless-ubuntu-8.04-server" rel="nofollow">http://www.howtoforge.com/vboxheadless-running-virtual-machines-with-virtualbox-2.0-on-a-headless-ubuntu-8.04-server</a></p>
<p>Best Regards</p>
]]></content:encoded>
	</item>
</channel>
</rss>
