From: Jim Fehlig <jfehlig@suse.com>
To: John McDermott CIV <john.mcdermott@nrl.navy.mil>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: After switching from "xm" to "xl" toolstack, can't get Guest networking to work.
Date: Wed, 25 Jan 2012 11:02:12 -0700 [thread overview]
Message-ID: <4F2043A4.7080708@suse.com> (raw)
In-Reply-To: <9EF3B1C1-BCD0-4DF0-B536-9B3F4DD28F6A@nrl.navy.mil>
John McDermott CIV wrote:
> So I should try this patch and report back if it works?
>
No, that patch causes the issue reported by Erin :-). In Erin's case,
the vif was not connected to the bridge. In the problem you described,
the vif was connected to the bridge but didn't work for other reasons.
Regards,
Jim
> On Jan 25, 2012, at 12:33 PM, Jim Fehlig wrote:
>
>
>> Ian Campbell wrote:
>>
>>> Please don't top post.
>>>
>>> On Wed, 2012-01-25 at 17:06 +0000, John McDermott CIV wrote:
>>>
>>>
>>>> This problem also happens in Fedora 16. Should we be making bugzilla
>>>> entries for problems with Xen?
>>>>
>>>>
>>> There is more than one reason why networking may not work for you so
>>> there isn't necessarily any reason (yet) to think you are seeing the
>>> same issue.
>>>
>>>
>> Yes, different issue. I'd be really surprised if Fedora had this patch
>>
>> http://old-list-archives.xen.org/archives/html/xen-devel/2011-10/msg01790.html
>>
>> Regards,
>> Jim
>>
>
> ----
> What is the formal meaning of the one-line program
> #include "/dev/tty"
>
> J.P. McDermott building 12
> Code 5542 john.mcdermott@nrl.navy.mil
> Naval Research Laboratory voice: +1 202.404.8301
> Washington, DC 20375, US fax: +1 202.404.7942
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
next prev parent reply other threads:[~2012-01-25 18:02 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1527.1327510060.1471.xen-devel@lists.xensource.com>
2012-01-25 17:06 ` After switching from "xm" to "xl" toolstack, can't get Guest networking to work John McDermott CIV
2012-01-25 17:16 ` Ian Campbell
2012-01-25 17:22 ` John McDermott CIV
2012-01-25 17:33 ` Jim Fehlig
2012-01-25 17:39 ` John McDermott CIV
2012-01-25 18:02 ` Jim Fehlig [this message]
2012-01-25 19:20 ` John McDermott CIV
2012-01-25 21:16 ` Jim Fehlig
2012-01-21 20:06 erin.balid
2012-01-21 22:57 ` Roger Pau Monné
2012-01-21 23:04 ` erin.balid
2012-01-22 0:54 ` erin.balid
2012-01-22 11:08 ` Roger Pau Monné
2012-01-22 17:11 ` erin.balid
2012-01-22 17:28 ` Roger Pau Monné
2012-01-22 17:54 ` erin.balid
2012-01-24 23:13 ` Jim Fehlig
2012-01-25 2:01 ` erin.balid
2012-01-25 15:55 ` Jim Fehlig
2012-01-25 16:27 ` erin.balid
2012-01-25 16:47 ` Jim Fehlig
2012-01-22 15:49 ` djmagee
2012-01-23 11:27 ` Ian Campbell
2012-01-23 15:28 ` erin.balid
2012-01-24 14:26 ` Ian Campbell
2012-01-24 15:56 ` erin.balid
2012-01-24 16:41 ` Ian Campbell
2012-01-24 17:10 ` erin.balid
2012-01-24 18:05 ` erin.balid
2012-01-24 18:19 ` erin.balid
2012-01-24 21:20 ` Ian Campbell
2012-01-24 21:20 ` Ian Campbell
2012-01-24 21:44 ` erin.balid
2012-01-25 3:59 ` erin.balid
2012-01-25 9:35 ` Ian Campbell
2012-01-25 16:19 ` Jim Fehlig
2012-01-25 16:32 ` Ian Campbell
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=4F2043A4.7080708@suse.com \
--to=jfehlig@suse.com \
--cc=john.mcdermott@nrl.navy.mil \
--cc=xen-devel@lists.xensource.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).