linux-kernel - Re: 3.0.0-rc2: Xen: QEMU Kernel panic - not syncing: IO-APIC + timer doesn't work!

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110613185602.GB31895@dumpdata.com>
Date:	Mon, 13 Jun 2011 14:56:02 -0400
From:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To:	Tobias Diedrich <ranma+xen@...edrich.de>,
	xen-users@...ts.xensource.com, linux-kernel@...r.kernel.org
Subject: Re: 3.0.0-rc2: Xen: QEMU Kernel panic - not syncing: IO-APIC + timer
 doesn't work!

On Mon, Jun 13, 2011 at 02:38:25PM -0400, Konrad Rzeszutek Wilk wrote:
> On Mon, Jun 13, 2011 at 07:35:32PM +0200, Tobias Diedrich wrote:
> > Hi,
> > 
> > I ran into this problem when trying to set up Xen on a root server
> > with a pre-Orleans Athlon64 (no svm, so no kvm):
> 
> Uhh, your output says otherwise. What is the serial output your
> box produced?
> > 
> > Since 3.0-rc is supposed to have Xen DOM0 support I of course want
> > to use this rather than some old xenified kernel version. :)
> > 
> 
> Ok.
> > I later got it to boot using "noapic apci=off" (just noapic wasn't
> > sufficient, I had to add acpi=off because it had interrupt routing
> > problems with just noapic), and I can see that the APIC handlers in
> > arch/x86/xen/enlighten.c are just stubs so far.
> 
> Right.
> > 
> > So is this supposed to work with APICs?
> 
> Yes. Well, it actually should just bypass/ignore the APIC calls and
> the warnings are suppose to be benign.
> 
> But somehow your environment triggered a weird state. I've to admint
> I hadn't tried to boot Xen + paravirt Linux under QEMU for some time.

Just tried (but didn't do it with KVM, just normal QEMU without KVM or Xen)
and I was able to reproduce the issue you saw. Thought it looks like as if
my default .config does not cause this issue.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/