Bugs item #1858940, was opened at 2007-12-27 15:08 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1858940&group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Kai Londenberg (kai_londenberg) Assigned to: Nobody/Anonymous (nobody) Summary: Kernel panic - not syncing: IO-APIC + timer doesn't work. Initial Comment: The problem: When booting a Guest with -smp 2 option (and without -no-acpi, since that's essential for SMP), I get a Kernel panic. My Setup: Host: 64_86 bit Ubuntu 7.10 with custom built 2.6.23.12 Kernel. AMD Dual CPU with Virtualization extensions. Guest: Ubuntu 6.06 - Server - with pre-compiled 2.6.15.29 server Kernel, with SMP Support. I logged the kernel output via serial console redirection into a file. ---------------------------------------------------------------------- >Comment By: Jes Sorensen (jessorensen) Date: 2010-06-21 13:32 Message: Ubuntu 6.06 x86_64 boots fine with -smp 2 on an AMD system with a recent KVM / qemu-kvm combo. Closing ---------------------------------------------------------------------- Comment By: TJ (tjworld) Date: 2008-01-30 21:40 Message: Logged In: YES user_id=1048563 Originator: NO I'm experiencing the same problem on Ubuntu Gutsy 7.10 x86_64 (2.6.22-14-generic). I have working guest images of Ubuntu Gutsy 7.10 x86 with kvm-51 but hadn't used them in a while. Tried to boot them earlier using the same launch scripts as usual and the process hung with the CPU looping at 100% usage. I then downloaded, built, and installed kvm-60 thinking it was some strange issue that hadn't manifested previously. The same problem occurs with kvm-60. I then booted the images with modified grub settings to watch the kernel log and saw it fails to find a timer as reported here. I eventually found that by adding "-no-acpi" to the launch command-line they would boot successfully. I'm not sure what changed in the interim but obviously something did. This is the working launch options: qemuctl -qemu vdeq kvm -name Gutsy-Desktop -boot c -m 512 -hda /home/all/VirtualMachines/Ubuntu-Gutsy-Desktop-x86.ovl -k en-gb -net nic,model=rtl8139,macaddr=56:44:45:30:30:31,vlan=0 -soundhw es1370 -usb -net vde,sock=/var/run/kvm0.ctl,vlan=0 -no-acpi ---------------------------------------------------------------------- Comment By: Technologov (technologov) Date: 2007-12-27 16:19 Message: Logged In: YES user_id=1839746 Originator: NO 1. If you use KVM from 2.6.23 kernel, then I strongly recommend you to try the newest KVM-58, as it has some fixes for AMD. 2. What bitness ? Guest OS is 32 or 64-bit ? 3. ACPI is essential only for Windows SMP. On Linux however, SMP works, and ACPI on/off doesn't affects it. -Alexey Technologov ---------------------------------------------------------------------- Comment By: Kai Londenberg (kai_londenberg) Date: 2007-12-27 15:11 Message: Logged In: YES user_id=1299941 Originator: YES Using kvm 58, started with -smp 2 option. ---------------------------------------------------------------------- Comment By: Kai Londenberg (kai_londenberg) Date: 2007-12-27 15:09 Message: Logged In: YES user_id=1299941 Originator: YES File Added: boot.log ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1858940&group_id=180599 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
