All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Garman <scott.a.garman@intel.com>
To: yocto@yoctoproject.org
Subject: Re: runqemu qemux86
Date: Tue, 22 May 2012 11:25:08 -0700	[thread overview]
Message-ID: <4FBBDA04.7020600@intel.com> (raw)
In-Reply-To: <4FBBD0B5.5020207@gmail.com>

On 05/22/2012 10:45 AM, jfabernathy wrote:
>>> https://bugzilla.yoctoproject.__org/show_bug.cgi?id=2329
>>> <https://bugzilla.yoctoproject.org/show_bug.cgi?id=2329>
>>>
>>> Scott
>>>
>>> So if I read this right, I don't need any route or bridge commands to
>>> make this work. If the bug gets fixed runqemu qemux86 should setup the
>>> environment correctly so the web-webkit should get out to the internet
>>> via the host machine connection?
>>> JIm A
>>
>> Correct.
>>
>> I'm hesitant to say this, but I'm hoping to have the bug fixed and
>> patch submitted by the end of this week. Hopefully I haven't just
>> jinxed myself. :)
>>
>
> I did try it out on core-image-minimal and I can ping anything I have
> the IP for. Not sure how you get the DNS connections working in qeum.

Since we use a static IP configuration for the QEMU sessions, 
/etc/resolv.conf isn't populated with a nameserver. If you enter one, it 
should work.

I'm not sure if there is something we can/should use as a default DNS 
setup that would work for all our end users. OpenDNS? Google's nameservers?

Scott

-- 
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center


      reply	other threads:[~2012-05-22 18:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-22 11:43 runqemu qemux86 jfabernathy
2012-05-22 14:45 ` Autif Khan
2012-05-22 15:15   ` James Abernathy
2012-05-22 17:04     ` Scott Garman
2012-05-22 17:26       ` James Abernathy
2012-05-22 17:42         ` Scott Garman
2012-05-22 17:45           ` jfabernathy
2012-05-22 18:25             ` Scott Garman [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FBBDA04.7020600@intel.com \
    --to=scott.a.garman@intel.com \
    --cc=yocto@yoctoproject.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.