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

[JÃrn Odberg <jorn.odberg@xxxxxxxxx>]

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