* [Fwd: bridging problem with Xen 2.0.1]
@ 2004-11-29 10:40 Pásztor Lénárd Zoltán
2004-11-29 11:58 ` kaz
` (2 more replies)
0 siblings, 3 replies; 16+ messages in thread
From: Pásztor Lénárd Zoltán @ 2004-11-29 10:40 UTC (permalink / raw)
To: xen-devel
[-- Attachment #1: Type: text/plain, Size: 349 bytes --]
Hello,
I sent this mail (see attachement) to the
zen-devel@lists.sourceforge.net address,
but there is no answer, and my email does not exist in the mail archive.
What did I wrong?
(sorry for my english...)
--
Pásztor Lénárd Zoltán
rendszergazda
Wonderline Rt.
Telefon: (+36-1) 272.0242
Fax: (+36-1) 272.0252
Honlap: www.wonderline.hu
[-- Attachment #2: bridging problem with Xen 2.0.1 --]
[-- Type: message/rfc822, Size: 10467 bytes --]
From: "Pásztor Lénárd Zoltán" <lenard.pasztor@wonderline.hu>
To: mailto:xen-devel@lists.sourceforge.net
Subject: bridging problem with Xen 2.0.1
Date: Fri, 26 Nov 2004 13:47:57 +0100
Message-ID: <41A725FD.7030008@wonderline.hu>
Hi All!
I need to setup a virtual host with 2 virtual ethernet interface on
separated bridge.
When the domain1 starts the second ethernet adapter does not connect to the
domain0's second bridge.
When I try to add the interface manually I got an error message.
Can help somebody to me to solve this problem?
Domain0:
Debinan/GNU linux (sarge)
Xen 2.0.1 (with recompiled 2.6.9 kernel)
Domain1:
Debian/GNU linux (sarge)
Xen unmodified vmlinuz-2.6.9-xenU kernel
(when I compile unprivileged kernel I got the following message from
build process:
CC arch/xen/i386/mm/ioremap.o
arch/xen/i386/mm/ioremap.c: In function `__ioremap':
arch/xen/i386/mm/ioremap.c:144: error:
`isa_bus_to_virt_needs_PRIVILEGED_BUILD' undeclared (first use in this
function)
arch/xen/i386/mm/ioremap.c:144: error: (Each undeclared identifier is
reported only once
arch/xen/i386/mm/ioremap.c:144: error: for each function it appears in.)
arch/xen/i386/mm/ioremap.c: In function `bt_ioremap':
arch/xen/i386/mm/ioremap.c:280: error:
`isa_bus_to_virt_needs_PRIVILEGED_BUILD' undeclared (first use in this
function)
make[1]: *** [arch/xen/i386/mm/ioremap.o] Error 1
make: *** [arch/xen/i386/mm] Error 2
)
Below the commands how I test it:
domain0:~# ifconfig xen-br0 10.10.254.254 netmask 255.255.0.0 broadcast
10.10.255.255 up
domain0:~# ifconfig xen-br1 10.11.254.254 netmask 255.255.0.0 broadcast
10.11.255.255 up
domain0:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:30:4F:13:DF:DD
inet addr:10.3.1.45 Bcast:10.3.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4636 errors:0 dropped:0 overruns:0 frame:0
TX packets:3055 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:421198 (411.3 KiB) TX bytes:565986 (552.7 KiB)
Interrupt:9 Base address:0xd400
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:3243 errors:0 dropped:0 overruns:0 frame:0
TX packets:3243 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:222710 (217.4 KiB) TX bytes:222710 (217.4 KiB)
xen-br0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:10.10.254.254 Bcast:10.10.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:88 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:8675 (8.4 KiB) TX bytes:0 (0.0 b)
xen-br1 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:10.11.254.254 Bcast:10.11.255.255 Mask:255.255.0.0
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:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
domain0:~# brctl show
bridge name bridge id STP enabled interfaces
xen-br0 8000.000000000000 no can't get port
info: Function not implemented
xen-br1 8000.000000000000 no can't get port
info: Function not implemented
domain0:~# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
10.3.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
10.10.0.0 0.0.0.0 255.255.0.0 U 0 0 0
xen-br0
10.11.0.0 0.0.0.0 255.255.0.0 U 0 0 0
xen-br1
0.0.0.0 10.3.0.2 0.0.0.0 UG 0 0 0 eth0
Now starting a domain1 with this nic config:
nics = 2
vif = [ 'mac=aa:00:00:00:00:11, bridge=xen-br0',
'mac=bb:00:00:00:00:22, bridge=xen-br1']
domain1:~$ ifconfig
eth0 Link encap:Ethernet HWaddr AA:00:00:00:00:11
inet addr:10.10.10.1 Bcast:10.10.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:42 (42.0 b) TX bytes:116 (116.0 b)
eth1 Link encap:Ethernet HWaddr BB:00:00:00:00:22
inet addr:10.11.10.1 Bcast:10.11.255.25 Mask:255.255.0.0
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:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
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)
domain1:~$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
10.10.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
10.11.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1
0.0.0.0 10.10.254.254 0.0.0.0 UG 0 0 0 eth0
domain0:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:30:4F:13:DF:DD
inet addr:10.3.1.45 Bcast:10.3.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5115 errors:0 dropped:0 overruns:0 frame:0
TX packets:3426 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:461687 (450.8 KiB) TX bytes:626631 (611.9 KiB)
Interrupt:9 Base address:0xd400
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:4524 errors:0 dropped:0 overruns:0 frame:0
TX packets:4524 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:299113 (292.1 KiB) TX bytes:299113 (292.1 KiB)
vif4.0 Link encap:Ethernet HWaddr AA:00:01:00:00:11
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:21 errors:0 dropped:0 overruns:0 frame:0
TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1346 (1.3 KiB) TX bytes:1062 (1.0 KiB)
vif4.1 Link encap:Ethernet HWaddr BB:00:01:00:00:22
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:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
xen-br0 Link encap:Ethernet HWaddr AA:00:01:00:00:11
inet addr:10.10.254.254 Bcast:10.10.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:109 errors:0 dropped:0 overruns:0 frame:0
TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:9727 (9.4 KiB) TX bytes:1062 (1.0 KiB)
xen-br1 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:10.11.254.254 Bcast:10.11.255.255 Mask:255.255.0.0
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:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
domain0:~# brctl show
bridge name bridge id STP enabled interfaces
xen-br0 8000.aa0001000011 no vif4.0
xen-br1 8000.000000000000 no can't get port
info: Function not implemented
Why vif4.1 not in xen-br1?
Let's add it manually...
domain0:~# brctl addif vif4.1 xen-br1
can't add xen-br1 to bridge vif4.1: Operation not supported
It gives error message :( What is the problem?
Testing vif4.0...
domain0:~# ping 10.10.10.1
PING 10.10.10.1 (10.10.10.1) 56(84) bytes of data.
64 bytes from 10.10.10.1: icmp_seq=1 ttl=64 time=0.399 ms
64 bytes from 10.10.10.1: icmp_seq=2 ttl=64 time=0.278 ms
--- 10.10.10.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1005ms
rtt min/avg/max/mdev = 0.278/0.338/0.399/0.063 ms
domain1:~$ ping 10.10.254.254
PING 10.10.254.254 (10.10.254.254) 56(84) bytes of data.
64 bytes from 10.10.254.254: icmp_seq=1 ttl=64 time=2.47 ms
64 bytes from 10.10.254.254: icmp_seq=2 ttl=64 time=0.364 ms
--- 10.10.254.254 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1006ms
rtt min/avg/max/mdev = 0.364/1.417/2.470/1.053 ms
It's OK.
Testing vif4.1...
domain1:~$ ping 10.11.254.254
PING 10.11.254.254 (10.11.254.254) 56(84) bytes of data.
--- 10.11.254.254 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
domain0:~# tcpdump -i vif4.1 -n
tcpdump: WARNING: vif4.1: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vif4.1, link-type EN10MB (Ethernet), capture size 96 bytes
11:11:49.011029 arp who-has 10.11.254.254 tell 10.11.10.1
11:11:50.010942 arp who-has 10.11.254.254 tell 10.11.10.1
11:11:51.010952 arp who-has 10.11.254.254 tell 10.11.10.1
3 packets captured
3 packets received by filter
0 packets dropped by kernel
So, the vif4.1 interface seems to be OK.
Other questions:
- When goes Xen 2.x to debian system?
- How can I define the nic name (vif) before I start a virtual machine?
udv,
Lenard
--
Pásztor Lénárd Zoltán
rendszergazda
Wonderline Rt.
Telefon: (+36-1) 272.0242
Fax: (+36-1) 272.0252
Honlap: www.wonderline.hu
^ permalink raw reply [flat|nested] 16+ messages in thread* Re: [Fwd: bridging problem with Xen 2.0.1]
2004-11-29 10:40 [Fwd: bridging problem with Xen 2.0.1] Pásztor Lénárd Zoltán
@ 2004-11-29 11:58 ` kaz
2004-11-29 14:12 ` Nuutti Kotivuori
2004-11-29 14:47 ` Xen 2.0 Debian packages Jérôme Petazzoni
2004-11-29 12:18 ` [Fwd: bridging problem with Xen 2.0.1] Keir Fraser
2004-11-29 13:08 ` Mike Wray
2 siblings, 2 replies; 16+ messages in thread
From: kaz @ 2004-11-29 11:58 UTC (permalink / raw)
To: lenard.pasztor; +Cc: xen-devel
Lenard wrote:
>
> - When goes Xen 2.x to debian system?
Try unofficial xen-2.0.1 deb packages at; http://www.terrabox.com/debian/
/etc/apt/sources.lists
deb http://www.terrabox.com/debian/ binary/
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Fwd: bridging problem with Xen 2.0.1]
2004-11-29 11:58 ` kaz
@ 2004-11-29 14:12 ` Nuutti Kotivuori
2004-11-29 15:41 ` kaz
2004-11-29 14:47 ` Xen 2.0 Debian packages Jérôme Petazzoni
1 sibling, 1 reply; 16+ messages in thread
From: Nuutti Kotivuori @ 2004-11-29 14:12 UTC (permalink / raw)
To: xen-devel
kaz wrote:
> Lenard wrote:
>>
>> - When goes Xen 2.x to debian system?
>
> Try unofficial xen-2.0.1 deb packages at;
> http://www.terrabox.com/debian/ /etc/apt/sources.lists deb
> http://www.terrabox.com/debian/ binary/
The apt repository there seems to house the 2.0.1 .deb packages, but
the Packages.gz file doesn't seem to mention them at all. Hence no
apt-getting.
I am wondering if this is intentional.
-- Naked
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Re: [Fwd: bridging problem with Xen 2.0.1]
2004-11-29 14:12 ` Nuutti Kotivuori
@ 2004-11-29 15:41 ` kaz
2004-11-29 15:47 ` Brian Wolfe
0 siblings, 1 reply; 16+ messages in thread
From: kaz @ 2004-11-29 15:41 UTC (permalink / raw)
To: Nuutti Kotivuori; +Cc: xen-devel
Nuutti Kotivuori wrote:
>
>>http://www.terrabox.com/debian/ binary/
>
> The apt repository there seems to house the 2.0.1 .deb packages, but
> the Packages.gz file doesn't seem to mention them at all. Hence no
> apt-getting.
>
> I am wondering if this is intentional.
It was me who packaged xen-2.0.1 into .deb and handed over them to Brian,
an owner of terrabox.com. So not sure, any intention being involved or not.
Ok, I will setup an apt-get'able repository somewhere anyway and let you
know the URI. Just wait for a while.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Re: [Fwd: bridging problem with Xen 2.0.1]
2004-11-29 15:41 ` kaz
@ 2004-11-29 15:47 ` Brian Wolfe
2004-11-29 15:56 ` kaz
0 siblings, 1 reply; 16+ messages in thread
From: Brian Wolfe @ 2004-11-29 15:47 UTC (permalink / raw)
To: kaz; +Cc: Nuutti Kotivuori, Xen Devel Mailing List
It was unintentional. I just verified the packages sources Friday and
forgot to run the update on Packages.gz. *sigh*
On Tue, 2004-11-30 at 00:41 +0900, kaz wrote:
> Nuutti Kotivuori wrote:
> >
> >>http://www.terrabox.com/debian/ binary/
> >
> > The apt repository there seems to house the 2.0.1 .deb packages, but
> > the Packages.gz file doesn't seem to mention them at all. Hence no
> > apt-getting.
> >
> > I am wondering if this is intentional.
>
> It was me who packaged xen-2.0.1 into .deb and handed over them to Brian,
> an owner of terrabox.com. So not sure, any intention being involved or not.
> Ok, I will setup an apt-get'able repository somewhere anyway and let you
> know the URI. Just wait for a while.
>
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
--
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Re: [Fwd: bridging problem with Xen 2.0.1]
2004-11-29 15:47 ` Brian Wolfe
@ 2004-11-29 15:56 ` kaz
2004-11-29 16:20 ` Brian Wolfe
0 siblings, 1 reply; 16+ messages in thread
From: kaz @ 2004-11-29 15:56 UTC (permalink / raw)
To: brianw; +Cc: Nuutti Kotivuori, Xen Devel Mailing List
Brian Wolfe wrote:
> It was unintentional. I just verified the packages sources Friday and
> forgot to run the update on Packages.gz. *sigh*
Aha, ok confirmed updated Packages.gz.
Could you please kindly update source .deb packages at;
http://www.terrabox.com/debian/source/
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Re: [Fwd: bridging problem with Xen 2.0.1]
2004-11-29 15:56 ` kaz
@ 2004-11-29 16:20 ` Brian Wolfe
2004-11-29 16:55 ` Nuutti Kotivuori
0 siblings, 1 reply; 16+ messages in thread
From: Brian Wolfe @ 2004-11-29 16:20 UTC (permalink / raw)
To: Xen Devel Mailing List
Done. Kind of burnt out this morning. 8-P
On Tue, 2004-11-30 at 00:56 +0900, kaz wrote:
> Brian Wolfe wrote:
> > It was unintentional. I just verified the packages sources Friday and
> > forgot to run the update on Packages.gz. *sigh*
>
> Aha, ok confirmed updated Packages.gz.
> Could you please kindly update source .deb packages at;
> http://www.terrabox.com/debian/source/
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
--
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Fwd: bridging problem with Xen 2.0.1]
2004-11-29 16:20 ` Brian Wolfe
@ 2004-11-29 16:55 ` Nuutti Kotivuori
2004-11-29 17:29 ` Brian Wolfe
0 siblings, 1 reply; 16+ messages in thread
From: Nuutti Kotivuori @ 2004-11-29 16:55 UTC (permalink / raw)
To: xen-devel
Brian Wolfe wrote:
> Done. Kind of burnt out this morning. 8-P
In that case, sorry to bother once more :-)
The url:
http://www.terrabox.com/debian/binary/Packages.gz
still contains the old package listings - no 2.0.1.
The url
http://www.terrabox.com/debian/binary/Packages
contains a *gzipped* version of Packages, which does have 2.0.1.
So I guess the Packages file should be renamed as Packages.gz,
overwriting the old file, and a decompressed version of that should be
created as Packages.
Hang in there :-)
-- Naked
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Re: [Fwd: bridging problem with Xen 2.0.1]
2004-11-29 16:55 ` Nuutti Kotivuori
@ 2004-11-29 17:29 ` Brian Wolfe
0 siblings, 0 replies; 16+ messages in thread
From: Brian Wolfe @ 2004-11-29 17:29 UTC (permalink / raw)
To: Nuutti Kotivuori; +Cc: Xen Devel Mailing List
*hangs a big "DITZ" sign on his neck*
8-P
Mv'd it. Please dont feel bad for pointing out fixes I need to do to
anything public. :)
I'm hoping to have more time to work on the xen packages in the next
week or two.
Gotta go fix my auto-builder and get it linked into the xen anounce
list.
On Mon, 2004-11-29 at 18:55 +0200, Nuutti Kotivuori wrote:
> Brian Wolfe wrote:
> > Done. Kind of burnt out this morning. 8-P
>
> In that case, sorry to bother once more :-)
>
> The url:
>
> http://www.terrabox.com/debian/binary/Packages.gz
>
> still contains the old package listings - no 2.0.1.
>
> The url
>
> http://www.terrabox.com/debian/binary/Packages
>
> contains a *gzipped* version of Packages, which does have 2.0.1.
>
> So I guess the Packages file should be renamed as Packages.gz,
> overwriting the old file, and a decompressed version of that should be
> created as Packages.
>
> Hang in there :-)
>
> -- Naked
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
--
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
^ permalink raw reply [flat|nested] 16+ messages in thread
* Xen 2.0 Debian packages
2004-11-29 11:58 ` kaz
2004-11-29 14:12 ` Nuutti Kotivuori
@ 2004-11-29 14:47 ` Jérôme Petazzoni
2004-11-30 1:12 ` Brian Wolfe
1 sibling, 1 reply; 16+ messages in thread
From: Jérôme Petazzoni @ 2004-11-29 14:47 UTC (permalink / raw)
To: xen-devel
>>- When goes Xen 2.x to debian system?
> Try unofficial xen-2.0.1 deb packages at; http://www.terrabox.com/debian/
Argh, either I'm a bit blind, or those packages should be advertised on
Xen website ; I couldn't find working debian packages for Xen 2 so I
decided to build my own packages - but they aren't as nice (one big xen
package with all the stuff inside).
Does Brian Wolfe plan to integrate those packages into sid (or better,
sarge) ?
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Xen 2.0 Debian packages
2004-11-29 14:47 ` Xen 2.0 Debian packages Jérôme Petazzoni
@ 2004-11-30 1:12 ` Brian Wolfe
0 siblings, 0 replies; 16+ messages in thread
From: Brian Wolfe @ 2004-11-30 1:12 UTC (permalink / raw)
To: Jérôme Petazzoni; +Cc: Xen Devel Mailing List
I'm curently under Adam Heath's mentoring for obtaining debian developer
status. I don't know what the chances are of xen 2.0 packages getting
into sid.
These are compiled against Sarge. It shouldn't be a problem to setup a
virtual server and merely recompile with specific version requirements
for sid though if you want to grab the sources from the same repo and
get them to build by merely changing the versions on the required debian
packages.
I'll accept a patch and add it to the compile targets if you get it to
work. :) I still need to get automatic builds going again and then fork
a set of xen-dev packages for sarge.
Brian
On Mon, 2004-11-29 at 15:47 +0100, Jérôme Petazzoni wrote:
> >>- When goes Xen 2.x to debian system?
>
> > Try unofficial xen-2.0.1 deb packages at; http://www.terrabox.com/debian/
>
> Argh, either I'm a bit blind, or those packages should be advertised on
> Xen website ; I couldn't find working debian packages for Xen 2 so I
> decided to build my own packages - but they aren't as nice (one big xen
> package with all the stuff inside).
>
> Does Brian Wolfe plan to integrate those packages into sid (or better,
> sarge) ?
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
> 81503241.M464660P17281V000000000000000AI1F563AFB_1.mail1,S=3886
> 56 1081503241.M466865P17281V000000000000000AI1F563AFC_2.mail1,S=3834
> 57 1081503241.M485042P17281V000000000000000AI1F563AFD_3.mail1,S=4216
> 58 1081503241.M487459P17281V000000000000000AI1F563AFE_4.mail1,S=3959
> 59 1081503241.M489581P17281V000000000000000AI1F563AFF_5.mail1,S=4434
> 60 1081503241.M491691P17281V
--
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Fwd: bridging problem with Xen 2.0.1]
2004-11-29 10:40 [Fwd: bridging problem with Xen 2.0.1] Pásztor Lénárd Zoltán
2004-11-29 11:58 ` kaz
@ 2004-11-29 12:18 ` Keir Fraser
2004-11-29 14:55 ` Pásztor Lénárd Zoltán
2004-11-29 16:01 ` Pásztor Lénárd Zoltán
2004-11-29 13:08 ` Mike Wray
2 siblings, 2 replies; 16+ messages in thread
From: Keir Fraser @ 2004-11-29 12:18 UTC (permalink / raw)
To: Pásztor Lénárd Zoltán; +Cc: xen-devel
> Hi All!
>
>
> I need to setup a virtual host with 2 virtual ethernet interface on
> separated bridge.
> When the domain1 starts the second ethernet adapter does not connect to the
> domain0's second bridge.
> When I try to add the interface manually I got an error message.
> Can help somebody to me to solve this problem?
I'm not sure about your setup problem (looks like an etherbridge tools
problem). But I've checked in a fix for you rbuild problem into the
2.0-testing tree.
-- Keir
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Fwd: bridging problem with Xen 2.0.1]
2004-11-29 12:18 ` [Fwd: bridging problem with Xen 2.0.1] Keir Fraser
@ 2004-11-29 14:55 ` Pásztor Lénárd Zoltán
2004-11-29 16:01 ` Pásztor Lénárd Zoltán
1 sibling, 0 replies; 16+ messages in thread
From: Pásztor Lénárd Zoltán @ 2004-11-29 14:55 UTC (permalink / raw)
To: Keir Fraser; +Cc: xen-devel
[-- Attachment #1: Type: text/plain, Size: 2056 bytes --]
Keir Fraser wrote:
>> Hi All!
>>
>>
>> I need to setup a virtual host with 2 virtual ethernet interface on
>>separated bridge.
>>When the domain1 starts the second ethernet adapter does not connect to the
>>domain0's second bridge.
>>When I try to add the interface manually I got an error message.
>>Can help somebody to me to solve this problem?
>>
>>
>
>I'm not sure about your setup problem (looks like an etherbridge tools
>problem). But I've checked in a fix for you rbuild problem into the
>2.0-testing tree.
>
>
>
I'am using bridge utils 1.0.4-1.
I downloaded the xen source after your mail with following command:
bk clone bk://xen.bkbits.net/xen-2.0-testing.bk
I tried to recompile the kernel again and I got the following message:
CC arch/xen/i386/mm/ioremap.o
arch/xen/i386/mm/ioremap.c: In function `__ioremap':
arch/xen/i386/mm/ioremap.c:161: error:
`isa_bus_to_virt_needs_PRIVILEGED_BUILD' undeclared (first use in this
function)
arch/xen/i386/mm/ioremap.c:161: error: (Each undeclared identifier is
reported only once
arch/xen/i386/mm/ioremap.c:161: error: for each function it appears in.)
arch/xen/i386/mm/ioremap.c: In function `bt_ioremap':
arch/xen/i386/mm/ioremap.c:294: error:
`isa_bus_to_virt_needs_PRIVILEGED_BUILD' undeclared (first use in this
function)
make[1]: *** [arch/xen/i386/mm/ioremap.o] Error 1
make: *** [arch/xen/i386/mm] Error 2
(I attached my .config file to this email)
> -- Keir
>
>
>-------------------------------------------------------
>SF email is sponsored by - The IT Product Guide
>Read honest & candid reviews on hundreds of IT Products from real users.
>Discover which products truly live up to the hype. Start reading now.
>http://productguide.itmanagersjournal.com/
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/xen-devel
>
>
--
Pásztor Lénárd Zoltán
rendszergazda
Wonderline Rt.
Telefon: (+36-1) 272.0242
Fax: (+36-1) 272.0252
Honlap: www.wonderline.hu
[-- Attachment #2: .config --]
[-- Type: text/plain, Size: 24537 bytes --]
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.9
# Mon Nov 29 15:21:43 2004
#
CONFIG_XEN=y
CONFIG_ARCH_XEN=y
CONFIG_NO_IDLE_HZ=y
#
# XEN
#
# CONFIG_XEN_PRIVILEGED_GUEST is not set
CONFIG_XEN_PHYSDEV_ACCESS=y
CONFIG_XEN_BLKDEV_BACKEND=y
CONFIG_XEN_NETDEV_BACKEND=y
CONFIG_XEN_BLKDEV_FRONTEND=y
CONFIG_XEN_NETDEV_FRONTEND=y
# CONFIG_XEN_NETDEV_FRONTEND_PIPELINED_TRANSMITTER is not set
CONFIG_XEN_WRITABLE_PAGETABLES=y
CONFIG_XEN_SCRUB_PAGES=y
CONFIG_HAVE_ARCH_DEV_ALLOC_SKB=y
CONFIG_X86=y
# CONFIG_X86_64 is not set
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
# CONFIG_CLEAN_COMPILE is not set
CONFIG_BROKEN=y
CONFIG_BROKEN_ON_SMP=y
#
# General setup
#
CONFIG_LOCALVERSION="-guest"
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
# CONFIG_POSIX_MQUEUE is not set
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
# CONFIG_AUDIT is not set
CONFIG_LOG_BUF_SHIFT=17
CONFIG_HOTPLUG=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SHMEM=y
# CONFIG_TINY_SHMEM is not set
#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_OBSOLETE_MODPARM=y
# CONFIG_MODVERSIONS is not set
CONFIG_KMOD=y
#
# X86 Processor Configuration
#
CONFIG_XENARCH="i386"
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
CONFIG_MPENTIUMIII=y
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
# CONFIG_HPET_TIMER is not set
# CONFIG_HPET_EMULATE_RTC is not set
# CONFIG_SMP is not set
CONFIG_PREEMPT=y
CONFIG_X86_CPUID=y
#
# Firmware Drivers
#
# CONFIG_EDD is not set
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
CONFIG_HIGHMEM=y
CONFIG_HAVE_DEC_LOCK=y
# CONFIG_REGPARM is not set
#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
CONFIG_PCI_DIRECT=y
# CONFIG_PCI_LEGACY_PROC is not set
CONFIG_PCI_NAMES=y
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
#
# PCMCIA/CardBus support
#
# CONFIG_PCMCIA is not set
#
# PCI Hotplug Support
#
# CONFIG_HOTPLUG_PCI is not set
#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
CONFIG_EARLY_PRINTK=y
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_SLAB is not set
CONFIG_MAGIC_SYSRQ=y
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_DEBUG_HIGHMEM is not set
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_FRAME_POINTER is not set
# CONFIG_4KSTACKS is not set
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_STD_RESOURCES=y
CONFIG_PC=y
#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_AOUT is not set
# CONFIG_BINFMT_MISC is not set
#
# Device Drivers
#
#
# Generic Driver Options
#
# CONFIG_STANDALONE is not set
# CONFIG_PREVENT_FIRMWARE_BUILD is not set
# CONFIG_FW_LOADER is not set
# CONFIG_DEBUG_DRIVER is not set
#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set
#
# Parallel port support
#
# CONFIG_PARPORT is not set
#
# Plug and Play support
#
#
# Block devices
#
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_CRYPTOLOOP=y
CONFIG_BLK_DEV_NBD=y
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y
# CONFIG_LBD is not set
#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
# CONFIG_IDEDISK_MULTI_MODE is not set
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
CONFIG_BLK_DEV_IDESCSI=m
# CONFIG_IDE_TASK_IOCTL is not set
# CONFIG_IDE_TASKFILE_IO is not set
#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_CMD640 is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_ATIIXP is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
CONFIG_BLK_DEV_PIIX=y
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_IDE_ARM is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_BLK_DEV_HD is not set
#
# SCSI device support
#
CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=y
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=y
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
#
# SCSI Transport Attributes
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
CONFIG_SCSI_AIC7XXX=y
CONFIG_AIC7XXX_CMDS_PER_DEVICE=32
CONFIG_AIC7XXX_RESET_DELAY_MS=15000
# CONFIG_AIC7XXX_BUILD_FIRMWARE is not set
CONFIG_AIC7XXX_DEBUG_ENABLE=y
CONFIG_AIC7XXX_DEBUG_MASK=0
CONFIG_AIC7XXX_REG_PRETTY_PRINT=y
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_SCSI_SATA is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_CPQFCTS is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_PCI2000 is not set
# CONFIG_SCSI_PCI2220I is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA2XXX=y
# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
# CONFIG_SCSI_QLA2300 is not set
# CONFIG_SCSI_QLA2322 is not set
# CONFIG_SCSI_QLA6312 is not set
# CONFIG_SCSI_QLA6322 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set
#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_LINEAR=y
CONFIG_MD_RAID0=y
CONFIG_MD_RAID1=y
# CONFIG_MD_RAID10 is not set
# CONFIG_MD_RAID5 is not set
# CONFIG_MD_RAID6 is not set
CONFIG_MD_MULTIPATH=y
CONFIG_BLK_DEV_DM=y
CONFIG_DM_CRYPT=y
# CONFIG_DM_SNAPSHOT is not set
# CONFIG_DM_MIRROR is not set
# CONFIG_DM_ZERO is not set
#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
#
# IEEE 1394 (FireWire) support
#
# CONFIG_IEEE1394 is not set
#
# I2O device support
#
# CONFIG_I2O is not set
#
# Networking support
#
CONFIG_NET=y
#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
# CONFIG_NETLINK_DEV is not set
CONFIG_UNIX=y
CONFIG_NET_KEY=y
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_ARPD is not set
# CONFIG_SYN_COOKIES is not set
CONFIG_INET_AH=y
CONFIG_INET_ESP=y
CONFIG_INET_IPCOMP=y
CONFIG_INET_TUNNEL=y
#
# IP: Virtual Server Configuration
#
CONFIG_IP_VS=y
CONFIG_IP_VS_DEBUG=y
CONFIG_IP_VS_TAB_BITS=12
#
# IPVS transport protocol load balancing support
#
CONFIG_IP_VS_PROTO_TCP=y
CONFIG_IP_VS_PROTO_UDP=y
CONFIG_IP_VS_PROTO_ESP=y
CONFIG_IP_VS_PROTO_AH=y
#
# IPVS scheduler
#
CONFIG_IP_VS_RR=y
CONFIG_IP_VS_WRR=y
CONFIG_IP_VS_LC=y
CONFIG_IP_VS_WLC=y
CONFIG_IP_VS_LBLC=y
CONFIG_IP_VS_LBLCR=y
CONFIG_IP_VS_DH=y
CONFIG_IP_VS_SH=y
CONFIG_IP_VS_SED=y
CONFIG_IP_VS_NQ=y
#
# IPVS application helper
#
CONFIG_IP_VS_FTP=y
# CONFIG_IPV6 is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_BRIDGE_NETFILTER=y
#
# IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=y
CONFIG_IP_NF_CT_ACCT=y
CONFIG_IP_NF_CT_PROTO_SCTP=y
CONFIG_IP_NF_FTP=y
CONFIG_IP_NF_IRC=y
CONFIG_IP_NF_TFTP=y
CONFIG_IP_NF_AMANDA=y
CONFIG_IP_NF_QUEUE=y
CONFIG_IP_NF_IPTABLES=y
CONFIG_IP_NF_MATCH_LIMIT=y
CONFIG_IP_NF_MATCH_IPRANGE=y
CONFIG_IP_NF_MATCH_MAC=y
CONFIG_IP_NF_MATCH_PKTTYPE=y
CONFIG_IP_NF_MATCH_MARK=y
CONFIG_IP_NF_MATCH_MULTIPORT=y
CONFIG_IP_NF_MATCH_TOS=y
CONFIG_IP_NF_MATCH_RECENT=y
CONFIG_IP_NF_MATCH_ECN=y
CONFIG_IP_NF_MATCH_DSCP=y
CONFIG_IP_NF_MATCH_AH_ESP=y
CONFIG_IP_NF_MATCH_LENGTH=y
CONFIG_IP_NF_MATCH_TTL=y
CONFIG_IP_NF_MATCH_TCPMSS=y
CONFIG_IP_NF_MATCH_HELPER=y
CONFIG_IP_NF_MATCH_STATE=y
CONFIG_IP_NF_MATCH_CONNTRACK=y
CONFIG_IP_NF_MATCH_OWNER=y
CONFIG_IP_NF_MATCH_PHYSDEV=y
CONFIG_IP_NF_MATCH_ADDRTYPE=y
CONFIG_IP_NF_MATCH_REALM=y
CONFIG_IP_NF_MATCH_SCTP=y
CONFIG_IP_NF_MATCH_COMMENT=y
CONFIG_IP_NF_FILTER=y
CONFIG_IP_NF_TARGET_REJECT=y
CONFIG_IP_NF_TARGET_LOG=y
CONFIG_IP_NF_TARGET_ULOG=y
CONFIG_IP_NF_TARGET_TCPMSS=y
CONFIG_IP_NF_NAT=y
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=y
CONFIG_IP_NF_TARGET_REDIRECT=y
CONFIG_IP_NF_TARGET_NETMAP=y
CONFIG_IP_NF_TARGET_SAME=y
CONFIG_IP_NF_NAT_LOCAL=y
CONFIG_IP_NF_NAT_SNMP_BASIC=y
CONFIG_IP_NF_NAT_IRC=y
CONFIG_IP_NF_NAT_FTP=y
CONFIG_IP_NF_NAT_TFTP=y
CONFIG_IP_NF_NAT_AMANDA=y
CONFIG_IP_NF_MANGLE=y
CONFIG_IP_NF_TARGET_TOS=y
CONFIG_IP_NF_TARGET_ECN=y
CONFIG_IP_NF_TARGET_DSCP=y
CONFIG_IP_NF_TARGET_MARK=y
CONFIG_IP_NF_TARGET_CLASSIFY=y
CONFIG_IP_NF_RAW=y
CONFIG_IP_NF_TARGET_NOTRACK=y
CONFIG_IP_NF_ARPTABLES=y
CONFIG_IP_NF_ARPFILTER=y
CONFIG_IP_NF_ARP_MANGLE=y
#
# Bridge: Netfilter Configuration
#
CONFIG_BRIDGE_NF_EBTABLES=y
CONFIG_BRIDGE_EBT_BROUTE=y
CONFIG_BRIDGE_EBT_T_FILTER=y
CONFIG_BRIDGE_EBT_T_NAT=y
CONFIG_BRIDGE_EBT_802_3=y
CONFIG_BRIDGE_EBT_AMONG=y
CONFIG_BRIDGE_EBT_ARP=y
CONFIG_BRIDGE_EBT_IP=y
CONFIG_BRIDGE_EBT_LIMIT=y
CONFIG_BRIDGE_EBT_MARK=y
CONFIG_BRIDGE_EBT_PKTTYPE=y
CONFIG_BRIDGE_EBT_STP=y
CONFIG_BRIDGE_EBT_VLAN=y
CONFIG_BRIDGE_EBT_ARPREPLY=y
CONFIG_BRIDGE_EBT_DNAT=y
CONFIG_BRIDGE_EBT_MARK_T=y
CONFIG_BRIDGE_EBT_REDIRECT=y
CONFIG_BRIDGE_EBT_SNAT=y
CONFIG_BRIDGE_EBT_LOG=y
CONFIG_XFRM=y
CONFIG_XFRM_USER=y
#
# SCTP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
CONFIG_BRIDGE=y
CONFIG_VLAN_8021Q=y
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_HW_FLOWCONTROL is not set
#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set
CONFIG_NET_CLS_ROUTE=y
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
CONFIG_NETDEVICES=y
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
#
# ARCnet devices
#
# CONFIG_ARCNET is not set
#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set
#
# Tulip family network device support
#
CONFIG_NET_TULIP=y
# CONFIG_DE2104X is not set
CONFIG_TULIP=y
# CONFIG_TULIP_MWI is not set
# CONFIG_TULIP_MMIO is not set
# CONFIG_TULIP_NAPI is not set
# CONFIG_DE4X5 is not set
# CONFIG_WINBOND_840 is not set
# CONFIG_DM9102 is not set
# CONFIG_HP100 is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_B44 is not set
# CONFIG_FORCEDETH is not set
# CONFIG_DGRS is not set
# CONFIG_EEPRO100 is not set
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139CP is not set
CONFIG_8139TOO=y
CONFIG_8139TOO_PIO=y
CONFIG_8139TOO_TUNE_TWISTER=y
# CONFIG_8139TOO_8129 is not set
# CONFIG_8139_OLD_RX_RESET is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_VIA_VELOCITY is not set
#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set
#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_S2IO is not set
#
# Token Ring devices
#
# CONFIG_TR is not set
#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set
#
# Wan interfaces
#
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set
#
# ISDN subsystem
#
# CONFIG_ISDN is not set
#
# Telephony Support
#
# CONFIG_PHONE is not set
#
# Input device support
#
CONFIG_INPUT=y
#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
# CONFIG_INPUT_MOUSEDEV_PSAUX is not set
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set
#
# Input I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PCIPS2 is not set
# CONFIG_SERIO_RAW is not set
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_INPUT_MOUSE is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set
#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set
#
# Serial drivers
#
# CONFIG_SERIAL_8250 is not set
#
# Non-8250 serial port support
#
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set
#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
CONFIG_HW_RANDOM=y
# CONFIG_NVRAM is not set
CONFIG_RTC=y
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set
#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
# CONFIG_AGP is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HANGCHECK_TIMER is not set
#
# I2C support
#
# CONFIG_I2C is not set
#
# Dallas's 1-wire bus
#
# CONFIG_W1 is not set
#
# Misc devices
#
# CONFIG_IBM_ASM is not set
#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set
#
# Graphics support
#
CONFIG_FB=y
CONFIG_FB_MODE_HELPERS=y
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
CONFIG_FB_VESA=y
CONFIG_VIDEO_SELECT=y
# CONFIG_FB_HGA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I810 is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON_OLD is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_VIRTUAL is not set
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
#
# Logo configuration
#
CONFIG_LOGO=y
# CONFIG_LOGO_LINUX_MONO is not set
# CONFIG_LOGO_LINUX_VGA16 is not set
CONFIG_LOGO_LINUX_CLUT224=y
#
# Sound
#
# CONFIG_SOUND is not set
#
# USB support
#
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set
#
# Miscellaneous USB options
#
# CONFIG_USB_DEVICEFS is not set
# CONFIG_USB_BANDWIDTH is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_OTG is not set
#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=m
CONFIG_USB_EHCI_SPLIT_ISO=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
# CONFIG_USB_OHCI_HCD is not set
CONFIG_USB_UHCI_HCD=m
#
# USB Device Class drivers
#
# CONFIG_USB_BLUETOOTH_TTY is not set
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_RW_DETECT is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_DPCM is not set
# CONFIG_USB_STORAGE_HP8200e is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set
#
# USB Human Interface Devices (HID)
#
CONFIG_USB_HID=m
CONFIG_USB_HIDINPUT=y
# CONFIG_HID_FF is not set
# CONFIG_USB_HIDDEV is not set
#
# USB HID Boot Protocol drivers
#
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE is not set
# CONFIG_USB_AIPTEK is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_KBTAB is not set
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_MTOUCH is not set
# CONFIG_USB_EGALAX is not set
# CONFIG_USB_XPAD is not set
# CONFIG_USB_ATI_REMOTE is not set
#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set
# CONFIG_USB_HPUSBSCSI is not set
#
# USB Multimedia devices
#
# CONFIG_USB_DABUSB is not set
#
# Video4Linux support is needed for USB Multimedia device support
#
#
# USB Network adaptors
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set
#
# USB port drivers
#
#
# USB Serial Converter support
#
# CONFIG_USB_SERIAL is not set
#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_TIGL is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_PHIDGETSERVO is not set
#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set
#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
# CONFIG_EXT3_FS_SECURITY is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_REISERFS_FS_XATTR is not set
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
CONFIG_QUOTA=y
CONFIG_QFMT_V1=y
CONFIG_QFMT_V2=y
CONFIG_QUOTACTL=y
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=y
#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_ZISOFS_FS=m
CONFIG_UDF_FS=m
CONFIG_UDF_NLS=y
#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_FAT_DEFAULT_CODEPAGE=852
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-2"
CONFIG_NTFS_FS=m
# CONFIG_NTFS_DEBUG is not set
# CONFIG_NTFS_RW is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
# CONFIG_DEVFS_FS is not set
# CONFIG_DEVPTS_FS_XATTR is not set
CONFIG_TMPFS=y
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y
#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
#
# Network File Systems
#
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
CONFIG_NFS_V4=y
CONFIG_NFS_DIRECTIO=y
CONFIG_NFSD=m
CONFIG_NFSD_V3=y
CONFIG_NFSD_V4=y
CONFIG_NFSD_TCP=y
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=m
CONFIG_SUNRPC=m
CONFIG_SUNRPC_GSS=m
CONFIG_RPCSEC_GSS_KRB5=m
# CONFIG_RPCSEC_GSS_SPKM3 is not set
CONFIG_SMB_FS=m
CONFIG_SMB_NLS_DEFAULT=y
CONFIG_SMB_NLS_REMOTE="cp852"
CONFIG_CIFS=m
CONFIG_CIFS_STATS=y
# CONFIG_CIFS_XATTR is not set
# CONFIG_CIFS_POSIX is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-2"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
CONFIG_NLS_CODEPAGE_850=y
CONFIG_NLS_CODEPAGE_852=y
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ASCII is not set
CONFIG_NLS_ISO8859_1=y
CONFIG_NLS_ISO8859_2=y
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=y
#
# Security options
#
# CONFIG_SECURITY is not set
#
# Cryptographic options
#
CONFIG_CRYPTO=y
CONFIG_CRYPTO_HMAC=y
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_MD4 is not set
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_SHA1=y
# CONFIG_CRYPTO_SHA256 is not set
CONFIG_CRYPTO_SHA512=m
# CONFIG_CRYPTO_WP512 is not set
CONFIG_CRYPTO_DES=y
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_SERPENT is not set
CONFIG_CRYPTO_AES_586=m
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
# CONFIG_CRYPTO_TEA is not set
# CONFIG_CRYPTO_ARC4 is not set
# CONFIG_CRYPTO_KHAZAD is not set
CONFIG_CRYPTO_DEFLATE=y
# CONFIG_CRYPTO_MICHAEL_MIC is not set
CONFIG_CRYPTO_CRC32C=m
# CONFIG_CRYPTO_TEST is not set
#
# Library routines
#
CONFIG_CRC_CCITT=m
CONFIG_CRC32=y
CONFIG_LIBCRC32C=m
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Fwd: bridging problem with Xen 2.0.1]
2004-11-29 12:18 ` [Fwd: bridging problem with Xen 2.0.1] Keir Fraser
2004-11-29 14:55 ` Pásztor Lénárd Zoltán
@ 2004-11-29 16:01 ` Pásztor Lénárd Zoltán
1 sibling, 0 replies; 16+ messages in thread
From: Pásztor Lénárd Zoltán @ 2004-11-29 16:01 UTC (permalink / raw)
To: Keir Fraser; +Cc: xen-devel
Keir Fraser wrote:
>> Hi All!
>>
>>
>> I need to setup a virtual host with 2 virtual ethernet interface on
>>separated bridge.
>>When the domain1 starts the second ethernet adapter does not connect to the
>>domain0's second bridge.
>>When I try to add the interface manually I got an error message.
>>Can help somebody to me to solve this problem?
>>
>>
>
>I'm not sure about your setup problem (looks like an etherbridge tools
>problem). But I've checked in a fix for you rbuild problem into the
>2.0-testing tree.
>
>
>
Now the build process stops here:
CC drivers/video/console/vgacon.o
drivers/video/console/vgacon.c: In function `vgacon_startup':
drivers/video/console/vgacon.c:286: error:
`isa_bus_to_virt_needs_PRIVILEGED_BUILD' undeclared (first use in this
function)
drivers/video/console/vgacon.c:286: error: (Each undeclared identifier
is reported only once
drivers/video/console/vgacon.c:286: error: for each function it appears in.)
drivers/video/console/vgacon.c: In function `vgacon_do_font_op':
drivers/video/console/vgacon.c:728: error:
`isa_bus_to_virt_needs_PRIVILEGED_BUILD' undeclared (first use in this
function)
make[3]: *** [drivers/video/console/vgacon.o] Error 1
make[2]: *** [drivers/video/console] Error 2
make[1]: *** [drivers/video] Error 2
make: *** [drivers] Error 2
> -- Keir
>
>
>-------------------------------------------------------
>SF email is sponsored by - The IT Product Guide
>Read honest & candid reviews on hundreds of IT Products from real users.
>Discover which products truly live up to the hype. Start reading now.
>http://productguide.itmanagersjournal.com/
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/xen-devel
>
>
--
Pásztor Lénárd Zoltán
rendszergazda
Wonderline Rt.
Telefon: (+36-1) 272.0242
Fax: (+36-1) 272.0252
Honlap: www.wonderline.hu
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Fwd: bridging problem with Xen 2.0.1]
2004-11-29 10:40 [Fwd: bridging problem with Xen 2.0.1] Pásztor Lénárd Zoltán
2004-11-29 11:58 ` kaz
2004-11-29 12:18 ` [Fwd: bridging problem with Xen 2.0.1] Keir Fraser
@ 2004-11-29 13:08 ` Mike Wray
2004-11-29 15:02 ` Pásztor Lénárd Zoltán
2 siblings, 1 reply; 16+ messages in thread
From: Mike Wray @ 2004-11-29 13:08 UTC (permalink / raw)
To: Pásztor Lénárd Zoltán; +Cc: xen-devel
Pásztor Lénárd Zoltán wrote:
>
> Hello,
>
>
> I sent this mail (see attachement) to the
> zen-devel@lists.sourceforge.net address,
> but there is no answer, and my email does not exist in the mail archive.
> What did I wrong?
>
> (sorry for my english...)
>
>
> ------------------------------------------------------------------------
>
> Subject:
> bridging problem with Xen 2.0.1
> From:
> Pásztor Lénárd Zoltán <lenard.pasztor@wonderline.hu>
> Date:
> Fri, 26 Nov 2004 13:47:57 +0100
> To:
> mailto:xen-devel@lists.sourceforge.net
>
> To:
> mailto:xen-devel@lists.sourceforge.net
>
>
>
> Hi All!
>
>
> I need to setup a virtual host with 2 virtual ethernet interface on
> separated bridge.
> When the domain1 starts the second ethernet adapter does not connect to the
> domain0's second bridge.
> When I try to add the interface manually I got an error message.
> Can help somebody to me to solve this problem?
>
>
> Domain0:
>
> Debinan/GNU linux (sarge)
> Xen 2.0.1 (with recompiled 2.6.9 kernel)
>
> Domain1:
> Debian/GNU linux (sarge)
> Xen unmodified vmlinuz-2.6.9-xenU kernel
>
> (when I compile unprivileged kernel I got the following message from
> build process:
> CC arch/xen/i386/mm/ioremap.o
> arch/xen/i386/mm/ioremap.c: In function `__ioremap':
> arch/xen/i386/mm/ioremap.c:144: error:
> `isa_bus_to_virt_needs_PRIVILEGED_BUILD' undeclared (first use in this
> function)
> arch/xen/i386/mm/ioremap.c:144: error: (Each undeclared identifier is
> reported only once
> arch/xen/i386/mm/ioremap.c:144: error: for each function it appears in.)
> arch/xen/i386/mm/ioremap.c: In function `bt_ioremap':
> arch/xen/i386/mm/ioremap.c:280: error:
> `isa_bus_to_virt_needs_PRIVILEGED_BUILD' undeclared (first use in this
> function)
> make[1]: *** [arch/xen/i386/mm/ioremap.o] Error 1
> make: *** [arch/xen/i386/mm] Error 2
> )
>
>
> Below the commands how I test it:
>
> domain0:~# ifconfig xen-br0 10.10.254.254 netmask 255.255.0.0 broadcast
> 10.10.255.255 up
> domain0:~# ifconfig xen-br1 10.11.254.254 netmask 255.255.0.0 broadcast
> 10.11.255.255 up
> domain0:~# ifconfig
> eth0 Link encap:Ethernet HWaddr 00:30:4F:13:DF:DD
> inet addr:10.3.1.45 Bcast:10.3.255.255 Mask:255.255.0.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:4636 errors:0 dropped:0 overruns:0 frame:0
> TX packets:3055 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:421198 (411.3 KiB) TX bytes:565986 (552.7 KiB)
> Interrupt:9 Base address:0xd400
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:3243 errors:0 dropped:0 overruns:0 frame:0
> TX packets:3243 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:222710 (217.4 KiB) TX bytes:222710 (217.4 KiB)
>
> xen-br0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
> inet addr:10.10.254.254 Bcast:10.10.255.255 Mask:255.255.0.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:88 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:8675 (8.4 KiB) TX bytes:0 (0.0 b)
>
> xen-br1 Link encap:Ethernet HWaddr 00:00:00:00:00:00
> inet addr:10.11.254.254 Bcast:10.11.255.255 Mask:255.255.0.0
> 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:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>
>
> domain0:~# brctl show
> bridge name bridge id STP enabled interfaces
> xen-br0 8000.000000000000 no can't get port
> info: Function not implemented
> xen-br1 8000.000000000000 no can't get port
> info: Function not implemented
>
> domain0:~# route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> 10.3.0.0 0.0.0.0 255.255.0.0 U 0 0 0
> eth0
> 10.10.0.0 0.0.0.0 255.255.0.0 U 0 0 0
> xen-br0
> 10.11.0.0 0.0.0.0 255.255.0.0 U 0 0 0
> xen-br1
> 0.0.0.0 10.3.0.2 0.0.0.0 UG 0 0 0
> eth0
>
>
> Now starting a domain1 with this nic config:
>
> nics = 2
>
> vif = [ 'mac=aa:00:00:00:00:11, bridge=xen-br0',
> 'mac=bb:00:00:00:00:22, bridge=xen-br1']
The second MAC addr is multicast (bit 1 on in first byte).
Try a unicast MAC addr like aa:00:00:00:00:12 instead.
>
>
> domain1:~$ ifconfig
> eth0 Link encap:Ethernet HWaddr AA:00:00:00:00:11
> inet addr:10.10.10.1 Bcast:10.10.255.255 Mask:255.255.0.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:1 errors:0 dropped:0 overruns:0 frame:0
> TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:42 (42.0 b) TX bytes:116 (116.0 b)
>
> eth1 Link encap:Ethernet HWaddr BB:00:00:00:00:22
> inet addr:10.11.10.1 Bcast:10.11.255.25 Mask:255.255.0.0
> 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:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> 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)
>
> domain1:~$ route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> 10.10.0.0 0.0.0.0 255.255.0.0 U 0 0 0
> eth0
> 10.11.0.0 0.0.0.0 255.255.0.0 U 0 0 0
> eth1
> 0.0.0.0 10.10.254.254 0.0.0.0 UG 0 0 0
> eth0
>
> domain0:~# ifconfig
> eth0 Link encap:Ethernet HWaddr 00:30:4F:13:DF:DD
> inet addr:10.3.1.45 Bcast:10.3.255.255 Mask:255.255.0.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:5115 errors:0 dropped:0 overruns:0 frame:0
> TX packets:3426 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:461687 (450.8 KiB) TX bytes:626631 (611.9 KiB)
> Interrupt:9 Base address:0xd400
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:4524 errors:0 dropped:0 overruns:0 frame:0
> TX packets:4524 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:299113 (292.1 KiB) TX bytes:299113 (292.1 KiB)
>
> vif4.0 Link encap:Ethernet HWaddr AA:00:01:00:00:11
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:21 errors:0 dropped:0 overruns:0 frame:0
> TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:1346 (1.3 KiB) TX bytes:1062 (1.0 KiB)
>
> vif4.1 Link encap:Ethernet HWaddr BB:00:01:00:00:22
> 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:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>
> xen-br0 Link encap:Ethernet HWaddr AA:00:01:00:00:11
> inet addr:10.10.254.254 Bcast:10.10.255.255 Mask:255.255.0.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:109 errors:0 dropped:0 overruns:0 frame:0
> TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:9727 (9.4 KiB) TX bytes:1062 (1.0 KiB)
>
> xen-br1 Link encap:Ethernet HWaddr 00:00:00:00:00:00
> inet addr:10.11.254.254 Bcast:10.11.255.255 Mask:255.255.0.0
> 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:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>
>
>
> domain0:~# brctl show
> bridge name bridge id STP enabled interfaces
> xen-br0 8000.aa0001000011 no vif4.0
> xen-br1 8000.000000000000 no can't get port
> info: Function not implemented
>
> Why vif4.1 not in xen-br1?
Something must have gone wrong. What's the ouput from 'xm list -l' show?
Also is there anything in /var/log/xend.log?
> Let's add it manually...
>
> domain0:~# brctl addif vif4.1 xen-br1
> can't add xen-br1 to bridge vif4.1: Operation not supported
>
> It gives error message :( What is the problem?
You've got the arguments round the wrong way, it should be
brctl addif xen-br1 vif4.1
>
> Testing vif4.0...
>
> domain0:~# ping 10.10.10.1
> PING 10.10.10.1 (10.10.10.1) 56(84) bytes of data.
> 64 bytes from 10.10.10.1: icmp_seq=1 ttl=64 time=0.399 ms
> 64 bytes from 10.10.10.1: icmp_seq=2 ttl=64 time=0.278 ms
>
> --- 10.10.10.1 ping statistics ---
> 2 packets transmitted, 2 received, 0% packet loss, time 1005ms
> rtt min/avg/max/mdev = 0.278/0.338/0.399/0.063 ms
>
> domain1:~$ ping 10.10.254.254
> PING 10.10.254.254 (10.10.254.254) 56(84) bytes of data.
> 64 bytes from 10.10.254.254: icmp_seq=1 ttl=64 time=2.47 ms
> 64 bytes from 10.10.254.254: icmp_seq=2 ttl=64 time=0.364 ms
>
> --- 10.10.254.254 ping statistics ---
> 2 packets transmitted, 2 received, 0% packet loss, time 1006ms
> rtt min/avg/max/mdev = 0.364/1.417/2.470/1.053 ms
>
> It's OK.
>
> Testing vif4.1...
> domain1:~$ ping 10.11.254.254
> PING 10.11.254.254 (10.11.254.254) 56(84) bytes of data.
>
> --- 10.11.254.254 ping statistics ---
> 1 packets transmitted, 0 received, 100% packet loss, time 0ms
>
> domain0:~# tcpdump -i vif4.1 -n
> tcpdump: WARNING: vif4.1: no IPv4 address assigned
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on vif4.1, link-type EN10MB (Ethernet), capture size 96 bytes
> 11:11:49.011029 arp who-has 10.11.254.254 tell 10.11.10.1
> 11:11:50.010942 arp who-has 10.11.254.254 tell 10.11.10.1
> 11:11:51.010952 arp who-has 10.11.254.254 tell 10.11.10.1
>
> 3 packets captured
> 3 packets received by filter
> 0 packets dropped by kernel
>
> So, the vif4.1 interface seems to be OK.
>
> Other questions:
>
> - When goes Xen 2.x to debian system?
> - How can I define the nic name (vif) before I start a virtual machine?
The vif device name in domain-0 is vif<domain id>.<interface>.
This is not changeable at the moment. If you need to do something with
the device, you could use the vif-bridge script to do it, or configure
another script.
Mike
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Fwd: bridging problem with Xen 2.0.1]
2004-11-29 13:08 ` Mike Wray
@ 2004-11-29 15:02 ` Pásztor Lénárd Zoltán
0 siblings, 0 replies; 16+ messages in thread
From: Pásztor Lénárd Zoltán @ 2004-11-29 15:02 UTC (permalink / raw)
To: Mike Wray; +Cc: xen-devel
Mike Wray wrote:
> Pásztor Lénárd Zoltán wrote:
>
>>
>>
>> domain0:~# brctl show
>> bridge name bridge id STP enabled interfaces
>> xen-br0 8000.aa0001000011 no vif4.0
>> xen-br1 8000.000000000000 no can't get
>> port info: Function not implemented
>>
>> Why vif4.1 not in xen-br1?
>
>
> Something must have gone wrong. What's the ouput from 'xm list -l' show?
> Also is there anything in /var/log/xend.log?
>
xm list -l output is:
(devices
(vif
(idx 0)
(vif 0)
(mac aa:00:00:00:00:11)
(bridge xen-br0)
(evtchn 14 4)
(index 0)
)
(vif
(idx 1)
(vif 1)
(mac bb:00:00:00:00:22)
(bridge xen-br1)
(evtchn 15 5)
(index 1)
)
Seems to bee OK.
xend.log has two lines associated by nic:
[2004-11-29 15:47:43 xend] DEBUG (XendDomainInfo:1059) Creating vif
dom=2 vif=0 mac=aa:00:00:00:00:11
[2004-11-29 15:47:43 xend] DEBUG (XendDomainInfo:1059) Creating vif
dom=2 vif=1 mac=bb:00:00:00:00:22
no error messages on it.
>> Let's add it manually...
>>
>> domain0:~# brctl addif vif4.1 xen-br1
>> can't add xen-br1 to bridge vif4.1: Operation not supported
>>
>> It gives error message :( What is the problem?
>
>
> You've got the arguments round the wrong way, it should be
>
> brctl addif xen-br1 vif4.1
>
sorry, I paste wrong the line o:)
domain1: brctl addif xen-br1 vif4.1
can't add vif4.1 to bridge xen-br1: Cannot assign requested address
>> - How can I define the nic name (vif) before I start a virtual machine?
>
>
> The vif device name in domain-0 is vif<domain id>.<interface>.
> This is not changeable at the moment. If you need to do something with
> the device, you could use the vif-bridge script to do it, or configure
> another script.
>
It's OK for me, thx!
--
Pásztor Lénárd Zoltán
rendszergazda
Wonderline Rt.
Telefon: (+36-1) 272.0242
Fax: (+36-1) 272.0252
Honlap: www.wonderline.hu
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
^ permalink raw reply [flat|nested] 16+ messages in thread
end of thread, other threads:[~2004-11-30 1:12 UTC | newest]
Thread overview: 16+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-11-29 10:40 [Fwd: bridging problem with Xen 2.0.1] Pásztor Lénárd Zoltán
2004-11-29 11:58 ` kaz
2004-11-29 14:12 ` Nuutti Kotivuori
2004-11-29 15:41 ` kaz
2004-11-29 15:47 ` Brian Wolfe
2004-11-29 15:56 ` kaz
2004-11-29 16:20 ` Brian Wolfe
2004-11-29 16:55 ` Nuutti Kotivuori
2004-11-29 17:29 ` Brian Wolfe
2004-11-29 14:47 ` Xen 2.0 Debian packages Jérôme Petazzoni
2004-11-30 1:12 ` Brian Wolfe
2004-11-29 12:18 ` [Fwd: bridging problem with Xen 2.0.1] Keir Fraser
2004-11-29 14:55 ` Pásztor Lénárd Zoltán
2004-11-29 16:01 ` Pásztor Lénárd Zoltán
2004-11-29 13:08 ` Mike Wray
2004-11-29 15:02 ` Pásztor Lénárd Zoltán
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.