Re: [Xen-users] Vanilla Kernel -- eth0: ERROR while getting interface flags: No such device

[Tegger <xen@xxxxxxxxx>]

I tried to load the module automatic with modprobe.conf but it doesn't 
work....
Setting up networking....
Configuring network interfaces...modprobe: WARNING: /etc/modprobe.conf 
line 1: ignoring bad line starting with 'xennet'
SIOCSIFADDR: No such device
modprobe: WARNING: /etc/modprobe.conf line 1: ignoring bad line starting 
with 'xennet'
eth0: ERROR while getting interface flags: No such device
modprobe: WARNING: /etc/modprobe.conf line 1: ignoring bad line starting 
with 'xennet'
SIOCSIFNETMASK: No such device
modprobe: WARNING: /etc/modprobe.conf line 1: ignoring bad line starting 
with 'xennet'
eth0: ERROR while getting interface flags: No such device
Failed to bring up eth0.
done.
INIT: Entering runlevel: 2




Am 02.04.2010 20:02, schrieb Tegger:
> the modul xennet wasn't started
> after modprobe xennet and ifup eth0
> the network is working
>
>
> Am 02.04.2010 16:49, schrieb Tegger:
> > works, and ifconfig shows only localhost
> >
> > xen205:~# ifconfig -a
> > 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:0 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:0 (0.0 B)  TX bytes:0 (0.0 B)
> >
> >
> > Dom0 interfaces :
> >
> > xen0:~# ifconfig -a
> > eth0      Link encap:Ethernet  Hardware Adresse 00:27:0e:08:47:1e
> >           inet Adresse:192.168.123.101  Bcast:192.168.123.255  
> > Maske:255.255.255.0
> >           inet6-Adresse: fe80::227:eff:fe08:471e/64 
> > GÃÂltigkeitsbereich:Verbindung
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metrik:1
> >           RX packets:3678774 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:2072462 errors:0 dropped:0 overruns:0 carrier:0
> >           Kollisionen:0 SendewarteschlangenlÃÂnge:0
> >           RX bytes:5508142978 (5.1 GiB)  TX bytes:149710680 (142.7 MiB)
> >
> > lo        Link encap:Lokale Schleife
> >           inet Adresse:127.0.0.1  Maske:255.0.0.0
> >           inet6-Adresse: ::1/128 GÃÂltigkeitsbereich:Maschine
> >           UP LOOPBACK RUNNING  MTU:16436  Metrik:1
> >           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> >           Kollisionen:0 SendewarteschlangenlÃÂnge:0
> >           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
> >
> > peth0     Link encap:Ethernet  Hardware Adresse 00:27:0e:08:47:1e
> >           inet6-Adresse: fe80::227:eff:fe08:471e/64 
> > GÃÂltigkeitsbereich:Verbindung
> >           UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metrik:1
> >           RX packets:3678775 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:2072470 errors:0 dropped:0 overruns:0 carrier:0
> >           Kollisionen:0 SendewarteschlangenlÃÂnge:10
> >           RX bytes:5559647662 (5.1 GiB)  TX bytes:149711316 (142.7 MiB)
> >           Speicher:f0100000-f0120000
> >
> > vif2.0    Link encap:Ethernet  Hardware Adresse fe:ff:ff:ff:ff:ff
> >           inet6-Adresse: fe80::fcff:ffff:feff:ffff/64 
> > GÃÂltigkeitsbereich:Verbindung
> >           UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metrik:1
> >           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:0 errors:0 dropped:71 overruns:0 carrier:0
> >           Kollisionen:0 SendewarteschlangenlÃÂnge:32
> >           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
> >
> >
> > Am 02.04.2010 16:26, schrieb Thomas Halinka:
> > > Hi,
> > >
> > > use hvc0 as console and see whats going on...
> > >
> > > You need to alter /etc/inittab in your domU
> > >
> > > 1:2345:respawn:/sbin/getty 38400 hvc0
> > >
> > > Then you should be able to login through "xm console".
> > >
> > > Check Networking with ifconfig -a
> > >
> > > cu,
> > >
> > > thomas
> > >
> > > Am Freitag, den 02.04.2010, 15:25 +0200 schrieb Tegger:
> > > > hi,
> > > >
> > > > i have problems with Debian Dom0 and Debian domU. I create the DomU 
> > > > with
> > > > xen-tools, changed hda to xvda, but i didn't get a console and network
> > > > i have a compiled 2.6.31.12 kernel by myself....
> > > >
> > > > ############################################################################################ 
> > > >
> > > > # Configuration file for the Xen instance xen205, created
> > > > # by xen-tools 3.9 on Thu Apr  1 14:29:36 2010.
> > > > #
> > > >
> > > > #
> > > > #  Kernel + memory size
> > > > #
> > > > kernel      = '/boot/vmlinuz-2.6.31.12'
> > > > ramdisk     = '/boot/initrd.img-2.6.31.12'
> > > > memory      = '512'
> > > >
> > > >
> > > > #
> > > > #  Disk device(s).
> > > > #
> > > > root        = '/dev/xvda1 ro'
> > > > disk        = [
> > > >
> > > > 'file:/home/user/vm_images/domains/xen205/swap.img,xvda2,w',
> > > >
> > > > 'file:/home/user/vm_images/domains/xen205/disk.img,xvda1,w',
> > > >                 ]
> > > >
> > > >
> > > > #
> > > > #  Hostname
> > > > #
> > > > name        = 'xen205'
> > > >
> > > > #
> > > > #  Networking
> > > > #
> > > > vif         = [ 'ip=192.168.123.205,mac=00:16:3E:E6:88:8B' ]
> > > >
> > > > #
> > > > #  Behaviour
> > > > #
> > > > on_poweroff = 'destroy'
> > > > on_reboot   = 'restart'
> > > > on_crash    = 'restart'
> > > > ############################################################################################ 
> > > >
> > > > this are the last lines at bootup
> > > >
> > > >
> > > > ############################################################################################ 
> > > >
> > > > INIT: version 2.86 booting
> > > > Mount point '/dev/shm' does not exist. Skipping mount. (warning).
> > > > Setting the system clock.
> > > > Cannot access the Hardware Clock via any known method.
> > > > Use the --debug option to see the details of our search for an access
> > > > method.
> > > > Unable to set System Clock to: Fri Apr 2 12:45:45 UTC 2010 (warning).
> > > > Activating swap...done.
> > > > Checking root file system...fsck 1.41.3 (12-Oct-2008)
> > > > /lib/init/rw/rootdev: clean, 12098/327680 files, 350810/1310720 blocks
> > > > done.
> > > > EXT3 FS on xvda1, internal journal
> > > > Setting the system clock.
> > > > Cannot access the Hardware Clock via any known method.
> > > > Use the --debug option to see the details of our search for an access
> > > > method.
> > > > Unable to set System Clock to: Fri Apr 2 12:45:46 UTC 2010 (warning).
> > > > Cleaning up ifupdown....
> > > > Loading kernel modules...done.
> > > > Checking file systems...fsck 1.41.3 (12-Oct-2008)
> > > > done.
> > > > Setting kernel variables (/etc/sysctl.conf)...done.
> > > > Mounting local filesystems...done.
> > > > Activating swapfile swap...done.
> > > > Setting up networking....
> > > > Configuring network interfaces...SIOCSIFADDR: No such device
> > > > eth0: ERROR while getting interface flags: No such device
> > > > SIOCSIFNETMASK: No such device
> > > > eth0: ERROR while getting interface flags: No such device
> > > > Failed to bring up eth0.
> > > > done.
> > > > INIT: Entering runlevel: 2
> > > > Starting enhanced syslogd: rsyslogd.
> > > > Starting OpenBSD Secure Shell server: sshdNET: Registered protocol 
> > > > family 10
> > > > lo: Disabled Privacy Extensions
> > > > .
> > > > Starting periodic command scheduler: crond.
> > > > ############################################################################################### 
> > > >
> > > >
> > > >
> > > > there are Problem with
> > > >
> > > > - Hardware Clock
> > > > - /dev/shm
> > > > - network eth0
> > > >
> > > > and perhaps with console......
> > > >
> > > > _______________________________________________
> > > > Xen-users mailing list
> > > > Xen-users@xxxxxxxxxxxxxxxxxxx
> > > > http://lists.xensource.com/xen-users
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users