From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: [Xen-users] Re: ARP problems with xen 4.0 with pvops kernel 2.6.32.15 Date: Wed, 09 Jun 2010 12:06:33 -0700 Message-ID: <4C0FE639.7000801@goop.org> References: <4C0FDF14.5090508@goop.org> <622843.98929.qm@web56107.mail.re3.yahoo.com> <20100609185554.GC17817@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20100609185554.GC17817@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: Boris Derzhavets , xen-devel@lists.xensource.com, luis.silva@axiomasoft.pt, xen-users@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 06/09/2010 11:55 AM, Pasi K=E4rkk=E4inen wrote: > On Wed, Jun 09, 2010 at 11:42:03AM -0700, Boris Derzhavets wrote: > =20 >> It doesn't happen with 2.6.32.10 loaded instead of 2.6.32.15 into the = same instance. >> Fetching data from same Apache Mirror. >> >> =20 > You could git bisect this.. so we find the exact patch that breaks it..= =20 > =20 That would be helpful, but the netback changes have a great big flashing light over them. J > -- Pasi > > =20 >> --- On Wed, 6/9/10, Jeremy Fitzhardinge wrote: >> >> From: Jeremy Fitzhardinge >> Subject: Re: [Xen-users] Re: [Xen-devel] ARP problems with xen 4.0 w= ith pvops kernel >> 2.6.32.15 >> To: "Pasi K=E4rkk=E4inen" >> Cc: "Boris Derzhavets" , xen-devel@lists.xens= ource.com, >> luis.silva@axiomasoft.pt, xen-users@lists.xensource.com >> Date: Wednesday, June 9, 2010, 2:36 PM >> >> On 06/09/2010 11:34 AM, Pasi K=E4rkk=E4inen wrote: >> > On Wed, Jun 09, 2010 at 10:46:13AM -0700, Boris Derzhavets wrote: >> > >> >> I've captured an exact error message in text virt-install console= :- >> >> >> --------------------------------------------------------------------= ------------------------- >> >> error 2 reading header: cpio: Bad magic >> >> >> >> Running anaconda 13.42, the Fedora system installer - please wait= . >> >> >> --------------------------------------------------------------------= ------------------------ >> >> >> >> >> > I guess that means the file anaconda downloaded is corrupt.. ie. n= etworking is broken. >> > >> >> I would expect that any cpio wrapped up in an rpm would have to go >> through a number of layers of sha1/md5/signature/etc checking before= the >> cpio header gets checked. If its making its way through that and th= en >> finding a bad magic in the cpio, it would seem to be memory or disk >> corruption. >> >> J >> >> > -- Pasi >> > >> > >> > >> >> Boris. >> >> P.S. Xen 4.0.1-rc2-pre, 2.6.32.15 (the most recent commit) >> >> >> >> --- On Wed, 6/9/10, Pasi K=E4rkk=E4inen <[1]pasik@iki.fi> wrote: >> >> >> >> From: Pasi K=E4rkk=E4inen <[2]pasik@iki.fi> >> >> Subject: Re: [Xen-users] Re: [Xen-devel] ARP problems with xen = 4.0 with pvops kernel >> >> 2.6.32.15 >> >> To: "Boris Derzhavets" <[3]bderzhavets@yahoo.com> >> >> Cc: "Jeremy Fitzhardinge" <[4]jeremy@goop.org>, [5]xen-devel@li= sts.xensource.com, >> >> [6]luis.silva@axiomasoft.pt, [7]xen-users@lists.xensource.com >> >> Date: Wednesday, June 9, 2010, 8:54 AM >> >> >> >> On Wed, Jun 09, 2010 at 05:47:42AM -0700, Boris Derzhavets wrot= e: >> >> > I was able to virt-install F13 PV DomU in nographics mode = under Xen >> >> > 4.0.1-rc2-pre (2.6.32.15 pvops c2cb3df04eb3ff68d0de102b2ac= acc9b8616e659) >> >> > at the point of extracting data from Apache mirror at Dom0= on top of >> >> > Ubuntu 10.04 ( text console mode message) >> >> > ------------------------------------------------- >> >> > 2 extracting cpio errors. Bad Magic >> >> > ------------------------------------------------- >> >> > However, virt-install proceeds further to promt "set up VN= C at DomU" >> >> > and completed successfully. >> >> > VNC mode cannot pass through this extractions. It just han= gs. >> >> > >> >> >> >> Yeah, there's something weird going on.. >> >> >> >> During the weekend I *think* I was successfully able to install= guests >> >> when they didn't have vfb set up at all.. but when I set up vfb= (ie. used virt-manager) >> >> the VM's started acting weird.. network problems, and problems = in general, >> >> VM's freezing.. >> >> >> >> I haven't had time to confirm that yet.. >> >> >> >> -- Pasi >> >> >> >> > Boris. >> >> > >> >> > --- On Mon, 6/7/10, Pasi K=E4rkk=E4inen <[1][8]pasik@iki.f= i> wrote: >> >> > >> >> > From: Pasi K=E4rkk=E4inen <[2][9]pasik@iki.fi> >> >> > Subject: Re: [Xen-users] Re: [Xen-devel] ARP problems wi= th xen 4.0 with >> >> > pvops kernel 2.6.32.15 >> >> > To: "Boris Derzhavets" <[3][10]bderzhavets@yahoo.com> >> >> > Cc: "Jeremy Fitzhardinge" <[4][11]jeremy@goop.org>, >> >> > [5][12]xen-devel@lists.xensource.com, [6][13]luis.silva@= axiomasoft.pt, >> >> > [7][14]xen-users@lists.xensource.com >> >> > Date: Monday, June 7, 2010, 3:55 AM >> >> > >> >> > On Sun, Jun 06, 2010 at 11:54:11AM -0700, Boris Derzhave= ts wrote: >> >> > > Virt-install hangs attempting to retrieve updates.i= mg from Apache >> >> > Mirror >> >> > > setup at Dom0 >> >> > > with kernel 2.6.32.15 >> >> > > It doesn't happen with 2.6.32.10 (12,14 final). >> >> > > Environment Xen 4.0 Dom0 on top Ubuntu 10.04 Server= . Libvirt is >> >> > 0.8.0 . >> >> > > Attempting to virt-install F13 PV DomU in vnc mode= . >> >> > > >> >> > > I believe that builds are consistent. >> >> > > Runtime behavior is the same for .10, .14, .15. See= ms to be >> >> > communicating >> >> > > problem between DomU and Dom0 during HTTP download. >> >> > > >> >> > >> >> > I'm seeing PV domU network issues aswell.. when running = Xen 4.0.0 on >> >> > Fedora 13. >> >> > I'll have to dig more into it.. >> >> > >> >> > -- Pasi >> >> > >> >> > > Boris. >> >> > > >> >> > > --- On Sun, 6/6/10, Jeremy Fitzhardinge <[1][8][15]= jeremy@goop.org> wrote: >> >> > > >> >> > > From: Jeremy Fitzhardinge <[2][9][16]jeremy@goop.= org> >> >> > > Subject: Re: [Xen-users] Re: [Xen-devel] ARP prob= lems with xen >> >> > 4.0 with >> >> > > pvops kernel 2.6.32.15 >> >> > > To: "Boris Derzhavets" <[3][10][17]bderzhavets@ya= hoo.com> >> >> > > Cc: [4][11][18]luis.silva@axiomasoft.pt, >> >> > [5][12][19]xen-devel@lists.xensource.com, >> >> > > [6][13][20]xen-users@lists.xensource.com >> >> > > Date: Sunday, June 6, 2010, 12:43 PM >> >> > > >> >> > > On 06/06/2010 03:19 AM, Boris Derzhavets wrote: >> >> > > > Network issues when working with DomUs in 2.6.3= 2.14 and finally >> >> > been >> >> > > > fixed, >> >> > > > seem to appear again in 2.6.32.15. Reverting to= back to >> >> > xen/stable - >> >> > > > 2.6.32.10 >> >> > > > works as a fix again. >> >> > > > >> >> > > >> >> > > There are no substantial differences between 2.6.= 32.14 and .15. >> >> > If >> >> > > there are any differences in behaviour between th= em, then I'd >> >> > suspect >> >> > > some inconsistency from boot to boot, or in your = kernel build >> >> > process. >> >> > > >> >> > > J >> >> > > >> >> > > > >> >> > > > Boris >> >> > > > >> >> > > > --- On *Thu, 6/3/10, Lu=EDs Silva >> >> > /<[1][7][14][21]luis.silva@axiomasoft.pt>/* >> >> > > wrote: >> >> > > > >> >> > > > >> >> > > > From: Lu=EDs Silva <[2][8][15][22]luis.silv= a@axiomasoft.pt> >> >> > > > Subject: Re: [Xen-users] Re: [Xen-devel] AR= P problems with >> >> > xen 4.0 >> >> > > > with pvops kernel >> >> > > > To: "Boris Derzhavets" <[3][9][16][23]bderz= havets@yahoo.com> >> >> > > > Cc: "Jeremy Fitzhardinge" <[4][10][17][24]j= eremy@goop.org>, >> >> > > > [5][11][18][25]xen-devel@lists.xensource.co= m, >> >> > [6][12][19][26]xen-users@lists.xensource.com >> >> > > > Date: Thursday, June 3, 2010, 6:20 AM >> >> > > > >> >> > > > Hello, >> >> > > > >> >> > > > Thanks for the suggestion, xen/stable works= ok for me. Only >> >> > > > problem is that I have to disable offload d= o get dhcp to >> >> > work on >> >> > > > domU, but the problem I described before do= esn't exist in >> >> > this >> >> > > > kernel. Later today I'm going to try a prev= ious build I >> >> > have based >> >> > > > on stable-2.6.32.x (2.6.32.13) to check if = it already had >> >> > this >> >> > > > problem or not and I'll post the results. >> >> > > > >> >> > > > Lu=EDs >> >> > > > >> >> > > > On Wed, 2010-06-02 at 12:26 -0700, Boris De= rzhavets wrote: >> >> > > >> Could you,please, build and try 2.6.32.10 = ( xen/stable) ? >> >> > > >> >> >> > > >> Boris. >> >> > > >> >> >> > > >> --- On *Wed, 6/2/10, Lu=EDs Silva >> >> > > **/<[7][13][20][27]luis.silva@axiomasoft.pt>/* >> >> > > >> wrote: >> >> > > >> >> >> > > >> >> >> > > >> From: Lu=EDs Silva <[8][14][21][28]lui= s.silva@axiomasoft.pt> >> >> > > >> Subject: [Xen-users] Re: [Xen-devel] A= RP problems with >> >> > xen >> >> > > >> 4.0 with pvops kernel >> >> > > >> To: "Jeremy Fitzhardinge" <[9][15][22]= [29]jeremy@goop.org> >> >> > > >> Cc: [10][16][23][30]xen-devel@lists.xe= nsource.com, >> >> > > [11][17][24][31]xen-users@lists.xensource.com >> >> > > >> Date: Wednesday, June 2, 2010, 2:53 PM >> >> > > >> >> >> > > >> Hello, >> >> > > >> >> >> > > >> On Wed, 2010-06-02 at 09:06 -0700, Jer= emy Fitzhardinge >> >> > wrote: >> >> > > >>> On 06/02/2010 01:47 AM, Lu=EDs Silva = wrote: >> >> > > >>> > Hello, >> >> > > >>> > >> >> > > >>> > I'm using the latest stable-2.6.32.= x. I already >> >> > tried >> >> > > "ethtool -K >> >> > > >>> > tx off", but that didn't m= ake any >> >> > difference. >> >> > > Also, this only >> >> > > >>> > happen with pv, in hvm mode all wor= ks ok and the >> >> > domU sees >> >> > > the arp >> >> > > >>> > messages... >> >> > > >>> >> >> > > >>> Yes, ARP is a new twist on network pr= oblems. I'm >> >> > guessing >> >> > > you're using >> >> > > >>> hvm without stubdoms, which means tha= t its networking >> >> > > originates from >> >> > > >>> qemu within dom0, whereas PV and HVM+= stubdom comes >> >> > via >> >> > > netback. >> >> > > >>> >> >> > > >>> >> >> > > >> Yes, when I mentioned hvm I was talkin= g about hvm >> >> > without >> >> > > >> stubdoms. I haven't tried those yet. >> >> > > >>> But aside from that, I'm stumped. Ar= e you running >> >> > any >> >> > > firewalls on >> >> > > >>> either side? Can you try disabling = all the offloads >> >> > (tx, >> >> > > rx, gso, tso) >> >> > > >>> on all the relevent interfaces (bridg= e, netback, >> >> > within the >> >> > > guest) and >> >> > > >>> see if that changes anything? >> >> > > >>> >> >> > > >>> J >> >> > > >>> >> >> > > >>> >> >> > > >> >> >> > > >> Ok, this is the bridge interface: >> >> > > >> >> >> > > >> brctl show >> >> > > >> bridge name bridge id STP en= abled >> >> > interfaces >> >> > > >> virbr0 8000.feffffffffff no = vif1.0 >> >> > > >> >> >> > > >> ifconfig virbr0 >> >> > > >> virbr0 Link encap:Ethernet HWaddr >> >> > c2:ef:67:2b:a4:23 >> >> > > >> inet addr:192.168.120.254 >> >> > Bcast:192.168.120.255 >> >> > > Mask:255.255.255.0 >> >> > > >> inet6 addr: fe80::c0ef:67ff:= fe2b:a423/64 >> >> > Scope:Link >> >> > > >> UP BROADCAST RUNNING MULTICA= ST MTU:1500 >> >> > Metric:1 >> >> > > >> RX packets:0 errors:0 droppe= d:0 overruns:0 >> >> > frame:0 >> >> > > >> TX packets:25 errors:0 dropp= ed:0 overruns:0 >> >> > > carrier:0 >> >> > > >> collisions:0 txqueuelen:0 >> >> > > >> RX bytes:0 (0.0 >> >> > > >> B) >> >> > > >> TX bytes:4662 (4.6 KB) >> >> > > >> >> >> > > >> >> >> > > >> >> >> > > >> I'm not using firewall other than the = rules defined by >> >> > > >> libvirt. DomU has no firewall and the = rules in dom0 >> >> > are only >> >> > > >> these (virbr0 is natted to the outside= , virbr1 is >> >> > routed. The >> >> > > >> result is the same in either one of th= em): >> >> > > >> >> >> > > >> sudo iptables -L -n -v >> >> > > >> Chain INPUT (policy ACCEPT 241K packet= s, 53M bytes) >> >> > > >> pkts bytes target prot opt in = out source >> >> > > destination >> >> > > >> 0 0 ACCEPT udp -- virbr1= * >> >> > 0.0.0.0/0 >> >> > > 0.0.0.0/0 udp dpt:53 >> >> > > >> 0 0 ACCEPT tcp -- virbr1= * >> >> > 0.0.0.0/0 >> >> > > 0.0.0.0/0 tcp dpt:53 >> >> > > >> >> >> > > >> >> >> > > >> 0 0 ACCEPT udp -- virbr1= * >> >> > 0.0.0.0/0 >> >> > > 0.0.0.0/0 udp dpt:67 >> >> > > >> 0 0 ACCEPT tcp -- virbr1= * >> >> > 0.0.0.0/0 >> >> > > 0.0.0.0/0 tcp dpt:67 >> >> > > >> 8 515 ACCEPT udp -- virbr0= * >> >> > 0.0.0.0/0 >> >> > > 0.0.0.0/0 udp dpt:53 >> >> > > >> 0 0 >> >> > > >> >> >> > > >> ACCEPT tcp -- virbr0 * 0.= 0.0.0/0 >> >> > > 0.0.0.0/0 tcp dpt:53 >> >> > > >> 0 0 ACCEPT udp -- virbr0= * >> >> > 0.0.0.0/0 >> >> > > 0.0.0.0/0 udp dpt:67 >> >> > > >> 0 0 ACCEPT tcp -- virbr0= * >> >> > 0.0.0.0/0 >> >> > > 0.0.0.0/0 tcp dpt:67 >> >> > > >> >> >> > > >> Chain FORWARD (policy ACCEPT 0 packets= , 0 bytes) >> >> > > >> pkts bytes target >> >> > > >> prot >> >> > > >> opt in out source = destination >> >> > > >> 0 0 ACCEPT all -- * = virbr1 >> >> > 0.0.0.0/0 >> >> > > 192.168.121.0/24 >> >> > > >> 0 0 ACCEPT all -- virbr1= * >> >> > > 192.168.121.0/24 0.0.0.0/0 >> >> > > >> 0 0 ACCEPT all -- virbr1= virbr1 >> >> > 0.0.0.0/0 >> >> > > >> >> > > >> >> >> > > >> 0.0.0.0/0 >> >> > > >> 0 0 REJECT all -- * = virbr1 >> >> > 0.0.0.0/0 >> >> > > 0.0.0.0/0 reject-with icmp-port-u= nreachable >> >> > > >> 0 0 REJECT all -- virbr1= * >> >> > 0.0.0.0/0 >> >> > > 0.0.0.0/0 reject-with icmp-port-u= nreachable >> >> > > >> 13 3448 ACCEPT all -- * = virbr0 >> >> > 0.0.0.0/0 >> >> > > 192.168.120.0/24 >> >> > > >> state >> >> > > >> RELATED,ESTABLISHED >> >> > > >> 16 1374 ACCEPT all -- virbr0= * >> >> > > 192.168.120.0/24 0.0.0.0/0 >> >> > > >> 0 0 ACCEPT all -- virbr0= virbr0 >> >> > 0.0.0.0/0 >> >> > > 0.0.0.0/0 >> >> > > >> 0 0 REJECT all -- * = virbr0 >> >> > 0.0.0.0/0 >> >> > > 0.0.0.0/0 reject-with icmp-port-u= nreachable >> >> > > >> 0 0 REJECT all -- >> >> > > >> virbr0 >> >> > > >> * 0.0.0.0/0 0.0.0.0/= 0 >> >> > reject-with >> >> > > icmp-port-unreachable >> >> > > >> >> >> > > >> Chain OUTPUT (policy ACCEPT 233K packe= ts, 27M bytes) >> >> > > >> pkts bytes target prot opt in = out source >> >> > > destination >> >> > > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > > >> And these are the various offload para= meters as set at >> >> > boot: >> >> > > >> >> >> > > >> Offload parameters for virbr0: >> >> > > >> rx-checksumming: on >> >> > > >> tx-checksumming: on >> >> > > >> scatter-gather: on >> >> > > >> tcp-segmentation-offload: on >> >> > > >> udp-fragmentation-offload: on >> >> > > >> generic-segmentation-offload: on >> >> > > >> generic-receive-offload: off >> >> > > >> large-receive-offload: off >> >> > > >> >> >> > > >> Offload parameters for vif1.0: >> >> > > >> rx-checksumming: on >> >> > > >> tx-checksumming: on >> >> > > >> scatter-gather: on >> >> > > >> tcp-segmentation-offload: on >> >> > > >> udp-fragmentation-offload: off >> >> > > >> generic-segmentation-offload: on >> >> > > >> generic-receive-offload: off >> >> > > >> large-receive-offload: off >> >> > > >> >> >> > > >> Offload parameters for eth0: >> >> > > >> rx-checksumming: on >> >> > > >> tx-checksumming: on >> >> > > >> scatter-gather: on >> >> > > >> tcp-segmentation-offload: on >> >> > > >> udp-fragmentation-offload: off >> >> > > >> generic-segmentation-offload: off >> >> > > >> generic-receive-offload: off >> >> > > >> large-receive-offload: off >> >> > > >> >> >> > > >> >> >> > > >> >> >> > > >> To disable all checksuming I run the f= ollowing >> >> > commands: >> >> > > >> dom0: >> >> > > >> >> >> > > >> sudo ethtool -K virbr0 tx off sg off t= so off gso off >> >> > gro off >> >> > > >> sudo ethtool -K vif1.0 tx off sg off t= so off gso off >> >> > gro off >> >> > > >> >> >> > > >> >> >> > > >> domU >> >> > > >> >> >> > > >> sudo ethtool -K eth0 tx off sg off tso= off gso off gro >> >> > off >> >> > > >> >> >> > > >> >> >> > > >> >> >> > > >> This managed to get all parameter to o= ff in the >> >> > mentioned >> >> > > >> interfaces, but unfortunately the resu= lt is the same. >> >> > The arp >> >> > > >> requests get to vif1.0, but not to eth= 0 on the domU. >> >> > > >> >> >> > > >> sudo tcpdump -i vif1.0 -n -vv arp >> >> > > >> tcpdump: WARNING: vif1.0: no IPv4 addr= ess assigned >> >> > > >> tcpdump: listening on vif1.0, link-typ= e EN10MB >> >> > (Ethernet), >> >> > > capture size 96 bytes >> >> > > >> 19:43:51.233378 ARP, Ethernet (len 6),= IPv4 (len 4), >> >> > Request >> >> > > who-has 192.168.120.1 tell 192.168.120.254, lengt= h 28 >> >> > > >> 19:43:52.233164 ARP, Ethernet (len 6),= IPv4 (len 4), >> >> > Request >> >> > > who-has 192.168.120.1 tell 192.168.120.254, lengt= h 28 >> >> > > >> 19:43:53.233166 ARP, Ethernet (len 6),= IPv4 (len 4), >> >> > Request >> >> > > who-has 192.168.120.1 tell 192.168.120.254, lengt= h 28 >> >> > > >> 19:43:54.684214 ARP, Ethernet (len 6),= IPv4 (len 4), >> >> > Request >> >> > > who-has 192.168.120.1 tell 192.168.120.254, lengt= h 28 >> >> > > >> 19:43:55.684218 ARP, Ethernet (len 6),= IPv4 (len 4), >> >> > Request >> >> > > who-has 192.168.120.1 tell 192.168.120.254, lengt= h 28 >> >> > > >> 19:43:56.684232 ARP, Ethernet (len 6),= IPv4 (len 4), >> >> > Request >> >> > > who-has 192.168.120.1 tell 192.168.120.254, lengt= h 28 >> >> > > >> >> >> > > >> >> >> > > >> >> >> > > >> I hope this information is enough. If = I can provide >> >> > anything >> >> > > >> else to help debug or test, please jus= t ask! ;) >> >> > > >> >> >> > > >> Thanks in advance, >> >> > > >> Lu=EDs >> >> > > >> >> >> > > >>> > >> >> > > >>> > Thanks, >> >> > > >>> > Lu=EDs >> >> > > >>> > >> >> > > >>> > On Tue, 2010-06-01 at 18:20 -0700, = Jeremy >> >> > Fitzhardinge >> >> > > wrote: >> >> > > >>> >> On 06/01/2010 05:38 PM, Lu=EDs Sil= va wrote: >> >> > > >>> >> > Hello, >> >> > > >>> >> > >> >> > > >>> >> > Finally I managed to get a xen 4= .0 working on >> >> > ubuntu >> >> > > 10.04 with pvops >> >> > > >>> >> > kernel and libvirt. However I am= having some >> >> > problems >> >> > > with >> >> > > >>> >> > networking... after initial inst= allation with >> >> > > netinstall image in hvm >> >> > > >>> >> > mode, when I transform the vm in= xen pv (via >> >> > pygrub >> >> > > with the current >> >> > > >>> >> > ubuntu kernel), networking start= Ed to act >> >> > weird... >> >> > > >>> >> > >> >> > > >>> >> > Basically I'm not using a networ= k script from >> >> > xen. I >> >> > > define a bridge >> >> > > >>> >> > (manually or via libvirt, the re= sult is the >> >> > same) and I >> >> > > use vif-bridge >> >> > > >>> >> > to connect the vif to it. But no= w the weird part >> >> > comes: >> >> > > I can >> >> > > >>> >> > communicate from domU to dom0, b= ut not the other >> >> > way >> >> > > >>> around, >> >> > > >>> unless I >> >> > > >>> >> > keep a ping running from domU to= dom0... That's >> >> > right, >> >> > > weird... while >> >> > > >>> >> > trying the ping from dom0 to dom= U, I used >> >> > tcpdump both >> >> > > on the bridge, >> >> > > >>> >> > on the vif and on the eth0 in th= e domU. The arp >> >> > packets >> >> > > never get to >> >> > > >>> >> > domU, but they appear both in th= e bridge and the >> >> > vif >> >> > > sniff's... >> >> > > >>> >> >> >> > > >>> >> What version of kernel are you usi= ng in dom0 and >> >> > domU? >> >> > > There was a >> >> > > >>> >> netback bug which caused problems = with dom0<->domU >> >> > > communication, but it >> >> > > >>> >> has been fixed for a while in 2.6.= 32 (but only >> >> > recently >> >> > > in .31). The >> >> > > >>> >> workaround is to disable tx checks= um offload on >> >> > your >> >> > > bridge (ethtool -K >> >> > > >>> >> tx off). >> >> > > >>> >> >> >> > > >>> >> J >> >> > > >>> >> >> >> > > >>> >> > >> >> > > >>> >> > Here is the bridge: >> >> > > >>> >> > ifconfig virbr0 >> >> > > >>> >> > virbr0 Link encap:Ethernet H= Waddr >> >> > > fe:ff:ff:ff:ff:ff >> >> > > >>> >> > >> >> > > >>> >> >> > > >>> inet addr:192.168.120.254 Bcast:192= .168.120.255 >> >> > > Mask:255.255.255.0 >> >> > > >>> >> > inet6 addr: >> >> > fe80::7cee:4bff:fe82:e63f/64 >> >> > > Scope:Link >> >> > > >>> >> > UP BROADCAST RUNNING M= ULTICAST >> >> > MTU:1500 >> >> > > Metric:1 >> >> > > >>> >> > RX packets:16 errors:0= dropped:0 >> >> > overruns:0 >> >> > > frame:0 >> >> > > >>> >> > TX packets:226 errors:= 0 dropped:0 >> >> > overruns:0 >> >> > > carrier:0 >> >> > > >>> >> > collisions:0 txqueuele= n:0 >> >> > > >>> >> > RX bytes:952 (952.0 B)= TX bytes:13953 >> >> > (13.9 >> >> > > KB) >> >> > > >>> >> > >> >> > > >>> >> > >> >> > > >>> >> > brctl show >> >> > > >>> >> > bridge name bridge id = STP enabled >> >> > > interfaces >> >> > > >>> >> > virbr0 8000.feffffffffff = no >> >> > vif5.0 >> >> > > >>> >> > >> >> > > >>> >> > >> >> > > >>> >> > tcpdump -i virbr0 -vv -n >> >> > > >>> >> > tcpdump: listening on virbr0, li= nk-type EN10MB >> >> > > (Ethernet), capture size 96 bytes >> >> > > >>> >> > 01:31:25.945151 IP (tos 0x0, ttl= 64, id 0, >> >> > offset 0, >> >> > > flags [DF], >> >> > > >>> proto ICMP (1), >> >> > > >>> length 84) >> >> > > >>> >> > 192.168.120.254 > 192.168.12= 0.1: ICMP echo >> >> > request, >> >> > > id 10317, seq 1, length 64 >> >> > > >>> >> > 01:31:26.945361 IP (tos 0x0, ttl= 64, id 0, >> >> > offset 0, >> >> > > flags [DF], proto ICMP (1), length 84) >> >> > > >>> >> > 192.168.120.254 > 192.168.12= 0.1: ICMP echo >> >> > request, >> >> > > id 10317, seq 2, length 64 >> >> > > >>> >> > 01:31:27.945420 IP (tos 0x0, ttl= 64, id 0, >> >> > offset 0, >> >> > > flags [DF], proto ICMP (1), length 84) >> >> > > >>> >> > 192.168.120.254 > 192.168.12= 0.1: ICMP echo >> >> > request, >> >> > > id 10317, seq 3, length 64 >> >> > > >>> >> > 01:31:28.945362 IP (tos 0x0, ttl= 64, id 0, >> >> > offset 0, >> >> > > flags [DF], proto ICMP (1), length 84) >> >> > > >>> >> > 192.168.120.254 > 192.168.12= 0.1: ICMP echo >> >> > request, >> >> > > id 10317, seq 4, length 64 >> >> > > >>> >> > 01:31:29.945364 IP (tos 0x0, ttl= 64, id 0, >> >> > offset 0, >> >> > > flags [DF], proto ICMP (1), length 84) >> >> > > >>> >> > 192.168.120.254 > 192.168.12= 0.1: ICMP echo >> >> > request, >> >> > > id 10317, >> >> > > >>> seq 5, length >> >> > > >>> 64 >> >> > > >>> >> > 01:31:30.944300 ARP, Ethernet (l= en 6), IPv4 (len >> >> > 4), >> >> > > Request who-has 192.168.120.1 tell 192.168.120.25= 4, length 28 >> >> > > >>> >> > 01:31:30.945359 IP (tos 0x0, ttl= 64, id 0, >> >> > offset 0, >> >> > > flags [DF], proto ICMP (1), length 84) >> >> > > >>> >> > 192.168.120.254 > 192.168.12= 0.1: ICMP echo >> >> > request, >> >> > > id 10317, seq 6, length 64 >> >> > > >>> >> > 01:31:31.944297 ARP, Ethernet (l= en 6), IPv4 (len >> >> > 4), >> >> > > Request who-has 192.168.120.1 tell 192.168.120.25= 4, length 28 >> >> > > >>> >> > 01:31:31.945444 IP (tos 0x0, ttl= 64, id 0, >> >> > offset 0, >> >> > > flags [DF], proto ICMP (1), length 84) >> >> > > >>> >> > 192.168.120.254 > 192.168.12= 0.1: ICMP echo >> >> > request, >> >> > > id 10317, seq 7, length 64 >> >> > > >>> >> > 01:31:32.944294 ARP, Ethernet (l= en 6), IPv4 (len >> >> > 4), >> >> > > Request who-has 192.168.120.1 tell 192.168.120.25= 4, length 28 >> >> > > >>> >> > 01:31:32.945401 IP (tos 0x0, ttl= 64, id 0, >> >> > offset 0, >> >> > > flags [DF], proto ICMP (1), length 84) >> >> > > >>> >> > >> >> > > >>> >> >> > > >>> 192.168.120.254 > 192.168.120.1: ICM= P echo request, >> >> > id >> >> > > 10317, seq 8, length 64 >> >> > > >>> >> > 01:31:33.947293 ARP, Ethernet (l= en 6), IPv4 (len >> >> > 4), >> >> > > Request who-has 192.168.120.1 tell 192.168.120.25= 4, length 28 >> >> > > >>> >> > 01:31:34.947373 ARP, Ethernet (l= en 6), IPv4 (len >> >> > 4), >> >> > > Request who-has 192.168.120.1 tell 192.168.120.25= 4, length 28 >> >> > > >>> >> > 01:31:35.947353 ARP, Ethernet (l= en 6), IPv4 (len >> >> > 4), >> >> > > Request who-has 192.168.120.1 tell 192.168.120.25= 4, length 28 >> >> > > >>> >> > 01:31:37.948352 ARP, Ethernet (l= en 6), IPv4 (len >> >> > 4), >> >> > > Request who-has 192.168.120.1 tell 192.168.120.25= 4, length 28 >> >> > > >>> >> > 01:31:38.948399 ARP, Ethernet (l= en 6), IPv4 (len >> >> > 4), >> >> > > Request who-has 192.168.120.1 tell 192.168.120.25= 4, length 28 >> >> > > >>> >> > 01:31:39.948376 ARP, Ethernet (l= en 6), IPv4 (len >> >> > 4), >> >> > > Request who-has 192.168.120.1 tell 192.168.120.25= 4, length 28 >> >> > > >>> >> > 01:31:40.949356 ARP, Ethernet (l= en 6), IPv4 (len >> >> > 4), >> >> > > Request >> >> > > >>> who-has >> >> > > >>> 192.168.120.1 tell 192.168.120.254, = length 28 >> >> > > >>> >> > >> >> > > >>> >> > >> >> > > >>> >> > tcpdump -i vif5.0 -vv -n >> >> > > >>> >> > tcpdump: WARNING: vif5.0: no IPv= 4 address >> >> > assigned >> >> > > >>> >> > tcpdump: listening on vif5.0, li= nk-type EN10MB >> >> > > (Ethernet), capture size 96 bytes >> >> > > >>> >> > 01:32:19.956358 ARP, Ethernet (l= en 6), IPv4 (len >> >> > 4), >> >> > > Request who-has 192.168.120.1 tell 192.168.120.25= 4, length 28 >> >> > > >>> >> > 01:32:20.956358 ARP, Ethernet (l= en 6), IPv4 (len >> >> > 4), >> >> > > Request who-has 192.168.120.1 tell 192.168.120.25= 4, length 28 >> >> > > >>> >> > 01:32:21.956359 ARP, Ethernet (l= en 6), IPv4 (len >> >> > 4), >> >> > > Request who-has 192.168.120.1 tell 192.168.120.25= 4, length 28 >> >> > > >>> >> > 01:32:23.957311 ARP, Ethernet (l= en 6), IPv4 (len >> >> > 4), >> >> > > Request who-has 192.168.120.1 tell 192.168.120.25= 4, length 28 >> >> > > >>> >> > 01:32:24.957312 ARP, Ethernet (l= en 6), IPv4 (len >> >> > 4), >> >> > > Request who-has 192.168.120.1 tell 192.168.120.25= 4, length >> >> > > >>> 28 >> >> > > >>> >> > >> >> > > >>> 01:32:25.957359 ARP, Ethernet (len 6= ), IPv4 (len 4), >> >> > > Request who-has 192.168.120.1 tell 192.168.120.25= 4, length 28 >> >> > > >>> >> > 01:32:27.958360 ARP, Ethernet (l= en 6), IPv4 (len >> >> > 4), >> >> > > Request who-has 192.168.120.1 tell 192.168.120.25= 4, length 28 >> >> > > >>> >> > 01:32:28.958310 ARP, Ethernet (l= en 6), IPv4 (len >> >> > 4), >> >> > > Request who-has 192.168.120.1 tell 192.168.120.25= 4, length 28 >> >> > > >>> >> > 01:32:29.958362 ARP, Ethernet (l= en 6), IPv4 (len >> >> > 4), >> >> > > Request who-has 192.168.120.1 tell 192.168.120.25= 4, length 28 >> >> > > >>> >> > >> >> > > >>> >> > >> >> > > >>> >> > >> >> > > >>> >> > Forwarding and iptables don't se= em to be the >> >> > problem, >> >> > > because if I >> >> > > >>> >> > initiate a ping from domU (at th= e same time as >> >> > the >> >> > > failing one from >> >> > > >>> >> > dom0), the ping in dom0 starts t= o work. As soon >> >> > as I >> >> > > stop the ping in >> >> > > >>> >> > domU, the one in dom0 starts fai= ling again... >> >> > > >>> >> > >> >> > > >>> >> > Is anyone having the same >> >> > > >>> problem? Is this a bug >> >> > > >>> in the kernel? In >> >> > > >>> >> > dom0 or domU? >> >> > > >>> >> > >> >> > > >>> >> > Thanks in advance, >> >> > > >>> >> > Lu=EDs >> >> > > >>> >> > >> >> > > >>> >> > >> >> > > >>> >> > ________________________________= _______________ >> >> > > >>> >> > Xen-devel mailing list >> >> > > >>> >> > [12][18][25][32]Xen-devel@lists.= xensource.com >> >> > > >> >> > > >> >> > > >>> >> > [15][21][28][35]http://lists.xen= source.com/xen-devel >> >> > > >>> >> > >> >> > > >>> >> >> >> > > >>> >> >> >> > > >>> >> __________________________________= _____________ >> >> > > >>> >> Xen-devel mailing list >> >> > > >>> >> [16][22][29][36]Xen-devel@lists.xe= nsource.com >> >> > > >> >> > > >> >> > > >>> >> [19][25][32][39]http://lists.xenso= urce.com/xen-devel >> >> > > >>> >> >> >> > > >>> >> >> >> > > >>> > >> >> > > >>> >> >> > > >>> >> >> > > >>> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > > >> -----Inline Attachment Follows----- >> >> > > >> >> >> > > >> ______________________________________= _________ >> >> > > >> Xen-users mailing list >> >> > > >> [20][26][33][40]Xen-users@lists.xensou= rce.com >> >> > > >> [21][27][34][41]http://lists.xensource= .com/xen-users >> >> > > >> >> >> > > >> >> >> > > > >> >> > > > >> >> > > > -----Inline Attachment Follows----- >> >> > > > >> >> > > > ___________________________________________= ____ >> >> > > > Xen-users mailing list >> >> > > > [22][28][35][42]Xen-users@lists.xensource.c= om >> >> > > > >> >> > > > [24][30][37][44]http://lists.xensource.com/= xen-users >> >> > > > >> >> > > > >> >> > > >> >> > > References >> >> > > >> >> > > Visible links >> >> > > 1. file:///mc/compose?to=3D[31][38][45]luis.silva@a= xiomasoft.pt >> >> > > 2. file:///mc/compose?to=3D[32][39][46]luis.silva@a= xiomasoft.pt >> >> > > 3. file:///mc/compose?to=3D[33][40][47]bderzhavets@= yahoo.com >> >> > > 4. file:///mc/compose?to=3D[34][41][48]jeremy@goop.= org >> >> > > 5. file:///mc/compose?to=3D[35][42][49]xen-devel@li= sts.xensource.com >> >> > > 6. file:///mc/compose?to=3D[36][43][50]xen-users@li= sts.xensource.com >> >> > > 7. file:///mc/compose?to=3D[37][44][51]luis.silva@a= xiomasoft.pt >> >> > > 8. file:///mc/compose?to=3D[38][45][52]luis.silva@a= xiomasoft.pt >> >> > > 9. file:///mc/compose?to=3D[39][46][53]jeremy@goop.= org >> >> > > 10. file:///mc/compose?to=3D[40][47][54]xen-devel@li= sts.xensource.com >> >> > > 11. file:///mc/compose?to=3D[41][48][55]xen-users@li= sts.xensource.com >> >> > > 12. file:///mc/compose?to=3D[42][49][56]Xen-devel@li= sts.xensource.com >> >> > > 13. file:///mc/compose?to=3D[43][50][57]Xen-devel@li= sts.xensource.com >> >> > > 14. file:///mc/compose?to=3D[44][51][58]Xen-devel@li= sts.xensource.com >> >> > > 15. [45][52][59]http://lists.xensource.com/xen-devel >> >> > > 16. file:///mc/compose?to=3D[46][53][60]Xen-devel@li= sts.xensource.com >> >> > > 17. file:///mc/compose?to=3D[47][54][61]Xen-devel@li= sts.xensource.com >> >> > > 18. file:///mc/compose?to=3D[48][55][62]Xen-devel@li= sts.xensource.com >> >> > > 19. [49][56][63]http://lists.xensource.com/xen-devel >> >> > > 20. file:///mc/compose?to=3D[50][57][64]Xen-users@li= sts.xensource.com >> >> > > 21. [51][58][65]http://lists.xensource.com/xen-users >> >> > > 22. file:///mc/compose?to=3D[52][59][66]Xen-users@li= sts.xensource.com >> >> > > 23. file:///mc/compose?to=3D[53][60][67]Xen-users@li= sts.xensource.com >> >> > > 24. [54][61][68]http://lists.xensource.com/xen-users >> >> > >> >> > > _______________________________________________ >> >> > > Xen-devel mailing list >> >> > > [55][62][69]Xen-devel@lists.xensource.com >> >> > > [56][63][70]http://lists.xensource.com/xen-devel >> >> > >> >> > _______________________________________________ >> >> > Xen-devel mailing list >> >> > [57][64][71]Xen-devel@lists.xensource.com >> >> > [58][65][72]http://lists.xensource.com/xen-devel >> >> > >> >> > References >> >> > >> >> > Visible links >> >> > 1. file:///mc/compose?to=3D[66][73]jeremy@goop.org >> >> > 2. file:///mc/compose?to=3D[67][74]jeremy@goop.org >> >> > 3. file:///mc/compose?to=3D[68][75]bderzhavets@yahoo.com >> >> > 4. file:///mc/compose?to=3D[69][76]luis.silva@axiomasoft.p= t >> >> > 5. file:///mc/compose?to=3D[70][77]xen-devel@lists.xensour= ce.com >> >> > 6. file:///mc/compose?to=3D[71][78]xen-users@lists.xensour= ce.com >> >> > 7. file:///mc/compose?to=3D[72][79]luis.silva@axiomasoft.p= t >> >> > 8. file:///mc/compose?to=3D[73][80]luis.silva@axiomasoft.p= t >> >> > 9. file:///mc/compose?to=3D[74][81]bderzhavets@yahoo.com >> >> > 10. file:///mc/compose?to=3D[75][82]jeremy@goop.org >> >> > 11. file:///mc/compose?to=3D[76][83]xen-devel@lists.xensour= ce.com >> >> > 12. file:///mc/compose?to=3D[77][84]xen-users@lists.xensour= ce.com >> >> > 13. file:///mc/compose?to=3D[78][85]luis.silva@axiomasoft.p= t >> >> > 14. file:///mc/compose?to=3D[79][86]luis.silva@axiomasoft.p= t >> >> > 15. file:///mc/compose?to=3D[80][87]jeremy@goop.org >> >> > 16. file:///mc/compose?to=3D[81][88]xen-devel@lists.xensour= ce.com >> >> > 17. file:///mc/compose?to=3D[82][89]xen-users@lists.xensour= ce.com >> >> > 18. file:///mc/compose?to=3D[83][90]Xen-devel@lists.xensour= ce.com >> >> > 19. file:///mc/compose?to=3D[84][91]Xen-devel@lists.xensour= ce.com >> >> > 20. file:///mc/compose?to=3D[85][92]Xen-devel@lists.xensour= ce.com >> >> > 21. [86][93]http://lists.xensource.com/xen-devel >> >> > 22. file:///mc/compose?to=3D[87][94]Xen-devel@lists.xensour= ce.com >> >> > 23. file:///mc/compose?to=3D[88][95]Xen-devel@lists.xensour= ce.com >> >> > 24. file:///mc/compose?to=3D[89][96]Xen-devel@lists.xensour= ce.com >> >> > 25. [90][97]http://lists.xensource.com/xen-devel >> >> > 26. file:///mc/compose?to=3D[91][98]Xen-users@lists.xensour= ce.com >> >> > 27. [92][99]http://lists.xensource.com/xen-users >> >> > 28. file:///mc/compose?to=3D[93][100]Xen-users@lists.xensou= rce.com >> >> > 29. file:///mc/compose?to=3D[94][101]Xen-users@lists.xensou= rce.com >> >> > 30. [95][102]http://lists.xensource.com/xen-users >> >> > 31. file:///mc/compose?to=3D[96][103]luis.silva@axiomasoft.= pt >> >> > 32. file:///mc/compose?to=3D[97][104]luis.silva@axiomasoft.= pt >> >> > 33. file:///mc/compose?to=3D[98][105]bderzhavets@yahoo.com >> >> > 34. file:///mc/compose?to=3D[99][106]jeremy@goop.org >> >> > 35. file:///mc/compose?to=3D[100][107]xen-devel@lists.xenso= urce.com >> >> > 36. file:///mc/compose?to=3D[101][108]xen-users@lists.xenso= urce.com >> >> > 37. file:///mc/compose?to=3D[102][109]luis.silva@axiomasoft= .pt >> >> > 38. file:///mc/compose?to=3D[103][110]luis.silva@axiomasoft= .pt >> >> > 39. file:///mc/compose?to=3D[104][111]jeremy@goop.org >> >> > 40. file:///mc/compose?to=3D[105][112]xen-devel@lists.xenso= urce.com >> >> > 41. file:///mc/compose?to=3D[106][113]xen-users@lists.xenso= urce.com >> >> > 42. file:///mc/compose?to=3D[107][114]Xen-devel@lists.xenso= urce.com >> >> > 43. file:///mc/compose?to=3D[108][115]Xen-devel@lists.xenso= urce.com >> >> > 44. file:///mc/compose?to=3D[109][116]Xen-devel@lists.xenso= urce.com >> >> > 45. [110][117]http://lists.xensource.com/xen-devel >> >> > 46. file:///mc/compose?to=3D[111][118]Xen-devel@lists.xenso= urce.com >> >> > 47. file:///mc/compose?to=3D[112][119]Xen-devel@lists.xenso= urce.com >> >> > 48. file:///mc/compose?to=3D[113][120]Xen-devel@lists.xenso= urce.com >> >> > 49. [114][121]http://lists.xensource.com/xen-devel >> >> > 50. file:///mc/compose?to=3D[115][122]Xen-users@lists.xenso= urce.com >> >> > 51. [116][123]http://lists.xensource.com/xen-users >> >> > 52. file:///mc/compose?to=3D[117][124]Xen-users@lists.xenso= urce.com >> >> > 53. file:///mc/compose?to=3D[118][125]Xen-users@lists.xenso= urce.com >> >> > 54. [119][126]http://lists.xensource.com/xen-users >> >> > 55. file:///mc/compose?to=3D[120][127]Xen-devel@lists.xenso= urce.com >> >> > 56. [121][128]http://lists.xensource.com/xen-devel >> >> > 57. file:///mc/compose?to=3D[122][129]Xen-devel@lists.xenso= urce.com >> >> > 58. [123][130]http://lists.xensource.com/xen-devel >> >> >> >> _______________________________________________ >> >> Xen-devel mailing list >> >> [124][131]Xen-devel@lists.xensource.com >> >> [125][132]http://lists.xensource.com/xen-devel >> >> >> >> References >> >> >> >> Visible links >> >> 1. file:///mc/compose?to=3D[133]pasik@iki.fi >> >> 2. file:///mc/compose?to=3D[134]pasik@iki.fi >> >> 3. file:///mc/compose?to=3D[135]bderzhavets@yahoo.com >> >> 4. file:///mc/compose?to=3D[136]jeremy@goop.org >> >> 5. file:///mc/compose?to=3D[137]xen-devel@lists.xensource.com >> >> 6. file:///mc/compose?to=3D[138]luis.silva@axiomasoft.pt >> >> 7. file:///mc/compose?to=3D[139]xen-users@lists.xensource.com >> >> 8. file:///mc/compose?to=3D[140]jeremy@goop.org >> >> 9. file:///mc/compose?to=3D[141]jeremy@goop.org >> >> 10. file:///mc/compose?to=3D[142]bderzhavets@yahoo.com >> >> 11. file:///mc/compose?to=3D[143]luis.silva@axiomasoft.pt >> >> 12. file:///mc/compose?to=3D[144]xen-devel@lists.xensource.com >> >> 13. file:///mc/compose?to=3D[145]xen-users@lists.xensource.com >> >> 14. file:///mc/compose?to=3D[146]luis.silva@axiomasoft.pt >> >> 15. file:///mc/compose?to=3D[147]luis.silva@axiomasoft.pt >> >> 16. file:///mc/compose?to=3D[148]bderzhavets@yahoo.com >> >> 17. file:///mc/compose?to=3D[149]jeremy@goop.org >> >> 18. file:///mc/compose?to=3D[150]xen-devel@lists.xensource.com >> >> 19. file:///mc/compose?to=3D[151]xen-users@lists.xensource.com >> >> 20. file:///mc/compose?to=3D[152]luis.silva@axiomasoft.pt >> >> 21. file:///mc/compose?to=3D[153]luis.silva@axiomasoft.pt >> >> 22. file:///mc/compose?to=3D[154]jeremy@goop.org >> >> 23. file:///mc/compose?to=3D[155]xen-devel@lists.xensource.com >> >> 24. file:///mc/compose?to=3D[156]xen-users@lists.xensource.com >> >> 25. file:///mc/compose?to=3D[157]Xen-devel@lists.xensource.com >> >> 26. file:///mc/compose?to=3D[158]Xen-devel@lists.xensource.com >> >> 27. file:///mc/compose?to=3D[159]Xen-devel@lists.xensource.com >> >> 28. [160]http://lists.xensource.com/xen-devel >> >> 29. file:///mc/compose?to=3D[161]Xen-devel@lists.xensource.com >> >> 30. file:///mc/compose?to=3D[162]Xen-devel@lists.xensource.com >> >> 31. file:///mc/compose?to=3D[163]Xen-devel@lists.xensource.com >> >> 32. [164]http://lists.xensource.com/xen-devel >> >> 33. file:///mc/compose?to=3D[165]Xen-users@lists.xensource.com >> >> 34. [166]http://lists.xensource.com/xen-users >> >> 35. file:///mc/compose?to=3D[167]Xen-users@lists.xensource.com >> >> 36. file:///mc/compose?to=3D[168]Xen-users@lists.xensource.com >> >> 37. [169]http://lists.xensource.com/xen-users >> >> 38. file:///mc/compose?to=3D[170]luis.silva@axiomasoft.pt >> >> 39. file:///mc/compose?to=3D[171]luis.silva@axiomasoft.pt >> >> 40. file:///mc/compose?to=3D[172]bderzhavets@yahoo.com >> >> 41. file:///mc/compose?to=3D[173]jeremy@goop.org >> >> 42. file:///mc/compose?to=3D[174]xen-devel@lists.xensource.com >> >> 43. file:///mc/compose?to=3D[175]xen-users@lists.xensource.com >> >> 44. file:///mc/compose?to=3D[176]luis.silva@axiomasoft.pt >> >> 45. file:///mc/compose?to=3D[177]luis.silva@axiomasoft.pt >> >> 46. file:///mc/compose?to=3D[178]jeremy@goop.org >> >> 47. file:///mc/compose?to=3D[179]xen-devel@lists.xensource.com >> >> 48. file:///mc/compose?to=3D[180]xen-users@lists.xensource.com >> >> 49. file:///mc/compose?to=3D[181]Xen-devel@lists.xensource.com >> >> 50. file:///mc/compose?to=3D[182]Xen-devel@lists.xensource.com >> >> 51. file:///mc/compose?to=3D[183]Xen-devel@lists.xensource.com >> >> 52. [184]http://lists.xensource.com/xen-devel >> >> 53. file:///mc/compose?to=3D[185]Xen-devel@lists.xensource.com >> >> 54. file:///mc/compose?to=3D[186]Xen-devel@lists.xensource.com >> >> 55. file:///mc/compose?to=3D[187]Xen-devel@lists.xensource.com >> >> 56. [188]http://lists.xensource.com/xen-devel >> >> 57. file:///mc/compose?to=3D[189]Xen-users@lists.xensource.com >> >> 58. [190]http://lists.xensource.com/xen-users >> >> 59. file:///mc/compose?to=3D[191]Xen-users@lists.xensource.com >> >> 60. file:///mc/compose?to=3D[192]Xen-users@lists.xensource.com >> >> 61. [193]http://lists.xensource.com/xen-users >> >> 62. file:///mc/compose?to=3D[194]Xen-devel@lists.xensource.com >> >> 63. [195]http://lists.xensource.com/xen-devel >> >> 64. file:///mc/compose?to=3D[196]Xen-devel@lists.xensource.com >> >> 65. [197]http://lists.xensource.com/xen-devel >> >> 66. file:///mc/compose?to=3D[198]jeremy@goop.org >> >> 67. file:///mc/compose?to=3D[199]jeremy@goop.org >> >> 68. file:///mc/compose?to=3D[200]bderzhavets@yahoo.com >> >> 69. file:///mc/compose?to=3D[201]luis.silva@axiomasoft.pt >> >> 70. file:///mc/compose?to=3D[202]xen-devel@lists.xensource.com >> >> 71. file:///mc/compose?to=3D[203]xen-users@lists.xensource.com >> >> 72. file:///mc/compose?to=3D[204]luis.silva@axiomasoft.pt >> >> 73. file:///mc/compose?to=3D[205]luis.silva@axiomasoft.pt >> >> 74. file:///mc/compose?to=3D[206]bderzhavets@yahoo.com >> >> 75. file:///mc/compose?to=3D[207]jeremy@goop.org >> >> 76. file:///mc/compose?to=3D[208]xen-devel@lists.xensource.com >> >> 77. file:///mc/compose?to=3D[209]xen-users@lists.xensource.com >> >> 78. file:///mc/compose?to=3D[210]luis.silva@axiomasoft.pt >> >> 79. file:///mc/compose?to=3D[211]luis.silva@axiomasoft.pt >> >> 80. file:///mc/compose?to=3D[212]jeremy@goop.org >> >> 81. file:///mc/compose?to=3D[213]xen-devel@lists.xensource.com >> >> 82. file:///mc/compose?to=3D[214]xen-users@lists.xensource.com >> >> 83. file:///mc/compose?to=3D[215]Xen-devel@lists.xensource.com >> >> 84. file:///mc/compose?to=3D[216]Xen-devel@lists.xensource.com >> >> 85. file:///mc/compose?to=3D[217]Xen-devel@lists.xensource.com >> >> 86. [218]http://lists.xensource.com/xen-devel >> >> 87. file:///mc/compose?to=3D[219]Xen-devel@lists.xensource.com >> >> 88. file:///mc/compose?to=3D[220]Xen-devel@lists.xensource.com >> >> 89. file:///mc/compose?to=3D[221]Xen-devel@lists.xensource.com >> >> 90. [222]http://lists.xensource.com/xen-devel >> >> 91. file:///mc/compose?to=3D[223]Xen-users@lists.xensource.com >> >> 92. [224]http://lists.xensource.com/xen-users >> >> 93. file:///mc/compose?to=3D[225]Xen-users@lists.xensource.com >> >> 94. file:///mc/compose?to=3D[226]Xen-users@lists.xensource.com >> >> 95. [227]http://lists.xensource.com/xen-users >> >> 96. file:///mc/compose?to=3D[228]luis.silva@axiomasoft.pt >> >> 97. file:///mc/compose?to=3D[229]luis.silva@axiomasoft.pt >> >> 98. file:///mc/compose?to=3D[230]bderzhavets@yahoo.com >> >> 99. file:///mc/compose?to=3D[231]jeremy@goop.org >> >> 100. file:///mc/compose?to=3D[232]xen-devel@lists.xensource.com >> >> 101. file:///mc/compose?to=3D[233]xen-users@lists.xensource.com >> >> 102. file:///mc/compose?to=3D[234]luis.silva@axiomasoft.pt >> >> 103. file:///mc/compose?to=3D[235]luis.silva@axiomasoft.pt >> >> 104. file:///mc/compose?to=3D[236]jeremy@goop.org >> >> 105. file:///mc/compose?to=3D[237]xen-devel@lists.xensource.com >> >> 106. file:///mc/compose?to=3D[238]xen-users@lists.xensource.com >> >> 107. file:///mc/compose?to=3D[239]Xen-devel@lists.xensource.com >> >> 108. file:///mc/compose?to=3D[240]Xen-devel@lists.xensource.com >> >> 109. file:///mc/compose?to=3D[241]Xen-devel@lists.xensource.com >> >> 110. [242]http://lists.xensource.com/xen-devel >> >> 111. file:///mc/compose?to=3D[243]Xen-devel@lists.xensource.com >> >> 112. file:///mc/compose?to=3D[244]Xen-devel@lists.xensource.com >> >> 113. file:///mc/compose?to=3D[245]Xen-devel@lists.xensource.com >> >> 114. [246]http://lists.xensource.com/xen-devel >> >> 115. file:///mc/compose?to=3D[247]Xen-users@lists.xensource.com >> >> 116. [248]http://lists.xensource.com/xen-users >> >> 117. file:///mc/compose?to=3D[249]Xen-users@lists.xensource.com >> >> 118. file:///mc/compose?to=3D[250]Xen-users@lists.xensource.com >> >> 119. [251]http://lists.xensource.com/xen-users >> >> 120. file:///mc/compose?to=3D[252]Xen-devel@lists.xensource.com >> >> 121. [253]http://lists.xensource.com/xen-devel >> >> 122. file:///mc/compose?to=3D[254]Xen-devel@lists.xensource.com >> >> 123. [255]http://lists.xensource.com/xen-devel >> >> 124. file:///mc/compose?to=3D[256]Xen-devel@lists.xensource.com >> >> 125. [257]http://lists.xensource.com/xen-devel >> >> >> > >> >> References >> >> Visible links >> 1. file:///mc/compose?to=3Dpasik@iki.fi >> 2. file:///mc/compose?to=3Dpasik@iki.fi >> 3. file:///mc/compose?to=3Dbderzhavets@yahoo.com >> 4. file:///mc/compose?to=3Djeremy@goop.org >> 5. file:///mc/compose?to=3Dxen-devel@lists.xensource.com >> 6. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 7. file:///mc/compose?to=3Dxen-users@lists.xensource.com >> 8. file:///mc/compose?to=3Dpasik@iki.fi >> 9. file:///mc/compose?to=3Dpasik@iki.fi >> 10. file:///mc/compose?to=3Dbderzhavets@yahoo.com >> 11. file:///mc/compose?to=3Djeremy@goop.org >> 12. file:///mc/compose?to=3Dxen-devel@lists.xensource.com >> 13. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 14. file:///mc/compose?to=3Dxen-users@lists.xensource.com >> 15. file:///mc/compose?to=3Djeremy@goop.org >> 16. file:///mc/compose?to=3Djeremy@goop.org >> 17. file:///mc/compose?to=3Dbderzhavets@yahoo.com >> 18. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 19. file:///mc/compose?to=3Dxen-devel@lists.xensource.com >> 20. file:///mc/compose?to=3Dxen-users@lists.xensource.com >> 21. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 22. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 23. file:///mc/compose?to=3Dbderzhavets@yahoo.com >> 24. file:///mc/compose?to=3Djeremy@goop.org >> 25. file:///mc/compose?to=3Dxen-devel@lists.xensource.com >> 26. file:///mc/compose?to=3Dxen-users@lists.xensource.com >> 27. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 28. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 29. file:///mc/compose?to=3Djeremy@goop.org >> 30. file:///mc/compose?to=3Dxen-devel@lists.xensource.com >> 31. file:///mc/compose?to=3Dxen-users@lists.xensource.com >> 32. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 33. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 34. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 35. http://lists.xensource.com/xen-devel >> 36. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 37. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 38. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 39. http://lists.xensource.com/xen-devel >> 40. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 41. http://lists.xensource.com/xen-users >> 42. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 43. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 44. http://lists.xensource.com/xen-users >> 45. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 46. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 47. file:///mc/compose?to=3Dbderzhavets@yahoo.com >> 48. file:///mc/compose?to=3Djeremy@goop.org >> 49. file:///mc/compose?to=3Dxen-devel@lists.xensource.com >> 50. file:///mc/compose?to=3Dxen-users@lists.xensource.com >> 51. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 52. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 53. file:///mc/compose?to=3Djeremy@goop.org >> 54. file:///mc/compose?to=3Dxen-devel@lists.xensource.com >> 55. file:///mc/compose?to=3Dxen-users@lists.xensource.com >> 56. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 57. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 58. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 59. http://lists.xensource.com/xen-devel >> 60. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 61. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 62. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 63. http://lists.xensource.com/xen-devel >> 64. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 65. http://lists.xensource.com/xen-users >> 66. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 67. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 68. http://lists.xensource.com/xen-users >> 69. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 70. http://lists.xensource.com/xen-devel >> 71. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 72. http://lists.xensource.com/xen-devel >> 73. file:///mc/compose?to=3Djeremy@goop.org >> 74. file:///mc/compose?to=3Djeremy@goop.org >> 75. file:///mc/compose?to=3Dbderzhavets@yahoo.com >> 76. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 77. file:///mc/compose?to=3Dxen-devel@lists.xensource.com >> 78. file:///mc/compose?to=3Dxen-users@lists.xensource.com >> 79. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 80. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 81. file:///mc/compose?to=3Dbderzhavets@yahoo.com >> 82. file:///mc/compose?to=3Djeremy@goop.org >> 83. file:///mc/compose?to=3Dxen-devel@lists.xensource.com >> 84. file:///mc/compose?to=3Dxen-users@lists.xensource.com >> 85. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 86. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 87. file:///mc/compose?to=3Djeremy@goop.org >> 88. file:///mc/compose?to=3Dxen-devel@lists.xensource.com >> 89. file:///mc/compose?to=3Dxen-users@lists.xensource.com >> 90. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 91. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 92. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 93. http://lists.xensource.com/xen-devel >> 94. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 95. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 96. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 97. http://lists.xensource.com/xen-devel >> 98. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 99. http://lists.xensource.com/xen-users >> 100. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 101. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 102. http://lists.xensource.com/xen-users >> 103. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 104. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 105. file:///mc/compose?to=3Dbderzhavets@yahoo.com >> 106. file:///mc/compose?to=3Djeremy@goop.org >> 107. file:///mc/compose?to=3Dxen-devel@lists.xensource.com >> 108. file:///mc/compose?to=3Dxen-users@lists.xensource.com >> 109. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 110. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 111. file:///mc/compose?to=3Djeremy@goop.org >> 112. file:///mc/compose?to=3Dxen-devel@lists.xensource.com >> 113. file:///mc/compose?to=3Dxen-users@lists.xensource.com >> 114. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 115. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 116. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 117. http://lists.xensource.com/xen-devel >> 118. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 119. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 120. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 121. http://lists.xensource.com/xen-devel >> 122. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 123. http://lists.xensource.com/xen-users >> 124. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 125. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 126. http://lists.xensource.com/xen-users >> 127. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 128. http://lists.xensource.com/xen-devel >> 129. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 130. http://lists.xensource.com/xen-devel >> 131. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 132. http://lists.xensource.com/xen-devel >> 133. file:///mc/compose?to=3Dpasik@iki.fi >> 134. file:///mc/compose?to=3Dpasik@iki.fi >> 135. file:///mc/compose?to=3Dbderzhavets@yahoo.com >> 136. file:///mc/compose?to=3Djeremy@goop.org >> 137. file:///mc/compose?to=3Dxen-devel@lists.xensource.com >> 138. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 139. file:///mc/compose?to=3Dxen-users@lists.xensource.com >> 140. file:///mc/compose?to=3Djeremy@goop.org >> 141. file:///mc/compose?to=3Djeremy@goop.org >> 142. file:///mc/compose?to=3Dbderzhavets@yahoo.com >> 143. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 144. file:///mc/compose?to=3Dxen-devel@lists.xensource.com >> 145. file:///mc/compose?to=3Dxen-users@lists.xensource.com >> 146. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 147. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 148. file:///mc/compose?to=3Dbderzhavets@yahoo.com >> 149. file:///mc/compose?to=3Djeremy@goop.org >> 150. file:///mc/compose?to=3Dxen-devel@lists.xensource.com >> 151. file:///mc/compose?to=3Dxen-users@lists.xensource.com >> 152. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 153. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 154. file:///mc/compose?to=3Djeremy@goop.org >> 155. file:///mc/compose?to=3Dxen-devel@lists.xensource.com >> 156. file:///mc/compose?to=3Dxen-users@lists.xensource.com >> 157. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 158. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 159. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 160. http://lists.xensource.com/xen-devel >> 161. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 162. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 163. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 164. http://lists.xensource.com/xen-devel >> 165. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 166. http://lists.xensource.com/xen-users >> 167. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 168. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 169. http://lists.xensource.com/xen-users >> 170. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 171. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 172. file:///mc/compose?to=3Dbderzhavets@yahoo.com >> 173. file:///mc/compose?to=3Djeremy@goop.org >> 174. file:///mc/compose?to=3Dxen-devel@lists.xensource.com >> 175. file:///mc/compose?to=3Dxen-users@lists.xensource.com >> 176. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 177. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 178. file:///mc/compose?to=3Djeremy@goop.org >> 179. file:///mc/compose?to=3Dxen-devel@lists.xensource.com >> 180. file:///mc/compose?to=3Dxen-users@lists.xensource.com >> 181. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 182. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 183. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 184. http://lists.xensource.com/xen-devel >> 185. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 186. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 187. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 188. http://lists.xensource.com/xen-devel >> 189. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 190. http://lists.xensource.com/xen-users >> 191. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 192. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 193. http://lists.xensource.com/xen-users >> 194. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 195. http://lists.xensource.com/xen-devel >> 196. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 197. http://lists.xensource.com/xen-devel >> 198. file:///mc/compose?to=3Djeremy@goop.org >> 199. file:///mc/compose?to=3Djeremy@goop.org >> 200. file:///mc/compose?to=3Dbderzhavets@yahoo.com >> 201. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 202. file:///mc/compose?to=3Dxen-devel@lists.xensource.com >> 203. file:///mc/compose?to=3Dxen-users@lists.xensource.com >> 204. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 205. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 206. file:///mc/compose?to=3Dbderzhavets@yahoo.com >> 207. file:///mc/compose?to=3Djeremy@goop.org >> 208. file:///mc/compose?to=3Dxen-devel@lists.xensource.com >> 209. file:///mc/compose?to=3Dxen-users@lists.xensource.com >> 210. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 211. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 212. file:///mc/compose?to=3Djeremy@goop.org >> 213. file:///mc/compose?to=3Dxen-devel@lists.xensource.com >> 214. file:///mc/compose?to=3Dxen-users@lists.xensource.com >> 215. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 216. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 217. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 218. http://lists.xensource.com/xen-devel >> 219. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 220. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 221. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 222. http://lists.xensource.com/xen-devel >> 223. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 224. http://lists.xensource.com/xen-users >> 225. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 226. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 227. http://lists.xensource.com/xen-users >> 228. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 229. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 230. file:///mc/compose?to=3Dbderzhavets@yahoo.com >> 231. file:///mc/compose?to=3Djeremy@goop.org >> 232. file:///mc/compose?to=3Dxen-devel@lists.xensource.com >> 233. file:///mc/compose?to=3Dxen-users@lists.xensource.com >> 234. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 235. file:///mc/compose?to=3Dluis.silva@axiomasoft.pt >> 236. file:///mc/compose?to=3Djeremy@goop.org >> 237. file:///mc/compose?to=3Dxen-devel@lists.xensource.com >> 238. file:///mc/compose?to=3Dxen-users@lists.xensource.com >> 239. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 240. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 241. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 242. http://lists.xensource.com/xen-devel >> 243. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 244. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 245. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 246. http://lists.xensource.com/xen-devel >> 247. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 248. http://lists.xensource.com/xen-users >> 249. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 250. file:///mc/compose?to=3DXen-users@lists.xensource.com >> 251. http://lists.xensource.com/xen-users >> 252. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 253. http://lists.xensource.com/xen-devel >> 254. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 255. http://lists.xensource.com/xen-devel >> 256. file:///mc/compose?to=3DXen-devel@lists.xensource.com >> 257. http://lists.xensource.com/xen-devel >> =20 > =20