This is caused by qemu using the PC-BIOS from the bochsbios package instead of the one packages with the qemu tarball. It's from bochs, but a much more recent CVS version.
if this is the case, then there should be two versions of the bochsbios package (similar to what is done for python, the kernel, gcc, etc). one version should be bochsbios2.1 (that supports the current bochs release in testing and whatever other apps depend on that version) and another should be bochsbios2.3 (that supports the latest needs of qemu 0.8.2). this is a pretty big problem, and i think that the "-kernel-kqemu" option should be disabled until it is fixed. i wouldn't want to see etch released with a major bug like this. mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
