On Tue, Jan 19, 2010 at 10:06:58PM +0100, Jørn Odberg wrote:
> 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. :\
>
Yeah.. it's a bit difficult atm.
Also many of the consumer motherboards seem to have buggy BIOSes regarding VT-d
support..
so even if your motherboard has VT-d support, it doesn't mean it actually works
:)
Asus is known to have multiple motherboard models with broken BIOS..
(they have wrong memory ranges in the VT-d DMAR tables).
When you get a new motherboard make sure to browse through xen-users and/or
xen-devel
archives and see what motherboards people have been successfully using..
> Greetings from Norway,
> JÞrn
>
Greetings from Finland :)
-- Pasi
>
> On Tue, Jan 19, 2010 at 9:58 PM, Pasi KÀrkkÀinen <[1]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):
> [2]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][3]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][4]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][5]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][6]Xen-users@xxxxxxxxxxxxxxxxxxx
> > Â Â Â > Ã* Â Ã* Â Ã* > Ã** Ã* Ã** Ã* Ã**
> [3][4][5][7]http://lists.xensource.com/xen-users
> > Â Â Â > Ã* Â Ã* Â Ã* >
> > Â Â Â > Ã* Â Ã* Â Ã* > References
> > Â Â Â > Ã* Â Ã* Â Ã* >
> > Â Â Â > Ã* Â Ã* Â Ã* > Ã** Ã* Ã** Visible links
> > Â Â Â > Ã* Â Ã* Â Ã* > Ã** Ã* Ã** 1. mailto:[5][6][8]kjw53@xxxxxxxxx
> > Â Â Â > Ã* Â Ã* Â Ã* > Ã** Ã* Ã** 2.
> mailto:[6][7][9]Xen-users@xxxxxxxxxxxxxxxxxxx
> > Â Â Â > Ã* Â Ã* Â Ã* > Ã** Ã* Ã** 3.
> [7][8][10]http://lists.xensource.com/xen-users
> > Â Â Â > Ã* Â Ã* Â Ã* >
> _______________________________________________
> > Â Â Â > Ã* Â Ã* Â Ã* > Xen-users mailing list
> > Â Â Â > Ã* Â Ã* Â Ã* > [8][9][11]Xen-users@xxxxxxxxxxxxxxxxxxx
> > Â Â Â > Ã* Â Ã* Â Ã* >
> [9][10][12]http://lists.xensource.com/xen-users
> > Â Â Â >
> > Â Â Â > Ã* Â Ã* Â Ã* _______________________________________________
> > Â Â Â > Ã* Â Ã* Â Ã* Xen-users mailing list
> > Â Â Â > Ã* Â Ã* Â Ã* [10][11][13]Xen-users@xxxxxxxxxxxxxxxxxxx
> > Â Â Â > Ã* Â Ã* Â Ã*
> [11][12][14]http://lists.xensource.com/xen-users
> > Â Â Â >
> > Â Â Â > References
> > Â Â Â >
> > Â Â Â > Ã* Â Ã* Visible links
> > Â Â Â > Ã* Â Ã* 1. mailto:[13][15]pasik@xxxxxx
> > Â Â Â > Ã* Â Ã* 2. mailto:[14][16]kjw53@xxxxxxxxx
> > Â Â Â > Ã* Â Ã* 3. mailto:[15][17]Xen-users@xxxxxxxxxxxxxxxxxxx
> > Â Â Â > Ã* Â Ã* 4. [16][18]http://lists.xensource.com/xen-users
> > Â Â Â > Ã* Â Ã* 5. mailto:[17][19]kjw53@xxxxxxxxx
> > Â Â Â > Ã* Â Ã* 6. mailto:[18][20]Xen-users@xxxxxxxxxxxxxxxxxxx
> > Â Â Â > Ã* Â Ã* 7. [19][21]http://lists.xensource.com/xen-users
> > Â Â Â > Ã* Â Ã* 8. mailto:[20][22]Xen-users@xxxxxxxxxxxxxxxxxxx
> > Â Â Â > Ã* Â Ã* 9. [21][23]http://lists.xensource.com/xen-users
> > Â Â Â > Ã* Â 10. mailto:[22][24]Xen-users@xxxxxxxxxxxxxxxxxxx
> > Â Â Â > Ã* Â 11. [23][25]http://lists.xensource.com/xen-users
> > Â Â Â _______________________________________________
> > Â Â Â Xen-users mailing list
> > Â Â Â [24][26]Xen-users@xxxxxxxxxxxxxxxxxxx
> > Â Â Â [25][27]http://lists.xensource.com/xen-users
> >
> > References
> >
> > Â Â Visible links
> > Â Â 1. mailto:[28]pasik@xxxxxx
> > Â Â 2. mailto:[29]pasik@xxxxxx
> > Â Â 3. mailto:[30]kjw53@xxxxxxxxx
> > Â Â 4. mailto:[31]Xen-users@xxxxxxxxxxxxxxxxxxx
> > Â Â 5. [32]http://lists.xensource.com/xen-users
> > Â Â 6. mailto:[33]kjw53@xxxxxxxxx
> > Â Â 7. mailto:[34]Xen-users@xxxxxxxxxxxxxxxxxxx
> > Â Â 8. [35]http://lists.xensource.com/xen-users
> > Â Â 9. mailto:[36]Xen-users@xxxxxxxxxxxxxxxxxxx
> > Â 10. [37]http://lists.xensource.com/xen-users
> > Â 11. mailto:[38]Xen-users@xxxxxxxxxxxxxxxxxxx
> > Â 12. [39]http://lists.xensource.com/xen-users
> > Â 13. mailto:[40]pasik@xxxxxx
> > Â 14. mailto:[41]kjw53@xxxxxxxxx
> > Â 15. mailto:[42]Xen-users@xxxxxxxxxxxxxxxxxxx
> > Â 16. [43]http://lists.xensource.com/xen-users
> > Â 17. mailto:[44]kjw53@xxxxxxxxx
> > Â 18. mailto:[45]Xen-users@xxxxxxxxxxxxxxxxxxx
> > Â 19. [46]http://lists.xensource.com/xen-users
> > Â 20. mailto:[47]Xen-users@xxxxxxxxxxxxxxxxxxx
> > Â 21. [48]http://lists.xensource.com/xen-users
> > Â 22. mailto:[49]Xen-users@xxxxxxxxxxxxxxxxxxx
> > Â 23. [50]http://lists.xensource.com/xen-users
> > Â 24. mailto:[51]Xen-users@xxxxxxxxxxxxxxxxxxx
> > Â 25. [52]http://lists.xensource.com/xen-users
>
> References
>
> Visible links
> 1. mailto:pasik@xxxxxx
> 2. http://wiki.xensource.com/xenwiki/VTdHowTo
> 3. mailto:pasik@xxxxxx
> 4. mailto:pasik@xxxxxx
> 5. mailto:kjw53@xxxxxxxxx
> 6. mailto:Xen-users@xxxxxxxxxxxxxxxxxxx
> 7. http://lists.xensource.com/xen-users
> 8. mailto:kjw53@xxxxxxxxx
> 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:Xen-users@xxxxxxxxxxxxxxxxxxx
> 14. http://lists.xensource.com/xen-users
> 15. mailto:pasik@xxxxxx
> 16. mailto:kjw53@xxxxxxxxx
> 17. mailto:Xen-users@xxxxxxxxxxxxxxxxxxx
> 18. http://lists.xensource.com/xen-users
> 19. mailto:kjw53@xxxxxxxxx
> 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
> 26. mailto:Xen-users@xxxxxxxxxxxxxxxxxxx
> 27. http://lists.xensource.com/xen-users
> 28. mailto:pasik@xxxxxx
> 29. mailto:pasik@xxxxxx
> 30. mailto:kjw53@xxxxxxxxx
> 31. mailto:Xen-users@xxxxxxxxxxxxxxxxxxx
> 32. http://lists.xensource.com/xen-users
> 33. mailto:kjw53@xxxxxxxxx
> 34. mailto:Xen-users@xxxxxxxxxxxxxxxxxxx
> 35. http://lists.xensource.com/xen-users
> 36. mailto:Xen-users@xxxxxxxxxxxxxxxxxxx
> 37. http://lists.xensource.com/xen-users
> 38. mailto:Xen-users@xxxxxxxxxxxxxxxxxxx
> 39. http://lists.xensource.com/xen-users
> 40. mailto:pasik@xxxxxx
> 41. mailto:kjw53@xxxxxxxxx
> 42. mailto:Xen-users@xxxxxxxxxxxxxxxxxxx
> 43. http://lists.xensource.com/xen-users
> 44. mailto:kjw53@xxxxxxxxx
> 45. mailto:Xen-users@xxxxxxxxxxxxxxxxxxx
> 46. http://lists.xensource.com/xen-users
> 47. mailto:Xen-users@xxxxxxxxxxxxxxxxxxx
> 48. http://lists.xensource.com/xen-users
> 49. mailto:Xen-users@xxxxxxxxxxxxxxxxxxx
> 50. http://lists.xensource.com/xen-users
> 51. mailto:Xen-users@xxxxxxxxxxxxxxxxxxx
> 52. http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home