Bug 1445164

Summary:	Boot guest failed with : -netdev socket,id=test,connect=:12233: Device 'socket' could not be initialized
Product:	Red Hat Enterprise Linux 7	Reporter:	xianwang <xianwang>
Component:	qemu-kvm-rhev	Assignee:	jason wang <jasowang>
Status:	CLOSED DUPLICATE	QA Contact:	xiywang
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.4	CC:	ailan, chayang, coli, juzhang, knoel, michen, pezhang, qzhang, stefanha, thuth, virt-maint, xianwang, xiywang
Target Milestone:	rc	Keywords:	Regression
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-06-01 06:53:22 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description xianwang 2017-04-25 07:29:16 UTC

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:

Comment 2 xianwang 2017-04-25 07:53:33 UTC

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

Comment 3 xianwang 2017-04-25 07:58:31 UTC

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.

Comment 5 jason wang 2017-05-04 08:16:12 UTC

Can you do a bisection to find the first bad commit?

Thanks

Comment 6 xianwang 2017-05-05 07:00:12 UTC

(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

Comment 7 Stefan Hajnoczi 2017-05-08 17:55:29 UTC

Please see Daniel Berrange's recent revert patch: https://lists.nongnu.org/archive/html/qemu-devel/2017-05/msg01348.html

Comment 8 jason wang 2017-05-17 07:29:58 UTC

Acked on the revert, wait it to be merged upstream (should be soon).

Thanks

Comment 9 jason wang 2017-06-01 06:53:22 UTC


*** This bug has been marked as a duplicate of bug 1451629 ***