Hi, i allready searched the archives, but found no message that really helps me. i am running debian etch on dom0 and debian sarge on domU. I had a running setup with debain sarge on dom0 before, but now with etch i can not get networking to work in domU. I use routed networking, but the same seems to happen with bridged networking: eth0 within domU is not brought up. I think it maybe related to udev, because sarge used hotpluging instead of udev. I boot domU with: xm create /dev/null kernel=/boot/vmlinuz-2.6-xen name=basic memory=150 disk=file:/images/basic.img,w root=/dev/hda ip=192.168.1.10 netmask=255.255.255.0 gateway="192.168.1.1" vif="ip=192.168.1.10" I tried it with the xen-binary-releases (not the deb-packages) xen 3.0.2 and xen 3.0.3, in both cases i had no success. Any hints how i could solve the problem, or gather more information that could help? Thank you, Julian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Julian Hagenauer wrote:> Hi, > i allready searched the archives, but found no message that really helps me. > i am running debian etch on dom0 and debian sarge on domU. > > I had a running setup with debain sarge on dom0 before, but now with etch i can not get networking to work in domU. > > I use routed networking, but the same seems to happen with bridged networking: eth0 within domU is not brought up. > > I think it maybe related to udev, because sarge used hotpluging instead of udev. > > I boot domU with: > xm create /dev/null kernel=/boot/vmlinuz-2.6-xen name=basic memory=150 disk=file:/images/basic.img,w root=/dev/hda ip=192.168.1.10 netmask=255.255.255.0 gateway="192.168.1.1" vif="ip=192.168.1.10" > > I tried it with the xen-binary-releases (not the deb-packages) xen 3.0.2 and xen 3.0.3, in both cases i had no success. > > Any hints how i could solve the problem, or gather more information that could help? > > Thank you, > Julian > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >Hi Julian, try http://lists.xensource.com/archives/html/xen-users/2006-10/msg00000.html and http://lists.xensource.com/archives/html/xen-users/2006-10/msg00003.html Sincerely, Jan. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Julian Hagenauer
2006-Oct-02 13:11 UTC
Re: [Xen-users] Neverending story: Networking in domU
> try > > http://lists.xensource.com/archives/html/xen-users/2006-10/msg00000.html > > and > > http://lists.xensource.com/archives/html/xen-users/2006-10/msg00003.html >Thank you for your answer. Unfortunately that helps not out. With the xen-binary comes no netloop-module (the loop-module is compiled in by default), nor do i have a missconfigured xend-config.sxp. Mine looks like: (xend-relocation-server yes) (xend-relocation-hosts-allow ''^localhost$ ^localhost\\.localdomain$'') (network-script network-nat) (vif-script vif-nat) (dom0-min-mem 196) (dom0-cpus 0) I think that should be ok. I can''t imagine what else could be wrong :-/ Sincerely, Julian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Julian Hagenauer
2006-Oct-02 14:45 UTC
Re: [Xen-users] Neverending story: Networking in domU
Hi, i think i am one step further. I looked at the outout of ifconfig at dom0 (i am using routed networking): eth0 Protokoll:Ethernet Hardware Adresse 00:16:D3:27:32:9E inet Adresse:192.168.1.15 Bcast:192.168.1.255 Maske:255.255.255.0 inet6 Adresse: fe80::216:d3ff:fe27:329e/64 Gültigkeitsbereich:Verbindung UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4219 errors:0 dropped:0 overruns:0 frame:0 TX packets:4242 errors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlänge:1000 RX bytes:3734115 (3.5 MiB) TX bytes:643767 (628.6 KiB) Interrupt:20 lo Protokoll:Lokale Schleife inet Adresse:127.0.0.1 Maske:255.0.0.0 inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:10 errors:0 dropped:0 overruns:0 frame:0 TX packets:10 errors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlänge:0 RX bytes:500 (500.0 b) TX bytes:500 (500.0 b) vif3.0 Protokoll:Ethernet Hardware Adresse FE:FF:FF:FF:FF:FF inet Adresse:192.168.1.137 Bcast:0.0.0.0 Maske:255.255.255.255 inet6 Adresse: fe80::fcff:ffff:feff:ffff/64 Gültigkeitsbereich:Verbindung UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlänge:100 RX bytes:0 (0.0 b) TX bytes:468 (468.0 b) Usually vif3.0 should have the same ip as eth0. I think the ip of vif3.0 is somehow random, because before the last reboot it was 192.168.1.16 ( maybe related to my dhcp-server, how assigns adresse starting from 192.168.1.15?) What could be the reason for the differing ips? How is the ip of vifX.0 determined? (As i said, i am using routed networking) Thanks, Julian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Julian Hagenauer
2006-Oct-02 17:05 UTC
Re: [Xen-users] Neverending story: Networking in domU
Hi, mhm, the fierrening ips resultet from a mistake i did confirguring routet network. Unfortunately that solves my problem not completly: eth0 is till not brought up, BUT i can with ''ifconfig 192.168.1.10 eth0 up'' bring up the interface and use it. Now i have to find out, why it is not braugh up automaticly... Maybe i will find something abiut that in the archives... Sincerely, Julian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users