[Thincrust-devel] generating scsi disks

[Bryan Kearney]

Resending a bounced message.

Finally, here is the result:

the error message I received during the boot was this:

error mounting /dev/root on /sysroot...
In this case the problem was caused by two different things:

1) missing driver - I had to put mptspi into the initrd
2) bug 466607 (https://bugzilla.redhat.com/show_bug.cgi?id=466607) in f10 -
    even though the corrected versions of mkinitrd and nash (on both the 
development system and the thincrust system) that are supposed to fix 
the bug were installed, I still had to load scsi_wait_scan in the initrd

Now, how can we do this directly in appliance-creator? One of the 
comments (#67) rebuilt the initrd in the %post section of the kickstart 
file. The previous comment to this thread suggests that the list of 
modules for initrd in appliance-creator can be modified? For vmware, we 
always need mptspi (at least for esxi) so it would be a good choice to 
be included in the standard modules.

Thanks for your help.

Mike

Bryan Kearney wrote:
 > David Huff wrote:
 >> David Huff wrote:
 >>> Technically you could modify the vmx file to present the disk to 
vmware as a scis disk, which should work, since the scsi drivers are 
loaded in the the ramdisk and everything need to use a scsi disk should 
be on the image.
 >>
 >> This is not %100 correct, I did have to add the sym53c8xx module to 
the initrd in order to boot the disk image created with 
appliance-creator as a scsi disk in kvm.
 >>
 >> Now the question is should this module be added to the default 
module list that get loaded via appliance-creator, or do we need to add 
the functionality where the module list can be customized as an argument?
 >
 > +1 for a new command line option
 >
 > -- bk
 >
 > _______________________________________________
 > Thincrust-devel mailing list
 > Thincrust-devel at redhat.com
 > https://www.redhat.com/mailman/listinfo/thincrust-devel
	
Mike Schmidt <mike at intello.com>
Vice-President
R&D
Intello Technologies Inc.