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.

I couldn't find any documentation about these parameter being deprecated or dropped, assuming this is a bug.

Testing oVirt Node in automation we use a call:


  virt-install -d \
        --name "$name" \
        --boot menu=off \
        --memory $MAX_VM_MEM \
        --vcpus $MAX_VM_CPUS \
        --cpu host \
        --location "${CENTOS_INSTALLATION_SOURCE}" \
        --extra-args "inst.ks=file:///node-install.ks console=ttyS0 inst.sshd=1" \
        --initrd-inject $ksfile \
        --check disk_size=off,path_in_use=off \
        --graphics none \
        --noreboot \
        --wait -1 \
        --os-variant rhel8.5 \
        --noautoconsole \
        --rng /dev/urandom \
        --network network:${LIBVIRT_NETWORK},model=virtio  \
        --disk path=$diskimg,bus=virtio,cache=unsafe,discard=unmap,format=qcow2 \
        --disk path=$squashfs,readonly=on,device=disk,bus=virtio,serial=livesrc \
        > $logfile 2>&1 || die "virt-install failed"

which worked fine on CentOS Stream 8 but is now failing on CentOS Stream 9 with:


virt-install: error: unrecognized arguments: inst.sshd=1 console=ttyS0

Hi, can you please provide the debug log as well? I've noticed that you already run the command with `-d`.

I can't reproduce this issue on RHEL-9 host:

Packages version:
libvirt-7.7.0-2.el9.x86_64
qemu-kvm-6.1.0-2.el9.x86_64
virt-install-3.2.0-9.el9.noarch


Command-line:
virt-install -d \
--name testvm2 \
--boot menu=off \
--memory 4096 \
--vcpus 4 \
--cpu host \
--location http://download.eng.pek2.redhat.com/rhel-8/rel-eng/RHEL-8/RHEL-8.5.0-20210902.5/compose/BaseOS/x86_64/os/ \
--extra-args "inst.ks=http://fileshare.englab.nay.redhat.com/pub/section3/run/http-ks/ks-rhel8u4-x86_64.cfg console=ttyS0 inst.sshd=1" \
--initrd-inject /home/ks-rhel8u4-x86_64.cfg  \
--check disk_size=off,path_in_use=off \
--graphics none \
--noreboot \
--wait -1 \
--os-variant rhel8.5 \
--noautoconsole \
--rng /dev/urandom \
--network network:default,model=virtio  \
--disk path=/home/testvm2.img,bus=virtio,cache=unsafe,discard=unmap,format=qcow2,size=10 \
> virt-install-debug.log 2>&1 

Test result: VM can be installed successfully.

Debug log - virt-install-debug.log

Sandro, QE did not reproduce it. Could it be a params quoting problem?

If you still hit the problem, please provide versions of packages you used and debug log from the installation. Thanks.

It was indeed a quoting problem, sorry for the noise