Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+++ This bug was initially created as a clone of Bug #1707379 +++
"virt-install ... --sysinfo foobar" silently defaults to smbios type.
We should pass that value to libvirt and libvirt validate it and error
out if it's incorrect.
I can reproduce this issue with package:
virt-manager-1.5.0-4.el7.noarch
Steps:
1. Install a vm with specified a invalid type to "--sysinfo".
# virt-install --name testvm --memory 1024 --boot initargs="none",smbios_mode=sysinfo --sysinfo foobar --disk none --debug
WARNING No operating system detected, VM performance may suffer. Specify an OS with --os-variant for optimal results.
Starting install...
...
<sysinfo type='smbios'/>
<os>
<type arch='x86_64' machine='pc-i440fx-rhel7.6.0'>hvm</type>
<boot dev='hd'/>
<smbios mode='sysinfo'/>
</os>
Result: Installation starts successfully with invalid sysinfo type, silently defaults to smbios type.
Then try to verify this bug with new build:
virt-manager-1.5.0-5.el7.noarch
libvirt-4.5.0-17.el7.x86_64
qemu-kvm-rhev-2.12.0-28.el7.x86_64
Steps:
# virt-install --name testvm --memory 1024 --boot initargs="none",smbios_mode=sysinfo --sysinfo foobar --disk none
WARNING No operating system detected, VM performance may suffer. Specify an OS with --os-variant for optimal results.
Starting install...
ERROR unsupported configuration: unknown sysinfo type 'foobar'
Domain installation does not appear to have been successful.
If it was, you can restart your domain by running:
virsh --connect qemu:///system start testvm
otherwise, please restart your installation.
Result: virt-install fails to start with clear error prompts "unsupported configuration: unknown sysinfo type 'foobar'", so I move this bug from ON_QA to VERIFIED.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2019:2232