kvm-45 problems

kvm-45 problems

[Farkas Levente]

[-- Attachment #1: Type: text/plain, Size: 2550 bytes --]

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?

-- 
  Levente                               "Si vis pacem para bellum!"

[-- Attachment #2: Screenshot-devel-i386VirtualMachineConsole.png --]
[-- Type: image/png, Size: 33590 bytes --]

[-- Attachment #3: Screenshot-devel-x86-64VirtualMachineConsole.png --]
[-- Type: image/png, Size: 31081 bytes --]

[-- Attachment #4: Screenshot-VirtualMachineManager.png --]
[-- Type: image/png, Size: 59599 bytes --]

[-- Attachment #5: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
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/

[-- Attachment #6: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: kvm-45 problems

[Dong, Eddie]

kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org 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)? 

-------------------------------------------------------------------------
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/

Re: kvm-45 problems

[Farkas Levente]

Dong, Eddie wrote:
> kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org 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/

Re: kvm-45 problems

[Zhao, Yunfeng]

[-- Attachment #1: Type: text/plain, Size: 4630 bytes --]

We run some booting multiple guest tests in our nightly testing.
Like booting two UP windows guests, booting one UP linux guest and one UP windows guest, and booting 4 UP linux guests.
The first two cases have no problem in our testing.
And booting 4 UP linux guests may crash host, but this problem doesn't happen very time. If the problem didn't happen, linux guest can be log in without any problem.

For smp guest, we meet a problem that booting linux guest with 4 vcpus causes soft lock error on host. Once this error happened, qemu process also could not be killed.

Our linux guests are using 2.6.9, 2.6.16, and 2.6.23 kernels.

Thanks
Yunfeng


>-----Original Message-----
>From: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
>[mailto:kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf Of Farkas Levente
>Sent: 2007年10月9日 14:45
>To: Dong, Eddie
>Cc: kvm-devel
>Subject: Re: [kvm-devel] kvm-45 problems
>
>Dong, Eddie wrote:
>> kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org 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-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
>https://lists.sourceforge.net/lists/listinfo/kvm-devel


[-- Attachment #2: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
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/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: kvm-45 problems

[Avi Kivity]

[-- Attachment #1: Type: text/plain, Size: 825 bytes --]

Zhao, Yunfeng wrote:
> We run some booting multiple guest tests in our nightly testing.
> Like booting two UP windows guests, booting one UP linux guest and one UP windows guest, and booting 4 UP linux guests.
> The first two cases have no problem in our testing.
> And booting 4 UP linux guests may crash host, but this problem doesn't happen very time. If the problem didn't happen, linux guest can be log in without any problem.
>
> For smp guest, we meet a problem that booting linux guest with 4 vcpus causes soft lock error on host. Once this error happened, qemu process also could not be killed.
>
> Our linux guests are using 2.6.9, 2.6.16, and 2.6.23 kernels.
>
>   

This may be due to NMIs or MCEs. Is it possible your machine is
receiving them?

-- 
error compiling committee.c: too many arguments to function



[-- Attachment #2: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
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/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: kvm-45 problems

[Farkas Levente]

[-- Attachment #1: Type: text/plain, Size: 888 bytes --]

Avi Kivity wrote:
> Zhao, Yunfeng wrote:
>> We run some booting multiple guest tests in our nightly testing.
>> Like booting two UP windows guests, booting one UP linux guest and one UP windows guest, and booting 4 UP linux guests.
>> The first two cases have no problem in our testing.
>> And booting 4 UP linux guests may crash host, but this problem doesn't happen very time. If the problem didn't happen, linux guest can be log in without any problem.
>>
>> For smp guest, we meet a problem that booting linux guest with 4 vcpus causes soft lock error on host. Once this error happened, qemu process also could not be killed.
>>
>> Our linux guests are using 2.6.9, 2.6.16, and 2.6.23 kernels.
>>
>>   
> 
> This may be due to NMIs or MCEs. Is it possible your machine is
> receiving them?

what does it mean?

-- 
  Levente                               "Si vis pacem para bellum!"


[-- Attachment #2: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
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/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: kvm-45 problems

[Avi Kivity]

[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]

Farkas Levente wrote:
> Avi Kivity wrote:
>   
>> Zhao, Yunfeng wrote:
>>     
>>> We run some booting multiple guest tests in our nightly testing.
>>> Like booting two UP windows guests, booting one UP linux guest and one UP windows guest, and booting 4 UP linux guests.
>>> The first two cases have no problem in our testing.
>>> And booting 4 UP linux guests may crash host, but this problem doesn't happen very time. If the problem didn't happen, linux guest can be log in without any problem.
>>>
>>> For smp guest, we meet a problem that booting linux guest with 4 vcpus causes soft lock error on host. Once this error happened, qemu process also could not be killed.
>>>
>>> Our linux guests are using 2.6.9, 2.6.16, and 2.6.23 kernels.
>>>
>>>   
>>>       
>> This may be due to NMIs or MCEs. Is it possible your machine is
>> receiving them?
>>     
>
> what does it mean?
>   

Non-maskable interrupts and machine check exceptions.




-- 
error compiling committee.c: too many arguments to function



[-- Attachment #2: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
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/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: kvm-45 problems

[Farkas Levente]

[-- Attachment #1: Type: text/plain, Size: 1117 bytes --]

Avi Kivity wrote:
> Farkas Levente wrote:
>> Avi Kivity wrote:
>>   
>>> Zhao, Yunfeng wrote:
>>>     
>>>> We run some booting multiple guest tests in our nightly testing.
>>>> Like booting two UP windows guests, booting one UP linux guest and one UP windows guest, and booting 4 UP linux guests.
>>>> The first two cases have no problem in our testing.
>>>> And booting 4 UP linux guests may crash host, but this problem doesn't happen very time. If the problem didn't happen, linux guest can be log in without any problem.
>>>>
>>>> For smp guest, we meet a problem that booting linux guest with 4 vcpus causes soft lock error on host. Once this error happened, qemu process also could not be killed.
>>>>
>>>> Our linux guests are using 2.6.9, 2.6.16, and 2.6.23 kernels.
>>>>
>>>>   
>>>>       
>>> This may be due to NMIs or MCEs. Is it possible your machine is
>>> receiving them?
>>>     
>> what does it mean?
>>   
> 
> Non-maskable interrupts and machine check exceptions.

is it something which i can trigger (as as user of kvm)?

-- 
  Levente                               "Si vis pacem para bellum!"


[-- Attachment #2: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
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/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: kvm-45 problems

[Avi Kivity]

[-- Attachment #1: Type: text/plain, Size: 1378 bytes --]

Farkas Levente wrote:
> Avi Kivity wrote:
>   
>> Farkas Levente wrote:
>>     
>>> Avi Kivity wrote:
>>>   
>>>       
>>>> Zhao, Yunfeng wrote:
>>>>     
>>>>         
>>>>> We run some booting multiple guest tests in our nightly testing.
>>>>> Like booting two UP windows guests, booting one UP linux guest and one UP windows guest, and booting 4 UP linux guests.
>>>>> The first two cases have no problem in our testing.
>>>>> And booting 4 UP linux guests may crash host, but this problem doesn't happen very time. If the problem didn't happen, linux guest can be log in without any problem.
>>>>>
>>>>> For smp guest, we meet a problem that booting linux guest with 4 vcpus causes soft lock error on host. Once this error happened, qemu process also could not be killed.
>>>>>
>>>>> Our linux guests are using 2.6.9, 2.6.16, and 2.6.23 kernels.
>>>>>
>>>>>   
>>>>>       
>>>>>           
>>>> This may be due to NMIs or MCEs. Is it possible your machine is
>>>> receiving them?
>>>>     
>>>>         
>>> what does it mean?
>>>   
>>>       
>> Non-maskable interrupts and machine check exceptions.
>>     
>
> is it something which i can trigger (as as user of kvm)?
>
>   

It's something that happens as part of the ordinary workload of the
machine. I suspect that kvm doesn't handle it correctly.


-- 
error compiling committee.c: too many arguments to function



[-- Attachment #2: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
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/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: kvm-45 problems

[Avi Kivity]

[-- Attachment #1: Type: text/plain, Size: 953 bytes --]

Avi Kivity wrote:
> Zhao, Yunfeng wrote:
>   
>> We run some booting multiple guest tests in our nightly testing.
>> Like booting two UP windows guests, booting one UP linux guest and one UP windows guest, and booting 4 UP linux guests.
>> The first two cases have no problem in our testing.
>> And booting 4 UP linux guests may crash host, but this problem doesn't happen very time. If the problem didn't happen, linux guest can be log in without any problem.
>>
>> For smp guest, we meet a problem that booting linux guest with 4 vcpus causes soft lock error on host. Once this error happened, qemu process also could not be killed.
>>
>> Our linux guests are using 2.6.9, 2.6.16, and 2.6.23 kernels.
>>
>>   
>>     
>
> This may be due to NMIs or MCEs. Is it possible your machine is
> receiving them?
>   


I pushed a fix for the NMI issue. Can you check if it fixes your hangs?


-- 
error compiling committee.c: too many arguments to function



[-- Attachment #2: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
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/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: kvm-45 problems

[Zhao, Yunfeng]

>> This may be due to NMIs or MCEs. Is it possible your machine is
>> receiving them?
>>
>
>
>I pushed a fix for the NMI issue. Can you check if it fixes your hangs?
[Yunfeng]  Sure, the result will be available tomorrow.
>
>
>--
>error compiling committee.c: too many arguments to function

-------------------------------------------------------------------------
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/

Re: kvm-45 problems

[Zhao, Yunfeng]

[-- Attachment #1: Type: text/plain, Size: 3193 bytes --]

This fix cannot resolve this issue.
Against latest kvm commits, SMP linux with 4 vcpus still cannot boot up.
But the issue will not happen , if adding "-smp4 -no-acpi".

Here is the error info in dmesg
BUG: soft lockup detected on CPU#0!
 [<c044a0b7>] softlockup_tick+0x98/0xa6
 [<c042cc98>] update_process_times+0x39/0x5c
 [<c04176ec>] smp_apic_timer_interrupt+0x5c/0x64
 [<c04049bf>] apic_timer_interrupt+0x1f/0x24
 [<f8abdfb7>] kvm_flush_remote_tlbs+0xcc/0xdb [kvm]
 [<f8ac3467>] kvm_mmu_pte_write+0x1f2/0x368 [kvm]
 [<f8abe7bb>] emulator_write_emulated_onepage+0x73/0xe6 [kvm]
 [<f8ac6268>] x86_emulate_insn+0x20c2/0x3122 [kvm]
 [<f8ac3f86>] x86_decode_insn+0x624/0x844 [kvm]
 [<f8abebd6>] emulate_instruction+0x12b/0x258 [kvm]
 [<f8a172d0>] handle_exception+0x163/0x23f [kvm_intel]
 [<f8a17087>] kvm_handle_exit+0x70/0x8a [kvm_intel]
 [<f8abf1fd>] kvm_vcpu_ioctl_run+0x21a/0x31f [kvm]
 [<f8abf3fc>] kvm_vcpu_ioctl+0x0/0xc58 [kvm]
 [<f8abf4ff>] kvm_vcpu_ioctl+0x103/0xc58 [kvm]
 [<c04db744>] __next_cpu+0x12/0x21
 [<c041c97f>] find_busiest_group+0x177/0x462
 [<c041d3cd>] enqueue_task+0x29/0x39
 [<c041d3f9>] __activate_task+0x1c/0x29
 [<c041dc43>] try_to_wake_up+0x371/0x37b
 [<c05facb9>] schedule+0x90d/0x9ba
 [<c041c41c>] __wake_up_common+0x2f/0x53
 [<c041d20d>] __wake_up+0x2a/0x3d
 [<c0437cef>] wake_futex+0x3a/0x44
 [<c0437fbf>] futex_wake+0xa9/0xb3
 [<c0438b9e>] do_futex+0x20d/0xb15
 [<c04db744>] __next_cpu+0x12/0x21
 [<c042d849>] __dequeue_signal+0x151/0x15c
 [<c042e942>] dequeue_signal+0x2d/0x9c
 [<c0415b61>] smp_call_function_interrupt+0x3e/0x52
 [<f8abf3fc>] kvm_vcpu_ioctl+0x0/0xc58 [kvm]
 [<c040499b>] call_function_interrupt+0x1f/0x24
 [<f8abf3fc>] kvm_vcpu_ioctl+0x0/0xc58 [kvm]
 [<c0415b61>] smp_call_function_interrupt+0x3e/0x52
 [<f8abf3fc>] kvm_vcpu_ioctl+0x0/0xc58 [kvm]
 [<c0479cc8>] do_ioctl+0x1c/0x5d
 [<c0479f53>] vfs_ioctl+0x24a/0x25c
 [<c0479fad>] sys_ioctl+0x48/0x5f
 [<c0403eff>] syscall_call+0x7/0xb

>-----Original Message-----
>From: Avi Kivity [mailto:avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org]
>Sent: 2007年10月9日 18:19
>To: Zhao, Yunfeng
>Cc: kvm-devel
>Subject: Re: [kvm-devel] kvm-45 problems
>
>Avi Kivity wrote:
>> Zhao, Yunfeng wrote:
>>
>>> We run some booting multiple guest tests in our nightly testing.
>>> Like booting two UP windows guests, booting one UP linux guest and one UP
>windows guest, and booting 4 UP linux guests.
>>> The first two cases have no problem in our testing.
>>> And booting 4 UP linux guests may crash host, but this problem doesn't happen
>very time. If the problem didn't happen, linux guest can be log in without any
>problem.
>>>
>>> For smp guest, we meet a problem that booting linux guest with 4 vcpus causes
>soft lock error on host. Once this error happened, qemu process also could not
>be killed.
>>>
>>> Our linux guests are using 2.6.9, 2.6.16, and 2.6.23 kernels.
>>>
>>>
>>>
>>
>> This may be due to NMIs or MCEs. Is it possible your machine is
>> receiving them?
>>
>
>
>I pushed a fix for the NMI issue. Can you check if it fixes your hangs?
>
>
>--
>error compiling committee.c: too many arguments to function


[-- Attachment #2: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
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/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: kvm-45 problems

[Avi Kivity]

[-- Attachment #1: Type: text/plain, Size: 303 bytes --]

Zhao, Yunfeng wrote:
> This fix cannot resolve this issue.
> Against latest kvm commits, SMP linux with 4 vcpus still cannot boot up.
> But the issue will not happen , if adding "-smp4 -no-acpi".
>   

Can you try the attached patch?




-- 
error compiling committee.c: too many arguments to function


[-- Attachment #2: remote-flush-test.patch --]
[-- Type: text/x-patch, Size: 574 bytes --]

diff --git a/kernel/kvm_main.c b/kernel/kvm_main.c
index 0b2894a..61d931e 100644
--- a/kernel/kvm_main.c
+++ b/kernel/kvm_main.c
@@ -235,11 +235,7 @@ void kvm_flush_remote_tlbs(struct kvm *kvm)
 	 * to complete.
 	 */
 	for (cpu = first_cpu(cpus); cpu != NR_CPUS; cpu = next_cpu(cpu, cpus))
-		smp_call_function_single(cpu, ack_flush, &completed, 1, 0);
-	while (atomic_read(&completed) != needed) {
-		cpu_relax();
-		barrier();
-	}
+		smp_call_function_single(cpu, ack_flush, &completed, 1, 1);
 }
 
 int kvm_vcpu_init(struct kvm_vcpu *vcpu, struct kvm *kvm, unsigned id)

[-- Attachment #3: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
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/

[-- Attachment #4: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: kvm-45 problems

[Laurent Vivier]

[-- Attachment #1.1.1: Type: text/plain, Size: 1667 bytes --]

Avi Kivity wrote:
> Zhao, Yunfeng wrote:
>> This fix cannot resolve this issue.
>> Against latest kvm commits, SMP linux with 4 vcpus still cannot boot up.
>> But the issue will not happen , if adding "-smp4 -no-acpi".
>>   
> 
> Can you try the attached patch?
> 
> 
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> diff --git a/kernel/kvm_main.c b/kernel/kvm_main.c
> index 0b2894a..61d931e 100644
> --- a/kernel/kvm_main.c
> +++ b/kernel/kvm_main.c
> @@ -235,11 +235,7 @@ void kvm_flush_remote_tlbs(struct kvm *kvm)
>  	 * to complete.
>  	 */
>  	for (cpu = first_cpu(cpus); cpu != NR_CPUS; cpu = next_cpu(cpu, cpus))
> -		smp_call_function_single(cpu, ack_flush, &completed, 1, 0);
> -	while (atomic_read(&completed) != needed) {
> -		cpu_relax();
> -		barrier();
> -	}
> +		smp_call_function_single(cpu, ack_flush, &completed, 1, 1);
>  }
>  
>  int kvm_vcpu_init(struct kvm_vcpu *vcpu, struct kvm *kvm, unsigned id)

This part will be obsolete as soon as linux will export
smp_call_function_mask(). This is already in mm tree:

ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc8/2.6.23-rc8-mm2/broken-out/x86_64-mm-export-i386-smp_call_function_mask-to-modules.patch
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc8/2.6.23-rc8-mm2/broken-out/x86_64-mm-implement-missing-x86_64-function-smp_call_function_mask.patch

Apply these patches and try the attached patch for KVM.

Laurent
-- 
---------------- Laurent.Vivier-6ktuUTfB/bM@public.gmane.org  -----------------
"Given enough eyeballs, all bugs are shallow" E. S. Raymond

[-- Attachment #1.1.2: smp_call_function_mask-kvm --]
[-- Type: text/plain, Size: 1470 bytes --]

Index: kvm/drivers/kvm/kvm_main.c
===================================================================
--- kvm.orig/drivers/kvm/kvm_main.c	2007-09-12 17:49:51.000000000 +0200
+++ kvm/drivers/kvm/kvm_main.c	2007-09-12 17:58:18.000000000 +0200
@@ -198,21 +198,15 @@ static void vcpu_put(struct kvm_vcpu *vc
 
 static void ack_flush(void *_completed)
 {
-	atomic_t *completed = _completed;
-
-	atomic_inc(completed);
 }
 
 void kvm_flush_remote_tlbs(struct kvm *kvm)
 {
-	int i, cpu, needed;
+	int i, cpu;
 	cpumask_t cpus;
 	struct kvm_vcpu *vcpu;
-	atomic_t completed;
 
-	atomic_set(&completed, 0);
 	cpus_clear(cpus);
-	needed = 0;
 	for (i = 0; i < KVM_MAX_VCPUS; ++i) {
 		vcpu = kvm->vcpus[i];
 		if (!vcpu)
@@ -221,23 +215,9 @@ void kvm_flush_remote_tlbs(struct kvm *k
 			continue;
 		cpu = vcpu->cpu;
 		if (cpu != -1 && cpu != raw_smp_processor_id())
-			if (!cpu_isset(cpu, cpus)) {
-				cpu_set(cpu, cpus);
-				++needed;
-			}
-	}
-
-	/*
-	 * We really want smp_call_function_mask() here.  But that's not
-	 * available, so ipi all cpus in parallel and wait for them
-	 * to complete.
-	 */
-	for (cpu = first_cpu(cpus); cpu != NR_CPUS; cpu = next_cpu(cpu, cpus))
-		smp_call_function_single(cpu, ack_flush, &completed, 1, 0);
-	while (atomic_read(&completed) != needed) {
-		cpu_relax();
-		barrier();
+			cpu_set(cpu, cpus);
 	}
+	smp_call_function_mask(cpus, ack_flush, NULL, 1);
 }
 
 int kvm_vcpu_init(struct kvm_vcpu *vcpu, struct kvm *kvm, unsigned id)

[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
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/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: kvm-45 problems

[Zhao, Yunfeng]

[-- Attachment #1: Type: text/plain, Size: 1372 bytes --]

Hi,Avi
With latest kvm commits,  the SMP linux guests causes host soft lock issues can not be reproduced on my machine.
Have you fixed it?

Thanks
Yunfeng

>-----Original Message-----
>From: Avi Kivity [mailto:avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org]
>Sent: 2007年10月9日 18:19
>To: Zhao, Yunfeng
>Cc: kvm-devel
>Subject: Re: [kvm-devel] kvm-45 problems
>
>Avi Kivity wrote:
>> Zhao, Yunfeng wrote:
>>
>>> We run some booting multiple guest tests in our nightly testing.
>>> Like booting two UP windows guests, booting one UP linux guest and one UP
>windows guest, and booting 4 UP linux guests.
>>> The first two cases have no problem in our testing.
>>> And booting 4 UP linux guests may crash host, but this problem doesn't happen
>very time. If the problem didn't happen, linux guest can be log in without any
>problem.
>>>
>>> For smp guest, we meet a problem that booting linux guest with 4 vcpus causes
>soft lock error on host. Once this error happened, qemu process also could not
>be killed.
>>>
>>> Our linux guests are using 2.6.9, 2.6.16, and 2.6.23 kernels.
>>>
>>>
>>>
>>
>> This may be due to NMIs or MCEs. Is it possible your machine is
>> receiving them?
>>
>
>
>I pushed a fix for the NMI issue. Can you check if it fixes your hangs?
>
>
>--
>error compiling committee.c: too many arguments to function


[-- Attachment #2: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
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/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: kvm-45 problems

[Avi Kivity]

[-- Attachment #1: Type: text/plain, Size: 329 bytes --]

Zhao, Yunfeng wrote:
> Hi,Avi
> With latest kvm commits,  the SMP linux guests causes host soft lock issues can not be reproduced on my machine.
> Have you fixed it?
>
>   

Not intentionally...

Maybe the rmap fix is somehow responsible.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.



[-- Attachment #2: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
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/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel