[Thincrust-devel] generating scsi disks
Bryan Kearney
bkearney at redhat.com
Mon Jan 12 14:46:21 UTC 2009
Alan Pevec wrote:
>
>
> On Thu, Jan 8, 2009 at 9:05 PM, Bryan Kearney <bkearney at redhat.com
> <mailto:bkearney at redhat.com>> 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
>
>
> kickstart has 'device' directive which should add the kmod to initrd:
> device kmod_name
>
> example usage:
> http://git.et.redhat.com/?p=ovirt-node-image.git;a=blob;f=common-install.ks;hb=refs/heads/next#l13
>
> but you need livecd-tools fix past 020 tag (so not in Fedora RPM yet):
> http://git.fedorahosted.org/git/?p=livecd;a=commitdiff;h=b98ad7391cef406967636f4fba7e3d5d2602e83f
Huff.. I thin kthis modedl is better as it keeps the external metadata
to a minimum.
-- bk
More information about the Thincrust-devel
mailing list