I have the same issue, but not on hardened.
Tried for 1-2 hours to send the output to serial console but failed.
The text below is what I posted at https://bugs.gentoo.org/show_bug.cgi?id=431640#c8:
###############
Same issue here (same screenshot with qemu-kvm-1.1.1-r1), but not on hardened.
Happens with 1.1.1-r3 with a different panic message (not the one
mentioned in bug #431444)
I fail miserably at "sending output to serial console or file", if anyone
would help me there I could provide the entire output of the kernel panic.
Below is what I've found out to far:
(Tests with qemu-kvm-1.1.1-r1)
Analysis:
=========
Happens with the following LiveCDs:
- Fedora-17-x86_64-netinst.iso: uname -r = 3.3.4-5.fc17.x86_64; image: /LiveOS/squashfs.img
- pentoo-x86_64-2012.0_beta1.7.iso: uname -r = 3.4.2-pentoo; image: image.squashfs
I have the same issue, but not on hardened. /bugs.gentoo. org/show_ bug.cgi? id=431640# c8:
Tried for 1-2 hours to send the output to serial console but failed.
The text below is what I posted at https:/
###############
Same issue here (same screenshot with qemu-kvm-1.1.1-r1), but not on hardened.
Happens with 1.1.1-r3 with a different panic message (not the one
mentioned in bug #431444)
I fail miserably at "sending output to serial console or file", if anyone
would help me there I could provide the entire output of the kernel panic.
Below is what I've found out to far:
(Tests with qemu-kvm-1.1.1-r1)
Analysis: 17-x86_ 64-netinst. iso: uname -r = 3.3.4-5. fc17.x86_ 64; image: /LiveOS/ squashfs. img x86_64- 2012.0_ beta1.7. iso: uname -r = 3.4.2-pentoo; image: image.squashfs
=========
Happens with the following LiveCDs:
- Fedora-
- pentoo-
Does not happen with: x86_64- 2009.0. iso: uname -r = 2.6.31-pentoo-r3; image: image.squashfs amd64-minimal- 20120621. iso: uname -r = 3.2.12-gentoo; image.squashfs x86-2.8. 1.iso (64bit kernel): uname -r = 3.2.23- std281- amd64: sysrcd.dat
- pentoo-
- (Gentoo) install-
- systemrescuecd-
Tried installing qemu-kvm-1.1.1-r1 without the 2 patches, no difference.
Guess:
======
This seems to happen only with newer guest-kernels (on newer CPUs).
Hardware-Info:
==============
see attachments