Farkas Levente wrote: > Laurent Vivier wrote: >> Farkas Levente a écrit : >>> Farkas Levente wrote: >>>> Avi Kivity wrote: >>>>> kvm-47 had a host memory corruption bug when setting the guest pte >>>>> dirty bit, so here's kvm-48 with a fix. >>>>> >>>>> Note that guest time accounting, below, will only work with Linux >>>>> 2.6.24+. >>>> smp guests still not working with kvm-48:-( i can't image what others >>>> can do to make it work. guests hang at random stage during boot. i >>>> attached guests boot screenshot. setup: >>>> ------------------------------------------------ >>>> - host: >>>> - Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz >>>> - Intel S3000AHV >>>> - 8GB RAM >>>> - CentOS-5 >>>> - kernel-2.6.18-8.1.14.el5 x86_64 64bit >>>> - guest-1: >>>> - CentOS-5 >>>> - kernel-2.6.18-8.1.14.el5 i386 32bit >>>> - guest-2: >>>> - CentOS-5 >>>> - kernel-2.6.18-8.1.14.el5 x86_64 64bit >>>> - guest-3: >>>> - Mandrake-9 >>>> - kernel-2.4.19.16mdk-1-1mdk 32bit >>>> - guest-4: >>>> - Windows XP Professional 32bit >>>> ------------------------------------------------ >>>> i try guest-1 and huest-2 with 4 vcpu others with 1 vcpu. >>>> on host the only thing i've got in dmesg: >>>> ------------------------------------------------ >>>> Call Trace: >>>> <IRQ> [<ffffffff800b2c30>] softlockup_tick+0xdb/0xed >>>> [<ffffffff800933ec>] update_process_times+0x42/0x68 >>>> [<ffffffff80073d61>] smp_local_timer_interrupt+0x23/0x47 >>>> [<ffffffff80074423>] smp_apic_timer_interrupt+0x41/0x47 >>>> [<ffffffff8005bcc2>] apic_timer_interrupt+0x66/0x6c >>>> <EOI> [<ffffffff88205999>] :kvm:kvm_flush_remote_tlbs+0xfb/0x109 >>>> [<ffffffff88205988>] :kvm:kvm_flush_remote_tlbs+0xea/0x109 >>>> [<ffffffff88206314>] :kvm:gfn_to_page+0xa3/0xd5 >>>> [<ffffffff88205573>] :kvm:mark_page_dirty+0x9/0x2a >>>> [<ffffffff8820b62c>] :kvm:kvm_mmu_pte_write+0x1fc/0x330 >>>> [<ffffffff882065d9>] :kvm:emulator_write_emulated_onepage+0x6e/0xce >>>> [<ffffffff8820fcd0>] :kvm:x86_emulate_insn+0x2b98/0x4134 >>>> [<ffffffff80008e1a>] __handle_mm_fault+0x832/0xdf2 >>>> [<ffffffff8840a404>] :kvm_intel:vmcs_readl+0x17/0x1c >>>> [<ffffffff88206ac2>] :kvm:emulate_instruction+0x152/0x290 >>>> [<ffffffff8840cb98>] :kvm_intel:handle_exception+0x170/0x250 >>>> [<ffffffff882074f6>] :kvm:kvm_vcpu_ioctl+0x343/0xf43 >>>> [<ffffffff80044d32>] try_to_wake_up+0x407/0x418 >>>> [<ffffffff800850b5>] __wake_up_common+0x3e/0x68 >>>> [<ffffffff8002dd9c>] __wake_up+0x38/0x4f >>>> [<ffffffff80021b8a>] __up_read+0x19/0x7f >>>> [<ffffffff8011735a>] avc_has_perm+0x43/0x55 >>>> [<ffffffff80117e91>] inode_has_perm+0x56/0x63 >>>> [<ffffffff80058bf1>] getnstimeofday+0x10/0x28 >>>> [<ffffffff80086c37>] default_wake_function+0x0/0xe >>>> [<ffffffff80117f32>] file_has_perm+0x94/0xa3 >>>> [<ffffffff8003fc5b>] do_ioctl+0x21/0x6b >>>> [<ffffffff8002fa61>] vfs_ioctl+0x248/0x261 >>>> [<ffffffff8004a267>] sys_ioctl+0x59/0x78 >>>> [<ffffffff8005b2c1>] tracesys+0xd1/0xdc >>>> ------------------------------------------------ >>> the situation is even worse, the guests are hang during boot even with >>> single vcpu and even with kvm-46:-( i attached another screenshot. but >>> after i kill the guest and start it again it works. it seems the problem >>> occurs when i start more guest at the same time (eg. after reboot the >>> host). and it seems there is some kind of acpi error since all of the >>> guest hang screenshot contains some kind of acpi error. >> What happens if you use "-noacpi" ? > > in this case single cpu guests are working with kvm-48, but 4 > vcpu/guests still hang:-(
one more thing which happened with single cpu guests on kvm-48 in dmesg on the host: Fault when IDT_Vectoring Fault when IDT_Vectoring Fault when IDT_Vectoring Fault when IDT_Vectoring Fault when IDT_Vectoring Fault when IDT_Vectoring Fault when IDT_Vectoring Fault when IDT_Vectoring Fault when IDT_Vectoring Fault when IDT_Vectoring Fault when IDT_Vectoring Fault when IDT_Vectoring -- Levente "Si vis pacem para bellum!" ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
