[Top] [All Lists]
[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 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

 

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.

Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.