1. Please describe the problem:
In the coreos-assembler ,we use supermin to create a qemu VM inside an F33 container (on a RHEL8 host). As part of the VM a virtioserialport is created:
Lately, we have seen error messages like this:
+ tee /dev/virtio-ports/cosa-cmdout
+ bash /srv/tmp/build.qemu/cmd.sh
tee: /dev/virtio-ports/cosa-cmdout: No such file or directory
which seem to suggest the device is not available.
When the kernel-core and kernel-modules packages were downgraded from 5.10.7-200.fc33.s390x to 5.9.16-200.fc33.s390x, the issue was doesn't show up.
After a little bit of testing - the build this started failing was : 5.10.6-200.fc33.s390x
This also happens on f32 when going from 5.9.16-100.fc32 --> 5.10.7-100.fc32
2. What is the Version-Release number of the kernel:
3. Did it work previously in Fedora? If so, what kernel version did the issue
*first* appear? Old kernels are available for download at
4. Can you reproduce this issue? If so, please provide the steps to reproduce
the issue below:
create a qemu VM with a virtio serial port and try to access it.
Actually I went back and tried kernel-5.10.0-98.fc33 and it had the same issue , so looks like the last build where this worked was 5.9.16-200.fc33.s390x
I think that the root cause is this change
+ # CONFIG_VIRTIO_CONSOLE is not set
introduced with the rebase to 5.10 in the s390x fedora configs with commit e18a08842c58c529ffcf0a8bca80776a5e14b3d5.
I'm in process to build and tests with the original kernel config option.
Which is caused by redhat/configs/pending-common/generic/s390x/CONFIG_VIRTIO_CONSOLE (setting N) overriding redhat/configs/common/generic/s390x/CONFIG_VIRTIO_CONSOLE (setting Y).
FEDORA-2021-e04cde3ff0 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-e04cde3ff0
FEDORA-2021-e04cde3ff0 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.