|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-users] Getting the bridged network running on Debian Squeeze with Xen 4.0.1
Hi,
For a few days, I have been trying to get a Xen 4.0.1 running on a fresh
installed Debian Squeeze 6.0.4. The host installation was fine at all. My
problem is, that I can't get the network in the guest domU up and running.
root@guest:~# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
root@guest:~# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 39:fa:a9:88:a1:5c
inet addr:192.168.67.14 Bcast:192.168.67.255 Mask:255.255.255.0
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:23
root@guest:~# ifconfig eth0 up
SIOCSIFFLAGS: Cannot assign requested address
On the Host, my xend-configuration.sxp looks like this:
(vif-script vif-bridge)
(network-script 'network-bridge bridge=eth0')
(dom0-min-mem 2048)
(enable-dom0-ballooning yes)
(total_available_memory 0)
(dom0-cpus 0)
(vncpasswd '').
(xend-unix-server yes)
brctl show looks like this:
bridge name bridge id STP enabled interfaces
eth0 8000.002590499320 no peth0
vif1.0
My host dmesg log looks like this:
[ 1110.116485] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 1122.775781] device vif2.0 entered promiscuous mode
[ 1122.781559] eth0: port 2(vif2.0) entering forwarding state
[ 1122.851644] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[ 1122.853593] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please
use
[ 1122.853597] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module
option or
[ 1122.853600] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
[ 1122.880067] physdev match: using --physdev-out in the OUTPUT, FORWARD and
POSTROUTING chains for non-bridged traffic is not supported anymore.
[ 1122.895044] physdev match: using --physdev-out in the OUTPUT, FORWARD and
POSTROUTING chains for non-bridged traffic is not supported anymore.
[ 1122.899251] physdev match: using --physdev-out in the OUTPUT, FORWARD and
POSTROUTING chains for non-bridged traffic is not supported anymore.
[ 1122.899258] physdev match: using --physdev-out in the OUTPUT, FORWARD and
POSTROUTING chains for non-bridged traffic is not supported anymore.
[ 1124.867103] blkback: ring-ref 770, event-channel 24, protocol 1 (x86_64-abi)
[ 1124.905556] blkback: ring-ref 771, event-channel 25, protocol 1 (x86_64-abi)
I created the guest with:
xen-create-image --force --fs=ext4 --genpass=0 --install=1
--memory=10G --password=test --pygrub --size=20G --swap=4G
--swap-dev=/dev/vg0/hostname.com-swap --vcpus=4 --dist=squeeze
--install-method=debootstrap --broadcast=192.168.67.127
--netmask=255.255.255.128 --gateway=192.168.67.1 --ip=192.168.67.14
--mac=39:fa:a9:88:a1:5c --nameserver=192.168.67.1 --hostname=hostname.com
--lvm=vg0
I found out that when I disable handle_iptables() (line 94 in
/etc/xen/scripts/vif-bridge), the errors about the physdev-out disappear, but
even when this error is gone the problem is still the same. I tried using
routed networking, but the same problem here. I have been reinstalling two
times but no success at all. I hope you can help me to find out how to get the
network in the guest running.
Thanks in Advance!
Daniel
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |