[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • To: Pasi KÃrkkÃinen <pasik@xxxxxx>
  • From: JÃrn Odberg <jorn.odberg@xxxxxxxxx>
  • Date: Tue, 19 Jan 2010 21:46:26 +0100
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 19 Jan 2010 12:47:19 -0800
  • 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=vyp1gHjlu65haaAixCnvXuh1cMohncOKjjD8P4ytB0E3WXsdAvLTHWeJMKucOg+s6J WrKtb9mlzwUE6tD1YC3QUsOzC+ehuzn5ZHO9BBLySK6km5VB9upB853d4ccUnYSSlJHO J87sxAwwyQPpSf7zBadsRntf+4AeWubhz5f6s=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

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? ;)


// JÃrn


On Tue, Jan 19, 2010 at 9:35 PM, Pasi KÃrkkÃinen <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]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]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]Xen-users@xxxxxxxxxxxxxxxxxxx
> Â Â Â> Ã ÂÃ ÂÃ [3][4]http://lists.xensource.com/xen-users
> Â Â Â>
> Â Â Â> References
> Â Â Â>
> Â Â Â> Ã ÂÃ Visible links
> Â Â Â> Ã ÂÃ 1. mailto:[5]kjw53@xxxxxxxxx
> Â Â Â> Ã ÂÃ 2. mailto:[6]Xen-users@xxxxxxxxxxxxxxxxxxx
> Â Â Â> Ã ÂÃ 3. [7]http://lists.xensource.com/xen-users
> Â Â Â> _______________________________________________
> Â Â Â> Xen-users mailing list
> Â Â Â> [8]Xen-users@xxxxxxxxxxxxxxxxxxx
> Â Â Â> [9]http://lists.xensource.com/xen-users
>
> Â Â Â_______________________________________________
> Â Â ÂXen-users mailing list
> Â Â Â[10]Xen-users@xxxxxxxxxxxxxxxxxxx
> Â Â Â[11]http://lists.xensource.com/xen-users
>
> References
>
> Â ÂVisible links
> Â Â1. mailto:pasik@xxxxxx
> Â Â2. mailto:kjw53@xxxxxxxxx
> Â Â3. mailto:Xen-users@xxxxxxxxxxxxxxxxxxx
> Â Â4. http://lists.xensource.com/xen-users
> Â Â5. mailto:kjw53@xxxxxxxxx
> Â Â6. mailto:Xen-users@xxxxxxxxxxxxxxxxxxx
> Â Â7. http://lists.xensource.com/xen-users
> Â Â9. http://lists.xensource.com/xen-users
> Â 10. mailto:Xen-users@xxxxxxxxxxxxxxxxxxx
> Â 11. http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

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