hi, after rebooting my host, i can''t have anymore the networking: here''s my output of /etc/init.d/networking restart Reconfiguring 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. cat /etc/xen/oreon.cfg kernel = ''/boot/vmlinuz-2.6.18-xen'' memory = ''32'' root = ''/dev/hda1 ro'' disk = [ ''file:/data/vserver/domains/oreon/disk.img,hda1,w'', ''file:/data/vserver/domains/oreon/swap.img,hda2,w'' ] name = ''oreon'' vif = [ ''ip=172.20.22.197'' ] on_poweroff = ''destroy'' on_reboot = ''restart'' on_crash = ''restart until today, it worked fine... cat /var/log/xen/xen-hotplug.log Nothing to flush. xenstore-read: couldn''t read path backend/vbd/8/769/node Nothing to flush. any help would be appreciated. thank in advance. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Koonz, more info will be necesary to solve the problem. Which is your network adapter? the kernel module loaded? Can you post the output of # ifconfig -a and # dmesg Regards, Marc ko0nz wrote:> hi, > > after rebooting my host, i can''t have anymore the networking: > here''s my output of /etc/init.d/networking restart > > Reconfiguring 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. > > cat /etc/xen/oreon.cfg > > kernel = ''/boot/vmlinuz-2.6.18-xen'' > memory = ''32'' > root = ''/dev/hda1 ro'' > disk = [ ''file:/data/vserver/domains/oreon/disk.img,hda1,w'', > ''file:/data/vserver/domains/oreon/swap.img,hda2,w'' ] > name = ''oreon'' > > vif = [ ''ip=172.20.22.197'' ] > > on_poweroff = ''destroy'' > on_reboot = ''restart'' > on_crash = ''restart > > until today, it worked fine... > > cat /var/log/xen/xen-hotplug.log > > Nothing to flush. > xenstore-read: couldn''t read path backend/vbd/8/769/node > Nothing to flush. > > any help would be appreciated. > thank in advance. > > _______________________________________________ > 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
hi Marc,
# ifconfig Dom0
eth0 Link encap:Ethernet HWaddr 00:0F:FE:6B:57:32
inet addr:172.20.22.191 Bcast:172.20.22.255 Mask:255.255.255.0
inet6 addr: fe80::20f:feff:fe6b:5732/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:24218 errors:0 dropped:0 overruns:0 frame:0
TX packets:33136 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2952113 (2.8 MiB) TX bytes:17840137 (17.0 MiB)
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:56113 errors:0 dropped:0 overruns:0 frame:0
TX packets:56113 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:14474440 (13.8 MiB) TX bytes:14474440 (13.8 MiB)
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:24551 errors:0 dropped:0 overruns:0 frame:0
TX packets:36349 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:3183587 (3.0 MiB) TX bytes:18200935 (17.3 MiB)
Base address:0x1100 Memory:f0500000-f0520000
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:33136 errors:0 dropped:0 overruns:0 frame:0
TX packets:24219 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:17840137 (17.0 MiB) TX bytes:2952183 (2.8 MiB)
vif2.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:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:32 errors:0 dropped:9594 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:0 (0.0 b) TX bytes:8368 (8.1 KiB)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:13505 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1947100 (1.8 MiB) TX bytes:168 (168.0 b)
# dmesg Dom0
vif4.0: no IPv6 routers present
xenbr0: port 4(vif4.0) entering disabled state
device vif4.0 left promiscuous mode
audit(1184761578.260:10): dev=vif4.0 prom=0 old_prom=256 auid=4294967295
xenbr0: port 4(vif4.0) entering disabled state
device vif5.0 entered promiscuous mode
audit(1184761578.670:11): dev=vif5.0 prom=256 old_prom=0 auid=4294967295
xenbr0: port 4(vif5.0) entering learning state
xenbr0: topology change detected, propagating
xenbr0: port 4(vif5.0) entering forwarding state
blkback: ring-ref 8, event-channel 6, protocol 1 (x86_32-abi)
blkback: ring-ref 9, event-channel 7, protocol 1 (x86_32-abi)
vif5.0: no IPv6 routers present
xenbr0: port 4(vif5.0) entering disabled state
device vif5.0 left promiscuous mode
audit(1184761929.900:12): dev=vif5.0 prom=0 old_prom=256 auid=4294967295
xenbr0: port 4(vif5.0) entering disabled state
# ifconfig Dom2
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:6 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:504 (504.0 b) TX bytes:504 (504.0 b)
# dmesg Dom2
IA-32 Microcode Update Driver: v1.14a-xen <tigran@veritas.com>
audit: initializing netlink socket (disabled)
audit(1184761327.801:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Floppy drive(s): fd0 is unknown type 15 (usb?), fd1 is unknown type 15 (usb?)
Failed to obtain physical IRQ 6
floppy0: no floppy controllers found
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
loop: loaded (max 8 devices)
Xen virtual console successfully installed as tty1
Event-channel device installed.
netfront: Initialising virtual ethernet driver.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI No-Shortcut mode
xen-vbd: registered block device major 3
blkfront: hda1: barriers enabled
blkfront: hda2: barriers enabled
netfront: device eth0 has copying receive path.
XENBUS: Device with no driver: device/console/0
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
EXT2-fs warning (device hda1): ext2_fill_super: mounting ext3 filesystem as ext2
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 192k freed
serial_core: no version for "struct_module" found: kernel tainted.
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
Adding 262136k swap on /dev/hda2. Priority:-1 extents:1 across:262136k
device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@redhat.com
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
thank in advance.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hi again,
sorry, after reading the first post I belived that problem was on
dom0''s
eth0 (my english is not as good as I want :) ), anyway the problem is in
your domU, and you can''t see eth0 when you make an ifconfig -a ( the
flag "a" is important).
When you boot your domU you see domU''s eth0? Or the problem appears
when
you restart the network init script?
On the other hand, in your dom0 ifconfig shows vif2.0 (I supose that you
are only running one DomU), so... it''s quite strange, also it shows
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:32 errors:0 dropped:9594 overruns:0 carrier:0
it''s dropping packets, you know why?
Probably if you post "xm create -c /etc/xen/oreon" output somebody
could help you, the output of a "brctl show" in dom0 will be helpful.
Excuse my poor english :)
Regards
ko0nz wrote:> hi Marc,
>
> # ifconfig Dom0
>
> eth0 Link encap:Ethernet HWaddr 00:0F:FE:6B:57:32
> inet addr:172.20.22.191 Bcast:172.20.22.255 Mask:255.255.255.0
> inet6 addr: fe80::20f:feff:fe6b:5732/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:24218 errors:0 dropped:0 overruns:0 frame:0
> TX packets:33136 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:2952113 (2.8 MiB) TX bytes:17840137 (17.0 MiB)
>
> 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:56113 errors:0 dropped:0 overruns:0 frame:0
> TX packets:56113 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:14474440 (13.8 MiB) TX bytes:14474440 (13.8 MiB)
>
> 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:24551 errors:0 dropped:0 overruns:0 frame:0
> TX packets:36349 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:3183587 (3.0 MiB) TX bytes:18200935 (17.3 MiB)
> Base address:0x1100 Memory:f0500000-f0520000
>
> 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:33136 errors:0 dropped:0 overruns:0 frame:0
> TX packets:24219 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:17840137 (17.0 MiB) TX bytes:2952183 (2.8 MiB)
>
> vif2.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:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:32 errors:0 dropped:9594 overruns:0 carrier:0
> collisions:0 txqueuelen:32
> RX bytes:0 (0.0 b) TX bytes:8368 (8.1 KiB)
>
> xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:13505 errors:0 dropped:0 overruns:0 frame:0
> TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:1947100 (1.8 MiB) TX bytes:168 (168.0 b)
>
>
>
> # dmesg Dom0
> vif4.0: no IPv6 routers present
> xenbr0: port 4(vif4.0) entering disabled state
> device vif4.0 left promiscuous mode
> audit(1184761578.260:10): dev=vif4.0 prom=0 old_prom=256 auid=4294967295
> xenbr0: port 4(vif4.0) entering disabled state
> device vif5.0 entered promiscuous mode
> audit(1184761578.670:11): dev=vif5.0 prom=256 old_prom=0 auid=4294967295
> xenbr0: port 4(vif5.0) entering learning state
> xenbr0: topology change detected, propagating
> xenbr0: port 4(vif5.0) entering forwarding state
> blkback: ring-ref 8, event-channel 6, protocol 1 (x86_32-abi)
> blkback: ring-ref 9, event-channel 7, protocol 1 (x86_32-abi)
> vif5.0: no IPv6 routers present
> xenbr0: port 4(vif5.0) entering disabled state
> device vif5.0 left promiscuous mode
> audit(1184761929.900:12): dev=vif5.0 prom=0 old_prom=256 auid=4294967295
> xenbr0: port 4(vif5.0) entering disabled state
>
> # ifconfig Dom2
> 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:6 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:504 (504.0 b) TX bytes:504 (504.0 b)
>
> # dmesg Dom2
>
> IA-32 Microcode Update Driver: v1.14a-xen <tigran@veritas.com>
> audit: initializing netlink socket (disabled)
> audit(1184761327.801:1): initialized
> VFS: Disk quotas dquot_6.5.1
> Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> Initializing Cryptographic API
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered (default)
> Floppy drive(s): fd0 is unknown type 15 (usb?), fd1 is unknown type 15
> (usb?)
> Failed to obtain physical IRQ 6
> floppy0: no floppy controllers found
> RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
> loop: loaded (max 8 devices)
> Xen virtual console successfully installed as tty1
> Event-channel device installed.
> netfront: Initialising virtual ethernet driver.
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> ide: Assuming 50MHz system bus speed for PIO modes; override with
> idebus=xx
> PNP: No PS/2 controller found. Probing ports directly.
> i8042.c: No controller found.
> mice: PS/2 mouse device common for all mice
> md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
> md: bitmap version 4.39
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> Using IPI No-Shortcut mode
> xen-vbd: registered block device major 3
> blkfront: hda1: barriers enabled
> blkfront: hda2: barriers enabled
> netfront: device eth0 has copying receive path.
> XENBUS: Device with no driver: device/console/0
> md: Autodetecting RAID arrays.
> md: autorun ...
> md: ... autorun DONE.
> EXT2-fs warning (device hda1): ext2_fill_super: mounting ext3
> filesystem as ext2
> VFS: Mounted root (ext2 filesystem) readonly.
> Freeing unused kernel memory: 192k freed
> serial_core: no version for "struct_module" found: kernel
tainted.
> Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
> Adding 262136k swap on /dev/hda2. Priority:-1 extents:1 across:262136k
> device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised:
> dm-devel@redhat.com
> NET: Registered protocol family 10
> lo: Disabled Privacy Extensions
> IPv6 over IPv4 tunneling driver
>
>
> thank in advance.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
hi Marc, my english is worse! :) it seems that with # ifconfig -a i can see a "eth4" but no "eth0" so i define an ip to eth4 and add default route to the gw and it works fine... i really don''t know why "eth0" diddn''t appear with th reboot of the host... thank you for your help. peace!> sorry, after reading the first post I belived that problem was on dom0''s > eth0 (my english is not as good as I want :) ), anyway the problem is in > your domU, and you can''t see eth0 when you make an ifconfig -a ( the > flag "a" is important). > > When you boot your domU you see domU''s eth0? Or the problem appears when > you restart the network init script? > > On the other hand, in your dom0 ifconfig shows vif2.0 (I supose that you > are only running one DomU), so... it''s quite strange, also it shows > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:32 errors:0 dropped:9594 overruns:0 carrier:0 > > it''s dropping packets, you know why? > > Probably if you post "xm create -c /etc/xen/oreon" output somebody > could help you, the output of a "brctl show" in dom0 will be helpful._______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Great! are you using udev? Search in udev config files and probably you will find key :) Regards, Marc ko0nz wrote:> hi Marc, > > my english is worse! :) > > it seems that with > # ifconfig -a > i can see a "eth4" but no "eth0" > so i define an ip to eth4 and add default route to the gw > and it works fine... > > i really don''t know why "eth0" diddn''t appear with th reboot of the > host... > > thank you for your help. > peace! > >> sorry, after reading the first post I belived that problem was on dom0''s >> eth0 (my english is not as good as I want :) ), anyway the problem is in >> your domU, and you can''t see eth0 when you make an ifconfig -a ( the >> flag "a" is important). >> >> When you boot your domU you see domU''s eth0? Or the problem appears when >> you restart the network init script? >> >> On the other hand, in your dom0 ifconfig shows vif2.0 (I supose that you >> are only running one DomU), so... it''s quite strange, also it shows >> >> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:32 errors:0 dropped:9594 overruns:0 carrier:0 >> >> it''s dropping packets, you know why? >> >> Probably if you post "xm create -c /etc/xen/oreon" output somebody >> could help you, the output of a "brctl show" in dom0 will be helpful._______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> are you using udev? Search in udev config files and probably you will > find key :)yes, i use udev. but it seems strange that eth0 disappeared and eth4 appereared... _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed Jul 18, 2007 at 17:51:31 +0200, ko0nz wrote:> yes, i use udev. > but it seems strange that eth0 > disappeared and eth4 appereared...Known issue. If you don''t specify a fixed MAC address with your xen guest then when your xen instance boots udev sees a "new" MAC address and gives it a new name - in the hope that the previously used one will reappear and be used for eth0. Two fixes; 1. Use a static MAC address. or 2. Remove the MAC address from : /etc/udev/rules.d/z25_persistent-net.rules Then make the file immutable .. Steve -- http://xen-tools.org/ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
hi Steve, thank you for your precisions. peace!> Known issue. > > If you don''t specify a fixed MAC address with your xen guest then > when your xen instance boots udev sees a "new" MAC address and gives > it a new name - in the hope that the previously used one will reappear > and be used for eth0. > > Two fixes; > > 1. Use a static MAC address. > > or > > 2. Remove the MAC address from : > /etc/udev/rules.d/z25_persistent-net.rules > Then make the file immutable .._______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users