Hi,
I have an Ubuntu 7.10 system that I want to run Xen on. I tried
Ubuntu''s own
packages but was not satisfied with the stability, so decided to give
xen-unstable a try. I removed all xen related packages and removed /etc/xen
configuration files. (hope it was enough).
I downloaded xen source code from Mercurial repository and compiled the
whole package with "make world" then "make install".
Everything went
smoothly.
However, now I have eth0, lo and peth0, but no vif or xenbr0 interfaces.
What shall I do? Is there a way to completely rewrite xen network settings?
I don''t understand why it doesn''t create the necessary
interfaces...
here''s the ifconfig -a (network is operational for dom0)
emre@xenroot:~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:18:F3:9D:6E:FC
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:15 errors:0 dropped:0 overruns:0 frame:0
TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3354 (3.2 KB) TX bytes:13361 (13.0 KB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:513 errors:0 dropped:0 overruns:0 frame:0
TX packets:513 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3036964 (2.8 MB) TX bytes:3036964 (2.8 MB)
peth0 Link encap:Ethernet HWaddr 00:18:F3:9D:6E:FC
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:36 errors:0 dropped:0 overruns:0 frame:0
TX packets:45 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4974 (4.8 KB) TX bytes:14786 (14.4 KB)
Memory:fe9c0000-fea00000
Thanks a lot,
--
Emre Erenoglu
erenoglu@gmail.com
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
> I have an Ubuntu 7.10 system that I want to run Xen on. I tried Ubuntu''s > own packages but was not satisfied with the stability, so decided to give > xen-unstable a try. I removed all xen related packages and removed /etc/xen > configuration files. (hope it was enough). > > I downloaded xen source code from Mercurial repository and compiled the > whole package with "make world" then "make install". Everything went > smoothly. > > However, now I have eth0, lo and peth0, but no vif or xenbr0 interfaces.At some point the configuration changed so that the default bridge is called "eth0", presumably in order to break less tools that assume "eth0" as the primary network interface. Run "brctl show" and it should list eth0 as being a bridge on your system. Cheers, Mark> What shall I do? Is there a way to completely rewrite xen network > settings? I don''t understand why it doesn''t create the necessary > interfaces... > > here''s the ifconfig -a (network is operational for dom0) > > emre@xenroot:~$ ifconfig -a > eth0 Link encap:Ethernet HWaddr 00:18:F3:9D:6E:FC > inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:15 errors:0 dropped:0 overruns:0 frame:0 > TX packets:32 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:3354 (3.2 KB) TX bytes:13361 (13.0 KB) > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:513 errors:0 dropped:0 overruns:0 frame:0 > TX packets:513 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:3036964 (2.8 MB) TX bytes:3036964 (2.8 MB) > > peth0 Link encap:Ethernet HWaddr 00:18:F3:9D:6E:FC > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:36 errors:0 dropped:0 overruns:0 frame:0 > TX packets:45 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:4974 (4.8 KB) TX bytes:14786 (14.4 KB) > Memory:fe9c0000-fea00000 > > Thanks a lot,-- Dave: Just a question. What use is a unicyle with no seat? And no pedals! Mark: To answer a question with a question: What use is a skateboard? Dave: Skateboards have wheels. Mark: My wheel has a wheel! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Mark, Thanks for your mail. I understood now that it''s the case. In fact, when I put eth0 as the bridge name in xen domU conf files, the DomU booted OK. However, this shall be loudly "announced" somewhere, I''m sure many people can ask the same question. Br, Emre On Dec 11, 2007 2:23 AM, Mark Williamson <mark.williamson@cl.cam.ac.uk> wrote:> > I have an Ubuntu 7.10 system that I want to run Xen on. I tried Ubuntu''s > > own packages but was not satisfied with the stability, so decided to > give > > xen-unstable a try. I removed all xen related packages and removed > /etc/xen > > configuration files. (hope it was enough). > > > > I downloaded xen source code from Mercurial repository and compiled the > > whole package with "make world" then "make install". Everything went > > smoothly. > > > > However, now I have eth0, lo and peth0, but no vif or xenbr0 interfaces. > > At some point the configuration changed so that the default bridge is > called "eth0", presumably in order to break less tools that assume "eth0" > as > the primary network interface. > > Run "brctl show" and it should list eth0 as being a bridge on your system. > > Cheers, > Mark > > > What shall I do? Is there a way to completely rewrite xen network > > settings? I don''t understand why it doesn''t create the necessary > > interfaces... > > > > here''s the ifconfig -a (network is operational for dom0) > > > > emre@xenroot:~$ ifconfig -a > > eth0 Link encap:Ethernet HWaddr 00:18:F3:9D:6E:FC > > inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0 > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:15 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:32 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:3354 (3.2 KB) TX bytes:13361 (13.0 KB) > > > > lo Link encap:Local Loopback > > inet addr:127.0.0.1 Mask:255.0.0.0 > > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > RX packets:513 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:513 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:3036964 (2.8 MB) TX bytes:3036964 (2.8 MB) > > > > peth0 Link encap:Ethernet HWaddr 00:18:F3:9D:6E:FC > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:36 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:45 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:4974 (4.8 KB) TX bytes:14786 (14.4 KB) > > Memory:fe9c0000-fea00000 > > > > Thanks a lot, > > > > -- > Dave: Just a question. What use is a unicyle with no seat? And no pedals! > Mark: To answer a question with a question: What use is a skateboard? > Dave: Skateboards have wheels. > Mark: My wheel has a wheel! >-- Emre Erenoglu erenoglu@gmail.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> On Dec 11, 2007 2:23 AM, Mark Williamson <mark.williamson@cl.cam.ac.uk>wrote:> At some point the configuration changed so that the default bridge is > called "eth0", presumably in order to break less tools that assume "eth0" > as the primary network interface.On Tue December 11 2007 5:22:49 am Emre Erenoglu wrote:> Thanks for your mail. I understood now that it''s the case. In fact, when I > put eth0 as the bridge name in xen domU conf files, the DomU booted OK. > > However, this shall be loudly "announced" somewhere, I''m sure many people > can ask the same question.It''s not even in the comments for /etc/xen/xend-config.sxp, which still makes reference to xenbr0. This and the new /dev/xv* devices are just some of the reasons that the 3.0 docs shipped with all distros I use, or the urls below, are not making it anymore. http://www.cl.cam.ac.uk/research/srg/netos/xen/readmes/user/user.html The links on this page (same code, apparently) don''t work anymore: http://xen.org/xen/documentation.html http://xen.xensource.com/documentation.html _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users