Option iommu=1 causes hypervisor to start debugger

Option iommu=1 causes hypervisor to start debugger

[Alexia Benington]

Hi,

In changeset 19130:c8962b24fb50, when using iommu=1, it goes into the
hypervisor debugger. Why is this so? Thanks.

-Alex

Re: Option iommu=1 causes hypervisor to start debugger

[Keir Fraser]

Perhaps the VT-d hardware/BIOS on your system causes Xen to crash and hence
drop itself into the debugger environment?

 -- Keir

On 02/02/2009 21:16, "Alexia Benington" <alexbenington@gmail.com> wrote:

> Hi,
> 
> In changeset 19130:c8962b24fb50, when using iommu=1, it goes into the
> hypervisor debugger. Why is this so? Thanks.
> 
> -Alex
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

Re: Option iommu=1 causes hypervisor to start debugger

[Alexia Benington]

[-- Attachment #1: Type: text/plain, Size: 544 bytes --]

At this moment, I'm not really sure. I'm using Intel DQ45CB with Bios
CBQ4510H.86A.0073.2009.0122.1353. Is anybody else using the same board
and having trouble with the I/O passthrough?

I've attached the connected console's output, can't really pick up
anything abnormal though, except that it just stops as you see it.

-Alex

On Mon, Feb 2, 2009 at 4:41 PM, Keir Fraser <keir.fraser@eu.citrix.com> wrote:
> Perhaps the VT-d hardware/BIOS on your system causes Xen to crash and hence
> drop itself into the debugger environment?
>
>  -- Keir

[-- Attachment #2: log --]
[-- Type: application/octet-stream, Size: 10199 bytes --]

 __  __            _____ _  _                      _        _     _      
 \ \/ /___ _ __   |___ /| || |     _   _ _ __  ___| |_ __ _| |__ | | ___ 
  \  // _ \ '_ \    |_ \| || |_ __| | | | '_ \/ __| __/ _` | '_ \| |/ _ \
  /  \  __/ | | |  ___) |__   _|__| |_| | | | \__ \ || (_| | |_) | |  __/
 /_/\_\___|_| |_| |____(_) |_|     \__,_|_| |_|___/\__\__,_|_.__/|_|\___|
                                                                         
(XEN) Xen version 3.4-unstable (xxx@xxx.xxx.xxx) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) Mon Feb  2 01:36:29 EST 2009
(XEN) Latest ChangeSet: Fri Jan 30 11:12:57 2009 +0900 19130:c8962b24fb50
(XEN) Command line: loglvl=all guest_loglvl=all com1=115200,8n1 console=com1 iommu=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 0 MBR signatures
(XEN)  Found 1 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009e800 (usable)
(XEN)  000000000009e800 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000bd6cb000 (usable)
(XEN)  00000000bd6cb000 - 00000000bd70d000 (ACPI NVS)
(XEN)  00000000bd70d000 - 00000000bd82b000 (reserved)
(XEN)  00000000bd82b000 - 00000000bd83f000 (ACPI NVS)
(XEN)  00000000bd83f000 - 00000000bd940000 (reserved)
(XEN)  00000000bd940000 - 00000000bd941000 (ACPI NVS)
(XEN)  00000000bd941000 - 00000000bd946000 (reserved)
(XEN)  00000000bd946000 - 00000000bd94e000 (ACPI data)
(XEN)  00000000bd94e000 - 00000000bd969000 (ACPI NVS)
(XEN)  00000000bd969000 - 00000000bd988000 (reserved)
(XEN)  00000000bd988000 - 00000000bd98e000 (ACPI NVS)
(XEN)  00000000bd98e000 - 00000000bdb00000 (usable)
(XEN)  00000000bdc00000 - 00000000c0000000 (reserved)
(XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
(XEN)  00000000ff000000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 000000013c000000 (usable)
(XEN) System RAM: 3991MB (4087660kB)
(XEN) ACPI: RSDP 000F03C0, 0024 (r2  INTEL)
(XEN) ACPI: XSDT BD94CE18, 005C (r1 INTEL  DQ45CB         49 MSFT    10013)
(XEN) ACPI: FACP BD94BD98, 00F4 (r4  INTEL    A M I  6222004 MSFT    10013)
(XEN) ACPI: DSDT BD946018, 4EE8 (r1 INTEL  DQ45CB         49 INTL 20051117)
(XEN) ACPI: FACS BD954F40, 0040
(XEN) ACPI: APIC BD94BF18, 006C (r2 INTEL  DQ45CB         49 MSFT    10013)
(XEN) ACPI: MCFG BD956E18, 003C (r1 INTEL  DQ45CB         49 MSFT       97)
(XEN) ACPI: ASF! BD955D18, 00A0 (r32 INTEL  DQ45CB         49 TFSM    F4240)
(XEN) ACPI: SPCR BD956D18, 0050 (r1 INTEL  DQ45CB         49 AMI.        3)
(XEN) ACPI: TCPA BD956C98, 0032 (r2 INTEL  DQ45CB         49 MSFT  1000013)
(XEN) ACPI: DMAR BD940C18, 0120 (r1 INTEL  DQ45CB         49 INTL        1)
(XEN) NUMA turned off
(XEN) Faking a node at 0000000000000000-000000013c000000
(XEN) Domain heap initialised
(XEN) DMI 2.4 present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x408
(XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[404,0], pm1x_evt[400,0]
(XEN) ACPI:                  wakeup_vec[bd954f4c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
(XEN) Processor #2 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
(XEN) Processor #3 7:7 APIC version 20
(XEN) ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) [VT-D]dmar.c:459: Host address width 36
(XEN) [VT-D]dmar.c:468: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:336: dmaru->address = fed90000
(XEN) [VT-D]dmar.c:287: found endpoint: bdf = 0:1b.0
(XEN) [VT-D]dmar.c:468: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:336: dmaru->address = fed91000
(XEN) [VT-D]dmar.c:287: found endpoint: bdf = 0:2.0
(XEN) [VT-D]dmar.c:287: found endpoint: bdf = 0:2.1
(XEN) [VT-D]dmar.c:468: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:336: dmaru->address = fed92000
(XEN) [VT-D]dmar.c:287: found endpoint: bdf = 0:3.0
(XEN) [VT-D]dmar.c:287: found endpoint: bdf = 0:3.2
(XEN) [VT-D]dmar.c:287: found endpoint: bdf = 0:3.3
(XEN) [VT-D]dmar.c:468: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:336: dmaru->address = fed93000
(XEN) [VT-D]dmar.c:345: found INCLUDE_ALL
(XEN) [VT-D]dmar.c:472: found ACPI_DMAR_RMRR
(XEN) [VT-D]dmar.c:287: found endpoint: bdf = 0:1d.0
(XEN) [VT-D]dmar.c:287: found endpoint: bdf = 0:1d.1
(XEN) [VT-D]dmar.c:287: found endpoint: bdf = 0:1d.2
(XEN) [VT-D]dmar.c:287: found endpoint: bdf = 0:1d.7
(XEN) [VT-D]dmar.c:287: found endpoint: bdf = 0:1a.0
(XEN) [VT-D]dmar.c:287: found endpoint: bdf = 0:1a.1
(XEN) [VT-D]dmar.c:287: found endpoint: bdf = 0:1a.2
(XEN) [VT-D]dmar.c:287: found endpoint: bdf = 0:1a.7
(XEN) [VT-D]dmar.c:472: found ACPI_DMAR_RMRR
(XEN) [VT-D]dmar.c:287: found endpoint: bdf = 0:2.0
(XEN) [VT-D]dmar.c:287: found endpoint: bdf = 0:2.1
(XEN) Intel VT-d has been enabled, snoop_control=1.
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Initializing CPU#0
(XEN) Detected 2499.798 MHz processor.
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 3072K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 0
(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) MCE: Intel newly family MC Init
(XEN) Intel machine check reporting enabled on CPU#0.
(XEN) CPU0: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU0 has no CMCI support
(XEN) CPU0: Intel(R) Core(TM)2 Quad  CPU   Q9300  @ 2.50GHz stepping 07
(XEN) Booting processor 1/1 eip 8c000
(XEN) Initializing CPU#1
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 3072K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 1
(XEN) MCE: Intel newly family MC Init
(XEN) Intel machine check reporting enabled on CPU#1.
(XEN) CPU1: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU1 has no CMCI support
(XEN) CPU1: Intel(R) Core(TM)2 Quad  CPU   Q9300  @ 2.50GHz stepping 07
(XEN) Booting processor 2/2 eip 8c000
(XEN) Initializing CPU#2
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 3072K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 2
(XEN) MCE: Intel newly family MC Init
(XEN) Intel machine check reporting enabled on CPU#2.
(XEN) CPU2: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU2 has no CMCI support
(XEN) CPU2: Intel(R) Core(TM)2 Quad  CPU   Q9300  @ 2.50GHz stepping 07
(XEN) Booting processor 3/3 eip 8c000
(XEN) Initializing CPU#3
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 3072K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 3
(XEN) MCE: Intel newly family MC Init
(XEN) Intel machine check reporting enabled on CPU#3.
(XEN) CPU3: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU3 has no CMCI support
(XEN) CPU3: Intel(R) Core(TM)2 Quad  CPU   Q9300  @ 2.50GHz stepping 07
(XEN) Total of 4 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) checking TSC synchronization across 4 CPUs: passed.
(XEN) Platform timer is 3.579MHz ACPI PM Timer
(XEN) microcode.c:73:d32767 microcode: CPU1 resumed
(XEN) microcode.c:73:d32767 microcode: CPU2 resumed
(XEN) Brought up 4 CPUs
(XEN) microcode.c:73:d32767 microcode: CPU3 resumed
(XEN) [VT-D]iommu.c:1697: Queued Invalidation hardware not found
(XEN) [VT-D]iommu.c:1697: Queued Invalidation hardware not found
(XEN) [VT-D]iommu.c:1697: Queued Invalidation hardware not found
(XEN) [VT-D]iommu.c:1697: Queued Invalidation hardware not found
(XEN) [VT-D]iommu.c:1705: Interrupt Remapping hardware not found
(XEN) [VT-D]iommu.c:1705: Interrupt Remapping hardware not found
(XEN) [VT-D]iommu.c:1705: Interrupt Remapping hardware not found
(XEN) [VT-D]iommu.c:1705: Interrupt Remapping hardware not found
(XEN) I/O virtualisation enabled
(XEN) I/O virtualisation for PV guests disabled
(XEN) ACPI sleep modes: S3
(XEN) mcheck_poll: Init_mcheck_timer
(XEN) mcheck_poll: Machine check polling timer started.
(XEN) [VT-D]iommu.c:1248:d32767 domain_context_mapping:PCI: bdf = 0:0.0
(XEN) [VT-D]iommu.c:1248:d32767 domain_context_mapping:PCI: bdf = 0:2.0
(XEN) [VT-D]iommu.c:1248:d32767 domain_context_mapping:PCI: bdf = 0:2.1
(XEN) [VT-D]iommu.c:1248:d32767 domain_context_mapping:PCI: bdf = 0:3.0
(XEN) [VT-D]iommu.c:1248:d32767 domain_context_mapping:PCI: bdf = 0:3.2
(XEN) [VT-D]iommu.c:1248:d32767 domain_context_mapping:PCI: bdf = 0:3.3
(XEN) [VT-D]iommu.c:1248:d32767 domain_context_mapping:PCI: bdf = 0:19.0
(XEN) [VT-D]iommu.c:1248:d32767 domain_context_mapping:PCI: bdf = 0:1a.0
(XEN) [VT-D]iommu.c:1248:d32767 domain_context_mapping:PCI: bdf = 0:1a.1
(XEN) [VT-D]iommu.c:1248:d32767 domain_context_mapping:PCI: bdf = 0:1a.2
(XEN) [VT-D]iommu.c:1248:d32767 domain_context_mapping:PCI: bdf = 0:1a.7
(XEN) [VT-D]iommu.c:1241:d32767 domain_context_mapping:PCIe: bdf = 0:1b.0
(XEN) [VT-D]iommu.c:1248:d32767 domain_context_mapping:PCI: bdf = 0:1d.0
(XEN) [VT-D]iommu.c:1248:d32767 domain_context_mapping:PCI: bdf = 0:1d.1
(XEN) [VT-D]iommu.c:1248:d32767 domain_context_mapping:PCI: bdf = 0:1d.2
(XEN) [VT-D]iommu.c:1248:d32767 domain_context_mapping:PCI: bdf = 0:1d.7
(XEN) [VT-D]iommu.c:1248:d32767 domain_context_mapping:PCI: bdf = 0:1f.0
(XEN) [VT-D]iommu.c:1248:d32767 domain_context_mapping:PCI: bdf = 0:1f.2
(XEN) [VT-D]iommu.c:1248:d32767 domain_context_mapping:PCI: bdf = 0:1f.3
(XEN) [VT-D]iommu.c:1248:d32767 domain_context_mapping:PCI: bdf = 0:1f.5
(XEN) [VT-D]iommu.c:1248:d32767 domain_context_mapping:PCI: bdf = 1:1.0

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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

Re: Option iommu=1 causes hypervisor to start debugger

[Neo Jia]

I didn't see any error in that log file. How can you tell it is
trapped into debugger?

Thanks,
Neo

On Mon, Feb 2, 2009 at 1:48 PM, Alexia Benington
<alexbenington@gmail.com> wrote:
> At this moment, I'm not really sure. I'm using Intel DQ45CB with Bios
> CBQ4510H.86A.0073.2009.0122.1353. Is anybody else using the same board
> and having trouble with the I/O passthrough?
>
> I've attached the connected console's output, can't really pick up
> anything abnormal though, except that it just stops as you see it.
>
> -Alex
>
> On Mon, Feb 2, 2009 at 4:41 PM, Keir Fraser <keir.fraser@eu.citrix.com> wrote:
>> Perhaps the VT-d hardware/BIOS on your system causes Xen to crash and hence
>> drop itself into the debugger environment?
>>
>>  -- Keir
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>



-- 
I would remember that if researchers were not ambitious
probably today we haven't the technology we are using!

Re: Option iommu=1 causes hypervisor to start debugger

[Alexia Benington]

Apologies, I should have clarified that it didn't automatically step
into the debugger, but hang at the last line of the output I attached
earlier. Pressing 'h' would show the list of installed handlers.

Thanks.

-Alex

On Mon, Feb 2, 2009 at 4:53 PM, Neo Jia <neojia@gmail.com> wrote:
> I didn't see any error in that log file. How can you tell it is
> trapped into debugger?
>
> Thanks,
> Neo
>
> On Mon, Feb 2, 2009 at 1:48 PM, Alexia Benington
> <alexbenington@gmail.com> wrote:
>> At this moment, I'm not really sure. I'm using Intel DQ45CB with Bios
>> CBQ4510H.86A.0073.2009.0122.1353. Is anybody else using the same board
>> and having trouble with the I/O passthrough?
>>
>> I've attached the connected console's output, can't really pick up
>> anything abnormal though, except that it just stops as you see it.
>>
>> -Alex
>>
>> On Mon, Feb 2, 2009 at 4:41 PM, Keir Fraser <keir.fraser@eu.citrix.com> wrote:
>>> Perhaps the VT-d hardware/BIOS on your system causes Xen to crash and hence
>>> drop itself into the debugger environment?
>>>
>>>  -- Keir
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>>
>>
>
>
>
> --
> I would remember that if researchers were not ambitious
> probably today we haven't the technology we are using!
>

Re: Option iommu=1 causes hypervisor to start debugger

[Alexia Benington]

If I do not include the iommu option, I/O virtualisation is disabled.
I never thought that iommu is a necessary prerequisite for I/O virt,
or am I mistaken?

-Alex

Re: Option iommu=1 causes hypervisor to start debugger

[Keir Fraser]

It's needed for passing through physical devices to HVM guests.

 -- Keir

On 02/02/2009 23:42, "Alexia Benington" <alexbenington@gmail.com> wrote:

> If I do not include the iommu option, I/O virtualisation is disabled.
> I never thought that iommu is a necessary prerequisite for I/O virt,
> or am I mistaken?
> 
> -Alex
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

Re: Option iommu=1 causes hypervisor to start debugger

[Alexia Benington]

Thanks Keir. Perhaps I should try with Yu Zhao's patch and see if that
fixes the problem.

-Alex

On Tue, Feb 3, 2009 at 3:06 AM, Keir Fraser <keir.fraser@eu.citrix.com> wrote:
> It's needed for passing through physical devices to HVM guests.
>
>  -- Keir
>
> On 02/02/2009 23:42, "Alexia Benington" <alexbenington@gmail.com> wrote:
>
>> If I do not include the iommu option, I/O virtualisation is disabled.
>> I never thought that iommu is a necessary prerequisite for I/O virt,
>> or am I mistaken?
>>
>> -Alex
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>
>
>

Re: Option iommu=1 causes hypervisor to start debugger

[Zhao, Yu]

Which patch are you talking about? Since we can't get any clue from your 
log, can you please send us the output of `lspci -vvv'?

Thanks,
Yu

Alexia Benington wrote:
> Thanks Keir. Perhaps I should try with Yu Zhao's patch and see if that
> fixes the problem.
> 
> -Alex
> 
> On Tue, Feb 3, 2009 at 3:06 AM, Keir Fraser <keir.fraser@eu.citrix.com> wrote:
>> It's needed for passing through physical devices to HVM guests.
>>
>>  -- Keir
>>
>> On 02/02/2009 23:42, "Alexia Benington" <alexbenington@gmail.com> wrote:
>>
>>> If I do not include the iommu option, I/O virtualisation is disabled.
>>> I never thought that iommu is a necessary prerequisite for I/O virt,
>>> or am I mistaken?
>>>
>>> -Alex
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xensource.com
>>> http://lists.xensource.com/xen-devel
>>
>>
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

Re: Option iommu=1 causes hypervisor to start debugger

[Alexia Benington]

[-- Attachment #1: Type: text/plain, Size: 1444 bytes --]

I was referring to the fix titled "ioemu: fix PCI ROM handling problem
in passthrough". Seriously, I don't even know if the problem is
related. Just trying something because I'm totally clueless now.

I've attached the lspci. Let me know if you need more info. Will be
glad to provide.

Thanks guys.

- Alex

On Tue, Feb 3, 2009 at 8:55 PM, Zhao, Yu <yu.zhao@intel.com> wrote:
> Which patch are you talking about? Since we can't get any clue from your
> log, can you please send us the output of `lspci -vvv'?
>
> Thanks,
> Yu
>
> Alexia Benington wrote:
>>
>> Thanks Keir. Perhaps I should try with Yu Zhao's patch and see if that
>> fixes the problem.
>>
>> -Alex
>>
>> On Tue, Feb 3, 2009 at 3:06 AM, Keir Fraser <keir.fraser@eu.citrix.com>
>> wrote:
>>>
>>> It's needed for passing through physical devices to HVM guests.
>>>
>>>  -- Keir
>>>
>>> On 02/02/2009 23:42, "Alexia Benington" <alexbenington@gmail.com> wrote:
>>>
>>>> If I do not include the iommu option, I/O virtualisation is disabled.
>>>> I never thought that iommu is a necessary prerequisite for I/O virt,
>>>> or am I mistaken?
>>>>
>>>> -Alex
>>>>
>>>> _______________________________________________
>>>> Xen-devel mailing list
>>>> Xen-devel@lists.xensource.com
>>>> http://lists.xensource.com/xen-devel
>>>
>>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>
>

[-- Attachment #2: lspci --]
[-- Type: application/octet-stream, Size: 11331 bytes --]

00:00.0 Host bridge: Intel Corporation Unknown device 2e10 (rev 03)
	Subsystem: Intel Corporation Unknown device 1003
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
	Latency: 0
	Capabilities: <access denied>

00:02.0 VGA compatible controller: Intel Corporation Unknown device 2e12 (rev 03) (prog-if 00 [VGA])
	Subsystem: Intel Corporation Unknown device 1003
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at d0000000 (64-bit, non-prefetchable) [disabled] [size=4M]
	Region 2: Memory at c0000000 (64-bit, prefetchable) [disabled] [size=256M]
	Region 4: I/O ports at f220 [disabled] [size=8]
	Capabilities: <access denied>

00:02.1 Display controller: Intel Corporation Unknown device 2e13 (rev 03)
	Subsystem: Intel Corporation Unknown device 1003
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Region 0: Memory at d0400000 (64-bit, non-prefetchable) [disabled] [size=1M]
	Capabilities: <access denied>

00:03.0 Communication controller: Intel Corporation Unknown device 2e14 (rev 03)
	Subsystem: Intel Corporation Unknown device 1003
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at d0627100 (64-bit, non-prefetchable) [size=16]
	Capabilities: <access denied>

00:03.2 IDE interface: Intel Corporation Unknown device 2e16 (rev 03) (prog-if 85 [Master SecO PriO])
	Subsystem: Intel Corporation Unknown device 1003
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin C routed to IRQ 10
	Region 0: I/O ports at f210 [size=8]
	Region 1: I/O ports at f200 [size=4]
	Region 2: I/O ports at f1f0 [size=8]
	Region 3: I/O ports at f1e0 [size=4]
	Region 4: I/O ports at f1d0 [size=16]
	Capabilities: <access denied>

00:03.3 Serial controller: Intel Corporation Unknown device 2e17 (rev 03) (prog-if 02 [16550])
	Subsystem: Intel Corporation Unknown device 1003
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin B routed to IRQ 3
	Region 0: I/O ports at f1c0 [size=8]
	Region 1: Memory at d0625000 (32-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>

00:19.0 Ethernet controller: Intel Corporation Unknown device 10de (rev 02)
	Subsystem: Intel Corporation Unknown device 1003
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin A routed to IRQ 7
	Region 0: Memory at d0600000 (32-bit, non-prefetchable) [size=128K]
	Region 1: Memory at d0624000 (32-bit, non-prefetchable) [size=4K]
	Region 2: I/O ports at f100 [size=32]
	Capabilities: <access denied>

00:1a.0 USB Controller: Intel Corporation Unknown device 3a67 (rev 02) (prog-if 00 [UHCI])
	Subsystem: Intel Corporation Unknown device 1003
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin A routed to IRQ 16
	Region 4: I/O ports at f0e0 [size=32]
	Capabilities: <access denied>

00:1a.1 USB Controller: Intel Corporation Unknown device 3a68 (rev 02) (prog-if 00 [UHCI])
	Subsystem: Intel Corporation Unknown device 1003
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin B routed to IRQ 18
	Region 4: I/O ports at f0c0 [size=32]
	Capabilities: <access denied>

00:1a.2 USB Controller: Intel Corporation Unknown device 3a69 (rev 02) (prog-if 00 [UHCI])
	Subsystem: Intel Corporation Unknown device 1003
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin C routed to IRQ 19
	Region 4: I/O ports at f0a0 [size=32]
	Capabilities: <access denied>

00:1a.7 USB Controller: Intel Corporation Unknown device 3a6c (rev 02) (prog-if 20 [EHCI])
	Subsystem: Intel Corporation Unknown device 1003
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin C routed to IRQ 10
	Region 0: Memory at d0626c00 (32-bit, non-prefetchable) [size=1K]
	Capabilities: <access denied>

00:1b.0 Audio device: Intel Corporation Unknown device 3a6e (rev 02)
	Subsystem: Intel Corporation Unknown device 1003
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 10
	Region 0: Memory at d0620000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>

00:1d.0 USB Controller: Intel Corporation Unknown device 3a64 (rev 02) (prog-if 00 [UHCI])
	Subsystem: Intel Corporation Unknown device 1003
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin A routed to IRQ 20
	Region 4: I/O ports at f080 [size=32]
	Capabilities: <access denied>

00:1d.1 USB Controller: Intel Corporation Unknown device 3a65 (rev 02) (prog-if 00 [UHCI])
	Subsystem: Intel Corporation Unknown device 1003
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin B routed to IRQ 17
	Region 4: I/O ports at f060 [size=32]
	Capabilities: <access denied>

00:1d.2 USB Controller: Intel Corporation Unknown device 3a66 (rev 02) (prog-if 00 [UHCI])
	Subsystem: Intel Corporation Unknown device 1003
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin C routed to IRQ 19
	Region 4: I/O ports at f040 [size=32]
	Capabilities: <access denied>

00:1d.7 USB Controller: Intel Corporation Unknown device 3a6a (rev 02) (prog-if 20 [EHCI])
	Subsystem: Intel Corporation Unknown device 1003
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin A routed to IRQ 3
	Region 0: Memory at d0626800 (32-bit, non-prefetchable) [size=1K]
	Capabilities: <access denied>

00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a2) (prog-if 01 [Subtractive decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
	I/O behind bridge: 0000f000-00000fff
	Memory behind bridge: d0500000-d05fffff
	Prefetchable memory behind bridge: 00000000fff00000-00000000000fffff
	Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
	Capabilities: <access denied>

00:1f.0 ISA bridge: Intel Corporation Unknown device 3a14 (rev 02)
	Subsystem: Intel Corporation Unknown device 1003
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Capabilities: <access denied>

00:1f.2 SATA controller: Intel Corporation Unknown device 3a02 (rev 02) (prog-if 01 [AHCI 1.0])
	Subsystem: Intel Corporation Unknown device 1003
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin B routed to IRQ 255
	Region 0: I/O ports at f1b0 [size=8]
	Region 1: I/O ports at f1a0 [size=4]
	Region 2: I/O ports at f190 [size=8]
	Region 3: I/O ports at f180 [size=4]
	Region 4: I/O ports at f020 [size=32]
	Region 5: Memory at d0626000 (32-bit, non-prefetchable) [size=2K]
	Capabilities: <access denied>

00:1f.3 SMBus: Intel Corporation Unknown device 3a60 (rev 02)
	Subsystem: Intel Corporation Unknown device 1003
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Interrupt: pin C routed to IRQ 10
	Region 0: Memory at d0627000 (64-bit, non-prefetchable) [size=256]
	Region 4: I/O ports at f000 [size=32]

00:1f.5 IDE interface: Intel Corporation Unknown device 3a06 (rev 02) (prog-if 85 [Master SecO PriO])
	Subsystem: Intel Corporation Unknown device 1003
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin B routed to IRQ 17
	Region 0: I/O ports at f170 [size=8]
	Region 1: I/O ports at f160 [size=4]
	Region 2: I/O ports at f150 [size=8]
	Region 3: I/O ports at f140 [size=4]
	Region 4: I/O ports at f130 [size=16]
	Region 5: I/O ports at f120 [size=16]
	Capabilities: <access denied>

01:01.0 FireWire (IEEE 1394): Agere Systems FW323 (rev 70) (prog-if 10 [OHCI])
	Subsystem: Intel Corporation Unknown device 1003
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 32 (3000ns min, 6000ns max), Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 10
	Region 0: Memory at d0500000 (32-bit, non-prefetchable) [size=4K]
	Region 1: Memory at d0501000 (32-bit, non-prefetchable) [size=256]
	Capabilities: <access denied>

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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

RE: Option iommu=1 causes hypervisor to start debugger

[Zhao, Yu]

[-- Attachment #1: Type: text/plain, Size: 1910 bytes --]

Can you please apply the attached patch and grab the log again?

Thanks,
Yu

>-----Original Message-----
>From: Alexia Benington [mailto:alexbenington@gmail.com]
>Sent: Wednesday, February 04, 2009 10:27 AM
>To: Zhao, Yu
>Cc: Keir Fraser; xen-devel@lists.xensource.com
>Subject: Re: [Xen-devel] Option iommu=1 causes hypervisor to start debugger
>
>I was referring to the fix titled "ioemu: fix PCI ROM handling problem
>in passthrough". Seriously, I don't even know if the problem is
>related. Just trying something because I'm totally clueless now.
>
>I've attached the lspci. Let me know if you need more info. Will be
>glad to provide.
>
>Thanks guys.
>
>- Alex
>
>On Tue, Feb 3, 2009 at 8:55 PM, Zhao, Yu <yu.zhao@intel.com> wrote:
>> Which patch are you talking about? Since we can't get any clue from your
>> log, can you please send us the output of `lspci -vvv'?
>>
>> Thanks,
>> Yu
>>
>> Alexia Benington wrote:
>>>
>>> Thanks Keir. Perhaps I should try with Yu Zhao's patch and see if that
>>> fixes the problem.
>>>
>>> -Alex
>>>
>>> On Tue, Feb 3, 2009 at 3:06 AM, Keir Fraser <keir.fraser@eu.citrix.com>
>>> wrote:
>>>>
>>>> It's needed for passing through physical devices to HVM guests.
>>>>
>>>>  -- Keir
>>>>
>>>> On 02/02/2009 23:42, "Alexia Benington" <alexbenington@gmail.com> wrote:
>>>>
>>>>> If I do not include the iommu option, I/O virtualisation is disabled.
>>>>> I never thought that iommu is a necessary prerequisite for I/O virt,
>>>>> or am I mistaken?
>>>>>
>>>>> -Alex
>>>>>
>>>>> _______________________________________________
>>>>> Xen-devel mailing list
>>>>> Xen-devel@lists.xensource.com
>>>>> http://lists.xensource.com/xen-devel
>>>>
>>>>
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xensource.com
>>> http://lists.xensource.com/xen-devel
>>
>>

[-- Attachment #2: debug.diff --]
[-- Type: application/octet-stream, Size: 2669 bytes --]

diff -r e265055ce11c xen/drivers/passthrough/vtd/iommu.c
--- a/xen/drivers/passthrough/vtd/iommu.c       Thu Jan 22 14:05:23 2009 -0500
+++ b/xen/drivers/passthrough/vtd/iommu.c       Wed Feb 04 05:47:08 2009 -0500
@@ -1039,6 +1039,7 @@

     ASSERT(spin_is_locked(&pcidevs_lock));
     spin_lock(&iommu->lock);
+    gdprintk(XENLOG_INFO VTDPREFIX, "domain_context_mapping_one: 1\n");
     maddr = bus_to_context_maddr(iommu, bus);
     context_entries = (struct context_entry *)map_vtd_domain_page(maddr);
     context = &context_entries[devfn];
@@ -1054,6 +1055,7 @@
             res = -EINVAL;
         unmap_vtd_domain_page(context_entries);
         spin_unlock(&iommu->lock);
+        gdprintk(XENLOG_INFO VTDPREFIX, "domain_context_mapping_one: 2\n");
         return res;
     }

@@ -1066,6 +1068,7 @@
     else
     {
         spin_lock(&hd->mapping_lock);
+        gdprintk(XENLOG_INFO VTDPREFIX, "domain_context_mapping_one: 3\n");

         /* Ensure we have pagetables allocated down to leaf PTE. */
         if ( hd->pgd_maddr == 0 )
@@ -1077,6 +1080,7 @@
                 spin_unlock(&hd->mapping_lock);
                 spin_unlock(&iommu->lock);
                 unmap_vtd_domain_page(context_entries);
+                gdprintk(XENLOG_INFO VTDPREFIX, "domain_context_mapping_one: 4\n");
                 return -ENOMEM;
             }
         }
@@ -1120,6 +1124,7 @@
     set_bit(iommu->index, &hd->iommu_bitmap);

     unmap_vtd_domain_page(context_entries);
+    gdprintk(XENLOG_INFO VTDPREFIX, "domain_context_mapping_one: 5\n");

     return 0;
 }
@@ -1268,12 +1273,16 @@
             secdevfn = devfn;
             devfn = bus2bridge[bus].devfn;
             bus = bus2bridge[bus].bus;
+            gdprintk(XENLOG_INFO VTDPREFIX,
+                     "domain_context_mapping:bus2bridge: bdf = %x:%x.%x\n",
+                      bus, PCI_SLOT(devfn), PCI_FUNC(devfn));
             ret = domain_context_mapping_one(domain, drhd->iommu, bus, devfn);
             if ( ret )
                 return ret;
         }

         if ( (secbus != bus) && (secdevfn != 0) )
+        {
             /*
              * The source-id for transactions on non-PCIe buses seem
              * to originate from devfn=0 on the secondary bus behind
@@ -1281,7 +1290,11 @@
              * these scanarios is not particularly well documented
              * anywhere.
              */
+            gdprintk(XENLOG_INFO VTDPREFIX,
+                     "domain_context_mapping:secbus: bdf = %x:%x.%x\n",
+                      secbus, 0, 0);
             ret = domain_context_mapping_one(domain, drhd->iommu, secbus, 0);
+        }
         break;

     default:

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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

Re: Option iommu=1 causes hypervisor to start debugger

[Alexia Benington]

[-- Attachment #1: Type: text/plain, Size: 2011 bytes --]

Here it is. Thanks.

-Alex

On Tue, Feb 3, 2009 at 9:52 PM, Zhao, Yu <yu.zhao@intel.com> wrote:
> Can you please apply the attached patch and grab the log again?
>
> Thanks,
> Yu
>
>>-----Original Message-----
>>From: Alexia Benington [mailto:alexbenington@gmail.com]
>>Sent: Wednesday, February 04, 2009 10:27 AM
>>To: Zhao, Yu
>>Cc: Keir Fraser; xen-devel@lists.xensource.com
>>Subject: Re: [Xen-devel] Option iommu=1 causes hypervisor to start debugger
>>
>>I was referring to the fix titled "ioemu: fix PCI ROM handling problem
>>in passthrough". Seriously, I don't even know if the problem is
>>related. Just trying something because I'm totally clueless now.
>>
>>I've attached the lspci. Let me know if you need more info. Will be
>>glad to provide.
>>
>>Thanks guys.
>>
>>- Alex
>>
>>On Tue, Feb 3, 2009 at 8:55 PM, Zhao, Yu <yu.zhao@intel.com> wrote:
>>> Which patch are you talking about? Since we can't get any clue from your
>>> log, can you please send us the output of `lspci -vvv'?
>>>
>>> Thanks,
>>> Yu
>>>
>>> Alexia Benington wrote:
>>>>
>>>> Thanks Keir. Perhaps I should try with Yu Zhao's patch and see if that
>>>> fixes the problem.
>>>>
>>>> -Alex
>>>>
>>>> On Tue, Feb 3, 2009 at 3:06 AM, Keir Fraser <keir.fraser@eu.citrix.com>
>>>> wrote:
>>>>>
>>>>> It's needed for passing through physical devices to HVM guests.
>>>>>
>>>>>  -- Keir
>>>>>
>>>>> On 02/02/2009 23:42, "Alexia Benington" <alexbenington@gmail.com> wrote:
>>>>>
>>>>>> If I do not include the iommu option, I/O virtualisation is disabled.
>>>>>> I never thought that iommu is a necessary prerequisite for I/O virt,
>>>>>> or am I mistaken?
>>>>>>
>>>>>> -Alex
>>>>>>
>>>>>> _______________________________________________
>>>>>> Xen-devel mailing list
>>>>>> Xen-devel@lists.xensource.com
>>>>>> http://lists.xensource.com/xen-devel
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> Xen-devel mailing list
>>>> Xen-devel@lists.xensource.com
>>>> http://lists.xensource.com/xen-devel
>>>
>>>
>

[-- Attachment #2: log.090204 --]
[-- Type: application/octet-stream, Size: 14632 bytes --]

 __  __            _____ _  _                      _        _     _      
 \ \/ /___ _ __   |___ /| || |     _   _ _ __  ___| |_ __ _| |__ | | ___ 
  \  // _ \ '_ \    |_ \| || |_ __| | | | '_ \/ __| __/ _` | '_ \| |/ _ \
  /  \  __/ | | |  ___) |__   _|__| |_| | | | \__ \ || (_| | |_) | |  __/
 /_/\_\___|_| |_| |____(_) |_|     \__,_|_| |_|___/\__\__,_|_.__/|_|\___|
                                                                         
(XEN) Xen version 3.4-unstable (xxx@xxx.xxx.xxx) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) Wed Feb  4 04:45:29 EST 2009
(XEN) Latest ChangeSet: Fri Jan 30 11:12:57 2009 +0900 19130:c8962b24fb50
(XEN) Command line: loglvl=all guest_loglvl=all com1=115200,8n1 console=com1 iommu=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 0 MBR signatures
(XEN)  Found 1 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009e800 (usable)
(XEN)  000000000009e800 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000bd6cb000 (usable)
(XEN)  00000000bd6cb000 - 00000000bd70d000 (ACPI NVS)
(XEN)  00000000bd70d000 - 00000000bd82b000 (reserved)
(XEN)  00000000bd82b000 - 00000000bd83f000 (ACPI NVS)
(XEN)  00000000bd83f000 - 00000000bd940000 (reserved)
(XEN)  00000000bd940000 - 00000000bd941000 (ACPI NVS)
(XEN)  00000000bd941000 - 00000000bd946000 (reserved)
(XEN)  00000000bd946000 - 00000000bd94e000 (ACPI data)
(XEN)  00000000bd94e000 - 00000000bd969000 (ACPI NVS)
(XEN)  00000000bd969000 - 00000000bd988000 (reserved)
(XEN)  00000000bd988000 - 00000000bd98e000 (ACPI NVS)
(XEN)  00000000bd98e000 - 00000000bdb00000 (usable)
(XEN)  00000000bdc00000 - 00000000c0000000 (reserved)
(XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
(XEN)  00000000ff000000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 000000013c000000 (usable)
(XEN) System RAM: 3991MB (4087660kB)
(XEN) ACPI: RSDP 000F03C0, 0024 (r2  INTEL)
(XEN) ACPI: XSDT BD94CE18, 005C (r1 INTEL  DQ45CB         49 MSFT    10013)
(XEN) ACPI: FACP BD94BD98, 00F4 (r4  INTEL    A M I  6222004 MSFT    10013)
(XEN) ACPI: DSDT BD946018, 4EE8 (r1 INTEL  DQ45CB         49 INTL 20051117)
(XEN) ACPI: FACS BD954F40, 0040
(XEN) ACPI: APIC BD94BF18, 006C (r2 INTEL  DQ45CB         49 MSFT    10013)
(XEN) ACPI: MCFG BD956E18, 003C (r1 INTEL  DQ45CB         49 MSFT       97)
(XEN) ACPI: ASF! BD955D18, 00A0 (r32 INTEL  DQ45CB         49 TFSM    F4240)
(XEN) ACPI: SPCR BD956D18, 0050 (r1 INTEL  DQ45CB         49 AMI.        3)
(XEN) ACPI: TCPA BD956C98, 0032 (r2 INTEL  DQ45CB         49 MSFT  1000013)
(XEN) ACPI: DMAR BD940C18, 0120 (r1 INTEL  DQ45CB         49 INTL        1)
(XEN) NUMA turned off
(XEN) Faking a node at 0000000000000000-000000013c000000
(XEN) Domain heap initialised
(XEN) DMI 2.4 present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x408
(XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[404,0], pm1x_evt[400,0]
(XEN) ACPI:                  wakeup_vec[bd954f4c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
(XEN) Processor #2 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
(XEN) Processor #3 7:7 APIC version 20
(XEN) ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) [VT-D]dmar.c:459: Host address width 36
(XEN) [VT-D]dmar.c:468: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:336: dmaru->address = fed90000
(XEN) [VT-D]dmar.c:287: found endpoint: bdf = 0:1b.0
(XEN) [VT-D]dmar.c:468: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:336: dmaru->address = fed91000
(XEN) [VT-D]dmar.c:287: found endpoint: bdf = 0:2.0
(XEN) [VT-D]dmar.c:287: found endpoint: bdf = 0:2.1
(XEN) [VT-D]dmar.c:468: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:336: dmaru->address = fed92000
(XEN) [VT-D]dmar.c:287: found endpoint: bdf = 0:3.0
(XEN) [VT-D]dmar.c:287: found endpoint: bdf = 0:3.2
(XEN) [VT-D]dmar.c:287: found endpoint: bdf = 0:3.3
(XEN) [VT-D]dmar.c:468: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:336: dmaru->address = fed93000
(XEN) [VT-D]dmar.c:345: found INCLUDE_ALL
(XEN) [VT-D]dmar.c:472: found ACPI_DMAR_RMRR
(XEN) [VT-D]dmar.c:287: found endpoint: bdf = 0:1d.0
(XEN) [VT-D]dmar.c:287: found endpoint: bdf = 0:1d.1
(XEN) [VT-D]dmar.c:287: found endpoint: bdf = 0:1d.2
(XEN) [VT-D]dmar.c:287: found endpoint: bdf = 0:1d.7
(XEN) [VT-D]dmar.c:287: found endpoint: bdf = 0:1a.0
(XEN) [VT-D]dmar.c:287: found endpoint: bdf = 0:1a.1
(XEN) [VT-D]dmar.c:287: found endpoint: bdf = 0:1a.2
(XEN) [VT-D]dmar.c:287: found endpoint: bdf = 0:1a.7
(XEN) [VT-D]dmar.c:472: found ACPI_DMAR_RMRR
(XEN) [VT-D]dmar.c:287: found endpoint: bdf = 0:2.0
(XEN) [VT-D]dmar.c:287: found endpoint: bdf = 0:2.1
(XEN) Intel VT-d has been enabled, snoop_control=1.
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Initializing CPU#0
(XEN) Detected 2499.760 MHz processor.
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 3072K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 0
(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) MCE: Intel newly family MC Init
(XEN) Intel machine check reporting enabled on CPU#0.
(XEN) CPU0: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU0 has no CMCI support
(XEN) CPU0: Intel(R) Core(TM)2 Quad  CPU   Q9300  @ 2.50GHz stepping 07
(XEN) Booting processor 1/1 eip 8c000
(XEN) Initializing CPU#1
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 3072K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 1
(XEN) MCE: Intel newly family MC Init
(XEN) Intel machine check reporting enabled on CPU#1.
(XEN) CPU1: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU1 has no CMCI support
(XEN) CPU1: Intel(R) Core(TM)2 Quad  CPU   Q9300  @ 2.50GHz stepping 07
(XEN) Booting processor 2/2 eip 8c000
(XEN) Initializing CPU#2
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 3072K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 2
(XEN) MCE: Intel newly family MC Init
(XEN) Intel machine check reporting enabled on CPU#2.
(XEN) CPU2: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU2 has no CMCI support
(XEN) CPU2: Intel(R) Core(TM)2 Quad  CPU   Q9300  @ 2.50GHz stepping 07
(XEN) Booting processor 3/3 eip 8c000
(XEN) Initializing CPU#3
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 3072K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 3
(XEN) MCE: Intel newly family MC Init
(XEN) Intel machine check reporting enabled on CPU#3.
(XEN) CPU3: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU3 has no CMCI support
(XEN) CPU3: Intel(R) Core(TM)2 Quad  CPU   Q9300  @ 2.50GHz stepping 07
(XEN) Total of 4 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) checking TSC synchronization across 4 CPUs: passed.
(XEN) Platform timer is 3.579MHz ACPI PM Timer
(XEN) microcode.c:73:d32767 microcode: CPU1 resumed
(XEN) microcode.c:73:d32767 microcode: CPU2 resumed
(XEN) Brought up 4 CPUs
(XEN) microcode.c:73:d32767 microcode: CPU3 resumed
(XEN) [VT-D]iommu.c:1710: Queued Invalidation hardware not found
(XEN) [VT-D]iommu.c:1710: Queued Invalidation hardware not found
(XEN) [VT-D]iommu.c:1710: Queued Invalidation hardware not found
(XEN) [VT-D]iommu.c:1710: Queued Invalidation hardware not found
(XEN) [VT-D]iommu.c:1718: Interrupt Remapping hardware not found
(XEN) [VT-D]iommu.c:1718: Interrupt Remapping hardware not found
(XEN) [VT-D]iommu.c:1718: Interrupt Remapping hardware not found
(XEN) [VT-D]iommu.c:1718: Interrupt Remapping hardware not found
(XEN) I/O virtualisation enabled
(XEN) I/O virtualisation for PV guests disabled
(XEN) ACPI sleep modes: S3
(XEN) mcheck_poll: Init_mcheck_timer
(XEN) mcheck_poll: Machine check polling timer started.
(XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 0:0.0
(XEN) [VT-D]iommu.c:1038:d32767 domain_context_mapping_one: 1
(XEN) [VT-D]iommu.c:1067:d32767 domain_context_mapping_one: 3
(XEN) [VT-D]iommu.c:1123:d32767 domain_context_mapping_one: 5
(XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 0:2.0
(XEN) [VT-D]iommu.c:1038:d32767 domain_context_mapping_one: 1
(XEN) [VT-D]iommu.c:1067:d32767 domain_context_mapping_one: 3
(XEN) [VT-D]iommu.c:1123:d32767 domain_context_mapping_one: 5
(XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 0:2.1
(XEN) [VT-D]iommu.c:1038:d32767 domain_context_mapping_one: 1
(XEN) [VT-D]iommu.c:1067:d32767 domain_context_mapping_one: 3
(XEN) [VT-D]iommu.c:1123:d32767 domain_context_mapping_one: 5
(XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 0:3.0
(XEN) [VT-D]iommu.c:1038:d32767 domain_context_mapping_one: 1
(XEN) [VT-D]iommu.c:1067:d32767 domain_context_mapping_one: 3
(XEN) [VT-D]iommu.c:1123:d32767 domain_context_mapping_one: 5
(XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 0:3.2
(XEN) [VT-D]iommu.c:1038:d32767 domain_context_mapping_one: 1
(XEN) [VT-D]iommu.c:1067:d32767 domain_context_mapping_one: 3
(XEN) [VT-D]iommu.c:1123:d32767 domain_context_mapping_one: 5
(XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 0:3.3
(XEN) [VT-D]iommu.c:1038:d32767 domain_context_mapping_one: 1
(XEN) [VT-D]iommu.c:1067:d32767 domain_context_mapping_one: 3
(XEN) [VT-D]iommu.c:1123:d32767 domain_context_mapping_one: 5
(XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 0:19.0
(XEN) [VT-D]iommu.c:1038:d32767 domain_context_mapping_one: 1
(XEN) [VT-D]iommu.c:1067:d32767 domain_context_mapping_one: 3
(XEN) [VT-D]iommu.c:1123:d32767 domain_context_mapping_one: 5
(XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 0:1a.0
(XEN) [VT-D]iommu.c:1038:d32767 domain_context_mapping_one: 1
(XEN) [VT-D]iommu.c:1067:d32767 domain_context_mapping_one: 3
(XEN) [VT-D]iommu.c:1123:d32767 domain_context_mapping_one: 5
(XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 0:1a.1
(XEN) [VT-D]iommu.c:1038:d32767 domain_context_mapping_one: 1
(XEN) [VT-D]iommu.c:1067:d32767 domain_context_mapping_one: 3
(XEN) [VT-D]iommu.c:1123:d32767 domain_context_mapping_one: 5
(XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 0:1a.2
(XEN) [VT-D]iommu.c:1038:d32767 domain_context_mapping_one: 1
(XEN) [VT-D]iommu.c:1067:d32767 domain_context_mapping_one: 3
(XEN) [VT-D]iommu.c:1123:d32767 domain_context_mapping_one: 5
(XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 0:1a.7
(XEN) [VT-D]iommu.c:1038:d32767 domain_context_mapping_one: 1
(XEN) [VT-D]iommu.c:1067:d32767 domain_context_mapping_one: 3
(XEN) [VT-D]iommu.c:1123:d32767 domain_context_mapping_one: 5
(XEN) [VT-D]iommu.c:1246:d32767 domain_context_mapping:PCIe: bdf = 0:1b.0
(XEN) [VT-D]iommu.c:1038:d32767 domain_context_mapping_one: 1
(XEN) [VT-D]iommu.c:1067:d32767 domain_context_mapping_one: 3
(XEN) [VT-D]iommu.c:1123:d32767 domain_context_mapping_one: 5
(XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 0:1d.0
(XEN) [VT-D]iommu.c:1038:d32767 domain_context_mapping_one: 1
(XEN) [VT-D]iommu.c:1067:d32767 domain_context_mapping_one: 3
(XEN) [VT-D]iommu.c:1123:d32767 domain_context_mapping_one: 5
(XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 0:1d.1
(XEN) [VT-D]iommu.c:1038:d32767 domain_context_mapping_one: 1
(XEN) [VT-D]iommu.c:1067:d32767 domain_context_mapping_one: 3
(XEN) [VT-D]iommu.c:1123:d32767 domain_context_mapping_one: 5
(XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 0:1d.2
(XEN) [VT-D]iommu.c:1038:d32767 domain_context_mapping_one: 1
(XEN) [VT-D]iommu.c:1067:d32767 domain_context_mapping_one: 3
(XEN) [VT-D]iommu.c:1123:d32767 domain_context_mapping_one: 5
(XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 0:1d.7
(XEN) [VT-D]iommu.c:1038:d32767 domain_context_mapping_one: 1
(XEN) [VT-D]iommu.c:1067:d32767 domain_context_mapping_one: 3
(XEN) [VT-D]iommu.c:1123:d32767 domain_context_mapping_one: 5
(XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 0:1f.0
(XEN) [VT-D]iommu.c:1038:d32767 domain_context_mapping_one: 1
(XEN) [VT-D]iommu.c:1067:d32767 domain_context_mapping_one: 3
(XEN) [VT-D]iommu.c:1123:d32767 domain_context_mapping_one: 5
(XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 0:1f.2
(XEN) [VT-D]iommu.c:1038:d32767 domain_context_mapping_one: 1
(XEN) [VT-D]iommu.c:1067:d32767 domain_context_mapping_one: 3
(XEN) [VT-D]iommu.c:1123:d32767 domain_context_mapping_one: 5
(XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 0:1f.3
(XEN) [VT-D]iommu.c:1038:d32767 domain_context_mapping_one: 1
(XEN) [VT-D]iommu.c:1067:d32767 domain_context_mapping_one: 3
(XEN) [VT-D]iommu.c:1123:d32767 domain_context_mapping_one: 5
(XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 0:1f.5
(XEN) [VT-D]iommu.c:1038:d32767 domain_context_mapping_one: 1
(XEN) [VT-D]iommu.c:1067:d32767 domain_context_mapping_one: 3
(XEN) [VT-D]iommu.c:1123:d32767 domain_context_mapping_one: 5
(XEN) [VT-D]iommu.c:1253:d32767 domain_context_mapping:PCI: bdf = 1:1.0
(XEN) [VT-D]iommu.c:1038:d32767 domain_context_mapping_one: 1
(XEN) [VT-D]iommu.c:1067:d32767 domain_context_mapping_one: 3
(XEN) [VT-D]iommu.c:1123:d32767 domain_context_mapping_one: 5
(XEN) [VT-D]iommu.c:1270:d32767 domain_context_mapping:bus2bridge: bdf = 0:1e.0
(XEN) [VT-D]iommu.c:1038:d32767 domain_context_mapping_one: 1
(XEN) [VT-D]iommu.c:1067:d32767 domain_context_mapping_one: 3
(XEN) [VT-D]iommu.c:1123:d32767 domain_context_mapping_one: 5
(XEN) [VT-D]iommu.c:1287:d32767 domain_context_mapping:secbus: bdf = 1:0.0
(XEN) [VT-D]iommu.c:1038:d32767 domain_context_mapping_one: 1
(XEN) [VT-D]iommu.c:1067:d32767 domain_context_mapping_one: 3
(XEN) [VT-D]iommu.c:1123:d32767 domain_context_mapping_one: 5

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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