Bug 967780
Summary: | Bad perfomance in virt-install (network boot) | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Igor Gnatenko <ignatenko> | ||||
Component: | virt-manager | Assignee: | Cole Robinson <crobinso> | ||||
Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 19 | CC: | awilliam, berrange, crobinso, hbrock, ignatenko, jforbes, virt-maint | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2013-06-12 19:59:18 UTC | Type: | Bug | ||||
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: | 834091 | ||||||
Attachments: |
|
Description
Igor Gnatenko
2013-05-28 10:33:30 UTC
Proposed as a Freeze Exception for 19-final by Fedora user ignatenkobrain using the blocker tracking app because: Virtualization load from network imho shall work I can't reproduce this exactly. CPU load does seem to be generally higher in the kernel pair boot case where anaconda itself is retrieved from the remote repo, but I don't ever see it 'stick' at 100%. if I do a kernel pair boot and pass 'inst.repo=http://dl.fedoraproject.org/pub/fedora/linux/development/19/x86_64/os/' then I see 100% CPU use for a short time during installer init, then it drops, then spikes to 100% for a while longer while 'calculating dependencies', then drops to almost 0% as long as I just sit on hub. when I start an install it again spikes to 100% a couple of times while partitioning, then when it settles into package installation, it tends to bounce between 20-30% and 100%. But at no point does it just 'stick' at 100% usage, and the times when it's at 100% seem to be reasonably related to actual operations happening at that point in time. Given lack of reproducer in Comment #2 and no follow up, closing. If someone can still reproduce, please reopen. |