Re: [ANNOUNCE] kvm-72 release

["Henrik Holst" <henrik@witsbits.com>]

2008/7/28 Henrik Holst <henrik@witsbits.com>:
>> Since this probably is due to something in qemu it would be great if
>> the release-log to kvm could include towards which revision of the
>> qemu svn repository that was merged. Or am I to understand that the
>> merge was performed on the same day as the new kvm release was
>> released?
>>
>> I'm thinking of this line:
>>  - merge qemu-svn
>>
>> That way I could myself begin to hunt down the culprit patch to qemu
>> much more easily. Also the qemu version in kvm seams to contain some
>> internal patches? I noted that -drive has an "boot" option (in vl.c)
>> in kvm which is not present in qemu-svn (atleast not in trunk).
>>
>
> I have now tried with qemu-svn and that won't even boot up a scsi drive at all!
>
> This will present a bios which founds no boot devices at all:
>  qemu -m 256 -drive file=test.img,if=scsi,media=disk -boot c
>
> While this will boot just fine:
>  qemu -m 256 -drive file=test.img,if=ide,media=disk -boot c
>
> So I will have to dig into previous revisions of qemu to see where it
> went wrong.
>
> /Henrik Holst
>

I have now tracked down the regression to extboot.bin, changing it to
the version from kvm-71 makes it all work just fine again. Will try
and find where in the code the regression is, sounds like it is the
recent extboot patches though.

/Henrik Holst