WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Xen

xen-devel

[Top] [All Lists]

Re: [Xen-devel] Re: nfsroot and brige

To: Nuutti Kotivuori <naked@xxxxxx>
Subject: Re: [Xen-devel] Re: nfsroot and brige
From: "Ronald G. Minnich" <rminnich@xxxxxxxx>
Date: 2005年1月13日 08:15:09 -0700 (MST)
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: 2005年1月13日 15:16:37 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: <877jmhh8ef.fsf@xxxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <51645.195.212.29.91.1105608600.squirrel@xxxxxxxxxxxxx> <E1Cp1MP-00070X-00@xxxxxxxxxxxxxxxxx> <877jmhh8ef.fsf@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
On 2005年1月13日, Nuutti Kotivuori wrote:
> But, I'd just like to make sure - this aversion to bridging is because
> of bridges getting configured wrong, people having wrong assumptions on
> how they work, and bridges being a bad default choice, right? There
> aren't any known actual bugs in Xen or bridge code wrt. bridging setups,
> are there?
it's probably incompetence on my part, but I've found a lot of 
half-working ways to configure the bridge but none that act like bridges 
(hardware ones I mean) that I've used in the past. 
Also we've seen real problems here with nfs root, when starting a domU and 
cutting over to xen-br0 the connection seems to die. 
So, tell me: I have a dom0 with eth0 at 10.128.107.187, eth1 at
192.168.0.65, and I want to bridge a domU at 192.168.0.66 to the dom0 such
that domU can go out over my 802.11 network to the world. How will my
xen-br0 and vif1.0 configuration look? I never got this to work correctly. 
What I really want is domU to DHCP to 192.168.0.1, and I never saw that 
work correctly either. But, if the bridge is really a bridge, that should 
"just happen" (or did on real hardware bridges).
ron
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date: Re: [Xen-devel] 'Sloppier' PCI access checks in main tree , Stijn De Weirdt
Next by Date: Re: [Xen-devel] Re: nfsroot and brige , Grzegorz Milos
Previous by Thread: [Xen-devel] Re: nfsroot and brige , Nuutti Kotivuori
Next by Thread: Re: [Xen-devel] Re: nfsroot and brige , Grzegorz Milos
Indexes: [Date] [Thread] [Top] [All Lists]

Copyright ©, Citrix Systems Inc. All rights reserved. Legal and Privacy
Citrix This site is hosted by Citrix

AltStyle によって変換されたページ (->オリジナル) /