<?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"
	>
<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 blog</description>
	<pubDate>Thu, 26 Nov 2009 20:09:44 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Linux Kernel 2.6.24 released - Enterprise Linux Log</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/linux-kernel-2623-win-for-xen-and-kvm-and-a-loss-for-vmware/#comment-1272</link>
		<dc:creator>Linux Kernel 2.6.24 released - Enterprise Linux Log</dc:creator>
		<pubDate>Fri, 06 Jun 2008 13:07:31 +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-1272</guid>
		<description>[...] - Licensing changes, which forces one to redact certain bits from the stock kernel (see my previous SVV blog post on 2.6.23 and VMware) [...]</description>
		<content:encoded><![CDATA[<p>[...] - Licensing changes, which forces one to redact certain bits from the stock kernel (see my previous SVV blog post on 2.6.23 and VMware) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Linux Kernel 2.6.24 released &#8212; Enterprise Linux Log</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/linux-kernel-2623-win-for-xen-and-kvm-and-a-loss-for-vmware/#comment-1271</link>
		<dc:creator>Linux Kernel 2.6.24 released &#8212; Enterprise Linux Log</dc:creator>
		<pubDate>Wed, 30 Jan 2008 13:43:59 +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-1271</guid>
		<description>[...] - Licensing changes, which forces one to redact certain bits from the stock kernel (see my previous SVV blog post on 2.6.23 and VMware) [...]</description>
		<content:encoded><![CDATA[<p>[...] - Licensing changes, which forces one to redact certain bits from the stock kernel (see my previous SVV blog post on 2.6.23 and VMware) [...]</p>
]]></content:encoded>
	</item>
	<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>"[...]There are two solutions to this problem.[...]"
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>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 "collaboration" 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'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 :&nbsp;&lt;a href="http://lkml.org/lkml/2006/12/13/370" title="http://lkml.org/lkml/2006/12/13/370" target="_blank"&gt;http://lkml.org/lkml/2006/12/13/370&lt;/a&gt;<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, :-). 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 - 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>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's hardly a big deal. If you're running servers, you don't arbitrarily update your kernel unless you really need the enhancements, anyway, so most users running VMWare probably won'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 - 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 - 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>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>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>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 "yum update" 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: The New Linux Kernel kicks WMware&#8217;s ass &#187; Krillz.com</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/linux-kernel-2623-win-for-xen-and-kvm-and-a-loss-for-vmware/#comment-1264</link>
		<dc:creator>The New Linux Kernel kicks WMware&#8217;s ass &#187; Krillz.com</dc:creator>
		<pubDate>Fri, 12 Oct 2007 14:19:26 +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-1264</guid>
		<description>[...] More details on this can be found here: Win for Xen and KVM and a loss for VMware    Share with the world: These icons link to social bookmarking sites where readers can share and discover new web pages. [...]</description>
		<content:encoded><![CDATA[<p>[...] More details on this can be found here: Win for Xen and KVM and a loss for VMware    Share with the world: These icons link to social bookmarking sites where readers can share and discover new web pages. [...]</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>I don'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>
</channel>
</rss>
<!-- dynamic -->