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@lists.xensource.com
http://lists.xensource.com/xen-users
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@masteremir.com> 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@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
The windows server is on DHCP and it got 192.168.122.187/24 i have no dhcp server setup(only router but that gives 192.168.1.0/24) the windows server can ping the routers and devices on 192.168.1.0 but from my router i cant ping 192.168.122.0/24 when i mean *"is there a way that the the guest OS belong to the same network? so they can be communicate easily?i mean *for the guest Os to be on the same subnet. thnx for helping..... On Fri, Feb 4, 2011 at 9:16 AM, Henrik Andersson < henrik.j.andersson@gmail.com> wrote:> 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@masteremir.com> 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@lists.xensource.com >> http://lists.xensource.com/xen-users >> > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, Feb 4, 2011 at 9:49 PM, Emir Sosa <emir@masteremir.com> wrote:> 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)192.168.122 is a private network to the xen dom0, created by libvirt (the virbr0 bridge)> > is there a way that the the guest OS belong to the same network? so they can > be communicate easily?Don''t use virbr0 then. There should be another bridge you can use, called xenbr0 (or eth0, depends on the xen version). -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Yes, quest OS can be on the same subnet. Just configure it like you would any windows server. You should propably check where that ip came from. My guess would be that it''s "windows zero conf" or something like that. Basicly windows assigns that ip if there is no static configuration or dhcp availeable. Try assigning some ip from 192.168.1.0/24 subnet manually and go from there. I don''t understand how you would be able to ping form wondows but not the other way, other than windows firewall preventing it. -Henrik Andersson On 4 February 2011 17:48, Emir Sosa <emir@masteremir.com> wrote:> The windows server is on DHCP and it got 192.168.122.187/24 i have no dhcp > server setup(only router but that gives 192.168.1.0/24) > > the windows server can ping the routers and devices on 192.168.1.0 but from > my router i cant ping 192.168.122.0/24 > > when i mean *"is there a way that the the guest OS belong to the same > network? so they can be communicate easily?i mean *for the guest Os to be > on the same subnet. > > thnx for helping..... > > On Fri, Feb 4, 2011 at 9:16 AM, Henrik Andersson < > henrik.j.andersson@gmail.com> wrote: > >> 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@masteremir.com> 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@lists.xensource.com >>> http://lists.xensource.com/xen-users >>> >> >> > > _______________________________________________ > 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
Ok, seem''s like I was talking crap. Didn''t know xen has such a feature. -Henrik Andersson On 4 February 2011 17:54, Fajar A. Nugraha <list@fajar.net> wrote:> On Fri, Feb 4, 2011 at 9:49 PM, Emir Sosa <emir@masteremir.com> wrote: > > 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) > > 192.168.122 is a private network to the xen dom0, created by libvirt > (the virbr0 bridge) > > > > > is there a way that the the guest OS belong to the same network? so they > can > > be communicate easily? > > Don''t use virbr0 then. > There should be another bridge you can use, called xenbr0 (or eth0, > depends on the xen version). > > -- > Fajar > > _______________________________________________ > 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
ok found my solution there are diff type of network the best one for me is bridge....the way it was on NAT(um port translation) any here is the solution http://www.virtuatopia.com/index.php/Xen_domainU_Guest_has_an_IP_address_on_192.168.122_subnet_instead_of_the_subnet_to_which_the_domain0_host_belongs i reboot the master and the guest OS and it works like a charm!!! On Fri, Feb 4, 2011 at 10:58 AM, Henrik Andersson < henrik.j.andersson@gmail.com> wrote:> Ok, seem''s like I was talking crap. Didn''t know xen has such a feature. > > -Henrik Andersson > > On 4 February 2011 17:54, Fajar A. Nugraha <list@fajar.net> wrote: > >> On Fri, Feb 4, 2011 at 9:49 PM, Emir Sosa <emir@masteremir.com> wrote: >> > 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) >> >> 192.168.122 is a private network to the xen dom0, created by libvirt >> (the virbr0 bridge) >> >> > >> > is there a way that the the guest OS belong to the same network? so they >> can >> > be communicate easily? >> >> Don''t use virbr0 then. >> There should be another bridge you can use, called xenbr0 (or eth0, >> depends on the xen version). >> >> -- >> Fajar >> >> _______________________________________________ >> 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