From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Graf Subject: Re: Nested KVM Date: Wed, 31 Dec 2008 16:17:05 +0100 Message-ID: <92130E24-DB72-45F3-B18A-ED445D41B801@suse.de> References: <1e16a9ed0812221855i78de14c4p98c047a3908b6884@mail.gmail.com> <1e16a9ed0812230835l11579c23p51511f5e1b9f4760@mail.gmail.com> <1e16a9ed0812232018u1b7af5f4x98bbde49a4dfb9ba@mail.gmail.com> <9F8C73AC-8AEF-48A7-8AC6-3BEEAF348ED9@suse.de> <1e16a9ed0812291547k52a14b56r7de24c4cf046206b@mail.gmail.com> <1e16a9ed0812300919g1b619520s8d6895109ff157bb@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v930.3) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Cc: "kvm@vger.kernel.org" To: deshantm@gmail.com Return-path: Received: from cantor2.suse.de ([195.135.220.15]:36320 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752515AbYLaPRZ (ORCPT ); Wed, 31 Dec 2008 10:17:25 -0500 In-Reply-To: <1e16a9ed0812300919g1b619520s8d6895109ff157bb@mail.gmail.com> Sender: kvm-owner@vger.kernel.org List-ID: On 30.12.2008, at 18:19, Todd Deshane wrote: > Some more information on this one: > > I just pulled and installed the latest userspace, Now I get > a kernel panic: not syncing: IO-APIC + timer doesn't work! > Boot with apic=debug and send a report. Then try booting > with the 'noapic' option. (this is during the ubuntu CD boot > with the qemu line as: > qemu-system-x86_64 -hda ubuntu-server.img -cdrom > ubuntu-8.10-server-amd64.isoa This message comes when less than n interrupts were received within m loop cycles. I actually do get that with native kvm too sometimes. Just try to boot the VM again. > I will try as the error says, but I think I am going to need > a better console (serial or vnc or something), since the > crash leaves the guest in a non usable state. can't ssh > or anything and it is spinning the CPU over 100%. Eh - the l1 guest or the l2 (nested) guest? The l1 guest should never get to an unusable state. > I'll report back any new information. Any debugging tips > for this type of situation are most welcome. Hum. I usually do a -monitor stdio for the nested kvm instance, but apart from that it's more a question of improvising :). PS: I won't be around any AMD machine until next week, so I can't really see if it works reliably for me. Alex