WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] no pci support in xen-3.0.1 with gentoo?

To: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
Subject: Re: [Xen-users] no pci support in xen-3.0.1 with gentoo?
From: Bobber Cheng <bobber.cheng@xxxxxxxxx>
Date: Sat, 11 Feb 2006 20:35:03 +0800
Cc: "Kneschke.Lars" <l.kneschke@xxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 11 Feb 2006 12:46:58 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <43EDD72C.1040009@xxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <907625E08839C4409CE5768403633E0B0EABEA@xxxxxxxxxxxxxxxxx> <43EDD72C.1040009@xxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5 (Windows/20051201)
Bobber Cheng wrote:
Hi, Mats,

Thanks for your help.

By default, no network interfaces are configured. When I added following line in my xen config file /etc/xen/rhel4
vif = [ '' ], i got guest network interface in domain 0:

sipxpbx ~ # ifconfig
eth0      Link encap:Ethernet  HWaddr 00:09:6B:E0:9C:0B
inet addr:192.168.18.180 Bcast:192.168.18.255 Mask:255.255.255.0
         inet6 addr: fe80::209:6bff:fee0:9c0b/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:6578 errors:0 dropped:0 overruns:0 frame:0
         TX packets:3228 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:789651 (771.1 Kb)  TX bytes:425744 (415.7 Kb)

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:8 errors:0 dropped:0 overruns:0 frame:0
         TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:696 (696.0 b)  TX bytes:696 (696.0 b)

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:6580 errors:0 dropped:0 overruns:0 frame:0
         TX packets:3242 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:791451 (772.9 Kb)  TX bytes:427812 (417.7 Kb)

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:3249 errors:0 dropped:0 overruns:0 frame:0
         TX packets:6616 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:429414 (419.3 Kb)  TX bytes:793331 (774.7 Kb)

vif5.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:848 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:3874 errors:0 dropped:0 overruns:0 frame:0
         TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:460931 (450.1 Kb)  TX bytes:378 (378.0 b)

But in my guest rhel, i don't find network interface:
[root@genxen ~]# ifconfig
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)


I know the reason. ifconfig could not find unactive network interface. When use iptables command ip. i found eth0 ;-)
[root@genxen ~]# ip a
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
   link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
   inet 127.0.0.1/8 scope host lo
   inet6 ::1/128 scope host
      valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
   link/ether 00:16:3e:64:ab:7b brd ff:ff:ff:ff:ff:ff
3: sit0: <NOARP> mtu 1480 qdisc noop
   link/sit 0.0.0.0 brd 0.0.0.0

Could you give me any hint?

Bests,
Bobber


Petersson, Mats wrote:
-----Original Message-----
From: Bobber Cheng [mailto:bobber.cheng@xxxxxxxxx] Sent: 10 February 2006 12:45
To: Petersson, Mats
Cc: Kneschke.Lars; xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] no pci support in xen-3.0.1 with gentoo?

Petersson, Mats wrote:
-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Bobber Cheng
Sent: 10 February 2006 11:27
To: Kneschke.Lars
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] no pci support in xen-3.0.1 with gentoo?

Kneschke.Lars wrote:
Bobber Cheng <bobber.cheng@xxxxxxxxx> schrieb:
Any suggestion?
The virtual machine has no PCI devices, until you assign some PCI slots to this machine.
And the assignment of PCI slots is also not working in 3.0.1
So you mean I could not use pci devices such as ethernet
device with
xen 3.0.1? if it's true, that's too bad cause a Linux
without network
function is nothing.
You can certainly get network functionality in DomU - you
just can't
get directly to the actual physical PCI device.

Generally, the DomU is linked to the rest of the world through a "bridge" device - which is just a piece of software that
transfers the
data to Dom0, where Dom0 decides whether it's going to send
it to the
Ethernet card or just transfer it to another domain - or perhaps answer itself (in case you ping dom0 for instance).

Could you tell me how to use bridge with xen?

I guess the best way to describe it is here: http://tx.downloads.xensource.com/downloads/docs/user/

--
Mats


_______________________________________________
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

<Prev in Thread] Current Thread [Next in Thread>