FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > CentOS > CentOS

 
 
LinkBack Thread Tools
 
Old 12-28-2007, 12:19 AM
"Joseph L. Casale"
 
Default Xen Networking Issue with CentOS 5.1

Hi,
I tried this post on the Xen list first with no answer. I have 4 machines and 3 of which (all different) have no network access when booted into Xen. I tried using Fedora Core 8 and it produced the same results. Is it normal for the virbr0 interface to take an arbitrary IP? How does it decide what to use? An ifconfig when booted into Xen shows the following:

eth0 Link encap:Ethernet HWaddr 00:0C:29:4A:69:63
inet addr:192.168.5.30 Bcast:192.168.5.255 Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:fe4a:6963/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:25 errors:0 dropped:0 overruns:0 frame:0
TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1763 (1.7 KiB) TX bytes:594 (594.0 b)

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:3 errors:0 dropped:0 overruns:0 frame:0
TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:336 (336.0 b) TX bytes:336 (336.0 b)

peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:28 errors:0 dropped:0 overruns:0 frame:0
TX packets:21 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1943 (1.8 KiB) TX bytes:1314 (1.2 KiB)
Interrupt:17 Base address:0x1400

vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:9 errors:0 dropped:0 overruns:0 frame:0
TX packets:25 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:594 (594.0 b) TX bytes:1763 (1.7 KiB)

virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
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:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:468 (468.0 b)

xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:34 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1881 (1.8 KiB) TX bytes:0 (0.0 b)

Thanks for any pointers!
jlc

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 12-28-2007, 03:00 PM
"Gary Richardson"
 
Default Xen Networking Issue with CentOS 5.1

I think, but don't know for a fact, that if you don't specify a bridge interface in your config, you'll get a 'nat' address in your domU. I posted about it in my blog:*
http://yablog-gary.blogspot.com/2007/12/xen-what-i-learned-today.html -- maybe that will get you on the right track?thanks.

On Dec 27, 2007 5:19 PM, Joseph L. Casale <
jcasale@activenetwerx.com> wrote:
Hi,
I tried this post on the Xen list first with no answer. I have 4 machines and 3 of which (all different) have no network access when booted into Xen. I tried using Fedora Core 8 and it produced the same results. Is it normal for the virbr0 interface to take an arbitrary IP? How does it decide what to use? An ifconfig when booted into Xen shows the following:


eth0 * * *Link encap:Ethernet *HWaddr 00:0C:29:4A:69:63
* * * * *inet addr:192.168.5.30 *Bcast:192.168.5.255
*Mask:255.255.255.0
* * * * *inet6 addr: fe80::20c:29ff:fe4a:6963/64 Scope:Link
* * * * *UP BROADCAST RUNNING MULTICAST *MTU:1500 *Metric:1
* * * * *RX packets:25 errors:0 dropped:0 overruns:0 frame:0

* * * * *TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
* * * * *collisions:0 txqueuelen:0
* * * * *RX bytes:1763 (1.7 KiB) *TX bytes:594 (594.0 b)

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:3 errors:0 dropped:0 overruns:0 frame:0
* * * * *TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
* * * * *collisions:0 txqueuelen:0
* * * * *RX bytes:336 (336.0 b) *TX bytes:336 (336.0
b)

peth0 * * Link encap:Ethernet *HWaddr FE:FF:FF:FF:FF:FF
* * * * *inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
* * * * *UP BROADCAST RUNNING NOARP *MTU:1500 *Metric:1
* * * * *RX packets:28 errors:0 dropped:0 overruns:0 frame:0

* * * * *TX packets:21 errors:0 dropped:0 overruns:0 carrier:0
* * * * *collisions:0 txqueuelen:1000
* * * * *RX bytes:1943 (1.8 KiB) *TX bytes:1314 (1.2 KiB)
* * * * *Interrupt:17 Base address:0x1400


vif0.0 * *Link encap:Ethernet *HWaddr FE:FF:FF:FF:FF:FF
* * * * *inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
* * * * *UP BROADCAST RUNNING NOARP *MTU:1500 *Metric:1
* * * * *RX packets:9 errors:0 dropped:0 overruns:0 frame:0

* * * * *TX packets:25 errors:0 dropped:0 overruns:0 carrier:0
* * * * *collisions:0 txqueuelen:0
* * * * *RX bytes:594 (594.0 b) *TX bytes:1763 (1.7 KiB)

virbr0 * *Link encap:Ethernet *HWaddr 00:00:00:00:00:00

* * * * *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:0 errors:0 dropped:0 overruns:0 frame:0
* * * * *TX packets:6 errors:0 dropped:0 overruns:0 carrier:0

* * * * *collisions:0 txqueuelen:0
* * * * *RX bytes:0 (0.0 b) *TX bytes:468 (468.0 b)

xenbr0 * *Link encap:Ethernet *HWaddr FE:FF:FF:FF:FF:FF
* * * * *inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link

* * * * *UP BROADCAST RUNNING NOARP *MTU:1500 *Metric:1
* * * * *RX packets:34 errors:0 dropped:0 overruns:0 frame:0
* * * * *TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
* * * * *collisions:0 txqueuelen:0

