On Jan 17, 2008 3:52 PM, fishor <email address hidden> wrote:
> Hmm.. Seems like this is not kvm issue. ata_piix modules was not loaded
> so it can't find you hdd( image ).
This means that prior to booting the guest install image, I added
"ata_piix.blacklist=yes" to the kernel options - and proceeded with a
normal command line installation.
As I was able to see the hd during installation I possibly wrongly
assumed that the driver was available, I did not take the time to
investigate the actual semantics of this option ... does this make
sense ?
On Jan 17, 2008 3:52 PM, fishor <email address hidden> wrote:
> Hmm.. Seems like this is not kvm issue. ata_piix modules was not loaded
> so it can't find you hdd( image ).
OK, this rings a bell. As I mentioned at the very top, I was "working /bugs.launchpad .net/ubuntu/ +source/ linux-source- 2.6.22/ +bug/120316/ comments/ 7"
around the cdrom detection problem using
https:/
This means that prior to booting the guest install image, I added blacklist= yes" to the kernel options - and proceeded with a
"ata_piix.
normal command line installation.
As I was able to see the hd during installation I possibly wrongly
assumed that the driver was available, I did not take the time to
investigate the actual semantics of this option ... does this make
sense ?
"Peter Dahl Vestergaard" <email address hidden>