Bug 1473604 - DNS problems in qemu user networking
Summary: DNS problems in qemu user networking
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: qemu
Version: 26
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Fedora Virtualization Maintainers
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-21 09:31 UTC by Jan ONDREJ
Modified: 2017-08-10 06:06 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-26 05:22:06 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jan ONDREJ 2017-07-21 09:31:29 UTC
Description of problem:
Currently DNS is completely broken in qemu. Trying to boot Fedora 26 netboot image with.

Version-Release number of selected component (if applicable):
qemu-kvm-2.9.0-1.fc26.1.x86_64
dnsmasq-2.76-3.fc26.x86_64

How reproducible:
always

Steps to Reproduce:
1. qemu-kvm -m 2000 -cdrom Fedora-Server-netinst-x86_64-26-1.5.iso -net user -net nic
2. curl -v http://www.redhat.com/

Actual results:
* Could not resolve host: www.redhat.com

Comment 1 Jan ONDREJ 2017-07-26 05:22:06 UTC
Works well with latest qemu-kvm-2.9.0-3.fc26.x86_64.
Thanks to all.

Comment 2 Cole Robinson 2017-07-26 14:56:12 UTC
(In reply to Jan ONDREJ from comment #1)
> Works well with latest qemu-kvm-2.9.0-3.fc26.x86_64.
> Thanks to all.

Glad it works but -3 didn't have anything explicitly targeted at this issue, just a bunch of corner case CVE fixes. So keep an eye out maybe it's still lingering

Comment 3 Jan ONDREJ 2017-07-26 15:02:40 UTC
(In reply to Cole Robinson from comment #2)
> Glad it works but -3 didn't have anything explicitly targeted at this issue,
> just a bunch of corner case CVE fixes. So keep an eye out maybe it's still
> lingering

Hmm, but still works. May be there was other update, which fixed this (selinux, dnsmasq, kernel, ...).

Trying to downgrade qemu and still works, I agree, that this didn't fixed this. If repeats, then I reopen it.

Comment 4 Jan ONDREJ 2017-08-10 06:06:58 UTC
Just for info, I found, what is the problem. My local named-chroot sometimes start and sometime don't after reboot, according to speed of network service startup. Looks like qemu can't use secondary DNS server from resolv.conf.
May be this can be a feature request to add usage of secondary nameservers.


Note You need to log in before you can comment on or make changes to this bug.