Results 1 to 1 of 1
I'm having problems setting up networking for Xen 3.2 in Debian 5.0 (Lenny). At startup, it says:
Code:
ADDRCONF(NETDEV_UP): peth0: link is not ready
device peth0 entered promiscuous mode
ignoring ...
- 09-25-2009 #1Just Joined!
- Join Date
- Sep 2009
- Posts
- 2
Debian Lenny Xen Networking
I'm having problems setting up networking for Xen 3.2 in Debian 5.0 (Lenny).
At startup, it says:
# brctl showCode:ADDRCONF(NETDEV_UP): peth0: link is not ready device peth0 entered promiscuous mode ignoring unknown interface eth0_br=eth0br suspend: event channel 27
I added an /etc/mactab file, I changed /etc/xen/xend-config.sxp, I created a network-custom file in /etc/xen/scripts, and I modified /etc/network/interfaces. Everything else has been left unchanged.Code:bridge name bridge id stp enabled interface eth0_br 8000.macaddress no peth0
/etc/mactab:
/etc/xen/xend-config.sxpCode:# Eth0 eth0 xx:xx:xx:xx:xx:xx
/etc/xen/scripts/network-custom:Code:# -*- sh -*- # # Xend configuration file. # #(xend-http-server no) #(xend-unix-server no) #(xend-tcp-xmlrpc-server no) #(xend-unix-xmlrpc-server yes) #(xend-relocation-server no) ## # To bridge network traffic, like this: # # dom0: ----------------- bridge -> real eth0 -> the network # | # domU: fake eth0 -> vifN.0 -+ # # use # # (network-script network-bridge) (network-script network-custom) # Your default ethernet device is used as the outgoing interface, by default. # To use a different one (e.g. eth1) use # # (network-script 'network-bridge netdev=eth1') # # The bridge is named xenbr0, by default. To rename the bridge, use # # (network-script 'network-bridge bridge=<name>') # # It is possible to use the network-bridge script in more complicated # scenarios, such as having two outgoing interfaces, with two bridges, and # two fake interfaces per guest domain. To do things like this, write # yourself a wrapper script, and call network-bridge from it, as appropriate. # # (network-script network-dummy) (vif-script vif-bridge) ## Use the following if network traffic is routed, as an alternative to the # settings for bridged networking given above. #(network-script network-route) #(vif-script vif-route) ## Use the following if network traffic is routed with NAT, as an alternative # to the settings for bridged networking given above. #(network-script network-nat) #(vif-script vif-nat) # Dom0 will balloon out when needed to free memory for domU. # dom0-min-mem is the lowest memory level (in MB) dom0 will get down to. # If dom0-min-mem=0, dom0 will never balloon out. (dom0-min-mem 196) # In SMP system, dom0 will use dom0-cpus # of CPUS # If dom0-cpus = 0, dom0 will take all cpus available (dom0-cpus 0) # Whether to enable core-dumps when domains crash. #(enable-dump no) # The tool used for initiating virtual TPM migration #(external-migration-tool '') # The interface for VNC servers to listen on. Defaults # to 127.0.0.1 To restore old 'listen everywhere' behaviour # set this to 0.0.0.0 #(vnc-listen '127.0.0.1') # The default password for VNC console on HVM domain. # Empty string is no authentication. (vncpasswd '') # The VNC server can be told to negotiate a TLS session # to encryption all traffic, and provide x509 cert to # clients enalbing them to verify server identity. The # GTK-VNC widget, virt-viewer, virt-manager and VeNCrypt # all support the VNC extension for TLS used in QEMU. The # TightVNC/RealVNC/UltraVNC clients do not. # # To enable this create x509 certificates / keys in the # directory /etc/xen/vnc # # ca-cert.pem - The CA certificate # server-cert.pem - The Server certificate signed by the CA # server-key.pem - The server private key # # and then uncomment this next line # (vnc-tls 1) # The certificate dir can be pointed elsewhere.. # # (vnc-x509-cert-dir /etc/xen/vnc) # The server can be told to request & validate an x509 # certificate from the client. Only clients with a cert # signed by the trusted CA will be able to connect. This # is more secure the password auth alone. Passwd auth can # used at the same time if desired. To enable client cert # checking uncomment this: # # (vnc-x509-verify 1) # The default keymap to use for the VM's virtual keyboard # when not specififed in VM's configuration #(keymap 'en-us') # Script to run when the label of a resource has changed. #(resource-label-change-script '')
/etc/network/interfaces:Code:#!/bin/sh NETBR="/etc/xen/scripts/network-bridge" $NETBR start bridge="eth0_br" vifnum=0 netdev="eth0" exit 0
Code:# This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet static address xx.x.x.xxx netmask 255.255.255.0 network xx.x.x.x broadcast xx.x.x.xxx gateway xx.x.x.x # dns-* options are implemented by the resolvconf package, if installed dns-nameservers xx.x.x.xx


Reply With Quote
