Red Hat Bugzilla – Bug 1247434
virt-install gives incorrect warning about console=ttyS0
Last modified: 2016-11-03 21:58:01 EDT
Description of problem:
When installing a guest on Power using virt-install with a "serial" console (actually the paravirtualized hypervisor console), virt-install gives this warning:
WARNING No 'console' seen in --extra-args, a 'console=ttyS0'
kernel argument is likely required to see text install output
from the guest.
This warning is incorrect on two counts: 1) the console= argument is not actually necessary because the Power kernel/userspace automatically use the hypervisor console as well a a graphical console if present, 2) to explicitly select the hypervisor console, the correct argument is console=hvc0, not console=ttyS0 (since it's not actually a serial console).
Basically, for Power systems, having only the hypervisor console, but not VGA console is the normal, rather than the exceptional case.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. virt-install \
--name test \
--location http://download.lab.bos.redhat.com/.../os/ \
--graphics none \
--network network=default,model=virtio \
Installer prints the warning described above before continuing successfully with installation.
Installation runs without warning.
Author: Pavel Hrdina <email@example.com>
Date: Mon Nov 9 15:15:43 2015 +0100
virt-install: don't report missing console in extra-args for ppc64
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see firstname.lastname@example.org with any questions
I can reproduce it with virt-manager-1.2.1-8.el7.noarch.
# virt-install --name testvm --memory 1024 --disk /var/lib/libvirt/images/testvm.img,size=5 -l http://download.eng.pek2.redhat.com//pub/rhel/released/RHEL-7/7.2/Server/ppc64le/os/ --graphics none
WARNING No 'console' seen in --extra-args, a 'console=ttyS0' kernel argument is likely required to see text install output from the guest.
Then verified it with latest virt-manager-1.4.0-1.el7.noarch, No above warning any more.
So 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.