<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi<br>
<br>
Lars Marowsky-Bree wrote:
<blockquote cite="mid:20090129120044.GT16895@suse.de" type="cite">
<pre wrap="">On 2009-01-29T11:57:53, Igor Neves <a class="moz-txt-link-rfc2396E" href="mailto:igor@3gnt.net"><igor@3gnt.net></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi,
Yes I have seen and I know that the module that don't loads correctly
it's from vmware.
</pre>
</blockquote>
<pre wrap=""><!---->
Well, so, on the node which is not currently primary, you're not running
the VMs, right? So, how about trying to see if it does not crash if
vmware is never loaded at all?
</pre>
</blockquote>
<br>
Yes, i was not running the virtual machine, but vmware was running.
Anyway, I have this vmware running in other places without problems, so
as half of the world! :)<br>
<br>
Yes i will do that too, and i will be investigating and working on
changing the virtualization plataform. I know there are much better
alternatives, but i don't have much time to try them out. Now i will be
forced to have. heheh.<br>
<br>
<blockquote cite="mid:20090129120044.GT16895@suse.de" type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">The problem with the module it's that it complains about it's license.
Vmware configure script try to load the module when configuring it and
and it says it loads OK, but kernel complains about license.
</pre>
</blockquote>
<pre wrap=""><!---->
Of course. vmware is a GPL violation, so the kernel rightfully complains
...
</pre>
</blockquote>
<br>
Yes.<br>
<br>
<blockquote cite="mid:20090129120044.GT16895@suse.de" type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">I'm just remembering now, that centos crew they recently change
kmod-drbd package politics, before they had one rpm for each kernel they
sent out. Now the same rpm it's for all the kernels. Can that be the
problem?
</pre>
</blockquote>
<pre wrap=""><!---->
Not sure. You'd see from the logs at boot time - when the modules are
initially loaded - which module load causes the taint flags to be set.
</pre>
</blockquote>
<br>
Yes, no doubts, it's vmware.<br>
<br>
vsock: no version for "VMCIDatagram_Send" found: kernel tainted.<br>
<br>
<blockquote cite="mid:20090129120044.GT16895@suse.de" type="cite">
<pre wrap="">Regards,
Lars
</pre>
</blockquote>
<br>
Cheers,<br>
Igor Neves<br>
</body>
</html>