g is reproducible with standard Debian kernels (if we use them as guests).
Reproduction steps are so:
- Install Debian Trixie to Qemu VM
- Boot it with "init=/bin/true" added (to cause kernel panic)
You will not see panic message.
I minimized this Debian bug to small config shown in the
The bug is not present in Qemu 2.12 (version reported by dpkg: qemu-
system-x86 1:2.12+dfsg-1+b1). There is similar minor bug instead. The
new bug doesn't harm me and I am not even sure is this a bug.
So, this is info about new minor bug.
Host is Debian Sid installed today (23 May MSK) with menti
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 m
And this is Screenshot_20161216_005917.png . Here (after grub) we see
"recovering journal" on top of seabios string
** Attachment added: "Screenshot_20161216_005917.png"
https://bugs.launchpad.net/qemu/+bug/922076/+attachment/4792206/+files/Screenshot_20161216_005917.png
--
You received this
This is Screenshot_20161216_005859.png , screenshot with grub
** Attachment added: "Screenshot_20161216_005859.png"
https://bugs.launchpad.net/qemu/+bug/922076/+attachment/4792205/+files/Screenshot_20161216_005859.png
--
You received this bug notification because you are a member of qemu-
de
** Description changed:
- When I start Linux in Qemu via "qemu -kernel /vmlinuz ...", opens Qemu
- window, it shows message "Starting Seabios (version 0.5.1-2010...)", and
- then Linux writes messages like "Loading, please wait..." on top of
+ When I start Linux in Qemu via "qemu -kernel /vmlinuz
UPDATE: The second bug (which is started with "Also, I found another
bug! I am learning...") is fixed in 1.4.0
About the first bug: screen clears on real hardware, so it is really
bug. Also, it is reproducible with Qemu 1.4.0 and Qemu
5e3a0f418c4d57399778cee0b55aebfb663b6425.
--
You received thi
I tried to reproduce this bug using lastest stable version (1.4.0) and master
(5e3a0f418c4d57399778cee0b55aebfb663b6425).
This versions seem to add "-usbdevice tablet" by default (and this is very
good). But I think that if guest OS doesn't support tablet device then bug will
still appear. So, I
** Description changed:
Let's assume we have some physical host A. This host runs qemu guest B
locally without any options like "-vnc" etc.
Then I connect from some physical host C to the host A via VNC or Teamviewer
( www.teamviewer.com ). And then I try to remote control (via this vnc
con
Public bug reported:
Let's assume we have some physical host A. This host runs qemu guest B locally
without any options like "-vnc" etc.
Then I connect from some physical host C to the host A via VNC or Teamviewer (
www.teamviewer.com ). And then I try to remote control (via this vnc
connection
** Attachment added: "kernel code. this kernel makes qemu bugs visible"
https://bugs.launchpad.net/bugs/922076/+attachment/2694574/+files/kernel.tar
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/92
Public bug reported:
When I start Linux in Qemu via "qemu -kernel /vmlinuz ...", opens Qemu
window, it shows message "Starting Seabios (version 0.5.1-2010...)", and
then Linux writes messages like "Loading, please wait..." on top of
previous message!
For example, I can see "Loading, please wait..
12 matches
Mail list logo
