[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Xen networking newbie


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Henrik Andersson <henrik.j.andersson@xxxxxxxxx>
  • Date: Fri, 4 Feb 2011 17:18:24 +0200
  • Delivery-date: Fri, 04 Feb 2011 07:19:17 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=nHPOmFlZG9kcK6U1XRn5p37nZ5fukSH/K4rUfCmE5iK55paRna1Kge6DMb2w2s28Qa y7rtgMFT7Rc2x6Sdxp5YkVG//+W4M0f5cIUCl12AI0ZwQeuNEV0gZkzfUuA6UUv80J5J 0KakUt6acH2Mgskd3/HACmilV6F1/iLPt/TkY=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

The IP you get? Where do you get it? From DHCP or from windows?

You do know that xen only gives mac address for the virtual ethernet adapter? You need to either configure IP-address manually or have dhcp enabled on the virtual machine for it to get/have ip address. Also you need to have dhcp server on the network for it (dhcp) to work.

I dont know what you mean by "is there a way that the the guest OS belong to the same network? so they can be communicate easily?" but you can assign any ip address to virtual host, xen doesn't mind. If routing works/they are on the same network, everything should work just as it would with non virtualized servers.

-Henrik Andersson
On 4 February 2011 16:49, Emir Sosa <emir@xxxxxxxxxxxxxx> wrote:
ok so i have centos installed configured with xen...installation went smooth.

the centOS is on 192.168.1.1/24 network

i managed to install windows server 2003 but the ip i get is 192.168.122.187 /24

this is what i get from ifconfig


eth0      Link encap:Ethernet  HWaddr 44:87:FC:55:23:49 
          inet addr:192.168.1.92  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::4687:fcff:fe55:2349/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:98604 errors:0 dropped:0 overruns:0 frame:0
          TX packets:44980 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:52446958 (50.0 MiB)  TX bytes:10128161 (9.6 MiB)

virbr0    Link encap:Ethernet  HWaddr 72:3E:16:81:25:6D 
          inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:594 errors:0 dropped:0 overruns:0 frame:0
          TX packets:213 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:89471 (87.3 KiB)  TX bytes:31046 (30.3 KiB)


and other stuff

but the thing is the windows server can ping the 192.168.1.1 but devices on 192.168.1.0 cant ping the 192.168.122.0(cuase they dont know of this network)

is there a way that the the guest OS belong to the same network? so they can be communicate easily?


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.