Re: Почему bridge называется eth0, а не xenbr0?
13:10 Fri 21 Aug , Peter Teslenko wrote:
> Nick wrote:
>
>> Уже довольно давно по умолчанию название моста eth0. Только в
>> документации никак не исправят.
>
> Кстати, почему, если я делаю
>
> xm destroy domU_id
> xm create domU.cfg
>
> то каждый раз создаются новые vif'ы?
>
> Aug 21 13:03:23 proxy logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/console/4/0
> Aug 21 13:03:23 proxy kernel: [ 2487.848440] eth0: port 3(vif4.0) entering disabled state
> Aug 21 13:03:23 proxy logger: /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/4/2049
> Aug 21 13:03:23 proxy kernel: [ 2487.876841] eth0: port 3(vif4.0) entering disabled state
> Aug 21 13:03:23 proxy logger: /etc/xen/scripts/vif-bridge: offline XENBUS_PATH=backend/vif/4/0
> Aug 21 13:03:23 proxy logger: /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/4/2050
> Aug 21 13:03:23 proxy logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vbd/4/2049
> Aug 21 13:03:23 proxy logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vbd/4/2050
> Aug 21 13:03:23 proxy logger: /etc/xen/scripts/vif-bridge: brctl delif eth0 vif4.0 failed
> Aug 21 13:03:23 proxy logger: /etc/xen/scripts/vif-bridge: ifconfig vif4.0 down failed
> Aug 21 13:03:23 proxy logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge offline for vif4.0, bridge eth0.
> Aug 21 13:03:23 proxy logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vif/4/0
> Aug 21 13:05:18 proxy logger: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/5/2049
> Aug 21 13:05:18 proxy logger: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/5/2050
> Aug 21 13:05:18 proxy logger: /etc/xen/scripts/vif-bridge: online XENBUS_PATH=backend/vif/5/0
> Aug 21 13:05:18 proxy kernel: [ 2603.044075] device vif5.0 entered promiscuous mode
> Aug 21 13:05:18 proxy kernel: [ 2603.049883] eth0: port 3(vif5.0) entering learning state
> Aug 21 13:05:18 proxy kernel: [ 2603.053009] eth0: topology change detected, propagating
> Aug 21 13:05:18 proxy kernel: [ 2603.053046] eth0: port 3(vif5.0) entering forwarding state
> Aug 21 13:05:18 proxy logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge online for vif5.0, bridge eth0.
> Aug 21 13:05:18 proxy logger: /etc/xen/scripts/vif-bridge: Writing backend/vif/5/0/hotplug-status connected to xenstore.
> Aug 21 13:05:18 proxy logger: /etc/xen/scripts/block: Writing backend/vbd/5/2049/node /dev/loop10 to xenstore.
> Aug 21 13:05:18 proxy logger: /etc/xen/scripts/block: Writing backend/vbd/5/2049/physical-device 7:a to xenstore.
> Aug 21 13:05:18 proxy logger: /etc/xen/scripts/block: Writing backend/vbd/5/2049/hotplug-status connected to xenstore.
> Aug 21 13:05:19 proxy logger: /etc/xen/scripts/block: Writing backend/vbd/5/2050/node /dev/loop11 to xenstore.
> Aug 21 13:05:19 proxy logger: /etc/xen/scripts/block: Writing backend/vbd/5/2050/physical-device 7:b to xenstore.
> Aug 21 13:05:19 proxy logger: /etc/xen/scripts/block: Writing backend/vbd/5/2050/hotplug-status connected to xenstore.
> Aug 21 13:05:20 proxy kernel: [ 2604.768550] blkback: ring-ref 8, event-channel 8, protocol 1 (x86_32-abi)
> Aug 21 13:05:20 proxy kernel: [ 2604.775482] blkback: ring-ref 9, event-channel 9, protocol 1 (x86_32-abi)
Наверное поэтому: Aug 21 13:03:23 proxy logger: /etc/xen/scripts/vif-bridge: ifconfig vif4.0 down failed
Посмотри что у тебя после xm destroy domU_id в конфигурации моста (brctl eth0 show - вроде так)
Reply to: