|
Bugzilla – Full Text Bug Listing |
| Summary: | Yast Xen Manager - Slow start, no busy pointer | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Tom Miller <madprogextrodinr> |
| Component: | YaST2 | Assignee: | Clyde Griffin <cgriffin> |
| Status: | RESOLVED WONTFIX | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Tom Miller
2007-01-28 17:03:00 UTC
This takes a long time to load, because it's connecting to the package database and ensuring that all the xen packages are installed. I think the slowness is actually in libzypp. Going forward, yast2-vm has been split: the yast tool has been streamlined and only checks the configuration, and it is faster now. The VM installation process is a separate tool, which also starts much faster. I don't think this large change won't be backported to 10.2, but it'll be in SLES10 SP1 and 10.3. I agree that you shouldn't back port the changes of splitting things up. What I would hope you would add is additional busy pointer calls for each step that you described above so that at least you see that it is processing vs thinking that the click processed for 20 seconds and then failed. I would think forcing the busy pointer would be easy to do, low risk to the code base. The new tool mentioned in comment #1 has the problem fixed in it and the old tool which exists in openSuse 10.2 is deprecated and will not be fixed. Sorry for the inconvenience. |