All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Knorr <kraxel@suse.de>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: help with bugs
Date: Fri, 5 Aug 2005 15:20:02 +0200	[thread overview]
Message-ID: <20050805132002.GA15968@bytesex> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D282988@liverpoolst.ad.cl.cam.ac.uk>

> I'd be inclined to rename the physical interface to pethN, and create
> veth0 as eth0. I think this should solve the DHCP issue.

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:

	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 */

  reply	other threads:[~2005-08-05 13:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-05  9:12 help with bugs Ian Pratt
2005-08-05 13:20 ` Gerd Knorr [this message]
2005-08-10 18:38   ` Nivedita Singhvi
  -- strict thread matches above, loose matches on Subject: below --
2005-08-10 18:39 Ian Pratt
2005-08-10 19:00 ` Nivedita Singhvi
2005-08-05 14:22 Ian Pratt
2005-08-04 21:48 Ian Pratt
2005-08-04 22:21 ` Sean Dague
2005-08-04 21:02 Ian Pratt
2005-08-04 21:29 ` David F Barrera
2005-08-04 21:55   ` Paul Larson
2005-08-05  3:10     ` David F Barrera
2005-08-04 15:04 Ian Pratt
2005-08-04 19:53 ` Anthony Liguori
2005-08-04 20:18 ` Sean Dague
2005-08-04 20:49 ` David F Barrera
2005-08-05  8:29 ` Gerd Knorr

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=20050805132002.GA15968@bytesex \
    --to=kraxel@suse.de \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --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 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.