|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] xen, pvops & nvidia graphics
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
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |