Bug 8804

Summary: Unable to connect to qemu on CentOS
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Mihail Stanciu <stanciux.mihail>
Component: connectivityAssignee: Cristian Iorga <cristian.iorga>
Status: VERIFIED DUPLICATE QA Contact: Mihail Stanciu <stanciux.mihail>
Severity: normal    
Priority: Medium CC: meta.mr.watcher, meta.watcher, sgw
Version: 2.1   
Target Milestone: 2.1 M2   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: Regression (Used to work)
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
qemu ping fail none

Description Mihail Stanciu 2015-12-14 13:41:23 UTC
Created attachment 2898 [details]
qemu ping fail

Tested on master: 5e3e2e0cbb0a49986f4653e64c4c8d2b5461645e
OS affected: Centos 7.1 (only; other OS are not affected)

Steps to reproduce:
1. Build core-image-sato for any qemu machine
2. Start qemu machine in nographic mode

Expected:
Ping/ssh connection from host machine(192.168.7.1) to qemu(192.168.7.2) should work

Observed:
Any attempts at communication between host and qemu fail.

Additional notes:
Tap interface on host machine was pre-configured.
Made sure that interfaces are up and running on both host and qemu machines.

See attachment for full log.
Comment 1 Saul Wold 2016-01-27 00:13:57 UTC
I reset the tap devices with the runqemu-gen-tapdevs and that seems to have resolved the problem, it may be that the networkmanager somehow changed the tapdev ip, I have seen this with my Fedora install.
Comment 2 Mihail Stanciu 2016-01-27 09:38:18 UTC
(In reply to comment #1)
> I reset the tap devices with the runqemu-gen-tapdevs and that seems to have
> resolved the problem, it may be that the networkmanager somehow changed the
> tapdev ip, I have seen this with my Fedora install.

I've disabled the NetworkManager for now and restarted the tests.

I'll update once tests complete.
Comment 3 Mihail Stanciu 2016-02-04 10:13:36 UTC
Redoing the workaround for bug 8587 seems to have fixed this issue.

Due to this development, I will mark this as a duplicate of bug 8587.

*** This bug has been marked as a duplicate of bug 8587 ***
Comment 4 Mihail Stanciu 2016-02-04 10:13:58 UTC
Verified duplicate.