[Excuse the duplicate; this is properly cc'd to bugs.debian.org.] On Tue, 2011-02-15 at 18:52 +0200, Timo Juhani Lindfors wrote: > Ben Hutchings <b...@decadent.org.uk> writes: > > It's a kernel feature to be more efficient when running in a recognised > > virtual machine implementation (PV = paravirtualisation). > > thanks. I think it is the following code from vmi_32.c: [...] > I don't understand how the first xchg instruction in > > 0x0000000000600889 <f+41>: 57 push %rdi > 0x000000000060088a <f+42>: 9d popfq > 0x000000000060088b <f+43>: 66 66 90 xchg %ax,%ax > 0x000000000060088e <f+46>: 66 90 xchg %ax,%ax > > can generate a general protection fault. I googled around and found > > "yes - it smells like it tries to deliver vector 0, after the panic > code has deinitialized the lapic / ioapic" > > which suggests a qemu bug from > http://linux.derkeiler.com/Mailing-Lists/Kernel/2008-09/msg09652.html > > Shall I reassign the bug or do you know how to investigate this more?
Sorry, I don't have a good idea how to investigate this further. The message you're referring to is quite old and I would expect the bug to have been fixed in qemu since then. Is the KVM host using an old version? Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
signature.asc
Description: This is a digitally signed message part
