Hi,
I''m running FC5 with the current 2.6.16-1.2080_FC5xen0 kernel in Dom0.
I
managed to set up several guests:
1) image-file based FC5 installed via xenguest-install.py. this one has
the eth0 device and a working network, but I don''t want to use the
image
file, but LVM volumes (which seems not possible with xenguest-install.py)
2) a centos 4.2 based on an image file I downloaded from a web site.
this one has no eth0 device in the guest, therefore networking doesn''t
work.
3) FC4 using LVM volumes, installed via "yum -c
http://people.redhat.com/~katzj/yum-xen.conf --installroot=/mnt -y
groupinstall Base". this one also has no eth0 device in the guest.
4) FC5 using LVM volumes, installed via "yum --installroot=/mnt/ -y
groupinstall base". this one also has no eth0 device in the guest.
in the latter case, ifconfig in Dom0 looks like this:
eth0 Link encap:Ethernet HWaddr 00:01:02:B5:F8:90
inet addr:192.168.5.10 Bcast:192.168.5.255 Mask:255.255.255.0
inet6 addr: fe80::201:2ff:feb5:f890/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:855425 errors:0 dropped:0 overruns:0 frame:0
TX packets:995199 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:568177794 (541.8 MiB) TX bytes:467490312 (445.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 MULTICAST MTU:1500 Metric:1
RX packets:855428 errors:0 dropped:0 overruns:1 frame:0
TX packets:995245 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:568177957 (541.8 MiB) TX bytes:468158849 (446.4 MiB)
Interrupt:9 Base address:0xe000
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 MULTICAST MTU:1500 Metric:1
RX packets:995199 errors:0 dropped:0 overruns:0 frame:0
TX packets:855427 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:467490312 (445.8 MiB) TX bytes:568177962 (541.8 MiB)
vif6.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:2715 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:359 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:41441 (40.4 KiB) TX bytes:468 (468.0 b)
domain config file:
name = "fc5"
memory = "128"
kernel="/boot/vmlinuz-2.6.16-1.2080_FC5xenU"
vif = [ ''mac=00:16:3e:4c:77:fa'' ]
disk = [ ''phy:/dev/vg_data/lv_fc5_root,sda1,w'',
''phy:/dev/vg_data/lv_fc5_data,sda2,w'',
''phy:/dev/vg_data/lv_fc5_swap,sda3,w'' ]
root="/dev/sda1"
extra = "ro selinux=0 3"
on startup, the FC5 domain doesn''t complain about missing kernel
modules
etc. I also installed the kernel-xenU-2.6.16-1.2080_FC5.i686.rpm in the
guest, but that didn''t help.
any idea what I have to do to get an eth0 in the guest ?
tnx in advance.
"modprobe xennet" solved the problem.> Hi, > > I''m running FC5 with the current 2.6.16-1.2080_FC5xen0 kernel in Dom0. I > managed to set up several guests: > > 1) image-file based FC5 installed via xenguest-install.py. this one has > the eth0 device and a working network, but I don''t want to use the image > file, but LVM volumes (which seems not possible with xenguest-install.py) > > 2) a centos 4.2 based on an image file I downloaded from a web site. > this one has no eth0 device in the guest, therefore networking doesn''t > work. > > 3) FC4 using LVM volumes, installed via "yum -c > http://people.redhat.com/~katzj/yum-xen.conf --installroot=/mnt -y > groupinstall Base". this one also has no eth0 device in the guest. > > 4) FC5 using LVM volumes, installed via "yum --installroot=/mnt/ -y > groupinstall base". this one also has no eth0 device in the guest. > > in the latter case, ifconfig in Dom0 looks like this: > > eth0 Link encap:Ethernet HWaddr 00:01:02:B5:F8:90 > inet addr:192.168.5.10 Bcast:192.168.5.255 Mask:255.255.255.0 > inet6 addr: fe80::201:2ff:feb5:f890/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:855425 errors:0 dropped:0 overruns:0 frame:0 > TX packets:995199 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:568177794 (541.8 MiB) TX bytes:467490312 (445.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 MULTICAST MTU:1500 Metric:1 > RX packets:855428 errors:0 dropped:0 overruns:1 frame:0 > TX packets:995245 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:568177957 (541.8 MiB) TX bytes:468158849 (446.4 MiB) > Interrupt:9 Base address:0xe000 > > 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 MULTICAST MTU:1500 Metric:1 > RX packets:995199 errors:0 dropped:0 overruns:0 frame:0 > TX packets:855427 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:467490312 (445.8 MiB) TX bytes:568177962 (541.8 MiB) > > vif6.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:2715 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:359 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:41441 (40.4 KiB) TX bytes:468 (468.0 b) > > domain config file: > > name = "fc5" > memory = "128" > kernel="/boot/vmlinuz-2.6.16-1.2080_FC5xenU" > vif = [ ''mac=00:16:3e:4c:77:fa'' ] > disk = [ ''phy:/dev/vg_data/lv_fc5_root,sda1,w'', > ''phy:/dev/vg_data/lv_fc5_data,sda2,w'', > ''phy:/dev/vg_data/lv_fc5_swap,sda3,w'' ] > root="/dev/sda1" > extra = "ro selinux=0 3" > > on startup, the FC5 domain doesn''t complain about missing kernel modules > etc. I also installed the kernel-xenU-2.6.16-1.2080_FC5.i686.rpm in the > guest, but that didn''t help. > > any idea what I have to do to get an eth0 in the guest ? > > tnx in advance. > > > -- > Fedora-xen mailing list > Fedora-xen@redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen >