[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1037675
Title:
Guest
** Bug watch removed: Gentoo Bugzilla #431640
https://bugs.gentoo.org/show_bug.cgi?id=431640
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1037675
Title:
Guest Kernel Panic if using "-cpu host"
Is there still something left to do here or can we close this bug
nowadays?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1037675
Title:
Guest
You can pass the level=9 param to disable the PMU emulation, this should
fix your issue as well. ( e.g. -cpu host,level=9 )
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1037675
Title:
Guest
I am seeing more or less the same thing. I am trying to boot Puppy Linux
from Gentoo with qemu-kvm-1.1.1-r3 and gentoo-sources-3.6.0.
Interestingly, I also found that AROS crashed when using -cpu host but
I initially chalked that up to AROS being flakey - perhaps not.
Obviously I can't enable
changing the guest config to enable paravirt seems to do the trick!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1037675
Title:
Guest Kernel Panic if using -cpu host in qemu-kvm 1.1.1
Status in
On Mon, Sep 10, 2012 at 10:24:51PM -, Till Schäfer wrote:
i started trace-cmd as suggested on http://www.linux-
kvm.org/page/Tracing and started the vm. after the panic i aborted
trace-cmd and here is the trace file
** Attachment added: trace from trace-cmd
I had exactly the same problem using custom kernel on Debian GNU/Linux /
qemu-kvm 1.1.1 or 1.2.0.
CPU: Intel(R) Xeon(R) CPU E5-2667 0 @ 2.90GHz stepping 7 microcode 0x70b
I have two solutions: (VERY UGGLY) patch the kernel to remove intel perf
events (hardware events):
---
Correcting myself (comment #2):
And forth, gentoo is very well known for breaking qemu-kvm by their
hardened patches. Disable the hardening and retry.
I mean the (host) KERNEL hardering, not qemu-kvm userspace hardering
there. Sorry for any potential confusion.
--
You received this bug
thx for the patience, i am currently very busy, therefore this took a
bit longer than it was planed:
- using a non hardened kernel (gentoo-sources-3.3.8) does not resolve
the issue
therefore i need to use the serial console, which is somewhat new to
me. i will do this as soon as i find some
** Attachment added: guest output of kernel panic (serial console output)
https://bugs.launchpad.net/qemu/+bug/1037675/+attachment/3305265/+files/serial_out.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
ok getting the serial console to work was not that hard. here is the
relevant serial output of the failing guest (full output is attached as
file):
[0.010706] mce: CPU supports 10 MCE banks
[0.011279] ACPI: Core revision 20110623
[0.014769] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1
On Mon, Sep 10, 2012 at 10:23:26AM -, Till Schäfer wrote:
[0.027998] Process swapper/0 (pid: 1, threadinfo 88000f8b8000, task
88000f8b)
[0.027998] Stack:
[0.027998] 81b1b550 88000f8b9ef0
81aa4989
[0.027998]
i started trace-cmd as suggested on http://www.linux-
kvm.org/page/Tracing and started the vm. after the panic i aborted
trace-cmd and here is the trace file
** Attachment added: trace from trace-cmd
https://bugs.launchpad.net/qemu/+bug/1037675/+attachment/3306241/+files/trace.dat.tar.bz2
--
i forgot to mention that the PID was 27374
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1037675
Title:
Guest Kernel Panic if using -cpu host in qemu-kvm 1.1.1
Status in QEMU:
New
Bug
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.
sorry for the not very usefull information i provides above.
i will try to reproduce the the failure with a vailla kernel (host) in
a few days. currently the server is in use and cannot be restarted.
the kernel panic was in the guest (thought this is clear by my vm
panic). If it is reproducable
** Attachment added: kernel panic screenshot
https://bugs.launchpad.net/bugs/1037675/+attachment/3264111/+files/kernel_panic.png
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1037675
Title:
First of all, your kernel panic screenshot is incomplete: it lacks the
most important information which were scrolled off the (virtual) screen.
Please enable serial console and capture whole OOPs in a text form.
Second, it isn't clear whenever this is HOST kernel panic or GUEST
kernel panic. I
19 matches
Mail list logo
