05.05.2011 09:28, Jonathan Nieder wrote: > m...@tls.msk.ru wrote: >> Usual cause of DNS errors in case of user-mode networking is >> a wrong list of nameservers in _host_ /etc/resolv.conf. Verify >> that the nameserver listed in there _first_ is functioning - >> qemu will only try first. > > I see. Yep, that explains it[] > > Cloning the bug. Is this limitation documented anywhere? and would > it be possible to fix?
No the limitation isn't documented (yet), and it will be difficult to fix too, or maybe not worth a trouble really. Two reasons. First of all, user-mode networking is not suitable for anything serious, you really want tap networking with bridges, which is about 100 times faster and actually works (e.g. ICMP). Second, the implementation is rather simplistic - for DNS it merely forwards (like a NAT box) packets from guest to a nameserver from host /resolv.conf - only one nameserver, because you can't NAT to TWO destinations at once. So in order to fix that, qemu has to become application-level proxy for DNS, instead of a simple NAT "device". But for documentation, indeed, it's a valid point. However it _is_ already documented, sort of: every guide will tell you that you shouldn't use user-mode networking to start with :) Kidding really, it _is_ a valid point. /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
