[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] help with bugs


  • To: "Gerd Knorr" <kraxel@xxxxxxx>
  • From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
  • Date: Fri, 5 Aug 2005 15:22:01 +0100
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 05 Aug 2005 14:20:47 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcWZwR0DMqhAkMJ4Ty+Yy4SzQGNppAAB4tgw
  • Thread-topic: [Xen-devel] help with bugs

> Hmm, just an idea, not sure how well that would work in 
> practice, maybe the network script should not even attempt to 
> copy the ip addresses, but instead use ifup and ifdown, i.e.
> something like this:

Do you think ifup/ifdown will do the right thing with the interface name
changed underneath them?

If so, that's a good soloution and we should adopt it. Please can
someone try?

Thanks,
Ian 
 
>       ifdown eth0
>       ip link set eth0 name peth0
>       ip link set veth0 name eth0
>       brctl addbr xen-br0
>       brctl addif xen-br0 peth0
>       brctl addif xen-br0 vif0.0
>       ip link set peth0 up
>       ip link set vif0.0 up
>       ip link set xen-br0 up
>       ifup eth0
> 
> At least suse, fedora and debian have ifup and ifdown to 
> control interfaces, not sure about others ...
> 
> > So you don't use veth0?
> 
> No.  Partly because it's not entriely clear to me how the 
> setup should look like (hope I got it right above), partly 
> because the same setup works for both xen2 and xen3 then.  
> And, no, I don't run services for the domUs on dom0 ...
> 
>   Gerd
> 
> --
> panic("it works"); /* avoid being flooded with debug messages */
> 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.