[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] Xen Networking
Hello.Approach one issue at time. First thing first, get a stable networking configuration on your Dom0. Read http://wiki.xensource.com/xenwiki/XenNetworking , it has nice pictures. El 13/09/12 13:46, Vinicius Kwiecien Ruoso escribió: eth0 is the interface used in the local network (ip: 172.16.10.1, 255.255.255.0) eth1 is the interface connected to the internet modem (dhcp) Good. Forget this one for the moment, shut it down while troubleshooting, if possible. Reduce the variables.I have a vpn interface as well (ip: 172.16.10.1, 255.255.0.0) configured with tinc. What I want to do is to give the VM the IP 172.16.10.50, 255.255.255.0 gw 172.16.10.1, just like any other machine in the local network. That seems the right setup. OK. Now I have an installed windows, but no networking. It makes sense to me the usage of a bridge with eth0. Windows is not a guest system I would start with, but should work anyway. What do you suggest? #vif = [ 'mac=00:16:3e:XX:XX:XX,bridge=xenbr0' ] vif = [ 'type=ioemu,mac=00:16:3e:XX:XX:XX,bridge=xenbr0' ]Us the same valid MAC in both cases. Comment out the second line and uncomment the first, when (and if) you install PV drivers. Don't do that. Do not set up IP address on the eth0 itself AND the bridge, configure only one address once. configure Dom0's address, leave the VM to deal with it's IP address on it's own.I've tried those with different configurations in /etc/network/interfaces using: auto eth0 iface eth0 inet static address 172.16.10.1 netmask 255.255.255.0 auto xenbr0 iface xenbr0 inet static address 172.16.10.50 netmask 255.255.255.0 bridge_ports eth0 You probably started like this: auto eth0 iface eth0 inet static address 172.16.10.1 netmask 255.255.255.0 End like this: #auto eth0 #iface eth0 inet static # address 172.16.10.1 # netmask 255.255.255.0 auto xenbr0 iface xenbr0 inet static address 172.16.10.1 netmask 255.255.255.0 bridge_ports eth0 Note, that while you already have VMs running, a "networking restart" is not a good idea: a starting VM will attach it's network interface to a existing bridge, after a "network restart" this on-the-fly configuration will be broken.also didn't work. When I configure the interfaces like this and run /etc/init.d/networking restart, the eth0 looses it IP address, and nothing works anymore... If there is no running VM's, "network restart" should be a valid operation.I am leaving out of this the masquerading setup. It's complete different matter, approach it once your networking is fine. Cheers. -- Alexandre Kouznetsov _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxx http://lists.xen.org/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |