Re: [Qemu-devel] bug (?) related to kqemu and/or Minix3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mulyadi Santosa wrote: Hi... The screen capture didn't show anything suspicious...maybe the issue is related to segmentation? Linux...AFAIK doesn't use CS segment that much in GDT I do not know. What I was trying to say is that it is weird if Minix (note that I was not meaning Linux) works fine: - - on bare hardware - - on QEMU (without kqemu) but does not work on QEMU with kqemu. Minix developers say that it is bug somewhere in kqemu. Bug in Minix is not relevant (to others) but if it revealed some bug in kqemu, this may be interesting to other operating systems too. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHxWE0L+CaXfJI/hgRAiqyAJ9nbsEykKH+TD5+sZConKmawrmiYwCeJMh/ Lry0bXR43uIcqN2X2DNWC1w= =xjFW -END PGP SIGNATURE-
[Qemu-devel] bug (?) related to kqemu and/or Minix3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I (and others) have observed the following problem with kqemu If you take Minix3 harddisk image such as: http://altair.sk/uploads/minix.img.gz and if you try to boot it via QEMU without kqemu qemu -hda minix.img -no-kqemu there are no problems. http://altair.sk/uploads/no-problem.png However, if you do the same but you try to use kqemu qemu -hda minix.img booting of the kernel halts in the middle. http://altair.sk/uploads/problem.png Do you think that this is a bug in Minix or in kqemu module? Best regards - -- Matej -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHw+aQL+CaXfJI/hgRAlepAJ4hqKv1P51pm+k/rebxNHCzaTW7iACgwKrT Rgv4l+3YW2CJybke119obEI= =0veM -END PGP SIGNATURE-
