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 
 
Home Products Support Community News
 
   
 

xen-api

[Xen-API] eth0 on hvm is not up on xen 4.0.1

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-API] eth0 on hvm is not up on xen 4.0.1
From: 姜晓东 <jxd431@xxxxxxxxx>
Date: Fri, 18 Feb 2011 15:03:44 +0800
Cc: "xen-api@xxxxxxxxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 17 Feb 2011 23:05:22 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:content-type; bh=YllyilQOfQNH65tand3Jkc8t2+w4N/T1VJGTHLl4BVQ=; b=rv5tlveUn2ztttJw4Rx/2FCZdvJrdJlqwB1iUPIb8tX4Iax2dFUOvBHZtHVHGFECMs yF7H7AnRBuzTTKZihfiJGHBIqjICFY5xnG5wraKj9cbzqhYCEdxnP32Cl7s1SALMHtt+ 2PMIvp686Ksac8gGgnLV8YB/ri617JtaK3s20=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :content-type; b=exLB20CAT7SDoF1h2npcTWAri9LyI/PJVvZfvEYKor1V76qZPyPuPT9MLOVN8IGaR/ YaIOApo/y1YqOIn/MUplHTef27Mr/kn3pCPBt6FDy2i1Iu96Eea/aG/raeqdeR9ibaEz jMHuJpBMl78FJT0pIyZj+ZHySKkQTzfty1WhE=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.11) Gecko/20101130 Lightning/1.0b3pre Thunderbird/3.1.5

Hi,all.

I create a hvm which boot up from gentoo livecd iso file, the config file 'xen/configs/gentoo' is as follows:
------------------------------
#  -*- mode: python; -*-
import os, re
arch_libdir = 'lib'
arch = os.uname()[4]
if os.uname()[0] == 'Linux' and re.search('64', arch):
    arch_libdir = 'lib64'
kernel = "/usr/lib/xen/boot/hvmloader"
builder='hvm'
memory = 2048
shadow_memory = 8
name = "centos"
vcpus=1
vif = [ 'type=ioemu, mac=00:16:3e:00:00:12, bridge=xenbr0' ]
disk = [ 'phy:/dev/sda6,sda,w','file:/root/downloads/install-amd64-minimal-20110113.iso,hdc:cdrom,r' ]
cdrom = 'dev/hdc'
device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
boot="dc"
sdl=0
opengl=0
vnc=1
vnclisten="0.0.0.0"
vncpasswd=''
vncconsole=1
stdvga=0
serial='pty'
usbdevice='tablet'
------------------------------

Then i create this vm using command:
xm create /xen/configs/gentoo


When i entered into the console of this vm, I cannot see eth0 using ifconfig command but only see lo interface is up

The tail of /var/log/messages on dom0 is as following:
-----------------------------------------------
Feb 18 22:50:20 server kernel: device tap1.0 entered promiscuous mode
Feb 18 22:50:20 server kernel: eth0: port 3(tap1.0) entering forwarding state
Feb 18 22:50:21 server logger: /etc/xen/scripts/block: Writing backend/vbd/1/5632/node /dev/loop0 to xenstore.
Feb 18 22:50:21 server logger: /etc/xen/scripts/block: Writing backend/vbd/1/5632/physical-device 7:0 to xenstore.
Feb 18 22:50:21 server kernel: (cdrom_add_media_watch() file=/usr/src/linux-2.6.34-xen-r4/drivers/xen/blkback/cdrom.c, line=108) nodename:backend/vbd/1/5632
Feb 18 22:50:21 server kernel: (cdrom_is_type() file=/usr/src/linux-2.6.34-xen-r4/drivers/xen/blkback/cdrom.c, line=95) type:1
Feb 18 22:50:21 server kernel: (cdrom_add_media_watch() file=/usr/src/linux-2.6.34-xen-r4/drivers/xen/blkback/cdrom.c, line=110) is a cdrom
Feb 18 22:50:21 server kernel: (cdrom_add_media_watch() file=/usr/src/linux-2.6.34-xen-r4/drivers/xen/blkback/cdrom.c, line=112) xenstore wrote OK
Feb 18 22:50:21 server kernel: (cdrom_is_type() file=/usr/src/linux-2.6.34-xen-r4/drivers/xen/blkback/cdrom.c, line=95) type:1
Feb 18 22:50:21 server logger: /etc/xen/scripts/block: Writing backend/vbd/1/5632/hotplug-status connected to xenstore.
Feb 18 22:50:36 server kernel: eth0: port 3(tap1.0) entering disabled state
Feb 18 22:50:36 server kernel: device tap1.0 left promiscuous mode
Feb 18 22:50:36 server kernel: eth0: port 3(tap1.0) entering disabled state
Feb 18 22:51:32 server kernel: blkback: ring-ref 8, event-channel 5, protocol 1 (x86_64-abi)
Feb 18 22:51:32 server logger: /etc/xen/scripts/vif-bridge: offline XENBUS_PATH=backend/vif/1/0
Feb 18 22:51:32 server kernel: eth0: port 2(vif1.0) entering disabled state
Feb 18 22:51:32 server kernel: eth0: port 2(vif1.0) entering disabled state
Feb 18 22:51:32 server logger: /etc/xen/scripts/vif-bridge: brctl delif eth0 vif1.0 failed
Feb 18 22:51:32 server logger: /etc/xen/scripts/vif-bridge: ifconfig vif1.0 down failed
Feb 18 22:51:32 server logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge offline for vif1.0, bridge eth0.
-----------------------------------------------

When i booting hvm, i can see tap1.0 and vif 1.0 is up but then they disappeared while booting finished
------------------------------------------------
server log # ifconfig
eth0      Link encap:Ethernet  HWaddr 00:25:90:08:c3:8a 
          inet addr:192.168.1.3  Bcast:192.168.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4272 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3743 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:322797 (315.2 KiB)  TX bytes:906019 (884.7 KiB)

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

peth0     Link encap:Ethernet  HWaddr 00:25:90:08:c3:8a 
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:4278 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3747 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:382965 (373.9 KiB)  TX bytes:906161 (884.9 KiB)
          Memory:fbce0000-fbd00000

ppp0      Link encap:Point-to-Point Protocol 
          inet addr:222.129.49.152  P-t-P:222.129.48.1  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1492  Metric:1
          RX packets:3261 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2736 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3
          RX bytes:249113 (243.2 KiB)  TX bytes:815361 (796.2 KiB)

vif1.0    Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff 
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
---------------------------------------------------------

While booting finished, the brctl shows as following:
-----------------------------------------------------------
server log # brctl show
bridge name    bridge id        STP enabled    interfaces
eth0        8000.00259008c38a    no        peth0
----------------------------------------------------------


I tried to change vif type to netfront, eth0 interface is up after booting from gentoo livecd. I don't understand why xen failed to load eth0 using
'type=ioemu'?

Anyone help me?
-- 
Xiaodong Jiang
jxd431@xxxxxxxxx
_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api
<Prev in Thread] Current Thread [Next in Thread>