Bug 890494
Summary: | Some issues about verifying SMBIOS values in domain xml and doc | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | hongming <honzhang> |
Component: | libvirt | Assignee: | John Ferlan <jferlan> |
Status: | CLOSED WONTFIX | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.4 | CC: | acathrow, cwei, dyuan, gsun, lsu, mzhan |
Target Milestone: | rc | Keywords: | Upstream |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-04-04 20:59:15 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: |
Description
hongming
2012-12-27 09:59:00 UTC
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux. I test in libvirt -16 version. For a) same xml in guest , in guest it shows Handle 0x0000, DMI type 0, 24 bytes BIOS Information Vendor: Seabios Version: 0.5.1 Release Date: 01/01/2007 Address: 0xE8000 Runtime Size: 96 kB ROM Size: 64 kB Characteristics: BIOS characteristics not supported Targeted content distribution is supported BIOS Revision: 1.0 b) it report an error error: internal error UUID mismatch between <uuid> and <sysinfo> c) just delete , no error report Is there alreday a patch covering the bug ? a. Validating the 'date' is possible; however, your assertion about 'release' being a date is incorrect. It is the System BIOS Major and Minor release. This is passed as a string to the underlying hypervisor driver. Knowing what is and isn't valid is not something easily discernible by libvirt. Theoretically, it would be of a format <major>.<minor> if both are provided, but it's also possible to just provide the <major> value since the two values would be contiguous in a Type 0 block. b. Mismatched uuid's were fixed by upstream commit '4117672ea' which appears in libvirt v0.8.7; however, that doesn't seem to be the original complaint. The original complaint was that adding additional "-" to the uuid could have caused an error (an easily missed nuance of the complaint) depending on the placement of the "-". If added within any byte pairing, then the change would be flagged as a "malformed uuid element"; however, if added between any byte pairing, then the change would be OK according to virUUIDParse() rules. However, since guest startup was disallowed with the incorrectly placed "-", the code will be changed in order to make the proper checks. c. This is not possible as the parsing code looks for specific strings and will only save those that it finds. The code does not look for invalid strings nor are the existing interfaces designed to loop through a list of "valid" entries and signal when an "invalid" entry is discovered. I will be sending patches for 'a' and 'b' upstream shortly. A change has been submitted/pushed upstream, see: https://www.redhat.com/archives/libvir-list/2013-May/msg00940.html Development Management has reviewed and declined this request. You may appeal this decision by reopening this request. |