Your message dated Thu, 5 Apr 2018 23:11:39 +0300 with message-id <[email protected]> and subject line Re: Bug#528077: MP-BIOS bug: 8254 timer not connected to IO-APIC has caused the Debian Bug report #528077, regarding kvm - fails to setup timer interrupt via io-apic to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 528077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528077 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: kvm Version: 84+dfsg-2 Severity: important kvm fails to setup the timer interrupt via io-apic in kvm-mode. kvm in interpreted mode and qemu 0.9.1-10 does this correctly. There are kernels which needs this. xen on kvm fails therefor with: | (XEN) ENABLING IO-APIC IRQs | (XEN) -> Using new ACK method | (XEN) ..MP-BIOS bug: 8254 timer not connected to IO-APIC | (XEN) | (XEN) **************************************** | (XEN) Panic on CPU 0: | (XEN) IO-APIC + timer doesn't work! Boot with apic=debug and send a report. Then try booting with the 'noapic' option | **************************************** | (XEN) Bastian -- The sooner our happiness together begins, the longer it will last. -- Miramanee, "The Paradise Syndrome", stardate 4842.6
--- End Message ---
--- Begin Message ---On Tue, 23 Sep 2014 18:40:21 +0400 Michael Tokarev <[email protected]> wrote: > It boils down to just this: > > qemu-system-x86_64 -enable-kvm -kernel /tmp/xen-4.1-amd64 -initrd > > /boot/vmlinuz-$(uname -r) -cpu host > > (where /tmp/xen-4.1-amd64 is the regular xen hypervisor, from > /boot/xen-4.1-amd64.gz, > just uncompressed; -cpu host is not mandatory, but you'll see why I used it > in a moment). > > So the above command fails with this 8254 timer not connected message. But > this: > > qemu-system-x86_64 -enable-kvm -kernel /tmp/xen-4.1-amd64 -initrd > /boot/vmlinuz-$(uname -r) -cpu host,-x2apic > > works fine (it fails down the line for me because I used kernel which is not > capable > of running as a dom0 but that's obviously a different issue). I can not reproduce this anymore neither with 2.1 qemu nor with 2.12 qemu, but in the past I verified the issue in qemu-2.4 and qemu-2.5. Maybe it was the host kernel which made the difference, I dunno, but the thing is that it all works now just fine. So closing this bugreport. If you think it is incorrect please reopen it and provide some additional details. Thanks! /mjt
--- End Message ---
