| Summary: | RFE: provide lspci, dmidecode outputs | ||
|---|---|---|---|
| Product: | [Retired] Beaker | Reporter: | Tomáš Bžatek <tbzatek> |
| Component: | inventory | Assignee: | beaker-dev-list |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | low | ||
| Version: | 0.8 | CC: | amahdal, arozansk, bpeck, cbouchar, crose, mcsontos, prarit, stl, tools-bugs, tsmetana |
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | Inventory | ||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-11-19 22:19:11 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Tomáš Bžatek
2011-12-05 17:06:33 UTC
(In reply to Tomáš Bžatek from comment #0) > It would be nice if we could display outputs of lspci, dmidecode and > /proc/cpuinfo directly from beaker web UI, for the particular machine. A > plain text file would do the trick, I find it easier to read than the parsed > information in the table. Thanks This will be very helpful. I recently needed DIMM slots and memory in each slot (for rasdaemon work) and it would have saved me hours if I had dmidecode output available on beaker UI. *** Bug 1199986 has been marked as a duplicate of this bug. *** How dependent are dmidecode and lscpi output on the kernel? Won't the output differ depending on which distro was used to scan the system and find the output of these commands? I have seen differing contents in /proc/cpuinfo depending on the kernel version (bug 1223115) (In reply to Amit Saha from comment #6) > How dependent are dmidecode and lscpi output on the kernel? Won't the output > differ depending on which distro was used to scan the system and find the > output of these commands? > > I have seen differing contents in /proc/cpuinfo depending on the kernel > version (bug 1223115) lspci may depend on how recent the PCI IDs file is on the particular version of OS, but dmidecode has been relatively stable over the past 5 years so I don't see it varying that much. P. Hi, I'd like to ask if this feature would still be helpful in order to determine priority in our backlog. What output would be most helpful of the three mentioned in comment 1: lspci, dmidecode and /proc/cpuinfo ? (In reply to Roman Joost from comment #8) > Hi, > > I'd like to ask if this feature would still be helpful in order to determine > priority in our backlog. What output would be most helpful of the three > mentioned in comment 1: lspci, dmidecode and /proc/cpuinfo ? Hi -- yes, this information is useful for each system because we can quickly search in this data. To start, I think /proc/cpuinfo is the most useful. However, we would only need the output of a single cpu. P. (In reply to Roman Joost from comment #8) > Hi, > > I'd like to ask if this feature would still be helpful in order to determine > priority in our backlog. What output would be most helpful of the three > mentioned in comment 1: lspci, dmidecode and /proc/cpuinfo ? dmidecode has BIOS version and DIMM information which is very useful. lspci helps with tracking down peripherals (include subvendor/device ID). Thanks guys for letting me know. |