I seem to have hit the same issue, but with just a single
NIC. This is on CentOS 5.2 with Xen 3.3 installed. I run
/etc/init.d/xend start manually since it is not (yet) hooked into the rc
scripts.
The eth0 works fine from dom0 but there is no bridge being
created that works with any of the VMs:
[root@xensys3
~]# brctl show
bridge name bridge
id STP
enabled interfaces
eth0 8000.001cc03c02d7
no peth0
Shouldn't that include a vif0.0? That is what I see with
Xen version 3.1.2-92.el5 on the same system:
[root@xensys3
~]# brctl show
bridge name bridge
id STP
enabled interfaces
virbr0 8000.000000000000
yes
xenbr0 8000.feffffffffff
no peth0
vif0.0
Below is a partial “xm log” output. To me
the messages about the “missing tmpbridge” and “VBD.set_device
not found” seem suspicious. Can anyone please tell me what those
messages mean?
Thanks,
Ed
[2008-09-11
14:42:54 6421] INFO (SrvDaemon:331) Xend Daemon started
[2008-09-11
14:42:54 6421] INFO (SrvDaemon:335) Xend changeset: unavailable.
[2008-09-11
14:42:54 6421] INFO
(XendNetwork:114) Not recreating missing unmanaged network tmpbridge
[2008-09-11
14:42:54 6421] DEBUG (XendDomainInfo:137) XendDomainInfo.recreate(<<snip>>)
[2008-09-11
14:42:54 6421] INFO (XendDomainInfo:153) Recreating domain 0, UUID
00000000-0000-0000-0000-000000000000. at /local/domain/0
[2008-09-11
14:42:54 6421] DEBUG (XendDomainInfo:2729) Storing VM details: {<<snip>>}
[2008-09-11
14:42:54 6421] DEBUG (XendDomainInfo:1359) Storing domain details: {<<snip>>}
[2008-09-11
14:42:54 6421] DEBUG (XendDomain:447) Adding Domain: 0
[2008-09-11
14:42:54 6421] DEBUG (XendDomain:383) number of vcpus to use is 0
[2008-09-11
14:42:54 6421] WARNING
(XendAPI:684) API call: VBD.set_device not found
[2008-09-11
14:42:54 6421] WARNING (XendAPI:684) API call: VBD.set_type not found
[2008-09-11
14:42:54 6421] WARNING (XendAPI:684) API call: session.get_all_records not found
[2008-09-11
14:42:54 6421] WARNING (XendAPI:684) API call: event.get_record not found
[2008-09-11
14:42:54 6421] WARNING (XendAPI:684) API call: event.get_all not found
[2008-09-11
14:42:54 6421] DEBUG (XendDomainInfo:1443) XendDomainInfo.handleShutdownWatch
[2008-09-11
14:42:54 6421] WARNING (XendAPI:684) API call: VM.get_auto_power_on not found
[2008-09-11
14:42:54 6421] WARNING (XendAPI:684) API call: VM.set_auto_power_on not found
[2008-09-11
14:42:54 6421] WARNING (XendAPI:684) API call: VIF.get_network not found
[2008-09-11
14:42:54 6421] WARNING (XendAPI:684) API call: VIF.set_device not found
[2008-09-11
14:42:54 6421] WARNING (XendAPI:684) API call: VIF.set_MAC not found
[2008-09-11
14:42:54 6421] WARNING (XendAPI:684) API call: VIF.set_MTU not found
[2008-09-11
14:42:54 6421] WARNING (XendAPI:684) API call: debug.get_all not found
-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Mike Power
Sent: Wednesday, September 10, 2008 9:25 AM
To: Thomas Robers
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Problems with bridged networking
>
>
> thank you for your answer. I looked at wiki entry and as Steffen
also
> told
> me, I can see, that in Xen 3.2.x the bridge names have changed
from
> 3.1.x -> 3.2.x
> So I tried what I found in almost every howto and book:
>
> server:/etc/xen/scripts# ./network-bridge
bridge=eth1 netdev=eth1
> start
> ifdown: interface eth1 not configured
> Nothing to flush.
> Waiting for peth1 to negotiate link......
> Ignoring unknown interface eth1=eth1
>
Are your physical interfaces configured? 3.2 bridge script
scrapes off
the information from netdev and applies it to bridge. If your
netdev is
not up and running by the time network-bridge is run I am not sure it
will be able to stand up the bridge.
Before you run your network-bridge scripts check the output of ifconfig
and make sure each physical interface is mentioned and has an ip.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
Home