lukas at laukamp
Aug 12, 2012, 4:22 AM
Post #2 of 3
(270 views)
Permalink
|
Am 12.08.2012 05:58, schrieb lyflyd:
>
> According to your way , I set up the bridge.And restart the domU system .
>
> XM LIST:
>
> root [at] dom0-22:/etc/xen# xm list
>
> Name ID Mem VCPUs State Time(s)
>
> 10.10.10.220_10.04 13 1048 1 -b---- 1.2
>
> 10.10.10.221 12 1048 1 -b---- 1.2
>
> Domain-0 0 13043 16 r----- 1281.7
>
> root [at] dom0-22:/etc/xen#
>
> NETWORK INFO：only one vif interfaces vif12.0 to guest id 10.10.10.221
>
> peth1 Link encap:Ethernet HWaddr 00:25:90:80:ee:95
>
> UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
>
> RX packets:199137 errors:0 dropped:4 overruns:0 frame:0
>
> TX packets:3497 errors:0 dropped:0 overruns:0 carrier:0
>
> collisions:0 txqueuelen:1000
>
> RX bytes:15072098 (15.0 MB) TX bytes:231364 (231.3 KB)
>
> Memory:faf60000-faf80000
>
> vif12.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
>
> inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>
> UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
>
> RX packets:17 errors:0 dropped:0 overruns:0 frame:0
>
> TX packets:113 errors:0 dropped:0 overruns:0 carrier:0
>
> collisions:0 txqueuelen:32
>
> RX bytes:1068 (1.0 KB) TX bytes:7958 (7.9 KB)
>
> xenbr1 Link encap:Ethernet HWaddr 00:25:90:80:ee:95
>
> inet addr:10.10.10.206 Bcast:10.10.10.255 Mask:255.255.255.0
>
> inet6 addr: fe80::225:90ff:fe80:ee95/64 Scope:Link
>
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>
> RX packets:1812 errors:0 dropped:0 overruns:0 frame:0
>
> TX packets:48 errors:0 dropped:0 overruns:0 carrier:0
>
> collisions:0 txqueuelen:0
>
> RX bytes:107020 (107.0 KB) TX bytes:4128 (4.1 KB)
>
> BRIDGE INFO
>
> root [at] dom0-22:/etc/xen# brctl show
>
> bridge name bridge id STP enabled interfaces
>
> xenbr1 8000.00259080ee95 no peth1
>
> vif12.0
>
> Guest ID : 10.10.10.220_10.04 system is copy from guest ID
> 10.10.10.221 system .But Guest ID : 10.10.10.220_10.04 haven’t vif
> interface。
>
> The vif12.0 is guest id 10.10.10.221。
>
> Dmesg info
>
> [214733.207060] xenbr1: port 2(vif12.0) entering forwarding state
>
> [214733.207065] xenbr1: port 2(vif12.0) entering forwarding state
>
> [214754.307598] xenbr1: port 3(vif13.0) entering disabled state
>
> [214754.307857] xenbr1: port 3(vif13.0) entering disabled state
>
> Vif13.0 interfaces belong to Guest ID : 10.10.10.220_10.04 but disabled.
>
> Normnal state is entering forwarding state .
>
> Why ?
>
> Whether through a copy guest system ,must be set some configuration file?
>
> The same, I'm running on ubuntu 8.04 xen dom0, but no such the problem.
>
> *发件人:*Lukas Laukamp [mailto:lukas [at] laukamp]
> *发 送时间:*2012年8月12日1:36
> *收件人:*lyflyd
> *抄送:*xen-users [at] lists
> *主题:*Re: 答复: [Xen-users] xen bug in ubuntu 12.04 ？
>
> Am 11.08.2012 19:14, schrieb lyflyd:
>
> Tks！
>
> I run pv guest ！When I create pv guest by xen-create-image
> command,the vif can up success.
>
> But when I create guest system through the following the script of
> the way to create.(In fact is to copy a guest system)
>
> #!/bin/bash
>
> # $1 is ipaddr
>
> if [ -z $1 ];then
>
> echo "Usage:$0 ip_addr"
>
> exit 0
>
> fi
>
> # get random string
>
> MATRIX="0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ"
>
> LENGTH="2"
>
> while [ "${n:=1}" -le "$LENGTH" ]
>
> do
>
> PASS="$PASS${MATRIX:$(($RANDOM%${#MATRIX})):1}"
>
> let n+=1
>
> done
>
> echo "$PASS"
>
> cp templates.cfg $1.cfg
>
> # set mac
>
> sed -i "s/TEMP/$PASS/g" $1.cfg
>
> # set hostname
>
> sed -i "s/HOSTNAME/$1/g" $1.cfg
>
> # set ipaddr
>
> sed -i "s/IPADDR/$1/g" $1.cfg
>
> #
>
> ## create disk iso and swap file
>
> #
>
> mkdir -p /data/xen/domains/$1
>
> dd if=/dev/zero of=/data/xen/domains/$1/disk.img bs=1 count=1 seek=20G
>
> dd if=/dev/zero of=/data/xen/domains/$1/swap.img bs=1M count=1024
>
> mkfs.ext4 /data/xen/domains/$1/disk.img
>
> sleep 2
>
> cd /data/xen/domains/$1
>
> mount -o loop disk.img /mnt
>
> tar -zxSf /data/xen/domains/templates_10.04/*ubuntu_10.04.tgz *-C
> /mnt/
>
> sleep 2
>
> sed -i "s/10.10.10.231/$1/g" /mnt/etc/network/interfaces
>
> sleep 2
>
> umount /mnt
>
> #
>
> ## start vps $1
>
> #
>
> xm create -c $1.cfg
>
> *ubuntu_10.04.tgz is a os iso file.*
>
> **
>
> *My configuration file :*
>
> #
>
> # Configuration file for the Xen instance 10.04, created
>
> # by xen-tools 4.3.1 on Sat Jul 28 03:10:44 2012.
>
> #
>
> #
>
> # Kernel + memory size
>
> #
>
> bootloader = '/usr/bin/pygrub'
>
> vcpus = '1'
>
> memory = '1048'
>
> #
>
> # Disk device(s).
>
> #
>
> root = '/dev/xvda2 ro'
>
> disk = [.
>
>
> 'file:/data/xen/domains/10.10.10.220/disk.img,xvda2,w
> <file:///%5C%5Cdata%5Cxen%5Cdomains%5C10.10.10.220%5Cdisk.img,xvda2,w>',
>
>
> 'file:/data/xen/domains/10.10.10.220/swap.img,xvda1,w
> <file:///%5C%5Cdata%5Cxen%5Cdomains%5C10.10.10.220%5Cswap.img,xvda1,w>',
>
> ]
>
> #
>
> # Physical volumes
>
> #
>
> #
>
> # Hostname
>
> #
>
> name = '10.10.10.220_10.04'
>
> #
>
> # Networking
>
> #
>
> vif = [ 'ip=10.10.10.220 ,mac=00:16:3E:22:5K:2F' ]
>
> #
>
> # Behaviour
>
> #
>
> on_poweroff = 'destroy'
>
> on_reboot = 'restart'
>
> on_crash = 'restart'
>
> *发件人:*Lukas Laukamp [mailto:lukas [at] laukamp]
> *发 送时间:*2012年8月12日0:53
> *收件人:*lyflyd
> *抄送:*xen-users [at] lists <mailto:xen-users [at] lists>
> *主题:*Re: [Xen-users] xen bug in ubuntu 12.04 ？
>
> Am 11.08.2012 18:27, schrieb lyflyd:
>
> Hi：
>
> in the ubuntu 12.04 ,i installed the xen dom0 success.
>
> In the startup xen guest, the guest system can be the normal
> starting, but guest system vif interface does not exist.
>
> View dmesg log shows:
>
> [2062.382385] device vif9.0 entered promiscuous mode
>
> [2062.387698] ADDRCONF (NETDEV_UP) : vif9.0: link is not ready
>
> [2072.221544] vif8.0: no IPv6 routers present
>
> [2076.808353] xen-blkback: ring-ref 8, event-channel 9,
> protocol 1 (x86_64-abi)
>
> [2076.847384] xen-blkback: ring-ref 9, event-channel 10,
> protocol 1 (x86_64-abi)
>
> *[2076.856078] eth1: port 4 (vif9.0) entering disabled state*
>
> *[2076.856268] eth1: port 4 (vif9.0) entering disabled state*
>
> this vif interfaces that the line is disabled.
>
> And the normal vif startup information is:
>
> [2035.861524] ADDRCONF (NETDEV_UP) : vif7.0: link is not ready
>
> [2048.585999] xen-blkback: ring-ref 8, event-channel 9,
> protocol 1 (x86_64-abi)
>
> [2048.629885] xen-blkback: ring-ref 9, event-channel 10,
> protocol 1 (x86_64-abi)
>
> [2048.648746] ADDRCONF (NETDEV_CHANGE) : vif7.0: link becomes
> ready
>
> *[2048.648801] eth1: port 2 (vif7.0) entering forwarding state*
>
> *[2048.648806] eth1: port 2 (vif7.0) entering forwarding state*
>
> why the vif interfaces disabled?
>
> what's wrong ?
>
> how can I do ?
>
>
>
>
>
> _______________________________________________
>
> Xen-users mailing list
>
> Xen-users [at] lists <mailto:Xen-users [at] lists>
>
> http://lists.xen.org/xen-users
>
>
> Hello,
>
> it would be useful to know if you run a HVM or PV guest and how
> your configuration look like. I don't have issues with Xen on
> Ubuntu 12.04 and Debian. The only case where I had problems was
> when the vif option in the configuration file of a HVM has the
> option type=ioemu. There it happened that the vif interface
> couldn't be setup correct or stopped after a while.
>
> Best Regards
>
>
> Hello,
>
> xen-create-image should generate a DomU configuration file in the
> specified output dir. Could you show us the configuration file of the
> DomU and the configuration of you bridge in /etc/network/interfaces.
> If you have created the bridge with the script network-bridge try to
> create the manually and try to start the guest with this bridge. So a
> possible bridge configuration could look like this:
>
> auto xenbr0
> iface xenbr0 inet static
> address IP-ADDRESS of Dom0
> netmask NETMASK-FOR-THE-NETWORK
> gateway GATEWAY-OF-THE-NETWORK
> bridge_ports eth0
> bridge_stp off (Spanning tree protocol is disabled in this case)
> bridge_fd 0 (sets the default forward delay)
>
> The configuration for eth0 then must look like this:
>
> auto eth0
> iface eth0 inet manual
>
> The configuration line for vif in the DomU configuration should look
> like this:
>
> vif [ 'bridge=xenbr0,ip=IP-OF-DOMU,mac=WANTED-MAC-ADDRESS' ]
>
> Best Regards
>
Hello,
so it looks like that you still have the Xen network-scripts active in
xend-config.sxp. Devices like pethX only get created by this scripts.
When you setup a bridge manually you should disable this scripts. Only
the vif-script vif-bridge have to be active so that the vif device of
the DomUs can be connected to the bridge.
The geust with the ID 12 has a vif device so its the guest with the name
10.10.10.221, does this guest can access the network or/and is reacheble
from the network?
Best Regards
|
