Revision 12f9d75e
| b/doc/install.rst | ||
|---|---|---|
| 341 | 341 |
instances, through their interface, in the table you specified (under |
| 342 | 342 |
KVM, and in the main table under Xen). |
| 343 | 343 |
|
| 344 |
.. admonition:: Bridging issues with certain kernels |
|
| 345 |
|
|
| 346 |
Some kernel versions (e.g. 2.6.32) have an issue where the bridge |
|
| 347 |
will automatically change its ``MAC`` address to the lower-numbered |
|
| 348 |
slave on port addition and removal. This means that, depending on |
|
| 349 |
the ``MAC`` address of the actual NIC on the node and the addresses |
|
| 350 |
of the instances, it could be that starting, stopping or migrating |
|
| 351 |
instances will lead to timeouts due to the address of the bridge |
|
| 352 |
(and thus node itself) changing. |
|
| 353 |
|
|
| 354 |
To prevent this, it's enough to set the bridge manually to a |
|
| 355 |
specific ``MAC`` address, which will disable this automatic address |
|
| 356 |
change. In Debian, this can be done as follows in the bridge |
|
| 357 |
configuration snippet:: |
|
| 358 |
|
|
| 359 |
up ip link set addr $(cat /sys/class/net/$IFACE/address) dev $IFACE |
|
| 360 |
|
|
| 361 |
which will "set" the bridge address to the initial one, disallowing |
|
| 362 |
changes. |
|
| 363 |
|
|
| 344 | 364 |
.. admonition:: Bridging under Debian |
| 345 | 365 |
|
| 346 | 366 |
The recommended way to configure the Xen bridge is to edit your |
| ... | ... | |
| 357 | 377 |
bridge_ports eth0 |
| 358 | 378 |
bridge_stp off |
| 359 | 379 |
bridge_fd 0 |
| 380 |
# example for setting manually the bridge address to the eth0 NIC |
|
| 381 |
up ip link set addr $(cat /sys/class/net/eth0/address) dev $IFACE |
|
| 360 | 382 |
|
| 361 | 383 |
The following commands need to be executed on the local console: |
| 362 | 384 |
|
Also available in: Unified diff