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 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
