Can’t boot a kernel on a SCSI device if you don’t load the SCSI device first, can you!? mkinitrd is easy, if not a little cumbersome, to use.
#HP CCISS CENTOS DRIVER DRIVERS#
Now, there’s no point in specifying a driver for which your kernel doesn’t have the appropriate module! For this reason, we’ll need to rebuild your initrd, which you can think of as being a small package that contains drivers - drivers necessary to boot your kernel. We do this, of course, because vSphere presents its virtualized storage device as being equivalent to an LSI Logic device, which is supported in your VM’s OS by the mptbase driver bundle. Such an example is alias_scsihostadapter 1. If there are any other SCSI-related entries in the modules file, remove them. Now, you’ll need to edit /etc/nf on the VM, and make its only SCSI configuration entry read like this: For vSphere, you have two (okay, three or four, really) choices: LSI Logic, BusLogic (or PVSCI, I guess.) BusLogic is more suited to older VMs running older OSs, so let’s choose LSI Logic. CentOS’ rescue disc does a chroot for you by default, but RHEL will not - so you need to enter something like chroot /mnt/sysimage (where /mnt/sysimage is the location of your VM’s filesystem(s), not the rescue disc’s filesystem(s)!) SCSI driverįirst things first, we need a SCSI driver that’s going to work. Note that these all need to be done in a chrooted environment. Mount the filesystems of your P2Ved VM, and then run the following. Once we’re there, a few relatively simple commands get us to where we need to be. It’s relatively easy to fix, though, so don’t worry! The easiest way to accomplish this is to boot the “new” Linux VM after it’s P2Ved - and when I say “boot”, I mean “boot via the Linux rescue CD that’s relevant for that OS.” So, for CentOS 2.1, I power on the new VM but boot it off the CentOS rescue disc. So, when you boot up the VM, you get a nice “NO OPERATING SYSTEM FOUND” message or something similar.
#HP CCISS CENTOS DRIVER INSTALL#
Out of the box, because VMware Converter can’t figure out what distribution you’re using, it can’t/won’t/doesn’t install the correct drivers when you P2V your old, busted Linux host. (I haven’t tried, but if anyone wants me to, just holler.) Given that CentOS is binary-compatible with RHEL, it’s very possible that you could simply edit /etc/redhat-release on the CentOS box to mirror what’s on a RHEL box and be done with it. However, I assumed that, and it turned out I was wrong. For example, I recently had to P2V a CentOS 2.1 VM, which you would assume would appear to vSphere as a Red Hat Enterprise Linux 2.1 VM, seeing as the two distributions are binary-compatible.
Occasionally, you will need to P2V a physical Linux machine that doesn’t quite match up with the accepted configuration defaults for vSphere - particularly, a distribution (or even a fork of a distribution) that’s not 100% supported.
0 kommentar(er)
