Pásztor Lénárd Zoltán
2004-Nov-29 10:40 UTC
[Xen-devel] [Fwd: bridging problem with Xen 2.0.1]
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/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/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/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/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/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Nuutti Kotivuori
2004-Nov-29 14:12 UTC
[Xen-devel] Re: [Fwd: bridging problem with Xen 2.0.1]
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/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/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/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Pásztor Lénárd Zoltán
2004-Nov-29 14:55 UTC
Re: [Xen-devel] [Fwd: bridging problem with Xen 2.0.1]
Pásztor Lénárd Zoltán
2004-Nov-29 15:02 UTC
Re: [Xen-devel] [Fwd: bridging problem with Xen 2.0.1]
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/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/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/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Brian Wolfe
2004-Nov-29 15:47 UTC
Re: [Xen-devel] Re: [Fwd: bridging problem with Xen 2.0.1]
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/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
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
Pásztor Lénárd Zoltán
2004-Nov-29 16:01 UTC
Re: [Xen-devel] [Fwd: bridging problem with Xen 2.0.1]
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/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Brian Wolfe
2004-Nov-29 16:20 UTC
Re: [Xen-devel] Re: [Fwd: bridging problem with Xen 2.0.1]
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/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Nuutti Kotivuori
2004-Nov-29 16:55 UTC
[Xen-devel] Re: [Fwd: bridging problem with Xen 2.0.1]
Brian Wolfe wrote:> Done. Kind of burnt out this morning. 8-PIn 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
Brian Wolfe
2004-Nov-29 17:29 UTC
Re: [Xen-devel] Re: [Fwd: bridging problem with Xen 2.0.1]
*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/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
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/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel