[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [1/3] [XEN] gnttab: Add new op unmap_and_replace
On Mon, Jun 04, 2007 at 02:18:13PM +0100, Keir Fraser wrote:
> On 4/6/07 14:12, "Daniel P. Berrange" <berrange@xxxxxxxxxx> wrote:
> > Is that XenD itself keeping around bogus cached state about your network
> > and re-creating xenbr0 from this ? Try rm -rf on /var/lib/xend/state
> > and reboot. The only places we reference xenbr0 is in the vif-bridge
> > and qemu-ifup scripts where we do auto-translation from xenbr0 to eth0
> > for back-compatability with old guest configs.
> Oh, I see. In that case I think everything is now fine. Perhaps we should
> leave the xenbr0 references as is then: at least it's clear we're talking
> about a bridge in the contexts where we use it, as opposed to an interface
> for local packet delivery.
The reason we renamed it to 'eth0' in Fedora is so edge closer towards a
single unified network setup that is applicable for any virtualization
tech. In Fedora 8 we're going to remove network-bridge from the default
config completely and just use regular init scripts for configuring
eg, have /etc/sysconfig/network-scripts/ifcfg-peth0 defining the physical
interface config thus:
And the bridge device config /etc/sysconfig/network-scripts/ifcfg-eth0
This will make it much easier for people who want to use bonding, or VLANs
and any other funky networking config in Dom0, and the same configs will
work for both Xen & KVM. Hence we wanted to have a generic 'eth0' and 'peth0'
rather than 'xenbr0' and 'eth0'. Of course there's plenty of other naming
schemes too, but figured since Xen already had the idea of a 'p' prefix for
identifying a physical device that seemed reasonable to keep.
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
Xen-devel mailing list