Hi, Sorry for crossposting, but maybe it''s interesting to both lists. I''ve tried to run a 3.0-devel dom0 using the Mandriva 2006 packages, everything went fine except one very important thing :-( The dom0 Mandriva domain had no network after starting xend which started xen-br0, and obviously failed to copy the config of the real eth0 network interface, like it successfuly does on an other (Debian Sarge, with xen-2.0.6) box. Thanks in advance, Geza Gemes _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 11/6/05, Gémes Géza <geza@kzsdabas.sulinet.hu> wrote:> > Hi, > > Sorry for crossposting, but maybe it''s interesting to both lists. > > I''ve tried to run a 3.0-devel dom0 using the Mandriva 2006 packages, > everything went fine except one very important thing :-( The dom0 > Mandriva domain had no network after starting xend which started > xen-br0, and obviously failed to copy the config of the real eth0 > network interface, like it successfuly does on an other (Debian Sarge, > with xen-2.0.6) box. > > Thanks in advance, > > Geza Gemes > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >Do you mean it''s off the network or xen-br0 does not have an IP address assigned? Does xen-br0 have the IP address of dom0''s eth0? Does running the below help? /etc/xen/scripts/network stop /etc/xen/scripts/network start -- benjamin rualthanzauva _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
benjamin írta:> > > On 11/6/05, *Gémes Géza* <geza@kzsdabas.sulinet.hu > <mailto:geza@kzsdabas.sulinet.hu>> wrote: > > Hi, > > Sorry for crossposting, but maybe it''s interesting to both lists. > > I''ve tried to run a 3.0-devel dom0 using the Mandriva 2006 packages, > everything went fine except one very important thing :-( The dom0 > Mandriva domain had no network after starting xend which started > xen-br0, and obviously failed to copy the config of the real eth0 > network interface, like it successfuly does on an other (Debian Sarge, > with xen-2.0.6 ) box. > > Thanks in advance, > > Geza Gemes > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com <mailto:Xen-users@lists.xensource.com> > http://lists.xensource.com/xen-users > > > > Do you mean it''s off the network or xen-br0 does not have an IP > address assigned? Does xen-br0 have the IP address of dom0''s eth0? > Does running the below help? > > > /etc/xen/scripts/network stop > /etc/xen/scripts/network start > > > > > > -- > benjamin rualthanzauvaThe xen-br0 interface comes up, but it hasn''t any IPv4 address, in the same time eth0 cannot be seen from the network (of course) Apparently there is no /etc/xen/scripts/network, just /etc/xen/scripts/network.bridge and /etc/xen/scripts/network.route, they should be called by /etc/init.d/xend but they aren''t, that script simply calls /usr/sbin/xend, which is a python script, without any reference to /etc/xen/scripts/network* Shall I ad some refernces to the /etc/xen/scripts/network* scripts somwhere? TIA Geza Gemes _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 11/8/05, Gémes Géza <geza@kzsdabas.sulinet.hu> wrote:> > benjamin írta: > > > > > > > On 11/6/05, *Gémes Géza* <geza@kzsdabas.sulinet.hu > > <mailto:geza@kzsdabas.sulinet.hu>> wrote: > > > > Hi, > > > > Sorry for crossposting, but maybe it''s interesting to both lists. > > > > I''ve tried to run a 3.0-devel dom0 using the Mandriva 2006 packages, > > everything went fine except one very important thing :-( The dom0 > > Mandriva domain had no network after starting xend which started > > xen-br0, and obviously failed to copy the config of the real eth0 > > network interface, like it successfuly does on an other (Debian Sarge, > > with xen-2.0.6 ) box. > > > > Thanks in advance, > > > > Geza Gemes > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com <mailto:Xen-users@lists.xensource.com> > > http://lists.xensource.com/xen-users > > > > > > > > Do you mean it''s off the network or xen-br0 does not have an IP > > address assigned? Does xen-br0 have the IP address of dom0''s eth0? > > Does running the below help? > > > > > > /etc/xen/scripts/network stop > > /etc/xen/scripts/network start > > > > > > > > > > > > -- > > benjamin rualthanzauva > > The xen-br0 interface comes up, but it hasn''t any IPv4 address, in the > same time eth0 cannot be seen from the network (of course) > Apparently there is no /etc/xen/scripts/network, just > /etc/xen/scripts/network.bridge and /etc/xen/scripts/network.route, they > should be called by /etc/init.d/xend but they aren''t, that script simply > calls /usr/sbin/xend, which is a python script, without any reference to > /etc/xen/scripts/network* > Shall I ad some refernces to the /etc/xen/scripts/network* scripts > somwhere? > > TIA > > Geza Gemes > >I am sorry. In 3.0, there should be network-bridge , network-nat, network-route -- benjamin rualthanzauva _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I am not sure if this should be on this list or Mandriva, but I am also having the same problem using the Mandriva xen-3.0 package (which seems to be using a snapshot form Aug 23, 2005, based on the name of the tarball in the SRPM) I am also using the Mandriva-patched kernel for Dom0, which is really just the standard Mandriva kernel but patched for Xen. If I boot into the stock (non-Xen-enabled) kernel, all is good. If I boot into the Dom0 kernel, all the right interfaces come up, but no IP is obtained (via DHCP). If I try to specify a static IP on eth0 and manually add the gateway information, I am still unable to ping out from the machine, nor get ping replies from it. There are no IPTables rules running. I do not believe the problem has to do with ''xend'', as I have stopped it, with no luck resulting, and have also set it to not start on reboot and then rebooted, with no IP still showing up on eth0. I am not sure if the problem lies with the xen-3.0 or the Mandriva packages. I have downloaded the latest "xen-unstable-src.tgz" file fromt he downloads page and will attempt to build a new RPM with that code and see if that fixes anything, but also just wanted to see if any other answers might be out there. TIA for your help. -Alan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> I am not sure if this should be on this list or Mandriva, but > I am also having the same problem using the Mandriva xen-3.0 > package (which seems to be using a snapshot form Aug 23, > 2005, based on the name of the tarball in the SRPM) > > I am also using the Mandriva-patched kernel for Dom0, which > is really just the standard Mandriva kernel but patched for Xen. > > If I boot into the stock (non-Xen-enabled) kernel, all is > good. If I boot into the Dom0 kernel, all the right > interfaces come up, but no IP is obtained (via DHCP). If I > try to specify a static IP on eth0 and manually add the > gateway information, I am still unable to ping out from the > machine, nor get ping replies from it.The problem is likely due to the ''network-bridge'' script needing a couple of tweaks for Mandriva. Staright after booting into xen-ified kernel, run ''sh -x /etc/xen/scripts/netork-bridge start'' and see what happens. Ian> There are no IPTables rules running. > > I do not believe the problem has to do with ''xend'', as I have > stopped it, with no luck resulting, and have also set it to > not start on reboot and then rebooted, with no IP still > showing up on eth0. > > I am not sure if the problem lies with the xen-3.0 or the > Mandriva packages. > > I have downloaded the latest "xen-unstable-src.tgz" file > fromt he downloads page and will attempt to build a new RPM > with that code and see if that fixes anything, but also just > wanted to see if any other answers might be out there. > > TIA for your help. > > -Alan > > > > _______________________________________________ > 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