Hi All, Now that I''ve got my domU running under OpenSUSE 10.0 I have an issue with setting up eth0 in the domU. The xenbr0 bridge is setup correctly in the dom0: # mnemosyne:/etc/xen # brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.feffffffffff no vif0.0 peth0 vif4.0 However, there is only the lo interface in domU: xenos10:/etc/sysconfig/network # 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:13 errors:0 dropped:0 overruns:0 frame:0 TX packets:13 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1135 (1.1 Kb) TX bytes:1135 (1.1 Kb) The contents of /etc/sysconfig/network in the domU is: xenos10:/etc/sysconfig/network # ls . config if-down.d ifcfg-lo ifroute-lo scripts . dhcp if-up.d ifcfg.template providers wireless However, executing rcnetwork restart in the domU produces the following: xenos10:/etc/sysconfig/network # rcnetwork restart Shutting down network interfaces: eth1 eth1 No configuration found for eth1 Nevertheless the interface will be shut down. eth1 configuration: done veth0 veth0 No configuration found for veth0 Nevertheless the interface will be shut down. veth0 configuration: done veth1 veth1 No configuration found for veth1 Nevertheless the interface will be shut down. veth1 configuration: done veth2 veth2 No configuration found for veth2 Nevertheless the interface will be shut down. veth2 configuration: done veth3 veth3 No configuration found for veth3 Nevertheless the interface will be shut down. veth3 configuration: done veth4 veth4 No configuration found for veth4 Nevertheless the interface will be shut down. veth4 configuration: done veth5 veth5 No configuration found for veth5 Nevertheless the interface will be shut down. veth5 configuration: done veth6 veth6 No configuration found for veth6 Nevertheless the interface will be shut down. veth6 configuration: done veth7 veth7 No configuration found for veth7 Nevertheless the interface will be shut down. veth7 configuration: done vif0.0 vif0.0 No configuration found for vif0.0 Nevertheless the interface will be shut down. vif0.0 configuration: done vif0.1 vif0.1 No configuration found for vif0.1 Nevertheless the interface will be shut down. vif0.1 configuration: done vif0.2 vif0.2 No configuration found for vif0.2 Nevertheless the interface will be shut down. vif0.2 configuration: done vif0.3 vif0.3 No configuration found for vif0.3 Nevertheless the interface will be shut down. vif0.3 configuration: done vif0.4 vif0.4 No configuration found for vif0.4 Nevertheless the interface will be shut down. vif0.4 configuration: done vif0.5 vif0.5 No configuration found for vif0.5 Nevertheless the interface will be shut down. vif0.5 configuration: done vif0.6 vif0.6 No configuration found for vif0.6 Nevertheless the interface will be shut down. vif0.6 configuration: done vif0.7 vif0.7 No configuration found for vif0.7 Nevertheless the interface will be shut down. vif0.7 configuration: done Shutting down service network . . . . . . . . . . . . . done. Setting up network interfaces: lo lo IP address: 127.0.0.1/8 done eth1 eth1 No configuration found for eth1 unused veth0 veth0 No configuration found for veth0 unused veth1 veth1 No configuration found for veth1 unused veth2 veth2 No configuration found for veth2 unused veth3 veth3 No configuration found for veth3 unused veth4 veth4 No configuration found for veth4 unused veth5 veth5 No configuration found for veth5 unused veth6 veth6 No configuration found for veth6 unused veth7 veth7 No configuration found for veth7 unused vif0.0 vif0.0 No configuration found for vif0.0 unused vif0.1 vif0.1 No configuration found for vif0.1 unused vif0.2 vif0.2 No configuration found for vif0.2 unused vif0.3 vif0.3 No configuration found for vif0.3 unused vif0.4 vif0.4 No configuration found for vif0.4 unused vif0.5 vif0.5 No configuration found for vif0.5 unused vif0.6 vif0.6 No configuration found for vif0.6 unused vif0.7 vif0.7 No configuration found for vif0.7 unused Setting up service network . . . . . . . . . . . . . . done. Is this normal? I have tried using ifconfig eth0 192.168.0.3 up in the domU but get an error that the device does not exist. I thought that a network interface would be created in the domU due to the vif line in the domU config file? How can I create eth0 in the domU? Thanks again, Steve. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I think I solved the problem. ifconfig -a showed a lot of network interfaces, one of which, eth1, had the MAC address I specified in the vif line of the domU config line. Issuing ifconfig eth1 192.168.0.3 up allows the domU to now ping the network. Writing the email made me think through the problem :-) I assume I can create an ifcfg-eth1 file in /etc/sysconfig/network in the domU to make eth1 come up automatically? Thanks, Steve. Quoting higgers <hpq8bfr.mailing.lists@dsl.pipex.com>:> Hi All, > > Now that I''ve got my domU running under OpenSUSE 10.0 I have an issue with > setting up eth0 in the domU. > > The xenbr0 bridge is setup correctly in the dom0: > > # mnemosyne:/etc/xen # brctl show > bridge name bridge id STP enabled interfaces > xenbr0 8000.feffffffffff no vif0.0 > peth0 > vif4.0 > > However, there is only the lo interface in domU: > > xenos10:/etc/sysconfig/network # 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:13 errors:0 dropped:0 overruns:0 frame:0 > TX packets:13 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:1135 (1.1 Kb) TX bytes:1135 (1.1 Kb) > > The contents of /etc/sysconfig/network in the domU is: > > xenos10:/etc/sysconfig/network # ls > . config if-down.d ifcfg-lo ifroute-lo scripts > . dhcp if-up.d ifcfg.template providers wireless > > However, executing rcnetwork restart in the domU produces the following: > > > xenos10:/etc/sysconfig/network # rcnetwork restart > Shutting down network interfaces: > eth1 > eth1 No configuration found for eth1 > Nevertheless the interface will be shut down. > eth1 configuration: done > veth0 > veth0 No configuration found for veth0 > Nevertheless the interface will be shut down. > veth0 configuration: done > veth1 > veth1 No configuration found for veth1 > Nevertheless the interface will be shut down. > veth1 configuration: done > veth2 > veth2 No configuration found for veth2 > Nevertheless the interface will be shut down. > veth2 configuration: done > veth3 > veth3 No configuration found for veth3 > Nevertheless the interface will be shut down. > veth3 configuration: done > veth4 > veth4 No configuration found for veth4 > Nevertheless the interface will be shut down. > veth4 configuration: done > veth5 > veth5 No configuration found for veth5 > Nevertheless the interface will be shut down. > veth5 configuration: done > veth6 > veth6 No configuration found for veth6 > Nevertheless the interface will be shut down. > veth6 configuration: done > veth7 > veth7 No configuration found for veth7 > Nevertheless the interface will be shut down. > veth7 configuration: done > vif0.0 > vif0.0 No configuration found for vif0.0 > Nevertheless the interface will be shut down. > vif0.0 configuration: done > vif0.1 > vif0.1 No configuration found for vif0.1 > Nevertheless the interface will be shut down. > vif0.1 configuration: done > vif0.2 > vif0.2 No configuration found for vif0.2 > Nevertheless the interface will be shut down. > vif0.2 configuration: done > vif0.3 > vif0.3 No configuration found for vif0.3 > Nevertheless the interface will be shut down. > vif0.3 configuration: done > vif0.4 > vif0.4 No configuration found for vif0.4 > Nevertheless the interface will be shut down. > vif0.4 configuration: done > vif0.5 > vif0.5 No configuration found for vif0.5 > Nevertheless the interface will be shut down. > vif0.5 configuration: done > vif0.6 > vif0.6 No configuration found for vif0.6 > Nevertheless the interface will be shut down. > vif0.6 configuration: done > vif0.7 > vif0.7 No configuration found for vif0.7 > Nevertheless the interface will be shut down. > vif0.7 configuration: done > Shutting down service network . . . . . . . . . . . . . done. > Setting up network interfaces: > lo > lo IP address: 127.0.0.1/8 done > eth1 > eth1 No configuration found for eth1 unused > veth0 > veth0 No configuration found for veth0 unused > veth1 > veth1 No configuration found for veth1 unused > veth2 > veth2 No configuration found for veth2 unused > veth3 > veth3 No configuration found for veth3 unused > veth4 > veth4 No configuration found for veth4 unused > veth5 > veth5 No configuration found for veth5 unused > veth6 > veth6 No configuration found for veth6 unused > veth7 > veth7 No configuration found for veth7 unused > vif0.0 > vif0.0 No configuration found for vif0.0 unused > vif0.1 > vif0.1 No configuration found for vif0.1 unused > vif0.2 > vif0.2 No configuration found for vif0.2 unused > vif0.3 > vif0.3 No configuration found for vif0.3 unused > vif0.4 > vif0.4 No configuration found for vif0.4 unused > vif0.5 > vif0.5 No configuration found for vif0.5 unused > vif0.6 > vif0.6 No configuration found for vif0.6 unused > vif0.7 > vif0.7 No configuration found for vif0.7 unused > Setting up service network . . . . . . . . . . . . . . done. > > Is this normal? > > I have tried using ifconfig eth0 192.168.0.3 up in the domU but get an error > > that the device does not exist. > > I thought that a network interface would be created in the domU due to the > vif > line in the domU config file? > > How can I create eth0 in the domU? > > Thanks again, > > Steve. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >-- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Stefan Schueffler
2006-Mar-14 12:44 UTC
Re: [Xen-users] Network Problem in domU under OpenSUSE 10.0
Hi I think you have a problem with the udev-rules. on suse-linux, the rules will give a persistent name to a mac address. i guess you tried to install xen some times before, so that the interface eth0 is locked to a (now unused) mac-address (and thus your suse selected eth1 as next free interface). you can release this mac-address-to-eth-interface-mapping by editing /etc/udev/rules.d/30-net_persistent_names.rules and deleting the (unused) line "eth0" _and_ the line for your eth1 in your domU. after a reboot, the device should show as eth0 instead as of eth0, and all the network-magic should work as expected. regards stefan ...................................................... Geschäftsführer softgarden GmbH Universität des Saarlandes . Geb. A1.1 66123 Saarbrücken T 0049 (0) 681 7 61 69 88 F 0049 (0) 681 6 85 27 02 office@softgarden.de http://www.softgarden.de _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users