Hi, I installed xen-3.0.1 in my gentoo with xen-sources-2.6.12.6-r2. My guest os is rhel4. I found guest os has no pci. I found some message when i boot guest rhel: .... NET: Registered protocol family 16 ACPI: Subsystem revision 20050309 ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay xen_mem: Initialising balloon driver. SCSI subsystem initialized Linux Kernel Card Services options: [pci] [cardbus] usbcore: registered new driver usbfs usbcore: registered new driver hub PCI: Using ACPI for IRQ routing PCI: If a device doesn''t work, try "pci=routeirq". If it helps, post a report PCI: System does not support PCI PCI: System does not support PCI ..... my config file is: kernel = "/boot/vmlinuz-2.6.12.6-xen-r2-U" ramdisk = "/boot/initrd-2.6.12.6-xen-r2.img" memory = 128 name = "rhel4" ip = "192.168.18.181" disk = [''file:/mnt/home/xenstore/rhel4.img,sda1,w''] root = "/dev/sda1" extra = "ro" Any suggestion? Bests, Bobber _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Kneschke.Lars
2006-Feb-10 11:15 UTC
Re: [Xen-users] no pci support in xen-3.0.1 with gentoo?
Bobber Cheng <bobber.cheng@cystar.cn> 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. -- Lars Kneschke Metaways Infosystems GmbH Pickhuben 4 20457 Hamburg Germany eGroupWare Training & Support ==> http://www.egroupware-support.de E-Mail: mailto:l.kneschke@metaways.de Web: http://www.metaways.de Tel: +49 (0)40 317031-21 Fax: +49 (0)40 317031-81 Mobile: +49 (0)175 9304324 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Bobber Cheng
2006-Feb-10 11:26 UTC
Re: [Xen-users] no pci support in xen-3.0.1 with gentoo?
Kneschke.Lars wrote:> Bobber Cheng <bobber.cheng@cystar.cn> 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.1So 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. Bests, Bobber _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Bobber Cheng
2006-Feb-10 11:38 UTC
Re: [Xen-users] no pci support in xen-3.0.1 with gentoo?
Mathias Diehl wrote:> Hi Bobber, > > as long as you''re using domU this is quite normal that there''s no pci device transfered to your guest. In order to have access to pci devices yo have to use a priviledged kernel (like the dom0 one), hide the pci devices from your dom0 and allocate them to your guest... > >I used privilege kernel on dom0.> I''m not sure if it''s already available with 3.0.1 but I''ve seen some posts on the devel list that it''s supposed to be back. However following Ian''s advise from the user list it''ll take some time to clean the code so it''s better to wait for 3.0.2 to use this feature. > > cheers, > > Mat > > -----Original Message----- > Sent: Freitag 10.02.06 19:02:28 > Subject: [Xen-users] no pci support in xen-3.0.1 with gentoo? > > >> Hi, >> >> I installed xen-3.0.1 in my gentoo with xen-sources-2.6.12.6-r2. My >> guest os is rhel4. I found guest os has no pci. I found some message >> when i boot guest rhel: >> .... >> NET: Registered protocol family 16 >> ACPI: Subsystem revision 20050309 >> ACPI: Interpreter disabled. >> Linux Plug and Play Support v0.97 (c) Adam Belay >> xen_mem: Initialising balloon driver. >> SCSI subsystem initialized >> Linux Kernel Card Services >> options: [pci] [cardbus] >> usbcore: registered new driver usbfs >> usbcore: registered new driver hub >> PCI: Using ACPI for IRQ routing >> PCI: If a device doesn''t work, try "pci=routeirq". If it helps, post a >> report >> PCI: System does not support PCI >> PCI: System does not support PCI >> ..... >> >> my config file is: >> >> kernel = "/boot/vmlinuz-2.6.12.6-xen-r2-U" >> ramdisk = "/boot/initrd-2.6.12.6-xen-r2.img" >> memory = 128 >> name = "rhel4" >> ip = "192.168.18.181" >> disk = [''file:/mnt/home/xenstore/rhel4.img,sda1,w''] >> root = "/dev/sda1" >> extra = "ro" >> >> Any suggestion? >> >> Bests, >> Bobber >> >> >> _______________________________________________ >> 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 > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Petersson, Mats
2006-Feb-10 11:45 UTC
RE: [Xen-users] no pci support in xen-3.0.1 with gentoo?
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > Bobber Cheng > Sent: 10 February 2006 11:27 > To: Kneschke.Lars > Cc: xen-users@lists.xensource.com > Subject: Re: [Xen-users] no pci support in xen-3.0.1 with gentoo? > > Kneschke.Lars wrote: > > Bobber Cheng <bobber.cheng@cystar.cn> 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). But if you really want to have direct access to the real hardware from a DomU, then you need to use either Xen 2.0.x, or wait for the PCI assignment feature in 3.0 to appear - I did see some patches a few days ago, but I''m not sure if they are applied to unstable or not. There were several comments and a bit of toing and froing on the patch, IIRC. -- Mats> > Bests, > Bobber > > _______________________________________________ > 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
Bobber Cheng
2006-Feb-10 12:45 UTC
Re: [Xen-users] no pci support in xen-3.0.1 with gentoo?
Petersson, Mats wrote:>> -----Original Message----- >> From: xen-users-bounces@lists.xensource.com >> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of >> Bobber Cheng >> Sent: 10 February 2006 11:27 >> To: Kneschke.Lars >> Cc: xen-users@lists.xensource.com >> Subject: Re: [Xen-users] no pci support in xen-3.0.1 with gentoo? >> >> Kneschke.Lars wrote: >> >>> Bobber Cheng <bobber.cheng@cystar.cn> 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?> But if you really want to have direct access to the real hardware from a > DomU, then you need to use either Xen 2.0.x, or wait for the PCI > assignment feature in 3.0 to appear - I did see some patches a few days > ago, but I''m not sure if they are applied to unstable or not. There were > several comments and a bit of toing and froing on the patch, IIRC. > > -- > Mats > >> Bests, >> Bobber >> >> _______________________________________________ >> 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
Mathias Diehl
2006-Feb-10 13:36 UTC
Re:[Xen-users] no pci support in xen-3.0.1 with gentoo?
Hi Bobber, as long as you''re using domU this is quite normal that there''s no pci device transfered to your guest. In order to have access to pci devices yo have to use a priviledged kernel (like the dom0 one), hide the pci devices from your dom0 and allocate them to your guest... I''m not sure if it''s already available with 3.0.1 but I''ve seen some posts on the devel list that it''s supposed to be back. However following Ian''s advise from the user list it''ll take some time to clean the code so it''s better to wait for 3.0.2 to use this feature. cheers, Mat -----Original Message----- Sent: Freitag 10.02.06 19:02:28 Subject: [Xen-users] no pci support in xen-3.0.1 with gentoo?>Hi, > >I installed xen-3.0.1 in my gentoo with xen-sources-2.6.12.6-r2. My >guest os is rhel4. I found guest os has no pci. I found some message >when i boot guest rhel: >.... >NET: Registered protocol family 16 >ACPI: Subsystem revision 20050309 >ACPI: Interpreter disabled. >Linux Plug and Play Support v0.97 (c) Adam Belay >xen_mem: Initialising balloon driver. >SCSI subsystem initialized >Linux Kernel Card Services > options: [pci] [cardbus] >usbcore: registered new driver usbfs >usbcore: registered new driver hub >PCI: Using ACPI for IRQ routing >PCI: If a device doesn''t work, try "pci=routeirq". If it helps, post a >report >PCI: System does not support PCI >PCI: System does not support PCI >..... > >my config file is: > >kernel = "/boot/vmlinuz-2.6.12.6-xen-r2-U" >ramdisk = "/boot/initrd-2.6.12.6-xen-r2.img" >memory = 128 >name = "rhel4" >ip = "192.168.18.181" >disk = [''file:/mnt/home/xenstore/rhel4.img,sda1,w''] >root = "/dev/sda1" >extra = "ro" > >Any suggestion? > >Bests, >Bobber > > >_______________________________________________ >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
Mathias Diehl
2006-Feb-10 14:15 UTC
Re:Re: [Xen-users] no pci support in xen-3.0.1 with gentoo?
>> >> as long as you''re using domU this is quite normal that there''s no pci device transfered to your guest. In order to have access to pci devices yo have to use a priviledged kernel (like the dom0 one), hide the pci devices from your dom0 and allocate them to your guest... >> >> >I used privilege kernel on dom0.yeah - but to use oci within a domU you need also to a priv kernel for your domU ;-) Or you follow the scenario mentioned by Mats keeping all pci on dom0 and do your networking using bridges/routes cheers, Mat _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Petersson, Mats
2006-Feb-10 14:19 UTC
RE: [Xen-users] no pci support in xen-3.0.1 with gentoo?
> -----Original Message----- > From: Bobber Cheng [mailto:bobber.cheng@cystar.cn] > Sent: 10 February 2006 12:45 > To: Petersson, Mats > Cc: Kneschke.Lars; xen-users@lists.xensource.com > Subject: Re: [Xen-users] no pci support in xen-3.0.1 with gentoo? > > Petersson, Mats wrote: > >> -----Original Message----- > >> From: xen-users-bounces@lists.xensource.com > >> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Bobber > >> Cheng > >> Sent: 10 February 2006 11:27 > >> To: Kneschke.Lars > >> Cc: xen-users@lists.xensource.com > >> Subject: Re: [Xen-users] no pci support in xen-3.0.1 with gentoo? > >> > >> Kneschke.Lars wrote: > >> > >>> Bobber Cheng <bobber.cheng@cystar.cn> 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@lists.xensource.com http://lists.xensource.com/xen-users
Bobber Cheng
2006-Feb-11 12:23 UTC
Re: [Xen-users] no pci support in xen-3.0.1 with gentoo?
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)
Could you give me any hint?
Bests,
Bobber
Petersson, Mats wrote:>
>
>
>> -----Original Message-----
>> From: Bobber Cheng [mailto:bobber.cheng@cystar.cn]
>> Sent: 10 February 2006 12:45
>> To: Petersson, Mats
>> Cc: Kneschke.Lars; xen-users@lists.xensource.com
>> Subject: Re: [Xen-users] no pci support in xen-3.0.1 with gentoo?
>>
>> Petersson, Mats wrote:
>>
>>>> -----Original Message-----
>>>> From: xen-users-bounces@lists.xensource.com
>>>> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of
Bobber
>>>> Cheng
>>>> Sent: 10 February 2006 11:27
>>>> To: Kneschke.Lars
>>>> Cc: xen-users@lists.xensource.com
>>>> Subject: Re: [Xen-users] no pci support in xen-3.0.1 with
gentoo?
>>>>
>>>> Kneschke.Lars wrote:
>>>>
>>>>
>>>>> Bobber Cheng <bobber.cheng@cystar.cn> 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@lists.xensource.com
> http://lists.xensource.com/xen-users
>
>
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Bobber Cheng
2006-Feb-11 12:35 UTC
Re: [Xen-users] no pci support in xen-3.0.1 with gentoo?
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@cystar.cn] Sent: 10 February >>> 2006 12:45 >>> To: Petersson, Mats >>> Cc: Kneschke.Lars; xen-users@lists.xensource.com >>> Subject: Re: [Xen-users] no pci support in xen-3.0.1 with gentoo? >>> >>> Petersson, Mats wrote: >>> >>>>> -----Original Message----- >>>>> From: xen-users-bounces@lists.xensource.com >>>>> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Bobber >>>>> Cheng >>>>> Sent: 10 February 2006 11:27 >>>>> To: Kneschke.Lars >>>>> Cc: xen-users@lists.xensource.com >>>>> Subject: Re: [Xen-users] no pci support in xen-3.0.1 with gentoo? >>>>> >>>>> Kneschke.Lars wrote: >>>>> >>>>>> Bobber Cheng <bobber.cheng@cystar.cn> 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@lists.xensource.com >> http://lists.xensource.com/xen-users >> >> >> > > > _______________________________________________ > 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
Should a 3.0.1 domU work on a 3.0.0 hypervisor? I''m having heaps of trouble trying to make gentoo linux-2.6.12.6-xen-r2 work, but of course it could be something else. My hypervisor is 3.0.0 (x86_64). I hesitate to upgrade the hypervisor because it works great in every other regard, and I would have to take the whole machine down to upgrade it. Cheers, Dan. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello Dan, You might get a better response if you started a new thread instead of replying to an existing one that is not really related. Best Regards, David On Saturday 11 February 2006 06:33 am, Daniel Goertzen wrote:> Should a 3.0.1 domU work on a 3.0.0 hypervisor? > > I''m having heaps of trouble trying to make gentoo linux-2.6.12.6-xen-r2 > work, but of course it could be something else. My hypervisor is 3.0.0 > (x86_64). I hesitate to upgrade the hypervisor because it works great > in every other regard, and I would have to take the whole machine down > to upgrade it. > > Cheers, > Dan. > > > > _______________________________________________ > 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
> I''m having heaps of trouble trying to make gentoo > linux-2.6.12.6-xen-r2 work, but of course it could be something else. > My hypervisor is 3.0.0 (x86_64). I hesitate to upgrade the hypervisor > because it works great in every other regard, and I would have to take > the whole machine down to upgrade it.I''m having heaps of trouble getting a gentoo XenU to even start up! Care to share what your problems are so that I can at least compare notes? Ed W _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
It turns out the linux-2.6.12.6-xen kernel works fine where linux-2.6.12.6-xen-r2 crashes instantly. (config attached) Again, I am using the 3.0.0 hypervisor (x86_64), and I still don''t know wether there is something broken in the r2 kernel or wether there is 3.0.0 -> 3.0.1 incompatibility. I''m still hoping for a compatibility hint on this list before I start mucking with the hypervisor... In gentoo, linux-2.6.12.6-xen is the kernel that is associated with xen-3.0.0. linux-2.6.12.6-xen-r2 is associated with xen-3.0.1. Dan. Ed Wildgoose wrote:> I built one system using the default .config and the Xen0 kernel died > on boot fairly late in the process (kernel panic). > > I have now built a new system (again using 2.6.12-xen-r2) and this was > with a custom kernel, but although this boots ok, I haven''t yet got a > XenU kernel to start up. The whole thing dies instantly with Xend > saying "sig 11". Perhaps this is the XenU kernel, perhaps something > else... Can''t see any evidence that the XenU kernel even started to > boot though - but I have never seen this thing work so I don''t know > what is supposed to happen... > > Interested to hear how you get on (please post your .config files if > you get something working!) > > Good luck > > Ed W > > > Daniel Goertzen wrote: > >> Hi Ed. Assuming there are no compatibility issues between 3.0.0 and >> 3.0.1, most likely my problem is bad kernel configuration. My >> kernels crash instantly with nothing printing on the screen. >> >> As I mentioned, I''ve had no luck with linux-2.6.12.6-xen-r2. I am >> going to try the older linux-2.6.12.6-xen tree to see if that works >> better with my system. >> >> I remember the default config for linux-2.6.12.6-xen was weak, and >> the default config for linux-2.6.12.6-xen-r2 looks different, and >> might be producing crashing kernels. >> >> Will keep you updated. >> Dan. >> >> Ed W wrote: >> >>> >>>> I''m having heaps of trouble trying to make gentoo >>>> linux-2.6.12.6-xen-r2 work, but of course it could be something >>>> else. My hypervisor is 3.0.0 (x86_64). I hesitate to upgrade the >>>> hypervisor because it works great in every other regard, and I >>>> would have to take the whole machine down to upgrade it. >>> >>> >>> >>> >>> >>> I''m having heaps of trouble getting a gentoo XenU to even start up! >>> Care to share what your problems are so that I can at least compare >>> notes? >>> >>> Ed W >>> >>> >> > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
The 2.6.12 kernel has security problems so I''m using the mercurial linux tree and xen-unstable. Works fine on gentoo; I''ll wait for portage to catch up, but it does seem that xen is not high priority on gentoo compared with, say, suse, who are tracking unstable too. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users