<?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: Sorry, no server for you today</title>
	<atom:link href="http://stage.vambenepe.com/archives/237/feed" rel="self" type="application/rss+xml" />
	<link>http://stage.vambenepe.com/archives/237</link>
	<description>IT management in a changing IT world</description>
	<lastBuildDate>Tue, 09 Mar 2010 22:10:17 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: William Vambenepe</title>
		<link>http://stage.vambenepe.com/archives/237#comment-49188</link>
		<dc:creator>William Vambenepe</dc:creator>
		<pubDate>Mon, 18 Aug 2008 16:20:23 +0000</pubDate>
		<guid isPermaLink="false">http://stage.vambenepe.com/?p=237#comment-49188</guid>
		<description>Fermin: Sure there are always bugs. But most of them are part of a the implementation of a feature that is (presumably) of some value to the user. License enforcement is a path of failure (designed to be a single point of failure) that is specifically added to the system and yet doesn&#039;t provide any customer benefit. It just seems to be in a different category.</description>
		<content:encoded><![CDATA[<p>Fermin: Sure there are always bugs. But most of them are part of a the implementation of a feature that is (presumably) of some value to the user. License enforcement is a path of failure (designed to be a single point of failure) that is specifically added to the system and yet doesn&#8217;t provide any customer benefit. It just seems to be in a different category.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fermin</title>
		<link>http://stage.vambenepe.com/archives/237#comment-49177</link>
		<dc:creator>fermin</dc:creator>
		<pubDate>Mon, 18 Aug 2008 08:24:04 +0000</pubDate>
		<guid isPermaLink="false">http://stage.vambenepe.com/?p=237#comment-49177</guid>
		<description>I think the &quot;leasing car &amp; gun&quot; situation is not new... conventional operating systems could exhibit the same problematic behaviour. I mean, even if you are not using VMware ESX or any other virtualization technology, it could happen that your old-fashioned operating system refuses to boot due to some obscure problem bug that only its vendor knows (theoretically). I didn&#039;t dig in, but I think that several examples could be found.

The fact is that whenever you rely your services/application/solution/etc. in someone piece of software (OS or hypervisor) you *need* to trust in its vendor. So, what VMware and other have to care about is the reliability perception of their virtualization products (and, of course, this kind of news damages their image). Moreover, some customer may prefer open software solutions (being the Xen hypervisor the most relevant case nowadays, I guess) by the old argument that the more eyes you keep in the code (so, less &quot;obscurity&quot;) the less bugs the code would have and, therefore, customers perceive more reliability from those products.</description>
		<content:encoded><![CDATA[<p>I think the &#8220;leasing car &amp; gun&#8221; situation is not new&#8230; conventional operating systems could exhibit the same problematic behaviour. I mean, even if you are not using VMware ESX or any other virtualization technology, it could happen that your old-fashioned operating system refuses to boot due to some obscure problem bug that only its vendor knows (theoretically). I didn&#8217;t dig in, but I think that several examples could be found.</p>
<p>The fact is that whenever you rely your services/application/solution/etc. in someone piece of software (OS or hypervisor) you *need* to trust in its vendor. So, what VMware and other have to care about is the reliability perception of their virtualization products (and, of course, this kind of news damages their image). Moreover, some customer may prefer open software solutions (being the Xen hypervisor the most relevant case nowadays, I guess) by the old argument that the more eyes you keep in the code (so, less &#8220;obscurity&#8221;) the less bugs the code would have and, therefore, customers perceive more reliability from those products.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alexis Le-Quoc</title>
		<link>http://stage.vambenepe.com/archives/237#comment-49052</link>
		<dc:creator>Alexis Le-Quoc</dc:creator>
		<pubDate>Thu, 14 Aug 2008 17:25:45 +0000</pubDate>
		<guid isPermaLink="false">http://stage.vambenepe.com/?p=237#comment-49052</guid>
		<description>Been there, done that. What a nice surprise when machines would fail with a &quot;General System Error&quot; message. Luckily for us, these VMs were used for development, not production. My whole team rants about VMware ESX, its quirkiness, the insistence with which it begs vmware-tools to be deployed... The basic VM hypervisor is a commodity, pretty much the way OS have gone, so I would not be surprised if VMware focussed solely on managing VMs, regardless of their provenance.

Nice blog by the way.</description>
		<content:encoded><![CDATA[<p>Been there, done that. What a nice surprise when machines would fail with a &#8220;General System Error&#8221; message. Luckily for us, these VMs were used for development, not production. My whole team rants about VMware ESX, its quirkiness, the insistence with which it begs vmware-tools to be deployed&#8230; The basic VM hypervisor is a commodity, pretty much the way OS have gone, so I would not be surprised if VMware focussed solely on managing VMs, regardless of their provenance.</p>
<p>Nice blog by the way.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
