Just make sure you add it properly, because resolv.conf can be overwritten by network manager. Something like: nmcli con mod <net interface> +ipv4.dns "127.0.0.1" Martin On Thu, Feb 18, 2016 at 12:35 PM, Michal Skrivanek <michal.skrivanek@redhat.com> wrote:
On 18 Feb 2016, at 10:44, Roy Golan <rgolan@redhat.com> wrote:
On Tue, Feb 16, 2016 at 2:45 PM, Roman Mohr <rmohr@redhat.com> wrote:
Hi,
A small heads up regarding to ovirt-vdsmfake. We merged some changes today which add support for oVirt 4.0 and make it much easier to get started with vdsmfake.
With the changes, now it is enough to just run `mvn jetty:run` to have a working vdsmfake. Have a look at the new quickstart guide in the README.md [1] to see how to get started..
Best regards, Roman
Thanks, nice for a real quick start.
I can add that I also use dnsmasq to resolve any address to an IP
dnsmasq --address=/vdsm.simulator/127.0.0.1
and that will resolve XXX.vdsm.simulator to 127.0.0.1. Just need to add nameserver to /etc/resolv.conf
I'll add that to the README as well
please make it the favorite solution. It’s way more clean than messing with /etc/hosts
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel