* KVM Test report, kernel 647e9e... qemu 7811d4...
@ 2010-03-08 6:40 Hao, Xudong
2010-03-24 15:17 ` Avi Kivity
0 siblings, 1 reply; 6+ messages in thread
From: Hao, Xudong @ 2010-03-08 6:40 UTC (permalink / raw)
To: kvm@vger.kernel.org
Hi, all,
This is KVM biweekly test result against kvm.git: 647e9ec3b543ea04d49a7323dfe0070682ed8465 and qemu-kvm.git: 7811d4e8ec057d25db68f900be1f09a142faca49.
In the last month, KVM testing was blocked by one qemu-img issue and two qemu build issues. Now the qemu build issue and qemu-img bug all get fixed.
One issue got fixed:
================================================
1. new Qemu-img can not create qcow image on read-only image
https://sourceforge.net/tracker/?func=detail&aid=2942075&group_id=180599&atid=893831
Four Old Issues:
================================================
1. Hot-added device is not visible in guest after migration
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2832416&group_id=180599
2. ltp diotest running time is 2.54 times than before
https://sourceforge.net/tracker/?func=detail&aid=2723366&group_id=180599&atid=893831
3. 32bits Rhel5/FC6 guest may fail to reboot after installation
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1991647&group_id=180599
4. perfctr wrmsr warning when booting 64bit RHEl5.3
https://sourceforge.net/tracker/?func=detail&aid=2721640&group_id=180599&atid=893831
5. [SR] qemu return form "migrate " command spend long time
https://sourceforge.net/tracker/?func=detail&aid=2942079&group_id=180599&atid=893831
Test environment
================================================
Platform A
Stoakley/Clovertown
CPU 4
Memory size 8G
Details
==========================================================================
Summary Test Report of Last Session
=====================================================================
Total Pass Fail NoResult Crash
=====================================================================
control_panel 17 13 4 0 0
gtest 23 21 2 0 0
=====================================================================
control_panel 17 13 4 0 0
:KVM_4G_guest_64_g32e 1 1 0 0 0
:KVM_four_sguest_64_gPAE 1 1 0 0 0
:KVM_LM_SMP_64_g32e 1 1 0 0 0
:KVM_linux_win_64_gPAE 1 1 0 0 0
:KVM_LM_SMP_64_gPAE 1 1 0 0 0
:KVM_SR_Continuity_64_gP 1 0 1 0 0
:KVM_four_sguest_64_g32e 1 1 0 0 0
:KVM_four_dguest_64_gPAE 1 1 0 0 0
:KVM_SR_SMP_64_gPAE 1 0 1 0 0
:KVM_LM_Continuity_64_g3 1 1 0 0 0
:KVM_1500M_guest_64_gPAE 1 1 0 0 0
:KVM_LM_Continuity_64_gP 1 1 0 0 0
:KVM_1500M_guest_64_g32e 1 1 0 0 0
:KVM_SR_Continuity_64_g3 1 0 1 0 0
:KVM_two_winxp_64_gPAE 1 0 1 0 0
:KVM_256M_guest_64_gPAE 1 1 0 0 0
:KVM_256M_guest_64_g32e 1 1 0 0 0
gtest 23 21 2 0 0
:boot_up_acpi_64_gPAE 1 1 0 0 0
:boot_up_noacpi_xp_64_gP 1 1 0 0 0
:boot_base_kernel_64_gPA 1 1 0 0 0
:boot_up_vista_64_g32e 1 1 0 0 0
:boot_smp_acpi_win2k3_64 1 0 1 0 0
:kb_nightly_64_gPAE 1 1 0 0 0
:boot_up_acpi_xp_64_g32e 1 1 0 0 0
:boot_smp_win7_ent_64_g3 1 1 0 0 0
:boot_smp_acpi_xp_64_gPA 1 0 1 0 0
:boot_smp_acpi_xp_64_g32 1 1 0 0 0
:boot_smp_vista_64_gPAE 1 1 0 0 0
:boot_up_acpi_64_g32e 1 1 0 0 0
:boot_base_kernel_64_g32 1 1 0 0 0
:kb_nightly_64_g32e 1 1 0 0 0
:boot_up_acpi_win2k3_64_ 1 1 0 0 0
:boot_up_win2008_64_gPAE 1 1 0 0 0
:ltp_nightly_64_g32e 1 1 0 0 0
:boot_smp_win2008_64_g32 1 1 0 0 0
:boot_up_vista_64_gPAE 1 1 0 0 0
:ltp_nightly_64_gPAE 1 1 0 0 0
:boot_smp_acpi_win2k3_64 1 1 0 0 0
:boot_up_noacpi_win2k3_6 1 1 0 0 0
:boot_smp_win7_ent_64_gP 1 1 0 0 0
=====================================================================
Total 40 34 6 0 0
Test environment
================================================
Platform B
Nehalem
CPU 8
Memory size 4G
Report Summary on IA32e on vt-nhm1
================================================
Summary Test Report of Last Session
=====================================================================
Total Pass Fail NoResult Crash
=====================================================================
control_panel_ept_vpid 12 10 2 0 0
control_panel_ept 4 4 0 0 0
control_panel 3 3 0 0 0
control_panel_vpid 3 3 0 0 0
gtest_vpid 1 1 0 0 0
gtest_ept 1 1 0 0 0
gtest 3 3 0 0 0
vtd_ept_vpid 8 5 3 0 0
gtest_ept_vpid 11 11 0 0 0
sriov_ept_vpid 6 0 5 1 0
=====================================================================
control_panel_ept_vpid 12 10 2 0 0
:KVM_LM_Continuity_64_g3 1 1 0 0 0
:KVM_four_dguest_64_g32e 1 1 0 0 0
:KVM_SR_SMP_64_g32e 1 0 1 0 0
:KVM_LM_SMP_64_g32e 1 1 0 0 0
:KVM_1500M_guest_64_gPAE 1 1 0 0 0
:KVM_linux_win_64_g32e 1 1 0 0 0
:KVM_1500M_guest_64_g32e 1 1 0 0 0
:KVM_two_winxp_64_g32e 1 1 0 0 0
:KVM_256M_guest_64_gPAE 1 1 0 0 0
:KVM_SR_Continuity_64_g3 1 0 1 0 0
:KVM_256M_guest_64_g32e 1 1 0 0 0
:KVM_four_sguest_64_g32e 1 1 0 0 0
control_panel_ept 4 4 0 0 0
:KVM_linux_win_64_g32e 1 1 0 0 0
:KVM_1500M_guest_64_g32e 1 1 0 0 0
:KVM_LM_SMP_64_g32e 1 1 0 0 0
:KVM_1500M_guest_64_gPAE 1 1 0 0 0
control_panel 3 3 0 0 0
:KVM_1500M_guest_64_g32e 1 1 0 0 0
:KVM_LM_SMP_64_g32e 1 1 0 0 0
:KVM_1500M_guest_64_gPAE 1 1 0 0 0
control_panel_vpid 3 3 0 0 0
:KVM_linux_win_64_g32e 1 1 0 0 0
:KVM_1500M_guest_64_g32e 1 1 0 0 0
:KVM_1500M_guest_64_gPAE 1 1 0 0 0
gtest_vpid 1 1 0 0 0
:boot_smp_win7_ent_64_g3 1 1 0 0 0
gtest_ept 1 1 0 0 0
:boot_smp_win7_ent_64_g3 1 1 0 0 0
gtest 3 3 0 0 0
:boot_smp_win2008_64_g32 1 1 0 0 0
:boot_smp_win7_ent_64_gP 1 1 0 0 0
:boot_smp_vista_64_g32e 1 1 0 0 0
vtd_ept_vpid 8 5 3 0 0
:one_pcie_smp_nomsi_64_g 1 1 0 0 0
:one_pcie_scp_64_g32e 1 1 0 0 0
:hp_pci_smp_nomsi_64_g32 1 0 1 0 0
:one_pcie_up_64_g32e 1 1 0 0 0
:lm_pcie_smp_64_g32e 1 0 1 0 0
:one_pcie_smp_64_g32e 1 1 0 0 0
:hp_pcie_smp_64_g32e 1 0 1 0 0
:hp_pcie_up_64_g32e 1 1 0 0 0
gtest_ept_vpid 11 11 0 0 0
:boot_up_acpi_64_g32e 1 1 0 0 0
:boot_base_kernel_64_g32 1 1 0 0 0
:boot_up_acpi_win2k3_64_ 1 1 0 0 0
:kb_nightly_64_g32e 1 1 0 0 0
:boot_up_vista_64_g32e 1 1 0 0 0
:ltp_nightly_64_g32e 1 1 0 0 0
:boot_smp_win2008_64_g32 1 1 0 0 0
:boot_up_acpi_xp_64_g32e 1 1 0 0 0
:boot_smp_acpi_win2k3_64 1 1 0 0 0
:boot_smp_win7_ent_64_g3 1 1 0 0 0
:boot_smp_acpi_xp_64_g32 1 1 0 0 0
sriov_ept_vpid 6 0 5 1 0
:one_vf_up_64_g32e 2 0 1 1 0
:hp_vf_up_64_g32e 1 0 1 0 0
:hp_vf_smp_64_g32e 1 0 1 0 0
:one_vf_smp_64_g32e 1 0 1 0 0
:two_dev_smp_64_g32e 1 0 1 0 0
=====================================================================
Total 52 41 10 1 0
Best Regards,
Xudong Hao
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: KVM Test report, kernel 647e9e... qemu 7811d4...
2010-03-08 6:40 KVM Test report, kernel 647e9e... qemu 7811d4 Hao, Xudong
@ 2010-03-24 15:17 ` Avi Kivity
2010-03-26 8:39 ` Hao, Xudong
0 siblings, 1 reply; 6+ messages in thread
From: Avi Kivity @ 2010-03-24 15:17 UTC (permalink / raw)
To: Hao, Xudong; +Cc: kvm@vger.kernel.org
On 03/08/2010 08:40 AM, Hao, Xudong wrote:
> Hi, all,
> This is KVM biweekly test result against kvm.git: 647e9ec3b543ea04d49a7323dfe0070682ed8465 and qemu-kvm.git: 7811d4e8ec057d25db68f900be1f09a142faca49.
>
> In the last month, KVM testing was blocked by one qemu-img issue and two qemu build issues. Now the qemu build issue and qemu-img bug all get fixed.
>
> 2. ltp diotest running time is 2.54 times than before
> https://sourceforge.net/tracker/?func=detail&aid=2723366&group_id=180599&atid=893831
>
Can you check the performance of this with cache=writeback?
The common on the report referring to cache=writethrough is incorrect (I
think?)
--
error compiling committee.c: too many arguments to function
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: KVM Test report, kernel 647e9e... qemu 7811d4...
2010-03-24 15:17 ` Avi Kivity
@ 2010-03-26 8:39 ` Hao, Xudong
2010-03-26 9:54 ` Avi Kivity
0 siblings, 1 reply; 6+ messages in thread
From: Hao, Xudong @ 2010-03-26 8:39 UTC (permalink / raw)
To: Avi Kivity; +Cc: kvm@vger.kernel.org
Avi Kivity wrote:
>>
>> 2. ltp diotest running time is 2.54 times than before
>> https://sourceforge.net/tracker/?func=detail&aid=2723366&group_id=180599&atid=893831
>>
>
> Can you check the performance of this with cache=writeback?
>
> The common on the report referring to cache=writethrough is incorrect
> (I think?)
Hi, Avi
I checked cache=writeback parameter, the diotest performance is much worse than "no this parameter"(about 20 times).
Followed qemu help, my command is "qemu-system-x86_64 -m 512 -smp 4 -net nic,macaddr=00:16:3e:79:0c:db,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -hda /share/ltp_guest.img -drive cache=writeback", is it right?
When booting guest with cache=writeback, there are some hdb drive Error printed in guest, and guest booting very slow.
Thanks,
Xudong
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: KVM Test report, kernel 647e9e... qemu 7811d4...
2010-03-26 8:39 ` Hao, Xudong
@ 2010-03-26 9:54 ` Avi Kivity
2010-03-28 9:03 ` Hao, Xudong
0 siblings, 1 reply; 6+ messages in thread
From: Avi Kivity @ 2010-03-26 9:54 UTC (permalink / raw)
To: Hao, Xudong; +Cc: kvm@vger.kernel.org
On 03/26/2010 11:39 AM, Hao, Xudong wrote:
>
> I checked cache=writeback parameter, the diotest performance is much worse than "no this parameter"(about 20 times).
>
> Followed qemu help, my command is "qemu-system-x86_64 -m 512 -smp 4 -net nic,macaddr=00:16:3e:79:0c:db,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -hda /share/ltp_guest.img -drive cache=writeback", is it right?
>
> When booting guest with cache=writeback, there are some hdb drive Error printed in guest, and guest booting very slow.
>
>
You need to fold the -hda parameter into -driver, so the whole command
line becomes
qemu-system-x86_64 -m 512 -smp 4 -net nic,macaddr=00:16:3e:79:0c:db,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -drive file=/share/ltp_guest.img,cache=writeback
-hda is deprecated, it forces cache=writethrough.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: KVM Test report, kernel 647e9e... qemu 7811d4...
2010-03-26 9:54 ` Avi Kivity
@ 2010-03-28 9:03 ` Hao, Xudong
2010-03-28 9:09 ` Avi Kivity
0 siblings, 1 reply; 6+ messages in thread
From: Hao, Xudong @ 2010-03-28 9:03 UTC (permalink / raw)
To: Avi Kivity; +Cc: kvm@vger.kernel.org
Avi Kivity wrote:
>
> You need to fold the -hda parameter into -driver, so the whole command
> line becomes
>
> qemu-system-x86_64 -m 512 -smp 4 -net
> nic,macaddr=00:16:3e:79:0c:db,model=rtl8139 -net
> tap,script=/etc/kvm/qemu-ifup -drive
> file=/share/ltp_guest.img,cache=writeback
>
>
> -hda is deprecated, it forces cache=writethrough.
Okay, cache=writeback can improve 28% performance of diotest, it cost 135 seconds which cost 182 sconds with cache=writethrough.
But in the report of bug, there was 2.53 times downgrade performance than before, so maybe still need somewhere tuning.
Thanks,
Xudong
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: KVM Test report, kernel 647e9e... qemu 7811d4...
2010-03-28 9:03 ` Hao, Xudong
@ 2010-03-28 9:09 ` Avi Kivity
0 siblings, 0 replies; 6+ messages in thread
From: Avi Kivity @ 2010-03-28 9:09 UTC (permalink / raw)
To: Hao, Xudong; +Cc: kvm@vger.kernel.org
On 03/28/2010 12:03 PM, Hao, Xudong wrote:
> Avi Kivity wrote:
>
>> You need to fold the -hda parameter into -driver, so the whole command
>> line becomes
>>
>> qemu-system-x86_64 -m 512 -smp 4 -net
>> nic,macaddr=00:16:3e:79:0c:db,model=rtl8139 -net
>> tap,script=/etc/kvm/qemu-ifup -drive
>> file=/share/ltp_guest.img,cache=writeback
>>
>>
>> -hda is deprecated, it forces cache=writethrough.
>>
> Okay, cache=writeback can improve 28% performance of diotest, it cost 135 seconds which cost 182 sconds with cache=writethrough.
> But in the report of bug, there was 2.53 times downgrade performance than before, so maybe still need somewhere tuning.
>
>
Can you try creating the image with
qemu-img create -f qcow2 -o cluster_size=4096 guest.img <size>
That reduces the cluster size to 4096, maybe that helps diotest.
--
error compiling committee.c: too many arguments to function
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2010-03-28 9:09 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-03-08 6:40 KVM Test report, kernel 647e9e... qemu 7811d4 Hao, Xudong
2010-03-24 15:17 ` Avi Kivity
2010-03-26 8:39 ` Hao, Xudong
2010-03-26 9:54 ` Avi Kivity
2010-03-28 9:03 ` Hao, Xudong
2010-03-28 9:09 ` Avi Kivity
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox