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@gmail.com
_______________________________________________
xen-api mailing list
xen-api@lists.xensource.com
http://lists.xensource.com/mailman/listinfo/xen-api
On 02/18/11 15:03, 姜晓东 wrote:> > 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@gmail.com-- Xiaodong Jiang jxd431@gmail.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Konrad Rzeszutek Wilk
2011-Feb-21 22:48 UTC
Re: [Xen-API] [Xen-Users] eth0 on hvm is not up on xen 4.0.1
On Fri, Feb 18, 2011 at 03:17:07PM +0800, 姜晓东 wrote:> On 02/18/11 15:03, 姜晓东 wrote: > > > > 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'' ]So you are using ''xenbr0'' but your brctl show the name of the bridge is ''eth0''? Why ''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@gmail.com > > > -- > Xiaodong Jiang > jxd431@gmail.com >> _______________________________________________ > xen-api mailing list > xen-api@lists.xensource.com > http://lists.xensource.com/mailman/listinfo/xen-api_______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api
Xiaodong Jiang
2011-Mar-01 14:26 UTC
Re: [Xen-API] [Xen-Users] eth0 on hvm is not up on xen 4.0.1
I have tried to use ''eth0'', but still have this problem 于 2011年02月22日 06:48, Konrad Rzeszutek Wilk 写道:> On Fri, Feb 18, 2011 at 03:17:07PM +0800, 姜晓东 wrote: >> On 02/18/11 15:03, 姜晓东 wrote: >>> 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'' ] > So you are using ''xenbr0'' but your brctl show the name of the bridge is ''eth0''? > Why ''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@gmail.com >> >> -- >> Xiaodong Jiang >> jxd431@gmail.com >> >> _______________________________________________ >> xen-api mailing list >> xen-api@lists.xensource.com >> http://lists.xensource.com/mailman/listinfo/xen-api-- Xiaodong Jiang jxd431@gmail.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Konrad Rzeszutek Wilk
2011-Mar-08 15:46 UTC
Re: [Xen-API] [Xen-Users] eth0 on hvm is not up on xen 4.0.1
On Tue, Mar 01, 2011 at 10:26:59PM +0800, Xiaodong Jiang wrote:> > I have tried to use ''eth0'', but still have this problemInteresting. I see the same thing when I use an Linux kernel(2.6.38) that has been compiled with PVonHVM functionality. If you boot your kernel with ''xen_emul_unplug=never'' does it work? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
hello all I think Ihave the same problem. First my config file has the same style and i use eth0 not xenbr0 I have tried in the kernel the last solution but nothing an idea ? -- View this message in context: http://xen.1045712.n5.nabble.com/eth0-on-hvm-is-not-up-on-xen-4-0-1-tp3390658p4462021.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
so my config
import os, re
arch = os.uname()[4]
if re.search(''64'', arch):
arch_libdir = ''lib64''
else:
arch_libdir = ''lib''
kernel = "/usr/lib/xen/boot/hvmloader"
builder=''hvm''
Vcpus=2
memory = 2048
shadow_memory = 8
name = "sourcewindows"
vif = [ ''type=ioemu, mac=aa:00:b0:00:00:11, bridge=eth0'' ]
disk = [ ''file:/mnt/data/xen/disks/sourcewindows.img,hda,w'',
''phy:/dev/cdrom,hdc:cdrom,r'' ]
device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
boot="dc"
sdl=0
vnc=1
vncconsole=1
vncpasswd=''''
logs
Jun 7 19:06:10 vitalinkmain logger: /etc/xen/scripts/block: add
XENBUS_PATH=backend/vbd/2/768
Jun 7 19:06:10 vitalinkmain logger: /etc/xen/scripts/block: add
XENBUS_PATH=backend/vbd/2/5632
Jun 7 19:06:10 vitalinkmain logger: /etc/xen/scripts/vif-bridge: online
type_if=vif XENBUS_PATH=backend/vif/2/0
Jun 7 19:06:10 vitalinkmain logger: /etc/xen/scripts/block: Writing
backend/vbd/2/768/node /dev/loop0 to xenstore.
Jun 7 19:06:10 vitalinkmain logger: /etc/xen/scripts/block: Writing
backend/vbd/2/768/physical-device 7:0 to xenstore.
Jun 7 19:06:10 vitalinkmain kernel: [ 1429.087779] (cdrom_add_media_watch()
file=/usr/src/linux-2.6.34-xen-r4/drivers/xen/blkback/cdrom.c, line=108)
nodename:backend/vbd/2/768
Jun 7 19:06:10 vitalinkmain kernel: [ 1429.087782] (cdrom_is_type()
file=/usr/src/linux-2.6.34-xen-r4/drivers/xen/blkback/cdrom.c, line=95)
type:0
Jun 7 19:06:10 vitalinkmain logger: /etc/xen/scripts/block: Writing
backend/vbd/2/768/hotplug-status connected to xenstore.
Jun 7 19:06:10 vitalinkmain kernel: [ 1429.097269] device vif2.0 entered
promiscuous mode
Jun 7 19:06:10 vitalinkmain kernel: [ 1429.098960] eth0: port 2(vif2.0)
entering forwarding state
Jun 7 19:06:10 vitalinkmain logger: /etc/xen/scripts/vif-bridge: Successful
vif-bridge online for vif2.0, bridge eth0.
Jun 7 19:06:10 vitalinkmain logger: /etc/xen/scripts/vif-bridge: Writing
backend/vif/2/0/hotplug-status connected to xenstore.
Jun 7 19:06:10 vitalinkmain logger: /etc/xen/scripts/block: Writing
backend/vbd/2/5632/physical-device b:0 to xenstore.
Jun 7 19:06:10 vitalinkmain logger: /etc/xen/scripts/block: Writing
backend/vbd/2/5632/hotplug-status connected to xenstore.
Jun 7 19:06:10 vitalinkmain kernel: [ 1429.158821] (cdrom_add_media_watch()
file=/usr/src/linux-2.6.34-xen-r4/drivers/xen/blkback/cdrom.c, line=108)
nodename:backend/vbd/2/5632
Jun 7 19:06:10 vitalinkmain kernel: [ 1429.158824] (cdrom_is_type()
file=/usr/src/linux-2.6.34-xen-r4/drivers/xen/blkback/cdrom.c, line=95)
type:3
Jun 7 19:06:10 vitalinkmain kernel: [ 1429.158826] (cdrom_add_media_watch()
file=/usr/src/linux-2.6.34-xen-r4/drivers/xen/blkback/cdrom.c, line=110) is
a cdrom
Jun 7 19:06:10 vitalinkmain kernel: [ 1429.159418] (cdrom_add_media_watch()
file=/usr/src/linux-2.6.34-xen-r4/drivers/xen/blkback/cdrom.c, line=112)
xenstore wrote OK
Jun 7 19:06:10 vitalinkmain kernel: [ 1429.159537] (cdrom_is_type()
file=/usr/src/linux-2.6.34-xen-r4/drivers/xen/blkback/cdrom.c, line=95)
type:3
Jun 7 19:06:11 vitalinkmain logger: /etc/xen/scripts/xen-hotplug-cleanup:
XENBUS_PATH=backend/console/2/0
Jun 7 19:06:11 vitalinkmain logger: /etc/xen/scripts/xen-hotplug-cleanup:
XENBUS_PATH=backend/vfb/2/0
Jun 7 19:06:11 vitalinkmain kernel: [ 1429.506828] eth0: port 2(vif2.0)
entering disabled state
Jun 7 19:06:11 vitalinkmain kernel: [ 1429.509229] eth0: port 2(vif2.0)
entering disabled state
Jun 7 19:06:11 vitalinkmain logger: /etc/xen/scripts/block: remove
XENBUS_PATH=backend/vbd/2/768
Jun 7 19:06:11 vitalinkmain logger: /etc/xen/scripts/block: remove
XENBUS_PATH=backend/vbd/2/5632
Jun 7 19:06:11 vitalinkmain logger: /etc/xen/scripts/vif-bridge: offline
type_if=vif XENBUS_PATH=backend/vif/2/0
Jun 7 19:06:11 vitalinkmain logger: /etc/xen/scripts/xen-hotplug-cleanup:
XENBUS_PATH=backend/vbd/2/5632
Jun 7 19:06:11 vitalinkmain logger: /etc/xen/scripts/vif-bridge: brctl
delif eth0 vif2.0 failed
Jun 7 19:06:11 vitalinkmain logger: /etc/xen/scripts/xen-hotplug-cleanup:
XENBUS_PATH=backend/vbd/2/768
Jun 7 19:06:11 vitalinkmain logger: /etc/xen/scripts/vif-bridge: ifconfig
vif2.0 down failed
Jun 7 19:06:11 vitalinkmain logger: /etc/xen/scripts/vif-bridge: Successful
vif-bridge offline for vif2.0, bridge eth0.
Jun 7 19:06:11 vitalinkmain logger: /etc/xen/scripts/xen-hotplug-cleanup:
XENBUS_PATH=backend/vif/2/0
any idea ?
--
View this message in context:
http://xen.1045712.n5.nabble.com/eth0-on-hvm-is-not-up-on-xen-4-0-1-tp3390658p4462131.html
Sent from the Xen - User mailing list archive at Nabble.com.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users