From mboxrd@z Thu Jan 1 00:00:00 1970 From: stoeni Subject: Re: domU - no networking Date: Sun, 16 Oct 2005 11:36:17 +0200 Message-ID: <43521F11.7020205@stoeni.de> References: <435170F7.20908@stoeni.de> <1909448a7ee1b26ff480078569eacf51@cl.cam.ac.uk> <4352192D.5000007@stoeni.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Keir Fraser schrieb: > On 16 Oct 2005, at 10:11, stoeni wrote: >> vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > No, that's part of domain0's network. hm, this is new to xen 3.0? on 2.0.7 there are only vif1.x interfaces, no vif0.0. did i miss something in the docs? > You are looking for something like vifx.1 (e.g., vif1.1, vif2.1, etc.). no interface like this, just startet the domU again. only eth0, peth0, vif0.0 and xen-br0. > If you don't have one of those, your domain has been set up with no > network. Which would probably be due to a problem in the config file. config used from 2.0.7: #============================== kernel = "/boot/vmlinuz-2.6-xenU" root = "/dev/sda1 ro" memory = 2048 name = "vm-tempo" cpu = -1 # leave to Xen to pick nics = 1 vif = [ 'bridge=xen-br0' ] disk = ['phy:/dev/vg_xlarge/tempo,sda1,w','phy:/dev/vg_xlarge/tempo_swap,sda2,w'] restart = 'onreboot' #============================== -- Tschaw/2, Stoeni! ++ Please remember: rm -rf means "read mail -really fast" ++