On 06.05.2017 00:38, FONNEMANN Mark wrote:
>> Could you run tcpdump inside the guest so we are sure what the nslookup call
>> emits?
>
> Is there another way to determine this info? My guest OS is an embedded
> system with BusyBox 1.25 and not much else.
FWIW, QEMU also has a built-in
>So, in your /etc/nsswitch.conf, use
>hosts: files dns
This resolved the problem. I am now able to do DNS queries using nslookup.
Thanks for all your help!
Mark.
FONNEMANN Mark, on sam. 06 mai 2017 04:18:52 +, wrote:
> >That's so weird there's no packet log. Does your guest perhaps have the
> >strace tool? Or perhaps you >can manage to copy it over from another VM,
> >since it only depends on libc.
>
> See attached file.
Ok, so for some reason it
FONNEMANN Mark, on sam. 06 mai 2017 01:06:31 +, wrote:
> root@qemu:~# /initrd/bin/nslookup www.google.com 10.0.2.3
> Server:10.0.2.3
> Address 1: 10.0.2.3
>
> nslookup: can't resolve 'www.google.com'
That's so weird there's no
>So it's supposed to be using 10.0.2.3 I guess. Just to make sure, you could try
>/initrd/bin/nslookup www.google.com 10.0.2.3
root@qemu:~# /initrd/bin/nslookup www.google.com 10.0.2.3
Server:10.0.2.3
Address 1: 10.0.2.3
nslookup:
FONNEMANN Mark, on sam. 06 mai 2017 00:33:40 +, wrote:
> >The attached patch should be dumping the same kind of information.
>
> Nslookup does not produce any output in curses or in logfile (-D logfile.txt).
Uh. So qemu can't be the culprit since it doesn't receive anything :)
>
>The attached patch should be dumping the same kind of information.
Nslookup does not produce any output in curses or in logfile (-D logfile.txt).
I tried it using the version installed on the root system (Busybox 1.0):
root@qemu:~# nslookup
BusyBox v1.00
FONNEMANN Mark, on ven. 05 mai 2017 22:38:20 +, wrote:
> >Could you run tcpdump inside the guest so we are sure what the nslookup call
> >emits?
>
> Is there another way to determine this info? My guest OS is an embedded
> system with BusyBox 1.25 and not much else.
The attached patch
>Could you run tcpdump inside the guest so we are sure what the nslookup call
>emits?
Is there another way to determine this info? My guest OS is an embedded system
with BusyBox 1.25 and not much else.
Mark.
FONNEMANN Mark, on dim. 30 avril 2017 12:42:41 +, wrote:
> root@qemu:~# nslookup www.google.com
>*** Unknown host
>
>nslookup: www.google.com: Unknown host
Could you run tcpdump inside the guest so we are sure what the nslookup
call emits?
Samuel
>Could you show us your NG.cfg, your guest /sbin/ifconfig and /sbin/route
>output and /etc/resolv.conf >content for that host?
[mfonnemann@desktopPC qemu]$ cat NG.cfg
[drive]
format = "raw"
file = "qemu_rootfs_512.img"
[drive]
format = "raw"
file = "placeholder2.vhdx"
[drive]
format
FONNEMANN Mark, on sam. 29 avril 2017 23:15:08 +, wrote:
> [mfonnemann@desktopPC qemu]$ /usr/local/bin/qemu-system-i386 -display curses
> -readconfig NG.cfg --enable-kvm
Could you show us your NG.cfg, your guest /sbin/ifconfig and /sbin/route
output and /etc/resolv.conf content for that
>Ah, you are using curses... I've been putting logs onto stderr for simplicity,
>not the proper qemu logs. Here is a fixed patch to get output in the log.
OK, I have an interesting development that I hope will shed some light on the
problem.
This configuration works using a different image
Hello-
>One first thing to note: the DNS or SMB servers can not be pinged, since that
>was never implemented (I'll post a patch for that), so there is no surprise on
>that end.
OK
>When running with a Linux host (since that's what I'm most familiar with),
>what do you have in
FONNEMANN Mark, on sam. 29 avril 2017 20:06:09 +, wrote:
> [mfonnemann@localhost qemu]$ /usr/local/bin/qemu-system-i386 -display curses
> -readconfig qemu.cfg -D logfile
Ah, you are using curses... I've been putting logs onto stderr for
simplicity, not the proper qemu logs. Here is a fixed
>Ok, so nothing going out from qemu. Could you try to apply the attached patch
>to qemu-2.9 and see what it makes qemu print when you resolve a domain from
>the guest?
After applying patch, compiling, installing and then doing a nslookup request
in the guest, I still receive no output in
FONNEMANN Mark, on sam. 29 avril 2017 18:25:26 +, wrote:
> 0 packets received by filter
Ok, so nothing going out from qemu. Could you try to apply the attached
patch to qemu-2.9 and see what it makes qemu print when you resolve a
domain from the guest?
Samuel
--- a/slirp/socket.c
+++
Hello-
>And I guess these do work fine on the host.
Yes:
[mfonnemann@localhost ~]$ nslookup www.google.com
Server: 4.2.2.1
Address:4.2.2.1#53
Non-authoritative answer:
Name: www.google.com
Address: 172.217.11.4
>Perhaps you should make sure that qemu does emit the DNS lookup
FONNEMANN Mark, on sam. 29 avril 2017 15:32:35 +, wrote:
> >When running with a Linux host (since that's what I'm most familiar with),
> >what do you have in /etc/resolv.conf?
>
> [mfonnemann@localhost ~]$ cat /etc/resolv.conf
> # Generated by NetworkManager
> nameserver 4.2.2.1
> nameserver
Hello,
FONNEMANN Mark, on mer. 19 avril 2017 18:11:59 +, wrote:
> I have tested 2.9-rc4 and the problem still exists there as well.
FONNEMANN Mark, on lun. 24 avril 2017 23:43:02 +, wrote:
> I just confirmed that the problem exists in 2.9 release using
> qemu-system-i386.exe as well.
-Original Message-
From: Stefan Weil [mailto:s...@weilnetz.de]
Sent: Friday, April 21, 2017 15:58
To: FONNEMANN Mark <mark.fonnem...@hexagon.com>; qemu-devel@nongnu.org; Samuel
Thibault <samuel.thiba...@gnu.org>
Subject: Re: [Qemu-devel] dns server not working in QEMU us
-Original Message-
From: Thomas Huth [mailto:th...@redhat.com]
Sent: Monday, April 24, 2017 04:00
To: FONNEMANN Mark <mark.fonnem...@hexagon.com>; qemu-devel@nongnu.org
Cc: Samuel Thibault <samuel.thiba...@ens-lyon.org>
Subject: Re: [Qemu-devel] dns server not working i
On 13.04.2017 22:17, FONNEMANN Mark wrote:
> Hello-
>
> I posted this question on stack overflow and got no response. Stefan
> recommended asking the question here.
>
> I’ve included a summary of the problem here in this email but more details
> can be found here:
>
>
Stefan Weil, on ven. 21 avril 2017 21:58:18 +0200, wrote:
> Am 17.04.2017 um 00:10 schrieb FONNEMANN Mark:
> > I hadn't seen the original report on the list, sorry. There is too much
> > traffic on qemu-devel for me to manage to catch these :/
> >
> > This problem was fixed by
> > e42f869b
ct: Re: [Qemu-devel] dns server not working in QEMU using usermode
networking (SLIRP)
Hello,
I hadn't seen the original report on the list, sorry. There is too much traffic
on qemu-devel for me to manage to catch these :/
This problem was fixed by
e42f869b ("slirp: Make RA build mo
This issue still exists for me in 2.9 rc4.
-Original Message-
From: Samuel Thibault [mailto:samuel.thiba...@gnu.org]
Sent: Sunday, April 16, 2017 04:10
To: FONNEMANN Mark <mark.fonnem...@hexagon.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] dns server not working i
Hello,
I hadn't seen the original report on the list, sorry. There is too much
traffic on qemu-devel for me to manage to catch these :/
This problem was fixed by
e42f869b ("slirp: Make RA build more flexible") and
a2f80fdf ("slirp: Send RDNSS in RA only if host has an IPv6 DNS server")
which
This has been filed as a bug: https://bugs.launchpad.net/qemu/+bug/1683084.
Mark.
Hello-
I posted this question on stack overflow and got no response. Stefan
recommended asking the question here.
I’ve included a summary of the problem here in this email but more details can
be found here:
29 matches
Mail list logo
