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.
Description of problem:
Boot a guest with "-netdev socket,id=test,connect=:12233", guest boot failed.
Version-Release number of selected component (if applicable):
Host:
3.10.0-653.el7.ppc64le
qemu-kvm-rhev-2.9.0-1.el7.ppc64le
SLOF-20170303-1.git66d250e.el7.noarch
How reproducible:
3/3
Steps to Reproduce:
1.Boot a guest with following qemu cli
/usr/libexec/qemu-kvm -device virtio-net-pci,netdev=test,mac=9a:7b:7c:7d:7e:71 -netdev socket,id=test,connect=:12233
2.
3.
Actual results:
Boot guest failed
qemu-kvm: -netdev socket,id=test,connect=:12233: address resolution failed for :12233: Name or service not known
qemu-kvm: -netdev socket,id=test,connect=:12233: Device 'socket' could not be initialized
Expected results:
Boot guest successfully.
Additional info:
This bug is also hit on x86_64,so modify the hardware to "all"
3.10.0-648.el7.x86_64
qemu-kvm-rhev-2.9.0-1.el7.x86_64
seabios-1.10.2-1.el7.x86_64
# /usr/libexec/qemu-kvm -device virtio-net-pci,netdev=test,mac=9a:7b:7c:7d:7e:71 -netdev socket,id=test,connect=:12233
qemu-kvm: -netdev socket,id=test,connect=:12233: address resolution failed for :12233: Name or service not known
qemu-kvm: -netdev socket,id=test,connect=:12233: Device 'socket' could not be initialized
This bug is a regression, it doesn't exist for qemu-kvm-rhev-2.6.0-27.el7
3.10.0-653.el7.ppc64le
qemu-kvm-rhev-2.6.0-27.el7.ppc64le
SLOF-20170303-1.git66d250e.el7.noarch
# /usr/libexec/qemu-kvm -device virtio-net-pci,netdev=test,mac=9a:7b:7c:7d:7e:71 -netdev socket,id=test,connect=:12233
VNC server running on '::1;5900'
Boot guest successfully.
So, it is a regression.
(In reply to jason wang from comment #5)
> Can you do a bisection to find the first bad commit?
>
> Thanks
The first bad commit id is:
commit 2d02ac10b6644d71c88cc7943e74d7ad6674fff1