Bugs item #1698925, was opened at 2007-04-11 23:09 Message generated for change (Settings changed) made by iggy_cav You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1698925&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: kucharsk (kucharsk) Assigned to: Amit Shah (amitshah) Summary: Booting 64-bit Solaris can cause Linux to spin Initial Comment: Attempting to boot 64-bit Solaris with the kmdb kernel debugger installed (adding "-k" to the boot arguments) causes Linux to spin, repeatedly emitting the following message to the console, requiring a reboot of the Linux machine to recover: rtc: lost some interrupts at 1024Hz. This does not occur when running software QEMU, so it appears KVM may be presenting an improper intial state for the x87 FPU. This is with kvm-18 running on Fedora Core 6 x86_64 kernel 2.6.20-1.2933.fc6 on a dual CPU rev. F Opteron platform: processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 65 model name : Dual-Core AMD Opteron(tm) Processor 2218 stepping : 2 cpu MHz : 2613.392 cache size : 1024 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 2 fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow pni cx16 lahf_lm cmp_legacy svm cr8_legacy bogomips : 5231.22 TLB size : 1024 4K pages clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts fid vid ttp tm stc ---------------------------------------------------------------------- Comment By: kucharsk (kucharsk) Date: 2007-12-05 21:46 Message: Logged In: YES user_id=1767421 Originator: YES Confirmed that it no longer hangs, but the 64-bit kernel does die with a #GP not seen if the image is run with --no-kvm. This is with kvm-55. ---------------------------------------------------------------------- Comment By: SourceForge Robot (sf-robot) Date: 2007-12-05 21:20 Message: Logged In: YES user_id=1312539 Originator: NO This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ---------------------------------------------------------------------- Comment By: Amit Shah (amitshah) Date: 2007-11-21 09:16 Message: Logged In: YES user_id=201894 Originator: NO This doesn't happen on my system with kvm-53. Can you confirm this doesn't happen for you as well? ---------------------------------------------------------------------- Comment By: Technologov (technologov) Date: 2007-11-08 07:30 Message: Logged In: YES user_id=1839746 Originator: NO This bug applies to Intel-64 hosts as well. Workaround: is to add "kernel/unix" to GRUB to force using Solaris 32-bit kernel. -Alexey ---------------------------------------------------------------------- Comment By: kucharsk (kucharsk) Date: 2007-08-13 22:04 Message: Logged In: YES user_id=1767421 Originator: YES At present kvm-34 will not boot Solaris; see RequestID 1773613. ---------------------------------------------------------------------- Comment By: Amit Shah (amitshah) Date: 2007-08-13 14:58 Message: Logged In: YES user_id=201894 Originator: NO See this thread for information on the RTC messages. http://thread.gmane.org/gmane.comp.emulators.kvm.devel/2325 Can you try the latest git or kvm-34? Problems with AMD64 have been fixed, and the root cause could be the same as for bug #1699695 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1698925&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
