If you need to revert for any reason, simply boot back into rescue mode and revert /etc/nf and the initrd-*.img file, then reboot. This package installs an updated version of the Microsoft Windows XP device driver for LSI SAS Storage Controller that comes preinstalled in your computer. mkinitrd -v -f /boot/initrd-*.img * (replace both instances of * with actual version number in the file you just renamed).Boot the system into rescue mode from the installation disc and chroot /mnt/sysimageīackup your /etc/nf file and replace any scsi_hostadapter entries in it with the following:.To resolve this, you'll need to rebuilt the initrd file using the following procedure:
If that initial ram disk file doesn't contain the drivers for your system, the system will not able to boot. The problem is that, when the system boots up, an initial ram disk is created from the contents of a file which contains certain drivers the system needs to continue booting. Follow the Found New Hardware wizard or the Windows device manager inside the Windows guest and provide location of the LSILogic SCSI controller driver. It's likely you are going the opposite way, but you just need to change the driver type:Īfter doing this, shut down and remove the 1 GB temporary disk.Ĭhange the controller for the root disk to whatever driver you just added to the ramdisk, and boot up the system. Third step - run the following command to add the correct driver to the RamDisk (Remember in my case I was moving from the VMWare Paravirtual to the LSI Logic SAS driver. Second step - Shut down your VM, Attach a 1 GB disk using the SCSI controller type you'd like to change your root disk to and bring the system back up to modprobe discover it. You may not need to do this second step, I did it in the theory that the disk controller would initialize itself if introduced to the system through an additional disk, just like you'd do for Windows: Whenever you are working with disks, it's best not to involve snapshots. I/O operation compared to that of the LSI Logic SAS virtual SCSI controller. As the previous posts suggest, this needs to be done in two places, the regular disk and the RamDisk as both will need to boot with the new driver.įirst, if possible, clone your machine, don't snapshot it. paravirtual scsi driver to get the best performance possible from them. disk of the machine (chose both IDE and SCSI drivers, but none worked). In my case I needed to change the controller for the root disk from Paravirtual to LSI Logic SAS. These characteristics are expected to repeat for most I/O device drivers and operating systems since they stem. 1 (LSI SAS, pvSCSI) latest QCOW2 is a storage format for virtual disks. In RHEL 7.x this is a bit different as nf doesn't exist.