Vmware tools installed the pvscsi library. But does not automatically
reconfigure the boot/kernel to use it.
Here is a good web page that explains the steps to remake the initrd. Once
you have done that under settings in
the vSphere Client change the SCSI controller setting to Paravirtual. I
think that the pvscsi lib will be included
in a forth coming linux kernel tree, which will make having to add this
manually, obsolete. Not sure when that will
be. I wish VMware would automate this as part of the install or P2V process.
http://vmadmin.nt.com.au/?p=28
-Mike
-----Original Message-----
From: centos-bounces@xxxxxxxxxx [mailto:centos-bounces@xxxxxxxxxx] On Behalf
Of Les Mikesell
Sent: Friday, February 05, 2010 1:36 PM
To: centos@xxxxxxxxxx
Subject: Re: VMWare ESXi & CentOS5.4
On 2/5/2010 12:25 PM, Michael Dross wrote:
> I have recently installed ESXi4 on a new HP DL380 G6 with 12GB of memory.
> I am running CentOS 5.4 and CentOS 4.8. A few things I have learned.
>
> First, for best I/O performance you should use the Vmware Paravirtualized
> storage controller driver. It's a little bit of a hassle setting it up.
> You just have to remake the initrd file. This will give about 10% better
> disk I/O than using the other emulated controllers.
Does this happen by itself if you've installed vmware tools in the guest
and then get a kernel update that triggers an initrd rebuild or do you
have to do something to specify the right module to include?
--
Les Mikesell
lesmikesell@xxxxxxxxx
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