* * * * *RX bytes:1881 (1.8 KiB) *TX bytes:0 (0.0 b)

Thanks for any pointers!
jlc

_______________________________________________
CentOS mailing list
CentOS@centos.org

http://lists.centos.org/mailman/listinfo/centos


_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 12-28-2007, 03:10 PM
Centos
 
Default Xen Networking Issue with CentOS 5.1

What is you actual problem? No networking or a strange ip?

CentOS uses virbr0 as the default and dnsmasc is issuing ip's
(192.168.1.x I believe) on this network (correct me if I'm wrong!).
xenbr0 is bridging the normal network.


I disabled the virbr0 using virsh and now all my domainU's use xenbr0.
You can also specify what bridge to use in de domainU-config-file
(/etc/xen/)


Cheers,

Bart

Joseph L. Casale wrote:

Hi,
I tried this post on the Xen list first with no answer. I have 4 machines and 3 of which (all different) have no network access when booted into Xen. I tried using Fedora Core 8 and it produced the same results. Is it normal for the virbr0 interface to take an arbitrary IP? How does it decide what to use? An ifconfig when booted into Xen shows the following:

eth0 Link encap:Ethernet HWaddr 00:0C:29:4A:69:63
inet addr:192.168.5.30 Bcast:192.168.5.255 Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:fe4a:6963/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:25 errors:0 dropped:0 overruns:0 frame:0
TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1763 (1.7 KiB) TX bytes:594 (594.0 b)

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:3 errors:0 dropped:0 overruns:0 frame:0
TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:336 (336.0 b) TX bytes:336 (336.0 b)

peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:28 errors:0 dropped:0 overruns:0 frame:0
TX packets:21 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1943 (1.8 KiB) TX bytes:1314 (1.2 KiB)
Interrupt:17 Base address:0x1400

vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:9 errors:0 dropped:0 overruns:0 frame:0
TX packets:25 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:594 (594.0 b) TX bytes:1763 (1.7 KiB)

virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
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:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:468 (468.0 b)

xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:34 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1881 (1.8 KiB) TX bytes:0 (0.0 b)

Thanks for any pointers!
jlc

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 12-28-2007, 03:32 PM
"Joseph L. Casale"
 
Default Xen Networking Issue with CentOS 5.1

>I think, but don't know for a fact, that if you don't specify a bridge interface in your config, you'll get a 'nat' address in your domU. I posted about it in my blog: http://yablog->gary.blogspot.com/2007/12/xen-what-i-learned-today.html -- maybe that will get you on the right track?
>
>thanks.
Gary,
I don't have a single DomU yet, as soon as I install Xen and reboot, I lose all network connectivity so I haven't proceeded! Is what you describe applicable to the Dom0 in any way?

Thanks!
jlc
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 12-28-2007, 03:33 PM
"Joseph L. Casale"
 
Default Xen Networking Issue with CentOS 5.1

>I disabled the virbr0 using virsh and now all my domainU's use xenbr0.

Bart,
How do you do this, I ran the command and attempted a few tries without any success?

Thanks!
jlc
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 12-29-2007, 02:13 PM
"Gary Richardson"
 
Default Xen Networking Issue with CentOS 5.1

No. I never experienced loss of networking in the Dom0. My guess is that your bridge interface isn't configured correctly. There's a bunch of good documentation on how Xen uses the different network interfaces.*
http://wiki.xensource.com/xenwiki/XenNetworking helped me understand it better.

On Dec 28, 2007 8:32 AM, Joseph L. Casale <jcasale@activenetwerx.com
> wrote:
>I think, but don't know for a fact, that if you don't specify a bridge interface in your config, you'll get a 'nat' address in your domU. I posted about it in my blog: *
http://yablog->gary.blogspot.com/2007/12/xen-what-i-learned-today.html -- maybe that will get you on the right track?

>
>thanks.
Gary,
I don't have a single DomU yet, as soon as I install Xen and reboot, I lose all network connectivity so I haven't proceeded! Is what you describe applicable to the Dom0 in any way?


Thanks!
jlc
_______________________________________________
CentOS mailing list
CentOS@centos.org

http://lists.centos.org/mailman/listinfo/centos


_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 12-29-2007, 03:18 PM
"Joseph L. Casale"
 
Default Xen Networking Issue with CentOS 5.1

>No. I never experienced loss of networking in the Dom0. My guess is that your bridge interface isn't configured correctly. There's a bunch of good >documentation on how Xen uses the different network interfaces. http://wiki.xensource.com/xenwiki/XenNetworking helped me understand it better.

I have read that over a few times now, but it misses the real fundamental elements that I am trying to learn now. Finally, installing CentOS without modifying _any_ defaults then logging in and performing a #yum install xen works? Problem is I don't want such a large bloated install, I had hoped for a minimal install but I am yet to deduce why the networking issue crops up repeatedly unless I install the defaults?

Do you know why the virbr0 in my system gets an IP not on my subnet, I only have one dhcp server which is scoped inside my subnet, obviously!

Soo confused

jlc
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 

Thread Tools




All times are GMT. The time now is 01:26 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org