The bug still exists in qemu 2.7 (version present in my debian stretch).
I was not able reproduce the bug with booting kernel directly with 2.7 (-kernel ...), but booting disk image causes the bug.
So, I have debian gnu/linux stretch amd64. debian package qemu-system-x86 1:2.7+dfsg-3+b1. I run my host system in qemu (i. e. I run in qemu same system that running on the host) using well known "-snapshot -drive file=/dev/sda" trick. Precise command line is:
Qemu appears and I see usual "SeaBIOS (version 1.9.3-20161025_171302-gandalf)" as you can see at screenshot Screenshot_20161216_005817.png .
Then qemu switches to grub.
And then qemu switches to text mode back. And fsck prints to console: "/dev/sda2: recovering journal", but this words appears on top of that SeaBIOS self-adver., so we have the following words mixture:
/dev/sda2: recovering journal25_171302-gandalf)
I use sdl. I don't know build option, this is qemu from debian package
The bug still exists in qemu 2.7 (version present in my debian stretch).
I was not able reproduce the bug with booting kernel directly with 2.7 (-kernel ...), but booting disk image causes the bug.
So, I have debian gnu/linux stretch amd64. debian package qemu-system-x86 1:2.7+dfsg-3+b1. I run my host system in qemu (i. e. I run in qemu same system that running on the host) using well known "-snapshot -drive file=/dev/sda" trick. Precise command line is:
kdesudo -c "exec qemu-system-x86_64 -m 1024M -enable-kvm -daemonize -snapshot -drive file=/dev/ sda,cache= none,format= raw"
Qemu appears and I see usual "SeaBIOS (version 1.9.3-20161025_ 171302- gandalf) " as you can see at screenshot Screenshot_ 20161216_ 005817. png .
Then qemu switches to grub.
And then qemu switches to text mode back. And fsck prints to console: "/dev/sda2: recovering journal", but this words appears on top of that SeaBIOS self-adver., so we have the following words mixture:
/dev/sda2: recovering journal25_ 171302- gandalf)
I use sdl. I don't know build option, this is qemu from debian package