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.
Bug 1505330 - No dhcp on virbr0 on s390 in guest
Summary: No dhcp on virbr0 on s390 in guest
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.4-Alt
Hardware: s390x
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Libvirt Maintainers
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-23 10:58 UTC by Lukáš Doktor
Modified: 2017-11-02 17:53 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-02 17:53:29 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1503507 0 unspecified CLOSED libvirt doesn't set up the network properly 2021-02-22 00:41:40 UTC

Internal Links: 1503507

Description Lukáš Doktor 2017-10-23 10:58:09 UTC 
Description of problem:
I'm getting no responses in guest when using virbr0 provided by libvirt. The network seems to work well when the IP addr is assigned manually and bridge used by libvirt.

Version-Release number of selected component (if applicable):
Host: RHEL-ALT-7.5-20171017.n.0
Kernel: https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=606293
Qemu: https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=607145

How reproducible:
Always

Steps to Reproduce:
1. /usr/libexec/qemu-kvm -device virtio-scsi-ccw,id=virtio_scsi_ccw0 -drive id=drive_image1,if=none,format=qcow2,file=rhel
7devel-s390x.qcow2 -device scsi-hd,id=image1,drive=drive_image1 -snapshot -m 2G -nographic -nodefaults -chardev socket,
id=serial_id_serial0,path=/tmp/aaa,server,nowait -device sclpconsole,chardev=serial_id_serial0 -device virtio-net-ccw,n
etdev=net0,mac=DE:AD:BE:EF:AA:BB -netdev bridge,br=virbr0,id=net0

Actual results:
Machine boots, network card available, but no ipv4 address available and `dhclient -d eth0` does not show any answers. When IP address manually assigned, host and guest can communicate just well.

Expected results:
Machine should boot and obtain the IP address automatically

Additional info:
I tried creating machine with `virsh` and they also suffered the same issue. I also tried stop/start the network in virt-manager as well as create a new one without any luck.
Comment 2 Lukáš Doktor 2017-10-23 10:59:47 UTC 
I forgot to mention `user` network works well.
Comment 3 Laine Stump 2017-10-25 09:06:56 UTC 
Last week Rich filed Bug 1503507 against libvirt in Fedora Rawhide, with similar circumstances and symptoms. In particular, he was using qemu:///session (unprivileged libvirt) which uses qemu-bridge-helper to create the tap device and connect it to the bridge, and he also saw failure to acquire an IP with dhclient, but everything worked fine when an IP address was manually assigned.

His suspicion is that it is a host kernel issue, and I don't have an alternative explanation. If there is an older kernel you can try to see if the problem disappears, that would be useful information.
Comment 4 Lukáš Doktor 2017-11-02 17:53:29 UTC 
Today I tried the RHEL-ALT-7.4-20171102.n.0-Server-s390x-dvd1.iso and it worked well. Either it's because I used directly LPAR (previously it was z/vm) to run the guest or this was fixed. I'll re-open this if I see this issue again.
Note You need to log in before you can comment on or make changes to this bug.