On 24.03.2011, at 05:41, David Gibson wrote: > On Wed, Mar 23, 2011 at 10:29:04PM +0100, Alexander Graf wrote: >> >> On 23.03.2011, at 22:08, Benjamin Herrenschmidt wrote: >> >>> On Wed, 2011-03-23 at 15:45 +0100, Alexander Graf wrote: >>>> >>>> What's the magic to start a guest? I tried passing a disk which SLOF >>>> didn't detect (obviously - there's no IDE there). I also tried running >>>> a kernel directly with -kernel which gave me no output. How are you >>>> usually running your images? >>> >>> hrm... you using -M pseries right ? >> >> Yup >> >>> so -kernel should work with a kernel that is compiled for the pseries >>> platform (and it won't use SLOF). >> >> Yeah, that part works. >> >>> >>> a disk should work with SLOF if you use the default which is scsi (ie >>> pseries machine sets that flag that tells qemu to default to scsi, which >>> is then picked up by our vscsi). >>> >>> IE. You should be able to stick a distro ISO in the virtual CD-ROM and >>> boot from that with SLOF. SLOF will read the qemu boot list (tho it only >>> knows about "c", "d" and "n" at that stage) and try them in order. >> >> That one doesn't. If I just pass in a disk w/o specifically saying >> it's a scsi disk I end up with no hard disk in the guest :). > > Um.. what exact command line are you using? For me, both -hda <file> > and a bare <file> on the command line work...
Ah, yes. It's the amount of RAM. I didn't pass in -m before which made SLOF not detect the SCSI adapter but crash before that. So yes, please add a min_ram field. Alex
