WARNING - OLD ARCHIVES

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

xen-devel

Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unst

To: Mark Schloesser <mark.schloesser@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Date: Sun, 6 Sep 2009 09:41:38 -0700 (PDT)
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, fedora-xen@xxxxxxxxxx
Delivery-date: Sun, 06 Sep 2009 09:42:26 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1252255298; bh=0BLfvNN0YAVmsYuFmhY0U8FM6TSlHxJCMsPaGkpOjVA=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=V0IT1SPGiNgSg4C1H3R64b1Da4kF/DYG/yU249fzeXGmP7IZwBzBtRSX+5s2MvfO4lvraVwI4fNNKqgeud1TNYLd6afTSdUUp59VQnhMK8D5oSpYJjQtODgok8ZBQbmhpORNPjK2tbGFrlW86D0SfrIV1CTuyNj2R8dTZjr/svY=
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=6BevyZO8ccpK+doTG0G6yk8wh045qBTUZwSgiUIyiLIk41cZVyQj/zQPd6vZ9eOYhkjGMqXp+tr78ehCaEwNv98W0jfBKkeqrjDu/PvTDZD85fQjVudpcpx9ytBhvb19G5l85zq/QMy2i84eMmbjlx9N0oc8RTXc7s1euWEElAA=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4AA3E0A3.8000902@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thanks.

--- On Sun, 9/6/09, Mark Schloesser <mark.schloesser@xxxxxxxxxxxxxx> wrote:

From: Mark Schloesser <mark.schloesser@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, fedora-xen@xxxxxxxxxx
Date: Sunday, September 6, 2009, 12:17 PM

I am on standard F11, using a fresh install and then updated all
packages before doing anything xen related. Xen build was done with
current xen-unstable checkout using only "xen" and "tools" build
targets. I have no libvirt or libvirt-preview currently. My Xorg still
does not want to come up btw :)

Do you need anything else?

Mark


Boris Derzhavets wrote:
>   I tried to build and load on F12 rawhide with the most recent
> gcc,glibc and kernel (fedoras). So, xen was installed via
> xen-3.4.1-3.src.rpm along with libvirt ( via rawhide again). Please,
> let me know your environment for successful build and load rc8 under
> Xen 3.5.
>
> Boris.
> BTW
> Please,be advised :-
>
> **********
> Quote:-
> **********
>
>> Does this help?
>
>> diff --git a/include/linux/swiotlb.h b/include/linux/swiotlb.h
>> index cb1a663..f4ebffb 100644
>> --- a/include/linux/swiotlb.h
>> +++ b/include/linux/swiotlb.h
>> @@ -2,6 +2,7 @@
>  >#define __LINUX_SWIOTLB_H

>  >#include <linux/types.h>
>> +#include <linux/dma-mapping.h>

>  >struct device;
>  >struct dma_attrs;
>
>   Now kernel gets built, but still fails to load under either Xen 3.5 or Xen
>  3.4.1.
>   Stack traces differ on C2D E8400 (Xen 3.4.1)  and Q9550 (Xen 3.5 unstable )boxes.
>   On the last box :-
>
>  do_one_initcall + 0x37/0x1a0
>  kernel_init + 0x164/0x1ba
>  child_rip + 0xa/0x20
>  ? int_ret_from_sys_call 0x7/0x16
>  ? retint_restore_arg + 0x5/0x6
>  ? child_rip 0x0/0x20
>
>  Two last
>  commands are the same on the first box. Previous differ.
>
> Boris.
> P.S. I cannot buy or order 20 m of NUL modem cable.
>        Just 2.5 m . That's all
>
> --- On Sat, 9/5/09, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
>
> From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
> Subject: [Xen-devel] Re: Errors when build 2.6.31-rc8
> To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
> Cc: "Xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
> Date: Saturday, September 5, 2009, 11:48 AM
>
> On
>  09/05/09 04:18, Boris Derzhavets wrote:
>> After fresh git clone, git checkout tune "make menuconfig" the same
>> way as for RC6
>>
>> When build :-
>>
>> In file included from /usr/src/linux-2.6-xen/arch/x86/include/asm/agp.h:5,
>>   
>                from drivers/gpu/drm/ttm/ttm_agp_backend.c:40:
>> include/linux/swiotlb.h:48: warning: ‘enum dma_data_direction’
>> declared inside parameter list
>> include/linux/swiotlb.h:48: warning: its scope is only this definition
>> or declaration, which is probably not what you want
>> include/linux/swiotlb.h:51: warning: ‘enum dma_data_direction’
>> declared inside parameter list
>> include/linux/swiotlb.h:63: warning: ‘enum dma_data_direction’
>> declared inside parameter list
>> include/linux/swiotlb.h:68: warning: ‘enum dma_data_direction’
>> declared inside parameter list
>> include/linux/swiotlb.h:72: warning: ‘enum dma_data_direction’
>> declared inside parameter list
>> include/linux/swiotlb.h:76: warning: ‘enum dma_data_direction’
>> declared inside parameter list
>> include/linux/swiotlb.h:80: warning:
>  ‘enum dma_data_direction’
>> declared inside parameter list
>> include/linux/swiotlb.h:84: warning: ‘enum dma_data_direction’
>> declared inside parameter list
>> include/linux/swiotlb.h:89: warning: ‘enum dma_data_direction’
>> declared inside parameter list
>> include/linux/swiotlb.h:94: warning: ‘enum dma_data_direction’
>> declared inside parameter list
>> In file included from /usr/src/linux-2.6-xen/arch/x86/include/asm/agp.h:9,
>>                   from drivers/gpu/drm/ttm/ttm_agp_backend.c:40:
>> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h: In function
>> ‘get_dma_ops’:
>> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:29: error:
>> dereferencing pointer to incomplete type
>> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:32: error:
>> dereferencing pointer to incomplete
>  type
>> In file included from
>> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:37,
>>                   from /usr/src/linux-2.6-xen/arch/x86/include/asm/agp.h:9,
>>                   from drivers/gpu/drm/ttm/ttm_agp_backend.c:40:
>> include/asm-generic/dma-mapping-common.h: At top level:
>> include/asm-generic/dma-mapping-common.h:12: warning: ‘enum
>> dma_data_direction’ declared inside parameter list
>> include/asm-generic/dma-mapping-common.h:11: error: parameter 4
>> (‘dir’) has incomplete type
>> include/asm-generic/dma-mapping-common.h: In function
>> ‘dma_map_single_attrs’:
>> include/asm-generic/dma-mapping-common.h:18: error: implicit
>> declaration of function ‘valid_dma_direction’
>> In file included from
>>
>  /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:37,
>>                   from /usr/src/linux-2.6-xen/arch/x86/include/asm/agp.h:9,
>>                   from drivers/gpu/drm/ttm/ttm_agp_backend.c:40:
>> include/asm-generic/dma-mapping-common.h:19: error: dereferencing
>> pointer to incomplete type
>> include/asm-generic/dma-mapping-common.h: At top level:
>> include/asm-generic/dma-mapping-common.h:31: warning: ‘enum
>> dma_data_direction’ declared inside parameter list
>> include/asm-generic/dma-mapping-common.h:30: error: parameter 4
>> (‘dir’) has incomplete type
>> include/asm-generic/dma-mapping-common.h: In function
>> ‘dma_unmap_single_attrs’:
>> include/asm-generic/dma-mapping-common.h:36: error: dereferencing
>> pointer to incomplete type
>>
>  include/asm-generic/dma-mapping-common.h:37: error: dereferencing
>> pointer to incomplete type
>> include/asm-generic/dma-mapping-common.h: At top level:
>> include/asm-generic/dma-mapping-common.h:43: warning: ‘enum
>> dma_data_direction’ declared inside parameter list
>> include/asm-generic/dma-mapping-common.h:42: error: parameter 4
>> (‘dir’) has incomplete type
>> include/asm-generic/dma-mapping-common.h: In function ‘dma_map_sg_attrs’:
>> include/asm-generic/dma-mapping-common.h:52: error: dereferencing
>> pointer to incomplete type
>> include/asm-generic/dma-mapping-common.h: At top level:
>> include/asm-generic/dma-mapping-common.h:60: warning: ‘enum
>> dma_data_direction’ declared inside parameter list
>> include/asm-generic/dma-mapping-common.h:59: error: parameter 4
>> (‘dir’) has incomplete type
>> include/asm-generic/dma-mapping-common.h: In
>  function
>> ‘dma_unmap_sg_attrs’:
>> include/asm-generic/dma-mapping-common.h:66: error: dereferencing
>> pointer to incomplete type
>> include/asm-generic/dma-mapping-common.h:67: error: dereferencing
>> pointer to incomplete type
>> include/asm-generic/dma-mapping-common.h: At top level:
>> include/asm-generic/dma-mapping-common.h:72: warning: ‘enum
>> dma_data_direction’ declared inside parameter list
>> include/asm-generic/dma-mapping-common.h:72: error: parameter 5
>> (‘dir’) has incomplete type
>> include/asm-generic/dma-mapping-common.h: In function ‘dma_map_page’:
>> include/asm-generic/dma-mapping-common.h:79: error: dereferencing
>> pointer to incomplete type
>> include/asm-generic/dma-mapping-common.h: At top level:
>> include/asm-generic/dma-mapping-common.h:86: warning: ‘enum
>> dma_data_direction’ declared inside parameter list
>>
>  include/asm-generic/dma-mapping-common.h:86: error: parameter 4
>> (‘dir’) has incomplete type
>> include/asm-generic/dma-mapping-common.h: In function ‘dma_unmap_page’:
>> include/asm-generic/dma-mapping-common.h:91: error: dereferencing
>> pointer to incomplete type
>> include/asm-generic/dma-mapping-common.h:92: error: dereferencing
>> pointer to incomplete type
>> include/asm-generic/dma-mapping-common.h: At top level:
>> include/asm-generic/dma-mapping-common.h:98: warning: ‘enum
>> dma_data_direction’ declared inside parameter list
>> include/asm-generic/dma-mapping-common.h:98: error: parameter 4
>> (‘dir’) has incomplete type
>> include/asm-generic/dma-mapping-common.h: In function
>> ‘dma_sync_single_for_cpu’:
>> include/asm-generic/dma-mapping-common.h:103: error: dereferencing
>> pointer to incomplete type
>>
>  include/asm-generic/dma-mapping-common.h:104: error: dereferencing
>> pointer to incomplete type
>> include/asm-generic/dma-mapping-common.h: At top level:
>> include/asm-generic/dma-mapping-common.h:111: warning: ‘enum
>> dma_data_direction’ declared inside parameter list
>> include/asm-generic/dma-mapping-common.h:111: error: parameter 4
>> (‘dir’) has incomplete type
>> include/asm-generic/dma-mapping-common.h: In function
>> ‘dma_sync_single_for_device’:
>> include/asm-generic/dma-mapping-common.h:116: error: dereferencing
>> pointer to incomplete type
>> include/asm-generic/dma-mapping-common.h:117: error: dereferencing
>> pointer to incomplete type
>> include/asm-generic/dma-mapping-common.h: At top level:
>> include/asm-generic/dma-mapping-common.h:126: warning: ‘enum
>> dma_data_direction’ declared inside parameter list
>>
>  include/asm-generic/dma-mapping-common.h:126: error: parameter 5
>> (‘dir’) has incomplete type
>> include/asm-generic/dma-mapping-common.h: In function
>> ‘dma_sync_single_range_for_cpu’:
>> include/asm-generic/dma-mapping-common.h:131: error: dereferencing
>> pointer to incomplete type
>> include/asm-generic/dma-mapping-common.h:132: error: dereferencing
>> pointer to incomplete type
>> include/asm-generic/dma-mapping-common.h:137: error: type of formal
>> parameter 4 is incomplete
>> include/asm-generic/dma-mapping-common.h: At top level:
>> include/asm-generic/dma-mapping-common.h:144: warning: ‘enum
>> dma_data_direction’ declared inside parameter list
>> include/asm-generic/dma-mapping-common.h:144: error: parameter 5
>> (‘dir’) has incomplete type
>> include/asm-generic/dma-mapping-common.h: In function
>>
>  ‘dma_sync_single_range_for_device’:
>> include/asm-generic/dma-mapping-common.h:149: error: dereferencing
>> pointer to incomplete type
>> include/asm-generic/dma-mapping-common.h:150: error: dereferencing
>> pointer to incomplete type
>> include/asm-generic/dma-mapping-common.h:155: error: type of formal
>> parameter 4 is incomplete
>> include/asm-generic/dma-mapping-common.h: At top level:
>> include/asm-generic/dma-mapping-common.h:160: warning: ‘enum
>> dma_data_direction’ declared inside parameter list
>> include/asm-generic/dma-mapping-common.h:160: error: parameter 4
>> (‘dir’) has incomplete type
>> include/asm-generic/dma-mapping-common.h: In function
>> ‘dma_sync_sg_for_cpu’:
>> include/asm-generic/dma-mapping-common.h:165: error: dereferencing
>> pointer to incomplete type
>> include/asm-generic/dma-mapping-common.h:166: error:
>  dereferencing
>> pointer to incomplete type
>> include/asm-generic/dma-mapping-common.h: At top level:
>> include/asm-generic/dma-mapping-common.h:173: warning: ‘enum
>> dma_data_direction’ declared inside parameter list
>> include/asm-generic/dma-mapping-common.h:173: error: parameter 4
>> (‘dir’) has incomplete type
>> include/asm-generic/dma-mapping-common.h: In function
>> ‘dma_sync_sg_for_device’:
>> include/asm-generic/dma-mapping-common.h:178: error: dereferencing
>> pointer to incomplete type
>> include/asm-generic/dma-mapping-common.h:179: error: dereferencing
>> pointer to incomplete type
>> In file included from /usr/src/linux-2.6-xen/arch/x86/include/asm/agp.h:9,
>>                   from drivers/gpu/drm/ttm/ttm_agp_backend.c:40:
>> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h: In function
>>
>  ‘dma_mapping_error’:
>> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:42: error:
>> dereferencing pointer to incomplete type
>> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:43: error:
>> dereferencing pointer to incomplete type
>> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h: At top level:
>> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:60: warning:
>> ‘enum dma_data_direction’ declared inside parameter list
>> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:60: error:
>> parameter 4 (‘dir’) has incomplete type
>> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h: In function
>> ‘dma_alloc_coherent_mask’:
>> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:77: error:
>> dereferencing pointer to incomplete type
>> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:79: error:
>>
>  implicit declaration of function ‘DMA_BIT_MASK’
>> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h: In function
>> ‘dma_alloc_coherent’:
>> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:114: error:
>> implicit declaration of function ‘is_device_dma_capable’
>> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:117: error:
>> dereferencing pointer to incomplete type
>> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:120: error:
>> dereferencing pointer to incomplete type
>> In file included from /usr/src/linux-2.6-xen/arch/x86/include/asm/agp.h:9,
>>                   from drivers/gpu/drm/ttm/ttm_agp_backend.c:40:
>> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h: In function
>> ‘dma_free_coherent’:
>> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:138: error:
>>
>  dereferencing pointer to incomplete type
>> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:139: error:
>> dereferencing pointer to incomplete type
>> make[4]: *** [drivers/gpu/drm/ttm/ttm_agp_backend.o] Error 1
>> make[3]: *** [drivers/gpu/drm/ttm] Error 2
>> make[2]: *** [drivers/gpu/drm] Error 2
>> make[1]: *** [drivers/gpu] Error 2
>> make: *** [drivers] Error 2
>>
>
> Does this help?
>
> diff --git a/include/linux/swiotlb.h b/include/linux/swiotlb.h
> index cb1a663..f4ebffb 100644
> --- a/include/linux/swiotlb.h
> +++ b/include/linux/swiotlb.h
> @@ -2,6 +2,7 @@
>  #define __LINUX_SWIOTLB_H

>  #include <linux/types.h>
> +#include <linux/dma-mapping.h>

>  struct device;
>  struct dma_attrs;
>
>     J
>
>
> --- On Sun, 9/6/09, Mark Schloesser <mark.schloesser@xxxxxxxxxxxxxx> wrote:
>
> From: Mark Schloesser <mark.schloesser@xxxxxxxxxxxxxx>
> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
> Cc: fedora-xen@xxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
> Date: Sunday, September 6, 2009, 11:09 AM
>
> Boris,
>
> actually I used your config. The same config as I used for -rc6 build.
> Works just fine for me - but I did not try booting with 3.4.1, only with
> xen-unstable.
>
> Mark
>
>
> Boris Derzhavets wrote:
>> Mark,
>> Could you share your .config for JF's 2.6.31-rc8 which loads under Xen Unstable.
>> Looks like i miss some point tuning kernel.
>>
>> Thanks.
>> Boris.
>>
>> --- On Fri, 9/4/09, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:
>>
>> From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
>> Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
>> To: fedora-xen@xxxxxxxxxx, "Mark Schloesser" <mark.schloesser@xxxxxxxxxxxxxxx>
>> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
>> Date: Friday, September 4, 2009, 2:02 PM
>>
>> I did "git pull" , built 2.6.31-c8 kernel with Xen Dom0 support.
>> However, attempt to load kernel under Xen 3.4.1 drops
>> into stack trace and hangs on both F11 and Ubuntu 9.10.
>> Old 2.6.31-rc6's .config file has been used without any changes.
>> I can't set up serial console in meantime.
>>
>> Boris
>>
>> --- On Fri, 9/4/09, Mark Schloesser <mark.schloesser@xxxxxxxxxxxxxx> wrote:
>>
>> From: Mark Schloesser <mark.schloesser@xxxxxxxxxxxxxx>
>> Subject: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
>> To: fedora-xen@xxxxxxxxxx
>> Date: Friday, September 4, 2009, 10:26 AM
>>
>> Hey guys,
>>
>> I sadly had no luck fixing my X problem. The system seems to run fine
>> and as the subject says I moved
>>   from 3.4.1-3 to xen-unstable. As I am
>> already doing fairly bleeding-edge stuff here I thought this would
>> probably make most sense.
>>
>> As I only have an nvs290 gfx card available right now I can't check if
>> this is the problem. But I'll try to get my hands on some other cards
>> for next week.
>>
>> Today I read through a lot of mailing list archives and PDFs trying to
>> dig deeper into the IOMMU/PCI passthrough stuff and I want to give the
>> graphics passthrough situation a shot myself. Sadly it is very confusing
>> to read about the different setups and hardware environments with both
>> positive and negative results. Also the patchsets and versions everybody
>> is talking about do not make it any easier :)
>>
>> My current questions would be:
>> - is the combination of JF git kernel with xen-unstable the right way to
>> go for this setup? Or should I perhaps use older xen version and apply
>> some patchset? I think some of those
>>   patches were applied in
>> xen-unstable already but I am not quite sure...
>>
>> - does anyone have hints or clarification regarding the Xorg problem on
>> dom0? As I said there are no eye-catching log entries or errors except
>> the Xorg backtrace at the end of the log file (posted to list before).
>> This happens regardless of which driver I enable (vesa/nv/nouveau). The
>> nvidia binary driver compiles without problems and seems to come up but
>> only gives me a black screen and also locks the vtys.
>>
>>
>> Thanks to the great help, reports and instructions Boris and others!
>>
>> Mark
>>
>>
>> -----Inline Attachment Follows-----
>>
>> --
>> Fedora-xen mailing list
>> Fedora-xen@xxxxxxxxxx
>> https://www.redhat.com/mailman/listinfo/fedora-xen
>>
>>
>>
>>
>>
>>       
>> -----Inline Attachment Follows-----
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel
>>
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel
>
>
>
>
>       
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>