 




<?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: Linux Kernel 2.6.23 = Win for Xen and KVM and a loss for VMware</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/server-virtualization/linux-kernel-2623-win-for-xen-and-kvm-and-a-loss-for-vmware/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/server-virtualization/linux-kernel-2623-win-for-xen-and-kvm-and-a-loss-for-vmware/</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: BlackHole</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/linux-kernel-2623-win-for-xen-and-kvm-and-a-loss-for-vmware/#comment-1270</link>
		<dc:creator>BlackHole</dc:creator>
		<pubDate>Thu, 10 Jan 2008 00:50:12 +0000</pubDate>
		<guid isPermaLink="false">http://servervirtualization.blogs.techtarget.com/2007/10/10/linux-kernel-2623-win-for-xen-and-kvm-and-a-loss-for-vmware/#comment-1270</guid>
		<description><![CDATA[&quot;[...]There are two solutions to this problem.[...]&quot;
I think the third one might be actually copying the set_dumpable() implementation into the linux/driver.c source file.]]></description>
		<content:encoded><![CDATA[<p>&#8220;[...]There are two solutions to this problem.[...]&#8221;<br />
I think the third one might be actually copying the set_dumpable() implementation into the linux/driver.c source file.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vlad</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/linux-kernel-2623-win-for-xen-and-kvm-and-a-loss-for-vmware/#comment-1269</link>
		<dc:creator>vlad</dc:creator>
		<pubDate>Wed, 24 Oct 2007 14:11:12 +0000</pubDate>
		<guid isPermaLink="false">http://servervirtualization.blogs.techtarget.com/2007/10/10/linux-kernel-2623-win-for-xen-and-kvm-and-a-loss-for-vmware/#comment-1269</guid>
		<description><![CDATA[Well, this has been going on in kernel development for some time already. Check this Linus response : http://lkml.org/lkml/2006/12/13/370
Also note that apparently there was a notice sent in December of last year about GPL compliance for kernel modules. It seems that kernel developers jumped the gun and broke their own deadline. How can we forget that &quot;collaboration&quot; is bad word for Linux kernel hackers. And if someone dares  to use Linux for other work than compiling kernel that marks that person as a worthless fool.
VMware guys are not much better (except petr, :-). They could at least follow Linux Kernel development and post on their web site that new kernel breaks VMware modules on the day of release, so we wouldn&#039;t need to scavenge the web for answers. Every time I upgrade the kernel I have to go through hoops to get VMware server  working again. Vmware 1.0.0.4 fixed many things and worked good until I upgraded last night. I feel like I stepped on a chewing gum - stop, drop everything I was doing and spent a couple hours on something that I could have avoided if I chose different path.]]></description>
		<content:encoded><![CDATA[<p>Well, this has been going on in kernel development for some time already. Check this Linus response : <a href="http://lkml.org/lkml/2006/12/13/370" rel="nofollow">http://lkml.org/lkml/2006/12/13/370</a><br />
Also note that apparently there was a notice sent in December of last year about GPL compliance for kernel modules. It seems that kernel developers jumped the gun and broke their own deadline. How can we forget that &#8220;collaboration&#8221; is bad word for Linux kernel hackers. And if someone dares  to use Linux for other work than compiling kernel that marks that person as a worthless fool.<br />
VMware guys are not much better (except petr, <img src='http://itknowledgeexchange.techtarget.com/server-virtualization/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> . They could at least follow Linux Kernel development and post on their web site that new kernel breaks VMware modules on the day of release, so we wouldn&#8217;t need to scavenge the web for answers. Every time I upgrade the kernel I have to go through hoops to get VMware server  working again. Vmware 1.0.0.4 fixed many things and worked good until I upgraded last night. I feel like I stepped on a chewing gum &#8211; stop, drop everything I was doing and spent a couple hours on something that I could have avoided if I chose different path.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Steven Hack</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/linux-kernel-2623-win-for-xen-and-kvm-and-a-loss-for-vmware/#comment-1268</link>
		<dc:creator>Richard Steven Hack</dc:creator>
		<pubDate>Wed, 17 Oct 2007 20:14:12 +0000</pubDate>
		<guid isPermaLink="false">http://servervirtualization.blogs.techtarget.com/2007/10/10/linux-kernel-2623-win-for-xen-and-kvm-and-a-loss-for-vmware/#comment-1268</guid>
		<description><![CDATA[I find the conspiracy theory unlikely. The kernel maintainers are not in the habit of deliberately breaking software that their users need to run their servers.

What is far more likely is that they did not test the impact of the changes on every piece of third party software out there - including VMWare. This is not surprising.

The GPL module licensing issue is likely a general change, the impact of which on VMWare was either not considered, or more likely, not even known.

Expect a fix from the kernel team shortly - and until then, since this kernel just came out, it&#039;s hardly a big deal. If you&#039;re running servers, you don&#039;t arbitrarily update your kernel unless you really need the enhancements, anyway, so most users running VMWare probably won&#039;t be affected until a kernel fix is implemented.

How that fix will be implemented is a good question, but I doubt it will involve any religious wars on the part of the kernel maintainers. Linus is not into religious wars, and when he sees this problem, it will get fixed.]]></description>
		<content:encoded><![CDATA[<p>I find the conspiracy theory unlikely. The kernel maintainers are not in the habit of deliberately breaking software that their users need to run their servers.</p>
<p>What is far more likely is that they did not test the impact of the changes on every piece of third party software out there &#8211; including VMWare. This is not surprising.</p>
<p>The GPL module licensing issue is likely a general change, the impact of which on VMWare was either not considered, or more likely, not even known.</p>
<p>Expect a fix from the kernel team shortly &#8211; and until then, since this kernel just came out, it&#8217;s hardly a big deal. If you&#8217;re running servers, you don&#8217;t arbitrarily update your kernel unless you really need the enhancements, anyway, so most users running VMWare probably won&#8217;t be affected until a kernel fix is implemented.</p>
<p>How that fix will be implemented is a good question, but I doubt it will involve any religious wars on the part of the kernel maintainers. Linus is not into religious wars, and when he sees this problem, it will get fixed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Schley Andrew Kutz</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/linux-kernel-2623-win-for-xen-and-kvm-and-a-loss-for-vmware/#comment-1267</link>
		<dc:creator>Schley Andrew Kutz</dc:creator>
		<pubDate>Sat, 13 Oct 2007 12:15:27 +0000</pubDate>
		<guid isPermaLink="false">http://servervirtualization.blogs.techtarget.com/2007/10/10/linux-kernel-2623-win-for-xen-and-kvm-and-a-loss-for-vmware/#comment-1267</guid>
		<description><![CDATA[Jim,

You are running Feisty with 2.6.23.1? I would like to talk to you about the process you used to achieve this. My e-mail is akutz BLARG at FUBAR lostcreations dot NOT SPAM com.]]></description>
		<content:encoded><![CDATA[<p>Jim,</p>
<p>You are running Feisty with 2.6.23.1? I would like to talk to you about the process you used to achieve this. My e-mail is akutz BLARG at FUBAR lostcreations dot NOT SPAM com.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/linux-kernel-2623-win-for-xen-and-kvm-and-a-loss-for-vmware/#comment-1266</link>
		<dc:creator>Jim</dc:creator>
		<pubDate>Fri, 12 Oct 2007 22:28:04 +0000</pubDate>
		<guid isPermaLink="false">http://servervirtualization.blogs.techtarget.com/2007/10/10/linux-kernel-2623-win-for-xen-and-kvm-and-a-loss-for-vmware/#comment-1266</guid>
		<description><![CDATA[Actually I am now using 2.6.23.1 and my systems are debian/stable and ubuntu/feisty.  no problems here.

compile your own ...

That said, I do wish that the vmware folks and the kernel folks would work more closely together.  There really is no reason why the new stable kernel should not always work with vmware when it is released.]]></description>
		<content:encoded><![CDATA[<p>Actually I am now using 2.6.23.1 and my systems are debian/stable and ubuntu/feisty.  no problems here.</p>
<p>compile your own &#8230;</p>
<p>That said, I do wish that the vmware folks and the kernel folks would work more closely together.  There really is no reason why the new stable kernel should not always work with vmware when it is released.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Schley Andrew Kutz</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/linux-kernel-2623-win-for-xen-and-kvm-and-a-loss-for-vmware/#comment-1265</link>
		<dc:creator>Schley Andrew Kutz</dc:creator>
		<pubDate>Fri, 12 Oct 2007 16:39:53 +0000</pubDate>
		<guid isPermaLink="false">http://servervirtualization.blogs.techtarget.com/2007/10/10/linux-kernel-2623-win-for-xen-and-kvm-and-a-loss-for-vmware/#comment-1265</guid>
		<description><![CDATA[Jim, 

Against VMware? Are you joking? I am very much in favor of VMware :) Are you sure you are using the 2.6.23 Kernel? It only came out a few days ago. Maybe you think I was implying that VMware Server somehow uses this Kernel. That is not what I meant. Read my response to a similar comment below.

Everyone,

The any-any patch did not work for me on 2.6.23. I was testing it on   FC 8 Test 3 (7.92) after running &quot;yum update&quot; to update the Kernel.

Janardhanan,

I apologize for not clarifying my remarks. I am referring to a Linux distro that uses 2.6.23 that you install VMware Server on. Does that help clear things up?]]></description>
		<content:encoded><![CDATA[<p>Jim, </p>
<p>Against VMware? Are you joking? I am very much in favor of VMware <img src='http://itknowledgeexchange.techtarget.com/server-virtualization/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  Are you sure you are using the 2.6.23 Kernel? It only came out a few days ago. Maybe you think I was implying that VMware Server somehow uses this Kernel. That is not what I meant. Read my response to a similar comment below.</p>
<p>Everyone,</p>
<p>The any-any patch did not work for me on 2.6.23. I was testing it on   FC 8 Test 3 (7.92) after running &#8220;yum update&#8221; to update the Kernel.</p>
<p>Janardhanan,</p>
<p>I apologize for not clarifying my remarks. I am referring to a Linux distro that uses 2.6.23 that you install VMware Server on. Does that help clear things up?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/linux-kernel-2623-win-for-xen-and-kvm-and-a-loss-for-vmware/#comment-1263</link>
		<dc:creator>Jim</dc:creator>
		<pubDate>Fri, 12 Oct 2007 14:15:16 +0000</pubDate>
		<guid isPermaLink="false">http://servervirtualization.blogs.techtarget.com/2007/10/10/linux-kernel-2623-win-for-xen-and-kvm-and-a-loss-for-vmware/#comment-1263</guid>
		<description><![CDATA[I don&#039;t know why you are so against vmware.  I find it to be a tremendous linux advocate and am proud and happy to be using it.  In response to your compiler concerns, I am happily using vmware-server-1.0.4, along with the vmware-any-any-update113 patches (documented many places) on no less than 5 machines without issue (all running windows-xp).]]></description>
		<content:encoded><![CDATA[<p>I don&#8217;t know why you are so against vmware.  I find it to be a tremendous linux advocate and am proud and happy to be using it.  In response to your compiler concerns, I am happily using vmware-server-1.0.4, along with the vmware-any-any-update113 patches (documented many places) on no less than 5 machines without issue (all running windows-xp).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Janardhanan PS</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/linux-kernel-2623-win-for-xen-and-kvm-and-a-loss-for-vmware/#comment-1262</link>
		<dc:creator>Janardhanan PS</dc:creator>
		<pubDate>Fri, 12 Oct 2007 08:02:13 +0000</pubDate>
		<guid isPermaLink="false">http://servervirtualization.blogs.techtarget.com/2007/10/10/linux-kernel-2623-win-for-xen-and-kvm-and-a-loss-for-vmware/#comment-1262</guid>
		<description><![CDATA[Which version of VMware Server uses Kernel 2.6.23  ?.
ESX server 3.0.2 uses Linux version 2.4.21-47.0.1 

What is missing here.]]></description>
		<content:encoded><![CDATA[<p>Which version of VMware Server uses Kernel 2.6.23  ?.<br />
ESX server 3.0.2 uses Linux version 2.4.21-47.0.1 </p>
<p>What is missing here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ++Don</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/linux-kernel-2623-win-for-xen-and-kvm-and-a-loss-for-vmware/#comment-1256</link>
		<dc:creator>++Don</dc:creator>
		<pubDate>Thu, 11 Oct 2007 15:34:11 +0000</pubDate>
		<guid isPermaLink="false">http://servervirtualization.blogs.techtarget.com/2007/10/10/linux-kernel-2623-win-for-xen-and-kvm-and-a-loss-for-vmware/#comment-1256</guid>
		<description><![CDATA[I like how they took away an existing functionality that isn&#039;t GPL-wrapped and replaced it with one that is. That message from the linux-kernel mailing list mentions killer penguins with chainsaws coming after anyone who applies EXPORT_SYMBOL_GPL to existing interfaces. Well that&#039;s easy to fix! Just get rid of the existing interface and replace it with something else.

Many of these people are the same ones who refuse to define a consistent kernel-module API specifically to hinder the development of binary blob kernel modules. They make noise about wanting the freedom to refactor kernel internals without having to support a legacy API*, but they also freely admit that it&#039;s as much religious as technical: they want to force the proprietary module developers to put their modules into the mainline kernel source (and yes, I&#039;ve read this exact sentiment expressed on public mailing lists by Linux kernel developers, so I&#039;m not making this up).

*The technical issue is a red herring. They could do what Apple started doing in OS X 10.4: standardize the kernel API in a structured way that facilitates deprecating old APIs when the time comes, but at the same time keeping them around for a certain length of time to give module authors time to update their code. It takes more time to get rid of an old API this way, but it still works.

I call this &quot;religious-based programming&quot;: &quot;You&#039;re not allowed to use my API unless you believe the same way I do.&quot; It seems to afflict people who care more about their forcing their views on others than about producing software that anyone can use. That l-k message you reference demonstrates it better than I ever could:

&gt; Some kernel developers are unhappy with providing external interfaces 
&gt; to their code, only to see those interfaces being used by binary only 
&gt; modules. They view it as their work being appropriated. Whether you 
&gt; agree with that view or not is completely irrelevant, the person who 
&gt; owns the copyright decides how their work can be used. 

I fail to see how this attitude of selfish arrogance is any different than the attitude of the movie and music industries, which seek to use ever more restrictive forms of DRM to control all aspects of how consumers make use of their content. EXPORT_SYMBOL_GPL is essentially a form of DRM: &quot;You can only use this API in ways that I allow you to.&quot;

This is all quite ironic, or perhaps hypocritical, since the religion in question claims to be all about freedom. These people particularly despise DRM when the content companies use it, but they&#039;re completely blind to the fact that they&#039;re doing the same thing themselves. I guess it&#039;s OK for them to do it because they have purer motives.

And no, I don&#039;t dislike the GPL, I just dislike how some people choose to use it as a sledge hammer to bludgeon non-believers. It&#039;s people like us, who just want to Make Things Go, who end up paying the price.]]></description>
		<content:encoded><![CDATA[<p>I like how they took away an existing functionality that isn&#8217;t GPL-wrapped and replaced it with one that is. That message from the linux-kernel mailing list mentions killer penguins with chainsaws coming after anyone who applies EXPORT_SYMBOL_GPL to existing interfaces. Well that&#8217;s easy to fix! Just get rid of the existing interface and replace it with something else.</p>
<p>Many of these people are the same ones who refuse to define a consistent kernel-module API specifically to hinder the development of binary blob kernel modules. They make noise about wanting the freedom to refactor kernel internals without having to support a legacy API*, but they also freely admit that it&#8217;s as much religious as technical: they want to force the proprietary module developers to put their modules into the mainline kernel source (and yes, I&#8217;ve read this exact sentiment expressed on public mailing lists by Linux kernel developers, so I&#8217;m not making this up).</p>
<p>*The technical issue is a red herring. They could do what Apple started doing in OS X 10.4: standardize the kernel API in a structured way that facilitates deprecating old APIs when the time comes, but at the same time keeping them around for a certain length of time to give module authors time to update their code. It takes more time to get rid of an old API this way, but it still works.</p>
<p>I call this &#8220;religious-based programming&#8221;: &#8220;You&#8217;re not allowed to use my API unless you believe the same way I do.&#8221; It seems to afflict people who care more about their forcing their views on others than about producing software that anyone can use. That l-k message you reference demonstrates it better than I ever could:</p>
<p>&gt; Some kernel developers are unhappy with providing external interfaces<br />
&gt; to their code, only to see those interfaces being used by binary only<br />
&gt; modules. They view it as their work being appropriated. Whether you<br />
&gt; agree with that view or not is completely irrelevant, the person who<br />
&gt; owns the copyright decides how their work can be used. </p>
<p>I fail to see how this attitude of selfish arrogance is any different than the attitude of the movie and music industries, which seek to use ever more restrictive forms of DRM to control all aspects of how consumers make use of their content. EXPORT_SYMBOL_GPL is essentially a form of DRM: &#8220;You can only use this API in ways that I allow you to.&#8221;</p>
<p>This is all quite ironic, or perhaps hypocritical, since the religion in question claims to be all about freedom. These people particularly despise DRM when the content companies use it, but they&#8217;re completely blind to the fact that they&#8217;re doing the same thing themselves. I guess it&#8217;s OK for them to do it because they have purer motives.</p>
<p>And no, I don&#8217;t dislike the GPL, I just dislike how some people choose to use it as a sledge hammer to bludgeon non-believers. It&#8217;s people like us, who just want to Make Things Go, who end up paying the price.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Petr Vandrovec</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/linux-kernel-2623-win-for-xen-and-kvm-and-a-loss-for-vmware/#comment-1257</link>
		<dc:creator>Petr Vandrovec</dc:creator>
		<pubDate>Thu, 11 Oct 2007 04:22:15 +0000</pubDate>
		<guid isPermaLink="false">http://servervirtualization.blogs.techtarget.com/2007/10/10/linux-kernel-2623-win-for-xen-and-kvm-and-a-loss-for-vmware/#comment-1257</guid>
		<description><![CDATA[You could also find that vmware-any-any-update111.tar.gz, which I released on July 22nd (current one is update 113, http://platan.vc.cvut.cz/ftp/pub/vmware/vmware-any-any-update113.tar.gz) solves both problems you mention.]]></description>
		<content:encoded><![CDATA[<p>You could also find that vmware-any-any-update111.tar.gz, which I released on July 22nd (current one is update 113, <a href="http://platan.vc.cvut.cz/ftp/pub/vmware/vmware-any-any-update113.tar.gz" rel="nofollow">http://platan.vc.cvut.cz/ftp/pub/vmware/vmware-any-any-update113.tar.gz</a>) solves both problems you mention.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
