Bug 601497
Summary: | RHEL4 guest diskdump with ide emulated device too slow | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Qian Cai <qcai> | ||||
Component: | qemu-kvm | Assignee: | Gleb Natapov <gleb> | ||||
Status: | CLOSED WONTFIX | QA Contact: | Virtualization Bugs <virt-bugs> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 6.0 | CC: | clalance, cye, knoel, mkenneth, rwheeler, tburke, virt-maint | ||||
Target Milestone: | rc | ||||||
Target Release: | 6.1 | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2011-03-24 10:25:52 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 524819, 580953 | ||||||
Attachments: |
|
Description
Qian Cai
2010-06-08 05:39:31 UTC
Created attachment 422036 [details]
guest xml
The vmcore is only around 300M, and it took around a hour to dump it... # du -sh 127.0.0.1-2010-06-08-05\:37/vmcore 273M 127.0.0.1-2010-06-08-05:37/vmcore Why is that a blocker? At least it works.. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion. Is this the same timer/interrupt problem causing problem with all kdump scenarios under KVM? Chris, could this be the IRQ routing issue you fixed upstream? This issue has been proposed when we are only considering blocker issues in the current Red Hat Enterprise Linux release. It has been denied for the current Red Hat Enterprise Linux release. ** If you would still like this issue considered for the current release, ask your support representative to file as a blocker on your behalf. Otherwise ask that it be considered for the next Red Hat Enterprise Linux release. ** CAI, please answer the above questions I am not sure. I'll need to re-test it on the latest RHEL6 bits to make sure. I tested with RHEL6-RC4, and installed RHEL4-U8-AS. And IDE disk was used as dump device. ===================================================================== First time I used hda1 as dump target, size is around 10GB. [root@dhcp70-103 ~]# du -sh /var/crash/* 206M /var/crash/127.0.0.1-2010-09-27-21:37 ===>Took around 30mins. 158M /var/crash/127.0.0.1-2010-09-27-22:22 ===>Took around 8mins. 401M /var/crash/127.0.0.1-2010-09-27-22:34 ===>Took around 8mins. Second time I resized hda1, new size is around 1GB. The process became more quick. [root@dhcp70-103 ~]# du -sh /var/crash/* ... 492M /var/crash/127.0.0.1-2010-09-27-22:53 ===>Took around 5mins. 494M /var/crash/127.0.0.1-2010-09-27-23:04 ===>Took around 5mins. 495M /var/crash/127.0.0.1-2010-09-27-23:21 ===>Took around 6mins. Third time I used a new dump target, size is around 10GB. [root@dhcp70-103 ~]# du -sh /var/crash/* ... 499M /var/crash/127.0.0.1-2010-09-28-02:20 ===>Took around 10mins. Seems the performance is not very stable. The question is if the above is reasonable or too slow. I rather optimize virtio-blk instead of investing time in ide. Can you please measure virtio time? Also, where is the bottle neck - cpu on the guest/host? IO? kvm_stat data? There is a bug prevent diskdump working with virtio - BZ#601491. |