Using the latest packages by Ralph Passgang for Debian Sid my virtula machines suddenly have no networking access. Upon the guest systems there is an error bringing up eth0 which wasn''t present previously. Has something changed wrt to networking devices? I''ll not post y configuration file, since that might be a bit unweidy, but I changed nothing from 3.0.0 -> 3.0.1 and suddenly things are failing.. Steve -- Debian GNU/Linux System Administration http://www.debian-administration.org/ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Sat, Feb 04, 2006 at 03:06:39PM +0000, Steve Kemp wrote:> > Using the latest packages by Ralph Passgang for Debian Sid > my virtula machines suddenly have no networking access. > > Upon the guest systems there is an error bringing up eth0 > which wasn''t present previously. Has something changed wrt > to networking devices?I''m seeing this too using upgrading from the precompiled 3.0.0 packages to the precompiled 3.0.1 packages from the Xen web site. I also saw the same when compiling 3.0.1 from source. Bog standard configuration with domU eth0 bridged onto the physical ethernet interface, no changes to the networking scripts. dom0 and domU are both Debian Sarge. That''s all very vague as I haven''t done any investigation yet - but another data point perhaps. Cheers, Dominic. -- Dominic Hargreaves | http://www.larted.org.uk/~dom/ PGP key 5178E2A5 from the.earth.li (keyserver,web,email) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Am Samstag, 4. Februar 2006 16:06 schrieb Steve Kemp:> Using the latest packages by Ralph Passgang for Debian Sid > my virtula machines suddenly have no networking access. > > Upon the guest systems there is an error bringing up eth0 > which wasn''t present previously. Has something changed wrt > to networking devices? > > I''ll not post y configuration file, since that might be > a bit unweidy, but I changed nothing from 3.0.0 -> 3.0.1 > and suddenly things are failing.. > > SteveHi Steve, I don''t see this problem on my xen3 machines (sarge & sid), but I got a report from a user having a clean debian sarge installation with xen-3.0.1-0tha2 and having problems too, but more a problem with xend (maybe because I changed some python dependencies). But neverless, can you give some more information what happens in your domUs? Do you see any errors or is the network up but simply not working? Have you copied /lib/modules/2.6.12.6-xen to your domU fs after you upgraded your xen3.0.0 kernel to 3.0.1? and last but not least, do you use my linux-xen0-2.6 package or do you compile your kernel on your own? --Ralph _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Am Samstag, 4. Februar 2006 16:27 schrieb Dominic Hargreaves:> On Sat, Feb 04, 2006 at 03:06:39PM +0000, Steve Kemp wrote: > > Using the latest packages by Ralph Passgang for Debian Sid > > my virtula machines suddenly have no networking access. > > > > Upon the guest systems there is an error bringing up eth0 > > which wasn''t present previously. Has something changed wrt > > to networking devices? > > I''m seeing this too using upgrading from the precompiled 3.0.0 packages > to the precompiled 3.0.1 packages from the Xen web site. I also saw the > same when compiling 3.0.1 from source. Bog standard configuration with > domU eth0 bridged onto the physical ethernet interface, no changes to > the networking scripts. dom0 and domU are both Debian Sarge. > > That''s all very vague as I haven''t done any investigation yet - but > another data point perhaps.yes, it is... you said that you used another packages then steve, so it seems to be more an upstream problem then a package problem. Debian Sarge is frozen and hasn''t changed, so that can not be the problem at all, even if you and steve have this problems on debian sarge. I got 3 recent sarge boxes using xen 3.0.1 without this problem. --Ralph> Cheers, > > Dominic._______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Sat, Feb 04, 2006 at 04:47:21PM +0100, Ralph Passgang wrote:> But neverless, can you give some more information what happens in your domUs? > Do you see any errors or is the network up but simply not working? Have you > copied /lib/modules/2.6.12.6-xen to your domU fs after you upgraded your > xen3.0.0 kernel to 3.0.1?I did copy all the modules, and built my own kernel using the same .config files as before. Happily it is now resolved. Mark Nijmeijer suggested adding the following line to my domU configuration files: vif = [ '''' ] This allows my domains to access networking correctly. (I''ll update xen-tools to do this too.) Steve -- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Am Samstag, 4. Februar 2006 19:30 schrieb Steve Kemp:> On Sat, Feb 04, 2006 at 04:47:21PM +0100, Ralph Passgang wrote: > > But neverless, can you give some more information what happens in your > > domUs? Do you see any errors or is the network up but simply not working? > > Have you copied /lib/modules/2.6.12.6-xen to your domU fs after you > > upgraded your xen3.0.0 kernel to 3.0.1? > > I did copy all the modules, and built my own kernel using the same > .config files as before. > > Happily it is now resolved. Mark Nijmeijer suggested adding the > following line to my domU configuration files: > > vif = [ '''' ] > > This allows my domains to access networking correctly. > > (I''ll update xen-tools to do this too.)Oh, I always used a "vif =" line in my configs in the past, but I noticed that "nics =" is now deprecated. :) --Ralph> Steve_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users