From: <jmarks2@gmail.com> To: <flent-users@flent.org> Subject: [Flent-users] issues with flent setup in VM Date: Mon, 25 May 2020 15:24:03 -0500 [thread overview] Message-ID: <007e01d632d2$6f8338c0$4e89aa40$@gmail.com> (raw) [-- Attachment #1.1.1: Type: text/plain, Size: 418 bytes --] Dear All, I stood up a guest Linux Mint VM under Hyper-V in Win 10 specifically to run tests with flent. However, this code: fails: I can ping netperf.buffetbloat.net just fine from the VM. I am not sure what lookup is failing. This is probably some basic networking setup issue with the VM, but it is beyond me. How would I go about debugging this issue? Many thanks for any help. [-- Attachment #1.1.2: Type: text/html, Size: 2995 bytes --] [-- Attachment #1.2: image001.png --] [-- Type: image/png, Size: 5108 bytes --] [-- Attachment #1.3: image002.png --] [-- Type: image/png, Size: 7611 bytes --] [-- Attachment #2: Type: text/plain, Size: 151 bytes --] _______________________________________________ Flent-users mailing list Flent-users@flent.org http://flent.org/mailman/listinfo/flent-users_flent.org
reply other threads:[~2020-05-25 20:25 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://lists.flent.org/postorius/lists/flent-users.flent.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='007e01d632d2$6f8338c0$4e89aa40$@gmail.com' \ --to=jmarks2@gmail.com \ --cc=flent-users@flent.org \ --subject='Re: [Flent-users] issues with flent setup in VM' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox