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-users

[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: [Xen-users] xen, pvops & nvidia graphics

from [Jørn Odberg] [Permanent Link][Original]
To: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: [Xen-users] xen, pvops & nvidia graphics
From: Jørn Odberg <jorn.odberg@xxxxxxxxx>
Date: Tue, 19 Jan 2010 22:06:58 +0100
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 19 Jan 2010 13:08:17 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=WZSj0bu+w73i+mnAXjRVn+HBJWymLJGcCbiuaSAZpBM=; b=xHi6AIpio905cmYWe2PPStKzO8QtcWVozmSwieac8e44BblO0tOdd5cYpmCyvWxoTA Ykor3ivkngBdojU3MD790InZE4o22i9ILdoaJD54yM55vP4KC1ffKTXC44VHvoEXwOCo z7oP/M0xqw4bgm07pNUhVmFBthborRB++JtQY=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=meXPtd5eE9tadnoYZ/NYMf9JPBlVg1O9lMCwCXOm5+vX9ihpZFWx2UUICoz852mYNW ErpFW596mIrJUtWfuQgfjFjF6jkFi3BhRKnmQAgk7Yuy7Uy1bM9QhdoDp+l/Wm5KTRtD 24wbyUNRK7tFf4EC2LkdKrd+9PHQE/Hlw6wdk=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100119205820.GJ2861@xxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <8187cf590912200728r3ecd6117ua6801fd171897f0e@xxxxxxxxxxxxxx> <31e44a110912210956x6d98f348k7bb5614d8595e4e1@xxxxxxxxxxxxxx> <8187cf590912211322n50970776l81ae85958b747af0@xxxxxxxxxxxxxx> <b879e2cb1001190549v7804418p9b986a14939ef615@xxxxxxxxxxxxxx> <20100119181915.GD2861@xxxxxxxxxxx> <b879e2cb1001191231m627212a5o1b565180b533978a@xxxxxxxxxxxxxx> <20100119203520.GI2861@xxxxxxxxxxx> <b879e2cb1001191246o1c4a7e69o8b9c4238c0d9a8e0@xxxxxxxxxxxxxx> <20100119205820.GJ2861@xxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thanks for your help, Pasi.

I feel like an idiot. As I said, I bought this hardware just to do Xen. In addition to some expensive graphic cards and such...
But I found very little info around the net regarding chipset doing VT-d. And most of the info I found, was a couple of years old. So I just thought that most of the recent motherboards/chipsets was doing this these days...

Damn. :\

Sorry for taking up your time to no use. But thanks a lot for helping me figure this out. Now I just have to go earn some more money so I can buy a new motherboard with the specifications I hope to find. :\


Greetings from Norway,
Jørn



On Tue, Jan 19, 2010 at 9:58 PM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
On Tue, Jan 19, 2010 at 09:46:26PM +0100, Jørn Odberg wrote:
>    Full xm dmesg output:
>
>    Â __Â  __Â Â Â Â Â Â Â Â Â Â Â  _____ _Â  _Â Â Â  ____Â
>    Â \ \/ /___ _ __Â Â  |___ /| || |Â  |___ \
>    Â  \Â  // _ \ '_ \Â Â Â  |_ \| || |_Â Â  __) |
>    Â  /Â  \Â  __/ | | |Â  ___) |__Â Â  _| / __/
>    Â /_/\_\___|_| |_| |____(_) |_|(_)_____|
>    Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â
>    (XEN) Xen version 3.4.2 (root@) (gcc version 4.3.4 (Gentoo 4.3.4 p1.0,
>    pie-10.1.5) ) Fri Jan 15 10:45:24 CET 2010
>    (XEN) Latest ChangeSet: unavailable
>    (XEN) Command line: iommu=1 vtd=1
>    (XEN) Video information:
>    (XEN)Â  VGA is text mode 80x25, font 8x16
>    (XEN)Â  VBE/DDC methods: V2; EDID transfer time: 1 seconds
>    (XEN) Disc information:
>    (XEN)Â  Found 2 MBR signatures
>    (XEN)Â  Found 2 EDD information structures
>    (XEN) Xen-e820 RAM map:
>    (XEN)Â  0000000000000000 - 000000000009cc00 (usable)
>    (XEN)Â  000000000009cc00 - 00000000000a0000 (reserved)
>    (XEN)Â  00000000000e4000 - 0000000000100000 (reserved)
>    (XEN)Â  0000000000100000 - 00000000bff70000 (usable)
>    (XEN)Â  00000000bff70000 - 00000000bff7e000 (ACPI data)
>    (XEN)Â  00000000bff7e000 - 00000000bffd0000 (ACPI NVS)
>    (XEN)Â  00000000bffd0000 - 00000000c0000000 (reserved)
>    (XEN)Â  00000000fee00000 - 00000000fee01000 (reserved)
>    (XEN)Â  00000000ffe00000 - 0000000100000000 (reserved)
>    (XEN)Â  0000000100000000 - 0000000140000000 (usable)
>    (XEN) System RAM: 4095MB (4193328kB)
>    (XEN) ACPI: RSDP 000FB280, 0014 (r0 ACPIAM)
>    (XEN) ACPI: RSDT BFF70000, 0044 (r1 A_M_I_ OEMRSDTÂ Â  5000922
>    MSFTÂ Â Â Â Â Â  97)
>    (XEN) ACPI: FACP BFF70200, 0084 (r2 A_M_I_ OEMFACPÂ Â  5000922
>    MSFTÂ Â Â Â Â Â  97)
>    (XEN) ACPI: DSDT BFF70440, 9EBF (r1Â  A1039 A1039001Â Â Â Â Â Â Â  1 INTL
>    20060113)
>    (XEN) ACPI: FACS BFF7E000, 0040
>    (XEN) ACPI: APIC BFF70390, 006C (r1 A_M_I_ OEMAPICÂ Â  5000922
>    MSFTÂ Â Â Â Â Â  97)
>    (XEN) ACPI: MCFG BFF70400, 003C (r1 A_M_I_ OEMMCFGÂ Â  5000922
>    MSFTÂ Â Â Â Â Â  97)
>    (XEN) ACPI: OEMB BFF7E040, 0089 (r1 A_M_I_ AMI_OEMÂ Â  5000922
>    MSFTÂ Â Â Â Â Â  97)
>    (XEN) ACPI: HPET BFF7A300, 0038 (r1 A_M_I_ OEMHPETÂ Â  5000922
>    MSFTÂ Â Â Â Â Â  97)
>    (XEN) ACPI: OSFR BFF7A340, 00B0 (r1 A_M_I_ OEMOSFRÂ Â  5000922
>    MSFTÂ Â Â Â Â Â  97)
>    (XEN) ACPI: TCPA BFF7A3F0, 0032 (r1 A_M_I_ TBLOEMIDÂ Â Â Â Â Â Â  1
>    MSFTÂ Â Â Â Â Â  97)
>    (XEN) ACPI: SSDT BFF91A70, 0A7C (r1 DpgPmm    CpuPm       12 INTL
>    20060113)
>    (XEN) Domain heap initialised
>    (XEN) Processor #0 7:7 APIC version 20
>    (XEN) Processor #1 7:7 APIC version 20
>    (XEN) Processor #2 7:7 APIC version 20
>    (XEN) Processor #3 7:7 APIC version 20
>    (XEN) IOAPIC[0]: apic_id 4, version 32, address 0xfec00000, GSI 0-23
>    (XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
>    (XEN) XSM Framework v1.0.0 initialized
>    (XEN) Using scheduler: SMP Credit Scheduler (credit)
>    (XEN) Detected 2666.422 MHz processor.
>    (XEN) VMX: Supported advanced features:
>    (XEN)Â  - APIC MMIO access virtualisation
>    (XEN)Â  - APIC TPR shadow
>    (XEN)Â  - Virtual NMI
>    (XEN)Â  - MSR direct-access bitmap
>    (XEN) HVM: VMX enabled
>    (XEN) CPU0: Intel(R) Core(TM)2 Quad CPUÂ Â Â  Q9400Â  @ 2.66GHz stepping
>    0a
>    (XEN) Booting processor 1/1 eip 8c000
>    (XEN) CPU1: Intel(R) Core(TM)2 Quad CPUÂ Â Â  Q9400Â  @ 2.66GHz stepping
>    0a
>    (XEN) Booting processor 2/2 eip 8c000
>    (XEN) CPU2: Intel(R) Core(TM)2 Quad CPUÂ Â Â  Q9400Â  @ 2.66GHz stepping
>    0a
>    (XEN) Booting processor 3/3 eip 8c000
>    (XEN) CPU3: Intel(R) Core(TM)2 Quad CPUÂ Â Â  Q9400Â  @ 2.66GHz stepping
>    0a
>    (XEN) Total of 4 processors activated.
>    (XEN) ENABLING IO-APIC IRQs
>    (XEN)Â  -> Using new ACK method
>    (XEN) checking TSC synchronization across 4 CPUs: passed.
>    (XEN) Platform timer is 14.318MHz HPET
>    (XEN) Brought up 4 CPUs
>    (XEN) I/O virtualisation disabled
>    (XEN) *** LOADING DOMAIN 0 ***
>    (XEN)  Xen  kernel: 64-bit, lsb, compat32
>    (XEN)Â  Dom0 kernel: 64-bit, lsb, paddr 0x200000 -> 0x7e6000
>    (XEN) PHYSICAL MEMORY ARRANGEMENT:
>    (XEN)Â  Dom0 alloc.:Â Â  000000013b000000->000000013c000000 (996433 pages
>    to be allocated)
>    (XEN) VIRTUAL MEMORY ARRANGEMENT:
>    (XEN)Â  Loaded kernel: ffffffff80200000->ffffffff807e6000
>    (XEN)Â  Init. ramdisk: ffffffff807e6000->ffffffff807e6000
>    (XEN)Â  Phys-Mach map: ffffea0000000000->ffffea00007a2288
>    (XEN)Â  Start info:Â Â Â  ffffffff807e6000->ffffffff807e64b4
>    (XEN)Â  Page tables:Â Â  ffffffff807e7000->ffffffff807f0000
>    (XEN)Â  Boot stack:Â Â Â  ffffffff807f0000->ffffffff807f1000
>    (XEN)Â  TOTAL:Â Â Â Â Â Â Â Â  ffffffff80000000->ffffffff80c00000
>    (XEN)Â  ENTRY ADDRESS: ffffffff80200000
>    (XEN) Dom0 has maximum 4 VCPUs
>    (XEN) Scrubbing Free RAM: .done.
>    (XEN) Xen trace buffers: disabled
>    (XEN) Std. Loglevel: Errors and warnings
>    (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
>    (XEN) Xen is relinquishing VGA console.
>    (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input
>    to Xen)
>    (XEN) Freed 136kB init memory.
>    (XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space
>    (XEN) CPU 0 initialization completed
>    (XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space
>    (XEN) CPU 1 initialization completed
>    (XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space
>    (XEN) CPU 2 initialization completed
>    (XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space
>    (XEN) CPU 3 initialization completed
>
>    In the BIOS I could only find "Intel(R) Virtualization Tech     -
>    Enabled" , but no setting for VT-d... damn... DAMN! Does that mean I'm
>    screwed?!? I bought this motherboard and cpu just to do Xen.
>
>    Motherboard: ASUS P5Q Premium, P45, Socket-775.
>    CPU: Intel Core 2 Quad Q9400. (Has "Intel Virtualization Technology")
>
>    I was under the impression the Intel P45 chipset had "VT-d" ? ... :\
>
>    Am I screwed, or is it only me who screws something up? ;)
>

Looks bad.. nothing about ACPI DMAR in the log, which is used by VT-d IOMMU..
It looks like your chipset/BIOS doesn't support VT-d.

This wiki page lists some motherboards/chipsets with IOMMU (VT-d):
http://wiki.xensource.com/xenwiki/VTdHowTo

I don't see P45 there.. does Asus claim it supports VT-d ?

-- Pasi

>    // JÞrn
>
>    On Tue, Jan 19, 2010 at 9:35 PM, Pasi KÀrkkÀinen <[1]pasik@xxxxxx>
>    wrote:
>
>      On Tue, Jan 19, 2010 at 09:31:27PM +0100, JÞrn Odberg wrote:
>      > Â  Â Hello, and thanks for the reply.
>      >
>      > Â  Â I've added this to my grub (it may be redundant, but I got
>      different
>      > Â  Â advices, so I added them all;):
>      >
>      > Â  Â title Xen / Gentoo Linux 2.6.31-xen-r10 IOMMU
>      > Â  Â root (hd0,0)
>      > Â  Â kernel /boot/xen.gz iommu=1 vtd=1
>      > Â  Â module /boot/vmlinuz-2.6.31-xen-r10 root=/dev/md2
>      pciback.permissive
>
>      Oh, it looks like you're not using pv_ops dom0 kernel, but gentoo kernel
>      with
>      xenlinux patches from opensuse.
>
>      Then you can forget my xen-pciback comment.
>      > Â  Â xen-pciback.hide=(01:00.0)(08:00.0)(09:00.0)
>      > Â  Â pciback.hide=(01:00.0)(08:00.0)(09:00.0)
>      guestdev=01:00.0,08:00.0,09:00.0
>      > Â  Â reassign_resources console=tty0
>      >
>      > Â  Â And I have installed Xen 3.4.2-r1.
>      >
>      > Â  Â xm dmesg , shows:
>      > Â  Â (XEN) Command line: iommu=1 vtd=1
>      > Â  Â (XEN) VMX: Supported advanced features:
>      > Â  Â (XEN)Ã* Â - APIC MMIO access virtualisation
>      > Â  Â (XEN)Ã* Â - APIC TPR shadow
>      > Â  Â (XEN)Ã* Â - Virtual NMI
>      > Â  Â (XEN)Ã* Â - MSR direct-access bitmap
>      > Â  Â (XEN) HVM: VMX enabled
>      > Â  Â (XEN) I/O virtualisation disabled
>      >
>
>      Please paste the full "xm dmesg", that doesn't show why it's disabled in
>      Xen hypervisor.
>
>      Did you enable VT-d in BIOS?
>
>      -- Pasi
>
>      > Â  Â // JÃ*ÅŸrn
>      >
>      > Â  Â On Tue, Jan 19, 2010 at 7:19 PM, Pasi KÃ*â*¬rkkÃ*â*¬inen
>      <[1][2]pasik@xxxxxx>
>      > Â  Â wrote:
>      >
>      > Â  Â  Â On Tue, Jan 19, 2010 at 02:49:52PM +0100, JÃ*ÅŸrn Odberg
>      wrote:
>      > Â  Â  Â > Ã* Â Ã* Hello.
>      > Â  Â  Â >
>      > Â  Â  Â > Ã* Â Ã* I have this exact same problem myself.
>      > Â  Â  Â >
>      > Â  Â  Â > Ã* Â Ã* (I have four onboard gigabit network cards, pci
>      05:00.0, 06:00.0,
>      > Â  Â  Â 07:00.0
>      > Â  Â  Â > Ã* Â Ã* and 08:00.0)
>      > Â  Â  Â > Ã* Â Ã* I tried using pciback.hide=(06:00.0)(07:00.0) . And
>      in dom0, I
>      > Â  Â  Â now get:
>      > Â  Â  Â >
>      >
>      > Â  Â  Â In the recent pv_ops dom0 kernels pciback module is now called
>      > Â  Â  Â xen-pciback,
>      > Â  Â  Â so you need to change that to xen-pciback.hide.
>      >
>      > Â  Â  Â -- Pasi
>      > Â  Â  Â > Ã* Â Ã* xen ~ # ifconfig eth1
>      > Â  Â  Â > Ã* Â Ã* eth1: error fetching interface information: Device
>      not found
>      > Â  Â  Â >
>      > Â  Â  Â > Ã* Â Ã* And the same for eth2. So it apparently got
>      "hidden", or
>      > Â  Â  Â detached.
>      > Â  Â  Â >
>      > Â  Â  Â > Ã* Â Ã* But the command "xm pci-list-assignable-devices"
>      doesn't return
>      > Â  Â  Â anything.
>      > Â  Â  Â > Ã* Â Ã* And when trying "xm pci-detach", I get the same
>      error as you
>      > Â  Â  Â (Cannot
>      > Â  Â  Â > Ã* Â Ã* detach when pci platform does not exist). Even
>      though I've
>      > Â  Â  Â compiled in all
>      > Â  Â  Â > Ã* Â Ã* the support I can think of in the kernel.
>      > Â  Â  Â >
>      > Â  Â  Â > Ã* Â Ã* Running:
>      > Â  Â  Â > Ã* Â Ã* Gentoo 2.6.31-xen-r10
>      > Â  Â  Â > Ã* Â Ã* xen-3.4.2-r1
>      > Â  Â  Â >
>      > Â  Â  Â > Ã* Â Ã* // JÃ**Ã*Åžrn
>      > Â  Â  Â >
>      > Â  Â  Â > Ã* Â Ã* On Mon, Dec 21, 2009 at 10:22 PM, Kai Wohlfahrt
>      > Â  Â  Â <[1][2][3]kjw53@xxxxxxxxx>
>      > Â  Â  Â > Ã* Â Ã* wrote:
>      > Â  Â  Â >
>      > Â  Â  Â > Ã* Â Ã* Â Ã* Still no luck with that. My grub entry looks
>      like so:
>      > Â  Â  Â >
>      > Â  Â  Â > Ã* Â Ã* Â Ã* Â Ã* Â Ã* menuentry "Xen-Unstable / Kubuntu
>      9.10 kernel 2.6.31.6
>      > Â  Â  Â pvops" {
>      > Â  Â  Â >
>      > Â  Â  Â > Ã* Â Ã* Â Ã* Â Ã* Â Ã* insmod ext2
>      > Â  Â  Â >
>      > Â  Â  Â > Ã* Â Ã* Â Ã* Â Ã* Â Ã* set root=(hd0,1)
>      > Â  Â  Â >
>      > Â  Â  Â > Ã* Â Ã* Â Ã* Â Ã* Â Ã* multiboot (hd0,1)/boot/xen.gz
>      dom0_mem=1048M iommu=force
>      > Â  Â  Â >
>      > Â  Â  Â > Ã* Â Ã* Â Ã* Â Ã* Â Ã* module
>      (hd0,1)/boot/vmlinuz-2.6.31.6-xen
>      > Â  Â  Â xen-pciback.hide=(01:00.0)
>      > Â  Â  Â >
>      > Â  Â  Â > Ã* Â Ã* Â Ã* Â Ã* Â Ã* module
>      (hd0,1)/boot/initrd.img-2.6.31.6-xen
>      > Â  Â  Â >
>      > Â  Â  Â > Ã* Â Ã* Â Ã* Â Ã* Â Ã* }
>      > Â  Â  Â >
>      > Â  Â  Â > Ã* Â Ã* Â Ã* but my lspci still looks the same (i.e. it
>      still has the line:
>      > Â  Â  Â 01:00.0
>      > Â  Â  Â > Ã* Â Ã* Â Ã* VGA compatible controller: nVidia Corporation
>      G96 [GeForce GT
>      > Â  Â  Â 130M] (rev
>      > Â  Â  Â > Ã* Â Ã* Â Ã* a1)).
>      > Â  Â  Â > Ã* Â Ã* Â Ã* Using xm pci-detach still gives the same error
>      as well (Error:
>      > Â  Â  Â Cannot
>      > Â  Â  Â > Ã* Â Ã* Â Ã* detach when pci platform does not exist)
>      > Â  Â  Â > Ã* Â Ã* Â Ã* Kai
>      > Â  Â  Â > Ã* Â Ã* Â Ã* _______________________________________________
>      > Â  Â  Â > Ã* Â Ã* Â Ã* Xen-users mailing list
>      > Â  Â  Â > Ã* Â Ã* Â Ã* [2][3][4]Xen-users@xxxxxxxxxxxxxxxxxxx
>      > Â  Â  Â > Ã* Â Ã* Â Ã* [3][4][5]http://lists.xensource.com/xen-users
>      > Â  Â  Â >
>      > Â  Â  Â > References
>      > Â  Â  Â >
>      > Â  Â  Â > Ã* Â Ã* Visible links
>      > Â  Â  Â > Ã* Â Ã* 1. mailto:[5][6]kjw53@xxxxxxxxx
>      > Â  Â  Â > Ã* Â Ã* 2. mailto:[6][7]Xen-users@xxxxxxxxxxxxxxxxxxx
>      > Â  Â  Â > Ã* Â Ã* 3. [7][8]http://lists.xensource.com/xen-users
>      > Â  Â  Â > _______________________________________________
>      > Â  Â  Â > Xen-users mailing list
>      > Â  Â  Â > [8][9]Xen-users@xxxxxxxxxxxxxxxxxxx
>      > Â  Â  Â > [9][10]http://lists.xensource.com/xen-users
>      >
>      > Â  Â  Â _______________________________________________
>      > Â  Â  Â Xen-users mailing list
>      > Â  Â  Â [10][11]Xen-users@xxxxxxxxxxxxxxxxxxx
>      > Â  Â  Â [11][12]http://lists.xensource.com/xen-users
>      >
>      > References
>      >
>      > Â  Â Visible links
>      > Â  Â 1. mailto:[13]pasik@xxxxxx
>      > Â  Â 2. mailto:[14]kjw53@xxxxxxxxx
>      > Â  Â 3. mailto:[15]Xen-users@xxxxxxxxxxxxxxxxxxx
>      > Â  Â 4. [16]http://lists.xensource.com/xen-users
>      > Â  Â 5. mailto:[17]kjw53@xxxxxxxxx
>      > Â  Â 6. mailto:[18]Xen-users@xxxxxxxxxxxxxxxxxxx
>      > Â  Â 7. [19]http://lists.xensource.com/xen-users
>      > Â  Â 8. mailto:[20]Xen-users@xxxxxxxxxxxxxxxxxxx
>      > Â  Â 9. [21]http://lists.xensource.com/xen-users
>      > Â  10. mailto:[22]Xen-users@xxxxxxxxxxxxxxxxxxx
>      > Â  11. [23]http://lists.xensource.com/xen-users
>      _______________________________________________
>      Xen-users mailing list
>      [24]Xen-users@xxxxxxxxxxxxxxxxxxx
>      [25]http://lists.xensource.com/xen-users
>
> References
>
>    Visible links
>    1. mailto:pasik@xxxxxx
>    2. mailto:pasik@xxxxxx
>    3. mailto:kjw53@xxxxxxxxx
>    4. mailto:Xen-users@xxxxxxxxxxxxxxxxxxx
>    5. http://lists.xensource.com/xen-users
>    6. mailto:kjw53@xxxxxxxxx
>    7. mailto:Xen-users@xxxxxxxxxxxxxxxxxxx
>    8. http://lists.xensource.com/xen-users
>    9. mailto:Xen-users@xxxxxxxxxxxxxxxxxxx
>   10. http://lists.xensource.com/xen-users
>   11. mailto:Xen-users@xxxxxxxxxxxxxxxxxxx
>   12. http://lists.xensource.com/xen-users
>   13. mailto:pasik@xxxxxx
>   14. mailto:kjw53@xxxxxxxxx
>   15. mailto:Xen-users@xxxxxxxxxxxxxxxxxxx
>   16. http://lists.xensource.com/xen-users
>   17. mailto:kjw53@xxxxxxxxx
>   18. mailto:Xen-users@xxxxxxxxxxxxxxxxxxx
>   19. http://lists.xensource.com/xen-users
>   20. mailto:Xen-users@xxxxxxxxxxxxxxxxxxx
>   21. http://lists.xensource.com/xen-users
>   22. mailto:Xen-users@xxxxxxxxxxxxxxxxxxx
>   23. http://lists.xensource.com/xen-users
>   24. mailto:Xen-users@xxxxxxxxxxxxxxxxxxx
>   25. http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: [Xen-users] xen, pvops & nvidia graphics, Pasi Kärkkäinen
Next by Date:  Re: [Xen-users] xen, pvops & nvidia graphics, Pasi Kärkkäinen
Previous by Thread:  Re: [Xen-users] xen, pvops & nvidia graphics, Pasi Kärkkäinen
Next by Thread:  Re: [Xen-users] xen, pvops & nvidia graphics, Pasi Kärkkäinen
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

Copyright , Citrix Systems Inc. All rights reserved. Legal and Privacy