Dong, Eddie wrote: > [EMAIL PROTECTED] wrote: >> hi, >> i'm just try kvm-45. for me it still unusable, so switch back >> to kvm-36:-( >> setup: >> - host: centos-5 x86-64 (4 core, 8gb ram) >> - guest: >> - centos-5 i386 4 cpu, 2gb >> - centos-5 x86-64 4 cpu, 1gb >> - mandrake-9 i586 2 cpu, 1gb >> - winxp 32bit 1gb >> the problems: >> after start the above setup none of the guest be able to boot until >> login screen (except winxp?:-( i attached the guest's virt-manager >> screenshots. the worse thing comes when i try to stop the guests. >> virt-manager crash. after that i try to kill qemu-kvm's but it was >> simple not possible!:-( --------------------------------- >> Ignoring de-assert INIT to vcpu 0 >> Ignoring de-assert INIT to vcpu 1 >> vcpu 1 received sipi with vector # 10 >> vcpu 2 received sipi with vector # 10 >> vcpu 3 received sipi with vector # 10 >> kvm: emulating exchange as write >> vcpu 1 received sipi with vector # 3 >> vcpu 2 received sipi with vector # 3 >> vcpu 3 received sipi with vector # 3 >> vcpu 1 received sipi with vector # 10 >> vcpu 2 received sipi with vector # 10 >> vcpu 3 received sipi with vector # 10 >> vcpu 1 received sipi with vector # 10 >> vcpu 1 received sipi with vector # 6 >> vcpu 2 received sipi with vector # 6 >> vcpu 3 received sipi with vector # 6 >> --------------------------------- >> in the host dmesg: >> --------------------------------- >> Ignoring de-assert INIT to vcpu 1 >> SIPI to vcpu 1 vector 0x06 >> vcpu 1 received sipi with vector # 6 >> SIPI to vcpu 1 vector 0x06 >> Ignoring de-assert INIT to vcpu 2 >> SIPI to vcpu 2 vector 0x06 >> vcpu 2 received sipi with vector # 6 >> SIPI to vcpu 2 vector 0x06 >> Ignoring de-assert INIT to vcpu 3 >> SIPI to vcpu 3 vector 0x06 >> vcpu 3 received sipi with vector # 6 >> SIPI to vcpu 3 vector 0x06 >> --------------------------------- >> so try to reboot, but the host crash during the shutdown (i've no >> screenshot of this and the important part are scrolled up), so >> reset:-( on the host console: the strange thing that after i reboot >> and replace all guest to 1 cpu all of the guests boot except the >> centos-i386 which also hang (may be because this is the only guest >> which has 2gb ram assigned?) but i still not able to login to them >> (except winxp), ie. after boot neither from console nor from remote i >> can't connect it's looks like guests are frozen, but there is nothing >> on the host console or log files. >> so i revert to kvm-36 which working with 1cpu/guest. >> my real question i do something wrong or just no one use more cpu and >> more guest on such and old kernel as centos's >> 2.6.18-8.1.14.el5:-( or my >> hardware are so strange? >> > Did u try above configuration in KVM-36 (i.e. multiple guest + SMP)?
smp is not working in kmv-36, but multiple guest with single cpu is stable. -- 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
