* bogus motherboard? IOMMU does not work
@ 2010-07-01 12:11 Csillag Kristof
0 siblings, 0 replies; 3+ messages in thread
From: Csillag Kristof @ 2010-07-01 12:11 UTC (permalink / raw)
To: xen-devel
[-- Attachment #1: Type: text/plain, Size: 574 bytes --]
Hi all,
I would like to get my system to work with IOMMU.
(The long-term goal is VGA passthru.)
System is as follows:
CPU: Core 2 Duo E6600
MB: Foxconn G9657MA-8EKRS2H (w. latest bios: 631F1P61)
Virtualization support is enabled in BIOS. (These is only one option.)
Hypervisor: xen 4.0.0 from Debian, AMD64
Xen config: iommu=verbose
output of xen dmesg is attached.
HVM domains work (lasd tried with xen 3.2), but IOMMU is disabled,
according to xen dmesg.
What can I do to increase the chances of getting this to work?
Thank you for your help:
Kristof Csillag
[-- Attachment #2: xen_dmesg --]
[-- Type: text/plain, Size: 3584 bytes --]
(XEN) Xen version 4.0.0 (Debian 4.0.0-2) (waldi@debian.org) (gcc version 4.4.4 (Debian 4.4.4-5) ) Mon Jun 21 15:25:05 UTC 2010
(XEN) Command line: iommu=verbose
(XEN) Video information:
(XEN) VGA is text mode 80x25, font 8x16
(XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds
(XEN) EDID info not retrieved because no DDC retrieval method detected
(XEN) Disc information:
(XEN) Found 2 MBR signatures
(XEN) Found 2 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 000000000009f000 (usable)
(XEN) 000000000009f000 - 00000000000a0000 (reserved)
(XEN) 00000000000f0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 00000000cf6e0000 (usable)
(XEN) 00000000cf6e0000 - 00000000cf6e3000 (ACPI NVS)
(XEN) 00000000cf6e3000 - 00000000cf6f0000 (ACPI data)
(XEN) 00000000cf6f0000 - 00000000cf700000 (reserved)
(XEN) 00000000e0000000 - 00000000f0000000 (reserved)
(XEN) 00000000fec00000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 0000000230000000 (usable)
(XEN) ACPI: RSDP 000F80C0, 0024 (r2 IntelR)
(XEN) ACPI: XSDT CF6E30C0, 0054 (r1 IntelR AWRDACPI 42302E31 AWRD 0)
(XEN) ACPI: FACP CF6E7F80, 00F4 (r3 IntelR AWRDACPI 42302E31 AWRD 0)
(XEN) ACPI: DSDT CF6E3240, 4CD9 (r1 INTELR AWRDACPI 1000 MSFT 100000E)
(XEN) ACPI: FACS CF6E0000, 0040
(XEN) ACPI: HPET CF6E81C0, 0038 (r1 IntelR AWRDACPI 42302E31 AWRD 98)
(XEN) ACPI: MCFG CF6E8240, 003C (r1 IntelR AWRDACPI 42302E31 AWRD 0)
(XEN) ACPI: APIC CF6E80C0, 0084 (r1 IntelR AWRDACPI 42302E31 AWRD 0)
(XEN) ACPI: SSDT CF6E82C0, 01EF (r1 PmRef Cpu0Ist 3000 INTL 20041203)
(XEN) ACPI: SSDT CF6E8820, 02F9 (r1 PmRef CpuPm 3000 INTL 20041203)
(XEN) System RAM: 8140MB (8336008kB)
(XEN) Domain heap initialised
(XEN) Processor #0 6:15 APIC version 20
(XEN) Processor #1 6:15 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) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2403.059 MHz processor.
(XEN) Initing memory sharing.
(XEN) VMX: Supported advanced features:
(XEN) - APIC TPR shadow
(XEN) - MSR direct-access bitmap
(XEN) HVM: ASIDs disabled.
(XEN) HVM: VMX enabled
(XEN) I/O virtualisation disabled
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) checking TSC synchronization across 2 CPUs: passed.
(XEN) Platform timer is 14.318MHz HPET
(XEN) Brought up 2 CPUs
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen kernel: 64-bit, lsb, compat32
(XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x16c1000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0000000224000000->0000000228000000 (2021044 pages to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff81000000->ffffffff816c1000
(XEN) Init. ramdisk: ffffffff816c1000->ffffffff82f79a00
(XEN) Phys-Mach map: ffffffff82f7a000->ffffffff83f055a0
(XEN) Start info: ffffffff83f06000->ffffffff83f064b4
(XEN) Page tables: ffffffff83f07000->ffffffff83f2a000
(XEN) Boot stack: ffffffff83f2a000->ffffffff83f2b000
(XEN) TOTAL: ffffffff80000000->ffffffff84000000
(XEN) ENTRY ADDRESS: ffffffff81501200
(XEN) Dom0 has maximum 2 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 164kB init memory.
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
* bogus motherboard? IOMMU does not work
@ 2010-07-02 14:03 Csillag Kristóf
2010-07-02 16:05 ` Konrad Rzeszutek Wilk
0 siblings, 1 reply; 3+ messages in thread
From: Csillag Kristóf @ 2010-07-02 14:03 UTC (permalink / raw)
To: xen-devel
[-- Attachment #1: Type: text/plain, Size: 574 bytes --]
Hi all,
I would like to get my system to work with IOMMU.
(The long-term goal is VGA passthru.)
System is as follows:
CPU: Core 2 Duo E6600
MB: Foxconn G9657MA-8EKRS2H (w. latest bios: 631F1P61)
Virtualization support is enabled in BIOS. (These is only one option.)
Hypervisor: xen 4.0.0 from Debian, AMD64
Xen config: iommu=verbose
output of xen dmesg is attached.
HVM domains work (lasd tried with xen 3.2), but IOMMU is disabled,
according to xen dmesg.
What can I do to increase the chances of getting this to work?
Thank you for your help:
Kristof Csillag
[-- Attachment #2: xen_dmesg --]
[-- Type: application/octet-stream, Size: 3585 bytes --]
(XEN) Xen version 4.0.0 (Debian 4.0.0-2) (waldi@debian.org) (gcc version 4.4.4 (Debian 4.4.4-5) ) Mon Jun 21 15:25:05 UTC 2010
(XEN) Command line: iommu=verbose
(XEN) Video information:
(XEN) VGA is text mode 80x25, font 8x16
(XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds
(XEN) EDID info not retrieved because no DDC retrieval method detected
(XEN) Disc information:
(XEN) Found 2 MBR signatures
(XEN) Found 2 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 000000000009f000 (usable)
(XEN) 000000000009f000 - 00000000000a0000 (reserved)
(XEN) 00000000000f0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 00000000cf6e0000 (usable)
(XEN) 00000000cf6e0000 - 00000000cf6e3000 (ACPI NVS)
(XEN) 00000000cf6e3000 - 00000000cf6f0000 (ACPI data)
(XEN) 00000000cf6f0000 - 00000000cf700000 (reserved)
(XEN) 00000000e0000000 - 00000000f0000000 (reserved)
(XEN) 00000000fec00000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 0000000230000000 (usable)
(XEN) ACPI: RSDP 000F80C0, 0024 (r2 IntelR)
(XEN) ACPI: XSDT CF6E30C0, 0054 (r1 IntelR AWRDACPI 42302E31 AWRD 0)
(XEN) ACPI: FACP CF6E7F80, 00F4 (r3 IntelR AWRDACPI 42302E31 AWRD 0)
(XEN) ACPI: DSDT CF6E3240, 4CD9 (r1 INTELR AWRDACPI 1000 MSFT 100000E)
(XEN) ACPI: FACS CF6E0000, 0040
(XEN) ACPI: HPET CF6E81C0, 0038 (r1 IntelR AWRDACPI 42302E31 AWRD 98)
(XEN) ACPI: MCFG CF6E8240, 003C (r1 IntelR AWRDACPI 42302E31 AWRD 0)
(XEN) ACPI: APIC CF6E80C0, 0084 (r1 IntelR AWRDACPI 42302E31 AWRD 0)
(XEN) ACPI: SSDT CF6E82C0, 01EF (r1 PmRef Cpu0Ist 3000 INTL 20041203)
(XEN) ACPI: SSDT CF6E8820, 02F9 (r1 PmRef CpuPm 3000 INTL 20041203)
(XEN) System RAM: 8140MB (8336008kB)
(XEN) Domain heap initialised
(XEN) Processor #0 6:15 APIC version 20
(XEN) Processor #1 6:15 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) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2403.059 MHz processor.
(XEN) Initing memory sharing.
(XEN) VMX: Supported advanced features:
(XEN) - APIC TPR shadow
(XEN) - MSR direct-access bitmap
(XEN) HVM: ASIDs disabled.
(XEN) HVM: VMX enabled
(XEN) I/O virtualisation disabled
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) checking TSC synchronization across 2 CPUs: passed.
(XEN) Platform timer is 14.318MHz HPET
(XEN) Brought up 2 CPUs
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen kernel: 64-bit, lsb, compat32
(XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x16c1000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0000000224000000->0000000228000000 (2021044 pages to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff81000000->ffffffff816c1000
(XEN) Init. ramdisk: ffffffff816c1000->ffffffff82f79a00
(XEN) Phys-Mach map: ffffffff82f7a000->ffffffff83f055a0
(XEN) Start info: ffffffff83f06000->ffffffff83f064b4
(XEN) Page tables: ffffffff83f07000->ffffffff83f2a000
(XEN) Boot stack: ffffffff83f2a000->ffffffff83f2b000
(XEN) TOTAL: ffffffff80000000->ffffffff84000000
(XEN) ENTRY ADDRESS: ffffffff81501200
(XEN) Dom0 has maximum 2 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 164kB init memory.
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: bogus motherboard? IOMMU does not work
2010-07-02 14:03 bogus motherboard? IOMMU does not work Csillag Kristóf
@ 2010-07-02 16:05 ` Konrad Rzeszutek Wilk
0 siblings, 0 replies; 3+ messages in thread
From: Konrad Rzeszutek Wilk @ 2010-07-02 16:05 UTC (permalink / raw)
To: Csillag Kristóf; +Cc: xen-devel
On Fri, Jul 02, 2010 at 04:03:04PM +0200, Csillag Kristóf wrote:
> Hi all,
>
> I would like to get my system to work with IOMMU.
You can't with that motherboard.
>
> (The long-term goal is VGA passthru.)
>
> System is as follows:
>
> CPU: Core 2 Duo E6600
> MB: Foxconn G9657MA-8EKRS2H (w. latest bios: 631F1P61)
> Virtualization support is enabled in BIOS. (These is only one option.)
>
> Hypervisor: xen 4.0.0 from Debian, AMD64
> Xen config: iommu=verbose
> output of xen dmesg is attached.
>
> HVM domains work (lasd tried with xen 3.2), but IOMMU is disabled,
> according to xen dmesg.
>
> What can I do to increase the chances of getting this to work?
Get a new motherboard that has the VT-d chipset. This is not a software
feature, but a chipset on the board.
Look at this list: http://en.wikipedia.org/wiki/List_of_Intel_chipsets
and look for VT-d.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-07-02 16:05 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-07-02 14:03 bogus motherboard? IOMMU does not work Csillag Kristóf
2010-07-02 16:05 ` Konrad Rzeszutek Wilk
-- strict thread matches above, loose matches on Subject: below --
2010-07-01 12:11 Csillag Kristof
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).