 




<?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: Is hypervisor-based virtualization doomed?</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/server-virtualization/is-hypervisor-based-virtualization-doomed/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/server-virtualization/is-hypervisor-based-virtualization-doomed/</link>
	<description>A SearchServerVirtualization.com and SearchVMware.com blog</description>
	<lastBuildDate>Wed, 12 Sep 2012 17:14:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Conrad</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/is-hypervisor-based-virtualization-doomed/#comment-1406</link>
		<dc:creator>Conrad</dc:creator>
		<pubDate>Wed, 30 Apr 2008 04:21:03 +0000</pubDate>
		<guid isPermaLink="false">http://servervirtualization.blogs.techtarget.com/2008/04/28/is-hypervisor-based-virtualization-doomed/#comment-1406</guid>
		<description><![CDATA[You seem to presume the motivation for hypervisor virtualization is fault isolation.  In my world, the primary motivation is to decouple the software platform (OS + middleware, etc.) and change management requirements of two applications.  AppA wants OS version 1.2.3, but AppB wants OS version 1.2.4 plus patch XYZ, or even a completely different OS family (e.g. Windows and Linux).  Or even if we can get the suppliers of AppA and AppB to deliver code that can piecefully co-exist on a common platform, AppA wants to upgrade next month to a new version that has new platform requirements, while AppB can&#039;t accomodate a corresponding upgrade until next year.]]></description>
		<content:encoded><![CDATA[<p>You seem to presume the motivation for hypervisor virtualization is fault isolation.  In my world, the primary motivation is to decouple the software platform (OS + middleware, etc.) and change management requirements of two applications.  AppA wants OS version 1.2.3, but AppB wants OS version 1.2.4 plus patch XYZ, or even a completely different OS family (e.g. Windows and Linux).  Or even if we can get the suppliers of AppA and AppB to deliver code that can piecefully co-exist on a common platform, AppA wants to upgrade next month to a new version that has new platform requirements, while AppB can&#8217;t accomodate a corresponding upgrade until next year.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony Austin</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/is-hypervisor-based-virtualization-doomed/#comment-1405</link>
		<dc:creator>Tony Austin</dc:creator>
		<pubDate>Wed, 30 Apr 2008 01:49:16 +0000</pubDate>
		<guid isPermaLink="false">http://servervirtualization.blogs.techtarget.com/2008/04/28/is-hypervisor-based-virtualization-doomed/#comment-1405</guid>
		<description><![CDATA[This is only my 39th year in IT, the first 25 of them as an IBM employee (now retired). I joined IBM Australia in 1970, the year that System/370 was announced, this range of systems being amongst the very first to have widespread use of VM as fundamental part of the architecture (as referred to by Dick Yexek just above). Then in 1978 I had my first visit to the IBM Rochester (Minnesota) Development Lab and became seriously involved with the IBM System/38, with a radical new machine architecture which included VM capabilities into the very hardware and microcode itself. This architecture lived on as the IBM Application System/400 -- or just AS/400, with operating system called OS/400 -- then the iSeries, then the System i, and a month or to ago as simply &quot;i&quot; brand (I think). Whatever the branding, IMHO this second very clean IBM virtual machine architecture also puts the other VMs and hypervisor offerings to shame!]]></description>
		<content:encoded><![CDATA[<p>This is only my 39th year in IT, the first 25 of them as an IBM employee (now retired). I joined IBM Australia in 1970, the year that System/370 was announced, this range of systems being amongst the very first to have widespread use of VM as fundamental part of the architecture (as referred to by Dick Yexek just above). Then in 1978 I had my first visit to the IBM Rochester (Minnesota) Development Lab and became seriously involved with the IBM System/38, with a radical new machine architecture which included VM capabilities into the very hardware and microcode itself. This architecture lived on as the IBM Application System/400 &#8212; or just AS/400, with operating system called OS/400 &#8212; then the iSeries, then the System i, and a month or to ago as simply &#8220;i&#8221; brand (I think). Whatever the branding, IMHO this second very clean IBM virtual machine architecture also puts the other VMs and hypervisor offerings to shame!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken J</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/is-hypervisor-based-virtualization-doomed/#comment-1404</link>
		<dc:creator>Ken J</dc:creator>
		<pubDate>Wed, 30 Apr 2008 00:23:17 +0000</pubDate>
		<guid isPermaLink="false">http://servervirtualization.blogs.techtarget.com/2008/04/28/is-hypervisor-based-virtualization-doomed/#comment-1404</guid>
		<description><![CDATA[Schorschi,

Nice article and quite informative, especially references to little known leading edge technologies like DEC&#039;s MS Job Engine API, which predated VMware.   There is not much new under this sun.

BTW: DEC is actually Digital Equipment Corp (not Digital Electronics Corp.). People oft forget the once #2 IT company whose legacy has greatly influenced the shape of technology today, unfortunately they were not as good at telling the world unlike M$. HP did more to bury the DEC legacy than Compaq.]]></description>
		<content:encoded><![CDATA[<p>Schorschi,</p>
<p>Nice article and quite informative, especially references to little known leading edge technologies like DEC&#8217;s MS Job Engine API, which predated VMware.   There is not much new under this sun.</p>
<p>BTW: DEC is actually Digital Equipment Corp (not Digital Electronics Corp.). People oft forget the once #2 IT company whose legacy has greatly influenced the shape of technology today, unfortunately they were not as good at telling the world unlike M$. HP did more to bury the DEC legacy than Compaq.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Neil Murphy</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/is-hypervisor-based-virtualization-doomed/#comment-1403</link>
		<dc:creator>Neil Murphy</dc:creator>
		<pubDate>Tue, 29 Apr 2008 21:37:11 +0000</pubDate>
		<guid isPermaLink="false">http://servervirtualization.blogs.techtarget.com/2008/04/28/is-hypervisor-based-virtualization-doomed/#comment-1403</guid>
		<description><![CDATA[&quot;Case in point, the Case in point, the recent Symantec Antivirus issue with VMware ESX OS&quot;. Eh? What? You can&#039;t just have a big rant and throw in a comment like that without hyperlinking it to additional info. I&#039;ve been Googling that comment and can&#039;t find any articles relating to a &quot;recent Symantec Antivirus issue with VMware ESX OS&quot;. Clarify please!]]></description>
		<content:encoded><![CDATA[<p>&#8220;Case in point, the Case in point, the recent Symantec Antivirus issue with VMware ESX OS&#8221;. Eh? What? You can&#8217;t just have a big rant and throw in a comment like that without hyperlinking it to additional info. I&#8217;ve been Googling that comment and can&#8217;t find any articles relating to a &#8220;recent Symantec Antivirus issue with VMware ESX OS&#8221;. Clarify please!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Massimo Re Ferre'</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/is-hypervisor-based-virtualization-doomed/#comment-1402</link>
		<dc:creator>Massimo Re Ferre'</dc:creator>
		<pubDate>Tue, 29 Apr 2008 21:08:46 +0000</pubDate>
		<guid isPermaLink="false">http://servervirtualization.blogs.techtarget.com/2008/04/28/is-hypervisor-based-virtualization-doomed/#comment-1402</guid>
		<description><![CDATA[Well I guess that on the same line we can even say: 

1) in Scotland you wouldn&#039;t need an umbrella if it wasn&#039;t raining.... or

2) if I could walk at 130 Km/Hour I wouldn&#039;t need a car or 

3) etc etc etc 

Point is that in Scotland... it rains (a lot) and I can only walk at about 3 Km/Hour (sustained).. so we need umbrellas and cars to overcome facts of the nature. 

We all know that x86 Operating Systems are not nearly close to the quality of other proprietary OS&#039;es on different platforms.... this is another fact .... and &quot;asking&quot; the OS vendor to &quot;fix them&quot; is not going to work. 

How can an OS (read Windows) that is able to run flight simulator as well as a backend 32-socket SQL database at the same time be engineered to be secure and reliable from the ground up? It&#039;s certainly flexible and cheap .... and that&#039;s pretty much it.... there is no secret sauce to build something that is as flexible as windows and as reliable as the zOS.... it&#039;s either one or the other. Your choice.

That&#039;s why I (personally) think that it&#039;s not the hypervisor to be doomed in the long run ..... but the Operating Systems that you are referring to. This is my side of the story: 

http://it20.info/files/3/documentation/entry54.aspx

http://it20.info/blogs/main/archive/2007/06/25/32.aspx

Massimo. 

P.S. Oh btw .... 

&gt;Poor software quality makes hypervisor-based virtualization &gt;more expensive than it should be and the publishers of &gt;operating systems love it

Well ... ask MS if they are happy about having VMware around .... ;-)]]></description>
		<content:encoded><![CDATA[<p>Well I guess that on the same line we can even say: </p>
<p>1) in Scotland you wouldn&#8217;t need an umbrella if it wasn&#8217;t raining&#8230;. or</p>
<p>2) if I could walk at 130 Km/Hour I wouldn&#8217;t need a car or </p>
<p>3) etc etc etc </p>
<p>Point is that in Scotland&#8230; it rains (a lot) and I can only walk at about 3 Km/Hour (sustained).. so we need umbrellas and cars to overcome facts of the nature. </p>
<p>We all know that x86 Operating Systems are not nearly close to the quality of other proprietary OS&#8217;es on different platforms&#8230;. this is another fact &#8230;. and &#8220;asking&#8221; the OS vendor to &#8220;fix them&#8221; is not going to work. </p>
<p>How can an OS (read Windows) that is able to run flight simulator as well as a backend 32-socket SQL database at the same time be engineered to be secure and reliable from the ground up? It&#8217;s certainly flexible and cheap &#8230;. and that&#8217;s pretty much it&#8230;. there is no secret sauce to build something that is as flexible as windows and as reliable as the zOS&#8230;. it&#8217;s either one or the other. Your choice.</p>
<p>That&#8217;s why I (personally) think that it&#8217;s not the hypervisor to be doomed in the long run &#8230;.. but the Operating Systems that you are referring to. This is my side of the story: </p>
<p><a href="http://it20.info/files/3/documentation/entry54.aspx" rel="nofollow">http://it20.info/files/3/documentation/entry54.aspx</a></p>
<p><a href="http://it20.info/blogs/main/archive/2007/06/25/32.aspx" rel="nofollow">http://it20.info/blogs/main/archive/2007/06/25/32.aspx</a></p>
<p>Massimo. </p>
<p>P.S. Oh btw &#8230;. </p>
<p>&gt;Poor software quality makes hypervisor-based virtualization &gt;more expensive than it should be and the publishers of &gt;operating systems love it</p>
<p>Well &#8230; ask MS if they are happy about having VMware around &#8230;. <img src='http://itknowledgeexchange.techtarget.com/server-virtualization/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dick Yezek</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/is-hypervisor-based-virtualization-doomed/#comment-1401</link>
		<dc:creator>Dick Yezek</dc:creator>
		<pubDate>Tue, 29 Apr 2008 19:41:35 +0000</pubDate>
		<guid isPermaLink="false">http://servervirtualization.blogs.techtarget.com/2008/04/28/is-hypervisor-based-virtualization-doomed/#comment-1401</guid>
		<description><![CDATA[This is my 44th year in mainframe technology. IBM announced mainframe VM in 1972 and it has been running on IBM mainframes ever since, alongside Z/OS, VM itself, VSE, TPF (the old airlines control program), Linux, and many others. All aspects of the hardware, software, and I/O have been fully virtualized in IBM&#039;s VM for years and are in use today. IBM used VM in the past to test new systems before rollout - and that continued into the present with the rollout of their Z10 machine this past February.

Every modern IBM mainframe today runs under the PR/SM hypervisor (Processor Resource / System manager) which is, in reality, a no charge specialized version of IBM&#039;s VM which loads automatically at POR (Power On Reset)- which many of you call &quot;boot up&quot; - from the mainframe&#039;s Service Elements (ThinkPad PCs) yet the PR/SM overhead is about 1% in our mainframes.  

I don&#039;t think anyone in my world thinks VM is a waste of time or effort, least of all IBM. It has the functionality many just dream about today - and it also has at least 30 years of developmemnt, testing, and debugging behind it.

One final comment: &quot;It works.&quot;]]></description>
		<content:encoded><![CDATA[<p>This is my 44th year in mainframe technology. IBM announced mainframe VM in 1972 and it has been running on IBM mainframes ever since, alongside Z/OS, VM itself, VSE, TPF (the old airlines control program), Linux, and many others. All aspects of the hardware, software, and I/O have been fully virtualized in IBM&#8217;s VM for years and are in use today. IBM used VM in the past to test new systems before rollout &#8211; and that continued into the present with the rollout of their Z10 machine this past February.</p>
<p>Every modern IBM mainframe today runs under the PR/SM hypervisor (Processor Resource / System manager) which is, in reality, a no charge specialized version of IBM&#8217;s VM which loads automatically at POR (Power On Reset)- which many of you call &#8220;boot up&#8221; &#8211; from the mainframe&#8217;s Service Elements (ThinkPad PCs) yet the PR/SM overhead is about 1% in our mainframes.  </p>
<p>I don&#8217;t think anyone in my world thinks VM is a waste of time or effort, least of all IBM. It has the functionality many just dream about today &#8211; and it also has at least 30 years of developmemnt, testing, and debugging behind it.</p>
<p>One final comment: &#8220;It works.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michal2000</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/is-hypervisor-based-virtualization-doomed/#comment-1400</link>
		<dc:creator>Michal2000</dc:creator>
		<pubDate>Tue, 29 Apr 2008 18:50:45 +0000</pubDate>
		<guid isPermaLink="false">http://servervirtualization.blogs.techtarget.com/2008/04/28/is-hypervisor-based-virtualization-doomed/#comment-1400</guid>
		<description><![CDATA[This sounds like biting the hand that feeds you. Xen, virtual Iron, ESX, Hyper-V...  they&#039;re all junk?  I have  hard time dealing with that analysis. I am not saying that he is wrong about the bloated code, but what is the alternative, rewriting all the code in assembly language? Virtualization is now an essential part of a datacenter infrastructure.  Whether Dev, QA, Training, or Production servers, these technologies allow more efficient usage of hardware, power, and high availability.]]></description>
		<content:encoded><![CDATA[<p>This sounds like biting the hand that feeds you. Xen, virtual Iron, ESX, Hyper-V&#8230;  they&#8217;re all junk?  I have  hard time dealing with that analysis. I am not saying that he is wrong about the bloated code, but what is the alternative, rewriting all the code in assembly language? Virtualization is now an essential part of a datacenter infrastructure.  Whether Dev, QA, Training, or Production servers, these technologies allow more efficient usage of hardware, power, and high availability.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/is-hypervisor-based-virtualization-doomed/#comment-1399</link>
		<dc:creator>Alan</dc:creator>
		<pubDate>Mon, 28 Apr 2008 23:10:11 +0000</pubDate>
		<guid isPermaLink="false">http://servervirtualization.blogs.techtarget.com/2008/04/28/is-hypervisor-based-virtualization-doomed/#comment-1399</guid>
		<description><![CDATA[I think your argument definitely has merit, but don&#039;t blame the technology just because of the implementation.  Hypervisor-based virtualization brings a tremendous number of benefits, most notably management.  You have to be able to manage virtualization in the server data center, and today that&#039;s via the hypervisor.  There&#039;s no better access to data for virtual operating systems than their parent running platform.  Might we someday get to a Softgrid model for server-based applications?  Maybe, but we&#039;re not even close to it today.  

There are advancements being made in building more intelligent hypervisors, such as Hyper-V and ESX 3i.  I do agree that the hypervisors that most people are using on their desktops today with Virtual Server, VMware Desktop/Workstaion/Server, and Parallels, leave a lot to be desired.  But again, don&#039;t blame hypervisor technologies just because they&#039;ve been poorly implemented today.  Let&#039;s think about how we can perfect this technology and reap the benefits rather than jump to killing it.  

-Alan]]></description>
		<content:encoded><![CDATA[<p>I think your argument definitely has merit, but don&#8217;t blame the technology just because of the implementation.  Hypervisor-based virtualization brings a tremendous number of benefits, most notably management.  You have to be able to manage virtualization in the server data center, and today that&#8217;s via the hypervisor.  There&#8217;s no better access to data for virtual operating systems than their parent running platform.  Might we someday get to a Softgrid model for server-based applications?  Maybe, but we&#8217;re not even close to it today.  </p>
<p>There are advancements being made in building more intelligent hypervisors, such as Hyper-V and ESX 3i.  I do agree that the hypervisors that most people are using on their desktops today with Virtual Server, VMware Desktop/Workstaion/Server, and Parallels, leave a lot to be desired.  But again, don&#8217;t blame hypervisor technologies just because they&#8217;ve been poorly implemented today.  Let&#8217;s think about how we can perfect this technology and reap the benefits rather than jump to killing it.  </p>
<p>-Alan</p>
]]></content:encoded>
	</item>
</channel>
</rss>
