<?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: Installing and using pvscsi in Red Hat and CentOS 5.3 under vSphere 4</title>
	<atom:link href="http://vmadmin.nt.com.au/?feed=rss2&#038;p=28" rel="self" type="application/rss+xml" />
	<link>http://vmadmin.nt.com.au/?p=28</link>
	<description>Useful Stuff we find interesting ...so should you!</description>
	<lastBuildDate>Sat, 09 Jan 2010 19:35:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Sven Lankes</title>
		<link>http://vmadmin.nt.com.au/?p=28&#038;cpage=1#comment-621</link>
		<dc:creator>Sven Lankes</dc:creator>
		<pubDate>Sat, 09 Jan 2010 19:35:31 +0000</pubDate>
		<guid isPermaLink="false">http://vmadmin.nt.com.au/?p=28#comment-621</guid>
		<description>Type your comment here&lt;blockquote cite=&quot;#comment-body-127&quot;&gt;
&lt;strong&gt;&lt;a href=&quot;#comment-127&quot; rel=&quot;nofollow&quot;&gt;Chris Lukas&lt;/a&gt; :&lt;/strong&gt;                       
         the real question is how to make the new boot controller permanently added to initrd…
         &lt;a&gt;&lt;/a&gt;
       &lt;/blockquote&gt;

Creating a file /etc/sysconfig/mkinitrd/vmware with:

  MODULES=&quot;pvscsi&quot;

should do the trick.</description>
		<content:encoded><![CDATA[<p>Type your comment here<br />
<blockquote cite="#comment-body-127">
<strong><a href="#comment-127" rel="nofollow">Chris Lukas</a> :</strong><br />
         the real question is how to make the new boot controller permanently added to initrd…<br />
         <a></a>
       </p></blockquote>
<p>Creating a file /etc/sysconfig/mkinitrd/vmware with:</p>
<p>  MODULES=&#8221;pvscsi&#8221;</p>
<p>should do the trick.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Installing RHEL 5 using the VMware Paravirtualized SCSI driver (pvscsi) &#124; Tork Wrench</title>
		<link>http://vmadmin.nt.com.au/?p=28&#038;cpage=1#comment-619</link>
		<dc:creator>Installing RHEL 5 using the VMware Paravirtualized SCSI driver (pvscsi) &#124; Tork Wrench</dc:creator>
		<pubDate>Wed, 06 Jan 2010 02:26:29 +0000</pubDate>
		<guid isPermaLink="false">http://vmadmin.nt.com.au/?p=28#comment-619</guid>
		<description>[...] Redhat&#8217;s excellent kickstart system. If you are just interested in doing this on one system, I would follow these steps instead . My steps are good if you want to automate this procedure over many machines, but it probably [...]</description>
		<content:encoded><![CDATA[<p>[...] Redhat&#8217;s excellent kickstart system. If you are just interested in doing this on one system, I would follow these steps instead . My steps are good if you want to automate this procedure over many machines, but it probably [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Lukas</title>
		<link>http://vmadmin.nt.com.au/?p=28&#038;cpage=1#comment-127</link>
		<dc:creator>Chris Lukas</dc:creator>
		<pubDate>Wed, 29 Jul 2009 16:07:16 +0000</pubDate>
		<guid isPermaLink="false">http://vmadmin.nt.com.au/?p=28#comment-127</guid>
		<description>the real question is how to make the new boot controller permanently added to initrd...</description>
		<content:encoded><![CDATA[<p>the real question is how to make the new boot controller permanently added to initrd&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Lukas</title>
		<link>http://vmadmin.nt.com.au/?p=28&#038;cpage=1#comment-126</link>
		<dc:creator>Chris Lukas</dc:creator>
		<pubDate>Wed, 29 Jul 2009 14:10:19 +0000</pubDate>
		<guid isPermaLink="false">http://vmadmin.nt.com.au/?p=28#comment-126</guid>
		<description>great tip....tried it on CentOS 4.7, worked great.
it boils down to:
1) install the VMware tools
2) mkinitrd -f --with=pvscsi  (rest of line from your tip)
    (-f forces overwrite)
3) shutdown, change the boot adapter type in VMware
4) boot, if you get a re-config screen, remove the old hardware</description>
		<content:encoded><![CDATA[<p>great tip&#8230;.tried it on CentOS 4.7, worked great.<br />
it boils down to:<br />
1) install the VMware tools<br />
2) mkinitrd -f &#8211;with=pvscsi  (rest of line from your tip)<br />
    (-f forces overwrite)<br />
3) shutdown, change the boot adapter type in VMware<br />
4) boot, if you get a re-config screen, remove the old hardware</p>
]]></content:encoded>
	</item>
</channel>
</rss>
