* Re: [Xen-users] xen/stable-2.6.32.x compilation failure in do_hvm_suspend() [not found] ` <AANLkTimKlhHnJ70MSbtniRbj6EirU-0BnT259Smgv_rb@mail.gmail.com> @ 2010-05-13 18:10 ` Pasi Kärkkäinen 2010-05-13 18:22 ` Dan Magenheimer 2010-05-13 18:32 ` M A Young 2010-05-13 18:28 ` [Xen-users] RE: Xen4 / Intel DX58SO Mobo / VT-d not working chris 1 sibling, 2 replies; 32+ messages in thread From: Pasi Kärkkäinen @ 2010-05-13 18:10 UTC (permalink / raw) To: chris; +Cc: xen-devel, Xen-Users List On Thu, May 13, 2010 at 02:07:47PM -0400, chris wrote: > I redid it with oldconfig which I didn't think would help and same > thing. I guess this tree is broken? Can someone else try and see if > they can build it? Ugh, whata day :) > I guess the tree is broken because of the recently added pv-on-hvm driver support.. Is there a known workaround for this? -- Pasi > On Thu, May 13, 2010 at 1:58 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > > On Thu, May 13, 2010 at 01:55:25PM -0400, chris wrote: > >> I used the default config on the wiki which you created. Steps I took were: > >> > >> # make clean distclean > >> # wget -O .config > >> "http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.10-pvops-dom0-xen-stable-x86_64" > > > > You should do "make oldconfig" at this point. > > > >> # make -j8 bzImage > >> (blah blah) > >> LD vmlinux.o > >> MODPOST vmlinux.o > >> WARNING: modpost: Found 7 section mismatch(es). > >> To see full details build your kernel with: > >> 'make CONFIG_DEBUG_SECTION_MISMATCH=y' > >> GEN .version > >> CHK include/linux/compile.h > >> UPD include/linux/compile.h > >> CC init/version.o > >> LD init/built-in.o > >> LD .tmp_vmlinux1 > >> drivers/built-in.o: In function `do_hvm_suspend': > >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: undefined reference > >> to `xenbus_suspend' > >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: undefined reference > >> to `xenbus_resume' > >> make: *** [.tmp_vmlinux1] Error 1 > >> > > > > Hmm.. weird. I wonder if something has changed recently or what's going on in here.. > > > > -- Pasi > > > >> > >> On Thu, May 13, 2010 at 11:47 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > >> > On Thu, May 13, 2010 at 11:33:57AM -0400, chris wrote: > >> >> Successfully grabbed the sources and failed to build: > >> >> > >> >> LD .tmp_vmlinux1 > >> >> drivers/built-in.o: In function `do_hvm_suspend': > >> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: undefined reference > >> >> to `xenbus_suspend' > >> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: undefined reference > >> >> to `xenbus_resume' > >> >> make: *** [.tmp_vmlinux1] Error 1 > >> >> > >> >> :( > >> >> > >> > > >> > Try the example .config files provided on the wiki page. > >> > > >> > -- Pasi > >> > > >> >> On Thu, May 13, 2010 at 10:14 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > >> >> > On Thu, May 13, 2010 at 10:12:56AM -0400, chris wrote: > >> >> >> Pasi, > >> >> >> > >> >> >> How do I pull those kernel sources you referenced? I see it mentioned > >> >> >> on http://wiki.xensource.com/xenwiki/XenParavirtOps but no details on > >> >> >> how to retrieve it. > >> >> >> > >> >> > > >> >> > The instructions are there if you read it carefully.. > >> >> > There's the topic of how to switch branches. > >> >> > > >> >> > -- Pasi > >> >> > > >> >> >> - chris > >> >> >> > >> >> >> On Thu, May 13, 2010 at 8:29 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > >> >> >> > On Wed, May 12, 2010 at 08:41:34PM -0400, chris wrote: > >> >> >> >> When reading the vtdhowto I noticed the ability to set iommu=verbose. > >> >> >> >> Here is that output, I don't know if it helps at all to figure out > >> >> >> >> what is wrong. > >> >> >> >> > >> >> >> > > >> >> >> > That seems to be OK: > >> >> >> > > >> >> >> > (XEN) I/O virtualisation enabled > >> >> >> > (XEN) I/O virtualisation for PV guests disabled > >> >> >> > > >> >> >> > So hmm.. I wonder if it's related to MSI stuff? > >> >> >> > You could try xen.git xen/stable-2.6.32.x branch instead and see if that makes a difference.. > >> >> >> > > >> >> >> > -- Pasi > >> >> >> > > >> >> >> >> > >> >> >> >> ---------- Forwarded message ---------- > >> >> >> >> From: chris <tknchris@gmail.com> > >> >> >> >> Date: Wed, May 12, 2010 at 5:28 PM > >> >> >> >> Subject: Xen4 / Intel DX58SO Mobo / VT-d not working > >> >> >> >> To: Xen-Users List <xen-users@lists.xensource.com> > >> >> >> >> > >> >> >> >> > >> >> >> >> Hello, > >> >> >> >> > >> >> >> >> I've previously been successful with Xen4 and VT-d on other systems. I > >> >> >> >> am having trouble getting VT-d passthrough working to a WinXP domain > >> >> >> >> with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is enabled in bios, > >> >> >> >> xm info shows hvm_directio capability, I have iommu=1 set, I have the > >> >> >> >> devices bound to pciback on dom0 cmdline, xm > >> >> >> >> pci-list-assignable-devices shows the devices as assignable. When I > >> >> >> >> attempt to start the VM I get the error: > >> >> >> >> > >> >> >> >> Error: Failed to assign device to IOMMU > >> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) > >> >> >> >> > >> >> >> >> Below is all the information I can think of that would be useful to > >> >> >> >> help debug it: > >> >> >> >> > >> >> >> >> BIOS VT-d Enabled: > >> >> >> >> http://i43.tinypic.com/nl3a5e.jpg > >> >> >> >> http://i42.tinypic.com/nqvlu1.jpg > >> >> >> >> > >> >> >> >> grub entry: > >> >> >> >> > >> >> >> >> title Xen 4.0.0 / Debian GNU/Linux, kernel 2.6.31.13 > >> >> >> >> root (hd0,0) > >> >> >> >> kernel /boot/xen-4.0.0.gz iommu=1 dom0_mem=256M > >> >> >> >> dom0_max_vcpus=1 dom0_vcpus_pin=true > >> >> >> >> module /boot/vmlinuz-2.6.31.13 root=/dev/md0 ro console=tty0 > >> >> >> >> xen-pciback.permissive > >> >> >> >> xen-pciback.hide=(02:00.0)(02:00.1)(02:00.2)(04:00.0)(04:00.1)(04:00.2)(07:00.0)(07:00.1)(07:00.2)(09:00.0)(09:00.1)(09:00.2) > >> >> >> >> module /boot/initrd.img-2.6.31.13 > >> >> >> >> > >> >> >> >> # xm pci-list-assignable-devices > >> >> >> >> 0000:09:00.0 > >> >> >> >> 0000:09:00.1 > >> >> >> >> 0000:09:00.2 > >> >> >> >> 0000:07:00.0 > >> >> >> >> 0000:07:00.1 > >> >> >> >> 0000:07:00.2 > >> >> >> >> 0000:04:00.0 > >> >> >> >> 0000:04:00.1 > >> >> >> >> 0000:04:00.2 > >> >> >> >> 0000:02:00.0 > >> >> >> >> 0000:02:00.1 > >> >> >> >> 0000:02:00.2 > >> >> >> >> > >> >> >> >> # xm info > >> >> >> >> host : test-box2 > >> >> >> >> release : 2.6.31.13 > >> >> >> >> version : #2 SMP Wed May 12 14:11:37 EDT 2010 > >> >> >> >> machine : x86_64 > >> >> >> >> nr_cpus : 8 > >> >> >> >> nr_nodes : 1 > >> >> >> >> cores_per_socket : 4 > >> >> >> >> threads_per_core : 2 > >> >> >> >> cpu_mhz : 2800 > >> >> >> >> hw_caps : > >> >> >> >> bfebfbff:28100800:00000000:00001b40:0098e3bd:00000000:00000001:00000000 > >> >> >> >> virt_caps : hvm hvm_directio > >> >> >> >> total_memory : 7950 > >> >> >> >> free_memory : 7812 > >> >> >> >> node_to_cpu : node0:0-7 > >> >> >> >> node_to_memory : node0:7812 > >> >> >> >> node_to_dma32_mem : node0:3249 > >> >> >> >> max_node_id : 0 > >> >> >> >> xen_major : 4 > >> >> >> >> xen_minor : 0 > >> >> >> >> xen_extra : .0 > >> >> >> >> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > >> >> >> >> hvm-3.0-x86_32p hvm-3.0-x86_64 > >> >> >> >> xen_scheduler : credit > >> >> >> >> xen_pagesize : 4096 > >> >> >> >> platform_params : virt_start=0xffff800000000000 > >> >> >> >> xen_changeset : unavailable > >> >> >> >> xen_commandline : iommu=1 dom0_mem=256M dom0_max_vcpus=1 > >> >> >> >> dom0_vcpus_pin=true > >> >> >> >> cc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1) > >> >> >> >> cc_compile_by : root > >> >> >> >> cc_compile_domain : > >> >> >> >> cc_compile_date : Thu May 6 13:41:25 EDT 2010 > >> >> >> >> xend_config_format : 4 > >> >> >> >> > >> >> >> >> # xm create vm-five.cfg > >> >> >> >> Using config file "./vm-five.cfg". > >> >> >> >> Error: Failed to assign device to IOMMU > >> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) > >> >> >> >> > >> >> >> >> I feel like I'm missing something really obvious but I've been at it > >> >> >> >> for a while now and have run out of brain power. Anyone have any idea > >> >> >> >> what might be wrong? > >> >> >> >> > >> >> >> >> - chris > >> >> >> > > >> >> >> >> __ __ _ _ ___ ___ > >> >> >> >> \ \/ /___ _ __ | || | / _ \ / _ \ > >> >> >> >> \ // _ \ \047_ \ | || |_| | | | | | | > >> >> >> >> / \ __/ | | | |__ _| |_| | |_| | > >> >> >> >> /_/\_\___|_| |_| |_|(_)___(_)___/ > >> >> >> >> > >> >> >> >> (XEN) Xen version 4.0.0 (root@) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) Thu May 6 13:41:25 EDT 2010 > >> >> >> >> (XEN) Latest ChangeSet: unavailable > >> >> >> >> (XEN) Command line: iommu=verbose dom0_mem=256M dom0_max_vcpus=1 dom0_vcpus_pin=true > >> >> >> >> (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 - 000000000008f000 (usable) > >> >> >> >> (XEN) 000000000008f000 - 0000000000090000 (reserved) > >> >> >> >> (XEN) 0000000000090000 - 000000000009ec00 (usable) > >> >> >> >> (XEN) 000000000009ec00 - 00000000000a0000 (reserved) > >> >> >> >> (XEN) 00000000000e0000 - 0000000000100000 (reserved) > >> >> >> >> (XEN) 0000000000100000 - 00000000cf4bd000 (usable) > >> >> >> >> (XEN) 00000000cf4bd000 - 00000000cf4bf000 (reserved) > >> >> >> >> (XEN) 00000000cf4bf000 - 00000000cf4c2000 (usable) > >> >> >> >> (XEN) 00000000cf4c2000 - 00000000cf7bf000 (ACPI NVS) > >> >> >> >> (XEN) 00000000cf7bf000 - 00000000cf7df000 (usable) > >> >> >> >> (XEN) 00000000cf7df000 - 00000000cf7ff000 (ACPI data) > >> >> >> >> (XEN) 00000000cf7ff000 - 00000000cf800000 (usable) > >> >> >> >> (XEN) 00000000cf800000 - 00000000d0000000 (reserved) > >> >> >> >> (XEN) 00000000f8000000 - 00000000fd000000 (reserved) > >> >> >> >> (XEN) 00000000ffe00000 - 0000000100000000 (reserved) > >> >> >> >> (XEN) 0000000100000000 - 0000000230000000 (usable) > >> >> >> >> (XEN) ACPI: RSDP 000FE020, 0024 (r2 INTEL ) > >> >> >> >> (XEN) ACPI: XSDT CF7FE120, 0074 (r1 INTEL DX58SO 11F6 1000013) > >> >> >> >> (XEN) ACPI: FACP CF7FD000, 00F4 (r3 INTEL DX58SO 11F6 MSFT 100000D) > >> >> >> >> (XEN) ACPI Warning (tbfadt-0444): Optional field "Pm2ControlBlock" has zero address or length: 0000000000000450/0 [20070126] > >> >> >> >> (XEN) ACPI: DSDT CF7F8000, 4641 (r2 INTEL DX58SO 11F6 MSFT 100000D) > >> >> >> >> (XEN) ACPI: FACS CF728000, 0040 > >> >> >> >> (XEN) ACPI: APIC CF7F7000, 0138 (r2 INTEL DX58SO 11F6 MSFT 100000D) > >> >> >> >> (XEN) ACPI: WDDT CF7F6000, 0040 (r1 INTEL DX58SO 11F6 MSFT 100000D) > >> >> >> >> (XEN) ACPI: MCFG CF7F5000, 003C (r1 INTEL DX58SO 11F6 MSFT 100000D) > >> >> >> >> (XEN) ACPI: ASF! CF7F4000, 00AC (r32 INTEL DX58SO 11F6 MSFT 100000D) > >> >> >> >> (XEN) ACPI: HPET CF7F3000, 0038 (r1 INTEL DX58SO 11F6 MSFT 100000D) > >> >> >> >> (XEN) ACPI: SSDT CF7E2000, E134 (r1 INTEL SSDT PM 11F6 MSFT 100000D) > >> >> >> >> (XEN) ACPI: DMAR CF7DF000, 0140 (r1 INTEL DX58SO 11F6 MSFT 100000D) > >> >> >> >> (XEN) ACPI: WDTT CF7F1000, 020C (r2 INTEL DX58SO 11F6 MSFT 100000D) > >> >> >> >> (XEN) ACPI: ASPT CF7F2000, 0034 (r4 INTEL PerfTune 11F6 MSFT 100000D) > >> >> >> >> (XEN) System RAM: 7950MB (8140820kB) > >> >> >> >> (XEN) Domain heap initialised > >> >> >> >> (XEN) Processor #0 7:10 APIC version 21 > >> >> >> >> (XEN) Processor #2 7:10 APIC version 21 > >> >> >> >> (XEN) Processor #4 7:10 APIC version 21 > >> >> >> >> (XEN) Processor #6 7:10 APIC version 21 > >> >> >> >> (XEN) Processor #1 7:10 APIC version 21 > >> >> >> >> (XEN) Processor #3 7:10 APIC version 21 > >> >> >> >> (XEN) Processor #5 7:10 APIC version 21 > >> >> >> >> (XEN) Processor #7 7:10 APIC version 21 > >> >> >> >> (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 > >> >> >> >> (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > >> >> >> >> (XEN) [VT-D]dmar.c:679: Host address width 39 > >> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: > >> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = fe711000 > >> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1b.0 > >> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: > >> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = fe710000 > >> >> >> >> (XEN) [VT-D]dmar.c:340: IOAPIC: f0:1f.7 > >> >> >> >> (XEN) [VT-D]dmar.c:411: flags: INCLUDE_ALL > >> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 > >> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e9000 end_address e9fff > >> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.1 > >> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ea000 end_address eafff > >> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.2 > >> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr eb000 end_address ebfff > >> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.0 > >> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e6000 end_address e6fff > >> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.1 > >> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e7000 end_address e7fff > >> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.2 > >> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e8000 end_address e8fff > >> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 > >> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ec000 end_address eefff > >> >> >> >> (XEN) Using scheduler: SMP Credit Scheduler (credit) > >> >> >> >> (XEN) Detected 2800.125 MHz processor. > >> >> >> >> (XEN) Initing memory sharing. > >> >> >> >> (XEN) VMX: Supported advanced features: > >> >> >> >> (XEN) - APIC MMIO access virtualisation > >> >> >> >> (XEN) - APIC TPR shadow > >> >> >> >> (XEN) - Extended Page Tables (EPT) > >> >> >> >> (XEN) - Virtual-Processor Identifiers (VPID) > >> >> >> >> (XEN) - Virtual NMI > >> >> >> >> (XEN) - MSR direct-access bitmap > >> >> >> >> (XEN) HVM: ASIDs enabled. > >> >> >> >> (XEN) HVM: VMX enabled > >> >> >> >> (XEN) HVM: Hardware Assisted Paging detected. > >> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = fe711000 iommu->reg = ffff82c3fff57000 > >> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c9008010e60262 ecap = f0207a > >> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = fe710000 iommu->reg = ffff82c3fff56000 > >> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c90780106f0462 ecap = f020fa > >> >> >> >> (XEN) Intel VT-d Snoop Control not supported. > >> >> >> >> (XEN) Intel VT-d DMA Passthrough not supported. > >> >> >> >> (XEN) Intel VT-d Queued Invalidation supported. > >> >> >> >> (XEN) Intel VT-d Interrupt Remapping supported. > >> >> >> >> (XEN) I/O virtualisation enabled > >> >> >> >> (XEN) I/O virtualisation for PV guests disabled > >> >> >> >> (XEN) Total of 8 processors activated. > >> >> >> >> (XEN) ENABLING IO-APIC IRQs > >> >> >> >> (XEN) -> Using new ACK method > >> >> >> >> (XEN) TSC is reliable, synchronization unnecessary > >> >> >> >> (XEN) Platform timer is 14.318MHz HPET > >> >> >> >> (XEN) Allocated console ring of 16 KiB. > >> >> >> >> (XEN) Brought up 8 CPUs > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:0.0 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.0 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.1 > >> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.0 > >> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.1 > >> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.2 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:14.3 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:19.0 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.0 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.1 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.2 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.7 > >> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:1b.0 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.0 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.1 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.2 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.7 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.0 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.2 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.3 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.5 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.0 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.1 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.2 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.0 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.1 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.2 > >> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 5:0.0 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.0 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.1 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.2 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.0 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.1 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.2 > >> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = a:0.0 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.0 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.1 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.2 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.3 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.4 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.5 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.6 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.7 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.0 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.1 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.0 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.1 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.0 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.1 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.4 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.0 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.1 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.2 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.3 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.0 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.1 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.2 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.3 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.0 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.1 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.2 > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.3 > >> >> >> >> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = ffff82c3fff57000 > >> >> >> >> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = ffff82c3fff56000 > >> >> >> >> (XEN) *** LOADING DOMAIN 0 *** > >> >> >> >> (XEN) Xen kernel: 64-bit, lsb, compat32 > >> >> >> >> (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x26ae000 > >> >> >> >> (XEN) PHYSICAL MEMORY ARRANGEMENT: > >> >> >> >> (XEN) Dom0 alloc.: 0000000210000000->0000000220000000 > >> >> >> >> (XEN) VIRTUAL MEMORY ARRANGEMENT: > >> >> >> >> (XEN) Loaded kernel: ffffffff81000000->ffffffff826ae000 > >> >> >> >> (XEN) Init. ramdisk: ffffffff826ae000->ffffffff8f4de600 > >> >> >> >> (XEN) Phys-Mach map: ffffffff8f4df000->ffffffff8f55f000 > >> >> >> >> (XEN) Start info: ffffffff8f55f000->ffffffff8f55f4b4 > >> >> >> >> (XEN) Page tables: ffffffff8f560000->ffffffff8f5df000 > >> >> >> >> (XEN) Boot stack: ffffffff8f5df000->ffffffff8f5e0000 > >> >> >> >> (XEN) TOTAL: ffffffff80000000->ffffffff8f800000 > >> >> >> >> (XEN) ENTRY ADDRESS: ffffffff81a10860 > >> >> >> >> (XEN) Dom0 has maximum 1 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 \047CTRL-a\047 three times to switch input to Xen) > >> >> >> >> (XEN) Freed 164kB init memory. > >> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 > >> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 > >> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 pirq=0 > >> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=2, irq=0 > >> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 > >> >> >> >> (XEN) ioapic_guest_write: old_entry=000009f0 pirq=0 > >> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 3 already mapped > >> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 4 already mapped > >> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 5 already mapped > >> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 6 already mapped > >> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 7 already mapped > >> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 8 already mapped > >> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 9 already mapped > >> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 10 already mapped > >> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 11 already mapped > >> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 12 already mapped > >> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 > >> >> >> >> (XEN) ioapic_guest_write: new_entry=000009f0 > >> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 pirq=0 > >> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 > >> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 > >> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 > >> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 > >> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 > >> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 > >> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=23, irq=23 > >> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a929 > >> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a929 pirq=23 > >> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 > >> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 > >> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 > >> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 > >> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 > >> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 > >> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 > >> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 > >> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 pirq=16 > >> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 > >> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 > >> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 pirq=16 > >> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 > >> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 > >> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 > >> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 > >> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 > >> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 > >> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >> >> >> > > >> >> >> >> _______________________________________________ > >> >> >> >> Xen-users mailing list > >> >> >> >> Xen-users@lists.xensource.com > >> >> >> >> http://lists.xensource.com/xen-users > >> >> >> > > >> >> > > >> > > > ^ permalink raw reply [flat|nested] 32+ messages in thread
* RE: Re: [Xen-users] xen/stable-2.6.32.x compilation failure in do_hvm_suspend() 2010-05-13 18:10 ` [Xen-users] xen/stable-2.6.32.x compilation failure in do_hvm_suspend() Pasi Kärkkäinen @ 2010-05-13 18:22 ` Dan Magenheimer 2010-05-13 18:32 ` M A Young 1 sibling, 0 replies; 32+ messages in thread From: Dan Magenheimer @ 2010-05-13 18:22 UTC (permalink / raw) To: "Pasi Kärkkäinen", chris; +Cc: xen-devel, Xen-Users List > -----Original Message----- > From: Pasi Kärkkäinen [mailto:pasik@iki.fi] > Sent: Thursday, May 13, 2010 12:11 PM > To: chris > Cc: xen-devel@lists.xensource.com; Xen-Users List > Subject: [Xen-devel] Re: [Xen-users] xen/stable-2.6.32.x compilation > failure in do_hvm_suspend() > > On Thu, May 13, 2010 at 02:07:47PM -0400, chris wrote: > > I redid it with oldconfig which I didn't think would help and same > > thing. I guess this tree is broken? Can someone else try and see if > > they can build it? Ugh, whata day :) > > > > I guess the tree is broken because of the recently added pv-on-hvm > driver > support.. > > Is there a known workaround for this? > > -- Pasi I changed a Kconfig file and got it to build, but never got it to boot (probably for other reasons). > > On Thu, May 13, 2010 at 1:58 PM, Pasi Kärkkäinen <pasik@iki.fi> > wrote: > > > On Thu, May 13, 2010 at 01:55:25PM -0400, chris wrote: > > >> I used the default config on the wiki which you created. Steps I > took were: > > >> > > >> # make clean distclean > > >> # wget -O .config > > >> "http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.10- > pvops-dom0-xen-stable-x86_64" > > > > > > You should do "make oldconfig" at this point. > > > > > >> # make -j8 bzImage > > >> (blah blah) > > >> LD vmlinux.o > > >> MODPOST vmlinux.o > > >> WARNING: modpost: Found 7 section mismatch(es). > > >> To see full details build your kernel with: > > >> 'make CONFIG_DEBUG_SECTION_MISMATCH=y' > > >> GEN .version > > >> CHK include/linux/compile.h > > >> UPD include/linux/compile.h > > >> CC init/version.o > > >> LD init/built-in.o > > >> LD .tmp_vmlinux1 > > >> drivers/built-in.o: In function `do_hvm_suspend': > > >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: undefined > reference > > >> to `xenbus_suspend' > > >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: undefined > reference > > >> to `xenbus_resume' > > >> make: *** [.tmp_vmlinux1] Error 1 > > >> > > > > > > Hmm.. weird. I wonder if something has changed recently or what's > going on in here.. > > > > > > -- Pasi > > > > > >> > > >> On Thu, May 13, 2010 at 11:47 AM, Pasi Kärkkäinen <pasik@iki.fi> > wrote: > > >> > On Thu, May 13, 2010 at 11:33:57AM -0400, chris wrote: > > >> >> Successfully grabbed the sources and failed to build: > > >> >> > > >> >> LD .tmp_vmlinux1 > > >> >> drivers/built-in.o: In function `do_hvm_suspend': > > >> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: undefined > reference > > >> >> to `xenbus_suspend' > > >> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: undefined > reference > > >> >> to `xenbus_resume' > > >> >> make: *** [.tmp_vmlinux1] Error 1 > > >> >> > > >> >> :( > > >> >> > > >> > > > >> > Try the example .config files provided on the wiki page. > > >> > > > >> > -- Pasi > > >> > > > >> >> On Thu, May 13, 2010 at 10:14 AM, Pasi Kärkkäinen > <pasik@iki.fi> wrote: > > >> >> > On Thu, May 13, 2010 at 10:12:56AM -0400, chris wrote: > > >> >> >> Pasi, > > >> >> >> > > >> >> >> How do I pull those kernel sources you referenced? I see it > mentioned > > >> >> >> on http://wiki.xensource.com/xenwiki/XenParavirtOps but no > details on > > >> >> >> how to retrieve it. > > >> >> >> > > >> >> > > > >> >> > The instructions are there if you read it carefully.. > > >> >> > There's the topic of how to switch branches. > > >> >> > > > >> >> > -- Pasi > > >> >> > > > >> >> >> - chris > > >> >> >> > > >> >> >> On Thu, May 13, 2010 at 8:29 AM, Pasi Kärkkäinen > <pasik@iki.fi> wrote: > > >> >> >> > On Wed, May 12, 2010 at 08:41:34PM -0400, chris wrote: > > >> >> >> >> When reading the vtdhowto I noticed the ability to set > iommu=verbose. > > >> >> >> >> Here is that output, I don't know if it helps at all to > figure out > > >> >> >> >> what is wrong. > > >> >> >> >> > > >> >> >> > > > >> >> >> > That seems to be OK: > > >> >> >> > > > >> >> >> > (XEN) I/O virtualisation enabled > > >> >> >> > (XEN) I/O virtualisation for PV guests disabled > > >> >> >> > > > >> >> >> > So hmm.. I wonder if it's related to MSI stuff? > > >> >> >> > You could try xen.git xen/stable-2.6.32.x branch instead > and see if that makes a difference.. > > >> >> >> > > > >> >> >> > -- Pasi > > >> >> >> > > > >> >> >> >> > > >> >> >> >> ---------- Forwarded message ---------- > > >> >> >> >> From: chris <tknchris@gmail.com> > > >> >> >> >> Date: Wed, May 12, 2010 at 5:28 PM > > >> >> >> >> Subject: Xen4 / Intel DX58SO Mobo / VT-d not working > > >> >> >> >> To: Xen-Users List <xen-users@lists.xensource.com> > > >> >> >> >> > > >> >> >> >> > > >> >> >> >> Hello, > > >> >> >> >> > > >> >> >> >> I've previously been successful with Xen4 and VT-d on > other systems. I > > >> >> >> >> am having trouble getting VT-d passthrough working to a > WinXP domain > > >> >> >> >> with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is > enabled in bios, > > >> >> >> >> xm info shows hvm_directio capability, I have iommu=1 > set, I have the > > >> >> >> >> devices bound to pciback on dom0 cmdline, xm > > >> >> >> >> pci-list-assignable-devices shows the devices as > assignable. When I > > >> >> >> >> attempt to start the VM I get the error: > > >> >> >> >> > > >> >> >> >> Error: Failed to assign device to IOMMU > > >> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) > > >> >> >> >> > > >> >> >> >> Below is all the information I can think of that would be > useful to > > >> >> >> >> help debug it: > > >> >> >> >> > > >> >> >> >> BIOS VT-d Enabled: > > >> >> >> >> http://i43.tinypic.com/nl3a5e.jpg > > >> >> >> >> http://i42.tinypic.com/nqvlu1.jpg > > >> >> >> >> > > >> >> >> >> grub entry: > > >> >> >> >> > > >> >> >> >> title Xen 4.0.0 / Debian GNU/Linux, kernel > 2.6.31.13 > > >> >> >> >> root (hd0,0) > > >> >> >> >> kernel /boot/xen-4.0.0.gz iommu=1 dom0_mem=256M > > >> >> >> >> dom0_max_vcpus=1 dom0_vcpus_pin=true > > >> >> >> >> module /boot/vmlinuz-2.6.31.13 root=/dev/md0 ro > console=tty0 > > >> >> >> >> xen-pciback.permissive > > >> >> >> >> xen- > pciback.hide=(02:00.0)(02:00.1)(02:00.2)(04:00.0)(04:00.1)(04:00.2)(07: > 00.0)(07:00.1)(07:00.2)(09:00.0)(09:00.1)(09:00.2) > > >> >> >> >> module /boot/initrd.img-2.6.31.13 > > >> >> >> >> > > >> >> >> >> # xm pci-list-assignable-devices > > >> >> >> >> 0000:09:00.0 > > >> >> >> >> 0000:09:00.1 > > >> >> >> >> 0000:09:00.2 > > >> >> >> >> 0000:07:00.0 > > >> >> >> >> 0000:07:00.1 > > >> >> >> >> 0000:07:00.2 > > >> >> >> >> 0000:04:00.0 > > >> >> >> >> 0000:04:00.1 > > >> >> >> >> 0000:04:00.2 > > >> >> >> >> 0000:02:00.0 > > >> >> >> >> 0000:02:00.1 > > >> >> >> >> 0000:02:00.2 > > >> >> >> >> > > >> >> >> >> # xm info > > >> >> >> >> host : test-box2 > > >> >> >> >> release : 2.6.31.13 > > >> >> >> >> version : #2 SMP Wed May 12 14:11:37 EDT > 2010 > > >> >> >> >> machine : x86_64 > > >> >> >> >> nr_cpus : 8 > > >> >> >> >> nr_nodes : 1 > > >> >> >> >> cores_per_socket : 4 > > >> >> >> >> threads_per_core : 2 > > >> >> >> >> cpu_mhz : 2800 > > >> >> >> >> hw_caps : > > >> >> >> >> > bfebfbff:28100800:00000000:00001b40:0098e3bd:00000000:00000001:00000000 > > >> >> >> >> virt_caps : hvm hvm_directio > > >> >> >> >> total_memory : 7950 > > >> >> >> >> free_memory : 7812 > > >> >> >> >> node_to_cpu : node0:0-7 > > >> >> >> >> node_to_memory : node0:7812 > > >> >> >> >> node_to_dma32_mem : node0:3249 > > >> >> >> >> max_node_id : 0 > > >> >> >> >> xen_major : 4 > > >> >> >> >> xen_minor : 0 > > >> >> >> >> xen_extra : .0 > > >> >> >> >> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p > hvm-3.0-x86_32 > > >> >> >> >> hvm-3.0-x86_32p hvm-3.0-x86_64 > > >> >> >> >> xen_scheduler : credit > > >> >> >> >> xen_pagesize : 4096 > > >> >> >> >> platform_params : virt_start=0xffff800000000000 > > >> >> >> >> xen_changeset : unavailable > > >> >> >> >> xen_commandline : iommu=1 dom0_mem=256M > dom0_max_vcpus=1 > > >> >> >> >> dom0_vcpus_pin=true > > >> >> >> >> cc_compiler : gcc version 4.3.2 (Debian 4.3.2- > 1.1) > > >> >> >> >> cc_compile_by : root > > >> >> >> >> cc_compile_domain : > > >> >> >> >> cc_compile_date : Thu May 6 13:41:25 EDT 2010 > > >> >> >> >> xend_config_format : 4 > > >> >> >> >> > > >> >> >> >> # xm create vm-five.cfg > > >> >> >> >> Using config file "./vm-five.cfg". > > >> >> >> >> Error: Failed to assign device to IOMMU > > >> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) > > >> >> >> >> > > >> >> >> >> I feel like I'm missing something really obvious but I've > been at it > > >> >> >> >> for a while now and have run out of brain power. Anyone > have any idea > > >> >> >> >> what might be wrong? > > >> >> >> >> > > >> >> >> >> - chris > > >> >> >> > > > >> >> >> >> __ __ _ _ ___ ___ > > >> >> >> >> \ \/ /___ _ __ | || | / _ \ / _ \ > > >> >> >> >> \ // _ \ \047_ \ | || |_| | | | | | | > > >> >> >> >> / \ __/ | | | |__ _| |_| | |_| | > > >> >> >> >> /_/\_\___|_| |_| |_|(_)___(_)___/ > > >> >> >> >> > > >> >> >> >> (XEN) Xen version 4.0.0 (root@) (gcc version 4.3.2 > (Debian 4.3.2-1.1) ) Thu May 6 13:41:25 EDT 2010 > > >> >> >> >> (XEN) Latest ChangeSet: unavailable > > >> >> >> >> (XEN) Command line: iommu=verbose dom0_mem=256M > dom0_max_vcpus=1 dom0_vcpus_pin=true > > >> >> >> >> (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 - 000000000008f000 (usable) > > >> >> >> >> (XEN) 000000000008f000 - 0000000000090000 (reserved) > > >> >> >> >> (XEN) 0000000000090000 - 000000000009ec00 (usable) > > >> >> >> >> (XEN) 000000000009ec00 - 00000000000a0000 (reserved) > > >> >> >> >> (XEN) 00000000000e0000 - 0000000000100000 (reserved) > > >> >> >> >> (XEN) 0000000000100000 - 00000000cf4bd000 (usable) > > >> >> >> >> (XEN) 00000000cf4bd000 - 00000000cf4bf000 (reserved) > > >> >> >> >> (XEN) 00000000cf4bf000 - 00000000cf4c2000 (usable) > > >> >> >> >> (XEN) 00000000cf4c2000 - 00000000cf7bf000 (ACPI NVS) > > >> >> >> >> (XEN) 00000000cf7bf000 - 00000000cf7df000 (usable) > > >> >> >> >> (XEN) 00000000cf7df000 - 00000000cf7ff000 (ACPI data) > > >> >> >> >> (XEN) 00000000cf7ff000 - 00000000cf800000 (usable) > > >> >> >> >> (XEN) 00000000cf800000 - 00000000d0000000 (reserved) > > >> >> >> >> (XEN) 00000000f8000000 - 00000000fd000000 (reserved) > > >> >> >> >> (XEN) 00000000ffe00000 - 0000000100000000 (reserved) > > >> >> >> >> (XEN) 0000000100000000 - 0000000230000000 (usable) > > >> >> >> >> (XEN) ACPI: RSDP 000FE020, 0024 (r2 INTEL ) > > >> >> >> >> (XEN) ACPI: XSDT CF7FE120, 0074 (r1 INTEL DX58SO > 11F6 1000013) > > >> >> >> >> (XEN) ACPI: FACP CF7FD000, 00F4 (r3 INTEL DX58SO > 11F6 MSFT 100000D) > > >> >> >> >> (XEN) ACPI Warning (tbfadt-0444): Optional field > "Pm2ControlBlock" has zero address or length: 0000000000000450/0 > [20070126] > > >> >> >> >> (XEN) ACPI: DSDT CF7F8000, 4641 (r2 INTEL DX58SO > 11F6 MSFT 100000D) > > >> >> >> >> (XEN) ACPI: FACS CF728000, 0040 > > >> >> >> >> (XEN) ACPI: APIC CF7F7000, 0138 (r2 INTEL DX58SO > 11F6 MSFT 100000D) > > >> >> >> >> (XEN) ACPI: WDDT CF7F6000, 0040 (r1 INTEL DX58SO > 11F6 MSFT 100000D) > > >> >> >> >> (XEN) ACPI: MCFG CF7F5000, 003C (r1 INTEL DX58SO > 11F6 MSFT 100000D) > > >> >> >> >> (XEN) ACPI: ASF! CF7F4000, 00AC (r32 INTEL DX58SO > 11F6 MSFT 100000D) > > >> >> >> >> (XEN) ACPI: HPET CF7F3000, 0038 (r1 INTEL DX58SO > 11F6 MSFT 100000D) > > >> >> >> >> (XEN) ACPI: SSDT CF7E2000, E134 (r1 INTEL SSDT PM > 11F6 MSFT 100000D) > > >> >> >> >> (XEN) ACPI: DMAR CF7DF000, 0140 (r1 INTEL DX58SO > 11F6 MSFT 100000D) > > >> >> >> >> (XEN) ACPI: WDTT CF7F1000, 020C (r2 INTEL DX58SO > 11F6 MSFT 100000D) > > >> >> >> >> (XEN) ACPI: ASPT CF7F2000, 0034 (r4 INTEL PerfTune > 11F6 MSFT 100000D) > > >> >> >> >> (XEN) System RAM: 7950MB (8140820kB) > > >> >> >> >> (XEN) Domain heap initialised > > >> >> >> >> (XEN) Processor #0 7:10 APIC version 21 > > >> >> >> >> (XEN) Processor #2 7:10 APIC version 21 > > >> >> >> >> (XEN) Processor #4 7:10 APIC version 21 > > >> >> >> >> (XEN) Processor #6 7:10 APIC version 21 > > >> >> >> >> (XEN) Processor #1 7:10 APIC version 21 > > >> >> >> >> (XEN) Processor #3 7:10 APIC version 21 > > >> >> >> >> (XEN) Processor #5 7:10 APIC version 21 > > >> >> >> >> (XEN) Processor #7 7:10 APIC version 21 > > >> >> >> >> (XEN) IOAPIC[0]: apic_id 8, version 32, address > 0xfec00000, GSI 0-23 > > >> >> >> >> (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > > >> >> >> >> (XEN) [VT-D]dmar.c:679: Host address width 39 > > >> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: > > >> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = fe711000 > > >> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1b.0 > > >> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: > > >> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = fe710000 > > >> >> >> >> (XEN) [VT-D]dmar.c:340: IOAPIC: f0:1f.7 > > >> >> >> >> (XEN) [VT-D]dmar.c:411: flags: INCLUDE_ALL > > >> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > > >> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 > > >> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e9000 > end_address e9fff > > >> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > > >> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.1 > > >> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ea000 > end_address eafff > > >> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > > >> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.2 > > >> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr eb000 > end_address ebfff > > >> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > > >> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.0 > > >> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e6000 > end_address e6fff > > >> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > > >> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.1 > > >> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e7000 > end_address e7fff > > >> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > > >> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.2 > > >> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e8000 > end_address e8fff > > >> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > > >> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 > > >> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ec000 > end_address eefff > > >> >> >> >> (XEN) Using scheduler: SMP Credit Scheduler (credit) > > >> >> >> >> (XEN) Detected 2800.125 MHz processor. > > >> >> >> >> (XEN) Initing memory sharing. > > >> >> >> >> (XEN) VMX: Supported advanced features: > > >> >> >> >> (XEN) - APIC MMIO access virtualisation > > >> >> >> >> (XEN) - APIC TPR shadow > > >> >> >> >> (XEN) - Extended Page Tables (EPT) > > >> >> >> >> (XEN) - Virtual-Processor Identifiers (VPID) > > >> >> >> >> (XEN) - Virtual NMI > > >> >> >> >> (XEN) - MSR direct-access bitmap > > >> >> >> >> (XEN) HVM: ASIDs enabled. > > >> >> >> >> (XEN) HVM: VMX enabled > > >> >> >> >> (XEN) HVM: Hardware Assisted Paging detected. > > >> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = fe711000 iommu- > >reg = ffff82c3fff57000 > > >> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c9008010e60262 ecap = > f0207a > > >> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = fe710000 iommu- > >reg = ffff82c3fff56000 > > >> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c90780106f0462 ecap = > f020fa > > >> >> >> >> (XEN) Intel VT-d Snoop Control not supported. > > >> >> >> >> (XEN) Intel VT-d DMA Passthrough not supported. > > >> >> >> >> (XEN) Intel VT-d Queued Invalidation supported. > > >> >> >> >> (XEN) Intel VT-d Interrupt Remapping supported. > > >> >> >> >> (XEN) I/O virtualisation enabled > > >> >> >> >> (XEN) I/O virtualisation for PV guests disabled > > >> >> >> >> (XEN) Total of 8 processors activated. > > >> >> >> >> (XEN) ENABLING IO-APIC IRQs > > >> >> >> >> (XEN) -> Using new ACK method > > >> >> >> >> (XEN) TSC is reliable, synchronization unnecessary > > >> >> >> >> (XEN) Platform timer is 14.318MHz HPET > > >> >> >> >> (XEN) Allocated console ring of 16 KiB. > > >> >> >> >> (XEN) Brought up 8 CPUs > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:0.0 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.0 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.1 > > >> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.0 > > >> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.1 > > >> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.2 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:14.3 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:19.0 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.0 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.1 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.2 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.7 > > >> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:1b.0 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.0 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.1 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.2 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.7 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.0 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.2 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.3 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.5 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.0 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.1 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.2 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.0 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.1 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.2 > > >> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 5:0.0 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.0 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.1 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.2 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.0 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.1 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.2 > > >> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = a:0.0 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.0 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.1 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.2 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.3 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.4 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.5 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.6 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.7 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.0 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.1 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.0 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.1 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.0 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.1 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.4 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.0 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.1 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.2 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.3 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.0 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.1 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.2 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.3 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.0 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.1 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.2 > > >> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.3 > > >> >> >> >> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu- > >reg = ffff82c3fff57000 > > >> >> >> >> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu- > >reg = ffff82c3fff56000 > > >> >> >> >> (XEN) *** LOADING DOMAIN 0 *** > > >> >> >> >> (XEN) Xen kernel: 64-bit, lsb, compat32 > > >> >> >> >> (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> > 0x26ae000 > > >> >> >> >> (XEN) PHYSICAL MEMORY ARRANGEMENT: > > >> >> >> >> (XEN) Dom0 alloc.: 0000000210000000->0000000220000000 > > >> >> >> >> (XEN) VIRTUAL MEMORY ARRANGEMENT: > > >> >> >> >> (XEN) Loaded kernel: ffffffff81000000->ffffffff826ae000 > > >> >> >> >> (XEN) Init. ramdisk: ffffffff826ae000->ffffffff8f4de600 > > >> >> >> >> (XEN) Phys-Mach map: ffffffff8f4df000->ffffffff8f55f000 > > >> >> >> >> (XEN) Start info: ffffffff8f55f000->ffffffff8f55f4b4 > > >> >> >> >> (XEN) Page tables: ffffffff8f560000->ffffffff8f5df000 > > >> >> >> >> (XEN) Boot stack: ffffffff8f5df000->ffffffff8f5e0000 > > >> >> >> >> (XEN) TOTAL: ffffffff80000000->ffffffff8f800000 > > >> >> >> >> (XEN) ENTRY ADDRESS: ffffffff81a10860 > > >> >> >> >> (XEN) Dom0 has maximum 1 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 \047CTRL-a\047 three > times to switch input to Xen) > > >> >> >> >> (XEN) Freed 164kB init memory. > > >> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 > > >> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 > > >> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 pirq=0 > > >> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin > for in-use IRQ! > > >> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=2, irq=0 > > >> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 > > >> >> >> >> (XEN) ioapic_guest_write: old_entry=000009f0 pirq=0 > > >> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin > for in-use IRQ! > > >> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 3 already mapped > > >> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 4 already mapped > > >> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 5 already mapped > > >> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 6 already mapped > > >> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 7 already mapped > > >> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 8 already mapped > > >> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 9 already mapped > > >> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 10 already mapped > > >> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 11 already mapped > > >> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 12 already mapped > > >> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 > > >> >> >> >> (XEN) ioapic_guest_write: new_entry=000009f0 > > >> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 pirq=0 > > >> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin > for in-use IRQ! > > >> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 > > >> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 > > >> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 > > >> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin > for in-use IRQ! > > >> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 > > >> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 > > >> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 > > >> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin > for in-use IRQ! > > >> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=23, irq=23 > > >> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a929 > > >> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a929 pirq=23 > > >> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin > for in-use IRQ! > > >> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 > > >> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 > > >> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 > > >> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin > for in-use IRQ! > > >> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 > > >> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 > > >> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 > > >> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin > for in-use IRQ! > > >> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 > > >> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 > > >> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 pirq=16 > > >> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin > for in-use IRQ! > > >> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 > > >> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 > > >> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 pirq=16 > > >> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin > for in-use IRQ! > > >> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 > > >> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 > > >> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 > > >> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin > for in-use IRQ! > > >> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 > > >> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 > > >> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 > > >> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin > for in-use IRQ! > > >> >> >> > > > >> >> >> >> _______________________________________________ > > >> >> >> >> Xen-users mailing list > > >> >> >> >> Xen-users@lists.xensource.com > > >> >> >> >> http://lists.xensource.com/xen-users > > >> >> >> > > > >> >> > > > >> > > > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: Re: [Xen-users] xen/stable-2.6.32.x compilation failure in do_hvm_suspend() 2010-05-13 18:10 ` [Xen-users] xen/stable-2.6.32.x compilation failure in do_hvm_suspend() Pasi Kärkkäinen 2010-05-13 18:22 ` Dan Magenheimer @ 2010-05-13 18:32 ` M A Young 2010-05-13 18:37 ` [Xen-devel] " chris 1 sibling, 1 reply; 32+ messages in thread From: M A Young @ 2010-05-13 18:32 UTC (permalink / raw) To: Pasi Kärkkäinen; +Cc: xen-devel, chris, Xen-Users List [-- Attachment #1: Type: TEXT/PLAIN, Size: 751 bytes --] On Thu, 13 May 2010, Pasi Kärkkäinen wrote: > On Thu, May 13, 2010 at 02:07:47PM -0400, chris wrote: >> I redid it with oldconfig which I didn't think would help and same >> thing. I guess this tree is broken? Can someone else try and see if >> they can build it? Ugh, whata day :) >> > > I guess the tree is broken because of the recently added pv-on-hvm driver > support.. > > Is there a known workaround for this? That looks like something I found a week or so ago. The current stable-2.6.32.x tree needs CONFIG_XEN_XENBUS_FRONTEND=y (or CONFIG_PM_SLEEP=n). However you can't set this directly, so one of XEN_PCIDEV_FRONTEND XEN_BLKDEV_FRONTEND XEN_NETDEV_FRONTEND XEN_FBDEV_FRONTEND needs to be set to y . Michael Young [-- Attachment #2: 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] 32+ messages in thread
* Re: [Xen-devel] Re: xen/stable-2.6.32.x compilation failure in do_hvm_suspend() 2010-05-13 18:32 ` M A Young @ 2010-05-13 18:37 ` chris 2010-05-13 18:44 ` Re: [Xen-users] " M A Young 0 siblings, 1 reply; 32+ messages in thread From: chris @ 2010-05-13 18:37 UTC (permalink / raw) To: M A Young; +Cc: xen-devel, Xen-Users List, Pasi Kärkkäinen I tried your config options and they do not help at all. Just FYI for other people following this thread On Thu, May 13, 2010 at 2:32 PM, M A Young <m.a.young@durham.ac.uk> wrote: > On Thu, 13 May 2010, Pasi Kärkkäinen wrote: > >> On Thu, May 13, 2010 at 02:07:47PM -0400, chris wrote: >>> >>> I redid it with oldconfig which I didn't think would help and same >>> thing. I guess this tree is broken? Can someone else try and see if >>> they can build it? Ugh, whata day :) >>> >> >> I guess the tree is broken because of the recently added pv-on-hvm driver >> support.. >> >> Is there a known workaround for this? > > That looks like something I found a week or so ago. The current > stable-2.6.32.x tree needs CONFIG_XEN_XENBUS_FRONTEND=y (or > CONFIG_PM_SLEEP=n). However you can't set this directly, so one of > XEN_PCIDEV_FRONTEND XEN_BLKDEV_FRONTEND XEN_NETDEV_FRONTEND > XEN_FBDEV_FRONTEND needs to be set to y . > > Michael Young ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: Re: [Xen-users] xen/stable-2.6.32.x compilation failure in do_hvm_suspend() 2010-05-13 18:37 ` [Xen-devel] " chris @ 2010-05-13 18:44 ` M A Young 2010-05-13 18:50 ` chris 0 siblings, 1 reply; 32+ messages in thread From: M A Young @ 2010-05-13 18:44 UTC (permalink / raw) To: chris; +Cc: xen-devel, Xen-Users List On Thu, 13 May 2010, chris wrote: > I tried your config options and they do not help at all. Just FYI for > other people following this thread What option did you change? Michael Young ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: Re: [Xen-users] xen/stable-2.6.32.x compilation failure in do_hvm_suspend() 2010-05-13 18:44 ` Re: [Xen-users] " M A Young @ 2010-05-13 18:50 ` chris 2010-05-14 14:45 ` chris 0 siblings, 1 reply; 32+ messages in thread From: chris @ 2010-05-13 18:50 UTC (permalink / raw) To: M A Young; +Cc: xen-devel, Xen-Users List i tried setting XEN_XENBUS_FRONTEND=y XEN_PCIDEV_FRONTEND=y XEN_BLKDEV_FRONTEND=y On Thu, May 13, 2010 at 2:44 PM, M A Young <m.a.young@durham.ac.uk> wrote: > On Thu, 13 May 2010, chris wrote: > >> I tried your config options and they do not help at all. Just FYI for >> other people following this thread > > What option did you change? > > Michael Young > ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: Re: [Xen-users] xen/stable-2.6.32.x compilation failure in do_hvm_suspend() 2010-05-13 18:50 ` chris @ 2010-05-14 14:45 ` chris [not found] ` <4BED8925.8010405@interface-tech.com> 0 siblings, 1 reply; 32+ messages in thread From: chris @ 2010-05-14 14:45 UTC (permalink / raw) To: M A Young; +Cc: xen-devel, Xen-Users List Is there any update on this? I would imagine the broken tree is kind of a big deal since many people build their dom0 from this? Even a workaround would be nice for the time being... On Thu, May 13, 2010 at 2:50 PM, chris <tknchris@gmail.com> wrote: > i tried setting > > XEN_XENBUS_FRONTEND=y > XEN_PCIDEV_FRONTEND=y > XEN_BLKDEV_FRONTEND=y > > On Thu, May 13, 2010 at 2:44 PM, M A Young <m.a.young@durham.ac.uk> wrote: >> On Thu, 13 May 2010, chris wrote: >> >>> I tried your config options and they do not help at all. Just FYI for >>> other people following this thread >> >> What option did you change? >> >> Michael Young >> > ^ permalink raw reply [flat|nested] 32+ messages in thread
[parent not found: <4BED8925.8010405@interface-tech.com>]
* Re: Re: [Xen-users] xen/stable-2.6.32.x compilation failure in do_hvm_suspend() [not found] ` <4BED8925.8010405@interface-tech.com> @ 2010-05-14 17:41 ` chris 2010-05-14 18:51 ` Pasi Kärkkäinen 0 siblings, 1 reply; 32+ messages in thread From: chris @ 2010-05-14 17:41 UTC (permalink / raw) To: Pierre POMES; +Cc: Xen-Devel List, Xen-Users List [-- Attachment #1.1.1: Type: text/plain, Size: 2904 bytes --] I haven't figured out what is different yet, but I CAN build with this kernel config. So what's different in pasi's config that causes it to fail? Thanks Pierre! - chris On Fri, May 14, 2010 at 1:32 PM, Pierre POMES < pierre.pomes@interface-tech.com> wrote: > Hi Chris, > > I just build yesterday a pvops kernel with the config in attachment, on > Ubuntu lucid 64 bits, from "xen/stable-2.6.32x" git branch. In my case, the > tree does not seem broken. > > My version of gcc is : > > root@narbonne:/usr/src/XEN/debian/xen-3.4-3.4.1# gcc -v > Using built-in specs. > Target: x86_64-linux-gnu > Configured with: ../src/configure -v --with-pkgversion='Ubuntu > 4.4.3-4ubuntu5' --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs--enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared > --enable-multiarch --enable-linker-build-id --with-system-zlib > --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix > --with-gxx-include-dir=/usr/include/c++/4.4 --program-suffix=-4.4 > --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-plugin > --enable-objc-gc --disable-werror --with-arch-32=i486 --with-tune=generic > --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu > --target=x86_64-linux-gnu > Thread model: posix > gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) > > Maybe a problem with your gcc ? I trashed all mail, can you remind me the > error you have ? I don't know if I could help you, but I will have a look. > > Pierre > > > > Is there any update on this? I would imagine the broken tree is kind > of a big deal since many people build their dom0 from this? Even a > workaround would be nice for the time being... > > On Thu, May 13, 2010 at 2:50 PM, chris <tknchris@gmail.com> <tknchris@gmail.com> wrote: > > > i tried setting > > XEN_XENBUS_FRONTEND=y > XEN_PCIDEV_FRONTEND=y > XEN_BLKDEV_FRONTEND=y > > On Thu, May 13, 2010 at 2:44 PM, M A Young <m.a.young@durham.ac.uk> <m.a.young@durham.ac.uk> wrote: > > > On Thu, 13 May 2010, chris wrote: > > > > I tried your config options and they do not help at all. Just FYI for > other people following this thread > > > What option did you change? > > Michael Young > > > > _______________________________________________ > Xen-devel mailing listXen-devel@lists.xensource.comhttp://lists.xensource.com/xen-devel > > > > -- > *Pierre Pomès * > *Responsable Administration Système - System Administration Manager * > *ReservIT* http://www.reservit.com > ------------------------------ > *Direct: * +33 (0)4 86 06 51 82 *Standard: * +33 (0)4 86 06 50 50 * > Fax: * +33 (0)4 86 06 50 51 pierre.pomes@intertace-tech.com > ------------------------------ > *Actiparc 1, Bâtiment 1.5 > 9001 Avenue Claude Antonetti > 13821 La Penne sur Huveaune - France > > * > [-- Attachment #1.1.2: Type: text/html, Size: 4726 bytes --] [-- Attachment #1.2: logo_signature.jpg --] [-- Type: image/jpeg, Size: 2634 bytes --] [-- Attachment #2: 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] 32+ messages in thread
* Re: Re: [Xen-users] xen/stable-2.6.32.x compilation failure in do_hvm_suspend() 2010-05-14 17:41 ` chris @ 2010-05-14 18:51 ` Pasi Kärkkäinen 2010-05-14 18:53 ` Pierre POMES 0 siblings, 1 reply; 32+ messages in thread From: Pasi Kärkkäinen @ 2010-05-14 18:51 UTC (permalink / raw) To: chris; +Cc: Xen-Devel List, Xen-Users List, Pierre POMES On Fri, May 14, 2010 at 01:41:34PM -0400, chris wrote: > I haven't figured out what is different yet, but I CAN build with this > kernel config. So what's different in pasi's config that causes it to > fail? > > Thanks Pierre! > Can you please post the working .config ? -- Pasi > - chris > > On Fri, May 14, 2010 at 1:32 PM, Pierre POMES > <[1]pierre.pomes@interface-tech.com> wrote: > > Hi Chris, > > I just build yesterday a pvops kernel with the config in attachment, on > Ubuntu lucid 64 bits, from "xen/stable-2.6.32x" git branch. In my case, > the tree does not seem broken. > > My version of gcc is : > > [2]root@narbonne:/usr/src/XEN/debian/xen-3.4-3.4.1# gcc -v > Using built-in specs. > Target: x86_64-linux-gnu > Configured with: ../src/configure -v --with-pkgversion='Ubuntu > 4.4.3-4ubuntu5' --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs > --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr > --enable-shared --enable-multiarch --enable-linker-build-id > --with-system-zlib --libexecdir=/usr/lib --without-included-gettext > --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.4 > --program-suffix=-4.4 --enable-nls --enable-clocale=gnu > --enable-libstdcxx-debug --enable-plugin --enable-objc-gc > --disable-werror --with-arch-32=i486 --with-tune=generic > --enable-checking=release --build=x86_64-linux-gnu > --host=x86_64-linux-gnu --target=x86_64-linux-gnu > Thread model: posix > gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) > Maybe a problem with your gcc ? I trashed all mail, can you remind me > the error you have ? I don't know if I could help you, but I will have a > look. > > Pierre > > Is there any update on this? I would imagine the broken tree is kind > of a big deal since many people build their dom0 from this? Even a > workaround would be nice for the time being... > > On Thu, May 13, 2010 at 2:50 PM, chris [3]<tknchris@gmail.com> wrote: > > > i tried setting > > XEN_XENBUS_FRONTEND=y > XEN_PCIDEV_FRONTEND=y > XEN_BLKDEV_FRONTEND=y > > On Thu, May 13, 2010 at 2:44 PM, M A Young [4]<m.a.young@durham.ac.uk> wrote: > > > On Thu, 13 May 2010, chris wrote: > > > > I tried your config options and they do not help at all. Just FYI for > other people following this thread > > > What option did you change? > > Michael Young > > > > > > _______________________________________________ > Xen-devel mailing list > [5]Xen-devel@lists.xensource.com > [6]http://lists.xensource.com/xen-devel > > > -- > Pierre Pomès > Responsable Administration Système - System Administration Manager > ReservIT [7]http://www.reservit.com > > ----------------------- > > Direct: +33 (0)4 86 06 51 82 > Standard: +33 (0)4 86 06 50 50 > Fax: +33 (0)4 86 06 50 51 > > [8]pierre.pomes@intertace-tech.com > > ----------------------- > > Actiparc 1, Bâtiment 1.5 > 9001 Avenue Claude Antonetti > 13821 La Penne sur Huveaune - France > > References > > Visible links > 1. mailto:pierre.pomes@interface-tech.com > 2. mailto:root@narbonne/usr/src/XEN/debian/xen-3.4-3.4.1# > 3. mailto:tknchris@gmail.com > 4. mailto:m.a.young@durham.ac.uk > 5. mailto:Xen-devel@lists.xensource.com > 6. http://lists.xensource.com/xen-devel > 7. http://www.reservit.com/ > 8. mailto:pierre.pomes@intertace-tech.com > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: Re: [Xen-users] xen/stable-2.6.32.x compilation failure in do_hvm_suspend() 2010-05-14 18:51 ` Pasi Kärkkäinen @ 2010-05-14 18:53 ` Pierre POMES 2010-05-14 19:15 ` Pasi Kärkkäinen 0 siblings, 1 reply; 32+ messages in thread From: Pierre POMES @ 2010-05-14 18:53 UTC (permalink / raw) To: Pasi Kärkkäinen; +Cc: Xen-Devel List, chris, Xen-Users List [-- Attachment #1: Type: text/plain, Size: 158 bytes --] Le 2010-05-14 14:51, Pasi Kärkkäinen a écrit : > > Can you please post the working .config ? > > -- Pasi > > Here it is ! Regards, Pierre [-- Attachment #2: config-2.6.32.12-it-xen --] [-- Type: text/plain, Size: 109204 bytes --] # # Automatically generated make config: don't edit # Linux kernel version: 2.6.32.12-it-xen # Thu May 13 22:31:10 2010 # CONFIG_64BIT=y # CONFIG_X86_32 is not set CONFIG_X86_64=y CONFIG_X86=y CONFIG_OUTPUT_FORMAT="elf64-x86-64" CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig" CONFIG_GENERIC_TIME=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_HAVE_LATENCYTOP_SUPPORT=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y CONFIG_GENERIC_HWEIGHT=y CONFIG_GENERIC_GPIO=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y # CONFIG_RWSEM_GENERIC_SPINLOCK is not set CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_GENERIC_TIME_VSYSCALL=y CONFIG_ARCH_HAS_CPU_RELAX=y CONFIG_ARCH_HAS_DEFAULT_IDLE=y CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y CONFIG_HAVE_SETUP_PER_CPU_AREA=y CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y CONFIG_HAVE_CPUMASK_OF_CPU_MAP=y CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y CONFIG_ZONE_DMA32=y CONFIG_ARCH_POPULATES_NODE_MAP=y CONFIG_AUDIT_ARCH=y CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_HARDIRQS_NO__DO_IRQ=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_GENERIC_PENDING_IRQ=y CONFIG_USE_GENERIC_SMP_HELPERS=y CONFIG_X86_64_SMP=y CONFIG_X86_HT=y CONFIG_X86_TRAMPOLINE=y # CONFIG_KTIME_SCALAR is not set CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" CONFIG_CONSTRUCTORS=y # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION="" # CONFIG_LOCALVERSION_AUTO is not set CONFIG_HAVE_KERNEL_GZIP=y CONFIG_HAVE_KERNEL_BZIP2=y CONFIG_HAVE_KERNEL_LZMA=y CONFIG_KERNEL_GZIP=y # CONFIG_KERNEL_BZIP2 is not set # CONFIG_KERNEL_LZMA is not set CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_POSIX_MQUEUE_SYSCTL=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_BSD_PROCESS_ACCT_V3=y CONFIG_TASKSTATS=y # CONFIG_TASK_DELAY_ACCT is not set CONFIG_TASK_XACCT=y CONFIG_TASK_IO_ACCOUNTING=y CONFIG_AUDIT=y CONFIG_AUDITSYSCALL=y CONFIG_AUDIT_TREE=y # # RCU Subsystem # CONFIG_TREE_RCU=y # CONFIG_TREE_PREEMPT_RCU is not set # CONFIG_RCU_TRACE is not set CONFIG_RCU_FANOUT=64 # CONFIG_RCU_FANOUT_EXACT is not set # CONFIG_TREE_RCU_TRACE is not set # CONFIG_IKCONFIG is not set CONFIG_LOG_BUF_SHIFT=18 CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y CONFIG_GROUP_SCHED=y CONFIG_FAIR_GROUP_SCHED=y CONFIG_RT_GROUP_SCHED=y # CONFIG_USER_SCHED is not set CONFIG_CGROUP_SCHED=y CONFIG_CGROUPS=y # CONFIG_CGROUP_DEBUG is not set CONFIG_CGROUP_NS=y CONFIG_CGROUP_FREEZER=y CONFIG_CGROUP_DEVICE=y CONFIG_CPUSETS=y CONFIG_PROC_PID_CPUSET=y CONFIG_CGROUP_CPUACCT=y CONFIG_RESOURCE_COUNTERS=y CONFIG_CGROUP_MEM_RES_CTLR=y CONFIG_CGROUP_MEM_RES_CTLR_SWAP=y CONFIG_MM_OWNER=y # CONFIG_SYSFS_DEPRECATED_V2 is not set CONFIG_RELAY=y CONFIG_NAMESPACES=y CONFIG_UTS_NS=y CONFIG_IPC_NS=y CONFIG_USER_NS=y CONFIG_PID_NS=y CONFIG_NET_NS=y CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="" CONFIG_RD_GZIP=y CONFIG_RD_BZIP2=y CONFIG_RD_LZMA=y # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=y CONFIG_ANON_INODES=y # CONFIG_EMBEDDED is not set CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_PCSPKR_PLATFORM=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_TIMERFD=y CONFIG_EVENTFD=y CONFIG_SHMEM=y CONFIG_AIO=y CONFIG_HAVE_PERF_EVENTS=y # # Kernel Performance Events And Counters # CONFIG_PERF_EVENTS=y CONFIG_EVENT_PROFILE=y CONFIG_PERF_COUNTERS=y # CONFIG_DEBUG_PERF_USE_VMALLOC is not set CONFIG_VM_EVENT_COUNTERS=y CONFIG_PCI_QUIRKS=y CONFIG_SLUB_DEBUG=y # CONFIG_COMPAT_BRK is not set # CONFIG_SLAB is not set CONFIG_SLUB=y # CONFIG_SLOB is not set CONFIG_PROFILING=y CONFIG_TRACEPOINTS=y CONFIG_OPROFILE=m CONFIG_OPROFILE_IBS=y # CONFIG_OPROFILE_EVENT_MULTIPLEX is not set CONFIG_HAVE_OPROFILE=y CONFIG_KPROBES=y CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y CONFIG_KRETPROBES=y CONFIG_HAVE_IOREMAP_PROT=y CONFIG_HAVE_KPROBES=y CONFIG_HAVE_KRETPROBES=y CONFIG_HAVE_ARCH_TRACEHOOK=y CONFIG_HAVE_DMA_ATTRS=y CONFIG_HAVE_DMA_API_DEBUG=y # # GCOV-based kernel profiling # # CONFIG_GCOV_KERNEL is not set CONFIG_SLOW_WORK=y # CONFIG_SLOW_WORK_DEBUG is not set # CONFIG_HAVE_GENERIC_DMA_COHERENT is not set CONFIG_SLABINFO=y CONFIG_RT_MUTEXES=y CONFIG_BASE_SMALL=0 CONFIG_MODULES=y # CONFIG_MODULE_FORCE_LOAD is not set CONFIG_MODULE_UNLOAD=y # CONFIG_MODULE_FORCE_UNLOAD is not set CONFIG_MODVERSIONS=y CONFIG_MODULE_SRCVERSION_ALL=y CONFIG_STOP_MACHINE=y CONFIG_BLOCK=y CONFIG_BLK_DEV_BSG=y CONFIG_BLK_DEV_INTEGRITY=y CONFIG_BLOCK_COMPAT=y # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y # CONFIG_DEFAULT_AS is not set CONFIG_DEFAULT_DEADLINE=y # CONFIG_DEFAULT_CFQ is not set # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="deadline" CONFIG_PREEMPT_NOTIFIERS=y CONFIG_FREEZER=y # # Processor type and features # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y CONFIG_GENERIC_CLOCKEVENTS_BUILD=y CONFIG_SMP=y CONFIG_SPARSE_IRQ=y CONFIG_NUMA_IRQ_DESC=y CONFIG_X86_MPPARSE=y CONFIG_X86_EXTENDED_PLATFORM=y # CONFIG_X86_VSMP is not set CONFIG_X86_SUPPORTS_MEMORY_FAILURE=y CONFIG_SCHED_OMIT_FRAME_POINTER=y CONFIG_PARAVIRT_GUEST=y CONFIG_XEN=y CONFIG_XEN_MAX_DOMAIN_MEMORY=32 CONFIG_XEN_SAVE_RESTORE=y # CONFIG_XEN_DEBUG_FS is not set CONFIG_SWIOTLB_XEN=y CONFIG_MICROCODE_XEN=y CONFIG_XEN_DOM0=y CONFIG_XEN_PRIVILEGED_GUEST=y CONFIG_XEN_DOM0_PCI=y CONFIG_XEN_PCI_PASSTHROUGH=y CONFIG_KVM_CLOCK=y CONFIG_KVM_GUEST=y CONFIG_PARAVIRT=y CONFIG_PARAVIRT_SPINLOCKS=y CONFIG_PARAVIRT_CLOCK=y # CONFIG_PARAVIRT_DEBUG is not set # CONFIG_MEMTEST is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MGEODEGX1 is not set # CONFIG_MGEODE_LX is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_MVIAC7 is not set # CONFIG_MPSC is not set # CONFIG_MCORE2 is not set # CONFIG_MATOM is not set CONFIG_GENERIC_CPU=y CONFIG_X86_CPU=y CONFIG_X86_L1_CACHE_BYTES=64 CONFIG_X86_INTERNODE_CACHE_BYTES=64 CONFIG_X86_CMPXCHG=y CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_X86_XADD=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_TSC=y CONFIG_X86_CMPXCHG64=y CONFIG_X86_CMOV=y CONFIG_X86_MINIMUM_CPU_FAMILY=64 CONFIG_X86_DEBUGCTLMSR=y CONFIG_CPU_SUP_INTEL=y CONFIG_CPU_SUP_AMD=y CONFIG_CPU_SUP_CENTAUR=y # CONFIG_X86_DS is not set CONFIG_HPET_TIMER=y CONFIG_HPET_EMULATE_RTC=y CONFIG_DMI=y CONFIG_GART_IOMMU=y CONFIG_CALGARY_IOMMU=y CONFIG_CALGARY_IOMMU_ENABLED_BY_DEFAULT=y CONFIG_AMD_IOMMU=y CONFIG_AMD_IOMMU_STATS=y CONFIG_SWIOTLB=y CONFIG_IOMMU_HELPER=y CONFIG_IOMMU_API=y # CONFIG_MAXSMP is not set CONFIG_NR_CPUS=64 CONFIG_SCHED_SMT=y CONFIG_SCHED_MC=y CONFIG_PREEMPT_NONE=y # CONFIG_PREEMPT_VOLUNTARY is not set # CONFIG_PREEMPT is not set CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS=y CONFIG_X86_MCE=y CONFIG_X86_MCE_INTEL=y CONFIG_X86_MCE_AMD=y CONFIG_X86_MCE_THRESHOLD=y CONFIG_X86_MCE_INJECT=m CONFIG_X86_THERMAL_VECTOR=y CONFIG_I8K=m CONFIG_MICROCODE=m CONFIG_MICROCODE_INTEL=y CONFIG_MICROCODE_AMD=y CONFIG_MICROCODE_OLD_INTERFACE=y CONFIG_X86_MSR=m CONFIG_X86_CPUID=m CONFIG_ARCH_PHYS_ADDR_T_64BIT=y CONFIG_DIRECT_GBPAGES=y CONFIG_NUMA=y CONFIG_K8_NUMA=y CONFIG_X86_64_ACPI_NUMA=y CONFIG_NODES_SPAN_OTHER_NODES=y # CONFIG_NUMA_EMU is not set CONFIG_NODES_SHIFT=6 CONFIG_ARCH_PROC_KCORE_TEXT=y CONFIG_ARCH_SPARSEMEM_DEFAULT=y CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_SELECT_MEMORY_MODEL=y CONFIG_ARCH_MEMORY_PROBE=y CONFIG_SELECT_MEMORY_MODEL=y # CONFIG_FLATMEM_MANUAL is not set # CONFIG_DISCONTIGMEM_MANUAL is not set CONFIG_SPARSEMEM_MANUAL=y CONFIG_SPARSEMEM=y CONFIG_NEED_MULTIPLE_NODES=y CONFIG_HAVE_MEMORY_PRESENT=y CONFIG_SPARSEMEM_EXTREME=y CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y CONFIG_SPARSEMEM_VMEMMAP=y CONFIG_MEMORY_HOTPLUG=y CONFIG_MEMORY_HOTPLUG_SPARSE=y CONFIG_MEMORY_HOTREMOVE=y CONFIG_PAGEFLAGS_EXTENDED=y CONFIG_SPLIT_PTLOCK_CPUS=4 CONFIG_MIGRATION=y CONFIG_PHYS_ADDR_T_64BIT=y CONFIG_ZONE_DMA_FLAG=1 CONFIG_BOUNCE=y CONFIG_VIRT_TO_BUS=y CONFIG_HAVE_MLOCK=y CONFIG_HAVE_MLOCKED_PAGE_BIT=y CONFIG_MMU_NOTIFIER=y CONFIG_KSM=y CONFIG_DEFAULT_MMAP_MIN_ADDR=65536 CONFIG_ARCH_SUPPORTS_MEMORY_FAILURE=y CONFIG_MEMORY_FAILURE=y # CONFIG_HWPOISON_INJECT is not set CONFIG_X86_CHECK_BIOS_CORRUPTION=y CONFIG_X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK=y CONFIG_X86_RESERVE_LOW_64K=y CONFIG_MTRR=y CONFIG_MTRR_SANITIZER=y CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=0 CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1 CONFIG_X86_PAT=y CONFIG_ARCH_USES_PG_UNCACHED=y CONFIG_EFI=y CONFIG_SECCOMP=y CONFIG_CC_STACKPROTECTOR=y CONFIG_HZ_100=y # CONFIG_HZ_250 is not set # CONFIG_HZ_300 is not set # CONFIG_HZ_1000 is not set CONFIG_HZ=100 CONFIG_SCHED_HRTICK=y CONFIG_KEXEC=y CONFIG_CRASH_DUMP=y CONFIG_KEXEC_JUMP=y CONFIG_PHYSICAL_START=0x200000 CONFIG_RELOCATABLE=y CONFIG_PHYSICAL_ALIGN=0x1000000 CONFIG_HOTPLUG_CPU=y # CONFIG_COMPAT_VDSO is not set # CONFIG_CMDLINE_BOOL is not set CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y CONFIG_ARCH_ENABLE_MEMORY_HOTREMOVE=y CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID=y # # Power management and ACPI options # CONFIG_ARCH_HIBERNATION_HEADER=y CONFIG_PM=y CONFIG_PM_DEBUG=y # CONFIG_PM_VERBOSE is not set CONFIG_CAN_PM_TRACE=y CONFIG_PM_TRACE=y CONFIG_PM_TRACE_RTC=y CONFIG_PM_SLEEP_SMP=y CONFIG_PM_SLEEP=y CONFIG_SUSPEND=y CONFIG_PM_TEST_SUSPEND=y CONFIG_SUSPEND_FREEZER=y CONFIG_HIBERNATION_NVS=y CONFIG_HIBERNATION=y CONFIG_PM_STD_PARTITION="" CONFIG_PM_RUNTIME=y CONFIG_ACPI=y CONFIG_ACPI_SLEEP=y CONFIG_ACPI_PROCFS=y CONFIG_ACPI_PROCFS_POWER=y CONFIG_ACPI_POWER_METER=m CONFIG_ACPI_SYSFS_POWER=y CONFIG_ACPI_PROC_EVENT=y CONFIG_ACPI_AC=y CONFIG_ACPI_BATTERY=y CONFIG_ACPI_BUTTON=y CONFIG_ACPI_VIDEO=m CONFIG_ACPI_FAN=y CONFIG_ACPI_DOCK=y CONFIG_ACPI_PROCESSOR=y CONFIG_ACPI_HOTPLUG_CPU=y CONFIG_ACPI_PROCESSOR_AGGREGATOR=m CONFIG_ACPI_THERMAL=y CONFIG_ACPI_NUMA=y CONFIG_ACPI_CUSTOM_DSDT_FILE="" # CONFIG_ACPI_CUSTOM_DSDT is not set CONFIG_ACPI_BLACKLIST_YEAR=0 # CONFIG_ACPI_DEBUG is not set CONFIG_ACPI_PCI_SLOT=y CONFIG_X86_PM_TIMER=y CONFIG_ACPI_CONTAINER=y CONFIG_ACPI_HOTPLUG_MEMORY=m CONFIG_ACPI_SBS=y CONFIG_SFI=y # # CPU Frequency scaling # CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_TABLE=y # CONFIG_CPU_FREQ_DEBUG is not set CONFIG_CPU_FREQ_STAT=y CONFIG_CPU_FREQ_STAT_DETAILS=y CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y # CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set CONFIG_CPU_FREQ_GOV_PERFORMANCE=y CONFIG_CPU_FREQ_GOV_POWERSAVE=y CONFIG_CPU_FREQ_GOV_USERSPACE=y CONFIG_CPU_FREQ_GOV_ONDEMAND=y CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y # # CPUFreq processor drivers # CONFIG_X86_ACPI_CPUFREQ=y CONFIG_X86_POWERNOW_K8=y CONFIG_X86_SPEEDSTEP_CENTRINO=y CONFIG_X86_P4_CLOCKMOD=m # # shared options # CONFIG_X86_SPEEDSTEP_LIB=m CONFIG_CPU_IDLE=y CONFIG_CPU_IDLE_GOV_LADDER=y CONFIG_CPU_IDLE_GOV_MENU=y # # Memory power savings # CONFIG_I7300_IDLE_IOAT_CHANNEL=y CONFIG_I7300_IDLE=m # # Bus options (PCI etc.) # CONFIG_PCI=y CONFIG_PCI_DIRECT=y CONFIG_PCI_MMCONFIG=y CONFIG_PCI_XEN=y CONFIG_PCI_DOMAINS=y # CONFIG_DMAR is not set # CONFIG_INTR_REMAP is not set CONFIG_PCIEPORTBUS=y CONFIG_HOTPLUG_PCI_PCIE=y CONFIG_PCIEAER=y # CONFIG_PCIE_ECRC is not set # CONFIG_PCIEAER_INJECT is not set # CONFIG_PCIEASPM is not set CONFIG_ARCH_SUPPORTS_MSI=y CONFIG_PCI_MSI=y CONFIG_PCI_LEGACY=y # CONFIG_PCI_DEBUG is not set CONFIG_PCI_STUB=m CONFIG_XEN_PCIDEV_FRONTEND=y CONFIG_HT_IRQ=y CONFIG_PCI_IOV=y CONFIG_ISA_DMA_API=y CONFIG_K8_NB=y CONFIG_PCCARD=m # CONFIG_PCMCIA_DEBUG is not set CONFIG_PCMCIA=m CONFIG_PCMCIA_LOAD_CIS=y CONFIG_PCMCIA_IOCTL=y CONFIG_CARDBUS=y # # PC-card bridges # CONFIG_YENTA=m CONFIG_YENTA_O2=y CONFIG_YENTA_RICOH=y CONFIG_YENTA_TI=y CONFIG_YENTA_ENE_TUNE=y CONFIG_YENTA_TOSHIBA=y CONFIG_PD6729=m CONFIG_I82092=m CONFIG_PCCARD_NONSTATIC=m CONFIG_HOTPLUG_PCI=y CONFIG_HOTPLUG_PCI_FAKE=m CONFIG_HOTPLUG_PCI_ACPI=m CONFIG_HOTPLUG_PCI_ACPI_IBM=m CONFIG_HOTPLUG_PCI_CPCI=y CONFIG_HOTPLUG_PCI_CPCI_ZT5550=m CONFIG_HOTPLUG_PCI_CPCI_GENERIC=m CONFIG_HOTPLUG_PCI_SHPC=m # # Executable file formats / Emulations # CONFIG_BINFMT_ELF=y CONFIG_COMPAT_BINFMT_ELF=y # CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set # CONFIG_HAVE_AOUT is not set CONFIG_BINFMT_MISC=m CONFIG_IA32_EMULATION=y # CONFIG_IA32_AOUT is not set CONFIG_COMPAT=y CONFIG_COMPAT_FOR_U64_ALIGNMENT=y CONFIG_SYSVIPC_COMPAT=y CONFIG_NET=y CONFIG_COMPAT_NETLINK_MESSAGES=y # # Networking options # CONFIG_PACKET=y CONFIG_PACKET_MMAP=y CONFIG_UNIX=y CONFIG_XFRM=y CONFIG_XFRM_USER=m # CONFIG_XFRM_SUB_POLICY is not set # CONFIG_XFRM_MIGRATE is not set # CONFIG_XFRM_STATISTICS is not set CONFIG_XFRM_IPCOMP=m CONFIG_NET_KEY=m # CONFIG_NET_KEY_MIGRATE is not set CONFIG_INET=y CONFIG_IP_MULTICAST=y CONFIG_IP_ADVANCED_ROUTER=y CONFIG_ASK_IP_FIB_HASH=y # CONFIG_IP_FIB_TRIE is not set CONFIG_IP_FIB_HASH=y CONFIG_IP_MULTIPLE_TABLES=y CONFIG_IP_ROUTE_MULTIPATH=y CONFIG_IP_ROUTE_VERBOSE=y # CONFIG_IP_PNP is not set CONFIG_NET_IPIP=m CONFIG_NET_IPGRE=m CONFIG_NET_IPGRE_BROADCAST=y CONFIG_IP_MROUTE=y CONFIG_IP_PIMSM_V1=y CONFIG_IP_PIMSM_V2=y # CONFIG_ARPD is not set CONFIG_SYN_COOKIES=y CONFIG_INET_AH=m CONFIG_INET_ESP=m CONFIG_INET_IPCOMP=m CONFIG_INET_XFRM_TUNNEL=m CONFIG_INET_TUNNEL=m CONFIG_INET_XFRM_MODE_TRANSPORT=m CONFIG_INET_XFRM_MODE_TUNNEL=m CONFIG_INET_XFRM_MODE_BEET=m CONFIG_INET_LRO=y CONFIG_INET_DIAG=y CONFIG_INET_TCP_DIAG=y CONFIG_TCP_CONG_ADVANCED=y CONFIG_TCP_CONG_BIC=m CONFIG_TCP_CONG_CUBIC=y CONFIG_TCP_CONG_WESTWOOD=m CONFIG_TCP_CONG_HTCP=m CONFIG_TCP_CONG_HSTCP=m CONFIG_TCP_CONG_HYBLA=m CONFIG_TCP_CONG_VEGAS=m CONFIG_TCP_CONG_SCALABLE=m CONFIG_TCP_CONG_LP=m CONFIG_TCP_CONG_VENO=m CONFIG_TCP_CONG_YEAH=m CONFIG_TCP_CONG_ILLINOIS=m # CONFIG_DEFAULT_BIC is not set CONFIG_DEFAULT_CUBIC=y # CONFIG_DEFAULT_HTCP is not set # CONFIG_DEFAULT_VEGAS is not set # CONFIG_DEFAULT_WESTWOOD is not set # CONFIG_DEFAULT_RENO is not set CONFIG_DEFAULT_TCP_CONG="cubic" CONFIG_TCP_MD5SIG=y CONFIG_IPV6=y CONFIG_IPV6_PRIVACY=y # CONFIG_IPV6_ROUTER_PREF is not set # CONFIG_IPV6_OPTIMISTIC_DAD is not set CONFIG_INET6_AH=m CONFIG_INET6_ESP=m CONFIG_INET6_IPCOMP=m # CONFIG_IPV6_MIP6 is not set CONFIG_INET6_XFRM_TUNNEL=m CONFIG_INET6_TUNNEL=m CONFIG_INET6_XFRM_MODE_TRANSPORT=m CONFIG_INET6_XFRM_MODE_TUNNEL=m CONFIG_INET6_XFRM_MODE_BEET=m CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION=m CONFIG_IPV6_SIT=m CONFIG_IPV6_NDISC_NODETYPE=y CONFIG_IPV6_TUNNEL=m CONFIG_IPV6_MULTIPLE_TABLES=y # CONFIG_IPV6_SUBTREES is not set # CONFIG_IPV6_MROUTE is not set CONFIG_NETLABEL=y CONFIG_NETWORK_SECMARK=y CONFIG_NETFILTER=y # CONFIG_NETFILTER_DEBUG is not set CONFIG_NETFILTER_ADVANCED=y CONFIG_BRIDGE_NETFILTER=y # # Core Netfilter Configuration # CONFIG_NETFILTER_NETLINK=m CONFIG_NETFILTER_NETLINK_QUEUE=m CONFIG_NETFILTER_NETLINK_LOG=m CONFIG_NF_CONNTRACK=m CONFIG_NF_CT_ACCT=y CONFIG_NF_CONNTRACK_MARK=y CONFIG_NF_CONNTRACK_SECMARK=y CONFIG_NF_CONNTRACK_EVENTS=y CONFIG_NF_CT_PROTO_DCCP=m CONFIG_NF_CT_PROTO_GRE=m CONFIG_NF_CT_PROTO_SCTP=m CONFIG_NF_CT_PROTO_UDPLITE=m CONFIG_NF_CONNTRACK_AMANDA=m CONFIG_NF_CONNTRACK_FTP=m CONFIG_NF_CONNTRACK_H323=m CONFIG_NF_CONNTRACK_IRC=m CONFIG_NF_CONNTRACK_NETBIOS_NS=m CONFIG_NF_CONNTRACK_PPTP=m CONFIG_NF_CONNTRACK_SANE=m CONFIG_NF_CONNTRACK_SIP=m CONFIG_NF_CONNTRACK_TFTP=m CONFIG_NF_CT_NETLINK=m CONFIG_NETFILTER_TPROXY=m CONFIG_NETFILTER_XTABLES=m CONFIG_NETFILTER_XT_TARGET_CLASSIFY=m CONFIG_NETFILTER_XT_TARGET_CONNMARK=m CONFIG_NETFILTER_XT_TARGET_CONNSECMARK=m CONFIG_NETFILTER_XT_TARGET_DSCP=m CONFIG_NETFILTER_XT_TARGET_HL=m CONFIG_NETFILTER_XT_TARGET_LED=m CONFIG_NETFILTER_XT_TARGET_MARK=m CONFIG_NETFILTER_XT_TARGET_NFLOG=m CONFIG_NETFILTER_XT_TARGET_NFQUEUE=m CONFIG_NETFILTER_XT_TARGET_NOTRACK=m CONFIG_NETFILTER_XT_TARGET_RATEEST=m CONFIG_NETFILTER_XT_TARGET_TPROXY=m CONFIG_NETFILTER_XT_TARGET_TRACE=m CONFIG_NETFILTER_XT_TARGET_SECMARK=m CONFIG_NETFILTER_XT_TARGET_TCPMSS=m # CONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP is not set CONFIG_NETFILTER_XT_MATCH_CLUSTER=m CONFIG_NETFILTER_XT_MATCH_COMMENT=m CONFIG_NETFILTER_XT_MATCH_CONNBYTES=m CONFIG_NETFILTER_XT_MATCH_CONNLIMIT=m CONFIG_NETFILTER_XT_MATCH_CONNMARK=m CONFIG_NETFILTER_XT_MATCH_CONNTRACK=m CONFIG_NETFILTER_XT_MATCH_DCCP=m CONFIG_NETFILTER_XT_MATCH_DSCP=m CONFIG_NETFILTER_XT_MATCH_ESP=m CONFIG_NETFILTER_XT_MATCH_HASHLIMIT=m CONFIG_NETFILTER_XT_MATCH_HELPER=m CONFIG_NETFILTER_XT_MATCH_HL=m CONFIG_NETFILTER_XT_MATCH_IPRANGE=m CONFIG_NETFILTER_XT_MATCH_LENGTH=m CONFIG_NETFILTER_XT_MATCH_LIMIT=m CONFIG_NETFILTER_XT_MATCH_MAC=m CONFIG_NETFILTER_XT_MATCH_MARK=m CONFIG_NETFILTER_XT_MATCH_MULTIPORT=m CONFIG_NETFILTER_XT_MATCH_OWNER=m CONFIG_NETFILTER_XT_MATCH_POLICY=m CONFIG_NETFILTER_XT_MATCH_PHYSDEV=m CONFIG_NETFILTER_XT_MATCH_PKTTYPE=m CONFIG_NETFILTER_XT_MATCH_QUOTA=m CONFIG_NETFILTER_XT_MATCH_RATEEST=m CONFIG_NETFILTER_XT_MATCH_REALM=m CONFIG_NETFILTER_XT_MATCH_RECENT=m # CONFIG_NETFILTER_XT_MATCH_RECENT_PROC_COMPAT is not set CONFIG_NETFILTER_XT_MATCH_SCTP=m CONFIG_NETFILTER_XT_MATCH_SOCKET=m CONFIG_NETFILTER_XT_MATCH_STATE=m CONFIG_NETFILTER_XT_MATCH_STATISTIC=m CONFIG_NETFILTER_XT_MATCH_STRING=m CONFIG_NETFILTER_XT_MATCH_TCPMSS=m CONFIG_NETFILTER_XT_MATCH_TIME=m CONFIG_NETFILTER_XT_MATCH_U32=m CONFIG_NETFILTER_XT_MATCH_OSF=m CONFIG_IP_VS=m CONFIG_IP_VS_IPV6=y # CONFIG_IP_VS_DEBUG is not set CONFIG_IP_VS_TAB_BITS=12 # # IPVS transport protocol load balancing support # CONFIG_IP_VS_PROTO_TCP=y CONFIG_IP_VS_PROTO_UDP=y CONFIG_IP_VS_PROTO_AH_ESP=y CONFIG_IP_VS_PROTO_ESP=y CONFIG_IP_VS_PROTO_AH=y # # IPVS scheduler # CONFIG_IP_VS_RR=m CONFIG_IP_VS_WRR=m CONFIG_IP_VS_LC=m CONFIG_IP_VS_WLC=m CONFIG_IP_VS_LBLC=m CONFIG_IP_VS_LBLCR=m CONFIG_IP_VS_DH=m CONFIG_IP_VS_SH=m CONFIG_IP_VS_SED=m CONFIG_IP_VS_NQ=m # # IPVS application helper # CONFIG_IP_VS_FTP=m # # IP: Netfilter Configuration # CONFIG_NF_DEFRAG_IPV4=m CONFIG_NF_CONNTRACK_IPV4=m CONFIG_NF_CONNTRACK_PROC_COMPAT=y CONFIG_IP_NF_QUEUE=m CONFIG_IP_NF_IPTABLES=m CONFIG_IP_NF_MATCH_ADDRTYPE=m CONFIG_IP_NF_MATCH_AH=m CONFIG_IP_NF_MATCH_ECN=m CONFIG_IP_NF_MATCH_TTL=m CONFIG_IP_NF_FILTER=m CONFIG_IP_NF_TARGET_REJECT=m CONFIG_IP_NF_TARGET_LOG=m CONFIG_IP_NF_TARGET_ULOG=m CONFIG_NF_NAT=m CONFIG_NF_NAT_NEEDED=y CONFIG_IP_NF_TARGET_MASQUERADE=m CONFIG_IP_NF_TARGET_NETMAP=m CONFIG_IP_NF_TARGET_REDIRECT=m CONFIG_NF_NAT_SNMP_BASIC=m CONFIG_NF_NAT_PROTO_DCCP=m CONFIG_NF_NAT_PROTO_GRE=m CONFIG_NF_NAT_PROTO_UDPLITE=m CONFIG_NF_NAT_PROTO_SCTP=m CONFIG_NF_NAT_FTP=m CONFIG_NF_NAT_IRC=m CONFIG_NF_NAT_TFTP=m CONFIG_NF_NAT_AMANDA=m CONFIG_NF_NAT_PPTP=m CONFIG_NF_NAT_H323=m CONFIG_NF_NAT_SIP=m CONFIG_IP_NF_MANGLE=m CONFIG_IP_NF_TARGET_CLUSTERIP=m CONFIG_IP_NF_TARGET_ECN=m CONFIG_IP_NF_TARGET_TTL=m CONFIG_IP_NF_RAW=m CONFIG_IP_NF_SECURITY=m CONFIG_IP_NF_ARPTABLES=m CONFIG_IP_NF_ARPFILTER=m CONFIG_IP_NF_ARP_MANGLE=m # # IPv6: Netfilter Configuration # CONFIG_NF_CONNTRACK_IPV6=m CONFIG_IP6_NF_QUEUE=m CONFIG_IP6_NF_IPTABLES=m CONFIG_IP6_NF_MATCH_AH=m CONFIG_IP6_NF_MATCH_EUI64=m CONFIG_IP6_NF_MATCH_FRAG=m CONFIG_IP6_NF_MATCH_OPTS=m CONFIG_IP6_NF_MATCH_HL=m CONFIG_IP6_NF_MATCH_IPV6HEADER=m CONFIG_IP6_NF_MATCH_MH=m CONFIG_IP6_NF_MATCH_RT=m CONFIG_IP6_NF_TARGET_HL=m CONFIG_IP6_NF_TARGET_LOG=m CONFIG_IP6_NF_FILTER=m CONFIG_IP6_NF_TARGET_REJECT=m CONFIG_IP6_NF_MANGLE=m CONFIG_IP6_NF_RAW=m CONFIG_IP6_NF_SECURITY=m # # DECnet: Netfilter Configuration # CONFIG_DECNET_NF_GRABULATOR=m CONFIG_BRIDGE_NF_EBTABLES=m CONFIG_BRIDGE_EBT_BROUTE=m CONFIG_BRIDGE_EBT_T_FILTER=m CONFIG_BRIDGE_EBT_T_NAT=m CONFIG_BRIDGE_EBT_802_3=m CONFIG_BRIDGE_EBT_AMONG=m CONFIG_BRIDGE_EBT_ARP=m CONFIG_BRIDGE_EBT_IP=m CONFIG_BRIDGE_EBT_IP6=m CONFIG_BRIDGE_EBT_LIMIT=m CONFIG_BRIDGE_EBT_MARK=m CONFIG_BRIDGE_EBT_PKTTYPE=m CONFIG_BRIDGE_EBT_STP=m CONFIG_BRIDGE_EBT_VLAN=m CONFIG_BRIDGE_EBT_ARPREPLY=m CONFIG_BRIDGE_EBT_DNAT=m CONFIG_BRIDGE_EBT_MARK_T=m CONFIG_BRIDGE_EBT_REDIRECT=m CONFIG_BRIDGE_EBT_SNAT=m CONFIG_BRIDGE_EBT_LOG=m CONFIG_BRIDGE_EBT_ULOG=m CONFIG_BRIDGE_EBT_NFLOG=m CONFIG_IP_DCCP=m CONFIG_INET_DCCP_DIAG=m # # DCCP CCIDs Configuration (EXPERIMENTAL) # # CONFIG_IP_DCCP_CCID2_DEBUG is not set CONFIG_IP_DCCP_CCID3=y # CONFIG_IP_DCCP_CCID3_DEBUG is not set CONFIG_IP_DCCP_CCID3_RTO=100 CONFIG_IP_DCCP_TFRC_LIB=y # # DCCP Kernel Hacking # # CONFIG_IP_DCCP_DEBUG is not set CONFIG_NET_DCCPPROBE=m CONFIG_IP_SCTP=m # CONFIG_SCTP_DBG_MSG is not set # CONFIG_SCTP_DBG_OBJCNT is not set # CONFIG_SCTP_HMAC_NONE is not set # CONFIG_SCTP_HMAC_SHA1 is not set CONFIG_SCTP_HMAC_MD5=y CONFIG_RDS=m CONFIG_RDS_RDMA=m CONFIG_RDS_TCP=m # CONFIG_RDS_DEBUG is not set CONFIG_TIPC=m # CONFIG_TIPC_ADVANCED is not set # CONFIG_TIPC_DEBUG is not set CONFIG_ATM=m CONFIG_ATM_CLIP=m # CONFIG_ATM_CLIP_NO_ICMP is not set CONFIG_ATM_LANE=m CONFIG_ATM_MPOA=m CONFIG_ATM_BR2684=m # CONFIG_ATM_BR2684_IPFILTER is not set CONFIG_STP=m CONFIG_GARP=m CONFIG_BRIDGE=m CONFIG_NET_DSA=y CONFIG_NET_DSA_TAG_DSA=y CONFIG_NET_DSA_TAG_EDSA=y CONFIG_NET_DSA_TAG_TRAILER=y CONFIG_NET_DSA_MV88E6XXX=y CONFIG_NET_DSA_MV88E6060=y CONFIG_NET_DSA_MV88E6XXX_NEED_PPU=y CONFIG_NET_DSA_MV88E6131=y CONFIG_NET_DSA_MV88E6123_61_65=y CONFIG_VLAN_8021Q=m CONFIG_VLAN_8021Q_GVRP=y CONFIG_DECNET=m # CONFIG_DECNET_ROUTER is not set CONFIG_LLC=y CONFIG_LLC2=m CONFIG_IPX=m # CONFIG_IPX_INTERN is not set CONFIG_ATALK=m CONFIG_DEV_APPLETALK=m CONFIG_IPDDP=m CONFIG_IPDDP_ENCAP=y CONFIG_IPDDP_DECAP=y CONFIG_X25=m CONFIG_LAPB=m CONFIG_ECONET=m CONFIG_ECONET_AUNUDP=y CONFIG_ECONET_NATIVE=y CONFIG_WAN_ROUTER=m CONFIG_PHONET=m CONFIG_IEEE802154=m CONFIG_NET_SCHED=y # # Queueing/Scheduling # CONFIG_NET_SCH_CBQ=m CONFIG_NET_SCH_HTB=m CONFIG_NET_SCH_HFSC=m CONFIG_NET_SCH_ATM=m CONFIG_NET_SCH_PRIO=m CONFIG_NET_SCH_MULTIQ=m CONFIG_NET_SCH_RED=m CONFIG_NET_SCH_SFQ=m CONFIG_NET_SCH_TEQL=m CONFIG_NET_SCH_TBF=m CONFIG_NET_SCH_GRED=m CONFIG_NET_SCH_DSMARK=m CONFIG_NET_SCH_NETEM=m CONFIG_NET_SCH_DRR=m CONFIG_NET_SCH_INGRESS=m # # Classification # CONFIG_NET_CLS=y CONFIG_NET_CLS_BASIC=m CONFIG_NET_CLS_TCINDEX=m CONFIG_NET_CLS_ROUTE4=m CONFIG_NET_CLS_ROUTE=y CONFIG_NET_CLS_FW=m CONFIG_NET_CLS_U32=m # CONFIG_CLS_U32_PERF is not set CONFIG_CLS_U32_MARK=y CONFIG_NET_CLS_RSVP=m CONFIG_NET_CLS_RSVP6=m CONFIG_NET_CLS_FLOW=m CONFIG_NET_CLS_CGROUP=y CONFIG_NET_EMATCH=y CONFIG_NET_EMATCH_STACK=32 CONFIG_NET_EMATCH_CMP=m CONFIG_NET_EMATCH_NBYTE=m CONFIG_NET_EMATCH_U32=m CONFIG_NET_EMATCH_META=m CONFIG_NET_EMATCH_TEXT=m CONFIG_NET_CLS_ACT=y CONFIG_NET_ACT_POLICE=m CONFIG_NET_ACT_GACT=m CONFIG_GACT_PROB=y CONFIG_NET_ACT_MIRRED=m CONFIG_NET_ACT_IPT=m CONFIG_NET_ACT_NAT=m CONFIG_NET_ACT_PEDIT=m CONFIG_NET_ACT_SIMP=m CONFIG_NET_ACT_SKBEDIT=m # CONFIG_NET_CLS_IND is not set CONFIG_NET_SCH_FIFO=y CONFIG_DCB=y # # Network testing # CONFIG_NET_PKTGEN=m CONFIG_NET_TCPPROBE=m # CONFIG_NET_DROP_MONITOR is not set CONFIG_HAMRADIO=y # # Packet Radio protocols # CONFIG_AX25=m CONFIG_AX25_DAMA_SLAVE=y CONFIG_NETROM=m CONFIG_ROSE=m # # AX.25 network device drivers # CONFIG_MKISS=m CONFIG_6PACK=m CONFIG_BPQETHER=m CONFIG_BAYCOM_SER_FDX=m CONFIG_BAYCOM_SER_HDX=m CONFIG_BAYCOM_PAR=m CONFIG_YAM=m CONFIG_CAN=m CONFIG_CAN_RAW=m CONFIG_CAN_BCM=m # # CAN Device Drivers # CONFIG_CAN_VCAN=m CONFIG_CAN_DEV=m # CONFIG_CAN_CALC_BITTIMING is not set CONFIG_CAN_SJA1000=m CONFIG_CAN_SJA1000_PLATFORM=m CONFIG_CAN_EMS_PCI=m CONFIG_CAN_KVASER_PCI=m # # CAN USB interfaces # CONFIG_CAN_EMS_USB=m # CONFIG_CAN_DEBUG_DEVICES is not set CONFIG_IRDA=m # # IrDA protocols # CONFIG_IRLAN=m CONFIG_IRNET=m CONFIG_IRCOMM=m CONFIG_IRDA_ULTRA=y # # IrDA options # CONFIG_IRDA_CACHE_LAST_LSAP=y CONFIG_IRDA_FAST_RR=y CONFIG_IRDA_DEBUG=y # # Infrared-port device drivers # # # SIR device drivers # CONFIG_IRTTY_SIR=m # # Dongle support # CONFIG_DONGLE=y CONFIG_ESI_DONGLE=m CONFIG_ACTISYS_DONGLE=m CONFIG_TEKRAM_DONGLE=m CONFIG_TOIM3232_DONGLE=m CONFIG_LITELINK_DONGLE=m CONFIG_MA600_DONGLE=m CONFIG_GIRBIL_DONGLE=m CONFIG_MCP2120_DONGLE=m CONFIG_OLD_BELKIN_DONGLE=m CONFIG_ACT200L_DONGLE=m CONFIG_KINGSUN_DONGLE=m CONFIG_KSDAZZLE_DONGLE=m CONFIG_KS959_DONGLE=m # # FIR device drivers # CONFIG_USB_IRDA=m CONFIG_SIGMATEL_FIR=m CONFIG_NSC_FIR=m CONFIG_WINBOND_FIR=m CONFIG_SMC_IRCC_FIR=m CONFIG_ALI_FIR=m CONFIG_VLSI_FIR=m CONFIG_VIA_FIR=m CONFIG_MCS_FIR=m CONFIG_BT=m CONFIG_BT_L2CAP=m CONFIG_BT_SCO=m CONFIG_BT_RFCOMM=m CONFIG_BT_RFCOMM_TTY=y CONFIG_BT_BNEP=m CONFIG_BT_BNEP_MC_FILTER=y CONFIG_BT_BNEP_PROTO_FILTER=y CONFIG_BT_CMTP=m CONFIG_BT_HIDP=m # # Bluetooth device drivers # CONFIG_BT_HCIBTUSB=m CONFIG_BT_HCIBTSDIO=m CONFIG_BT_HCIUART=m CONFIG_BT_HCIUART_H4=y CONFIG_BT_HCIUART_BCSP=y CONFIG_BT_HCIUART_LL=y CONFIG_BT_HCIBCM203X=m CONFIG_BT_HCIBPA10X=m CONFIG_BT_HCIBFUSB=m CONFIG_BT_HCIDTL1=m CONFIG_BT_HCIBT3C=m CONFIG_BT_HCIBLUECARD=m CONFIG_BT_HCIBTUART=m CONFIG_BT_HCIVHCI=m CONFIG_BT_MRVL=m CONFIG_BT_MRVL_SDIO=m CONFIG_AF_RXRPC=m # CONFIG_AF_RXRPC_DEBUG is not set CONFIG_RXKAD=m CONFIG_FIB_RULES=y CONFIG_WIRELESS=y CONFIG_CFG80211=m CONFIG_NL80211_TESTMODE=y # CONFIG_CFG80211_DEVELOPER_WARNINGS is not set CONFIG_CFG80211_REG_DEBUG=y CONFIG_CFG80211_DEFAULT_PS=y CONFIG_CFG80211_DEFAULT_PS_VALUE=1 CONFIG_CFG80211_DEBUGFS=y # CONFIG_WIRELESS_OLD_REGULATORY is not set CONFIG_WIRELESS_EXT=y CONFIG_WIRELESS_EXT_SYSFS=y CONFIG_LIB80211=m CONFIG_LIB80211_CRYPT_WEP=m CONFIG_LIB80211_CRYPT_CCMP=m CONFIG_LIB80211_CRYPT_TKIP=m # CONFIG_LIB80211_DEBUG is not set CONFIG_MAC80211=m CONFIG_MAC80211_RC_MINSTREL=y # CONFIG_MAC80211_RC_DEFAULT_PID is not set CONFIG_MAC80211_RC_DEFAULT_MINSTREL=y CONFIG_MAC80211_RC_DEFAULT="minstrel" CONFIG_MAC80211_MESH=y CONFIG_MAC80211_LEDS=y CONFIG_MAC80211_DEBUGFS=y # CONFIG_MAC80211_DEBUG_MENU is not set CONFIG_WIMAX=m CONFIG_WIMAX_DEBUG_LEVEL=8 CONFIG_RFKILL=y CONFIG_RFKILL_LEDS=y CONFIG_RFKILL_INPUT=y CONFIG_NET_9P=m CONFIG_NET_9P_VIRTIO=m CONFIG_NET_9P_RDMA=m # CONFIG_NET_9P_DEBUG is not set # # Device Drivers # # # Generic Driver Options # CONFIG_UEVENT_HELPER_PATH="" CONFIG_DEVTMPFS=y CONFIG_DEVTMPFS_MOUNT=y # CONFIG_STANDALONE is not set CONFIG_PREVENT_FIRMWARE_BUILD=y CONFIG_FW_LOADER=y CONFIG_FIRMWARE_IN_KERNEL=y CONFIG_EXTRA_FIRMWARE="" # CONFIG_DEBUG_DRIVER is not set # CONFIG_DEBUG_DEVRES is not set CONFIG_SYS_HYPERVISOR=y CONFIG_CONNECTOR=y CONFIG_PROC_EVENTS=y CONFIG_MTD=m # CONFIG_MTD_DEBUG is not set CONFIG_MTD_TESTS=m CONFIG_MTD_CONCAT=m CONFIG_MTD_PARTITIONS=y CONFIG_MTD_REDBOOT_PARTS=m CONFIG_MTD_REDBOOT_DIRECTORY_BLOCK=-1 # CONFIG_MTD_REDBOOT_PARTS_UNALLOCATED is not set # CONFIG_MTD_REDBOOT_PARTS_READONLY is not set CONFIG_MTD_AR7_PARTS=m # # User Modules And Translation Layers # CONFIG_MTD_CHAR=m CONFIG_HAVE_MTD_OTP=y CONFIG_MTD_BLKDEVS=m CONFIG_MTD_BLOCK=m CONFIG_MTD_BLOCK_RO=m CONFIG_FTL=m CONFIG_NFTL=m CONFIG_NFTL_RW=y CONFIG_INFTL=m CONFIG_RFD_FTL=m CONFIG_SSFDC=m CONFIG_MTD_OOPS=m # # RAM/ROM/Flash chip drivers # CONFIG_MTD_CFI=m CONFIG_MTD_JEDECPROBE=m CONFIG_MTD_GEN_PROBE=m # CONFIG_MTD_CFI_ADV_OPTIONS is not set CONFIG_MTD_MAP_BANK_WIDTH_1=y CONFIG_MTD_MAP_BANK_WIDTH_2=y CONFIG_MTD_MAP_BANK_WIDTH_4=y # CONFIG_MTD_MAP_BANK_WIDTH_8 is not set # CONFIG_MTD_MAP_BANK_WIDTH_16 is not set # CONFIG_MTD_MAP_BANK_WIDTH_32 is not set CONFIG_MTD_CFI_I1=y CONFIG_MTD_CFI_I2=y # CONFIG_MTD_CFI_I4 is not set # CONFIG_MTD_CFI_I8 is not set CONFIG_MTD_CFI_INTELEXT=m CONFIG_MTD_CFI_AMDSTD=m CONFIG_MTD_CFI_STAA=m CONFIG_MTD_CFI_UTIL=m CONFIG_MTD_RAM=m CONFIG_MTD_ROM=m CONFIG_MTD_ABSENT=m # # Mapping drivers for chip access # CONFIG_MTD_COMPLEX_MAPPINGS=y CONFIG_MTD_PHYSMAP=m # CONFIG_MTD_PHYSMAP_COMPAT is not set CONFIG_MTD_SC520CDP=m CONFIG_MTD_NETSC520=m CONFIG_MTD_TS5500=m CONFIG_MTD_SBC_GXX=m CONFIG_MTD_AMD76XROM=m CONFIG_MTD_ICHXROM=m CONFIG_MTD_ESB2ROM=m CONFIG_MTD_CK804XROM=m CONFIG_MTD_SCB2_FLASH=m CONFIG_MTD_NETtel=m CONFIG_MTD_L440GX=m CONFIG_MTD_PCI=m CONFIG_MTD_GPIO_ADDR=m CONFIG_MTD_INTEL_VR_NOR=m CONFIG_MTD_PLATRAM=m # # Self-contained MTD device drivers # CONFIG_MTD_PMC551=m # CONFIG_MTD_PMC551_BUGFIX is not set # CONFIG_MTD_PMC551_DEBUG is not set CONFIG_MTD_DATAFLASH=m # CONFIG_MTD_DATAFLASH_WRITE_VERIFY is not set CONFIG_MTD_DATAFLASH_OTP=y CONFIG_MTD_M25P80=m CONFIG_M25PXX_USE_FAST_READ=y CONFIG_MTD_SST25L=m CONFIG_MTD_SLRAM=m CONFIG_MTD_PHRAM=m CONFIG_MTD_MTDRAM=m CONFIG_MTDRAM_TOTAL_SIZE=4096 CONFIG_MTDRAM_ERASE_SIZE=128 CONFIG_MTD_BLOCK2MTD=m # # Disk-On-Chip Device Drivers # CONFIG_MTD_DOC2000=m CONFIG_MTD_DOC2001=m CONFIG_MTD_DOC2001PLUS=m CONFIG_MTD_DOCPROBE=m CONFIG_MTD_DOCECC=m # CONFIG_MTD_DOCPROBE_ADVANCED is not set CONFIG_MTD_DOCPROBE_ADDRESS=0 CONFIG_MTD_NAND=m # CONFIG_MTD_NAND_VERIFY_WRITE is not set # CONFIG_MTD_NAND_ECC_SMC is not set # CONFIG_MTD_NAND_MUSEUM_IDS is not set CONFIG_MTD_NAND_IDS=m CONFIG_MTD_NAND_DISKONCHIP=m # CONFIG_MTD_NAND_DISKONCHIP_PROBE_ADVANCED is not set CONFIG_MTD_NAND_DISKONCHIP_PROBE_ADDRESS=0 # CONFIG_MTD_NAND_DISKONCHIP_BBTWRITE is not set CONFIG_MTD_NAND_CAFE=m CONFIG_MTD_NAND_NANDSIM=m CONFIG_MTD_NAND_PLATFORM=m CONFIG_MTD_ALAUDA=m CONFIG_MTD_ONENAND=m CONFIG_MTD_ONENAND_VERIFY_WRITE=y CONFIG_MTD_ONENAND_GENERIC=m # CONFIG_MTD_ONENAND_OTP is not set CONFIG_MTD_ONENAND_2X_PROGRAM=y CONFIG_MTD_ONENAND_SIM=m # # LPDDR flash memory drivers # CONFIG_MTD_LPDDR=m CONFIG_MTD_QINFO_PROBE=m # # UBI - Unsorted block images # CONFIG_MTD_UBI=m CONFIG_MTD_UBI_WL_THRESHOLD=4096 CONFIG_MTD_UBI_BEB_RESERVE=1 CONFIG_MTD_UBI_GLUEBI=m # # UBI debugging options # # CONFIG_MTD_UBI_DEBUG is not set CONFIG_PARPORT=m CONFIG_PARPORT_PC=m CONFIG_PARPORT_SERIAL=m CONFIG_PARPORT_PC_FIFO=y # CONFIG_PARPORT_PC_SUPERIO is not set CONFIG_PARPORT_PC_PCMCIA=m # CONFIG_PARPORT_GSC is not set CONFIG_PARPORT_AX88796=m CONFIG_PARPORT_1284=y CONFIG_PARPORT_NOT_PC=y CONFIG_PNP=y CONFIG_PNP_DEBUG_MESSAGES=y # # Protocols # CONFIG_PNPACPI=y CONFIG_BLK_DEV=y CONFIG_BLK_DEV_FD=m CONFIG_PARIDE=m # # Parallel IDE high-level drivers # CONFIG_PARIDE_PD=m CONFIG_PARIDE_PCD=m CONFIG_PARIDE_PF=m CONFIG_PARIDE_PT=m CONFIG_PARIDE_PG=m # # Parallel IDE protocol modules # CONFIG_PARIDE_ATEN=m CONFIG_PARIDE_BPCK=m CONFIG_PARIDE_COMM=m CONFIG_PARIDE_DSTR=m CONFIG_PARIDE_FIT2=m CONFIG_PARIDE_FIT3=m CONFIG_PARIDE_EPAT=m # CONFIG_PARIDE_EPATC8 is not set CONFIG_PARIDE_EPIA=m CONFIG_PARIDE_FRIQ=m CONFIG_PARIDE_FRPW=m CONFIG_PARIDE_KBIC=m CONFIG_PARIDE_KTTI=m CONFIG_PARIDE_ON20=m CONFIG_PARIDE_ON26=m CONFIG_BLK_CPQ_DA=m CONFIG_BLK_CPQ_CISS_DA=m CONFIG_CISS_SCSI_TAPE=y CONFIG_BLK_DEV_DAC960=m CONFIG_BLK_DEV_UMEM=m # CONFIG_BLK_DEV_COW_COMMON is not set CONFIG_BLK_DEV_LOOP=y CONFIG_BLK_DEV_CRYPTOLOOP=m CONFIG_BLK_DEV_NBD=m CONFIG_BLK_DEV_OSD=m CONFIG_BLK_DEV_SX8=m # CONFIG_BLK_DEV_UB is not set CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_COUNT=16 CONFIG_BLK_DEV_RAM_SIZE=65536 # CONFIG_BLK_DEV_XIP is not set CONFIG_CDROM_PKTCDVD=y CONFIG_CDROM_PKTCDVD_BUFFERS=8 # CONFIG_CDROM_PKTCDVD_WCACHE is not set CONFIG_ATA_OVER_ETH=m CONFIG_XEN_BLKDEV_FRONTEND=m CONFIG_VIRTIO_BLK=y # CONFIG_BLK_DEV_HD is not set CONFIG_MISC_DEVICES=y CONFIG_IBM_ASM=m CONFIG_PHANTOM=m CONFIG_SGI_IOC4=m CONFIG_TIFM_CORE=m CONFIG_TIFM_7XX1=m CONFIG_ICS932S401=m CONFIG_ENCLOSURE_SERVICES=m CONFIG_HP_ILO=m CONFIG_DELL_LAPTOP=m CONFIG_ISL29003=m CONFIG_C2PORT=m CONFIG_C2PORT_DURAMAR_2150=m # # EEPROM support # CONFIG_EEPROM_AT24=m CONFIG_EEPROM_AT25=m CONFIG_EEPROM_LEGACY=m CONFIG_EEPROM_MAX6875=m CONFIG_EEPROM_93CX6=m CONFIG_CB710_CORE=m # CONFIG_CB710_DEBUG is not set CONFIG_CB710_DEBUG_ASSUMPTIONS=y CONFIG_HAVE_IDE=y # CONFIG_IDE is not set # # SCSI device support # CONFIG_RAID_ATTRS=m CONFIG_SCSI=y CONFIG_SCSI_DMA=y CONFIG_SCSI_TGT=m CONFIG_SCSI_NETLINK=y CONFIG_SCSI_PROC_FS=y # # SCSI support type (disk, tape, CD-ROM) # CONFIG_BLK_DEV_SD=y CONFIG_CHR_DEV_ST=m CONFIG_CHR_DEV_OSST=m CONFIG_BLK_DEV_SR=y # CONFIG_BLK_DEV_SR_VENDOR is not set CONFIG_CHR_DEV_SG=y CONFIG_CHR_DEV_SCH=m CONFIG_SCSI_ENCLOSURE=m CONFIG_SCSI_MULTI_LUN=y CONFIG_SCSI_CONSTANTS=y CONFIG_SCSI_LOGGING=y CONFIG_SCSI_SCAN_ASYNC=y CONFIG_SCSI_WAIT_SCAN=m # # SCSI Transports # CONFIG_SCSI_SPI_ATTRS=y CONFIG_SCSI_FC_ATTRS=m CONFIG_SCSI_FC_TGT_ATTRS=y CONFIG_SCSI_ISCSI_ATTRS=m CONFIG_SCSI_SAS_ATTRS=m CONFIG_SCSI_SAS_LIBSAS=m CONFIG_SCSI_SAS_ATA=y CONFIG_SCSI_SAS_HOST_SMP=y # CONFIG_SCSI_SAS_LIBSAS_DEBUG is not set CONFIG_SCSI_SRP_ATTRS=m CONFIG_SCSI_SRP_TGT_ATTRS=y CONFIG_SCSI_LOWLEVEL=y CONFIG_ISCSI_TCP=m CONFIG_SCSI_CXGB3_ISCSI=m CONFIG_SCSI_BNX2_ISCSI=m CONFIG_BE2ISCSI=m CONFIG_BLK_DEV_3W_XXXX_RAID=m CONFIG_SCSI_3W_9XXX=m CONFIG_SCSI_ACARD=m CONFIG_SCSI_AACRAID=m CONFIG_SCSI_AIC7XXX=m CONFIG_AIC7XXX_CMDS_PER_DEVICE=8 CONFIG_AIC7XXX_RESET_DELAY_MS=15000 CONFIG_AIC7XXX_DEBUG_ENABLE=y CONFIG_AIC7XXX_DEBUG_MASK=0 CONFIG_AIC7XXX_REG_PRETTY_PRINT=y # CONFIG_SCSI_AIC7XXX_OLD is not set CONFIG_SCSI_AIC79XX=m CONFIG_AIC79XX_CMDS_PER_DEVICE=32 CONFIG_AIC79XX_RESET_DELAY_MS=5000 CONFIG_AIC79XX_DEBUG_ENABLE=y CONFIG_AIC79XX_DEBUG_MASK=0 CONFIG_AIC79XX_REG_PRETTY_PRINT=y CONFIG_SCSI_AIC94XX=m # CONFIG_AIC94XX_DEBUG is not set CONFIG_SCSI_MVSAS=m CONFIG_SCSI_MVSAS_DEBUG=y CONFIG_SCSI_DPT_I2O=m CONFIG_SCSI_ADVANSYS=m CONFIG_SCSI_ARCMSR=m CONFIG_SCSI_ARCMSR_AER=y CONFIG_MEGARAID_NEWGEN=y CONFIG_MEGARAID_MM=m CONFIG_MEGARAID_MAILBOX=m CONFIG_MEGARAID_LEGACY=m CONFIG_MEGARAID_SAS=m CONFIG_SCSI_MPT2SAS=m CONFIG_SCSI_MPT2SAS_MAX_SGE=128 # CONFIG_SCSI_MPT2SAS_LOGGING is not set CONFIG_SCSI_HPTIOP=m CONFIG_SCSI_BUSLOGIC=m CONFIG_LIBFC=m CONFIG_LIBFCOE=m CONFIG_FCOE=m CONFIG_FCOE_FNIC=m CONFIG_SCSI_DMX3191D=m CONFIG_SCSI_EATA=m CONFIG_SCSI_EATA_TAGGED_QUEUE=y CONFIG_SCSI_EATA_LINKED_COMMANDS=y CONFIG_SCSI_EATA_MAX_TAGS=16 CONFIG_SCSI_FUTURE_DOMAIN=m CONFIG_SCSI_GDTH=m CONFIG_SCSI_IPS=m CONFIG_SCSI_INITIO=m CONFIG_SCSI_INIA100=m CONFIG_SCSI_PPA=m CONFIG_SCSI_IMM=m # CONFIG_SCSI_IZIP_EPP16 is not set # CONFIG_SCSI_IZIP_SLOW_CTR is not set CONFIG_SCSI_STEX=m CONFIG_SCSI_SYM53C8XX_2=y CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1 CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16 CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64 CONFIG_SCSI_SYM53C8XX_MMIO=y CONFIG_SCSI_IPR=m # CONFIG_SCSI_IPR_TRACE is not set # CONFIG_SCSI_IPR_DUMP is not set CONFIG_SCSI_QLOGIC_1280=m CONFIG_SCSI_QLA_FC=m CONFIG_SCSI_QLA_ISCSI=m CONFIG_SCSI_LPFC=m CONFIG_SCSI_LPFC_DEBUG_FS=y CONFIG_SCSI_DC395x=m CONFIG_SCSI_DC390T=m CONFIG_SCSI_DEBUG=m CONFIG_SCSI_PMCRAID=m CONFIG_SCSI_SRP=m CONFIG_SCSI_BFA_FC=m CONFIG_SCSI_LOWLEVEL_PCMCIA=y CONFIG_PCMCIA_FDOMAIN=m CONFIG_PCMCIA_QLOGIC=m CONFIG_PCMCIA_SYM53C500=m CONFIG_SCSI_DH=y CONFIG_SCSI_DH_RDAC=m CONFIG_SCSI_DH_HP_SW=m CONFIG_SCSI_DH_EMC=m CONFIG_SCSI_DH_ALUA=m CONFIG_SCSI_OSD_INITIATOR=m CONFIG_SCSI_OSD_ULD=m CONFIG_SCSI_OSD_DPRINT_SENSE=1 # CONFIG_SCSI_OSD_DEBUG is not set CONFIG_ATA=y # CONFIG_ATA_NONSTANDARD is not set CONFIG_ATA_VERBOSE_ERROR=y CONFIG_ATA_ACPI=y CONFIG_SATA_PMP=y CONFIG_SATA_AHCI=m CONFIG_SATA_SIL24=m CONFIG_ATA_SFF=y CONFIG_SATA_SVW=m CONFIG_ATA_PIIX=y CONFIG_SATA_MV=m CONFIG_SATA_NV=m CONFIG_PDC_ADMA=y CONFIG_SATA_QSTOR=m CONFIG_SATA_PROMISE=m CONFIG_SATA_SX4=m CONFIG_SATA_SIL=m CONFIG_SATA_SIS=m CONFIG_SATA_ULI=m CONFIG_SATA_VIA=m CONFIG_SATA_VITESSE=m CONFIG_SATA_INIC162X=m CONFIG_PATA_ACPI=y CONFIG_PATA_ALI=m CONFIG_PATA_AMD=m CONFIG_PATA_ARTOP=m CONFIG_PATA_ATP867X=m CONFIG_PATA_ATIIXP=m CONFIG_PATA_CMD640_PCI=m CONFIG_PATA_CMD64X=m CONFIG_PATA_CS5520=m CONFIG_PATA_CS5530=m CONFIG_PATA_CYPRESS=m CONFIG_PATA_EFAR=m CONFIG_ATA_GENERIC=y CONFIG_PATA_HPT366=m CONFIG_PATA_HPT37X=m CONFIG_PATA_HPT3X2N=m CONFIG_PATA_HPT3X3=m # CONFIG_PATA_HPT3X3_DMA is not set CONFIG_PATA_IT821X=m CONFIG_PATA_IT8213=m CONFIG_PATA_JMICRON=m CONFIG_PATA_TRIFLEX=m CONFIG_PATA_MARVELL=m CONFIG_PATA_MPIIX=m CONFIG_PATA_OLDPIIX=m CONFIG_PATA_NETCELL=m CONFIG_PATA_NINJA32=m CONFIG_PATA_NS87410=m CONFIG_PATA_NS87415=m CONFIG_PATA_OPTI=m CONFIG_PATA_OPTIDMA=m CONFIG_PATA_PCMCIA=m CONFIG_PATA_PDC_OLD=m CONFIG_PATA_RADISYS=m CONFIG_PATA_RDC=m CONFIG_PATA_RZ1000=m CONFIG_PATA_SC1200=m CONFIG_PATA_SERVERWORKS=m CONFIG_PATA_PDC2027X=m CONFIG_PATA_SIL680=m CONFIG_PATA_SIS=y CONFIG_PATA_VIA=m CONFIG_PATA_WINBOND=m CONFIG_PATA_SCH=m CONFIG_MD=y CONFIG_BLK_DEV_MD=y CONFIG_MD_AUTODETECT=y CONFIG_MD_LINEAR=m CONFIG_MD_RAID0=m CONFIG_MD_RAID1=m CONFIG_MD_RAID10=m CONFIG_MD_RAID456=m # CONFIG_MULTICORE_RAID456 is not set CONFIG_MD_RAID6_PQ=m CONFIG_ASYNC_RAID6_TEST=m CONFIG_MD_MULTIPATH=m CONFIG_MD_FAULTY=m CONFIG_BLK_DEV_DM=y # CONFIG_DM_DEBUG is not set CONFIG_DM_CRYPT=m CONFIG_DM_SNAPSHOT=y CONFIG_DM_MIRROR=y # CONFIG_DM_LOG_USERSPACE is not set CONFIG_DM_ZERO=m CONFIG_DM_MULTIPATH=y CONFIG_DM_MULTIPATH_QL=m CONFIG_DM_MULTIPATH_ST=m # CONFIG_DM_DELAY is not set CONFIG_DM_UEVENT=y CONFIG_FUSION=y CONFIG_FUSION_SPI=m CONFIG_FUSION_FC=m CONFIG_FUSION_SAS=m CONFIG_FUSION_MAX_SGE=128 CONFIG_FUSION_CTL=m CONFIG_FUSION_LAN=m CONFIG_FUSION_LOGGING=y # # IEEE 1394 (FireWire) support # # # You can enable one or both FireWire driver stacks. # # # See the help texts for more information. # CONFIG_FIREWIRE=m CONFIG_FIREWIRE_OHCI=m CONFIG_FIREWIRE_OHCI_DEBUG=y CONFIG_FIREWIRE_SBP2=m CONFIG_FIREWIRE_NET=m CONFIG_IEEE1394=m CONFIG_IEEE1394_OHCI1394=m CONFIG_IEEE1394_PCILYNX=m CONFIG_IEEE1394_SBP2=m # CONFIG_IEEE1394_SBP2_PHYS_DMA is not set CONFIG_IEEE1394_ETH1394_ROM_ENTRY=y CONFIG_IEEE1394_ETH1394=m CONFIG_IEEE1394_RAWIO=m CONFIG_IEEE1394_VIDEO1394=m CONFIG_IEEE1394_DV1394=m # CONFIG_IEEE1394_VERBOSEDEBUG is not set CONFIG_I2O=m CONFIG_I2O_LCT_NOTIFY_ON_CHANGES=y CONFIG_I2O_EXT_ADAPTEC=y CONFIG_I2O_EXT_ADAPTEC_DMA64=y CONFIG_I2O_CONFIG=m CONFIG_I2O_CONFIG_OLD_IOCTL=y CONFIG_I2O_BUS=m CONFIG_I2O_BLOCK=m CONFIG_I2O_SCSI=m CONFIG_I2O_PROC=m CONFIG_MACINTOSH_DRIVERS=y CONFIG_MAC_EMUMOUSEBTN=y CONFIG_NETDEVICES=y CONFIG_IFB=m CONFIG_DUMMY=m CONFIG_BONDING=m CONFIG_MACVLAN=m CONFIG_EQUALIZER=m CONFIG_TUN=y CONFIG_VETH=m CONFIG_NET_SB1000=m CONFIG_ARCNET=m CONFIG_ARCNET_1201=m CONFIG_ARCNET_1051=m CONFIG_ARCNET_RAW=m CONFIG_ARCNET_CAP=m CONFIG_ARCNET_COM90xx=m CONFIG_ARCNET_COM90xxIO=m CONFIG_ARCNET_RIM_I=m CONFIG_ARCNET_COM20020=m CONFIG_ARCNET_COM20020_PCI=m CONFIG_PHYLIB=y # # MII PHY device drivers # CONFIG_MARVELL_PHY=y CONFIG_DAVICOM_PHY=y CONFIG_QSEMI_PHY=y CONFIG_LXT_PHY=y CONFIG_CICADA_PHY=y CONFIG_VITESSE_PHY=y CONFIG_SMSC_PHY=y CONFIG_BROADCOM_PHY=y CONFIG_ICPLUS_PHY=y CONFIG_REALTEK_PHY=y CONFIG_NATIONAL_PHY=y CONFIG_STE10XP=y CONFIG_LSI_ET1011C_PHY=y CONFIG_FIXED_PHY=y CONFIG_MDIO_BITBANG=y CONFIG_MDIO_GPIO=y CONFIG_NET_ETHERNET=y CONFIG_MII=m CONFIG_HAPPYMEAL=m CONFIG_SUNGEM=m CONFIG_CASSINI=m CONFIG_NET_VENDOR_3COM=y CONFIG_VORTEX=m CONFIG_TYPHOON=m # CONFIG_ENC28J60 is not set CONFIG_ETHOC=m CONFIG_DNET=m CONFIG_NET_TULIP=y CONFIG_DE2104X=m CONFIG_DE2104X_DSL=0 CONFIG_TULIP=m # CONFIG_TULIP_MWI is not set # CONFIG_TULIP_MMIO is not set # CONFIG_TULIP_NAPI is not set CONFIG_DE4X5=m CONFIG_WINBOND_840=m CONFIG_DM9102=m CONFIG_ULI526X=m CONFIG_PCMCIA_XIRCOM=m CONFIG_HP100=m # CONFIG_IBM_NEW_EMAC_ZMII is not set # CONFIG_IBM_NEW_EMAC_RGMII is not set # CONFIG_IBM_NEW_EMAC_TAH is not set # CONFIG_IBM_NEW_EMAC_EMAC4 is not set # CONFIG_IBM_NEW_EMAC_NO_FLOW_CTRL is not set # CONFIG_IBM_NEW_EMAC_MAL_CLR_ICINTSTAT is not set # CONFIG_IBM_NEW_EMAC_MAL_COMMON_ERR is not set CONFIG_NET_PCI=y CONFIG_PCNET32=m CONFIG_AMD8111_ETH=m CONFIG_ADAPTEC_STARFIRE=m CONFIG_B44=m CONFIG_B44_PCI_AUTOSELECT=y CONFIG_B44_PCICORE_AUTOSELECT=y CONFIG_B44_PCI=y CONFIG_FORCEDETH=m # CONFIG_FORCEDETH_NAPI is not set CONFIG_E100=m CONFIG_FEALNX=m CONFIG_NATSEMI=m CONFIG_NE2K_PCI=m CONFIG_8139CP=m CONFIG_8139TOO=m CONFIG_8139TOO_PIO=y # CONFIG_8139TOO_TUNE_TWISTER is not set CONFIG_8139TOO_8129=y # CONFIG_8139_OLD_RX_RESET is not set # CONFIG_R6040 is not set CONFIG_SIS900=m CONFIG_EPIC100=m CONFIG_SMSC9420=m CONFIG_SUNDANCE=m # CONFIG_SUNDANCE_MMIO is not set CONFIG_TLAN=m CONFIG_KS8842=m CONFIG_KS8851=m CONFIG_KS8851_MLL=m CONFIG_VIA_RHINE=m CONFIG_VIA_RHINE_MMIO=y CONFIG_SC92031=m CONFIG_NET_POCKET=y CONFIG_ATP=m CONFIG_DE600=m CONFIG_DE620=m CONFIG_ATL2=m CONFIG_NETDEV_1000=y CONFIG_ACENIC=m # CONFIG_ACENIC_OMIT_TIGON_I is not set # CONFIG_DL2K is not set CONFIG_E1000=m CONFIG_E1000E=m CONFIG_IP1000=m CONFIG_IGB=m CONFIG_IGB_DCA=y CONFIG_IGBVF=m CONFIG_NS83820=m CONFIG_HAMACHI=m CONFIG_YELLOWFIN=m CONFIG_R8169=m CONFIG_R8169_VLAN=y CONFIG_SIS190=m CONFIG_SKGE=m # CONFIG_SKGE_DEBUG is not set CONFIG_SKY2=m # CONFIG_SKY2_DEBUG is not set CONFIG_VIA_VELOCITY=m CONFIG_TIGON3=m CONFIG_BNX2=m CONFIG_CNIC=m CONFIG_QLA3XXX=m CONFIG_ATL1=m CONFIG_ATL1E=m CONFIG_ATL1C=m CONFIG_JME=m CONFIG_NETDEV_10000=y CONFIG_MDIO=m CONFIG_CHELSIO_T1=m CONFIG_CHELSIO_T1_1G=y CONFIG_CHELSIO_T3_DEPENDS=y CONFIG_CHELSIO_T3=m CONFIG_ENIC=m CONFIG_IXGBE=m CONFIG_IXGBE_DCA=y CONFIG_IXGBE_DCB=y CONFIG_IXGB=m CONFIG_S2IO=m CONFIG_VXGE=m # CONFIG_VXGE_DEBUG_TRACE_ALL is not set CONFIG_MYRI10GE=m CONFIG_MYRI10GE_DCA=y CONFIG_NETXEN_NIC=m CONFIG_NIU=m CONFIG_MLX4_EN=m CONFIG_MLX4_CORE=m CONFIG_MLX4_DEBUG=y CONFIG_TEHUTI=m CONFIG_BNX2X=m CONFIG_QLGE=m CONFIG_SFC=m CONFIG_SFC_MTD=y CONFIG_BE2NET=m CONFIG_TR=y CONFIG_IBMOL=m CONFIG_3C359=m CONFIG_TMS380TR=m CONFIG_TMSPCI=m CONFIG_ABYSS=m CONFIG_WLAN=y CONFIG_WLAN_PRE80211=y CONFIG_STRIP=m CONFIG_PCMCIA_WAVELAN=m CONFIG_PCMCIA_NETWAVE=m CONFIG_WLAN_80211=y CONFIG_PCMCIA_RAYCS=m CONFIG_LIBERTAS=m CONFIG_LIBERTAS_USB=m CONFIG_LIBERTAS_CS=m CONFIG_LIBERTAS_SDIO=m CONFIG_LIBERTAS_SPI=m # CONFIG_LIBERTAS_DEBUG is not set CONFIG_LIBERTAS_THINFIRM=m CONFIG_LIBERTAS_THINFIRM_USB=m CONFIG_AIRO=m CONFIG_ATMEL=m CONFIG_PCI_ATMEL=m CONFIG_PCMCIA_ATMEL=m CONFIG_AT76C50X_USB=m CONFIG_AIRO_CS=m CONFIG_PCMCIA_WL3501=m CONFIG_PRISM54=m CONFIG_USB_ZD1201=m CONFIG_USB_NET_RNDIS_WLAN=m CONFIG_RTL8180=m CONFIG_RTL8187=m CONFIG_RTL8187_LEDS=y CONFIG_ADM8211=m CONFIG_MAC80211_HWSIM=m CONFIG_MWL8K=m CONFIG_P54_COMMON=m CONFIG_P54_USB=m CONFIG_P54_PCI=m CONFIG_P54_SPI=m CONFIG_P54_LEDS=y CONFIG_ATH_COMMON=m CONFIG_ATH5K=m # CONFIG_ATH5K_DEBUG is not set CONFIG_ATH9K=m CONFIG_ATH9K_DEBUG=y CONFIG_AR9170_USB=m CONFIG_AR9170_LEDS=y CONFIG_IPW2100=m CONFIG_IPW2100_MONITOR=y # CONFIG_IPW2100_DEBUG is not set CONFIG_IPW2200=m CONFIG_IPW2200_MONITOR=y CONFIG_IPW2200_RADIOTAP=y CONFIG_IPW2200_PROMISCUOUS=y CONFIG_IPW2200_QOS=y # CONFIG_IPW2200_DEBUG is not set CONFIG_LIBIPW=m CONFIG_LIBIPW_DEBUG=y CONFIG_IWLWIFI=m CONFIG_IWLWIFI_LEDS=y # CONFIG_IWLWIFI_SPECTRUM_MEASUREMENT is not set # CONFIG_IWLWIFI_DEBUG is not set CONFIG_IWLAGN=m CONFIG_IWL4965=y CONFIG_IWL5000=y CONFIG_IWL3945=m CONFIG_IWL3945_SPECTRUM_MEASUREMENT=y CONFIG_HOSTAP=m CONFIG_HOSTAP_FIRMWARE=y CONFIG_HOSTAP_FIRMWARE_NVRAM=y CONFIG_HOSTAP_PLX=m CONFIG_HOSTAP_PCI=m CONFIG_HOSTAP_CS=m CONFIG_B43=m CONFIG_B43_PCI_AUTOSELECT=y CONFIG_B43_PCICORE_AUTOSELECT=y # CONFIG_B43_PCMCIA is not set # CONFIG_B43_SDIO is not set CONFIG_B43_PIO=y CONFIG_B43_PHY_LP=y CONFIG_B43_LEDS=y CONFIG_B43_HWRNG=y # CONFIG_B43_DEBUG is not set CONFIG_B43LEGACY=m CONFIG_B43LEGACY_PCI_AUTOSELECT=y CONFIG_B43LEGACY_PCICORE_AUTOSELECT=y CONFIG_B43LEGACY_LEDS=y CONFIG_B43LEGACY_HWRNG=y CONFIG_B43LEGACY_DEBUG=y CONFIG_B43LEGACY_DMA=y CONFIG_B43LEGACY_PIO=y CONFIG_B43LEGACY_DMA_AND_PIO_MODE=y # CONFIG_B43LEGACY_DMA_MODE is not set # CONFIG_B43LEGACY_PIO_MODE is not set CONFIG_ZD1211RW=m # CONFIG_ZD1211RW_DEBUG is not set CONFIG_RT2X00=m CONFIG_RT2400PCI=m CONFIG_RT2500PCI=m CONFIG_RT61PCI=m CONFIG_RT2500USB=m CONFIG_RT73USB=m CONFIG_RT2800USB=m CONFIG_RT2X00_LIB_PCI=m CONFIG_RT2X00_LIB_USB=m CONFIG_RT2X00_LIB=m CONFIG_RT2X00_LIB_HT=y CONFIG_RT2X00_LIB_FIRMWARE=y CONFIG_RT2X00_LIB_CRYPTO=y CONFIG_RT2X00_LIB_LEDS=y # CONFIG_RT2X00_LIB_DEBUGFS is not set # CONFIG_RT2X00_DEBUG is not set CONFIG_HERMES=m CONFIG_HERMES_CACHE_FW_ON_INIT=y CONFIG_PLX_HERMES=m CONFIG_TMD_HERMES=m CONFIG_NORTEL_HERMES=m CONFIG_PCI_HERMES=m CONFIG_PCMCIA_HERMES=m CONFIG_PCMCIA_SPECTRUM=m CONFIG_WL12XX=m CONFIG_WL1251=m CONFIG_WL1251_SPI=m CONFIG_WL1251_SDIO=m CONFIG_WL1271=m CONFIG_IWM=m # CONFIG_IWM_DEBUG is not set # # WiMAX Wireless Broadband devices # CONFIG_WIMAX_I2400M=m CONFIG_WIMAX_I2400M_USB=m CONFIG_WIMAX_I2400M_SDIO=m CONFIG_WIMAX_I2400M_DEBUG_LEVEL=8 # # USB Network Adapters # CONFIG_USB_CATC=m CONFIG_USB_KAWETH=m CONFIG_USB_PEGASUS=m CONFIG_USB_RTL8150=m CONFIG_USB_USBNET=m CONFIG_USB_NET_AX8817X=m CONFIG_USB_NET_CDCETHER=m CONFIG_USB_NET_CDC_EEM=m CONFIG_USB_NET_DM9601=m CONFIG_USB_NET_SMSC95XX=m CONFIG_USB_NET_GL620A=m CONFIG_USB_NET_NET1080=m CONFIG_USB_NET_PLUSB=m CONFIG_USB_NET_MCS7830=m CONFIG_USB_NET_RNDIS_HOST=m CONFIG_USB_NET_CDC_SUBSET=m CONFIG_USB_ALI_M5632=y CONFIG_USB_AN2720=y CONFIG_USB_BELKIN=y CONFIG_USB_ARMLINUX=y CONFIG_USB_EPSON2888=y CONFIG_USB_KC2190=y CONFIG_USB_NET_ZAURUS=m CONFIG_USB_HSO=m CONFIG_USB_NET_INT51X1=m CONFIG_USB_CDC_PHONET=m CONFIG_NET_PCMCIA=y CONFIG_PCMCIA_3C589=m CONFIG_PCMCIA_3C574=m CONFIG_PCMCIA_FMVJ18X=m CONFIG_PCMCIA_PCNET=m CONFIG_PCMCIA_NMCLAN=m CONFIG_PCMCIA_SMC91C92=m CONFIG_PCMCIA_XIRC2PS=m CONFIG_PCMCIA_AXNET=m CONFIG_ARCNET_COM20020_CS=m CONFIG_PCMCIA_IBMTR=m CONFIG_WAN=y CONFIG_LANMEDIA=m CONFIG_HDLC=m CONFIG_HDLC_RAW=m CONFIG_HDLC_RAW_ETH=m CONFIG_HDLC_CISCO=m CONFIG_HDLC_FR=m CONFIG_HDLC_PPP=m CONFIG_HDLC_X25=m CONFIG_PCI200SYN=m CONFIG_WANXL=m # CONFIG_PC300TOO is not set CONFIG_FARSYNC=m CONFIG_DSCC4=m CONFIG_DSCC4_PCISYNC=y CONFIG_DSCC4_PCI_RST=y CONFIG_DLCI=m CONFIG_DLCI_MAX=8 CONFIG_WAN_ROUTER_DRIVERS=m CONFIG_CYCLADES_SYNC=m CONFIG_CYCLOMX_X25=y CONFIG_LAPBETHER=m CONFIG_X25_ASY=m CONFIG_SBNI=m # CONFIG_SBNI_MULTILINE is not set CONFIG_ATM_DRIVERS=y # CONFIG_ATM_DUMMY is not set CONFIG_ATM_TCP=m CONFIG_ATM_LANAI=m CONFIG_ATM_ENI=m # CONFIG_ATM_ENI_DEBUG is not set # CONFIG_ATM_ENI_TUNE_BURST is not set CONFIG_ATM_FIRESTREAM=m CONFIG_ATM_ZATM=m # CONFIG_ATM_ZATM_DEBUG is not set CONFIG_ATM_IDT77252=m # CONFIG_ATM_IDT77252_DEBUG is not set # CONFIG_ATM_IDT77252_RCV_ALL is not set CONFIG_ATM_IDT77252_USE_SUNI=y CONFIG_ATM_AMBASSADOR=m # CONFIG_ATM_AMBASSADOR_DEBUG is not set CONFIG_ATM_HORIZON=m # CONFIG_ATM_HORIZON_DEBUG is not set CONFIG_ATM_IA=m # CONFIG_ATM_IA_DEBUG is not set CONFIG_ATM_FORE200E=m # CONFIG_ATM_FORE200E_USE_TASKLET is not set CONFIG_ATM_FORE200E_TX_RETRY=16 CONFIG_ATM_FORE200E_DEBUG=0 CONFIG_ATM_HE=m CONFIG_ATM_HE_USE_SUNI=y CONFIG_ATM_SOLOS=m CONFIG_IEEE802154_DRIVERS=m # CONFIG_IEEE802154_FAKEHARD is not set CONFIG_XEN_NETDEV_FRONTEND=m CONFIG_FDDI=y CONFIG_DEFXX=m # CONFIG_DEFXX_MMIO is not set CONFIG_SKFP=m CONFIG_HIPPI=y CONFIG_ROADRUNNER=m # CONFIG_ROADRUNNER_LARGE_RINGS is not set CONFIG_PLIP=m CONFIG_PPP=y CONFIG_PPP_MULTILINK=y CONFIG_PPP_FILTER=y CONFIG_PPP_ASYNC=m CONFIG_PPP_SYNC_TTY=m CONFIG_PPP_DEFLATE=m CONFIG_PPP_BSDCOMP=m CONFIG_PPP_MPPE=m CONFIG_PPPOE=m CONFIG_PPPOATM=m CONFIG_PPPOL2TP=m CONFIG_SLIP=m CONFIG_SLIP_COMPRESSED=y CONFIG_SLHC=y CONFIG_SLIP_SMART=y CONFIG_SLIP_MODE_SLIP6=y CONFIG_NET_FC=y CONFIG_NETCONSOLE=m CONFIG_NETCONSOLE_DYNAMIC=y CONFIG_NETPOLL=y # CONFIG_NETPOLL_TRAP is not set CONFIG_NET_POLL_CONTROLLER=y CONFIG_VIRTIO_NET=y CONFIG_VMXNET3=m CONFIG_ISDN=y CONFIG_ISDN_I4L=m CONFIG_MISDN=m CONFIG_MISDN_DSP=m CONFIG_MISDN_L1OIP=m # # mISDN hardware drivers # CONFIG_MISDN_HFCPCI=m CONFIG_MISDN_HFCMULTI=m CONFIG_MISDN_HFCUSB=m CONFIG_MISDN_AVMFRITZ=m CONFIG_MISDN_SPEEDFAX=m CONFIG_MISDN_INFINEON=m CONFIG_MISDN_W6692=m CONFIG_MISDN_NETJET=m CONFIG_MISDN_IPAC=m CONFIG_MISDN_ISAR=m CONFIG_ISDN_PPP=y CONFIG_ISDN_PPP_VJ=y CONFIG_ISDN_MPP=y CONFIG_IPPP_FILTER=y CONFIG_ISDN_PPP_BSDCOMP=m CONFIG_ISDN_AUDIO=y CONFIG_ISDN_TTY_FAX=y CONFIG_ISDN_X25=y # # ISDN feature submodules # CONFIG_ISDN_DIVERSION=m # # ISDN4Linux hardware drivers # # # Passive cards # CONFIG_ISDN_DRV_HISAX=m # # D-channel protocol features # CONFIG_HISAX_EURO=y CONFIG_DE_AOC=y # CONFIG_HISAX_NO_SENDCOMPLETE is not set # CONFIG_HISAX_NO_LLC is not set # CONFIG_HISAX_NO_KEYPAD is not set CONFIG_HISAX_1TR6=y CONFIG_HISAX_NI1=y CONFIG_HISAX_MAX_CARDS=8 # # HiSax supported cards # CONFIG_HISAX_16_3=y CONFIG_HISAX_TELESPCI=y CONFIG_HISAX_S0BOX=y CONFIG_HISAX_FRITZPCI=y CONFIG_HISAX_AVM_A1_PCMCIA=y CONFIG_HISAX_ELSA=y CONFIG_HISAX_DIEHLDIVA=y CONFIG_HISAX_SEDLBAUER=y CONFIG_HISAX_NETJET=y CONFIG_HISAX_NETJET_U=y CONFIG_HISAX_NICCY=y CONFIG_HISAX_BKM_A4T=y CONFIG_HISAX_SCT_QUADRO=y CONFIG_HISAX_GAZEL=y CONFIG_HISAX_HFC_PCI=y CONFIG_HISAX_W6692=y CONFIG_HISAX_HFC_SX=y CONFIG_HISAX_ENTERNOW_PCI=y # CONFIG_HISAX_DEBUG is not set # # HiSax PCMCIA card service modules # CONFIG_HISAX_SEDLBAUER_CS=m CONFIG_HISAX_ELSA_CS=m CONFIG_HISAX_AVM_A1_CS=m CONFIG_HISAX_TELES_CS=m # # HiSax sub driver modules # CONFIG_HISAX_ST5481=m CONFIG_HISAX_HFCUSB=m CONFIG_HISAX_HFC4S8S=m CONFIG_HISAX_FRITZ_PCIPNP=m # # Active cards # CONFIG_HYSDN=m CONFIG_HYSDN_CAPI=y CONFIG_ISDN_HDLC=m CONFIG_ISDN_CAPI=m CONFIG_ISDN_DRV_AVMB1_VERBOSE_REASON=y CONFIG_CAPI_TRACE=y CONFIG_ISDN_CAPI_MIDDLEWARE=y CONFIG_ISDN_CAPI_CAPI20=m CONFIG_ISDN_CAPI_CAPIFS_BOOL=y CONFIG_ISDN_CAPI_CAPIFS=m CONFIG_ISDN_CAPI_CAPIDRV=m # # CAPI hardware drivers # CONFIG_CAPI_AVM=y CONFIG_ISDN_DRV_AVMB1_B1PCI=m CONFIG_ISDN_DRV_AVMB1_B1PCIV4=y CONFIG_ISDN_DRV_AVMB1_B1PCMCIA=m CONFIG_ISDN_DRV_AVMB1_AVM_CS=m CONFIG_ISDN_DRV_AVMB1_T1PCI=m CONFIG_ISDN_DRV_AVMB1_C4=m CONFIG_CAPI_EICON=y CONFIG_ISDN_DIVAS=m CONFIG_ISDN_DIVAS_BRIPCI=y CONFIG_ISDN_DIVAS_PRIPCI=y CONFIG_ISDN_DIVAS_DIVACAPI=m CONFIG_ISDN_DIVAS_USERIDI=m CONFIG_ISDN_DIVAS_MAINT=m CONFIG_ISDN_DRV_GIGASET=m CONFIG_GIGASET_BASE=m CONFIG_GIGASET_M105=m CONFIG_GIGASET_M101=m # CONFIG_GIGASET_DEBUG is not set CONFIG_PHONE=m CONFIG_PHONE_IXJ=m CONFIG_PHONE_IXJ_PCMCIA=m # # Input device support # CONFIG_INPUT=y CONFIG_INPUT_FF_MEMLESS=m CONFIG_INPUT_POLLDEV=m # # Userland interfaces # CONFIG_INPUT_MOUSEDEV=y CONFIG_INPUT_MOUSEDEV_PSAUX=y CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 CONFIG_INPUT_JOYDEV=m CONFIG_INPUT_EVDEV=y CONFIG_INPUT_EVBUG=m CONFIG_XEN_KBDDEV_FRONTEND=m # # Input Device Drivers # CONFIG_INPUT_KEYBOARD=y CONFIG_KEYBOARD_ADP5588=m CONFIG_KEYBOARD_ATKBD=y CONFIG_QT2160=m CONFIG_KEYBOARD_LKKBD=m CONFIG_KEYBOARD_GPIO=m CONFIG_KEYBOARD_MATRIX=m CONFIG_KEYBOARD_LM8323=m CONFIG_KEYBOARD_MAX7359=m CONFIG_KEYBOARD_NEWTON=m CONFIG_KEYBOARD_OPENCORES=m CONFIG_KEYBOARD_STOWAWAY=m CONFIG_KEYBOARD_SUNKBD=m CONFIG_KEYBOARD_TWL4030=m CONFIG_KEYBOARD_XTKBD=m CONFIG_INPUT_MOUSE=y CONFIG_MOUSE_PS2=m CONFIG_MOUSE_PS2_ALPS=y CONFIG_MOUSE_PS2_LOGIPS2PP=y CONFIG_MOUSE_PS2_SYNAPTICS=y CONFIG_MOUSE_PS2_LIFEBOOK=y CONFIG_MOUSE_PS2_TRACKPOINT=y CONFIG_MOUSE_PS2_ELANTECH=y CONFIG_MOUSE_PS2_SENTELIC=y # CONFIG_MOUSE_PS2_TOUCHKIT is not set CONFIG_MOUSE_SERIAL=m CONFIG_MOUSE_APPLETOUCH=m CONFIG_MOUSE_BCM5974=m CONFIG_MOUSE_VSXXXAA=m CONFIG_MOUSE_GPIO=m CONFIG_MOUSE_SYNAPTICS_I2C=m CONFIG_INPUT_JOYSTICK=y CONFIG_JOYSTICK_ANALOG=m CONFIG_JOYSTICK_A3D=m CONFIG_JOYSTICK_ADI=m CONFIG_JOYSTICK_COBRA=m CONFIG_JOYSTICK_GF2K=m CONFIG_JOYSTICK_GRIP=m CONFIG_JOYSTICK_GRIP_MP=m CONFIG_JOYSTICK_GUILLEMOT=m CONFIG_JOYSTICK_INTERACT=m CONFIG_JOYSTICK_SIDEWINDER=m CONFIG_JOYSTICK_TMDC=m CONFIG_JOYSTICK_IFORCE=m CONFIG_JOYSTICK_IFORCE_USB=y CONFIG_JOYSTICK_IFORCE_232=y CONFIG_JOYSTICK_WARRIOR=m CONFIG_JOYSTICK_MAGELLAN=m CONFIG_JOYSTICK_SPACEORB=m CONFIG_JOYSTICK_SPACEBALL=m CONFIG_JOYSTICK_STINGER=m CONFIG_JOYSTICK_TWIDJOY=m CONFIG_JOYSTICK_ZHENHUA=m CONFIG_JOYSTICK_DB9=m CONFIG_JOYSTICK_GAMECON=m CONFIG_JOYSTICK_TURBOGRAFX=m CONFIG_JOYSTICK_JOYDUMP=m CONFIG_JOYSTICK_XPAD=m CONFIG_JOYSTICK_XPAD_FF=y CONFIG_JOYSTICK_XPAD_LEDS=y CONFIG_JOYSTICK_WALKERA0701=m CONFIG_INPUT_TABLET=y CONFIG_TABLET_USB_ACECAD=m CONFIG_TABLET_USB_AIPTEK=m CONFIG_TABLET_USB_GTCO=m CONFIG_TABLET_USB_KBTAB=m CONFIG_TABLET_USB_WACOM=m CONFIG_INPUT_TOUCHSCREEN=y CONFIG_TOUCHSCREEN_ADS7846=m CONFIG_TOUCHSCREEN_AD7877=m CONFIG_TOUCHSCREEN_AD7879_I2C=m CONFIG_TOUCHSCREEN_AD7879=m CONFIG_TOUCHSCREEN_DA9034=m CONFIG_TOUCHSCREEN_EETI=m CONFIG_TOUCHSCREEN_FUJITSU=m CONFIG_TOUCHSCREEN_GUNZE=m CONFIG_TOUCHSCREEN_ELO=m CONFIG_TOUCHSCREEN_WACOM_W8001=m CONFIG_TOUCHSCREEN_MCS5000=m CONFIG_TOUCHSCREEN_MTOUCH=m CONFIG_TOUCHSCREEN_INEXIO=m CONFIG_TOUCHSCREEN_MK712=m CONFIG_TOUCHSCREEN_PENMOUNT=m CONFIG_TOUCHSCREEN_TOUCHRIGHT=m CONFIG_TOUCHSCREEN_TOUCHWIN=m CONFIG_TOUCHSCREEN_UCB1400=m CONFIG_TOUCHSCREEN_WM97XX=m CONFIG_TOUCHSCREEN_WM9705=y CONFIG_TOUCHSCREEN_WM9712=y CONFIG_TOUCHSCREEN_WM9713=y CONFIG_TOUCHSCREEN_USB_COMPOSITE=m CONFIG_TOUCHSCREEN_USB_EGALAX=y CONFIG_TOUCHSCREEN_USB_PANJIT=y CONFIG_TOUCHSCREEN_USB_3M=y CONFIG_TOUCHSCREEN_USB_ITM=y CONFIG_TOUCHSCREEN_USB_ETURBO=y CONFIG_TOUCHSCREEN_USB_GUNZE=y CONFIG_TOUCHSCREEN_USB_DMC_TSC10=y CONFIG_TOUCHSCREEN_USB_IRTOUCH=y CONFIG_TOUCHSCREEN_USB_IDEALTEK=y CONFIG_TOUCHSCREEN_USB_GENERAL_TOUCH=y CONFIG_TOUCHSCREEN_USB_GOTOP=y CONFIG_TOUCHSCREEN_USB_JASTEC=y CONFIG_TOUCHSCREEN_USB_E2I=y CONFIG_TOUCHSCREEN_TOUCHIT213=m CONFIG_TOUCHSCREEN_TSC2007=m CONFIG_INPUT_MISC=y CONFIG_INPUT_PCSPKR=m # CONFIG_INPUT_APANEL is not set CONFIG_INPUT_ATLAS_BTNS=m CONFIG_INPUT_ATI_REMOTE=m CONFIG_INPUT_ATI_REMOTE2=m CONFIG_INPUT_KEYSPAN_REMOTE=m CONFIG_INPUT_POWERMATE=m CONFIG_INPUT_YEALINK=m CONFIG_INPUT_CM109=m CONFIG_INPUT_TWL4030_PWRBUTTON=m CONFIG_INPUT_UINPUT=m CONFIG_INPUT_WINBOND_CIR=m CONFIG_INPUT_PCF50633_PMU=m CONFIG_INPUT_GPIO_ROTARY_ENCODER=m CONFIG_INPUT_WM831X_ON=m # # Hardware I/O ports # CONFIG_SERIO=y CONFIG_SERIO_I8042=y CONFIG_SERIO_SERPORT=m CONFIG_SERIO_CT82C710=m CONFIG_SERIO_PARKBD=m CONFIG_SERIO_PCIPS2=m CONFIG_SERIO_LIBPS2=y CONFIG_SERIO_RAW=m CONFIG_GAMEPORT=m CONFIG_GAMEPORT_NS558=m CONFIG_GAMEPORT_L4=m CONFIG_GAMEPORT_EMU10K1=m CONFIG_GAMEPORT_FM801=m # # Character devices # CONFIG_VT=y CONFIG_CONSOLE_TRANSLATIONS=y CONFIG_VT_CONSOLE=y CONFIG_HW_CONSOLE=y CONFIG_VT_HW_CONSOLE_BINDING=y # CONFIG_DEVKMEM is not set CONFIG_SERIAL_NONSTANDARD=y CONFIG_COMPUTONE=m CONFIG_ROCKETPORT=m CONFIG_CYCLADES=m # CONFIG_CYZ_INTR is not set CONFIG_DIGIEPCA=m CONFIG_MOXA_INTELLIO=m CONFIG_MOXA_SMARTIO=m # CONFIG_ISI is not set CONFIG_SYNCLINK=m CONFIG_SYNCLINKMP=m CONFIG_SYNCLINK_GT=m CONFIG_N_HDLC=m CONFIG_RISCOM8=m CONFIG_SPECIALIX=m CONFIG_STALDRV=y CONFIG_STALLION=m CONFIG_ISTALLION=m CONFIG_NOZOMI=m # # Serial drivers # CONFIG_SERIAL_8250=y CONFIG_SERIAL_8250_CONSOLE=y CONFIG_FIX_EARLYCON_MEM=y CONFIG_SERIAL_8250_PCI=y CONFIG_SERIAL_8250_PNP=y CONFIG_SERIAL_8250_CS=m CONFIG_SERIAL_8250_NR_UARTS=48 CONFIG_SERIAL_8250_RUNTIME_UARTS=4 CONFIG_SERIAL_8250_EXTENDED=y CONFIG_SERIAL_8250_MANY_PORTS=y CONFIG_SERIAL_8250_SHARE_IRQ=y # CONFIG_SERIAL_8250_DETECT_IRQ is not set CONFIG_SERIAL_8250_RSA=y # # Non-8250 serial port support # CONFIG_SERIAL_MAX3100=m CONFIG_SERIAL_CORE=y CONFIG_SERIAL_CORE_CONSOLE=y CONFIG_CONSOLE_POLL=y CONFIG_SERIAL_JSM=m CONFIG_UNIX98_PTYS=y CONFIG_DEVPTS_MULTIPLE_INSTANCES=y CONFIG_LEGACY_PTYS=y CONFIG_LEGACY_PTY_COUNT=0 CONFIG_PRINTER=m # CONFIG_LP_CONSOLE is not set CONFIG_PPDEV=m CONFIG_HVC_DRIVER=y CONFIG_HVC_IRQ=y CONFIG_HVC_XEN=y CONFIG_VIRTIO_CONSOLE=m CONFIG_IPMI_HANDLER=m # CONFIG_IPMI_PANIC_EVENT is not set CONFIG_IPMI_DEVICE_INTERFACE=m CONFIG_IPMI_SI=m CONFIG_IPMI_WATCHDOG=m CONFIG_IPMI_POWEROFF=m CONFIG_HW_RANDOM=y CONFIG_HW_RANDOM_TIMERIOMEM=m CONFIG_HW_RANDOM_INTEL=m CONFIG_HW_RANDOM_AMD=m CONFIG_HW_RANDOM_VIA=m CONFIG_HW_RANDOM_VIRTIO=m CONFIG_NVRAM=m CONFIG_R3964=m CONFIG_APPLICOM=m # # PCMCIA character devices # CONFIG_SYNCLINK_CS=m CONFIG_CARDMAN_4000=m CONFIG_CARDMAN_4040=m CONFIG_IPWIRELESS=m CONFIG_MWAVE=m CONFIG_PC8736x_GPIO=m CONFIG_NSC_GPIO=m CONFIG_RAW_DRIVER=m CONFIG_MAX_RAW_DEVS=256 CONFIG_HPET=y CONFIG_HPET_MMAP=y CONFIG_HANGCHECK_TIMER=m CONFIG_TCG_TPM=m CONFIG_TCG_TIS=m CONFIG_TCG_NSC=m CONFIG_TCG_ATMEL=m CONFIG_TCG_INFINEON=m CONFIG_TELCLOCK=m CONFIG_DEVPORT=y CONFIG_I2C=y CONFIG_I2C_BOARDINFO=y CONFIG_I2C_COMPAT=y CONFIG_I2C_CHARDEV=m # CONFIG_I2C_HELPER_AUTO is not set # # I2C Algorithms # CONFIG_I2C_ALGOBIT=m CONFIG_I2C_ALGOPCF=m CONFIG_I2C_ALGOPCA=m # # I2C Hardware Bus support # # # PC SMBus host controller drivers # CONFIG_I2C_ALI1535=m CONFIG_I2C_ALI1563=m CONFIG_I2C_ALI15X3=m CONFIG_I2C_AMD756=m CONFIG_I2C_AMD756_S4882=m CONFIG_I2C_AMD8111=m CONFIG_I2C_I801=m CONFIG_I2C_ISCH=m CONFIG_I2C_PIIX4=m CONFIG_I2C_NFORCE2=m CONFIG_I2C_NFORCE2_S4985=m CONFIG_I2C_SIS5595=m CONFIG_I2C_SIS630=m CONFIG_I2C_SIS96X=m CONFIG_I2C_VIA=m CONFIG_I2C_VIAPRO=m # # ACPI drivers # CONFIG_I2C_SCMI=m # # I2C system bus drivers (mostly embedded / system-on-chip) # CONFIG_I2C_GPIO=m CONFIG_I2C_OCORES=m CONFIG_I2C_SIMTEC=m # # External I2C/SMBus adapter drivers # CONFIG_I2C_PARPORT=m CONFIG_I2C_PARPORT_LIGHT=m CONFIG_I2C_TAOS_EVM=m CONFIG_I2C_TINY_USB=m # # Graphics adapter I2C/DDC channel drivers # CONFIG_I2C_VOODOO3=m # # Other I2C/SMBus bus drivers # CONFIG_I2C_PCA_PLATFORM=m CONFIG_I2C_STUB=m # # Miscellaneous I2C Chip support # CONFIG_DS1682=m CONFIG_SENSORS_TSL2550=m # CONFIG_I2C_DEBUG_CORE is not set # CONFIG_I2C_DEBUG_ALGO is not set # CONFIG_I2C_DEBUG_BUS is not set # CONFIG_I2C_DEBUG_CHIP is not set CONFIG_SPI=y # CONFIG_SPI_DEBUG is not set CONFIG_SPI_MASTER=y # # SPI Master Controller Drivers # CONFIG_SPI_BITBANG=m CONFIG_SPI_BUTTERFLY=m CONFIG_SPI_GPIO=m CONFIG_SPI_LM70_LLP=m # # SPI Protocol Masters # CONFIG_SPI_SPIDEV=m CONFIG_SPI_TLE62X0=m # # PPS support # CONFIG_PPS=m # CONFIG_PPS_DEBUG is not set CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y CONFIG_GPIOLIB=y # CONFIG_DEBUG_GPIO is not set CONFIG_GPIO_SYSFS=y # # Memory mapped GPIO expanders: # # # I2C GPIO expanders: # CONFIG_GPIO_MAX732X=m CONFIG_GPIO_PCA953X=m CONFIG_GPIO_PCF857X=m CONFIG_GPIO_TWL4030=m CONFIG_GPIO_WM831X=m # # PCI GPIO expanders: # CONFIG_GPIO_LANGWELL=y # # SPI GPIO expanders: # CONFIG_GPIO_MAX7301=m CONFIG_GPIO_MCP23S08=m CONFIG_GPIO_MC33880=m # # AC97 GPIO expanders: # CONFIG_GPIO_UCB1400=y CONFIG_W1=m CONFIG_W1_CON=y # # 1-wire Bus Masters # CONFIG_W1_MASTER_MATROX=m CONFIG_W1_MASTER_DS2490=m CONFIG_W1_MASTER_DS2482=m CONFIG_W1_MASTER_GPIO=m # # 1-wire Slaves # CONFIG_W1_SLAVE_THERM=m CONFIG_W1_SLAVE_SMEM=m CONFIG_W1_SLAVE_DS2431=m CONFIG_W1_SLAVE_DS2433=m # CONFIG_W1_SLAVE_DS2433_CRC is not set CONFIG_W1_SLAVE_DS2760=m CONFIG_W1_SLAVE_BQ27000=m CONFIG_POWER_SUPPLY=y # CONFIG_POWER_SUPPLY_DEBUG is not set CONFIG_PDA_POWER=m CONFIG_WM831X_POWER=m CONFIG_WM8350_POWER=m CONFIG_BATTERY_DS2760=m CONFIG_BATTERY_DS2782=m CONFIG_BATTERY_BQ27x00=m CONFIG_BATTERY_DA9030=m CONFIG_BATTERY_MAX17040=m CONFIG_CHARGER_PCF50633=m CONFIG_HWMON=y CONFIG_HWMON_VID=m # CONFIG_HWMON_DEBUG_CHIP is not set # # Native drivers # CONFIG_SENSORS_ABITUGURU=m CONFIG_SENSORS_ABITUGURU3=m CONFIG_SENSORS_AD7414=m CONFIG_SENSORS_AD7418=m CONFIG_SENSORS_ADCXX=m CONFIG_SENSORS_ADM1021=m CONFIG_SENSORS_ADM1025=m CONFIG_SENSORS_ADM1026=m CONFIG_SENSORS_ADM1029=m CONFIG_SENSORS_ADM1031=m CONFIG_SENSORS_ADM9240=m CONFIG_SENSORS_ADT7462=m CONFIG_SENSORS_ADT7470=m CONFIG_SENSORS_ADT7473=m CONFIG_SENSORS_ADT7475=m CONFIG_SENSORS_K8TEMP=m CONFIG_SENSORS_ASB100=m CONFIG_SENSORS_ATXP1=m CONFIG_SENSORS_DS1621=m CONFIG_SENSORS_I5K_AMB=m CONFIG_SENSORS_F71805F=m CONFIG_SENSORS_F71882FG=m CONFIG_SENSORS_F75375S=m CONFIG_SENSORS_FSCHMD=m CONFIG_SENSORS_G760A=m CONFIG_SENSORS_GL518SM=m CONFIG_SENSORS_GL520SM=m CONFIG_SENSORS_CORETEMP=m CONFIG_SENSORS_IBMAEM=m CONFIG_SENSORS_IBMPEX=m CONFIG_SENSORS_IT87=m CONFIG_SENSORS_LM63=m CONFIG_SENSORS_LM70=m CONFIG_SENSORS_LM75=m CONFIG_SENSORS_LM77=m CONFIG_SENSORS_LM78=m CONFIG_SENSORS_LM80=m CONFIG_SENSORS_LM83=m CONFIG_SENSORS_LM85=m CONFIG_SENSORS_LM87=m CONFIG_SENSORS_LM90=m CONFIG_SENSORS_LM92=m CONFIG_SENSORS_LM93=m CONFIG_SENSORS_LTC4215=m CONFIG_SENSORS_LTC4245=m CONFIG_SENSORS_LM95241=m CONFIG_SENSORS_MAX1111=m CONFIG_SENSORS_MAX1619=m CONFIG_SENSORS_MAX6650=m CONFIG_SENSORS_PC87360=m CONFIG_SENSORS_PC87427=m CONFIG_SENSORS_PCF8591=m CONFIG_SENSORS_SHT15=m CONFIG_SENSORS_SIS5595=m CONFIG_SENSORS_DME1737=m CONFIG_SENSORS_SMSC47M1=m CONFIG_SENSORS_SMSC47M192=m CONFIG_SENSORS_SMSC47B397=m CONFIG_SENSORS_ADS7828=m CONFIG_SENSORS_THMC50=m CONFIG_SENSORS_TMP401=m CONFIG_SENSORS_TMP421=m CONFIG_SENSORS_VIA686A=m CONFIG_SENSORS_VT1211=m CONFIG_SENSORS_VT8231=m CONFIG_SENSORS_W83781D=m CONFIG_SENSORS_W83791D=m CONFIG_SENSORS_W83792D=m CONFIG_SENSORS_W83793=m CONFIG_SENSORS_W83L785TS=m CONFIG_SENSORS_W83L786NG=m CONFIG_SENSORS_W83627HF=m CONFIG_SENSORS_W83627EHF=m CONFIG_SENSORS_WM831X=m CONFIG_SENSORS_WM8350=m CONFIG_SENSORS_HDAPS=m CONFIG_SENSORS_APPLESMC=m # # ACPI drivers # CONFIG_SENSORS_ATK0110=m CONFIG_SENSORS_LIS3LV02D=m CONFIG_THERMAL=y CONFIG_THERMAL_HWMON=y CONFIG_WATCHDOG=y # CONFIG_WATCHDOG_NOWAYOUT is not set # # Watchdog Device Drivers # CONFIG_SOFT_WATCHDOG=m CONFIG_WM831X_WATCHDOG=m CONFIG_WM8350_WATCHDOG=m CONFIG_TWL4030_WATCHDOG=m CONFIG_ACQUIRE_WDT=m CONFIG_ADVANTECH_WDT=m CONFIG_ALIM1535_WDT=m CONFIG_ALIM7101_WDT=m CONFIG_SC520_WDT=m CONFIG_SBC_FITPC2_WATCHDOG=m CONFIG_EUROTECH_WDT=m CONFIG_IB700_WDT=m CONFIG_IBMASR=m CONFIG_WAFER_WDT=m CONFIG_I6300ESB_WDT=m CONFIG_ITCO_WDT=m CONFIG_ITCO_VENDOR_SUPPORT=y CONFIG_IT8712F_WDT=m CONFIG_IT87_WDT=m # CONFIG_HP_WATCHDOG is not set CONFIG_SC1200_WDT=m CONFIG_PC87413_WDT=m CONFIG_60XX_WDT=m CONFIG_SBC8360_WDT=m CONFIG_CPU5_WDT=m CONFIG_SMSC_SCH311X_WDT=m CONFIG_SMSC37B787_WDT=m CONFIG_W83627HF_WDT=m CONFIG_W83697HF_WDT=m CONFIG_W83697UG_WDT=m CONFIG_W83877F_WDT=m CONFIG_W83977F_WDT=m CONFIG_MACHZ_WDT=m CONFIG_SBC_EPX_C3_WATCHDOG=m # # PCI-based Watchdog Cards # CONFIG_PCIPCWATCHDOG=m CONFIG_WDTPCI=m # # USB-based Watchdog Cards # CONFIG_USBPCWATCHDOG=m CONFIG_SSB_POSSIBLE=y # # Sonics Silicon Backplane # CONFIG_SSB=m CONFIG_SSB_SPROM=y CONFIG_SSB_BLOCKIO=y CONFIG_SSB_PCIHOST_POSSIBLE=y CONFIG_SSB_PCIHOST=y CONFIG_SSB_B43_PCI_BRIDGE=y CONFIG_SSB_PCMCIAHOST_POSSIBLE=y # CONFIG_SSB_PCMCIAHOST is not set CONFIG_SSB_SDIOHOST_POSSIBLE=y CONFIG_SSB_SDIOHOST=y # CONFIG_SSB_DEBUG is not set CONFIG_SSB_DRIVER_PCICORE_POSSIBLE=y CONFIG_SSB_DRIVER_PCICORE=y # # Multifunction device drivers # CONFIG_MFD_CORE=m CONFIG_MFD_SM501=m # CONFIG_MFD_SM501_GPIO is not set CONFIG_HTC_PASIC3=m CONFIG_UCB1400_CORE=m CONFIG_TPS65010=m CONFIG_TWL4030_CORE=y # CONFIG_MFD_TMIO is not set CONFIG_PMIC_DA903X=y CONFIG_MFD_WM8400=m CONFIG_MFD_WM831X=m CONFIG_MFD_WM8350=m CONFIG_MFD_WM8350_I2C=m CONFIG_MFD_PCF50633=m CONFIG_MFD_MC13783=m CONFIG_PCF50633_ADC=m CONFIG_PCF50633_GPIO=m CONFIG_AB3100_CORE=m CONFIG_AB3100_OTP=m # CONFIG_EZX_PCAP is not set CONFIG_REGULATOR=y # CONFIG_REGULATOR_DEBUG is not set # CONFIG_REGULATOR_FIXED_VOLTAGE is not set CONFIG_REGULATOR_VIRTUAL_CONSUMER=m CONFIG_REGULATOR_USERSPACE_CONSUMER=m CONFIG_REGULATOR_BQ24022=m CONFIG_REGULATOR_MAX1586=m CONFIG_REGULATOR_TWL4030=y CONFIG_REGULATOR_WM831X=m CONFIG_REGULATOR_WM8350=m CONFIG_REGULATOR_WM8400=m CONFIG_REGULATOR_DA903X=m CONFIG_REGULATOR_PCF50633=m CONFIG_REGULATOR_LP3971=m CONFIG_REGULATOR_MC13783=m CONFIG_REGULATOR_AB3100=m CONFIG_REGULATOR_TPS65023=m CONFIG_REGULATOR_TPS6507X=m CONFIG_MEDIA_SUPPORT=m # # Multimedia core support # CONFIG_VIDEO_DEV=m CONFIG_VIDEO_V4L2_COMMON=m CONFIG_VIDEO_ALLOW_V4L1=y CONFIG_VIDEO_V4L1_COMPAT=y CONFIG_DVB_CORE=m CONFIG_VIDEO_MEDIA=m # # Multimedia drivers # CONFIG_VIDEO_SAA7146=m CONFIG_VIDEO_SAA7146_VV=m CONFIG_MEDIA_ATTACH=y CONFIG_MEDIA_TUNER=m # CONFIG_MEDIA_TUNER_CUSTOMISE is not set CONFIG_MEDIA_TUNER_SIMPLE=m CONFIG_MEDIA_TUNER_TDA8290=m CONFIG_MEDIA_TUNER_TDA827X=m CONFIG_MEDIA_TUNER_TDA18271=m CONFIG_MEDIA_TUNER_TDA9887=m CONFIG_MEDIA_TUNER_TEA5761=m CONFIG_MEDIA_TUNER_TEA5767=m CONFIG_MEDIA_TUNER_MT20XX=m CONFIG_MEDIA_TUNER_MT2060=m CONFIG_MEDIA_TUNER_MT2266=m CONFIG_MEDIA_TUNER_MT2131=m CONFIG_MEDIA_TUNER_QT1010=m CONFIG_MEDIA_TUNER_XC2028=m CONFIG_MEDIA_TUNER_XC5000=m CONFIG_MEDIA_TUNER_MXL5005S=m CONFIG_MEDIA_TUNER_MXL5007T=m CONFIG_MEDIA_TUNER_MC44S803=m CONFIG_VIDEO_V4L2=m CONFIG_VIDEO_V4L1=m CONFIG_VIDEOBUF_GEN=m CONFIG_VIDEOBUF_DMA_SG=m CONFIG_VIDEOBUF_VMALLOC=m CONFIG_VIDEOBUF_DVB=m CONFIG_VIDEO_BTCX=m CONFIG_VIDEO_IR=m CONFIG_VIDEO_TVEEPROM=m CONFIG_VIDEO_TUNER=m CONFIG_VIDEO_CAPTURE_DRIVERS=y # CONFIG_VIDEO_ADV_DEBUG is not set # CONFIG_VIDEO_FIXED_MINOR_RANGES is not set CONFIG_VIDEO_HELPER_CHIPS_AUTO=y CONFIG_VIDEO_IR_I2C=m CONFIG_VIDEO_TVAUDIO=m CONFIG_VIDEO_TDA7432=m CONFIG_VIDEO_TDA9840=m CONFIG_VIDEO_TEA6415C=m CONFIG_VIDEO_TEA6420=m CONFIG_VIDEO_MSP3400=m CONFIG_VIDEO_CS5345=m CONFIG_VIDEO_CS53L32A=m CONFIG_VIDEO_M52790=m CONFIG_VIDEO_WM8775=m CONFIG_VIDEO_WM8739=m CONFIG_VIDEO_VP27SMPX=m CONFIG_VIDEO_SAA6588=m CONFIG_VIDEO_BT819=m CONFIG_VIDEO_BT856=m CONFIG_VIDEO_BT866=m CONFIG_VIDEO_KS0127=m CONFIG_VIDEO_OV7670=m CONFIG_VIDEO_MT9V011=m CONFIG_VIDEO_SAA7110=m CONFIG_VIDEO_SAA711X=m CONFIG_VIDEO_SAA717X=m CONFIG_VIDEO_TVP5150=m CONFIG_VIDEO_VPX3220=m CONFIG_VIDEO_CX25840=m CONFIG_VIDEO_CX2341X=m CONFIG_VIDEO_SAA7127=m CONFIG_VIDEO_SAA7185=m CONFIG_VIDEO_ADV7170=m CONFIG_VIDEO_ADV7175=m CONFIG_VIDEO_UPD64031A=m CONFIG_VIDEO_UPD64083=m CONFIG_VIDEO_VIVI=m CONFIG_VIDEO_BT848=m CONFIG_VIDEO_BT848_DVB=y CONFIG_VIDEO_BWQCAM=m CONFIG_VIDEO_CQCAM=m CONFIG_VIDEO_W9966=m CONFIG_VIDEO_CPIA=m CONFIG_VIDEO_CPIA_PP=m CONFIG_VIDEO_CPIA_USB=m CONFIG_VIDEO_CPIA2=m CONFIG_VIDEO_SAA5246A=m CONFIG_VIDEO_SAA5249=m CONFIG_VIDEO_STRADIS=m CONFIG_VIDEO_ZORAN=m CONFIG_VIDEO_ZORAN_DC30=m CONFIG_VIDEO_ZORAN_ZR36060=m CONFIG_VIDEO_ZORAN_BUZ=m CONFIG_VIDEO_ZORAN_DC10=m CONFIG_VIDEO_ZORAN_LML33=m CONFIG_VIDEO_ZORAN_LML33R10=m CONFIG_VIDEO_ZORAN_AVS6EYES=m CONFIG_VIDEO_MEYE=m CONFIG_VIDEO_SAA7134=m CONFIG_VIDEO_SAA7134_ALSA=m CONFIG_VIDEO_SAA7134_DVB=m CONFIG_VIDEO_MXB=m CONFIG_VIDEO_HEXIUM_ORION=m CONFIG_VIDEO_HEXIUM_GEMINI=m CONFIG_VIDEO_CX88=m CONFIG_VIDEO_CX88_ALSA=m CONFIG_VIDEO_CX88_BLACKBIRD=m CONFIG_VIDEO_CX88_DVB=m CONFIG_VIDEO_CX88_MPEG=m CONFIG_VIDEO_CX88_VP3054=m CONFIG_VIDEO_CX23885=m CONFIG_VIDEO_AU0828=m CONFIG_VIDEO_IVTV=m CONFIG_VIDEO_FB_IVTV=m CONFIG_VIDEO_CX18=m CONFIG_VIDEO_SAA7164=m CONFIG_VIDEO_CAFE_CCIC=m CONFIG_SOC_CAMERA=m CONFIG_SOC_CAMERA_MT9M001=m CONFIG_SOC_CAMERA_MT9M111=m CONFIG_SOC_CAMERA_MT9T031=m CONFIG_SOC_CAMERA_MT9V022=m CONFIG_SOC_CAMERA_TW9910=m CONFIG_SOC_CAMERA_PLATFORM=m CONFIG_SOC_CAMERA_OV772X=m CONFIG_V4L_USB_DRIVERS=y CONFIG_USB_VIDEO_CLASS=m CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y CONFIG_USB_GSPCA=m CONFIG_USB_M5602=m CONFIG_USB_STV06XX=m CONFIG_USB_GL860=m CONFIG_USB_GSPCA_CONEX=m CONFIG_USB_GSPCA_ETOMS=m CONFIG_USB_GSPCA_FINEPIX=m CONFIG_USB_GSPCA_JEILINJ=m CONFIG_USB_GSPCA_MARS=m CONFIG_USB_GSPCA_MR97310A=m CONFIG_USB_GSPCA_OV519=m CONFIG_USB_GSPCA_OV534=m CONFIG_USB_GSPCA_PAC207=m CONFIG_USB_GSPCA_PAC7311=m CONFIG_USB_GSPCA_SN9C20X=m # CONFIG_USB_GSPCA_SN9C20X_EVDEV is not set CONFIG_USB_GSPCA_SONIXB=m CONFIG_USB_GSPCA_SONIXJ=m CONFIG_USB_GSPCA_SPCA500=m CONFIG_USB_GSPCA_SPCA501=m CONFIG_USB_GSPCA_SPCA505=m CONFIG_USB_GSPCA_SPCA506=m CONFIG_USB_GSPCA_SPCA508=m CONFIG_USB_GSPCA_SPCA561=m CONFIG_USB_GSPCA_SQ905=m CONFIG_USB_GSPCA_SQ905C=m CONFIG_USB_GSPCA_STK014=m CONFIG_USB_GSPCA_SUNPLUS=m CONFIG_USB_GSPCA_T613=m CONFIG_USB_GSPCA_TV8532=m CONFIG_USB_GSPCA_VC032X=m CONFIG_USB_GSPCA_ZC3XX=m CONFIG_VIDEO_PVRUSB2=m CONFIG_VIDEO_PVRUSB2_SYSFS=y CONFIG_VIDEO_PVRUSB2_DVB=y # CONFIG_VIDEO_PVRUSB2_DEBUGIFC is not set CONFIG_VIDEO_HDPVR=m CONFIG_VIDEO_EM28XX=m CONFIG_VIDEO_EM28XX_ALSA=m CONFIG_VIDEO_EM28XX_DVB=m CONFIG_VIDEO_CX231XX=m CONFIG_VIDEO_CX231XX_ALSA=m CONFIG_VIDEO_CX231XX_DVB=m CONFIG_VIDEO_USBVISION=m CONFIG_VIDEO_USBVIDEO=m CONFIG_USB_VICAM=m CONFIG_USB_IBMCAM=m CONFIG_USB_KONICAWC=m CONFIG_USB_QUICKCAM_MESSENGER=m CONFIG_USB_ET61X251=m CONFIG_VIDEO_OVCAMCHIP=m CONFIG_USB_W9968CF=m # CONFIG_USB_OV511 is not set CONFIG_USB_SE401=m CONFIG_USB_SN9C102=m CONFIG_USB_STV680=m CONFIG_USB_ZC0301=m CONFIG_USB_PWC=m # CONFIG_USB_PWC_DEBUG is not set CONFIG_USB_PWC_INPUT_EVDEV=y CONFIG_USB_ZR364XX=m CONFIG_USB_STKWEBCAM=m CONFIG_USB_S2255=m CONFIG_RADIO_ADAPTERS=y CONFIG_RADIO_GEMTEK_PCI=m CONFIG_RADIO_MAXIRADIO=m CONFIG_RADIO_MAESTRO=m CONFIG_I2C_SI4713=m CONFIG_RADIO_SI4713=m CONFIG_USB_DSBR=m CONFIG_RADIO_SI470X=y CONFIG_USB_SI470X=m CONFIG_I2C_SI470X=m CONFIG_USB_MR800=m CONFIG_RADIO_TEA5764=m CONFIG_DVB_MAX_ADAPTERS=8 CONFIG_DVB_DYNAMIC_MINORS=y CONFIG_DVB_CAPTURE_DRIVERS=y # # Supported SAA7146 based PCI Adapters # CONFIG_TTPCI_EEPROM=m CONFIG_DVB_AV7110=m CONFIG_DVB_AV7110_OSD=y CONFIG_DVB_BUDGET_CORE=m CONFIG_DVB_BUDGET=m CONFIG_DVB_BUDGET_CI=m CONFIG_DVB_BUDGET_AV=m CONFIG_DVB_BUDGET_PATCH=m # # Supported USB Adapters # CONFIG_DVB_USB=m # CONFIG_DVB_USB_DEBUG is not set CONFIG_DVB_USB_A800=m CONFIG_DVB_USB_DIBUSB_MB=m # CONFIG_DVB_USB_DIBUSB_MB_FAULTY is not set CONFIG_DVB_USB_DIBUSB_MC=m CONFIG_DVB_USB_DIB0700=m CONFIG_DVB_USB_UMT_010=m CONFIG_DVB_USB_CXUSB=m CONFIG_DVB_USB_M920X=m CONFIG_DVB_USB_GL861=m CONFIG_DVB_USB_AU6610=m CONFIG_DVB_USB_DIGITV=m CONFIG_DVB_USB_VP7045=m CONFIG_DVB_USB_VP702X=m CONFIG_DVB_USB_GP8PSK=m CONFIG_DVB_USB_NOVA_T_USB2=m CONFIG_DVB_USB_TTUSB2=m CONFIG_DVB_USB_DTT200U=m CONFIG_DVB_USB_OPERA1=m CONFIG_DVB_USB_AF9005=m CONFIG_DVB_USB_AF9005_REMOTE=m CONFIG_DVB_USB_DW2102=m CONFIG_DVB_USB_CINERGY_T2=m CONFIG_DVB_USB_ANYSEE=m CONFIG_DVB_USB_DTV5100=m CONFIG_DVB_USB_AF9015=m CONFIG_DVB_USB_CE6230=m CONFIG_DVB_USB_FRIIO=m CONFIG_DVB_TTUSB_BUDGET=m CONFIG_DVB_TTUSB_DEC=m CONFIG_SMS_SIANO_MDTV=m # # Siano module components # CONFIG_SMS_USB_DRV=m CONFIG_SMS_SDIO_DRV=m # # Supported FlexCopII (B2C2) Adapters # CONFIG_DVB_B2C2_FLEXCOP=m CONFIG_DVB_B2C2_FLEXCOP_PCI=m CONFIG_DVB_B2C2_FLEXCOP_USB=m # CONFIG_DVB_B2C2_FLEXCOP_DEBUG is not set # # Supported BT878 Adapters # CONFIG_DVB_BT8XX=m # # Supported Pluto2 Adapters # CONFIG_DVB_PLUTO2=m # # Supported SDMC DM1105 Adapters # CONFIG_DVB_DM1105=m # # Supported FireWire (IEEE 1394) Adapters # CONFIG_DVB_FIREDTV=m CONFIG_DVB_FIREDTV_IEEE1394=y CONFIG_DVB_FIREDTV_INPUT=y # # Supported Earthsoft PT1 Adapters # CONFIG_DVB_PT1=m # # Supported DVB Frontends # # CONFIG_DVB_FE_CUSTOMISE is not set CONFIG_DVB_STB0899=m CONFIG_DVB_STB6100=m CONFIG_DVB_CX24110=m CONFIG_DVB_CX24123=m CONFIG_DVB_MT312=m CONFIG_DVB_ZL10036=m CONFIG_DVB_ZL10039=m CONFIG_DVB_S5H1420=m CONFIG_DVB_STV0288=m CONFIG_DVB_STB6000=m CONFIG_DVB_STV0299=m CONFIG_DVB_STV6110=m CONFIG_DVB_STV0900=m CONFIG_DVB_TDA8083=m CONFIG_DVB_TDA10086=m CONFIG_DVB_TDA8261=m CONFIG_DVB_VES1X93=m CONFIG_DVB_TUNER_ITD1000=m CONFIG_DVB_TUNER_CX24113=m CONFIG_DVB_TDA826X=m CONFIG_DVB_TUA6100=m CONFIG_DVB_CX24116=m CONFIG_DVB_SI21XX=m CONFIG_DVB_SP8870=m CONFIG_DVB_SP887X=m CONFIG_DVB_CX22700=m CONFIG_DVB_CX22702=m CONFIG_DVB_L64781=m CONFIG_DVB_TDA1004X=m CONFIG_DVB_NXT6000=m CONFIG_DVB_MT352=m CONFIG_DVB_ZL10353=m CONFIG_DVB_DIB3000MB=m CONFIG_DVB_DIB3000MC=m CONFIG_DVB_DIB7000M=m CONFIG_DVB_DIB7000P=m CONFIG_DVB_TDA10048=m CONFIG_DVB_AF9013=m CONFIG_DVB_VES1820=m CONFIG_DVB_TDA10021=m CONFIG_DVB_TDA10023=m CONFIG_DVB_STV0297=m CONFIG_DVB_NXT200X=m CONFIG_DVB_OR51211=m CONFIG_DVB_OR51132=m CONFIG_DVB_BCM3510=m CONFIG_DVB_LGDT330X=m CONFIG_DVB_LGDT3305=m CONFIG_DVB_S5H1409=m CONFIG_DVB_AU8522=m CONFIG_DVB_S5H1411=m CONFIG_DVB_DIB8000=m CONFIG_DVB_PLL=m CONFIG_DVB_TUNER_DIB0070=m CONFIG_DVB_LNBP21=m CONFIG_DVB_ISL6405=m CONFIG_DVB_ISL6421=m CONFIG_DVB_LGS8GXX=m CONFIG_DAB=y CONFIG_USB_DABUSB=m # # Graphics support # CONFIG_AGP=y CONFIG_AGP_AMD64=y CONFIG_AGP_INTEL=m CONFIG_AGP_SIS=m CONFIG_AGP_VIA=m CONFIG_VGA_ARB=y CONFIG_DRM=m CONFIG_DRM_KMS_HELPER=m CONFIG_DRM_TTM=m CONFIG_DRM_TDFX=m CONFIG_DRM_R128=m CONFIG_DRM_RADEON=m CONFIG_DRM_I810=m CONFIG_DRM_I830=m CONFIG_DRM_I915=m CONFIG_DRM_I915_KMS=y CONFIG_DRM_MGA=m CONFIG_DRM_SIS=m CONFIG_DRM_VIA=m CONFIG_DRM_SAVAGE=m CONFIG_VGASTATE=m CONFIG_VIDEO_OUTPUT_CONTROL=m CONFIG_FB=y CONFIG_FIRMWARE_EDID=y CONFIG_FB_DDC=m # CONFIG_FB_BOOT_VESA_SUPPORT is not set CONFIG_FB_CFB_FILLRECT=y CONFIG_FB_CFB_COPYAREA=y CONFIG_FB_CFB_IMAGEBLIT=y # CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set CONFIG_FB_SYS_FILLRECT=m CONFIG_FB_SYS_COPYAREA=m CONFIG_FB_SYS_IMAGEBLIT=m # CONFIG_FB_FOREIGN_ENDIAN is not set CONFIG_FB_SYS_FOPS=m CONFIG_FB_DEFERRED_IO=y CONFIG_FB_HECUBA=m CONFIG_FB_SVGALIB=m # CONFIG_FB_MACMODES is not set CONFIG_FB_BACKLIGHT=y CONFIG_FB_MODE_HELPERS=y CONFIG_FB_TILEBLITTING=y # # Frame buffer hardware drivers # CONFIG_FB_CIRRUS=m CONFIG_FB_PM2=m CONFIG_FB_PM2_FIFO_DISCONNECT=y CONFIG_FB_CYBER2000=m CONFIG_FB_ARC=m CONFIG_FB_ASILIANT=y CONFIG_FB_IMSTT=y CONFIG_FB_VGA16=m CONFIG_FB_UVESA=m # CONFIG_FB_VESA is not set CONFIG_FB_EFI=y CONFIG_FB_N411=m CONFIG_FB_HGA=m # CONFIG_FB_HGA_ACCEL is not set CONFIG_FB_S1D13XXX=m CONFIG_FB_NVIDIA=m CONFIG_FB_NVIDIA_I2C=y # CONFIG_FB_NVIDIA_DEBUG is not set CONFIG_FB_NVIDIA_BACKLIGHT=y CONFIG_FB_RIVA=m CONFIG_FB_RIVA_I2C=y # CONFIG_FB_RIVA_DEBUG is not set CONFIG_FB_RIVA_BACKLIGHT=y CONFIG_FB_LE80578=m CONFIG_FB_CARILLO_RANCH=m CONFIG_FB_MATROX=m CONFIG_FB_MATROX_MILLENIUM=y CONFIG_FB_MATROX_MYSTIQUE=y CONFIG_FB_MATROX_G=y CONFIG_FB_MATROX_I2C=m CONFIG_FB_MATROX_MAVEN=m CONFIG_FB_RADEON=m CONFIG_FB_RADEON_I2C=y CONFIG_FB_RADEON_BACKLIGHT=y # CONFIG_FB_RADEON_DEBUG is not set CONFIG_FB_ATY128=m CONFIG_FB_ATY128_BACKLIGHT=y CONFIG_FB_ATY=m CONFIG_FB_ATY_CT=y CONFIG_FB_ATY_GENERIC_LCD=y CONFIG_FB_ATY_GX=y CONFIG_FB_ATY_BACKLIGHT=y CONFIG_FB_S3=m CONFIG_FB_SAVAGE=m CONFIG_FB_SAVAGE_I2C=y CONFIG_FB_SAVAGE_ACCEL=y CONFIG_FB_SIS=m CONFIG_FB_SIS_300=y CONFIG_FB_SIS_315=y CONFIG_FB_VIA=m CONFIG_FB_NEOMAGIC=m CONFIG_FB_KYRO=m CONFIG_FB_3DFX=m # CONFIG_FB_3DFX_ACCEL is not set CONFIG_FB_3DFX_I2C=y CONFIG_FB_VOODOO1=m CONFIG_FB_VT8623=m CONFIG_FB_TRIDENT=m CONFIG_FB_ARK=m CONFIG_FB_PM3=m CONFIG_FB_CARMINE=m CONFIG_FB_CARMINE_DRAM_EVAL=y # CONFIG_CARMINE_DRAM_CUSTOM is not set CONFIG_FB_GEODE=y CONFIG_FB_GEODE_LX=m CONFIG_FB_GEODE_GX=m CONFIG_FB_GEODE_GX1=m CONFIG_FB_TMIO=m CONFIG_FB_TMIO_ACCELL=y CONFIG_FB_SM501=m # CONFIG_FB_VIRTUAL is not set CONFIG_XEN_FBDEV_FRONTEND=m CONFIG_FB_METRONOME=m CONFIG_FB_MB862XX=m CONFIG_FB_MB862XX_PCI_GDC=y CONFIG_FB_BROADSHEET=m CONFIG_BACKLIGHT_LCD_SUPPORT=y CONFIG_LCD_CLASS_DEVICE=m CONFIG_LCD_LMS283GF05=m CONFIG_LCD_LTV350QV=m CONFIG_LCD_ILI9320=m CONFIG_LCD_TDO24M=m CONFIG_LCD_VGG2432A4=m CONFIG_LCD_PLATFORM=m CONFIG_BACKLIGHT_CLASS_DEVICE=y CONFIG_BACKLIGHT_GENERIC=m CONFIG_BACKLIGHT_PROGEAR=m CONFIG_BACKLIGHT_CARILLO_RANCH=m CONFIG_BACKLIGHT_DA903X=m CONFIG_BACKLIGHT_MBP_NVIDIA=m CONFIG_BACKLIGHT_SAHARA=m CONFIG_BACKLIGHT_WM831X=m # # Display device support # CONFIG_DISPLAY_SUPPORT=m # # Display hardware drivers # # # Console display driver support # CONFIG_VGA_CONSOLE=y # CONFIG_VGACON_SOFT_SCROLLBACK is not set CONFIG_DUMMY_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE=m # CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set # CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set # CONFIG_FONTS is not set CONFIG_FONT_8x8=y CONFIG_FONT_8x16=y # CONFIG_LOGO is not set CONFIG_SOUND=m CONFIG_SOUND_OSS_CORE=y CONFIG_SOUND_OSS_CORE_PRECLAIM=y CONFIG_SND=m CONFIG_SND_TIMER=m CONFIG_SND_PCM=m CONFIG_SND_HWDEP=m CONFIG_SND_RAWMIDI=m CONFIG_SND_JACK=y CONFIG_SND_SEQUENCER=m CONFIG_SND_SEQ_DUMMY=m CONFIG_SND_OSSEMUL=y CONFIG_SND_MIXER_OSS=m CONFIG_SND_PCM_OSS=m CONFIG_SND_PCM_OSS_PLUGINS=y CONFIG_SND_SEQUENCER_OSS=y CONFIG_SND_HRTIMER=m CONFIG_SND_SEQ_HRTIMER_DEFAULT=y CONFIG_SND_DYNAMIC_MINORS=y CONFIG_SND_SUPPORT_OLD_API=y CONFIG_SND_VERBOSE_PROCFS=y # CONFIG_SND_VERBOSE_PRINTK is not set # CONFIG_SND_DEBUG is not set CONFIG_SND_VMASTER=y CONFIG_SND_DMA_SGBUF=y CONFIG_SND_RAWMIDI_SEQ=m CONFIG_SND_OPL3_LIB_SEQ=m # CONFIG_SND_OPL4_LIB_SEQ is not set # CONFIG_SND_SBAWE_SEQ is not set CONFIG_SND_EMU10K1_SEQ=m CONFIG_SND_MPU401_UART=m CONFIG_SND_OPL3_LIB=m CONFIG_SND_VX_LIB=m CONFIG_SND_AC97_CODEC=m CONFIG_SND_DRIVERS=y CONFIG_SND_PCSP=m CONFIG_SND_DUMMY=m CONFIG_SND_VIRMIDI=m CONFIG_SND_MTPAV=m CONFIG_SND_MTS64=m CONFIG_SND_SERIAL_U16550=m CONFIG_SND_MPU401=m CONFIG_SND_PORTMAN2X4=m CONFIG_SND_AC97_POWER_SAVE=y CONFIG_SND_AC97_POWER_SAVE_DEFAULT=0 CONFIG_SND_SB_COMMON=m CONFIG_SND_SB16_DSP=m CONFIG_SND_PCI=y CONFIG_SND_AD1889=m CONFIG_SND_ALS300=m CONFIG_SND_ALS4000=m CONFIG_SND_ALI5451=m CONFIG_SND_ATIIXP=m CONFIG_SND_ATIIXP_MODEM=m CONFIG_SND_AU8810=m CONFIG_SND_AU8820=m CONFIG_SND_AU8830=m CONFIG_SND_AW2=m CONFIG_SND_AZT3328=m CONFIG_SND_BT87X=m # CONFIG_SND_BT87X_OVERCLOCK is not set CONFIG_SND_CA0106=m CONFIG_SND_CMIPCI=m CONFIG_SND_OXYGEN_LIB=m CONFIG_SND_OXYGEN=m CONFIG_SND_CS4281=m CONFIG_SND_CS46XX=m CONFIG_SND_CS46XX_NEW_DSP=y CONFIG_SND_CS5530=m CONFIG_SND_CS5535AUDIO=m CONFIG_SND_CTXFI=m CONFIG_SND_DARLA20=m CONFIG_SND_GINA20=m CONFIG_SND_LAYLA20=m CONFIG_SND_DARLA24=m CONFIG_SND_GINA24=m CONFIG_SND_LAYLA24=m CONFIG_SND_MONA=m CONFIG_SND_MIA=m CONFIG_SND_ECHO3G=m CONFIG_SND_INDIGO=m CONFIG_SND_INDIGOIO=m CONFIG_SND_INDIGODJ=m CONFIG_SND_INDIGOIOX=m CONFIG_SND_INDIGODJX=m CONFIG_SND_EMU10K1=m CONFIG_SND_EMU10K1X=m CONFIG_SND_ENS1370=m CONFIG_SND_ENS1371=m CONFIG_SND_ES1938=m CONFIG_SND_ES1968=m CONFIG_SND_FM801=m CONFIG_SND_FM801_TEA575X_BOOL=y CONFIG_SND_FM801_TEA575X=m CONFIG_SND_HDA_INTEL=m CONFIG_SND_HDA_HWDEP=y CONFIG_SND_HDA_RECONFIG=y CONFIG_SND_HDA_INPUT_BEEP=y CONFIG_SND_HDA_INPUT_JACK=y CONFIG_SND_HDA_PATCH_LOADER=y CONFIG_SND_HDA_CODEC_REALTEK=y CONFIG_SND_HDA_CODEC_ANALOG=y CONFIG_SND_HDA_CODEC_SIGMATEL=y CONFIG_SND_HDA_CODEC_VIA=y CONFIG_SND_HDA_CODEC_ATIHDMI=y CONFIG_SND_HDA_CODEC_NVHDMI=y CONFIG_SND_HDA_CODEC_INTELHDMI=y CONFIG_SND_HDA_ELD=y CONFIG_SND_HDA_CODEC_CIRRUS=y CONFIG_SND_HDA_CODEC_CONEXANT=y CONFIG_SND_HDA_CODEC_CA0110=y CONFIG_SND_HDA_CODEC_CMEDIA=y CONFIG_SND_HDA_CODEC_SI3054=y CONFIG_SND_HDA_GENERIC=y CONFIG_SND_HDA_POWER_SAVE=y CONFIG_SND_HDA_POWER_SAVE_DEFAULT=0 CONFIG_SND_HDSP=m CONFIG_SND_HDSPM=m CONFIG_SND_HIFIER=m CONFIG_SND_ICE1712=m CONFIG_SND_ICE1724=m CONFIG_SND_INTEL8X0=m CONFIG_SND_INTEL8X0M=m CONFIG_SND_KORG1212=m CONFIG_SND_LX6464ES=m CONFIG_SND_MAESTRO3=m CONFIG_SND_MIXART=m CONFIG_SND_NM256=m CONFIG_SND_PCXHR=m CONFIG_SND_RIPTIDE=m CONFIG_SND_RME32=m CONFIG_SND_RME96=m CONFIG_SND_RME9652=m CONFIG_SND_SONICVIBES=m CONFIG_SND_TRIDENT=m CONFIG_SND_VIA82XX=m CONFIG_SND_VIA82XX_MODEM=m CONFIG_SND_VIRTUOSO=m CONFIG_SND_VX222=m CONFIG_SND_YMFPCI=m CONFIG_SND_SPI=y CONFIG_SND_USB=y CONFIG_SND_USB_AUDIO=m CONFIG_SND_USB_USX2Y=m CONFIG_SND_USB_CAIAQ=m CONFIG_SND_USB_CAIAQ_INPUT=y CONFIG_SND_USB_US122L=m CONFIG_SND_PCMCIA=y CONFIG_SND_VXPOCKET=m CONFIG_SND_PDAUDIOCF=m CONFIG_SND_SOC=m CONFIG_SND_SOC_I2C_AND_SPI=m CONFIG_SND_SOC_ALL_CODECS=m CONFIG_SND_SOC_WM_HUBS=m CONFIG_SND_SOC_AD1836=m CONFIG_SND_SOC_AD1938=m CONFIG_SND_SOC_AD73311=m CONFIG_SND_SOC_AK4104=m CONFIG_SND_SOC_AK4535=m CONFIG_SND_SOC_AK4642=m CONFIG_SND_SOC_CS4270=m CONFIG_SND_SOC_L3=m CONFIG_SND_SOC_PCM3008=m CONFIG_SND_SOC_SPDIF=m CONFIG_SND_SOC_SSM2602=m CONFIG_SND_SOC_TLV320AIC23=m CONFIG_SND_SOC_TLV320AIC26=m CONFIG_SND_SOC_TLV320AIC3X=m CONFIG_SND_SOC_TWL4030=m CONFIG_SND_SOC_UDA134X=m CONFIG_SND_SOC_UDA1380=m CONFIG_SND_SOC_WM8350=m CONFIG_SND_SOC_WM8400=m CONFIG_SND_SOC_WM8510=m CONFIG_SND_SOC_WM8523=m CONFIG_SND_SOC_WM8580=m CONFIG_SND_SOC_WM8728=m CONFIG_SND_SOC_WM8731=m CONFIG_SND_SOC_WM8750=m CONFIG_SND_SOC_WM8753=m CONFIG_SND_SOC_WM8776=m CONFIG_SND_SOC_WM8900=m CONFIG_SND_SOC_WM8903=m CONFIG_SND_SOC_WM8940=m CONFIG_SND_SOC_WM8960=m CONFIG_SND_SOC_WM8961=m CONFIG_SND_SOC_WM8971=m CONFIG_SND_SOC_WM8974=m CONFIG_SND_SOC_WM8988=m CONFIG_SND_SOC_WM8990=m CONFIG_SND_SOC_WM8993=m CONFIG_SND_SOC_WM9081=m CONFIG_SND_SOC_MAX9877=m CONFIG_SOUND_PRIME=m CONFIG_SOUND_OSS=m # CONFIG_SOUND_TRACEINIT is not set CONFIG_SOUND_DMAP=y CONFIG_SOUND_SSCAPE=m CONFIG_SOUND_VMIDI=m CONFIG_SOUND_TRIX=m CONFIG_SOUND_MSS=m CONFIG_SOUND_MPU401=m CONFIG_SOUND_PAS=m CONFIG_SOUND_PSS=m CONFIG_PSS_MIXER=y # CONFIG_PSS_HAVE_BOOT is not set CONFIG_SOUND_SB=m CONFIG_SOUND_YM3812=m CONFIG_SOUND_UART6850=m CONFIG_SOUND_AEDSP16=m CONFIG_SC6600=y CONFIG_SC6600_JOY=y CONFIG_SC6600_CDROM=4 CONFIG_SC6600_CDROMBASE=0 CONFIG_SOUND_KAHLUA=m CONFIG_AC97_BUS=m CONFIG_HID_SUPPORT=y CONFIG_HID=m CONFIG_HIDRAW=y # # USB Input Devices # CONFIG_USB_HID=m CONFIG_HID_PID=y CONFIG_USB_HIDDEV=y # # Special HID drivers # CONFIG_HID_A4TECH=m CONFIG_HID_APPLE=m CONFIG_HID_BELKIN=m CONFIG_HID_CHERRY=m CONFIG_HID_CHICONY=m CONFIG_HID_CYPRESS=m CONFIG_HID_DRAGONRISE=m CONFIG_DRAGONRISE_FF=y CONFIG_HID_EZKEY=m CONFIG_HID_KYE=m CONFIG_HID_GYRATION=m CONFIG_HID_TWINHAN=m CONFIG_HID_KENSINGTON=m CONFIG_HID_LOGITECH=m CONFIG_LOGITECH_FF=y CONFIG_LOGIRUMBLEPAD2_FF=y CONFIG_HID_MICROSOFT=m CONFIG_HID_MONTEREY=m CONFIG_HID_NTRIG=m CONFIG_HID_PANTHERLORD=m CONFIG_PANTHERLORD_FF=y CONFIG_HID_PETALYNX=m CONFIG_HID_SAMSUNG=m CONFIG_HID_SONY=m CONFIG_HID_SUNPLUS=m CONFIG_HID_GREENASIA=m CONFIG_GREENASIA_FF=y CONFIG_HID_SMARTJOYPLUS=m CONFIG_SMARTJOYPLUS_FF=y CONFIG_HID_TOPSEED=m CONFIG_HID_THRUSTMASTER=m CONFIG_THRUSTMASTER_FF=y CONFIG_HID_WACOM=m CONFIG_HID_ZEROPLUS=m CONFIG_ZEROPLUS_FF=y CONFIG_USB_SUPPORT=y CONFIG_USB_ARCH_HAS_HCD=y CONFIG_USB_ARCH_HAS_OHCI=y CONFIG_USB_ARCH_HAS_EHCI=y CONFIG_USB=y # CONFIG_USB_DEBUG is not set # CONFIG_USB_ANNOUNCE_NEW_DEVICES is not set # # Miscellaneous USB options # # CONFIG_USB_DEVICEFS is not set # CONFIG_USB_DEVICE_CLASS is not set # CONFIG_USB_DYNAMIC_MINORS is not set CONFIG_USB_SUSPEND=y # CONFIG_USB_OTG is not set CONFIG_USB_MON=y CONFIG_USB_WUSB=m CONFIG_USB_WUSB_CBAF=m # CONFIG_USB_WUSB_CBAF_DEBUG is not set # # USB Host Controller Drivers # CONFIG_USB_C67X00_HCD=m CONFIG_USB_XHCI_HCD=m # CONFIG_USB_XHCI_HCD_DEBUGGING is not set CONFIG_USB_EHCI_HCD=y CONFIG_USB_EHCI_ROOT_HUB_TT=y CONFIG_USB_EHCI_TT_NEWSCHED=y CONFIG_USB_OXU210HP_HCD=m CONFIG_USB_ISP116X_HCD=m CONFIG_USB_ISP1760_HCD=m CONFIG_USB_ISP1362_HCD=m CONFIG_USB_OHCI_HCD=y # CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set # CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set CONFIG_USB_OHCI_LITTLE_ENDIAN=y CONFIG_USB_UHCI_HCD=y CONFIG_USB_U132_HCD=m CONFIG_USB_SL811_HCD=m CONFIG_USB_SL811_CS=m CONFIG_USB_R8A66597_HCD=m CONFIG_USB_WHCI_HCD=m CONFIG_USB_HWA_HCD=m # CONFIG_USB_GADGET_MUSB_HDRC is not set # # USB Device Class drivers # CONFIG_USB_ACM=m CONFIG_USB_PRINTER=m CONFIG_USB_WDM=m CONFIG_USB_TMC=m # # NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may # # # also be needed; see USB_STORAGE Help for more info # CONFIG_USB_STORAGE=m # CONFIG_USB_STORAGE_DEBUG is not set CONFIG_USB_STORAGE_DATAFAB=m CONFIG_USB_STORAGE_FREECOM=m CONFIG_USB_STORAGE_ISD200=m CONFIG_USB_STORAGE_USBAT=m CONFIG_USB_STORAGE_SDDR09=m CONFIG_USB_STORAGE_SDDR55=m CONFIG_USB_STORAGE_JUMPSHOT=m CONFIG_USB_STORAGE_ALAUDA=m CONFIG_USB_STORAGE_ONETOUCH=m CONFIG_USB_STORAGE_KARMA=m CONFIG_USB_STORAGE_CYPRESS_ATACB=m # CONFIG_USB_LIBUSUAL is not set # # USB Imaging devices # CONFIG_USB_MDC800=m CONFIG_USB_MICROTEK=m # # USB port drivers # CONFIG_USB_USS720=m CONFIG_USB_SERIAL=m CONFIG_USB_EZUSB=y CONFIG_USB_SERIAL_GENERIC=y CONFIG_USB_SERIAL_AIRCABLE=m CONFIG_USB_SERIAL_ARK3116=m CONFIG_USB_SERIAL_BELKIN=m CONFIG_USB_SERIAL_CH341=m CONFIG_USB_SERIAL_WHITEHEAT=m CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m CONFIG_USB_SERIAL_CP210X=m CONFIG_USB_SERIAL_CYPRESS_M8=m CONFIG_USB_SERIAL_EMPEG=m CONFIG_USB_SERIAL_FTDI_SIO=m CONFIG_USB_SERIAL_FUNSOFT=m CONFIG_USB_SERIAL_VISOR=m CONFIG_USB_SERIAL_IPAQ=m CONFIG_USB_SERIAL_IR=m CONFIG_USB_SERIAL_EDGEPORT=m CONFIG_USB_SERIAL_EDGEPORT_TI=m CONFIG_USB_SERIAL_GARMIN=m CONFIG_USB_SERIAL_IPW=m CONFIG_USB_SERIAL_IUU=m CONFIG_USB_SERIAL_KEYSPAN_PDA=m CONFIG_USB_SERIAL_KEYSPAN=m CONFIG_USB_SERIAL_KEYSPAN_MPR=y CONFIG_USB_SERIAL_KEYSPAN_USA28=y CONFIG_USB_SERIAL_KEYSPAN_USA28X=y CONFIG_USB_SERIAL_KEYSPAN_USA28XA=y CONFIG_USB_SERIAL_KEYSPAN_USA28XB=y CONFIG_USB_SERIAL_KEYSPAN_USA19=y CONFIG_USB_SERIAL_KEYSPAN_USA18X=y CONFIG_USB_SERIAL_KEYSPAN_USA19W=y CONFIG_USB_SERIAL_KEYSPAN_USA19QW=y CONFIG_USB_SERIAL_KEYSPAN_USA19QI=y CONFIG_USB_SERIAL_KEYSPAN_USA49W=y CONFIG_USB_SERIAL_KEYSPAN_USA49WLC=y CONFIG_USB_SERIAL_KLSI=m CONFIG_USB_SERIAL_KOBIL_SCT=m CONFIG_USB_SERIAL_MCT_U232=m CONFIG_USB_SERIAL_MOS7720=m CONFIG_USB_SERIAL_MOS7840=m CONFIG_USB_SERIAL_MOTOROLA=m CONFIG_USB_SERIAL_NAVMAN=m CONFIG_USB_SERIAL_PL2303=m CONFIG_USB_SERIAL_OTI6858=m CONFIG_USB_SERIAL_QUALCOMM=m CONFIG_USB_SERIAL_SPCP8X5=m CONFIG_USB_SERIAL_HP4X=m CONFIG_USB_SERIAL_SAFE=m # CONFIG_USB_SERIAL_SAFE_PADDED is not set CONFIG_USB_SERIAL_SIEMENS_MPI=m CONFIG_USB_SERIAL_SIERRAWIRELESS=m CONFIG_USB_SERIAL_SYMBOL=m CONFIG_USB_SERIAL_TI=m CONFIG_USB_SERIAL_CYBERJACK=m CONFIG_USB_SERIAL_XIRCOM=m CONFIG_USB_SERIAL_OPTION=m CONFIG_USB_SERIAL_OMNINET=m CONFIG_USB_SERIAL_OPTICON=m CONFIG_USB_SERIAL_DEBUG=m # # USB Miscellaneous drivers # CONFIG_USB_EMI62=m CONFIG_USB_EMI26=m CONFIG_USB_ADUTUX=m CONFIG_USB_SEVSEG=m CONFIG_USB_RIO500=m CONFIG_USB_LEGOTOWER=m CONFIG_USB_LCD=m CONFIG_USB_BERRY_CHARGE=m CONFIG_USB_LED=m CONFIG_USB_CYPRESS_CY7C63=m CONFIG_USB_CYTHERM=m CONFIG_USB_IDMOUSE=m CONFIG_USB_FTDI_ELAN=m CONFIG_USB_APPLEDISPLAY=m CONFIG_USB_SISUSBVGA=m # CONFIG_USB_SISUSBVGA_CON is not set CONFIG_USB_LD=m CONFIG_USB_TRANCEVIBRATOR=m CONFIG_USB_IOWARRIOR=m CONFIG_USB_TEST=m CONFIG_USB_ISIGHTFW=m CONFIG_USB_VST=m CONFIG_USB_ATM=m CONFIG_USB_SPEEDTOUCH=m CONFIG_USB_CXACRU=m CONFIG_USB_UEAGLEATM=m CONFIG_USB_XUSBATM=m CONFIG_USB_GADGET=m # CONFIG_USB_GADGET_DEBUG is not set # CONFIG_USB_GADGET_DEBUG_FILES is not set # CONFIG_USB_GADGET_DEBUG_FS is not set CONFIG_USB_GADGET_VBUS_DRAW=2 CONFIG_USB_GADGET_SELECTED=y # CONFIG_USB_GADGET_AT91 is not set # CONFIG_USB_GADGET_ATMEL_USBA is not set # CONFIG_USB_GADGET_FSL_USB2 is not set # CONFIG_USB_GADGET_LH7A40X is not set # CONFIG_USB_GADGET_OMAP is not set # CONFIG_USB_GADGET_PXA25X is not set # CONFIG_USB_GADGET_R8A66597 is not set # CONFIG_USB_GADGET_PXA27X is not set # CONFIG_USB_GADGET_S3C_HSOTG is not set # CONFIG_USB_GADGET_IMX is not set # CONFIG_USB_GADGET_S3C2410 is not set # CONFIG_USB_GADGET_M66592 is not set # CONFIG_USB_GADGET_AMD5536UDC is not set # CONFIG_USB_GADGET_FSL_QE is not set # CONFIG_USB_GADGET_CI13XXX is not set # CONFIG_USB_GADGET_NET2280 is not set # CONFIG_USB_GADGET_GOKU is not set # CONFIG_USB_GADGET_LANGWELL is not set CONFIG_USB_GADGET_DUMMY_HCD=y CONFIG_USB_DUMMY_HCD=m CONFIG_USB_GADGET_DUALSPEED=y CONFIG_USB_ZERO=m CONFIG_USB_AUDIO=m CONFIG_USB_ETH=m CONFIG_USB_ETH_RNDIS=y # CONFIG_USB_ETH_EEM is not set CONFIG_USB_GADGETFS=m CONFIG_USB_FILE_STORAGE=m # CONFIG_USB_FILE_STORAGE_TEST is not set CONFIG_USB_G_SERIAL=m CONFIG_USB_MIDI_GADGET=m CONFIG_USB_G_PRINTER=m CONFIG_USB_CDC_COMPOSITE=m # # OTG and related infrastructure # CONFIG_USB_OTG_UTILS=y CONFIG_USB_GPIO_VBUS=m CONFIG_TWL4030_USB=m CONFIG_NOP_USB_XCEIV=m CONFIG_UWB=m CONFIG_UWB_HWA=m CONFIG_UWB_WHCI=m CONFIG_UWB_WLP=m CONFIG_UWB_I1480U=m CONFIG_UWB_I1480U_WLP=m CONFIG_MMC=y # CONFIG_MMC_DEBUG is not set # CONFIG_MMC_UNSAFE_RESUME is not set # # MMC/SD/SDIO Card Drivers # CONFIG_MMC_BLOCK=m CONFIG_MMC_BLOCK_BOUNCE=y CONFIG_SDIO_UART=m # CONFIG_MMC_TEST is not set # # MMC/SD/SDIO Host Controller Drivers # CONFIG_MMC_SDHCI=m CONFIG_MMC_SDHCI_PCI=m CONFIG_MMC_RICOH_MMC=m CONFIG_MMC_SDHCI_PLTFM=m CONFIG_MMC_WBSD=m # CONFIG_MMC_AT91 is not set # CONFIG_MMC_ATMELMCI is not set CONFIG_MMC_TIFM_SD=m CONFIG_MMC_SPI=m CONFIG_MMC_SDRICOH_CS=m CONFIG_MMC_CB710=m CONFIG_MMC_VIA_SDMMC=m CONFIG_MEMSTICK=m # CONFIG_MEMSTICK_DEBUG is not set # # MemoryStick drivers # # CONFIG_MEMSTICK_UNSAFE_RESUME is not set CONFIG_MSPRO_BLOCK=m # # MemoryStick Host Controller Drivers # CONFIG_MEMSTICK_TIFM_MS=m CONFIG_MEMSTICK_JMICRON_38X=m CONFIG_NEW_LEDS=y CONFIG_LEDS_CLASS=m # # LED drivers # CONFIG_LEDS_ALIX2=m CONFIG_LEDS_PCA9532=m CONFIG_LEDS_GPIO=m CONFIG_LEDS_GPIO_PLATFORM=y CONFIG_LEDS_LP3944=m # CONFIG_LEDS_CLEVO_MAIL is not set CONFIG_LEDS_PCA955X=m CONFIG_LEDS_WM831X_STATUS=m CONFIG_LEDS_WM8350=m CONFIG_LEDS_DA903X=m CONFIG_LEDS_DAC124S085=m CONFIG_LEDS_BD2802=m # # LED Triggers # CONFIG_LEDS_TRIGGERS=y CONFIG_LEDS_TRIGGER_TIMER=m CONFIG_LEDS_TRIGGER_HEARTBEAT=m CONFIG_LEDS_TRIGGER_BACKLIGHT=m CONFIG_LEDS_TRIGGER_GPIO=m CONFIG_LEDS_TRIGGER_DEFAULT_ON=m # # iptables trigger is under Netfilter config (LED target) # # CONFIG_ACCESSIBILITY is not set CONFIG_INFINIBAND=m CONFIG_INFINIBAND_USER_MAD=m CONFIG_INFINIBAND_USER_ACCESS=m CONFIG_INFINIBAND_USER_MEM=y CONFIG_INFINIBAND_ADDR_TRANS=y CONFIG_INFINIBAND_MTHCA=m CONFIG_INFINIBAND_MTHCA_DEBUG=y CONFIG_INFINIBAND_IPATH=m CONFIG_INFINIBAND_AMSO1100=m CONFIG_INFINIBAND_AMSO1100_DEBUG=y CONFIG_INFINIBAND_CXGB3=m # CONFIG_INFINIBAND_CXGB3_DEBUG is not set CONFIG_MLX4_INFINIBAND=m # CONFIG_INFINIBAND_NES is not set CONFIG_INFINIBAND_IPOIB=m CONFIG_INFINIBAND_IPOIB_CM=y CONFIG_INFINIBAND_IPOIB_DEBUG=y # CONFIG_INFINIBAND_IPOIB_DEBUG_DATA is not set CONFIG_INFINIBAND_SRP=m CONFIG_INFINIBAND_ISER=m CONFIG_EDAC=y # # Reporting subsystems # # CONFIG_EDAC_DEBUG is not set CONFIG_EDAC_DECODE_MCE=m CONFIG_EDAC_MM_EDAC=m CONFIG_EDAC_AMD64=m # CONFIG_EDAC_AMD64_ERROR_INJECTION is not set CONFIG_EDAC_E752X=m CONFIG_EDAC_I82975X=m CONFIG_EDAC_I3000=m CONFIG_EDAC_I3200=m CONFIG_EDAC_X38=m CONFIG_EDAC_I5400=m CONFIG_EDAC_I5000=m CONFIG_EDAC_I5100=m CONFIG_RTC_LIB=y CONFIG_RTC_CLASS=y CONFIG_RTC_HCTOSYS=y CONFIG_RTC_HCTOSYS_DEVICE="rtc0" # CONFIG_RTC_DEBUG is not set # # RTC interfaces # CONFIG_RTC_INTF_SYSFS=y CONFIG_RTC_INTF_PROC=y CONFIG_RTC_INTF_DEV=y CONFIG_RTC_INTF_DEV_UIE_EMUL=y CONFIG_RTC_DRV_TEST=m # # I2C RTC drivers # CONFIG_RTC_DRV_DS1307=m CONFIG_RTC_DRV_DS1374=m CONFIG_RTC_DRV_DS1672=m CONFIG_RTC_DRV_MAX6900=m CONFIG_RTC_DRV_RS5C372=m CONFIG_RTC_DRV_ISL1208=m CONFIG_RTC_DRV_X1205=m CONFIG_RTC_DRV_PCF8563=m CONFIG_RTC_DRV_PCF8583=m CONFIG_RTC_DRV_M41T80=m CONFIG_RTC_DRV_M41T80_WDT=y CONFIG_RTC_DRV_TWL4030=m CONFIG_RTC_DRV_S35390A=m CONFIG_RTC_DRV_FM3130=m CONFIG_RTC_DRV_RX8581=m CONFIG_RTC_DRV_RX8025=m # # SPI RTC drivers # CONFIG_RTC_DRV_M41T94=m CONFIG_RTC_DRV_DS1305=m CONFIG_RTC_DRV_DS1390=m CONFIG_RTC_DRV_MAX6902=m CONFIG_RTC_DRV_R9701=m CONFIG_RTC_DRV_RS5C348=m CONFIG_RTC_DRV_DS3234=m CONFIG_RTC_DRV_PCF2123=m # # Platform RTC drivers # CONFIG_RTC_DRV_CMOS=y CONFIG_RTC_DRV_DS1286=m CONFIG_RTC_DRV_DS1511=m CONFIG_RTC_DRV_DS1553=m CONFIG_RTC_DRV_DS1742=m CONFIG_RTC_DRV_STK17TA8=m CONFIG_RTC_DRV_M48T86=m CONFIG_RTC_DRV_M48T35=m CONFIG_RTC_DRV_M48T59=m CONFIG_RTC_DRV_BQ4802=m CONFIG_RTC_DRV_V3020=m CONFIG_RTC_DRV_WM831X=m CONFIG_RTC_DRV_WM8350=m CONFIG_RTC_DRV_PCF50633=m CONFIG_RTC_DRV_AB3100=m # # on-CPU RTC drivers # CONFIG_DMADEVICES=y # # DMA Devices # CONFIG_ASYNC_TX_DISABLE_CHANNEL_SWITCH=y CONFIG_INTEL_IOATDMA=m CONFIG_DMA_ENGINE=y # # DMA Clients # CONFIG_NET_DMA=y # CONFIG_ASYNC_TX_DMA is not set # CONFIG_DMATEST is not set CONFIG_DCA=m CONFIG_AUXDISPLAY=y CONFIG_KS0108=m CONFIG_KS0108_PORT=0x378 CONFIG_KS0108_DELAY=2 CONFIG_CFAG12864B=m CONFIG_CFAG12864B_RATE=20 CONFIG_UIO=m CONFIG_UIO_CIF=m CONFIG_UIO_PDRV=m CONFIG_UIO_PDRV_GENIRQ=m CONFIG_UIO_SMX=m CONFIG_UIO_AEC=m CONFIG_UIO_SERCOS3=m CONFIG_UIO_PCI_GENERIC=m # # TI VLYNQ # CONFIG_XEN_BALLOON=y CONFIG_XEN_SCRUB_PAGES=y CONFIG_XEN_DEV_EVTCHN=y CONFIG_XEN_BACKEND=y CONFIG_XEN_NETDEV_BACKEND=y CONFIG_XEN_BLKDEV_BACKEND=y CONFIG_XEN_BLKDEV_TAP=y CONFIG_XEN_BLKBACK_PAGEMAP=y CONFIG_XEN_PCIDEV_BACKEND=y CONFIG_XEN_PCIDEV_BACKEND_VPCI=y # CONFIG_XEN_PCIDEV_BACKEND_PASS is not set # CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set # CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set # CONFIG_XEN_PCIDEV_BE_DEBUG is not set CONFIG_XENFS=y CONFIG_XEN_COMPAT_XENFS=y CONFIG_XEN_SYS_HYPERVISOR=y CONFIG_XEN_PLATFORM_PCI=y CONFIG_XEN_MCE=y CONFIG_XEN_XENBUS_FRONTEND=y CONFIG_XEN_GNTDEV=y CONFIG_XEN_S3=y CONFIG_ACPI_PROCESSOR_XEN=y CONFIG_STAGING=y # CONFIG_STAGING_EXCLUDE_BUILD is not set CONFIG_ET131X=m # CONFIG_ET131X_DEBUG is not set CONFIG_SLICOSS=m CONFIG_VIDEO_GO7007=m CONFIG_VIDEO_GO7007_USB=m CONFIG_VIDEO_GO7007_USB_S2250_BOARD=m CONFIG_VIDEO_GO7007_OV7640=m CONFIG_VIDEO_GO7007_SAA7113=m CONFIG_VIDEO_GO7007_SAA7115=m CONFIG_VIDEO_GO7007_TW9903=m CONFIG_VIDEO_GO7007_UDA1342=m CONFIG_VIDEO_GO7007_SONY_TUNER=m CONFIG_VIDEO_GO7007_TW2804=m CONFIG_VIDEO_CX25821=m CONFIG_VIDEO_CX25821_ALSA=m CONFIG_USB_IP_COMMON=m CONFIG_USB_IP_VHCI_HCD=m CONFIG_USB_IP_HOST=m CONFIG_W35UND=m CONFIG_PRISM2_USB=m CONFIG_ECHO=m CONFIG_POCH=m # CONFIG_OTUS is not set CONFIG_RT2860=m CONFIG_RT2870=m CONFIG_RT3090=m CONFIG_COMEDI=m # CONFIG_COMEDI_DEBUG is not set CONFIG_COMEDI_PCI_DRIVERS=m CONFIG_COMEDI_PCMCIA_DRIVERS=m CONFIG_COMEDI_USB_DRIVERS=m CONFIG_ASUS_OLED=m CONFIG_PANEL=m CONFIG_PANEL_PARPORT=0 CONFIG_PANEL_PROFILE=5 # CONFIG_PANEL_CHANGE_MESSAGE is not set CONFIG_ALTERA_PCIE_CHDMA=m CONFIG_RTL8187SE=m CONFIG_RTL8192SU=m CONFIG_RTL8192E=m CONFIG_TRANZPORT=m # # Android # # # Qualcomm MSM Camera And Video # # # Camera Sensor Selection # CONFIG_INPUT_GPIO=m CONFIG_DST=m # CONFIG_DST_DEBUG is not set CONFIG_POHMELFS=m # CONFIG_POHMELFS_DEBUG is not set CONFIG_POHMELFS_CRYPTO=y CONFIG_B3DFG=m CONFIG_IDE_PHISON=m CONFIG_PLAN9AUTH=m CONFIG_LINE6_USB=m CONFIG_DRM_RADEON_KMS=y CONFIG_USB_SERIAL_QUATECH2=m CONFIG_USB_SERIAL_QUATECH_USB2=m # CONFIG_VT6655 is not set CONFIG_VT6656=m CONFIG_FB_UDL=m CONFIG_HYPERV=m CONFIG_HYPERV_STORAGE=m CONFIG_HYPERV_BLOCK=m CONFIG_HYPERV_NET=m CONFIG_VME_BUS=m # # VME Bridge Drivers # CONFIG_VME_CA91CX42=m CONFIG_VME_TSI148=m # # VME Device Drivers # CONFIG_VME_USER=m # # RAR Register Driver # CONFIG_RAR_REGISTER=m CONFIG_DX_SEP=m CONFIG_IIO=m # CONFIG_IIO_RING_BUFFER is not set # CONFIG_IIO_TRIGGER is not set # # Accelerometers # CONFIG_KXSD9=m CONFIG_LIS3L02DQ=m # # Analog to digital convertors # CONFIG_MAX1363=m # # Light sensors # CONFIG_TSL2561=m # # Triggers - standalone # CONFIG_X86_PLATFORM_DEVICES=y CONFIG_ACER_WMI=m CONFIG_ACERHDF=m CONFIG_ASUS_LAPTOP=m CONFIG_DELL_WMI=m CONFIG_FUJITSU_LAPTOP=m # CONFIG_FUJITSU_LAPTOP_DEBUG is not set CONFIG_HP_WMI=m CONFIG_MSI_LAPTOP=m CONFIG_PANASONIC_LAPTOP=m CONFIG_COMPAL_LAPTOP=m CONFIG_SONY_LAPTOP=m CONFIG_SONYPI_COMPAT=y CONFIG_THINKPAD_ACPI=m CONFIG_THINKPAD_ACPI_DEBUGFACILITIES=y # CONFIG_THINKPAD_ACPI_DEBUG is not set # CONFIG_THINKPAD_ACPI_UNSAFE_LEDS is not set CONFIG_THINKPAD_ACPI_VIDEO=y CONFIG_THINKPAD_ACPI_HOTKEY_POLL=y CONFIG_INTEL_MENLOW=m CONFIG_EEEPC_LAPTOP=m CONFIG_ACPI_WMI=y # CONFIG_ACPI_ASUS is not set CONFIG_TOPSTAR_LAPTOP=m CONFIG_ACPI_TOSHIBA=m # # Firmware Drivers # CONFIG_EDD=y CONFIG_EDD_OFF=y CONFIG_FIRMWARE_MEMMAP=y CONFIG_EFI_VARS=y CONFIG_DELL_RBU=m CONFIG_DCDBAS=m CONFIG_DMIID=y CONFIG_ISCSI_IBFT_FIND=y CONFIG_ISCSI_IBFT=m # # File systems # CONFIG_EXT2_FS=y CONFIG_EXT2_FS_XATTR=y CONFIG_EXT2_FS_POSIX_ACL=y CONFIG_EXT2_FS_SECURITY=y # CONFIG_EXT2_FS_XIP is not set CONFIG_EXT3_FS=y CONFIG_EXT3_DEFAULTS_TO_ORDERED=y CONFIG_EXT3_FS_XATTR=y CONFIG_EXT3_FS_POSIX_ACL=y CONFIG_EXT3_FS_SECURITY=y CONFIG_EXT4_FS=y CONFIG_EXT4_FS_XATTR=y CONFIG_EXT4_FS_POSIX_ACL=y CONFIG_EXT4_FS_SECURITY=y # CONFIG_EXT4_DEBUG is not set CONFIG_JBD=y # CONFIG_JBD_DEBUG is not set CONFIG_JBD2=y # CONFIG_JBD2_DEBUG is not set CONFIG_FS_MBCACHE=y CONFIG_REISERFS_FS=m # CONFIG_REISERFS_CHECK is not set # CONFIG_REISERFS_PROC_INFO is not set CONFIG_REISERFS_FS_XATTR=y CONFIG_REISERFS_FS_POSIX_ACL=y CONFIG_REISERFS_FS_SECURITY=y CONFIG_JFS_FS=m CONFIG_JFS_POSIX_ACL=y CONFIG_JFS_SECURITY=y # CONFIG_JFS_DEBUG is not set CONFIG_JFS_STATISTICS=y CONFIG_FS_POSIX_ACL=y CONFIG_XFS_FS=m CONFIG_XFS_QUOTA=y CONFIG_XFS_POSIX_ACL=y CONFIG_XFS_RT=y # CONFIG_XFS_DEBUG is not set CONFIG_GFS2_FS=m CONFIG_GFS2_FS_LOCKING_DLM=y CONFIG_OCFS2_FS=m CONFIG_OCFS2_FS_O2CB=m CONFIG_OCFS2_FS_USERSPACE_CLUSTER=m CONFIG_OCFS2_FS_STATS=y CONFIG_OCFS2_DEBUG_MASKLOG=y # CONFIG_OCFS2_DEBUG_FS is not set CONFIG_OCFS2_FS_POSIX_ACL=y CONFIG_BTRFS_FS=m CONFIG_BTRFS_FS_POSIX_ACL=y CONFIG_NILFS2_FS=m CONFIG_FILE_LOCKING=y CONFIG_FSNOTIFY=y CONFIG_DNOTIFY=y CONFIG_INOTIFY=y CONFIG_INOTIFY_USER=y CONFIG_QUOTA=y CONFIG_QUOTA_NETLINK_INTERFACE=y # CONFIG_PRINT_QUOTA_WARNING is not set CONFIG_QUOTA_TREE=m CONFIG_QFMT_V1=m CONFIG_QFMT_V2=m CONFIG_QUOTACTL=y CONFIG_AUTOFS_FS=m CONFIG_AUTOFS4_FS=m CONFIG_FUSE_FS=y CONFIG_CUSE=m CONFIG_GENERIC_ACL=y # # Caches # CONFIG_FSCACHE=m # CONFIG_FSCACHE_STATS is not set # CONFIG_FSCACHE_HISTOGRAM is not set # CONFIG_FSCACHE_DEBUG is not set # CONFIG_FSCACHE_OBJECT_LIST is not set CONFIG_CACHEFILES=m # CONFIG_CACHEFILES_DEBUG is not set # CONFIG_CACHEFILES_HISTOGRAM is not set # # CD-ROM/DVD Filesystems # CONFIG_ISO9660_FS=m CONFIG_JOLIET=y CONFIG_ZISOFS=y CONFIG_UDF_FS=m CONFIG_UDF_NLS=y # # DOS/FAT/NT Filesystems # CONFIG_FAT_FS=m CONFIG_MSDOS_FS=m CONFIG_VFAT_FS=m CONFIG_FAT_DEFAULT_CODEPAGE=437 CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1" CONFIG_NTFS_FS=m # CONFIG_NTFS_DEBUG is not set # CONFIG_NTFS_RW is not set # # Pseudo filesystems # CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_PROC_VMCORE=y CONFIG_PROC_SYSCTL=y CONFIG_PROC_PAGE_MONITOR=y CONFIG_SYSFS=y CONFIG_TMPFS=y CONFIG_TMPFS_POSIX_ACL=y CONFIG_HUGETLBFS=y CONFIG_HUGETLB_PAGE=y CONFIG_CONFIGFS_FS=m CONFIG_MISC_FILESYSTEMS=y CONFIG_ADFS_FS=m # CONFIG_ADFS_FS_RW is not set CONFIG_AFFS_FS=m CONFIG_ECRYPT_FS=y CONFIG_HFS_FS=m CONFIG_HFSPLUS_FS=m CONFIG_BEFS_FS=m # CONFIG_BEFS_DEBUG is not set CONFIG_BFS_FS=m CONFIG_EFS_FS=m CONFIG_JFFS2_FS=m CONFIG_JFFS2_FS_DEBUG=0 CONFIG_JFFS2_FS_WRITEBUFFER=y # CONFIG_JFFS2_FS_WBUF_VERIFY is not set # CONFIG_JFFS2_SUMMARY is not set # CONFIG_JFFS2_FS_XATTR is not set CONFIG_JFFS2_COMPRESSION_OPTIONS=y CONFIG_JFFS2_ZLIB=y CONFIG_JFFS2_LZO=y CONFIG_JFFS2_RTIME=y # CONFIG_JFFS2_RUBIN is not set # CONFIG_JFFS2_CMODE_NONE is not set # CONFIG_JFFS2_CMODE_PRIORITY is not set # CONFIG_JFFS2_CMODE_SIZE is not set CONFIG_JFFS2_CMODE_FAVOURLZO=y CONFIG_UBIFS_FS=m CONFIG_UBIFS_FS_XATTR=y # CONFIG_UBIFS_FS_ADVANCED_COMPR is not set CONFIG_UBIFS_FS_LZO=y CONFIG_UBIFS_FS_ZLIB=y # CONFIG_UBIFS_FS_DEBUG is not set CONFIG_CRAMFS=m CONFIG_SQUASHFS=m # CONFIG_SQUASHFS_EMBEDDED is not set CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE=3 CONFIG_VXFS_FS=m CONFIG_MINIX_FS=m CONFIG_OMFS_FS=m CONFIG_HPFS_FS=m CONFIG_QNX4FS_FS=m CONFIG_ROMFS_FS=m CONFIG_ROMFS_BACKED_BY_BLOCK=y # CONFIG_ROMFS_BACKED_BY_MTD is not set # CONFIG_ROMFS_BACKED_BY_BOTH is not set CONFIG_ROMFS_ON_BLOCK=y CONFIG_SYSV_FS=m CONFIG_UFS_FS=m # CONFIG_UFS_FS_WRITE is not set # CONFIG_UFS_DEBUG is not set CONFIG_EXOFS_FS=m # CONFIG_EXOFS_DEBUG is not set CONFIG_NETWORK_FILESYSTEMS=y CONFIG_NFS_FS=m CONFIG_NFS_V3=y CONFIG_NFS_V3_ACL=y CONFIG_NFS_V4=y # CONFIG_NFS_V4_1 is not set # CONFIG_NFS_FSCACHE is not set CONFIG_NFSD=m CONFIG_NFSD_V2_ACL=y CONFIG_NFSD_V3=y CONFIG_NFSD_V3_ACL=y CONFIG_NFSD_V4=y CONFIG_LOCKD=m CONFIG_LOCKD_V4=y CONFIG_EXPORTFS=m CONFIG_NFS_ACL_SUPPORT=m CONFIG_NFS_COMMON=y CONFIG_SUNRPC=m CONFIG_SUNRPC_GSS=m CONFIG_SUNRPC_XPRT_RDMA=m CONFIG_RPCSEC_GSS_KRB5=m CONFIG_RPCSEC_GSS_SPKM3=m CONFIG_SMB_FS=m # CONFIG_SMB_NLS_DEFAULT is not set CONFIG_CIFS=m # CONFIG_CIFS_STATS is not set CONFIG_CIFS_WEAK_PW_HASH=y CONFIG_CIFS_UPCALL=y CONFIG_CIFS_XATTR=y CONFIG_CIFS_POSIX=y # CONFIG_CIFS_DEBUG2 is not set CONFIG_CIFS_DFS_UPCALL=y CONFIG_CIFS_EXPERIMENTAL=y CONFIG_NCP_FS=m CONFIG_NCPFS_PACKET_SIGNING=y CONFIG_NCPFS_IOCTL_LOCKING=y CONFIG_NCPFS_STRONG=y CONFIG_NCPFS_NFS_NS=y CONFIG_NCPFS_OS2_NS=y # CONFIG_NCPFS_SMALLDOS is not set CONFIG_NCPFS_NLS=y CONFIG_NCPFS_EXTRAS=y CONFIG_CODA_FS=m CONFIG_AFS_FS=m # CONFIG_AFS_DEBUG is not set # CONFIG_AFS_FSCACHE is not set CONFIG_9P_FS=m # CONFIG_9P_FSCACHE is not set # # Partition Types # CONFIG_PARTITION_ADVANCED=y CONFIG_ACORN_PARTITION=y # CONFIG_ACORN_PARTITION_CUMANA is not set # CONFIG_ACORN_PARTITION_EESOX is not set CONFIG_ACORN_PARTITION_ICS=y # CONFIG_ACORN_PARTITION_ADFS is not set # CONFIG_ACORN_PARTITION_POWERTEC is not set CONFIG_ACORN_PARTITION_RISCIX=y CONFIG_OSF_PARTITION=y CONFIG_AMIGA_PARTITION=y CONFIG_ATARI_PARTITION=y CONFIG_MAC_PARTITION=y CONFIG_MSDOS_PARTITION=y CONFIG_BSD_DISKLABEL=y CONFIG_MINIX_SUBPARTITION=y CONFIG_SOLARIS_X86_PARTITION=y CONFIG_UNIXWARE_DISKLABEL=y CONFIG_LDM_PARTITION=y # CONFIG_LDM_DEBUG is not set CONFIG_SGI_PARTITION=y CONFIG_ULTRIX_PARTITION=y CONFIG_SUN_PARTITION=y CONFIG_KARMA_PARTITION=y CONFIG_EFI_PARTITION=y CONFIG_SYSV68_PARTITION=y CONFIG_NLS=y CONFIG_NLS_DEFAULT="cp437" CONFIG_NLS_CODEPAGE_437=m CONFIG_NLS_CODEPAGE_737=m CONFIG_NLS_CODEPAGE_775=m CONFIG_NLS_CODEPAGE_850=m CONFIG_NLS_CODEPAGE_852=m CONFIG_NLS_CODEPAGE_855=m CONFIG_NLS_CODEPAGE_857=m CONFIG_NLS_CODEPAGE_860=m CONFIG_NLS_CODEPAGE_861=m CONFIG_NLS_CODEPAGE_862=m CONFIG_NLS_CODEPAGE_863=m CONFIG_NLS_CODEPAGE_864=m CONFIG_NLS_CODEPAGE_865=m CONFIG_NLS_CODEPAGE_866=m CONFIG_NLS_CODEPAGE_869=m CONFIG_NLS_CODEPAGE_936=m CONFIG_NLS_CODEPAGE_950=m CONFIG_NLS_CODEPAGE_932=m CONFIG_NLS_CODEPAGE_949=m CONFIG_NLS_CODEPAGE_874=m CONFIG_NLS_ISO8859_8=m CONFIG_NLS_CODEPAGE_1250=m CONFIG_NLS_CODEPAGE_1251=m CONFIG_NLS_ASCII=m CONFIG_NLS_ISO8859_1=m CONFIG_NLS_ISO8859_2=m CONFIG_NLS_ISO8859_3=m CONFIG_NLS_ISO8859_4=m CONFIG_NLS_ISO8859_5=m CONFIG_NLS_ISO8859_6=m CONFIG_NLS_ISO8859_7=m CONFIG_NLS_ISO8859_9=m CONFIG_NLS_ISO8859_13=m CONFIG_NLS_ISO8859_14=m CONFIG_NLS_ISO8859_15=m CONFIG_NLS_KOI8_R=m CONFIG_NLS_KOI8_U=m CONFIG_NLS_UTF8=m CONFIG_DLM=m # CONFIG_DLM_DEBUG is not set # # Kernel hacking # CONFIG_TRACE_IRQFLAGS_SUPPORT=y CONFIG_PRINTK_TIME=y # CONFIG_ENABLE_WARN_DEPRECATED is not set # CONFIG_ENABLE_MUST_CHECK is not set CONFIG_FRAME_WARN=1024 CONFIG_MAGIC_SYSRQ=y # CONFIG_STRIP_ASM_SYMS is not set CONFIG_UNUSED_SYMBOLS=y CONFIG_DEBUG_FS=y # CONFIG_HEADERS_CHECK is not set CONFIG_DEBUG_KERNEL=y # CONFIG_DEBUG_SHIRQ is not set CONFIG_DETECT_SOFTLOCKUP=y # CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC is not set CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=0 CONFIG_DETECT_HUNG_TASK=y # CONFIG_BOOTPARAM_HUNG_TASK_PANIC is not set CONFIG_BOOTPARAM_HUNG_TASK_PANIC_VALUE=0 CONFIG_SCHED_DEBUG=y CONFIG_SCHEDSTATS=y CONFIG_TIMER_STATS=y # CONFIG_DEBUG_OBJECTS is not set # CONFIG_SLUB_DEBUG_ON is not set # CONFIG_SLUB_STATS is not set # CONFIG_DEBUG_RT_MUTEXES is not set # CONFIG_RT_MUTEX_TESTER is not set # CONFIG_DEBUG_SPINLOCK is not set # CONFIG_DEBUG_MUTEXES is not set # CONFIG_DEBUG_LOCK_ALLOC is not set # CONFIG_PROVE_LOCKING is not set # CONFIG_LOCK_STAT is not set # CONFIG_DEBUG_SPINLOCK_SLEEP is not set # CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set CONFIG_STACKTRACE=y # CONFIG_DEBUG_KOBJECT is not set CONFIG_DEBUG_BUGVERBOSE=y CONFIG_DEBUG_INFO=y # CONFIG_DEBUG_VM is not set # CONFIG_DEBUG_VIRTUAL is not set # CONFIG_DEBUG_WRITECOUNT is not set CONFIG_DEBUG_MEMORY_INIT=y # CONFIG_DEBUG_LIST is not set # CONFIG_DEBUG_SG is not set # CONFIG_DEBUG_NOTIFIERS is not set # CONFIG_DEBUG_CREDENTIALS is not set CONFIG_ARCH_WANT_FRAME_POINTERS=y CONFIG_FRAME_POINTER=y # CONFIG_BOOT_PRINTK_DELAY is not set # CONFIG_RCU_TORTURE_TEST is not set # CONFIG_RCU_CPU_STALL_DETECTOR is not set # CONFIG_KPROBES_SANITY_TEST is not set # CONFIG_BACKTRACE_SELF_TEST is not set # CONFIG_DEBUG_BLOCK_EXT_DEVT is not set # CONFIG_DEBUG_FORCE_WEAK_PER_CPU is not set # CONFIG_LKDTM is not set # CONFIG_FAULT_INJECTION is not set CONFIG_LATENCYTOP=y CONFIG_SYSCTL_SYSCALL_CHECK=y # CONFIG_DEBUG_PAGEALLOC is not set CONFIG_USER_STACKTRACE_SUPPORT=y CONFIG_NOP_TRACER=y CONFIG_HAVE_FTRACE_NMI_ENTER=y CONFIG_HAVE_FUNCTION_TRACER=y CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y CONFIG_HAVE_FUNCTION_GRAPH_FP_TEST=y CONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=y CONFIG_HAVE_DYNAMIC_FTRACE=y CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y CONFIG_HAVE_SYSCALL_TRACEPOINTS=y CONFIG_RING_BUFFER=y CONFIG_FTRACE_NMI_ENTER=y CONFIG_EVENT_TRACING=y CONFIG_CONTEXT_SWITCH_TRACER=y CONFIG_RING_BUFFER_ALLOW_SWAP=y CONFIG_TRACING=y CONFIG_GENERIC_TRACER=y CONFIG_TRACING_SUPPORT=y CONFIG_FTRACE=y CONFIG_FUNCTION_TRACER=y CONFIG_FUNCTION_GRAPH_TRACER=y # CONFIG_IRQSOFF_TRACER is not set # CONFIG_SYSPROF_TRACER is not set # CONFIG_SCHED_TRACER is not set # CONFIG_FTRACE_SYSCALLS is not set # CONFIG_BOOT_TRACER is not set CONFIG_BRANCH_PROFILE_NONE=y # CONFIG_PROFILE_ANNOTATED_BRANCHES is not set # CONFIG_PROFILE_ALL_BRANCHES is not set # CONFIG_POWER_TRACER is not set # CONFIG_STACK_TRACER is not set # CONFIG_KMEMTRACE is not set # CONFIG_WORKQUEUE_TRACER is not set CONFIG_BLK_DEV_IO_TRACE=y CONFIG_DYNAMIC_FTRACE=y # CONFIG_FUNCTION_PROFILER is not set CONFIG_FTRACE_MCOUNT_RECORD=y # CONFIG_FTRACE_STARTUP_TEST is not set CONFIG_MMIOTRACE=y # CONFIG_MMIOTRACE_TEST is not set # CONFIG_RING_BUFFER_BENCHMARK is not set # CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set # CONFIG_FIREWIRE_OHCI_REMOTE_DMA is not set # CONFIG_DYNAMIC_DEBUG is not set # CONFIG_DMA_API_DEBUG is not set # CONFIG_SAMPLES is not set CONFIG_HAVE_ARCH_KGDB=y CONFIG_KGDB=y CONFIG_KGDB_SERIAL_CONSOLE=y # CONFIG_KGDB_TESTS is not set CONFIG_HAVE_ARCH_KMEMCHECK=y CONFIG_STRICT_DEVMEM=y # CONFIG_X86_VERBOSE_BOOTUP is not set CONFIG_EARLY_PRINTK=y # CONFIG_EARLY_PRINTK_DBGP is not set # CONFIG_DEBUG_STACKOVERFLOW is not set # CONFIG_DEBUG_STACK_USAGE is not set # CONFIG_DEBUG_PER_CPU_MAPS is not set # CONFIG_X86_PTDUMP is not set CONFIG_DEBUG_RODATA=y # CONFIG_DEBUG_RODATA_TEST is not set # CONFIG_DEBUG_NX_TEST is not set # CONFIG_IOMMU_DEBUG is not set # CONFIG_IOMMU_STRESS is not set CONFIG_HAVE_MMIOTRACE_SUPPORT=y CONFIG_IO_DELAY_TYPE_0X80=0 CONFIG_IO_DELAY_TYPE_0XED=1 CONFIG_IO_DELAY_TYPE_UDELAY=2 CONFIG_IO_DELAY_TYPE_NONE=3 # CONFIG_IO_DELAY_0X80 is not set CONFIG_IO_DELAY_0XED=y # CONFIG_IO_DELAY_UDELAY is not set # CONFIG_IO_DELAY_NONE is not set CONFIG_DEFAULT_IO_DELAY_TYPE=1 # CONFIG_DEBUG_BOOT_PARAMS is not set # CONFIG_CPA_DEBUG is not set CONFIG_OPTIMIZE_INLINING=y # # Security options # CONFIG_KEYS=y # CONFIG_KEYS_DEBUG_PROC_KEYS is not set CONFIG_SECURITY=y CONFIG_SECURITYFS=y CONFIG_SECURITY_NETWORK=y # CONFIG_SECURITY_NETWORK_XFRM is not set CONFIG_SECURITY_PATH=y CONFIG_SECURITY_FILE_CAPABILITIES=y # CONFIG_SECURITY_ROOTPLUG is not set CONFIG_LSM_MMAP_MIN_ADDR=0 CONFIG_SECURITY_SELINUX=y CONFIG_SECURITY_SELINUX_BOOTPARAM=y CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=0 CONFIG_SECURITY_SELINUX_DISABLE=y CONFIG_SECURITY_SELINUX_DEVELOP=y CONFIG_SECURITY_SELINUX_AVC_STATS=y CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE=1 # CONFIG_SECURITY_SELINUX_POLICYDB_VERSION_MAX is not set CONFIG_SECURITY_SMACK=y CONFIG_SECURITY_TOMOYO=y # CONFIG_IMA is not set CONFIG_XOR_BLOCKS=m CONFIG_ASYNC_CORE=m CONFIG_ASYNC_MEMCPY=m CONFIG_ASYNC_XOR=m CONFIG_ASYNC_PQ=m CONFIG_ASYNC_RAID6_RECOV=m CONFIG_ASYNC_TX_DISABLE_PQ_VAL_DMA=y CONFIG_ASYNC_TX_DISABLE_XOR_VAL_DMA=y CONFIG_CRYPTO=y # # Crypto core or helper # CONFIG_CRYPTO_FIPS=y CONFIG_CRYPTO_ALGAPI=y CONFIG_CRYPTO_ALGAPI2=y CONFIG_CRYPTO_AEAD=m CONFIG_CRYPTO_AEAD2=y CONFIG_CRYPTO_BLKCIPHER=y CONFIG_CRYPTO_BLKCIPHER2=y CONFIG_CRYPTO_HASH=y CONFIG_CRYPTO_HASH2=y CONFIG_CRYPTO_RNG=m CONFIG_CRYPTO_RNG2=y CONFIG_CRYPTO_PCOMP=y CONFIG_CRYPTO_MANAGER=y CONFIG_CRYPTO_MANAGER2=y CONFIG_CRYPTO_GF128MUL=m CONFIG_CRYPTO_NULL=m CONFIG_CRYPTO_WORKQUEUE=y CONFIG_CRYPTO_CRYPTD=m CONFIG_CRYPTO_AUTHENC=m CONFIG_CRYPTO_TEST=m # # Authenticated Encryption with Associated Data # CONFIG_CRYPTO_CCM=m CONFIG_CRYPTO_GCM=m CONFIG_CRYPTO_SEQIV=m # # Block modes # CONFIG_CRYPTO_CBC=y CONFIG_CRYPTO_CTR=m CONFIG_CRYPTO_CTS=m CONFIG_CRYPTO_ECB=y CONFIG_CRYPTO_LRW=m CONFIG_CRYPTO_PCBC=m CONFIG_CRYPTO_XTS=m CONFIG_CRYPTO_FPU=m # # Hash modes # CONFIG_CRYPTO_HMAC=y CONFIG_CRYPTO_XCBC=m CONFIG_CRYPTO_VMAC=m # # Digest # CONFIG_CRYPTO_CRC32C=m CONFIG_CRYPTO_CRC32C_INTEL=m CONFIG_CRYPTO_GHASH=m CONFIG_CRYPTO_MD4=m CONFIG_CRYPTO_MD5=y CONFIG_CRYPTO_MICHAEL_MIC=m CONFIG_CRYPTO_RMD128=m CONFIG_CRYPTO_RMD160=m CONFIG_CRYPTO_RMD256=m CONFIG_CRYPTO_RMD320=m CONFIG_CRYPTO_SHA1=m CONFIG_CRYPTO_SHA256=m CONFIG_CRYPTO_SHA512=m CONFIG_CRYPTO_TGR192=m CONFIG_CRYPTO_WP512=m # # Ciphers # CONFIG_CRYPTO_AES=m CONFIG_CRYPTO_AES_X86_64=m CONFIG_CRYPTO_AES_NI_INTEL=m CONFIG_CRYPTO_ANUBIS=m CONFIG_CRYPTO_ARC4=m CONFIG_CRYPTO_BLOWFISH=m CONFIG_CRYPTO_CAMELLIA=m CONFIG_CRYPTO_CAST5=m CONFIG_CRYPTO_CAST6=m CONFIG_CRYPTO_DES=m CONFIG_CRYPTO_FCRYPT=m CONFIG_CRYPTO_KHAZAD=m CONFIG_CRYPTO_SALSA20=m CONFIG_CRYPTO_SALSA20_X86_64=m CONFIG_CRYPTO_SEED=m CONFIG_CRYPTO_SERPENT=m CONFIG_CRYPTO_TEA=m CONFIG_CRYPTO_TWOFISH=m CONFIG_CRYPTO_TWOFISH_COMMON=m CONFIG_CRYPTO_TWOFISH_X86_64=m # # Compression # CONFIG_CRYPTO_DEFLATE=m CONFIG_CRYPTO_ZLIB=m CONFIG_CRYPTO_LZO=m # # Random Number Generation # CONFIG_CRYPTO_ANSI_CPRNG=m CONFIG_CRYPTO_HW=y CONFIG_CRYPTO_DEV_PADLOCK=y CONFIG_CRYPTO_DEV_PADLOCK_AES=m CONFIG_CRYPTO_DEV_PADLOCK_SHA=m CONFIG_CRYPTO_DEV_HIFN_795X=m CONFIG_CRYPTO_DEV_HIFN_795X_RNG=y CONFIG_HAVE_KVM=y CONFIG_HAVE_KVM_IRQCHIP=y CONFIG_HAVE_KVM_EVENTFD=y CONFIG_KVM_APIC_ARCHITECTURE=y CONFIG_VIRTUALIZATION=y CONFIG_KVM=m CONFIG_KVM_INTEL=m CONFIG_KVM_AMD=m CONFIG_VIRTIO=y CONFIG_VIRTIO_RING=y CONFIG_VIRTIO_PCI=y CONFIG_VIRTIO_BALLOON=m CONFIG_BINARY_PRINTF=y # # Library routines # CONFIG_BITREVERSE=y CONFIG_GENERIC_FIND_FIRST_BIT=y CONFIG_GENERIC_FIND_NEXT_BIT=y CONFIG_GENERIC_FIND_LAST_BIT=y CONFIG_CRC_CCITT=m CONFIG_CRC16=y CONFIG_CRC_T10DIF=y CONFIG_CRC_ITU_T=m CONFIG_CRC32=y CONFIG_CRC7=m CONFIG_LIBCRC32C=m CONFIG_ZLIB_INFLATE=y CONFIG_ZLIB_DEFLATE=m CONFIG_LZO_COMPRESS=m CONFIG_LZO_DECOMPRESS=m CONFIG_DECOMPRESS_GZIP=y CONFIG_DECOMPRESS_BZIP2=y CONFIG_DECOMPRESS_LZMA=y CONFIG_GENERIC_ALLOCATOR=y CONFIG_REED_SOLOMON=m CONFIG_REED_SOLOMON_DEC16=y CONFIG_TEXTSEARCH=y CONFIG_TEXTSEARCH_KMP=m CONFIG_TEXTSEARCH_BM=m CONFIG_TEXTSEARCH_FSM=m CONFIG_HAS_IOMEM=y CONFIG_HAS_IOPORT=y CONFIG_HAS_DMA=y CONFIG_CHECK_SIGNATURE=y CONFIG_NLATTR=y [-- 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] 32+ messages in thread
* Re: Re: [Xen-users] xen/stable-2.6.32.x compilation failure in do_hvm_suspend() 2010-05-14 18:53 ` Pierre POMES @ 2010-05-14 19:15 ` Pasi Kärkkäinen 2010-05-14 19:43 ` [Xen-devel] " Pierre POMES 0 siblings, 1 reply; 32+ messages in thread From: Pasi Kärkkäinen @ 2010-05-14 19:15 UTC (permalink / raw) To: Pierre POMES; +Cc: Xen-Devel List, chris, Xen-Users List On Fri, May 14, 2010 at 02:53:19PM -0400, Pierre POMES wrote: > Le 2010-05-14 14:51, Pasi Kärkkäinen a écrit : >> >> Can you please post the working .config ? >> >> -- Pasi >> >> > > Here it is ! > Thanks, Here are the changes between the .config files. First is .config by Pierre, second is mine (which doesn't build): diff -u config-2.6.32.12-it-xen config-2.6.32.10-pvops-dom0-xen-stable-x86_64 | grep XEN CONFIG_XEN=y CONFIG_XEN_MAX_DOMAIN_MEMORY=32 CONFIG_XEN_SAVE_RESTORE=y -# CONFIG_XEN_DEBUG_FS is not set +CONFIG_XEN_DEBUG_FS=y CONFIG_SWIOTLB_XEN=y CONFIG_MICROCODE_XEN=y CONFIG_XEN_DOM0=y CONFIG_PCI_XEN=y -CONFIG_XEN_PCIDEV_FRONTEND=y +CONFIG_XEN_PCIDEV_FRONTEND=m CONFIG_XEN_BLKDEV_FRONTEND=m CONFIG_XEN_NETDEV_FRONTEND=m CONFIG_XEN_KBDDEV_FRONTEND=m CONFIG_XEN_FBDEV_FRONTEND=m CONFIG_XEN_BALLOON=y CONFIG_XEN_SCRUB_PAGES=y -CONFIG_XEN_DEV_EVTCHN=y +CONFIG_XEN_DEV_EVTCHN=m CONFIG_XEN_BACKEND=y CONFIG_XEN_NETDEV_BACKEND=y CONFIG_XEN_BLKDEV_BACKEND=y -CONFIG_XEN_BLKDEV_TAP=y +CONFIG_XEN_BLKDEV_TAP=m CONFIG_XEN_BLKBACK_PAGEMAP=y -CONFIG_XEN_PCIDEV_BACKEND=y +CONFIG_XEN_PCIDEV_BACKEND=m CONFIG_XEN_PCIDEV_BACKEND_VPCI=y # CONFIG_XEN_PCIDEV_BACKEND_PASS is not set # CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set # CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set # CONFIG_XEN_PCIDEV_BE_DEBUG is not set -CONFIG_XENFS=y +CONFIG_XENFS=m CONFIG_XEN_COMPAT_XENFS=y CONFIG_XEN_SYS_HYPERVISOR=y -CONFIG_XEN_PLATFORM_PCI=y -CONFIG_XEN_MCE=y -CONFIG_XEN_XENBUS_FRONTEND=y -CONFIG_XEN_GNTDEV=y -CONFIG_XEN_S3=y -CONFIG_ACPI_PROCESSOR_XEN=y +CONFIG_XEN_XENBUS_FRONTEND=m +CONFIG_XEN_GNTDEV=m So it seems I have more stuff as modules.. while Pierre has them statically built-in. I guess that's causing the problem? Or did I overlook something? -- Pasi ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [Xen-devel] Re: xen/stable-2.6.32.x compilation failure in do_hvm_suspend() 2010-05-14 19:15 ` Pasi Kärkkäinen @ 2010-05-14 19:43 ` Pierre POMES 0 siblings, 0 replies; 32+ messages in thread From: Pierre POMES @ 2010-05-14 19:43 UTC (permalink / raw) To: Pasi Kärkkäinen; +Cc: Xen-Devel List, chris, Xen-Users List Le 2010-05-14 15:15, Pasi Kärkkäinen a écrit : > So it seems I have more stuff as modules.. while Pierre has them statically built-in. > I guess that's causing the problem? Or did I overlook something? > Yes I did not take a chance and I compiled all statically to have no initrd problem. You also have XEN_DEBUG_FS, but it should not hurt. If I remember well, the error is: drivers/built-in.o: In function `do_hvm_suspend': /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: undefined reference to `xenbus_suspend' /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: undefined reference to `xenbus_resume' These 2 functions are in drivers/xen/xenbus/xenbus_probe_frontend.c, and you have : CONFIG_XEN_XENBUS_FRONTEND=m On my side, I have: CONFIG_XEN_XENBUS_FRONTEND=y I think this could explain. There is a maybe a dependency problem in CONFIG_*: - the code here (where the compilation fails) is for CONFIG_PM_SLEEP: have a look at the code in drivers/xen/manage.c, the section is in a "#ifdef CONFIG_PM_SLEEP" section. - So if CONFIG_PM_SLEEP is set, CONFIG_XEN_XENBUS_FRONTEND should be compiled statically, and should not be set as a module in config kernel (make menuconfig bug ?) Am I wrong ? Maybe ! I am not a kernel hacker ! Pierre ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [Xen-users] RE: Xen4 / Intel DX58SO Mobo / VT-d not working [not found] ` <AANLkTimKlhHnJ70MSbtniRbj6EirU-0BnT259Smgv_rb@mail.gmail.com> 2010-05-13 18:10 ` [Xen-users] xen/stable-2.6.32.x compilation failure in do_hvm_suspend() Pasi Kärkkäinen @ 2010-05-13 18:28 ` chris 2010-05-14 19:05 ` chris 1 sibling, 1 reply; 32+ messages in thread From: chris @ 2010-05-13 18:28 UTC (permalink / raw) To: Pasi Kärkkäinen; +Cc: Xen-Devel List, Xen-Users List [-- Attachment #1: Type: text/plain, Size: 26202 bytes --] Forwarding to xen-devel. Can't seem to get VT-d working with xen4 from tarball on xen.org 2.6.31.13 pv_ops dom0. On pasi's advice I tried switching to stable/2.6.32.x branch for dom0 and that doesnt even build. Did something change recently thats breaking compilation? Attached is xen dmesg with iommu=verbose loglvl=all guest_loglvl=all, and dom0 dmesg from 2.6.31.x Any ideas on why VT-d is not working on this board? Initialization looks good, xen reports hvm_directio capability, everything says VT-d should work until domain is created. Any ideas why stable/2.6.32.x wont build? - chris On Thu, May 13, 2010 at 2:07 PM, chris <tknchris@gmail.com> wrote: > I redid it with oldconfig which I didn't think would help and same > thing. I guess this tree is broken? Can someone else try and see if > they can build it? Ugh, whata day :) > > On Thu, May 13, 2010 at 1:58 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >> On Thu, May 13, 2010 at 01:55:25PM -0400, chris wrote: >>> I used the default config on the wiki which you created. Steps I took were: >>> >>> # make clean distclean >>> # wget -O .config >>> "http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.10-pvops-dom0-xen-stable-x86_64" >> >> You should do "make oldconfig" at this point. >> >>> # make -j8 bzImage >>> (blah blah) >>> LD vmlinux.o >>> MODPOST vmlinux.o >>> WARNING: modpost: Found 7 section mismatch(es). >>> To see full details build your kernel with: >>> 'make CONFIG_DEBUG_SECTION_MISMATCH=y' >>> GEN .version >>> CHK include/linux/compile.h >>> UPD include/linux/compile.h >>> CC init/version.o >>> LD init/built-in.o >>> LD .tmp_vmlinux1 >>> drivers/built-in.o: In function `do_hvm_suspend': >>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: undefined reference >>> to `xenbus_suspend' >>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: undefined reference >>> to `xenbus_resume' >>> make: *** [.tmp_vmlinux1] Error 1 >>> >> >> Hmm.. weird. I wonder if something has changed recently or what's going on in here.. >> >> -- Pasi >> >>> >>> On Thu, May 13, 2010 at 11:47 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>> > On Thu, May 13, 2010 at 11:33:57AM -0400, chris wrote: >>> >> Successfully grabbed the sources and failed to build: >>> >> >>> >> LD .tmp_vmlinux1 >>> >> drivers/built-in.o: In function `do_hvm_suspend': >>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: undefined reference >>> >> to `xenbus_suspend' >>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: undefined reference >>> >> to `xenbus_resume' >>> >> make: *** [.tmp_vmlinux1] Error 1 >>> >> >>> >> :( >>> >> >>> > >>> > Try the example .config files provided on the wiki page. >>> > >>> > -- Pasi >>> > >>> >> On Thu, May 13, 2010 at 10:14 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>> >> > On Thu, May 13, 2010 at 10:12:56AM -0400, chris wrote: >>> >> >> Pasi, >>> >> >> >>> >> >> How do I pull those kernel sources you referenced? I see it mentioned >>> >> >> on http://wiki.xensource.com/xenwiki/XenParavirtOps but no details on >>> >> >> how to retrieve it. >>> >> >> >>> >> > >>> >> > The instructions are there if you read it carefully.. >>> >> > There's the topic of how to switch branches. >>> >> > >>> >> > -- Pasi >>> >> > >>> >> >> - chris >>> >> >> >>> >> >> On Thu, May 13, 2010 at 8:29 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>> >> >> > On Wed, May 12, 2010 at 08:41:34PM -0400, chris wrote: >>> >> >> >> When reading the vtdhowto I noticed the ability to set iommu=verbose. >>> >> >> >> Here is that output, I don't know if it helps at all to figure out >>> >> >> >> what is wrong. >>> >> >> >> >>> >> >> > >>> >> >> > That seems to be OK: >>> >> >> > >>> >> >> > (XEN) I/O virtualisation enabled >>> >> >> > (XEN) I/O virtualisation for PV guests disabled >>> >> >> > >>> >> >> > So hmm.. I wonder if it's related to MSI stuff? >>> >> >> > You could try xen.git xen/stable-2.6.32.x branch instead and see if that makes a difference.. >>> >> >> > >>> >> >> > -- Pasi >>> >> >> > >>> >> >> >> >>> >> >> >> ---------- Forwarded message ---------- >>> >> >> >> From: chris <tknchris@gmail.com> >>> >> >> >> Date: Wed, May 12, 2010 at 5:28 PM >>> >> >> >> Subject: Xen4 / Intel DX58SO Mobo / VT-d not working >>> >> >> >> To: Xen-Users List <xen-users@lists.xensource.com> >>> >> >> >> >>> >> >> >> >>> >> >> >> Hello, >>> >> >> >> >>> >> >> >> I've previously been successful with Xen4 and VT-d on other systems. I >>> >> >> >> am having trouble getting VT-d passthrough working to a WinXP domain >>> >> >> >> with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is enabled in bios, >>> >> >> >> xm info shows hvm_directio capability, I have iommu=1 set, I have the >>> >> >> >> devices bound to pciback on dom0 cmdline, xm >>> >> >> >> pci-list-assignable-devices shows the devices as assignable. When I >>> >> >> >> attempt to start the VM I get the error: >>> >> >> >> >>> >> >> >> Error: Failed to assign device to IOMMU >>> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>> >> >> >> >>> >> >> >> Below is all the information I can think of that would be useful to >>> >> >> >> help debug it: >>> >> >> >> >>> >> >> >> BIOS VT-d Enabled: >>> >> >> >> http://i43.tinypic.com/nl3a5e.jpg >>> >> >> >> http://i42.tinypic.com/nqvlu1.jpg >>> >> >> >> >>> >> >> >> grub entry: >>> >> >> >> >>> >> >> >> title Xen 4.0.0 / Debian GNU/Linux, kernel 2.6.31.13 >>> >> >> >> root (hd0,0) >>> >> >> >> kernel /boot/xen-4.0.0.gz iommu=1 dom0_mem=256M >>> >> >> >> dom0_max_vcpus=1 dom0_vcpus_pin=true >>> >> >> >> module /boot/vmlinuz-2.6.31.13 root=/dev/md0 ro console=tty0 >>> >> >> >> xen-pciback.permissive >>> >> >> >> xen-pciback.hide=(02:00.0)(02:00.1)(02:00.2)(04:00.0)(04:00.1)(04:00.2)(07:00.0)(07:00.1)(07:00.2)(09:00.0)(09:00.1)(09:00.2) >>> >> >> >> module /boot/initrd.img-2.6.31.13 >>> >> >> >> >>> >> >> >> # xm pci-list-assignable-devices >>> >> >> >> 0000:09:00.0 >>> >> >> >> 0000:09:00.1 >>> >> >> >> 0000:09:00.2 >>> >> >> >> 0000:07:00.0 >>> >> >> >> 0000:07:00.1 >>> >> >> >> 0000:07:00.2 >>> >> >> >> 0000:04:00.0 >>> >> >> >> 0000:04:00.1 >>> >> >> >> 0000:04:00.2 >>> >> >> >> 0000:02:00.0 >>> >> >> >> 0000:02:00.1 >>> >> >> >> 0000:02:00.2 >>> >> >> >> >>> >> >> >> # xm info >>> >> >> >> host : test-box2 >>> >> >> >> release : 2.6.31.13 >>> >> >> >> version : #2 SMP Wed May 12 14:11:37 EDT 2010 >>> >> >> >> machine : x86_64 >>> >> >> >> nr_cpus : 8 >>> >> >> >> nr_nodes : 1 >>> >> >> >> cores_per_socket : 4 >>> >> >> >> threads_per_core : 2 >>> >> >> >> cpu_mhz : 2800 >>> >> >> >> hw_caps : >>> >> >> >> bfebfbff:28100800:00000000:00001b40:0098e3bd:00000000:00000001:00000000 >>> >> >> >> virt_caps : hvm hvm_directio >>> >> >> >> total_memory : 7950 >>> >> >> >> free_memory : 7812 >>> >> >> >> node_to_cpu : node0:0-7 >>> >> >> >> node_to_memory : node0:7812 >>> >> >> >> node_to_dma32_mem : node0:3249 >>> >> >> >> max_node_id : 0 >>> >> >> >> xen_major : 4 >>> >> >> >> xen_minor : 0 >>> >> >> >> xen_extra : .0 >>> >> >> >> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 >>> >> >> >> hvm-3.0-x86_32p hvm-3.0-x86_64 >>> >> >> >> xen_scheduler : credit >>> >> >> >> xen_pagesize : 4096 >>> >> >> >> platform_params : virt_start=0xffff800000000000 >>> >> >> >> xen_changeset : unavailable >>> >> >> >> xen_commandline : iommu=1 dom0_mem=256M dom0_max_vcpus=1 >>> >> >> >> dom0_vcpus_pin=true >>> >> >> >> cc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1) >>> >> >> >> cc_compile_by : root >>> >> >> >> cc_compile_domain : >>> >> >> >> cc_compile_date : Thu May 6 13:41:25 EDT 2010 >>> >> >> >> xend_config_format : 4 >>> >> >> >> >>> >> >> >> # xm create vm-five.cfg >>> >> >> >> Using config file "./vm-five.cfg". >>> >> >> >> Error: Failed to assign device to IOMMU >>> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>> >> >> >> >>> >> >> >> I feel like I'm missing something really obvious but I've been at it >>> >> >> >> for a while now and have run out of brain power. Anyone have any idea >>> >> >> >> what might be wrong? >>> >> >> >> >>> >> >> >> - chris >>> >> >> > >>> >> >> >> __ __ _ _ ___ ___ >>> >> >> >> \ \/ /___ _ __ | || | / _ \ / _ \ >>> >> >> >> \ // _ \ \047_ \ | || |_| | | | | | | >>> >> >> >> / \ __/ | | | |__ _| |_| | |_| | >>> >> >> >> /_/\_\___|_| |_| |_|(_)___(_)___/ >>> >> >> >> >>> >> >> >> (XEN) Xen version 4.0.0 (root@) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) Thu May 6 13:41:25 EDT 2010 >>> >> >> >> (XEN) Latest ChangeSet: unavailable >>> >> >> >> (XEN) Command line: iommu=verbose dom0_mem=256M dom0_max_vcpus=1 dom0_vcpus_pin=true >>> >> >> >> (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 - 000000000008f000 (usable) >>> >> >> >> (XEN) 000000000008f000 - 0000000000090000 (reserved) >>> >> >> >> (XEN) 0000000000090000 - 000000000009ec00 (usable) >>> >> >> >> (XEN) 000000000009ec00 - 00000000000a0000 (reserved) >>> >> >> >> (XEN) 00000000000e0000 - 0000000000100000 (reserved) >>> >> >> >> (XEN) 0000000000100000 - 00000000cf4bd000 (usable) >>> >> >> >> (XEN) 00000000cf4bd000 - 00000000cf4bf000 (reserved) >>> >> >> >> (XEN) 00000000cf4bf000 - 00000000cf4c2000 (usable) >>> >> >> >> (XEN) 00000000cf4c2000 - 00000000cf7bf000 (ACPI NVS) >>> >> >> >> (XEN) 00000000cf7bf000 - 00000000cf7df000 (usable) >>> >> >> >> (XEN) 00000000cf7df000 - 00000000cf7ff000 (ACPI data) >>> >> >> >> (XEN) 00000000cf7ff000 - 00000000cf800000 (usable) >>> >> >> >> (XEN) 00000000cf800000 - 00000000d0000000 (reserved) >>> >> >> >> (XEN) 00000000f8000000 - 00000000fd000000 (reserved) >>> >> >> >> (XEN) 00000000ffe00000 - 0000000100000000 (reserved) >>> >> >> >> (XEN) 0000000100000000 - 0000000230000000 (usable) >>> >> >> >> (XEN) ACPI: RSDP 000FE020, 0024 (r2 INTEL ) >>> >> >> >> (XEN) ACPI: XSDT CF7FE120, 0074 (r1 INTEL DX58SO 11F6 1000013) >>> >> >> >> (XEN) ACPI: FACP CF7FD000, 00F4 (r3 INTEL DX58SO 11F6 MSFT 100000D) >>> >> >> >> (XEN) ACPI Warning (tbfadt-0444): Optional field "Pm2ControlBlock" has zero address or length: 0000000000000450/0 [20070126] >>> >> >> >> (XEN) ACPI: DSDT CF7F8000, 4641 (r2 INTEL DX58SO 11F6 MSFT 100000D) >>> >> >> >> (XEN) ACPI: FACS CF728000, 0040 >>> >> >> >> (XEN) ACPI: APIC CF7F7000, 0138 (r2 INTEL DX58SO 11F6 MSFT 100000D) >>> >> >> >> (XEN) ACPI: WDDT CF7F6000, 0040 (r1 INTEL DX58SO 11F6 MSFT 100000D) >>> >> >> >> (XEN) ACPI: MCFG CF7F5000, 003C (r1 INTEL DX58SO 11F6 MSFT 100000D) >>> >> >> >> (XEN) ACPI: ASF! CF7F4000, 00AC (r32 INTEL DX58SO 11F6 MSFT 100000D) >>> >> >> >> (XEN) ACPI: HPET CF7F3000, 0038 (r1 INTEL DX58SO 11F6 MSFT 100000D) >>> >> >> >> (XEN) ACPI: SSDT CF7E2000, E134 (r1 INTEL SSDT PM 11F6 MSFT 100000D) >>> >> >> >> (XEN) ACPI: DMAR CF7DF000, 0140 (r1 INTEL DX58SO 11F6 MSFT 100000D) >>> >> >> >> (XEN) ACPI: WDTT CF7F1000, 020C (r2 INTEL DX58SO 11F6 MSFT 100000D) >>> >> >> >> (XEN) ACPI: ASPT CF7F2000, 0034 (r4 INTEL PerfTune 11F6 MSFT 100000D) >>> >> >> >> (XEN) System RAM: 7950MB (8140820kB) >>> >> >> >> (XEN) Domain heap initialised >>> >> >> >> (XEN) Processor #0 7:10 APIC version 21 >>> >> >> >> (XEN) Processor #2 7:10 APIC version 21 >>> >> >> >> (XEN) Processor #4 7:10 APIC version 21 >>> >> >> >> (XEN) Processor #6 7:10 APIC version 21 >>> >> >> >> (XEN) Processor #1 7:10 APIC version 21 >>> >> >> >> (XEN) Processor #3 7:10 APIC version 21 >>> >> >> >> (XEN) Processor #5 7:10 APIC version 21 >>> >> >> >> (XEN) Processor #7 7:10 APIC version 21 >>> >> >> >> (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 >>> >> >> >> (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs >>> >> >> >> (XEN) [VT-D]dmar.c:679: Host address width 39 >>> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: >>> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = fe711000 >>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1b.0 >>> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: >>> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = fe710000 >>> >> >> >> (XEN) [VT-D]dmar.c:340: IOAPIC: f0:1f.7 >>> >> >> >> (XEN) [VT-D]dmar.c:411: flags: INCLUDE_ALL >>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 >>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e9000 end_address e9fff >>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.1 >>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ea000 end_address eafff >>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.2 >>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr eb000 end_address ebfff >>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.0 >>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e6000 end_address e6fff >>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.1 >>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e7000 end_address e7fff >>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.2 >>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e8000 end_address e8fff >>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 >>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ec000 end_address eefff >>> >> >> >> (XEN) Using scheduler: SMP Credit Scheduler (credit) >>> >> >> >> (XEN) Detected 2800.125 MHz processor. >>> >> >> >> (XEN) Initing memory sharing. >>> >> >> >> (XEN) VMX: Supported advanced features: >>> >> >> >> (XEN) - APIC MMIO access virtualisation >>> >> >> >> (XEN) - APIC TPR shadow >>> >> >> >> (XEN) - Extended Page Tables (EPT) >>> >> >> >> (XEN) - Virtual-Processor Identifiers (VPID) >>> >> >> >> (XEN) - Virtual NMI >>> >> >> >> (XEN) - MSR direct-access bitmap >>> >> >> >> (XEN) HVM: ASIDs enabled. >>> >> >> >> (XEN) HVM: VMX enabled >>> >> >> >> (XEN) HVM: Hardware Assisted Paging detected. >>> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = fe711000 iommu->reg = ffff82c3fff57000 >>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c9008010e60262 ecap = f0207a >>> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = fe710000 iommu->reg = ffff82c3fff56000 >>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c90780106f0462 ecap = f020fa >>> >> >> >> (XEN) Intel VT-d Snoop Control not supported. >>> >> >> >> (XEN) Intel VT-d DMA Passthrough not supported. >>> >> >> >> (XEN) Intel VT-d Queued Invalidation supported. >>> >> >> >> (XEN) Intel VT-d Interrupt Remapping supported. >>> >> >> >> (XEN) I/O virtualisation enabled >>> >> >> >> (XEN) I/O virtualisation for PV guests disabled >>> >> >> >> (XEN) Total of 8 processors activated. >>> >> >> >> (XEN) ENABLING IO-APIC IRQs >>> >> >> >> (XEN) -> Using new ACK method >>> >> >> >> (XEN) TSC is reliable, synchronization unnecessary >>> >> >> >> (XEN) Platform timer is 14.318MHz HPET >>> >> >> >> (XEN) Allocated console ring of 16 KiB. >>> >> >> >> (XEN) Brought up 8 CPUs >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:0.0 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.0 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.1 >>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.0 >>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.1 >>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.2 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:14.3 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:19.0 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.0 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.1 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.2 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.7 >>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:1b.0 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.0 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.1 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.2 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.7 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.0 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.2 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.3 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.5 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.0 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.1 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.2 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.0 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.1 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.2 >>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 5:0.0 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.0 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.1 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.2 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.0 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.1 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.2 >>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = a:0.0 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.0 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.1 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.2 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.3 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.4 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.5 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.6 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.7 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.0 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.1 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.0 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.1 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.0 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.1 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.4 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.0 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.1 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.2 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.3 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.0 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.1 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.2 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.3 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.0 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.1 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.2 >>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.3 >>> >> >> >> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = ffff82c3fff57000 >>> >> >> >> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = ffff82c3fff56000 >>> >> >> >> (XEN) *** LOADING DOMAIN 0 *** >>> >> >> >> (XEN) Xen kernel: 64-bit, lsb, compat32 >>> >> >> >> (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x26ae000 >>> >> >> >> (XEN) PHYSICAL MEMORY ARRANGEMENT: >>> >> >> >> (XEN) Dom0 alloc.: 0000000210000000->0000000220000000 >>> >> >> >> (XEN) VIRTUAL MEMORY ARRANGEMENT: >>> >> >> >> (XEN) Loaded kernel: ffffffff81000000->ffffffff826ae000 >>> >> >> >> (XEN) Init. ramdisk: ffffffff826ae000->ffffffff8f4de600 >>> >> >> >> (XEN) Phys-Mach map: ffffffff8f4df000->ffffffff8f55f000 >>> >> >> >> (XEN) Start info: ffffffff8f55f000->ffffffff8f55f4b4 >>> >> >> >> (XEN) Page tables: ffffffff8f560000->ffffffff8f5df000 >>> >> >> >> (XEN) Boot stack: ffffffff8f5df000->ffffffff8f5e0000 >>> >> >> >> (XEN) TOTAL: ffffffff80000000->ffffffff8f800000 >>> >> >> >> (XEN) ENTRY ADDRESS: ffffffff81a10860 >>> >> >> >> (XEN) Dom0 has maximum 1 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 \047CTRL-a\047 three times to switch input to Xen) >>> >> >> >> (XEN) Freed 164kB init memory. >>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 >>> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 >>> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 pirq=0 >>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=2, irq=0 >>> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 >>> >> >> >> (XEN) ioapic_guest_write: old_entry=000009f0 pirq=0 >>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 3 already mapped >>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 4 already mapped >>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 5 already mapped >>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 6 already mapped >>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 7 already mapped >>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 8 already mapped >>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 9 already mapped >>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 10 already mapped >>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 11 already mapped >>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 12 already mapped >>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 >>> >> >> >> (XEN) ioapic_guest_write: new_entry=000009f0 >>> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 pirq=0 >>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 >>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 >>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=23, irq=23 >>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a929 >>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a929 pirq=23 >>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 >>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 >>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 >>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 >>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 pirq=16 >>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 >>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 >>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 pirq=16 >>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 >>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 >>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >> > >>> >> >> >> _______________________________________________ >>> >> >> >> Xen-users mailing list >>> >> >> >> Xen-users@lists.xensource.com >>> >> >> >> http://lists.xensource.com/xen-users >>> >> >> > >>> >> > >>> > >> > [-- Attachment #2: xm-dmesg-verbose.txt --] [-- Type: text/plain, Size: 19975 bytes --] __ __ _ _ ___ ___ \ \/ /___ _ __ | || | / _ \ / _ \ \ // _ \ \047_ \ | || |_| | | | | | | / \ __/ | | | |__ _| |_| | |_| | /_/\_\___|_| |_| |_|(_)___(_)___/ (XEN) Xen version 4.0.0 (root@) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) Thu May 6 13:41:25 EDT 2010 (XEN) Latest ChangeSet: unavailable (XEN) Command line: iommu=verbose dom0_mem=2048M dom0_max_vcpus=8 dom0_vcpus_pin=true loglvl=all guest_loglvl=all (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 - 000000000008f000 (usable) (XEN) 000000000008f000 - 0000000000090000 (reserved) (XEN) 0000000000090000 - 000000000009ec00 (usable) (XEN) 000000000009ec00 - 00000000000a0000 (reserved) (XEN) 00000000000e0000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 00000000cf4bd000 (usable) (XEN) 00000000cf4bd000 - 00000000cf4bf000 (reserved) (XEN) 00000000cf4bf000 - 00000000cf4c2000 (usable) (XEN) 00000000cf4c2000 - 00000000cf7bf000 (ACPI NVS) (XEN) 00000000cf7bf000 - 00000000cf7df000 (usable) (XEN) 00000000cf7df000 - 00000000cf7ff000 (ACPI data) (XEN) 00000000cf7ff000 - 00000000cf800000 (usable) (XEN) 00000000cf800000 - 00000000d0000000 (reserved) (XEN) 00000000f8000000 - 00000000fd000000 (reserved) (XEN) 00000000ffe00000 - 0000000100000000 (reserved) (XEN) 0000000100000000 - 0000000230000000 (usable) (XEN) ACPI: RSDP 000FE020, 0024 (r2 INTEL ) (XEN) ACPI: XSDT CF7FE120, 0074 (r1 INTEL DX58SO 11F6 1000013) (XEN) ACPI: FACP CF7FD000, 00F4 (r3 INTEL DX58SO 11F6 MSFT 100000D) (XEN) ACPI Warning (tbfadt-0444): Optional field "Pm2ControlBlock" has zero address or length: 0000000000000450/0 [20070126] (XEN) ACPI: DSDT CF7F8000, 4641 (r2 INTEL DX58SO 11F6 MSFT 100000D) (XEN) ACPI: FACS CF728000, 0040 (XEN) ACPI: APIC CF7F7000, 0138 (r2 INTEL DX58SO 11F6 MSFT 100000D) (XEN) ACPI: WDDT CF7F6000, 0040 (r1 INTEL DX58SO 11F6 MSFT 100000D) (XEN) ACPI: MCFG CF7F5000, 003C (r1 INTEL DX58SO 11F6 MSFT 100000D) (XEN) ACPI: ASF! CF7F4000, 00AC (r32 INTEL DX58SO 11F6 MSFT 100000D) (XEN) ACPI: HPET CF7F3000, 0038 (r1 INTEL DX58SO 11F6 MSFT 100000D) (XEN) ACPI: SSDT CF7E2000, E134 (r1 INTEL SSDT PM 11F6 MSFT 100000D) (XEN) ACPI: DMAR CF7DF000, 0140 (r1 INTEL DX58SO 11F6 MSFT 100000D) (XEN) ACPI: WDTT CF7F1000, 020C (r2 INTEL DX58SO 11F6 MSFT 100000D) (XEN) ACPI: ASPT CF7F2000, 0034 (r4 INTEL PerfTune 11F6 MSFT 100000D) (XEN) System RAM: 7950MB (8140820kB) (XEN) No NUMA configuration found (XEN) Faking a node at 0000000000000000-0000000230000000 (XEN) Domain heap initialised (XEN) DMI 2.5 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[cf72800c], vec_size[20] (XEN) ACPI: Local APIC address 0xfee00000 (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) (XEN) Processor #0 7:10 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x02] enabled) (XEN) Processor #2 7:10 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x04] enabled) (XEN) Processor #4 7:10 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x06] enabled) (XEN) Processor #6 7:10 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x01] enabled) (XEN) Processor #1 7:10 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x03] enabled) (XEN) Processor #3 7:10 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x05] enabled) (XEN) Processor #5 7:10 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] enabled) (XEN) Processor #7 7:10 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x10] disabled) (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x12] disabled) (XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x14] disabled) (XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x16] disabled) (XEN) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x11] disabled) (XEN) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x13] disabled) (XEN) ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x15] disabled) (XEN) ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x17] disabled) (XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high level lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high level lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x02] high level lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x03] high level lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x04] high level lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x05] high level lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x06] high level lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x07] high level lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x08] high level lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x09] high level lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x0a] high level lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x0b] high level lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x0c] high level lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x0d] high level lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x0e] high level lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x0f] high level lint[0x1]) (XEN) ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0]) (XEN) IOAPIC[0]: apic_id 8, 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) ACPI: HPET id: 0x8086a301 base: 0xfed00000 (XEN) [VT-D]dmar.c:679: Host address width 39 (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: (XEN) [VT-D]dmar.c:398: dmaru->address = fe711000 (XEN) [VT-D]dmar.c:334: endpoint: 0:1b.0 (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: (XEN) [VT-D]dmar.c:398: dmaru->address = fe710000 (XEN) [VT-D]dmar.c:340: IOAPIC: f0:1f.7 (XEN) [VT-D]dmar.c:411: flags: INCLUDE_ALL (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e9000 end_address e9fff (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.1 (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ea000 end_address eafff (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.2 (XEN) [VT-D]dmar.c:571: RMRR region: base_addr eb000 end_address ebfff (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.0 (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e6000 end_address e6fff (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.1 (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e7000 end_address e7fff (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.2 (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e8000 end_address e8fff (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ec000 end_address eefff (XEN) PCI: MCFG configuration 0: base f8000000 segment 0 buses 0 - 63 (XEN) PCI: MCFG area at f8000000 reserved in E820 (XEN) Using ACPI (MADT) for SMP configuration information (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Detected 2800.172 MHz processor. (XEN) Initing memory sharing. (XEN) VMX: Supported advanced features: (XEN) - APIC MMIO access virtualisation (XEN) - APIC TPR shadow (XEN) - Extended Page Tables (EPT) (XEN) - Virtual-Processor Identifiers (VPID) (XEN) - Virtual NMI (XEN) - MSR direct-access bitmap (XEN) HVM: ASIDs enabled. (XEN) HVM: VMX enabled (XEN) HVM: Hardware Assisted Paging detected. (XEN) Intel machine check reporting enabled (XEN) [VT-D]iommu.c:1078: drhd->address = fe711000 iommu->reg = ffff82c3fff57000 (XEN) [VT-D]iommu.c:1080: cap = c9008010e60262 ecap = f0207a (XEN) [VT-D]iommu.c:1078: drhd->address = fe710000 iommu->reg = ffff82c3fff56000 (XEN) [VT-D]iommu.c:1080: cap = c90780106f0462 ecap = f020fa (XEN) Intel VT-d Snoop Control not supported. (XEN) Intel VT-d DMA Passthrough not supported. (XEN) Intel VT-d Queued Invalidation supported. (XEN) Intel VT-d Interrupt Remapping supported. (XEN) I/O virtualisation enabled (XEN) I/O virtualisation for PV guests disabled (XEN) Total of 8 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) TSC is reliable, synchronization unnecessary (XEN) Platform timer is 14.318MHz HPET (XEN) Allocated console ring of 64 KiB. (XEN) microcode.c:73:d32767 microcode: CPU1 resumed (XEN) microcode.c:73:d32767 microcode: CPU2 resumed (XEN) microcode.c:73:d32767 microcode: CPU5 resumed (XEN) microcode.c:73:d32767 microcode: CPU7 resumed (XEN) Brought up 8 CPUs (XEN) microcode.c:73:d32767 microcode: CPU6 resumed (XEN) microcode.c:73:d32767 microcode: CPU3 resumed (XEN) microcode.c:73:d32767 microcode: CPU4 resumed (XEN) Turbo Mode detected! (XEN) HPET\047s MSI mode hasn\047t been supported when Interrupt Remapping is enabled. (XEN) ACPI sleep modes: S3 (XEN) mcheck_poll: Machine check polling timer started. (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:0.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.1 (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.0 (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.1 (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.2 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:14.3 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:19.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.1 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.2 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.7 (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:1b.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.1 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.2 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.7 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.2 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.3 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.5 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.1 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.2 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.1 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.2 (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 5:0.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.1 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.2 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.1 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.2 (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = a:0.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.1 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.2 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.3 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.4 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.5 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.6 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.7 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.1 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.1 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.1 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.4 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.1 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.2 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.3 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.1 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.2 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.3 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.1 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.2 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.3 (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = ffff82c3fff57000 (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = ffff82c3fff56000 (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x26ae000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000210000000->0000000220000000 (458752 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff81000000->ffffffff826ae000 (XEN) Init. ramdisk: ffffffff826ae000->ffffffff8f4de600 (XEN) Phys-Mach map: ffffffff8f4df000->ffffffff8f8df000 (XEN) Start info: ffffffff8f8df000->ffffffff8f8df4b4 (XEN) Page tables: ffffffff8f8e0000->ffffffff8f961000 (XEN) Boot stack: ffffffff8f961000->ffffffff8f962000 (XEN) TOTAL: ffffffff80000000->ffffffff8fc00000 (XEN) ENTRY ADDRESS: ffffffff81a10860 (XEN) Dom0 has maximum 8 VCPUs (XEN) Scrubbing Free RAM: ............................................................done. (XEN) Xen trace buffers: disabled (XEN) Std. Loglevel: All (XEN) Guest Loglevel: All (XEN) Xen is relinquishing VGA console. (XEN) *** Serial input -> DOM0 (type \047CTRL-a\047 three times to switch input to Xen) (XEN) Freed 164kB init memory. (XEN) io_apic.c:2290: (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 (XEN) ioapic_guest_write: new_entry=000109f0 (XEN) ioapic_guest_write: old_entry=00010000 pirq=0 (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! (XEN) io_apic.c:2290: (XEN) ioapic_guest_write: apic=0, pin=2, irq=0 (XEN) ioapic_guest_write: new_entry=000109f0 (XEN) ioapic_guest_write: old_entry=000009f0 pirq=0 (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! (XEN) irq.c:1445: dom0: pirq 0 or irq 3 already mapped (XEN) irq.c:1445: dom0: pirq 0 or irq 4 already mapped (XEN) irq.c:1445: dom0: pirq 0 or irq 5 already mapped (XEN) irq.c:1445: dom0: pirq 0 or irq 6 already mapped (XEN) irq.c:1445: dom0: pirq 0 or irq 7 already mapped (XEN) irq.c:1445: dom0: pirq 0 or irq 8 already mapped (XEN) irq.c:1445: dom0: pirq 0 or irq 9 already mapped (XEN) irq.c:1445: dom0: pirq 0 or irq 10 already mapped (XEN) irq.c:1445: dom0: pirq 0 or irq 11 already mapped (XEN) irq.c:1445: dom0: pirq 0 or irq 12 already mapped (XEN) irq.c:1445: dom0: pirq 0 or irq 13 already mapped (XEN) irq.c:1445: dom0: pirq 0 or irq 14 already mapped (XEN) irq.c:1445: dom0: pirq 0 or irq 15 already mapped (XEN) allocated vector b0 for irq 16 (XEN) irq.c:1445: dom0: pirq 0 or irq 16 already mapped (XEN) allocated vector b8 for irq 17 (XEN) irq.c:1445: dom0: pirq 0 or irq 17 already mapped (XEN) allocated vector c0 for irq 18 (XEN) irq.c:1445: dom0: pirq 0 or irq 18 already mapped (XEN) allocated vector c8 for irq 19 (XEN) irq.c:1445: dom0: pirq 0 or irq 19 already mapped (XEN) allocated vector d0 for irq 20 (XEN) irq.c:1445: dom0: pirq 0 or irq 20 already mapped (XEN) allocated vector d8 for irq 21 (XEN) irq.c:1445: dom0: pirq 0 or irq 21 already mapped (XEN) allocated vector 21 for irq 22 (XEN) irq.c:1445: dom0: pirq 0 or irq 22 already mapped (XEN) allocated vector 29 for irq 23 (XEN) irq.c:1445: dom0: pirq 0 or irq 23 already mapped (XEN) io_apic.c:2290: (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 (XEN) ioapic_guest_write: new_entry=000009f0 (XEN) ioapic_guest_write: old_entry=00010000 pirq=0 (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! (XEN) PCI add device 00:00.0 (XEN) PCI add device 00:01.0 (XEN) PCI add device 00:03.0 (XEN) PCI add device 00:07.0 (XEN) PCI add device 00:10.0 (XEN) PCI add device 00:10.1 (XEN) PCI add device 00:14.0 (XEN) PCI add device 00:14.1 (XEN) PCI add device 00:14.2 (XEN) PCI add device 00:14.3 (XEN) PCI add device 00:19.0 (XEN) PCI add device 00:1a.0 (XEN) PCI add device 00:1a.1 (XEN) PCI add device 00:1a.2 (XEN) PCI add device 00:1a.7 (XEN) PCI add device 00:1b.0 (XEN) PCI add device 00:1c.0 (XEN) PCI add device 00:1c.1 (XEN) PCI add device 00:1c.4 (XEN) PCI add device 00:1d.0 (XEN) PCI add device 00:1d.1 (XEN) PCI add device 00:1d.2 (XEN) PCI add device 00:1d.7 (XEN) PCI add device 00:1e.0 (XEN) PCI add device 00:1f.0 (XEN) PCI add device 00:1f.2 (XEN) PCI add device 00:1f.3 (XEN) PCI add device 00:1f.5 (XEN) PCI add device 01:00.0 (XEN) PCI add device 02:00.0 (XEN) PCI add device 02:00.1 (XEN) PCI add device 02:00.2 (XEN) PCI add device 03:00.0 (XEN) PCI add device 04:00.0 (XEN) PCI add device 04:00.1 (XEN) PCI add device 04:00.2 (XEN) PCI add device 05:00.0 (XEN) PCI add device 06:00.0 (XEN) PCI add device 07:00.0 (XEN) PCI add device 07:00.1 (XEN) PCI add device 07:00.2 (XEN) PCI add device 08:00.0 (XEN) PCI add device 09:00.0 (XEN) PCI add device 09:00.1 (XEN) PCI add device 09:00.2 (XEN) PCI add device 0a:00.0 (XEN) PCI add device 0b:03.0 (XEN) irq.c:1182:d0 Cannot bind IRQ 0 to guest. Will not share with others. (XEN) irq.c:1182:d0 Cannot bind IRQ 0 to guest. Will not share with others. (XEN) irq.c:1182:d0 Cannot bind IRQ 0 to guest. Will not share with others. (XEN) irq.c:1182:d0 Cannot bind IRQ 0 to guest. Will not share with others. (XEN) io_apic.c:2290: (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 (XEN) ioapic_guest_write: new_entry=0001a9c0 (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! (XEN) io_apic.c:2290: (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 (XEN) ioapic_guest_write: new_entry=0001a9c8 (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! (XEN) io_apic.c:2290: (XEN) ioapic_guest_write: apic=0, pin=23, irq=23 (XEN) ioapic_guest_write: new_entry=0001a929 (XEN) ioapic_guest_write: old_entry=0000a929 pirq=23 (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! (XEN) io_apic.c:2290: (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 (XEN) ioapic_guest_write: new_entry=0001a9c8 (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! (XEN) io_apic.c:2290: (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 (XEN) ioapic_guest_write: new_entry=0001a9c0 (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! (XEN) io_apic.c:2290: (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 (XEN) ioapic_guest_write: new_entry=0001a9c8 (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! (XEN) io_apic.c:2290: (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 (XEN) ioapic_guest_write: new_entry=0001a9b0 (XEN) ioapic_guest_write: old_entry=0000a9b0 pirq=16 (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! (XEN) io_apic.c:2290: (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 (XEN) ioapic_guest_write: new_entry=0001a9c0 (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! [-- 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] 32+ messages in thread
* Re: RE: Xen4 / Intel DX58SO Mobo / VT-d not working 2010-05-13 18:28 ` [Xen-users] RE: Xen4 / Intel DX58SO Mobo / VT-d not working chris @ 2010-05-14 19:05 ` chris 2010-05-14 19:11 ` Pasi Kärkkäinen 0 siblings, 1 reply; 32+ messages in thread From: chris @ 2010-05-14 19:05 UTC (permalink / raw) To: Pasi Kärkkäinen; +Cc: Xen-Devel List, Xen-Users List Pasi, Tried latest stable/2.6.32.x per your advice, no change. Anyone on xen-devel that can help me troubleshoot further? Everything looks right, can't figure out why vt-d is not working but it must be some kind of bug :( test-box2:~# uname -a Linux test-box2 2.6.32.12 #1 SMP Fri May 14 13:40:05 EDT 2010 x86_64 GNU/Linux test-box2:~# xm info | grep virt_caps virt_caps : hvm hvm_directio test-box2:~# xm pci-list-assignable-devices 0000:02:00.0 0000:02:00.1 0000:02:00.2 test-box2:~# xm create /etc/xen/vm-five.cfg Using config file "/etc/xen/vm-five.cfg". Error: Failed to assign device to IOMMU (0000:02:00.0@100,msitranslate=1,power_mgmt=0) test-box2:~# cat /etc/xen/vm-five.cfg | grep -v '#' kernel = '/usr/lib/xen/boot/hvmloader' builder = 'hvm' memory = '1792' device_model='/usr/lib/xen/bin/qemu-dm' disk = [ 'phy:/dev/storage/vm-five,ioemu:hda,w', 'phy:/dev/sr0,ioemu:hdc:cdrom,r' ] name = 'vm-five' vif = ['type=ioemu, bridge=eth0, mac=00:16:3D:37:A1:42'] boot='dc' cpus='0-1' vcpus=2 acpi=1 ahci=1 vnc=1 sdl=0 timer_mode=1 usb=1 usbdevice='tablet' localtime=1 pci = ['02:00.0','02:00.1','02:00.2'] On Thu, May 13, 2010 at 2:28 PM, chris <tknchris@gmail.com> wrote: > Forwarding to xen-devel. Can't seem to get VT-d working with xen4 from > tarball on xen.org 2.6.31.13 pv_ops dom0. On pasi's advice I tried > switching to stable/2.6.32.x branch for dom0 and that doesnt even > build. Did something change recently thats breaking compilation? > > Attached is xen dmesg with iommu=verbose loglvl=all guest_loglvl=all, > and dom0 dmesg from 2.6.31.x > > Any ideas on why VT-d is not working on this board? Initialization > looks good, xen reports hvm_directio capability, everything says VT-d > should work until domain is created. > > Any ideas why stable/2.6.32.x wont build? > > - chris > > On Thu, May 13, 2010 at 2:07 PM, chris <tknchris@gmail.com> wrote: >> I redid it with oldconfig which I didn't think would help and same >> thing. I guess this tree is broken? Can someone else try and see if >> they can build it? Ugh, whata day :) >> >> On Thu, May 13, 2010 at 1:58 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>> On Thu, May 13, 2010 at 01:55:25PM -0400, chris wrote: >>>> I used the default config on the wiki which you created. Steps I took were: >>>> >>>> # make clean distclean >>>> # wget -O .config >>>> "http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.10-pvops-dom0-xen-stable-x86_64" >>> >>> You should do "make oldconfig" at this point. >>> >>>> # make -j8 bzImage >>>> (blah blah) >>>> LD vmlinux.o >>>> MODPOST vmlinux.o >>>> WARNING: modpost: Found 7 section mismatch(es). >>>> To see full details build your kernel with: >>>> 'make CONFIG_DEBUG_SECTION_MISMATCH=y' >>>> GEN .version >>>> CHK include/linux/compile.h >>>> UPD include/linux/compile.h >>>> CC init/version.o >>>> LD init/built-in.o >>>> LD .tmp_vmlinux1 >>>> drivers/built-in.o: In function `do_hvm_suspend': >>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: undefined reference >>>> to `xenbus_suspend' >>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: undefined reference >>>> to `xenbus_resume' >>>> make: *** [.tmp_vmlinux1] Error 1 >>>> >>> >>> Hmm.. weird. I wonder if something has changed recently or what's going on in here.. >>> >>> -- Pasi >>> >>>> >>>> On Thu, May 13, 2010 at 11:47 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>>> > On Thu, May 13, 2010 at 11:33:57AM -0400, chris wrote: >>>> >> Successfully grabbed the sources and failed to build: >>>> >> >>>> >> LD .tmp_vmlinux1 >>>> >> drivers/built-in.o: In function `do_hvm_suspend': >>>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: undefined reference >>>> >> to `xenbus_suspend' >>>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: undefined reference >>>> >> to `xenbus_resume' >>>> >> make: *** [.tmp_vmlinux1] Error 1 >>>> >> >>>> >> :( >>>> >> >>>> > >>>> > Try the example .config files provided on the wiki page. >>>> > >>>> > -- Pasi >>>> > >>>> >> On Thu, May 13, 2010 at 10:14 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>>> >> > On Thu, May 13, 2010 at 10:12:56AM -0400, chris wrote: >>>> >> >> Pasi, >>>> >> >> >>>> >> >> How do I pull those kernel sources you referenced? I see it mentioned >>>> >> >> on http://wiki.xensource.com/xenwiki/XenParavirtOps but no details on >>>> >> >> how to retrieve it. >>>> >> >> >>>> >> > >>>> >> > The instructions are there if you read it carefully.. >>>> >> > There's the topic of how to switch branches. >>>> >> > >>>> >> > -- Pasi >>>> >> > >>>> >> >> - chris >>>> >> >> >>>> >> >> On Thu, May 13, 2010 at 8:29 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>>> >> >> > On Wed, May 12, 2010 at 08:41:34PM -0400, chris wrote: >>>> >> >> >> When reading the vtdhowto I noticed the ability to set iommu=verbose. >>>> >> >> >> Here is that output, I don't know if it helps at all to figure out >>>> >> >> >> what is wrong. >>>> >> >> >> >>>> >> >> > >>>> >> >> > That seems to be OK: >>>> >> >> > >>>> >> >> > (XEN) I/O virtualisation enabled >>>> >> >> > (XEN) I/O virtualisation for PV guests disabled >>>> >> >> > >>>> >> >> > So hmm.. I wonder if it's related to MSI stuff? >>>> >> >> > You could try xen.git xen/stable-2.6.32.x branch instead and see if that makes a difference.. >>>> >> >> > >>>> >> >> > -- Pasi >>>> >> >> > >>>> >> >> >> >>>> >> >> >> ---------- Forwarded message ---------- >>>> >> >> >> From: chris <tknchris@gmail.com> >>>> >> >> >> Date: Wed, May 12, 2010 at 5:28 PM >>>> >> >> >> Subject: Xen4 / Intel DX58SO Mobo / VT-d not working >>>> >> >> >> To: Xen-Users List <xen-users@lists.xensource.com> >>>> >> >> >> >>>> >> >> >> >>>> >> >> >> Hello, >>>> >> >> >> >>>> >> >> >> I've previously been successful with Xen4 and VT-d on other systems. I >>>> >> >> >> am having trouble getting VT-d passthrough working to a WinXP domain >>>> >> >> >> with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is enabled in bios, >>>> >> >> >> xm info shows hvm_directio capability, I have iommu=1 set, I have the >>>> >> >> >> devices bound to pciback on dom0 cmdline, xm >>>> >> >> >> pci-list-assignable-devices shows the devices as assignable. When I >>>> >> >> >> attempt to start the VM I get the error: >>>> >> >> >> >>>> >> >> >> Error: Failed to assign device to IOMMU >>>> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>>> >> >> >> >>>> >> >> >> Below is all the information I can think of that would be useful to >>>> >> >> >> help debug it: >>>> >> >> >> >>>> >> >> >> BIOS VT-d Enabled: >>>> >> >> >> http://i43.tinypic.com/nl3a5e.jpg >>>> >> >> >> http://i42.tinypic.com/nqvlu1.jpg >>>> >> >> >> >>>> >> >> >> grub entry: >>>> >> >> >> >>>> >> >> >> title Xen 4.0.0 / Debian GNU/Linux, kernel 2.6.31.13 >>>> >> >> >> root (hd0,0) >>>> >> >> >> kernel /boot/xen-4.0.0.gz iommu=1 dom0_mem=256M >>>> >> >> >> dom0_max_vcpus=1 dom0_vcpus_pin=true >>>> >> >> >> module /boot/vmlinuz-2.6.31.13 root=/dev/md0 ro console=tty0 >>>> >> >> >> xen-pciback.permissive >>>> >> >> >> xen-pciback.hide=(02:00.0)(02:00.1)(02:00.2)(04:00.0)(04:00.1)(04:00.2)(07:00.0)(07:00.1)(07:00.2)(09:00.0)(09:00.1)(09:00.2) >>>> >> >> >> module /boot/initrd.img-2.6.31.13 >>>> >> >> >> >>>> >> >> >> # xm pci-list-assignable-devices >>>> >> >> >> 0000:09:00.0 >>>> >> >> >> 0000:09:00.1 >>>> >> >> >> 0000:09:00.2 >>>> >> >> >> 0000:07:00.0 >>>> >> >> >> 0000:07:00.1 >>>> >> >> >> 0000:07:00.2 >>>> >> >> >> 0000:04:00.0 >>>> >> >> >> 0000:04:00.1 >>>> >> >> >> 0000:04:00.2 >>>> >> >> >> 0000:02:00.0 >>>> >> >> >> 0000:02:00.1 >>>> >> >> >> 0000:02:00.2 >>>> >> >> >> >>>> >> >> >> # xm info >>>> >> >> >> host : test-box2 >>>> >> >> >> release : 2.6.31.13 >>>> >> >> >> version : #2 SMP Wed May 12 14:11:37 EDT 2010 >>>> >> >> >> machine : x86_64 >>>> >> >> >> nr_cpus : 8 >>>> >> >> >> nr_nodes : 1 >>>> >> >> >> cores_per_socket : 4 >>>> >> >> >> threads_per_core : 2 >>>> >> >> >> cpu_mhz : 2800 >>>> >> >> >> hw_caps : >>>> >> >> >> bfebfbff:28100800:00000000:00001b40:0098e3bd:00000000:00000001:00000000 >>>> >> >> >> virt_caps : hvm hvm_directio >>>> >> >> >> total_memory : 7950 >>>> >> >> >> free_memory : 7812 >>>> >> >> >> node_to_cpu : node0:0-7 >>>> >> >> >> node_to_memory : node0:7812 >>>> >> >> >> node_to_dma32_mem : node0:3249 >>>> >> >> >> max_node_id : 0 >>>> >> >> >> xen_major : 4 >>>> >> >> >> xen_minor : 0 >>>> >> >> >> xen_extra : .0 >>>> >> >> >> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 >>>> >> >> >> hvm-3.0-x86_32p hvm-3.0-x86_64 >>>> >> >> >> xen_scheduler : credit >>>> >> >> >> xen_pagesize : 4096 >>>> >> >> >> platform_params : virt_start=0xffff800000000000 >>>> >> >> >> xen_changeset : unavailable >>>> >> >> >> xen_commandline : iommu=1 dom0_mem=256M dom0_max_vcpus=1 >>>> >> >> >> dom0_vcpus_pin=true >>>> >> >> >> cc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1) >>>> >> >> >> cc_compile_by : root >>>> >> >> >> cc_compile_domain : >>>> >> >> >> cc_compile_date : Thu May 6 13:41:25 EDT 2010 >>>> >> >> >> xend_config_format : 4 >>>> >> >> >> >>>> >> >> >> # xm create vm-five.cfg >>>> >> >> >> Using config file "./vm-five.cfg". >>>> >> >> >> Error: Failed to assign device to IOMMU >>>> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>>> >> >> >> >>>> >> >> >> I feel like I'm missing something really obvious but I've been at it >>>> >> >> >> for a while now and have run out of brain power. Anyone have any idea >>>> >> >> >> what might be wrong? >>>> >> >> >> >>>> >> >> >> - chris >>>> >> >> > >>>> >> >> >> __ __ _ _ ___ ___ >>>> >> >> >> \ \/ /___ _ __ | || | / _ \ / _ \ >>>> >> >> >> \ // _ \ \047_ \ | || |_| | | | | | | >>>> >> >> >> / \ __/ | | | |__ _| |_| | |_| | >>>> >> >> >> /_/\_\___|_| |_| |_|(_)___(_)___/ >>>> >> >> >> >>>> >> >> >> (XEN) Xen version 4.0.0 (root@) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) Thu May 6 13:41:25 EDT 2010 >>>> >> >> >> (XEN) Latest ChangeSet: unavailable >>>> >> >> >> (XEN) Command line: iommu=verbose dom0_mem=256M dom0_max_vcpus=1 dom0_vcpus_pin=true >>>> >> >> >> (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 - 000000000008f000 (usable) >>>> >> >> >> (XEN) 000000000008f000 - 0000000000090000 (reserved) >>>> >> >> >> (XEN) 0000000000090000 - 000000000009ec00 (usable) >>>> >> >> >> (XEN) 000000000009ec00 - 00000000000a0000 (reserved) >>>> >> >> >> (XEN) 00000000000e0000 - 0000000000100000 (reserved) >>>> >> >> >> (XEN) 0000000000100000 - 00000000cf4bd000 (usable) >>>> >> >> >> (XEN) 00000000cf4bd000 - 00000000cf4bf000 (reserved) >>>> >> >> >> (XEN) 00000000cf4bf000 - 00000000cf4c2000 (usable) >>>> >> >> >> (XEN) 00000000cf4c2000 - 00000000cf7bf000 (ACPI NVS) >>>> >> >> >> (XEN) 00000000cf7bf000 - 00000000cf7df000 (usable) >>>> >> >> >> (XEN) 00000000cf7df000 - 00000000cf7ff000 (ACPI data) >>>> >> >> >> (XEN) 00000000cf7ff000 - 00000000cf800000 (usable) >>>> >> >> >> (XEN) 00000000cf800000 - 00000000d0000000 (reserved) >>>> >> >> >> (XEN) 00000000f8000000 - 00000000fd000000 (reserved) >>>> >> >> >> (XEN) 00000000ffe00000 - 0000000100000000 (reserved) >>>> >> >> >> (XEN) 0000000100000000 - 0000000230000000 (usable) >>>> >> >> >> (XEN) ACPI: RSDP 000FE020, 0024 (r2 INTEL ) >>>> >> >> >> (XEN) ACPI: XSDT CF7FE120, 0074 (r1 INTEL DX58SO 11F6 1000013) >>>> >> >> >> (XEN) ACPI: FACP CF7FD000, 00F4 (r3 INTEL DX58SO 11F6 MSFT 100000D) >>>> >> >> >> (XEN) ACPI Warning (tbfadt-0444): Optional field "Pm2ControlBlock" has zero address or length: 0000000000000450/0 [20070126] >>>> >> >> >> (XEN) ACPI: DSDT CF7F8000, 4641 (r2 INTEL DX58SO 11F6 MSFT 100000D) >>>> >> >> >> (XEN) ACPI: FACS CF728000, 0040 >>>> >> >> >> (XEN) ACPI: APIC CF7F7000, 0138 (r2 INTEL DX58SO 11F6 MSFT 100000D) >>>> >> >> >> (XEN) ACPI: WDDT CF7F6000, 0040 (r1 INTEL DX58SO 11F6 MSFT 100000D) >>>> >> >> >> (XEN) ACPI: MCFG CF7F5000, 003C (r1 INTEL DX58SO 11F6 MSFT 100000D) >>>> >> >> >> (XEN) ACPI: ASF! CF7F4000, 00AC (r32 INTEL DX58SO 11F6 MSFT 100000D) >>>> >> >> >> (XEN) ACPI: HPET CF7F3000, 0038 (r1 INTEL DX58SO 11F6 MSFT 100000D) >>>> >> >> >> (XEN) ACPI: SSDT CF7E2000, E134 (r1 INTEL SSDT PM 11F6 MSFT 100000D) >>>> >> >> >> (XEN) ACPI: DMAR CF7DF000, 0140 (r1 INTEL DX58SO 11F6 MSFT 100000D) >>>> >> >> >> (XEN) ACPI: WDTT CF7F1000, 020C (r2 INTEL DX58SO 11F6 MSFT 100000D) >>>> >> >> >> (XEN) ACPI: ASPT CF7F2000, 0034 (r4 INTEL PerfTune 11F6 MSFT 100000D) >>>> >> >> >> (XEN) System RAM: 7950MB (8140820kB) >>>> >> >> >> (XEN) Domain heap initialised >>>> >> >> >> (XEN) Processor #0 7:10 APIC version 21 >>>> >> >> >> (XEN) Processor #2 7:10 APIC version 21 >>>> >> >> >> (XEN) Processor #4 7:10 APIC version 21 >>>> >> >> >> (XEN) Processor #6 7:10 APIC version 21 >>>> >> >> >> (XEN) Processor #1 7:10 APIC version 21 >>>> >> >> >> (XEN) Processor #3 7:10 APIC version 21 >>>> >> >> >> (XEN) Processor #5 7:10 APIC version 21 >>>> >> >> >> (XEN) Processor #7 7:10 APIC version 21 >>>> >> >> >> (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 >>>> >> >> >> (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs >>>> >> >> >> (XEN) [VT-D]dmar.c:679: Host address width 39 >>>> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: >>>> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = fe711000 >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1b.0 >>>> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: >>>> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = fe710000 >>>> >> >> >> (XEN) [VT-D]dmar.c:340: IOAPIC: f0:1f.7 >>>> >> >> >> (XEN) [VT-D]dmar.c:411: flags: INCLUDE_ALL >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e9000 end_address e9fff >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.1 >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ea000 end_address eafff >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.2 >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr eb000 end_address ebfff >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.0 >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e6000 end_address e6fff >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.1 >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e7000 end_address e7fff >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.2 >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e8000 end_address e8fff >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ec000 end_address eefff >>>> >> >> >> (XEN) Using scheduler: SMP Credit Scheduler (credit) >>>> >> >> >> (XEN) Detected 2800.125 MHz processor. >>>> >> >> >> (XEN) Initing memory sharing. >>>> >> >> >> (XEN) VMX: Supported advanced features: >>>> >> >> >> (XEN) - APIC MMIO access virtualisation >>>> >> >> >> (XEN) - APIC TPR shadow >>>> >> >> >> (XEN) - Extended Page Tables (EPT) >>>> >> >> >> (XEN) - Virtual-Processor Identifiers (VPID) >>>> >> >> >> (XEN) - Virtual NMI >>>> >> >> >> (XEN) - MSR direct-access bitmap >>>> >> >> >> (XEN) HVM: ASIDs enabled. >>>> >> >> >> (XEN) HVM: VMX enabled >>>> >> >> >> (XEN) HVM: Hardware Assisted Paging detected. >>>> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = fe711000 iommu->reg = ffff82c3fff57000 >>>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c9008010e60262 ecap = f0207a >>>> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = fe710000 iommu->reg = ffff82c3fff56000 >>>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c90780106f0462 ecap = f020fa >>>> >> >> >> (XEN) Intel VT-d Snoop Control not supported. >>>> >> >> >> (XEN) Intel VT-d DMA Passthrough not supported. >>>> >> >> >> (XEN) Intel VT-d Queued Invalidation supported. >>>> >> >> >> (XEN) Intel VT-d Interrupt Remapping supported. >>>> >> >> >> (XEN) I/O virtualisation enabled >>>> >> >> >> (XEN) I/O virtualisation for PV guests disabled >>>> >> >> >> (XEN) Total of 8 processors activated. >>>> >> >> >> (XEN) ENABLING IO-APIC IRQs >>>> >> >> >> (XEN) -> Using new ACK method >>>> >> >> >> (XEN) TSC is reliable, synchronization unnecessary >>>> >> >> >> (XEN) Platform timer is 14.318MHz HPET >>>> >> >> >> (XEN) Allocated console ring of 16 KiB. >>>> >> >> >> (XEN) Brought up 8 CPUs >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:0.0 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.0 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.1 >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.0 >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.1 >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.2 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:14.3 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:19.0 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.0 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.1 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.2 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.7 >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:1b.0 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.0 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.1 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.2 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.7 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.0 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.2 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.3 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.5 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.0 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.1 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.2 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.0 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.1 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.2 >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 5:0.0 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.0 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.1 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.2 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.0 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.1 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.2 >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = a:0.0 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.0 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.1 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.2 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.3 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.4 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.5 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.6 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.7 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.0 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.1 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.0 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.1 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.0 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.1 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.4 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.0 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.1 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.2 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.3 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.0 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.1 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.2 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.3 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.0 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.1 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.2 >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.3 >>>> >> >> >> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = ffff82c3fff57000 >>>> >> >> >> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = ffff82c3fff56000 >>>> >> >> >> (XEN) *** LOADING DOMAIN 0 *** >>>> >> >> >> (XEN) Xen kernel: 64-bit, lsb, compat32 >>>> >> >> >> (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x26ae000 >>>> >> >> >> (XEN) PHYSICAL MEMORY ARRANGEMENT: >>>> >> >> >> (XEN) Dom0 alloc.: 0000000210000000->0000000220000000 >>>> >> >> >> (XEN) VIRTUAL MEMORY ARRANGEMENT: >>>> >> >> >> (XEN) Loaded kernel: ffffffff81000000->ffffffff826ae000 >>>> >> >> >> (XEN) Init. ramdisk: ffffffff826ae000->ffffffff8f4de600 >>>> >> >> >> (XEN) Phys-Mach map: ffffffff8f4df000->ffffffff8f55f000 >>>> >> >> >> (XEN) Start info: ffffffff8f55f000->ffffffff8f55f4b4 >>>> >> >> >> (XEN) Page tables: ffffffff8f560000->ffffffff8f5df000 >>>> >> >> >> (XEN) Boot stack: ffffffff8f5df000->ffffffff8f5e0000 >>>> >> >> >> (XEN) TOTAL: ffffffff80000000->ffffffff8f800000 >>>> >> >> >> (XEN) ENTRY ADDRESS: ffffffff81a10860 >>>> >> >> >> (XEN) Dom0 has maximum 1 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 \047CTRL-a\047 three times to switch input to Xen) >>>> >> >> >> (XEN) Freed 164kB init memory. >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 pirq=0 >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=2, irq=0 >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=000009f0 pirq=0 >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 3 already mapped >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 4 already mapped >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 5 already mapped >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 6 already mapped >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 7 already mapped >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 8 already mapped >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 9 already mapped >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 10 already mapped >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 11 already mapped >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 12 already mapped >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000009f0 >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 pirq=0 >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=23, irq=23 >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a929 >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a929 pirq=23 >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 pirq=16 >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 pirq=16 >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >> >> > >>>> >> >> >> _______________________________________________ >>>> >> >> >> Xen-users mailing list >>>> >> >> >> Xen-users@lists.xensource.com >>>> >> >> >> http://lists.xensource.com/xen-users >>>> >> >> > >>>> >> > >>>> > >>> >> > ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: RE: Xen4 / Intel DX58SO Mobo / VT-d not working 2010-05-14 19:05 ` chris @ 2010-05-14 19:11 ` Pasi Kärkkäinen 2010-05-14 19:18 ` [Xen-users] " chris 0 siblings, 1 reply; 32+ messages in thread From: Pasi Kärkkäinen @ 2010-05-14 19:11 UTC (permalink / raw) To: chris; +Cc: Xen-Devel List, Xen-Users List On Fri, May 14, 2010 at 03:05:49PM -0400, chris wrote: > Pasi, > > Tried latest stable/2.6.32.x per your advice, no change. Anyone on > xen-devel that can help me troubleshoot further? Everything looks > right, can't figure out why vt-d is not working but it must be some > kind of bug :( > Did you try the suggestion said earlier.. try to just passthru the first pci device? -- Pasi > test-box2:~# uname -a > Linux test-box2 2.6.32.12 #1 SMP Fri May 14 13:40:05 EDT 2010 x86_64 GNU/Linux > > test-box2:~# xm info | grep virt_caps > virt_caps : hvm hvm_directio > > test-box2:~# xm pci-list-assignable-devices > 0000:02:00.0 > 0000:02:00.1 > 0000:02:00.2 > > test-box2:~# xm create /etc/xen/vm-five.cfg > Using config file "/etc/xen/vm-five.cfg". > Error: Failed to assign device to IOMMU > (0000:02:00.0@100,msitranslate=1,power_mgmt=0) > > test-box2:~# cat /etc/xen/vm-five.cfg | grep -v '#' > kernel = '/usr/lib/xen/boot/hvmloader' > builder = 'hvm' > memory = '1792' > device_model='/usr/lib/xen/bin/qemu-dm' > disk = [ 'phy:/dev/storage/vm-five,ioemu:hda,w', > 'phy:/dev/sr0,ioemu:hdc:cdrom,r' > ] > name = 'vm-five' > vif = ['type=ioemu, bridge=eth0, mac=00:16:3D:37:A1:42'] > boot='dc' > cpus='0-1' > vcpus=2 > acpi=1 > ahci=1 > vnc=1 > sdl=0 > timer_mode=1 > usb=1 > usbdevice='tablet' > localtime=1 > pci = ['02:00.0','02:00.1','02:00.2'] > > On Thu, May 13, 2010 at 2:28 PM, chris <tknchris@gmail.com> wrote: > > Forwarding to xen-devel. Can't seem to get VT-d working with xen4 from > > tarball on xen.org 2.6.31.13 pv_ops dom0. On pasi's advice I tried > > switching to stable/2.6.32.x branch for dom0 and that doesnt even > > build. Did something change recently thats breaking compilation? > > > > Attached is xen dmesg with iommu=verbose loglvl=all guest_loglvl=all, > > and dom0 dmesg from 2.6.31.x > > > > Any ideas on why VT-d is not working on this board? Initialization > > looks good, xen reports hvm_directio capability, everything says VT-d > > should work until domain is created. > > > > Any ideas why stable/2.6.32.x wont build? > > > > - chris > > > > On Thu, May 13, 2010 at 2:07 PM, chris <tknchris@gmail.com> wrote: > >> I redid it with oldconfig which I didn't think would help and same > >> thing. I guess this tree is broken? Can someone else try and see if > >> they can build it? Ugh, whata day :) > >> > >> On Thu, May 13, 2010 at 1:58 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > >>> On Thu, May 13, 2010 at 01:55:25PM -0400, chris wrote: > >>>> I used the default config on the wiki which you created. Steps I took were: > >>>> > >>>> # make clean distclean > >>>> # wget -O .config > >>>> "http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.10-pvops-dom0-xen-stable-x86_64" > >>> > >>> You should do "make oldconfig" at this point. > >>> > >>>> # make -j8 bzImage > >>>> (blah blah) > >>>> LD vmlinux.o > >>>> MODPOST vmlinux.o > >>>> WARNING: modpost: Found 7 section mismatch(es). > >>>> To see full details build your kernel with: > >>>> 'make CONFIG_DEBUG_SECTION_MISMATCH=y' > >>>> GEN .version > >>>> CHK include/linux/compile.h > >>>> UPD include/linux/compile.h > >>>> CC init/version.o > >>>> LD init/built-in.o > >>>> LD .tmp_vmlinux1 > >>>> drivers/built-in.o: In function `do_hvm_suspend': > >>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: undefined reference > >>>> to `xenbus_suspend' > >>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: undefined reference > >>>> to `xenbus_resume' > >>>> make: *** [.tmp_vmlinux1] Error 1 > >>>> > >>> > >>> Hmm.. weird. I wonder if something has changed recently or what's going on in here.. > >>> > >>> -- Pasi > >>> > >>>> > >>>> On Thu, May 13, 2010 at 11:47 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > >>>> > On Thu, May 13, 2010 at 11:33:57AM -0400, chris wrote: > >>>> >> Successfully grabbed the sources and failed to build: > >>>> >> > >>>> >> LD .tmp_vmlinux1 > >>>> >> drivers/built-in.o: In function `do_hvm_suspend': > >>>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: undefined reference > >>>> >> to `xenbus_suspend' > >>>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: undefined reference > >>>> >> to `xenbus_resume' > >>>> >> make: *** [.tmp_vmlinux1] Error 1 > >>>> >> > >>>> >> :( > >>>> >> > >>>> > > >>>> > Try the example .config files provided on the wiki page. > >>>> > > >>>> > -- Pasi > >>>> > > >>>> >> On Thu, May 13, 2010 at 10:14 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > >>>> >> > On Thu, May 13, 2010 at 10:12:56AM -0400, chris wrote: > >>>> >> >> Pasi, > >>>> >> >> > >>>> >> >> How do I pull those kernel sources you referenced? I see it mentioned > >>>> >> >> on http://wiki.xensource.com/xenwiki/XenParavirtOps but no details on > >>>> >> >> how to retrieve it. > >>>> >> >> > >>>> >> > > >>>> >> > The instructions are there if you read it carefully.. > >>>> >> > There's the topic of how to switch branches. > >>>> >> > > >>>> >> > -- Pasi > >>>> >> > > >>>> >> >> - chris > >>>> >> >> > >>>> >> >> On Thu, May 13, 2010 at 8:29 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > >>>> >> >> > On Wed, May 12, 2010 at 08:41:34PM -0400, chris wrote: > >>>> >> >> >> When reading the vtdhowto I noticed the ability to set iommu=verbose. > >>>> >> >> >> Here is that output, I don't know if it helps at all to figure out > >>>> >> >> >> what is wrong. > >>>> >> >> >> > >>>> >> >> > > >>>> >> >> > That seems to be OK: > >>>> >> >> > > >>>> >> >> > (XEN) I/O virtualisation enabled > >>>> >> >> > (XEN) I/O virtualisation for PV guests disabled > >>>> >> >> > > >>>> >> >> > So hmm.. I wonder if it's related to MSI stuff? > >>>> >> >> > You could try xen.git xen/stable-2.6.32.x branch instead and see if that makes a difference.. > >>>> >> >> > > >>>> >> >> > -- Pasi > >>>> >> >> > > >>>> >> >> >> > >>>> >> >> >> ---------- Forwarded message ---------- > >>>> >> >> >> From: chris <tknchris@gmail.com> > >>>> >> >> >> Date: Wed, May 12, 2010 at 5:28 PM > >>>> >> >> >> Subject: Xen4 / Intel DX58SO Mobo / VT-d not working > >>>> >> >> >> To: Xen-Users List <xen-users@lists.xensource.com> > >>>> >> >> >> > >>>> >> >> >> > >>>> >> >> >> Hello, > >>>> >> >> >> > >>>> >> >> >> I've previously been successful with Xen4 and VT-d on other systems. I > >>>> >> >> >> am having trouble getting VT-d passthrough working to a WinXP domain > >>>> >> >> >> with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is enabled in bios, > >>>> >> >> >> xm info shows hvm_directio capability, I have iommu=1 set, I have the > >>>> >> >> >> devices bound to pciback on dom0 cmdline, xm > >>>> >> >> >> pci-list-assignable-devices shows the devices as assignable. When I > >>>> >> >> >> attempt to start the VM I get the error: > >>>> >> >> >> > >>>> >> >> >> Error: Failed to assign device to IOMMU > >>>> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) > >>>> >> >> >> > >>>> >> >> >> Below is all the information I can think of that would be useful to > >>>> >> >> >> help debug it: > >>>> >> >> >> > >>>> >> >> >> BIOS VT-d Enabled: > >>>> >> >> >> http://i43.tinypic.com/nl3a5e.jpg > >>>> >> >> >> http://i42.tinypic.com/nqvlu1.jpg > >>>> >> >> >> > >>>> >> >> >> grub entry: > >>>> >> >> >> > >>>> >> >> >> title Xen 4.0.0 / Debian GNU/Linux, kernel 2.6.31.13 > >>>> >> >> >> root (hd0,0) > >>>> >> >> >> kernel /boot/xen-4.0.0.gz iommu=1 dom0_mem=256M > >>>> >> >> >> dom0_max_vcpus=1 dom0_vcpus_pin=true > >>>> >> >> >> module /boot/vmlinuz-2.6.31.13 root=/dev/md0 ro console=tty0 > >>>> >> >> >> xen-pciback.permissive > >>>> >> >> >> xen-pciback.hide=(02:00.0)(02:00.1)(02:00.2)(04:00.0)(04:00.1)(04:00.2)(07:00.0)(07:00.1)(07:00.2)(09:00.0)(09:00.1)(09:00.2) > >>>> >> >> >> module /boot/initrd.img-2.6.31.13 > >>>> >> >> >> > >>>> >> >> >> # xm pci-list-assignable-devices > >>>> >> >> >> 0000:09:00.0 > >>>> >> >> >> 0000:09:00.1 > >>>> >> >> >> 0000:09:00.2 > >>>> >> >> >> 0000:07:00.0 > >>>> >> >> >> 0000:07:00.1 > >>>> >> >> >> 0000:07:00.2 > >>>> >> >> >> 0000:04:00.0 > >>>> >> >> >> 0000:04:00.1 > >>>> >> >> >> 0000:04:00.2 > >>>> >> >> >> 0000:02:00.0 > >>>> >> >> >> 0000:02:00.1 > >>>> >> >> >> 0000:02:00.2 > >>>> >> >> >> > >>>> >> >> >> # xm info > >>>> >> >> >> host : test-box2 > >>>> >> >> >> release : 2.6.31.13 > >>>> >> >> >> version : #2 SMP Wed May 12 14:11:37 EDT 2010 > >>>> >> >> >> machine : x86_64 > >>>> >> >> >> nr_cpus : 8 > >>>> >> >> >> nr_nodes : 1 > >>>> >> >> >> cores_per_socket : 4 > >>>> >> >> >> threads_per_core : 2 > >>>> >> >> >> cpu_mhz : 2800 > >>>> >> >> >> hw_caps : > >>>> >> >> >> bfebfbff:28100800:00000000:00001b40:0098e3bd:00000000:00000001:00000000 > >>>> >> >> >> virt_caps : hvm hvm_directio > >>>> >> >> >> total_memory : 7950 > >>>> >> >> >> free_memory : 7812 > >>>> >> >> >> node_to_cpu : node0:0-7 > >>>> >> >> >> node_to_memory : node0:7812 > >>>> >> >> >> node_to_dma32_mem : node0:3249 > >>>> >> >> >> max_node_id : 0 > >>>> >> >> >> xen_major : 4 > >>>> >> >> >> xen_minor : 0 > >>>> >> >> >> xen_extra : .0 > >>>> >> >> >> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > >>>> >> >> >> hvm-3.0-x86_32p hvm-3.0-x86_64 > >>>> >> >> >> xen_scheduler : credit > >>>> >> >> >> xen_pagesize : 4096 > >>>> >> >> >> platform_params : virt_start=0xffff800000000000 > >>>> >> >> >> xen_changeset : unavailable > >>>> >> >> >> xen_commandline : iommu=1 dom0_mem=256M dom0_max_vcpus=1 > >>>> >> >> >> dom0_vcpus_pin=true > >>>> >> >> >> cc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1) > >>>> >> >> >> cc_compile_by : root > >>>> >> >> >> cc_compile_domain : > >>>> >> >> >> cc_compile_date : Thu May 6 13:41:25 EDT 2010 > >>>> >> >> >> xend_config_format : 4 > >>>> >> >> >> > >>>> >> >> >> # xm create vm-five.cfg > >>>> >> >> >> Using config file "./vm-five.cfg". > >>>> >> >> >> Error: Failed to assign device to IOMMU > >>>> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) > >>>> >> >> >> > >>>> >> >> >> I feel like I'm missing something really obvious but I've been at it > >>>> >> >> >> for a while now and have run out of brain power. Anyone have any idea > >>>> >> >> >> what might be wrong? > >>>> >> >> >> > >>>> >> >> >> - chris > >>>> >> >> > > >>>> >> >> >> __ __ _ _ ___ ___ > >>>> >> >> >> \ \/ /___ _ __ | || | / _ \ / _ \ > >>>> >> >> >> \ // _ \ \047_ \ | || |_| | | | | | | > >>>> >> >> >> / \ __/ | | | |__ _| |_| | |_| | > >>>> >> >> >> /_/\_\___|_| |_| |_|(_)___(_)___/ > >>>> >> >> >> > >>>> >> >> >> (XEN) Xen version 4.0.0 (root@) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) Thu May 6 13:41:25 EDT 2010 > >>>> >> >> >> (XEN) Latest ChangeSet: unavailable > >>>> >> >> >> (XEN) Command line: iommu=verbose dom0_mem=256M dom0_max_vcpus=1 dom0_vcpus_pin=true > >>>> >> >> >> (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 - 000000000008f000 (usable) > >>>> >> >> >> (XEN) 000000000008f000 - 0000000000090000 (reserved) > >>>> >> >> >> (XEN) 0000000000090000 - 000000000009ec00 (usable) > >>>> >> >> >> (XEN) 000000000009ec00 - 00000000000a0000 (reserved) > >>>> >> >> >> (XEN) 00000000000e0000 - 0000000000100000 (reserved) > >>>> >> >> >> (XEN) 0000000000100000 - 00000000cf4bd000 (usable) > >>>> >> >> >> (XEN) 00000000cf4bd000 - 00000000cf4bf000 (reserved) > >>>> >> >> >> (XEN) 00000000cf4bf000 - 00000000cf4c2000 (usable) > >>>> >> >> >> (XEN) 00000000cf4c2000 - 00000000cf7bf000 (ACPI NVS) > >>>> >> >> >> (XEN) 00000000cf7bf000 - 00000000cf7df000 (usable) > >>>> >> >> >> (XEN) 00000000cf7df000 - 00000000cf7ff000 (ACPI data) > >>>> >> >> >> (XEN) 00000000cf7ff000 - 00000000cf800000 (usable) > >>>> >> >> >> (XEN) 00000000cf800000 - 00000000d0000000 (reserved) > >>>> >> >> >> (XEN) 00000000f8000000 - 00000000fd000000 (reserved) > >>>> >> >> >> (XEN) 00000000ffe00000 - 0000000100000000 (reserved) > >>>> >> >> >> (XEN) 0000000100000000 - 0000000230000000 (usable) > >>>> >> >> >> (XEN) ACPI: RSDP 000FE020, 0024 (r2 INTEL ) > >>>> >> >> >> (XEN) ACPI: XSDT CF7FE120, 0074 (r1 INTEL DX58SO 11F6 1000013) > >>>> >> >> >> (XEN) ACPI: FACP CF7FD000, 00F4 (r3 INTEL DX58SO 11F6 MSFT 100000D) > >>>> >> >> >> (XEN) ACPI Warning (tbfadt-0444): Optional field "Pm2ControlBlock" has zero address or length: 0000000000000450/0 [20070126] > >>>> >> >> >> (XEN) ACPI: DSDT CF7F8000, 4641 (r2 INTEL DX58SO 11F6 MSFT 100000D) > >>>> >> >> >> (XEN) ACPI: FACS CF728000, 0040 > >>>> >> >> >> (XEN) ACPI: APIC CF7F7000, 0138 (r2 INTEL DX58SO 11F6 MSFT 100000D) > >>>> >> >> >> (XEN) ACPI: WDDT CF7F6000, 0040 (r1 INTEL DX58SO 11F6 MSFT 100000D) > >>>> >> >> >> (XEN) ACPI: MCFG CF7F5000, 003C (r1 INTEL DX58SO 11F6 MSFT 100000D) > >>>> >> >> >> (XEN) ACPI: ASF! CF7F4000, 00AC (r32 INTEL DX58SO 11F6 MSFT 100000D) > >>>> >> >> >> (XEN) ACPI: HPET CF7F3000, 0038 (r1 INTEL DX58SO 11F6 MSFT 100000D) > >>>> >> >> >> (XEN) ACPI: SSDT CF7E2000, E134 (r1 INTEL SSDT PM 11F6 MSFT 100000D) > >>>> >> >> >> (XEN) ACPI: DMAR CF7DF000, 0140 (r1 INTEL DX58SO 11F6 MSFT 100000D) > >>>> >> >> >> (XEN) ACPI: WDTT CF7F1000, 020C (r2 INTEL DX58SO 11F6 MSFT 100000D) > >>>> >> >> >> (XEN) ACPI: ASPT CF7F2000, 0034 (r4 INTEL PerfTune 11F6 MSFT 100000D) > >>>> >> >> >> (XEN) System RAM: 7950MB (8140820kB) > >>>> >> >> >> (XEN) Domain heap initialised > >>>> >> >> >> (XEN) Processor #0 7:10 APIC version 21 > >>>> >> >> >> (XEN) Processor #2 7:10 APIC version 21 > >>>> >> >> >> (XEN) Processor #4 7:10 APIC version 21 > >>>> >> >> >> (XEN) Processor #6 7:10 APIC version 21 > >>>> >> >> >> (XEN) Processor #1 7:10 APIC version 21 > >>>> >> >> >> (XEN) Processor #3 7:10 APIC version 21 > >>>> >> >> >> (XEN) Processor #5 7:10 APIC version 21 > >>>> >> >> >> (XEN) Processor #7 7:10 APIC version 21 > >>>> >> >> >> (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 > >>>> >> >> >> (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > >>>> >> >> >> (XEN) [VT-D]dmar.c:679: Host address width 39 > >>>> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: > >>>> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = fe711000 > >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1b.0 > >>>> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: > >>>> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = fe710000 > >>>> >> >> >> (XEN) [VT-D]dmar.c:340: IOAPIC: f0:1f.7 > >>>> >> >> >> (XEN) [VT-D]dmar.c:411: flags: INCLUDE_ALL > >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 > >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e9000 end_address e9fff > >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.1 > >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ea000 end_address eafff > >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.2 > >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr eb000 end_address ebfff > >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.0 > >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e6000 end_address e6fff > >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.1 > >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e7000 end_address e7fff > >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.2 > >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e8000 end_address e8fff > >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 > >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ec000 end_address eefff > >>>> >> >> >> (XEN) Using scheduler: SMP Credit Scheduler (credit) > >>>> >> >> >> (XEN) Detected 2800.125 MHz processor. > >>>> >> >> >> (XEN) Initing memory sharing. > >>>> >> >> >> (XEN) VMX: Supported advanced features: > >>>> >> >> >> (XEN) - APIC MMIO access virtualisation > >>>> >> >> >> (XEN) - APIC TPR shadow > >>>> >> >> >> (XEN) - Extended Page Tables (EPT) > >>>> >> >> >> (XEN) - Virtual-Processor Identifiers (VPID) > >>>> >> >> >> (XEN) - Virtual NMI > >>>> >> >> >> (XEN) - MSR direct-access bitmap > >>>> >> >> >> (XEN) HVM: ASIDs enabled. > >>>> >> >> >> (XEN) HVM: VMX enabled > >>>> >> >> >> (XEN) HVM: Hardware Assisted Paging detected. > >>>> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = fe711000 iommu->reg = ffff82c3fff57000 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c9008010e60262 ecap = f0207a > >>>> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = fe710000 iommu->reg = ffff82c3fff56000 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c90780106f0462 ecap = f020fa > >>>> >> >> >> (XEN) Intel VT-d Snoop Control not supported. > >>>> >> >> >> (XEN) Intel VT-d DMA Passthrough not supported. > >>>> >> >> >> (XEN) Intel VT-d Queued Invalidation supported. > >>>> >> >> >> (XEN) Intel VT-d Interrupt Remapping supported. > >>>> >> >> >> (XEN) I/O virtualisation enabled > >>>> >> >> >> (XEN) I/O virtualisation for PV guests disabled > >>>> >> >> >> (XEN) Total of 8 processors activated. > >>>> >> >> >> (XEN) ENABLING IO-APIC IRQs > >>>> >> >> >> (XEN) -> Using new ACK method > >>>> >> >> >> (XEN) TSC is reliable, synchronization unnecessary > >>>> >> >> >> (XEN) Platform timer is 14.318MHz HPET > >>>> >> >> >> (XEN) Allocated console ring of 16 KiB. > >>>> >> >> >> (XEN) Brought up 8 CPUs > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:0.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.1 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.1 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.2 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:14.3 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:19.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.1 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.2 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.7 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:1b.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.1 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.2 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.7 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.2 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.3 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.5 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.1 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.2 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.1 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.2 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 5:0.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.1 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.2 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.1 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.2 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = a:0.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.1 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.2 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.3 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.4 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.5 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.6 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.7 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.1 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.1 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.1 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.4 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.1 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.2 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.3 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.1 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.2 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.3 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.1 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.2 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.3 > >>>> >> >> >> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = ffff82c3fff57000 > >>>> >> >> >> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = ffff82c3fff56000 > >>>> >> >> >> (XEN) *** LOADING DOMAIN 0 *** > >>>> >> >> >> (XEN) Xen kernel: 64-bit, lsb, compat32 > >>>> >> >> >> (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x26ae000 > >>>> >> >> >> (XEN) PHYSICAL MEMORY ARRANGEMENT: > >>>> >> >> >> (XEN) Dom0 alloc.: 0000000210000000->0000000220000000 > >>>> >> >> >> (XEN) VIRTUAL MEMORY ARRANGEMENT: > >>>> >> >> >> (XEN) Loaded kernel: ffffffff81000000->ffffffff826ae000 > >>>> >> >> >> (XEN) Init. ramdisk: ffffffff826ae000->ffffffff8f4de600 > >>>> >> >> >> (XEN) Phys-Mach map: ffffffff8f4df000->ffffffff8f55f000 > >>>> >> >> >> (XEN) Start info: ffffffff8f55f000->ffffffff8f55f4b4 > >>>> >> >> >> (XEN) Page tables: ffffffff8f560000->ffffffff8f5df000 > >>>> >> >> >> (XEN) Boot stack: ffffffff8f5df000->ffffffff8f5e0000 > >>>> >> >> >> (XEN) TOTAL: ffffffff80000000->ffffffff8f800000 > >>>> >> >> >> (XEN) ENTRY ADDRESS: ffffffff81a10860 > >>>> >> >> >> (XEN) Dom0 has maximum 1 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 \047CTRL-a\047 three times to switch input to Xen) > >>>> >> >> >> (XEN) Freed 164kB init memory. > >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 > >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 > >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 pirq=0 > >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=2, irq=0 > >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 > >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=000009f0 pirq=0 > >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 3 already mapped > >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 4 already mapped > >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 5 already mapped > >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 6 already mapped > >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 7 already mapped > >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 8 already mapped > >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 9 already mapped > >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 10 already mapped > >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 11 already mapped > >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 12 already mapped > >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 > >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000009f0 > >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 pirq=0 > >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 > >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 > >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 > >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 > >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 > >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 > >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=23, irq=23 > >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a929 > >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a929 pirq=23 > >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 > >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 > >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 > >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 > >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 > >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 > >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 > >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 > >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 pirq=16 > >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 > >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 > >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 pirq=16 > >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 > >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 > >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 > >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 > >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 > >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 > >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>>> >> >> > > >>>> >> >> >> _______________________________________________ > >>>> >> >> >> Xen-users mailing list > >>>> >> >> >> Xen-users@lists.xensource.com > >>>> >> >> >> http://lists.xensource.com/xen-users > >>>> >> >> > > >>>> >> > > >>>> > > >>> > >> > > ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [Xen-users] RE: Xen4 / Intel DX58SO Mobo / VT-d not working 2010-05-14 19:11 ` Pasi Kärkkäinen @ 2010-05-14 19:18 ` chris 2010-05-14 19:21 ` Pasi Kärkkäinen 0 siblings, 1 reply; 32+ messages in thread From: chris @ 2010-05-14 19:18 UTC (permalink / raw) To: Pasi Kärkkäinen; +Cc: Xen-Devel List, Xen-Users List It is a multifunction device, a pci-e usb controller, so I assumed all them had to be passed through. I just changed it to only 02:00.0 and same thing test-box2:~# cat /etc/xen/vm-five.cfg | grep pci pci = ['02:00.0'] test-box2:~# xm create /etc/xen/vm-five.cfg Using config file "/etc/xen/vm-five.cfg". Error: Failed to assign device to IOMMU (0000:02:00.0@100,msitranslate=1,power_mgmt=0) On Fri, May 14, 2010 at 3:11 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > On Fri, May 14, 2010 at 03:05:49PM -0400, chris wrote: >> Pasi, >> >> Tried latest stable/2.6.32.x per your advice, no change. Anyone on >> xen-devel that can help me troubleshoot further? Everything looks >> right, can't figure out why vt-d is not working but it must be some >> kind of bug :( >> > > Did you try the suggestion said earlier.. try to just passthru the first pci device? > > -- Pasi > >> test-box2:~# uname -a >> Linux test-box2 2.6.32.12 #1 SMP Fri May 14 13:40:05 EDT 2010 x86_64 GNU/Linux >> >> test-box2:~# xm info | grep virt_caps >> virt_caps : hvm hvm_directio >> >> test-box2:~# xm pci-list-assignable-devices >> 0000:02:00.0 >> 0000:02:00.1 >> 0000:02:00.2 >> >> test-box2:~# xm create /etc/xen/vm-five.cfg >> Using config file "/etc/xen/vm-five.cfg". >> Error: Failed to assign device to IOMMU >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >> >> test-box2:~# cat /etc/xen/vm-five.cfg | grep -v '#' >> kernel = '/usr/lib/xen/boot/hvmloader' >> builder = 'hvm' >> memory = '1792' >> device_model='/usr/lib/xen/bin/qemu-dm' >> disk = [ 'phy:/dev/storage/vm-five,ioemu:hda,w', >> 'phy:/dev/sr0,ioemu:hdc:cdrom,r' >> ] >> name = 'vm-five' >> vif = ['type=ioemu, bridge=eth0, mac=00:16:3D:37:A1:42'] >> boot='dc' >> cpus='0-1' >> vcpus=2 >> acpi=1 >> ahci=1 >> vnc=1 >> sdl=0 >> timer_mode=1 >> usb=1 >> usbdevice='tablet' >> localtime=1 >> pci = ['02:00.0','02:00.1','02:00.2'] >> >> On Thu, May 13, 2010 at 2:28 PM, chris <tknchris@gmail.com> wrote: >> > Forwarding to xen-devel. Can't seem to get VT-d working with xen4 from >> > tarball on xen.org 2.6.31.13 pv_ops dom0. On pasi's advice I tried >> > switching to stable/2.6.32.x branch for dom0 and that doesnt even >> > build. Did something change recently thats breaking compilation? >> > >> > Attached is xen dmesg with iommu=verbose loglvl=all guest_loglvl=all, >> > and dom0 dmesg from 2.6.31.x >> > >> > Any ideas on why VT-d is not working on this board? Initialization >> > looks good, xen reports hvm_directio capability, everything says VT-d >> > should work until domain is created. >> > >> > Any ideas why stable/2.6.32.x wont build? >> > >> > - chris >> > >> > On Thu, May 13, 2010 at 2:07 PM, chris <tknchris@gmail.com> wrote: >> >> I redid it with oldconfig which I didn't think would help and same >> >> thing. I guess this tree is broken? Can someone else try and see if >> >> they can build it? Ugh, whata day :) >> >> >> >> On Thu, May 13, 2010 at 1:58 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >> >>> On Thu, May 13, 2010 at 01:55:25PM -0400, chris wrote: >> >>>> I used the default config on the wiki which you created. Steps I took were: >> >>>> >> >>>> # make clean distclean >> >>>> # wget -O .config >> >>>> "http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.10-pvops-dom0-xen-stable-x86_64" >> >>> >> >>> You should do "make oldconfig" at this point. >> >>> >> >>>> # make -j8 bzImage >> >>>> (blah blah) >> >>>> LD vmlinux.o >> >>>> MODPOST vmlinux.o >> >>>> WARNING: modpost: Found 7 section mismatch(es). >> >>>> To see full details build your kernel with: >> >>>> 'make CONFIG_DEBUG_SECTION_MISMATCH=y' >> >>>> GEN .version >> >>>> CHK include/linux/compile.h >> >>>> UPD include/linux/compile.h >> >>>> CC init/version.o >> >>>> LD init/built-in.o >> >>>> LD .tmp_vmlinux1 >> >>>> drivers/built-in.o: In function `do_hvm_suspend': >> >>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: undefined reference >> >>>> to `xenbus_suspend' >> >>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: undefined reference >> >>>> to `xenbus_resume' >> >>>> make: *** [.tmp_vmlinux1] Error 1 >> >>>> >> >>> >> >>> Hmm.. weird. I wonder if something has changed recently or what's going on in here.. >> >>> >> >>> -- Pasi >> >>> >> >>>> >> >>>> On Thu, May 13, 2010 at 11:47 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >> >>>> > On Thu, May 13, 2010 at 11:33:57AM -0400, chris wrote: >> >>>> >> Successfully grabbed the sources and failed to build: >> >>>> >> >> >>>> >> LD .tmp_vmlinux1 >> >>>> >> drivers/built-in.o: In function `do_hvm_suspend': >> >>>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: undefined reference >> >>>> >> to `xenbus_suspend' >> >>>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: undefined reference >> >>>> >> to `xenbus_resume' >> >>>> >> make: *** [.tmp_vmlinux1] Error 1 >> >>>> >> >> >>>> >> :( >> >>>> >> >> >>>> > >> >>>> > Try the example .config files provided on the wiki page. >> >>>> > >> >>>> > -- Pasi >> >>>> > >> >>>> >> On Thu, May 13, 2010 at 10:14 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >> >>>> >> > On Thu, May 13, 2010 at 10:12:56AM -0400, chris wrote: >> >>>> >> >> Pasi, >> >>>> >> >> >> >>>> >> >> How do I pull those kernel sources you referenced? I see it mentioned >> >>>> >> >> on http://wiki.xensource.com/xenwiki/XenParavirtOps but no details on >> >>>> >> >> how to retrieve it. >> >>>> >> >> >> >>>> >> > >> >>>> >> > The instructions are there if you read it carefully.. >> >>>> >> > There's the topic of how to switch branches. >> >>>> >> > >> >>>> >> > -- Pasi >> >>>> >> > >> >>>> >> >> - chris >> >>>> >> >> >> >>>> >> >> On Thu, May 13, 2010 at 8:29 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >> >>>> >> >> > On Wed, May 12, 2010 at 08:41:34PM -0400, chris wrote: >> >>>> >> >> >> When reading the vtdhowto I noticed the ability to set iommu=verbose. >> >>>> >> >> >> Here is that output, I don't know if it helps at all to figure out >> >>>> >> >> >> what is wrong. >> >>>> >> >> >> >> >>>> >> >> > >> >>>> >> >> > That seems to be OK: >> >>>> >> >> > >> >>>> >> >> > (XEN) I/O virtualisation enabled >> >>>> >> >> > (XEN) I/O virtualisation for PV guests disabled >> >>>> >> >> > >> >>>> >> >> > So hmm.. I wonder if it's related to MSI stuff? >> >>>> >> >> > You could try xen.git xen/stable-2.6.32.x branch instead and see if that makes a difference.. >> >>>> >> >> > >> >>>> >> >> > -- Pasi >> >>>> >> >> > >> >>>> >> >> >> >> >>>> >> >> >> ---------- Forwarded message ---------- >> >>>> >> >> >> From: chris <tknchris@gmail.com> >> >>>> >> >> >> Date: Wed, May 12, 2010 at 5:28 PM >> >>>> >> >> >> Subject: Xen4 / Intel DX58SO Mobo / VT-d not working >> >>>> >> >> >> To: Xen-Users List <xen-users@lists.xensource.com> >> >>>> >> >> >> >> >>>> >> >> >> >> >>>> >> >> >> Hello, >> >>>> >> >> >> >> >>>> >> >> >> I've previously been successful with Xen4 and VT-d on other systems. I >> >>>> >> >> >> am having trouble getting VT-d passthrough working to a WinXP domain >> >>>> >> >> >> with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is enabled in bios, >> >>>> >> >> >> xm info shows hvm_directio capability, I have iommu=1 set, I have the >> >>>> >> >> >> devices bound to pciback on dom0 cmdline, xm >> >>>> >> >> >> pci-list-assignable-devices shows the devices as assignable. When I >> >>>> >> >> >> attempt to start the VM I get the error: >> >>>> >> >> >> >> >>>> >> >> >> Error: Failed to assign device to IOMMU >> >>>> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >> >>>> >> >> >> >> >>>> >> >> >> Below is all the information I can think of that would be useful to >> >>>> >> >> >> help debug it: >> >>>> >> >> >> >> >>>> >> >> >> BIOS VT-d Enabled: >> >>>> >> >> >> http://i43.tinypic.com/nl3a5e.jpg >> >>>> >> >> >> http://i42.tinypic.com/nqvlu1.jpg >> >>>> >> >> >> >> >>>> >> >> >> grub entry: >> >>>> >> >> >> >> >>>> >> >> >> title Xen 4.0.0 / Debian GNU/Linux, kernel 2.6.31.13 >> >>>> >> >> >> root (hd0,0) >> >>>> >> >> >> kernel /boot/xen-4.0.0.gz iommu=1 dom0_mem=256M >> >>>> >> >> >> dom0_max_vcpus=1 dom0_vcpus_pin=true >> >>>> >> >> >> module /boot/vmlinuz-2.6.31.13 root=/dev/md0 ro console=tty0 >> >>>> >> >> >> xen-pciback.permissive >> >>>> >> >> >> xen-pciback.hide=(02:00.0)(02:00.1)(02:00.2)(04:00.0)(04:00.1)(04:00.2)(07:00.0)(07:00.1)(07:00.2)(09:00.0)(09:00.1)(09:00.2) >> >>>> >> >> >> module /boot/initrd.img-2.6.31.13 >> >>>> >> >> >> >> >>>> >> >> >> # xm pci-list-assignable-devices >> >>>> >> >> >> 0000:09:00.0 >> >>>> >> >> >> 0000:09:00.1 >> >>>> >> >> >> 0000:09:00.2 >> >>>> >> >> >> 0000:07:00.0 >> >>>> >> >> >> 0000:07:00.1 >> >>>> >> >> >> 0000:07:00.2 >> >>>> >> >> >> 0000:04:00.0 >> >>>> >> >> >> 0000:04:00.1 >> >>>> >> >> >> 0000:04:00.2 >> >>>> >> >> >> 0000:02:00.0 >> >>>> >> >> >> 0000:02:00.1 >> >>>> >> >> >> 0000:02:00.2 >> >>>> >> >> >> >> >>>> >> >> >> # xm info >> >>>> >> >> >> host : test-box2 >> >>>> >> >> >> release : 2.6.31.13 >> >>>> >> >> >> version : #2 SMP Wed May 12 14:11:37 EDT 2010 >> >>>> >> >> >> machine : x86_64 >> >>>> >> >> >> nr_cpus : 8 >> >>>> >> >> >> nr_nodes : 1 >> >>>> >> >> >> cores_per_socket : 4 >> >>>> >> >> >> threads_per_core : 2 >> >>>> >> >> >> cpu_mhz : 2800 >> >>>> >> >> >> hw_caps : >> >>>> >> >> >> bfebfbff:28100800:00000000:00001b40:0098e3bd:00000000:00000001:00000000 >> >>>> >> >> >> virt_caps : hvm hvm_directio >> >>>> >> >> >> total_memory : 7950 >> >>>> >> >> >> free_memory : 7812 >> >>>> >> >> >> node_to_cpu : node0:0-7 >> >>>> >> >> >> node_to_memory : node0:7812 >> >>>> >> >> >> node_to_dma32_mem : node0:3249 >> >>>> >> >> >> max_node_id : 0 >> >>>> >> >> >> xen_major : 4 >> >>>> >> >> >> xen_minor : 0 >> >>>> >> >> >> xen_extra : .0 >> >>>> >> >> >> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 >> >>>> >> >> >> hvm-3.0-x86_32p hvm-3.0-x86_64 >> >>>> >> >> >> xen_scheduler : credit >> >>>> >> >> >> xen_pagesize : 4096 >> >>>> >> >> >> platform_params : virt_start=0xffff800000000000 >> >>>> >> >> >> xen_changeset : unavailable >> >>>> >> >> >> xen_commandline : iommu=1 dom0_mem=256M dom0_max_vcpus=1 >> >>>> >> >> >> dom0_vcpus_pin=true >> >>>> >> >> >> cc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1) >> >>>> >> >> >> cc_compile_by : root >> >>>> >> >> >> cc_compile_domain : >> >>>> >> >> >> cc_compile_date : Thu May 6 13:41:25 EDT 2010 >> >>>> >> >> >> xend_config_format : 4 >> >>>> >> >> >> >> >>>> >> >> >> # xm create vm-five.cfg >> >>>> >> >> >> Using config file "./vm-five.cfg". >> >>>> >> >> >> Error: Failed to assign device to IOMMU >> >>>> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >> >>>> >> >> >> >> >>>> >> >> >> I feel like I'm missing something really obvious but I've been at it >> >>>> >> >> >> for a while now and have run out of brain power. Anyone have any idea >> >>>> >> >> >> what might be wrong? >> >>>> >> >> >> >> >>>> >> >> >> - chris >> >>>> >> >> > >> >>>> >> >> >> __ __ _ _ ___ ___ >> >>>> >> >> >> \ \/ /___ _ __ | || | / _ \ / _ \ >> >>>> >> >> >> \ // _ \ \047_ \ | || |_| | | | | | | >> >>>> >> >> >> / \ __/ | | | |__ _| |_| | |_| | >> >>>> >> >> >> /_/\_\___|_| |_| |_|(_)___(_)___/ >> >>>> >> >> >> >> >>>> >> >> >> (XEN) Xen version 4.0.0 (root@) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) Thu May 6 13:41:25 EDT 2010 >> >>>> >> >> >> (XEN) Latest ChangeSet: unavailable >> >>>> >> >> >> (XEN) Command line: iommu=verbose dom0_mem=256M dom0_max_vcpus=1 dom0_vcpus_pin=true >> >>>> >> >> >> (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 - 000000000008f000 (usable) >> >>>> >> >> >> (XEN) 000000000008f000 - 0000000000090000 (reserved) >> >>>> >> >> >> (XEN) 0000000000090000 - 000000000009ec00 (usable) >> >>>> >> >> >> (XEN) 000000000009ec00 - 00000000000a0000 (reserved) >> >>>> >> >> >> (XEN) 00000000000e0000 - 0000000000100000 (reserved) >> >>>> >> >> >> (XEN) 0000000000100000 - 00000000cf4bd000 (usable) >> >>>> >> >> >> (XEN) 00000000cf4bd000 - 00000000cf4bf000 (reserved) >> >>>> >> >> >> (XEN) 00000000cf4bf000 - 00000000cf4c2000 (usable) >> >>>> >> >> >> (XEN) 00000000cf4c2000 - 00000000cf7bf000 (ACPI NVS) >> >>>> >> >> >> (XEN) 00000000cf7bf000 - 00000000cf7df000 (usable) >> >>>> >> >> >> (XEN) 00000000cf7df000 - 00000000cf7ff000 (ACPI data) >> >>>> >> >> >> (XEN) 00000000cf7ff000 - 00000000cf800000 (usable) >> >>>> >> >> >> (XEN) 00000000cf800000 - 00000000d0000000 (reserved) >> >>>> >> >> >> (XEN) 00000000f8000000 - 00000000fd000000 (reserved) >> >>>> >> >> >> (XEN) 00000000ffe00000 - 0000000100000000 (reserved) >> >>>> >> >> >> (XEN) 0000000100000000 - 0000000230000000 (usable) >> >>>> >> >> >> (XEN) ACPI: RSDP 000FE020, 0024 (r2 INTEL ) >> >>>> >> >> >> (XEN) ACPI: XSDT CF7FE120, 0074 (r1 INTEL DX58SO 11F6 1000013) >> >>>> >> >> >> (XEN) ACPI: FACP CF7FD000, 00F4 (r3 INTEL DX58SO 11F6 MSFT 100000D) >> >>>> >> >> >> (XEN) ACPI Warning (tbfadt-0444): Optional field "Pm2ControlBlock" has zero address or length: 0000000000000450/0 [20070126] >> >>>> >> >> >> (XEN) ACPI: DSDT CF7F8000, 4641 (r2 INTEL DX58SO 11F6 MSFT 100000D) >> >>>> >> >> >> (XEN) ACPI: FACS CF728000, 0040 >> >>>> >> >> >> (XEN) ACPI: APIC CF7F7000, 0138 (r2 INTEL DX58SO 11F6 MSFT 100000D) >> >>>> >> >> >> (XEN) ACPI: WDDT CF7F6000, 0040 (r1 INTEL DX58SO 11F6 MSFT 100000D) >> >>>> >> >> >> (XEN) ACPI: MCFG CF7F5000, 003C (r1 INTEL DX58SO 11F6 MSFT 100000D) >> >>>> >> >> >> (XEN) ACPI: ASF! CF7F4000, 00AC (r32 INTEL DX58SO 11F6 MSFT 100000D) >> >>>> >> >> >> (XEN) ACPI: HPET CF7F3000, 0038 (r1 INTEL DX58SO 11F6 MSFT 100000D) >> >>>> >> >> >> (XEN) ACPI: SSDT CF7E2000, E134 (r1 INTEL SSDT PM 11F6 MSFT 100000D) >> >>>> >> >> >> (XEN) ACPI: DMAR CF7DF000, 0140 (r1 INTEL DX58SO 11F6 MSFT 100000D) >> >>>> >> >> >> (XEN) ACPI: WDTT CF7F1000, 020C (r2 INTEL DX58SO 11F6 MSFT 100000D) >> >>>> >> >> >> (XEN) ACPI: ASPT CF7F2000, 0034 (r4 INTEL PerfTune 11F6 MSFT 100000D) >> >>>> >> >> >> (XEN) System RAM: 7950MB (8140820kB) >> >>>> >> >> >> (XEN) Domain heap initialised >> >>>> >> >> >> (XEN) Processor #0 7:10 APIC version 21 >> >>>> >> >> >> (XEN) Processor #2 7:10 APIC version 21 >> >>>> >> >> >> (XEN) Processor #4 7:10 APIC version 21 >> >>>> >> >> >> (XEN) Processor #6 7:10 APIC version 21 >> >>>> >> >> >> (XEN) Processor #1 7:10 APIC version 21 >> >>>> >> >> >> (XEN) Processor #3 7:10 APIC version 21 >> >>>> >> >> >> (XEN) Processor #5 7:10 APIC version 21 >> >>>> >> >> >> (XEN) Processor #7 7:10 APIC version 21 >> >>>> >> >> >> (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 >> >>>> >> >> >> (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs >> >>>> >> >> >> (XEN) [VT-D]dmar.c:679: Host address width 39 >> >>>> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: >> >>>> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = fe711000 >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1b.0 >> >>>> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: >> >>>> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = fe710000 >> >>>> >> >> >> (XEN) [VT-D]dmar.c:340: IOAPIC: f0:1f.7 >> >>>> >> >> >> (XEN) [VT-D]dmar.c:411: flags: INCLUDE_ALL >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e9000 end_address e9fff >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.1 >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ea000 end_address eafff >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.2 >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr eb000 end_address ebfff >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.0 >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e6000 end_address e6fff >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.1 >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e7000 end_address e7fff >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.2 >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e8000 end_address e8fff >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ec000 end_address eefff >> >>>> >> >> >> (XEN) Using scheduler: SMP Credit Scheduler (credit) >> >>>> >> >> >> (XEN) Detected 2800.125 MHz processor. >> >>>> >> >> >> (XEN) Initing memory sharing. >> >>>> >> >> >> (XEN) VMX: Supported advanced features: >> >>>> >> >> >> (XEN) - APIC MMIO access virtualisation >> >>>> >> >> >> (XEN) - APIC TPR shadow >> >>>> >> >> >> (XEN) - Extended Page Tables (EPT) >> >>>> >> >> >> (XEN) - Virtual-Processor Identifiers (VPID) >> >>>> >> >> >> (XEN) - Virtual NMI >> >>>> >> >> >> (XEN) - MSR direct-access bitmap >> >>>> >> >> >> (XEN) HVM: ASIDs enabled. >> >>>> >> >> >> (XEN) HVM: VMX enabled >> >>>> >> >> >> (XEN) HVM: Hardware Assisted Paging detected. >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = fe711000 iommu->reg = ffff82c3fff57000 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c9008010e60262 ecap = f0207a >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = fe710000 iommu->reg = ffff82c3fff56000 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c90780106f0462 ecap = f020fa >> >>>> >> >> >> (XEN) Intel VT-d Snoop Control not supported. >> >>>> >> >> >> (XEN) Intel VT-d DMA Passthrough not supported. >> >>>> >> >> >> (XEN) Intel VT-d Queued Invalidation supported. >> >>>> >> >> >> (XEN) Intel VT-d Interrupt Remapping supported. >> >>>> >> >> >> (XEN) I/O virtualisation enabled >> >>>> >> >> >> (XEN) I/O virtualisation for PV guests disabled >> >>>> >> >> >> (XEN) Total of 8 processors activated. >> >>>> >> >> >> (XEN) ENABLING IO-APIC IRQs >> >>>> >> >> >> (XEN) -> Using new ACK method >> >>>> >> >> >> (XEN) TSC is reliable, synchronization unnecessary >> >>>> >> >> >> (XEN) Platform timer is 14.318MHz HPET >> >>>> >> >> >> (XEN) Allocated console ring of 16 KiB. >> >>>> >> >> >> (XEN) Brought up 8 CPUs >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:0.0 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.0 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.1 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.0 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.1 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.2 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:14.3 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:19.0 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.0 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.1 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.2 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.7 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:1b.0 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.0 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.1 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.2 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.7 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.0 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.2 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.3 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.5 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.0 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.1 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.2 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.0 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.1 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.2 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 5:0.0 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.0 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.1 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.2 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.0 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.1 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.2 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = a:0.0 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.0 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.1 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.2 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.3 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.4 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.5 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.6 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.7 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.0 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.1 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.0 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.1 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.0 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.1 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.4 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.0 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.1 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.2 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.3 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.0 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.1 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.2 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.3 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.0 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.1 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.2 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.3 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = ffff82c3fff57000 >> >>>> >> >> >> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = ffff82c3fff56000 >> >>>> >> >> >> (XEN) *** LOADING DOMAIN 0 *** >> >>>> >> >> >> (XEN) Xen kernel: 64-bit, lsb, compat32 >> >>>> >> >> >> (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x26ae000 >> >>>> >> >> >> (XEN) PHYSICAL MEMORY ARRANGEMENT: >> >>>> >> >> >> (XEN) Dom0 alloc.: 0000000210000000->0000000220000000 >> >>>> >> >> >> (XEN) VIRTUAL MEMORY ARRANGEMENT: >> >>>> >> >> >> (XEN) Loaded kernel: ffffffff81000000->ffffffff826ae000 >> >>>> >> >> >> (XEN) Init. ramdisk: ffffffff826ae000->ffffffff8f4de600 >> >>>> >> >> >> (XEN) Phys-Mach map: ffffffff8f4df000->ffffffff8f55f000 >> >>>> >> >> >> (XEN) Start info: ffffffff8f55f000->ffffffff8f55f4b4 >> >>>> >> >> >> (XEN) Page tables: ffffffff8f560000->ffffffff8f5df000 >> >>>> >> >> >> (XEN) Boot stack: ffffffff8f5df000->ffffffff8f5e0000 >> >>>> >> >> >> (XEN) TOTAL: ffffffff80000000->ffffffff8f800000 >> >>>> >> >> >> (XEN) ENTRY ADDRESS: ffffffff81a10860 >> >>>> >> >> >> (XEN) Dom0 has maximum 1 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 \047CTRL-a\047 three times to switch input to Xen) >> >>>> >> >> >> (XEN) Freed 164kB init memory. >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 pirq=0 >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=2, irq=0 >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=000009f0 pirq=0 >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 3 already mapped >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 4 already mapped >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 5 already mapped >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 6 already mapped >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 7 already mapped >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 8 already mapped >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 9 already mapped >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 10 already mapped >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 11 already mapped >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 12 already mapped >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000009f0 >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 pirq=0 >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=23, irq=23 >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a929 >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a929 pirq=23 >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 pirq=16 >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 pirq=16 >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>>> >> >> > >> >>>> >> >> >> _______________________________________________ >> >>>> >> >> >> Xen-users mailing list >> >>>> >> >> >> Xen-users@lists.xensource.com >> >>>> >> >> >> http://lists.xensource.com/xen-users >> >>>> >> >> > >> >>>> >> > >> >>>> > >> >>> >> >> >> > > ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: RE: Xen4 / Intel DX58SO Mobo / VT-d not working 2010-05-14 19:18 ` [Xen-users] " chris @ 2010-05-14 19:21 ` Pasi Kärkkäinen 2010-05-14 19:46 ` [Xen-users] " chris 0 siblings, 1 reply; 32+ messages in thread From: Pasi Kärkkäinen @ 2010-05-14 19:21 UTC (permalink / raw) To: chris; +Cc: Xen-Devel List, Xen-Users List On Fri, May 14, 2010 at 03:18:02PM -0400, chris wrote: > It is a multifunction device, a pci-e usb controller, so I assumed all > them had to be passed through. I just changed it to only 02:00.0 and > same thing > > test-box2:~# cat /etc/xen/vm-five.cfg | grep pci > pci = ['02:00.0'] > test-box2:~# xm create /etc/xen/vm-five.cfg > Using config file "/etc/xen/vm-five.cfg". > Error: Failed to assign device to IOMMU > (0000:02:00.0@100,msitranslate=1,power_mgmt=0) > Hmm.. weird. Two things to try: 1) Try passthru some other device (which is just a single pci id) 2) Try passthru that pci-e usb controller to Linux PV guest and see if that works -- Pasi > > On Fri, May 14, 2010 at 3:11 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > > On Fri, May 14, 2010 at 03:05:49PM -0400, chris wrote: > >> Pasi, > >> > >> Tried latest stable/2.6.32.x per your advice, no change. Anyone on > >> xen-devel that can help me troubleshoot further? Everything looks > >> right, can't figure out why vt-d is not working but it must be some > >> kind of bug :( > >> > > > > Did you try the suggestion said earlier.. try to just passthru the first pci device? > > > > -- Pasi > > > >> test-box2:~# uname -a > >> Linux test-box2 2.6.32.12 #1 SMP Fri May 14 13:40:05 EDT 2010 x86_64 GNU/Linux > >> > >> test-box2:~# xm info | grep virt_caps > >> virt_caps : hvm hvm_directio > >> > >> test-box2:~# xm pci-list-assignable-devices > >> 0000:02:00.0 > >> 0000:02:00.1 > >> 0000:02:00.2 > >> > >> test-box2:~# xm create /etc/xen/vm-five.cfg > >> Using config file "/etc/xen/vm-five.cfg". > >> Error: Failed to assign device to IOMMU > >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) > >> > >> test-box2:~# cat /etc/xen/vm-five.cfg | grep -v '#' > >> kernel = '/usr/lib/xen/boot/hvmloader' > >> builder = 'hvm' > >> memory = '1792' > >> device_model='/usr/lib/xen/bin/qemu-dm' > >> disk = [ 'phy:/dev/storage/vm-five,ioemu:hda,w', > >> 'phy:/dev/sr0,ioemu:hdc:cdrom,r' > >> ] > >> name = 'vm-five' > >> vif = ['type=ioemu, bridge=eth0, mac=00:16:3D:37:A1:42'] > >> boot='dc' > >> cpus='0-1' > >> vcpus=2 > >> acpi=1 > >> ahci=1 > >> vnc=1 > >> sdl=0 > >> timer_mode=1 > >> usb=1 > >> usbdevice='tablet' > >> localtime=1 > >> pci = ['02:00.0','02:00.1','02:00.2'] > >> > >> On Thu, May 13, 2010 at 2:28 PM, chris <tknchris@gmail.com> wrote: > >> > Forwarding to xen-devel. Can't seem to get VT-d working with xen4 from > >> > tarball on xen.org 2.6.31.13 pv_ops dom0. On pasi's advice I tried > >> > switching to stable/2.6.32.x branch for dom0 and that doesnt even > >> > build. Did something change recently thats breaking compilation? > >> > > >> > Attached is xen dmesg with iommu=verbose loglvl=all guest_loglvl=all, > >> > and dom0 dmesg from 2.6.31.x > >> > > >> > Any ideas on why VT-d is not working on this board? Initialization > >> > looks good, xen reports hvm_directio capability, everything says VT-d > >> > should work until domain is created. > >> > > >> > Any ideas why stable/2.6.32.x wont build? > >> > > >> > - chris > >> > > >> > On Thu, May 13, 2010 at 2:07 PM, chris <tknchris@gmail.com> wrote: > >> >> I redid it with oldconfig which I didn't think would help and same > >> >> thing. I guess this tree is broken? Can someone else try and see if > >> >> they can build it? Ugh, whata day :) > >> >> > >> >> On Thu, May 13, 2010 at 1:58 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > >> >>> On Thu, May 13, 2010 at 01:55:25PM -0400, chris wrote: > >> >>>> I used the default config on the wiki which you created. Steps I took were: > >> >>>> > >> >>>> # make clean distclean > >> >>>> # wget -O .config > >> >>>> "http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.10-pvops-dom0-xen-stable-x86_64" > >> >>> > >> >>> You should do "make oldconfig" at this point. > >> >>> > >> >>>> # make -j8 bzImage > >> >>>> (blah blah) > >> >>>> LD vmlinux.o > >> >>>> MODPOST vmlinux.o > >> >>>> WARNING: modpost: Found 7 section mismatch(es). > >> >>>> To see full details build your kernel with: > >> >>>> 'make CONFIG_DEBUG_SECTION_MISMATCH=y' > >> >>>> GEN .version > >> >>>> CHK include/linux/compile.h > >> >>>> UPD include/linux/compile.h > >> >>>> CC init/version.o > >> >>>> LD init/built-in.o > >> >>>> LD .tmp_vmlinux1 > >> >>>> drivers/built-in.o: In function `do_hvm_suspend': > >> >>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: undefined reference > >> >>>> to `xenbus_suspend' > >> >>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: undefined reference > >> >>>> to `xenbus_resume' > >> >>>> make: *** [.tmp_vmlinux1] Error 1 > >> >>>> > >> >>> > >> >>> Hmm.. weird. I wonder if something has changed recently or what's going on in here.. > >> >>> > >> >>> -- Pasi > >> >>> > >> >>>> > >> >>>> On Thu, May 13, 2010 at 11:47 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > >> >>>> > On Thu, May 13, 2010 at 11:33:57AM -0400, chris wrote: > >> >>>> >> Successfully grabbed the sources and failed to build: > >> >>>> >> > >> >>>> >> LD .tmp_vmlinux1 > >> >>>> >> drivers/built-in.o: In function `do_hvm_suspend': > >> >>>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: undefined reference > >> >>>> >> to `xenbus_suspend' > >> >>>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: undefined reference > >> >>>> >> to `xenbus_resume' > >> >>>> >> make: *** [.tmp_vmlinux1] Error 1 > >> >>>> >> > >> >>>> >> :( > >> >>>> >> > >> >>>> > > >> >>>> > Try the example .config files provided on the wiki page. > >> >>>> > > >> >>>> > -- Pasi > >> >>>> > > >> >>>> >> On Thu, May 13, 2010 at 10:14 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > >> >>>> >> > On Thu, May 13, 2010 at 10:12:56AM -0400, chris wrote: > >> >>>> >> >> Pasi, > >> >>>> >> >> > >> >>>> >> >> How do I pull those kernel sources you referenced? I see it mentioned > >> >>>> >> >> on http://wiki.xensource.com/xenwiki/XenParavirtOps but no details on > >> >>>> >> >> how to retrieve it. > >> >>>> >> >> > >> >>>> >> > > >> >>>> >> > The instructions are there if you read it carefully.. > >> >>>> >> > There's the topic of how to switch branches. > >> >>>> >> > > >> >>>> >> > -- Pasi > >> >>>> >> > > >> >>>> >> >> - chris > >> >>>> >> >> > >> >>>> >> >> On Thu, May 13, 2010 at 8:29 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > >> >>>> >> >> > On Wed, May 12, 2010 at 08:41:34PM -0400, chris wrote: > >> >>>> >> >> >> When reading the vtdhowto I noticed the ability to set iommu=verbose. > >> >>>> >> >> >> Here is that output, I don't know if it helps at all to figure out > >> >>>> >> >> >> what is wrong. > >> >>>> >> >> >> > >> >>>> >> >> > > >> >>>> >> >> > That seems to be OK: > >> >>>> >> >> > > >> >>>> >> >> > (XEN) I/O virtualisation enabled > >> >>>> >> >> > (XEN) I/O virtualisation for PV guests disabled > >> >>>> >> >> > > >> >>>> >> >> > So hmm.. I wonder if it's related to MSI stuff? > >> >>>> >> >> > You could try xen.git xen/stable-2.6.32.x branch instead and see if that makes a difference.. > >> >>>> >> >> > > >> >>>> >> >> > -- Pasi > >> >>>> >> >> > > >> >>>> >> >> >> > >> >>>> >> >> >> ---------- Forwarded message ---------- > >> >>>> >> >> >> From: chris <tknchris@gmail.com> > >> >>>> >> >> >> Date: Wed, May 12, 2010 at 5:28 PM > >> >>>> >> >> >> Subject: Xen4 / Intel DX58SO Mobo / VT-d not working > >> >>>> >> >> >> To: Xen-Users List <xen-users@lists.xensource.com> > >> >>>> >> >> >> > >> >>>> >> >> >> > >> >>>> >> >> >> Hello, > >> >>>> >> >> >> > >> >>>> >> >> >> I've previously been successful with Xen4 and VT-d on other systems. I > >> >>>> >> >> >> am having trouble getting VT-d passthrough working to a WinXP domain > >> >>>> >> >> >> with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is enabled in bios, > >> >>>> >> >> >> xm info shows hvm_directio capability, I have iommu=1 set, I have the > >> >>>> >> >> >> devices bound to pciback on dom0 cmdline, xm > >> >>>> >> >> >> pci-list-assignable-devices shows the devices as assignable. When I > >> >>>> >> >> >> attempt to start the VM I get the error: > >> >>>> >> >> >> > >> >>>> >> >> >> Error: Failed to assign device to IOMMU > >> >>>> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) > >> >>>> >> >> >> > >> >>>> >> >> >> Below is all the information I can think of that would be useful to > >> >>>> >> >> >> help debug it: > >> >>>> >> >> >> > >> >>>> >> >> >> BIOS VT-d Enabled: > >> >>>> >> >> >> http://i43.tinypic.com/nl3a5e.jpg > >> >>>> >> >> >> http://i42.tinypic.com/nqvlu1.jpg > >> >>>> >> >> >> > >> >>>> >> >> >> grub entry: > >> >>>> >> >> >> > >> >>>> >> >> >> title Xen 4.0.0 / Debian GNU/Linux, kernel 2.6.31.13 > >> >>>> >> >> >> root (hd0,0) > >> >>>> >> >> >> kernel /boot/xen-4.0.0.gz iommu=1 dom0_mem=256M > >> >>>> >> >> >> dom0_max_vcpus=1 dom0_vcpus_pin=true > >> >>>> >> >> >> module /boot/vmlinuz-2.6.31.13 root=/dev/md0 ro console=tty0 > >> >>>> >> >> >> xen-pciback.permissive > >> >>>> >> >> >> xen-pciback.hide=(02:00.0)(02:00.1)(02:00.2)(04:00.0)(04:00.1)(04:00.2)(07:00.0)(07:00.1)(07:00.2)(09:00.0)(09:00.1)(09:00.2) > >> >>>> >> >> >> module /boot/initrd.img-2.6.31.13 > >> >>>> >> >> >> > >> >>>> >> >> >> # xm pci-list-assignable-devices > >> >>>> >> >> >> 0000:09:00.0 > >> >>>> >> >> >> 0000:09:00.1 > >> >>>> >> >> >> 0000:09:00.2 > >> >>>> >> >> >> 0000:07:00.0 > >> >>>> >> >> >> 0000:07:00.1 > >> >>>> >> >> >> 0000:07:00.2 > >> >>>> >> >> >> 0000:04:00.0 > >> >>>> >> >> >> 0000:04:00.1 > >> >>>> >> >> >> 0000:04:00.2 > >> >>>> >> >> >> 0000:02:00.0 > >> >>>> >> >> >> 0000:02:00.1 > >> >>>> >> >> >> 0000:02:00.2 > >> >>>> >> >> >> > >> >>>> >> >> >> # xm info > >> >>>> >> >> >> host : test-box2 > >> >>>> >> >> >> release : 2.6.31.13 > >> >>>> >> >> >> version : #2 SMP Wed May 12 14:11:37 EDT 2010 > >> >>>> >> >> >> machine : x86_64 > >> >>>> >> >> >> nr_cpus : 8 > >> >>>> >> >> >> nr_nodes : 1 > >> >>>> >> >> >> cores_per_socket : 4 > >> >>>> >> >> >> threads_per_core : 2 > >> >>>> >> >> >> cpu_mhz : 2800 > >> >>>> >> >> >> hw_caps : > >> >>>> >> >> >> bfebfbff:28100800:00000000:00001b40:0098e3bd:00000000:00000001:00000000 > >> >>>> >> >> >> virt_caps : hvm hvm_directio > >> >>>> >> >> >> total_memory : 7950 > >> >>>> >> >> >> free_memory : 7812 > >> >>>> >> >> >> node_to_cpu : node0:0-7 > >> >>>> >> >> >> node_to_memory : node0:7812 > >> >>>> >> >> >> node_to_dma32_mem : node0:3249 > >> >>>> >> >> >> max_node_id : 0 > >> >>>> >> >> >> xen_major : 4 > >> >>>> >> >> >> xen_minor : 0 > >> >>>> >> >> >> xen_extra : .0 > >> >>>> >> >> >> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > >> >>>> >> >> >> hvm-3.0-x86_32p hvm-3.0-x86_64 > >> >>>> >> >> >> xen_scheduler : credit > >> >>>> >> >> >> xen_pagesize : 4096 > >> >>>> >> >> >> platform_params : virt_start=0xffff800000000000 > >> >>>> >> >> >> xen_changeset : unavailable > >> >>>> >> >> >> xen_commandline : iommu=1 dom0_mem=256M dom0_max_vcpus=1 > >> >>>> >> >> >> dom0_vcpus_pin=true > >> >>>> >> >> >> cc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1) > >> >>>> >> >> >> cc_compile_by : root > >> >>>> >> >> >> cc_compile_domain : > >> >>>> >> >> >> cc_compile_date : Thu May 6 13:41:25 EDT 2010 > >> >>>> >> >> >> xend_config_format : 4 > >> >>>> >> >> >> > >> >>>> >> >> >> # xm create vm-five.cfg > >> >>>> >> >> >> Using config file "./vm-five.cfg". > >> >>>> >> >> >> Error: Failed to assign device to IOMMU > >> >>>> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) > >> >>>> >> >> >> > >> >>>> >> >> >> I feel like I'm missing something really obvious but I've been at it > >> >>>> >> >> >> for a while now and have run out of brain power. Anyone have any idea > >> >>>> >> >> >> what might be wrong? > >> >>>> >> >> >> > >> >>>> >> >> >> - chris > >> >>>> >> >> > > >> >>>> >> >> >> __ __ _ _ ___ ___ > >> >>>> >> >> >> \ \/ /___ _ __ | || | / _ \ / _ \ > >> >>>> >> >> >> \ // _ \ \047_ \ | || |_| | | | | | | > >> >>>> >> >> >> / \ __/ | | | |__ _| |_| | |_| | > >> >>>> >> >> >> /_/\_\___|_| |_| |_|(_)___(_)___/ > >> >>>> >> >> >> > >> >>>> >> >> >> (XEN) Xen version 4.0.0 (root@) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) Thu May 6 13:41:25 EDT 2010 > >> >>>> >> >> >> (XEN) Latest ChangeSet: unavailable > >> >>>> >> >> >> (XEN) Command line: iommu=verbose dom0_mem=256M dom0_max_vcpus=1 dom0_vcpus_pin=true > >> >>>> >> >> >> (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 - 000000000008f000 (usable) > >> >>>> >> >> >> (XEN) 000000000008f000 - 0000000000090000 (reserved) > >> >>>> >> >> >> (XEN) 0000000000090000 - 000000000009ec00 (usable) > >> >>>> >> >> >> (XEN) 000000000009ec00 - 00000000000a0000 (reserved) > >> >>>> >> >> >> (XEN) 00000000000e0000 - 0000000000100000 (reserved) > >> >>>> >> >> >> (XEN) 0000000000100000 - 00000000cf4bd000 (usable) > >> >>>> >> >> >> (XEN) 00000000cf4bd000 - 00000000cf4bf000 (reserved) > >> >>>> >> >> >> (XEN) 00000000cf4bf000 - 00000000cf4c2000 (usable) > >> >>>> >> >> >> (XEN) 00000000cf4c2000 - 00000000cf7bf000 (ACPI NVS) > >> >>>> >> >> >> (XEN) 00000000cf7bf000 - 00000000cf7df000 (usable) > >> >>>> >> >> >> (XEN) 00000000cf7df000 - 00000000cf7ff000 (ACPI data) > >> >>>> >> >> >> (XEN) 00000000cf7ff000 - 00000000cf800000 (usable) > >> >>>> >> >> >> (XEN) 00000000cf800000 - 00000000d0000000 (reserved) > >> >>>> >> >> >> (XEN) 00000000f8000000 - 00000000fd000000 (reserved) > >> >>>> >> >> >> (XEN) 00000000ffe00000 - 0000000100000000 (reserved) > >> >>>> >> >> >> (XEN) 0000000100000000 - 0000000230000000 (usable) > >> >>>> >> >> >> (XEN) ACPI: RSDP 000FE020, 0024 (r2 INTEL ) > >> >>>> >> >> >> (XEN) ACPI: XSDT CF7FE120, 0074 (r1 INTEL DX58SO 11F6 1000013) > >> >>>> >> >> >> (XEN) ACPI: FACP CF7FD000, 00F4 (r3 INTEL DX58SO 11F6 MSFT 100000D) > >> >>>> >> >> >> (XEN) ACPI Warning (tbfadt-0444): Optional field "Pm2ControlBlock" has zero address or length: 0000000000000450/0 [20070126] > >> >>>> >> >> >> (XEN) ACPI: DSDT CF7F8000, 4641 (r2 INTEL DX58SO 11F6 MSFT 100000D) > >> >>>> >> >> >> (XEN) ACPI: FACS CF728000, 0040 > >> >>>> >> >> >> (XEN) ACPI: APIC CF7F7000, 0138 (r2 INTEL DX58SO 11F6 MSFT 100000D) > >> >>>> >> >> >> (XEN) ACPI: WDDT CF7F6000, 0040 (r1 INTEL DX58SO 11F6 MSFT 100000D) > >> >>>> >> >> >> (XEN) ACPI: MCFG CF7F5000, 003C (r1 INTEL DX58SO 11F6 MSFT 100000D) > >> >>>> >> >> >> (XEN) ACPI: ASF! CF7F4000, 00AC (r32 INTEL DX58SO 11F6 MSFT 100000D) > >> >>>> >> >> >> (XEN) ACPI: HPET CF7F3000, 0038 (r1 INTEL DX58SO 11F6 MSFT 100000D) > >> >>>> >> >> >> (XEN) ACPI: SSDT CF7E2000, E134 (r1 INTEL SSDT PM 11F6 MSFT 100000D) > >> >>>> >> >> >> (XEN) ACPI: DMAR CF7DF000, 0140 (r1 INTEL DX58SO 11F6 MSFT 100000D) > >> >>>> >> >> >> (XEN) ACPI: WDTT CF7F1000, 020C (r2 INTEL DX58SO 11F6 MSFT 100000D) > >> >>>> >> >> >> (XEN) ACPI: ASPT CF7F2000, 0034 (r4 INTEL PerfTune 11F6 MSFT 100000D) > >> >>>> >> >> >> (XEN) System RAM: 7950MB (8140820kB) > >> >>>> >> >> >> (XEN) Domain heap initialised > >> >>>> >> >> >> (XEN) Processor #0 7:10 APIC version 21 > >> >>>> >> >> >> (XEN) Processor #2 7:10 APIC version 21 > >> >>>> >> >> >> (XEN) Processor #4 7:10 APIC version 21 > >> >>>> >> >> >> (XEN) Processor #6 7:10 APIC version 21 > >> >>>> >> >> >> (XEN) Processor #1 7:10 APIC version 21 > >> >>>> >> >> >> (XEN) Processor #3 7:10 APIC version 21 > >> >>>> >> >> >> (XEN) Processor #5 7:10 APIC version 21 > >> >>>> >> >> >> (XEN) Processor #7 7:10 APIC version 21 > >> >>>> >> >> >> (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 > >> >>>> >> >> >> (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > >> >>>> >> >> >> (XEN) [VT-D]dmar.c:679: Host address width 39 > >> >>>> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: > >> >>>> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = fe711000 > >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1b.0 > >> >>>> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: > >> >>>> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = fe710000 > >> >>>> >> >> >> (XEN) [VT-D]dmar.c:340: IOAPIC: f0:1f.7 > >> >>>> >> >> >> (XEN) [VT-D]dmar.c:411: flags: INCLUDE_ALL > >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 > >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e9000 end_address e9fff > >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.1 > >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ea000 end_address eafff > >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.2 > >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr eb000 end_address ebfff > >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.0 > >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e6000 end_address e6fff > >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.1 > >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e7000 end_address e7fff > >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.2 > >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e8000 end_address e8fff > >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 > >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ec000 end_address eefff > >> >>>> >> >> >> (XEN) Using scheduler: SMP Credit Scheduler (credit) > >> >>>> >> >> >> (XEN) Detected 2800.125 MHz processor. > >> >>>> >> >> >> (XEN) Initing memory sharing. > >> >>>> >> >> >> (XEN) VMX: Supported advanced features: > >> >>>> >> >> >> (XEN) - APIC MMIO access virtualisation > >> >>>> >> >> >> (XEN) - APIC TPR shadow > >> >>>> >> >> >> (XEN) - Extended Page Tables (EPT) > >> >>>> >> >> >> (XEN) - Virtual-Processor Identifiers (VPID) > >> >>>> >> >> >> (XEN) - Virtual NMI > >> >>>> >> >> >> (XEN) - MSR direct-access bitmap > >> >>>> >> >> >> (XEN) HVM: ASIDs enabled. > >> >>>> >> >> >> (XEN) HVM: VMX enabled > >> >>>> >> >> >> (XEN) HVM: Hardware Assisted Paging detected. > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = fe711000 iommu->reg = ffff82c3fff57000 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c9008010e60262 ecap = f0207a > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = fe710000 iommu->reg = ffff82c3fff56000 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c90780106f0462 ecap = f020fa > >> >>>> >> >> >> (XEN) Intel VT-d Snoop Control not supported. > >> >>>> >> >> >> (XEN) Intel VT-d DMA Passthrough not supported. > >> >>>> >> >> >> (XEN) Intel VT-d Queued Invalidation supported. > >> >>>> >> >> >> (XEN) Intel VT-d Interrupt Remapping supported. > >> >>>> >> >> >> (XEN) I/O virtualisation enabled > >> >>>> >> >> >> (XEN) I/O virtualisation for PV guests disabled > >> >>>> >> >> >> (XEN) Total of 8 processors activated. > >> >>>> >> >> >> (XEN) ENABLING IO-APIC IRQs > >> >>>> >> >> >> (XEN) -> Using new ACK method > >> >>>> >> >> >> (XEN) TSC is reliable, synchronization unnecessary > >> >>>> >> >> >> (XEN) Platform timer is 14.318MHz HPET > >> >>>> >> >> >> (XEN) Allocated console ring of 16 KiB. > >> >>>> >> >> >> (XEN) Brought up 8 CPUs > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:0.0 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.0 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.1 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.0 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.1 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.2 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:14.3 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:19.0 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.0 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.1 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.2 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.7 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:1b.0 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.0 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.1 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.2 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.7 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.0 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.2 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.3 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.5 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.0 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.1 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.2 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.0 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.1 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.2 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 5:0.0 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.0 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.1 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.2 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.0 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.1 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.2 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = a:0.0 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.0 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.1 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.2 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.3 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.4 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.5 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.6 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.7 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.0 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.1 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.0 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.1 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.0 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.1 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.4 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.0 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.1 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.2 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.3 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.0 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.1 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.2 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.3 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.0 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.1 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.2 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.3 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = ffff82c3fff57000 > >> >>>> >> >> >> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = ffff82c3fff56000 > >> >>>> >> >> >> (XEN) *** LOADING DOMAIN 0 *** > >> >>>> >> >> >> (XEN) Xen kernel: 64-bit, lsb, compat32 > >> >>>> >> >> >> (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x26ae000 > >> >>>> >> >> >> (XEN) PHYSICAL MEMORY ARRANGEMENT: > >> >>>> >> >> >> (XEN) Dom0 alloc.: 0000000210000000->0000000220000000 > >> >>>> >> >> >> (XEN) VIRTUAL MEMORY ARRANGEMENT: > >> >>>> >> >> >> (XEN) Loaded kernel: ffffffff81000000->ffffffff826ae000 > >> >>>> >> >> >> (XEN) Init. ramdisk: ffffffff826ae000->ffffffff8f4de600 > >> >>>> >> >> >> (XEN) Phys-Mach map: ffffffff8f4df000->ffffffff8f55f000 > >> >>>> >> >> >> (XEN) Start info: ffffffff8f55f000->ffffffff8f55f4b4 > >> >>>> >> >> >> (XEN) Page tables: ffffffff8f560000->ffffffff8f5df000 > >> >>>> >> >> >> (XEN) Boot stack: ffffffff8f5df000->ffffffff8f5e0000 > >> >>>> >> >> >> (XEN) TOTAL: ffffffff80000000->ffffffff8f800000 > >> >>>> >> >> >> (XEN) ENTRY ADDRESS: ffffffff81a10860 > >> >>>> >> >> >> (XEN) Dom0 has maximum 1 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 \047CTRL-a\047 three times to switch input to Xen) > >> >>>> >> >> >> (XEN) Freed 164kB init memory. > >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 > >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 > >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 pirq=0 > >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=2, irq=0 > >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 > >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=000009f0 pirq=0 > >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 3 already mapped > >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 4 already mapped > >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 5 already mapped > >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 6 already mapped > >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 7 already mapped > >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 8 already mapped > >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 9 already mapped > >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 10 already mapped > >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 11 already mapped > >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 12 already mapped > >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 > >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000009f0 > >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 pirq=0 > >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 > >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 > >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 > >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 > >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 > >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 > >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=23, irq=23 > >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a929 > >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a929 pirq=23 > >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 > >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 > >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 > >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 > >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 > >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 > >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 > >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 > >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 pirq=16 > >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 > >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 > >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 pirq=16 > >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 > >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 > >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 > >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 > >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 > >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 > >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >> >>>> >> >> > > >> >>>> >> >> >> _______________________________________________ > >> >>>> >> >> >> Xen-users mailing list > >> >>>> >> >> >> Xen-users@lists.xensource.com > >> >>>> >> >> >> http://lists.xensource.com/xen-users > >> >>>> >> >> > > >> >>>> >> > > >> >>>> > > >> >>> > >> >> > >> > > > ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [Xen-users] RE: Xen4 / Intel DX58SO Mobo / VT-d not working 2010-05-14 19:21 ` Pasi Kärkkäinen @ 2010-05-14 19:46 ` chris 2010-05-14 20:39 ` chris 2010-05-14 21:25 ` Re: [Xen-users] " Sander Eikelenboom 0 siblings, 2 replies; 32+ messages in thread From: chris @ 2010-05-14 19:46 UTC (permalink / raw) To: Pasi Kärkkäinen; +Cc: Xen-Devel List, Xen-Users List I added a pci sound card and interestingly that works. I'm digging around for another pci-e device to try to identify if its all pci-e or only this device. Strange this is that I have a few other machines with this same usb controller which is working on 3.4.2. *scratches head* - chris On Fri, May 14, 2010 at 3:21 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > On Fri, May 14, 2010 at 03:18:02PM -0400, chris wrote: >> It is a multifunction device, a pci-e usb controller, so I assumed all >> them had to be passed through. I just changed it to only 02:00.0 and >> same thing >> >> test-box2:~# cat /etc/xen/vm-five.cfg | grep pci >> pci = ['02:00.0'] >> test-box2:~# xm create /etc/xen/vm-five.cfg >> Using config file "/etc/xen/vm-five.cfg". >> Error: Failed to assign device to IOMMU >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >> > > Hmm.. weird. > > Two things to try: > > 1) Try passthru some other device (which is just a single pci id) > 2) Try passthru that pci-e usb controller to Linux PV guest and see if that works > > -- Pasi > >> >> On Fri, May 14, 2010 at 3:11 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >> > On Fri, May 14, 2010 at 03:05:49PM -0400, chris wrote: >> >> Pasi, >> >> >> >> Tried latest stable/2.6.32.x per your advice, no change. Anyone on >> >> xen-devel that can help me troubleshoot further? Everything looks >> >> right, can't figure out why vt-d is not working but it must be some >> >> kind of bug :( >> >> >> > >> > Did you try the suggestion said earlier.. try to just passthru the first pci device? >> > >> > -- Pasi >> > >> >> test-box2:~# uname -a >> >> Linux test-box2 2.6.32.12 #1 SMP Fri May 14 13:40:05 EDT 2010 x86_64 GNU/Linux >> >> >> >> test-box2:~# xm info | grep virt_caps >> >> virt_caps : hvm hvm_directio >> >> >> >> test-box2:~# xm pci-list-assignable-devices >> >> 0000:02:00.0 >> >> 0000:02:00.1 >> >> 0000:02:00.2 >> >> >> >> test-box2:~# xm create /etc/xen/vm-five.cfg >> >> Using config file "/etc/xen/vm-five.cfg". >> >> Error: Failed to assign device to IOMMU >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >> >> >> >> test-box2:~# cat /etc/xen/vm-five.cfg | grep -v '#' >> >> kernel = '/usr/lib/xen/boot/hvmloader' >> >> builder = 'hvm' >> >> memory = '1792' >> >> device_model='/usr/lib/xen/bin/qemu-dm' >> >> disk = [ 'phy:/dev/storage/vm-five,ioemu:hda,w', >> >> 'phy:/dev/sr0,ioemu:hdc:cdrom,r' >> >> ] >> >> name = 'vm-five' >> >> vif = ['type=ioemu, bridge=eth0, mac=00:16:3D:37:A1:42'] >> >> boot='dc' >> >> cpus='0-1' >> >> vcpus=2 >> >> acpi=1 >> >> ahci=1 >> >> vnc=1 >> >> sdl=0 >> >> timer_mode=1 >> >> usb=1 >> >> usbdevice='tablet' >> >> localtime=1 >> >> pci = ['02:00.0','02:00.1','02:00.2'] >> >> >> >> On Thu, May 13, 2010 at 2:28 PM, chris <tknchris@gmail.com> wrote: >> >> > Forwarding to xen-devel. Can't seem to get VT-d working with xen4 from >> >> > tarball on xen.org 2.6.31.13 pv_ops dom0. On pasi's advice I tried >> >> > switching to stable/2.6.32.x branch for dom0 and that doesnt even >> >> > build. Did something change recently thats breaking compilation? >> >> > >> >> > Attached is xen dmesg with iommu=verbose loglvl=all guest_loglvl=all, >> >> > and dom0 dmesg from 2.6.31.x >> >> > >> >> > Any ideas on why VT-d is not working on this board? Initialization >> >> > looks good, xen reports hvm_directio capability, everything says VT-d >> >> > should work until domain is created. >> >> > >> >> > Any ideas why stable/2.6.32.x wont build? >> >> > >> >> > - chris >> >> > >> >> > On Thu, May 13, 2010 at 2:07 PM, chris <tknchris@gmail.com> wrote: >> >> >> I redid it with oldconfig which I didn't think would help and same >> >> >> thing. I guess this tree is broken? Can someone else try and see if >> >> >> they can build it? Ugh, whata day :) >> >> >> >> >> >> On Thu, May 13, 2010 at 1:58 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >> >> >>> On Thu, May 13, 2010 at 01:55:25PM -0400, chris wrote: >> >> >>>> I used the default config on the wiki which you created. Steps I took were: >> >> >>>> >> >> >>>> # make clean distclean >> >> >>>> # wget -O .config >> >> >>>> "http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.10-pvops-dom0-xen-stable-x86_64" >> >> >>> >> >> >>> You should do "make oldconfig" at this point. >> >> >>> >> >> >>>> # make -j8 bzImage >> >> >>>> (blah blah) >> >> >>>> LD vmlinux.o >> >> >>>> MODPOST vmlinux.o >> >> >>>> WARNING: modpost: Found 7 section mismatch(es). >> >> >>>> To see full details build your kernel with: >> >> >>>> 'make CONFIG_DEBUG_SECTION_MISMATCH=y' >> >> >>>> GEN .version >> >> >>>> CHK include/linux/compile.h >> >> >>>> UPD include/linux/compile.h >> >> >>>> CC init/version.o >> >> >>>> LD init/built-in.o >> >> >>>> LD .tmp_vmlinux1 >> >> >>>> drivers/built-in.o: In function `do_hvm_suspend': >> >> >>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: undefined reference >> >> >>>> to `xenbus_suspend' >> >> >>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: undefined reference >> >> >>>> to `xenbus_resume' >> >> >>>> make: *** [.tmp_vmlinux1] Error 1 >> >> >>>> >> >> >>> >> >> >>> Hmm.. weird. I wonder if something has changed recently or what's going on in here.. >> >> >>> >> >> >>> -- Pasi >> >> >>> >> >> >>>> >> >> >>>> On Thu, May 13, 2010 at 11:47 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >> >> >>>> > On Thu, May 13, 2010 at 11:33:57AM -0400, chris wrote: >> >> >>>> >> Successfully grabbed the sources and failed to build: >> >> >>>> >> >> >> >>>> >> LD .tmp_vmlinux1 >> >> >>>> >> drivers/built-in.o: In function `do_hvm_suspend': >> >> >>>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: undefined reference >> >> >>>> >> to `xenbus_suspend' >> >> >>>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: undefined reference >> >> >>>> >> to `xenbus_resume' >> >> >>>> >> make: *** [.tmp_vmlinux1] Error 1 >> >> >>>> >> >> >> >>>> >> :( >> >> >>>> >> >> >> >>>> > >> >> >>>> > Try the example .config files provided on the wiki page. >> >> >>>> > >> >> >>>> > -- Pasi >> >> >>>> > >> >> >>>> >> On Thu, May 13, 2010 at 10:14 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >> >> >>>> >> > On Thu, May 13, 2010 at 10:12:56AM -0400, chris wrote: >> >> >>>> >> >> Pasi, >> >> >>>> >> >> >> >> >>>> >> >> How do I pull those kernel sources you referenced? I see it mentioned >> >> >>>> >> >> on http://wiki.xensource.com/xenwiki/XenParavirtOps but no details on >> >> >>>> >> >> how to retrieve it. >> >> >>>> >> >> >> >> >>>> >> > >> >> >>>> >> > The instructions are there if you read it carefully.. >> >> >>>> >> > There's the topic of how to switch branches. >> >> >>>> >> > >> >> >>>> >> > -- Pasi >> >> >>>> >> > >> >> >>>> >> >> - chris >> >> >>>> >> >> >> >> >>>> >> >> On Thu, May 13, 2010 at 8:29 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >> >> >>>> >> >> > On Wed, May 12, 2010 at 08:41:34PM -0400, chris wrote: >> >> >>>> >> >> >> When reading the vtdhowto I noticed the ability to set iommu=verbose. >> >> >>>> >> >> >> Here is that output, I don't know if it helps at all to figure out >> >> >>>> >> >> >> what is wrong. >> >> >>>> >> >> >> >> >> >>>> >> >> > >> >> >>>> >> >> > That seems to be OK: >> >> >>>> >> >> > >> >> >>>> >> >> > (XEN) I/O virtualisation enabled >> >> >>>> >> >> > (XEN) I/O virtualisation for PV guests disabled >> >> >>>> >> >> > >> >> >>>> >> >> > So hmm.. I wonder if it's related to MSI stuff? >> >> >>>> >> >> > You could try xen.git xen/stable-2.6.32.x branch instead and see if that makes a difference.. >> >> >>>> >> >> > >> >> >>>> >> >> > -- Pasi >> >> >>>> >> >> > >> >> >>>> >> >> >> >> >> >>>> >> >> >> ---------- Forwarded message ---------- >> >> >>>> >> >> >> From: chris <tknchris@gmail.com> >> >> >>>> >> >> >> Date: Wed, May 12, 2010 at 5:28 PM >> >> >>>> >> >> >> Subject: Xen4 / Intel DX58SO Mobo / VT-d not working >> >> >>>> >> >> >> To: Xen-Users List <xen-users@lists.xensource.com> >> >> >>>> >> >> >> >> >> >>>> >> >> >> >> >> >>>> >> >> >> Hello, >> >> >>>> >> >> >> >> >> >>>> >> >> >> I've previously been successful with Xen4 and VT-d on other systems. I >> >> >>>> >> >> >> am having trouble getting VT-d passthrough working to a WinXP domain >> >> >>>> >> >> >> with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is enabled in bios, >> >> >>>> >> >> >> xm info shows hvm_directio capability, I have iommu=1 set, I have the >> >> >>>> >> >> >> devices bound to pciback on dom0 cmdline, xm >> >> >>>> >> >> >> pci-list-assignable-devices shows the devices as assignable. When I >> >> >>>> >> >> >> attempt to start the VM I get the error: >> >> >>>> >> >> >> >> >> >>>> >> >> >> Error: Failed to assign device to IOMMU >> >> >>>> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >> >> >>>> >> >> >> >> >> >>>> >> >> >> Below is all the information I can think of that would be useful to >> >> >>>> >> >> >> help debug it: >> >> >>>> >> >> >> >> >> >>>> >> >> >> BIOS VT-d Enabled: >> >> >>>> >> >> >> http://i43.tinypic.com/nl3a5e.jpg >> >> >>>> >> >> >> http://i42.tinypic.com/nqvlu1.jpg >> >> >>>> >> >> >> >> >> >>>> >> >> >> grub entry: >> >> >>>> >> >> >> >> >> >>>> >> >> >> title Xen 4.0.0 / Debian GNU/Linux, kernel 2.6.31.13 >> >> >>>> >> >> >> root (hd0,0) >> >> >>>> >> >> >> kernel /boot/xen-4.0.0.gz iommu=1 dom0_mem=256M >> >> >>>> >> >> >> dom0_max_vcpus=1 dom0_vcpus_pin=true >> >> >>>> >> >> >> module /boot/vmlinuz-2.6.31.13 root=/dev/md0 ro console=tty0 >> >> >>>> >> >> >> xen-pciback.permissive >> >> >>>> >> >> >> xen-pciback.hide=(02:00.0)(02:00.1)(02:00.2)(04:00.0)(04:00.1)(04:00.2)(07:00.0)(07:00.1)(07:00.2)(09:00.0)(09:00.1)(09:00.2) >> >> >>>> >> >> >> module /boot/initrd.img-2.6.31.13 >> >> >>>> >> >> >> >> >> >>>> >> >> >> # xm pci-list-assignable-devices >> >> >>>> >> >> >> 0000:09:00.0 >> >> >>>> >> >> >> 0000:09:00.1 >> >> >>>> >> >> >> 0000:09:00.2 >> >> >>>> >> >> >> 0000:07:00.0 >> >> >>>> >> >> >> 0000:07:00.1 >> >> >>>> >> >> >> 0000:07:00.2 >> >> >>>> >> >> >> 0000:04:00.0 >> >> >>>> >> >> >> 0000:04:00.1 >> >> >>>> >> >> >> 0000:04:00.2 >> >> >>>> >> >> >> 0000:02:00.0 >> >> >>>> >> >> >> 0000:02:00.1 >> >> >>>> >> >> >> 0000:02:00.2 >> >> >>>> >> >> >> >> >> >>>> >> >> >> # xm info >> >> >>>> >> >> >> host : test-box2 >> >> >>>> >> >> >> release : 2.6.31.13 >> >> >>>> >> >> >> version : #2 SMP Wed May 12 14:11:37 EDT 2010 >> >> >>>> >> >> >> machine : x86_64 >> >> >>>> >> >> >> nr_cpus : 8 >> >> >>>> >> >> >> nr_nodes : 1 >> >> >>>> >> >> >> cores_per_socket : 4 >> >> >>>> >> >> >> threads_per_core : 2 >> >> >>>> >> >> >> cpu_mhz : 2800 >> >> >>>> >> >> >> hw_caps : >> >> >>>> >> >> >> bfebfbff:28100800:00000000:00001b40:0098e3bd:00000000:00000001:00000000 >> >> >>>> >> >> >> virt_caps : hvm hvm_directio >> >> >>>> >> >> >> total_memory : 7950 >> >> >>>> >> >> >> free_memory : 7812 >> >> >>>> >> >> >> node_to_cpu : node0:0-7 >> >> >>>> >> >> >> node_to_memory : node0:7812 >> >> >>>> >> >> >> node_to_dma32_mem : node0:3249 >> >> >>>> >> >> >> max_node_id : 0 >> >> >>>> >> >> >> xen_major : 4 >> >> >>>> >> >> >> xen_minor : 0 >> >> >>>> >> >> >> xen_extra : .0 >> >> >>>> >> >> >> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 >> >> >>>> >> >> >> hvm-3.0-x86_32p hvm-3.0-x86_64 >> >> >>>> >> >> >> xen_scheduler : credit >> >> >>>> >> >> >> xen_pagesize : 4096 >> >> >>>> >> >> >> platform_params : virt_start=0xffff800000000000 >> >> >>>> >> >> >> xen_changeset : unavailable >> >> >>>> >> >> >> xen_commandline : iommu=1 dom0_mem=256M dom0_max_vcpus=1 >> >> >>>> >> >> >> dom0_vcpus_pin=true >> >> >>>> >> >> >> cc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1) >> >> >>>> >> >> >> cc_compile_by : root >> >> >>>> >> >> >> cc_compile_domain : >> >> >>>> >> >> >> cc_compile_date : Thu May 6 13:41:25 EDT 2010 >> >> >>>> >> >> >> xend_config_format : 4 >> >> >>>> >> >> >> >> >> >>>> >> >> >> # xm create vm-five.cfg >> >> >>>> >> >> >> Using config file "./vm-five.cfg". >> >> >>>> >> >> >> Error: Failed to assign device to IOMMU >> >> >>>> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >> >> >>>> >> >> >> >> >> >>>> >> >> >> I feel like I'm missing something really obvious but I've been at it >> >> >>>> >> >> >> for a while now and have run out of brain power. Anyone have any idea >> >> >>>> >> >> >> what might be wrong? >> >> >>>> >> >> >> >> >> >>>> >> >> >> - chris >> >> >>>> >> >> > >> >> >>>> >> >> >> __ __ _ _ ___ ___ >> >> >>>> >> >> >> \ \/ /___ _ __ | || | / _ \ / _ \ >> >> >>>> >> >> >> \ // _ \ \047_ \ | || |_| | | | | | | >> >> >>>> >> >> >> / \ __/ | | | |__ _| |_| | |_| | >> >> >>>> >> >> >> /_/\_\___|_| |_| |_|(_)___(_)___/ >> >> >>>> >> >> >> >> >> >>>> >> >> >> (XEN) Xen version 4.0.0 (root@) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) Thu May 6 13:41:25 EDT 2010 >> >> >>>> >> >> >> (XEN) Latest ChangeSet: unavailable >> >> >>>> >> >> >> (XEN) Command line: iommu=verbose dom0_mem=256M dom0_max_vcpus=1 dom0_vcpus_pin=true >> >> >>>> >> >> >> (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 - 000000000008f000 (usable) >> >> >>>> >> >> >> (XEN) 000000000008f000 - 0000000000090000 (reserved) >> >> >>>> >> >> >> (XEN) 0000000000090000 - 000000000009ec00 (usable) >> >> >>>> >> >> >> (XEN) 000000000009ec00 - 00000000000a0000 (reserved) >> >> >>>> >> >> >> (XEN) 00000000000e0000 - 0000000000100000 (reserved) >> >> >>>> >> >> >> (XEN) 0000000000100000 - 00000000cf4bd000 (usable) >> >> >>>> >> >> >> (XEN) 00000000cf4bd000 - 00000000cf4bf000 (reserved) >> >> >>>> >> >> >> (XEN) 00000000cf4bf000 - 00000000cf4c2000 (usable) >> >> >>>> >> >> >> (XEN) 00000000cf4c2000 - 00000000cf7bf000 (ACPI NVS) >> >> >>>> >> >> >> (XEN) 00000000cf7bf000 - 00000000cf7df000 (usable) >> >> >>>> >> >> >> (XEN) 00000000cf7df000 - 00000000cf7ff000 (ACPI data) >> >> >>>> >> >> >> (XEN) 00000000cf7ff000 - 00000000cf800000 (usable) >> >> >>>> >> >> >> (XEN) 00000000cf800000 - 00000000d0000000 (reserved) >> >> >>>> >> >> >> (XEN) 00000000f8000000 - 00000000fd000000 (reserved) >> >> >>>> >> >> >> (XEN) 00000000ffe00000 - 0000000100000000 (reserved) >> >> >>>> >> >> >> (XEN) 0000000100000000 - 0000000230000000 (usable) >> >> >>>> >> >> >> (XEN) ACPI: RSDP 000FE020, 0024 (r2 INTEL ) >> >> >>>> >> >> >> (XEN) ACPI: XSDT CF7FE120, 0074 (r1 INTEL DX58SO 11F6 1000013) >> >> >>>> >> >> >> (XEN) ACPI: FACP CF7FD000, 00F4 (r3 INTEL DX58SO 11F6 MSFT 100000D) >> >> >>>> >> >> >> (XEN) ACPI Warning (tbfadt-0444): Optional field "Pm2ControlBlock" has zero address or length: 0000000000000450/0 [20070126] >> >> >>>> >> >> >> (XEN) ACPI: DSDT CF7F8000, 4641 (r2 INTEL DX58SO 11F6 MSFT 100000D) >> >> >>>> >> >> >> (XEN) ACPI: FACS CF728000, 0040 >> >> >>>> >> >> >> (XEN) ACPI: APIC CF7F7000, 0138 (r2 INTEL DX58SO 11F6 MSFT 100000D) >> >> >>>> >> >> >> (XEN) ACPI: WDDT CF7F6000, 0040 (r1 INTEL DX58SO 11F6 MSFT 100000D) >> >> >>>> >> >> >> (XEN) ACPI: MCFG CF7F5000, 003C (r1 INTEL DX58SO 11F6 MSFT 100000D) >> >> >>>> >> >> >> (XEN) ACPI: ASF! CF7F4000, 00AC (r32 INTEL DX58SO 11F6 MSFT 100000D) >> >> >>>> >> >> >> (XEN) ACPI: HPET CF7F3000, 0038 (r1 INTEL DX58SO 11F6 MSFT 100000D) >> >> >>>> >> >> >> (XEN) ACPI: SSDT CF7E2000, E134 (r1 INTEL SSDT PM 11F6 MSFT 100000D) >> >> >>>> >> >> >> (XEN) ACPI: DMAR CF7DF000, 0140 (r1 INTEL DX58SO 11F6 MSFT 100000D) >> >> >>>> >> >> >> (XEN) ACPI: WDTT CF7F1000, 020C (r2 INTEL DX58SO 11F6 MSFT 100000D) >> >> >>>> >> >> >> (XEN) ACPI: ASPT CF7F2000, 0034 (r4 INTEL PerfTune 11F6 MSFT 100000D) >> >> >>>> >> >> >> (XEN) System RAM: 7950MB (8140820kB) >> >> >>>> >> >> >> (XEN) Domain heap initialised >> >> >>>> >> >> >> (XEN) Processor #0 7:10 APIC version 21 >> >> >>>> >> >> >> (XEN) Processor #2 7:10 APIC version 21 >> >> >>>> >> >> >> (XEN) Processor #4 7:10 APIC version 21 >> >> >>>> >> >> >> (XEN) Processor #6 7:10 APIC version 21 >> >> >>>> >> >> >> (XEN) Processor #1 7:10 APIC version 21 >> >> >>>> >> >> >> (XEN) Processor #3 7:10 APIC version 21 >> >> >>>> >> >> >> (XEN) Processor #5 7:10 APIC version 21 >> >> >>>> >> >> >> (XEN) Processor #7 7:10 APIC version 21 >> >> >>>> >> >> >> (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 >> >> >>>> >> >> >> (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs >> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:679: Host address width 39 >> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: >> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = fe711000 >> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1b.0 >> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: >> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = fe710000 >> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:340: IOAPIC: f0:1f.7 >> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:411: flags: INCLUDE_ALL >> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 >> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e9000 end_address e9fff >> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.1 >> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ea000 end_address eafff >> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.2 >> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr eb000 end_address ebfff >> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.0 >> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e6000 end_address e6fff >> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.1 >> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e7000 end_address e7fff >> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.2 >> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e8000 end_address e8fff >> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 >> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ec000 end_address eefff >> >> >>>> >> >> >> (XEN) Using scheduler: SMP Credit Scheduler (credit) >> >> >>>> >> >> >> (XEN) Detected 2800.125 MHz processor. >> >> >>>> >> >> >> (XEN) Initing memory sharing. >> >> >>>> >> >> >> (XEN) VMX: Supported advanced features: >> >> >>>> >> >> >> (XEN) - APIC MMIO access virtualisation >> >> >>>> >> >> >> (XEN) - APIC TPR shadow >> >> >>>> >> >> >> (XEN) - Extended Page Tables (EPT) >> >> >>>> >> >> >> (XEN) - Virtual-Processor Identifiers (VPID) >> >> >>>> >> >> >> (XEN) - Virtual NMI >> >> >>>> >> >> >> (XEN) - MSR direct-access bitmap >> >> >>>> >> >> >> (XEN) HVM: ASIDs enabled. >> >> >>>> >> >> >> (XEN) HVM: VMX enabled >> >> >>>> >> >> >> (XEN) HVM: Hardware Assisted Paging detected. >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = fe711000 iommu->reg = ffff82c3fff57000 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c9008010e60262 ecap = f0207a >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = fe710000 iommu->reg = ffff82c3fff56000 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c90780106f0462 ecap = f020fa >> >> >>>> >> >> >> (XEN) Intel VT-d Snoop Control not supported. >> >> >>>> >> >> >> (XEN) Intel VT-d DMA Passthrough not supported. >> >> >>>> >> >> >> (XEN) Intel VT-d Queued Invalidation supported. >> >> >>>> >> >> >> (XEN) Intel VT-d Interrupt Remapping supported. >> >> >>>> >> >> >> (XEN) I/O virtualisation enabled >> >> >>>> >> >> >> (XEN) I/O virtualisation for PV guests disabled >> >> >>>> >> >> >> (XEN) Total of 8 processors activated. >> >> >>>> >> >> >> (XEN) ENABLING IO-APIC IRQs >> >> >>>> >> >> >> (XEN) -> Using new ACK method >> >> >>>> >> >> >> (XEN) TSC is reliable, synchronization unnecessary >> >> >>>> >> >> >> (XEN) Platform timer is 14.318MHz HPET >> >> >>>> >> >> >> (XEN) Allocated console ring of 16 KiB. >> >> >>>> >> >> >> (XEN) Brought up 8 CPUs >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:0.0 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.0 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.1 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.0 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.1 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.2 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:14.3 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:19.0 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.0 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.1 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.2 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.7 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:1b.0 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.0 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.1 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.2 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.7 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.0 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.2 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.3 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.5 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.0 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.1 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.2 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.0 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.1 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.2 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 5:0.0 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.0 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.1 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.2 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.0 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.1 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.2 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = a:0.0 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.0 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.1 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.2 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.3 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.4 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.5 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.6 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.7 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.0 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.1 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.0 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.1 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.0 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.1 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.4 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.0 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.1 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.2 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.3 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.0 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.1 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.2 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.3 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.0 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.1 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.2 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.3 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = ffff82c3fff57000 >> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = ffff82c3fff56000 >> >> >>>> >> >> >> (XEN) *** LOADING DOMAIN 0 *** >> >> >>>> >> >> >> (XEN) Xen kernel: 64-bit, lsb, compat32 >> >> >>>> >> >> >> (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x26ae000 >> >> >>>> >> >> >> (XEN) PHYSICAL MEMORY ARRANGEMENT: >> >> >>>> >> >> >> (XEN) Dom0 alloc.: 0000000210000000->0000000220000000 >> >> >>>> >> >> >> (XEN) VIRTUAL MEMORY ARRANGEMENT: >> >> >>>> >> >> >> (XEN) Loaded kernel: ffffffff81000000->ffffffff826ae000 >> >> >>>> >> >> >> (XEN) Init. ramdisk: ffffffff826ae000->ffffffff8f4de600 >> >> >>>> >> >> >> (XEN) Phys-Mach map: ffffffff8f4df000->ffffffff8f55f000 >> >> >>>> >> >> >> (XEN) Start info: ffffffff8f55f000->ffffffff8f55f4b4 >> >> >>>> >> >> >> (XEN) Page tables: ffffffff8f560000->ffffffff8f5df000 >> >> >>>> >> >> >> (XEN) Boot stack: ffffffff8f5df000->ffffffff8f5e0000 >> >> >>>> >> >> >> (XEN) TOTAL: ffffffff80000000->ffffffff8f800000 >> >> >>>> >> >> >> (XEN) ENTRY ADDRESS: ffffffff81a10860 >> >> >>>> >> >> >> (XEN) Dom0 has maximum 1 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 \047CTRL-a\047 three times to switch input to Xen) >> >> >>>> >> >> >> (XEN) Freed 164kB init memory. >> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 pirq=0 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=2, irq=0 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=000009f0 pirq=0 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 3 already mapped >> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 4 already mapped >> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 5 already mapped >> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 6 already mapped >> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 7 already mapped >> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 8 already mapped >> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 9 already mapped >> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 10 already mapped >> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 11 already mapped >> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 12 already mapped >> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000009f0 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 pirq=0 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=23, irq=23 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a929 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a929 pirq=23 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 pirq=16 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 pirq=16 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 >> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >> >>>> >> >> > >> >> >>>> >> >> >> _______________________________________________ >> >> >>>> >> >> >> Xen-users mailing list >> >> >>>> >> >> >> Xen-users@lists.xensource.com >> >> >>>> >> >> >> http://lists.xensource.com/xen-users >> >> >>>> >> >> > >> >> >>>> >> > >> >> >>>> > >> >> >>> >> >> >> >> >> > >> > > ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: RE: Xen4 / Intel DX58SO Mobo / VT-d not working 2010-05-14 19:46 ` [Xen-users] " chris @ 2010-05-14 20:39 ` chris 2010-05-14 20:50 ` Pasi Kärkkäinen 2010-05-14 21:25 ` Re: [Xen-users] " Sander Eikelenboom 1 sibling, 1 reply; 32+ messages in thread From: chris @ 2010-05-14 20:39 UTC (permalink / raw) To: Pasi Kärkkäinen; +Cc: Xen-Devel List, Xen-Users List Alright so a pci sound card works, I tried a geforce 8600 pci e card and while vga passthrough didnt work it did seem to attach to the domain ok. So I guess the problem must be somehow related to the device. I'm still confused since it works in another box. I remember there was some reassign_resources or something, maybe the issue is with some resources the card uses? Below is a lspci -vv of the card 02:00.0 USB Controller: NEC Corporation USB (rev 43) (prog-if 10 [OHCI]) Subsystem: NEC Corporation Hama USB 2.0 CardBus Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Interrupt: pin A routed to IRQ 16 Region 0: Memory at d2502000 (32-bit, non-prefetchable) [disabled] [size=4K] Capabilities: [40] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: pciback 02:00.1 USB Controller: NEC Corporation USB (rev 43) (prog-if 10 [OHCI]) Subsystem: NEC Corporation Hama USB 2.0 CardBus Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Interrupt: pin B routed to IRQ 17 Region 0: Memory at d2501000 (32-bit, non-prefetchable) [disabled] [size=4K] Capabilities: [40] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: pciback 02:00.2 USB Controller: NEC Corporation USB 2.0 (rev 04) (prog-if 20 [EHCI]) Subsystem: NEC Corporation USB 2.0 Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Interrupt: pin C routed to IRQ 18 Region 0: Memory at d2500000 (32-bit, non-prefetchable) [disabled] [size=256] Capabilities: [40] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: pciback On Fri, May 14, 2010 at 3:46 PM, chris <tknchris@gmail.com> wrote: > I added a pci sound card and interestingly that works. I'm digging > around for another pci-e device to try to identify if its all pci-e or > only this device. Strange this is that I have a few other machines > with this same usb controller which is working on 3.4.2. > > *scratches head* > > - chris > > On Fri, May 14, 2010 at 3:21 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >> On Fri, May 14, 2010 at 03:18:02PM -0400, chris wrote: >>> It is a multifunction device, a pci-e usb controller, so I assumed all >>> them had to be passed through. I just changed it to only 02:00.0 and >>> same thing >>> >>> test-box2:~# cat /etc/xen/vm-five.cfg | grep pci >>> pci = ['02:00.0'] >>> test-box2:~# xm create /etc/xen/vm-five.cfg >>> Using config file "/etc/xen/vm-five.cfg". >>> Error: Failed to assign device to IOMMU >>> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>> >> >> Hmm.. weird. >> >> Two things to try: >> >> 1) Try passthru some other device (which is just a single pci id) >> 2) Try passthru that pci-e usb controller to Linux PV guest and see if that works >> >> -- Pasi >> >>> >>> On Fri, May 14, 2010 at 3:11 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>> > On Fri, May 14, 2010 at 03:05:49PM -0400, chris wrote: >>> >> Pasi, >>> >> >>> >> Tried latest stable/2.6.32.x per your advice, no change. Anyone on >>> >> xen-devel that can help me troubleshoot further? Everything looks >>> >> right, can't figure out why vt-d is not working but it must be some >>> >> kind of bug :( >>> >> >>> > >>> > Did you try the suggestion said earlier.. try to just passthru the first pci device? >>> > >>> > -- Pasi >>> > >>> >> test-box2:~# uname -a >>> >> Linux test-box2 2.6.32.12 #1 SMP Fri May 14 13:40:05 EDT 2010 x86_64 GNU/Linux >>> >> >>> >> test-box2:~# xm info | grep virt_caps >>> >> virt_caps : hvm hvm_directio >>> >> >>> >> test-box2:~# xm pci-list-assignable-devices >>> >> 0000:02:00.0 >>> >> 0000:02:00.1 >>> >> 0000:02:00.2 >>> >> >>> >> test-box2:~# xm create /etc/xen/vm-five.cfg >>> >> Using config file "/etc/xen/vm-five.cfg". >>> >> Error: Failed to assign device to IOMMU >>> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>> >> >>> >> test-box2:~# cat /etc/xen/vm-five.cfg | grep -v '#' >>> >> kernel = '/usr/lib/xen/boot/hvmloader' >>> >> builder = 'hvm' >>> >> memory = '1792' >>> >> device_model='/usr/lib/xen/bin/qemu-dm' >>> >> disk = [ 'phy:/dev/storage/vm-five,ioemu:hda,w', >>> >> 'phy:/dev/sr0,ioemu:hdc:cdrom,r' >>> >> ] >>> >> name = 'vm-five' >>> >> vif = ['type=ioemu, bridge=eth0, mac=00:16:3D:37:A1:42'] >>> >> boot='dc' >>> >> cpus='0-1' >>> >> vcpus=2 >>> >> acpi=1 >>> >> ahci=1 >>> >> vnc=1 >>> >> sdl=0 >>> >> timer_mode=1 >>> >> usb=1 >>> >> usbdevice='tablet' >>> >> localtime=1 >>> >> pci = ['02:00.0','02:00.1','02:00.2'] >>> >> >>> >> On Thu, May 13, 2010 at 2:28 PM, chris <tknchris@gmail.com> wrote: >>> >> > Forwarding to xen-devel. Can't seem to get VT-d working with xen4 from >>> >> > tarball on xen.org 2.6.31.13 pv_ops dom0. On pasi's advice I tried >>> >> > switching to stable/2.6.32.x branch for dom0 and that doesnt even >>> >> > build. Did something change recently thats breaking compilation? >>> >> > >>> >> > Attached is xen dmesg with iommu=verbose loglvl=all guest_loglvl=all, >>> >> > and dom0 dmesg from 2.6.31.x >>> >> > >>> >> > Any ideas on why VT-d is not working on this board? Initialization >>> >> > looks good, xen reports hvm_directio capability, everything says VT-d >>> >> > should work until domain is created. >>> >> > >>> >> > Any ideas why stable/2.6.32.x wont build? >>> >> > >>> >> > - chris >>> >> > >>> >> > On Thu, May 13, 2010 at 2:07 PM, chris <tknchris@gmail.com> wrote: >>> >> >> I redid it with oldconfig which I didn't think would help and same >>> >> >> thing. I guess this tree is broken? Can someone else try and see if >>> >> >> they can build it? Ugh, whata day :) >>> >> >> >>> >> >> On Thu, May 13, 2010 at 1:58 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>> >> >>> On Thu, May 13, 2010 at 01:55:25PM -0400, chris wrote: >>> >> >>>> I used the default config on the wiki which you created. Steps I took were: >>> >> >>>> >>> >> >>>> # make clean distclean >>> >> >>>> # wget -O .config >>> >> >>>> "http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.10-pvops-dom0-xen-stable-x86_64" >>> >> >>> >>> >> >>> You should do "make oldconfig" at this point. >>> >> >>> >>> >> >>>> # make -j8 bzImage >>> >> >>>> (blah blah) >>> >> >>>> LD vmlinux.o >>> >> >>>> MODPOST vmlinux.o >>> >> >>>> WARNING: modpost: Found 7 section mismatch(es). >>> >> >>>> To see full details build your kernel with: >>> >> >>>> 'make CONFIG_DEBUG_SECTION_MISMATCH=y' >>> >> >>>> GEN .version >>> >> >>>> CHK include/linux/compile.h >>> >> >>>> UPD include/linux/compile.h >>> >> >>>> CC init/version.o >>> >> >>>> LD init/built-in.o >>> >> >>>> LD .tmp_vmlinux1 >>> >> >>>> drivers/built-in.o: In function `do_hvm_suspend': >>> >> >>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: undefined reference >>> >> >>>> to `xenbus_suspend' >>> >> >>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: undefined reference >>> >> >>>> to `xenbus_resume' >>> >> >>>> make: *** [.tmp_vmlinux1] Error 1 >>> >> >>>> >>> >> >>> >>> >> >>> Hmm.. weird. I wonder if something has changed recently or what's going on in here.. >>> >> >>> >>> >> >>> -- Pasi >>> >> >>> >>> >> >>>> >>> >> >>>> On Thu, May 13, 2010 at 11:47 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>> >> >>>> > On Thu, May 13, 2010 at 11:33:57AM -0400, chris wrote: >>> >> >>>> >> Successfully grabbed the sources and failed to build: >>> >> >>>> >> >>> >> >>>> >> LD .tmp_vmlinux1 >>> >> >>>> >> drivers/built-in.o: In function `do_hvm_suspend': >>> >> >>>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: undefined reference >>> >> >>>> >> to `xenbus_suspend' >>> >> >>>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: undefined reference >>> >> >>>> >> to `xenbus_resume' >>> >> >>>> >> make: *** [.tmp_vmlinux1] Error 1 >>> >> >>>> >> >>> >> >>>> >> :( >>> >> >>>> >> >>> >> >>>> > >>> >> >>>> > Try the example .config files provided on the wiki page. >>> >> >>>> > >>> >> >>>> > -- Pasi >>> >> >>>> > >>> >> >>>> >> On Thu, May 13, 2010 at 10:14 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>> >> >>>> >> > On Thu, May 13, 2010 at 10:12:56AM -0400, chris wrote: >>> >> >>>> >> >> Pasi, >>> >> >>>> >> >> >>> >> >>>> >> >> How do I pull those kernel sources you referenced? I see it mentioned >>> >> >>>> >> >> on http://wiki.xensource.com/xenwiki/XenParavirtOps but no details on >>> >> >>>> >> >> how to retrieve it. >>> >> >>>> >> >> >>> >> >>>> >> > >>> >> >>>> >> > The instructions are there if you read it carefully.. >>> >> >>>> >> > There's the topic of how to switch branches. >>> >> >>>> >> > >>> >> >>>> >> > -- Pasi >>> >> >>>> >> > >>> >> >>>> >> >> - chris >>> >> >>>> >> >> >>> >> >>>> >> >> On Thu, May 13, 2010 at 8:29 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>> >> >>>> >> >> > On Wed, May 12, 2010 at 08:41:34PM -0400, chris wrote: >>> >> >>>> >> >> >> When reading the vtdhowto I noticed the ability to set iommu=verbose. >>> >> >>>> >> >> >> Here is that output, I don't know if it helps at all to figure out >>> >> >>>> >> >> >> what is wrong. >>> >> >>>> >> >> >> >>> >> >>>> >> >> > >>> >> >>>> >> >> > That seems to be OK: >>> >> >>>> >> >> > >>> >> >>>> >> >> > (XEN) I/O virtualisation enabled >>> >> >>>> >> >> > (XEN) I/O virtualisation for PV guests disabled >>> >> >>>> >> >> > >>> >> >>>> >> >> > So hmm.. I wonder if it's related to MSI stuff? >>> >> >>>> >> >> > You could try xen.git xen/stable-2.6.32.x branch instead and see if that makes a difference.. >>> >> >>>> >> >> > >>> >> >>>> >> >> > -- Pasi >>> >> >>>> >> >> > >>> >> >>>> >> >> >> >>> >> >>>> >> >> >> ---------- Forwarded message ---------- >>> >> >>>> >> >> >> From: chris <tknchris@gmail.com> >>> >> >>>> >> >> >> Date: Wed, May 12, 2010 at 5:28 PM >>> >> >>>> >> >> >> Subject: Xen4 / Intel DX58SO Mobo / VT-d not working >>> >> >>>> >> >> >> To: Xen-Users List <xen-users@lists.xensource.com> >>> >> >>>> >> >> >> >>> >> >>>> >> >> >> >>> >> >>>> >> >> >> Hello, >>> >> >>>> >> >> >> >>> >> >>>> >> >> >> I've previously been successful with Xen4 and VT-d on other systems. I >>> >> >>>> >> >> >> am having trouble getting VT-d passthrough working to a WinXP domain >>> >> >>>> >> >> >> with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is enabled in bios, >>> >> >>>> >> >> >> xm info shows hvm_directio capability, I have iommu=1 set, I have the >>> >> >>>> >> >> >> devices bound to pciback on dom0 cmdline, xm >>> >> >>>> >> >> >> pci-list-assignable-devices shows the devices as assignable. When I >>> >> >>>> >> >> >> attempt to start the VM I get the error: >>> >> >>>> >> >> >> >>> >> >>>> >> >> >> Error: Failed to assign device to IOMMU >>> >> >>>> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>> >> >>>> >> >> >> >>> >> >>>> >> >> >> Below is all the information I can think of that would be useful to >>> >> >>>> >> >> >> help debug it: >>> >> >>>> >> >> >> >>> >> >>>> >> >> >> BIOS VT-d Enabled: >>> >> >>>> >> >> >> http://i43.tinypic.com/nl3a5e.jpg >>> >> >>>> >> >> >> http://i42.tinypic.com/nqvlu1.jpg >>> >> >>>> >> >> >> >>> >> >>>> >> >> >> grub entry: >>> >> >>>> >> >> >> >>> >> >>>> >> >> >> title Xen 4.0.0 / Debian GNU/Linux, kernel 2.6.31.13 >>> >> >>>> >> >> >> root (hd0,0) >>> >> >>>> >> >> >> kernel /boot/xen-4.0.0.gz iommu=1 dom0_mem=256M >>> >> >>>> >> >> >> dom0_max_vcpus=1 dom0_vcpus_pin=true >>> >> >>>> >> >> >> module /boot/vmlinuz-2.6.31.13 root=/dev/md0 ro console=tty0 >>> >> >>>> >> >> >> xen-pciback.permissive >>> >> >>>> >> >> >> xen-pciback.hide=(02:00.0)(02:00.1)(02:00.2)(04:00.0)(04:00.1)(04:00.2)(07:00.0)(07:00.1)(07:00.2)(09:00.0)(09:00.1)(09:00.2) >>> >> >>>> >> >> >> module /boot/initrd.img-2.6.31.13 >>> >> >>>> >> >> >> >>> >> >>>> >> >> >> # xm pci-list-assignable-devices >>> >> >>>> >> >> >> 0000:09:00.0 >>> >> >>>> >> >> >> 0000:09:00.1 >>> >> >>>> >> >> >> 0000:09:00.2 >>> >> >>>> >> >> >> 0000:07:00.0 >>> >> >>>> >> >> >> 0000:07:00.1 >>> >> >>>> >> >> >> 0000:07:00.2 >>> >> >>>> >> >> >> 0000:04:00.0 >>> >> >>>> >> >> >> 0000:04:00.1 >>> >> >>>> >> >> >> 0000:04:00.2 >>> >> >>>> >> >> >> 0000:02:00.0 >>> >> >>>> >> >> >> 0000:02:00.1 >>> >> >>>> >> >> >> 0000:02:00.2 >>> >> >>>> >> >> >> >>> >> >>>> >> >> >> # xm info >>> >> >>>> >> >> >> host : test-box2 >>> >> >>>> >> >> >> release : 2.6.31.13 >>> >> >>>> >> >> >> version : #2 SMP Wed May 12 14:11:37 EDT 2010 >>> >> >>>> >> >> >> machine : x86_64 >>> >> >>>> >> >> >> nr_cpus : 8 >>> >> >>>> >> >> >> nr_nodes : 1 >>> >> >>>> >> >> >> cores_per_socket : 4 >>> >> >>>> >> >> >> threads_per_core : 2 >>> >> >>>> >> >> >> cpu_mhz : 2800 >>> >> >>>> >> >> >> hw_caps : >>> >> >>>> >> >> >> bfebfbff:28100800:00000000:00001b40:0098e3bd:00000000:00000001:00000000 >>> >> >>>> >> >> >> virt_caps : hvm hvm_directio >>> >> >>>> >> >> >> total_memory : 7950 >>> >> >>>> >> >> >> free_memory : 7812 >>> >> >>>> >> >> >> node_to_cpu : node0:0-7 >>> >> >>>> >> >> >> node_to_memory : node0:7812 >>> >> >>>> >> >> >> node_to_dma32_mem : node0:3249 >>> >> >>>> >> >> >> max_node_id : 0 >>> >> >>>> >> >> >> xen_major : 4 >>> >> >>>> >> >> >> xen_minor : 0 >>> >> >>>> >> >> >> xen_extra : .0 >>> >> >>>> >> >> >> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 >>> >> >>>> >> >> >> hvm-3.0-x86_32p hvm-3.0-x86_64 >>> >> >>>> >> >> >> xen_scheduler : credit >>> >> >>>> >> >> >> xen_pagesize : 4096 >>> >> >>>> >> >> >> platform_params : virt_start=0xffff800000000000 >>> >> >>>> >> >> >> xen_changeset : unavailable >>> >> >>>> >> >> >> xen_commandline : iommu=1 dom0_mem=256M dom0_max_vcpus=1 >>> >> >>>> >> >> >> dom0_vcpus_pin=true >>> >> >>>> >> >> >> cc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1) >>> >> >>>> >> >> >> cc_compile_by : root >>> >> >>>> >> >> >> cc_compile_domain : >>> >> >>>> >> >> >> cc_compile_date : Thu May 6 13:41:25 EDT 2010 >>> >> >>>> >> >> >> xend_config_format : 4 >>> >> >>>> >> >> >> >>> >> >>>> >> >> >> # xm create vm-five.cfg >>> >> >>>> >> >> >> Using config file "./vm-five.cfg". >>> >> >>>> >> >> >> Error: Failed to assign device to IOMMU >>> >> >>>> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>> >> >>>> >> >> >> >>> >> >>>> >> >> >> I feel like I'm missing something really obvious but I've been at it >>> >> >>>> >> >> >> for a while now and have run out of brain power. Anyone have any idea >>> >> >>>> >> >> >> what might be wrong? >>> >> >>>> >> >> >> >>> >> >>>> >> >> >> - chris >>> >> >>>> >> >> > >>> >> >>>> >> >> >> __ __ _ _ ___ ___ >>> >> >>>> >> >> >> \ \/ /___ _ __ | || | / _ \ / _ \ >>> >> >>>> >> >> >> \ // _ \ \047_ \ | || |_| | | | | | | >>> >> >>>> >> >> >> / \ __/ | | | |__ _| |_| | |_| | >>> >> >>>> >> >> >> /_/\_\___|_| |_| |_|(_)___(_)___/ >>> >> >>>> >> >> >> >>> >> >>>> >> >> >> (XEN) Xen version 4.0.0 (root@) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) Thu May 6 13:41:25 EDT 2010 >>> >> >>>> >> >> >> (XEN) Latest ChangeSet: unavailable >>> >> >>>> >> >> >> (XEN) Command line: iommu=verbose dom0_mem=256M dom0_max_vcpus=1 dom0_vcpus_pin=true >>> >> >>>> >> >> >> (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 - 000000000008f000 (usable) >>> >> >>>> >> >> >> (XEN) 000000000008f000 - 0000000000090000 (reserved) >>> >> >>>> >> >> >> (XEN) 0000000000090000 - 000000000009ec00 (usable) >>> >> >>>> >> >> >> (XEN) 000000000009ec00 - 00000000000a0000 (reserved) >>> >> >>>> >> >> >> (XEN) 00000000000e0000 - 0000000000100000 (reserved) >>> >> >>>> >> >> >> (XEN) 0000000000100000 - 00000000cf4bd000 (usable) >>> >> >>>> >> >> >> (XEN) 00000000cf4bd000 - 00000000cf4bf000 (reserved) >>> >> >>>> >> >> >> (XEN) 00000000cf4bf000 - 00000000cf4c2000 (usable) >>> >> >>>> >> >> >> (XEN) 00000000cf4c2000 - 00000000cf7bf000 (ACPI NVS) >>> >> >>>> >> >> >> (XEN) 00000000cf7bf000 - 00000000cf7df000 (usable) >>> >> >>>> >> >> >> (XEN) 00000000cf7df000 - 00000000cf7ff000 (ACPI data) >>> >> >>>> >> >> >> (XEN) 00000000cf7ff000 - 00000000cf800000 (usable) >>> >> >>>> >> >> >> (XEN) 00000000cf800000 - 00000000d0000000 (reserved) >>> >> >>>> >> >> >> (XEN) 00000000f8000000 - 00000000fd000000 (reserved) >>> >> >>>> >> >> >> (XEN) 00000000ffe00000 - 0000000100000000 (reserved) >>> >> >>>> >> >> >> (XEN) 0000000100000000 - 0000000230000000 (usable) >>> >> >>>> >> >> >> (XEN) ACPI: RSDP 000FE020, 0024 (r2 INTEL ) >>> >> >>>> >> >> >> (XEN) ACPI: XSDT CF7FE120, 0074 (r1 INTEL DX58SO 11F6 1000013) >>> >> >>>> >> >> >> (XEN) ACPI: FACP CF7FD000, 00F4 (r3 INTEL DX58SO 11F6 MSFT 100000D) >>> >> >>>> >> >> >> (XEN) ACPI Warning (tbfadt-0444): Optional field "Pm2ControlBlock" has zero address or length: 0000000000000450/0 [20070126] >>> >> >>>> >> >> >> (XEN) ACPI: DSDT CF7F8000, 4641 (r2 INTEL DX58SO 11F6 MSFT 100000D) >>> >> >>>> >> >> >> (XEN) ACPI: FACS CF728000, 0040 >>> >> >>>> >> >> >> (XEN) ACPI: APIC CF7F7000, 0138 (r2 INTEL DX58SO 11F6 MSFT 100000D) >>> >> >>>> >> >> >> (XEN) ACPI: WDDT CF7F6000, 0040 (r1 INTEL DX58SO 11F6 MSFT 100000D) >>> >> >>>> >> >> >> (XEN) ACPI: MCFG CF7F5000, 003C (r1 INTEL DX58SO 11F6 MSFT 100000D) >>> >> >>>> >> >> >> (XEN) ACPI: ASF! CF7F4000, 00AC (r32 INTEL DX58SO 11F6 MSFT 100000D) >>> >> >>>> >> >> >> (XEN) ACPI: HPET CF7F3000, 0038 (r1 INTEL DX58SO 11F6 MSFT 100000D) >>> >> >>>> >> >> >> (XEN) ACPI: SSDT CF7E2000, E134 (r1 INTEL SSDT PM 11F6 MSFT 100000D) >>> >> >>>> >> >> >> (XEN) ACPI: DMAR CF7DF000, 0140 (r1 INTEL DX58SO 11F6 MSFT 100000D) >>> >> >>>> >> >> >> (XEN) ACPI: WDTT CF7F1000, 020C (r2 INTEL DX58SO 11F6 MSFT 100000D) >>> >> >>>> >> >> >> (XEN) ACPI: ASPT CF7F2000, 0034 (r4 INTEL PerfTune 11F6 MSFT 100000D) >>> >> >>>> >> >> >> (XEN) System RAM: 7950MB (8140820kB) >>> >> >>>> >> >> >> (XEN) Domain heap initialised >>> >> >>>> >> >> >> (XEN) Processor #0 7:10 APIC version 21 >>> >> >>>> >> >> >> (XEN) Processor #2 7:10 APIC version 21 >>> >> >>>> >> >> >> (XEN) Processor #4 7:10 APIC version 21 >>> >> >>>> >> >> >> (XEN) Processor #6 7:10 APIC version 21 >>> >> >>>> >> >> >> (XEN) Processor #1 7:10 APIC version 21 >>> >> >>>> >> >> >> (XEN) Processor #3 7:10 APIC version 21 >>> >> >>>> >> >> >> (XEN) Processor #5 7:10 APIC version 21 >>> >> >>>> >> >> >> (XEN) Processor #7 7:10 APIC version 21 >>> >> >>>> >> >> >> (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 >>> >> >>>> >> >> >> (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:679: Host address width 39 >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = fe711000 >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1b.0 >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = fe710000 >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:340: IOAPIC: f0:1f.7 >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:411: flags: INCLUDE_ALL >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e9000 end_address e9fff >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.1 >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ea000 end_address eafff >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.2 >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr eb000 end_address ebfff >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.0 >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e6000 end_address e6fff >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.1 >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e7000 end_address e7fff >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.2 >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e8000 end_address e8fff >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ec000 end_address eefff >>> >> >>>> >> >> >> (XEN) Using scheduler: SMP Credit Scheduler (credit) >>> >> >>>> >> >> >> (XEN) Detected 2800.125 MHz processor. >>> >> >>>> >> >> >> (XEN) Initing memory sharing. >>> >> >>>> >> >> >> (XEN) VMX: Supported advanced features: >>> >> >>>> >> >> >> (XEN) - APIC MMIO access virtualisation >>> >> >>>> >> >> >> (XEN) - APIC TPR shadow >>> >> >>>> >> >> >> (XEN) - Extended Page Tables (EPT) >>> >> >>>> >> >> >> (XEN) - Virtual-Processor Identifiers (VPID) >>> >> >>>> >> >> >> (XEN) - Virtual NMI >>> >> >>>> >> >> >> (XEN) - MSR direct-access bitmap >>> >> >>>> >> >> >> (XEN) HVM: ASIDs enabled. >>> >> >>>> >> >> >> (XEN) HVM: VMX enabled >>> >> >>>> >> >> >> (XEN) HVM: Hardware Assisted Paging detected. >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = fe711000 iommu->reg = ffff82c3fff57000 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c9008010e60262 ecap = f0207a >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = fe710000 iommu->reg = ffff82c3fff56000 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c90780106f0462 ecap = f020fa >>> >> >>>> >> >> >> (XEN) Intel VT-d Snoop Control not supported. >>> >> >>>> >> >> >> (XEN) Intel VT-d DMA Passthrough not supported. >>> >> >>>> >> >> >> (XEN) Intel VT-d Queued Invalidation supported. >>> >> >>>> >> >> >> (XEN) Intel VT-d Interrupt Remapping supported. >>> >> >>>> >> >> >> (XEN) I/O virtualisation enabled >>> >> >>>> >> >> >> (XEN) I/O virtualisation for PV guests disabled >>> >> >>>> >> >> >> (XEN) Total of 8 processors activated. >>> >> >>>> >> >> >> (XEN) ENABLING IO-APIC IRQs >>> >> >>>> >> >> >> (XEN) -> Using new ACK method >>> >> >>>> >> >> >> (XEN) TSC is reliable, synchronization unnecessary >>> >> >>>> >> >> >> (XEN) Platform timer is 14.318MHz HPET >>> >> >>>> >> >> >> (XEN) Allocated console ring of 16 KiB. >>> >> >>>> >> >> >> (XEN) Brought up 8 CPUs >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:0.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.1 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.1 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.2 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:14.3 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:19.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.1 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.2 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.7 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:1b.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.1 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.2 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.7 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.2 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.3 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.5 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.1 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.2 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.1 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.2 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 5:0.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.1 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.2 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.1 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.2 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = a:0.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.1 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.2 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.3 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.4 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.5 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.6 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.7 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.1 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.1 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.1 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.4 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.1 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.2 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.3 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.1 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.2 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.3 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.1 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.2 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.3 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = ffff82c3fff57000 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = ffff82c3fff56000 >>> >> >>>> >> >> >> (XEN) *** LOADING DOMAIN 0 *** >>> >> >>>> >> >> >> (XEN) Xen kernel: 64-bit, lsb, compat32 >>> >> >>>> >> >> >> (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x26ae000 >>> >> >>>> >> >> >> (XEN) PHYSICAL MEMORY ARRANGEMENT: >>> >> >>>> >> >> >> (XEN) Dom0 alloc.: 0000000210000000->0000000220000000 >>> >> >>>> >> >> >> (XEN) VIRTUAL MEMORY ARRANGEMENT: >>> >> >>>> >> >> >> (XEN) Loaded kernel: ffffffff81000000->ffffffff826ae000 >>> >> >>>> >> >> >> (XEN) Init. ramdisk: ffffffff826ae000->ffffffff8f4de600 >>> >> >>>> >> >> >> (XEN) Phys-Mach map: ffffffff8f4df000->ffffffff8f55f000 >>> >> >>>> >> >> >> (XEN) Start info: ffffffff8f55f000->ffffffff8f55f4b4 >>> >> >>>> >> >> >> (XEN) Page tables: ffffffff8f560000->ffffffff8f5df000 >>> >> >>>> >> >> >> (XEN) Boot stack: ffffffff8f5df000->ffffffff8f5e0000 >>> >> >>>> >> >> >> (XEN) TOTAL: ffffffff80000000->ffffffff8f800000 >>> >> >>>> >> >> >> (XEN) ENTRY ADDRESS: ffffffff81a10860 >>> >> >>>> >> >> >> (XEN) Dom0 has maximum 1 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 \047CTRL-a\047 three times to switch input to Xen) >>> >> >>>> >> >> >> (XEN) Freed 164kB init memory. >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 pirq=0 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=2, irq=0 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=000009f0 pirq=0 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 3 already mapped >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 4 already mapped >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 5 already mapped >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 6 already mapped >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 7 already mapped >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 8 already mapped >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 9 already mapped >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 10 already mapped >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 11 already mapped >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 12 already mapped >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000009f0 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 pirq=0 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=23, irq=23 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a929 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a929 pirq=23 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 pirq=16 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 pirq=16 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >>>> >> >> > >>> >> >>>> >> >> >> _______________________________________________ >>> >> >>>> >> >> >> Xen-users mailing list >>> >> >>>> >> >> >> Xen-users@lists.xensource.com >>> >> >>>> >> >> >> http://lists.xensource.com/xen-users >>> >> >>>> >> >> > >>> >> >>>> >> > >>> >> >>>> > >>> >> >>> >>> >> >> >>> >> > >>> > >> > ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: RE: Xen4 / Intel DX58SO Mobo / VT-d not working 2010-05-14 20:39 ` chris @ 2010-05-14 20:50 ` Pasi Kärkkäinen 2010-05-14 21:17 ` [Xen-users] " chris 0 siblings, 1 reply; 32+ messages in thread From: Pasi Kärkkäinen @ 2010-05-14 20:50 UTC (permalink / raw) To: chris; +Cc: Xen-Devel List, Xen-Users List On Fri, May 14, 2010 at 04:39:54PM -0400, chris wrote: > Alright so a pci sound card works, I tried a geforce 8600 pci e card > and while vga passthrough didnt work it did seem to attach to the > domain ok. So I guess the problem must be somehow related to the > device. I'm still confused since it works in another box. > > I remember there was some reassign_resources or something, maybe the > issue is with some resources the card uses? > http://wiki.xensource.com/xenwiki/XenPCIpassthrough -- Pasi > Below is a lspci -vv of the card > > 02:00.0 USB Controller: NEC Corporation USB (rev 43) (prog-if 10 [OHCI]) > Subsystem: NEC Corporation Hama USB 2.0 CardBus > Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- > ParErr- Stepping- SERR- FastB2B- DisINTx- > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium > >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- > Interrupt: pin A routed to IRQ 16 > Region 0: Memory at d2502000 (32-bit, non-prefetchable) > [disabled] [size=4K] > Capabilities: [40] Power Management version 2 > Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA > PME(D0+,D1+,D2+,D3hot+,D3cold-) > Status: D0 PME-Enable- DSel=0 DScale=0 PME- > Kernel driver in use: pciback > > 02:00.1 USB Controller: NEC Corporation USB (rev 43) (prog-if 10 [OHCI]) > Subsystem: NEC Corporation Hama USB 2.0 CardBus > Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- > ParErr- Stepping- SERR- FastB2B- DisINTx- > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium > >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- > Interrupt: pin B routed to IRQ 17 > Region 0: Memory at d2501000 (32-bit, non-prefetchable) > [disabled] [size=4K] > Capabilities: [40] Power Management version 2 > Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA > PME(D0+,D1+,D2+,D3hot+,D3cold-) > Status: D0 PME-Enable- DSel=0 DScale=0 PME- > Kernel driver in use: pciback > > 02:00.2 USB Controller: NEC Corporation USB 2.0 (rev 04) (prog-if 20 [EHCI]) > Subsystem: NEC Corporation USB 2.0 > Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- > ParErr- Stepping- SERR- FastB2B- DisINTx- > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium > >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- > Interrupt: pin C routed to IRQ 18 > Region 0: Memory at d2500000 (32-bit, non-prefetchable) > [disabled] [size=256] > Capabilities: [40] Power Management version 2 > Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA > PME(D0+,D1+,D2+,D3hot+,D3cold-) > Status: D0 PME-Enable- DSel=0 DScale=0 PME- > Kernel driver in use: pciback > > > On Fri, May 14, 2010 at 3:46 PM, chris <tknchris@gmail.com> wrote: > > I added a pci sound card and interestingly that works. I'm digging > > around for another pci-e device to try to identify if its all pci-e or > > only this device. Strange this is that I have a few other machines > > with this same usb controller which is working on 3.4.2. > > > > *scratches head* > > > > - chris > > > > On Fri, May 14, 2010 at 3:21 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > >> On Fri, May 14, 2010 at 03:18:02PM -0400, chris wrote: > >>> It is a multifunction device, a pci-e usb controller, so I assumed all > >>> them had to be passed through. I just changed it to only 02:00.0 and > >>> same thing > >>> > >>> test-box2:~# cat /etc/xen/vm-five.cfg | grep pci > >>> pci = ['02:00.0'] > >>> test-box2:~# xm create /etc/xen/vm-five.cfg > >>> Using config file "/etc/xen/vm-five.cfg". > >>> Error: Failed to assign device to IOMMU > >>> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) > >>> > >> > >> Hmm.. weird. > >> > >> Two things to try: > >> > >> 1) Try passthru some other device (which is just a single pci id) > >> 2) Try passthru that pci-e usb controller to Linux PV guest and see if that works > >> > >> -- Pasi > >> > >>> > >>> On Fri, May 14, 2010 at 3:11 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > >>> > On Fri, May 14, 2010 at 03:05:49PM -0400, chris wrote: > >>> >> Pasi, > >>> >> > >>> >> Tried latest stable/2.6.32.x per your advice, no change. Anyone on > >>> >> xen-devel that can help me troubleshoot further? Everything looks > >>> >> right, can't figure out why vt-d is not working but it must be some > >>> >> kind of bug :( > >>> >> > >>> > > >>> > Did you try the suggestion said earlier.. try to just passthru the first pci device? > >>> > > >>> > -- Pasi > >>> > > >>> >> test-box2:~# uname -a > >>> >> Linux test-box2 2.6.32.12 #1 SMP Fri May 14 13:40:05 EDT 2010 x86_64 GNU/Linux > >>> >> > >>> >> test-box2:~# xm info | grep virt_caps > >>> >> virt_caps : hvm hvm_directio > >>> >> > >>> >> test-box2:~# xm pci-list-assignable-devices > >>> >> 0000:02:00.0 > >>> >> 0000:02:00.1 > >>> >> 0000:02:00.2 > >>> >> > >>> >> test-box2:~# xm create /etc/xen/vm-five.cfg > >>> >> Using config file "/etc/xen/vm-five.cfg". > >>> >> Error: Failed to assign device to IOMMU > >>> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) > >>> >> > >>> >> test-box2:~# cat /etc/xen/vm-five.cfg | grep -v '#' > >>> >> kernel = '/usr/lib/xen/boot/hvmloader' > >>> >> builder = 'hvm' > >>> >> memory = '1792' > >>> >> device_model='/usr/lib/xen/bin/qemu-dm' > >>> >> disk = [ 'phy:/dev/storage/vm-five,ioemu:hda,w', > >>> >> 'phy:/dev/sr0,ioemu:hdc:cdrom,r' > >>> >> ] > >>> >> name = 'vm-five' > >>> >> vif = ['type=ioemu, bridge=eth0, mac=00:16:3D:37:A1:42'] > >>> >> boot='dc' > >>> >> cpus='0-1' > >>> >> vcpus=2 > >>> >> acpi=1 > >>> >> ahci=1 > >>> >> vnc=1 > >>> >> sdl=0 > >>> >> timer_mode=1 > >>> >> usb=1 > >>> >> usbdevice='tablet' > >>> >> localtime=1 > >>> >> pci = ['02:00.0','02:00.1','02:00.2'] > >>> >> > >>> >> On Thu, May 13, 2010 at 2:28 PM, chris <tknchris@gmail.com> wrote: > >>> >> > Forwarding to xen-devel. Can't seem to get VT-d working with xen4 from > >>> >> > tarball on xen.org 2.6.31.13 pv_ops dom0. On pasi's advice I tried > >>> >> > switching to stable/2.6.32.x branch for dom0 and that doesnt even > >>> >> > build. Did something change recently thats breaking compilation? > >>> >> > > >>> >> > Attached is xen dmesg with iommu=verbose loglvl=all guest_loglvl=all, > >>> >> > and dom0 dmesg from 2.6.31.x > >>> >> > > >>> >> > Any ideas on why VT-d is not working on this board? Initialization > >>> >> > looks good, xen reports hvm_directio capability, everything says VT-d > >>> >> > should work until domain is created. > >>> >> > > >>> >> > Any ideas why stable/2.6.32.x wont build? > >>> >> > > >>> >> > - chris > >>> >> > > >>> >> > On Thu, May 13, 2010 at 2:07 PM, chris <tknchris@gmail.com> wrote: > >>> >> >> I redid it with oldconfig which I didn't think would help and same > >>> >> >> thing. I guess this tree is broken? Can someone else try and see if > >>> >> >> they can build it? Ugh, whata day :) > >>> >> >> > >>> >> >> On Thu, May 13, 2010 at 1:58 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > >>> >> >>> On Thu, May 13, 2010 at 01:55:25PM -0400, chris wrote: > >>> >> >>>> I used the default config on the wiki which you created. Steps I took were: > >>> >> >>>> > >>> >> >>>> # make clean distclean > >>> >> >>>> # wget -O .config > >>> >> >>>> "http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.10-pvops-dom0-xen-stable-x86_64" > >>> >> >>> > >>> >> >>> You should do "make oldconfig" at this point. > >>> >> >>> > >>> >> >>>> # make -j8 bzImage > >>> >> >>>> (blah blah) > >>> >> >>>> LD vmlinux.o > >>> >> >>>> MODPOST vmlinux.o > >>> >> >>>> WARNING: modpost: Found 7 section mismatch(es). > >>> >> >>>> To see full details build your kernel with: > >>> >> >>>> 'make CONFIG_DEBUG_SECTION_MISMATCH=y' > >>> >> >>>> GEN .version > >>> >> >>>> CHK include/linux/compile.h > >>> >> >>>> UPD include/linux/compile.h > >>> >> >>>> CC init/version.o > >>> >> >>>> LD init/built-in.o > >>> >> >>>> LD .tmp_vmlinux1 > >>> >> >>>> drivers/built-in.o: In function `do_hvm_suspend': > >>> >> >>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: undefined reference > >>> >> >>>> to `xenbus_suspend' > >>> >> >>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: undefined reference > >>> >> >>>> to `xenbus_resume' > >>> >> >>>> make: *** [.tmp_vmlinux1] Error 1 > >>> >> >>>> > >>> >> >>> > >>> >> >>> Hmm.. weird. I wonder if something has changed recently or what's going on in here.. > >>> >> >>> > >>> >> >>> -- Pasi > >>> >> >>> > >>> >> >>>> > >>> >> >>>> On Thu, May 13, 2010 at 11:47 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > >>> >> >>>> > On Thu, May 13, 2010 at 11:33:57AM -0400, chris wrote: > >>> >> >>>> >> Successfully grabbed the sources and failed to build: > >>> >> >>>> >> > >>> >> >>>> >> LD .tmp_vmlinux1 > >>> >> >>>> >> drivers/built-in.o: In function `do_hvm_suspend': > >>> >> >>>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: undefined reference > >>> >> >>>> >> to `xenbus_suspend' > >>> >> >>>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: undefined reference > >>> >> >>>> >> to `xenbus_resume' > >>> >> >>>> >> make: *** [.tmp_vmlinux1] Error 1 > >>> >> >>>> >> > >>> >> >>>> >> :( > >>> >> >>>> >> > >>> >> >>>> > > >>> >> >>>> > Try the example .config files provided on the wiki page. > >>> >> >>>> > > >>> >> >>>> > -- Pasi > >>> >> >>>> > > >>> >> >>>> >> On Thu, May 13, 2010 at 10:14 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > >>> >> >>>> >> > On Thu, May 13, 2010 at 10:12:56AM -0400, chris wrote: > >>> >> >>>> >> >> Pasi, > >>> >> >>>> >> >> > >>> >> >>>> >> >> How do I pull those kernel sources you referenced? I see it mentioned > >>> >> >>>> >> >> on http://wiki.xensource.com/xenwiki/XenParavirtOps but no details on > >>> >> >>>> >> >> how to retrieve it. > >>> >> >>>> >> >> > >>> >> >>>> >> > > >>> >> >>>> >> > The instructions are there if you read it carefully.. > >>> >> >>>> >> > There's the topic of how to switch branches. > >>> >> >>>> >> > > >>> >> >>>> >> > -- Pasi > >>> >> >>>> >> > > >>> >> >>>> >> >> - chris > >>> >> >>>> >> >> > >>> >> >>>> >> >> On Thu, May 13, 2010 at 8:29 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > >>> >> >>>> >> >> > On Wed, May 12, 2010 at 08:41:34PM -0400, chris wrote: > >>> >> >>>> >> >> >> When reading the vtdhowto I noticed the ability to set iommu=verbose. > >>> >> >>>> >> >> >> Here is that output, I don't know if it helps at all to figure out > >>> >> >>>> >> >> >> what is wrong. > >>> >> >>>> >> >> >> > >>> >> >>>> >> >> > > >>> >> >>>> >> >> > That seems to be OK: > >>> >> >>>> >> >> > > >>> >> >>>> >> >> > (XEN) I/O virtualisation enabled > >>> >> >>>> >> >> > (XEN) I/O virtualisation for PV guests disabled > >>> >> >>>> >> >> > > >>> >> >>>> >> >> > So hmm.. I wonder if it's related to MSI stuff? > >>> >> >>>> >> >> > You could try xen.git xen/stable-2.6.32.x branch instead and see if that makes a difference.. > >>> >> >>>> >> >> > > >>> >> >>>> >> >> > -- Pasi > >>> >> >>>> >> >> > > >>> >> >>>> >> >> >> > >>> >> >>>> >> >> >> ---------- Forwarded message ---------- > >>> >> >>>> >> >> >> From: chris <tknchris@gmail.com> > >>> >> >>>> >> >> >> Date: Wed, May 12, 2010 at 5:28 PM > >>> >> >>>> >> >> >> Subject: Xen4 / Intel DX58SO Mobo / VT-d not working > >>> >> >>>> >> >> >> To: Xen-Users List <xen-users@lists.xensource.com> > >>> >> >>>> >> >> >> > >>> >> >>>> >> >> >> > >>> >> >>>> >> >> >> Hello, > >>> >> >>>> >> >> >> > >>> >> >>>> >> >> >> I've previously been successful with Xen4 and VT-d on other systems. I > >>> >> >>>> >> >> >> am having trouble getting VT-d passthrough working to a WinXP domain > >>> >> >>>> >> >> >> with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is enabled in bios, > >>> >> >>>> >> >> >> xm info shows hvm_directio capability, I have iommu=1 set, I have the > >>> >> >>>> >> >> >> devices bound to pciback on dom0 cmdline, xm > >>> >> >>>> >> >> >> pci-list-assignable-devices shows the devices as assignable. When I > >>> >> >>>> >> >> >> attempt to start the VM I get the error: > >>> >> >>>> >> >> >> > >>> >> >>>> >> >> >> Error: Failed to assign device to IOMMU > >>> >> >>>> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) > >>> >> >>>> >> >> >> > >>> >> >>>> >> >> >> Below is all the information I can think of that would be useful to > >>> >> >>>> >> >> >> help debug it: > >>> >> >>>> >> >> >> > >>> >> >>>> >> >> >> BIOS VT-d Enabled: > >>> >> >>>> >> >> >> http://i43.tinypic.com/nl3a5e.jpg > >>> >> >>>> >> >> >> http://i42.tinypic.com/nqvlu1.jpg > >>> >> >>>> >> >> >> > >>> >> >>>> >> >> >> grub entry: > >>> >> >>>> >> >> >> > >>> >> >>>> >> >> >> title Xen 4.0.0 / Debian GNU/Linux, kernel 2.6.31.13 > >>> >> >>>> >> >> >> root (hd0,0) > >>> >> >>>> >> >> >> kernel /boot/xen-4.0.0.gz iommu=1 dom0_mem=256M > >>> >> >>>> >> >> >> dom0_max_vcpus=1 dom0_vcpus_pin=true > >>> >> >>>> >> >> >> module /boot/vmlinuz-2.6.31.13 root=/dev/md0 ro console=tty0 > >>> >> >>>> >> >> >> xen-pciback.permissive > >>> >> >>>> >> >> >> xen-pciback.hide=(02:00.0)(02:00.1)(02:00.2)(04:00.0)(04:00.1)(04:00.2)(07:00.0)(07:00.1)(07:00.2)(09:00.0)(09:00.1)(09:00.2) > >>> >> >>>> >> >> >> module /boot/initrd.img-2.6.31.13 > >>> >> >>>> >> >> >> > >>> >> >>>> >> >> >> # xm pci-list-assignable-devices > >>> >> >>>> >> >> >> 0000:09:00.0 > >>> >> >>>> >> >> >> 0000:09:00.1 > >>> >> >>>> >> >> >> 0000:09:00.2 > >>> >> >>>> >> >> >> 0000:07:00.0 > >>> >> >>>> >> >> >> 0000:07:00.1 > >>> >> >>>> >> >> >> 0000:07:00.2 > >>> >> >>>> >> >> >> 0000:04:00.0 > >>> >> >>>> >> >> >> 0000:04:00.1 > >>> >> >>>> >> >> >> 0000:04:00.2 > >>> >> >>>> >> >> >> 0000:02:00.0 > >>> >> >>>> >> >> >> 0000:02:00.1 > >>> >> >>>> >> >> >> 0000:02:00.2 > >>> >> >>>> >> >> >> > >>> >> >>>> >> >> >> # xm info > >>> >> >>>> >> >> >> host : test-box2 > >>> >> >>>> >> >> >> release : 2.6.31.13 > >>> >> >>>> >> >> >> version : #2 SMP Wed May 12 14:11:37 EDT 2010 > >>> >> >>>> >> >> >> machine : x86_64 > >>> >> >>>> >> >> >> nr_cpus : 8 > >>> >> >>>> >> >> >> nr_nodes : 1 > >>> >> >>>> >> >> >> cores_per_socket : 4 > >>> >> >>>> >> >> >> threads_per_core : 2 > >>> >> >>>> >> >> >> cpu_mhz : 2800 > >>> >> >>>> >> >> >> hw_caps : > >>> >> >>>> >> >> >> bfebfbff:28100800:00000000:00001b40:0098e3bd:00000000:00000001:00000000 > >>> >> >>>> >> >> >> virt_caps : hvm hvm_directio > >>> >> >>>> >> >> >> total_memory : 7950 > >>> >> >>>> >> >> >> free_memory : 7812 > >>> >> >>>> >> >> >> node_to_cpu : node0:0-7 > >>> >> >>>> >> >> >> node_to_memory : node0:7812 > >>> >> >>>> >> >> >> node_to_dma32_mem : node0:3249 > >>> >> >>>> >> >> >> max_node_id : 0 > >>> >> >>>> >> >> >> xen_major : 4 > >>> >> >>>> >> >> >> xen_minor : 0 > >>> >> >>>> >> >> >> xen_extra : .0 > >>> >> >>>> >> >> >> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > >>> >> >>>> >> >> >> hvm-3.0-x86_32p hvm-3.0-x86_64 > >>> >> >>>> >> >> >> xen_scheduler : credit > >>> >> >>>> >> >> >> xen_pagesize : 4096 > >>> >> >>>> >> >> >> platform_params : virt_start=0xffff800000000000 > >>> >> >>>> >> >> >> xen_changeset : unavailable > >>> >> >>>> >> >> >> xen_commandline : iommu=1 dom0_mem=256M dom0_max_vcpus=1 > >>> >> >>>> >> >> >> dom0_vcpus_pin=true > >>> >> >>>> >> >> >> cc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1) > >>> >> >>>> >> >> >> cc_compile_by : root > >>> >> >>>> >> >> >> cc_compile_domain : > >>> >> >>>> >> >> >> cc_compile_date : Thu May 6 13:41:25 EDT 2010 > >>> >> >>>> >> >> >> xend_config_format : 4 > >>> >> >>>> >> >> >> > >>> >> >>>> >> >> >> # xm create vm-five.cfg > >>> >> >>>> >> >> >> Using config file "./vm-five.cfg". > >>> >> >>>> >> >> >> Error: Failed to assign device to IOMMU > >>> >> >>>> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) > >>> >> >>>> >> >> >> > >>> >> >>>> >> >> >> I feel like I'm missing something really obvious but I've been at it > >>> >> >>>> >> >> >> for a while now and have run out of brain power. Anyone have any idea > >>> >> >>>> >> >> >> what might be wrong? > >>> >> >>>> >> >> >> > >>> >> >>>> >> >> >> - chris > >>> >> >>>> >> >> > > >>> >> >>>> >> >> >> __ __ _ _ ___ ___ > >>> >> >>>> >> >> >> \ \/ /___ _ __ | || | / _ \ / _ \ > >>> >> >>>> >> >> >> \ // _ \ \047_ \ | || |_| | | | | | | > >>> >> >>>> >> >> >> / \ __/ | | | |__ _| |_| | |_| | > >>> >> >>>> >> >> >> /_/\_\___|_| |_| |_|(_)___(_)___/ > >>> >> >>>> >> >> >> > >>> >> >>>> >> >> >> (XEN) Xen version 4.0.0 (root@) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) Thu May 6 13:41:25 EDT 2010 > >>> >> >>>> >> >> >> (XEN) Latest ChangeSet: unavailable > >>> >> >>>> >> >> >> (XEN) Command line: iommu=verbose dom0_mem=256M dom0_max_vcpus=1 dom0_vcpus_pin=true > >>> >> >>>> >> >> >> (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 - 000000000008f000 (usable) > >>> >> >>>> >> >> >> (XEN) 000000000008f000 - 0000000000090000 (reserved) > >>> >> >>>> >> >> >> (XEN) 0000000000090000 - 000000000009ec00 (usable) > >>> >> >>>> >> >> >> (XEN) 000000000009ec00 - 00000000000a0000 (reserved) > >>> >> >>>> >> >> >> (XEN) 00000000000e0000 - 0000000000100000 (reserved) > >>> >> >>>> >> >> >> (XEN) 0000000000100000 - 00000000cf4bd000 (usable) > >>> >> >>>> >> >> >> (XEN) 00000000cf4bd000 - 00000000cf4bf000 (reserved) > >>> >> >>>> >> >> >> (XEN) 00000000cf4bf000 - 00000000cf4c2000 (usable) > >>> >> >>>> >> >> >> (XEN) 00000000cf4c2000 - 00000000cf7bf000 (ACPI NVS) > >>> >> >>>> >> >> >> (XEN) 00000000cf7bf000 - 00000000cf7df000 (usable) > >>> >> >>>> >> >> >> (XEN) 00000000cf7df000 - 00000000cf7ff000 (ACPI data) > >>> >> >>>> >> >> >> (XEN) 00000000cf7ff000 - 00000000cf800000 (usable) > >>> >> >>>> >> >> >> (XEN) 00000000cf800000 - 00000000d0000000 (reserved) > >>> >> >>>> >> >> >> (XEN) 00000000f8000000 - 00000000fd000000 (reserved) > >>> >> >>>> >> >> >> (XEN) 00000000ffe00000 - 0000000100000000 (reserved) > >>> >> >>>> >> >> >> (XEN) 0000000100000000 - 0000000230000000 (usable) > >>> >> >>>> >> >> >> (XEN) ACPI: RSDP 000FE020, 0024 (r2 INTEL ) > >>> >> >>>> >> >> >> (XEN) ACPI: XSDT CF7FE120, 0074 (r1 INTEL DX58SO 11F6 1000013) > >>> >> >>>> >> >> >> (XEN) ACPI: FACP CF7FD000, 00F4 (r3 INTEL DX58SO 11F6 MSFT 100000D) > >>> >> >>>> >> >> >> (XEN) ACPI Warning (tbfadt-0444): Optional field "Pm2ControlBlock" has zero address or length: 0000000000000450/0 [20070126] > >>> >> >>>> >> >> >> (XEN) ACPI: DSDT CF7F8000, 4641 (r2 INTEL DX58SO 11F6 MSFT 100000D) > >>> >> >>>> >> >> >> (XEN) ACPI: FACS CF728000, 0040 > >>> >> >>>> >> >> >> (XEN) ACPI: APIC CF7F7000, 0138 (r2 INTEL DX58SO 11F6 MSFT 100000D) > >>> >> >>>> >> >> >> (XEN) ACPI: WDDT CF7F6000, 0040 (r1 INTEL DX58SO 11F6 MSFT 100000D) > >>> >> >>>> >> >> >> (XEN) ACPI: MCFG CF7F5000, 003C (r1 INTEL DX58SO 11F6 MSFT 100000D) > >>> >> >>>> >> >> >> (XEN) ACPI: ASF! CF7F4000, 00AC (r32 INTEL DX58SO 11F6 MSFT 100000D) > >>> >> >>>> >> >> >> (XEN) ACPI: HPET CF7F3000, 0038 (r1 INTEL DX58SO 11F6 MSFT 100000D) > >>> >> >>>> >> >> >> (XEN) ACPI: SSDT CF7E2000, E134 (r1 INTEL SSDT PM 11F6 MSFT 100000D) > >>> >> >>>> >> >> >> (XEN) ACPI: DMAR CF7DF000, 0140 (r1 INTEL DX58SO 11F6 MSFT 100000D) > >>> >> >>>> >> >> >> (XEN) ACPI: WDTT CF7F1000, 020C (r2 INTEL DX58SO 11F6 MSFT 100000D) > >>> >> >>>> >> >> >> (XEN) ACPI: ASPT CF7F2000, 0034 (r4 INTEL PerfTune 11F6 MSFT 100000D) > >>> >> >>>> >> >> >> (XEN) System RAM: 7950MB (8140820kB) > >>> >> >>>> >> >> >> (XEN) Domain heap initialised > >>> >> >>>> >> >> >> (XEN) Processor #0 7:10 APIC version 21 > >>> >> >>>> >> >> >> (XEN) Processor #2 7:10 APIC version 21 > >>> >> >>>> >> >> >> (XEN) Processor #4 7:10 APIC version 21 > >>> >> >>>> >> >> >> (XEN) Processor #6 7:10 APIC version 21 > >>> >> >>>> >> >> >> (XEN) Processor #1 7:10 APIC version 21 > >>> >> >>>> >> >> >> (XEN) Processor #3 7:10 APIC version 21 > >>> >> >>>> >> >> >> (XEN) Processor #5 7:10 APIC version 21 > >>> >> >>>> >> >> >> (XEN) Processor #7 7:10 APIC version 21 > >>> >> >>>> >> >> >> (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 > >>> >> >>>> >> >> >> (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:679: Host address width 39 > >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: > >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = fe711000 > >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1b.0 > >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: > >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = fe710000 > >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:340: IOAPIC: f0:1f.7 > >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:411: flags: INCLUDE_ALL > >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 > >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e9000 end_address e9fff > >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.1 > >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ea000 end_address eafff > >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.2 > >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr eb000 end_address ebfff > >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.0 > >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e6000 end_address e6fff > >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.1 > >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e7000 end_address e7fff > >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.2 > >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e8000 end_address e8fff > >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 > >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ec000 end_address eefff > >>> >> >>>> >> >> >> (XEN) Using scheduler: SMP Credit Scheduler (credit) > >>> >> >>>> >> >> >> (XEN) Detected 2800.125 MHz processor. > >>> >> >>>> >> >> >> (XEN) Initing memory sharing. > >>> >> >>>> >> >> >> (XEN) VMX: Supported advanced features: > >>> >> >>>> >> >> >> (XEN) - APIC MMIO access virtualisation > >>> >> >>>> >> >> >> (XEN) - APIC TPR shadow > >>> >> >>>> >> >> >> (XEN) - Extended Page Tables (EPT) > >>> >> >>>> >> >> >> (XEN) - Virtual-Processor Identifiers (VPID) > >>> >> >>>> >> >> >> (XEN) - Virtual NMI > >>> >> >>>> >> >> >> (XEN) - MSR direct-access bitmap > >>> >> >>>> >> >> >> (XEN) HVM: ASIDs enabled. > >>> >> >>>> >> >> >> (XEN) HVM: VMX enabled > >>> >> >>>> >> >> >> (XEN) HVM: Hardware Assisted Paging detected. > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = fe711000 iommu->reg = ffff82c3fff57000 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c9008010e60262 ecap = f0207a > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = fe710000 iommu->reg = ffff82c3fff56000 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c90780106f0462 ecap = f020fa > >>> >> >>>> >> >> >> (XEN) Intel VT-d Snoop Control not supported. > >>> >> >>>> >> >> >> (XEN) Intel VT-d DMA Passthrough not supported. > >>> >> >>>> >> >> >> (XEN) Intel VT-d Queued Invalidation supported. > >>> >> >>>> >> >> >> (XEN) Intel VT-d Interrupt Remapping supported. > >>> >> >>>> >> >> >> (XEN) I/O virtualisation enabled > >>> >> >>>> >> >> >> (XEN) I/O virtualisation for PV guests disabled > >>> >> >>>> >> >> >> (XEN) Total of 8 processors activated. > >>> >> >>>> >> >> >> (XEN) ENABLING IO-APIC IRQs > >>> >> >>>> >> >> >> (XEN) -> Using new ACK method > >>> >> >>>> >> >> >> (XEN) TSC is reliable, synchronization unnecessary > >>> >> >>>> >> >> >> (XEN) Platform timer is 14.318MHz HPET > >>> >> >>>> >> >> >> (XEN) Allocated console ring of 16 KiB. > >>> >> >>>> >> >> >> (XEN) Brought up 8 CPUs > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:0.0 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.0 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.1 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.0 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.1 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.2 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:14.3 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:19.0 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.0 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.1 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.2 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.7 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:1b.0 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.0 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.1 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.2 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.7 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.0 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.2 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.3 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.5 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.0 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.1 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.2 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.0 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.1 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.2 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 5:0.0 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.0 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.1 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.2 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.0 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.1 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.2 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = a:0.0 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.0 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.1 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.2 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.3 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.4 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.5 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.6 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.7 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.0 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.1 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.0 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.1 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.0 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.1 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.4 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.0 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.1 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.2 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.3 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.0 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.1 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.2 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.3 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.0 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.1 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.2 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.3 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = ffff82c3fff57000 > >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = ffff82c3fff56000 > >>> >> >>>> >> >> >> (XEN) *** LOADING DOMAIN 0 *** > >>> >> >>>> >> >> >> (XEN) Xen kernel: 64-bit, lsb, compat32 > >>> >> >>>> >> >> >> (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x26ae000 > >>> >> >>>> >> >> >> (XEN) PHYSICAL MEMORY ARRANGEMENT: > >>> >> >>>> >> >> >> (XEN) Dom0 alloc.: 0000000210000000->0000000220000000 > >>> >> >>>> >> >> >> (XEN) VIRTUAL MEMORY ARRANGEMENT: > >>> >> >>>> >> >> >> (XEN) Loaded kernel: ffffffff81000000->ffffffff826ae000 > >>> >> >>>> >> >> >> (XEN) Init. ramdisk: ffffffff826ae000->ffffffff8f4de600 > >>> >> >>>> >> >> >> (XEN) Phys-Mach map: ffffffff8f4df000->ffffffff8f55f000 > >>> >> >>>> >> >> >> (XEN) Start info: ffffffff8f55f000->ffffffff8f55f4b4 > >>> >> >>>> >> >> >> (XEN) Page tables: ffffffff8f560000->ffffffff8f5df000 > >>> >> >>>> >> >> >> (XEN) Boot stack: ffffffff8f5df000->ffffffff8f5e0000 > >>> >> >>>> >> >> >> (XEN) TOTAL: ffffffff80000000->ffffffff8f800000 > >>> >> >>>> >> >> >> (XEN) ENTRY ADDRESS: ffffffff81a10860 > >>> >> >>>> >> >> >> (XEN) Dom0 has maximum 1 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 \047CTRL-a\047 three times to switch input to Xen) > >>> >> >>>> >> >> >> (XEN) Freed 164kB init memory. > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 pirq=0 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=2, irq=0 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=000009f0 pirq=0 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 3 already mapped > >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 4 already mapped > >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 5 already mapped > >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 6 already mapped > >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 7 already mapped > >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 8 already mapped > >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 9 already mapped > >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 10 already mapped > >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 11 already mapped > >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 12 already mapped > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000009f0 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 pirq=0 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=23, irq=23 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a929 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a929 pirq=23 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 pirq=16 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 pirq=16 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 > >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>> >> >>>> >> >> > > >>> >> >>>> >> >> >> _______________________________________________ > >>> >> >>>> >> >> >> Xen-users mailing list > >>> >> >>>> >> >> >> Xen-users@lists.xensource.com > >>> >> >>>> >> >> >> http://lists.xensource.com/xen-users > >>> >> >>>> >> >> > > >>> >> >>>> >> > > >>> >> >>>> > > >>> >> >>> > >>> >> >> > >>> >> > > >>> > > >> > > ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [Xen-users] RE: Xen4 / Intel DX58SO Mobo / VT-d not working 2010-05-14 20:50 ` Pasi Kärkkäinen @ 2010-05-14 21:17 ` chris 2010-05-16 7:36 ` [Xen-devel] " Han, Weidong 0 siblings, 1 reply; 32+ messages in thread From: chris @ 2010-05-14 21:17 UTC (permalink / raw) To: Pasi Kärkkäinen; +Cc: Xen-Devel List, Xen-Users List [-- Attachment #1: Type: text/plain, Size: 38333 bytes --] Played around with xen_platform_pc, pci_msitranslate, pci_power_mgmt in the cfg, none of which seem to have any effect, also tried pci=resource_alignment=02:00.0;02:00.1;02:00.2 on dom0 cmdline, no effect. I'm worn out been fighting this all day. Attached is some various output from the machine that works with the same cards and has Xen 3.4.2 and the new machine with 4.0 which doesn't work. I'm hoping this information can get the right attention and we can figure it out :( - chris On Fri, May 14, 2010 at 4:50 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > On Fri, May 14, 2010 at 04:39:54PM -0400, chris wrote: >> Alright so a pci sound card works, I tried a geforce 8600 pci e card >> and while vga passthrough didnt work it did seem to attach to the >> domain ok. So I guess the problem must be somehow related to the >> device. I'm still confused since it works in another box. >> >> I remember there was some reassign_resources or something, maybe the >> issue is with some resources the card uses? >> > > http://wiki.xensource.com/xenwiki/XenPCIpassthrough > > -- Pasi > >> Below is a lspci -vv of the card >> >> 02:00.0 USB Controller: NEC Corporation USB (rev 43) (prog-if 10 [OHCI]) >> Subsystem: NEC Corporation Hama USB 2.0 CardBus >> Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- >> ParErr- Stepping- SERR- FastB2B- DisINTx- >> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >> >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- >> Interrupt: pin A routed to IRQ 16 >> Region 0: Memory at d2502000 (32-bit, non-prefetchable) >> [disabled] [size=4K] >> Capabilities: [40] Power Management version 2 >> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA >> PME(D0+,D1+,D2+,D3hot+,D3cold-) >> Status: D0 PME-Enable- DSel=0 DScale=0 PME- >> Kernel driver in use: pciback >> >> 02:00.1 USB Controller: NEC Corporation USB (rev 43) (prog-if 10 [OHCI]) >> Subsystem: NEC Corporation Hama USB 2.0 CardBus >> Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- >> ParErr- Stepping- SERR- FastB2B- DisINTx- >> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >> >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- >> Interrupt: pin B routed to IRQ 17 >> Region 0: Memory at d2501000 (32-bit, non-prefetchable) >> [disabled] [size=4K] >> Capabilities: [40] Power Management version 2 >> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA >> PME(D0+,D1+,D2+,D3hot+,D3cold-) >> Status: D0 PME-Enable- DSel=0 DScale=0 PME- >> Kernel driver in use: pciback >> >> 02:00.2 USB Controller: NEC Corporation USB 2.0 (rev 04) (prog-if 20 [EHCI]) >> Subsystem: NEC Corporation USB 2.0 >> Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- >> ParErr- Stepping- SERR- FastB2B- DisINTx- >> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >> >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- >> Interrupt: pin C routed to IRQ 18 >> Region 0: Memory at d2500000 (32-bit, non-prefetchable) >> [disabled] [size=256] >> Capabilities: [40] Power Management version 2 >> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA >> PME(D0+,D1+,D2+,D3hot+,D3cold-) >> Status: D0 PME-Enable- DSel=0 DScale=0 PME- >> Kernel driver in use: pciback >> >> >> On Fri, May 14, 2010 at 3:46 PM, chris <tknchris@gmail.com> wrote: >> > I added a pci sound card and interestingly that works. I'm digging >> > around for another pci-e device to try to identify if its all pci-e or >> > only this device. Strange this is that I have a few other machines >> > with this same usb controller which is working on 3.4.2. >> > >> > *scratches head* >> > >> > - chris >> > >> > On Fri, May 14, 2010 at 3:21 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >> >> On Fri, May 14, 2010 at 03:18:02PM -0400, chris wrote: >> >>> It is a multifunction device, a pci-e usb controller, so I assumed all >> >>> them had to be passed through. I just changed it to only 02:00.0 and >> >>> same thing >> >>> >> >>> test-box2:~# cat /etc/xen/vm-five.cfg | grep pci >> >>> pci = ['02:00.0'] >> >>> test-box2:~# xm create /etc/xen/vm-five.cfg >> >>> Using config file "/etc/xen/vm-five.cfg". >> >>> Error: Failed to assign device to IOMMU >> >>> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >> >>> >> >> >> >> Hmm.. weird. >> >> >> >> Two things to try: >> >> >> >> 1) Try passthru some other device (which is just a single pci id) >> >> 2) Try passthru that pci-e usb controller to Linux PV guest and see if that works >> >> >> >> -- Pasi >> >> >> >>> >> >>> On Fri, May 14, 2010 at 3:11 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >> >>> > On Fri, May 14, 2010 at 03:05:49PM -0400, chris wrote: >> >>> >> Pasi, >> >>> >> >> >>> >> Tried latest stable/2.6.32.x per your advice, no change. Anyone on >> >>> >> xen-devel that can help me troubleshoot further? Everything looks >> >>> >> right, can't figure out why vt-d is not working but it must be some >> >>> >> kind of bug :( >> >>> >> >> >>> > >> >>> > Did you try the suggestion said earlier.. try to just passthru the first pci device? >> >>> > >> >>> > -- Pasi >> >>> > >> >>> >> test-box2:~# uname -a >> >>> >> Linux test-box2 2.6.32.12 #1 SMP Fri May 14 13:40:05 EDT 2010 x86_64 GNU/Linux >> >>> >> >> >>> >> test-box2:~# xm info | grep virt_caps >> >>> >> virt_caps : hvm hvm_directio >> >>> >> >> >>> >> test-box2:~# xm pci-list-assignable-devices >> >>> >> 0000:02:00.0 >> >>> >> 0000:02:00.1 >> >>> >> 0000:02:00.2 >> >>> >> >> >>> >> test-box2:~# xm create /etc/xen/vm-five.cfg >> >>> >> Using config file "/etc/xen/vm-five.cfg". >> >>> >> Error: Failed to assign device to IOMMU >> >>> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >> >>> >> >> >>> >> test-box2:~# cat /etc/xen/vm-five.cfg | grep -v '#' >> >>> >> kernel = '/usr/lib/xen/boot/hvmloader' >> >>> >> builder = 'hvm' >> >>> >> memory = '1792' >> >>> >> device_model='/usr/lib/xen/bin/qemu-dm' >> >>> >> disk = [ 'phy:/dev/storage/vm-five,ioemu:hda,w', >> >>> >> 'phy:/dev/sr0,ioemu:hdc:cdrom,r' >> >>> >> ] >> >>> >> name = 'vm-five' >> >>> >> vif = ['type=ioemu, bridge=eth0, mac=00:16:3D:37:A1:42'] >> >>> >> boot='dc' >> >>> >> cpus='0-1' >> >>> >> vcpus=2 >> >>> >> acpi=1 >> >>> >> ahci=1 >> >>> >> vnc=1 >> >>> >> sdl=0 >> >>> >> timer_mode=1 >> >>> >> usb=1 >> >>> >> usbdevice='tablet' >> >>> >> localtime=1 >> >>> >> pci = ['02:00.0','02:00.1','02:00.2'] >> >>> >> >> >>> >> On Thu, May 13, 2010 at 2:28 PM, chris <tknchris@gmail.com> wrote: >> >>> >> > Forwarding to xen-devel. Can't seem to get VT-d working with xen4 from >> >>> >> > tarball on xen.org 2.6.31.13 pv_ops dom0. On pasi's advice I tried >> >>> >> > switching to stable/2.6.32.x branch for dom0 and that doesnt even >> >>> >> > build. Did something change recently thats breaking compilation? >> >>> >> > >> >>> >> > Attached is xen dmesg with iommu=verbose loglvl=all guest_loglvl=all, >> >>> >> > and dom0 dmesg from 2.6.31.x >> >>> >> > >> >>> >> > Any ideas on why VT-d is not working on this board? Initialization >> >>> >> > looks good, xen reports hvm_directio capability, everything says VT-d >> >>> >> > should work until domain is created. >> >>> >> > >> >>> >> > Any ideas why stable/2.6.32.x wont build? >> >>> >> > >> >>> >> > - chris >> >>> >> > >> >>> >> > On Thu, May 13, 2010 at 2:07 PM, chris <tknchris@gmail.com> wrote: >> >>> >> >> I redid it with oldconfig which I didn't think would help and same >> >>> >> >> thing. I guess this tree is broken? Can someone else try and see if >> >>> >> >> they can build it? Ugh, whata day :) >> >>> >> >> >> >>> >> >> On Thu, May 13, 2010 at 1:58 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >> >>> >> >>> On Thu, May 13, 2010 at 01:55:25PM -0400, chris wrote: >> >>> >> >>>> I used the default config on the wiki which you created. Steps I took were: >> >>> >> >>>> >> >>> >> >>>> # make clean distclean >> >>> >> >>>> # wget -O .config >> >>> >> >>>> "http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.10-pvops-dom0-xen-stable-x86_64" >> >>> >> >>> >> >>> >> >>> You should do "make oldconfig" at this point. >> >>> >> >>> >> >>> >> >>>> # make -j8 bzImage >> >>> >> >>>> (blah blah) >> >>> >> >>>> LD vmlinux.o >> >>> >> >>>> MODPOST vmlinux.o >> >>> >> >>>> WARNING: modpost: Found 7 section mismatch(es). >> >>> >> >>>> To see full details build your kernel with: >> >>> >> >>>> 'make CONFIG_DEBUG_SECTION_MISMATCH=y' >> >>> >> >>>> GEN .version >> >>> >> >>>> CHK include/linux/compile.h >> >>> >> >>>> UPD include/linux/compile.h >> >>> >> >>>> CC init/version.o >> >>> >> >>>> LD init/built-in.o >> >>> >> >>>> LD .tmp_vmlinux1 >> >>> >> >>>> drivers/built-in.o: In function `do_hvm_suspend': >> >>> >> >>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: undefined reference >> >>> >> >>>> to `xenbus_suspend' >> >>> >> >>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: undefined reference >> >>> >> >>>> to `xenbus_resume' >> >>> >> >>>> make: *** [.tmp_vmlinux1] Error 1 >> >>> >> >>>> >> >>> >> >>> >> >>> >> >>> Hmm.. weird. I wonder if something has changed recently or what's going on in here.. >> >>> >> >>> >> >>> >> >>> -- Pasi >> >>> >> >>> >> >>> >> >>>> >> >>> >> >>>> On Thu, May 13, 2010 at 11:47 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >> >>> >> >>>> > On Thu, May 13, 2010 at 11:33:57AM -0400, chris wrote: >> >>> >> >>>> >> Successfully grabbed the sources and failed to build: >> >>> >> >>>> >> >> >>> >> >>>> >> LD .tmp_vmlinux1 >> >>> >> >>>> >> drivers/built-in.o: In function `do_hvm_suspend': >> >>> >> >>>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: undefined reference >> >>> >> >>>> >> to `xenbus_suspend' >> >>> >> >>>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: undefined reference >> >>> >> >>>> >> to `xenbus_resume' >> >>> >> >>>> >> make: *** [.tmp_vmlinux1] Error 1 >> >>> >> >>>> >> >> >>> >> >>>> >> :( >> >>> >> >>>> >> >> >>> >> >>>> > >> >>> >> >>>> > Try the example .config files provided on the wiki page. >> >>> >> >>>> > >> >>> >> >>>> > -- Pasi >> >>> >> >>>> > >> >>> >> >>>> >> On Thu, May 13, 2010 at 10:14 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >> >>> >> >>>> >> > On Thu, May 13, 2010 at 10:12:56AM -0400, chris wrote: >> >>> >> >>>> >> >> Pasi, >> >>> >> >>>> >> >> >> >>> >> >>>> >> >> How do I pull those kernel sources you referenced? I see it mentioned >> >>> >> >>>> >> >> on http://wiki.xensource.com/xenwiki/XenParavirtOps but no details on >> >>> >> >>>> >> >> how to retrieve it. >> >>> >> >>>> >> >> >> >>> >> >>>> >> > >> >>> >> >>>> >> > The instructions are there if you read it carefully.. >> >>> >> >>>> >> > There's the topic of how to switch branches. >> >>> >> >>>> >> > >> >>> >> >>>> >> > -- Pasi >> >>> >> >>>> >> > >> >>> >> >>>> >> >> - chris >> >>> >> >>>> >> >> >> >>> >> >>>> >> >> On Thu, May 13, 2010 at 8:29 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >> >>> >> >>>> >> >> > On Wed, May 12, 2010 at 08:41:34PM -0400, chris wrote: >> >>> >> >>>> >> >> >> When reading the vtdhowto I noticed the ability to set iommu=verbose. >> >>> >> >>>> >> >> >> Here is that output, I don't know if it helps at all to figure out >> >>> >> >>>> >> >> >> what is wrong. >> >>> >> >>>> >> >> >> >> >>> >> >>>> >> >> > >> >>> >> >>>> >> >> > That seems to be OK: >> >>> >> >>>> >> >> > >> >>> >> >>>> >> >> > (XEN) I/O virtualisation enabled >> >>> >> >>>> >> >> > (XEN) I/O virtualisation for PV guests disabled >> >>> >> >>>> >> >> > >> >>> >> >>>> >> >> > So hmm.. I wonder if it's related to MSI stuff? >> >>> >> >>>> >> >> > You could try xen.git xen/stable-2.6.32.x branch instead and see if that makes a difference.. >> >>> >> >>>> >> >> > >> >>> >> >>>> >> >> > -- Pasi >> >>> >> >>>> >> >> > >> >>> >> >>>> >> >> >> >> >>> >> >>>> >> >> >> ---------- Forwarded message ---------- >> >>> >> >>>> >> >> >> From: chris <tknchris@gmail.com> >> >>> >> >>>> >> >> >> Date: Wed, May 12, 2010 at 5:28 PM >> >>> >> >>>> >> >> >> Subject: Xen4 / Intel DX58SO Mobo / VT-d not working >> >>> >> >>>> >> >> >> To: Xen-Users List <xen-users@lists.xensource.com> >> >>> >> >>>> >> >> >> >> >>> >> >>>> >> >> >> >> >>> >> >>>> >> >> >> Hello, >> >>> >> >>>> >> >> >> >> >>> >> >>>> >> >> >> I've previously been successful with Xen4 and VT-d on other systems. I >> >>> >> >>>> >> >> >> am having trouble getting VT-d passthrough working to a WinXP domain >> >>> >> >>>> >> >> >> with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is enabled in bios, >> >>> >> >>>> >> >> >> xm info shows hvm_directio capability, I have iommu=1 set, I have the >> >>> >> >>>> >> >> >> devices bound to pciback on dom0 cmdline, xm >> >>> >> >>>> >> >> >> pci-list-assignable-devices shows the devices as assignable. When I >> >>> >> >>>> >> >> >> attempt to start the VM I get the error: >> >>> >> >>>> >> >> >> >> >>> >> >>>> >> >> >> Error: Failed to assign device to IOMMU >> >>> >> >>>> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >> >>> >> >>>> >> >> >> >> >>> >> >>>> >> >> >> Below is all the information I can think of that would be useful to >> >>> >> >>>> >> >> >> help debug it: >> >>> >> >>>> >> >> >> >> >>> >> >>>> >> >> >> BIOS VT-d Enabled: >> >>> >> >>>> >> >> >> http://i43.tinypic.com/nl3a5e.jpg >> >>> >> >>>> >> >> >> http://i42.tinypic.com/nqvlu1.jpg >> >>> >> >>>> >> >> >> >> >>> >> >>>> >> >> >> grub entry: >> >>> >> >>>> >> >> >> >> >>> >> >>>> >> >> >> title Xen 4.0.0 / Debian GNU/Linux, kernel 2.6.31.13 >> >>> >> >>>> >> >> >> root (hd0,0) >> >>> >> >>>> >> >> >> kernel /boot/xen-4.0.0.gz iommu=1 dom0_mem=256M >> >>> >> >>>> >> >> >> dom0_max_vcpus=1 dom0_vcpus_pin=true >> >>> >> >>>> >> >> >> module /boot/vmlinuz-2.6.31.13 root=/dev/md0 ro console=tty0 >> >>> >> >>>> >> >> >> xen-pciback.permissive >> >>> >> >>>> >> >> >> xen-pciback.hide=(02:00.0)(02:00.1)(02:00.2)(04:00.0)(04:00.1)(04:00.2)(07:00.0)(07:00.1)(07:00.2)(09:00.0)(09:00.1)(09:00.2) >> >>> >> >>>> >> >> >> module /boot/initrd.img-2.6.31.13 >> >>> >> >>>> >> >> >> >> >>> >> >>>> >> >> >> # xm pci-list-assignable-devices >> >>> >> >>>> >> >> >> 0000:09:00.0 >> >>> >> >>>> >> >> >> 0000:09:00.1 >> >>> >> >>>> >> >> >> 0000:09:00.2 >> >>> >> >>>> >> >> >> 0000:07:00.0 >> >>> >> >>>> >> >> >> 0000:07:00.1 >> >>> >> >>>> >> >> >> 0000:07:00.2 >> >>> >> >>>> >> >> >> 0000:04:00.0 >> >>> >> >>>> >> >> >> 0000:04:00.1 >> >>> >> >>>> >> >> >> 0000:04:00.2 >> >>> >> >>>> >> >> >> 0000:02:00.0 >> >>> >> >>>> >> >> >> 0000:02:00.1 >> >>> >> >>>> >> >> >> 0000:02:00.2 >> >>> >> >>>> >> >> >> >> >>> >> >>>> >> >> >> # xm info >> >>> >> >>>> >> >> >> host : test-box2 >> >>> >> >>>> >> >> >> release : 2.6.31.13 >> >>> >> >>>> >> >> >> version : #2 SMP Wed May 12 14:11:37 EDT 2010 >> >>> >> >>>> >> >> >> machine : x86_64 >> >>> >> >>>> >> >> >> nr_cpus : 8 >> >>> >> >>>> >> >> >> nr_nodes : 1 >> >>> >> >>>> >> >> >> cores_per_socket : 4 >> >>> >> >>>> >> >> >> threads_per_core : 2 >> >>> >> >>>> >> >> >> cpu_mhz : 2800 >> >>> >> >>>> >> >> >> hw_caps : >> >>> >> >>>> >> >> >> bfebfbff:28100800:00000000:00001b40:0098e3bd:00000000:00000001:00000000 >> >>> >> >>>> >> >> >> virt_caps : hvm hvm_directio >> >>> >> >>>> >> >> >> total_memory : 7950 >> >>> >> >>>> >> >> >> free_memory : 7812 >> >>> >> >>>> >> >> >> node_to_cpu : node0:0-7 >> >>> >> >>>> >> >> >> node_to_memory : node0:7812 >> >>> >> >>>> >> >> >> node_to_dma32_mem : node0:3249 >> >>> >> >>>> >> >> >> max_node_id : 0 >> >>> >> >>>> >> >> >> xen_major : 4 >> >>> >> >>>> >> >> >> xen_minor : 0 >> >>> >> >>>> >> >> >> xen_extra : .0 >> >>> >> >>>> >> >> >> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 >> >>> >> >>>> >> >> >> hvm-3.0-x86_32p hvm-3.0-x86_64 >> >>> >> >>>> >> >> >> xen_scheduler : credit >> >>> >> >>>> >> >> >> xen_pagesize : 4096 >> >>> >> >>>> >> >> >> platform_params : virt_start=0xffff800000000000 >> >>> >> >>>> >> >> >> xen_changeset : unavailable >> >>> >> >>>> >> >> >> xen_commandline : iommu=1 dom0_mem=256M dom0_max_vcpus=1 >> >>> >> >>>> >> >> >> dom0_vcpus_pin=true >> >>> >> >>>> >> >> >> cc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1) >> >>> >> >>>> >> >> >> cc_compile_by : root >> >>> >> >>>> >> >> >> cc_compile_domain : >> >>> >> >>>> >> >> >> cc_compile_date : Thu May 6 13:41:25 EDT 2010 >> >>> >> >>>> >> >> >> xend_config_format : 4 >> >>> >> >>>> >> >> >> >> >>> >> >>>> >> >> >> # xm create vm-five.cfg >> >>> >> >>>> >> >> >> Using config file "./vm-five.cfg". >> >>> >> >>>> >> >> >> Error: Failed to assign device to IOMMU >> >>> >> >>>> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >> >>> >> >>>> >> >> >> >> >>> >> >>>> >> >> >> I feel like I'm missing something really obvious but I've been at it >> >>> >> >>>> >> >> >> for a while now and have run out of brain power. Anyone have any idea >> >>> >> >>>> >> >> >> what might be wrong? >> >>> >> >>>> >> >> >> >> >>> >> >>>> >> >> >> - chris >> >>> >> >>>> >> >> > >> >>> >> >>>> >> >> >> __ __ _ _ ___ ___ >> >>> >> >>>> >> >> >> \ \/ /___ _ __ | || | / _ \ / _ \ >> >>> >> >>>> >> >> >> \ // _ \ \047_ \ | || |_| | | | | | | >> >>> >> >>>> >> >> >> / \ __/ | | | |__ _| |_| | |_| | >> >>> >> >>>> >> >> >> /_/\_\___|_| |_| |_|(_)___(_)___/ >> >>> >> >>>> >> >> >> >> >>> >> >>>> >> >> >> (XEN) Xen version 4.0.0 (root@) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) Thu May 6 13:41:25 EDT 2010 >> >>> >> >>>> >> >> >> (XEN) Latest ChangeSet: unavailable >> >>> >> >>>> >> >> >> (XEN) Command line: iommu=verbose dom0_mem=256M dom0_max_vcpus=1 dom0_vcpus_pin=true >> >>> >> >>>> >> >> >> (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 - 000000000008f000 (usable) >> >>> >> >>>> >> >> >> (XEN) 000000000008f000 - 0000000000090000 (reserved) >> >>> >> >>>> >> >> >> (XEN) 0000000000090000 - 000000000009ec00 (usable) >> >>> >> >>>> >> >> >> (XEN) 000000000009ec00 - 00000000000a0000 (reserved) >> >>> >> >>>> >> >> >> (XEN) 00000000000e0000 - 0000000000100000 (reserved) >> >>> >> >>>> >> >> >> (XEN) 0000000000100000 - 00000000cf4bd000 (usable) >> >>> >> >>>> >> >> >> (XEN) 00000000cf4bd000 - 00000000cf4bf000 (reserved) >> >>> >> >>>> >> >> >> (XEN) 00000000cf4bf000 - 00000000cf4c2000 (usable) >> >>> >> >>>> >> >> >> (XEN) 00000000cf4c2000 - 00000000cf7bf000 (ACPI NVS) >> >>> >> >>>> >> >> >> (XEN) 00000000cf7bf000 - 00000000cf7df000 (usable) >> >>> >> >>>> >> >> >> (XEN) 00000000cf7df000 - 00000000cf7ff000 (ACPI data) >> >>> >> >>>> >> >> >> (XEN) 00000000cf7ff000 - 00000000cf800000 (usable) >> >>> >> >>>> >> >> >> (XEN) 00000000cf800000 - 00000000d0000000 (reserved) >> >>> >> >>>> >> >> >> (XEN) 00000000f8000000 - 00000000fd000000 (reserved) >> >>> >> >>>> >> >> >> (XEN) 00000000ffe00000 - 0000000100000000 (reserved) >> >>> >> >>>> >> >> >> (XEN) 0000000100000000 - 0000000230000000 (usable) >> >>> >> >>>> >> >> >> (XEN) ACPI: RSDP 000FE020, 0024 (r2 INTEL ) >> >>> >> >>>> >> >> >> (XEN) ACPI: XSDT CF7FE120, 0074 (r1 INTEL DX58SO 11F6 1000013) >> >>> >> >>>> >> >> >> (XEN) ACPI: FACP CF7FD000, 00F4 (r3 INTEL DX58SO 11F6 MSFT 100000D) >> >>> >> >>>> >> >> >> (XEN) ACPI Warning (tbfadt-0444): Optional field "Pm2ControlBlock" has zero address or length: 0000000000000450/0 [20070126] >> >>> >> >>>> >> >> >> (XEN) ACPI: DSDT CF7F8000, 4641 (r2 INTEL DX58SO 11F6 MSFT 100000D) >> >>> >> >>>> >> >> >> (XEN) ACPI: FACS CF728000, 0040 >> >>> >> >>>> >> >> >> (XEN) ACPI: APIC CF7F7000, 0138 (r2 INTEL DX58SO 11F6 MSFT 100000D) >> >>> >> >>>> >> >> >> (XEN) ACPI: WDDT CF7F6000, 0040 (r1 INTEL DX58SO 11F6 MSFT 100000D) >> >>> >> >>>> >> >> >> (XEN) ACPI: MCFG CF7F5000, 003C (r1 INTEL DX58SO 11F6 MSFT 100000D) >> >>> >> >>>> >> >> >> (XEN) ACPI: ASF! CF7F4000, 00AC (r32 INTEL DX58SO 11F6 MSFT 100000D) >> >>> >> >>>> >> >> >> (XEN) ACPI: HPET CF7F3000, 0038 (r1 INTEL DX58SO 11F6 MSFT 100000D) >> >>> >> >>>> >> >> >> (XEN) ACPI: SSDT CF7E2000, E134 (r1 INTEL SSDT PM 11F6 MSFT 100000D) >> >>> >> >>>> >> >> >> (XEN) ACPI: DMAR CF7DF000, 0140 (r1 INTEL DX58SO 11F6 MSFT 100000D) >> >>> >> >>>> >> >> >> (XEN) ACPI: WDTT CF7F1000, 020C (r2 INTEL DX58SO 11F6 MSFT 100000D) >> >>> >> >>>> >> >> >> (XEN) ACPI: ASPT CF7F2000, 0034 (r4 INTEL PerfTune 11F6 MSFT 100000D) >> >>> >> >>>> >> >> >> (XEN) System RAM: 7950MB (8140820kB) >> >>> >> >>>> >> >> >> (XEN) Domain heap initialised >> >>> >> >>>> >> >> >> (XEN) Processor #0 7:10 APIC version 21 >> >>> >> >>>> >> >> >> (XEN) Processor #2 7:10 APIC version 21 >> >>> >> >>>> >> >> >> (XEN) Processor #4 7:10 APIC version 21 >> >>> >> >>>> >> >> >> (XEN) Processor #6 7:10 APIC version 21 >> >>> >> >>>> >> >> >> (XEN) Processor #1 7:10 APIC version 21 >> >>> >> >>>> >> >> >> (XEN) Processor #3 7:10 APIC version 21 >> >>> >> >>>> >> >> >> (XEN) Processor #5 7:10 APIC version 21 >> >>> >> >>>> >> >> >> (XEN) Processor #7 7:10 APIC version 21 >> >>> >> >>>> >> >> >> (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 >> >>> >> >>>> >> >> >> (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:679: Host address width 39 >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = fe711000 >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1b.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = fe710000 >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:340: IOAPIC: f0:1f.7 >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:411: flags: INCLUDE_ALL >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e9000 end_address e9fff >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.1 >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ea000 end_address eafff >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.2 >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr eb000 end_address ebfff >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e6000 end_address e6fff >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.1 >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e7000 end_address e7fff >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.2 >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e8000 end_address e8fff >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ec000 end_address eefff >> >>> >> >>>> >> >> >> (XEN) Using scheduler: SMP Credit Scheduler (credit) >> >>> >> >>>> >> >> >> (XEN) Detected 2800.125 MHz processor. >> >>> >> >>>> >> >> >> (XEN) Initing memory sharing. >> >>> >> >>>> >> >> >> (XEN) VMX: Supported advanced features: >> >>> >> >>>> >> >> >> (XEN) - APIC MMIO access virtualisation >> >>> >> >>>> >> >> >> (XEN) - APIC TPR shadow >> >>> >> >>>> >> >> >> (XEN) - Extended Page Tables (EPT) >> >>> >> >>>> >> >> >> (XEN) - Virtual-Processor Identifiers (VPID) >> >>> >> >>>> >> >> >> (XEN) - Virtual NMI >> >>> >> >>>> >> >> >> (XEN) - MSR direct-access bitmap >> >>> >> >>>> >> >> >> (XEN) HVM: ASIDs enabled. >> >>> >> >>>> >> >> >> (XEN) HVM: VMX enabled >> >>> >> >>>> >> >> >> (XEN) HVM: Hardware Assisted Paging detected. >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = fe711000 iommu->reg = ffff82c3fff57000 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c9008010e60262 ecap = f0207a >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = fe710000 iommu->reg = ffff82c3fff56000 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c90780106f0462 ecap = f020fa >> >>> >> >>>> >> >> >> (XEN) Intel VT-d Snoop Control not supported. >> >>> >> >>>> >> >> >> (XEN) Intel VT-d DMA Passthrough not supported. >> >>> >> >>>> >> >> >> (XEN) Intel VT-d Queued Invalidation supported. >> >>> >> >>>> >> >> >> (XEN) Intel VT-d Interrupt Remapping supported. >> >>> >> >>>> >> >> >> (XEN) I/O virtualisation enabled >> >>> >> >>>> >> >> >> (XEN) I/O virtualisation for PV guests disabled >> >>> >> >>>> >> >> >> (XEN) Total of 8 processors activated. >> >>> >> >>>> >> >> >> (XEN) ENABLING IO-APIC IRQs >> >>> >> >>>> >> >> >> (XEN) -> Using new ACK method >> >>> >> >>>> >> >> >> (XEN) TSC is reliable, synchronization unnecessary >> >>> >> >>>> >> >> >> (XEN) Platform timer is 14.318MHz HPET >> >>> >> >>>> >> >> >> (XEN) Allocated console ring of 16 KiB. >> >>> >> >>>> >> >> >> (XEN) Brought up 8 CPUs >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:0.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.1 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.1 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.2 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:14.3 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:19.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.1 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.2 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.7 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:1b.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.1 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.2 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.7 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.2 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.3 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.5 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.1 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.2 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.1 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.2 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 5:0.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.1 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.2 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.1 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.2 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = a:0.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.1 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.2 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.3 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.4 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.5 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.6 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.7 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.1 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.1 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.1 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.4 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.1 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.2 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.3 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.1 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.2 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.3 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.1 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.2 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.3 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = ffff82c3fff57000 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = ffff82c3fff56000 >> >>> >> >>>> >> >> >> (XEN) *** LOADING DOMAIN 0 *** >> >>> >> >>>> >> >> >> (XEN) Xen kernel: 64-bit, lsb, compat32 >> >>> >> >>>> >> >> >> (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x26ae000 >> >>> >> >>>> >> >> >> (XEN) PHYSICAL MEMORY ARRANGEMENT: >> >>> >> >>>> >> >> >> (XEN) Dom0 alloc.: 0000000210000000->0000000220000000 >> >>> >> >>>> >> >> >> (XEN) VIRTUAL MEMORY ARRANGEMENT: >> >>> >> >>>> >> >> >> (XEN) Loaded kernel: ffffffff81000000->ffffffff826ae000 >> >>> >> >>>> >> >> >> (XEN) Init. ramdisk: ffffffff826ae000->ffffffff8f4de600 >> >>> >> >>>> >> >> >> (XEN) Phys-Mach map: ffffffff8f4df000->ffffffff8f55f000 >> >>> >> >>>> >> >> >> (XEN) Start info: ffffffff8f55f000->ffffffff8f55f4b4 >> >>> >> >>>> >> >> >> (XEN) Page tables: ffffffff8f560000->ffffffff8f5df000 >> >>> >> >>>> >> >> >> (XEN) Boot stack: ffffffff8f5df000->ffffffff8f5e0000 >> >>> >> >>>> >> >> >> (XEN) TOTAL: ffffffff80000000->ffffffff8f800000 >> >>> >> >>>> >> >> >> (XEN) ENTRY ADDRESS: ffffffff81a10860 >> >>> >> >>>> >> >> >> (XEN) Dom0 has maximum 1 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 \047CTRL-a\047 three times to switch input to Xen) >> >>> >> >>>> >> >> >> (XEN) Freed 164kB init memory. >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 pirq=0 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=2, irq=0 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=000009f0 pirq=0 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 3 already mapped >> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 4 already mapped >> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 5 already mapped >> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 6 already mapped >> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 7 already mapped >> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 8 already mapped >> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 9 already mapped >> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 10 already mapped >> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 11 already mapped >> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 12 already mapped >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000009f0 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 pirq=0 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=23, irq=23 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a929 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a929 pirq=23 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 pirq=16 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 pirq=16 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>> >> >>>> >> >> > >> >>> >> >>>> >> >> >> _______________________________________________ >> >>> >> >>>> >> >> >> Xen-users mailing list >> >>> >> >>>> >> >> >> Xen-users@lists.xensource.com >> >>> >> >>>> >> >> >> http://lists.xensource.com/xen-users >> >>> >> >>>> >> >> > >> >>> >> >>>> >> > >> >>> >> >>>> > >> >>> >> >>> >> >>> >> >> >> >>> >> > >> >>> > >> >> >> > > [-- Attachment #2: WORKING.txt --] [-- Type: text/plain, Size: 64902 bytes --] scanmaster1:~# uname -a Linux scanmaster1 2.6.31.6 #1 SMP Wed Dec 23 16:20:35 EST 2009 x86_64 GNU/Linux scanmaster1:~# xm info host : scanmaster1 release : 2.6.31.6 version : #1 SMP Wed Dec 23 16:20:35 EST 2009 machine : x86_64 nr_cpus : 4 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 2660 hw_caps : bfebfbff:20100800:00000000:00000140:0408e3fd:00000000:00000001:00000000 virt_caps : hvm hvm_directio total_memory : 4016 free_memory : 63 node_to_cpu : node0:0-3 node_to_memory : node0:63 xen_major : 3 xen_minor : 4 xen_extra : .2 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable cc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1) cc_compile_by : root cc_compile_domain : cc_compile_date : Wed Dec 23 15:58:58 EST 2009 xend_config_format : 4 __ __ _____ _ _ ____ \ \/ /___ _ __ |___ /| || | |___ \ \ // _ \ '_ \ |_ \| || |_ __) | / \ __/ | | | ___) |__ _| / __/ /_/\_\___|_| |_| |____(_) |_|(_)_____| (XEN) Xen version 3.4.2 (root@) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) Wed Dec 23 15:58:58 EST 2009 (XEN) Latest ChangeSet: unavailable (XEN) Command line: vtd=1 iommu=1 dom0_mem=768M dom0_max_vcpus=1 dom0_vcpus_pin=true (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 - 000000000008f000 (usable) (XEN) 000000000008f000 - 0000000000090000 (reserved) (XEN) 0000000000090000 - 000000000009dc00 (usable) (XEN) 000000000009dc00 - 00000000000a0000 (reserved) (XEN) 00000000000e0000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 00000000cde36000 (usable) (XEN) 00000000cde36000 - 00000000cdeb7000 (ACPI NVS) (XEN) 00000000cdeb7000 - 00000000cf02a000 (usable) (XEN) 00000000cf02a000 - 00000000cf02c000 (reserved) (XEN) 00000000cf02c000 - 00000000cf156000 (usable) (XEN) 00000000cf156000 - 00000000cf1e3000 (ACPI NVS) (XEN) 00000000cf1e3000 - 00000000cf1eb000 (usable) (XEN) 00000000cf1eb000 - 00000000cf1f3000 (ACPI data) (XEN) 00000000cf1f3000 - 00000000cf1f4000 (usable) (XEN) 00000000cf1f4000 - 00000000cf1ff000 (ACPI data) (XEN) 00000000cf1ff000 - 00000000cf200000 (usable) (XEN) 00000000cf200000 - 00000000d0000000 (reserved) (XEN) 00000000f0000000 - 00000000f8000000 (reserved) (XEN) 00000000ffc00000 - 0000000100000000 (reserved) (XEN) 0000000100000000 - 000000012c000000 (usable) (XEN) System RAM: 4016MB (4112868kB) (XEN) ACPI: RSDP 000FE020, 0014 (r0 INTEL ) (XEN) ACPI: RSDT CF1FD038, 005C (r1 INTEL DQ3510J 466 1000013) (XEN) ACPI: FACP CF1FC000, 0074 (r1 INTEL DQ3510J 466 MSFT 1000013) (XEN) ACPI: DSDT CF1F8000, 3D6A (r1 INTEL DQ3510J 466 MSFT 1000013) (XEN) ACPI: FACS CF163000, 0040 (XEN) ACPI: APIC CF1F7000, 0078 (r1 INTEL DQ3510J 466 MSFT 1000013) (XEN) ACPI: WDDT CF1F6000, 0040 (r1 INTEL DQ3510J 466 MSFT 1000013) (XEN) ACPI: MCFG CF1F5000, 003C (r1 INTEL DQ3510J 466 MSFT 1000013) (XEN) ACPI: ASF! CF1F4000, 00A6 (r32 INTEL DQ3510J 466 MSFT 1000013) (XEN) ACPI: DMAR CF1F2000, 0120 (r1 INTEL DQ3510J 466 MSFT 1000013) (XEN) ACPI: ASPT CF1F1000, 0034 (r3 INTEL DQ3510J 466 MSFT 1000013) (XEN) ACPI: WDTT CF1F0000, 02CC (r1 INTEL DQ3510J 466 MSFT 1000013) (XEN) ACPI: SSDT CF1EF000, 0204 (r1 INTEL CpuPm 466 MSFT 1000013) (XEN) ACPI: SSDT CF1EE000, 00DD (r1 INTEL Cpu0Cst 466 MSFT 1000013) (XEN) ACPI: SSDT CF1ED000, 00DD (r1 INTEL Cpu1Cst 466 MSFT 1000013) (XEN) ACPI: SSDT CF1EC000, 00DD (r1 INTEL Cpu2Cst 466 MSFT 1000013) (XEN) ACPI: SSDT CF1EB000, 00DD (r1 INTEL Cpu3Cst 466 MSFT 1000013) (XEN) ACPI: TCPA CF157000, 0032 (r2 INTEL TIANO 2 MSFT 1000013) (XEN) Domain heap initialised (XEN) Processor #0 7:7 APIC version 20 (XEN) Processor #2 7:7 APIC version 20 (XEN) Processor #1 7:7 APIC version 20 (XEN) Processor #3 7:7 APIC version 20 (XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23 (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) Intel VT-d DMAR tables have been parsed. (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Detected 2660.038 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/2 eip 8c000 (XEN) CPU1: Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz stepping 0a (XEN) Booting processor 2/1 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 3.579MHz ACPI PM Timer (XEN) Brought up 4 CPUs (XEN) Intel VT-d Snoop Control not supported. (XEN) Intel VT-d DMA Passthrough not supported. (XEN) Intel VT-d Queued Invalidation not supported. (XEN) Intel VT-d Interrupt Remapping not supported. (XEN) I/O virtualisation enabled (XEN) I/O virtualisation for PV guests disabled (XEN) CPUIDLE: disabled due to no HPET. Force enable with 'cpuidle'. (XEN) [VT-D]iommu.c:721: iommu_page_fault: iommu->reg = ffff828bfff56000 (XEN) [VT-D]iommu.c:690: iommu_fault_status: Fault Overflow (XEN) [VT-D]iommu.c:693: iommu_fault_status: Primary Pending Fault (XEN) [VT-D]iommu.c:675: iommu_fault:DMA Write: 0:2.0 addr 280002000 REASON 5 iommu->reg = ffff828bfff56000 (XEN) print_vtd_entries: iommu = ffff83012bde4590 bdf = 0:2:0 gmfn = 280002 (XEN) root_entry = ffff83012bdad000 (XEN) root_entry[0] = 12822f001 (XEN) context = ffff83012822f000 (XEN) context[10] = 101_12bd8f001 (XEN) l3 = ffff83012bd8f000 (XEN) l3_index = a (XEN) l3[a] = 0 (XEN) l3[a] not present (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x26a5000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000110000000->0000000120000000 (131072 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff81000000->ffffffff826a5000 (XEN) Init. ramdisk: ffffffff826a5000->ffffffff8f501a00 (XEN) Phys-Mach map: ffffffff8f502000->ffffffff8f682000 (XEN) Start info: ffffffff8f682000->ffffffff8f6824b4 (XEN) Page tables: ffffffff8f683000->ffffffff8f702000 (XEN) Boot stack: ffffffff8f702000->ffffffff8f703000 (XEN) TOTAL: ffffffff80000000->ffffffff8f800000 (XEN) ENTRY ADDRESS: ffffffff81a08860 (XEN) Dom0 has maximum 1 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) ioapic_guest_write: apic=0, pin=2, old_irq=0, new_irq=-1 (XEN) ioapic_guest_write: old_entry=000009f0, new_entry=00010900 (XEN) ioapic_guest_write: Attempt to remove IO-APIC pin of in-use IRQ! (XEN) ioapic_guest_write: apic=0, pin=0, old_irq=-1, new_irq=0 (XEN) ioapic_guest_write: old_entry=00010900, new_entry=000009f0 (XEN) ioapic_guest_write: Attempt to add IO-APIC pin for in-use IRQ! (XEN) mm.c:806:d0 Error getting mfn 30000 (pfn 5555555555555555) from L1 entry 8000000030000473 for l1e_owner=0, pg_owner=32753 (XEN) ioapic_guest_write: apic=0, pin=17, old_irq=17, new_irq=17 (XEN) ioapic_guest_write: old_entry=0000a9c0, new_entry=0001a9c0 (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! (XEN) ioapic_guest_write: apic=0, pin=23, old_irq=23, new_irq=23 (XEN) ioapic_guest_write: old_entry=0000a951, new_entry=0001a951 (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! (XEN) ioapic_guest_write: apic=0, pin=18, old_irq=18, new_irq=18 (XEN) ioapic_guest_write: old_entry=0000a9d0, new_entry=0001a9d0 (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! (XEN) ioapic_guest_write: apic=0, pin=18, old_irq=18, new_irq=18 (XEN) ioapic_guest_write: old_entry=0000a9d0, new_entry=0001a9d0 (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! (XEN) ioapic_guest_write: apic=0, pin=18, old_irq=18, new_irq=18 (XEN) ioapic_guest_write: old_entry=0000a9d0, new_entry=0001a9d0 (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! (XEN) ioapic_guest_write: apic=0, pin=18, old_irq=18, new_irq=18 (XEN) ioapic_guest_write: old_entry=0000a9d0, new_entry=0001a9d0 (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! Initializing cgroup subsys cpuset Initializing cgroup subsys cpu Linux version 2.6.31.6 (root@scanmaster1) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #1 SMP Wed Dec 23 16:20:35 EST 2009 Command line: root=/dev/md0 ro console=tty0 xen-pciback.permissive xen-pciback.hide=(02:00.0)(02:00.1)(02:00.2)(04:00.0)(04:00.1)(04:00.2)(06:00.0)(06:00.1)(06:00.2)(0a:00.0)(0a :00.1)(0a:00.2)(0a:03.0) KERNEL supported cpus: Intel GenuineIntel AMD AuthenticAMD Centaur CentaurHauls xen_release_chunk: looking at area pfn 30000-cde36 xen_release_chunk: looking at area pfn cdeb7-cf02a xen_release_chunk: looking at area pfn cf02c-cf156 xen_release_chunk: looking at area pfn cf1e3-cf1eb xen_release_chunk: looking at area pfn cf1f3-cf1f4 xen_release_chunk: looking at area pfn cf1ff-cf200 xen_release_chunk: looking at area pfn d0000-f0000 xen_release_chunk: looking at area pfn f8000-ffc00 released 0 pages of unused memory BIOS-provided physical RAM map: Xen: 0000000000000000 - 000000000008f000 (usable) Xen: 000000000008f000 - 0000000000090000 (reserved) Xen: 0000000000090000 - 000000000009dc00 (usable) Xen: 000000000009dc00 - 0000000000100000 (reserved) Xen: 0000000000100000 - 0000000030000000 (usable) Xen: 00000000cde36000 - 00000000cdeb7000 (ACPI NVS) Xen: 00000000cf02a000 - 00000000cf02c000 (reserved) Xen: 00000000cf156000 - 00000000cf1e3000 (ACPI NVS) Xen: 00000000cf1eb000 - 00000000cf1f3000 (ACPI data) Xen: 00000000cf1f4000 - 00000000cf1ff000 (ACPI data) Xen: 00000000cf200000 - 00000000d0000000 (reserved) Xen: 00000000f0000000 - 00000000f8000000 (reserved) Xen: 00000000ffc00000 - 0000000100000000 (reserved) DMI 2.4 present. last_pfn = 0x30000 max_arch_pfn = 0x400000000 initial memory mapped : 0 - 20000000 init_memory_mapping: 0000000000000000-0000000030000000 0000000000 - 0030000000 page 4k kernel direct mapping tables up to 30000000 @ 100000-282000 RAMDISK: 026a5000 - 0f501a00 ACPI: RSDP 00000000000fe020 00014 (v00 INTEL ) ACPI: RSDT 00000000cf1fd038 0005C (v01 INTEL DQ3510J 00000466 01000013) ACPI: FACP 00000000cf1fc000 00074 (v01 INTEL DQ3510J 00000466 MSFT 01000013) ACPI: DSDT 00000000cf1f8000 03D6A (v01 INTEL DQ3510J 00000466 MSFT 01000013) ACPI: FACS 00000000cf163000 00040 ACPI: APIC 00000000cf1f7000 00078 (v01 INTEL DQ3510J 00000466 MSFT 01000013) ACPI: WDDT 00000000cf1f6000 00040 (v01 INTEL DQ3510J 00000466 MSFT 01000013) ACPI: MCFG 00000000cf1f5000 0003C (v01 INTEL DQ3510J 00000466 MSFT 01000013) ACPI: ASF! 00000000cf1f4000 000A6 (v32 INTEL DQ3510J 00000466 MSFT 01000013) ACPI: 00000000cf1f2000 00120 (v01 INTEL DQ3510J 00000466 MSFT 01000013) ACPI: ASPT 00000000cf1f1000 00034 (v03 INTEL DQ3510J 00000466 MSFT 01000013) ACPI: WDTT 00000000cf1f0000 002CC (v01 INTEL DQ3510J 00000466 MSFT 01000013) ACPI: SSDT 00000000cf1ef000 00204 (v01 INTEL CpuPm 00000466 MSFT 01000013) ACPI: SSDT 00000000cf1ee000 000DD (v01 INTEL Cpu0Cst 00000466 MSFT 01000013) ACPI: SSDT 00000000cf1ed000 000DD (v01 INTEL Cpu1Cst 00000466 MSFT 01000013) ACPI: SSDT 00000000cf1ec000 000DD (v01 INTEL Cpu2Cst 00000466 MSFT 01000013) ACPI: SSDT 00000000cf1eb000 000DD (v01 INTEL Cpu3Cst 00000466 MSFT 01000013) ACPI: TCPA 00000000cf157000 00032 (v02 INTEL TIANO 00000002 MSFT 01000013) ACPI: Local APIC address 0xfee00000 No NUMA configuration found Faking a node at 0000000000000000-0000000030000000 Bootmem setup node 0 0000000000000000-0000000030000000 NODE_DATA [0000000000008000 - 000000000001ffff] bootmap [0000000000020000 - 0000000000025fff] pages 6 (8 early reservations) ==> bootmem [0000000000 - 0030000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] #1 [000f683000 - 000f702000] XEN PAGETABLES ==> [000f683000 - 000f702000] #2 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 - 0000008000] #3 [0001000000 - 0002684090] TEXT DATA BSS ==> [0001000000 - 0002684090] #4 [00026a5000 - 000f501a00] RAMDISK ==> [00026a5000 - 000f501a00] #5 [000f502000 - 000f683000] XEN START INFO ==> [000f502000 - 000f683000] #6 [0002685000 - 00026851a6] BRK ==> [0002685000 - 00026851a6] #7 [0000100000 - 0000200000] PGTABLE ==> [0000100000 - 0000200000] found SMP MP-table at [ffff8800000fe5c0] fe5c0 Zone PFN ranges: DMA 0x00000000 -> 0x00001000 DMA32 0x00001000 -> 0x00100000 Normal 0x00100000 -> 0x00100000 Movable zone start PFN for each node early_node_map[3] active PFN ranges 0: 0x00000000 -> 0x0000008f 0: 0x00000090 -> 0x0000009d 0: 0x00000100 -> 0x00030000 On node 0 totalpages: 196508 DMA zone: 104 pages used for memmap DMA zone: 259 pages reserved DMA zone: 3633 pages, LIFO batch:0 DMA32 zone: 4888 pages used for memmap DMA32 zone: 187624 pages, LIFO batch:31 ACPI: PM-Timer IO Port: 0x408 ACPI: Local APIC address 0xfee00000 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled) ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1]) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Using ACPI (MADT) for SMP configuration information SMP: Allowing 1 CPUs, 0 hotplug CPUs nr_irqs_gsi: 24 PM: Registered nosave memory: 000000000008f000 - 0000000000090000 PM: Registered nosave memory: 000000000009d000 - 000000000009e000 PM: Registered nosave memory: 000000000009e000 - 0000000000100000 Allocating PCI resources starting at 30000000 (gap: 30000000:9de36000) NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:1 nr_node_ids:1 PERCPU: Allocated 471 4k pages, static data 1926752 bytes trying to map vcpu_info 0 at ffffc9000000b020, mfn 11f727, offset 32 cpu 0 using vcpu_info at ffffc9000000b020 Xen: using vcpu_info placement Built 1 zonelists in Node order, mobility grouping on. Total pages: 191257 Policy zone: DMA32 Kernel command line: root=/dev/md0 ro console=tty0 xen-pciback.permissive xen-pciback.hide=(02:00.0)(02:00.1)(02:00.2)(04:00.0)(04:00.1)(04:00.2)(06:00.0)(06:00.1)(06:00.2)(0a:0 0.0)(0a:00.1)(0a:00.2)(0a:03.0) PID hash table entries: 4096 (order: 12, 32768 bytes) Initializing CPU#0 PCI-DMA: Using Xen software bounce buffering for IO (Xen-SWIOTLB) xen_swiotlb_fixup: buf=ffff880010e8f000 size=67108864 xen_swiotlb_fixup: buf=ffff880014eef000 size=32768 Placing 64MB Xen software IO TLB between ffff880010e8f000 - ffff880014e8f000 Xen software IO TLB at phys 0x10e8f000 - 0x14e8f000 Memory: 460440k/786432k available (5257k kernel code, 400k absent, 325592k reserved, 3127k data, 3208k init) SLUB: Genslabs=14, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 Hierarchical RCU implementation. NR_IRQS:4352 nr_irqs:256 xen: registering gsi 0 triggering 1 polarity 0 xen: --> irq=0 xen_set_ioapic_routing: irq 0 gsi 0 vector 240 ioapic 0 pin 0 triggering 0 polarity 0 xen: registering gsi 1 triggering 1 polarity 0 xen: --> irq=1 xen_set_ioapic_routing: irq 1 gsi 1 vector 32 ioapic 0 pin 1 triggering 0 polarity 0 xen: registering gsi 3 triggering 1 polarity 0 xen: --> irq=3 xen_set_ioapic_routing: irq 3 gsi 3 vector 40 ioapic 0 pin 3 triggering 0 polarity 0 xen: registering gsi 4 triggering 1 polarity 0 xen: --> irq=4 xen_set_ioapic_routing: irq 4 gsi 4 vector 48 ioapic 0 pin 4 triggering 0 polarity 0 xen: registering gsi 5 triggering 1 polarity 0 xen: --> irq=5 xen_set_ioapic_routing: irq 5 gsi 5 vector 56 ioapic 0 pin 5 triggering 0 polarity 0 xen: registering gsi 6 triggering 1 polarity 0 xen: --> irq=6 xen_set_ioapic_routing: irq 6 gsi 6 vector 64 ioapic 0 pin 6 triggering 0 polarity 0 xen: registering gsi 7 triggering 1 polarity 0 xen: --> irq=7 xen_set_ioapic_routing: irq 7 gsi 7 vector 72 ioapic 0 pin 7 triggering 0 polarity 0 xen: registering gsi 8 triggering 1 polarity 0 xen: --> irq=8 xen_set_ioapic_routing: irq 8 gsi 8 vector 80 ioapic 0 pin 8 triggering 0 polarity 0 xen: registering gsi 9 triggering 0 polarity 0 xen: --> irq=9 xen_set_ioapic_routing: irq 9 gsi 9 vector 88 ioapic 0 pin 9 triggering 1 polarity 0 xen: registering gsi 10 triggering 1 polarity 0 xen: --> irq=10 xen_set_ioapic_routing: irq 10 gsi 10 vector 96 ioapic 0 pin 10 triggering 0 polarity 0 xen: registering gsi 11 triggering 1 polarity 0 xen: --> irq=11 xen_set_ioapic_routing: irq 11 gsi 11 vector 104 ioapic 0 pin 11 triggering 0 polarity 0 xen: registering gsi 12 triggering 1 polarity 0 xen: --> irq=12 xen_set_ioapic_routing: irq 12 gsi 12 vector 112 ioapic 0 pin 12 triggering 0 polarity 0 xen: registering gsi 13 triggering 1 polarity 0 xen: --> irq=13 xen_set_ioapic_routing: irq 13 gsi 13 vector 120 ioapic 0 pin 13 triggering 0 polarity 0 xen: registering gsi 14 triggering 1 polarity 0 xen: --> irq=14 xen_set_ioapic_routing: irq 14 gsi 14 vector 136 ioapic 0 pin 14 triggering 0 polarity 0 xen: registering gsi 15 triggering 1 polarity 0 xen: --> irq=15 xen_set_ioapic_routing: irq 15 gsi 15 vector 144 ioapic 0 pin 15 triggering 0 polarity 0 Detected 2660.002 MHz processor. Console: colour VGA+ 80x25 console [tty0] enabled Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar ... MAX_LOCKDEP_SUBCLASSES: 8 ... MAX_LOCK_DEPTH: 48 ... MAX_LOCKDEP_KEYS: 8191 ... CLASSHASH_SIZE: 4096 ... MAX_LOCKDEP_ENTRIES: 16384 ... MAX_LOCKDEP_CHAINS: 32768 ... CHAINHASH_SIZE: 16384 memory used by lock dependency info: 6207 kB per task-struct memory footprint: 2688 bytes allocated 7864320 bytes of page_cgroup please try 'cgroup_disable=memory' option if you don't want memory cgroups ODEBUG: 9 of 9 active objects replaced Xen: using vcpuop timer interface installing Xen timer for CPU 0 alloc irq_desc for 255 on node 0 alloc kstat_irqs on node 0 xen: vcpu_time_info placement not supported Calibrating delay loop (skipped), value calculated using timer frequency.. 5320.00 BogoMIPS (lpj=2660002) Security Framework initialized SELinux: Initializing. SELinux: Starting in permissive mode Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) Mount-cache hash table entries: 256 Initializing cgroup subsys ns Initializing cgroup subsys cpuacct Initializing cgroup subsys memory Initializing cgroup subsys devices Initializing cgroup subsys freezer Initializing cgroup subsys net_cls CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 3072K CPU 0/0x0 -> Node 0 CPU: Unsupported number of siblings 4 mce: CPU supports 6 MCE banks Performance Counters: unsupported p6 CPU model 23 no PMU driver, software counters only. SMP alternatives: switching to UP code Freeing SMP alternatives: 31k freed ACPI: Core revision 20090521 ftrace: converting mcount calls to 0f 1f 44 00 00 ftrace: allocating 20187 entries in 80 pages alloc irq_desc for 254 on node 0 alloc kstat_irqs on node 0 alloc irq_desc for 253 on node 0 alloc kstat_irqs on node 0 alloc irq_desc for 252 on node 0 alloc kstat_irqs on node 0 alloc irq_desc for 251 on node 0 alloc kstat_irqs on node 0 Brought up 1 CPUs CPU0 attaching NULL sched-domain. Booting paravirtualized kernel on Xen Xen version: 3.4.2 (preserve-AD) (dom0) Grant tables using version 1 layout. Grant table initialized regulator: core version 0.5 Time: 12:08:39 Date: 05/11/10 NET: Registered protocol family 16 alloc irq_desc for 250 on node 0 alloc kstat_irqs on node 0 xenbus_probe_init ok ACPI: bus type pci registered PCI: MCFG configuration 0: base f0000000 segment 0 buses 0 - 127 PCI: MCFG area at f0000000 reserved in E820 PCI: Using MMCONFIG at f0000000 - f7ffffff PCI: Using configuration type 1 for base access bio: create slab <bio-0> at 0 ACPI: EC: Look up EC in DSDT ACPI: Interpreter enabled ACPI: (supports S0 S1 S3 S4 S5) ACPI: Using IOAPIC for interrupt routing ACPI Warning: Incorrect checksum in table [ ] - A8, should be EC 20090521 tbutils-246 ACPI: No dock devices found. ACPI: PCI Root Bridge [PCI0] (0000:00) pci 0000:00:01.0: PME# supported from D0 D3hot D3cold pci 0000:00:01.0: PME# disabled pci 0000:00:02.0: reg 10 32bit mmio: [0xe0680000-0xe06fffff] pci 0000:00:02.0: reg 14 io port: [0x2430-0x2437] pci 0000:00:02.0: reg 18 32bit mmio: [0xd0000000-0xdfffffff] pci 0000:00:02.0: reg 1c 32bit mmio: [0xe0400000-0xe04fffff] pci 0000:00:02.1: reg 10 32bit mmio: [0xe0600000-0xe067ffff] pci 0000:00:03.0: reg 10 64bit mmio: [0xe0726100-0xe072610f] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold pci 0000:00:03.0: PME# disabled pci 0000:00:19.0: reg 10 32bit mmio: [0xe0700000-0xe071ffff] pci 0000:00:19.0: reg 14 32bit mmio: [0xe0724000-0xe0724fff] pci 0000:00:19.0: reg 18 io port: [0x2400-0x241f] pci 0000:00:19.0: PME# supported from D0 D3hot D3cold pci 0000:00:19.0: PME# disabled pci 0000:00:1a.0: reg 20 io port: [0x20e0-0x20ff] pci 0000:00:1a.1: reg 20 io port: [0x20c0-0x20df] pci 0000:00:1a.2: reg 20 io port: [0x20a0-0x20bf] pci 0000:00:1a.7: reg 10 32bit mmio: [0xe0725c00-0xe0725fff] pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold pci 0000:00:1a.7: PME# disabled pci 0000:00:1b.0: reg 10 64bit mmio: [0xe0720000-0xe0723fff] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold pci 0000:00:1b.0: PME# disabled pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold pci 0000:00:1c.0: PME# disabled pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold pci 0000:00:1c.1: PME# disabled pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold pci 0000:00:1c.2: PME# disabled pci 0000:00:1c.3: PME# supported from D0 D3hot D3cold pci 0000:00:1c.3: PME# disabled pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold pci 0000:00:1c.4: PME# disabled pci 0000:00:1d.0: reg 20 io port: [0x2080-0x209f] pci 0000:00:1d.1: reg 20 io port: [0x2060-0x207f] pci 0000:00:1d.2: reg 20 io port: [0x2040-0x205f] pci 0000:00:1d.7: reg 10 32bit mmio: [0xe0725800-0xe0725bff] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold pci 0000:00:1d.7: PME# disabled pci 0000:00:1f.0: quirk: region 0400-047f claimed by ICH6 ACPI/GPIO/TCO pci 0000:00:1f.0: quirk: region 0500-053f claimed by ICH6 GPIO pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0680 (mask 007f) pci 0000:00:1f.2: reg 10 io port: [0x2428-0x242f] pci 0000:00:1f.2: reg 14 io port: [0x243c-0x243f] pci 0000:00:1f.2: reg 18 io port: [0x2420-0x2427] pci 0000:00:1f.2: reg 1c io port: [0x2438-0x243b] pci 0000:00:1f.2: reg 20 io port: [0x2020-0x203f] pci 0000:00:1f.2: reg 24 32bit mmio: [0xe0725000-0xe07257ff] pci 0000:00:1f.2: PME# supported from D3hot pci 0000:00:1f.2: PME# disabled pci 0000:00:1f.3: reg 10 64bit mmio: [0xe0726000-0xe07260ff] pci 0000:00:1f.3: reg 20 io port: [0x2000-0x201f] pci 0000:01:00.0: supports D1 D2 pci 0000:01:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force' pci 0000:00:01.0: bridge 32bit mmio: [0xe0500000-0xe05fffff] pci 0000:02:00.0: reg 10 32bit mmio: [0xe0501000-0xe0501fff] pci 0000:02:00.0: supports D1 D2 pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot pci 0000:02:00.0: PME# disabled pci 0000:02:00.1: reg 10 32bit mmio: [0xe0500000-0xe0500fff] pci 0000:02:00.1: supports D1 D2 pci 0000:02:00.1: PME# supported from D0 D1 D2 D3hot pci 0000:02:00.1: PME# disabled pci 0000:02:00.2: reg 10 32bit mmio: [0xe0502000-0xe05020ff] pci 0000:02:00.2: supports D1 D2 pci 0000:02:00.2: PME# supported from D0 D1 D2 D3hot pci 0000:02:00.2: PME# disabled pci 0000:01:00.0: bridge 32bit mmio: [0xe0500000-0xe05fffff] pci 0000:03:00.0: supports D1 D2 pci 0000:03:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force' pci 0000:00:1c.0: bridge 32bit mmio: [0xe0300000-0xe03fffff] pci 0000:04:00.0: reg 10 32bit mmio: [0xe0301000-0xe0301fff] pci 0000:04:00.0: supports D1 D2 pci 0000:04:00.0: PME# supported from D0 D1 D2 D3hot pci 0000:04:00.0: PME# disabled pci 0000:04:00.1: reg 10 32bit mmio: [0xe0300000-0xe0300fff] pci 0000:04:00.1: supports D1 D2 pci 0000:04:00.1: PME# supported from D0 D1 D2 D3hot pci 0000:04:00.1: PME# disabled pci 0000:04:00.2: reg 10 32bit mmio: [0xe0302000-0xe03020ff] pci 0000:04:00.2: supports D1 D2 pci 0000:04:00.2: PME# supported from D0 D1 D2 D3hot pci 0000:04:00.2: PME# disabled pci 0000:03:00.0: bridge 32bit mmio: [0xe0300000-0xe03fffff] pci 0000:05:00.0: supports D1 D2 pci 0000:05:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force' pci 0000:00:1c.1: bridge 32bit mmio: [0xe0200000-0xe02fffff] pci 0000:06:00.0: reg 10 32bit mmio: [0xe0201000-0xe0201fff] pci 0000:06:00.0: supports D1 D2 pci 0000:06:00.0: PME# supported from D0 D1 D2 D3hot pci 0000:06:00.0: PME# disabled pci 0000:06:00.1: reg 10 32bit mmio: [0xe0200000-0xe0200fff] pci 0000:06:00.1: supports D1 D2 pci 0000:06:00.1: PME# supported from D0 D1 D2 D3hot pci 0000:06:00.1: PME# disabled pci 0000:06:00.2: reg 10 32bit mmio: [0xe0202000-0xe02020ff] pci 0000:06:00.2: supports D1 D2 pci 0000:06:00.2: PME# supported from D0 D1 D2 D3hot pci 0000:06:00.2: PME# disabled pci 0000:05:00.0: bridge 32bit mmio: [0xe0200000-0xe02fffff] pci 0000:07:00.0: reg 10 io port: [0x1018-0x101f] pci 0000:07:00.0: reg 14 io port: [0x1024-0x1027] pci 0000:07:00.0: reg 18 io port: [0x1010-0x1017] pci 0000:07:00.0: reg 1c io port: [0x1020-0x1023] pci 0000:07:00.0: reg 20 io port: [0x1000-0x100f] pci 0000:07:00.0: reg 24 32bit mmio: [0xe0100000-0xe01001ff] pci 0000:07:00.0: supports D1 pci 0000:07:00.0: PME# supported from D0 D1 D3hot pci 0000:07:00.0: PME# disabled pci 0000:07:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force' pci 0000:00:1c.2: bridge io port: [0x1000-0x1fff] pci 0000:00:1c.2: bridge 32bit mmio: [0xe0100000-0xe01fffff] pci 0000:0a:00.0: reg 10 32bit mmio: [0xe0002000-0xe0002fff] pci 0000:0a:00.0: supports D1 D2 pci 0000:0a:00.0: PME# supported from D0 D1 D2 D3hot pci 0000:0a:00.0: PME# disabled pci 0000:0a:00.1: reg 10 32bit mmio: [0xe0001000-0xe0001fff] pci 0000:0a:00.1: supports D1 D2 pci 0000:0a:00.1: PME# supported from D0 D1 D2 D3hot pci 0000:0a:00.1: PME# disabled pci 0000:0a:00.2: reg 10 32bit mmio: [0xe0003000-0xe00030ff] pci 0000:0a:00.2: supports D1 D2 pci 0000:0a:00.2: PME# supported from D0 D1 D2 D3hot pci 0000:0a:00.2: PME# disabled pci 0000:0a:03.0: reg 10 32bit mmio: [0xe0000000-0xe0000fff] pci 0000:0a:03.0: supports D1 D2 pci 0000:0a:03.0: PME# supported from D0 D1 D2 D3hot pci 0000:0a:03.0: PME# disabled pci 0000:00:1e.0: transparent bridge pci 0000:00:1e.0: bridge 32bit mmio: [0xe0000000-0xe00fffff] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P32_._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX0._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX1._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX2._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX3._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX4._PRT] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 9 10 *11 12) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 *9 10 11 12) ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 9 *10 11 12) ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 9 10 *11 12) ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 9 10 *11 12) ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 *9 10 11 12) ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 7 9 *10 11 12) ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 7 9 10 *11 12) sync cpu 0 get result ffffffff max_id 0 Failed to sync pcpu 0 xenbus_probe_backend_init bus registered ok xen_balloon: Initialising balloon driver with page order 0. SCSI subsystem initialized libata version 3.00 loaded. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: Using ACPI for IRQ routing IO APIC resources couldn't be allocated. NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default DMA-API: preallocated 32768 debug entries DMA-API: debugging enabled by kernel config Switched to high resolution mode on CPU 0 pnp: PnP ACPI init ACPI: bus type pnp registered xen: registering gsi 8 triggering 1 polarity 0 xen_allocate_pirq: returning irq 8 for gsi 8 xen: --> irq=8 xen_set_ioapic_routing: irq 8 gsi 8 vector 80 ioapic 0 pin 8 triggering 0 polarity 0 xen: registering gsi 13 triggering 1 polarity 0 xen_allocate_pirq: returning irq 13 for gsi 13 xen: --> irq=13 xen_set_ioapic_routing: irq 13 gsi 13 vector 120 ioapic 0 pin 13 triggering 0 polarity 0 xen: registering gsi 4 triggering 1 polarity 0 xen_allocate_pirq: returning irq 4 for gsi 4 xen: --> irq=4 xen_set_ioapic_routing: irq 4 gsi 4 vector 48 ioapic 0 pin 4 triggering 0 polarity 0 pnp: PnP ACPI: found 11 devices ACPI: ACPI bus type pnp unregistered system 00:01: iomem range 0xf0000000-0xf7ffffff has been reserved system 00:01: iomem range 0xfeb00000-0xfeb03fff has been reserved system 00:01: iomem range 0xfed13000-0xfed13fff has been reserved system 00:01: iomem range 0xfed14000-0xfed17fff has been reserved system 00:01: iomem range 0xfed18000-0xfed18fff has been reserved system 00:01: iomem range 0xfed19000-0xfed19fff has been reserved system 00:01: iomem range 0xfed1c000-0xfed1ffff has been reserved system 00:01: iomem range 0xfed20000-0xfed3ffff has been reserved system 00:01: iomem range 0xfed45000-0xfed99fff has been reserved system 00:01: iomem range 0xc0000-0xdffff could not be reserved system 00:01: iomem range 0xe0000-0xfffff could not be reserved system 00:01: iomem range 0xffc00000-0xffffffff has been reserved system 00:06: ioport range 0x500-0x53f has been reserved system 00:06: ioport range 0x400-0x47f has been reserved system 00:06: ioport range 0x680-0x6ff has been reserved work_for_cpu used greatest stack depth: 6624 bytes left work_for_cpu used greatest stack depth: 6416 bytes left pciback 0000:02:00.0: seizing device work_for_cpu used greatest stack depth: 6376 bytes left pciback 0000:02:00.1: seizing device pciback 0000:02:00.2: seizing device pciback 0000:04:00.0: seizing device pciback 0000:04:00.1: seizing device pciback 0000:04:00.2: seizing device pciback 0000:06:00.0: seizing device pciback 0000:06:00.1: seizing device pciback 0000:06:00.2: seizing device pciback 0000:0a:00.0: seizing device pciback 0000:0a:00.1: seizing device pciback 0000:0a:00.2: seizing device pciback 0000:0a:03.0: seizing device pci 0000:01:00.0: PCI bridge, secondary bus 0000:02 pci 0000:01:00.0: IO window: disabled pci 0000:01:00.0: MEM window: 0xe0500000-0xe05fffff pci 0000:01:00.0: PREFETCH window: disabled pci 0000:00:01.0: PCI bridge, secondary bus 0000:01 pci 0000:00:01.0: IO window: disabled pci 0000:00:01.0: MEM window: 0xe0500000-0xe05fffff pci 0000:00:01.0: PREFETCH window: disabled pci 0000:03:00.0: PCI bridge, secondary bus 0000:04 pci 0000:03:00.0: IO window: disabled pci 0000:03:00.0: MEM window: 0xe0300000-0xe03fffff pci 0000:03:00.0: PREFETCH window: disabled pci 0000:00:1c.0: PCI bridge, secondary bus 0000:03 pci 0000:00:1c.0: IO window: disabled pci 0000:00:1c.0: MEM window: 0xe0300000-0xe03fffff pci 0000:00:1c.0: PREFETCH window: disabled pci 0000:05:00.0: PCI bridge, secondary bus 0000:06 pci 0000:05:00.0: IO window: disabled pci 0000:05:00.0: MEM window: 0xe0200000-0xe02fffff pci 0000:05:00.0: PREFETCH window: disabled pci 0000:00:1c.1: PCI bridge, secondary bus 0000:05 pci 0000:00:1c.1: IO window: disabled pci 0000:00:1c.1: MEM window: 0xe0200000-0xe02fffff pci 0000:00:1c.1: PREFETCH window: disabled pci 0000:00:1c.2: PCI bridge, secondary bus 0000:07 pci 0000:00:1c.2: IO window: 0x1000-0x1fff pci 0000:00:1c.2: MEM window: 0xe0100000-0xe01fffff pci 0000:00:1c.2: PREFETCH window: disabled pci 0000:00:1c.3: PCI bridge, secondary bus 0000:08 pci 0000:00:1c.3: IO window: disabled pci 0000:00:1c.3: MEM window: disabled pci 0000:00:1c.3: PREFETCH window: disabled pci 0000:00:1c.4: PCI bridge, secondary bus 0000:09 pci 0000:00:1c.4: IO window: disabled pci 0000:00:1c.4: MEM window: disabled pci 0000:00:1c.4: PREFETCH window: disabled pci 0000:00:1e.0: PCI bridge, secondary bus 0000:0a pci 0000:00:1e.0: IO window: disabled pci 0000:00:1e.0: MEM window: 0xe0000000-0xe00fffff pci 0000:00:1e.0: PREFETCH window: disabled xen: registering gsi 16 triggering 0 polarity 1 alloc irq_desc for 16 on node 0 alloc kstat_irqs on node 0 xen: --> irq=16 xen_set_ioapic_routing: irq 16 gsi 16 vector 184 ioapic 0 pin 16 triggering 1 polarity 1 pci 0000:00:01.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 pci 0000:00:01.0: setting latency timer to 64 pci 0000:01:00.0: setting latency timer to 64 xen: registering gsi 17 triggering 0 polarity 1 alloc irq_desc for 17 on node 0 alloc kstat_irqs on node 0 xen: --> irq=17 xen_set_ioapic_routing: irq 17 gsi 17 vector 192 ioapic 0 pin 17 triggering 1 polarity 1 pci 0000:00:1c.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 pci 0000:00:1c.0: setting latency timer to 64 pci 0000:03:00.0: setting latency timer to 64 xen: registering gsi 20 triggering 0 polarity 1 alloc irq_desc for 20 on node 0 alloc kstat_irqs on node 0 xen: --> irq=20 xen_set_ioapic_routing: irq 20 gsi 20 vector 200 ioapic 0 pin 20 triggering 1 polarity 1 pci 0000:00:1c.1: PCI INT B -> GSI 20 (level, low) -> IRQ 20 pci 0000:00:1c.1: setting latency timer to 64 pci 0000:05:00.0: setting latency timer to 64 xen: registering gsi 18 triggering 0 polarity 1 alloc irq_desc for 18 on node 0 alloc kstat_irqs on node 0 xen: --> irq=18 xen_set_ioapic_routing: irq 18 gsi 18 vector 208 ioapic 0 pin 18 triggering 1 polarity 1 pci 0000:00:1c.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18 pci 0000:00:1c.2: setting latency timer to 64 xen: registering gsi 19 triggering 0 polarity 1 alloc irq_desc for 19 on node 0 alloc kstat_irqs on node 0 xen: --> irq=19 xen_set_ioapic_routing: irq 19 gsi 19 vector 216 ioapic 0 pin 19 triggering 1 polarity 1 pci 0000:00:1c.3: PCI INT D -> GSI 19 (level, low) -> IRQ 19 pci 0000:00:1c.3: setting latency timer to 64 xen: registering gsi 17 triggering 0 polarity 1 xen_allocate_pirq: returning irq 17 for gsi 17 xen: --> irq=17 xen_set_ioapic_routing: irq 17 gsi 17 vector 192 ioapic 0 pin 17 triggering 1 polarity 1 pci 0000:00:1c.4: PCI INT A -> GSI 17 (level, low) -> IRQ 17 pci 0000:00:1c.4: setting latency timer to 64 pci 0000:00:1e.0: setting latency timer to 64 pci_bus 0000:00: resource 0 io: [0x00-0xffff] pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffffffffffff] pci_bus 0000:01: resource 1 mem: [0xe0500000-0xe05fffff] pci_bus 0000:02: resource 1 mem: [0xe0500000-0xe05fffff] pci_bus 0000:03: resource 1 mem: [0xe0300000-0xe03fffff] pci_bus 0000:04: resource 1 mem: [0xe0300000-0xe03fffff] pci_bus 0000:05: resource 1 mem: [0xe0200000-0xe02fffff] pci_bus 0000:06: resource 1 mem: [0xe0200000-0xe02fffff] pci_bus 0000:07: resource 0 io: [0x1000-0x1fff] pci_bus 0000:07: resource 1 mem: [0xe0100000-0xe01fffff] pci_bus 0000:0a: resource 1 mem: [0xe0000000-0xe00fffff] pci_bus 0000:0a: resource 3 io: [0x00-0xffff] pci_bus 0000:0a: resource 4 mem: [0x000000-0xffffffffffffffff] NET: Registered protocol family 2 IP route cache hash table entries: 32768 (order: 6, 262144 bytes) TCP established hash table entries: 131072 (order: 9, 2097152 bytes) TCP bind hash table entries: 65536 (order: 10, 4718592 bytes) TCP: Hash tables configured (established 131072 bind 65536) TCP reno registered NET: Registered protocol family 1 Trying to unpack rootfs image as initramfs... Freeing initrd memory: 211314k freed audit: initializing netlink socket (disabled) type=2000 audit(1273579720.766:1): initialized HugeTLB registered 2 MB page size, pre-allocated 0 pages VFS: Disk quotas dquot_6.5.2 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) msgmni has been set to 1312 SELinux: Registering netfilter hooks cryptomgr_test used greatest stack depth: 5480 bytes left alg: No test for stdrng (krng) Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci 0000:00:02.0: Boot video device alloc irq_desc for 249 on node 0 alloc kstat_irqs on node 0 pcieport-driver 0000:00:01.0: setting latency timer to 64 alloc irq_desc for 248 on node 0 alloc kstat_irqs on node 0 pcieport-driver 0000:00:1c.0: setting latency timer to 64 alloc irq_desc for 247 on node 0 alloc kstat_irqs on node 0 pcieport-driver 0000:00:1c.1: setting latency timer to 64 alloc irq_desc for 246 on node 0 alloc kstat_irqs on node 0 pcieport-driver 0000:00:1c.2: setting latency timer to 64 alloc irq_desc for 245 on node 0 alloc kstat_irqs on node 0 pcieport-driver 0000:00:1c.3: setting latency timer to 64 alloc irq_desc for 244 on node 0 alloc kstat_irqs on node 0 pcieport-driver 0000:00:1c.4: setting latency timer to 64 pci_hotplug: PCI Hot Plug PCI Core version: 0.5 pciehp: PCI Express Hot Plug Controller Driver version: 0.4 acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 acpiphp_glue: can't get bus number, assuming 0 input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0 ACPI: Power Button [PWRF] input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input1 ACPI: Sleep Button [SLPB] ACPI: Invalid PBLK length [0] ACPI: Invalid PBLK length [0] ACPI: Invalid PBLK length [0] ACPI: Invalid PBLK length [0] Event-channel device installed. registering netback xen: registering gsi 19 triggering 0 polarity 1 xen_allocate_pirq: returning irq 19 for gsi 19 xen: --> irq=19 xen_set_ioapic_routing: irq 19 gsi 19 vector 216 ioapic 0 pin 19 triggering 1 polarity 1 pciback 0000:0a:03.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 pciback 0000:0a:03.0: PCI INT A disabled xen: registering gsi 23 triggering 0 polarity 1 alloc irq_desc for 23 on node 0 alloc kstat_irqs on node 0 xen: --> irq=23 xen_set_ioapic_routing: irq 23 gsi 23 vector 81 ioapic 0 pin 23 triggering 1 polarity 1 pciback 0000:0a:00.2: PCI INT C -> GSI 23 (level, low) -> IRQ 23 pciback 0000:0a:00.2: PCI INT C disabled xen: registering gsi 22 triggering 0 polarity 1 alloc irq_desc for 22 on node 0 alloc kstat_irqs on node 0 xen: --> irq=22 xen_set_ioapic_routing: irq 22 gsi 22 vector 89 ioapic 0 pin 22 triggering 1 polarity 1 pciback 0000:0a:00.1: PCI INT B -> GSI 22 (level, low) -> IRQ 22 pciback 0000:0a:00.1: PCI INT B disabled xen: registering gsi 21 triggering 0 polarity 1 alloc irq_desc for 21 on node 0 alloc kstat_irqs on node 0 xen: --> irq=21 xen_set_ioapic_routing: irq 21 gsi 21 vector 97 ioapic 0 pin 21 triggering 1 polarity 1 pciback 0000:0a:00.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21 pciback 0000:0a:00.0: PCI INT A disabled xen: registering gsi 19 triggering 0 polarity 1 xen_allocate_pirq: returning irq 19 for gsi 19 xen: --> irq=19 xen_set_ioapic_routing: irq 19 gsi 19 vector 216 ioapic 0 pin 19 triggering 1 polarity 1 pciback 0000:06:00.2: PCI INT C -> GSI 19 (level, low) -> IRQ 19 pciback 0000:06:00.2: PCI INT C disabled xen: registering gsi 18 triggering 0 polarity 1 xen_allocate_pirq: returning irq 18 for gsi 18 xen: --> irq=18 xen_set_ioapic_routing: irq 18 gsi 18 vector 208 ioapic 0 pin 18 triggering 1 polarity 1 pciback 0000:06:00.1: PCI INT B -> GSI 18 (level, low) -> IRQ 18 pciback 0000:06:00.1: PCI INT B disabled xen: registering gsi 17 triggering 0 polarity 1 xen_allocate_pirq: returning irq 17 for gsi 17 xen: --> irq=17 xen_set_ioapic_routing: irq 17 gsi 17 vector 192 ioapic 0 pin 17 triggering 1 polarity 1 pciback 0000:06:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 pciback 0000:06:00.0: PCI INT A disabled xen: registering gsi 18 triggering 0 polarity 1 xen_allocate_pirq: returning irq 18 for gsi 18 xen: --> irq=18 xen_set_ioapic_routing: irq 18 gsi 18 vector 208 ioapic 0 pin 18 triggering 1 polarity 1 pciback 0000:04:00.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18 pciback 0000:04:00.2: PCI INT C disabled xen: registering gsi 17 triggering 0 polarity 1 xen_allocate_pirq: returning irq 17 for gsi 17 xen: --> irq=17 xen_set_ioapic_routing: irq 17 gsi 17 vector 192 ioapic 0 pin 17 triggering 1 polarity 1 pciback 0000:04:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17 pciback 0000:04:00.1: PCI INT B disabled xen: registering gsi 16 triggering 0 polarity 1 xen_allocate_pirq: returning irq 16 for gsi 16 xen: --> irq=16 xen_set_ioapic_routing: irq 16 gsi 16 vector 184 ioapic 0 pin 16 triggering 1 polarity 1 pciback 0000:04:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 pciback 0000:04:00.0: PCI INT A disabled xen: registering gsi 18 triggering 0 polarity 1 xen_allocate_pirq: returning irq 18 for gsi 18 xen: --> irq=18 xen_set_ioapic_routing: irq 18 gsi 18 vector 208 ioapic 0 pin 18 triggering 1 polarity 1 pciback 0000:02:00.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18 pciback 0000:02:00.2: PCI INT C disabled xen: registering gsi 17 triggering 0 polarity 1 xen_allocate_pirq: returning irq 17 for gsi 17 xen: --> irq=17 xen_set_ioapic_routing: irq 17 gsi 17 vector 192 ioapic 0 pin 17 triggering 1 polarity 1 pciback 0000:02:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17 pciback 0000:02:00.1: PCI INT B disabled xen: registering gsi 16 triggering 0 polarity 1 xen_allocate_pirq: returning irq 16 for gsi 16 xen: --> irq=16 xen_set_ioapic_routing: irq 16 gsi 16 vector 184 ioapic 0 pin 16 triggering 1 polarity 1 pciback 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 pciback 0000:02:00.0: PCI INT A disabled alloc irq_desc for 243 on node 0 alloc kstat_irqs on node 0 alloc irq_desc for 242 on node 0 alloc kstat_irqs on node 0 Non-volatile memory driver v1.3 Linux agpgart interface v0.103 agpgart-intel 0000:00:00.0: Intel Q35 Chipset agpgart-intel 0000:00:00.0: detected 6140K stolen memory agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xd0000000 tpm_tis 00:07: 1.2 TPM (device-id 0xFE, rev-id 70) Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A 00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A brd: module loaded loop: module loaded input: Macintosh mouse button emulation as /devices/virtual/input/input2 ahci 0000:00:1f.2: version 3.0 xen: registering gsi 21 triggering 0 polarity 1 xen_allocate_pirq: returning irq 21 for gsi 21 xen: --> irq=21 xen_set_ioapic_routing: irq 21 gsi 21 vector 97 ioapic 0 pin 21 triggering 1 polarity 1 ahci 0000:00:1f.2: PCI INT A -> GSI 21 (level, low) -> IRQ 21 alloc irq_desc for 241 on node 0 alloc kstat_irqs on node 0 ahci 0000:00:1f.2: AHCI 0001.0200 32 slots 6 ports 3 Gbps 0x3f impl SATA mode ahci 0000:00:1f.2: flags: 64bit ncq sntf pm led clo pmp pio slum part ems ahci 0000:00:1f.2: setting latency timer to 64 scsi0 : ahci scsi1 : ahci scsi2 : ahci scsi3 : ahci scsi4 : ahci scsi5 : ahci ata1: SATA max UDMA/133 irq_stat 0x00400040, connection status changed irq 241 ata2: SATA max UDMA/133 irq_stat 0x00400040, connection status changed irq 241 ata3: SATA max UDMA/133 irq_stat 0x00400040, connection status changed irq 241 ata4: SATA max UDMA/133 abar m2048@0xe0725000 port 0xe0725280 irq 241 ata5: SATA max UDMA/133 abar m2048@0xe0725000 port 0xe0725300 irq 241 ata6: SATA max UDMA/133 abar m2048@0xe0725000 port 0xe0725380 irq 241 work_for_cpu used greatest stack depth: 4992 bytes left Fixed MDIO Bus: probed ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver xen: registering gsi 17 triggering 0 polarity 1 xen_allocate_pirq: returning irq 17 for gsi 17 xen: --> irq=17 xen_set_ioapic_routing: irq 17 gsi 17 vector 192 ioapic 0 pin 17 triggering 1 polarity 1 ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 17 (level, low) -> IRQ 17 ehci_hcd 0000:00:1a.7: setting latency timer to 64 ehci_hcd 0000:00:1a.7: EHCI Host Controller ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1 ehci_hcd 0000:00:1a.7: debug port 1 ehci_hcd 0000:00:1a.7: cache line size of 32 is not supported ehci_hcd 0000:00:1a.7: irq 17, io mem 0xe0725c00 ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00 usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb1: Product: EHCI Host Controller usb usb1: Manufacturer: Linux 2.6.31.6 ehci_hcd usb usb1: SerialNumber: 0000:00:1a.7 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 6 ports detected work_for_cpu used greatest stack depth: 3936 bytes left xen: registering gsi 23 triggering 0 polarity 1 xen_allocate_pirq: returning irq 23 for gsi 23 xen: --> irq=23 xen_set_ioapic_routing: irq 23 gsi 23 vector 81 ioapic 0 pin 23 triggering 1 polarity 1 ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23 ehci_hcd 0000:00:1d.7: setting latency timer to 64 ehci_hcd 0000:00:1d.7: EHCI Host Controller ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2 ehci_hcd 0000:00:1d.7: debug port 1 ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported ehci_hcd 0000:00:1d.7: irq 23, io mem 0xe0725800 ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00 usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb2: Product: EHCI Host Controller usb usb2: Manufacturer: Linux 2.6.31.6 ehci_hcd usb usb2: SerialNumber: 0000:00:1d.7 usb usb2: configuration #1 chosen from 1 choice hub 2-0:1.0: USB hub found hub 2-0:1.0: 6 ports detected ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver uhci_hcd: USB Universal Host Controller Interface driver xen: registering gsi 18 triggering 0 polarity 1 xen_allocate_pirq: returning irq 18 for gsi 18 xen: --> irq=18 xen_set_ioapic_routing: irq 18 gsi 18 vector 208 ioapic 0 pin 18 triggering 1 polarity 1 uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 uhci_hcd 0000:00:1a.0: setting latency timer to 64 uhci_hcd 0000:00:1a.0: UHCI Host Controller uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3 uhci_hcd 0000:00:1a.0: irq 18, io base 0x000020e0 usb usb3: New USB device found, idVendor=1d6b, idProduct=0001 usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb3: Product: UHCI Host Controller usb usb3: Manufacturer: Linux 2.6.31.6 uhci_hcd usb usb3: SerialNumber: 0000:00:1a.0 usb usb3: configuration #1 chosen from 1 choice hub 3-0:1.0: USB hub found hub 3-0:1.0: 2 ports detected xen: registering gsi 21 triggering 0 polarity 1 xen_allocate_pirq: returning irq 21 for gsi 21 xen: --> irq=21 xen_set_ioapic_routing: irq 21 gsi 21 vector 97 ioapic 0 pin 21 triggering 1 polarity 1 uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21 uhci_hcd 0000:00:1a.1: setting latency timer to 64 uhci_hcd 0000:00:1a.1: UHCI Host Controller uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4 uhci_hcd 0000:00:1a.1: irq 21, io base 0x000020c0 usb usb4: New USB device found, idVendor=1d6b, idProduct=0001 usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb4: Product: UHCI Host Controller usb usb4: Manufacturer: Linux 2.6.31.6 uhci_hcd usb usb4: SerialNumber: 0000:00:1a.1 usb usb4: configuration #1 chosen from 1 choice hub 4-0:1.0: USB hub found hub 4-0:1.0: 2 ports detected xen: registering gsi 17 triggering 0 polarity 1 xen_allocate_pirq: returning irq 17 for gsi 17 xen: --> irq=17 xen_set_ioapic_routing: irq 17 gsi 17 vector 192 ioapic 0 pin 17 triggering 1 polarity 1 uhci_hcd 0000:00:1a.2: PCI INT C -> GSI 17 (level, low) -> IRQ 17 uhci_hcd 0000:00:1a.2: setting latency timer to 64 uhci_hcd 0000:00:1a.2: UHCI Host Controller uhci_hcd 0000:00:1a.2: new USB bus registered, assigned bus number 5 uhci_hcd 0000:00:1a.2: irq 17, io base 0x000020a0 usb usb5: New USB device found, idVendor=1d6b, idProduct=0001 usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb5: Product: UHCI Host Controller usb usb5: Manufacturer: Linux 2.6.31.6 uhci_hcd usb usb5: SerialNumber: 0000:00:1a.2 usb usb5: configuration #1 chosen from 1 choice hub 5-0:1.0: USB hub found hub 5-0:1.0: 2 ports detected xen: registering gsi 23 triggering 0 polarity 1 xen_allocate_pirq: returning irq 23 for gsi 23 xen: --> irq=23 xen_set_ioapic_routing: irq 23 gsi 23 vector 81 ioapic 0 pin 23 triggering 1 polarity 1 uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23 uhci_hcd 0000:00:1d.0: setting latency timer to 64 uhci_hcd 0000:00:1d.0: UHCI Host Controller uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 6 uhci_hcd 0000:00:1d.0: irq 23, io base 0x00002080 usb usb6: New USB device found, idVendor=1d6b, idProduct=0001 usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb6: Product: UHCI Host Controller usb usb6: Manufacturer: Linux 2.6.31.6 uhci_hcd usb usb6: SerialNumber: 0000:00:1d.0 usb usb6: configuration #1 chosen from 1 choice hub 6-0:1.0: USB hub found hub 6-0:1.0: 2 ports detected xen: registering gsi 19 triggering 0 polarity 1 xen_allocate_pirq: returning irq 19 for gsi 19 xen: --> irq=19 xen_set_ioapic_routing: irq 19 gsi 19 vector 216 ioapic 0 pin 19 triggering 1 polarity 1 uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19 uhci_hcd 0000:00:1d.1: setting latency timer to 64 uhci_hcd 0000:00:1d.1: UHCI Host Controller uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 7 uhci_hcd 0000:00:1d.1: irq 19, io base 0x00002060 usb usb7: New USB device found, idVendor=1d6b, idProduct=0001 usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb7: Product: UHCI Host Controller usb usb7: Manufacturer: Linux 2.6.31.6 uhci_hcd usb usb7: SerialNumber: 0000:00:1d.1 usb usb7: configuration #1 chosen from 1 choice hub 7-0:1.0: USB hub found hub 7-0:1.0: 2 ports detected xen: registering gsi 18 triggering 0 polarity 1 xen_allocate_pirq: returning irq 18 for gsi 18 xen: --> irq=18 xen_set_ioapic_routing: irq 18 gsi 18 vector 208 ioapic 0 pin 18 triggering 1 polarity 1 uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18 uhci_hcd 0000:00:1d.2: setting latency timer to 64 uhci_hcd 0000:00:1d.2: UHCI Host Controller uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 8 uhci_hcd 0000:00:1d.2: irq 18, io base 0x00002040 usb usb8: New USB device found, idVendor=1d6b, idProduct=0001 usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb8: Product: UHCI Host Controller usb usb8: Manufacturer: Linux 2.6.31.6 uhci_hcd usb usb8: SerialNumber: 0000:00:1d.2 usb usb8: configuration #1 chosen from 1 choice hub 8-0:1.0: USB hub found hub 8-0:1.0: 2 ports detected PNP: No PS/2 controller found. Probing ports directly. serio: i8042 KBD port at 0x60,0x64 irq 1 serio: i8042 AUX port at 0x60,0x64 irq 12 mice: PS/2 mouse device common for all mice rtc_cmos 00:03: RTC can wake from S4 rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0 rtc0: alarms up to one month, 114 bytes nvram device-mapper: uevent: version 1.0.3 device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com cpuidle: using governor ladder cpuidle: using governor menu usbcore: registered new interface driver hiddev usbcore: registered new interface driver usbhid usbhid: v2.6:USB HID core driver nf_conntrack version 0.5.0 (6144 buckets, 24576 max) CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or sysctl net.netfilter.nf_conntrack_acct=1 to enable it. ip_tables: (C) 2000-2006 Netfilter Core Team TCP cubic registered Initializing XFRM netlink socket NET: Registered protocol family 17 PM: Resume from disk failed. registered taskstats version 1 No TPM chip found, activating TPM-bypass! Magic number: 10:156:127 acpi device:02: hash matches rtc_cmos 00:03: setting system clock to 2010-05-11 12:08:40 UTC (1273579720) Initalizing network drop monitor service ata6: SATA link down (SStatus 0 SControl 300) ata5: SATA link down (SStatus 0 SControl 300) ata4: SATA link down (SStatus 0 SControl 300) ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata3.00: ATAPI: TSSTcorp CDDVDW SH-S223C, SB00, max UDMA/100 ata3.00: configured for UDMA/100 ata1.00: ATA-8: WDC WD2500AAJS-52B4A0, 01.03A01, max UDMA/133 ata1.00: 488397168 sectors, multi 0: LBA48 NCQ (depth 31/32) ata1.00: configured for UDMA/133 ata2.00: HPA detected: current 488395055, native 488397168 ata2.00: ATA-8: WDC WD2500AAJS-52B4A0, 01.03A01, max UDMA/133 ata2.00: 488395055 sectors, multi 0: LBA48 NCQ (depth 31/32) ata2.00: configured for UDMA/133 scsi 0:0:0:0: Direct-Access ATA WDC WD2500AAJS-5 01.0 PQ: 0 ANSI: 5 sd 0:0:0:0: Attached scsi generic sg0 type 0 scsi 1:0:0:0: Direct-Access ATA WDC WD2500AAJS-5 01.0 PQ: 0 ANSI: 5 sd 1:0:0:0: Attached scsi generic sg1 type 0 sd 1:0:0:0: [sdb] 488395055 512-byte logical blocks: (250 GB/232 GiB) sd 1:0:0:0: [sdb] Write Protect is off sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sdb: sd 0:0:0:0: [sda] 488397168 512-byte logical blocks: (250 GB/232 GiB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sda: sdb1 sdb2 sdb3 sd 1:0:0:0: [sdb] Attached SCSI disk scsi 2:0:0:0: CD-ROM TSSTcorp CDDVDW SH-S223C SB00 PQ: 0 ANSI: 5 sda1 sda2 sda3 sd 0:0:0:0: [sda] Attached SCSI disk sr0: scsi3-mmc drive: 52x/52x writer dvd-ram cd/rw xa/form2 cdda tray Uniform CD-ROM driver Revision: 3.20 sr 2:0:0:0: Attached scsi CD-ROM sr0 sr 2:0:0:0: Attached scsi generic sg2 type 5 Freeing unused kernel memory: 3208k freed Write protecting the kernel read-only data: 7480k e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2 e1000e: Copyright (c) 1999-2008 Intel Corporation. xen: registering gsi 20 triggering 0 polarity 1 xen_allocate_pirq: returning irq 20 for gsi 20 xen: --> irq=20 xen_set_ioapic_routing: irq 20 gsi 20 vector 200 ioapic 0 pin 20 triggering 1 polarity 1 e1000e 0000:00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20 e1000e 0000:00:19.0: pci_enable_pcie_error_reporting failed 0xfffffffb e1000e 0000:00:19.0: setting latency timer to 64 alloc irq_desc for 240 on node 0 alloc kstat_irqs on node 0 xen: registering gsi 18 triggering 0 polarity 1 xen_allocate_pirq: returning irq 18 for gsi 18 xen: --> irq=18 xen_set_ioapic_routing: irq 18 gsi 18 vector 208 ioapic 0 pin 18 triggering 1 polarity 1 pata_acpi 0000:07:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 pata_acpi 0000:07:00.0: setting latency timer to 64 pata_acpi 0000:07:00.0: PCI INT A disabled xen: registering gsi 18 triggering 0 polarity 1 xen_allocate_pirq: returning irq 18 for gsi 18 xen: --> irq=18 xen_set_ioapic_routing: irq 18 gsi 18 vector 208 ioapic 0 pin 18 triggering 1 polarity 1 pata_marvell 0000:07:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 pata_marvell 0000:07:00.0: setting latency timer to 64 scsi6 : pata_marvell scsi7 : pata_marvell ata7: PATA max UDMA/100 cmd 0x1018 ctl 0x1024 bmdma 0x1000 irq 18 ata8: DUMMY 0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1) 00:1c:c0:cb:ba:89 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection 0000:00:19.0: eth0: MAC: 7, PHY: 6, PBA No: ffffff-0ff cdrom_id used greatest stack depth: 3896 bytes left md: raid0 personality registered for level 0 md: raid1 personality registered for level 1 md: md0 stopped. md: bind<sdb1> md: bind<sda1> raid1: raid set md0 active with 2 out of 2 mirrors md0: detected capacity change from 0 to 15998058496 md: md1 stopped. md0: unknown partition table md: bind<sdb2> md: bind<sda2> raid0: looking at sda2 raid0: comparing sda2(3903616) with sda2(3903616) raid0: END raid0: ==> UNIQUE raid0: 1 zones raid0: looking at sdb2 raid0: comparing sdb2(3903616) with sda2(3903616) raid0: EQUAL raid0: FINAL 1 zones raid0: done. raid0 : md_size is 7807232 sectors. ******* md1 configuration ********* zone0=[sda2/sdb2/] zone offset=0kb device offset=0kb size=3903616kb ********************************** md1: detected capacity change from 0 to 3997302784 md: md2 stopped. md1: unknown partition table md: bind<sdb3> md: bind<sda3> raid1: raid set md2 active with 2 out of 2 mirrors md2: detected capacity change from 0 to 232059699200 md2: unknown partition table PM: Starting manual resume from disk PM: Resume from partition 9:1 PM: Checking hibernation image. PM: Resume from disk failed. EXT3-fs: INFO: recovery required on readonly filesystem. EXT3-fs: write access will be enabled during recovery. kjournald starting. Commit interval 5 seconds EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. exe used greatest stack depth: 3760 bytes left stty used greatest stack depth: 3184 bytes left udevd version 125 started shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 xen: registering gsi 22 triggering 0 polarity 1 xen_allocate_pirq: returning irq 22 for gsi 22 xen: --> irq=22 xen_set_ioapic_routing: irq 22 gsi 22 vector 89 ioapic 0 pin 22 triggering 1 polarity 1 HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22 HDA Intel 0000:00:1b.0: setting latency timer to 64 hda_codec: Unknown model for ALC268, trying auto-probe from BIOS... ALSA sound/pci/hda/hda_codec.c:3857: autoconfig: line_outs=1 (0x14/0x0/0x0/0x0/0x0) ALSA sound/pci/hda/hda_codec.c:3861: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) ALSA sound/pci/hda/hda_codec.c:3865: hp_outs=1 (0x15/0x0/0x0/0x0/0x0) ALSA sound/pci/hda/hda_codec.c:3866: mono: mono_out=0x0 ALSA sound/pci/hda/hda_codec.c:3877: inputs: mic=0x18, fmic=0x1a, line=0x19, fline=0x0, cd=0x0, aux=0x0 ALSA sound/pci/hda/patch_realtek.c:1181: realtek: No valid SSID, checking pincfg 0x411111f0 for NID 0x1d ALSA sound/pci/hda/patch_realtek.c:1255: realtek: Enable default setup for auto mode as fallback input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input3 input: PC Speaker as /devices/platform/pcspkr/input/input4 xen: registering gsi 18 triggering 0 polarity 1 xen_allocate_pirq: returning irq 18 for gsi 18 xen: --> irq=18 xen_set_ioapic_routing: irq 18 gsi 18 vector 208 ioapic 0 pin 18 triggering 1 polarity 1 i801_smbus 0000:00:1f.3: PCI INT B -> GSI 18 (level, low) -> IRQ 18 Error: Driver 'pcspkr' is already registered, aborting... Adding 3903608k swap on /dev/md1. Priority:-1 extents:1 across:3903608k EXT3 FS on md0, internal journal rc used greatest stack depth: 2896 bytes left NET: Registered protocol family 10 lo: Disabled Privacy Extensions ADDRCONF(NETDEV_UP): eth0: link is not ready e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Bridge firewalling registered ADDRCONF(NETDEV_UP): peth0: link is not ready e1000e: peth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX ADDRCONF(NETDEV_CHANGE): peth0: link becomes ready device peth0 entered promiscuous mode eth0: port 1(peth0) entering forwarding state alloc irq_desc for 239 on node 0 alloc kstat_irqs on node 0 xenbus_probe wake_waiting xenbus_probe wake_waiting alloc irq_desc for 238 on node 0 alloc kstat_irqs on node 0 XENBUS: Unable to read cpu state xenbus_probe_devices backend xenbus_probe_devices failed xenbus_directory backend_probe_and_watch devices probed ok backend_probe_and_watch watch add ok ok backend_probe_and_watch all done alloc irq_desc for 237 on node 0 alloc kstat_irqs on node 0 02:00.0 USB Controller: NEC Corporation USB (rev 43) (prog-if 10 [OHCI]) Subsystem: NEC Corporation Hama USB 2.0 CardBus Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 32 (250ns min, 10500ns max), Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 16 Region 0: Memory at e0501000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: pciback 02:00.1 USB Controller: NEC Corporation USB (rev 43) (prog-if 10 [OHCI]) Subsystem: NEC Corporation Hama USB 2.0 CardBus Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 32 (250ns min, 10500ns max), Cache Line Size: 64 bytes Interrupt: pin B routed to IRQ 17 Region 0: Memory at e0500000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: pciback 02:00.2 USB Controller: NEC Corporation USB 2.0 (rev 04) (prog-if 20 [EHCI]) Subsystem: NEC Corporation USB 2.0 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 32 (4000ns min, 8500ns max), Cache Line Size: 64 bytes Interrupt: pin C routed to IRQ 18 Region 0: Memory at e0502000 (32-bit, non-prefetchable) [size=256] Capabilities: [40] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: pciback [-- Attachment #3: NOTWORKING.txt --] [-- Type: text/plain, Size: 90941 bytes --] scanmaster2:~# uname -a Linux scanmaster2 2.6.32.12 #1 SMP Fri May 14 13:40:05 EDT 2010 x86_64 GNU/Linux scanmaster2:~# xm info host : scanmaster2 release : 2.6.32.12 version : #1 SMP Fri May 14 13:40:05 EDT 2010 machine : x86_64 nr_cpus : 8 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 2 cpu_mhz : 2800 hw_caps : bfebfbff:28100800:00000000:00001b40:0098e3bd:00000000:00000001:00000000 virt_caps : hvm hvm_directio total_memory : 7932 free_memory : 6023 node_to_cpu : node0:0-7 node_to_memory : node0:6023 node_to_dma32_mem : node0:3249 max_node_id : 0 xen_major : 4 xen_minor : 0 xen_extra : .0 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable xen_commandline : iommu=verbose dom0_mem=2048M cc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1) cc_compile_by : root cc_compile_domain : cc_compile_date : Thu May 6 13:41:25 EDT 2010 xend_config_format : 4 __ __ _ _ ___ ___ \ \/ /___ _ __ | || | / _ \ / _ \ \ // _ \ \047_ \ | || |_| | | | | | | / \ __/ | | | |__ _| |_| | |_| | /_/\_\___|_| |_| |_|(_)___(_)___/ (XEN) Xen version 4.0.0 (root@) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) Thu May 6 13:41:25 EDT 2010 (XEN) Latest ChangeSet: unavailable (XEN) Command line: iommu=verbose dom0_mem=2048M (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 - 000000000008f000 (usable) (XEN) 000000000008f000 - 0000000000090000 (reserved) (XEN) 0000000000090000 - 000000000009ec00 (usable) (XEN) 000000000009ec00 - 00000000000a0000 (reserved) (XEN) 00000000000e0000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 00000000cf4bd000 (usable) (XEN) 00000000cf4bd000 - 00000000cf4bf000 (reserved) (XEN) 00000000cf4bf000 - 00000000cf4c2000 (usable) (XEN) 00000000cf4c2000 - 00000000cf7bf000 (ACPI NVS) (XEN) 00000000cf7bf000 - 00000000cf7df000 (usable) (XEN) 00000000cf7df000 - 00000000cf7ff000 (ACPI data) (XEN) 00000000cf7ff000 - 00000000cf800000 (usable) (XEN) 00000000cf800000 - 00000000d0000000 (reserved) (XEN) 00000000f8000000 - 00000000fd000000 (reserved) (XEN) 00000000ffe00000 - 0000000100000000 (reserved) (XEN) 0000000100000000 - 0000000230000000 (usable) (XEN) ACPI: RSDP 000FE020, 0024 (r2 INTEL ) (XEN) ACPI: XSDT CF7FE120, 0074 (r1 INTEL DX58SO 11F6 1000013) (XEN) ACPI: FACP CF7FD000, 00F4 (r3 INTEL DX58SO 11F6 MSFT 100000D) (XEN) ACPI Warning (tbfadt-0444): Optional field "Pm2ControlBlock" has zero address or length: 0000000000000450/0 [20070126] (XEN) ACPI: DSDT CF7F8000, 4641 (r2 INTEL DX58SO 11F6 MSFT 100000D) (XEN) ACPI: FACS CF728000, 0040 (XEN) ACPI: APIC CF7F7000, 0138 (r2 INTEL DX58SO 11F6 MSFT 100000D) (XEN) ACPI: WDDT CF7F6000, 0040 (r1 INTEL DX58SO 11F6 MSFT 100000D) (XEN) ACPI: MCFG CF7F5000, 003C (r1 INTEL DX58SO 11F6 MSFT 100000D) (XEN) ACPI: ASF! CF7F4000, 00AC (r32 INTEL DX58SO 11F6 MSFT 100000D) (XEN) ACPI: HPET CF7F3000, 0038 (r1 INTEL DX58SO 11F6 MSFT 100000D) (XEN) ACPI: SSDT CF7E2000, E134 (r1 INTEL SSDT PM 11F6 MSFT 100000D) (XEN) ACPI: DMAR CF7DF000, 0140 (r1 INTEL DX58SO 11F6 MSFT 100000D) (XEN) ACPI: WDTT CF7F1000, 020C (r2 INTEL DX58SO 11F6 MSFT 100000D) (XEN) ACPI: ASPT CF7F2000, 0034 (r4 INTEL PerfTune 11F6 MSFT 100000D) (XEN) System RAM: 7932MB (8123268kB) (XEN) Domain heap initialised (XEN) Processor #0 7:10 APIC version 21 (XEN) Processor #2 7:10 APIC version 21 (XEN) Processor #4 7:10 APIC version 21 (XEN) Processor #6 7:10 APIC version 21 (XEN) Processor #1 7:10 APIC version 21 (XEN) Processor #3 7:10 APIC version 21 (XEN) Processor #5 7:10 APIC version 21 (XEN) Processor #7 7:10 APIC version 21 (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) [VT-D]dmar.c:679: Host address width 39 (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: (XEN) [VT-D]dmar.c:398: dmaru->address = fe711000 (XEN) [VT-D]dmar.c:334: endpoint: 0:1b.0 (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: (XEN) [VT-D]dmar.c:398: dmaru->address = fe710000 (XEN) [VT-D]dmar.c:340: IOAPIC: f0:1f.7 (XEN) [VT-D]dmar.c:411: flags: INCLUDE_ALL (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e9000 end_address e9fff (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.1 (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ea000 end_address eafff (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.2 (XEN) [VT-D]dmar.c:571: RMRR region: base_addr eb000 end_address ebfff (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.0 (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e6000 end_address e6fff (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.1 (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e7000 end_address e7fff (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.2 (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e8000 end_address e8fff (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ec000 end_address eefff (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Detected 2800.177 MHz processor. (XEN) Initing memory sharing. (XEN) VMX: Supported advanced features: (XEN) - APIC MMIO access virtualisation (XEN) - APIC TPR shadow (XEN) - Extended Page Tables (EPT) (XEN) - Virtual-Processor Identifiers (VPID) (XEN) - Virtual NMI (XEN) - MSR direct-access bitmap (XEN) HVM: ASIDs enabled. (XEN) HVM: VMX enabled (XEN) HVM: Hardware Assisted Paging detected. (XEN) [VT-D]iommu.c:1078: drhd->address = fe711000 iommu->reg = ffff82c3fff57000 (XEN) [VT-D]iommu.c:1080: cap = c9008010e60262 ecap = f0207a (XEN) [VT-D]iommu.c:1078: drhd->address = fe710000 iommu->reg = ffff82c3fff56000 (XEN) [VT-D]iommu.c:1080: cap = c90780106f0462 ecap = f020fa (XEN) Intel VT-d Snoop Control not supported. (XEN) Intel VT-d DMA Passthrough not supported. (XEN) Intel VT-d Queued Invalidation supported. (XEN) Intel VT-d Interrupt Remapping supported. (XEN) I/O virtualisation enabled (XEN) I/O virtualisation for PV guests disabled (XEN) Total of 8 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) TSC is reliable, synchronization unnecessary (XEN) Platform timer is 14.318MHz HPET (XEN) Allocated console ring of 16 KiB. (XEN) Brought up 8 CPUs (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:0.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.1 (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.0 (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.1 (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.2 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:14.3 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:19.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.1 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.2 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.7 (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:1b.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.1 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.2 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.7 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.2 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.3 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.5 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.1 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.2 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.1 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.2 (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 5:0.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.1 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.2 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.1 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.2 (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = a:0.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.1 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.2 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.3 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.4 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.5 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.6 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.7 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.1 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.1 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.1 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.4 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.1 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.2 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.3 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.1 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.2 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.3 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.1 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.2 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.3 (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = ffff82c3fff57000 (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = ffff82c3fff56000 (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1a92000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000200000000->0000000220000000 (393216 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff81000000->ffffffff81a92000 (XEN) Init. ramdisk: ffffffff81a92000->ffffffff8fb9d200 (XEN) Phys-Mach map: ffffffff8fb9e000->ffffffff8ff9e000 (XEN) Start info: ffffffff8ff9e000->ffffffff8ff9e4b4 (XEN) Page tables: ffffffff8ff9f000->ffffffff90024000 (XEN) Boot stack: ffffffff90024000->ffffffff90025000 (XEN) TOTAL: ffffffff80000000->ffffffff90400000 (XEN) ENTRY ADDRESS: ffffffff81895200 (XEN) Dom0 has maximum 8 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 \047CTRL-a\047 three times to switch input to Xen) (XEN) Freed 164kB init memory. (XEN) [VT-D]iommu.c:1461: d0:PCI: unmap bdf = 2:0.0 (XEN) [VT-D]iommu.c:1332: d1:PCI: map bdf = 2:0.0 (XEN) domctl.c:853:d0 XEN_DOMCTL_assign_device: assign device (2:0.0) failed (XEN) [VT-D]iommu.c:1461: d0:PCI: unmap bdf = 2:0.0 (XEN) [VT-D]iommu.c:1332: d2:PCI: map bdf = 2:0.0 (XEN) domctl.c:853:d0 XEN_DOMCTL_assign_device: assign device (2:0.0) failed (XEN) event_channel.c:192:d0 EVTCHNOP failure: domain 2, error -22 [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Linux version 2.6.32.12 (root@scanmaster2) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #1 SMP Fri May 14 13:40:05 EDT 2010 [ 0.000000] Command line: root=/dev/md0 ro console=tty0 xen-pciback.permissive pci=resource_alignment=02:00.0;02:00.1;02:00.2 xen-pciback.hide=(02:00.0)(02:00.1)(02:00.2)(0b: 02.0)(0b:02.1)(0b:03.0)(03:00.0) [ 0.000000] KERNEL supported cpus: [ 0.000000] Intel GenuineIntel [ 0.000000] AMD AuthenticAMD [ 0.000000] Centaur CentaurHauls [ 0.000000] released 0 pages of unused memory [ 0.000000] BIOS-provided physical RAM map: [ 0.000000] Xen: 0000000000000000 - 000000000008f000 (usable) [ 0.000000] Xen: 000000000008f000 - 0000000000090000 (reserved) [ 0.000000] Xen: 0000000000090000 - 000000000009ec00 (usable) [ 0.000000] Xen: 000000000009ec00 - 0000000000100000 (reserved) [ 0.000000] Xen: 0000000000100000 - 0000000080000000 (usable) [ 0.000000] Xen: 00000000cf4bd000 - 00000000cf4bf000 (reserved) [ 0.000000] Xen: 00000000cf4c2000 - 00000000cf7bf000 (ACPI NVS) [ 0.000000] Xen: 00000000cf7df000 - 00000000cf7ff000 (ACPI data) [ 0.000000] Xen: 00000000cf800000 - 00000000d0000000 (reserved) [ 0.000000] Xen: 00000000f8000000 - 00000000fd000000 (reserved) [ 0.000000] Xen: 00000000fec00000 - 00000000fec01000 (reserved) [ 0.000000] Xen: 00000000fee00000 - 00000000fee01000 (reserved) [ 0.000000] Xen: 00000000ffe00000 - 0000000100000000 (reserved) [ 0.000000] DMI 2.5 present. [ 0.000000] last_pfn = 0x80000 max_arch_pfn = 0x400000000 [ 0.000000] x86 PAT enabled: cpu 0, old 0x50100070406, new 0x7010600070106 [ 0.000000] e820 update range: 0000000000001000 - 0000000000006000 (usable) ==> (reserved) [ 0.000000] Scanning 1 areas for low memory corruption [ 0.000000] modified physical RAM map: [ 0.000000] modified: 0000000000000000 - 0000000000001000 (usable) [ 0.000000] modified: 0000000000001000 - 0000000000006000 (reserved) [ 0.000000] modified: 0000000000006000 - 000000000008f000 (usable) [ 0.000000] modified: 000000000008f000 - 0000000000090000 (reserved) [ 0.000000] modified: 0000000000090000 - 000000000009ec00 (usable) [ 0.000000] modified: 000000000009ec00 - 0000000000100000 (reserved) [ 0.000000] modified: 0000000000100000 - 0000000080000000 (usable) [ 0.000000] modified: 00000000cf4bd000 - 00000000cf4bf000 (reserved) [ 0.000000] modified: 00000000cf4c2000 - 00000000cf7bf000 (ACPI NVS) [ 0.000000] modified: 00000000cf7df000 - 00000000cf7ff000 (ACPI data) [ 0.000000] modified: 00000000cf800000 - 00000000d0000000 (reserved) [ 0.000000] modified: 00000000f8000000 - 00000000fd000000 (reserved) [ 0.000000] modified: 00000000fec00000 - 00000000fec01000 (reserved) [ 0.000000] modified: 00000000fee00000 - 00000000fee01000 (reserved) [ 0.000000] modified: 00000000ffe00000 - 0000000100000000 (reserved) [ 0.000000] initial memory mapped : 0 - 20000000 [ 0.000000] init_memory_mapping: 0000000000000000-0000000080000000 [ 0.000000] 0000000000 - 0080000000 page 4k [ 0.000000] kernel direct mapping tables up to 80000000 @ 100000-503000 [ 0.000000] RAMDISK: 01a92000 - 0fb9d200 [ 0.000000] ACPI: RSDP 00000000000fe020 00024 (v02 INTEL ) [ 0.000000] ACPI: XSDT 00000000cf7fe120 00074 (v01 INTEL DX58SO 000011F6 01000013) [ 0.000000] ACPI: FACP 00000000cf7fd000 000F4 (v03 INTEL DX58SO 000011F6 MSFT 0100000D) [ 0.000000] ACPI Warning: Optional field Pm2ControlBlock has zero address or length: 0000000000000450/0 (20090903/tbfadt-557) [ 0.000000] ACPI Warning: Invalid length for Pm2ControlBlock: 0, using default 8 (20090903/tbfadt-607) [ 0.000000] ACPI: DSDT 00000000cf7f8000 04641 (v02 INTEL DX58SO 000011F6 MSFT 0100000D) [ 0.000000] ACPI: FACS 00000000cf728000 00040 [ 0.000000] ACPI: APIC 00000000cf7f7000 00138 (v02 INTEL DX58SO 000011F6 MSFT 0100000D) [ 0.000000] ACPI: WDDT 00000000cf7f6000 00040 (v01 INTEL DX58SO 000011F6 MSFT 0100000D) [ 0.000000] ACPI: MCFG 00000000cf7f5000 0003C (v01 INTEL DX58SO 000011F6 MSFT 0100000D) [ 0.000000] ACPI: ASF! 00000000cf7f4000 000AC (v32 INTEL DX58SO 000011F6 MSFT 0100000D) [ 0.000000] ACPI: HPET 00000000cf7f3000 00038 (v01 INTEL DX58SO 000011F6 MSFT 0100000D) [ 0.000000] ACPI: SSDT 00000000cf7e2000 0E134 (v01 INTEL SSDT PM 000011F6 MSFT 0100000D) [ 0.000000] ACPI: 00000000cf7df000 00140 (v01 INTEL DX58SO 000011F6 MSFT 0100000D) [ 0.000000] ACPI: WDTT 00000000cf7f1000 0020C (v02 INTEL DX58SO 000011F6 MSFT 0100000D) [ 0.000000] ACPI: ASPT 00000000cf7f2000 00034 (v04 INTEL PerfTune 000011F6 MSFT 0100000D) [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] No NUMA configuration found [ 0.000000] Faking a node at 0000000000000000-0000000080000000 [ 0.000000] Bootmem setup node 0 0000000000000000-0000000080000000 [ 0.000000] NODE_DATA [0000000000008000 - 000000000000cfff] [ 0.000000] bootmap [000000000000d000 - 000000000001cfff] pages 10 [ 0.000000] (8 early reservations) ==> bootmem [0000000000 - 0080000000] [ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] [ 0.000000] #1 [000ff9f000 - 0010024000] XEN PAGETABLES ==> [000ff9f000 - 0010024000] [ 0.000000] #2 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 - 0000008000] [ 0.000000] #3 [0001000000 - 0001a718e4] TEXT DATA BSS ==> [0001000000 - 0001a718e4] [ 0.000000] #4 [0001a92000 - 000fb9d200] RAMDISK ==> [0001a92000 - 000fb9d200] [ 0.000000] #5 [000fb9e000 - 000ff9f000] XEN START INFO ==> [000fb9e000 - 000ff9f000] [ 0.000000] #6 [0001a72000 - 0001a7215e] BRK ==> [0001a72000 - 0001a7215e] [ 0.000000] #7 [0000100000 - 000047b000] PGTABLE ==> [0000100000 - 000047b000] [ 0.000000] Zone PFN ranges: [ 0.000000] DMA 0x00000000 -> 0x00001000 [ 0.000000] DMA32 0x00001000 -> 0x00100000 [ 0.000000] Normal 0x00100000 -> 0x00100000 [ 0.000000] Movable zone start PFN for each node [ 0.000000] early_node_map[4] active PFN ranges [ 0.000000] 0: 0x00000000 -> 0x00000001 [ 0.000000] 0: 0x00000006 -> 0x0000008f [ 0.000000] 0: 0x00000090 -> 0x0000009e [ 0.000000] 0: 0x00000100 -> 0x00080000 [ 0.000000] On node 0 totalpages: 524184 [ 0.000000] DMA zone: 56 pages used for memmap [ 0.000000] DMA zone: 894 pages reserved [ 0.000000] DMA zone: 3042 pages, LIFO batch:0 [ 0.000000] DMA32 zone: 7112 pages used for memmap [ 0.000000] DMA32 zone: 513080 pages, LIFO batch:31 [ 0.000000] ACPI: PM-Timer IO Port: 0x408 [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x02] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x04] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x06] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x01] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x03] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x05] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x10] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x12] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x14] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x16] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x11] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x13] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x15] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x17] disabled) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x04] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x05] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x06] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x07] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x0c] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x0d] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x0e] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x0f] high level lint[0x1]) [ 0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0]) [ 0.000000] IOAPIC[0]: apic_id 8, version 0, address 0xfec00000, GSI 0-0 [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [ 0.000000] ERROR: Unable to locate IOAPIC for GSI 2 [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [ 0.000000] ERROR: Unable to locate IOAPIC for GSI 9 [ 0.000000] Using ACPI (MADT) for SMP configuration information [ 0.000000] ACPI: HPET id: 0x8086a301 base: 0xfed00000 [ 0.000000] SMP: Allowing 8 CPUs, 0 hotplug CPUs [ 0.000000] nr_irqs_gsi: 256 [ 0.000000] PM: Registered nosave memory: 0000000000001000 - 0000000000006000 [ 0.000000] PM: Registered nosave memory: 000000000008f000 - 0000000000090000 [ 0.000000] PM: Registered nosave memory: 000000000009e000 - 000000000009f000 [ 0.000000] PM: Registered nosave memory: 000000000009f000 - 0000000000100000 [ 0.000000] Allocating PCI resources starting at 80000000 (gap: 80000000:4f4bd000) [ 0.000000] Booting paravirtualized kernel on Xen [ 0.000000] Xen version: 4.0.0 (preserve-AD) (dom0) [ 0.000000] NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:8 nr_node_ids:1 [ 0.000000] PERCPU: Embedded 30 pages/cpu @ffff88001005a000 s91416 r8192 d23272 u122880 [ 0.000000] pcpu-alloc: s91416 r8192 d23272 u122880 alloc=30*4096 [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5 [0] 6 [0] 7 [ 0.101661] trying to map vcpu_info 0 at ffff880010065020, mfn 210065, offset 32 [ 0.101665] cpu 0 using vcpu_info at ffff880010065020 [ 0.101667] trying to map vcpu_info 1 at ffff880010083020, mfn 210083, offset 32 [ 0.101669] cpu 1 using vcpu_info at ffff880010083020 [ 0.101671] trying to map vcpu_info 2 at ffff8800100a1020, mfn 2100a1, offset 32 [ 0.101673] cpu 2 using vcpu_info at ffff8800100a1020 [ 0.101675] trying to map vcpu_info 3 at ffff8800100bf020, mfn 2100bf, offset 32 [ 0.101677] cpu 3 using vcpu_info at ffff8800100bf020 [ 0.101679] trying to map vcpu_info 4 at ffff8800100dd020, mfn 2100dd, offset 32 [ 0.101681] cpu 4 using vcpu_info at ffff8800100dd020 [ 0.101683] trying to map vcpu_info 5 at ffff8800100fb020, mfn 2100fb, offset 32 [ 0.101685] cpu 5 using vcpu_info at ffff8800100fb020 [ 0.101687] trying to map vcpu_info 6 at ffff880010119020, mfn 210119, offset 32 [ 0.101689] cpu 6 using vcpu_info at ffff880010119020 [ 0.101691] trying to map vcpu_info 7 at ffff880010137020, mfn 210137, offset 32 [ 0.101693] cpu 7 using vcpu_info at ffff880010137020 [ 0.101694] Xen: using vcpu_info placement [ 0.101699] Built 1 zonelists in Node order, mobility grouping on. Total pages: 516122 [ 0.101701] Policy zone: DMA32 [ 0.101703] Kernel command line: root=/dev/md0 ro console=tty0 xen-pciback.permissive pci=resource_alignment=02:00.0;02:00.1;02:00.2 xen-pciback.hide=(02:00.0)(02:00.1)(02:00 .2)(0b:02.0)(0b:02.1)(0b:03.0)(03:00.0) [ 0.101732] PID hash table entries: 4096 (order: 3, 32768 bytes) [ 0.102061] Initializing CPU#0 [ 0.114275] DMA: Placing 64MB software IO TLB between ffff880012016000 - ffff880016016000 [ 0.114279] DMA: software IO TLB at phys 0x12016000 - 0x16016000 [ 0.114281] xen_swiotlb_fixup: buf=ffff880012016000 size=67108864 [ 0.136136] xen_swiotlb_fixup: buf=ffff880016076000 size=32768 [ 0.142429] Memory: 1751436k/2097152k available (5631k kernel code, 416k absent, 345300k reserved, 3058k data, 816k init) [ 0.142454] SLUB: Genslabs=14, HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1 [ 0.142482] Hierarchical RCU implementation. [ 0.142488] NR_IRQS:4352 nr_irqs:2304 [ 0.142572] xen: --> irq=0 [ 0.142579] xen: --> irq=1 [ 0.142584] xen: --> irq=2 [ 0.142589] xen: --> irq=3 [ 0.142594] xen: --> irq=4 [ 0.142598] xen: --> irq=5 [ 0.142603] xen: --> irq=6 [ 0.142607] xen: --> irq=7 [ 0.142612] xen: --> irq=8 [ 0.142617] xen: --> irq=9 [ 0.142621] xen: --> irq=10 [ 0.142626] xen: --> irq=11 [ 0.142631] xen: --> irq=12 [ 0.142635] xen: --> irq=13 [ 0.142640] xen: --> irq=14 [ 0.142645] xen: --> irq=15 [ 0.142657] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [ 0.142660] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [ 0.142662] xen: sci override: source_irq=9 global_irq=9 trigger=c polarity=1 [ 0.142664] xen: registering gsi 9 triggering 0 polarity 0 [ 0.142666] xen_allocate_pirq: returning irq 9 for gsi 9 [ 0.142668] xen: --> irq=9 [ 0.142700] xen: acpi sci 9 [ 0.144674] Console: colour VGA+ 80x25 [ 0.153136] console [tty0] enabled [ 0.156719] allocated 20971520 bytes of page_cgroup [ 0.156776] please try 'cgroup_disable=memory' option if you don't want memory cgroups [ 0.156878] Xen: using vcpuop timer interface [ 0.156876] installing Xen timer for CPU 0 [ 0.156935] alloc irq_desc for 2303 on node 0 [ 0.156938] alloc kstat_irqs on node 0 [ 0.156953] Detected 2800.176 MHz processor. [ 0.157009] Calibrating delay loop (skipped), value calculated using timer frequency.. 5600.35 BogoMIPS (lpj=28001760) [ 0.157125] Security Framework initialized [ 0.157178] SELinux: Disabled at boot. [ 0.157538] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes) [ 0.158137] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes) [ 0.158379] Mount-cache hash table entries: 256 [ 0.159875] Initializing cgroup subsys ns [ 0.159927] Initializing cgroup subsys cpuacct [ 0.159979] Initializing cgroup subsys memory [ 0.160034] Initializing cgroup subsys devices [ 0.160086] Initializing cgroup subsys freezer [ 0.160137] Initializing cgroup subsys net_cls [ 0.160213] CPU: L1 I cache: 32K, L1 D cache: 32K [ 0.160291] CPU: L2 cache: 256K [ 0.160339] CPU: L3 cache: 8192K [ 0.160389] CPU 0/0x0 -> Node 0 [ 0.160437] CPU: Unsupported number of siblings 16 [ 0.160475] mce: CPU supports 9 MCE banks [ 0.160583] Performance Events: unsupported p6 CPU model 26 no PMU driver, software events only. [ 0.160719] SMP alternatives: switching to UP code [ 0.192384] ACPI: Core revision 20090903 [ 0.207233] ftrace: converting mcount calls to 0f 1f 44 00 00 [ 0.207289] ftrace: allocating 21472 entries in 85 pages [ 0.212402] alloc irq_desc for 2302 on node 0 [ 0.212405] alloc kstat_irqs on node 0 [ 0.212410] cpu 0 spinlock event irq 2302 [ 0.212463] alloc irq_desc for 2301 on node 0 [ 0.212465] alloc kstat_irqs on node 0 [ 0.212469] alloc irq_desc for 2300 on node 0 [ 0.212470] alloc kstat_irqs on node 0 [ 0.212474] alloc irq_desc for 2299 on node 0 [ 0.212476] alloc kstat_irqs on node 0 [ 0.212480] alloc irq_desc for 2298 on node 0 [ 0.212482] alloc kstat_irqs on node 0 [ 0.212634] installing Xen timer for CPU 1 [ 0.212686] alloc irq_desc for 2297 on node 0 [ 0.212688] alloc kstat_irqs on node 0 [ 0.212693] alloc irq_desc for 2296 on node 0 [ 0.212695] alloc kstat_irqs on node 0 [ 0.212698] cpu 1 spinlock event irq 2296 [ 0.212766] SMP alternatives: switching to SMP code [ 0.242090] alloc irq_desc for 2295 on node 0 [ 0.242092] alloc kstat_irqs on node 0 [ 0.242102] alloc irq_desc for 2294 on node 0 [ 0.242104] alloc kstat_irqs on node 0 [ 0.242108] alloc irq_desc for 2293 on node 0 [ 0.242109] alloc kstat_irqs on node 0 [ 0.242115] alloc irq_desc for 2292 on node 0 [ 0.242116] alloc kstat_irqs on node 0 [ 0.000006] Initializing CPU#1 [ 0.000037] CPU: L1 I cache: 32K, L1 D cache: 32K [ 0.000039] CPU: L2 cache: 256K [ 0.000040] CPU: L3 cache: 8192K [ 0.000043] CPU 1/0x0 -> Node 0 [ 0.000045] CPU: Unsupported number of siblings 16 [ 0.242250] installing Xen timer for CPU 2 [ 0.242586] alloc irq_desc for 2291 on node 0 [ 0.242588] alloc kstat_irqs on node 0 [ 0.242592] alloc irq_desc for 2290 on node 0 [ 0.242594] alloc kstat_irqs on node 0 [ 0.242597] cpu 2 spinlock event irq 2290 [ 0.242661] alloc irq_desc for 2289 on node 0 [ 0.242663] alloc kstat_irqs on node 0 [ 0.242667] alloc irq_desc for 2288 on node 0 [ 0.242669] alloc kstat_irqs on node 0 [ 0.242672] alloc irq_desc for 2287 on node 0 [ 0.242674] alloc kstat_irqs on node 0 [ 0.242678] alloc irq_desc for 2286 on node 0 [ 0.242679] alloc kstat_irqs on node 0 [ 0.000005] Initializing CPU#2 [ 0.000034] CPU: L1 I cache: 32K, L1 D cache: 32K [ 0.000036] CPU: L2 cache: 256K [ 0.000037] CPU: L3 cache: 8192K [ 0.000040] CPU 2/0x0 -> Node 0 [ 0.000042] CPU: Unsupported number of siblings 16 [ 0.242803] installing Xen timer for CPU 3 [ 0.243138] alloc irq_desc for 2285 on node 0 [ 0.243140] alloc kstat_irqs on node 0 [ 0.243144] alloc irq_desc for 2284 on node 0 [ 0.243146] alloc kstat_irqs on node 0 [ 0.243149] cpu 3 spinlock event irq 2284 [ 0.243212] alloc irq_desc for 2283 on node 0 [ 0.243214] alloc kstat_irqs on node 0 [ 0.243218] alloc irq_desc for 2282 on node 0 [ 0.243220] alloc kstat_irqs on node 0 [ 0.243223] alloc irq_desc for 2281 on node 0 [ 0.243225] alloc kstat_irqs on node 0 [ 0.243229] alloc irq_desc for 2280 on node 0 [ 0.243230] alloc kstat_irqs on node 0 [ 0.000005] Initializing CPU#3 [ 0.000034] CPU: L1 I cache: 32K, L1 D cache: 32K [ 0.000036] CPU: L2 cache: 256K [ 0.000037] CPU: L3 cache: 8192K [ 0.000040] CPU 3/0x0 -> Node 0 [ 0.000041] CPU: Unsupported number of siblings 16 [ 0.243354] installing Xen timer for CPU 4 [ 0.243690] alloc irq_desc for 2279 on node 0 [ 0.243692] alloc kstat_irqs on node 0 [ 0.243696] alloc irq_desc for 2278 on node 0 [ 0.243698] alloc kstat_irqs on node 0 [ 0.243701] cpu 4 spinlock event irq 2278 [ 0.243764] alloc irq_desc for 2277 on node 0 [ 0.243766] alloc kstat_irqs on node 0 [ 0.243770] alloc irq_desc for 2276 on node 0 [ 0.243772] alloc kstat_irqs on node 0 [ 0.243776] alloc irq_desc for 2275 on node 0 [ 0.243777] alloc kstat_irqs on node 0 [ 0.243781] alloc irq_desc for 2274 on node 0 [ 0.243782] alloc kstat_irqs on node 0 [ 0.000004] Initializing CPU#4 [ 0.000041] CPU: L1 I cache: 32K, L1 D cache: 32K [ 0.000044] CPU: L2 cache: 256K [ 0.000046] CPU: L3 cache: 8192K [ 0.000050] CPU 4/0x0 -> Node 0 [ 0.000053] CPU: Unsupported number of siblings 16 [ 0.243929] installing Xen timer for CPU 5 [ 0.244265] alloc irq_desc for 2273 on node 0 [ 0.244267] alloc kstat_irqs on node 0 [ 0.244272] alloc irq_desc for 2272 on node 0 [ 0.244273] alloc kstat_irqs on node 0 [ 0.244277] cpu 5 spinlock event irq 2272 [ 0.244340] alloc irq_desc for 2271 on node 0 [ 0.244341] alloc kstat_irqs on node 0 [ 0.244346] alloc irq_desc for 2270 on node 0 [ 0.244347] alloc kstat_irqs on node 0 [ 0.244351] alloc irq_desc for 2269 on node 0 [ 0.244353] alloc kstat_irqs on node 0 [ 0.244357] alloc irq_desc for 2268 on node 0 [ 0.244358] alloc kstat_irqs on node 0 [ 0.000003] Initializing CPU#5 [ 0.000030] CPU: L1 I cache: 32K, L1 D cache: 32K [ 0.000032] CPU: L2 cache: 256K [ 0.000033] CPU: L3 cache: 8192K [ 0.000036] CPU 5/0x0 -> Node 0 [ 0.000037] CPU: Unsupported number of siblings 16 [ 0.244475] installing Xen timer for CPU 6 [ 0.244810] alloc irq_desc for 2267 on node 0 [ 0.244812] alloc kstat_irqs on node 0 [ 0.244816] alloc irq_desc for 2266 on node 0 [ 0.244818] alloc kstat_irqs on node 0 [ 0.244822] cpu 6 spinlock event irq 2266 [ 0.244884] alloc irq_desc for 2265 on node 0 [ 0.244886] alloc kstat_irqs on node 0 [ 0.244890] alloc irq_desc for 2264 on node 0 [ 0.244892] alloc kstat_irqs on node 0 [ 0.244896] alloc irq_desc for 2263 on node 0 [ 0.244898] alloc kstat_irqs on node 0 [ 0.244901] alloc irq_desc for 2262 on node 0 [ 0.244903] alloc kstat_irqs on node 0 [ 0.000004] Initializing CPU#6 [ 0.000030] CPU: L1 I cache: 32K, L1 D cache: 32K [ 0.000032] CPU: L2 cache: 256K [ 0.000033] CPU: L3 cache: 8192K [ 0.000036] CPU 6/0x0 -> Node 0 [ 0.000037] CPU: Unsupported number of siblings 16 [ 0.245021] installing Xen timer for CPU 7 [ 0.245357] alloc irq_desc for 2261 on node 0 [ 0.245359] alloc kstat_irqs on node 0 [ 0.245365] alloc irq_desc for 2260 on node 0 [ 0.245366] alloc kstat_irqs on node 0 [ 0.245370] cpu 7 spinlock event irq 2260 [ 0.245433] alloc irq_desc for 2259 on node 0 [ 0.245435] alloc kstat_irqs on node 0 [ 0.245439] alloc irq_desc for 2258 on node 0 [ 0.245440] alloc kstat_irqs on node 0 [ 0.245445] alloc irq_desc for 2257 on node 0 [ 0.245446] alloc kstat_irqs on node 0 [ 0.245450] alloc irq_desc for 2256 on node 0 [ 0.245451] alloc kstat_irqs on node 0 [ 0.000004] Initializing CPU#7 [ 0.000030] CPU: L1 I cache: 32K, L1 D cache: 32K [ 0.000032] CPU: L2 cache: 256K [ 0.000033] CPU: L3 cache: 8192K [ 0.000035] CPU 7/0x0 -> Node 0 [ 0.000037] CPU: Unsupported number of siblings 16 [ 0.245521] Brought up 8 CPUs [ 0.245864] CPU0 attaching sched-domain: [ 0.245867] domain 0: span 0-7 level CPU [ 0.245869] groups: 0 1 2 3 4 5 6 7 [ 0.245879] CPU1 attaching sched-domain: [ 0.245881] domain 0: span 0-7 level CPU [ 0.245883] groups: 1 2 3 4 5 6 7 0 [ 0.245892] CPU2 attaching sched-domain: [ 0.245894] domain 0: span 0-7 level CPU [ 0.245896] groups: 2 3 4 5 6 7 0 1 [ 0.245905] CPU3 attaching sched-domain: [ 0.245906] domain 0: span 0-7 level CPU [ 0.245909] groups: 3 4 5 6 7 0 1 2 [ 0.245917] CPU4 attaching sched-domain: [ 0.245919] domain 0: span 0-7 level CPU [ 0.245921] groups: 4 5 6 7 0 1 2 3 [ 0.245930] CPU5 attaching sched-domain: [ 0.245932] domain 0: span 0-7 level CPU [ 0.245934] groups: 5 6 7 0 1 2 3 4 [ 0.245943] CPU6 attaching sched-domain: [ 0.245945] domain 0: span 0-7 level CPU [ 0.245947] groups: 6 7 0 1 2 3 4 5 [ 0.245956] CPU7 attaching sched-domain: [ 0.245957] domain 0: span 0-7 level CPU [ 0.245960] groups: 7 0 1 2 3 4 5 6 [ 0.246279] devtmpfs: initialized [ 0.247479] Grant table initialized [ 0.247530] regulator: core version 0.5 [ 0.247608] Time: 20:53:18 Date: 05/14/10 [ 0.247700] NET: Registered protocol family 16 [ 0.247791] alloc irq_desc for 2255 on node 0 [ 0.247793] alloc kstat_irqs on node 0 [ 0.247903] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [ 0.247977] ACPI: bus type pci registered [ 0.248087] PCI: MCFG configuration 0: base f8000000 segment 0 buses 0 - 63 [ 0.248143] PCI: MCFG area at f8000000 reserved in E820 [ 0.256477] PCI: Using MMCONFIG at f8000000 - fbffffff [ 0.256529] PCI: Using configuration type 1 for base access [ 0.257462] bio: create slab <bio-0> at 0 [ 0.259199] ERROR: Unable to locate IOAPIC for GSI 9 [ 0.259314] ACPI: EC: Look up EC in DSDT [ 0.281724] ACPI: Interpreter enabled [ 0.281777] ACPI: (supports S0 S1 S3 S4 S5) [ 0.281984] ACPI: Using IOAPIC for interrupt routing [ 0.287661] ACPI Warning: Incorrect checksum in table [ ] - 1D, should be 61 (20090903/tbutils-314) [ 0.287993] ACPI: No dock devices found. [ 0.288632] ACPI: PCI Root Bridge [PCI0] (0000:00) [ 0.288908] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold [ 0.288965] pci 0000:00:01.0: PME# disabled [ 0.289143] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold [ 0.289200] pci 0000:00:03.0: PME# disabled [ 0.289380] pci 0000:00:07.0: PME# supported from D0 D3hot D3cold [ 0.289437] pci 0000:00:07.0: PME# disabled [ 0.290110] pci 0000:00:19.0: reg 10 32bit mmio: [0xd2600000-0xd261ffff] [ 0.290119] pci 0000:00:19.0: reg 14 32bit mmio: [0xd2622000-0xd2622fff] [ 0.290129] pci 0000:00:19.0: reg 18 io port: [0x20e0-0x20ff] [ 0.290198] pci 0000:00:19.0: PME# supported from D0 D3hot D3cold [ 0.290255] pci 0000:00:19.0: PME# disabled [ 0.290388] pci 0000:00:1a.0: reg 20 io port: [0x20c0-0x20df] [ 0.290507] pci 0000:00:1a.1: reg 20 io port: [0x20a0-0x20bf] [ 0.290626] pci 0000:00:1a.2: reg 20 io port: [0x2080-0x209f] [ 0.290750] pci 0000:00:1a.7: reg 10 32bit mmio: [0xd2621000-0xd26213ff] [ 0.290841] pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold [ 0.290899] pci 0000:00:1a.7: PME# disabled [ 0.291016] pci 0000:00:1b.0: reg 10 64bit mmio: [0xf0000000-0xf0003fff] [ 0.291091] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold [ 0.291148] pci 0000:00:1b.0: PME# disabled [ 0.291306] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold [ 0.291363] pci 0000:00:1c.0: PME# disabled [ 0.291523] pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold [ 0.291580] pci 0000:00:1c.1: PME# disabled [ 0.291743] pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold [ 0.291800] pci 0000:00:1c.4: PME# disabled [ 0.291943] pci 0000:00:1d.0: reg 20 io port: [0x2060-0x207f] [ 0.292061] pci 0000:00:1d.1: reg 20 io port: [0x2040-0x205f] [ 0.292178] pci 0000:00:1d.2: reg 20 io port: [0x2020-0x203f] [ 0.292295] pci 0000:00:1d.7: reg 10 32bit mmio: [0xd2620000-0xd26203ff] [ 0.292383] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold [ 0.292440] pci 0000:00:1d.7: PME# disabled [ 0.292696] pci 0000:00:1f.0: quirk: region 0400-047f claimed by ICH6 ACPI/GPIO/TCO [ 0.292770] pci 0000:00:1f.0: quirk: region 0500-053f claimed by ICH6 GPIO [ 0.292828] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0680 (mask 007f) [ 0.292902] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 2 PIO at 0810 (mask 007f) [ 0.293062] pci 0000:00:1f.2: reg 10 io port: [0x2158-0x215f] [ 0.293071] pci 0000:00:1f.2: reg 14 io port: [0x216c-0x216f] [ 0.293080] pci 0000:00:1f.2: reg 18 io port: [0x2150-0x2157] [ 0.293089] pci 0000:00:1f.2: reg 1c io port: [0x2168-0x216b] [ 0.293098] pci 0000:00:1f.2: reg 20 io port: [0x2130-0x213f] [ 0.293107] pci 0000:00:1f.2: reg 24 io port: [0x2120-0x212f] [ 0.293189] pci 0000:00:1f.3: reg 10 64bit mmio: [0xf0004000-0xf00040ff] [ 0.293212] pci 0000:00:1f.3: reg 20 io port: [0x2000-0x201f] [ 0.293288] pci 0000:00:1f.5: reg 10 io port: [0x2148-0x214f] [ 0.293297] pci 0000:00:1f.5: reg 14 io port: [0x2164-0x2167] [ 0.293306] pci 0000:00:1f.5: reg 18 io port: [0x2140-0x2147] [ 0.293315] pci 0000:00:1f.5: reg 1c io port: [0x2160-0x2163] [ 0.293324] pci 0000:00:1f.5: reg 20 io port: [0x2110-0x211f] [ 0.293332] pci 0000:00:1f.5: reg 24 io port: [0x2100-0x210f] [ 0.293545] pci 0000:01:00.0: supports D1 D2 [ 0.293617] pci 0000:00:01.0: bridge 32bit mmio: [0xd2500000-0xd25fffff] [ 0.293690] pci 0000:02:00.0: reg 10 32bit mmio: [0xd2502000-0xd2502fff] [ 0.293756] pci 0000:02:00.0: Disabling memory decoding and releasing memory resources. [ 0.293867] pci 0000:02:00.0: supports D1 D2 [ 0.293869] pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot [ 0.293927] pci 0000:02:00.0: PME# disabled [ 0.294045] pci 0000:02:00.1: reg 10 32bit mmio: [0xd2501000-0xd2501fff] [ 0.294112] pci 0000:02:00.1: Disabling memory decoding and releasing memory resources. [ 0.294223] pci 0000:02:00.1: supports D1 D2 [ 0.294224] pci 0000:02:00.1: PME# supported from D0 D1 D2 D3hot [ 0.294283] pci 0000:02:00.1: PME# disabled [ 0.294400] pci 0000:02:00.2: reg 10 32bit mmio: [0xd2500000-0xd25000ff] [ 0.294467] pci 0000:02:00.2: Disabling memory decoding and releasing memory resources. [ 0.294546] pci 0000:02:00.2: Rounding up size of resource #0 to 0x1000. [ 0.294632] pci 0000:02:00.2: supports D1 D2 [ 0.294633] pci 0000:02:00.2: PME# supported from D0 D1 D2 D3hot [ 0.294692] pci 0000:02:00.2: PME# disabled [ 0.294862] pci 0000:01:00.0: bridge 32bit mmio: [0xd2500000-0xd25fffff] [ 0.295047] pci 0000:03:00.0: supports D1 D2 [ 0.295119] pci 0000:00:03.0: bridge 32bit mmio: [0xd2400000-0xd24fffff] [ 0.295193] pci 0000:04:00.0: reg 10 32bit mmio: [0xd2402000-0xd2402fff] [ 0.295294] pci 0000:04:00.0: supports D1 D2 [ 0.295296] pci 0000:04:00.0: PME# supported from D0 D1 D2 D3hot [ 0.295355] pci 0000:04:00.0: PME# disabled [ 0.295473] pci 0000:04:00.1: reg 10 32bit mmio: [0xd2401000-0xd2401fff] [ 0.295580] pci 0000:04:00.1: supports D1 D2 [ 0.295582] pci 0000:04:00.1: PME# supported from D0 D1 D2 D3hot [ 0.295642] pci 0000:04:00.1: PME# disabled [ 0.295761] pci 0000:04:00.2: reg 10 32bit mmio: [0xd2400000-0xd24000ff] [ 0.295868] pci 0000:04:00.2: supports D1 D2 [ 0.295869] pci 0000:04:00.2: PME# supported from D0 D1 D2 D3hot [ 0.295928] pci 0000:04:00.2: PME# disabled [ 0.296097] pci 0000:03:00.0: bridge 32bit mmio: [0xd2400000-0xd24fffff] [ 0.296167] pci 0000:05:00.0: reg 10 32bit mmio: [0xd1000000-0xd1ffffff] [ 0.296182] pci 0000:05:00.0: reg 14 64bit mmio pref: [0xe0000000-0xefffffff] [ 0.296196] pci 0000:05:00.0: reg 1c 64bit mmio: [0xd0000000-0xd0ffffff] [ 0.296211] pci 0000:05:00.0: reg 30 32bit mmio pref: [0xfffe0000-0xffffffff] [ 0.296309] pci 0000:00:07.0: bridge 32bit mmio: [0xd0000000-0xd1ffffff] [ 0.296317] pci 0000:00:07.0: bridge 64bit mmio pref: [0xe0000000-0xefffffff] [ 0.296542] pci 0000:06:00.0: supports D1 D2 [ 0.296637] pci 0000:00:1c.0: bridge 32bit mmio: [0xd2300000-0xd23fffff] [ 0.296729] pci 0000:07:00.0: reg 10 32bit mmio: [0xd2302000-0xd2302fff] [ 0.296863] pci 0000:07:00.0: supports D1 D2 [ 0.296865] pci 0000:07:00.0: PME# supported from D0 D1 D2 D3hot [ 0.296926] pci 0000:07:00.0: PME# disabled [ 0.297063] pci 0000:07:00.1: reg 10 32bit mmio: [0xd2301000-0xd2301fff] [ 0.297198] pci 0000:07:00.1: supports D1 D2 [ 0.297199] pci 0000:07:00.1: PME# supported from D0 D1 D2 D3hot [ 0.297260] pci 0000:07:00.1: PME# disabled [ 0.297401] pci 0000:07:00.2: reg 10 32bit mmio: [0xd2300000-0xd23000ff] [ 0.297535] pci 0000:07:00.2: supports D1 D2 [ 0.297537] pci 0000:07:00.2: PME# supported from D0 D1 D2 D3hot [ 0.297597] pci 0000:07:00.2: PME# disabled [ 0.297804] pci 0000:06:00.0: bridge 32bit mmio: [0xd2300000-0xd23fffff] [ 0.298060] pci 0000:08:00.0: supports D1 D2 [ 0.298156] pci 0000:00:1c.1: bridge 32bit mmio: [0xd2200000-0xd22fffff] [ 0.298251] pci 0000:09:00.0: reg 10 32bit mmio: [0xd2202000-0xd2202fff] [ 0.298386] pci 0000:09:00.0: supports D1 D2 [ 0.298387] pci 0000:09:00.0: PME# supported from D0 D1 D2 D3hot [ 0.298448] pci 0000:09:00.0: PME# disabled [ 0.298586] pci 0000:09:00.1: reg 10 32bit mmio: [0xd2201000-0xd2201fff] [ 0.298720] pci 0000:09:00.1: supports D1 D2 [ 0.298722] pci 0000:09:00.1: PME# supported from D0 D1 D2 D3hot [ 0.298782] pci 0000:09:00.1: PME# disabled [ 0.298921] pci 0000:09:00.2: reg 10 32bit mmio: [0xd2200000-0xd22000ff] [ 0.299055] pci 0000:09:00.2: supports D1 D2 [ 0.299057] pci 0000:09:00.2: PME# supported from D0 D1 D2 D3hot [ 0.299117] pci 0000:09:00.2: PME# disabled [ 0.299326] pci 0000:08:00.0: bridge 32bit mmio: [0xd2200000-0xd22fffff] [ 0.299423] pci 0000:0a:00.0: reg 10 io port: [0x1018-0x101f] [ 0.299434] pci 0000:0a:00.0: reg 14 io port: [0x1024-0x1027] [ 0.299445] pci 0000:0a:00.0: reg 18 io port: [0x1010-0x1017] [ 0.299457] pci 0000:0a:00.0: reg 1c io port: [0x1020-0x1023] [ 0.299469] pci 0000:0a:00.0: reg 20 io port: [0x1000-0x100f] [ 0.299480] pci 0000:0a:00.0: reg 24 32bit mmio: [0xd2100000-0xd21003ff] [ 0.299543] pci 0000:0a:00.0: supports D1 [ 0.299545] pci 0000:0a:00.0: PME# supported from D0 D1 D3hot [ 0.299603] pci 0000:0a:00.0: PME# disabled [ 0.299728] pci 0000:00:1c.4: bridge io port: [0x1000-0x1fff] [ 0.299734] pci 0000:00:1c.4: bridge 32bit mmio: [0xd2100000-0xd21fffff] [ 0.299801] pci 0000:0b:03.0: reg 10 32bit mmio: [0xd2004000-0xd20047ff] [ 0.299812] pci 0000:0b:03.0: reg 14 32bit mmio: [0xd2000000-0xd2003fff] [ 0.299883] pci 0000:0b:03.0: supports D1 D2 [ 0.299885] pci 0000:0b:03.0: PME# supported from D0 D1 D2 D3hot [ 0.299942] pci 0000:0b:03.0: PME# disabled [ 0.300056] pci 0000:00:1e.0: transparent bridge [ 0.300114] pci 0000:00:1e.0: bridge 32bit mmio: [0xd2000000-0xd20fffff] [ 0.300175] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] [ 0.300876] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P32_._PRT] [ 0.301098] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEG1._PRT] [ 0.301173] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEG3._PRT] [ 0.301247] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEG7._PRT] [ 0.301319] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX0._PRT] [ 0.301392] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX1._PRT] [ 0.301472] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX4._PRT] [ 0.315096] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) [ 0.315626] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) [ 0.316151] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 9 10 11 12 14 15) [ 0.316670] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 7 9 10 11 12 14 15) [ 0.317187] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) [ 0.317705] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) [ 0.318226] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) [ 0.318744] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) [ 0.319222] sync cpu 0 get result 1 max_id 7 [ 0.319229] sync cpu 1 get result 1 max_id 7 [ 0.319236] sync cpu 2 get result 1 max_id 7 [ 0.319245] sync cpu 3 get result 1 max_id 7 [ 0.319252] sync cpu 4 get result 1 max_id 7 [ 0.319258] sync cpu 5 get result 1 max_id 7 [ 0.319265] sync cpu 6 get result 1 max_id 7 [ 0.319271] sync cpu 7 get result 1 max_id 7 [ 0.319275] alloc irq_desc for 2254 on node 0 [ 0.319277] alloc kstat_irqs on node 0 [ 0.319299] xen_balloon: Initialising balloon driver with page order 0. [ 0.319421] vgaarb: device added: PCI:0000:05:00.0,decodes=io+mem,owns=io+mem,locks=none [ 0.320859] vgaarb: loaded [ 0.320992] SCSI subsystem initialized [ 0.321238] libata version 3.00 loaded. [ 0.321305] usbcore: registered new interface driver usbfs [ 0.321366] usbcore: registered new interface driver hub [ 0.321449] usbcore: registered new device driver usb [ 0.321638] ACPI: WMI: Mapper loaded [ 0.321688] PCI: Using ACPI for IRQ routing [ 0.322065] NetLabel: Initializing [ 0.322115] NetLabel: domain hash size = 128 [ 0.322165] NetLabel: protocols = UNLABELED CIPSOv4 [ 0.322224] NetLabel: unlabeled traffic allowed by default [ 0.322321] Switching to clocksource xen [ 0.324085] pnp: PnP ACPI init [ 0.324142] ACPI: bus type pnp registered [ 0.325011] xen: registering gsi 8 triggering 1 polarity 0 [ 0.325013] xen_allocate_pirq: returning irq 8 for gsi 8 [ 0.325066] xen: --> irq=8 [ 0.325136] xen: registering gsi 13 triggering 1 polarity 0 [ 0.325138] xen_allocate_pirq: returning irq 13 for gsi 13 [ 0.325191] xen: --> irq=13 [ 0.326197] pnp: PnP ACPI: found 9 devices [ 0.326248] ACPI: ACPI bus type pnp unregistered [ 0.326305] system 00:05: ioport range 0x500-0x53f has been reserved [ 0.326360] system 00:05: ioport range 0x400-0x47f has been reserved [ 0.326415] system 00:05: ioport range 0x680-0x6ff has been reserved [ 0.326582] pciback 0000:02:00.0: seizing device [ 0.326636] pciback 0000:02:00.1: seizing device [ 0.326693] pciback 0000:02:00.2: seizing device [ 0.326746] pciback 0000:03:00.0: seizing device [ 0.326800] pciback 0000:04:00.0: seizing device [ 0.326854] pciback 0000:04:00.1: seizing device [ 0.326907] pciback 0000:04:00.2: seizing device [ 0.326997] pciback 0000:0b:03.0: seizing device [ 0.330754] PM-Timer failed consistency check (0x0xffffff) - aborting. [ 0.330830] pci 0000:05:00.0: BAR 6: no parent found for of device [0xfffe0000-0xffffffff] [ 0.331077] pci 0000:01:00.0: PCI bridge, secondary bus 0000:02 [ 0.331131] pci 0000:01:00.0: IO window: disabled [ 0.331189] pci 0000:01:00.0: MEM window: 0xd2500000-0xd25fffff [ 0.331247] pci 0000:01:00.0: PREFETCH window: disabled [ 0.331308] pci 0000:00:01.0: PCI bridge, secondary bus 0000:01 [ 0.331361] pci 0000:00:01.0: IO window: disabled [ 0.331417] pci 0000:00:01.0: MEM window: 0xd2500000-0xd25fffff [ 0.331474] pci 0000:00:01.0: PREFETCH window: disabled [ 0.331533] pciback 0000:03:00.0: PCI bridge, secondary bus 0000:04 [ 0.331586] pciback 0000:03:00.0: IO window: disabled [ 0.331645] pciback 0000:03:00.0: MEM window: 0xd2400000-0xd24fffff [ 0.331704] pciback 0000:03:00.0: PREFETCH window: disabled [ 0.331766] pci 0000:00:03.0: PCI bridge, secondary bus 0000:03 [ 0.331819] pci 0000:00:03.0: IO window: disabled [ 0.331875] pci 0000:00:03.0: MEM window: 0xd2400000-0xd24fffff [ 0.331932] pci 0000:00:03.0: PREFETCH window: disabled [ 0.331991] pci 0000:05:00.0: BAR 6: can't allocate mem resource [0xf0000000-0xefffffff] [ 0.332064] pci 0000:00:07.0: PCI bridge, secondary bus 0000:05 [ 0.332117] pci 0000:00:07.0: IO window: disabled [ 0.332173] pci 0000:00:07.0: MEM window: 0xd0000000-0xd1ffffff [ 0.332230] pci 0000:00:07.0: PREFETCH window: 0x000000e0000000-0x000000efffffff [ 0.332308] pci 0000:06:00.0: PCI bridge, secondary bus 0000:07 [ 0.332361] pci 0000:06:00.0: IO window: disabled [ 0.332422] pci 0000:06:00.0: MEM window: 0xd2300000-0xd23fffff [ 0.332481] pci 0000:06:00.0: PREFETCH window: disabled [ 0.332546] pci 0000:00:1c.0: PCI bridge, secondary bus 0000:06 [ 0.332599] pci 0000:00:1c.0: IO window: disabled [ 0.332656] pci 0000:00:1c.0: MEM window: 0xd2300000-0xd23fffff [ 0.332713] pci 0000:00:1c.0: PREFETCH window: disabled [ 0.332772] pci 0000:08:00.0: PCI bridge, secondary bus 0000:09 [ 0.332825] pci 0000:08:00.0: IO window: disabled [ 0.332886] pci 0000:08:00.0: MEM window: 0xd2200000-0xd22fffff [ 0.332945] pci 0000:08:00.0: PREFETCH window: disabled [ 0.333010] pci 0000:00:1c.1: PCI bridge, secondary bus 0000:08 [ 0.333063] pci 0000:00:1c.1: IO window: disabled [ 0.333119] pci 0000:00:1c.1: MEM window: 0xd2200000-0xd22fffff [ 0.333176] pci 0000:00:1c.1: PREFETCH window: disabled [ 0.333235] pci 0000:00:1c.4: PCI bridge, secondary bus 0000:0a [ 0.333290] pci 0000:00:1c.4: IO window: 0x1000-0x1fff [ 0.333347] pci 0000:00:1c.4: MEM window: 0xd2100000-0xd21fffff [ 0.333404] pci 0000:00:1c.4: PREFETCH window: disabled [ 0.333464] pci 0000:00:1e.0: PCI bridge, secondary bus 0000:0b [ 0.333517] pci 0000:00:1e.0: IO window: disabled [ 0.333573] pci 0000:00:1e.0: MEM window: 0xd2000000-0xd20fffff [ 0.333630] pci 0000:00:1e.0: PREFETCH window: disabled [ 0.333698] xen: registering gsi 16 triggering 0 polarity 1 [ 0.333707] alloc irq_desc for 16 on node 0 [ 0.333709] alloc kstat_irqs on node 0 [ 0.333712] xen: --> irq=16 [ 0.333743] pci 0000:00:01.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 0.333802] pci 0000:00:01.0: setting latency timer to 64 [ 0.333819] pci 0000:01:00.0: setting latency timer to 64 [ 0.333831] xen: registering gsi 16 triggering 0 polarity 1 [ 0.333833] xen_allocate_pirq: returning irq 16 for gsi 16 [ 0.333885] xen: --> irq=16 [ 0.333887] Already setup the GSI :16 [ 0.333936] pci 0000:00:03.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 0.333994] pci 0000:00:03.0: setting latency timer to 64 [ 0.334011] pciback 0000:03:00.0: setting latency timer to 64 [ 0.334023] xen: registering gsi 16 triggering 0 polarity 1 [ 0.334025] xen_allocate_pirq: returning irq 16 for gsi 16 [ 0.334078] xen: --> irq=16 [ 0.334080] Already setup the GSI :16 [ 0.334129] pci 0000:00:07.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 0.334187] pci 0000:00:07.0: setting latency timer to 64 [ 0.334199] xen: registering gsi 17 triggering 0 polarity 1 [ 0.334203] alloc irq_desc for 17 on node 0 [ 0.334205] alloc kstat_irqs on node 0 [ 0.334207] xen: --> irq=17 [ 0.334237] pci 0000:00:1c.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [ 0.334295] pci 0000:00:1c.0: setting latency timer to 64 [ 0.334318] pci 0000:06:00.0: setting latency timer to 64 [ 0.334331] xen: registering gsi 16 triggering 0 polarity 1 [ 0.334333] xen_allocate_pirq: returning irq 16 for gsi 16 [ 0.334385] xen: --> irq=16 [ 0.334387] Already setup the GSI :16 [ 0.334436] pci 0000:00:1c.1: PCI INT B -> GSI 16 (level, low) -> IRQ 16 [ 0.334495] pci 0000:00:1c.1: setting latency timer to 64 [ 0.334517] pci 0000:08:00.0: setting latency timer to 64 [ 0.334531] xen: registering gsi 17 triggering 0 polarity 1 [ 0.334532] xen_allocate_pirq: returning irq 17 for gsi 17 [ 0.334585] xen: --> irq=17 [ 0.334586] Already setup the GSI :17 [ 0.334636] pci 0000:00:1c.4: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [ 0.334694] pci 0000:00:1c.4: setting latency timer to 64 [ 0.334704] pci 0000:00:1e.0: setting latency timer to 64 [ 0.334709] pci_bus 0000:00: resource 0 io: [0x00-0xffff] [ 0.334711] pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffffffffffff] [ 0.334713] pci_bus 0000:01: resource 1 mem: [0xd2500000-0xd25fffff] [ 0.334715] pci_bus 0000:02: resource 1 mem: [0xd2500000-0xd25fffff] [ 0.334718] pci_bus 0000:03: resource 1 mem: [0xd2400000-0xd24fffff] [ 0.334720] pci_bus 0000:04: resource 1 mem: [0xd2400000-0xd24fffff] [ 0.334722] pci_bus 0000:05: resource 1 mem: [0xd0000000-0xd1ffffff] [ 0.334724] pci_bus 0000:05: resource 2 pref mem [0xe0000000-0xefffffff] [ 0.334726] pci_bus 0000:06: resource 1 mem: [0xd2300000-0xd23fffff] [ 0.334729] pci_bus 0000:07: resource 1 mem: [0xd2300000-0xd23fffff] [ 0.334731] pci_bus 0000:08: resource 1 mem: [0xd2200000-0xd22fffff] [ 0.334733] pci_bus 0000:09: resource 1 mem: [0xd2200000-0xd22fffff] [ 0.334735] pci_bus 0000:0a: resource 0 io: [0x1000-0x1fff] [ 0.334737] pci_bus 0000:0a: resource 1 mem: [0xd2100000-0xd21fffff] [ 0.334739] pci_bus 0000:0b: resource 1 mem: [0xd2000000-0xd20fffff] [ 0.334741] pci_bus 0000:0b: resource 3 io: [0x00-0xffff] [ 0.334743] pci_bus 0000:0b: resource 4 mem: [0x000000-0xffffffffffffffff] [ 0.334766] NET: Registered protocol family 2 [ 0.334960] IP route cache hash table entries: 65536 (order: 7, 524288 bytes) [ 0.335796] TCP established hash table entries: 262144 (order: 10, 4194304 bytes) [ 0.336604] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) [ 0.336815] TCP: Hash tables configured (established 262144 bind 65536) [ 0.336871] TCP reno registered [ 0.336994] NET: Registered protocol family 1 [ 0.337443] pci 0000:01:00.0: TI XIO2000a quirk detected; secondary bus fast back-to-back transfers disabled [ 0.337539] pciback 0000:03:00.0: TI XIO2000a quirk detected; secondary bus fast back-to-back transfers disabled [ 0.337690] pci 0000:05:00.0: Boot video device [ 0.337693] pci 0000:06:00.0: TI XIO2000a quirk detected; secondary bus fast back-to-back transfers disabled [ 0.337833] pci 0000:08:00.0: TI XIO2000a quirk detected; secondary bus fast back-to-back transfers disabled [ 0.338016] Trying to unpack rootfs image as initramfs... [ 0.454199] Freeing initrd memory: 230444k freed [ 0.491457] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [ 0.491520] DMA: Placing 64MB software IO TLB between ffff880012016000 - ffff880016016000 [ 0.491593] DMA: software IO TLB at phys 0x12016000 - 0x16016000 [ 0.492163] Scanning for low memory corruption every 60 seconds [ 0.492327] audit: initializing netlink socket (disabled) [ 0.492389] type=2000 audit(1273870399.766:1): initialized [ 0.499809] HugeTLB registered 2 MB page size, pre-allocated 0 pages [ 0.501106] VFS: Disk quotas dquot_6.5.2 [ 0.501205] Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 0.501735] fuse init (API version 7.13) [ 0.501854] msgmni has been set to 3870 [ 0.259594] alg: No test for stdrng (krng) [ 0.502334] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) [ 0.502407] io scheduler noop registered [ 0.502456] io scheduler anticipatory registered [ 0.502507] io scheduler deadline registered (default) [ 0.502622] io scheduler cfq registered [ 0.502907] alloc irq_desc for 2253 on node 0 [ 0.502909] alloc kstat_irqs on node 0 [ 0.502962] pcieport 0000:00:01.0: setting latency timer to 64 [ 0.503142] alloc irq_desc for 2252 on node 0 [ 0.503144] alloc kstat_irqs on node 0 [ 0.503184] pcieport 0000:00:03.0: setting latency timer to 64 [ 0.503363] alloc irq_desc for 2251 on node 0 [ 0.503365] alloc kstat_irqs on node 0 [ 0.503405] pcieport 0000:00:07.0: setting latency timer to 64 [ 0.503567] alloc irq_desc for 2250 on node 0 [ 0.503569] alloc kstat_irqs on node 0 [ 0.503608] pcieport 0000:00:1c.0: setting latency timer to 64 [ 0.503764] alloc irq_desc for 2249 on node 0 [ 0.503766] alloc kstat_irqs on node 0 [ 0.503805] pcieport 0000:00:1c.1: setting latency timer to 64 [ 0.503961] alloc irq_desc for 2248 on node 0 [ 0.503962] alloc kstat_irqs on node 0 [ 0.504002] pcieport 0000:00:1c.4: setting latency timer to 64 [ 0.504598] aer 0000:00:01.0:pcie02: service driver aer loaded [ 0.504668] aer 0000:00:03.0:pcie02: service driver aer loaded [ 0.504735] aer 0000:00:07.0:pcie02: service driver aer loaded [ 0.504744] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [ 0.504816] pciehp: PCI Express Hot Plug Controller Driver version: 0.4 [ 0.504978] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0 [ 0.505057] ACPI: Sleep Button [SLPB] [ 0.505146] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1 [ 0.505218] ACPI: Power Button [PWRF] [ 0.510481] [Firmware Bug]: ACPI: Invalid BIOS _PSS frequency: 0x80000000 MHz [ 0.510540] [Firmware Bug]: BIOS needs update for CPU frequency support [ 0.510599] processor: probe of LNXCPU:08 failed with error -14 [ 0.511100] [Firmware Bug]: ACPI: Invalid BIOS _PSS frequency: 0x80000000 MHz [ 0.511157] [Firmware Bug]: BIOS needs update for CPU frequency support [ 0.511214] processor: probe of LNXCPU:09 failed with error -14 [ 0.511709] [Firmware Bug]: ACPI: Invalid BIOS _PSS frequency: 0x80000000 MHz [ 0.511767] [Firmware Bug]: BIOS needs update for CPU frequency support [ 0.511824] processor: probe of LNXCPU:0a failed with error -14 [ 0.512320] [Firmware Bug]: ACPI: Invalid BIOS _PSS frequency: 0x80000000 MHz [ 0.512377] [Firmware Bug]: BIOS needs update for CPU frequency support [ 0.512434] processor: probe of LNXCPU:0b failed with error -14 [ 0.512939] [Firmware Bug]: ACPI: Invalid BIOS _PSS frequency: 0x80000000 MHz [ 0.512997] [Firmware Bug]: BIOS needs update for CPU frequency support [ 0.513055] processor: probe of LNXCPU:0c failed with error -14 [ 0.513550] [Firmware Bug]: ACPI: Invalid BIOS _PSS frequency: 0x80000000 MHz [ 0.513608] [Firmware Bug]: BIOS needs update for CPU frequency support [ 0.513665] processor: probe of LNXCPU:0d failed with error -14 [ 0.514159] [Firmware Bug]: ACPI: Invalid BIOS _PSS frequency: 0x80000000 MHz [ 0.514217] [Firmware Bug]: BIOS needs update for CPU frequency support [ 0.514274] processor: probe of LNXCPU:0e failed with error -14 [ 0.514766] [Firmware Bug]: ACPI: Invalid BIOS _PSS frequency: 0x80000000 MHz [ 0.514823] [Firmware Bug]: BIOS needs update for CPU frequency support [ 0.514880] processor: probe of LNXCPU:0f failed with error -14 [ 0.516894] Event-channel device installed. [ 0.517001] xen: registering gsi 19 triggering 0 polarity 1 [ 0.517011] alloc irq_desc for 19 on node 0 [ 0.517013] alloc kstat_irqs on node 0 [ 0.517016] xen: --> irq=19 [ 0.517048] pciback 0000:0b:03.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 [ 0.517110] pciback 0000:0b:03.0: PCI INT A disabled [ 0.517205] xen: registering gsi 18 triggering 0 polarity 1 [ 0.517210] alloc irq_desc for 18 on node 0 [ 0.517211] alloc kstat_irqs on node 0 [ 0.517214] xen: --> irq=18 [ 0.517243] pciback 0000:04:00.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18 [ 0.517306] pciback 0000:04:00.2: PCI INT C disabled [ 0.517397] xen: registering gsi 17 triggering 0 polarity 1 [ 0.517399] xen_allocate_pirq: returning irq 17 for gsi 17 [ 0.517452] xen: --> irq=17 [ 0.517454] Already setup the GSI :17 [ 0.517503] pciback 0000:04:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17 [ 0.517565] pciback 0000:04:00.1: PCI INT B disabled [ 0.517657] xen: registering gsi 16 triggering 0 polarity 1 [ 0.517659] xen_allocate_pirq: returning irq 16 for gsi 16 [ 0.517711] xen: --> irq=16 [ 0.517713] Already setup the GSI :16 [ 0.517762] pciback 0000:04:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 0.517824] pciback 0000:04:00.0: PCI INT A disabled [ 0.517957] pciback 0000:02:00.2: enabling device (0014 -> 0016) [ 0.518014] xen: registering gsi 18 triggering 0 polarity 1 [ 0.518016] xen_allocate_pirq: returning irq 18 for gsi 18 [ 0.518069] xen: --> irq=18 [ 0.518070] Already setup the GSI :18 [ 0.518120] pciback 0000:02:00.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18 [ 0.518181] pciback 0000:02:00.2: PCI INT C disabled [ 0.519635] pciback 0000:02:00.1: enabling device (0014 -> 0016) [ 0.519692] xen: registering gsi 17 triggering 0 polarity 1 [ 0.519694] xen_allocate_pirq: returning irq 17 for gsi 17 [ 0.519746] xen: --> irq=17 [ 0.519748] Already setup the GSI :17 [ 0.519797] pciback 0000:02:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17 [ 0.519858] pciback 0000:02:00.1: PCI INT B disabled [ 0.519951] pciback 0000:02:00.0: enabling device (0014 -> 0016) [ 0.520008] xen: registering gsi 16 triggering 0 polarity 1 [ 0.520010] xen_allocate_pirq: returning irq 16 for gsi 16 [ 0.520062] xen: --> irq=16 [ 0.520064] Already setup the GSI :16 [ 0.520113] pciback 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 0.520175] pciback 0000:02:00.0: PCI INT A disabled [ 0.522747] blktap_device_init: blktap device major 253 [ 0.522806] blktap_ring_init: blktap ring major: 252 [ 0.523300] registering netback [ 0.523382] xen-platform-pcifailed backend handshake: unrecognised magic value [ 0.523465] alloc irq_desc for 2247 on node 0 [ 0.523467] alloc kstat_irqs on node 0 [ 0.524366] alloc irq_desc for 2246 on node 0 [ 0.524368] alloc kstat_irqs on node 0 [ 0.524620] hpet_acpi_add: no address or irqs in _CRS [ 0.524682] Linux agpgart interface v0.103 [ 0.524734] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 0.524927] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a NS16550A [ 0.525900] brd: module loaded [ 0.526305] loop: module loaded [ 0.526425] input: Macintosh mouse button emulation as /devices/virtual/input/input2 [ 0.526586] ata_piix 0000:00:1f.2: version 2.13 [ 0.526605] xen: registering gsi 19 triggering 0 polarity 1 [ 0.526607] xen_allocate_pirq: returning irq 19 for gsi 19 [ 0.526659] xen: --> irq=19 [ 0.526663] Already setup the GSI :19 [ 0.526711] ata_piix 0000:00:1f.2: PCI INT A -> GSI 19 (level, low) -> IRQ 19 [ 0.526771] ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ] [ 0.526999] ata_piix 0000:00:1f.2: setting latency timer to 64 [ 0.527122] scsi0 : ata_piix [ 0.527236] scsi1 : ata_piix [ 0.527459] ata1: SATA max UDMA/133 cmd 0x2158 ctl 0x216c bmdma 0x2130 irq 19 [ 0.527519] ata2: SATA max UDMA/133 cmd 0x2150 ctl 0x2168 bmdma 0x2138 irq 19 [ 0.527595] xen: registering gsi 18 triggering 0 polarity 1 [ 0.527597] xen_allocate_pirq: returning irq 18 for gsi 18 [ 0.527649] xen: --> irq=18 [ 0.527651] Already setup the GSI :18 [ 0.527700] ata_piix 0000:00:1f.5: PCI INT B -> GSI 18 (level, low) -> IRQ 18 [ 0.527759] ata_piix 0000:00:1f.5: MAP [ P0 -- P1 -- ] [ 0.527976] ata_piix 0000:00:1f.5: setting latency timer to 64 [ 0.528097] scsi2 : ata_piix [ 0.528200] scsi3 : ata_piix [ 0.528355] ata3: SATA max UDMA/133 cmd 0x2148 ctl 0x2164 bmdma 0x2110 irq 18 [ 0.528413] ata4: SATA max UDMA/133 cmd 0x2140 ctl 0x2160 bmdma 0x2118 irq 18 [ 0.528534] xen: registering gsi 16 triggering 0 polarity 1 [ 0.528536] xen_allocate_pirq: returning irq 16 for gsi 16 [ 0.528588] xen: --> irq=16 [ 0.528590] Already setup the GSI :16 [ 0.528639] pata_acpi 0000:0a:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 0.528730] pata_acpi 0000:0a:00.0: setting latency timer to 64 [ 0.528745] pata_acpi 0000:0a:00.0: PCI INT A disabled [ 0.529011] Fixed MDIO Bus: probed [ 0.529082] PPP generic driver version 2.4.2 [ 0.529158] tun: Universal TUN/TAP device driver, 1.6 [ 0.529209] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com> [ 0.529327] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 0.529399] xen: registering gsi 18 triggering 0 polarity 1 [ 0.529401] xen_allocate_pirq: returning irq 18 for gsi 18 [ 0.529453] xen: --> irq=18 [ 0.529455] Already setup the GSI :18 [ 0.529503] ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 18 (level, low) -> IRQ 18 [ 0.529569] ehci_hcd 0000:00:1a.7: setting latency timer to 64 [ 0.529574] ehci_hcd 0000:00:1a.7: EHCI Host Controller [ 0.529653] ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1 [ 0.529762] ehci_hcd 0000:00:1a.7: debug port 1 [ 0.533692] ehci_hcd 0000:00:1a.7: cache line size of 32 is not supported [ 0.533697] ehci_hcd 0000:00:1a.7: irq 18, io mem 0xd2621000 [ 0.552543] ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00 [ 0.552723] usb usb1: configuration #1 chosen from 1 choice [ 0.552822] hub 1-0:1.0: USB hub found [ 0.552904] hub 1-0:1.0: 6 ports detected [ 0.553055] xen: registering gsi 23 triggering 0 polarity 1 [ 0.553066] alloc irq_desc for 23 on node 0 [ 0.553069] alloc kstat_irqs on node 0 [ 0.553074] xen: --> irq=23 [ 0.553109] ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23 [ 0.553197] ehci_hcd 0000:00:1d.7: setting latency timer to 64 [ 0.553203] ehci_hcd 0000:00:1d.7: EHCI Host Controller [ 0.553314] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2 [ 0.553453] ehci_hcd 0000:00:1d.7: debug port 1 [ 0.557407] ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported [ 0.557474] ehci_hcd 0000:00:1d.7: irq 23, io mem 0xd2620000 [ 0.572543] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00 [ 0.572742] usb usb2: configuration #1 chosen from 1 choice [ 0.572840] hub 2-0:1.0: USB hub found [ 0.572920] hub 2-0:1.0: 6 ports detected [ 0.573073] xen: registering gsi 18 triggering 0 polarity 1 [ 0.573077] xen_allocate_pirq: returning irq 18 for gsi 18 [ 0.573142] xen: --> irq=18 [ 0.573146] Already setup the GSI :18 [ 0.573207] ehci_hcd 0000:07:00.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18 [ 0.573296] ehci_hcd 0000:07:00.2: EHCI Host Controller [ 0.573407] ehci_hcd 0000:07:00.2: new USB bus registered, assigned bus number 3 [ 0.602553] ehci_hcd 0000:07:00.2: irq 18, io mem 0xd2300000 [ 0.622538] ehci_hcd 0000:07:00.2: USB 2.0 started, EHCI 1.00 [ 0.622698] usb usb3: configuration #1 chosen from 1 choice [ 0.622799] hub 3-0:1.0: USB hub found [ 0.622876] hub 3-0:1.0: 5 ports detected [ 0.623031] xen: registering gsi 19 triggering 0 polarity 1 [ 0.623035] xen_allocate_pirq: returning irq 19 for gsi 19 [ 0.623099] xen: --> irq=19 [ 0.623103] Already setup the GSI :19 [ 0.623165] ehci_hcd 0000:09:00.2: PCI INT C -> GSI 19 (level, low) -> IRQ 19 [ 0.623253] ehci_hcd 0000:09:00.2: EHCI Host Controller [ 0.623365] ehci_hcd 0000:09:00.2: new USB bus registered, assigned bus number 4 [ 0.652580] ehci_hcd 0000:09:00.2: irq 19, io mem 0xd2200000 [ 0.672568] ehci_hcd 0000:09:00.2: USB 2.0 started, EHCI 1.00 [ 0.672727] usb usb4: configuration #1 chosen from 1 choice [ 0.672828] hub 4-0:1.0: USB hub found [ 0.672906] hub 4-0:1.0: 5 ports detected [ 0.673049] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 0.673157] xen: registering gsi 16 triggering 0 polarity 1 [ 0.673161] xen_allocate_pirq: returning irq 16 for gsi 16 [ 0.673225] xen: --> irq=16 [ 0.673229] Already setup the GSI :16 [ 0.673290] ohci_hcd 0000:07:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 0.673379] ohci_hcd 0000:07:00.0: OHCI Host Controller [ 0.673490] ohci_hcd 0000:07:00.0: new USB bus registered, assigned bus number 5 [ 0.673663] ohci_hcd 0000:07:00.0: irq 16, io mem 0xd2302000 [ 0.762602] usb usb5: configuration #1 chosen from 1 choice [ 0.762676] hub 5-0:1.0: USB hub found [ 0.762739] hub 5-0:1.0: 3 ports detected [ 0.762845] xen: registering gsi 17 triggering 0 polarity 1 [ 0.762847] xen_allocate_pirq: returning irq 17 for gsi 17 [ 0.762899] xen: --> irq=17 [ 0.762901] Already setup the GSI :17 [ 0.762950] ohci_hcd 0000:07:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17 [ 0.763021] ohci_hcd 0000:07:00.1: OHCI Host Controller [ 0.763098] ohci_hcd 0000:07:00.1: new USB bus registered, assigned bus number 6 [ 0.763237] ohci_hcd 0000:07:00.1: irq 17, io mem 0xd2301000 [ 0.852620] usb usb6: configuration #1 chosen from 1 choice [ 0.852691] hub 6-0:1.0: USB hub found [ 0.852754] hub 6-0:1.0: 2 ports detected [ 0.852860] xen: registering gsi 17 triggering 0 polarity 1 [ 0.852863] xen_allocate_pirq: returning irq 17 for gsi 17 [ 0.852914] xen: --> irq=17 [ 0.852916] Already setup the GSI :17 [ 0.852965] ohci_hcd 0000:09:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [ 0.853035] ohci_hcd 0000:09:00.0: OHCI Host Controller [ 0.853112] ohci_hcd 0000:09:00.0: new USB bus registered, assigned bus number 7 [ 0.853198] ohci_hcd 0000:09:00.0: irq 17, io mem 0xd2202000 [ 0.884416] ata3: SATA link down (SStatus 0 SControl 300) [ 0.896230] ata4: SATA link down (SStatus 0 SControl 300) [ 0.942617] usb usb7: configuration #1 chosen from 1 choice [ 0.942688] hub 7-0:1.0: USB hub found [ 0.942753] hub 7-0:1.0: 3 ports detected [ 0.942860] xen: registering gsi 18 triggering 0 polarity 1 [ 0.942862] xen_allocate_pirq: returning irq 18 for gsi 18 [ 0.942914] xen: --> irq=18 [ 0.942916] Already setup the GSI :18 [ 0.942965] ohci_hcd 0000:09:00.1: PCI INT B -> GSI 18 (level, low) -> IRQ 18 [ 0.943035] ohci_hcd 0000:09:00.1: OHCI Host Controller [ 0.943111] ohci_hcd 0000:09:00.1: new USB bus registered, assigned bus number 8 [ 0.943198] ohci_hcd 0000:09:00.1: irq 18, io mem 0xd2201000 [ 1.032597] usb usb8: configuration #1 chosen from 1 choice [ 1.032668] hub 8-0:1.0: USB hub found [ 1.032731] hub 8-0:1.0: 2 ports detected [ 1.032823] uhci_hcd: USB Universal Host Controller Interface driver [ 1.032894] xen: registering gsi 16 triggering 0 polarity 1 [ 1.032896] xen_allocate_pirq: returning irq 16 for gsi 16 [ 1.032948] xen: --> irq=16 [ 1.032950] Already setup the GSI :16 [ 1.032999] uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 1.033060] uhci_hcd 0000:00:1a.0: setting latency timer to 64 [ 1.033064] uhci_hcd 0000:00:1a.0: UHCI Host Controller [ 1.033144] uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 9 [ 1.033242] uhci_hcd 0000:00:1a.0: irq 16, io base 0x000020c0 [ 1.033376] usb usb9: configuration #1 chosen from 1 choice [ 1.033448] hub 9-0:1.0: USB hub found [ 1.033504] hub 9-0:1.0: 2 ports detected [ 1.033595] xen: registering gsi 21 triggering 0 polarity 1 [ 1.033600] alloc irq_desc for 21 on node 0 [ 1.033602] alloc kstat_irqs on node 0 [ 1.033605] xen: --> irq=21 [ 1.033635] uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21 [ 1.033696] uhci_hcd 0000:00:1a.1: setting latency timer to 64 [ 1.033700] uhci_hcd 0000:00:1a.1: UHCI Host Controller [ 1.033783] uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 10 [ 1.033934] uhci_hcd 0000:00:1a.1: irq 21, io base 0x000020a0 [ 1.034068] usb usb10: configuration #1 chosen from 1 choice [ 1.034138] hub 10-0:1.0: USB hub found [ 1.034194] hub 10-0:1.0: 2 ports detected [ 1.034286] xen: registering gsi 19 triggering 0 polarity 1 [ 1.034288] xen_allocate_pirq: returning irq 19 for gsi 19 [ 1.034339] xen: --> irq=19 [ 1.034341] Already setup the GSI :19 [ 1.034390] uhci_hcd 0000:00:1a.2: PCI INT D -> GSI 19 (level, low) -> IRQ 19 [ 1.034450] uhci_hcd 0000:00:1a.2: setting latency timer to 64 [ 1.034454] uhci_hcd 0000:00:1a.2: UHCI Host Controller [ 1.034531] uhci_hcd 0000:00:1a.2: new USB bus registered, assigned bus number 11 [ 1.034631] uhci_hcd 0000:00:1a.2: irq 19, io base 0x00002080 [ 1.034764] usb usb11: configuration #1 chosen from 1 choice [ 1.034836] hub 11-0:1.0: USB hub found [ 1.034893] hub 11-0:1.0: 2 ports detected [ 1.034982] xen: registering gsi 23 triggering 0 polarity 1 [ 1.034984] xen_allocate_pirq: returning irq 23 for gsi 23 [ 1.035036] xen: --> irq=23 [ 1.035038] Already setup the GSI :23 [ 1.035087] uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23 [ 1.035147] uhci_hcd 0000:00:1d.0: setting latency timer to 64 [ 1.035151] uhci_hcd 0000:00:1d.0: UHCI Host Controller [ 1.035226] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 12 [ 1.035324] uhci_hcd 0000:00:1d.0: irq 23, io base 0x00002060 [ 1.035461] usb usb12: configuration #1 chosen from 1 choice [ 1.035533] hub 12-0:1.0: USB hub found [ 1.035590] hub 12-0:1.0: 2 ports detected [ 1.035680] xen: registering gsi 19 triggering 0 polarity 1 [ 1.035682] xen_allocate_pirq: returning irq 19 for gsi 19 [ 1.035733] xen: --> irq=19 [ 1.035736] Already setup the GSI :19 [ 1.035784] uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19 [ 1.035844] uhci_hcd 0000:00:1d.1: setting latency timer to 64 [ 1.035848] uhci_hcd 0000:00:1d.1: UHCI Host Controller [ 1.035924] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 13 [ 1.037379] uhci_hcd 0000:00:1d.1: irq 19, io base 0x00002040 [ 1.037514] usb usb13: configuration #1 chosen from 1 choice [ 1.037585] hub 13-0:1.0: USB hub found [ 1.037641] hub 13-0:1.0: 2 ports detected [ 1.037730] xen: registering gsi 18 triggering 0 polarity 1 [ 1.037732] xen_allocate_pirq: returning irq 18 for gsi 18 [ 1.037784] xen: --> irq=18 [ 1.037786] Already setup the GSI :18 [ 1.037835] uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18 [ 1.037895] uhci_hcd 0000:00:1d.2: setting latency timer to 64 [ 1.037899] uhci_hcd 0000:00:1d.2: UHCI Host Controller [ 1.037978] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 14 [ 1.038076] uhci_hcd 0000:00:1d.2: irq 18, io base 0x00002020 [ 1.038211] usb usb14: configuration #1 chosen from 1 choice [ 1.038282] hub 14-0:1.0: USB hub found [ 1.038339] hub 14-0:1.0: 2 ports detected [ 1.038460] PNP: No PS/2 controller found. Probing ports directly. [ 1.041586] serio: i8042 KBD port at 0x60,0x64 irq 1 [ 1.041641] serio: i8042 AUX port at 0x60,0x64 irq 12 [ 1.041760] mice: PS/2 mouse device common for all mice [ 1.041887] rtc_cmos 00:02: RTC can wake from S4 [ 1.041966] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0 [ 1.042089] rtc0: alarms up to one month, y3k, 114 bytes nvram [ 1.042148] md: raid1 personality registered for level 1 [ 1.042277] device-mapper: uevent: version 1.0.3 [ 1.042411] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com [ 1.042708] device-mapper: multipath: version 1.1.0 loaded [ 1.042762] device-mapper: multipath round-robin: version 1.0.0 loaded [ 1.043228] cpuidle: using governor ladder [ 1.043282] cpuidle: using governor menu [ 1.043621] TCP cubic registered [ 1.043757] NET: Registered protocol family 10 [ 1.044204] lo: Disabled Privacy Extensions [ 1.044471] NET: Registered protocol family 17 [ 1.044651] PM: Resume from disk failed. [ 1.044660] registered taskstats version 1 [ 1.045994] Magic number: 10:506:902 [ 1.046113] rtc_cmos 00:02: setting system clock to 2010-05-14 20:53:19 UTC (1273870399) [ 1.046186] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found [ 1.046238] EDD information not available. [ 1.352495] usb 14-1: new full speed USB device using uhci_hcd and address 2 [ 1.402593] ata2.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 1.402682] ata2.01: SATA link down (SStatus 0 SControl 300) [ 1.403005] ata1.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 1.403097] ata1.01: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 1.423775] ata2.00: ATA-8: WDC WD2502ABYS-02B7A0, 02.03B03, max UDMA/133 [ 1.423844] ata2.00: 490350672 sectors, multi 16: LBA48 NCQ (depth 0/32) [ 1.443718] ata1.00: ATA-8: WDC WD2502ABYS-02B7A0, 02.03B03, max UDMA/133 [ 1.443787] ata1.00: 490350672 sectors, multi 16: LBA48 NCQ (depth 0/32) [ 1.443881] ata1.01: ATAPI: PIONEER DVD-RW DVR-218L, 1.02, max UDMA/100 [ 1.463820] ata2.00: configured for UDMA/133 [ 1.483769] ata1.00: configured for UDMA/133 [ 1.522772] ata1.01: configured for UDMA/100 [ 1.282953] scsi 0:0:0:0: Direct-Access ATA WDC WD2502ABYS-0 02.0 PQ: 0 ANSI: 5 [ 1.283221] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 1.282305] sd 0:0:0:0: [sda] 490350672 512-byte logical blocks: (251 GB/233 GiB) [ 1.282392] sd 0:0:0:0: [sda] Write Protect is off [ 1.282397] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 1.282440] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 1.287803] scsi 0:0:1:0: CD-ROM PIONEER DVD-RW DVR-218L 1.02 PQ: 0 ANSI: 5 [ 1.286847] sda: [ 1.537220] usb 14-1: configuration #1 chosen from 1 choice [ 1.538897] sda1 sda2 sda3 [ 1.539269] hub 14-1:1.0: USB hub found [ 1.541146] hub 14-1:1.0: 3 ports detected [ 1.314108] sr0: scsi3-mmc drive: 40x/40x writer dvd-ram cd/rw xa/form2 cdda tray [ 1.314197] Uniform CD-ROM driver Revision: 3.20 [ 1.556319] sd 0:0:0:0: [sda] Attached SCSI disk [ 1.314421] sr 0:0:1:0: Attached scsi CD-ROM sr0 [ 1.314478] sr 0:0:1:0: Attached scsi generic sg1 type 5 [ 1.556796] scsi 1:0:0:0: Direct-Access ATA WDC WD2502ABYS-0 02.0 PQ: 0 ANSI: 5 [ 1.314917] sd 1:0:0:0: [sdb] 490350672 512-byte logical blocks: (251 GB/233 GiB) [ 1.557040] sd 1:0:0:0: Attached scsi generic sg2 type 0 [ 1.315154] sd 1:0:0:0: [sdb] Write Protect is off [ 1.315219] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 [ 1.315264] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 1.315573] sdb: sdb1 sdb2 sdb3 [ 1.568532] sd 1:0:0:0: [sdb] Attached SCSI disk [ 1.568726] Freeing unused kernel memory: 816k freed [ 1.568956] Write protecting the kernel read-only data: 7904k [ 1.864075] usb 14-1.1: new full speed USB device using uhci_hcd and address 3 [ 2.056045] usb 14-1.1: configuration #1 chosen from 1 choice [ 1.818189] e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2 [ 1.818245] e1000e: Copyright (c) 1999-2008 Intel Corporation. [ 1.818344] xen: registering gsi 20 triggering 0 polarity 1 [ 1.818354] alloc irq_desc for 20 on node 0 [ 1.818356] alloc kstat_irqs on node 0 [ 1.818359] xen: --> irq=20 [ 1.818393] e1000e 0000:00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20 [ 1.818456] e1000e 0000:00:19.0: setting latency timer to 64 [ 1.818582] alloc irq_desc for 2245 on node 0 [ 1.818583] alloc kstat_irqs on node 0 [ 1.849345] ahci 0000:0a:00.0: version 3.0 [ 1.850758] xen: registering gsi 16 triggering 0 polarity 1 [ 1.850760] xen_allocate_pirq: returning irq 16 for gsi 16 [ 1.850820] xen: --> irq=16 [ 1.850824] Already setup the GSI :16 [ 1.850876] pata_marvell 0000:0a:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 1.850975] pata_marvell 0000:0a:00.0: setting latency timer to 64 [ 1.851053] scsi4 : pata_marvell [ 1.851160] scsi5 : pata_marvell [ 1.851235] ata5: PATA max UDMA/100 cmd 0x1018 ctl 0x1024 bmdma 0x1000 irq 16 [ 1.851294] ata6: PATA max UDMA/133 cmd 0x1010 ctl 0x1020 bmdma 0x1008 irq 16 [ 2.224891] 0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1) 00:1c:c0:b2:11:1d [ 2.224975] 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection [ 2.225062] 0000:00:19.0: eth0: MAC: 7, PHY: 8, PBA No: ffffff-0ff [ 2.246745] usbcore: registered new interface driver hiddev [ 2.249535] input: Mitsumi Electric Apple Extended USB Keyboard as /devices/pci0000:00/0000:00:1d.2/usb14/14-1/14-1.1/14-1.1:1.0/input/input3 [ 2.249675] generic-usb 0003:05AC:0204.0001: input,hidraw0: USB HID v1.10 Keyboard [Mitsumi Electric Apple Extended USB Keyboard] on usb-0000:00:1d.2-1.1/input0 [ 2.253398] input: Mitsumi Electric Apple Extended USB Keyboard as /devices/pci0000:00/0000:00:1d.2/usb14/14-1/14-1.1/14-1.1:1.1/input/input4 [ 2.253521] generic-usb 0003:05AC:0204.0002: input,hidraw1: USB HID v1.10 Device [Mitsumi Electric Apple Extended USB Keyboard] on usb-0000:00:1d.2-1.1/input1 [ 2.253632] usbcore: registered new interface driver usbhid [ 2.253684] usbhid: v2.6:USB HID core driver [ 2.370330] md: raid0 personality registered for level 0 [ 2.397129] md: md0 stopped. [ 2.653428] md: bind<sdb1> [ 2.653683] md: bind<sda1> [ 2.660556] raid1: raid set md0 active with 2 out of 2 mirrors [ 2.660635] md0: detected capacity change from 0 to 8003059712 [ 2.660990] md: md1 stopped. [ 2.661138] md0: unknown partition table [ 2.714120] md: bind<sdb2> [ 2.714414] md: bind<sda2> [ 2.723526] raid1: raid set md1 active with 2 out of 2 mirrors [ 2.723618] md1: detected capacity change from 0 to 241000579072 [ 2.724126] md: md2 stopped. [ 2.724356] md1: unknown partition table [ 2.769574] md: bind<sdb3> [ 2.773297] md: bind<sda3> [ 2.783028] raid0: looking at sda3 [ 2.783092] raid0: comparing sda3(4000000) [ 2.783137] with sda3(4000000) [ 2.783246] raid0: END [ 2.783304] raid0: ==> UNIQUE [ 2.783363] raid0: 1 zones [ 2.783421] raid0: looking at sdb3 [ 2.783481] raid0: comparing sdb3(4000000) [ 2.783526] with sda3(4000000) [ 2.783635] raid0: EQUAL [ 2.783693] raid0: FINAL 1 zones [ 2.783754] raid0: done. [ 2.783812] raid0 : md_size is 8000000 sectors. [ 2.783874] ******* md2 configuration ********* [ 2.783936] zone0=[sda3/sdb3/] [ 2.784101] zone offset=0kb device offset=0kb size=4000000kb [ 2.784167] ********************************** [ 2.784168] [ 2.784290] md2: detected capacity change from 0 to 4096000000 [ 2.784732] md2: unknown partition table [ 2.660667] PM: Starting manual resume from disk [ 2.660718] PM: Resume from partition 9:2 [ 2.660720] PM: Checking hibernation image. [ 2.904980] PM: Error -22 checking image file [ 2.904982] PM: Resume from disk failed. [ 2.711245] kjournald starting. Commit interval 5 seconds [ 2.956568] EXT3-fs: mounted filesystem with ordered data mode. [ 3.740403] udevd version 125 started [ 4.738670] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 5.071182] input: PC Speaker as /devices/platform/pcspkr/input/input5 [ 5.087723] xen: registering gsi 18 triggering 0 polarity 1 [ 5.087726] xen_allocate_pirq: returning irq 18 for gsi 18 [ 5.087781] xen: --> irq=18 [ 5.087785] Already setup the GSI :18 [ 5.087836] i801_smbus 0000:00:1f.3: PCI INT B -> GSI 18 (level, low) -> IRQ 18 [ 5.112451] xen: registering gsi 22 triggering 0 polarity 1 [ 5.112461] alloc irq_desc for 22 on node 0 [ 5.112463] alloc kstat_irqs on node 0 [ 5.112466] xen: --> irq=22 [ 5.112499] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22 [ 5.112665] HDA Intel 0000:00:1b.0: setting latency timer to 64 [ 5.122022] Error: Driver 'pcspkr' is already registered, aborting... [ 5.262265] Error: Driver 'pcspkr' is already registered, aborting... [ 5.516255] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input6 [ 6.390738] Adding 3999992k swap on /dev/md2. Priority:-1 extents:1 across:3999992k [ 6.500494] EXT3 FS on md0, internal journal [ 9.952882] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 11.666735] Bridge firewalling registered [ 12.092219] ADDRCONF(NETDEV_UP): peth0: link is not ready [ 16.062225] e1000e: peth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX [ 16.062785] ADDRCONF(NETDEV_CHANGE): peth0: link becomes ready [ 15.917421] device peth0 entered promiscuous mode [ 15.955423] eth0: port 1(peth0) entering forwarding state [ 19.537450] alloc irq_desc for 2244 on node 0 [ 19.537454] alloc kstat_irqs on node 0 [ 19.537511] alloc irq_desc for 2243 on node 0 [ 19.537515] alloc kstat_irqs on node 0 [ 19.765345] XENBUS: Unable to read cpu state [ 19.765616] XENBUS: Unable to read cpu state [ 19.765859] XENBUS: Unable to read cpu state [ 19.766134] XENBUS: Unable to read cpu state [ 19.768061] XENBUS: Unable to read cpu state [ 19.768340] XENBUS: Unable to read cpu state [ 19.768593] XENBUS: Unable to read cpu state [ 19.768823] XENBUS: Unable to read cpu state [ 22.803502] alloc irq_desc for 2242 on node 0 [ 22.803505] alloc kstat_irqs on node 0 02:00.0 USB Controller: NEC Corporation USB (rev 43) (prog-if 10 [OHCI]) Subsystem: NEC Corporation Hama USB 2.0 CardBus Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Interrupt: pin A routed to IRQ 16 Region 0: Memory at d2500000 (32-bit, non-prefetchable) [disabled] [size=4K] Capabilities: [40] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: pciback 02:00.1 USB Controller: NEC Corporation USB (rev 43) (prog-if 10 [OHCI]) Subsystem: NEC Corporation Hama USB 2.0 CardBus Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Interrupt: pin B routed to IRQ 17 Region 0: Memory at d2501000 (32-bit, non-prefetchable) [disabled] [size=4K] Capabilities: [40] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: pciback 02:00.2 USB Controller: NEC Corporation USB 2.0 (rev 04) (prog-if 20 [EHCI]) Subsystem: NEC Corporation USB 2.0 Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Interrupt: pin C routed to IRQ 18 Region 0: Memory at d2502000 (32-bit, non-prefetchable) [disabled] [size=4K] Capabilities: [40] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: pciback [-- Attachment #4: 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] 32+ messages in thread
* RE: [Xen-devel] Re: RE: Xen4 / Intel DX58SO Mobo / VT-d not working 2010-05-14 21:17 ` [Xen-users] " chris @ 2010-05-16 7:36 ` Han, Weidong 2010-05-16 13:00 ` chris 0 siblings, 1 reply; 32+ messages in thread From: Han, Weidong @ 2010-05-16 7:36 UTC (permalink / raw) To: chris, Pasi Kärkkäinen; +Cc: Xen-Devel List, Xen-Users List I noticed this line " (XEN) domctl.c:853:d0 XEN_DOMCTL_assign_device: assign device (2:0.0) failed" in NOTWORKING.txt. could you add some logs to intel_iommu_assign_device to know where it fails? I prefer you to use a clean Xen 4.0 environment. Regards, Weidong -----Original Message----- From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of chris Sent: Saturday, May 15, 2010 5:18 AM To: Pasi Kärkkäinen Cc: Xen-Devel List; Xen-Users List Subject: [Xen-devel] Re: [Xen-users] RE: Xen4 / Intel DX58SO Mobo / VT-d not working Played around with xen_platform_pc, pci_msitranslate, pci_power_mgmt in the cfg, none of which seem to have any effect, also tried pci=resource_alignment=02:00.0;02:00.1;02:00.2 on dom0 cmdline, no effect. I'm worn out been fighting this all day. Attached is some various output from the machine that works with the same cards and has Xen 3.4.2 and the new machine with 4.0 which doesn't work. I'm hoping this information can get the right attention and we can figure it out :( - chris On Fri, May 14, 2010 at 4:50 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > On Fri, May 14, 2010 at 04:39:54PM -0400, chris wrote: >> Alright so a pci sound card works, I tried a geforce 8600 pci e card >> and while vga passthrough didnt work it did seem to attach to the >> domain ok. So I guess the problem must be somehow related to the >> device. I'm still confused since it works in another box. >> >> I remember there was some reassign_resources or something, maybe the >> issue is with some resources the card uses? >> > > http://wiki.xensource.com/xenwiki/XenPCIpassthrough > > -- Pasi > >> Below is a lspci -vv of the card >> >> 02:00.0 USB Controller: NEC Corporation USB (rev 43) (prog-if 10 >> [OHCI]) >> Subsystem: NEC Corporation Hama USB 2.0 CardBus >> Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- >> ParErr- Stepping- SERR- FastB2B- DisINTx- >> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >> >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- >> Interrupt: pin A routed to IRQ 16 >> Region 0: Memory at d2502000 (32-bit, non-prefetchable) >> [disabled] [size=4K] >> Capabilities: [40] Power Management version 2 >> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA >> PME(D0+,D1+,D2+,D3hot+,D3cold-) >> Status: D0 PME-Enable- DSel=0 DScale=0 PME- >> Kernel driver in use: pciback >> >> 02:00.1 USB Controller: NEC Corporation USB (rev 43) (prog-if 10 >> [OHCI]) >> Subsystem: NEC Corporation Hama USB 2.0 CardBus >> Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- >> ParErr- Stepping- SERR- FastB2B- DisINTx- >> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >> >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- >> Interrupt: pin B routed to IRQ 17 >> Region 0: Memory at d2501000 (32-bit, non-prefetchable) >> [disabled] [size=4K] >> Capabilities: [40] Power Management version 2 >> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA >> PME(D0+,D1+,D2+,D3hot+,D3cold-) >> Status: D0 PME-Enable- DSel=0 DScale=0 PME- >> Kernel driver in use: pciback >> >> 02:00.2 USB Controller: NEC Corporation USB 2.0 (rev 04) (prog-if 20 >> [EHCI]) >> Subsystem: NEC Corporation USB 2.0 >> Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- >> ParErr- Stepping- SERR- FastB2B- DisINTx- >> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >> >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- >> Interrupt: pin C routed to IRQ 18 >> Region 0: Memory at d2500000 (32-bit, non-prefetchable) >> [disabled] [size=256] >> Capabilities: [40] Power Management version 2 >> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA >> PME(D0+,D1+,D2+,D3hot+,D3cold-) >> Status: D0 PME-Enable- DSel=0 DScale=0 PME- >> Kernel driver in use: pciback >> >> >> On Fri, May 14, 2010 at 3:46 PM, chris <tknchris@gmail.com> wrote: >> > I added a pci sound card and interestingly that works. I'm digging >> > around for another pci-e device to try to identify if its all pci-e >> > or only this device. Strange this is that I have a few other >> > machines with this same usb controller which is working on 3.4.2. >> > >> > *scratches head* >> > >> > - chris >> > >> > On Fri, May 14, 2010 at 3:21 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >> >> On Fri, May 14, 2010 at 03:18:02PM -0400, chris wrote: >> >>> It is a multifunction device, a pci-e usb controller, so I >> >>> assumed all them had to be passed through. I just changed it to >> >>> only 02:00.0 and same thing >> >>> >> >>> test-box2:~# cat /etc/xen/vm-five.cfg | grep pci pci = >> >>> ['02:00.0'] test-box2:~# xm create /etc/xen/vm-five.cfg Using >> >>> config file "/etc/xen/vm-five.cfg". >> >>> Error: Failed to assign device to IOMMU >> >>> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >> >>> >> >> >> >> Hmm.. weird. >> >> >> >> Two things to try: >> >> >> >> 1) Try passthru some other device (which is just a single pci id) >> >> 2) Try passthru that pci-e usb controller to Linux PV guest and >> >> see if that works >> >> >> >> -- Pasi >> >> >> >>> >> >>> On Fri, May 14, 2010 at 3:11 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >> >>> > On Fri, May 14, 2010 at 03:05:49PM -0400, chris wrote: >> >>> >> Pasi, >> >>> >> >> >>> >> Tried latest stable/2.6.32.x per your advice, no change. >> >>> >> Anyone on xen-devel that can help me troubleshoot further? >> >>> >> Everything looks right, can't figure out why vt-d is not >> >>> >> working but it must be some kind of bug :( >> >>> >> >> >>> > >> >>> > Did you try the suggestion said earlier.. try to just passthru the first pci device? >> >>> > >> >>> > -- Pasi >> >>> > >> >>> >> test-box2:~# uname -a >> >>> >> Linux test-box2 2.6.32.12 #1 SMP Fri May 14 13:40:05 EDT 2010 >> >>> >> x86_64 GNU/Linux >> >>> >> >> >>> >> test-box2:~# xm info | grep virt_caps virt_caps : >> >>> >> hvm hvm_directio >> >>> >> >> >>> >> test-box2:~# xm pci-list-assignable-devices 0000:02:00.0 >> >>> >> 0000:02:00.1 >> >>> >> 0000:02:00.2 >> >>> >> >> >>> >> test-box2:~# xm create /etc/xen/vm-five.cfg Using config file >> >>> >> "/etc/xen/vm-five.cfg". >> >>> >> Error: Failed to assign device to IOMMU >> >>> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >> >>> >> >> >>> >> test-box2:~# cat /etc/xen/vm-five.cfg | grep -v '#' >> >>> >> kernel = '/usr/lib/xen/boot/hvmloader' >> >>> >> builder = 'hvm' >> >>> >> memory = '1792' >> >>> >> device_model='/usr/lib/xen/bin/qemu-dm' >> >>> >> disk = [ 'phy:/dev/storage/vm-five,ioemu:hda,w', >> >>> >> 'phy:/dev/sr0,ioemu:hdc:cdrom,r' >> >>> >> ] >> >>> >> name = 'vm-five' >> >>> >> vif = ['type=ioemu, bridge=eth0, mac=00:16:3D:37:A1:42'] >> >>> >> boot='dc' >> >>> >> cpus='0-1' >> >>> >> vcpus=2 >> >>> >> acpi=1 >> >>> >> ahci=1 >> >>> >> vnc=1 >> >>> >> sdl=0 >> >>> >> timer_mode=1 >> >>> >> usb=1 >> >>> >> usbdevice='tablet' >> >>> >> localtime=1 >> >>> >> pci = ['02:00.0','02:00.1','02:00.2'] >> >>> >> >> >>> >> On Thu, May 13, 2010 at 2:28 PM, chris <tknchris@gmail.com> wrote: >> >>> >> > Forwarding to xen-devel. Can't seem to get VT-d working with >> >>> >> > xen4 from tarball on xen.org 2.6.31.13 pv_ops dom0. On >> >>> >> > pasi's advice I tried switching to stable/2.6.32.x branch >> >>> >> > for dom0 and that doesnt even build. Did something change recently thats breaking compilation? >> >>> >> > >> >>> >> > Attached is xen dmesg with iommu=verbose loglvl=all >> >>> >> > guest_loglvl=all, and dom0 dmesg from 2.6.31.x >> >>> >> > >> >>> >> > Any ideas on why VT-d is not working on this board? >> >>> >> > Initialization looks good, xen reports hvm_directio >> >>> >> > capability, everything says VT-d should work until domain is created. >> >>> >> > >> >>> >> > Any ideas why stable/2.6.32.x wont build? >> >>> >> > >> >>> >> > - chris >> >>> >> > >> >>> >> > On Thu, May 13, 2010 at 2:07 PM, chris <tknchris@gmail.com> wrote: >> >>> >> >> I redid it with oldconfig which I didn't think would help >> >>> >> >> and same thing. I guess this tree is broken? Can someone >> >>> >> >> else try and see if they can build it? Ugh, whata day :) >> >>> >> >> >> >>> >> >> On Thu, May 13, 2010 at 1:58 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >> >>> >> >>> On Thu, May 13, 2010 at 01:55:25PM -0400, chris wrote: >> >>> >> >>>> I used the default config on the wiki which you created. Steps I took were: >> >>> >> >>>> >> >>> >> >>>> # make clean distclean >> >>> >> >>>> # wget -O .config >> >>> >> >>>> "http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.10-pvops-dom0-xen-stable-x86_64" >> >>> >> >>> >> >>> >> >>> You should do "make oldconfig" at this point. >> >>> >> >>> >> >>> >> >>>> # make -j8 bzImage >> >>> >> >>>> (blah blah) >> >>> >> >>>> LD vmlinux.o >> >>> >> >>>> MODPOST vmlinux.o >> >>> >> >>>> WARNING: modpost: Found 7 section mismatch(es). >> >>> >> >>>> To see full details build your kernel with: >> >>> >> >>>> 'make CONFIG_DEBUG_SECTION_MISMATCH=y' >> >>> >> >>>> GEN .version >> >>> >> >>>> CHK include/linux/compile.h >> >>> >> >>>> UPD include/linux/compile.h >> >>> >> >>>> CC init/version.o >> >>> >> >>>> LD init/built-in.o >> >>> >> >>>> LD .tmp_vmlinux1 >> >>> >> >>>> drivers/built-in.o: In function `do_hvm_suspend': >> >>> >> >>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: >> >>> >> >>>> undefined reference to `xenbus_suspend' >> >>> >> >>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: >> >>> >> >>>> undefined reference to `xenbus_resume' >> >>> >> >>>> make: *** [.tmp_vmlinux1] Error 1 >> >>> >> >>>> >> >>> >> >>> >> >>> >> >>> Hmm.. weird. I wonder if something has changed recently or what's going on in here.. >> >>> >> >>> >> >>> >> >>> -- Pasi >> >>> >> >>> >> >>> >> >>>> >> >>> >> >>>> On Thu, May 13, 2010 at 11:47 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >> >>> >> >>>> > On Thu, May 13, 2010 at 11:33:57AM -0400, chris wrote: >> >>> >> >>>> >> Successfully grabbed the sources and failed to build: >> >>> >> >>>> >> >> >>> >> >>>> >> LD .tmp_vmlinux1 >> >>> >> >>>> >> drivers/built-in.o: In function `do_hvm_suspend': >> >>> >> >>>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: >> >>> >> >>>> >> undefined reference to `xenbus_suspend' >> >>> >> >>>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: >> >>> >> >>>> >> undefined reference to `xenbus_resume' >> >>> >> >>>> >> make: *** [.tmp_vmlinux1] Error 1 >> >>> >> >>>> >> >> >>> >> >>>> >> :( >> >>> >> >>>> >> >> >>> >> >>>> > >> >>> >> >>>> > Try the example .config files provided on the wiki page. >> >>> >> >>>> > >> >>> >> >>>> > -- Pasi >> >>> >> >>>> > >> >>> >> >>>> >> On Thu, May 13, 2010 at 10:14 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >> >>> >> >>>> >> > On Thu, May 13, 2010 at 10:12:56AM -0400, chris wrote: >> >>> >> >>>> >> >> Pasi, >> >>> >> >>>> >> >> >> >>> >> >>>> >> >> How do I pull those kernel sources you referenced? >> >>> >> >>>> >> >> I see it mentioned on >> >>> >> >>>> >> >> http://wiki.xensource.com/xenwiki/XenParavirtOps but no details on how to retrieve it. >> >>> >> >>>> >> >> >> >>> >> >>>> >> > >> >>> >> >>>> >> > The instructions are there if you read it carefully.. >> >>> >> >>>> >> > There's the topic of how to switch branches. >> >>> >> >>>> >> > >> >>> >> >>>> >> > -- Pasi >> >>> >> >>>> >> > >> >>> >> >>>> >> >> - chris >> >>> >> >>>> >> >> >> >>> >> >>>> >> >> On Thu, May 13, 2010 at 8:29 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >> >>> >> >>>> >> >> > On Wed, May 12, 2010 at 08:41:34PM -0400, chris wrote: >> >>> >> >>>> >> >> >> When reading the vtdhowto I noticed the ability to set iommu=verbose. >> >>> >> >>>> >> >> >> Here is that output, I don't know if it helps at >> >>> >> >>>> >> >> >> all to figure out what is wrong. >> >>> >> >>>> >> >> >> >> >>> >> >>>> >> >> > >> >>> >> >>>> >> >> > That seems to be OK: >> >>> >> >>>> >> >> > >> >>> >> >>>> >> >> > (XEN) I/O virtualisation enabled >> >>> >> >>>> >> >> > (XEN) I/O virtualisation for PV guests disabled >> >>> >> >>>> >> >> > >> >>> >> >>>> >> >> > So hmm.. I wonder if it's related to MSI stuff? >> >>> >> >>>> >> >> > You could try xen.git xen/stable-2.6.32.x branch instead and see if that makes a difference.. >> >>> >> >>>> >> >> > >> >>> >> >>>> >> >> > -- Pasi >> >>> >> >>>> >> >> > >> >>> >> >>>> >> >> >> >> >>> >> >>>> >> >> >> ---------- Forwarded message ---------- >> >>> >> >>>> >> >> >> From: chris <tknchris@gmail.com> >> >>> >> >>>> >> >> >> Date: Wed, May 12, 2010 at 5:28 PM >> >>> >> >>>> >> >> >> Subject: Xen4 / Intel DX58SO Mobo / VT-d not >> >>> >> >>>> >> >> >> working >> >>> >> >>>> >> >> >> To: Xen-Users List >> >>> >> >>>> >> >> >> <xen-users@lists.xensource.com> >> >>> >> >>>> >> >> >> >> >>> >> >>>> >> >> >> >> >>> >> >>>> >> >> >> Hello, >> >>> >> >>>> >> >> >> >> >>> >> >>>> >> >> >> I've previously been successful with Xen4 and >> >>> >> >>>> >> >> >> VT-d on other systems. I am having trouble >> >>> >> >>>> >> >> >> getting VT-d passthrough working to a WinXP >> >>> >> >>>> >> >> >> domain with DX58SO (Q45) motherboard and i7 930 >> >>> >> >>>> >> >> >> CPU. VT-d is enabled in bios, xm info shows >> >>> >> >>>> >> >> >> hvm_directio capability, I have iommu=1 set, I >> >>> >> >>>> >> >> >> have the devices bound to pciback on dom0 cmdline, xm pci-list-assignable-devices shows the devices as assignable. When I attempt to start the VM I get the error: >> >>> >> >>>> >> >> >> >> >>> >> >>>> >> >> >> Error: Failed to assign device to IOMMU >> >>> >> >>>> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >> >>> >> >>>> >> >> >> >> >>> >> >>>> >> >> >> Below is all the information I can think of that >> >>> >> >>>> >> >> >> would be useful to help debug it: >> >>> >> >>>> >> >> >> >> >>> >> >>>> >> >> >> BIOS VT-d Enabled: >> >>> >> >>>> >> >> >> http://i43.tinypic.com/nl3a5e.jpg >> >>> >> >>>> >> >> >> http://i42.tinypic.com/nqvlu1.jpg >> >>> >> >>>> >> >> >> >> >>> >> >>>> >> >> >> grub entry: >> >>> >> >>>> >> >> >> >> >>> >> >>>> >> >> >> title Xen 4.0.0 / Debian GNU/Linux, >> >>> >> >>>> >> >> >> kernel 2.6.31.13 root (hd0,0) kernel >> >>> >> >>>> >> >> >> /boot/xen-4.0.0.gz iommu=1 dom0_mem=256M >> >>> >> >>>> >> >> >> dom0_max_vcpus=1 dom0_vcpus_pin=true module >> >>> >> >>>> >> >> >> /boot/vmlinuz-2.6.31.13 root=/dev/md0 ro >> >>> >> >>>> >> >> >> console=tty0 xen-pciback.permissive >> >>> >> >>>> >> >> >> xen-pciback.hide=(02:00.0)(02:00.1)(02:00.2)(04: >> >>> >> >>>> >> >> >> 00.0)(04:00.1)(04:00.2)(07:00.0)(07:00.1)(07:00. >> >>> >> >>>> >> >> >> 2)(09:00.0)(09:00.1)(09:00.2) module >> >>> >> >>>> >> >> >> /boot/initrd.img-2.6.31.13 >> >>> >> >>>> >> >> >> >> >>> >> >>>> >> >> >> # xm pci-list-assignable-devices 0000:09:00.0 >> >>> >> >>>> >> >> >> 0000:09:00.1 >> >>> >> >>>> >> >> >> 0000:09:00.2 >> >>> >> >>>> >> >> >> 0000:07:00.0 >> >>> >> >>>> >> >> >> 0000:07:00.1 >> >>> >> >>>> >> >> >> 0000:07:00.2 >> >>> >> >>>> >> >> >> 0000:04:00.0 >> >>> >> >>>> >> >> >> 0000:04:00.1 >> >>> >> >>>> >> >> >> 0000:04:00.2 >> >>> >> >>>> >> >> >> 0000:02:00.0 >> >>> >> >>>> >> >> >> 0000:02:00.1 >> >>> >> >>>> >> >> >> 0000:02:00.2 >> >>> >> >>>> >> >> >> >> >>> >> >>>> >> >> >> # xm info >> >>> >> >>>> >> >> >> host : test-box2 release >> >>> >> >>>> >> >> >> : 2.6.31.13 version : #2 SMP Wed >> >>> >> >>>> >> >> >> May 12 14:11:37 EDT 2010 machine >> >>> >> >>>> >> >> >> : x86_64 nr_cpus : 8 nr_nodes >> >>> >> >>>> >> >> >> : 1 cores_per_socket : 4 threads_per_core >> >>> >> >>>> >> >> >> : 2 cpu_mhz : 2800 hw_caps >> >>> >> >>>> >> >> >> : >> >>> >> >>>> >> >> >> bfebfbff:28100800:00000000:00001b40:0098e3bd:000 >> >>> >> >>>> >> >> >> 00000:00000001:00000000 virt_caps : >> >>> >> >>>> >> >> >> hvm hvm_directio total_memory : 7950 >> >>> >> >>>> >> >> >> free_memory : 7812 node_to_cpu >> >>> >> >>>> >> >> >> : node0:0-7 node_to_memory : node0:7812 >> >>> >> >>>> >> >> >> node_to_dma32_mem : node0:3249 max_node_id >> >>> >> >>>> >> >> >> : 0 xen_major : 4 xen_minor >> >>> >> >>>> >> >> >> : 0 xen_extra : .0 xen_caps >> >>> >> >>>> >> >> >> : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 >> >>> >> >>>> >> >> >> hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler >> >>> >> >>>> >> >> >> : credit xen_pagesize : 4096 >> >>> >> >>>> >> >> >> platform_params : >> >>> >> >>>> >> >> >> virt_start=0xffff800000000000 xen_changeset >> >>> >> >>>> >> >> >> : unavailable xen_commandline : iommu=1 >> >>> >> >>>> >> >> >> dom0_mem=256M dom0_max_vcpus=1 >> >>> >> >>>> >> >> >> dom0_vcpus_pin=true cc_compiler : gcc >> >>> >> >>>> >> >> >> version 4.3.2 (Debian 4.3.2-1.1) cc_compile_by >> >>> >> >>>> >> >> >> : root cc_compile_domain : >> >>> >> >>>> >> >> >> cc_compile_date : Thu May 6 13:41:25 EDT >> >>> >> >>>> >> >> >> 2010 xend_config_format : 4 >> >>> >> >>>> >> >> >> >> >>> >> >>>> >> >> >> # xm create vm-five.cfg Using config file >> >>> >> >>>> >> >> >> "./vm-five.cfg". >> >>> >> >>>> >> >> >> Error: Failed to assign device to IOMMU >> >>> >> >>>> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >> >>> >> >>>> >> >> >> >> >>> >> >>>> >> >> >> I feel like I'm missing something really obvious >> >>> >> >>>> >> >> >> but I've been at it for a while now and have run >> >>> >> >>>> >> >> >> out of brain power. Anyone have any idea what might be wrong? >> >>> >> >>>> >> >> >> >> >>> >> >>>> >> >> >> - chris >> >>> >> >>>> >> >> > >> >>> >> >>>> >> >> >> __ __ _ _ ___ ___ >> >>> >> >>>> >> >> >> \ \/ /___ _ __ | || | / _ \ / _ \ >> >>> >> >>>> >> >> >> \ // _ \ \047_ \ | || |_| | | | | | | >> >>> >> >>>> >> >> >> / \ __/ | | | |__ _| |_| | |_| | >> >>> >> >>>> >> >> >> /_/\_\___|_| |_| |_|(_)___(_)___/ >> >>> >> >>>> >> >> >> >> >>> >> >>>> >> >> >> (XEN) Xen version 4.0.0 (root@) (gcc version >> >>> >> >>>> >> >> >> 4.3.2 (Debian 4.3.2-1.1) ) Thu May 6 13:41:25 >> >>> >> >>>> >> >> >> EDT 2010 >> >>> >> >>>> >> >> >> (XEN) Latest ChangeSet: unavailable >> >>> >> >>>> >> >> >> (XEN) Command line: iommu=verbose dom0_mem=256M >> >>> >> >>>> >> >> >> dom0_max_vcpus=1 dom0_vcpus_pin=true >> >>> >> >>>> >> >> >> (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 - 000000000008f000 >> >>> >> >>>> >> >> >> (usable) >> >>> >> >>>> >> >> >> (XEN) 000000000008f000 - 0000000000090000 >> >>> >> >>>> >> >> >> (reserved) >> >>> >> >>>> >> >> >> (XEN) 0000000000090000 - 000000000009ec00 >> >>> >> >>>> >> >> >> (usable) >> >>> >> >>>> >> >> >> (XEN) 000000000009ec00 - 00000000000a0000 >> >>> >> >>>> >> >> >> (reserved) >> >>> >> >>>> >> >> >> (XEN) 00000000000e0000 - 0000000000100000 >> >>> >> >>>> >> >> >> (reserved) >> >>> >> >>>> >> >> >> (XEN) 0000000000100000 - 00000000cf4bd000 >> >>> >> >>>> >> >> >> (usable) >> >>> >> >>>> >> >> >> (XEN) 00000000cf4bd000 - 00000000cf4bf000 >> >>> >> >>>> >> >> >> (reserved) >> >>> >> >>>> >> >> >> (XEN) 00000000cf4bf000 - 00000000cf4c2000 >> >>> >> >>>> >> >> >> (usable) >> >>> >> >>>> >> >> >> (XEN) 00000000cf4c2000 - 00000000cf7bf000 (ACPI >> >>> >> >>>> >> >> >> NVS) >> >>> >> >>>> >> >> >> (XEN) 00000000cf7bf000 - 00000000cf7df000 >> >>> >> >>>> >> >> >> (usable) >> >>> >> >>>> >> >> >> (XEN) 00000000cf7df000 - 00000000cf7ff000 (ACPI >> >>> >> >>>> >> >> >> data) >> >>> >> >>>> >> >> >> (XEN) 00000000cf7ff000 - 00000000cf800000 >> >>> >> >>>> >> >> >> (usable) >> >>> >> >>>> >> >> >> (XEN) 00000000cf800000 - 00000000d0000000 >> >>> >> >>>> >> >> >> (reserved) >> >>> >> >>>> >> >> >> (XEN) 00000000f8000000 - 00000000fd000000 >> >>> >> >>>> >> >> >> (reserved) >> >>> >> >>>> >> >> >> (XEN) 00000000ffe00000 - 0000000100000000 >> >>> >> >>>> >> >> >> (reserved) >> >>> >> >>>> >> >> >> (XEN) 0000000100000000 - 0000000230000000 >> >>> >> >>>> >> >> >> (usable) >> >>> >> >>>> >> >> >> (XEN) ACPI: RSDP 000FE020, 0024 (r2 INTEL ) >> >>> >> >>>> >> >> >> (XEN) ACPI: XSDT CF7FE120, 0074 (r1 INTEL >> >>> >> >>>> >> >> >> DX58SO 11F6 1000013) >> >>> >> >>>> >> >> >> (XEN) ACPI: FACP CF7FD000, 00F4 (r3 INTEL >> >>> >> >>>> >> >> >> DX58SO 11F6 MSFT 100000D) >> >>> >> >>>> >> >> >> (XEN) ACPI Warning (tbfadt-0444): Optional field >> >>> >> >>>> >> >> >> "Pm2ControlBlock" has zero address or length: >> >>> >> >>>> >> >> >> 0000000000000450/0 [20070126] >> >>> >> >>>> >> >> >> (XEN) ACPI: DSDT CF7F8000, 4641 (r2 INTEL >> >>> >> >>>> >> >> >> DX58SO 11F6 MSFT 100000D) >> >>> >> >>>> >> >> >> (XEN) ACPI: FACS CF728000, 0040 >> >>> >> >>>> >> >> >> (XEN) ACPI: APIC CF7F7000, 0138 (r2 INTEL >> >>> >> >>>> >> >> >> DX58SO 11F6 MSFT 100000D) >> >>> >> >>>> >> >> >> (XEN) ACPI: WDDT CF7F6000, 0040 (r1 INTEL >> >>> >> >>>> >> >> >> DX58SO 11F6 MSFT 100000D) >> >>> >> >>>> >> >> >> (XEN) ACPI: MCFG CF7F5000, 003C (r1 INTEL >> >>> >> >>>> >> >> >> DX58SO 11F6 MSFT 100000D) >> >>> >> >>>> >> >> >> (XEN) ACPI: ASF! CF7F4000, 00AC (r32 INTEL >> >>> >> >>>> >> >> >> DX58SO 11F6 MSFT 100000D) >> >>> >> >>>> >> >> >> (XEN) ACPI: HPET CF7F3000, 0038 (r1 INTEL >> >>> >> >>>> >> >> >> DX58SO 11F6 MSFT 100000D) >> >>> >> >>>> >> >> >> (XEN) ACPI: SSDT CF7E2000, E134 (r1 INTEL SSDT >> >>> >> >>>> >> >> >> PM 11F6 MSFT 100000D) >> >>> >> >>>> >> >> >> (XEN) ACPI: DMAR CF7DF000, 0140 (r1 INTEL >> >>> >> >>>> >> >> >> DX58SO 11F6 MSFT 100000D) >> >>> >> >>>> >> >> >> (XEN) ACPI: WDTT CF7F1000, 020C (r2 INTEL >> >>> >> >>>> >> >> >> DX58SO 11F6 MSFT 100000D) >> >>> >> >>>> >> >> >> (XEN) ACPI: ASPT CF7F2000, 0034 (r4 INTEL >> >>> >> >>>> >> >> >> PerfTune 11F6 MSFT 100000D) >> >>> >> >>>> >> >> >> (XEN) System RAM: 7950MB (8140820kB) >> >>> >> >>>> >> >> >> (XEN) Domain heap initialised >> >>> >> >>>> >> >> >> (XEN) Processor #0 7:10 APIC version 21 >> >>> >> >>>> >> >> >> (XEN) Processor #2 7:10 APIC version 21 >> >>> >> >>>> >> >> >> (XEN) Processor #4 7:10 APIC version 21 >> >>> >> >>>> >> >> >> (XEN) Processor #6 7:10 APIC version 21 >> >>> >> >>>> >> >> >> (XEN) Processor #1 7:10 APIC version 21 >> >>> >> >>>> >> >> >> (XEN) Processor #3 7:10 APIC version 21 >> >>> >> >>>> >> >> >> (XEN) Processor #5 7:10 APIC version 21 >> >>> >> >>>> >> >> >> (XEN) Processor #7 7:10 APIC version 21 >> >>> >> >>>> >> >> >> (XEN) IOAPIC[0]: apic_id 8, version 32, address >> >>> >> >>>> >> >> >> 0xfec00000, GSI 0-23 >> >>> >> >>>> >> >> >> (XEN) Enabling APIC mode: Flat. Using 1 I/O >> >>> >> >>>> >> >> >> APICs >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:679: Host address width 39 >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = >> >>> >> >>>> >> >> >> fe711000 >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1b.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = >> >>> >> >>>> >> >> >> fe710000 >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:340: IOAPIC: f0:1f.7 >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:411: flags: INCLUDE_ALL >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >> >>> >> >>>> >> >> >> e9000 end_address e9fff >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.1 >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >> >>> >> >>>> >> >> >> ea000 end_address eafff >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.2 >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >> >>> >> >>>> >> >> >> eb000 end_address ebfff >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >> >>> >> >>>> >> >> >> e6000 end_address e6fff >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.1 >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >> >>> >> >>>> >> >> >> e7000 end_address e7fff >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.2 >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >> >>> >> >>>> >> >> >> e8000 end_address e8fff >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >> >>> >> >>>> >> >> >> ec000 end_address eefff >> >>> >> >>>> >> >> >> (XEN) Using scheduler: SMP Credit Scheduler >> >>> >> >>>> >> >> >> (credit) >> >>> >> >>>> >> >> >> (XEN) Detected 2800.125 MHz processor. >> >>> >> >>>> >> >> >> (XEN) Initing memory sharing. >> >>> >> >>>> >> >> >> (XEN) VMX: Supported advanced features: >> >>> >> >>>> >> >> >> (XEN) - APIC MMIO access virtualisation >> >>> >> >>>> >> >> >> (XEN) - APIC TPR shadow >> >>> >> >>>> >> >> >> (XEN) - Extended Page Tables (EPT) >> >>> >> >>>> >> >> >> (XEN) - Virtual-Processor Identifiers (VPID) >> >>> >> >>>> >> >> >> (XEN) - Virtual NMI >> >>> >> >>>> >> >> >> (XEN) - MSR direct-access bitmap >> >>> >> >>>> >> >> >> (XEN) HVM: ASIDs enabled. >> >>> >> >>>> >> >> >> (XEN) HVM: VMX enabled >> >>> >> >>>> >> >> >> (XEN) HVM: Hardware Assisted Paging detected. >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = >> >>> >> >>>> >> >> >> fe711000 iommu->reg = ffff82c3fff57000 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c9008010e60262 >> >>> >> >>>> >> >> >> ecap = f0207a >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = >> >>> >> >>>> >> >> >> fe710000 iommu->reg = ffff82c3fff56000 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c90780106f0462 >> >>> >> >>>> >> >> >> ecap = f020fa >> >>> >> >>>> >> >> >> (XEN) Intel VT-d Snoop Control not supported. >> >>> >> >>>> >> >> >> (XEN) Intel VT-d DMA Passthrough not supported. >> >>> >> >>>> >> >> >> (XEN) Intel VT-d Queued Invalidation supported. >> >>> >> >>>> >> >> >> (XEN) Intel VT-d Interrupt Remapping supported. >> >>> >> >>>> >> >> >> (XEN) I/O virtualisation enabled >> >>> >> >>>> >> >> >> (XEN) I/O virtualisation for PV guests disabled >> >>> >> >>>> >> >> >> (XEN) Total of 8 processors activated. >> >>> >> >>>> >> >> >> (XEN) ENABLING IO-APIC IRQs >> >>> >> >>>> >> >> >> (XEN) -> Using new ACK method >> >>> >> >>>> >> >> >> (XEN) TSC is reliable, synchronization >> >>> >> >>>> >> >> >> unnecessary >> >>> >> >>>> >> >> >> (XEN) Platform timer is 14.318MHz HPET >> >>> >> >>>> >> >> >> (XEN) Allocated console ring of 16 KiB. >> >>> >> >>>> >> >> >> (XEN) Brought up 8 CPUs >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 0:0.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 0:10.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 0:10.1 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >> >>> >> >>>> >> >> >> 0:14.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >> >>> >> >>>> >> >> >> 0:14.1 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >> >>> >> >>>> >> >> >> 0:14.2 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 0:14.3 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 0:19.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 0:1a.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 0:1a.1 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 0:1a.2 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 0:1a.7 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >> >>> >> >>>> >> >> >> 0:1b.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 0:1d.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 0:1d.1 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 0:1d.2 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 0:1d.7 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 0:1f.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 0:1f.2 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 0:1f.3 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 0:1f.5 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 2:0.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 2:0.1 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 2:0.2 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 4:0.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 4:0.1 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 4:0.2 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >> >>> >> >>>> >> >> >> 5:0.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 7:0.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 7:0.1 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 7:0.2 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 9:0.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 9:0.1 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 9:0.2 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >> >>> >> >>>> >> >> >> a:0.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> b:3.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> b:3.1 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> b:3.2 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> b:3.3 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> b:3.4 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> b:3.5 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> b:3.6 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> b:3.7 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 3f:0.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 3f:0.1 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 3f:2.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 3f:2.1 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 3f:3.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 3f:3.1 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 3f:3.4 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 3f:4.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 3f:4.1 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 3f:4.2 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 3f:4.3 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 3f:5.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 3f:5.1 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 3f:5.2 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 3f:5.3 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 3f:6.0 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 3f:6.1 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 3f:6.2 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >> >>> >> >>>> >> >> >> 3f:6.3 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:695: >> >>> >> >>>> >> >> >> iommu_enable_translation: iommu->reg = >> >>> >> >>>> >> >> >> ffff82c3fff57000 >> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:695: >> >>> >> >>>> >> >> >> iommu_enable_translation: iommu->reg = >> >>> >> >>>> >> >> >> ffff82c3fff56000 >> >>> >> >>>> >> >> >> (XEN) *** LOADING DOMAIN 0 *** >> >>> >> >>>> >> >> >> (XEN) Xen kernel: 64-bit, lsb, compat32 >> >>> >> >>>> >> >> >> (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr >> >>> >> >>>> >> >> >> 0x1000000 -> 0x26ae000 >> >>> >> >>>> >> >> >> (XEN) PHYSICAL MEMORY ARRANGEMENT: >> >>> >> >>>> >> >> >> (XEN) Dom0 alloc.: >> >>> >> >>>> >> >> >> 0000000210000000->0000000220000000 >> >>> >> >>>> >> >> >> (XEN) VIRTUAL MEMORY ARRANGEMENT: >> >>> >> >>>> >> >> >> (XEN) Loaded kernel: >> >>> >> >>>> >> >> >> ffffffff81000000->ffffffff826ae000 >> >>> >> >>>> >> >> >> (XEN) Init. ramdisk: >> >>> >> >>>> >> >> >> ffffffff826ae000->ffffffff8f4de600 >> >>> >> >>>> >> >> >> (XEN) Phys-Mach map: >> >>> >> >>>> >> >> >> ffffffff8f4df000->ffffffff8f55f000 >> >>> >> >>>> >> >> >> (XEN) Start info: >> >>> >> >>>> >> >> >> ffffffff8f55f000->ffffffff8f55f4b4 >> >>> >> >>>> >> >> >> (XEN) Page tables: >> >>> >> >>>> >> >> >> ffffffff8f560000->ffffffff8f5df000 >> >>> >> >>>> >> >> >> (XEN) Boot stack: >> >>> >> >>>> >> >> >> ffffffff8f5df000->ffffffff8f5e0000 >> >>> >> >>>> >> >> >> (XEN) TOTAL: >> >>> >> >>>> >> >> >> ffffffff80000000->ffffffff8f800000 >> >>> >> >>>> >> >> >> (XEN) ENTRY ADDRESS: ffffffff81a10860 >> >>> >> >>>> >> >> >> (XEN) Dom0 has maximum 1 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 >> >>> >> >>>> >> >> >> \047CTRL-a\047 three times to switch input to >> >>> >> >>>> >> >> >> Xen) >> >>> >> >>>> >> >> >> (XEN) Freed 164kB init memory. >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 >> >>> >> >>>> >> >> >> pirq=0 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=2, irq=0 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=000009f0 >> >>> >> >>>> >> >> >> pirq=0 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 3 already >> >>> >> >>>> >> >> >> mapped >> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 4 already >> >>> >> >>>> >> >> >> mapped >> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 5 already >> >>> >> >>>> >> >> >> mapped >> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 6 already >> >>> >> >>>> >> >> >> mapped >> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 7 already >> >>> >> >>>> >> >> >> mapped >> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 8 already >> >>> >> >>>> >> >> >> mapped >> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 9 already >> >>> >> >>>> >> >> >> mapped >> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 10 already >> >>> >> >>>> >> >> >> mapped >> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 11 already >> >>> >> >>>> >> >> >> mapped >> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 12 already >> >>> >> >>>> >> >> >> mapped >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000009f0 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 >> >>> >> >>>> >> >> >> pirq=0 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 >> >>> >> >>>> >> >> >> pirq=18 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 >> >>> >> >>>> >> >> >> pirq=19 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=23, irq=23 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a929 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a929 >> >>> >> >>>> >> >> >> pirq=23 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 >> >>> >> >>>> >> >> >> pirq=19 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 >> >>> >> >>>> >> >> >> pirq=18 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 >> >>> >> >>>> >> >> >> pirq=16 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 >> >>> >> >>>> >> >> >> pirq=16 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 >> >>> >> >>>> >> >> >> pirq=19 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 >> >>> >> >>>> >> >> >> pirq=18 >> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>> >> >>>> >> >> > >> >>> >> >>>> >> >> >> _______________________________________________ >> >>> >> >>>> >> >> >> Xen-users mailing list >> >>> >> >>>> >> >> >> Xen-users@lists.xensource.com >> >>> >> >>>> >> >> >> http://lists.xensource.com/xen-users >> >>> >> >>>> >> >> > >> >>> >> >>>> >> > >> >>> >> >>>> > >> >>> >> >>> >> >>> >> >> >> >>> >> > >> >>> > >> >> >> > > ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [Xen-devel] Re: RE: Xen4 / Intel DX58SO Mobo / VT-d not working 2010-05-16 7:36 ` [Xen-devel] " Han, Weidong @ 2010-05-16 13:00 ` chris 2010-05-17 17:05 ` chris 0 siblings, 1 reply; 32+ messages in thread From: chris @ 2010-05-16 13:00 UTC (permalink / raw) To: Han, Weidong; +Cc: Xen-Devel List, Xen-Users List, Pasi Kärkkäinen I'm not sure I understand what you want me to do, but that does look interesting and I didn't notice it before. - chris On Sun, May 16, 2010 at 3:36 AM, Han, Weidong <weidong.han@intel.com> wrote: > I noticed this line " (XEN) domctl.c:853:d0 XEN_DOMCTL_assign_device: assign device (2:0.0) failed" in NOTWORKING.txt. could you add some logs to intel_iommu_assign_device to know where it fails? I prefer you to use a clean Xen 4.0 environment. > > Regards, > Weidong > > -----Original Message----- > From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of chris > Sent: Saturday, May 15, 2010 5:18 AM > To: Pasi Kärkkäinen > Cc: Xen-Devel List; Xen-Users List > Subject: [Xen-devel] Re: [Xen-users] RE: Xen4 / Intel DX58SO Mobo / VT-d not working > > Played around with xen_platform_pc, pci_msitranslate, pci_power_mgmt in the cfg, none of which seem to have any effect, also tried > pci=resource_alignment=02:00.0;02:00.1;02:00.2 on dom0 cmdline, no effect. > > I'm worn out been fighting this all day. Attached is some various output from the machine that works with the same cards and has Xen > 3.4.2 and the new machine with 4.0 which doesn't work. I'm hoping this information can get the right attention and we can figure it out :( > > - chris > > > On Fri, May 14, 2010 at 4:50 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >> On Fri, May 14, 2010 at 04:39:54PM -0400, chris wrote: >>> Alright so a pci sound card works, I tried a geforce 8600 pci e card >>> and while vga passthrough didnt work it did seem to attach to the >>> domain ok. So I guess the problem must be somehow related to the >>> device. I'm still confused since it works in another box. >>> >>> I remember there was some reassign_resources or something, maybe the >>> issue is with some resources the card uses? >>> >> >> http://wiki.xensource.com/xenwiki/XenPCIpassthrough >> >> -- Pasi >> >>> Below is a lspci -vv of the card >>> >>> 02:00.0 USB Controller: NEC Corporation USB (rev 43) (prog-if 10 >>> [OHCI]) >>> Subsystem: NEC Corporation Hama USB 2.0 CardBus >>> Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- >>> ParErr- Stepping- SERR- FastB2B- DisINTx- >>> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >>> >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- >>> Interrupt: pin A routed to IRQ 16 >>> Region 0: Memory at d2502000 (32-bit, non-prefetchable) >>> [disabled] [size=4K] >>> Capabilities: [40] Power Management version 2 >>> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA >>> PME(D0+,D1+,D2+,D3hot+,D3cold-) >>> Status: D0 PME-Enable- DSel=0 DScale=0 PME- >>> Kernel driver in use: pciback >>> >>> 02:00.1 USB Controller: NEC Corporation USB (rev 43) (prog-if 10 >>> [OHCI]) >>> Subsystem: NEC Corporation Hama USB 2.0 CardBus >>> Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- >>> ParErr- Stepping- SERR- FastB2B- DisINTx- >>> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >>> >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- >>> Interrupt: pin B routed to IRQ 17 >>> Region 0: Memory at d2501000 (32-bit, non-prefetchable) >>> [disabled] [size=4K] >>> Capabilities: [40] Power Management version 2 >>> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA >>> PME(D0+,D1+,D2+,D3hot+,D3cold-) >>> Status: D0 PME-Enable- DSel=0 DScale=0 PME- >>> Kernel driver in use: pciback >>> >>> 02:00.2 USB Controller: NEC Corporation USB 2.0 (rev 04) (prog-if 20 >>> [EHCI]) >>> Subsystem: NEC Corporation USB 2.0 >>> Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- >>> ParErr- Stepping- SERR- FastB2B- DisINTx- >>> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >>> >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- >>> Interrupt: pin C routed to IRQ 18 >>> Region 0: Memory at d2500000 (32-bit, non-prefetchable) >>> [disabled] [size=256] >>> Capabilities: [40] Power Management version 2 >>> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA >>> PME(D0+,D1+,D2+,D3hot+,D3cold-) >>> Status: D0 PME-Enable- DSel=0 DScale=0 PME- >>> Kernel driver in use: pciback >>> >>> >>> On Fri, May 14, 2010 at 3:46 PM, chris <tknchris@gmail.com> wrote: >>> > I added a pci sound card and interestingly that works. I'm digging >>> > around for another pci-e device to try to identify if its all pci-e >>> > or only this device. Strange this is that I have a few other >>> > machines with this same usb controller which is working on 3.4.2. >>> > >>> > *scratches head* >>> > >>> > - chris >>> > >>> > On Fri, May 14, 2010 at 3:21 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>> >> On Fri, May 14, 2010 at 03:18:02PM -0400, chris wrote: >>> >>> It is a multifunction device, a pci-e usb controller, so I >>> >>> assumed all them had to be passed through. I just changed it to >>> >>> only 02:00.0 and same thing >>> >>> >>> >>> test-box2:~# cat /etc/xen/vm-five.cfg | grep pci pci = >>> >>> ['02:00.0'] test-box2:~# xm create /etc/xen/vm-five.cfg Using >>> >>> config file "/etc/xen/vm-five.cfg". >>> >>> Error: Failed to assign device to IOMMU >>> >>> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>> >>> >>> >> >>> >> Hmm.. weird. >>> >> >>> >> Two things to try: >>> >> >>> >> 1) Try passthru some other device (which is just a single pci id) >>> >> 2) Try passthru that pci-e usb controller to Linux PV guest and >>> >> see if that works >>> >> >>> >> -- Pasi >>> >> >>> >>> >>> >>> On Fri, May 14, 2010 at 3:11 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>> >>> > On Fri, May 14, 2010 at 03:05:49PM -0400, chris wrote: >>> >>> >> Pasi, >>> >>> >> >>> >>> >> Tried latest stable/2.6.32.x per your advice, no change. >>> >>> >> Anyone on xen-devel that can help me troubleshoot further? >>> >>> >> Everything looks right, can't figure out why vt-d is not >>> >>> >> working but it must be some kind of bug :( >>> >>> >> >>> >>> > >>> >>> > Did you try the suggestion said earlier.. try to just passthru the first pci device? >>> >>> > >>> >>> > -- Pasi >>> >>> > >>> >>> >> test-box2:~# uname -a >>> >>> >> Linux test-box2 2.6.32.12 #1 SMP Fri May 14 13:40:05 EDT 2010 >>> >>> >> x86_64 GNU/Linux >>> >>> >> >>> >>> >> test-box2:~# xm info | grep virt_caps virt_caps : >>> >>> >> hvm hvm_directio >>> >>> >> >>> >>> >> test-box2:~# xm pci-list-assignable-devices 0000:02:00.0 >>> >>> >> 0000:02:00.1 >>> >>> >> 0000:02:00.2 >>> >>> >> >>> >>> >> test-box2:~# xm create /etc/xen/vm-five.cfg Using config file >>> >>> >> "/etc/xen/vm-five.cfg". >>> >>> >> Error: Failed to assign device to IOMMU >>> >>> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>> >>> >> >>> >>> >> test-box2:~# cat /etc/xen/vm-five.cfg | grep -v '#' >>> >>> >> kernel = '/usr/lib/xen/boot/hvmloader' >>> >>> >> builder = 'hvm' >>> >>> >> memory = '1792' >>> >>> >> device_model='/usr/lib/xen/bin/qemu-dm' >>> >>> >> disk = [ 'phy:/dev/storage/vm-five,ioemu:hda,w', >>> >>> >> 'phy:/dev/sr0,ioemu:hdc:cdrom,r' >>> >>> >> ] >>> >>> >> name = 'vm-five' >>> >>> >> vif = ['type=ioemu, bridge=eth0, mac=00:16:3D:37:A1:42'] >>> >>> >> boot='dc' >>> >>> >> cpus='0-1' >>> >>> >> vcpus=2 >>> >>> >> acpi=1 >>> >>> >> ahci=1 >>> >>> >> vnc=1 >>> >>> >> sdl=0 >>> >>> >> timer_mode=1 >>> >>> >> usb=1 >>> >>> >> usbdevice='tablet' >>> >>> >> localtime=1 >>> >>> >> pci = ['02:00.0','02:00.1','02:00.2'] >>> >>> >> >>> >>> >> On Thu, May 13, 2010 at 2:28 PM, chris <tknchris@gmail.com> wrote: >>> >>> >> > Forwarding to xen-devel. Can't seem to get VT-d working with >>> >>> >> > xen4 from tarball on xen.org 2.6.31.13 pv_ops dom0. On >>> >>> >> > pasi's advice I tried switching to stable/2.6.32.x branch >>> >>> >> > for dom0 and that doesnt even build. Did something change recently thats breaking compilation? >>> >>> >> > >>> >>> >> > Attached is xen dmesg with iommu=verbose loglvl=all >>> >>> >> > guest_loglvl=all, and dom0 dmesg from 2.6.31.x >>> >>> >> > >>> >>> >> > Any ideas on why VT-d is not working on this board? >>> >>> >> > Initialization looks good, xen reports hvm_directio >>> >>> >> > capability, everything says VT-d should work until domain is created. >>> >>> >> > >>> >>> >> > Any ideas why stable/2.6.32.x wont build? >>> >>> >> > >>> >>> >> > - chris >>> >>> >> > >>> >>> >> > On Thu, May 13, 2010 at 2:07 PM, chris <tknchris@gmail.com> wrote: >>> >>> >> >> I redid it with oldconfig which I didn't think would help >>> >>> >> >> and same thing. I guess this tree is broken? Can someone >>> >>> >> >> else try and see if they can build it? Ugh, whata day :) >>> >>> >> >> >>> >>> >> >> On Thu, May 13, 2010 at 1:58 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>> >>> >> >>> On Thu, May 13, 2010 at 01:55:25PM -0400, chris wrote: >>> >>> >> >>>> I used the default config on the wiki which you created. Steps I took were: >>> >>> >> >>>> >>> >>> >> >>>> # make clean distclean >>> >>> >> >>>> # wget -O .config >>> >>> >> >>>> "http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.10-pvops-dom0-xen-stable-x86_64" >>> >>> >> >>> >>> >>> >> >>> You should do "make oldconfig" at this point. >>> >>> >> >>> >>> >>> >> >>>> # make -j8 bzImage >>> >>> >> >>>> (blah blah) >>> >>> >> >>>> LD vmlinux.o >>> >>> >> >>>> MODPOST vmlinux.o >>> >>> >> >>>> WARNING: modpost: Found 7 section mismatch(es). >>> >>> >> >>>> To see full details build your kernel with: >>> >>> >> >>>> 'make CONFIG_DEBUG_SECTION_MISMATCH=y' >>> >>> >> >>>> GEN .version >>> >>> >> >>>> CHK include/linux/compile.h >>> >>> >> >>>> UPD include/linux/compile.h >>> >>> >> >>>> CC init/version.o >>> >>> >> >>>> LD init/built-in.o >>> >>> >> >>>> LD .tmp_vmlinux1 >>> >>> >> >>>> drivers/built-in.o: In function `do_hvm_suspend': >>> >>> >> >>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: >>> >>> >> >>>> undefined reference to `xenbus_suspend' >>> >>> >> >>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: >>> >>> >> >>>> undefined reference to `xenbus_resume' >>> >>> >> >>>> make: *** [.tmp_vmlinux1] Error 1 >>> >>> >> >>>> >>> >>> >> >>> >>> >>> >> >>> Hmm.. weird. I wonder if something has changed recently or what's going on in here.. >>> >>> >> >>> >>> >>> >> >>> -- Pasi >>> >>> >> >>> >>> >>> >> >>>> >>> >>> >> >>>> On Thu, May 13, 2010 at 11:47 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>> >>> >> >>>> > On Thu, May 13, 2010 at 11:33:57AM -0400, chris wrote: >>> >>> >> >>>> >> Successfully grabbed the sources and failed to build: >>> >>> >> >>>> >> >>> >>> >> >>>> >> LD .tmp_vmlinux1 >>> >>> >> >>>> >> drivers/built-in.o: In function `do_hvm_suspend': >>> >>> >> >>>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: >>> >>> >> >>>> >> undefined reference to `xenbus_suspend' >>> >>> >> >>>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: >>> >>> >> >>>> >> undefined reference to `xenbus_resume' >>> >>> >> >>>> >> make: *** [.tmp_vmlinux1] Error 1 >>> >>> >> >>>> >> >>> >>> >> >>>> >> :( >>> >>> >> >>>> >> >>> >>> >> >>>> > >>> >>> >> >>>> > Try the example .config files provided on the wiki page. >>> >>> >> >>>> > >>> >>> >> >>>> > -- Pasi >>> >>> >> >>>> > >>> >>> >> >>>> >> On Thu, May 13, 2010 at 10:14 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>> >>> >> >>>> >> > On Thu, May 13, 2010 at 10:12:56AM -0400, chris wrote: >>> >>> >> >>>> >> >> Pasi, >>> >>> >> >>>> >> >> >>> >>> >> >>>> >> >> How do I pull those kernel sources you referenced? >>> >>> >> >>>> >> >> I see it mentioned on >>> >>> >> >>>> >> >> http://wiki.xensource.com/xenwiki/XenParavirtOps but no details on how to retrieve it. >>> >>> >> >>>> >> >> >>> >>> >> >>>> >> > >>> >>> >> >>>> >> > The instructions are there if you read it carefully.. >>> >>> >> >>>> >> > There's the topic of how to switch branches. >>> >>> >> >>>> >> > >>> >>> >> >>>> >> > -- Pasi >>> >>> >> >>>> >> > >>> >>> >> >>>> >> >> - chris >>> >>> >> >>>> >> >> >>> >>> >> >>>> >> >> On Thu, May 13, 2010 at 8:29 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>> >>> >> >>>> >> >> > On Wed, May 12, 2010 at 08:41:34PM -0400, chris wrote: >>> >>> >> >>>> >> >> >> When reading the vtdhowto I noticed the ability to set iommu=verbose. >>> >>> >> >>>> >> >> >> Here is that output, I don't know if it helps at >>> >>> >> >>>> >> >> >> all to figure out what is wrong. >>> >>> >> >>>> >> >> >> >>> >>> >> >>>> >> >> > >>> >>> >> >>>> >> >> > That seems to be OK: >>> >>> >> >>>> >> >> > >>> >>> >> >>>> >> >> > (XEN) I/O virtualisation enabled >>> >>> >> >>>> >> >> > (XEN) I/O virtualisation for PV guests disabled >>> >>> >> >>>> >> >> > >>> >>> >> >>>> >> >> > So hmm.. I wonder if it's related to MSI stuff? >>> >>> >> >>>> >> >> > You could try xen.git xen/stable-2.6.32.x branch instead and see if that makes a difference.. >>> >>> >> >>>> >> >> > >>> >>> >> >>>> >> >> > -- Pasi >>> >>> >> >>>> >> >> > >>> >>> >> >>>> >> >> >> >>> >>> >> >>>> >> >> >> ---------- Forwarded message ---------- >>> >>> >> >>>> >> >> >> From: chris <tknchris@gmail.com> >>> >>> >> >>>> >> >> >> Date: Wed, May 12, 2010 at 5:28 PM >>> >>> >> >>>> >> >> >> Subject: Xen4 / Intel DX58SO Mobo / VT-d not >>> >>> >> >>>> >> >> >> working >>> >>> >> >>>> >> >> >> To: Xen-Users List >>> >>> >> >>>> >> >> >> <xen-users@lists.xensource.com> >>> >>> >> >>>> >> >> >> >>> >>> >> >>>> >> >> >> >>> >>> >> >>>> >> >> >> Hello, >>> >>> >> >>>> >> >> >> >>> >>> >> >>>> >> >> >> I've previously been successful with Xen4 and >>> >>> >> >>>> >> >> >> VT-d on other systems. I am having trouble >>> >>> >> >>>> >> >> >> getting VT-d passthrough working to a WinXP >>> >>> >> >>>> >> >> >> domain with DX58SO (Q45) motherboard and i7 930 >>> >>> >> >>>> >> >> >> CPU. VT-d is enabled in bios, xm info shows >>> >>> >> >>>> >> >> >> hvm_directio capability, I have iommu=1 set, I >>> >>> >> >>>> >> >> >> have the devices bound to pciback on dom0 cmdline, xm pci-list-assignable-devices shows the devices as assignable. When I attempt to start the VM I get the error: >>> >>> >> >>>> >> >> >> >>> >>> >> >>>> >> >> >> Error: Failed to assign device to IOMMU >>> >>> >> >>>> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>> >>> >> >>>> >> >> >> >>> >>> >> >>>> >> >> >> Below is all the information I can think of that >>> >>> >> >>>> >> >> >> would be useful to help debug it: >>> >>> >> >>>> >> >> >> >>> >>> >> >>>> >> >> >> BIOS VT-d Enabled: >>> >>> >> >>>> >> >> >> http://i43.tinypic.com/nl3a5e.jpg >>> >>> >> >>>> >> >> >> http://i42.tinypic.com/nqvlu1.jpg >>> >>> >> >>>> >> >> >> >>> >>> >> >>>> >> >> >> grub entry: >>> >>> >> >>>> >> >> >> >>> >>> >> >>>> >> >> >> title Xen 4.0.0 / Debian GNU/Linux, >>> >>> >> >>>> >> >> >> kernel 2.6.31.13 root (hd0,0) kernel >>> >>> >> >>>> >> >> >> /boot/xen-4.0.0.gz iommu=1 dom0_mem=256M >>> >>> >> >>>> >> >> >> dom0_max_vcpus=1 dom0_vcpus_pin=true module >>> >>> >> >>>> >> >> >> /boot/vmlinuz-2.6.31.13 root=/dev/md0 ro >>> >>> >> >>>> >> >> >> console=tty0 xen-pciback.permissive >>> >>> >> >>>> >> >> >> xen-pciback.hide=(02:00.0)(02:00.1)(02:00.2)(04: >>> >>> >> >>>> >> >> >> 00.0)(04:00.1)(04:00.2)(07:00.0)(07:00.1)(07:00. >>> >>> >> >>>> >> >> >> 2)(09:00.0)(09:00.1)(09:00.2) module >>> >>> >> >>>> >> >> >> /boot/initrd.img-2.6.31.13 >>> >>> >> >>>> >> >> >> >>> >>> >> >>>> >> >> >> # xm pci-list-assignable-devices 0000:09:00.0 >>> >>> >> >>>> >> >> >> 0000:09:00.1 >>> >>> >> >>>> >> >> >> 0000:09:00.2 >>> >>> >> >>>> >> >> >> 0000:07:00.0 >>> >>> >> >>>> >> >> >> 0000:07:00.1 >>> >>> >> >>>> >> >> >> 0000:07:00.2 >>> >>> >> >>>> >> >> >> 0000:04:00.0 >>> >>> >> >>>> >> >> >> 0000:04:00.1 >>> >>> >> >>>> >> >> >> 0000:04:00.2 >>> >>> >> >>>> >> >> >> 0000:02:00.0 >>> >>> >> >>>> >> >> >> 0000:02:00.1 >>> >>> >> >>>> >> >> >> 0000:02:00.2 >>> >>> >> >>>> >> >> >> >>> >>> >> >>>> >> >> >> # xm info >>> >>> >> >>>> >> >> >> host : test-box2 release >>> >>> >> >>>> >> >> >> : 2.6.31.13 version : #2 SMP Wed >>> >>> >> >>>> >> >> >> May 12 14:11:37 EDT 2010 machine >>> >>> >> >>>> >> >> >> : x86_64 nr_cpus : 8 nr_nodes >>> >>> >> >>>> >> >> >> : 1 cores_per_socket : 4 threads_per_core >>> >>> >> >>>> >> >> >> : 2 cpu_mhz : 2800 hw_caps >>> >>> >> >>>> >> >> >> : >>> >>> >> >>>> >> >> >> bfebfbff:28100800:00000000:00001b40:0098e3bd:000 >>> >>> >> >>>> >> >> >> 00000:00000001:00000000 virt_caps : >>> >>> >> >>>> >> >> >> hvm hvm_directio total_memory : 7950 >>> >>> >> >>>> >> >> >> free_memory : 7812 node_to_cpu >>> >>> >> >>>> >> >> >> : node0:0-7 node_to_memory : node0:7812 >>> >>> >> >>>> >> >> >> node_to_dma32_mem : node0:3249 max_node_id >>> >>> >> >>>> >> >> >> : 0 xen_major : 4 xen_minor >>> >>> >> >>>> >> >> >> : 0 xen_extra : .0 xen_caps >>> >>> >> >>>> >> >> >> : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 >>> >>> >> >>>> >> >> >> hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler >>> >>> >> >>>> >> >> >> : credit xen_pagesize : 4096 >>> >>> >> >>>> >> >> >> platform_params : >>> >>> >> >>>> >> >> >> virt_start=0xffff800000000000 xen_changeset >>> >>> >> >>>> >> >> >> : unavailable xen_commandline : iommu=1 >>> >>> >> >>>> >> >> >> dom0_mem=256M dom0_max_vcpus=1 >>> >>> >> >>>> >> >> >> dom0_vcpus_pin=true cc_compiler : gcc >>> >>> >> >>>> >> >> >> version 4.3.2 (Debian 4.3.2-1.1) cc_compile_by >>> >>> >> >>>> >> >> >> : root cc_compile_domain : >>> >>> >> >>>> >> >> >> cc_compile_date : Thu May 6 13:41:25 EDT >>> >>> >> >>>> >> >> >> 2010 xend_config_format : 4 >>> >>> >> >>>> >> >> >> >>> >>> >> >>>> >> >> >> # xm create vm-five.cfg Using config file >>> >>> >> >>>> >> >> >> "./vm-five.cfg". >>> >>> >> >>>> >> >> >> Error: Failed to assign device to IOMMU >>> >>> >> >>>> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>> >>> >> >>>> >> >> >> >>> >>> >> >>>> >> >> >> I feel like I'm missing something really obvious >>> >>> >> >>>> >> >> >> but I've been at it for a while now and have run >>> >>> >> >>>> >> >> >> out of brain power. Anyone have any idea what might be wrong? >>> >>> >> >>>> >> >> >> >>> >>> >> >>>> >> >> >> - chris >>> >>> >> >>>> >> >> > >>> >>> >> >>>> >> >> >> __ __ _ _ ___ ___ >>> >>> >> >>>> >> >> >> \ \/ /___ _ __ | || | / _ \ / _ \ >>> >>> >> >>>> >> >> >> \ // _ \ \047_ \ | || |_| | | | | | | >>> >>> >> >>>> >> >> >> / \ __/ | | | |__ _| |_| | |_| | >>> >>> >> >>>> >> >> >> /_/\_\___|_| |_| |_|(_)___(_)___/ >>> >>> >> >>>> >> >> >> >>> >>> >> >>>> >> >> >> (XEN) Xen version 4.0.0 (root@) (gcc version >>> >>> >> >>>> >> >> >> 4.3.2 (Debian 4.3.2-1.1) ) Thu May 6 13:41:25 >>> >>> >> >>>> >> >> >> EDT 2010 >>> >>> >> >>>> >> >> >> (XEN) Latest ChangeSet: unavailable >>> >>> >> >>>> >> >> >> (XEN) Command line: iommu=verbose dom0_mem=256M >>> >>> >> >>>> >> >> >> dom0_max_vcpus=1 dom0_vcpus_pin=true >>> >>> >> >>>> >> >> >> (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 - 000000000008f000 >>> >>> >> >>>> >> >> >> (usable) >>> >>> >> >>>> >> >> >> (XEN) 000000000008f000 - 0000000000090000 >>> >>> >> >>>> >> >> >> (reserved) >>> >>> >> >>>> >> >> >> (XEN) 0000000000090000 - 000000000009ec00 >>> >>> >> >>>> >> >> >> (usable) >>> >>> >> >>>> >> >> >> (XEN) 000000000009ec00 - 00000000000a0000 >>> >>> >> >>>> >> >> >> (reserved) >>> >>> >> >>>> >> >> >> (XEN) 00000000000e0000 - 0000000000100000 >>> >>> >> >>>> >> >> >> (reserved) >>> >>> >> >>>> >> >> >> (XEN) 0000000000100000 - 00000000cf4bd000 >>> >>> >> >>>> >> >> >> (usable) >>> >>> >> >>>> >> >> >> (XEN) 00000000cf4bd000 - 00000000cf4bf000 >>> >>> >> >>>> >> >> >> (reserved) >>> >>> >> >>>> >> >> >> (XEN) 00000000cf4bf000 - 00000000cf4c2000 >>> >>> >> >>>> >> >> >> (usable) >>> >>> >> >>>> >> >> >> (XEN) 00000000cf4c2000 - 00000000cf7bf000 (ACPI >>> >>> >> >>>> >> >> >> NVS) >>> >>> >> >>>> >> >> >> (XEN) 00000000cf7bf000 - 00000000cf7df000 >>> >>> >> >>>> >> >> >> (usable) >>> >>> >> >>>> >> >> >> (XEN) 00000000cf7df000 - 00000000cf7ff000 (ACPI >>> >>> >> >>>> >> >> >> data) >>> >>> >> >>>> >> >> >> (XEN) 00000000cf7ff000 - 00000000cf800000 >>> >>> >> >>>> >> >> >> (usable) >>> >>> >> >>>> >> >> >> (XEN) 00000000cf800000 - 00000000d0000000 >>> >>> >> >>>> >> >> >> (reserved) >>> >>> >> >>>> >> >> >> (XEN) 00000000f8000000 - 00000000fd000000 >>> >>> >> >>>> >> >> >> (reserved) >>> >>> >> >>>> >> >> >> (XEN) 00000000ffe00000 - 0000000100000000 >>> >>> >> >>>> >> >> >> (reserved) >>> >>> >> >>>> >> >> >> (XEN) 0000000100000000 - 0000000230000000 >>> >>> >> >>>> >> >> >> (usable) >>> >>> >> >>>> >> >> >> (XEN) ACPI: RSDP 000FE020, 0024 (r2 INTEL ) >>> >>> >> >>>> >> >> >> (XEN) ACPI: XSDT CF7FE120, 0074 (r1 INTEL >>> >>> >> >>>> >> >> >> DX58SO 11F6 1000013) >>> >>> >> >>>> >> >> >> (XEN) ACPI: FACP CF7FD000, 00F4 (r3 INTEL >>> >>> >> >>>> >> >> >> DX58SO 11F6 MSFT 100000D) >>> >>> >> >>>> >> >> >> (XEN) ACPI Warning (tbfadt-0444): Optional field >>> >>> >> >>>> >> >> >> "Pm2ControlBlock" has zero address or length: >>> >>> >> >>>> >> >> >> 0000000000000450/0 [20070126] >>> >>> >> >>>> >> >> >> (XEN) ACPI: DSDT CF7F8000, 4641 (r2 INTEL >>> >>> >> >>>> >> >> >> DX58SO 11F6 MSFT 100000D) >>> >>> >> >>>> >> >> >> (XEN) ACPI: FACS CF728000, 0040 >>> >>> >> >>>> >> >> >> (XEN) ACPI: APIC CF7F7000, 0138 (r2 INTEL >>> >>> >> >>>> >> >> >> DX58SO 11F6 MSFT 100000D) >>> >>> >> >>>> >> >> >> (XEN) ACPI: WDDT CF7F6000, 0040 (r1 INTEL >>> >>> >> >>>> >> >> >> DX58SO 11F6 MSFT 100000D) >>> >>> >> >>>> >> >> >> (XEN) ACPI: MCFG CF7F5000, 003C (r1 INTEL >>> >>> >> >>>> >> >> >> DX58SO 11F6 MSFT 100000D) >>> >>> >> >>>> >> >> >> (XEN) ACPI: ASF! CF7F4000, 00AC (r32 INTEL >>> >>> >> >>>> >> >> >> DX58SO 11F6 MSFT 100000D) >>> >>> >> >>>> >> >> >> (XEN) ACPI: HPET CF7F3000, 0038 (r1 INTEL >>> >>> >> >>>> >> >> >> DX58SO 11F6 MSFT 100000D) >>> >>> >> >>>> >> >> >> (XEN) ACPI: SSDT CF7E2000, E134 (r1 INTEL SSDT >>> >>> >> >>>> >> >> >> PM 11F6 MSFT 100000D) >>> >>> >> >>>> >> >> >> (XEN) ACPI: DMAR CF7DF000, 0140 (r1 INTEL >>> >>> >> >>>> >> >> >> DX58SO 11F6 MSFT 100000D) >>> >>> >> >>>> >> >> >> (XEN) ACPI: WDTT CF7F1000, 020C (r2 INTEL >>> >>> >> >>>> >> >> >> DX58SO 11F6 MSFT 100000D) >>> >>> >> >>>> >> >> >> (XEN) ACPI: ASPT CF7F2000, 0034 (r4 INTEL >>> >>> >> >>>> >> >> >> PerfTune 11F6 MSFT 100000D) >>> >>> >> >>>> >> >> >> (XEN) System RAM: 7950MB (8140820kB) >>> >>> >> >>>> >> >> >> (XEN) Domain heap initialised >>> >>> >> >>>> >> >> >> (XEN) Processor #0 7:10 APIC version 21 >>> >>> >> >>>> >> >> >> (XEN) Processor #2 7:10 APIC version 21 >>> >>> >> >>>> >> >> >> (XEN) Processor #4 7:10 APIC version 21 >>> >>> >> >>>> >> >> >> (XEN) Processor #6 7:10 APIC version 21 >>> >>> >> >>>> >> >> >> (XEN) Processor #1 7:10 APIC version 21 >>> >>> >> >>>> >> >> >> (XEN) Processor #3 7:10 APIC version 21 >>> >>> >> >>>> >> >> >> (XEN) Processor #5 7:10 APIC version 21 >>> >>> >> >>>> >> >> >> (XEN) Processor #7 7:10 APIC version 21 >>> >>> >> >>>> >> >> >> (XEN) IOAPIC[0]: apic_id 8, version 32, address >>> >>> >> >>>> >> >> >> 0xfec00000, GSI 0-23 >>> >>> >> >>>> >> >> >> (XEN) Enabling APIC mode: Flat. Using 1 I/O >>> >>> >> >>>> >> >> >> APICs >>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:679: Host address width 39 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: >>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = >>> >>> >> >>>> >> >> >> fe711000 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1b.0 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: >>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = >>> >>> >> >>>> >> >> >> fe710000 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:340: IOAPIC: f0:1f.7 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:411: flags: INCLUDE_ALL >>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >>> >>> >> >>>> >> >> >> e9000 end_address e9fff >>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.1 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >>> >>> >> >>>> >> >> >> ea000 end_address eafff >>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.2 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >>> >>> >> >>>> >> >> >> eb000 end_address ebfff >>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.0 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >>> >>> >> >>>> >> >> >> e6000 end_address e6fff >>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.1 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >>> >>> >> >>>> >> >> >> e7000 end_address e7fff >>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.2 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >>> >>> >> >>>> >> >> >> e8000 end_address e8fff >>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >>> >>> >> >>>> >> >> >> ec000 end_address eefff >>> >>> >> >>>> >> >> >> (XEN) Using scheduler: SMP Credit Scheduler >>> >>> >> >>>> >> >> >> (credit) >>> >>> >> >>>> >> >> >> (XEN) Detected 2800.125 MHz processor. >>> >>> >> >>>> >> >> >> (XEN) Initing memory sharing. >>> >>> >> >>>> >> >> >> (XEN) VMX: Supported advanced features: >>> >>> >> >>>> >> >> >> (XEN) - APIC MMIO access virtualisation >>> >>> >> >>>> >> >> >> (XEN) - APIC TPR shadow >>> >>> >> >>>> >> >> >> (XEN) - Extended Page Tables (EPT) >>> >>> >> >>>> >> >> >> (XEN) - Virtual-Processor Identifiers (VPID) >>> >>> >> >>>> >> >> >> (XEN) - Virtual NMI >>> >>> >> >>>> >> >> >> (XEN) - MSR direct-access bitmap >>> >>> >> >>>> >> >> >> (XEN) HVM: ASIDs enabled. >>> >>> >> >>>> >> >> >> (XEN) HVM: VMX enabled >>> >>> >> >>>> >> >> >> (XEN) HVM: Hardware Assisted Paging detected. >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = >>> >>> >> >>>> >> >> >> fe711000 iommu->reg = ffff82c3fff57000 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c9008010e60262 >>> >>> >> >>>> >> >> >> ecap = f0207a >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = >>> >>> >> >>>> >> >> >> fe710000 iommu->reg = ffff82c3fff56000 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c90780106f0462 >>> >>> >> >>>> >> >> >> ecap = f020fa >>> >>> >> >>>> >> >> >> (XEN) Intel VT-d Snoop Control not supported. >>> >>> >> >>>> >> >> >> (XEN) Intel VT-d DMA Passthrough not supported. >>> >>> >> >>>> >> >> >> (XEN) Intel VT-d Queued Invalidation supported. >>> >>> >> >>>> >> >> >> (XEN) Intel VT-d Interrupt Remapping supported. >>> >>> >> >>>> >> >> >> (XEN) I/O virtualisation enabled >>> >>> >> >>>> >> >> >> (XEN) I/O virtualisation for PV guests disabled >>> >>> >> >>>> >> >> >> (XEN) Total of 8 processors activated. >>> >>> >> >>>> >> >> >> (XEN) ENABLING IO-APIC IRQs >>> >>> >> >>>> >> >> >> (XEN) -> Using new ACK method >>> >>> >> >>>> >> >> >> (XEN) TSC is reliable, synchronization >>> >>> >> >>>> >> >> >> unnecessary >>> >>> >> >>>> >> >> >> (XEN) Platform timer is 14.318MHz HPET >>> >>> >> >>>> >> >> >> (XEN) Allocated console ring of 16 KiB. >>> >>> >> >>>> >> >> >> (XEN) Brought up 8 CPUs >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 0:0.0 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 0:10.0 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 0:10.1 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >>> >>> >> >>>> >> >> >> 0:14.0 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >>> >>> >> >>>> >> >> >> 0:14.1 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >>> >>> >> >>>> >> >> >> 0:14.2 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 0:14.3 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 0:19.0 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 0:1a.0 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 0:1a.1 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 0:1a.2 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 0:1a.7 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >>> >>> >> >>>> >> >> >> 0:1b.0 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 0:1d.0 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 0:1d.1 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 0:1d.2 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 0:1d.7 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 0:1f.0 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 0:1f.2 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 0:1f.3 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 0:1f.5 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 2:0.0 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 2:0.1 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 2:0.2 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 4:0.0 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 4:0.1 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 4:0.2 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >>> >>> >> >>>> >> >> >> 5:0.0 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 7:0.0 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 7:0.1 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 7:0.2 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 9:0.0 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 9:0.1 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 9:0.2 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >>> >>> >> >>>> >> >> >> a:0.0 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> b:3.0 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> b:3.1 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> b:3.2 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> b:3.3 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> b:3.4 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> b:3.5 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> b:3.6 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> b:3.7 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 3f:0.0 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 3f:0.1 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 3f:2.0 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 3f:2.1 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 3f:3.0 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 3f:3.1 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 3f:3.4 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 3f:4.0 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 3f:4.1 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 3f:4.2 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 3f:4.3 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 3f:5.0 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 3f:5.1 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 3f:5.2 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 3f:5.3 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 3f:6.0 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 3f:6.1 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 3f:6.2 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>> >>> >> >>>> >> >> >> 3f:6.3 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:695: >>> >>> >> >>>> >> >> >> iommu_enable_translation: iommu->reg = >>> >>> >> >>>> >> >> >> ffff82c3fff57000 >>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:695: >>> >>> >> >>>> >> >> >> iommu_enable_translation: iommu->reg = >>> >>> >> >>>> >> >> >> ffff82c3fff56000 >>> >>> >> >>>> >> >> >> (XEN) *** LOADING DOMAIN 0 *** >>> >>> >> >>>> >> >> >> (XEN) Xen kernel: 64-bit, lsb, compat32 >>> >>> >> >>>> >> >> >> (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr >>> >>> >> >>>> >> >> >> 0x1000000 -> 0x26ae000 >>> >>> >> >>>> >> >> >> (XEN) PHYSICAL MEMORY ARRANGEMENT: >>> >>> >> >>>> >> >> >> (XEN) Dom0 alloc.: >>> >>> >> >>>> >> >> >> 0000000210000000->0000000220000000 >>> >>> >> >>>> >> >> >> (XEN) VIRTUAL MEMORY ARRANGEMENT: >>> >>> >> >>>> >> >> >> (XEN) Loaded kernel: >>> >>> >> >>>> >> >> >> ffffffff81000000->ffffffff826ae000 >>> >>> >> >>>> >> >> >> (XEN) Init. ramdisk: >>> >>> >> >>>> >> >> >> ffffffff826ae000->ffffffff8f4de600 >>> >>> >> >>>> >> >> >> (XEN) Phys-Mach map: >>> >>> >> >>>> >> >> >> ffffffff8f4df000->ffffffff8f55f000 >>> >>> >> >>>> >> >> >> (XEN) Start info: >>> >>> >> >>>> >> >> >> ffffffff8f55f000->ffffffff8f55f4b4 >>> >>> >> >>>> >> >> >> (XEN) Page tables: >>> >>> >> >>>> >> >> >> ffffffff8f560000->ffffffff8f5df000 >>> >>> >> >>>> >> >> >> (XEN) Boot stack: >>> >>> >> >>>> >> >> >> ffffffff8f5df000->ffffffff8f5e0000 >>> >>> >> >>>> >> >> >> (XEN) TOTAL: >>> >>> >> >>>> >> >> >> ffffffff80000000->ffffffff8f800000 >>> >>> >> >>>> >> >> >> (XEN) ENTRY ADDRESS: ffffffff81a10860 >>> >>> >> >>>> >> >> >> (XEN) Dom0 has maximum 1 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 >>> >>> >> >>>> >> >> >> \047CTRL-a\047 three times to switch input to >>> >>> >> >>>> >> >> >> Xen) >>> >>> >> >>>> >> >> >> (XEN) Freed 164kB init memory. >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 >>> >>> >> >>>> >> >> >> pirq=0 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=2, irq=0 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=000009f0 >>> >>> >> >>>> >> >> >> pirq=0 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 3 already >>> >>> >> >>>> >> >> >> mapped >>> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 4 already >>> >>> >> >>>> >> >> >> mapped >>> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 5 already >>> >>> >> >>>> >> >> >> mapped >>> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 6 already >>> >>> >> >>>> >> >> >> mapped >>> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 7 already >>> >>> >> >>>> >> >> >> mapped >>> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 8 already >>> >>> >> >>>> >> >> >> mapped >>> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 9 already >>> >>> >> >>>> >> >> >> mapped >>> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 10 already >>> >>> >> >>>> >> >> >> mapped >>> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 11 already >>> >>> >> >>>> >> >> >> mapped >>> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 12 already >>> >>> >> >>>> >> >> >> mapped >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000009f0 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 >>> >>> >> >>>> >> >> >> pirq=0 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 >>> >>> >> >>>> >> >> >> pirq=18 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 >>> >>> >> >>>> >> >> >> pirq=19 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=23, irq=23 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a929 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a929 >>> >>> >> >>>> >> >> >> pirq=23 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 >>> >>> >> >>>> >> >> >> pirq=19 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 >>> >>> >> >>>> >> >> >> pirq=18 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 >>> >>> >> >>>> >> >> >> pirq=16 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 >>> >>> >> >>>> >> >> >> pirq=16 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 >>> >>> >> >>>> >> >> >> pirq=19 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 >>> >>> >> >>>> >> >> >> pirq=18 >>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >>> >> >>>> >> >> > >>> >>> >> >>>> >> >> >> _______________________________________________ >>> >>> >> >>>> >> >> >> Xen-users mailing list >>> >>> >> >>>> >> >> >> Xen-users@lists.xensource.com >>> >>> >> >>>> >> >> >> http://lists.xensource.com/xen-users >>> >>> >> >>>> >> >> > >>> >>> >> >>>> >> > >>> >>> >> >>>> > >>> >>> >> >>> >>> >>> >> >> >>> >>> >> > >>> >>> > >>> >> >>> > >> > ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [Xen-devel] Re: RE: Xen4 / Intel DX58SO Mobo / VT-d not working 2010-05-16 13:00 ` chris @ 2010-05-17 17:05 ` chris 2010-05-18 9:31 ` Re: [Xen-users] " Weidong Han 0 siblings, 1 reply; 32+ messages in thread From: chris @ 2010-05-17 17:05 UTC (permalink / raw) To: Han, Weidong; +Cc: Xen-Devel List, Xen-Users List, Pasi Kärkkäinen Can you explain to me what it is you want me to try? I'm not a developer and I don't really understand what you are asking... - chris On Sun, May 16, 2010 at 9:00 AM, chris <tknchris@gmail.com> wrote: > I'm not sure I understand what you want me to do, but that does look > interesting and I didn't notice it before. > > - chris > > On Sun, May 16, 2010 at 3:36 AM, Han, Weidong <weidong.han@intel.com> wrote: >> I noticed this line " (XEN) domctl.c:853:d0 XEN_DOMCTL_assign_device: assign device (2:0.0) failed" in NOTWORKING.txt. could you add some logs to intel_iommu_assign_device to know where it fails? I prefer you to use a clean Xen 4.0 environment. >> >> Regards, >> Weidong >> >> -----Original Message----- >> From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of chris >> Sent: Saturday, May 15, 2010 5:18 AM >> To: Pasi Kärkkäinen >> Cc: Xen-Devel List; Xen-Users List >> Subject: [Xen-devel] Re: [Xen-users] RE: Xen4 / Intel DX58SO Mobo / VT-d not working >> >> Played around with xen_platform_pc, pci_msitranslate, pci_power_mgmt in the cfg, none of which seem to have any effect, also tried >> pci=resource_alignment=02:00.0;02:00.1;02:00.2 on dom0 cmdline, no effect. >> >> I'm worn out been fighting this all day. Attached is some various output from the machine that works with the same cards and has Xen >> 3.4.2 and the new machine with 4.0 which doesn't work. I'm hoping this information can get the right attention and we can figure it out :( >> >> - chris >> >> >> On Fri, May 14, 2010 at 4:50 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>> On Fri, May 14, 2010 at 04:39:54PM -0400, chris wrote: >>>> Alright so a pci sound card works, I tried a geforce 8600 pci e card >>>> and while vga passthrough didnt work it did seem to attach to the >>>> domain ok. So I guess the problem must be somehow related to the >>>> device. I'm still confused since it works in another box. >>>> >>>> I remember there was some reassign_resources or something, maybe the >>>> issue is with some resources the card uses? >>>> >>> >>> http://wiki.xensource.com/xenwiki/XenPCIpassthrough >>> >>> -- Pasi >>> >>>> Below is a lspci -vv of the card >>>> >>>> 02:00.0 USB Controller: NEC Corporation USB (rev 43) (prog-if 10 >>>> [OHCI]) >>>> Subsystem: NEC Corporation Hama USB 2.0 CardBus >>>> Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- >>>> ParErr- Stepping- SERR- FastB2B- DisINTx- >>>> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >>>> >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- >>>> Interrupt: pin A routed to IRQ 16 >>>> Region 0: Memory at d2502000 (32-bit, non-prefetchable) >>>> [disabled] [size=4K] >>>> Capabilities: [40] Power Management version 2 >>>> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA >>>> PME(D0+,D1+,D2+,D3hot+,D3cold-) >>>> Status: D0 PME-Enable- DSel=0 DScale=0 PME- >>>> Kernel driver in use: pciback >>>> >>>> 02:00.1 USB Controller: NEC Corporation USB (rev 43) (prog-if 10 >>>> [OHCI]) >>>> Subsystem: NEC Corporation Hama USB 2.0 CardBus >>>> Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- >>>> ParErr- Stepping- SERR- FastB2B- DisINTx- >>>> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >>>> >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- >>>> Interrupt: pin B routed to IRQ 17 >>>> Region 0: Memory at d2501000 (32-bit, non-prefetchable) >>>> [disabled] [size=4K] >>>> Capabilities: [40] Power Management version 2 >>>> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA >>>> PME(D0+,D1+,D2+,D3hot+,D3cold-) >>>> Status: D0 PME-Enable- DSel=0 DScale=0 PME- >>>> Kernel driver in use: pciback >>>> >>>> 02:00.2 USB Controller: NEC Corporation USB 2.0 (rev 04) (prog-if 20 >>>> [EHCI]) >>>> Subsystem: NEC Corporation USB 2.0 >>>> Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- >>>> ParErr- Stepping- SERR- FastB2B- DisINTx- >>>> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >>>> >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- >>>> Interrupt: pin C routed to IRQ 18 >>>> Region 0: Memory at d2500000 (32-bit, non-prefetchable) >>>> [disabled] [size=256] >>>> Capabilities: [40] Power Management version 2 >>>> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA >>>> PME(D0+,D1+,D2+,D3hot+,D3cold-) >>>> Status: D0 PME-Enable- DSel=0 DScale=0 PME- >>>> Kernel driver in use: pciback >>>> >>>> >>>> On Fri, May 14, 2010 at 3:46 PM, chris <tknchris@gmail.com> wrote: >>>> > I added a pci sound card and interestingly that works. I'm digging >>>> > around for another pci-e device to try to identify if its all pci-e >>>> > or only this device. Strange this is that I have a few other >>>> > machines with this same usb controller which is working on 3.4.2. >>>> > >>>> > *scratches head* >>>> > >>>> > - chris >>>> > >>>> > On Fri, May 14, 2010 at 3:21 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>>> >> On Fri, May 14, 2010 at 03:18:02PM -0400, chris wrote: >>>> >>> It is a multifunction device, a pci-e usb controller, so I >>>> >>> assumed all them had to be passed through. I just changed it to >>>> >>> only 02:00.0 and same thing >>>> >>> >>>> >>> test-box2:~# cat /etc/xen/vm-five.cfg | grep pci pci = >>>> >>> ['02:00.0'] test-box2:~# xm create /etc/xen/vm-five.cfg Using >>>> >>> config file "/etc/xen/vm-five.cfg". >>>> >>> Error: Failed to assign device to IOMMU >>>> >>> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>>> >>> >>>> >> >>>> >> Hmm.. weird. >>>> >> >>>> >> Two things to try: >>>> >> >>>> >> 1) Try passthru some other device (which is just a single pci id) >>>> >> 2) Try passthru that pci-e usb controller to Linux PV guest and >>>> >> see if that works >>>> >> >>>> >> -- Pasi >>>> >> >>>> >>> >>>> >>> On Fri, May 14, 2010 at 3:11 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>>> >>> > On Fri, May 14, 2010 at 03:05:49PM -0400, chris wrote: >>>> >>> >> Pasi, >>>> >>> >> >>>> >>> >> Tried latest stable/2.6.32.x per your advice, no change. >>>> >>> >> Anyone on xen-devel that can help me troubleshoot further? >>>> >>> >> Everything looks right, can't figure out why vt-d is not >>>> >>> >> working but it must be some kind of bug :( >>>> >>> >> >>>> >>> > >>>> >>> > Did you try the suggestion said earlier.. try to just passthru the first pci device? >>>> >>> > >>>> >>> > -- Pasi >>>> >>> > >>>> >>> >> test-box2:~# uname -a >>>> >>> >> Linux test-box2 2.6.32.12 #1 SMP Fri May 14 13:40:05 EDT 2010 >>>> >>> >> x86_64 GNU/Linux >>>> >>> >> >>>> >>> >> test-box2:~# xm info | grep virt_caps virt_caps : >>>> >>> >> hvm hvm_directio >>>> >>> >> >>>> >>> >> test-box2:~# xm pci-list-assignable-devices 0000:02:00.0 >>>> >>> >> 0000:02:00.1 >>>> >>> >> 0000:02:00.2 >>>> >>> >> >>>> >>> >> test-box2:~# xm create /etc/xen/vm-five.cfg Using config file >>>> >>> >> "/etc/xen/vm-five.cfg". >>>> >>> >> Error: Failed to assign device to IOMMU >>>> >>> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>>> >>> >> >>>> >>> >> test-box2:~# cat /etc/xen/vm-five.cfg | grep -v '#' >>>> >>> >> kernel = '/usr/lib/xen/boot/hvmloader' >>>> >>> >> builder = 'hvm' >>>> >>> >> memory = '1792' >>>> >>> >> device_model='/usr/lib/xen/bin/qemu-dm' >>>> >>> >> disk = [ 'phy:/dev/storage/vm-five,ioemu:hda,w', >>>> >>> >> 'phy:/dev/sr0,ioemu:hdc:cdrom,r' >>>> >>> >> ] >>>> >>> >> name = 'vm-five' >>>> >>> >> vif = ['type=ioemu, bridge=eth0, mac=00:16:3D:37:A1:42'] >>>> >>> >> boot='dc' >>>> >>> >> cpus='0-1' >>>> >>> >> vcpus=2 >>>> >>> >> acpi=1 >>>> >>> >> ahci=1 >>>> >>> >> vnc=1 >>>> >>> >> sdl=0 >>>> >>> >> timer_mode=1 >>>> >>> >> usb=1 >>>> >>> >> usbdevice='tablet' >>>> >>> >> localtime=1 >>>> >>> >> pci = ['02:00.0','02:00.1','02:00.2'] >>>> >>> >> >>>> >>> >> On Thu, May 13, 2010 at 2:28 PM, chris <tknchris@gmail.com> wrote: >>>> >>> >> > Forwarding to xen-devel. Can't seem to get VT-d working with >>>> >>> >> > xen4 from tarball on xen.org 2.6.31.13 pv_ops dom0. On >>>> >>> >> > pasi's advice I tried switching to stable/2.6.32.x branch >>>> >>> >> > for dom0 and that doesnt even build. Did something change recently thats breaking compilation? >>>> >>> >> > >>>> >>> >> > Attached is xen dmesg with iommu=verbose loglvl=all >>>> >>> >> > guest_loglvl=all, and dom0 dmesg from 2.6.31.x >>>> >>> >> > >>>> >>> >> > Any ideas on why VT-d is not working on this board? >>>> >>> >> > Initialization looks good, xen reports hvm_directio >>>> >>> >> > capability, everything says VT-d should work until domain is created. >>>> >>> >> > >>>> >>> >> > Any ideas why stable/2.6.32.x wont build? >>>> >>> >> > >>>> >>> >> > - chris >>>> >>> >> > >>>> >>> >> > On Thu, May 13, 2010 at 2:07 PM, chris <tknchris@gmail.com> wrote: >>>> >>> >> >> I redid it with oldconfig which I didn't think would help >>>> >>> >> >> and same thing. I guess this tree is broken? Can someone >>>> >>> >> >> else try and see if they can build it? Ugh, whata day :) >>>> >>> >> >> >>>> >>> >> >> On Thu, May 13, 2010 at 1:58 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>>> >>> >> >>> On Thu, May 13, 2010 at 01:55:25PM -0400, chris wrote: >>>> >>> >> >>>> I used the default config on the wiki which you created. Steps I took were: >>>> >>> >> >>>> >>>> >>> >> >>>> # make clean distclean >>>> >>> >> >>>> # wget -O .config >>>> >>> >> >>>> "http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.10-pvops-dom0-xen-stable-x86_64" >>>> >>> >> >>> >>>> >>> >> >>> You should do "make oldconfig" at this point. >>>> >>> >> >>> >>>> >>> >> >>>> # make -j8 bzImage >>>> >>> >> >>>> (blah blah) >>>> >>> >> >>>> LD vmlinux.o >>>> >>> >> >>>> MODPOST vmlinux.o >>>> >>> >> >>>> WARNING: modpost: Found 7 section mismatch(es). >>>> >>> >> >>>> To see full details build your kernel with: >>>> >>> >> >>>> 'make CONFIG_DEBUG_SECTION_MISMATCH=y' >>>> >>> >> >>>> GEN .version >>>> >>> >> >>>> CHK include/linux/compile.h >>>> >>> >> >>>> UPD include/linux/compile.h >>>> >>> >> >>>> CC init/version.o >>>> >>> >> >>>> LD init/built-in.o >>>> >>> >> >>>> LD .tmp_vmlinux1 >>>> >>> >> >>>> drivers/built-in.o: In function `do_hvm_suspend': >>>> >>> >> >>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: >>>> >>> >> >>>> undefined reference to `xenbus_suspend' >>>> >>> >> >>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: >>>> >>> >> >>>> undefined reference to `xenbus_resume' >>>> >>> >> >>>> make: *** [.tmp_vmlinux1] Error 1 >>>> >>> >> >>>> >>>> >>> >> >>> >>>> >>> >> >>> Hmm.. weird. I wonder if something has changed recently or what's going on in here.. >>>> >>> >> >>> >>>> >>> >> >>> -- Pasi >>>> >>> >> >>> >>>> >>> >> >>>> >>>> >>> >> >>>> On Thu, May 13, 2010 at 11:47 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>>> >>> >> >>>> > On Thu, May 13, 2010 at 11:33:57AM -0400, chris wrote: >>>> >>> >> >>>> >> Successfully grabbed the sources and failed to build: >>>> >>> >> >>>> >> >>>> >>> >> >>>> >> LD .tmp_vmlinux1 >>>> >>> >> >>>> >> drivers/built-in.o: In function `do_hvm_suspend': >>>> >>> >> >>>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: >>>> >>> >> >>>> >> undefined reference to `xenbus_suspend' >>>> >>> >> >>>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: >>>> >>> >> >>>> >> undefined reference to `xenbus_resume' >>>> >>> >> >>>> >> make: *** [.tmp_vmlinux1] Error 1 >>>> >>> >> >>>> >> >>>> >>> >> >>>> >> :( >>>> >>> >> >>>> >> >>>> >>> >> >>>> > >>>> >>> >> >>>> > Try the example .config files provided on the wiki page. >>>> >>> >> >>>> > >>>> >>> >> >>>> > -- Pasi >>>> >>> >> >>>> > >>>> >>> >> >>>> >> On Thu, May 13, 2010 at 10:14 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>>> >>> >> >>>> >> > On Thu, May 13, 2010 at 10:12:56AM -0400, chris wrote: >>>> >>> >> >>>> >> >> Pasi, >>>> >>> >> >>>> >> >> >>>> >>> >> >>>> >> >> How do I pull those kernel sources you referenced? >>>> >>> >> >>>> >> >> I see it mentioned on >>>> >>> >> >>>> >> >> http://wiki.xensource.com/xenwiki/XenParavirtOps but no details on how to retrieve it. >>>> >>> >> >>>> >> >> >>>> >>> >> >>>> >> > >>>> >>> >> >>>> >> > The instructions are there if you read it carefully.. >>>> >>> >> >>>> >> > There's the topic of how to switch branches. >>>> >>> >> >>>> >> > >>>> >>> >> >>>> >> > -- Pasi >>>> >>> >> >>>> >> > >>>> >>> >> >>>> >> >> - chris >>>> >>> >> >>>> >> >> >>>> >>> >> >>>> >> >> On Thu, May 13, 2010 at 8:29 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>>> >>> >> >>>> >> >> > On Wed, May 12, 2010 at 08:41:34PM -0400, chris wrote: >>>> >>> >> >>>> >> >> >> When reading the vtdhowto I noticed the ability to set iommu=verbose. >>>> >>> >> >>>> >> >> >> Here is that output, I don't know if it helps at >>>> >>> >> >>>> >> >> >> all to figure out what is wrong. >>>> >>> >> >>>> >> >> >> >>>> >>> >> >>>> >> >> > >>>> >>> >> >>>> >> >> > That seems to be OK: >>>> >>> >> >>>> >> >> > >>>> >>> >> >>>> >> >> > (XEN) I/O virtualisation enabled >>>> >>> >> >>>> >> >> > (XEN) I/O virtualisation for PV guests disabled >>>> >>> >> >>>> >> >> > >>>> >>> >> >>>> >> >> > So hmm.. I wonder if it's related to MSI stuff? >>>> >>> >> >>>> >> >> > You could try xen.git xen/stable-2.6.32.x branch instead and see if that makes a difference.. >>>> >>> >> >>>> >> >> > >>>> >>> >> >>>> >> >> > -- Pasi >>>> >>> >> >>>> >> >> > >>>> >>> >> >>>> >> >> >> >>>> >>> >> >>>> >> >> >> ---------- Forwarded message ---------- >>>> >>> >> >>>> >> >> >> From: chris <tknchris@gmail.com> >>>> >>> >> >>>> >> >> >> Date: Wed, May 12, 2010 at 5:28 PM >>>> >>> >> >>>> >> >> >> Subject: Xen4 / Intel DX58SO Mobo / VT-d not >>>> >>> >> >>>> >> >> >> working >>>> >>> >> >>>> >> >> >> To: Xen-Users List >>>> >>> >> >>>> >> >> >> <xen-users@lists.xensource.com> >>>> >>> >> >>>> >> >> >> >>>> >>> >> >>>> >> >> >> >>>> >>> >> >>>> >> >> >> Hello, >>>> >>> >> >>>> >> >> >> >>>> >>> >> >>>> >> >> >> I've previously been successful with Xen4 and >>>> >>> >> >>>> >> >> >> VT-d on other systems. I am having trouble >>>> >>> >> >>>> >> >> >> getting VT-d passthrough working to a WinXP >>>> >>> >> >>>> >> >> >> domain with DX58SO (Q45) motherboard and i7 930 >>>> >>> >> >>>> >> >> >> CPU. VT-d is enabled in bios, xm info shows >>>> >>> >> >>>> >> >> >> hvm_directio capability, I have iommu=1 set, I >>>> >>> >> >>>> >> >> >> have the devices bound to pciback on dom0 cmdline, xm pci-list-assignable-devices shows the devices as assignable. When I attempt to start the VM I get the error: >>>> >>> >> >>>> >> >> >> >>>> >>> >> >>>> >> >> >> Error: Failed to assign device to IOMMU >>>> >>> >> >>>> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>>> >>> >> >>>> >> >> >> >>>> >>> >> >>>> >> >> >> Below is all the information I can think of that >>>> >>> >> >>>> >> >> >> would be useful to help debug it: >>>> >>> >> >>>> >> >> >> >>>> >>> >> >>>> >> >> >> BIOS VT-d Enabled: >>>> >>> >> >>>> >> >> >> http://i43.tinypic.com/nl3a5e.jpg >>>> >>> >> >>>> >> >> >> http://i42.tinypic.com/nqvlu1.jpg >>>> >>> >> >>>> >> >> >> >>>> >>> >> >>>> >> >> >> grub entry: >>>> >>> >> >>>> >> >> >> >>>> >>> >> >>>> >> >> >> title Xen 4.0.0 / Debian GNU/Linux, >>>> >>> >> >>>> >> >> >> kernel 2.6.31.13 root (hd0,0) kernel >>>> >>> >> >>>> >> >> >> /boot/xen-4.0.0.gz iommu=1 dom0_mem=256M >>>> >>> >> >>>> >> >> >> dom0_max_vcpus=1 dom0_vcpus_pin=true module >>>> >>> >> >>>> >> >> >> /boot/vmlinuz-2.6.31.13 root=/dev/md0 ro >>>> >>> >> >>>> >> >> >> console=tty0 xen-pciback.permissive >>>> >>> >> >>>> >> >> >> xen-pciback.hide=(02:00.0)(02:00.1)(02:00.2)(04: >>>> >>> >> >>>> >> >> >> 00.0)(04:00.1)(04:00.2)(07:00.0)(07:00.1)(07:00. >>>> >>> >> >>>> >> >> >> 2)(09:00.0)(09:00.1)(09:00.2) module >>>> >>> >> >>>> >> >> >> /boot/initrd.img-2.6.31.13 >>>> >>> >> >>>> >> >> >> >>>> >>> >> >>>> >> >> >> # xm pci-list-assignable-devices 0000:09:00.0 >>>> >>> >> >>>> >> >> >> 0000:09:00.1 >>>> >>> >> >>>> >> >> >> 0000:09:00.2 >>>> >>> >> >>>> >> >> >> 0000:07:00.0 >>>> >>> >> >>>> >> >> >> 0000:07:00.1 >>>> >>> >> >>>> >> >> >> 0000:07:00.2 >>>> >>> >> >>>> >> >> >> 0000:04:00.0 >>>> >>> >> >>>> >> >> >> 0000:04:00.1 >>>> >>> >> >>>> >> >> >> 0000:04:00.2 >>>> >>> >> >>>> >> >> >> 0000:02:00.0 >>>> >>> >> >>>> >> >> >> 0000:02:00.1 >>>> >>> >> >>>> >> >> >> 0000:02:00.2 >>>> >>> >> >>>> >> >> >> >>>> >>> >> >>>> >> >> >> # xm info >>>> >>> >> >>>> >> >> >> host : test-box2 release >>>> >>> >> >>>> >> >> >> : 2.6.31.13 version : #2 SMP Wed >>>> >>> >> >>>> >> >> >> May 12 14:11:37 EDT 2010 machine >>>> >>> >> >>>> >> >> >> : x86_64 nr_cpus : 8 nr_nodes >>>> >>> >> >>>> >> >> >> : 1 cores_per_socket : 4 threads_per_core >>>> >>> >> >>>> >> >> >> : 2 cpu_mhz : 2800 hw_caps >>>> >>> >> >>>> >> >> >> : >>>> >>> >> >>>> >> >> >> bfebfbff:28100800:00000000:00001b40:0098e3bd:000 >>>> >>> >> >>>> >> >> >> 00000:00000001:00000000 virt_caps : >>>> >>> >> >>>> >> >> >> hvm hvm_directio total_memory : 7950 >>>> >>> >> >>>> >> >> >> free_memory : 7812 node_to_cpu >>>> >>> >> >>>> >> >> >> : node0:0-7 node_to_memory : node0:7812 >>>> >>> >> >>>> >> >> >> node_to_dma32_mem : node0:3249 max_node_id >>>> >>> >> >>>> >> >> >> : 0 xen_major : 4 xen_minor >>>> >>> >> >>>> >> >> >> : 0 xen_extra : .0 xen_caps >>>> >>> >> >>>> >> >> >> : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 >>>> >>> >> >>>> >> >> >> hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler >>>> >>> >> >>>> >> >> >> : credit xen_pagesize : 4096 >>>> >>> >> >>>> >> >> >> platform_params : >>>> >>> >> >>>> >> >> >> virt_start=0xffff800000000000 xen_changeset >>>> >>> >> >>>> >> >> >> : unavailable xen_commandline : iommu=1 >>>> >>> >> >>>> >> >> >> dom0_mem=256M dom0_max_vcpus=1 >>>> >>> >> >>>> >> >> >> dom0_vcpus_pin=true cc_compiler : gcc >>>> >>> >> >>>> >> >> >> version 4.3.2 (Debian 4.3.2-1.1) cc_compile_by >>>> >>> >> >>>> >> >> >> : root cc_compile_domain : >>>> >>> >> >>>> >> >> >> cc_compile_date : Thu May 6 13:41:25 EDT >>>> >>> >> >>>> >> >> >> 2010 xend_config_format : 4 >>>> >>> >> >>>> >> >> >> >>>> >>> >> >>>> >> >> >> # xm create vm-five.cfg Using config file >>>> >>> >> >>>> >> >> >> "./vm-five.cfg". >>>> >>> >> >>>> >> >> >> Error: Failed to assign device to IOMMU >>>> >>> >> >>>> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>>> >>> >> >>>> >> >> >> >>>> >>> >> >>>> >> >> >> I feel like I'm missing something really obvious >>>> >>> >> >>>> >> >> >> but I've been at it for a while now and have run >>>> >>> >> >>>> >> >> >> out of brain power. Anyone have any idea what might be wrong? >>>> >>> >> >>>> >> >> >> >>>> >>> >> >>>> >> >> >> - chris >>>> >>> >> >>>> >> >> > >>>> >>> >> >>>> >> >> >> __ __ _ _ ___ ___ >>>> >>> >> >>>> >> >> >> \ \/ /___ _ __ | || | / _ \ / _ \ >>>> >>> >> >>>> >> >> >> \ // _ \ \047_ \ | || |_| | | | | | | >>>> >>> >> >>>> >> >> >> / \ __/ | | | |__ _| |_| | |_| | >>>> >>> >> >>>> >> >> >> /_/\_\___|_| |_| |_|(_)___(_)___/ >>>> >>> >> >>>> >> >> >> >>>> >>> >> >>>> >> >> >> (XEN) Xen version 4.0.0 (root@) (gcc version >>>> >>> >> >>>> >> >> >> 4.3.2 (Debian 4.3.2-1.1) ) Thu May 6 13:41:25 >>>> >>> >> >>>> >> >> >> EDT 2010 >>>> >>> >> >>>> >> >> >> (XEN) Latest ChangeSet: unavailable >>>> >>> >> >>>> >> >> >> (XEN) Command line: iommu=verbose dom0_mem=256M >>>> >>> >> >>>> >> >> >> dom0_max_vcpus=1 dom0_vcpus_pin=true >>>> >>> >> >>>> >> >> >> (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 - 000000000008f000 >>>> >>> >> >>>> >> >> >> (usable) >>>> >>> >> >>>> >> >> >> (XEN) 000000000008f000 - 0000000000090000 >>>> >>> >> >>>> >> >> >> (reserved) >>>> >>> >> >>>> >> >> >> (XEN) 0000000000090000 - 000000000009ec00 >>>> >>> >> >>>> >> >> >> (usable) >>>> >>> >> >>>> >> >> >> (XEN) 000000000009ec00 - 00000000000a0000 >>>> >>> >> >>>> >> >> >> (reserved) >>>> >>> >> >>>> >> >> >> (XEN) 00000000000e0000 - 0000000000100000 >>>> >>> >> >>>> >> >> >> (reserved) >>>> >>> >> >>>> >> >> >> (XEN) 0000000000100000 - 00000000cf4bd000 >>>> >>> >> >>>> >> >> >> (usable) >>>> >>> >> >>>> >> >> >> (XEN) 00000000cf4bd000 - 00000000cf4bf000 >>>> >>> >> >>>> >> >> >> (reserved) >>>> >>> >> >>>> >> >> >> (XEN) 00000000cf4bf000 - 00000000cf4c2000 >>>> >>> >> >>>> >> >> >> (usable) >>>> >>> >> >>>> >> >> >> (XEN) 00000000cf4c2000 - 00000000cf7bf000 (ACPI >>>> >>> >> >>>> >> >> >> NVS) >>>> >>> >> >>>> >> >> >> (XEN) 00000000cf7bf000 - 00000000cf7df000 >>>> >>> >> >>>> >> >> >> (usable) >>>> >>> >> >>>> >> >> >> (XEN) 00000000cf7df000 - 00000000cf7ff000 (ACPI >>>> >>> >> >>>> >> >> >> data) >>>> >>> >> >>>> >> >> >> (XEN) 00000000cf7ff000 - 00000000cf800000 >>>> >>> >> >>>> >> >> >> (usable) >>>> >>> >> >>>> >> >> >> (XEN) 00000000cf800000 - 00000000d0000000 >>>> >>> >> >>>> >> >> >> (reserved) >>>> >>> >> >>>> >> >> >> (XEN) 00000000f8000000 - 00000000fd000000 >>>> >>> >> >>>> >> >> >> (reserved) >>>> >>> >> >>>> >> >> >> (XEN) 00000000ffe00000 - 0000000100000000 >>>> >>> >> >>>> >> >> >> (reserved) >>>> >>> >> >>>> >> >> >> (XEN) 0000000100000000 - 0000000230000000 >>>> >>> >> >>>> >> >> >> (usable) >>>> >>> >> >>>> >> >> >> (XEN) ACPI: RSDP 000FE020, 0024 (r2 INTEL ) >>>> >>> >> >>>> >> >> >> (XEN) ACPI: XSDT CF7FE120, 0074 (r1 INTEL >>>> >>> >> >>>> >> >> >> DX58SO 11F6 1000013) >>>> >>> >> >>>> >> >> >> (XEN) ACPI: FACP CF7FD000, 00F4 (r3 INTEL >>>> >>> >> >>>> >> >> >> DX58SO 11F6 MSFT 100000D) >>>> >>> >> >>>> >> >> >> (XEN) ACPI Warning (tbfadt-0444): Optional field >>>> >>> >> >>>> >> >> >> "Pm2ControlBlock" has zero address or length: >>>> >>> >> >>>> >> >> >> 0000000000000450/0 [20070126] >>>> >>> >> >>>> >> >> >> (XEN) ACPI: DSDT CF7F8000, 4641 (r2 INTEL >>>> >>> >> >>>> >> >> >> DX58SO 11F6 MSFT 100000D) >>>> >>> >> >>>> >> >> >> (XEN) ACPI: FACS CF728000, 0040 >>>> >>> >> >>>> >> >> >> (XEN) ACPI: APIC CF7F7000, 0138 (r2 INTEL >>>> >>> >> >>>> >> >> >> DX58SO 11F6 MSFT 100000D) >>>> >>> >> >>>> >> >> >> (XEN) ACPI: WDDT CF7F6000, 0040 (r1 INTEL >>>> >>> >> >>>> >> >> >> DX58SO 11F6 MSFT 100000D) >>>> >>> >> >>>> >> >> >> (XEN) ACPI: MCFG CF7F5000, 003C (r1 INTEL >>>> >>> >> >>>> >> >> >> DX58SO 11F6 MSFT 100000D) >>>> >>> >> >>>> >> >> >> (XEN) ACPI: ASF! CF7F4000, 00AC (r32 INTEL >>>> >>> >> >>>> >> >> >> DX58SO 11F6 MSFT 100000D) >>>> >>> >> >>>> >> >> >> (XEN) ACPI: HPET CF7F3000, 0038 (r1 INTEL >>>> >>> >> >>>> >> >> >> DX58SO 11F6 MSFT 100000D) >>>> >>> >> >>>> >> >> >> (XEN) ACPI: SSDT CF7E2000, E134 (r1 INTEL SSDT >>>> >>> >> >>>> >> >> >> PM 11F6 MSFT 100000D) >>>> >>> >> >>>> >> >> >> (XEN) ACPI: DMAR CF7DF000, 0140 (r1 INTEL >>>> >>> >> >>>> >> >> >> DX58SO 11F6 MSFT 100000D) >>>> >>> >> >>>> >> >> >> (XEN) ACPI: WDTT CF7F1000, 020C (r2 INTEL >>>> >>> >> >>>> >> >> >> DX58SO 11F6 MSFT 100000D) >>>> >>> >> >>>> >> >> >> (XEN) ACPI: ASPT CF7F2000, 0034 (r4 INTEL >>>> >>> >> >>>> >> >> >> PerfTune 11F6 MSFT 100000D) >>>> >>> >> >>>> >> >> >> (XEN) System RAM: 7950MB (8140820kB) >>>> >>> >> >>>> >> >> >> (XEN) Domain heap initialised >>>> >>> >> >>>> >> >> >> (XEN) Processor #0 7:10 APIC version 21 >>>> >>> >> >>>> >> >> >> (XEN) Processor #2 7:10 APIC version 21 >>>> >>> >> >>>> >> >> >> (XEN) Processor #4 7:10 APIC version 21 >>>> >>> >> >>>> >> >> >> (XEN) Processor #6 7:10 APIC version 21 >>>> >>> >> >>>> >> >> >> (XEN) Processor #1 7:10 APIC version 21 >>>> >>> >> >>>> >> >> >> (XEN) Processor #3 7:10 APIC version 21 >>>> >>> >> >>>> >> >> >> (XEN) Processor #5 7:10 APIC version 21 >>>> >>> >> >>>> >> >> >> (XEN) Processor #7 7:10 APIC version 21 >>>> >>> >> >>>> >> >> >> (XEN) IOAPIC[0]: apic_id 8, version 32, address >>>> >>> >> >>>> >> >> >> 0xfec00000, GSI 0-23 >>>> >>> >> >>>> >> >> >> (XEN) Enabling APIC mode: Flat. Using 1 I/O >>>> >>> >> >>>> >> >> >> APICs >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:679: Host address width 39 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = >>>> >>> >> >>>> >> >> >> fe711000 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1b.0 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = >>>> >>> >> >>>> >> >> >> fe710000 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:340: IOAPIC: f0:1f.7 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:411: flags: INCLUDE_ALL >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >>>> >>> >> >>>> >> >> >> e9000 end_address e9fff >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.1 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >>>> >>> >> >>>> >> >> >> ea000 end_address eafff >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.2 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >>>> >>> >> >>>> >> >> >> eb000 end_address ebfff >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.0 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >>>> >>> >> >>>> >> >> >> e6000 end_address e6fff >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.1 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >>>> >>> >> >>>> >> >> >> e7000 end_address e7fff >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.2 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >>>> >>> >> >>>> >> >> >> e8000 end_address e8fff >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >>>> >>> >> >>>> >> >> >> ec000 end_address eefff >>>> >>> >> >>>> >> >> >> (XEN) Using scheduler: SMP Credit Scheduler >>>> >>> >> >>>> >> >> >> (credit) >>>> >>> >> >>>> >> >> >> (XEN) Detected 2800.125 MHz processor. >>>> >>> >> >>>> >> >> >> (XEN) Initing memory sharing. >>>> >>> >> >>>> >> >> >> (XEN) VMX: Supported advanced features: >>>> >>> >> >>>> >> >> >> (XEN) - APIC MMIO access virtualisation >>>> >>> >> >>>> >> >> >> (XEN) - APIC TPR shadow >>>> >>> >> >>>> >> >> >> (XEN) - Extended Page Tables (EPT) >>>> >>> >> >>>> >> >> >> (XEN) - Virtual-Processor Identifiers (VPID) >>>> >>> >> >>>> >> >> >> (XEN) - Virtual NMI >>>> >>> >> >>>> >> >> >> (XEN) - MSR direct-access bitmap >>>> >>> >> >>>> >> >> >> (XEN) HVM: ASIDs enabled. >>>> >>> >> >>>> >> >> >> (XEN) HVM: VMX enabled >>>> >>> >> >>>> >> >> >> (XEN) HVM: Hardware Assisted Paging detected. >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = >>>> >>> >> >>>> >> >> >> fe711000 iommu->reg = ffff82c3fff57000 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c9008010e60262 >>>> >>> >> >>>> >> >> >> ecap = f0207a >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = >>>> >>> >> >>>> >> >> >> fe710000 iommu->reg = ffff82c3fff56000 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c90780106f0462 >>>> >>> >> >>>> >> >> >> ecap = f020fa >>>> >>> >> >>>> >> >> >> (XEN) Intel VT-d Snoop Control not supported. >>>> >>> >> >>>> >> >> >> (XEN) Intel VT-d DMA Passthrough not supported. >>>> >>> >> >>>> >> >> >> (XEN) Intel VT-d Queued Invalidation supported. >>>> >>> >> >>>> >> >> >> (XEN) Intel VT-d Interrupt Remapping supported. >>>> >>> >> >>>> >> >> >> (XEN) I/O virtualisation enabled >>>> >>> >> >>>> >> >> >> (XEN) I/O virtualisation for PV guests disabled >>>> >>> >> >>>> >> >> >> (XEN) Total of 8 processors activated. >>>> >>> >> >>>> >> >> >> (XEN) ENABLING IO-APIC IRQs >>>> >>> >> >>>> >> >> >> (XEN) -> Using new ACK method >>>> >>> >> >>>> >> >> >> (XEN) TSC is reliable, synchronization >>>> >>> >> >>>> >> >> >> unnecessary >>>> >>> >> >>>> >> >> >> (XEN) Platform timer is 14.318MHz HPET >>>> >>> >> >>>> >> >> >> (XEN) Allocated console ring of 16 KiB. >>>> >>> >> >>>> >> >> >> (XEN) Brought up 8 CPUs >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 0:0.0 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 0:10.0 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 0:10.1 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >>>> >>> >> >>>> >> >> >> 0:14.0 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >>>> >>> >> >>>> >> >> >> 0:14.1 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >>>> >>> >> >>>> >> >> >> 0:14.2 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 0:14.3 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 0:19.0 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 0:1a.0 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 0:1a.1 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 0:1a.2 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 0:1a.7 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >>>> >>> >> >>>> >> >> >> 0:1b.0 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 0:1d.0 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 0:1d.1 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 0:1d.2 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 0:1d.7 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 0:1f.0 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 0:1f.2 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 0:1f.3 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 0:1f.5 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 2:0.0 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 2:0.1 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 2:0.2 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 4:0.0 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 4:0.1 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 4:0.2 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >>>> >>> >> >>>> >> >> >> 5:0.0 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 7:0.0 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 7:0.1 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 7:0.2 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 9:0.0 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 9:0.1 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 9:0.2 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >>>> >>> >> >>>> >> >> >> a:0.0 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> b:3.0 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> b:3.1 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> b:3.2 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> b:3.3 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> b:3.4 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> b:3.5 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> b:3.6 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> b:3.7 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 3f:0.0 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 3f:0.1 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 3f:2.0 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 3f:2.1 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 3f:3.0 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 3f:3.1 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 3f:3.4 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 3f:4.0 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 3f:4.1 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 3f:4.2 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 3f:4.3 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 3f:5.0 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 3f:5.1 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 3f:5.2 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 3f:5.3 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 3f:6.0 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 3f:6.1 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 3f:6.2 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>> >>> >> >>>> >> >> >> 3f:6.3 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:695: >>>> >>> >> >>>> >> >> >> iommu_enable_translation: iommu->reg = >>>> >>> >> >>>> >> >> >> ffff82c3fff57000 >>>> >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:695: >>>> >>> >> >>>> >> >> >> iommu_enable_translation: iommu->reg = >>>> >>> >> >>>> >> >> >> ffff82c3fff56000 >>>> >>> >> >>>> >> >> >> (XEN) *** LOADING DOMAIN 0 *** >>>> >>> >> >>>> >> >> >> (XEN) Xen kernel: 64-bit, lsb, compat32 >>>> >>> >> >>>> >> >> >> (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr >>>> >>> >> >>>> >> >> >> 0x1000000 -> 0x26ae000 >>>> >>> >> >>>> >> >> >> (XEN) PHYSICAL MEMORY ARRANGEMENT: >>>> >>> >> >>>> >> >> >> (XEN) Dom0 alloc.: >>>> >>> >> >>>> >> >> >> 0000000210000000->0000000220000000 >>>> >>> >> >>>> >> >> >> (XEN) VIRTUAL MEMORY ARRANGEMENT: >>>> >>> >> >>>> >> >> >> (XEN) Loaded kernel: >>>> >>> >> >>>> >> >> >> ffffffff81000000->ffffffff826ae000 >>>> >>> >> >>>> >> >> >> (XEN) Init. ramdisk: >>>> >>> >> >>>> >> >> >> ffffffff826ae000->ffffffff8f4de600 >>>> >>> >> >>>> >> >> >> (XEN) Phys-Mach map: >>>> >>> >> >>>> >> >> >> ffffffff8f4df000->ffffffff8f55f000 >>>> >>> >> >>>> >> >> >> (XEN) Start info: >>>> >>> >> >>>> >> >> >> ffffffff8f55f000->ffffffff8f55f4b4 >>>> >>> >> >>>> >> >> >> (XEN) Page tables: >>>> >>> >> >>>> >> >> >> ffffffff8f560000->ffffffff8f5df000 >>>> >>> >> >>>> >> >> >> (XEN) Boot stack: >>>> >>> >> >>>> >> >> >> ffffffff8f5df000->ffffffff8f5e0000 >>>> >>> >> >>>> >> >> >> (XEN) TOTAL: >>>> >>> >> >>>> >> >> >> ffffffff80000000->ffffffff8f800000 >>>> >>> >> >>>> >> >> >> (XEN) ENTRY ADDRESS: ffffffff81a10860 >>>> >>> >> >>>> >> >> >> (XEN) Dom0 has maximum 1 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 >>>> >>> >> >>>> >> >> >> \047CTRL-a\047 three times to switch input to >>>> >>> >> >>>> >> >> >> Xen) >>>> >>> >> >>>> >> >> >> (XEN) Freed 164kB init memory. >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 >>>> >>> >> >>>> >> >> >> pirq=0 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=2, irq=0 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=000009f0 >>>> >>> >> >>>> >> >> >> pirq=0 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 3 already >>>> >>> >> >>>> >> >> >> mapped >>>> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 4 already >>>> >>> >> >>>> >> >> >> mapped >>>> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 5 already >>>> >>> >> >>>> >> >> >> mapped >>>> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 6 already >>>> >>> >> >>>> >> >> >> mapped >>>> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 7 already >>>> >>> >> >>>> >> >> >> mapped >>>> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 8 already >>>> >>> >> >>>> >> >> >> mapped >>>> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 9 already >>>> >>> >> >>>> >> >> >> mapped >>>> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 10 already >>>> >>> >> >>>> >> >> >> mapped >>>> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 11 already >>>> >>> >> >>>> >> >> >> mapped >>>> >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 12 already >>>> >>> >> >>>> >> >> >> mapped >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000009f0 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 >>>> >>> >> >>>> >> >> >> pirq=0 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 >>>> >>> >> >>>> >> >> >> pirq=18 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 >>>> >>> >> >>>> >> >> >> pirq=19 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=23, irq=23 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a929 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a929 >>>> >>> >> >>>> >> >> >> pirq=23 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 >>>> >>> >> >>>> >> >> >> pirq=19 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 >>>> >>> >> >>>> >> >> >> pirq=18 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 >>>> >>> >> >>>> >> >> >> pirq=16 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 >>>> >>> >> >>>> >> >> >> pirq=16 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 >>>> >>> >> >>>> >> >> >> pirq=19 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 >>>> >>> >> >>>> >> >> >> pirq=18 >>>> >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >>> >> >>>> >> >> > >>>> >>> >> >>>> >> >> >> _______________________________________________ >>>> >>> >> >>>> >> >> >> Xen-users mailing list >>>> >>> >> >>>> >> >> >> Xen-users@lists.xensource.com >>>> >>> >> >>>> >> >> >> http://lists.xensource.com/xen-users >>>> >>> >> >>>> >> >> > >>>> >>> >> >>>> >> > >>>> >>> >> >>>> > >>>> >>> >> >>> >>>> >>> >> >> >>>> >>> >> > >>>> >>> > >>>> >> >>>> > >>> >> > ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: Re: [Xen-users] RE: Xen4 / Intel DX58SO Mobo / VT-d not working 2010-05-17 17:05 ` chris @ 2010-05-18 9:31 ` Weidong Han 2010-05-21 19:41 ` chris 0 siblings, 1 reply; 32+ messages in thread From: Weidong Han @ 2010-05-18 9:31 UTC (permalink / raw) To: chris; +Cc: Xen-Devel List, Xen-Users List chris wrote: > Can you explain to me what it is you want me to try? I'm not a > developer and I don't really understand what you are asking... > I mean you can add some printk to intel_iommu_assign_device function, then we can know where it fails in the function. this needs you to rebuild xen. Regards, Weidong > - chris > > On Sun, May 16, 2010 at 9:00 AM, chris <tknchris@gmail.com> wrote: > >> I'm not sure I understand what you want me to do, but that does look >> interesting and I didn't notice it before. >> >> - chris >> >> On Sun, May 16, 2010 at 3:36 AM, Han, Weidong <weidong.han@intel.com> wrote: >> >>> I noticed this line " (XEN) domctl.c:853:d0 XEN_DOMCTL_assign_device: assign device (2:0.0) failed" in NOTWORKING.txt. could you add some logs to intel_iommu_assign_device to know where it fails? I prefer you to use a clean Xen 4.0 environment. >>> >>> Regards, >>> Weidong >>> >>> -----Original Message----- >>> From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of chris >>> Sent: Saturday, May 15, 2010 5:18 AM >>> To: Pasi Kärkkäinen >>> Cc: Xen-Devel List; Xen-Users List >>> Subject: [Xen-devel] Re: [Xen-users] RE: Xen4 / Intel DX58SO Mobo / VT-d not working >>> >>> Played around with xen_platform_pc, pci_msitranslate, pci_power_mgmt in the cfg, none of which seem to have any effect, also tried >>> pci=resource_alignment=02:00.0;02:00.1;02:00.2 on dom0 cmdline, no effect. >>> >>> I'm worn out been fighting this all day. Attached is some various output from the machine that works with the same cards and has Xen >>> 3.4.2 and the new machine with 4.0 which doesn't work. I'm hoping this information can get the right attention and we can figure it out :( >>> >>> - chris >>> >>> >>> On Fri, May 14, 2010 at 4:50 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>> >>>> On Fri, May 14, 2010 at 04:39:54PM -0400, chris wrote: >>>> >>>>> Alright so a pci sound card works, I tried a geforce 8600 pci e card >>>>> and while vga passthrough didnt work it did seem to attach to the >>>>> domain ok. So I guess the problem must be somehow related to the >>>>> device. I'm still confused since it works in another box. >>>>> >>>>> I remember there was some reassign_resources or something, maybe the >>>>> issue is with some resources the card uses? >>>>> >>>>> >>>> http://wiki.xensource.com/xenwiki/XenPCIpassthrough >>>> >>>> -- Pasi >>>> >>>> >>>>> Below is a lspci -vv of the card >>>>> >>>>> 02:00.0 USB Controller: NEC Corporation USB (rev 43) (prog-if 10 >>>>> [OHCI]) >>>>> Subsystem: NEC Corporation Hama USB 2.0 CardBus >>>>> Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- >>>>> ParErr- Stepping- SERR- FastB2B- DisINTx- >>>>> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >>>>> >>>>>> TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- >>>>>> >>>>> Interrupt: pin A routed to IRQ 16 >>>>> Region 0: Memory at d2502000 (32-bit, non-prefetchable) >>>>> [disabled] [size=4K] >>>>> Capabilities: [40] Power Management version 2 >>>>> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA >>>>> PME(D0+,D1+,D2+,D3hot+,D3cold-) >>>>> Status: D0 PME-Enable- DSel=0 DScale=0 PME- >>>>> Kernel driver in use: pciback >>>>> >>>>> 02:00.1 USB Controller: NEC Corporation USB (rev 43) (prog-if 10 >>>>> [OHCI]) >>>>> Subsystem: NEC Corporation Hama USB 2.0 CardBus >>>>> Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- >>>>> ParErr- Stepping- SERR- FastB2B- DisINTx- >>>>> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >>>>> >>>>>> TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- >>>>>> >>>>> Interrupt: pin B routed to IRQ 17 >>>>> Region 0: Memory at d2501000 (32-bit, non-prefetchable) >>>>> [disabled] [size=4K] >>>>> Capabilities: [40] Power Management version 2 >>>>> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA >>>>> PME(D0+,D1+,D2+,D3hot+,D3cold-) >>>>> Status: D0 PME-Enable- DSel=0 DScale=0 PME- >>>>> Kernel driver in use: pciback >>>>> >>>>> 02:00.2 USB Controller: NEC Corporation USB 2.0 (rev 04) (prog-if 20 >>>>> [EHCI]) >>>>> Subsystem: NEC Corporation USB 2.0 >>>>> Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- >>>>> ParErr- Stepping- SERR- FastB2B- DisINTx- >>>>> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >>>>> >>>>>> TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- >>>>>> >>>>> Interrupt: pin C routed to IRQ 18 >>>>> Region 0: Memory at d2500000 (32-bit, non-prefetchable) >>>>> [disabled] [size=256] >>>>> Capabilities: [40] Power Management version 2 >>>>> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA >>>>> PME(D0+,D1+,D2+,D3hot+,D3cold-) >>>>> Status: D0 PME-Enable- DSel=0 DScale=0 PME- >>>>> Kernel driver in use: pciback >>>>> >>>>> >>>>> On Fri, May 14, 2010 at 3:46 PM, chris <tknchris@gmail.com> wrote: >>>>> >>>>>> I added a pci sound card and interestingly that works. I'm digging >>>>>> around for another pci-e device to try to identify if its all pci-e >>>>>> or only this device. Strange this is that I have a few other >>>>>> machines with this same usb controller which is working on 3.4.2. >>>>>> >>>>>> *scratches head* >>>>>> >>>>>> - chris >>>>>> >>>>>> On Fri, May 14, 2010 at 3:21 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>>>>> >>>>>>> On Fri, May 14, 2010 at 03:18:02PM -0400, chris wrote: >>>>>>> >>>>>>>> It is a multifunction device, a pci-e usb controller, so I >>>>>>>> assumed all them had to be passed through. I just changed it to >>>>>>>> only 02:00.0 and same thing >>>>>>>> >>>>>>>> test-box2:~# cat /etc/xen/vm-five.cfg | grep pci pci = >>>>>>>> ['02:00.0'] test-box2:~# xm create /etc/xen/vm-five.cfg Using >>>>>>>> config file "/etc/xen/vm-five.cfg". >>>>>>>> Error: Failed to assign device to IOMMU >>>>>>>> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>>>>>>> >>>>>>>> >>>>>>> Hmm.. weird. >>>>>>> >>>>>>> Two things to try: >>>>>>> >>>>>>> 1) Try passthru some other device (which is just a single pci id) >>>>>>> 2) Try passthru that pci-e usb controller to Linux PV guest and >>>>>>> see if that works >>>>>>> >>>>>>> -- Pasi >>>>>>> >>>>>>> >>>>>>>> On Fri, May 14, 2010 at 3:11 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>>>>>>> >>>>>>>>> On Fri, May 14, 2010 at 03:05:49PM -0400, chris wrote: >>>>>>>>> >>>>>>>>>> Pasi, >>>>>>>>>> >>>>>>>>>> Tried latest stable/2.6.32.x per your advice, no change. >>>>>>>>>> Anyone on xen-devel that can help me troubleshoot further? >>>>>>>>>> Everything looks right, can't figure out why vt-d is not >>>>>>>>>> working but it must be some kind of bug :( >>>>>>>>>> >>>>>>>>>> >>>>>>>>> Did you try the suggestion said earlier.. try to just passthru the first pci device? >>>>>>>>> >>>>>>>>> -- Pasi >>>>>>>>> >>>>>>>>> >>>>>>>>>> test-box2:~# uname -a >>>>>>>>>> Linux test-box2 2.6.32.12 #1 SMP Fri May 14 13:40:05 EDT 2010 >>>>>>>>>> x86_64 GNU/Linux >>>>>>>>>> >>>>>>>>>> test-box2:~# xm info | grep virt_caps virt_caps : >>>>>>>>>> hvm hvm_directio >>>>>>>>>> >>>>>>>>>> test-box2:~# xm pci-list-assignable-devices 0000:02:00.0 >>>>>>>>>> 0000:02:00.1 >>>>>>>>>> 0000:02:00.2 >>>>>>>>>> >>>>>>>>>> test-box2:~# xm create /etc/xen/vm-five.cfg Using config file >>>>>>>>>> "/etc/xen/vm-five.cfg". >>>>>>>>>> Error: Failed to assign device to IOMMU >>>>>>>>>> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>>>>>>>>> >>>>>>>>>> test-box2:~# cat /etc/xen/vm-five.cfg | grep -v '#' >>>>>>>>>> kernel = '/usr/lib/xen/boot/hvmloader' >>>>>>>>>> builder = 'hvm' >>>>>>>>>> memory = '1792' >>>>>>>>>> device_model='/usr/lib/xen/bin/qemu-dm' >>>>>>>>>> disk = [ 'phy:/dev/storage/vm-five,ioemu:hda,w', >>>>>>>>>> 'phy:/dev/sr0,ioemu:hdc:cdrom,r' >>>>>>>>>> ] >>>>>>>>>> name = 'vm-five' >>>>>>>>>> vif = ['type=ioemu, bridge=eth0, mac=00:16:3D:37:A1:42'] >>>>>>>>>> boot='dc' >>>>>>>>>> cpus='0-1' >>>>>>>>>> vcpus=2 >>>>>>>>>> acpi=1 >>>>>>>>>> ahci=1 >>>>>>>>>> vnc=1 >>>>>>>>>> sdl=0 >>>>>>>>>> timer_mode=1 >>>>>>>>>> usb=1 >>>>>>>>>> usbdevice='tablet' >>>>>>>>>> localtime=1 >>>>>>>>>> pci = ['02:00.0','02:00.1','02:00.2'] >>>>>>>>>> >>>>>>>>>> On Thu, May 13, 2010 at 2:28 PM, chris <tknchris@gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Forwarding to xen-devel. Can't seem to get VT-d working with >>>>>>>>>>> xen4 from tarball on xen.org 2.6.31.13 pv_ops dom0. On >>>>>>>>>>> pasi's advice I tried switching to stable/2.6.32.x branch >>>>>>>>>>> for dom0 and that doesnt even build. Did something change recently thats breaking compilation? >>>>>>>>>>> >>>>>>>>>>> Attached is xen dmesg with iommu=verbose loglvl=all >>>>>>>>>>> guest_loglvl=all, and dom0 dmesg from 2.6.31.x >>>>>>>>>>> >>>>>>>>>>> > > >>>>>>>>>>> Any ideas on why VT-d is not working on this board? >>>>>>>>>>> Initialization looks good, xen reports hvm_directio >>>>>>>>>>> capability, everything says VT-d should work until domain is created. >>>>>>>>>>> >>>>>>>>>>> Any ideas why stable/2.6.32.x wont build? >>>>>>>>>>> >>>>>>>>>>> - chris >>>>>>>>>>> >>>>>>>>>>> On Thu, May 13, 2010 at 2:07 PM, chris <tknchris@gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> I redid it with oldconfig which I didn't think would help >>>>>>>>>>>> and same thing. I guess this tree is broken? Can someone >>>>>>>>>>>> else try and see if they can build it? Ugh, whata day :) >>>>>>>>>>>> >>>>>>>>>>>> On Thu, May 13, 2010 at 1:58 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> On Thu, May 13, 2010 at 01:55:25PM -0400, chris wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> I used the default config on the wiki which you created. Steps I took were: >>>>>>>>>>>>>> >>>>>>>>>>>>>> # make clean distclean >>>>>>>>>>>>>> # wget -O .config >>>>>>>>>>>>>> "http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.10-pvops-dom0-xen-stable-x86_64" >>>>>>>>>>>>>> >>>>>>>>>>>>> You should do "make oldconfig" at this point. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>>> # make -j8 bzImage >>>>>>>>>>>>>> (blah blah) >>>>>>>>>>>>>> LD vmlinux.o >>>>>>>>>>>>>> MODPOST vmlinux.o >>>>>>>>>>>>>> WARNING: modpost: Found 7 section mismatch(es). >>>>>>>>>>>>>> To see full details build your kernel with: >>>>>>>>>>>>>> 'make CONFIG_DEBUG_SECTION_MISMATCH=y' >>>>>>>>>>>>>> GEN .version >>>>>>>>>>>>>> CHK include/linux/compile.h >>>>>>>>>>>>>> UPD include/linux/compile.h >>>>>>>>>>>>>> CC init/version.o >>>>>>>>>>>>>> LD init/built-in.o >>>>>>>>>>>>>> LD .tmp_vmlinux1 >>>>>>>>>>>>>> drivers/built-in.o: In function `do_hvm_suspend': >>>>>>>>>>>>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: >>>>>>>>>>>>>> undefined reference to `xenbus_suspend' >>>>>>>>>>>>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: >>>>>>>>>>>>>> undefined reference to `xenbus_resume' >>>>>>>>>>>>>> make: *** [.tmp_vmlinux1] Error 1 >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> Hmm.. weird. I wonder if something has changed recently or what's going on in here.. >>>>>>>>>>>>> >>>>>>>>>>>>> -- Pasi >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>>> On Thu, May 13, 2010 at 11:47 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Thu, May 13, 2010 at 11:33:57AM -0400, chris wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Successfully grabbed the sources and failed to build: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> LD .tmp_vmlinux1 >>>>>>>>>>>>>>>> drivers/built-in.o: In function `do_hvm_suspend': >>>>>>>>>>>>>>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: >>>>>>>>>>>>>>>> undefined reference to `xenbus_suspend' >>>>>>>>>>>>>>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: >>>>>>>>>>>>>>>> undefined reference to `xenbus_resume' >>>>>>>>>>>>>>>> make: *** [.tmp_vmlinux1] Error 1 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> :( >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Try the example .config files provided on the wiki page. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- Pasi >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Thu, May 13, 2010 at 10:14 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Thu, May 13, 2010 at 10:12:56AM -0400, chris wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Pasi, >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> How do I pull those kernel sources you referenced? >>>>>>>>>>>>>>>>>> I see it mentioned on >>>>>>>>>>>>>>>>>> http://wiki.xensource.com/xenwiki/XenParavirtOps but no details on how to retrieve it. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> The instructions are there if you read it carefully.. >>>>>>>>>>>>>>>>> There's the topic of how to switch branches. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> -- Pasi >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> - chris >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Thu, May 13, 2010 at 8:29 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> On Wed, May 12, 2010 at 08:41:34PM -0400, chris wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> When reading the vtdhowto I noticed the ability to set iommu=verbose. >>>>>>>>>>>>>>>>>>>> Here is that output, I don't know if it helps at >>>>>>>>>>>>>>>>>>>> all to figure out what is wrong. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> That seems to be OK: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> (XEN) I/O virtualisation enabled >>>>>>>>>>>>>>>>>>> (XEN) I/O virtualisation for PV guests disabled >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> So hmm.. I wonder if it's related to MSI stuff? >>>>>>>>>>>>>>>>>>> You could try xen.git xen/stable-2.6.32.x branch instead and see if that makes a difference.. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> -- Pasi >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> ---------- Forwarded message ---------- >>>>>>>>>>>>>>>>>>>> From: chris <tknchris@gmail.com> >>>>>>>>>>>>>>>>>>>> Date: Wed, May 12, 2010 at 5:28 PM >>>>>>>>>>>>>>>>>>>> Subject: Xen4 / Intel DX58SO Mobo / VT-d not >>>>>>>>>>>>>>>>>>>> working >>>>>>>>>>>>>>>>>>>> To: Xen-Users List >>>>>>>>>>>>>>>>>>>> <xen-users@lists.xensource.com> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Hello, >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> I've previously been successful with Xen4 and >>>>>>>>>>>>>>>>>>>> VT-d on other systems. I am having trouble >>>>>>>>>>>>>>>>>>>> getting VT-d passthrough working to a WinXP >>>>>>>>>>>>>>>>>>>> domain with DX58SO (Q45) motherboard and i7 930 >>>>>>>>>>>>>>>>>>>> CPU. VT-d is enabled in bios, xm info shows >>>>>>>>>>>>>>>>>>>> hvm_directio capability, I have iommu=1 set, I >>>>>>>>>>>>>>>>>>>> have the devices bound to pciback on dom0 cmdline, xm pci-list-assignable-devices shows the devices as assignable. When I attempt to start the VM I get the error: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Error: Failed to assign device to IOMMU >>>>>>>>>>>>>>>>>>>> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Below is all the information I can think of that >>>>>>>>>>>>>>>>>>>> would be useful to help debug it: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> BIOS VT-d Enabled: >>>>>>>>>>>>>>>>>>>> http://i43.tinypic.com/nl3a5e.jpg >>>>>>>>>>>>>>>>>>>> http://i42.tinypic.com/nqvlu1.jpg >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> grub entry: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> title Xen 4.0.0 / Debian GNU/Linux, >>>>>>>>>>>>>>>>>>>> kernel 2.6.31.13 root (hd0,0) kernel >>>>>>>>>>>>>>>>>>>> /boot/xen-4.0.0.gz iommu=1 dom0_mem=256M >>>>>>>>>>>>>>>>>>>> dom0_max_vcpus=1 dom0_vcpus_pin=true module >>>>>>>>>>>>>>>>>>>> /boot/vmlinuz-2.6.31.13 root=/dev/md0 ro >>>>>>>>>>>>>>>>>>>> console=tty0 xen-pciback.permissive >>>>>>>>>>>>>>>>>>>> xen-pciback.hide=(02:00.0)(02:00.1)(02:00.2)(04: >>>>>>>>>>>>>>>>>>>> 00.0)(04:00.1)(04:00.2)(07:00.0)(07:00.1)(07:00. >>>>>>>>>>>>>>>>>>>> 2)(09:00.0)(09:00.1)(09:00.2) module >>>>>>>>>>>>>>>>>>>> /boot/initrd.img-2.6.31.13 >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> # xm pci-list-assignable-devices 0000:09:00.0 >>>>>>>>>>>>>>>>>>>> 0000:09:00.1 >>>>>>>>>>>>>>>>>>>> 0000:09:00.2 >>>>>>>>>>>>>>>>>>>> 0000:07:00.0 >>>>>>>>>>>>>>>>>>>> 0000:07:00.1 >>>>>>>>>>>>>>>>>>>> 0000:07:00.2 >>>>>>>>>>>>>>>>>>>> 0000:04:00.0 >>>>>>>>>>>>>>>>>>>> 0000:04:00.1 >>>>>>>>>>>>>>>>>>>> 0000:04:00.2 >>>>>>>>>>>>>>>>>>>> 0000:02:00.0 >>>>>>>>>>>>>>>>>>>> 0000:02:00.1 >>>>>>>>>>>>>>>>>>>> 0000:02:00.2 >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> # xm info >>>>>>>>>>>>>>>>>>>> host : test-box2 release >>>>>>>>>>>>>>>>>>>> : 2.6.31.13 version : #2 SMP Wed >>>>>>>>>>>>>>>>>>>> May 12 14:11:37 EDT 2010 machine >>>>>>>>>>>>>>>>>>>> : x86_64 nr_cpus : 8 nr_nodes >>>>>>>>>>>>>>>>>>>> : 1 cores_per_socket : 4 threads_per_core >>>>>>>>>>>>>>>>>>>> : 2 cpu_mhz : 2800 hw_caps >>>>>>>>>>>>>>>>>>>> : >>>>>>>>>>>>>>>>>>>> bfebfbff:28100800:00000000:00001b40:0098e3bd:000 >>>>>>>>>>>>>>>>>>>> 00000:00000001:00000000 virt_caps : >>>>>>>>>>>>>>>>>>>> hvm hvm_directio total_memory : 7950 >>>>>>>>>>>>>>>>>>>> free_memory : 7812 node_to_cpu >>>>>>>>>>>>>>>>>>>> : node0:0-7 node_to_memory : node0:7812 >>>>>>>>>>>>>>>>>>>> node_to_dma32_mem : node0:3249 max_node_id >>>>>>>>>>>>>>>>>>>> : 0 xen_major : 4 xen_minor >>>>>>>>>>>>>>>>>>>> : 0 xen_extra : .0 xen_caps >>>>>>>>>>>>>>>>>>>> : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 >>>>>>>>>>>>>>>>>>>> hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler >>>>>>>>>>>>>>>>>>>> : credit xen_pagesize : 4096 >>>>>>>>>>>>>>>>>>>> platform_params : >>>>>>>>>>>>>>>>>>>> virt_start=0xffff800000000000 xen_changeset >>>>>>>>>>>>>>>>>>>> : unavailable xen_commandline : iommu=1 >>>>>>>>>>>>>>>>>>>> dom0_mem=256M dom0_max_vcpus=1 >>>>>>>>>>>>>>>>>>>> dom0_vcpus_pin=true cc_compiler : gcc >>>>>>>>>>>>>>>>>>>> version 4.3.2 (Debian 4.3.2-1.1) cc_compile_by >>>>>>>>>>>>>>>>>>>> : root cc_compile_domain : >>>>>>>>>>>>>>>>>>>> cc_compile_date : Thu May 6 13:41:25 EDT >>>>>>>>>>>>>>>>>>>> 2010 xend_config_format : 4 >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> # xm create vm-five.cfg Using config file >>>>>>>>>>>>>>>>>>>> "./vm-five.cfg". >>>>>>>>>>>>>>>>>>>> Error: Failed to assign device to IOMMU >>>>>>>>>>>>>>>>>>>> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> I feel like I'm missing something really obvious >>>>>>>>>>>>>>>>>>>> but I've been at it for a while now and have run >>>>>>>>>>>>>>>>>>>> out of brain power. Anyone have any idea what might be wrong? >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> - chris >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> __ __ _ _ ___ ___ >>>>>>>>>>>>>>>>>>>> \ \/ /___ _ __ | || | / _ \ / _ \ >>>>>>>>>>>>>>>>>>>> \ // _ \ \047_ \ | || |_| | | | | | | >>>>>>>>>>>>>>>>>>>> / \ __/ | | | |__ _| |_| | |_| | >>>>>>>>>>>>>>>>>>>> /_/\_\___|_| |_| |_|(_)___(_)___/ >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> (XEN) Xen version 4.0.0 (root@) (gcc version >>>>>>>>>>>>>>>>>>>> 4.3.2 (Debian 4.3.2-1.1) ) Thu May 6 13:41:25 >>>>>>>>>>>>>>>>>>>> EDT 2010 >>>>>>>>>>>>>>>>>>>> (XEN) Latest ChangeSet: unavailable >>>>>>>>>>>>>>>>>>>> (XEN) Command line: iommu=verbose dom0_mem=256M >>>>>>>>>>>>>>>>>>>> dom0_max_vcpus=1 dom0_vcpus_pin=true >>>>>>>>>>>>>>>>>>>> (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 - 000000000008f000 >>>>>>>>>>>>>>>>>>>> (usable) >>>>>>>>>>>>>>>>>>>> (XEN) 000000000008f000 - 0000000000090000 >>>>>>>>>>>>>>>>>>>> (reserved) >>>>>>>>>>>>>>>>>>>> (XEN) 0000000000090000 - 000000000009ec00 >>>>>>>>>>>>>>>>>>>> (usable) >>>>>>>>>>>>>>>>>>>> (XEN) 000000000009ec00 - 00000000000a0000 >>>>>>>>>>>>>>>>>>>> (reserved) >>>>>>>>>>>>>>>>>>>> (XEN) 00000000000e0000 - 0000000000100000 >>>>>>>>>>>>>>>>>>>> (reserved) >>>>>>>>>>>>>>>>>>>> (XEN) 0000000000100000 - 00000000cf4bd000 >>>>>>>>>>>>>>>>>>>> (usable) >>>>>>>>>>>>>>>>>>>> (XEN) 00000000cf4bd000 - 00000000cf4bf000 >>>>>>>>>>>>>>>>>>>> (reserved) >>>>>>>>>>>>>>>>>>>> (XEN) 00000000cf4bf000 - 00000000cf4c2000 >>>>>>>>>>>>>>>>>>>> (usable) >>>>>>>>>>>>>>>>>>>> (XEN) 00000000cf4c2000 - 00000000cf7bf000 (ACPI >>>>>>>>>>>>>>>>>>>> NVS) >>>>>>>>>>>>>>>>>>>> (XEN) 00000000cf7bf000 - 00000000cf7df000 >>>>>>>>>>>>>>>>>>>> (usable) >>>>>>>>>>>>>>>>>>>> (XEN) 00000000cf7df000 - 00000000cf7ff000 (ACPI >>>>>>>>>>>>>>>>>>>> data) >>>>>>>>>>>>>>>>>>>> (XEN) 00000000cf7ff000 - 00000000cf800000 >>>>>>>>>>>>>>>>>>>> (usable) >>>>>>>>>>>>>>>>>>>> (XEN) 00000000cf800000 - 00000000d0000000 >>>>>>>>>>>>>>>>>>>> (reserved) >>>>>>>>>>>>>>>>>>>> (XEN) 00000000f8000000 - 00000000fd000000 >>>>>>>>>>>>>>>>>>>> (reserved) >>>>>>>>>>>>>>>>>>>> (XEN) 00000000ffe00000 - 0000000100000000 >>>>>>>>>>>>>>>>>>>> (reserved) >>>>>>>>>>>>>>>>>>>> (XEN) 0000000100000000 - 0000000230000000 >>>>>>>>>>>>>>>>>>>> (usable) >>>>>>>>>>>>>>>>>>>> (XEN) ACPI: RSDP 000FE020, 0024 (r2 INTEL ) >>>>>>>>>>>>>>>>>>>> (XEN) ACPI: XSDT CF7FE120, 0074 (r1 INTEL >>>>>>>>>>>>>>>>>>>> DX58SO 11F6 1000013) >>>>>>>>>>>>>>>>>>>> (XEN) ACPI: FACP CF7FD000, 00F4 (r3 INTEL >>>>>>>>>>>>>>>>>>>> DX58SO 11F6 MSFT 100000D) >>>>>>>>>>>>>>>>>>>> (XEN) ACPI Warning (tbfadt-0444): Optional field >>>>>>>>>>>>>>>>>>>> "Pm2ControlBlock" has zero address or length: >>>>>>>>>>>>>>>>>>>> 0000000000000450/0 [20070126] >>>>>>>>>>>>>>>>>>>> (XEN) ACPI: DSDT CF7F8000, 4641 (r2 INTEL >>>>>>>>>>>>>>>>>>>> DX58SO 11F6 MSFT 100000D) >>>>>>>>>>>>>>>>>>>> (XEN) ACPI: FACS CF728000, 0040 >>>>>>>>>>>>>>>>>>>> (XEN) ACPI: APIC CF7F7000, 0138 (r2 INTEL >>>>>>>>>>>>>>>>>>>> DX58SO 11F6 MSFT 100000D) >>>>>>>>>>>>>>>>>>>> (XEN) ACPI: WDDT CF7F6000, 0040 (r1 INTEL >>>>>>>>>>>>>>>>>>>> DX58SO 11F6 MSFT 100000D) >>>>>>>>>>>>>>>>>>>> (XEN) ACPI: MCFG CF7F5000, 003C (r1 INTEL >>>>>>>>>>>>>>>>>>>> DX58SO 11F6 MSFT 100000D) >>>>>>>>>>>>>>>>>>>> (XEN) ACPI: ASF! CF7F4000, 00AC (r32 INTEL >>>>>>>>>>>>>>>>>>>> DX58SO 11F6 MSFT 100000D) >>>>>>>>>>>>>>>>>>>> (XEN) ACPI: HPET CF7F3000, 0038 (r1 INTEL >>>>>>>>>>>>>>>>>>>> DX58SO 11F6 MSFT 100000D) >>>>>>>>>>>>>>>>>>>> (XEN) ACPI: SSDT CF7E2000, E134 (r1 INTEL SSDT >>>>>>>>>>>>>>>>>>>> PM 11F6 MSFT 100000D) >>>>>>>>>>>>>>>>>>>> (XEN) ACPI: DMAR CF7DF000, 0140 (r1 INTEL >>>>>>>>>>>>>>>>>>>> DX58SO 11F6 MSFT 100000D) >>>>>>>>>>>>>>>>>>>> (XEN) ACPI: WDTT CF7F1000, 020C (r2 INTEL >>>>>>>>>>>>>>>>>>>> DX58SO 11F6 MSFT 100000D) >>>>>>>>>>>>>>>>>>>> (XEN) ACPI: ASPT CF7F2000, 0034 (r4 INTEL >>>>>>>>>>>>>>>>>>>> PerfTune 11F6 MSFT 100000D) >>>>>>>>>>>>>>>>>>>> (XEN) System RAM: 7950MB (8140820kB) >>>>>>>>>>>>>>>>>>>> (XEN) Domain heap initialised >>>>>>>>>>>>>>>>>>>> (XEN) Processor #0 7:10 APIC version 21 >>>>>>>>>>>>>>>>>>>> (XEN) Processor #2 7:10 APIC version 21 >>>>>>>>>>>>>>>>>>>> (XEN) Processor #4 7:10 APIC version 21 >>>>>>>>>>>>>>>>>>>> (XEN) Processor #6 7:10 APIC version 21 >>>>>>>>>>>>>>>>>>>> (XEN) Processor #1 7:10 APIC version 21 >>>>>>>>>>>>>>>>>>>> (XEN) Processor #3 7:10 APIC version 21 >>>>>>>>>>>>>>>>>>>> (XEN) Processor #5 7:10 APIC version 21 >>>>>>>>>>>>>>>>>>>> (XEN) Processor #7 7:10 APIC version 21 >>>>>>>>>>>>>>>>>>>> (XEN) IOAPIC[0]: apic_id 8, version 32, address >>>>>>>>>>>>>>>>>>>> 0xfec00000, GSI 0-23 >>>>>>>>>>>>>>>>>>>> (XEN) Enabling APIC mode: Flat. Using 1 I/O >>>>>>>>>>>>>>>>>>>> APICs >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:679: Host address width 39 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:398: dmaru->address = >>>>>>>>>>>>>>>>>>>> fe711000 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:334: endpoint: 0:1b.0 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:398: dmaru->address = >>>>>>>>>>>>>>>>>>>> fe710000 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:340: IOAPIC: f0:1f.7 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:411: flags: INCLUDE_ALL >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >>>>>>>>>>>>>>>>>>>> e9000 end_address e9fff >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.1 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >>>>>>>>>>>>>>>>>>>> ea000 end_address eafff >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.2 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >>>>>>>>>>>>>>>>>>>> eb000 end_address ebfff >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.0 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >>>>>>>>>>>>>>>>>>>> e6000 end_address e6fff >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.1 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >>>>>>>>>>>>>>>>>>>> e7000 end_address e7fff >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.2 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >>>>>>>>>>>>>>>>>>>> e8000 end_address e8fff >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >>>>>>>>>>>>>>>>>>>> ec000 end_address eefff >>>>>>>>>>>>>>>>>>>> (XEN) Using scheduler: SMP Credit Scheduler >>>>>>>>>>>>>>>>>>>> (credit) >>>>>>>>>>>>>>>>>>>> (XEN) Detected 2800.125 MHz processor. >>>>>>>>>>>>>>>>>>>> (XEN) Initing memory sharing. >>>>>>>>>>>>>>>>>>>> (XEN) VMX: Supported advanced features: >>>>>>>>>>>>>>>>>>>> (XEN) - APIC MMIO access virtualisation >>>>>>>>>>>>>>>>>>>> (XEN) - APIC TPR shadow >>>>>>>>>>>>>>>>>>>> (XEN) - Extended Page Tables (EPT) >>>>>>>>>>>>>>>>>>>> (XEN) - Virtual-Processor Identifiers (VPID) >>>>>>>>>>>>>>>>>>>> (XEN) - Virtual NMI >>>>>>>>>>>>>>>>>>>> (XEN) - MSR direct-access bitmap >>>>>>>>>>>>>>>>>>>> (XEN) HVM: ASIDs enabled. >>>>>>>>>>>>>>>>>>>> (XEN) HVM: VMX enabled >>>>>>>>>>>>>>>>>>>> (XEN) HVM: Hardware Assisted Paging detected. >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1078: drhd->address = >>>>>>>>>>>>>>>>>>>> fe711000 iommu->reg = ffff82c3fff57000 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1080: cap = c9008010e60262 >>>>>>>>>>>>>>>>>>>> ecap = f0207a >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1078: drhd->address = >>>>>>>>>>>>>>>>>>>> fe710000 iommu->reg = ffff82c3fff56000 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1080: cap = c90780106f0462 >>>>>>>>>>>>>>>>>>>> ecap = f020fa >>>>>>>>>>>>>>>>>>>> (XEN) Intel VT-d Snoop Control not supported. >>>>>>>>>>>>>>>>>>>> (XEN) Intel VT-d DMA Passthrough not supported. >>>>>>>>>>>>>>>>>>>> (XEN) Intel VT-d Queued Invalidation supported. >>>>>>>>>>>>>>>>>>>> (XEN) Intel VT-d Interrupt Remapping supported. >>>>>>>>>>>>>>>>>>>> (XEN) I/O virtualisation enabled >>>>>>>>>>>>>>>>>>>> (XEN) I/O virtualisation for PV guests disabled >>>>>>>>>>>>>>>>>>>> (XEN) Total of 8 processors activated. >>>>>>>>>>>>>>>>>>>> (XEN) ENABLING IO-APIC IRQs >>>>>>>>>>>>>>>>>>>> (XEN) -> Using new ACK method >>>>>>>>>>>>>>>>>>>> (XEN) TSC is reliable, synchronization >>>>>>>>>>>>>>>>>>>> unnecessary >>>>>>>>>>>>>>>>>>>> (XEN) Platform timer is 14.318MHz HPET >>>>>>>>>>>>>>>>>>>> (XEN) Allocated console ring of 16 KiB. >>>>>>>>>>>>>>>>>>>> (XEN) Brought up 8 CPUs >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 0:0.0 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 0:10.0 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 0:10.1 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >>>>>>>>>>>>>>>>>>>> 0:14.0 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >>>>>>>>>>>>>>>>>>>> 0:14.1 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >>>>>>>>>>>>>>>>>>>> 0:14.2 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 0:14.3 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 0:19.0 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 0:1a.0 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 0:1a.1 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 0:1a.2 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 0:1a.7 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >>>>>>>>>>>>>>>>>>>> 0:1b.0 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 0:1d.0 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 0:1d.1 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 0:1d.2 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 0:1d.7 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 0:1f.0 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 0:1f.2 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 0:1f.3 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 0:1f.5 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 2:0.0 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 2:0.1 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 2:0.2 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 4:0.0 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 4:0.1 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 4:0.2 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >>>>>>>>>>>>>>>>>>>> 5:0.0 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 7:0.0 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 7:0.1 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 7:0.2 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 9:0.0 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 9:0.1 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 9:0.2 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >>>>>>>>>>>>>>>>>>>> a:0.0 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> b:3.0 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> b:3.1 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> b:3.2 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> b:3.3 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> b:3.4 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> b:3.5 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> b:3.6 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> b:3.7 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 3f:0.0 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 3f:0.1 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 3f:2.0 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 3f:2.1 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 3f:3.0 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 3f:3.1 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 3f:3.4 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 3f:4.0 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 3f:4.1 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 3f:4.2 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 3f:4.3 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 3f:5.0 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 3f:5.1 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 3f:5.2 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 3f:5.3 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 3f:6.0 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 3f:6.1 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 3f:6.2 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>> 3f:6.3 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:695: >>>>>>>>>>>>>>>>>>>> iommu_enable_translation: iommu->reg = >>>>>>>>>>>>>>>>>>>> ffff82c3fff57000 >>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:695: >>>>>>>>>>>>>>>>>>>> iommu_enable_translation: iommu->reg = >>>>>>>>>>>>>>>>>>>> ffff82c3fff56000 >>>>>>>>>>>>>>>>>>>> (XEN) *** LOADING DOMAIN 0 *** >>>>>>>>>>>>>>>>>>>> (XEN) Xen kernel: 64-bit, lsb, compat32 >>>>>>>>>>>>>>>>>>>> (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr >>>>>>>>>>>>>>>>>>>> 0x1000000 -> 0x26ae000 >>>>>>>>>>>>>>>>>>>> (XEN) PHYSICAL MEMORY ARRANGEMENT: >>>>>>>>>>>>>>>>>>>> (XEN) Dom0 alloc.: >>>>>>>>>>>>>>>>>>>> 0000000210000000->0000000220000000 >>>>>>>>>>>>>>>>>>>> (XEN) VIRTUAL MEMORY ARRANGEMENT: >>>>>>>>>>>>>>>>>>>> (XEN) Loaded kernel: >>>>>>>>>>>>>>>>>>>> ffffffff81000000->ffffffff826ae000 >>>>>>>>>>>>>>>>>>>> (XEN) Init. ramdisk: >>>>>>>>>>>>>>>>>>>> ffffffff826ae000->ffffffff8f4de600 >>>>>>>>>>>>>>>>>>>> (XEN) Phys-Mach map: >>>>>>>>>>>>>>>>>>>> ffffffff8f4df000->ffffffff8f55f000 >>>>>>>>>>>>>>>>>>>> (XEN) Start info: >>>>>>>>>>>>>>>>>>>> ffffffff8f55f000->ffffffff8f55f4b4 >>>>>>>>>>>>>>>>>>>> (XEN) Page tables: >>>>>>>>>>>>>>>>>>>> ffffffff8f560000->ffffffff8f5df000 >>>>>>>>>>>>>>>>>>>> (XEN) Boot stack: >>>>>>>>>>>>>>>>>>>> ffffffff8f5df000->ffffffff8f5e0000 >>>>>>>>>>>>>>>>>>>> (XEN) TOTAL: >>>>>>>>>>>>>>>>>>>> ffffffff80000000->ffffffff8f800000 >>>>>>>>>>>>>>>>>>>> (XEN) ENTRY ADDRESS: ffffffff81a10860 >>>>>>>>>>>>>>>>>>>> (XEN) Dom0 has maximum 1 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 >>>>>>>>>>>>>>>>>>>> \047CTRL-a\047 three times to switch input to >>>>>>>>>>>>>>>>>>>> Xen) >>>>>>>>>>>>>>>>>>>> (XEN) Freed 164kB init memory. >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=000109f0 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=00010000 >>>>>>>>>>>>>>>>>>>> pirq=0 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=2, irq=0 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=000109f0 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=000009f0 >>>>>>>>>>>>>>>>>>>> pirq=0 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>>>>>>>>>>>>>>>>>> (XEN) irq.c:1445: dom0: pirq 0 or irq 3 already >>>>>>>>>>>>>>>>>>>> mapped >>>>>>>>>>>>>>>>>>>> (XEN) irq.c:1445: dom0: pirq 0 or irq 4 already >>>>>>>>>>>>>>>>>>>> mapped >>>>>>>>>>>>>>>>>>>> (XEN) irq.c:1445: dom0: pirq 0 or irq 5 already >>>>>>>>>>>>>>>>>>>> mapped >>>>>>>>>>>>>>>>>>>> (XEN) irq.c:1445: dom0: pirq 0 or irq 6 already >>>>>>>>>>>>>>>>>>>> mapped >>>>>>>>>>>>>>>>>>>> (XEN) irq.c:1445: dom0: pirq 0 or irq 7 already >>>>>>>>>>>>>>>>>>>> mapped >>>>>>>>>>>>>>>>>>>> (XEN) irq.c:1445: dom0: pirq 0 or irq 8 already >>>>>>>>>>>>>>>>>>>> mapped >>>>>>>>>>>>>>>>>>>> (XEN) irq.c:1445: dom0: pirq 0 or irq 9 already >>>>>>>>>>>>>>>>>>>> mapped >>>>>>>>>>>>>>>>>>>> (XEN) irq.c:1445: dom0: pirq 0 or irq 10 already >>>>>>>>>>>>>>>>>>>> mapped >>>>>>>>>>>>>>>>>>>> (XEN) irq.c:1445: dom0: pirq 0 or irq 11 already >>>>>>>>>>>>>>>>>>>> mapped >>>>>>>>>>>>>>>>>>>> (XEN) irq.c:1445: dom0: pirq 0 or irq 12 already >>>>>>>>>>>>>>>>>>>> mapped >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=000009f0 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=00010000 >>>>>>>>>>>>>>>>>>>> pirq=0 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=0001a9c0 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=0000a9c0 >>>>>>>>>>>>>>>>>>>> pirq=18 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=0001a9c8 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=0000a9c8 >>>>>>>>>>>>>>>>>>>> pirq=19 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=23, irq=23 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=0001a929 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=0000a929 >>>>>>>>>>>>>>>>>>>> pirq=23 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=0001a9c8 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=0000a9c8 >>>>>>>>>>>>>>>>>>>> pirq=19 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=0001a9c0 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=0000a9c0 >>>>>>>>>>>>>>>>>>>> pirq=18 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=0001a9b0 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=0000a9b0 >>>>>>>>>>>>>>>>>>>> pirq=16 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=0001a9b0 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=0000a9b0 >>>>>>>>>>>>>>>>>>>> pirq=16 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=0001a9c8 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=0000a9c8 >>>>>>>>>>>>>>>>>>>> pirq=19 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=0001a9c0 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=0000a9c0 >>>>>>>>>>>>>>>>>>>> pirq=18 >>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>>> Xen-users mailing list >>>>>>>>>>>>>>>>>>>> Xen-users@lists.xensource.com >>>>>>>>>>>>>>>>>>>> http://lists.xensource.com/xen-users >>>>>>>>>>>>>>>>>>>> ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: Re: [Xen-users] RE: Xen4 / Intel DX58SO Mobo / VT-d not working 2010-05-18 9:31 ` Re: [Xen-users] " Weidong Han @ 2010-05-21 19:41 ` chris 2010-05-24 2:54 ` [Xen-devel] " Weidong Han 0 siblings, 1 reply; 32+ messages in thread From: chris @ 2010-05-21 19:41 UTC (permalink / raw) To: Weidong Han; +Cc: Xen-Devel List, Xen-Users List I had some more time to play with this. I copied my sources from the production server to this machine and I have VT-d working with these USB controllers so something since 3.4.3 must have broken something :( Identical hardware and passthrough of USB controller via VT-d. dom0 is 2.6.31.6. Would it be worth anything to post details which are working on this system compare against the not working Xen4 / 2.6.32.x dom0 ? - chris On Tue, May 18, 2010 at 5:31 AM, Weidong Han <weidong.han@intel.com> wrote: > chris wrote: >> >> Can you explain to me what it is you want me to try? I'm not a >> developer and I don't really understand what you are asking... >> > > I mean you can add some printk to intel_iommu_assign_device function, then > we can know where it fails in the function. this needs you to rebuild xen. > > Regards, > Weidong >> >> - chris >> >> On Sun, May 16, 2010 at 9:00 AM, chris <tknchris@gmail.com> wrote: >> >>> >>> I'm not sure I understand what you want me to do, but that does look >>> interesting and I didn't notice it before. >>> >>> - chris >>> >>> On Sun, May 16, 2010 at 3:36 AM, Han, Weidong <weidong.han@intel.com> >>> wrote: >>> >>>> >>>> I noticed this line " (XEN) domctl.c:853:d0 XEN_DOMCTL_assign_device: >>>> assign device (2:0.0) failed" in NOTWORKING.txt. could you add some logs to >>>> intel_iommu_assign_device to know where it fails? I prefer you to use a >>>> clean Xen 4.0 environment. >>>> >>>> Regards, >>>> Weidong >>>> >>>> -----Original Message----- >>>> From: xen-devel-bounces@lists.xensource.com >>>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of chris >>>> Sent: Saturday, May 15, 2010 5:18 AM >>>> To: Pasi Kärkkäinen >>>> Cc: Xen-Devel List; Xen-Users List >>>> Subject: [Xen-devel] Re: [Xen-users] RE: Xen4 / Intel DX58SO Mobo / VT-d >>>> not working >>>> >>>> Played around with xen_platform_pc, pci_msitranslate, pci_power_mgmt in >>>> the cfg, none of which seem to have any effect, also tried >>>> pci=resource_alignment=02:00.0;02:00.1;02:00.2 on dom0 cmdline, no >>>> effect. >>>> >>>> I'm worn out been fighting this all day. Attached is some various output >>>> from the machine that works with the same cards and has Xen >>>> 3.4.2 and the new machine with 4.0 which doesn't work. I'm hoping this >>>> information can get the right attention and we can figure it out :( >>>> >>>> - chris >>>> >>>> >>>> On Fri, May 14, 2010 at 4:50 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>>> >>>>> >>>>> On Fri, May 14, 2010 at 04:39:54PM -0400, chris wrote: >>>>> >>>>>> >>>>>> Alright so a pci sound card works, I tried a geforce 8600 pci e card >>>>>> and while vga passthrough didnt work it did seem to attach to the >>>>>> domain ok. So I guess the problem must be somehow related to the >>>>>> device. I'm still confused since it works in another box. >>>>>> >>>>>> I remember there was some reassign_resources or something, maybe the >>>>>> issue is with some resources the card uses? >>>>>> >>>>>> >>>>> >>>>> http://wiki.xensource.com/xenwiki/XenPCIpassthrough >>>>> >>>>> -- Pasi >>>>> >>>>> >>>>>> >>>>>> Below is a lspci -vv of the card >>>>>> >>>>>> 02:00.0 USB Controller: NEC Corporation USB (rev 43) (prog-if 10 >>>>>> [OHCI]) >>>>>> Subsystem: NEC Corporation Hama USB 2.0 CardBus >>>>>> Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- >>>>>> ParErr- Stepping- SERR- FastB2B- DisINTx- >>>>>> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >>>>>> >>>>>>> >>>>>>> TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- >>>>>>> >>>>>> >>>>>> Interrupt: pin A routed to IRQ 16 >>>>>> Region 0: Memory at d2502000 (32-bit, non-prefetchable) >>>>>> [disabled] [size=4K] >>>>>> Capabilities: [40] Power Management version 2 >>>>>> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA >>>>>> PME(D0+,D1+,D2+,D3hot+,D3cold-) >>>>>> Status: D0 PME-Enable- DSel=0 DScale=0 PME- >>>>>> Kernel driver in use: pciback >>>>>> >>>>>> 02:00.1 USB Controller: NEC Corporation USB (rev 43) (prog-if 10 >>>>>> [OHCI]) >>>>>> Subsystem: NEC Corporation Hama USB 2.0 CardBus >>>>>> Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- >>>>>> ParErr- Stepping- SERR- FastB2B- DisINTx- >>>>>> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >>>>>> >>>>>>> >>>>>>> TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- >>>>>>> >>>>>> >>>>>> Interrupt: pin B routed to IRQ 17 >>>>>> Region 0: Memory at d2501000 (32-bit, non-prefetchable) >>>>>> [disabled] [size=4K] >>>>>> Capabilities: [40] Power Management version 2 >>>>>> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA >>>>>> PME(D0+,D1+,D2+,D3hot+,D3cold-) >>>>>> Status: D0 PME-Enable- DSel=0 DScale=0 PME- >>>>>> Kernel driver in use: pciback >>>>>> >>>>>> 02:00.2 USB Controller: NEC Corporation USB 2.0 (rev 04) (prog-if 20 >>>>>> [EHCI]) >>>>>> Subsystem: NEC Corporation USB 2.0 >>>>>> Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- >>>>>> ParErr- Stepping- SERR- FastB2B- DisINTx- >>>>>> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >>>>>> >>>>>>> >>>>>>> TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- >>>>>>> >>>>>> >>>>>> Interrupt: pin C routed to IRQ 18 >>>>>> Region 0: Memory at d2500000 (32-bit, non-prefetchable) >>>>>> [disabled] [size=256] >>>>>> Capabilities: [40] Power Management version 2 >>>>>> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA >>>>>> PME(D0+,D1+,D2+,D3hot+,D3cold-) >>>>>> Status: D0 PME-Enable- DSel=0 DScale=0 PME- >>>>>> Kernel driver in use: pciback >>>>>> >>>>>> >>>>>> On Fri, May 14, 2010 at 3:46 PM, chris <tknchris@gmail.com> wrote: >>>>>> >>>>>>> >>>>>>> I added a pci sound card and interestingly that works. I'm digging >>>>>>> around for another pci-e device to try to identify if its all pci-e >>>>>>> or only this device. Strange this is that I have a few other >>>>>>> machines with this same usb controller which is working on 3.4.2. >>>>>>> >>>>>>> *scratches head* >>>>>>> >>>>>>> - chris >>>>>>> >>>>>>> On Fri, May 14, 2010 at 3:21 PM, Pasi Kärkkäinen <pasik@iki.fi> >>>>>>> wrote: >>>>>>> >>>>>>>> >>>>>>>> On Fri, May 14, 2010 at 03:18:02PM -0400, chris wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> It is a multifunction device, a pci-e usb controller, so I >>>>>>>>> assumed all them had to be passed through. I just changed it to >>>>>>>>> only 02:00.0 and same thing >>>>>>>>> >>>>>>>>> test-box2:~# cat /etc/xen/vm-five.cfg | grep pci pci = >>>>>>>>> ['02:00.0'] test-box2:~# xm create /etc/xen/vm-five.cfg Using >>>>>>>>> config file "/etc/xen/vm-five.cfg". >>>>>>>>> Error: Failed to assign device to IOMMU >>>>>>>>> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> Hmm.. weird. >>>>>>>> >>>>>>>> Two things to try: >>>>>>>> >>>>>>>> 1) Try passthru some other device (which is just a single pci id) >>>>>>>> 2) Try passthru that pci-e usb controller to Linux PV guest and >>>>>>>> see if that works >>>>>>>> >>>>>>>> -- Pasi >>>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>> On Fri, May 14, 2010 at 3:11 PM, Pasi Kärkkäinen <pasik@iki.fi> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Fri, May 14, 2010 at 03:05:49PM -0400, chris wrote: >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Pasi, >>>>>>>>>>> >>>>>>>>>>> Tried latest stable/2.6.32.x per your advice, no change. >>>>>>>>>>> Anyone on xen-devel that can help me troubleshoot further? >>>>>>>>>>> Everything looks right, can't figure out why vt-d is not >>>>>>>>>>> working but it must be some kind of bug :( >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Did you try the suggestion said earlier.. try to just passthru the >>>>>>>>>> first pci device? >>>>>>>>>> >>>>>>>>>> -- Pasi >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> test-box2:~# uname -a >>>>>>>>>>> Linux test-box2 2.6.32.12 #1 SMP Fri May 14 13:40:05 EDT 2010 >>>>>>>>>>> x86_64 GNU/Linux >>>>>>>>>>> >>>>>>>>>>> test-box2:~# xm info | grep virt_caps virt_caps : >>>>>>>>>>> hvm hvm_directio >>>>>>>>>>> >>>>>>>>>>> test-box2:~# xm pci-list-assignable-devices 0000:02:00.0 >>>>>>>>>>> 0000:02:00.1 >>>>>>>>>>> 0000:02:00.2 >>>>>>>>>>> >>>>>>>>>>> test-box2:~# xm create /etc/xen/vm-five.cfg Using config file >>>>>>>>>>> "/etc/xen/vm-five.cfg". >>>>>>>>>>> Error: Failed to assign device to IOMMU >>>>>>>>>>> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>>>>>>>>>> >>>>>>>>>>> test-box2:~# cat /etc/xen/vm-five.cfg | grep -v '#' >>>>>>>>>>> kernel = '/usr/lib/xen/boot/hvmloader' >>>>>>>>>>> builder = 'hvm' >>>>>>>>>>> memory = '1792' >>>>>>>>>>> device_model='/usr/lib/xen/bin/qemu-dm' >>>>>>>>>>> disk = [ 'phy:/dev/storage/vm-five,ioemu:hda,w', >>>>>>>>>>> 'phy:/dev/sr0,ioemu:hdc:cdrom,r' >>>>>>>>>>> ] >>>>>>>>>>> name = 'vm-five' >>>>>>>>>>> vif = ['type=ioemu, bridge=eth0, mac=00:16:3D:37:A1:42'] >>>>>>>>>>> boot='dc' >>>>>>>>>>> cpus='0-1' >>>>>>>>>>> vcpus=2 >>>>>>>>>>> acpi=1 >>>>>>>>>>> ahci=1 >>>>>>>>>>> vnc=1 >>>>>>>>>>> sdl=0 >>>>>>>>>>> timer_mode=1 >>>>>>>>>>> usb=1 >>>>>>>>>>> usbdevice='tablet' >>>>>>>>>>> localtime=1 >>>>>>>>>>> pci = ['02:00.0','02:00.1','02:00.2'] >>>>>>>>>>> >>>>>>>>>>> On Thu, May 13, 2010 at 2:28 PM, chris <tknchris@gmail.com> >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Forwarding to xen-devel. Can't seem to get VT-d working with >>>>>>>>>>>> xen4 from tarball on xen.org 2.6.31.13 pv_ops dom0. On >>>>>>>>>>>> pasi's advice I tried switching to stable/2.6.32.x branch >>>>>>>>>>>> for dom0 and that doesnt even build. Did something change >>>>>>>>>>>> recently thats breaking compilation? >>>>>>>>>>>> >>>>>>>>>>>> Attached is xen dmesg with iommu=verbose loglvl=all >>>>>>>>>>>> guest_loglvl=all, and dom0 dmesg from 2.6.31.x >>>>>>>>>>>> >>>>>>>>>>>> >> >> >>>>>>>>>>>> >>>>>>>>>>>> Any ideas on why VT-d is not working on this board? >>>>>>>>>>>> Initialization looks good, xen reports hvm_directio >>>>>>>>>>>> capability, everything says VT-d should work until domain is >>>>>>>>>>>> created. >>>>>>>>>>>> >>>>>>>>>>>> Any ideas why stable/2.6.32.x wont build? >>>>>>>>>>>> >>>>>>>>>>>> - chris >>>>>>>>>>>> >>>>>>>>>>>> On Thu, May 13, 2010 at 2:07 PM, chris <tknchris@gmail.com> >>>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> I redid it with oldconfig which I didn't think would help >>>>>>>>>>>>> and same thing. I guess this tree is broken? Can someone >>>>>>>>>>>>> else try and see if they can build it? Ugh, whata day :) >>>>>>>>>>>>> >>>>>>>>>>>>> On Thu, May 13, 2010 at 1:58 PM, Pasi Kärkkäinen <pasik@iki.fi> >>>>>>>>>>>>> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Thu, May 13, 2010 at 01:55:25PM -0400, chris wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> I used the default config on the wiki which you created. >>>>>>>>>>>>>>> Steps I took were: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> # make clean distclean >>>>>>>>>>>>>>> # wget -O .config >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> "http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.10-pvops-dom0-xen-stable-x86_64" >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> You should do "make oldconfig" at this point. >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> # make -j8 bzImage >>>>>>>>>>>>>>> (blah blah) >>>>>>>>>>>>>>> LD vmlinux.o >>>>>>>>>>>>>>> MODPOST vmlinux.o >>>>>>>>>>>>>>> WARNING: modpost: Found 7 section mismatch(es). >>>>>>>>>>>>>>> To see full details build your kernel with: >>>>>>>>>>>>>>> 'make CONFIG_DEBUG_SECTION_MISMATCH=y' >>>>>>>>>>>>>>> GEN .version >>>>>>>>>>>>>>> CHK include/linux/compile.h >>>>>>>>>>>>>>> UPD include/linux/compile.h >>>>>>>>>>>>>>> CC init/version.o >>>>>>>>>>>>>>> LD init/built-in.o >>>>>>>>>>>>>>> LD .tmp_vmlinux1 >>>>>>>>>>>>>>> drivers/built-in.o: In function `do_hvm_suspend': >>>>>>>>>>>>>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: >>>>>>>>>>>>>>> undefined reference to `xenbus_suspend' >>>>>>>>>>>>>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: >>>>>>>>>>>>>>> undefined reference to `xenbus_resume' >>>>>>>>>>>>>>> make: *** [.tmp_vmlinux1] Error 1 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Hmm.. weird. I wonder if something has changed recently or >>>>>>>>>>>>>> what's going on in here.. >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- Pasi >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Thu, May 13, 2010 at 11:47 AM, Pasi Kärkkäinen >>>>>>>>>>>>>>> <pasik@iki.fi> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Thu, May 13, 2010 at 11:33:57AM -0400, chris wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Successfully grabbed the sources and failed to build: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> LD .tmp_vmlinux1 >>>>>>>>>>>>>>>>> drivers/built-in.o: In function `do_hvm_suspend': >>>>>>>>>>>>>>>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: >>>>>>>>>>>>>>>>> undefined reference to `xenbus_suspend' >>>>>>>>>>>>>>>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: >>>>>>>>>>>>>>>>> undefined reference to `xenbus_resume' >>>>>>>>>>>>>>>>> make: *** [.tmp_vmlinux1] Error 1 >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> :( >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Try the example .config files provided on the wiki page. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -- Pasi >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Thu, May 13, 2010 at 10:14 AM, Pasi Kärkkäinen >>>>>>>>>>>>>>>>> <pasik@iki.fi> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Thu, May 13, 2010 at 10:12:56AM -0400, chris wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Pasi, >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> How do I pull those kernel sources you referenced? >>>>>>>>>>>>>>>>>>> I see it mentioned on >>>>>>>>>>>>>>>>>>> http://wiki.xensource.com/xenwiki/XenParavirtOps but no >>>>>>>>>>>>>>>>>>> details on how to retrieve it. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> The instructions are there if you read it carefully.. >>>>>>>>>>>>>>>>>> There's the topic of how to switch branches. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> -- Pasi >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> - chris >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> On Thu, May 13, 2010 at 8:29 AM, Pasi Kärkkäinen >>>>>>>>>>>>>>>>>>> <pasik@iki.fi> wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> On Wed, May 12, 2010 at 08:41:34PM -0400, chris wrote: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> When reading the vtdhowto I noticed the ability to set >>>>>>>>>>>>>>>>>>>>> iommu=verbose. >>>>>>>>>>>>>>>>>>>>> Here is that output, I don't know if it helps at >>>>>>>>>>>>>>>>>>>>> all to figure out what is wrong. >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> That seems to be OK: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> (XEN) I/O virtualisation enabled >>>>>>>>>>>>>>>>>>>> (XEN) I/O virtualisation for PV guests disabled >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> So hmm.. I wonder if it's related to MSI stuff? >>>>>>>>>>>>>>>>>>>> You could try xen.git xen/stable-2.6.32.x branch instead >>>>>>>>>>>>>>>>>>>> and see if that makes a difference.. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> -- Pasi >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> ---------- Forwarded message ---------- >>>>>>>>>>>>>>>>>>>>> From: chris <tknchris@gmail.com> >>>>>>>>>>>>>>>>>>>>> Date: Wed, May 12, 2010 at 5:28 PM >>>>>>>>>>>>>>>>>>>>> Subject: Xen4 / Intel DX58SO Mobo / VT-d not >>>>>>>>>>>>>>>>>>>>> working >>>>>>>>>>>>>>>>>>>>> To: Xen-Users List >>>>>>>>>>>>>>>>>>>>> <xen-users@lists.xensource.com> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Hello, >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> I've previously been successful with Xen4 and >>>>>>>>>>>>>>>>>>>>> VT-d on other systems. I am having trouble >>>>>>>>>>>>>>>>>>>>> getting VT-d passthrough working to a WinXP >>>>>>>>>>>>>>>>>>>>> domain with DX58SO (Q45) motherboard and i7 930 >>>>>>>>>>>>>>>>>>>>> CPU. VT-d is enabled in bios, xm info shows >>>>>>>>>>>>>>>>>>>>> hvm_directio capability, I have iommu=1 set, I >>>>>>>>>>>>>>>>>>>>> have the devices bound to pciback on dom0 cmdline, xm >>>>>>>>>>>>>>>>>>>>> pci-list-assignable-devices shows the devices as assignable. When I attempt >>>>>>>>>>>>>>>>>>>>> to start the VM I get the error: >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Error: Failed to assign device to IOMMU >>>>>>>>>>>>>>>>>>>>> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Below is all the information I can think of that >>>>>>>>>>>>>>>>>>>>> would be useful to help debug it: >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> BIOS VT-d Enabled: >>>>>>>>>>>>>>>>>>>>> http://i43.tinypic.com/nl3a5e.jpg >>>>>>>>>>>>>>>>>>>>> http://i42.tinypic.com/nqvlu1.jpg >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> grub entry: >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> title Xen 4.0.0 / Debian GNU/Linux, >>>>>>>>>>>>>>>>>>>>> kernel 2.6.31.13 root (hd0,0) kernel >>>>>>>>>>>>>>>>>>>>> /boot/xen-4.0.0.gz iommu=1 dom0_mem=256M >>>>>>>>>>>>>>>>>>>>> dom0_max_vcpus=1 dom0_vcpus_pin=true module >>>>>>>>>>>>>>>>>>>>> /boot/vmlinuz-2.6.31.13 root=/dev/md0 ro >>>>>>>>>>>>>>>>>>>>> console=tty0 xen-pciback.permissive >>>>>>>>>>>>>>>>>>>>> xen-pciback.hide=(02:00.0)(02:00.1)(02:00.2)(04: >>>>>>>>>>>>>>>>>>>>> 00.0)(04:00.1)(04:00.2)(07:00.0)(07:00.1)(07:00. >>>>>>>>>>>>>>>>>>>>> 2)(09:00.0)(09:00.1)(09:00.2) module >>>>>>>>>>>>>>>>>>>>> /boot/initrd.img-2.6.31.13 >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> # xm pci-list-assignable-devices 0000:09:00.0 >>>>>>>>>>>>>>>>>>>>> 0000:09:00.1 >>>>>>>>>>>>>>>>>>>>> 0000:09:00.2 >>>>>>>>>>>>>>>>>>>>> 0000:07:00.0 >>>>>>>>>>>>>>>>>>>>> 0000:07:00.1 >>>>>>>>>>>>>>>>>>>>> 0000:07:00.2 >>>>>>>>>>>>>>>>>>>>> 0000:04:00.0 >>>>>>>>>>>>>>>>>>>>> 0000:04:00.1 >>>>>>>>>>>>>>>>>>>>> 0000:04:00.2 >>>>>>>>>>>>>>>>>>>>> 0000:02:00.0 >>>>>>>>>>>>>>>>>>>>> 0000:02:00.1 >>>>>>>>>>>>>>>>>>>>> 0000:02:00.2 >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> # xm info >>>>>>>>>>>>>>>>>>>>> host : test-box2 release >>>>>>>>>>>>>>>>>>>>> : 2.6.31.13 version : #2 SMP Wed >>>>>>>>>>>>>>>>>>>>> May 12 14:11:37 EDT 2010 machine >>>>>>>>>>>>>>>>>>>>> : x86_64 nr_cpus : 8 nr_nodes >>>>>>>>>>>>>>>>>>>>> : 1 cores_per_socket : 4 threads_per_core >>>>>>>>>>>>>>>>>>>>> : 2 cpu_mhz : 2800 hw_caps >>>>>>>>>>>>>>>>>>>>> : >>>>>>>>>>>>>>>>>>>>> bfebfbff:28100800:00000000:00001b40:0098e3bd:000 >>>>>>>>>>>>>>>>>>>>> 00000:00000001:00000000 virt_caps : >>>>>>>>>>>>>>>>>>>>> hvm hvm_directio total_memory : 7950 >>>>>>>>>>>>>>>>>>>>> free_memory : 7812 node_to_cpu >>>>>>>>>>>>>>>>>>>>> : node0:0-7 node_to_memory : node0:7812 >>>>>>>>>>>>>>>>>>>>> node_to_dma32_mem : node0:3249 max_node_id >>>>>>>>>>>>>>>>>>>>> : 0 xen_major : 4 xen_minor >>>>>>>>>>>>>>>>>>>>> : 0 xen_extra : .0 xen_caps >>>>>>>>>>>>>>>>>>>>> : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 >>>>>>>>>>>>>>>>>>>>> hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler >>>>>>>>>>>>>>>>>>>>> : credit xen_pagesize : 4096 >>>>>>>>>>>>>>>>>>>>> platform_params : >>>>>>>>>>>>>>>>>>>>> virt_start=0xffff800000000000 xen_changeset >>>>>>>>>>>>>>>>>>>>> : unavailable xen_commandline : iommu=1 >>>>>>>>>>>>>>>>>>>>> dom0_mem=256M dom0_max_vcpus=1 >>>>>>>>>>>>>>>>>>>>> dom0_vcpus_pin=true cc_compiler : gcc >>>>>>>>>>>>>>>>>>>>> version 4.3.2 (Debian 4.3.2-1.1) cc_compile_by >>>>>>>>>>>>>>>>>>>>> : root cc_compile_domain : >>>>>>>>>>>>>>>>>>>>> cc_compile_date : Thu May 6 13:41:25 EDT >>>>>>>>>>>>>>>>>>>>> 2010 xend_config_format : 4 >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> # xm create vm-five.cfg Using config file >>>>>>>>>>>>>>>>>>>>> "./vm-five.cfg". >>>>>>>>>>>>>>>>>>>>> Error: Failed to assign device to IOMMU >>>>>>>>>>>>>>>>>>>>> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> I feel like I'm missing something really obvious >>>>>>>>>>>>>>>>>>>>> but I've been at it for a while now and have run >>>>>>>>>>>>>>>>>>>>> out of brain power. Anyone have any idea what might be >>>>>>>>>>>>>>>>>>>>> wrong? >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> - chris >>>>>>>>>>>>>>>>>>>>> __ __ >>>>>>>>>>>>>>>>>>>>> _ _ ___ ___ >>>>>>>>>>>>>>>>>>>>> \ \/ /___ _ __ | || | / _ \ / _ \ >>>>>>>>>>>>>>>>>>>>> \ // _ \ \047_ \ | || |_| | | | | | | >>>>>>>>>>>>>>>>>>>>> / \ __/ | | | |__ _| |_| | |_| | >>>>>>>>>>>>>>>>>>>>> /_/\_\___|_| |_| |_|(_)___(_)___/ >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> (XEN) Xen version 4.0.0 (root@) (gcc version >>>>>>>>>>>>>>>>>>>>> 4.3.2 (Debian 4.3.2-1.1) ) Thu May 6 13:41:25 >>>>>>>>>>>>>>>>>>>>> EDT 2010 >>>>>>>>>>>>>>>>>>>>> (XEN) Latest ChangeSet: unavailable >>>>>>>>>>>>>>>>>>>>> (XEN) Command line: iommu=verbose dom0_mem=256M >>>>>>>>>>>>>>>>>>>>> dom0_max_vcpus=1 dom0_vcpus_pin=true >>>>>>>>>>>>>>>>>>>>> (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 - 000000000008f000 >>>>>>>>>>>>>>>>>>>>> (usable) >>>>>>>>>>>>>>>>>>>>> (XEN) 000000000008f000 - 0000000000090000 >>>>>>>>>>>>>>>>>>>>> (reserved) >>>>>>>>>>>>>>>>>>>>> (XEN) 0000000000090000 - 000000000009ec00 >>>>>>>>>>>>>>>>>>>>> (usable) >>>>>>>>>>>>>>>>>>>>> (XEN) 000000000009ec00 - 00000000000a0000 >>>>>>>>>>>>>>>>>>>>> (reserved) >>>>>>>>>>>>>>>>>>>>> (XEN) 00000000000e0000 - 0000000000100000 >>>>>>>>>>>>>>>>>>>>> (reserved) >>>>>>>>>>>>>>>>>>>>> (XEN) 0000000000100000 - 00000000cf4bd000 >>>>>>>>>>>>>>>>>>>>> (usable) >>>>>>>>>>>>>>>>>>>>> (XEN) 00000000cf4bd000 - 00000000cf4bf000 >>>>>>>>>>>>>>>>>>>>> (reserved) >>>>>>>>>>>>>>>>>>>>> (XEN) 00000000cf4bf000 - 00000000cf4c2000 >>>>>>>>>>>>>>>>>>>>> (usable) >>>>>>>>>>>>>>>>>>>>> (XEN) 00000000cf4c2000 - 00000000cf7bf000 (ACPI >>>>>>>>>>>>>>>>>>>>> NVS) >>>>>>>>>>>>>>>>>>>>> (XEN) 00000000cf7bf000 - 00000000cf7df000 >>>>>>>>>>>>>>>>>>>>> (usable) >>>>>>>>>>>>>>>>>>>>> (XEN) 00000000cf7df000 - 00000000cf7ff000 (ACPI >>>>>>>>>>>>>>>>>>>>> data) >>>>>>>>>>>>>>>>>>>>> (XEN) 00000000cf7ff000 - 00000000cf800000 >>>>>>>>>>>>>>>>>>>>> (usable) >>>>>>>>>>>>>>>>>>>>> (XEN) 00000000cf800000 - 00000000d0000000 >>>>>>>>>>>>>>>>>>>>> (reserved) >>>>>>>>>>>>>>>>>>>>> (XEN) 00000000f8000000 - 00000000fd000000 >>>>>>>>>>>>>>>>>>>>> (reserved) >>>>>>>>>>>>>>>>>>>>> (XEN) 00000000ffe00000 - 0000000100000000 >>>>>>>>>>>>>>>>>>>>> (reserved) >>>>>>>>>>>>>>>>>>>>> (XEN) 0000000100000000 - 0000000230000000 >>>>>>>>>>>>>>>>>>>>> (usable) >>>>>>>>>>>>>>>>>>>>> (XEN) ACPI: RSDP 000FE020, 0024 (r2 INTEL ) >>>>>>>>>>>>>>>>>>>>> (XEN) ACPI: XSDT CF7FE120, 0074 (r1 INTEL >>>>>>>>>>>>>>>>>>>>> DX58SO 11F6 1000013) >>>>>>>>>>>>>>>>>>>>> (XEN) ACPI: FACP CF7FD000, 00F4 (r3 INTEL >>>>>>>>>>>>>>>>>>>>> DX58SO 11F6 MSFT 100000D) >>>>>>>>>>>>>>>>>>>>> (XEN) ACPI Warning (tbfadt-0444): Optional field >>>>>>>>>>>>>>>>>>>>> "Pm2ControlBlock" has zero address or length: >>>>>>>>>>>>>>>>>>>>> 0000000000000450/0 [20070126] >>>>>>>>>>>>>>>>>>>>> (XEN) ACPI: DSDT CF7F8000, 4641 (r2 INTEL >>>>>>>>>>>>>>>>>>>>> DX58SO 11F6 MSFT 100000D) >>>>>>>>>>>>>>>>>>>>> (XEN) ACPI: FACS CF728000, 0040 >>>>>>>>>>>>>>>>>>>>> (XEN) ACPI: APIC CF7F7000, 0138 (r2 INTEL >>>>>>>>>>>>>>>>>>>>> DX58SO 11F6 MSFT 100000D) >>>>>>>>>>>>>>>>>>>>> (XEN) ACPI: WDDT CF7F6000, 0040 (r1 INTEL >>>>>>>>>>>>>>>>>>>>> DX58SO 11F6 MSFT 100000D) >>>>>>>>>>>>>>>>>>>>> (XEN) ACPI: MCFG CF7F5000, 003C (r1 INTEL >>>>>>>>>>>>>>>>>>>>> DX58SO 11F6 MSFT 100000D) >>>>>>>>>>>>>>>>>>>>> (XEN) ACPI: ASF! CF7F4000, 00AC (r32 INTEL >>>>>>>>>>>>>>>>>>>>> DX58SO 11F6 MSFT 100000D) >>>>>>>>>>>>>>>>>>>>> (XEN) ACPI: HPET CF7F3000, 0038 (r1 INTEL >>>>>>>>>>>>>>>>>>>>> DX58SO 11F6 MSFT 100000D) >>>>>>>>>>>>>>>>>>>>> (XEN) ACPI: SSDT CF7E2000, E134 (r1 INTEL SSDT >>>>>>>>>>>>>>>>>>>>> PM 11F6 MSFT 100000D) >>>>>>>>>>>>>>>>>>>>> (XEN) ACPI: DMAR CF7DF000, 0140 (r1 INTEL >>>>>>>>>>>>>>>>>>>>> DX58SO 11F6 MSFT 100000D) >>>>>>>>>>>>>>>>>>>>> (XEN) ACPI: WDTT CF7F1000, 020C (r2 INTEL >>>>>>>>>>>>>>>>>>>>> DX58SO 11F6 MSFT 100000D) >>>>>>>>>>>>>>>>>>>>> (XEN) ACPI: ASPT CF7F2000, 0034 (r4 INTEL >>>>>>>>>>>>>>>>>>>>> PerfTune 11F6 MSFT 100000D) >>>>>>>>>>>>>>>>>>>>> (XEN) System RAM: 7950MB (8140820kB) >>>>>>>>>>>>>>>>>>>>> (XEN) Domain heap initialised >>>>>>>>>>>>>>>>>>>>> (XEN) Processor #0 7:10 APIC version 21 >>>>>>>>>>>>>>>>>>>>> (XEN) Processor #2 7:10 APIC version 21 >>>>>>>>>>>>>>>>>>>>> (XEN) Processor #4 7:10 APIC version 21 >>>>>>>>>>>>>>>>>>>>> (XEN) Processor #6 7:10 APIC version 21 >>>>>>>>>>>>>>>>>>>>> (XEN) Processor #1 7:10 APIC version 21 >>>>>>>>>>>>>>>>>>>>> (XEN) Processor #3 7:10 APIC version 21 >>>>>>>>>>>>>>>>>>>>> (XEN) Processor #5 7:10 APIC version 21 >>>>>>>>>>>>>>>>>>>>> (XEN) Processor #7 7:10 APIC version 21 >>>>>>>>>>>>>>>>>>>>> (XEN) IOAPIC[0]: apic_id 8, version 32, address >>>>>>>>>>>>>>>>>>>>> 0xfec00000, GSI 0-23 >>>>>>>>>>>>>>>>>>>>> (XEN) Enabling APIC mode: Flat. Using 1 I/O >>>>>>>>>>>>>>>>>>>>> APICs >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:679: Host address width 39 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:398: dmaru->address = >>>>>>>>>>>>>>>>>>>>> fe711000 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:334: endpoint: 0:1b.0 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:398: dmaru->address = >>>>>>>>>>>>>>>>>>>>> fe710000 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:340: IOAPIC: f0:1f.7 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:411: flags: INCLUDE_ALL >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >>>>>>>>>>>>>>>>>>>>> e9000 end_address e9fff >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.1 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >>>>>>>>>>>>>>>>>>>>> ea000 end_address eafff >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.2 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >>>>>>>>>>>>>>>>>>>>> eb000 end_address ebfff >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.0 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >>>>>>>>>>>>>>>>>>>>> e6000 end_address e6fff >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.1 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >>>>>>>>>>>>>>>>>>>>> e7000 end_address e7fff >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.2 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >>>>>>>>>>>>>>>>>>>>> e8000 end_address e8fff >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >>>>>>>>>>>>>>>>>>>>> ec000 end_address eefff >>>>>>>>>>>>>>>>>>>>> (XEN) Using scheduler: SMP Credit Scheduler >>>>>>>>>>>>>>>>>>>>> (credit) >>>>>>>>>>>>>>>>>>>>> (XEN) Detected 2800.125 MHz processor. >>>>>>>>>>>>>>>>>>>>> (XEN) Initing memory sharing. >>>>>>>>>>>>>>>>>>>>> (XEN) VMX: Supported advanced features: >>>>>>>>>>>>>>>>>>>>> (XEN) - APIC MMIO access virtualisation >>>>>>>>>>>>>>>>>>>>> (XEN) - APIC TPR shadow >>>>>>>>>>>>>>>>>>>>> (XEN) - Extended Page Tables (EPT) >>>>>>>>>>>>>>>>>>>>> (XEN) - Virtual-Processor Identifiers (VPID) >>>>>>>>>>>>>>>>>>>>> (XEN) - Virtual NMI >>>>>>>>>>>>>>>>>>>>> (XEN) - MSR direct-access bitmap >>>>>>>>>>>>>>>>>>>>> (XEN) HVM: ASIDs enabled. >>>>>>>>>>>>>>>>>>>>> (XEN) HVM: VMX enabled >>>>>>>>>>>>>>>>>>>>> (XEN) HVM: Hardware Assisted Paging detected. >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1078: drhd->address = >>>>>>>>>>>>>>>>>>>>> fe711000 iommu->reg = ffff82c3fff57000 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1080: cap = c9008010e60262 >>>>>>>>>>>>>>>>>>>>> ecap = f0207a >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1078: drhd->address = >>>>>>>>>>>>>>>>>>>>> fe710000 iommu->reg = ffff82c3fff56000 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1080: cap = c90780106f0462 >>>>>>>>>>>>>>>>>>>>> ecap = f020fa >>>>>>>>>>>>>>>>>>>>> (XEN) Intel VT-d Snoop Control not supported. >>>>>>>>>>>>>>>>>>>>> (XEN) Intel VT-d DMA Passthrough not supported. >>>>>>>>>>>>>>>>>>>>> (XEN) Intel VT-d Queued Invalidation supported. >>>>>>>>>>>>>>>>>>>>> (XEN) Intel VT-d Interrupt Remapping supported. >>>>>>>>>>>>>>>>>>>>> (XEN) I/O virtualisation enabled >>>>>>>>>>>>>>>>>>>>> (XEN) I/O virtualisation for PV guests disabled >>>>>>>>>>>>>>>>>>>>> (XEN) Total of 8 processors activated. >>>>>>>>>>>>>>>>>>>>> (XEN) ENABLING IO-APIC IRQs >>>>>>>>>>>>>>>>>>>>> (XEN) -> Using new ACK method >>>>>>>>>>>>>>>>>>>>> (XEN) TSC is reliable, synchronization >>>>>>>>>>>>>>>>>>>>> unnecessary >>>>>>>>>>>>>>>>>>>>> (XEN) Platform timer is 14.318MHz HPET >>>>>>>>>>>>>>>>>>>>> (XEN) Allocated console ring of 16 KiB. >>>>>>>>>>>>>>>>>>>>> (XEN) Brought up 8 CPUs >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 0:0.0 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 0:10.0 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 0:10.1 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >>>>>>>>>>>>>>>>>>>>> 0:14.0 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >>>>>>>>>>>>>>>>>>>>> 0:14.1 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >>>>>>>>>>>>>>>>>>>>> 0:14.2 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 0:14.3 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 0:19.0 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 0:1a.0 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 0:1a.1 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 0:1a.2 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 0:1a.7 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >>>>>>>>>>>>>>>>>>>>> 0:1b.0 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 0:1d.0 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 0:1d.1 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 0:1d.2 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 0:1d.7 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 0:1f.0 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 0:1f.2 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 0:1f.3 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 0:1f.5 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 2:0.0 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 2:0.1 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 2:0.2 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 4:0.0 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 4:0.1 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 4:0.2 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >>>>>>>>>>>>>>>>>>>>> 5:0.0 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 7:0.0 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 7:0.1 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 7:0.2 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 9:0.0 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 9:0.1 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 9:0.2 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >>>>>>>>>>>>>>>>>>>>> a:0.0 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> b:3.0 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> b:3.1 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> b:3.2 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> b:3.3 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> b:3.4 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> b:3.5 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> b:3.6 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> b:3.7 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 3f:0.0 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 3f:0.1 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 3f:2.0 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 3f:2.1 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 3f:3.0 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 3f:3.1 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 3f:3.4 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 3f:4.0 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 3f:4.1 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 3f:4.2 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 3f:4.3 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 3f:5.0 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 3f:5.1 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 3f:5.2 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 3f:5.3 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 3f:6.0 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 3f:6.1 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 3f:6.2 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>> 3f:6.3 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:695: >>>>>>>>>>>>>>>>>>>>> iommu_enable_translation: iommu->reg = >>>>>>>>>>>>>>>>>>>>> ffff82c3fff57000 >>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:695: >>>>>>>>>>>>>>>>>>>>> iommu_enable_translation: iommu->reg = >>>>>>>>>>>>>>>>>>>>> ffff82c3fff56000 >>>>>>>>>>>>>>>>>>>>> (XEN) *** LOADING DOMAIN 0 *** >>>>>>>>>>>>>>>>>>>>> (XEN) Xen kernel: 64-bit, lsb, compat32 >>>>>>>>>>>>>>>>>>>>> (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr >>>>>>>>>>>>>>>>>>>>> 0x1000000 -> 0x26ae000 >>>>>>>>>>>>>>>>>>>>> (XEN) PHYSICAL MEMORY ARRANGEMENT: >>>>>>>>>>>>>>>>>>>>> (XEN) Dom0 alloc.: >>>>>>>>>>>>>>>>>>>>> 0000000210000000->0000000220000000 >>>>>>>>>>>>>>>>>>>>> (XEN) VIRTUAL MEMORY ARRANGEMENT: >>>>>>>>>>>>>>>>>>>>> (XEN) Loaded kernel: >>>>>>>>>>>>>>>>>>>>> ffffffff81000000->ffffffff826ae000 >>>>>>>>>>>>>>>>>>>>> (XEN) Init. ramdisk: >>>>>>>>>>>>>>>>>>>>> ffffffff826ae000->ffffffff8f4de600 >>>>>>>>>>>>>>>>>>>>> (XEN) Phys-Mach map: >>>>>>>>>>>>>>>>>>>>> ffffffff8f4df000->ffffffff8f55f000 >>>>>>>>>>>>>>>>>>>>> (XEN) Start info: >>>>>>>>>>>>>>>>>>>>> ffffffff8f55f000->ffffffff8f55f4b4 >>>>>>>>>>>>>>>>>>>>> (XEN) Page tables: >>>>>>>>>>>>>>>>>>>>> ffffffff8f560000->ffffffff8f5df000 >>>>>>>>>>>>>>>>>>>>> (XEN) Boot stack: >>>>>>>>>>>>>>>>>>>>> ffffffff8f5df000->ffffffff8f5e0000 >>>>>>>>>>>>>>>>>>>>> (XEN) TOTAL: >>>>>>>>>>>>>>>>>>>>> ffffffff80000000->ffffffff8f800000 >>>>>>>>>>>>>>>>>>>>> (XEN) ENTRY ADDRESS: ffffffff81a10860 >>>>>>>>>>>>>>>>>>>>> (XEN) Dom0 has maximum 1 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 >>>>>>>>>>>>>>>>>>>>> \047CTRL-a\047 three times to switch input to >>>>>>>>>>>>>>>>>>>>> Xen) >>>>>>>>>>>>>>>>>>>>> (XEN) Freed 164kB init memory. >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=000109f0 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=00010000 >>>>>>>>>>>>>>>>>>>>> pirq=0 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin >>>>>>>>>>>>>>>>>>>>> for in-use IRQ! >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=2, irq=0 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=000109f0 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=000009f0 >>>>>>>>>>>>>>>>>>>>> pirq=0 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin >>>>>>>>>>>>>>>>>>>>> for in-use IRQ! >>>>>>>>>>>>>>>>>>>>> (XEN) irq.c:1445: dom0: pirq 0 or irq 3 already >>>>>>>>>>>>>>>>>>>>> mapped >>>>>>>>>>>>>>>>>>>>> (XEN) irq.c:1445: dom0: pirq 0 or irq 4 already >>>>>>>>>>>>>>>>>>>>> mapped >>>>>>>>>>>>>>>>>>>>> (XEN) irq.c:1445: dom0: pirq 0 or irq 5 already >>>>>>>>>>>>>>>>>>>>> mapped >>>>>>>>>>>>>>>>>>>>> (XEN) irq.c:1445: dom0: pirq 0 or irq 6 already >>>>>>>>>>>>>>>>>>>>> mapped >>>>>>>>>>>>>>>>>>>>> (XEN) irq.c:1445: dom0: pirq 0 or irq 7 already >>>>>>>>>>>>>>>>>>>>> mapped >>>>>>>>>>>>>>>>>>>>> (XEN) irq.c:1445: dom0: pirq 0 or irq 8 already >>>>>>>>>>>>>>>>>>>>> mapped >>>>>>>>>>>>>>>>>>>>> (XEN) irq.c:1445: dom0: pirq 0 or irq 9 already >>>>>>>>>>>>>>>>>>>>> mapped >>>>>>>>>>>>>>>>>>>>> (XEN) irq.c:1445: dom0: pirq 0 or irq 10 already >>>>>>>>>>>>>>>>>>>>> mapped >>>>>>>>>>>>>>>>>>>>> (XEN) irq.c:1445: dom0: pirq 0 or irq 11 already >>>>>>>>>>>>>>>>>>>>> mapped >>>>>>>>>>>>>>>>>>>>> (XEN) irq.c:1445: dom0: pirq 0 or irq 12 already >>>>>>>>>>>>>>>>>>>>> mapped >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=000009f0 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=00010000 >>>>>>>>>>>>>>>>>>>>> pirq=0 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin >>>>>>>>>>>>>>>>>>>>> for in-use IRQ! >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=0001a9c0 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=0000a9c0 >>>>>>>>>>>>>>>>>>>>> pirq=18 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin >>>>>>>>>>>>>>>>>>>>> for in-use IRQ! >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=0001a9c8 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=0000a9c8 >>>>>>>>>>>>>>>>>>>>> pirq=19 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin >>>>>>>>>>>>>>>>>>>>> for in-use IRQ! >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=23, irq=23 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=0001a929 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=0000a929 >>>>>>>>>>>>>>>>>>>>> pirq=23 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin >>>>>>>>>>>>>>>>>>>>> for in-use IRQ! >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=0001a9c8 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=0000a9c8 >>>>>>>>>>>>>>>>>>>>> pirq=19 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin >>>>>>>>>>>>>>>>>>>>> for in-use IRQ! >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=0001a9c0 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=0000a9c0 >>>>>>>>>>>>>>>>>>>>> pirq=18 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin >>>>>>>>>>>>>>>>>>>>> for in-use IRQ! >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=0001a9b0 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=0000a9b0 >>>>>>>>>>>>>>>>>>>>> pirq=16 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin >>>>>>>>>>>>>>>>>>>>> for in-use IRQ! >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=0001a9b0 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=0000a9b0 >>>>>>>>>>>>>>>>>>>>> pirq=16 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin >>>>>>>>>>>>>>>>>>>>> for in-use IRQ! >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=0001a9c8 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=0000a9c8 >>>>>>>>>>>>>>>>>>>>> pirq=19 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin >>>>>>>>>>>>>>>>>>>>> for in-use IRQ! >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=0001a9c0 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=0000a9c0 >>>>>>>>>>>>>>>>>>>>> pirq=18 >>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin >>>>>>>>>>>>>>>>>>>>> for in-use IRQ! >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>>>> Xen-users mailing list >>>>>>>>>>>>>>>>>>>>> Xen-users@lists.xensource.com >>>>>>>>>>>>>>>>>>>>> http://lists.xensource.com/xen-users >>>>>>>>>>>>>>>>>>>>> > > ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [Xen-devel] Re: RE: Xen4 / Intel DX58SO Mobo / VT-d not working 2010-05-21 19:41 ` chris @ 2010-05-24 2:54 ` Weidong Han 0 siblings, 0 replies; 32+ messages in thread From: Weidong Han @ 2010-05-24 2:54 UTC (permalink / raw) To: chris; +Cc: Xen-Devel List, Xen-Users List, Pasi Kärkkäinen chris wrote: > I had some more time to play with this. I copied my sources from the > production server to this machine and I have VT-d working with these > USB controllers so something since 3.4.3 must have broken something :( > Identical hardware and passthrough of USB controller via VT-d. dom0 is > 2.6.31.6. Would it be worth anything to post details which are working > on this system compare against the not working Xen4 / 2.6.32.x dom0 ? > it's helpful if you can provide serial output and qemu log in both two cases. Regards, Weidong > - chris > > On Tue, May 18, 2010 at 5:31 AM, Weidong Han <weidong.han@intel.com> wrote: > >> chris wrote: >> >>> Can you explain to me what it is you want me to try? I'm not a >>> developer and I don't really understand what you are asking... >>> >>> >> I mean you can add some printk to intel_iommu_assign_device function, then >> we can know where it fails in the function. this needs you to rebuild xen. >> >> Regards, >> Weidong >> >>> - chris >>> >>> On Sun, May 16, 2010 at 9:00 AM, chris <tknchris@gmail.com> wrote: >>> >>> >>>> I'm not sure I understand what you want me to do, but that does look >>>> interesting and I didn't notice it before. >>>> >>>> - chris >>>> >>>> On Sun, May 16, 2010 at 3:36 AM, Han, Weidong <weidong.han@intel.com> >>>> wrote: >>>> >>>> >>>>> I noticed this line " (XEN) domctl.c:853:d0 XEN_DOMCTL_assign_device: >>>>> assign device (2:0.0) failed" in NOTWORKING.txt. could you add some logs to >>>>> intel_iommu_assign_device to know where it fails? I prefer you to use a >>>>> clean Xen 4.0 environment. >>>>> >>>>> Regards, >>>>> Weidong >>>>> >>>>> -----Original Message----- >>>>> From: xen-devel-bounces@lists.xensource.com >>>>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of chris >>>>> Sent: Saturday, May 15, 2010 5:18 AM >>>>> To: Pasi Kärkkäinen >>>>> Cc: Xen-Devel List; Xen-Users List >>>>> Subject: [Xen-devel] Re: [Xen-users] RE: Xen4 / Intel DX58SO Mobo / VT-d >>>>> not working >>>>> >>>>> Played around with xen_platform_pc, pci_msitranslate, pci_power_mgmt in >>>>> the cfg, none of which seem to have any effect, also tried >>>>> pci=resource_alignment=02:00.0;02:00.1;02:00.2 on dom0 cmdline, no >>>>> effect. >>>>> >>>>> I'm worn out been fighting this all day. Attached is some various output >>>>> from the machine that works with the same cards and has Xen >>>>> 3.4.2 and the new machine with 4.0 which doesn't work. I'm hoping this >>>>> information can get the right attention and we can figure it out :( >>>>> >>>>> - chris >>>>> >>>>> >>>>> On Fri, May 14, 2010 at 4:50 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>>>> >>>>> >>>>>> On Fri, May 14, 2010 at 04:39:54PM -0400, chris wrote: >>>>>> >>>>>> >>>>>>> Alright so a pci sound card works, I tried a geforce 8600 pci e card >>>>>>> and while vga passthrough didnt work it did seem to attach to the >>>>>>> domain ok. So I guess the problem must be somehow related to the >>>>>>> device. I'm still confused since it works in another box. >>>>>>> >>>>>>> I remember there was some reassign_resources or something, maybe the >>>>>>> issue is with some resources the card uses? >>>>>>> >>>>>>> >>>>>>> >>>>>> http://wiki.xensource.com/xenwiki/XenPCIpassthrough >>>>>> >>>>>> -- Pasi >>>>>> >>>>>> >>>>>> >>>>>>> Below is a lspci -vv of the card >>>>>>> >>>>>>> 02:00.0 USB Controller: NEC Corporation USB (rev 43) (prog-if 10 >>>>>>> [OHCI]) >>>>>>> Subsystem: NEC Corporation Hama USB 2.0 CardBus >>>>>>> Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- >>>>>>> ParErr- Stepping- SERR- FastB2B- DisINTx- >>>>>>> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >>>>>>> >>>>>>> >>>>>>>> TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- >>>>>>>> >>>>>>>> >>>>>>> Interrupt: pin A routed to IRQ 16 >>>>>>> Region 0: Memory at d2502000 (32-bit, non-prefetchable) >>>>>>> [disabled] [size=4K] >>>>>>> Capabilities: [40] Power Management version 2 >>>>>>> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA >>>>>>> PME(D0+,D1+,D2+,D3hot+,D3cold-) >>>>>>> Status: D0 PME-Enable- DSel=0 DScale=0 PME- >>>>>>> Kernel driver in use: pciback >>>>>>> >>>>>>> 02:00.1 USB Controller: NEC Corporation USB (rev 43) (prog-if 10 >>>>>>> [OHCI]) >>>>>>> Subsystem: NEC Corporation Hama USB 2.0 CardBus >>>>>>> Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- >>>>>>> ParErr- Stepping- SERR- FastB2B- DisINTx- >>>>>>> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >>>>>>> >>>>>>> >>>>>>>> TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- >>>>>>>> >>>>>>>> >>>>>>> Interrupt: pin B routed to IRQ 17 >>>>>>> Region 0: Memory at d2501000 (32-bit, non-prefetchable) >>>>>>> [disabled] [size=4K] >>>>>>> Capabilities: [40] Power Management version 2 >>>>>>> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA >>>>>>> PME(D0+,D1+,D2+,D3hot+,D3cold-) >>>>>>> Status: D0 PME-Enable- DSel=0 DScale=0 PME- >>>>>>> Kernel driver in use: pciback >>>>>>> >>>>>>> 02:00.2 USB Controller: NEC Corporation USB 2.0 (rev 04) (prog-if 20 >>>>>>> [EHCI]) >>>>>>> Subsystem: NEC Corporation USB 2.0 >>>>>>> Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- >>>>>>> ParErr- Stepping- SERR- FastB2B- DisINTx- >>>>>>> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >>>>>>> >>>>>>> >>>>>>>> TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- >>>>>>>> >>>>>>>> >>>>>>> Interrupt: pin C routed to IRQ 18 >>>>>>> Region 0: Memory at d2500000 (32-bit, non-prefetchable) >>>>>>> [disabled] [size=256] >>>>>>> Capabilities: [40] Power Management version 2 >>>>>>> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA >>>>>>> PME(D0+,D1+,D2+,D3hot+,D3cold-) >>>>>>> Status: D0 PME-Enable- DSel=0 DScale=0 PME- >>>>>>> Kernel driver in use: pciback >>>>>>> >>>>>>> >>>>>>> On Fri, May 14, 2010 at 3:46 PM, chris <tknchris@gmail.com> wrote: >>>>>>> >>>>>>> >>>>>>>> I added a pci sound card and interestingly that works. I'm digging >>>>>>>> around for another pci-e device to try to identify if its all pci-e >>>>>>>> or only this device. Strange this is that I have a few other >>>>>>>> machines with this same usb controller which is working on 3.4.2. >>>>>>>> >>>>>>>> *scratches head* >>>>>>>> >>>>>>>> - chris >>>>>>>> >>>>>>>> On Fri, May 14, 2010 at 3:21 PM, Pasi Kärkkäinen <pasik@iki.fi> >>>>>>>> wrote: >>>>>>>> >>>>>>>> >>>>>>>>> On Fri, May 14, 2010 at 03:18:02PM -0400, chris wrote: >>>>>>>>> >>>>>>>>> >>>>>>>>>> It is a multifunction device, a pci-e usb controller, so I >>>>>>>>>> assumed all them had to be passed through. I just changed it to >>>>>>>>>> only 02:00.0 and same thing >>>>>>>>>> >>>>>>>>>> test-box2:~# cat /etc/xen/vm-five.cfg | grep pci pci = >>>>>>>>>> ['02:00.0'] test-box2:~# xm create /etc/xen/vm-five.cfg Using >>>>>>>>>> config file "/etc/xen/vm-five.cfg". >>>>>>>>>> Error: Failed to assign device to IOMMU >>>>>>>>>> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> Hmm.. weird. >>>>>>>>> >>>>>>>>> Two things to try: >>>>>>>>> >>>>>>>>> 1) Try passthru some other device (which is just a single pci id) >>>>>>>>> 2) Try passthru that pci-e usb controller to Linux PV guest and >>>>>>>>> see if that works >>>>>>>>> >>>>>>>>> -- Pasi >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> On Fri, May 14, 2010 at 3:11 PM, Pasi Kärkkäinen <pasik@iki.fi> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> On Fri, May 14, 2010 at 03:05:49PM -0400, chris wrote: >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> Pasi, >>>>>>>>>>>> >>>>>>>>>>>> Tried latest stable/2.6.32.x per your advice, no change. >>>>>>>>>>>> Anyone on xen-devel that can help me troubleshoot further? >>>>>>>>>>>> Everything looks right, can't figure out why vt-d is not >>>>>>>>>>>> working but it must be some kind of bug :( >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> Did you try the suggestion said earlier.. try to just passthru the >>>>>>>>>>> first pci device? >>>>>>>>>>> >>>>>>>>>>> -- Pasi >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> test-box2:~# uname -a >>>>>>>>>>>> Linux test-box2 2.6.32.12 #1 SMP Fri May 14 13:40:05 EDT 2010 >>>>>>>>>>>> x86_64 GNU/Linux >>>>>>>>>>>> >>>>>>>>>>>> test-box2:~# xm info | grep virt_caps virt_caps : >>>>>>>>>>>> hvm hvm_directio >>>>>>>>>>>> >>>>>>>>>>>> test-box2:~# xm pci-list-assignable-devices 0000:02:00.0 >>>>>>>>>>>> 0000:02:00.1 >>>>>>>>>>>> 0000:02:00.2 >>>>>>>>>>>> >>>>>>>>>>>> test-box2:~# xm create /etc/xen/vm-five.cfg Using config file >>>>>>>>>>>> "/etc/xen/vm-five.cfg". >>>>>>>>>>>> Error: Failed to assign device to IOMMU >>>>>>>>>>>> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>>>>>>>>>>> >>>>>>>>>>>> test-box2:~# cat /etc/xen/vm-five.cfg | grep -v '#' >>>>>>>>>>>> kernel = '/usr/lib/xen/boot/hvmloader' >>>>>>>>>>>> builder = 'hvm' >>>>>>>>>>>> memory = '1792' >>>>>>>>>>>> device_model='/usr/lib/xen/bin/qemu-dm' >>>>>>>>>>>> disk = [ 'phy:/dev/storage/vm-five,ioemu:hda,w', >>>>>>>>>>>> 'phy:/dev/sr0,ioemu:hdc:cdrom,r' >>>>>>>>>>>> ] >>>>>>>>>>>> name = 'vm-five' >>>>>>>>>>>> vif = ['type=ioemu, bridge=eth0, mac=00:16:3D:37:A1:42'] >>>>>>>>>>>> boot='dc' >>>>>>>>>>>> cpus='0-1' >>>>>>>>>>>> vcpus=2 >>>>>>>>>>>> acpi=1 >>>>>>>>>>>> ahci=1 >>>>>>>>>>>> vnc=1 >>>>>>>>>>>> sdl=0 >>>>>>>>>>>> timer_mode=1 >>>>>>>>>>>> usb=1 >>>>>>>>>>>> usbdevice='tablet' >>>>>>>>>>>> localtime=1 >>>>>>>>>>>> pci = ['02:00.0','02:00.1','02:00.2'] >>>>>>>>>>>> >>>>>>>>>>>> On Thu, May 13, 2010 at 2:28 PM, chris <tknchris@gmail.com> >>>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>> Forwarding to xen-devel. Can't seem to get VT-d working with >>>>>>>>>>>>> xen4 from tarball on xen.org 2.6.31.13 pv_ops dom0. On >>>>>>>>>>>>> pasi's advice I tried switching to stable/2.6.32.x branch >>>>>>>>>>>>> for dom0 and that doesnt even build. Did something change >>>>>>>>>>>>> recently thats breaking compilation? >>>>>>>>>>>>> >>>>>>>>>>>>> Attached is xen dmesg with iommu=verbose loglvl=all >>>>>>>>>>>>> guest_loglvl=all, and dom0 dmesg from 2.6.31.x >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>> >>>>>>>>>>>>> Any ideas on why VT-d is not working on this board? >>>>>>>>>>>>> Initialization looks good, xen reports hvm_directio >>>>>>>>>>>>> capability, everything says VT-d should work until domain is >>>>>>>>>>>>> created. >>>>>>>>>>>>> >>>>>>>>>>>>> Any ideas why stable/2.6.32.x wont build? >>>>>>>>>>>>> >>>>>>>>>>>>> - chris >>>>>>>>>>>>> >>>>>>>>>>>>> On Thu, May 13, 2010 at 2:07 PM, chris <tknchris@gmail.com> >>>>>>>>>>>>> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>>> I redid it with oldconfig which I didn't think would help >>>>>>>>>>>>>> and same thing. I guess this tree is broken? Can someone >>>>>>>>>>>>>> else try and see if they can build it? Ugh, whata day :) >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Thu, May 13, 2010 at 1:58 PM, Pasi Kärkkäinen <pasik@iki.fi> >>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Thu, May 13, 2010 at 01:55:25PM -0400, chris wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I used the default config on the wiki which you created. >>>>>>>>>>>>>>>> Steps I took were: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> # make clean distclean >>>>>>>>>>>>>>>> # wget -O .config >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> "http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.10-pvops-dom0-xen-stable-x86_64" >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> You should do "make oldconfig" at this point. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> # make -j8 bzImage >>>>>>>>>>>>>>>> (blah blah) >>>>>>>>>>>>>>>> LD vmlinux.o >>>>>>>>>>>>>>>> MODPOST vmlinux.o >>>>>>>>>>>>>>>> WARNING: modpost: Found 7 section mismatch(es). >>>>>>>>>>>>>>>> To see full details build your kernel with: >>>>>>>>>>>>>>>> 'make CONFIG_DEBUG_SECTION_MISMATCH=y' >>>>>>>>>>>>>>>> GEN .version >>>>>>>>>>>>>>>> CHK include/linux/compile.h >>>>>>>>>>>>>>>> UPD include/linux/compile.h >>>>>>>>>>>>>>>> CC init/version.o >>>>>>>>>>>>>>>> LD init/built-in.o >>>>>>>>>>>>>>>> LD .tmp_vmlinux1 >>>>>>>>>>>>>>>> drivers/built-in.o: In function `do_hvm_suspend': >>>>>>>>>>>>>>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: >>>>>>>>>>>>>>>> undefined reference to `xenbus_suspend' >>>>>>>>>>>>>>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: >>>>>>>>>>>>>>>> undefined reference to `xenbus_resume' >>>>>>>>>>>>>>>> make: *** [.tmp_vmlinux1] Error 1 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hmm.. weird. I wonder if something has changed recently or >>>>>>>>>>>>>>> what's going on in here.. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- Pasi >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Thu, May 13, 2010 at 11:47 AM, Pasi Kärkkäinen >>>>>>>>>>>>>>>> <pasik@iki.fi> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Thu, May 13, 2010 at 11:33:57AM -0400, chris wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Successfully grabbed the sources and failed to build: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> LD .tmp_vmlinux1 >>>>>>>>>>>>>>>>>> drivers/built-in.o: In function `do_hvm_suspend': >>>>>>>>>>>>>>>>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: >>>>>>>>>>>>>>>>>> undefined reference to `xenbus_suspend' >>>>>>>>>>>>>>>>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: >>>>>>>>>>>>>>>>>> undefined reference to `xenbus_resume' >>>>>>>>>>>>>>>>>> make: *** [.tmp_vmlinux1] Error 1 >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> :( >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Try the example .config files provided on the wiki page. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> -- Pasi >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Thu, May 13, 2010 at 10:14 AM, Pasi Kärkkäinen >>>>>>>>>>>>>>>>>> <pasik@iki.fi> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> On Thu, May 13, 2010 at 10:12:56AM -0400, chris wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Pasi, >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> How do I pull those kernel sources you referenced? >>>>>>>>>>>>>>>>>>>> I see it mentioned on >>>>>>>>>>>>>>>>>>>> http://wiki.xensource.com/xenwiki/XenParavirtOps but no >>>>>>>>>>>>>>>>>>>> details on how to retrieve it. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> The instructions are there if you read it carefully.. >>>>>>>>>>>>>>>>>>> There's the topic of how to switch branches. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> -- Pasi >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> - chris >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> On Thu, May 13, 2010 at 8:29 AM, Pasi Kärkkäinen >>>>>>>>>>>>>>>>>>>> <pasik@iki.fi> wrote: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> On Wed, May 12, 2010 at 08:41:34PM -0400, chris wrote: >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> When reading the vtdhowto I noticed the ability to set >>>>>>>>>>>>>>>>>>>>>> iommu=verbose. >>>>>>>>>>>>>>>>>>>>>> Here is that output, I don't know if it helps at >>>>>>>>>>>>>>>>>>>>>> all to figure out what is wrong. >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> That seems to be OK: >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> (XEN) I/O virtualisation enabled >>>>>>>>>>>>>>>>>>>>> (XEN) I/O virtualisation for PV guests disabled >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> So hmm.. I wonder if it's related to MSI stuff? >>>>>>>>>>>>>>>>>>>>> You could try xen.git xen/stable-2.6.32.x branch instead >>>>>>>>>>>>>>>>>>>>> and see if that makes a difference.. >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> -- Pasi >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> ---------- Forwarded message ---------- >>>>>>>>>>>>>>>>>>>>>> From: chris <tknchris@gmail.com> >>>>>>>>>>>>>>>>>>>>>> Date: Wed, May 12, 2010 at 5:28 PM >>>>>>>>>>>>>>>>>>>>>> Subject: Xen4 / Intel DX58SO Mobo / VT-d not >>>>>>>>>>>>>>>>>>>>>> working >>>>>>>>>>>>>>>>>>>>>> To: Xen-Users List >>>>>>>>>>>>>>>>>>>>>> <xen-users@lists.xensource.com> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> Hello, >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> I've previously been successful with Xen4 and >>>>>>>>>>>>>>>>>>>>>> VT-d on other systems. I am having trouble >>>>>>>>>>>>>>>>>>>>>> getting VT-d passthrough working to a WinXP >>>>>>>>>>>>>>>>>>>>>> domain with DX58SO (Q45) motherboard and i7 930 >>>>>>>>>>>>>>>>>>>>>> CPU. VT-d is enabled in bios, xm info shows >>>>>>>>>>>>>>>>>>>>>> hvm_directio capability, I have iommu=1 set, I >>>>>>>>>>>>>>>>>>>>>> have the devices bound to pciback on dom0 cmdline, xm >>>>>>>>>>>>>>>>>>>>>> pci-list-assignable-devices shows the devices as assignable. When I attempt >>>>>>>>>>>>>>>>>>>>>> to start the VM I get the error: >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> Error: Failed to assign device to IOMMU >>>>>>>>>>>>>>>>>>>>>> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> Below is all the information I can think of that >>>>>>>>>>>>>>>>>>>>>> would be useful to help debug it: >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> BIOS VT-d Enabled: >>>>>>>>>>>>>>>>>>>>>> http://i43.tinypic.com/nl3a5e.jpg >>>>>>>>>>>>>>>>>>>>>> http://i42.tinypic.com/nqvlu1.jpg >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> grub entry: >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> title Xen 4.0.0 / Debian GNU/Linux, >>>>>>>>>>>>>>>>>>>>>> kernel 2.6.31.13 root (hd0,0) kernel >>>>>>>>>>>>>>>>>>>>>> /boot/xen-4.0.0.gz iommu=1 dom0_mem=256M >>>>>>>>>>>>>>>>>>>>>> dom0_max_vcpus=1 dom0_vcpus_pin=true module >>>>>>>>>>>>>>>>>>>>>> /boot/vmlinuz-2.6.31.13 root=/dev/md0 ro >>>>>>>>>>>>>>>>>>>>>> console=tty0 xen-pciback.permissive >>>>>>>>>>>>>>>>>>>>>> xen-pciback.hide=(02:00.0)(02:00.1)(02:00.2)(04: >>>>>>>>>>>>>>>>>>>>>> 00.0)(04:00.1)(04:00.2)(07:00.0)(07:00.1)(07:00. >>>>>>>>>>>>>>>>>>>>>> 2)(09:00.0)(09:00.1)(09:00.2) module >>>>>>>>>>>>>>>>>>>>>> /boot/initrd.img-2.6.31.13 >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> # xm pci-list-assignable-devices 0000:09:00.0 >>>>>>>>>>>>>>>>>>>>>> 0000:09:00.1 >>>>>>>>>>>>>>>>>>>>>> 0000:09:00.2 >>>>>>>>>>>>>>>>>>>>>> 0000:07:00.0 >>>>>>>>>>>>>>>>>>>>>> 0000:07:00.1 >>>>>>>>>>>>>>>>>>>>>> 0000:07:00.2 >>>>>>>>>>>>>>>>>>>>>> 0000:04:00.0 >>>>>>>>>>>>>>>>>>>>>> 0000:04:00.1 >>>>>>>>>>>>>>>>>>>>>> 0000:04:00.2 >>>>>>>>>>>>>>>>>>>>>> 0000:02:00.0 >>>>>>>>>>>>>>>>>>>>>> 0000:02:00.1 >>>>>>>>>>>>>>>>>>>>>> 0000:02:00.2 >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> # xm info >>>>>>>>>>>>>>>>>>>>>> host : test-box2 release >>>>>>>>>>>>>>>>>>>>>> : 2.6.31.13 version : #2 SMP Wed >>>>>>>>>>>>>>>>>>>>>> May 12 14:11:37 EDT 2010 machine >>>>>>>>>>>>>>>>>>>>>> : x86_64 nr_cpus : 8 nr_nodes >>>>>>>>>>>>>>>>>>>>>> : 1 cores_per_socket : 4 threads_per_core >>>>>>>>>>>>>>>>>>>>>> : 2 cpu_mhz : 2800 hw_caps >>>>>>>>>>>>>>>>>>>>>> : >>>>>>>>>>>>>>>>>>>>>> bfebfbff:28100800:00000000:00001b40:0098e3bd:000 >>>>>>>>>>>>>>>>>>>>>> 00000:00000001:00000000 virt_caps : >>>>>>>>>>>>>>>>>>>>>> hvm hvm_directio total_memory : 7950 >>>>>>>>>>>>>>>>>>>>>> free_memory : 7812 node_to_cpu >>>>>>>>>>>>>>>>>>>>>> : node0:0-7 node_to_memory : node0:7812 >>>>>>>>>>>>>>>>>>>>>> node_to_dma32_mem : node0:3249 max_node_id >>>>>>>>>>>>>>>>>>>>>> : 0 xen_major : 4 xen_minor >>>>>>>>>>>>>>>>>>>>>> : 0 xen_extra : .0 xen_caps >>>>>>>>>>>>>>>>>>>>>> : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 >>>>>>>>>>>>>>>>>>>>>> hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler >>>>>>>>>>>>>>>>>>>>>> : credit xen_pagesize : 4096 >>>>>>>>>>>>>>>>>>>>>> platform_params : >>>>>>>>>>>>>>>>>>>>>> virt_start=0xffff800000000000 xen_changeset >>>>>>>>>>>>>>>>>>>>>> : unavailable xen_commandline : iommu=1 >>>>>>>>>>>>>>>>>>>>>> dom0_mem=256M dom0_max_vcpus=1 >>>>>>>>>>>>>>>>>>>>>> dom0_vcpus_pin=true cc_compiler : gcc >>>>>>>>>>>>>>>>>>>>>> version 4.3.2 (Debian 4.3.2-1.1) cc_compile_by >>>>>>>>>>>>>>>>>>>>>> : root cc_compile_domain : >>>>>>>>>>>>>>>>>>>>>> cc_compile_date : Thu May 6 13:41:25 EDT >>>>>>>>>>>>>>>>>>>>>> 2010 xend_config_format : 4 >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> # xm create vm-five.cfg Using config file >>>>>>>>>>>>>>>>>>>>>> "./vm-five.cfg". >>>>>>>>>>>>>>>>>>>>>> Error: Failed to assign device to IOMMU >>>>>>>>>>>>>>>>>>>>>> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> I feel like I'm missing something really obvious >>>>>>>>>>>>>>>>>>>>>> but I've been at it for a while now and have run >>>>>>>>>>>>>>>>>>>>>> out of brain power. Anyone have any idea what might be >>>>>>>>>>>>>>>>>>>>>> wrong? >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> - chris >>>>>>>>>>>>>>>>>>>>>> __ __ >>>>>>>>>>>>>>>>>>>>>> _ _ ___ ___ >>>>>>>>>>>>>>>>>>>>>> \ \/ /___ _ __ | || | / _ \ / _ \ >>>>>>>>>>>>>>>>>>>>>> \ // _ \ \047_ \ | || |_| | | | | | | >>>>>>>>>>>>>>>>>>>>>> / \ __/ | | | |__ _| |_| | |_| | >>>>>>>>>>>>>>>>>>>>>> /_/\_\___|_| |_| |_|(_)___(_)___/ >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> (XEN) Xen version 4.0.0 (root@) (gcc version >>>>>>>>>>>>>>>>>>>>>> 4.3.2 (Debian 4.3.2-1.1) ) Thu May 6 13:41:25 >>>>>>>>>>>>>>>>>>>>>> EDT 2010 >>>>>>>>>>>>>>>>>>>>>> (XEN) Latest ChangeSet: unavailable >>>>>>>>>>>>>>>>>>>>>> (XEN) Command line: iommu=verbose dom0_mem=256M >>>>>>>>>>>>>>>>>>>>>> dom0_max_vcpus=1 dom0_vcpus_pin=true >>>>>>>>>>>>>>>>>>>>>> (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 - 000000000008f000 >>>>>>>>>>>>>>>>>>>>>> (usable) >>>>>>>>>>>>>>>>>>>>>> (XEN) 000000000008f000 - 0000000000090000 >>>>>>>>>>>>>>>>>>>>>> (reserved) >>>>>>>>>>>>>>>>>>>>>> (XEN) 0000000000090000 - 000000000009ec00 >>>>>>>>>>>>>>>>>>>>>> (usable) >>>>>>>>>>>>>>>>>>>>>> (XEN) 000000000009ec00 - 00000000000a0000 >>>>>>>>>>>>>>>>>>>>>> (reserved) >>>>>>>>>>>>>>>>>>>>>> (XEN) 00000000000e0000 - 0000000000100000 >>>>>>>>>>>>>>>>>>>>>> (reserved) >>>>>>>>>>>>>>>>>>>>>> (XEN) 0000000000100000 - 00000000cf4bd000 >>>>>>>>>>>>>>>>>>>>>> (usable) >>>>>>>>>>>>>>>>>>>>>> (XEN) 00000000cf4bd000 - 00000000cf4bf000 >>>>>>>>>>>>>>>>>>>>>> (reserved) >>>>>>>>>>>>>>>>>>>>>> (XEN) 00000000cf4bf000 - 00000000cf4c2000 >>>>>>>>>>>>>>>>>>>>>> (usable) >>>>>>>>>>>>>>>>>>>>>> (XEN) 00000000cf4c2000 - 00000000cf7bf000 (ACPI >>>>>>>>>>>>>>>>>>>>>> NVS) >>>>>>>>>>>>>>>>>>>>>> (XEN) 00000000cf7bf000 - 00000000cf7df000 >>>>>>>>>>>>>>>>>>>>>> (usable) >>>>>>>>>>>>>>>>>>>>>> (XEN) 00000000cf7df000 - 00000000cf7ff000 (ACPI >>>>>>>>>>>>>>>>>>>>>> data) >>>>>>>>>>>>>>>>>>>>>> (XEN) 00000000cf7ff000 - 00000000cf800000 >>>>>>>>>>>>>>>>>>>>>> (usable) >>>>>>>>>>>>>>>>>>>>>> (XEN) 00000000cf800000 - 00000000d0000000 >>>>>>>>>>>>>>>>>>>>>> (reserved) >>>>>>>>>>>>>>>>>>>>>> (XEN) 00000000f8000000 - 00000000fd000000 >>>>>>>>>>>>>>>>>>>>>> (reserved) >>>>>>>>>>>>>>>>>>>>>> (XEN) 00000000ffe00000 - 0000000100000000 >>>>>>>>>>>>>>>>>>>>>> (reserved) >>>>>>>>>>>>>>>>>>>>>> (XEN) 0000000100000000 - 0000000230000000 >>>>>>>>>>>>>>>>>>>>>> (usable) >>>>>>>>>>>>>>>>>>>>>> (XEN) ACPI: RSDP 000FE020, 0024 (r2 INTEL ) >>>>>>>>>>>>>>>>>>>>>> (XEN) ACPI: XSDT CF7FE120, 0074 (r1 INTEL >>>>>>>>>>>>>>>>>>>>>> DX58SO 11F6 1000013) >>>>>>>>>>>>>>>>>>>>>> (XEN) ACPI: FACP CF7FD000, 00F4 (r3 INTEL >>>>>>>>>>>>>>>>>>>>>> DX58SO 11F6 MSFT 100000D) >>>>>>>>>>>>>>>>>>>>>> (XEN) ACPI Warning (tbfadt-0444): Optional field >>>>>>>>>>>>>>>>>>>>>> "Pm2ControlBlock" has zero address or length: >>>>>>>>>>>>>>>>>>>>>> 0000000000000450/0 [20070126] >>>>>>>>>>>>>>>>>>>>>> (XEN) ACPI: DSDT CF7F8000, 4641 (r2 INTEL >>>>>>>>>>>>>>>>>>>>>> DX58SO 11F6 MSFT 100000D) >>>>>>>>>>>>>>>>>>>>>> (XEN) ACPI: FACS CF728000, 0040 >>>>>>>>>>>>>>>>>>>>>> (XEN) ACPI: APIC CF7F7000, 0138 (r2 INTEL >>>>>>>>>>>>>>>>>>>>>> DX58SO 11F6 MSFT 100000D) >>>>>>>>>>>>>>>>>>>>>> (XEN) ACPI: WDDT CF7F6000, 0040 (r1 INTEL >>>>>>>>>>>>>>>>>>>>>> DX58SO 11F6 MSFT 100000D) >>>>>>>>>>>>>>>>>>>>>> (XEN) ACPI: MCFG CF7F5000, 003C (r1 INTEL >>>>>>>>>>>>>>>>>>>>>> DX58SO 11F6 MSFT 100000D) >>>>>>>>>>>>>>>>>>>>>> (XEN) ACPI: ASF! CF7F4000, 00AC (r32 INTEL >>>>>>>>>>>>>>>>>>>>>> DX58SO 11F6 MSFT 100000D) >>>>>>>>>>>>>>>>>>>>>> (XEN) ACPI: HPET CF7F3000, 0038 (r1 INTEL >>>>>>>>>>>>>>>>>>>>>> DX58SO 11F6 MSFT 100000D) >>>>>>>>>>>>>>>>>>>>>> (XEN) ACPI: SSDT CF7E2000, E134 (r1 INTEL SSDT >>>>>>>>>>>>>>>>>>>>>> PM 11F6 MSFT 100000D) >>>>>>>>>>>>>>>>>>>>>> (XEN) ACPI: DMAR CF7DF000, 0140 (r1 INTEL >>>>>>>>>>>>>>>>>>>>>> DX58SO 11F6 MSFT 100000D) >>>>>>>>>>>>>>>>>>>>>> (XEN) ACPI: WDTT CF7F1000, 020C (r2 INTEL >>>>>>>>>>>>>>>>>>>>>> DX58SO 11F6 MSFT 100000D) >>>>>>>>>>>>>>>>>>>>>> (XEN) ACPI: ASPT CF7F2000, 0034 (r4 INTEL >>>>>>>>>>>>>>>>>>>>>> PerfTune 11F6 MSFT 100000D) >>>>>>>>>>>>>>>>>>>>>> (XEN) System RAM: 7950MB (8140820kB) >>>>>>>>>>>>>>>>>>>>>> (XEN) Domain heap initialised >>>>>>>>>>>>>>>>>>>>>> (XEN) Processor #0 7:10 APIC version 21 >>>>>>>>>>>>>>>>>>>>>> (XEN) Processor #2 7:10 APIC version 21 >>>>>>>>>>>>>>>>>>>>>> (XEN) Processor #4 7:10 APIC version 21 >>>>>>>>>>>>>>>>>>>>>> (XEN) Processor #6 7:10 APIC version 21 >>>>>>>>>>>>>>>>>>>>>> (XEN) Processor #1 7:10 APIC version 21 >>>>>>>>>>>>>>>>>>>>>> (XEN) Processor #3 7:10 APIC version 21 >>>>>>>>>>>>>>>>>>>>>> (XEN) Processor #5 7:10 APIC version 21 >>>>>>>>>>>>>>>>>>>>>> (XEN) Processor #7 7:10 APIC version 21 >>>>>>>>>>>>>>>>>>>>>> (XEN) IOAPIC[0]: apic_id 8, version 32, address >>>>>>>>>>>>>>>>>>>>>> 0xfec00000, GSI 0-23 >>>>>>>>>>>>>>>>>>>>>> (XEN) Enabling APIC mode: Flat. Using 1 I/O >>>>>>>>>>>>>>>>>>>>>> APICs >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:679: Host address width 39 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:398: dmaru->address = >>>>>>>>>>>>>>>>>>>>>> fe711000 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:334: endpoint: 0:1b.0 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:398: dmaru->address = >>>>>>>>>>>>>>>>>>>>>> fe710000 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:340: IOAPIC: f0:1f.7 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:411: flags: INCLUDE_ALL >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >>>>>>>>>>>>>>>>>>>>>> e9000 end_address e9fff >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.1 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >>>>>>>>>>>>>>>>>>>>>> ea000 end_address eafff >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.2 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >>>>>>>>>>>>>>>>>>>>>> eb000 end_address ebfff >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.0 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >>>>>>>>>>>>>>>>>>>>>> e6000 end_address e6fff >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.1 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >>>>>>>>>>>>>>>>>>>>>> e7000 end_address e7fff >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.2 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >>>>>>>>>>>>>>>>>>>>>> e8000 end_address e8fff >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr >>>>>>>>>>>>>>>>>>>>>> ec000 end_address eefff >>>>>>>>>>>>>>>>>>>>>> (XEN) Using scheduler: SMP Credit Scheduler >>>>>>>>>>>>>>>>>>>>>> (credit) >>>>>>>>>>>>>>>>>>>>>> (XEN) Detected 2800.125 MHz processor. >>>>>>>>>>>>>>>>>>>>>> (XEN) Initing memory sharing. >>>>>>>>>>>>>>>>>>>>>> (XEN) VMX: Supported advanced features: >>>>>>>>>>>>>>>>>>>>>> (XEN) - APIC MMIO access virtualisation >>>>>>>>>>>>>>>>>>>>>> (XEN) - APIC TPR shadow >>>>>>>>>>>>>>>>>>>>>> (XEN) - Extended Page Tables (EPT) >>>>>>>>>>>>>>>>>>>>>> (XEN) - Virtual-Processor Identifiers (VPID) >>>>>>>>>>>>>>>>>>>>>> (XEN) - Virtual NMI >>>>>>>>>>>>>>>>>>>>>> (XEN) - MSR direct-access bitmap >>>>>>>>>>>>>>>>>>>>>> (XEN) HVM: ASIDs enabled. >>>>>>>>>>>>>>>>>>>>>> (XEN) HVM: VMX enabled >>>>>>>>>>>>>>>>>>>>>> (XEN) HVM: Hardware Assisted Paging detected. >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1078: drhd->address = >>>>>>>>>>>>>>>>>>>>>> fe711000 iommu->reg = ffff82c3fff57000 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1080: cap = c9008010e60262 >>>>>>>>>>>>>>>>>>>>>> ecap = f0207a >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1078: drhd->address = >>>>>>>>>>>>>>>>>>>>>> fe710000 iommu->reg = ffff82c3fff56000 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1080: cap = c90780106f0462 >>>>>>>>>>>>>>>>>>>>>> ecap = f020fa >>>>>>>>>>>>>>>>>>>>>> (XEN) Intel VT-d Snoop Control not supported. >>>>>>>>>>>>>>>>>>>>>> (XEN) Intel VT-d DMA Passthrough not supported. >>>>>>>>>>>>>>>>>>>>>> (XEN) Intel VT-d Queued Invalidation supported. >>>>>>>>>>>>>>>>>>>>>> (XEN) Intel VT-d Interrupt Remapping supported. >>>>>>>>>>>>>>>>>>>>>> (XEN) I/O virtualisation enabled >>>>>>>>>>>>>>>>>>>>>> (XEN) I/O virtualisation for PV guests disabled >>>>>>>>>>>>>>>>>>>>>> (XEN) Total of 8 processors activated. >>>>>>>>>>>>>>>>>>>>>> (XEN) ENABLING IO-APIC IRQs >>>>>>>>>>>>>>>>>>>>>> (XEN) -> Using new ACK method >>>>>>>>>>>>>>>>>>>>>> (XEN) TSC is reliable, synchronization >>>>>>>>>>>>>>>>>>>>>> unnecessary >>>>>>>>>>>>>>>>>>>>>> (XEN) Platform timer is 14.318MHz HPET >>>>>>>>>>>>>>>>>>>>>> (XEN) Allocated console ring of 16 KiB. >>>>>>>>>>>>>>>>>>>>>> (XEN) Brought up 8 CPUs >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 0:0.0 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 0:10.0 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 0:10.1 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >>>>>>>>>>>>>>>>>>>>>> 0:14.0 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >>>>>>>>>>>>>>>>>>>>>> 0:14.1 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >>>>>>>>>>>>>>>>>>>>>> 0:14.2 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 0:14.3 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 0:19.0 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 0:1a.0 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 0:1a.1 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 0:1a.2 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 0:1a.7 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >>>>>>>>>>>>>>>>>>>>>> 0:1b.0 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 0:1d.0 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 0:1d.1 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 0:1d.2 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 0:1d.7 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 0:1f.0 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 0:1f.2 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 0:1f.3 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 0:1f.5 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 2:0.0 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 2:0.1 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 2:0.2 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 4:0.0 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 4:0.1 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 4:0.2 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >>>>>>>>>>>>>>>>>>>>>> 5:0.0 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 7:0.0 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 7:0.1 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 7:0.2 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 9:0.0 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 9:0.1 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 9:0.2 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = >>>>>>>>>>>>>>>>>>>>>> a:0.0 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> b:3.0 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> b:3.1 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> b:3.2 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> b:3.3 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> b:3.4 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> b:3.5 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> b:3.6 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> b:3.7 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 3f:0.0 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 3f:0.1 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 3f:2.0 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 3f:2.1 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 3f:3.0 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 3f:3.1 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 3f:3.4 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 3f:4.0 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 3f:4.1 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 3f:4.2 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 3f:4.3 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 3f:5.0 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 3f:5.1 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 3f:5.2 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 3f:5.3 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 3f:6.0 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 3f:6.1 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 3f:6.2 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = >>>>>>>>>>>>>>>>>>>>>> 3f:6.3 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:695: >>>>>>>>>>>>>>>>>>>>>> iommu_enable_translation: iommu->reg = >>>>>>>>>>>>>>>>>>>>>> ffff82c3fff57000 >>>>>>>>>>>>>>>>>>>>>> (XEN) [VT-D]iommu.c:695: >>>>>>>>>>>>>>>>>>>>>> iommu_enable_translation: iommu->reg = >>>>>>>>>>>>>>>>>>>>>> ffff82c3fff56000 >>>>>>>>>>>>>>>>>>>>>> (XEN) *** LOADING DOMAIN 0 *** >>>>>>>>>>>>>>>>>>>>>> (XEN) Xen kernel: 64-bit, lsb, compat32 >>>>>>>>>>>>>>>>>>>>>> (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr >>>>>>>>>>>>>>>>>>>>>> 0x1000000 -> 0x26ae000 >>>>>>>>>>>>>>>>>>>>>> (XEN) PHYSICAL MEMORY ARRANGEMENT: >>>>>>>>>>>>>>>>>>>>>> (XEN) Dom0 alloc.: >>>>>>>>>>>>>>>>>>>>>> 0000000210000000->0000000220000000 >>>>>>>>>>>>>>>>>>>>>> (XEN) VIRTUAL MEMORY ARRANGEMENT: >>>>>>>>>>>>>>>>>>>>>> (XEN) Loaded kernel: >>>>>>>>>>>>>>>>>>>>>> ffffffff81000000->ffffffff826ae000 >>>>>>>>>>>>>>>>>>>>>> (XEN) Init. ramdisk: >>>>>>>>>>>>>>>>>>>>>> ffffffff826ae000->ffffffff8f4de600 >>>>>>>>>>>>>>>>>>>>>> (XEN) Phys-Mach map: >>>>>>>>>>>>>>>>>>>>>> ffffffff8f4df000->ffffffff8f55f000 >>>>>>>>>>>>>>>>>>>>>> (XEN) Start info: >>>>>>>>>>>>>>>>>>>>>> ffffffff8f55f000->ffffffff8f55f4b4 >>>>>>>>>>>>>>>>>>>>>> (XEN) Page tables: >>>>>>>>>>>>>>>>>>>>>> ffffffff8f560000->ffffffff8f5df000 >>>>>>>>>>>>>>>>>>>>>> (XEN) Boot stack: >>>>>>>>>>>>>>>>>>>>>> ffffffff8f5df000->ffffffff8f5e0000 >>>>>>>>>>>>>>>>>>>>>> (XEN) TOTAL: >>>>>>>>>>>>>>>>>>>>>> ffffffff80000000->ffffffff8f800000 >>>>>>>>>>>>>>>>>>>>>> (XEN) ENTRY ADDRESS: ffffffff81a10860 >>>>>>>>>>>>>>>>>>>>>> (XEN) Dom0 has maximum 1 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 >>>>>>>>>>>>>>>>>>>>>> \047CTRL-a\047 three times to switch input to >>>>>>>>>>>>>>>>>>>>>> Xen) >>>>>>>>>>>>>>>>>>>>>> (XEN) Freed 164kB init memory. >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=000109f0 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=00010000 >>>>>>>>>>>>>>>>>>>>>> pirq=0 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin >>>>>>>>>>>>>>>>>>>>>> for in-use IRQ! >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=2, irq=0 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=000109f0 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=000009f0 >>>>>>>>>>>>>>>>>>>>>> pirq=0 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin >>>>>>>>>>>>>>>>>>>>>> for in-use IRQ! >>>>>>>>>>>>>>>>>>>>>> (XEN) irq.c:1445: dom0: pirq 0 or irq 3 already >>>>>>>>>>>>>>>>>>>>>> mapped >>>>>>>>>>>>>>>>>>>>>> (XEN) irq.c:1445: dom0: pirq 0 or irq 4 already >>>>>>>>>>>>>>>>>>>>>> mapped >>>>>>>>>>>>>>>>>>>>>> (XEN) irq.c:1445: dom0: pirq 0 or irq 5 already >>>>>>>>>>>>>>>>>>>>>> mapped >>>>>>>>>>>>>>>>>>>>>> (XEN) irq.c:1445: dom0: pirq 0 or irq 6 already >>>>>>>>>>>>>>>>>>>>>> mapped >>>>>>>>>>>>>>>>>>>>>> (XEN) irq.c:1445: dom0: pirq 0 or irq 7 already >>>>>>>>>>>>>>>>>>>>>> mapped >>>>>>>>>>>>>>>>>>>>>> (XEN) irq.c:1445: dom0: pirq 0 or irq 8 already >>>>>>>>>>>>>>>>>>>>>> mapped >>>>>>>>>>>>>>>>>>>>>> (XEN) irq.c:1445: dom0: pirq 0 or irq 9 already >>>>>>>>>>>>>>>>>>>>>> mapped >>>>>>>>>>>>>>>>>>>>>> (XEN) irq.c:1445: dom0: pirq 0 or irq 10 already >>>>>>>>>>>>>>>>>>>>>> mapped >>>>>>>>>>>>>>>>>>>>>> (XEN) irq.c:1445: dom0: pirq 0 or irq 11 already >>>>>>>>>>>>>>>>>>>>>> mapped >>>>>>>>>>>>>>>>>>>>>> (XEN) irq.c:1445: dom0: pirq 0 or irq 12 already >>>>>>>>>>>>>>>>>>>>>> mapped >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=000009f0 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=00010000 >>>>>>>>>>>>>>>>>>>>>> pirq=0 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin >>>>>>>>>>>>>>>>>>>>>> for in-use IRQ! >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=0001a9c0 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=0000a9c0 >>>>>>>>>>>>>>>>>>>>>> pirq=18 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin >>>>>>>>>>>>>>>>>>>>>> for in-use IRQ! >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=0001a9c8 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=0000a9c8 >>>>>>>>>>>>>>>>>>>>>> pirq=19 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin >>>>>>>>>>>>>>>>>>>>>> for in-use IRQ! >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=23, irq=23 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=0001a929 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=0000a929 >>>>>>>>>>>>>>>>>>>>>> pirq=23 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin >>>>>>>>>>>>>>>>>>>>>> for in-use IRQ! >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=0001a9c8 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=0000a9c8 >>>>>>>>>>>>>>>>>>>>>> pirq=19 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin >>>>>>>>>>>>>>>>>>>>>> for in-use IRQ! >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=0001a9c0 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=0000a9c0 >>>>>>>>>>>>>>>>>>>>>> pirq=18 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin >>>>>>>>>>>>>>>>>>>>>> for in-use IRQ! >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=0001a9b0 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=0000a9b0 >>>>>>>>>>>>>>>>>>>>>> pirq=16 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin >>>>>>>>>>>>>>>>>>>>>> for in-use IRQ! >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=0001a9b0 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=0000a9b0 >>>>>>>>>>>>>>>>>>>>>> pirq=16 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin >>>>>>>>>>>>>>>>>>>>>> for in-use IRQ! >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=0001a9c8 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=0000a9c8 >>>>>>>>>>>>>>>>>>>>>> pirq=19 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin >>>>>>>>>>>>>>>>>>>>>> for in-use IRQ! >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: new_entry=0001a9c0 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: old_entry=0000a9c0 >>>>>>>>>>>>>>>>>>>>>> pirq=18 >>>>>>>>>>>>>>>>>>>>>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin >>>>>>>>>>>>>>>>>>>>>> for in-use IRQ! >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>>>>> Xen-users mailing list >>>>>>>>>>>>>>>>>>>>>> Xen-users@lists.xensource.com >>>>>>>>>>>>>>>>>>>>>> http://lists.xensource.com/xen-users >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >> ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: Re: [Xen-users] RE: Xen4 / Intel DX58SO Mobo / VT-d not working 2010-05-14 19:46 ` [Xen-users] " chris 2010-05-14 20:39 ` chris @ 2010-05-14 21:25 ` Sander Eikelenboom 2010-05-14 21:26 ` chris 1 sibling, 1 reply; 32+ messages in thread From: Sander Eikelenboom @ 2010-05-14 21:25 UTC (permalink / raw) To: chris; +Cc: Xen-Devel List, Xen-Users List Hello chris, But does the other machine have an IOMMU on 3.4.2 ? I passthrough a few USB controllers my self, but the machine doesn't have a hardware IOMMU, so it uses the SWIOTLB changed by Konrad to work with Xen and let the DMA of the USB controllers work. It's working on xen-4.0.1-testing, xen-next pvops kernel from a few weeks ago, various domU kernel. One domU kernel is a 2.6.33 from Konrad's tree, with patched and backported xhci support from 2.6.34. So perhaps you could try with the IOMMU off, see if it makes a difference, and would point the problem to the IOMMU more specifically. Oh yes, what pci backend mode have you choosen in your dom0 kernel config ? You have 3 options, virtual, passthrough or slot. I allways tend to use passthrough, don't know it it makes a big difference though, but at least all functions get registered under the same device id in the guest. -- Sander Friday, May 14, 2010, 9:46:01 PM, you wrote: > I added a pci sound card and interestingly that works. I'm digging > around for another pci-e device to try to identify if its all pci-e or > only this device. Strange this is that I have a few other machines > with this same usb controller which is working on 3.4.2. > *scratches head* > - chris > On Fri, May 14, 2010 at 3:21 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >> On Fri, May 14, 2010 at 03:18:02PM -0400, chris wrote: >>> It is a multifunction device, a pci-e usb controller, so I assumed all >>> them had to be passed through. I just changed it to only 02:00.0 and >>> same thing >>> >>> test-box2:~# cat /etc/xen/vm-five.cfg | grep pci >>> pci = ['02:00.0'] >>> test-box2:~# xm create /etc/xen/vm-five.cfg >>> Using config file "/etc/xen/vm-five.cfg". >>> Error: Failed to assign device to IOMMU >>> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>> >> >> Hmm.. weird. >> >> Two things to try: >> >> 1) Try passthru some other device (which is just a single pci id) >> 2) Try passthru that pci-e usb controller to Linux PV guest and see if that works >> >> -- Pasi >> >>> >>> On Fri, May 14, 2010 at 3:11 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>> > On Fri, May 14, 2010 at 03:05:49PM -0400, chris wrote: >>> >> Pasi, >>> >> >>> >> Tried latest stable/2.6.32.x per your advice, no change. Anyone on >>> >> xen-devel that can help me troubleshoot further? Everything looks >>> >> right, can't figure out why vt-d is not working but it must be some >>> >> kind of bug :( >>> >> >>> > >>> > Did you try the suggestion said earlier.. try to just passthru the first pci device? >>> > >>> > -- Pasi >>> > >>> >> test-box2:~# uname -a >>> >> Linux test-box2 2.6.32.12 #1 SMP Fri May 14 13:40:05 EDT 2010 x86_64 GNU/Linux >>> >> >>> >> test-box2:~# xm info | grep virt_caps >>> >> virt_caps : hvm hvm_directio >>> >> >>> >> test-box2:~# xm pci-list-assignable-devices >>> >> 0000:02:00.0 >>> >> 0000:02:00.1 >>> >> 0000:02:00.2 >>> >> >>> >> test-box2:~# xm create /etc/xen/vm-five.cfg >>> >> Using config file "/etc/xen/vm-five.cfg". >>> >> Error: Failed to assign device to IOMMU >>> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>> >> >>> >> test-box2:~# cat /etc/xen/vm-five.cfg | grep -v '#' >>> >> kernel = '/usr/lib/xen/boot/hvmloader' >>> >> builder = 'hvm' >>> >> memory = '1792' >>> >> device_model='/usr/lib/xen/bin/qemu-dm' >>> >> disk = [ 'phy:/dev/storage/vm-five,ioemu:hda,w', >>> >> 'phy:/dev/sr0,ioemu:hdc:cdrom,r' >>> >> ] >>> >> name = 'vm-five' >>> >> vif = ['type=ioemu, bridge=eth0, mac=00:16:3D:37:A1:42'] >>> >> boot='dc' >>> >> cpus='0-1' >>> >> vcpus=2 >>> >> acpi=1 >>> >> ahci=1 >>> >> vnc=1 >>> >> sdl=0 >>> >> timer_mode=1 >>> >> usb=1 >>> >> usbdevice='tablet' >>> >> localtime=1 >>> >> pci = ['02:00.0','02:00.1','02:00.2'] >>> >> >>> >> On Thu, May 13, 2010 at 2:28 PM, chris <tknchris@gmail.com> wrote: >>> >> > Forwarding to xen-devel. Can't seem to get VT-d working with xen4 from >>> >> > tarball on xen.org 2.6.31.13 pv_ops dom0. On pasi's advice I tried >>> >> > switching to stable/2.6.32.x branch for dom0 and that doesnt even >>> >> > build. Did something change recently thats breaking compilation? >>> >> > >>> >> > Attached is xen dmesg with iommu=verbose loglvl=all guest_loglvl=all, >>> >> > and dom0 dmesg from 2.6.31.x >>> >> > >>> >> > Any ideas on why VT-d is not working on this board? Initialization >>> >> > looks good, xen reports hvm_directio capability, everything says VT-d >>> >> > should work until domain is created. >>> >> > >>> >> > Any ideas why stable/2.6.32.x wont build? >>> >> > >>> >> > - chris >>> >> > >>> >> > On Thu, May 13, 2010 at 2:07 PM, chris <tknchris@gmail.com> wrote: >>> >> >> I redid it with oldconfig which I didn't think would help and same >>> >> >> thing. I guess this tree is broken? Can someone else try and see if >>> >> >> they can build it? Ugh, whata day :) >>> >> >> >>> >> >> On Thu, May 13, 2010 at 1:58 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>> >> >>> On Thu, May 13, 2010 at 01:55:25PM -0400, chris wrote: >>> >> >>>> I used the default config on the wiki which you created. Steps I took were: >>> >> >>>> >>> >> >>>> # make clean distclean >>> >> >>>> # wget -O .config >>> >> >>>> "http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.10-pvops-dom0-xen-stable-x86_64" >>> >> >>> >>> >> >>> You should do "make oldconfig" at this point. >>> >> >>> >>> >> >>>> # make -j8 bzImage >>> >> >>>> (blah blah) >>> >> >>>> LD vmlinux.o >>> >> >>>> MODPOST vmlinux.o >>> >> >>>> WARNING: modpost: Found 7 section mismatch(es). >>> >> >>>> To see full details build your kernel with: >>> >> >>>> 'make CONFIG_DEBUG_SECTION_MISMATCH=y' >>> >> >>>> GEN .version >>> >> >>>> CHK include/linux/compile.h >>> >> >>>> UPD include/linux/compile.h >>> >> >>>> CC init/version.o >>> >> >>>> LD init/built-in.o >>> >> >>>> LD .tmp_vmlinux1 >>> >> >>>> drivers/built-in.o: In function `do_hvm_suspend': >>> >> >>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: undefined reference >>> >> >>>> to `xenbus_suspend' >>> >> >>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: undefined reference >>> >> >>>> to `xenbus_resume' >>> >> >>>> make: *** [.tmp_vmlinux1] Error 1 >>> >> >>>> >>> >> >>> >>> >> >>> Hmm.. weird. I wonder if something has changed recently or what's going on in here.. >>> >> >>> >>> >> >>> -- Pasi >>> >> >>> >>> >> >>>> >>> >> >>>> On Thu, May 13, 2010 at 11:47 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>> >> >>>> > On Thu, May 13, 2010 at 11:33:57AM -0400, chris wrote: >>> >> >>>> >> Successfully grabbed the sources and failed to build: >>> >> >>>> >> >>> >> >>>> >> LD .tmp_vmlinux1 >>> >> >>>> >> drivers/built-in.o: In function `do_hvm_suspend': >>> >> >>>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: undefined reference >>> >> >>>> >> to `xenbus_suspend' >>> >> >>>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: undefined reference >>> >> >>>> >> to `xenbus_resume' >>> >> >>>> >> make: *** [.tmp_vmlinux1] Error 1 >>> >> >>>> >> >>> >> >>>> >> :( >>> >> >>>> >> >>> >> >>>> > >>> >> >>>> > Try the example .config files provided on the wiki page. >>> >> >>>> > >>> >> >>>> > -- Pasi >>> >> >>>> > >>> >> >>>> >> On Thu, May 13, 2010 at 10:14 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>> >> >>>> >> > On Thu, May 13, 2010 at 10:12:56AM -0400, chris wrote: >>> >> >>>> >> >> Pasi, >>> >> >>>> >> >> >>> >> >>>> >> >> How do I pull those kernel sources you referenced? I see it mentioned >>> >> >>>> >> >> on http://wiki.xensource.com/xenwiki/XenParavirtOps but no details on >>> >> >>>> >> >> how to retrieve it. >>> >> >>>> >> >> >>> >> >>>> >> > >>> >> >>>> >> > The instructions are there if you read it carefully.. >>> >> >>>> >> > There's the topic of how to switch branches. >>> >> >>>> >> > >>> >> >>>> >> > -- Pasi >>> >> >>>> >> > >>> >> >>>> >> >> - chris >>> >> >>>> >> >> >>> >> >>>> >> >> On Thu, May 13, 2010 at 8:29 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>> >> >>>> >> >> > On Wed, May 12, 2010 at 08:41:34PM -0400, chris wrote: >>> >> >>>> >> >> >> When reading the vtdhowto I noticed the ability to set iommu=verbose. >>> >> >>>> >> >> >> Here is that output, I don't know if it helps at all to figure out >>> >> >>>> >> >> >> what is wrong. >>> >> >>>> >> >> >> >>> >> >>>> >> >> > >>> >> >>>> >> >> > That seems to be OK: >>> >> >>>> >> >> > >>> >> >>>> >> >> > (XEN) I/O virtualisation enabled >>> >> >>>> >> >> > (XEN) I/O virtualisation for PV guests disabled >>> >> >>>> >> >> > >>> >> >>>> >> >> > So hmm.. I wonder if it's related to MSI stuff? >>> >> >>>> >> >> > You could try xen.git xen/stable-2.6.32.x branch instead and see if that makes a difference.. >>> >> >>>> >> >> > >>> >> >>>> >> >> > -- Pasi >>> >> >>>> >> >> > >>> >> >>>> >> >> >> >>> >> >>>> >> >> >> ---------- Forwarded message ---------- >>> >> >>>> >> >> >> From: chris <tknchris@gmail.com> >>> >> >>>> >> >> >> Date: Wed, May 12, 2010 at 5:28 PM >>> >> >>>> >> >> >> Subject: Xen4 / Intel DX58SO Mobo / VT-d not working >>> >> >>>> >> >> >> To: Xen-Users List <xen-users@lists.xensource.com> >>> >> >>>> >> >> >> >>> >> >>>> >> >> >> >>> >> >>>> >> >> >> Hello, >>> >> >>>> >> >> >> >>> >> >>>> >> >> >> I've previously been successful with Xen4 and VT-d on other systems. I >>> >> >>>> >> >> >> am having trouble getting VT-d passthrough working to a WinXP domain >>> >> >>>> >> >> >> with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is enabled in bios, >>> >> >>>> >> >> >> xm info shows hvm_directio capability, I have iommu=1 set, I have the >>> >> >>>> >> >> >> devices bound to pciback on dom0 cmdline, xm >>> >> >>>> >> >> >> pci-list-assignable-devices shows the devices as assignable. When I >>> >> >>>> >> >> >> attempt to start the VM I get the error: >>> >> >>>> >> >> >> >>> >> >>>> >> >> >> Error: Failed to assign device to IOMMU >>> >> >>>> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>> >> >>>> >> >> >> >>> >> >>>> >> >> >> Below is all the information I can think of that would be useful to >>> >> >>>> >> >> >> help debug it: >>> >> >>>> >> >> >> >>> >> >>>> >> >> >> BIOS VT-d Enabled: >>> >> >>>> >> >> >> http://i43.tinypic.com/nl3a5e.jpg >>> >> >>>> >> >> >> http://i42.tinypic.com/nqvlu1.jpg >>> >> >>>> >> >> >> >>> >> >>>> >> >> >> grub entry: >>> >> >>>> >> >> >> >>> >> >>>> >> >> >> title Xen 4.0.0 / Debian GNU/Linux, kernel 2.6.31.13 >>> >> >>>> >> >> >> root (hd0,0) >>> >> >>>> >> >> >> kernel /boot/xen-4.0.0.gz iommu=1 dom0_mem=256M >>> >> >>>> >> >> >> dom0_max_vcpus=1 dom0_vcpus_pin=true >>> >> >>>> >> >> >> module /boot/vmlinuz-2.6.31.13 root=/dev/md0 ro console=tty0 >>> >> >>>> >> >> >> xen-pciback.permissive >>> >> >>>> >> >> >> xen-pciback.hide=(02:00.0)(02:00.1)(02:00.2)(04:00.0)(04:00.1)(04:00.2)(07:00.0)(07:00.1)(07:00.2)(09:00.0)(09:00.1)(09:00.2) >>> >> >>>> >> >> >> module /boot/initrd.img-2.6.31.13 >>> >> >>>> >> >> >> >>> >> >>>> >> >> >> # xm pci-list-assignable-devices >>> >> >>>> >> >> >> 0000:09:00.0 >>> >> >>>> >> >> >> 0000:09:00.1 >>> >> >>>> >> >> >> 0000:09:00.2 >>> >> >>>> >> >> >> 0000:07:00.0 >>> >> >>>> >> >> >> 0000:07:00.1 >>> >> >>>> >> >> >> 0000:07:00.2 >>> >> >>>> >> >> >> 0000:04:00.0 >>> >> >>>> >> >> >> 0000:04:00.1 >>> >> >>>> >> >> >> 0000:04:00.2 >>> >> >>>> >> >> >> 0000:02:00.0 >>> >> >>>> >> >> >> 0000:02:00.1 >>> >> >>>> >> >> >> 0000:02:00.2 >>> >> >>>> >> >> >> >>> >> >>>> >> >> >> # xm info >>> >> >>>> >> >> >> host : test-box2 >>> >> >>>> >> >> >> release : 2.6.31.13 >>> >> >>>> >> >> >> version : #2 SMP Wed May 12 14:11:37 EDT 2010 >>> >> >>>> >> >> >> machine : x86_64 >>> >> >>>> >> >> >> nr_cpus : 8 >>> >> >>>> >> >> >> nr_nodes : 1 >>> >> >>>> >> >> >> cores_per_socket : 4 >>> >> >>>> >> >> >> threads_per_core : 2 >>> >> >>>> >> >> >> cpu_mhz : 2800 >>> >> >>>> >> >> >> hw_caps : >>> >> >>>> >> >> >> bfebfbff:28100800:00000000:00001b40:0098e3bd:00000000:00000001:00000000 >>> >> >>>> >> >> >> virt_caps : hvm hvm_directio >>> >> >>>> >> >> >> total_memory : 7950 >>> >> >>>> >> >> >> free_memory : 7812 >>> >> >>>> >> >> >> node_to_cpu : node0:0-7 >>> >> >>>> >> >> >> node_to_memory : node0:7812 >>> >> >>>> >> >> >> node_to_dma32_mem : node0:3249 >>> >> >>>> >> >> >> max_node_id : 0 >>> >> >>>> >> >> >> xen_major : 4 >>> >> >>>> >> >> >> xen_minor : 0 >>> >> >>>> >> >> >> xen_extra : .0 >>> >> >>>> >> >> >> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 >>> >> >>>> >> >> >> hvm-3.0-x86_32p hvm-3.0-x86_64 >>> >> >>>> >> >> >> xen_scheduler : credit >>> >> >>>> >> >> >> xen_pagesize : 4096 >>> >> >>>> >> >> >> platform_params : virt_start=0xffff800000000000 >>> >> >>>> >> >> >> xen_changeset : unavailable >>> >> >>>> >> >> >> xen_commandline : iommu=1 dom0_mem=256M dom0_max_vcpus=1 >>> >> >>>> >> >> >> dom0_vcpus_pin=true >>> >> >>>> >> >> >> cc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1) >>> >> >>>> >> >> >> cc_compile_by : root >>> >> >>>> >> >> >> cc_compile_domain : >>> >> >>>> >> >> >> cc_compile_date : Thu May 6 13:41:25 EDT 2010 >>> >> >>>> >> >> >> xend_config_format : 4 >>> >> >>>> >> >> >> >>> >> >>>> >> >> >> # xm create vm-five.cfg >>> >> >>>> >> >> >> Using config file "./vm-five.cfg". >>> >> >>>> >> >> >> Error: Failed to assign device to IOMMU >>> >> >>>> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>> >> >>>> >> >> >> >>> >> >>>> >> >> >> I feel like I'm missing something really obvious but I've been at it >>> >> >>>> >> >> >> for a while now and have run out of brain power. Anyone have any idea >>> >> >>>> >> >> >> what might be wrong? >>> >> >>>> >> >> >> >>> >> >>>> >> >> >> - chris >>> >> >>>> >> >> > >>> >> >>>> >> >> >> __ __ _ _ ___ ___ >>> >> >>>> >> >> >> \ \/ /___ _ __ | || | / _ \ / _ \ >>> >> >>>> >> >> >> \ // _ \ \047_ \ | || |_| | | | | | | >>> >> >>>> >> >> >> / \ __/ | | | |__ _| |_| | |_| | >>> >> >>>> >> >> >> /_/\_\___|_| |_| |_|(_)___(_)___/ >>> >> >>>> >> >> >> >>> >> >>>> >> >> >> (XEN) Xen version 4.0.0 (root@) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) Thu May 6 13:41:25 EDT 2010 >>> >> >>>> >> >> >> (XEN) Latest ChangeSet: unavailable >>> >> >>>> >> >> >> (XEN) Command line: iommu=verbose dom0_mem=256M dom0_max_vcpus=1 dom0_vcpus_pin=true >>> >> >>>> >> >> >> (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 - 000000000008f000 (usable) >>> >> >>>> >> >> >> (XEN) 000000000008f000 - 0000000000090000 (reserved) >>> >> >>>> >> >> >> (XEN) 0000000000090000 - 000000000009ec00 (usable) >>> >> >>>> >> >> >> (XEN) 000000000009ec00 - 00000000000a0000 (reserved) >>> >> >>>> >> >> >> (XEN) 00000000000e0000 - 0000000000100000 (reserved) >>> >> >>>> >> >> >> (XEN) 0000000000100000 - 00000000cf4bd000 (usable) >>> >> >>>> >> >> >> (XEN) 00000000cf4bd000 - 00000000cf4bf000 (reserved) >>> >> >>>> >> >> >> (XEN) 00000000cf4bf000 - 00000000cf4c2000 (usable) >>> >> >>>> >> >> >> (XEN) 00000000cf4c2000 - 00000000cf7bf000 (ACPI NVS) >>> >> >>>> >> >> >> (XEN) 00000000cf7bf000 - 00000000cf7df000 (usable) >>> >> >>>> >> >> >> (XEN) 00000000cf7df000 - 00000000cf7ff000 (ACPI data) >>> >> >>>> >> >> >> (XEN) 00000000cf7ff000 - 00000000cf800000 (usable) >>> >> >>>> >> >> >> (XEN) 00000000cf800000 - 00000000d0000000 (reserved) >>> >> >>>> >> >> >> (XEN) 00000000f8000000 - 00000000fd000000 (reserved) >>> >> >>>> >> >> >> (XEN) 00000000ffe00000 - 0000000100000000 (reserved) >>> >> >>>> >> >> >> (XEN) 0000000100000000 - 0000000230000000 (usable) >>> >> >>>> >> >> >> (XEN) ACPI: RSDP 000FE020, 0024 (r2 INTEL ) >>> >> >>>> >> >> >> (XEN) ACPI: XSDT CF7FE120, 0074 (r1 INTEL DX58SO 11F6 1000013) >>> >> >>>> >> >> >> (XEN) ACPI: FACP CF7FD000, 00F4 (r3 INTEL DX58SO 11F6 MSFT 100000D) >>> >> >>>> >> >> >> (XEN) ACPI Warning (tbfadt-0444): Optional field "Pm2ControlBlock" has zero address or length: 0000000000000450/0 [20070126] >>> >> >>>> >> >> >> (XEN) ACPI: DSDT CF7F8000, 4641 (r2 INTEL DX58SO 11F6 MSFT 100000D) >>> >> >>>> >> >> >> (XEN) ACPI: FACS CF728000, 0040 >>> >> >>>> >> >> >> (XEN) ACPI: APIC CF7F7000, 0138 (r2 INTEL DX58SO 11F6 MSFT 100000D) >>> >> >>>> >> >> >> (XEN) ACPI: WDDT CF7F6000, 0040 (r1 INTEL DX58SO 11F6 MSFT 100000D) >>> >> >>>> >> >> >> (XEN) ACPI: MCFG CF7F5000, 003C (r1 INTEL DX58SO 11F6 MSFT 100000D) >>> >> >>>> >> >> >> (XEN) ACPI: ASF! CF7F4000, 00AC (r32 INTEL DX58SO 11F6 MSFT 100000D) >>> >> >>>> >> >> >> (XEN) ACPI: HPET CF7F3000, 0038 (r1 INTEL DX58SO 11F6 MSFT 100000D) >>> >> >>>> >> >> >> (XEN) ACPI: SSDT CF7E2000, E134 (r1 INTEL SSDT PM 11F6 MSFT 100000D) >>> >> >>>> >> >> >> (XEN) ACPI: DMAR CF7DF000, 0140 (r1 INTEL DX58SO 11F6 MSFT 100000D) >>> >> >>>> >> >> >> (XEN) ACPI: WDTT CF7F1000, 020C (r2 INTEL DX58SO 11F6 MSFT 100000D) >>> >> >>>> >> >> >> (XEN) ACPI: ASPT CF7F2000, 0034 (r4 INTEL PerfTune 11F6 MSFT 100000D) >>> >> >>>> >> >> >> (XEN) System RAM: 7950MB (8140820kB) >>> >> >>>> >> >> >> (XEN) Domain heap initialised >>> >> >>>> >> >> >> (XEN) Processor #0 7:10 APIC version 21 >>> >> >>>> >> >> >> (XEN) Processor #2 7:10 APIC version 21 >>> >> >>>> >> >> >> (XEN) Processor #4 7:10 APIC version 21 >>> >> >>>> >> >> >> (XEN) Processor #6 7:10 APIC version 21 >>> >> >>>> >> >> >> (XEN) Processor #1 7:10 APIC version 21 >>> >> >>>> >> >> >> (XEN) Processor #3 7:10 APIC version 21 >>> >> >>>> >> >> >> (XEN) Processor #5 7:10 APIC version 21 >>> >> >>>> >> >> >> (XEN) Processor #7 7:10 APIC version 21 >>> >> >>>> >> >> >> (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 >>> >> >>>> >> >> >> (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:679: Host address width 39 >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = fe711000 >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1b.0 >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = fe710000 >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:340: IOAPIC: f0:1f.7 >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:411: flags: INCLUDE_ALL >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e9000 end_address e9fff >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.1 >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ea000 end_address eafff >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.2 >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr eb000 end_address ebfff >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.0 >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e6000 end_address e6fff >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.1 >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e7000 end_address e7fff >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.2 >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e8000 end_address e8fff >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 >>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ec000 end_address eefff >>> >> >>>> >> >> >> (XEN) Using scheduler: SMP Credit Scheduler (credit) >>> >> >>>> >> >> >> (XEN) Detected 2800.125 MHz processor. >>> >> >>>> >> >> >> (XEN) Initing memory sharing. >>> >> >>>> >> >> >> (XEN) VMX: Supported advanced features: >>> >> >>>> >> >> >> (XEN) - APIC MMIO access virtualisation >>> >> >>>> >> >> >> (XEN) - APIC TPR shadow >>> >> >>>> >> >> >> (XEN) - Extended Page Tables (EPT) >>> >> >>>> >> >> >> (XEN) - Virtual-Processor Identifiers (VPID) >>> >> >>>> >> >> >> (XEN) - Virtual NMI >>> >> >>>> >> >> >> (XEN) - MSR direct-access bitmap >>> >> >>>> >> >> >> (XEN) HVM: ASIDs enabled. >>> >> >>>> >> >> >> (XEN) HVM: VMX enabled >>> >> >>>> >> >> >> (XEN) HVM: Hardware Assisted Paging detected. >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = fe711000 iommu->reg = ffff82c3fff57000 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c9008010e60262 ecap = f0207a >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = fe710000 iommu->reg = ffff82c3fff56000 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c90780106f0462 ecap = f020fa >>> >> >>>> >> >> >> (XEN) Intel VT-d Snoop Control not supported. >>> >> >>>> >> >> >> (XEN) Intel VT-d DMA Passthrough not supported. >>> >> >>>> >> >> >> (XEN) Intel VT-d Queued Invalidation supported. >>> >> >>>> >> >> >> (XEN) Intel VT-d Interrupt Remapping supported. >>> >> >>>> >> >> >> (XEN) I/O virtualisation enabled >>> >> >>>> >> >> >> (XEN) I/O virtualisation for PV guests disabled >>> >> >>>> >> >> >> (XEN) Total of 8 processors activated. >>> >> >>>> >> >> >> (XEN) ENABLING IO-APIC IRQs >>> >> >>>> >> >> >> (XEN) -> Using new ACK method >>> >> >>>> >> >> >> (XEN) TSC is reliable, synchronization unnecessary >>> >> >>>> >> >> >> (XEN) Platform timer is 14.318MHz HPET >>> >> >>>> >> >> >> (XEN) Allocated console ring of 16 KiB. >>> >> >>>> >> >> >> (XEN) Brought up 8 CPUs >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:0.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.1 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.1 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.2 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:14.3 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:19.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.1 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.2 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.7 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:1b.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.1 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.2 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.7 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.2 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.3 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.5 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.1 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.2 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.1 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.2 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 5:0.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.1 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.2 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.1 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.2 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = a:0.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.1 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.2 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.3 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.4 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.5 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.6 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.7 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.1 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.1 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.1 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.4 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.1 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.2 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.3 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.1 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.2 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.3 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.0 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.1 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.2 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.3 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = ffff82c3fff57000 >>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = ffff82c3fff56000 >>> >> >>>> >> >> >> (XEN) *** LOADING DOMAIN 0 *** >>> >> >>>> >> >> >> (XEN) Xen kernel: 64-bit, lsb, compat32 >>> >> >>>> >> >> >> (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x26ae000 >>> >> >>>> >> >> >> (XEN) PHYSICAL MEMORY ARRANGEMENT: >>> >> >>>> >> >> >> (XEN) Dom0 alloc.: 0000000210000000->0000000220000000 >>> >> >>>> >> >> >> (XEN) VIRTUAL MEMORY ARRANGEMENT: >>> >> >>>> >> >> >> (XEN) Loaded kernel: ffffffff81000000->ffffffff826ae000 >>> >> >>>> >> >> >> (XEN) Init. ramdisk: ffffffff826ae000->ffffffff8f4de600 >>> >> >>>> >> >> >> (XEN) Phys-Mach map: ffffffff8f4df000->ffffffff8f55f000 >>> >> >>>> >> >> >> (XEN) Start info: ffffffff8f55f000->ffffffff8f55f4b4 >>> >> >>>> >> >> >> (XEN) Page tables: ffffffff8f560000->ffffffff8f5df000 >>> >> >>>> >> >> >> (XEN) Boot stack: ffffffff8f5df000->ffffffff8f5e0000 >>> >> >>>> >> >> >> (XEN) TOTAL: ffffffff80000000->ffffffff8f800000 >>> >> >>>> >> >> >> (XEN) ENTRY ADDRESS: ffffffff81a10860 >>> >> >>>> >> >> >> (XEN) Dom0 has maximum 1 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 \047CTRL-a\047 three times to switch input to Xen) >>> >> >>>> >> >> >> (XEN) Freed 164kB init memory. >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 pirq=0 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=2, irq=0 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=000009f0 pirq=0 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 3 already mapped >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 4 already mapped >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 5 already mapped >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 6 already mapped >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 7 already mapped >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 8 already mapped >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 9 already mapped >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 10 already mapped >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 11 already mapped >>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 12 already mapped >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000009f0 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 pirq=0 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=23, irq=23 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a929 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a929 pirq=23 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 pirq=16 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 pirq=16 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 >>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >> >>>> >> >> > >>> >> >>>> >> >> >> _______________________________________________ >>> >> >>>> >> >> >> Xen-users mailing list >>> >> >>>> >> >> >> Xen-users@lists.xensource.com >>> >> >>>> >> >> >> http://lists.xensource.com/xen-users >>> >> >>>> >> >> > >>> >> >>>> >> > >>> >> >>>> > >>> >> >>> >>> >> >> >>> >> > >>> > >> -- Best regards, Sander mailto:linux@eikelenboom.it ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: Re: [Xen-users] RE: Xen4 / Intel DX58SO Mobo / VT-d not working 2010-05-14 21:25 ` Re: [Xen-users] " Sander Eikelenboom @ 2010-05-14 21:26 ` chris 2010-05-14 21:34 ` Pasi Kärkkäinen 0 siblings, 1 reply; 32+ messages in thread From: chris @ 2010-05-14 21:26 UTC (permalink / raw) To: Sander Eikelenboom; +Cc: Xen-Devel List, Xen-Users List My guests are HVM so thats not really possible. Yes the machine with 3.4.2 has a hardware IOMMU. - chris On Fri, May 14, 2010 at 5:25 PM, Sander Eikelenboom <linux@eikelenboom.it> wrote: > Hello chris, > > But does the other machine have an IOMMU on 3.4.2 ? > I passthrough a few USB controllers my self, but the machine doesn't have a hardware IOMMU, > so it uses the SWIOTLB changed by Konrad to work with Xen and let the DMA of the USB controllers work. > It's working on xen-4.0.1-testing, xen-next pvops kernel from a few weeks ago, various domU kernel. > One domU kernel is a 2.6.33 from Konrad's tree, with patched and backported xhci support from 2.6.34. > > So perhaps you could try with the IOMMU off, see if it makes a difference, and would point the problem to the IOMMU more specifically. > Oh yes, what pci backend mode have you choosen in your dom0 kernel config ? > You have 3 options, virtual, passthrough or slot. > I allways tend to use passthrough, don't know it it makes a big difference though, but at least all functions get registered under the same device id in the guest. > > > > -- > > Sander > > > > Friday, May 14, 2010, 9:46:01 PM, you wrote: > >> I added a pci sound card and interestingly that works. I'm digging >> around for another pci-e device to try to identify if its all pci-e or >> only this device. Strange this is that I have a few other machines >> with this same usb controller which is working on 3.4.2. > >> *scratches head* > >> - chris > >> On Fri, May 14, 2010 at 3:21 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>> On Fri, May 14, 2010 at 03:18:02PM -0400, chris wrote: >>>> It is a multifunction device, a pci-e usb controller, so I assumed all >>>> them had to be passed through. I just changed it to only 02:00.0 and >>>> same thing >>>> >>>> test-box2:~# cat /etc/xen/vm-five.cfg | grep pci >>>> pci = ['02:00.0'] >>>> test-box2:~# xm create /etc/xen/vm-five.cfg >>>> Using config file "/etc/xen/vm-five.cfg". >>>> Error: Failed to assign device to IOMMU >>>> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>>> >>> >>> Hmm.. weird. >>> >>> Two things to try: >>> >>> 1) Try passthru some other device (which is just a single pci id) >>> 2) Try passthru that pci-e usb controller to Linux PV guest and see if that works >>> >>> -- Pasi >>> >>>> >>>> On Fri, May 14, 2010 at 3:11 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>>> > On Fri, May 14, 2010 at 03:05:49PM -0400, chris wrote: >>>> >> Pasi, >>>> >> >>>> >> Tried latest stable/2.6.32.x per your advice, no change. Anyone on >>>> >> xen-devel that can help me troubleshoot further? Everything looks >>>> >> right, can't figure out why vt-d is not working but it must be some >>>> >> kind of bug :( >>>> >> >>>> > >>>> > Did you try the suggestion said earlier.. try to just passthru the first pci device? >>>> > >>>> > -- Pasi >>>> > >>>> >> test-box2:~# uname -a >>>> >> Linux test-box2 2.6.32.12 #1 SMP Fri May 14 13:40:05 EDT 2010 x86_64 GNU/Linux >>>> >> >>>> >> test-box2:~# xm info | grep virt_caps >>>> >> virt_caps : hvm hvm_directio >>>> >> >>>> >> test-box2:~# xm pci-list-assignable-devices >>>> >> 0000:02:00.0 >>>> >> 0000:02:00.1 >>>> >> 0000:02:00.2 >>>> >> >>>> >> test-box2:~# xm create /etc/xen/vm-five.cfg >>>> >> Using config file "/etc/xen/vm-five.cfg". >>>> >> Error: Failed to assign device to IOMMU >>>> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>>> >> >>>> >> test-box2:~# cat /etc/xen/vm-five.cfg | grep -v '#' >>>> >> kernel = '/usr/lib/xen/boot/hvmloader' >>>> >> builder = 'hvm' >>>> >> memory = '1792' >>>> >> device_model='/usr/lib/xen/bin/qemu-dm' >>>> >> disk = [ 'phy:/dev/storage/vm-five,ioemu:hda,w', >>>> >> 'phy:/dev/sr0,ioemu:hdc:cdrom,r' >>>> >> ] >>>> >> name = 'vm-five' >>>> >> vif = ['type=ioemu, bridge=eth0, mac=00:16:3D:37:A1:42'] >>>> >> boot='dc' >>>> >> cpus='0-1' >>>> >> vcpus=2 >>>> >> acpi=1 >>>> >> ahci=1 >>>> >> vnc=1 >>>> >> sdl=0 >>>> >> timer_mode=1 >>>> >> usb=1 >>>> >> usbdevice='tablet' >>>> >> localtime=1 >>>> >> pci = ['02:00.0','02:00.1','02:00.2'] >>>> >> >>>> >> On Thu, May 13, 2010 at 2:28 PM, chris <tknchris@gmail.com> wrote: >>>> >> > Forwarding to xen-devel. Can't seem to get VT-d working with xen4 from >>>> >> > tarball on xen.org 2.6.31.13 pv_ops dom0. On pasi's advice I tried >>>> >> > switching to stable/2.6.32.x branch for dom0 and that doesnt even >>>> >> > build. Did something change recently thats breaking compilation? >>>> >> > >>>> >> > Attached is xen dmesg with iommu=verbose loglvl=all guest_loglvl=all, >>>> >> > and dom0 dmesg from 2.6.31.x >>>> >> > >>>> >> > Any ideas on why VT-d is not working on this board? Initialization >>>> >> > looks good, xen reports hvm_directio capability, everything says VT-d >>>> >> > should work until domain is created. >>>> >> > >>>> >> > Any ideas why stable/2.6.32.x wont build? >>>> >> > >>>> >> > - chris >>>> >> > >>>> >> > On Thu, May 13, 2010 at 2:07 PM, chris <tknchris@gmail.com> wrote: >>>> >> >> I redid it with oldconfig which I didn't think would help and same >>>> >> >> thing. I guess this tree is broken? Can someone else try and see if >>>> >> >> they can build it? Ugh, whata day :) >>>> >> >> >>>> >> >> On Thu, May 13, 2010 at 1:58 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>>> >> >>> On Thu, May 13, 2010 at 01:55:25PM -0400, chris wrote: >>>> >> >>>> I used the default config on the wiki which you created. Steps I took were: >>>> >> >>>> >>>> >> >>>> # make clean distclean >>>> >> >>>> # wget -O .config >>>> >> >>>> "http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.10-pvops-dom0-xen-stable-x86_64" >>>> >> >>> >>>> >> >>> You should do "make oldconfig" at this point. >>>> >> >>> >>>> >> >>>> # make -j8 bzImage >>>> >> >>>> (blah blah) >>>> >> >>>> LD vmlinux.o >>>> >> >>>> MODPOST vmlinux.o >>>> >> >>>> WARNING: modpost: Found 7 section mismatch(es). >>>> >> >>>> To see full details build your kernel with: >>>> >> >>>> 'make CONFIG_DEBUG_SECTION_MISMATCH=y' >>>> >> >>>> GEN .version >>>> >> >>>> CHK include/linux/compile.h >>>> >> >>>> UPD include/linux/compile.h >>>> >> >>>> CC init/version.o >>>> >> >>>> LD init/built-in.o >>>> >> >>>> LD .tmp_vmlinux1 >>>> >> >>>> drivers/built-in.o: In function `do_hvm_suspend': >>>> >> >>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: undefined reference >>>> >> >>>> to `xenbus_suspend' >>>> >> >>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: undefined reference >>>> >> >>>> to `xenbus_resume' >>>> >> >>>> make: *** [.tmp_vmlinux1] Error 1 >>>> >> >>>> >>>> >> >>> >>>> >> >>> Hmm.. weird. I wonder if something has changed recently or what's going on in here.. >>>> >> >>> >>>> >> >>> -- Pasi >>>> >> >>> >>>> >> >>>> >>>> >> >>>> On Thu, May 13, 2010 at 11:47 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>>> >> >>>> > On Thu, May 13, 2010 at 11:33:57AM -0400, chris wrote: >>>> >> >>>> >> Successfully grabbed the sources and failed to build: >>>> >> >>>> >> >>>> >> >>>> >> LD .tmp_vmlinux1 >>>> >> >>>> >> drivers/built-in.o: In function `do_hvm_suspend': >>>> >> >>>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: undefined reference >>>> >> >>>> >> to `xenbus_suspend' >>>> >> >>>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: undefined reference >>>> >> >>>> >> to `xenbus_resume' >>>> >> >>>> >> make: *** [.tmp_vmlinux1] Error 1 >>>> >> >>>> >> >>>> >> >>>> >> :( >>>> >> >>>> >> >>>> >> >>>> > >>>> >> >>>> > Try the example .config files provided on the wiki page. >>>> >> >>>> > >>>> >> >>>> > -- Pasi >>>> >> >>>> > >>>> >> >>>> >> On Thu, May 13, 2010 at 10:14 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>>> >> >>>> >> > On Thu, May 13, 2010 at 10:12:56AM -0400, chris wrote: >>>> >> >>>> >> >> Pasi, >>>> >> >>>> >> >> >>>> >> >>>> >> >> How do I pull those kernel sources you referenced? I see it mentioned >>>> >> >>>> >> >> on http://wiki.xensource.com/xenwiki/XenParavirtOps but no details on >>>> >> >>>> >> >> how to retrieve it. >>>> >> >>>> >> >> >>>> >> >>>> >> > >>>> >> >>>> >> > The instructions are there if you read it carefully.. >>>> >> >>>> >> > There's the topic of how to switch branches. >>>> >> >>>> >> > >>>> >> >>>> >> > -- Pasi >>>> >> >>>> >> > >>>> >> >>>> >> >> - chris >>>> >> >>>> >> >> >>>> >> >>>> >> >> On Thu, May 13, 2010 at 8:29 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>>> >> >>>> >> >> > On Wed, May 12, 2010 at 08:41:34PM -0400, chris wrote: >>>> >> >>>> >> >> >> When reading the vtdhowto I noticed the ability to set iommu=verbose. >>>> >> >>>> >> >> >> Here is that output, I don't know if it helps at all to figure out >>>> >> >>>> >> >> >> what is wrong. >>>> >> >>>> >> >> >> >>>> >> >>>> >> >> > >>>> >> >>>> >> >> > That seems to be OK: >>>> >> >>>> >> >> > >>>> >> >>>> >> >> > (XEN) I/O virtualisation enabled >>>> >> >>>> >> >> > (XEN) I/O virtualisation for PV guests disabled >>>> >> >>>> >> >> > >>>> >> >>>> >> >> > So hmm.. I wonder if it's related to MSI stuff? >>>> >> >>>> >> >> > You could try xen.git xen/stable-2.6.32.x branch instead and see if that makes a difference.. >>>> >> >>>> >> >> > >>>> >> >>>> >> >> > -- Pasi >>>> >> >>>> >> >> > >>>> >> >>>> >> >> >> >>>> >> >>>> >> >> >> ---------- Forwarded message ---------- >>>> >> >>>> >> >> >> From: chris <tknchris@gmail.com> >>>> >> >>>> >> >> >> Date: Wed, May 12, 2010 at 5:28 PM >>>> >> >>>> >> >> >> Subject: Xen4 / Intel DX58SO Mobo / VT-d not working >>>> >> >>>> >> >> >> To: Xen-Users List <xen-users@lists.xensource.com> >>>> >> >>>> >> >> >> >>>> >> >>>> >> >> >> >>>> >> >>>> >> >> >> Hello, >>>> >> >>>> >> >> >> >>>> >> >>>> >> >> >> I've previously been successful with Xen4 and VT-d on other systems. I >>>> >> >>>> >> >> >> am having trouble getting VT-d passthrough working to a WinXP domain >>>> >> >>>> >> >> >> with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is enabled in bios, >>>> >> >>>> >> >> >> xm info shows hvm_directio capability, I have iommu=1 set, I have the >>>> >> >>>> >> >> >> devices bound to pciback on dom0 cmdline, xm >>>> >> >>>> >> >> >> pci-list-assignable-devices shows the devices as assignable. When I >>>> >> >>>> >> >> >> attempt to start the VM I get the error: >>>> >> >>>> >> >> >> >>>> >> >>>> >> >> >> Error: Failed to assign device to IOMMU >>>> >> >>>> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>>> >> >>>> >> >> >> >>>> >> >>>> >> >> >> Below is all the information I can think of that would be useful to >>>> >> >>>> >> >> >> help debug it: >>>> >> >>>> >> >> >> >>>> >> >>>> >> >> >> BIOS VT-d Enabled: >>>> >> >>>> >> >> >> http://i43.tinypic.com/nl3a5e.jpg >>>> >> >>>> >> >> >> http://i42.tinypic.com/nqvlu1.jpg >>>> >> >>>> >> >> >> >>>> >> >>>> >> >> >> grub entry: >>>> >> >>>> >> >> >> >>>> >> >>>> >> >> >> title Xen 4.0.0 / Debian GNU/Linux, kernel 2.6.31.13 >>>> >> >>>> >> >> >> root (hd0,0) >>>> >> >>>> >> >> >> kernel /boot/xen-4.0.0.gz iommu=1 dom0_mem=256M >>>> >> >>>> >> >> >> dom0_max_vcpus=1 dom0_vcpus_pin=true >>>> >> >>>> >> >> >> module /boot/vmlinuz-2.6.31.13 root=/dev/md0 ro console=tty0 >>>> >> >>>> >> >> >> xen-pciback.permissive >>>> >> >>>> >> >> >> xen-pciback.hide=(02:00.0)(02:00.1)(02:00.2)(04:00.0)(04:00.1)(04:00.2)(07:00.0)(07:00.1)(07:00.2)(09:00.0)(09:00.1)(09:00.2) >>>> >> >>>> >> >> >> module /boot/initrd.img-2.6.31.13 >>>> >> >>>> >> >> >> >>>> >> >>>> >> >> >> # xm pci-list-assignable-devices >>>> >> >>>> >> >> >> 0000:09:00.0 >>>> >> >>>> >> >> >> 0000:09:00.1 >>>> >> >>>> >> >> >> 0000:09:00.2 >>>> >> >>>> >> >> >> 0000:07:00.0 >>>> >> >>>> >> >> >> 0000:07:00.1 >>>> >> >>>> >> >> >> 0000:07:00.2 >>>> >> >>>> >> >> >> 0000:04:00.0 >>>> >> >>>> >> >> >> 0000:04:00.1 >>>> >> >>>> >> >> >> 0000:04:00.2 >>>> >> >>>> >> >> >> 0000:02:00.0 >>>> >> >>>> >> >> >> 0000:02:00.1 >>>> >> >>>> >> >> >> 0000:02:00.2 >>>> >> >>>> >> >> >> >>>> >> >>>> >> >> >> # xm info >>>> >> >>>> >> >> >> host : test-box2 >>>> >> >>>> >> >> >> release : 2.6.31.13 >>>> >> >>>> >> >> >> version : #2 SMP Wed May 12 14:11:37 EDT 2010 >>>> >> >>>> >> >> >> machine : x86_64 >>>> >> >>>> >> >> >> nr_cpus : 8 >>>> >> >>>> >> >> >> nr_nodes : 1 >>>> >> >>>> >> >> >> cores_per_socket : 4 >>>> >> >>>> >> >> >> threads_per_core : 2 >>>> >> >>>> >> >> >> cpu_mhz : 2800 >>>> >> >>>> >> >> >> hw_caps : >>>> >> >>>> >> >> >> bfebfbff:28100800:00000000:00001b40:0098e3bd:00000000:00000001:00000000 >>>> >> >>>> >> >> >> virt_caps : hvm hvm_directio >>>> >> >>>> >> >> >> total_memory : 7950 >>>> >> >>>> >> >> >> free_memory : 7812 >>>> >> >>>> >> >> >> node_to_cpu : node0:0-7 >>>> >> >>>> >> >> >> node_to_memory : node0:7812 >>>> >> >>>> >> >> >> node_to_dma32_mem : node0:3249 >>>> >> >>>> >> >> >> max_node_id : 0 >>>> >> >>>> >> >> >> xen_major : 4 >>>> >> >>>> >> >> >> xen_minor : 0 >>>> >> >>>> >> >> >> xen_extra : .0 >>>> >> >>>> >> >> >> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 >>>> >> >>>> >> >> >> hvm-3.0-x86_32p hvm-3.0-x86_64 >>>> >> >>>> >> >> >> xen_scheduler : credit >>>> >> >>>> >> >> >> xen_pagesize : 4096 >>>> >> >>>> >> >> >> platform_params : virt_start=0xffff800000000000 >>>> >> >>>> >> >> >> xen_changeset : unavailable >>>> >> >>>> >> >> >> xen_commandline : iommu=1 dom0_mem=256M dom0_max_vcpus=1 >>>> >> >>>> >> >> >> dom0_vcpus_pin=true >>>> >> >>>> >> >> >> cc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1) >>>> >> >>>> >> >> >> cc_compile_by : root >>>> >> >>>> >> >> >> cc_compile_domain : >>>> >> >>>> >> >> >> cc_compile_date : Thu May 6 13:41:25 EDT 2010 >>>> >> >>>> >> >> >> xend_config_format : 4 >>>> >> >>>> >> >> >> >>>> >> >>>> >> >> >> # xm create vm-five.cfg >>>> >> >>>> >> >> >> Using config file "./vm-five.cfg". >>>> >> >>>> >> >> >> Error: Failed to assign device to IOMMU >>>> >> >>>> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>>> >> >>>> >> >> >> >>>> >> >>>> >> >> >> I feel like I'm missing something really obvious but I've been at it >>>> >> >>>> >> >> >> for a while now and have run out of brain power. Anyone have any idea >>>> >> >>>> >> >> >> what might be wrong? >>>> >> >>>> >> >> >> >>>> >> >>>> >> >> >> - chris >>>> >> >>>> >> >> > >>>> >> >>>> >> >> >> __ __ _ _ ___ ___ >>>> >> >>>> >> >> >> \ \/ /___ _ __ | || | / _ \ / _ \ >>>> >> >>>> >> >> >> \ // _ \ \047_ \ | || |_| | | | | | | >>>> >> >>>> >> >> >> / \ __/ | | | |__ _| |_| | |_| | >>>> >> >>>> >> >> >> /_/\_\___|_| |_| |_|(_)___(_)___/ >>>> >> >>>> >> >> >> >>>> >> >>>> >> >> >> (XEN) Xen version 4.0.0 (root@) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) Thu May 6 13:41:25 EDT 2010 >>>> >> >>>> >> >> >> (XEN) Latest ChangeSet: unavailable >>>> >> >>>> >> >> >> (XEN) Command line: iommu=verbose dom0_mem=256M dom0_max_vcpus=1 dom0_vcpus_pin=true >>>> >> >>>> >> >> >> (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 - 000000000008f000 (usable) >>>> >> >>>> >> >> >> (XEN) 000000000008f000 - 0000000000090000 (reserved) >>>> >> >>>> >> >> >> (XEN) 0000000000090000 - 000000000009ec00 (usable) >>>> >> >>>> >> >> >> (XEN) 000000000009ec00 - 00000000000a0000 (reserved) >>>> >> >>>> >> >> >> (XEN) 00000000000e0000 - 0000000000100000 (reserved) >>>> >> >>>> >> >> >> (XEN) 0000000000100000 - 00000000cf4bd000 (usable) >>>> >> >>>> >> >> >> (XEN) 00000000cf4bd000 - 00000000cf4bf000 (reserved) >>>> >> >>>> >> >> >> (XEN) 00000000cf4bf000 - 00000000cf4c2000 (usable) >>>> >> >>>> >> >> >> (XEN) 00000000cf4c2000 - 00000000cf7bf000 (ACPI NVS) >>>> >> >>>> >> >> >> (XEN) 00000000cf7bf000 - 00000000cf7df000 (usable) >>>> >> >>>> >> >> >> (XEN) 00000000cf7df000 - 00000000cf7ff000 (ACPI data) >>>> >> >>>> >> >> >> (XEN) 00000000cf7ff000 - 00000000cf800000 (usable) >>>> >> >>>> >> >> >> (XEN) 00000000cf800000 - 00000000d0000000 (reserved) >>>> >> >>>> >> >> >> (XEN) 00000000f8000000 - 00000000fd000000 (reserved) >>>> >> >>>> >> >> >> (XEN) 00000000ffe00000 - 0000000100000000 (reserved) >>>> >> >>>> >> >> >> (XEN) 0000000100000000 - 0000000230000000 (usable) >>>> >> >>>> >> >> >> (XEN) ACPI: RSDP 000FE020, 0024 (r2 INTEL ) >>>> >> >>>> >> >> >> (XEN) ACPI: XSDT CF7FE120, 0074 (r1 INTEL DX58SO 11F6 1000013) >>>> >> >>>> >> >> >> (XEN) ACPI: FACP CF7FD000, 00F4 (r3 INTEL DX58SO 11F6 MSFT 100000D) >>>> >> >>>> >> >> >> (XEN) ACPI Warning (tbfadt-0444): Optional field "Pm2ControlBlock" has zero address or length: 0000000000000450/0 [20070126] >>>> >> >>>> >> >> >> (XEN) ACPI: DSDT CF7F8000, 4641 (r2 INTEL DX58SO 11F6 MSFT 100000D) >>>> >> >>>> >> >> >> (XEN) ACPI: FACS CF728000, 0040 >>>> >> >>>> >> >> >> (XEN) ACPI: APIC CF7F7000, 0138 (r2 INTEL DX58SO 11F6 MSFT 100000D) >>>> >> >>>> >> >> >> (XEN) ACPI: WDDT CF7F6000, 0040 (r1 INTEL DX58SO 11F6 MSFT 100000D) >>>> >> >>>> >> >> >> (XEN) ACPI: MCFG CF7F5000, 003C (r1 INTEL DX58SO 11F6 MSFT 100000D) >>>> >> >>>> >> >> >> (XEN) ACPI: ASF! CF7F4000, 00AC (r32 INTEL DX58SO 11F6 MSFT 100000D) >>>> >> >>>> >> >> >> (XEN) ACPI: HPET CF7F3000, 0038 (r1 INTEL DX58SO 11F6 MSFT 100000D) >>>> >> >>>> >> >> >> (XEN) ACPI: SSDT CF7E2000, E134 (r1 INTEL SSDT PM 11F6 MSFT 100000D) >>>> >> >>>> >> >> >> (XEN) ACPI: DMAR CF7DF000, 0140 (r1 INTEL DX58SO 11F6 MSFT 100000D) >>>> >> >>>> >> >> >> (XEN) ACPI: WDTT CF7F1000, 020C (r2 INTEL DX58SO 11F6 MSFT 100000D) >>>> >> >>>> >> >> >> (XEN) ACPI: ASPT CF7F2000, 0034 (r4 INTEL PerfTune 11F6 MSFT 100000D) >>>> >> >>>> >> >> >> (XEN) System RAM: 7950MB (8140820kB) >>>> >> >>>> >> >> >> (XEN) Domain heap initialised >>>> >> >>>> >> >> >> (XEN) Processor #0 7:10 APIC version 21 >>>> >> >>>> >> >> >> (XEN) Processor #2 7:10 APIC version 21 >>>> >> >>>> >> >> >> (XEN) Processor #4 7:10 APIC version 21 >>>> >> >>>> >> >> >> (XEN) Processor #6 7:10 APIC version 21 >>>> >> >>>> >> >> >> (XEN) Processor #1 7:10 APIC version 21 >>>> >> >>>> >> >> >> (XEN) Processor #3 7:10 APIC version 21 >>>> >> >>>> >> >> >> (XEN) Processor #5 7:10 APIC version 21 >>>> >> >>>> >> >> >> (XEN) Processor #7 7:10 APIC version 21 >>>> >> >>>> >> >> >> (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 >>>> >> >>>> >> >> >> (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:679: Host address width 39 >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = fe711000 >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1b.0 >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = fe710000 >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:340: IOAPIC: f0:1f.7 >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:411: flags: INCLUDE_ALL >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e9000 end_address e9fff >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.1 >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ea000 end_address eafff >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.2 >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr eb000 end_address ebfff >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.0 >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e6000 end_address e6fff >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.1 >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e7000 end_address e7fff >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.2 >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e8000 end_address e8fff >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ec000 end_address eefff >>>> >> >>>> >> >> >> (XEN) Using scheduler: SMP Credit Scheduler (credit) >>>> >> >>>> >> >> >> (XEN) Detected 2800.125 MHz processor. >>>> >> >>>> >> >> >> (XEN) Initing memory sharing. >>>> >> >>>> >> >> >> (XEN) VMX: Supported advanced features: >>>> >> >>>> >> >> >> (XEN) - APIC MMIO access virtualisation >>>> >> >>>> >> >> >> (XEN) - APIC TPR shadow >>>> >> >>>> >> >> >> (XEN) - Extended Page Tables (EPT) >>>> >> >>>> >> >> >> (XEN) - Virtual-Processor Identifiers (VPID) >>>> >> >>>> >> >> >> (XEN) - Virtual NMI >>>> >> >>>> >> >> >> (XEN) - MSR direct-access bitmap >>>> >> >>>> >> >> >> (XEN) HVM: ASIDs enabled. >>>> >> >>>> >> >> >> (XEN) HVM: VMX enabled >>>> >> >>>> >> >> >> (XEN) HVM: Hardware Assisted Paging detected. >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = fe711000 iommu->reg = ffff82c3fff57000 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c9008010e60262 ecap = f0207a >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = fe710000 iommu->reg = ffff82c3fff56000 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c90780106f0462 ecap = f020fa >>>> >> >>>> >> >> >> (XEN) Intel VT-d Snoop Control not supported. >>>> >> >>>> >> >> >> (XEN) Intel VT-d DMA Passthrough not supported. >>>> >> >>>> >> >> >> (XEN) Intel VT-d Queued Invalidation supported. >>>> >> >>>> >> >> >> (XEN) Intel VT-d Interrupt Remapping supported. >>>> >> >>>> >> >> >> (XEN) I/O virtualisation enabled >>>> >> >>>> >> >> >> (XEN) I/O virtualisation for PV guests disabled >>>> >> >>>> >> >> >> (XEN) Total of 8 processors activated. >>>> >> >>>> >> >> >> (XEN) ENABLING IO-APIC IRQs >>>> >> >>>> >> >> >> (XEN) -> Using new ACK method >>>> >> >>>> >> >> >> (XEN) TSC is reliable, synchronization unnecessary >>>> >> >>>> >> >> >> (XEN) Platform timer is 14.318MHz HPET >>>> >> >>>> >> >> >> (XEN) Allocated console ring of 16 KiB. >>>> >> >>>> >> >> >> (XEN) Brought up 8 CPUs >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:0.0 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.0 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.1 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.0 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.1 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.2 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:14.3 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:19.0 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.0 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.1 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.2 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.7 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:1b.0 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.0 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.1 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.2 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.7 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.0 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.2 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.3 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.5 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.0 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.1 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.2 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.0 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.1 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.2 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 5:0.0 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.0 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.1 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.2 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.0 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.1 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.2 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = a:0.0 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.0 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.1 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.2 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.3 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.4 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.5 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.6 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.7 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.0 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.1 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.0 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.1 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.0 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.1 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.4 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.0 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.1 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.2 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.3 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.0 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.1 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.2 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.3 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.0 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.1 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.2 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.3 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = ffff82c3fff57000 >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = ffff82c3fff56000 >>>> >> >>>> >> >> >> (XEN) *** LOADING DOMAIN 0 *** >>>> >> >>>> >> >> >> (XEN) Xen kernel: 64-bit, lsb, compat32 >>>> >> >>>> >> >> >> (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x26ae000 >>>> >> >>>> >> >> >> (XEN) PHYSICAL MEMORY ARRANGEMENT: >>>> >> >>>> >> >> >> (XEN) Dom0 alloc.: 0000000210000000->0000000220000000 >>>> >> >>>> >> >> >> (XEN) VIRTUAL MEMORY ARRANGEMENT: >>>> >> >>>> >> >> >> (XEN) Loaded kernel: ffffffff81000000->ffffffff826ae000 >>>> >> >>>> >> >> >> (XEN) Init. ramdisk: ffffffff826ae000->ffffffff8f4de600 >>>> >> >>>> >> >> >> (XEN) Phys-Mach map: ffffffff8f4df000->ffffffff8f55f000 >>>> >> >>>> >> >> >> (XEN) Start info: ffffffff8f55f000->ffffffff8f55f4b4 >>>> >> >>>> >> >> >> (XEN) Page tables: ffffffff8f560000->ffffffff8f5df000 >>>> >> >>>> >> >> >> (XEN) Boot stack: ffffffff8f5df000->ffffffff8f5e0000 >>>> >> >>>> >> >> >> (XEN) TOTAL: ffffffff80000000->ffffffff8f800000 >>>> >> >>>> >> >> >> (XEN) ENTRY ADDRESS: ffffffff81a10860 >>>> >> >>>> >> >> >> (XEN) Dom0 has maximum 1 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 \047CTRL-a\047 three times to switch input to Xen) >>>> >> >>>> >> >> >> (XEN) Freed 164kB init memory. >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 pirq=0 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=2, irq=0 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=000009f0 pirq=0 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 3 already mapped >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 4 already mapped >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 5 already mapped >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 6 already mapped >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 7 already mapped >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 8 already mapped >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 9 already mapped >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 10 already mapped >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 11 already mapped >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 12 already mapped >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000009f0 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 pirq=0 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=23, irq=23 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a929 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a929 pirq=23 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 pirq=16 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 pirq=16 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>>> >> >>>> >> >> > >>>> >> >>>> >> >> >> _______________________________________________ >>>> >> >>>> >> >> >> Xen-users mailing list >>>> >> >>>> >> >> >> Xen-users@lists.xensource.com >>>> >> >>>> >> >> >> http://lists.xensource.com/xen-users >>>> >> >>>> >> >> > >>>> >> >>>> >> > >>>> >> >>>> > >>>> >> >>> >>>> >> >> >>>> >> > >>>> > >>> > > > > > > -- > Best regards, > Sander mailto:linux@eikelenboom.it > > ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: Re: [Xen-users] RE: Xen4 / Intel DX58SO Mobo / VT-d not working 2010-05-14 21:26 ` chris @ 2010-05-14 21:34 ` Pasi Kärkkäinen 2010-05-14 21:57 ` chris 0 siblings, 1 reply; 32+ messages in thread From: Pasi Kärkkäinen @ 2010-05-14 21:34 UTC (permalink / raw) To: chris; +Cc: Sander Eikelenboom, Xen-Devel List, Xen-Users List On Fri, May 14, 2010 at 05:26:22PM -0400, chris wrote: > My guests are HVM so thats not really possible. Yes the machine with > 3.4.2 has a hardware IOMMU. > What if you install Xen 4.0 to the other machine? Or Xen 3.4.2 to this machine? Does it work then? Trying to figure out if it's hardware/BIOS related, or Xen version related. -- Pasi > - chris > > On Fri, May 14, 2010 at 5:25 PM, Sander Eikelenboom > <linux@eikelenboom.it> wrote: > > Hello chris, > > > > But does the other machine have an IOMMU on 3.4.2 ? > > I passthrough a few USB controllers my self, but the machine doesn't have a hardware IOMMU, > > so it uses the SWIOTLB changed by Konrad to work with Xen and let the DMA of the USB controllers work. > > It's working on xen-4.0.1-testing, xen-next pvops kernel from a few weeks ago, various domU kernel. > > One domU kernel is a 2.6.33 from Konrad's tree, with patched and backported xhci support from 2.6.34. > > > > So perhaps you could try with the IOMMU off, see if it makes a difference, and would point the problem to the IOMMU more specifically. > > Oh yes, what pci backend mode have you choosen in your dom0 kernel config ? > > You have 3 options, virtual, passthrough or slot. > > I allways tend to use passthrough, don't know it it makes a big difference though, but at least all functions get registered under the same device id in the guest. > > > > > > > > -- > > > > Sander > > > > > > > > Friday, May 14, 2010, 9:46:01 PM, you wrote: > > > >> I added a pci sound card and interestingly that works. I'm digging > >> around for another pci-e device to try to identify if its all pci-e or > >> only this device. Strange this is that I have a few other machines > >> with this same usb controller which is working on 3.4.2. > > > >> *scratches head* > > > >> - chris > > > >> On Fri, May 14, 2010 at 3:21 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > >>> On Fri, May 14, 2010 at 03:18:02PM -0400, chris wrote: > >>>> It is a multifunction device, a pci-e usb controller, so I assumed all > >>>> them had to be passed through. I just changed it to only 02:00.0 and > >>>> same thing > >>>> > >>>> test-box2:~# cat /etc/xen/vm-five.cfg | grep pci > >>>> pci = ['02:00.0'] > >>>> test-box2:~# xm create /etc/xen/vm-five.cfg > >>>> Using config file "/etc/xen/vm-five.cfg". > >>>> Error: Failed to assign device to IOMMU > >>>> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) > >>>> > >>> > >>> Hmm.. weird. > >>> > >>> Two things to try: > >>> > >>> 1) Try passthru some other device (which is just a single pci id) > >>> 2) Try passthru that pci-e usb controller to Linux PV guest and see if that works > >>> > >>> -- Pasi > >>> > >>>> > >>>> On Fri, May 14, 2010 at 3:11 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > >>>> > On Fri, May 14, 2010 at 03:05:49PM -0400, chris wrote: > >>>> >> Pasi, > >>>> >> > >>>> >> Tried latest stable/2.6.32.x per your advice, no change. Anyone on > >>>> >> xen-devel that can help me troubleshoot further? Everything looks > >>>> >> right, can't figure out why vt-d is not working but it must be some > >>>> >> kind of bug :( > >>>> >> > >>>> > > >>>> > Did you try the suggestion said earlier.. try to just passthru the first pci device? > >>>> > > >>>> > -- Pasi > >>>> > > >>>> >> test-box2:~# uname -a > >>>> >> Linux test-box2 2.6.32.12 #1 SMP Fri May 14 13:40:05 EDT 2010 x86_64 GNU/Linux > >>>> >> > >>>> >> test-box2:~# xm info | grep virt_caps > >>>> >> virt_caps : hvm hvm_directio > >>>> >> > >>>> >> test-box2:~# xm pci-list-assignable-devices > >>>> >> 0000:02:00.0 > >>>> >> 0000:02:00.1 > >>>> >> 0000:02:00.2 > >>>> >> > >>>> >> test-box2:~# xm create /etc/xen/vm-five.cfg > >>>> >> Using config file "/etc/xen/vm-five.cfg". > >>>> >> Error: Failed to assign device to IOMMU > >>>> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) > >>>> >> > >>>> >> test-box2:~# cat /etc/xen/vm-five.cfg | grep -v '#' > >>>> >> kernel = '/usr/lib/xen/boot/hvmloader' > >>>> >> builder = 'hvm' > >>>> >> memory = '1792' > >>>> >> device_model='/usr/lib/xen/bin/qemu-dm' > >>>> >> disk = [ 'phy:/dev/storage/vm-five,ioemu:hda,w', > >>>> >> 'phy:/dev/sr0,ioemu:hdc:cdrom,r' > >>>> >> ] > >>>> >> name = 'vm-five' > >>>> >> vif = ['type=ioemu, bridge=eth0, mac=00:16:3D:37:A1:42'] > >>>> >> boot='dc' > >>>> >> cpus='0-1' > >>>> >> vcpus=2 > >>>> >> acpi=1 > >>>> >> ahci=1 > >>>> >> vnc=1 > >>>> >> sdl=0 > >>>> >> timer_mode=1 > >>>> >> usb=1 > >>>> >> usbdevice='tablet' > >>>> >> localtime=1 > >>>> >> pci = ['02:00.0','02:00.1','02:00.2'] > >>>> >> > >>>> >> On Thu, May 13, 2010 at 2:28 PM, chris <tknchris@gmail.com> wrote: > >>>> >> > Forwarding to xen-devel. Can't seem to get VT-d working with xen4 from > >>>> >> > tarball on xen.org 2.6.31.13 pv_ops dom0. On pasi's advice I tried > >>>> >> > switching to stable/2.6.32.x branch for dom0 and that doesnt even > >>>> >> > build. Did something change recently thats breaking compilation? > >>>> >> > > >>>> >> > Attached is xen dmesg with iommu=verbose loglvl=all guest_loglvl=all, > >>>> >> > and dom0 dmesg from 2.6.31.x > >>>> >> > > >>>> >> > Any ideas on why VT-d is not working on this board? Initialization > >>>> >> > looks good, xen reports hvm_directio capability, everything says VT-d > >>>> >> > should work until domain is created. > >>>> >> > > >>>> >> > Any ideas why stable/2.6.32.x wont build? > >>>> >> > > >>>> >> > - chris > >>>> >> > > >>>> >> > On Thu, May 13, 2010 at 2:07 PM, chris <tknchris@gmail.com> wrote: > >>>> >> >> I redid it with oldconfig which I didn't think would help and same > >>>> >> >> thing. I guess this tree is broken? Can someone else try and see if > >>>> >> >> they can build it? Ugh, whata day :) > >>>> >> >> > >>>> >> >> On Thu, May 13, 2010 at 1:58 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > >>>> >> >>> On Thu, May 13, 2010 at 01:55:25PM -0400, chris wrote: > >>>> >> >>>> I used the default config on the wiki which you created. Steps I took were: > >>>> >> >>>> > >>>> >> >>>> # make clean distclean > >>>> >> >>>> # wget -O .config > >>>> >> >>>> "http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.10-pvops-dom0-xen-stable-x86_64" > >>>> >> >>> > >>>> >> >>> You should do "make oldconfig" at this point. > >>>> >> >>> > >>>> >> >>>> # make -j8 bzImage > >>>> >> >>>> (blah blah) > >>>> >> >>>> LD vmlinux.o > >>>> >> >>>> MODPOST vmlinux.o > >>>> >> >>>> WARNING: modpost: Found 7 section mismatch(es). > >>>> >> >>>> To see full details build your kernel with: > >>>> >> >>>> 'make CONFIG_DEBUG_SECTION_MISMATCH=y' > >>>> >> >>>> GEN .version > >>>> >> >>>> CHK include/linux/compile.h > >>>> >> >>>> UPD include/linux/compile.h > >>>> >> >>>> CC init/version.o > >>>> >> >>>> LD init/built-in.o > >>>> >> >>>> LD .tmp_vmlinux1 > >>>> >> >>>> drivers/built-in.o: In function `do_hvm_suspend': > >>>> >> >>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: undefined reference > >>>> >> >>>> to `xenbus_suspend' > >>>> >> >>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: undefined reference > >>>> >> >>>> to `xenbus_resume' > >>>> >> >>>> make: *** [.tmp_vmlinux1] Error 1 > >>>> >> >>>> > >>>> >> >>> > >>>> >> >>> Hmm.. weird. I wonder if something has changed recently or what's going on in here.. > >>>> >> >>> > >>>> >> >>> -- Pasi > >>>> >> >>> > >>>> >> >>>> > >>>> >> >>>> On Thu, May 13, 2010 at 11:47 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > >>>> >> >>>> > On Thu, May 13, 2010 at 11:33:57AM -0400, chris wrote: > >>>> >> >>>> >> Successfully grabbed the sources and failed to build: > >>>> >> >>>> >> > >>>> >> >>>> >> LD .tmp_vmlinux1 > >>>> >> >>>> >> drivers/built-in.o: In function `do_hvm_suspend': > >>>> >> >>>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: undefined reference > >>>> >> >>>> >> to `xenbus_suspend' > >>>> >> >>>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: undefined reference > >>>> >> >>>> >> to `xenbus_resume' > >>>> >> >>>> >> make: *** [.tmp_vmlinux1] Error 1 > >>>> >> >>>> >> > >>>> >> >>>> >> :( > >>>> >> >>>> >> > >>>> >> >>>> > > >>>> >> >>>> > Try the example .config files provided on the wiki page. > >>>> >> >>>> > > >>>> >> >>>> > -- Pasi > >>>> >> >>>> > > >>>> >> >>>> >> On Thu, May 13, 2010 at 10:14 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > >>>> >> >>>> >> > On Thu, May 13, 2010 at 10:12:56AM -0400, chris wrote: > >>>> >> >>>> >> >> Pasi, > >>>> >> >>>> >> >> > >>>> >> >>>> >> >> How do I pull those kernel sources you referenced? I see it mentioned > >>>> >> >>>> >> >> on http://wiki.xensource.com/xenwiki/XenParavirtOps but no details on > >>>> >> >>>> >> >> how to retrieve it. > >>>> >> >>>> >> >> > >>>> >> >>>> >> > > >>>> >> >>>> >> > The instructions are there if you read it carefully.. > >>>> >> >>>> >> > There's the topic of how to switch branches. > >>>> >> >>>> >> > > >>>> >> >>>> >> > -- Pasi > >>>> >> >>>> >> > > >>>> >> >>>> >> >> - chris > >>>> >> >>>> >> >> > >>>> >> >>>> >> >> On Thu, May 13, 2010 at 8:29 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > >>>> >> >>>> >> >> > On Wed, May 12, 2010 at 08:41:34PM -0400, chris wrote: > >>>> >> >>>> >> >> >> When reading the vtdhowto I noticed the ability to set iommu=verbose. > >>>> >> >>>> >> >> >> Here is that output, I don't know if it helps at all to figure out > >>>> >> >>>> >> >> >> what is wrong. > >>>> >> >>>> >> >> >> > >>>> >> >>>> >> >> > > >>>> >> >>>> >> >> > That seems to be OK: > >>>> >> >>>> >> >> > > >>>> >> >>>> >> >> > (XEN) I/O virtualisation enabled > >>>> >> >>>> >> >> > (XEN) I/O virtualisation for PV guests disabled > >>>> >> >>>> >> >> > > >>>> >> >>>> >> >> > So hmm.. I wonder if it's related to MSI stuff? > >>>> >> >>>> >> >> > You could try xen.git xen/stable-2.6.32.x branch instead and see if that makes a difference.. > >>>> >> >>>> >> >> > > >>>> >> >>>> >> >> > -- Pasi > >>>> >> >>>> >> >> > > >>>> >> >>>> >> >> >> > >>>> >> >>>> >> >> >> ---------- Forwarded message ---------- > >>>> >> >>>> >> >> >> From: chris <tknchris@gmail.com> > >>>> >> >>>> >> >> >> Date: Wed, May 12, 2010 at 5:28 PM > >>>> >> >>>> >> >> >> Subject: Xen4 / Intel DX58SO Mobo / VT-d not working > >>>> >> >>>> >> >> >> To: Xen-Users List <xen-users@lists.xensource.com> > >>>> >> >>>> >> >> >> > >>>> >> >>>> >> >> >> > >>>> >> >>>> >> >> >> Hello, > >>>> >> >>>> >> >> >> > >>>> >> >>>> >> >> >> I've previously been successful with Xen4 and VT-d on other systems. I > >>>> >> >>>> >> >> >> am having trouble getting VT-d passthrough working to a WinXP domain > >>>> >> >>>> >> >> >> with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is enabled in bios, > >>>> >> >>>> >> >> >> xm info shows hvm_directio capability, I have iommu=1 set, I have the > >>>> >> >>>> >> >> >> devices bound to pciback on dom0 cmdline, xm > >>>> >> >>>> >> >> >> pci-list-assignable-devices shows the devices as assignable. When I > >>>> >> >>>> >> >> >> attempt to start the VM I get the error: > >>>> >> >>>> >> >> >> > >>>> >> >>>> >> >> >> Error: Failed to assign device to IOMMU > >>>> >> >>>> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) > >>>> >> >>>> >> >> >> > >>>> >> >>>> >> >> >> Below is all the information I can think of that would be useful to > >>>> >> >>>> >> >> >> help debug it: > >>>> >> >>>> >> >> >> > >>>> >> >>>> >> >> >> BIOS VT-d Enabled: > >>>> >> >>>> >> >> >> http://i43.tinypic.com/nl3a5e.jpg > >>>> >> >>>> >> >> >> http://i42.tinypic.com/nqvlu1.jpg > >>>> >> >>>> >> >> >> > >>>> >> >>>> >> >> >> grub entry: > >>>> >> >>>> >> >> >> > >>>> >> >>>> >> >> >> title Xen 4.0.0 / Debian GNU/Linux, kernel 2.6.31.13 > >>>> >> >>>> >> >> >> root (hd0,0) > >>>> >> >>>> >> >> >> kernel /boot/xen-4.0.0.gz iommu=1 dom0_mem=256M > >>>> >> >>>> >> >> >> dom0_max_vcpus=1 dom0_vcpus_pin=true > >>>> >> >>>> >> >> >> module /boot/vmlinuz-2.6.31.13 root=/dev/md0 ro console=tty0 > >>>> >> >>>> >> >> >> xen-pciback.permissive > >>>> >> >>>> >> >> >> xen-pciback.hide=(02:00.0)(02:00.1)(02:00.2)(04:00.0)(04:00.1)(04:00.2)(07:00.0)(07:00.1)(07:00.2)(09:00.0)(09:00.1)(09:00.2) > >>>> >> >>>> >> >> >> module /boot/initrd.img-2.6.31.13 > >>>> >> >>>> >> >> >> > >>>> >> >>>> >> >> >> # xm pci-list-assignable-devices > >>>> >> >>>> >> >> >> 0000:09:00.0 > >>>> >> >>>> >> >> >> 0000:09:00.1 > >>>> >> >>>> >> >> >> 0000:09:00.2 > >>>> >> >>>> >> >> >> 0000:07:00.0 > >>>> >> >>>> >> >> >> 0000:07:00.1 > >>>> >> >>>> >> >> >> 0000:07:00.2 > >>>> >> >>>> >> >> >> 0000:04:00.0 > >>>> >> >>>> >> >> >> 0000:04:00.1 > >>>> >> >>>> >> >> >> 0000:04:00.2 > >>>> >> >>>> >> >> >> 0000:02:00.0 > >>>> >> >>>> >> >> >> 0000:02:00.1 > >>>> >> >>>> >> >> >> 0000:02:00.2 > >>>> >> >>>> >> >> >> > >>>> >> >>>> >> >> >> # xm info > >>>> >> >>>> >> >> >> host : test-box2 > >>>> >> >>>> >> >> >> release : 2.6.31.13 > >>>> >> >>>> >> >> >> version : #2 SMP Wed May 12 14:11:37 EDT 2010 > >>>> >> >>>> >> >> >> machine : x86_64 > >>>> >> >>>> >> >> >> nr_cpus : 8 > >>>> >> >>>> >> >> >> nr_nodes : 1 > >>>> >> >>>> >> >> >> cores_per_socket : 4 > >>>> >> >>>> >> >> >> threads_per_core : 2 > >>>> >> >>>> >> >> >> cpu_mhz : 2800 > >>>> >> >>>> >> >> >> hw_caps : > >>>> >> >>>> >> >> >> bfebfbff:28100800:00000000:00001b40:0098e3bd:00000000:00000001:00000000 > >>>> >> >>>> >> >> >> virt_caps : hvm hvm_directio > >>>> >> >>>> >> >> >> total_memory : 7950 > >>>> >> >>>> >> >> >> free_memory : 7812 > >>>> >> >>>> >> >> >> node_to_cpu : node0:0-7 > >>>> >> >>>> >> >> >> node_to_memory : node0:7812 > >>>> >> >>>> >> >> >> node_to_dma32_mem : node0:3249 > >>>> >> >>>> >> >> >> max_node_id : 0 > >>>> >> >>>> >> >> >> xen_major : 4 > >>>> >> >>>> >> >> >> xen_minor : 0 > >>>> >> >>>> >> >> >> xen_extra : .0 > >>>> >> >>>> >> >> >> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > >>>> >> >>>> >> >> >> hvm-3.0-x86_32p hvm-3.0-x86_64 > >>>> >> >>>> >> >> >> xen_scheduler : credit > >>>> >> >>>> >> >> >> xen_pagesize : 4096 > >>>> >> >>>> >> >> >> platform_params : virt_start=0xffff800000000000 > >>>> >> >>>> >> >> >> xen_changeset : unavailable > >>>> >> >>>> >> >> >> xen_commandline : iommu=1 dom0_mem=256M dom0_max_vcpus=1 > >>>> >> >>>> >> >> >> dom0_vcpus_pin=true > >>>> >> >>>> >> >> >> cc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1) > >>>> >> >>>> >> >> >> cc_compile_by : root > >>>> >> >>>> >> >> >> cc_compile_domain : > >>>> >> >>>> >> >> >> cc_compile_date : Thu May 6 13:41:25 EDT 2010 > >>>> >> >>>> >> >> >> xend_config_format : 4 > >>>> >> >>>> >> >> >> > >>>> >> >>>> >> >> >> # xm create vm-five.cfg > >>>> >> >>>> >> >> >> Using config file "./vm-five.cfg". > >>>> >> >>>> >> >> >> Error: Failed to assign device to IOMMU > >>>> >> >>>> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) > >>>> >> >>>> >> >> >> > >>>> >> >>>> >> >> >> I feel like I'm missing something really obvious but I've been at it > >>>> >> >>>> >> >> >> for a while now and have run out of brain power. Anyone have any idea > >>>> >> >>>> >> >> >> what might be wrong? > >>>> >> >>>> >> >> >> > >>>> >> >>>> >> >> >> - chris > >>>> >> >>>> >> >> > > >>>> >> >>>> >> >> >> __ __ _ _ ___ ___ > >>>> >> >>>> >> >> >> \ \/ /___ _ __ | || | / _ \ / _ \ > >>>> >> >>>> >> >> >> \ // _ \ \047_ \ | || |_| | | | | | | > >>>> >> >>>> >> >> >> / \ __/ | | | |__ _| |_| | |_| | > >>>> >> >>>> >> >> >> /_/\_\___|_| |_| |_|(_)___(_)___/ > >>>> >> >>>> >> >> >> > >>>> >> >>>> >> >> >> (XEN) Xen version 4.0.0 (root@) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) Thu May 6 13:41:25 EDT 2010 > >>>> >> >>>> >> >> >> (XEN) Latest ChangeSet: unavailable > >>>> >> >>>> >> >> >> (XEN) Command line: iommu=verbose dom0_mem=256M dom0_max_vcpus=1 dom0_vcpus_pin=true > >>>> >> >>>> >> >> >> (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 - 000000000008f000 (usable) > >>>> >> >>>> >> >> >> (XEN) 000000000008f000 - 0000000000090000 (reserved) > >>>> >> >>>> >> >> >> (XEN) 0000000000090000 - 000000000009ec00 (usable) > >>>> >> >>>> >> >> >> (XEN) 000000000009ec00 - 00000000000a0000 (reserved) > >>>> >> >>>> >> >> >> (XEN) 00000000000e0000 - 0000000000100000 (reserved) > >>>> >> >>>> >> >> >> (XEN) 0000000000100000 - 00000000cf4bd000 (usable) > >>>> >> >>>> >> >> >> (XEN) 00000000cf4bd000 - 00000000cf4bf000 (reserved) > >>>> >> >>>> >> >> >> (XEN) 00000000cf4bf000 - 00000000cf4c2000 (usable) > >>>> >> >>>> >> >> >> (XEN) 00000000cf4c2000 - 00000000cf7bf000 (ACPI NVS) > >>>> >> >>>> >> >> >> (XEN) 00000000cf7bf000 - 00000000cf7df000 (usable) > >>>> >> >>>> >> >> >> (XEN) 00000000cf7df000 - 00000000cf7ff000 (ACPI data) > >>>> >> >>>> >> >> >> (XEN) 00000000cf7ff000 - 00000000cf800000 (usable) > >>>> >> >>>> >> >> >> (XEN) 00000000cf800000 - 00000000d0000000 (reserved) > >>>> >> >>>> >> >> >> (XEN) 00000000f8000000 - 00000000fd000000 (reserved) > >>>> >> >>>> >> >> >> (XEN) 00000000ffe00000 - 0000000100000000 (reserved) > >>>> >> >>>> >> >> >> (XEN) 0000000100000000 - 0000000230000000 (usable) > >>>> >> >>>> >> >> >> (XEN) ACPI: RSDP 000FE020, 0024 (r2 INTEL ) > >>>> >> >>>> >> >> >> (XEN) ACPI: XSDT CF7FE120, 0074 (r1 INTEL DX58SO 11F6 1000013) > >>>> >> >>>> >> >> >> (XEN) ACPI: FACP CF7FD000, 00F4 (r3 INTEL DX58SO 11F6 MSFT 100000D) > >>>> >> >>>> >> >> >> (XEN) ACPI Warning (tbfadt-0444): Optional field "Pm2ControlBlock" has zero address or length: 0000000000000450/0 [20070126] > >>>> >> >>>> >> >> >> (XEN) ACPI: DSDT CF7F8000, 4641 (r2 INTEL DX58SO 11F6 MSFT 100000D) > >>>> >> >>>> >> >> >> (XEN) ACPI: FACS CF728000, 0040 > >>>> >> >>>> >> >> >> (XEN) ACPI: APIC CF7F7000, 0138 (r2 INTEL DX58SO 11F6 MSFT 100000D) > >>>> >> >>>> >> >> >> (XEN) ACPI: WDDT CF7F6000, 0040 (r1 INTEL DX58SO 11F6 MSFT 100000D) > >>>> >> >>>> >> >> >> (XEN) ACPI: MCFG CF7F5000, 003C (r1 INTEL DX58SO 11F6 MSFT 100000D) > >>>> >> >>>> >> >> >> (XEN) ACPI: ASF! CF7F4000, 00AC (r32 INTEL DX58SO 11F6 MSFT 100000D) > >>>> >> >>>> >> >> >> (XEN) ACPI: HPET CF7F3000, 0038 (r1 INTEL DX58SO 11F6 MSFT 100000D) > >>>> >> >>>> >> >> >> (XEN) ACPI: SSDT CF7E2000, E134 (r1 INTEL SSDT PM 11F6 MSFT 100000D) > >>>> >> >>>> >> >> >> (XEN) ACPI: DMAR CF7DF000, 0140 (r1 INTEL DX58SO 11F6 MSFT 100000D) > >>>> >> >>>> >> >> >> (XEN) ACPI: WDTT CF7F1000, 020C (r2 INTEL DX58SO 11F6 MSFT 100000D) > >>>> >> >>>> >> >> >> (XEN) ACPI: ASPT CF7F2000, 0034 (r4 INTEL PerfTune 11F6 MSFT 100000D) > >>>> >> >>>> >> >> >> (XEN) System RAM: 7950MB (8140820kB) > >>>> >> >>>> >> >> >> (XEN) Domain heap initialised > >>>> >> >>>> >> >> >> (XEN) Processor #0 7:10 APIC version 21 > >>>> >> >>>> >> >> >> (XEN) Processor #2 7:10 APIC version 21 > >>>> >> >>>> >> >> >> (XEN) Processor #4 7:10 APIC version 21 > >>>> >> >>>> >> >> >> (XEN) Processor #6 7:10 APIC version 21 > >>>> >> >>>> >> >> >> (XEN) Processor #1 7:10 APIC version 21 > >>>> >> >>>> >> >> >> (XEN) Processor #3 7:10 APIC version 21 > >>>> >> >>>> >> >> >> (XEN) Processor #5 7:10 APIC version 21 > >>>> >> >>>> >> >> >> (XEN) Processor #7 7:10 APIC version 21 > >>>> >> >>>> >> >> >> (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 > >>>> >> >>>> >> >> >> (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:679: Host address width 39 > >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: > >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = fe711000 > >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1b.0 > >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: > >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = fe710000 > >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:340: IOAPIC: f0:1f.7 > >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:411: flags: INCLUDE_ALL > >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 > >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e9000 end_address e9fff > >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.1 > >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ea000 end_address eafff > >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.2 > >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr eb000 end_address ebfff > >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.0 > >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e6000 end_address e6fff > >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.1 > >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e7000 end_address e7fff > >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.2 > >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e8000 end_address e8fff > >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 > >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ec000 end_address eefff > >>>> >> >>>> >> >> >> (XEN) Using scheduler: SMP Credit Scheduler (credit) > >>>> >> >>>> >> >> >> (XEN) Detected 2800.125 MHz processor. > >>>> >> >>>> >> >> >> (XEN) Initing memory sharing. > >>>> >> >>>> >> >> >> (XEN) VMX: Supported advanced features: > >>>> >> >>>> >> >> >> (XEN) - APIC MMIO access virtualisation > >>>> >> >>>> >> >> >> (XEN) - APIC TPR shadow > >>>> >> >>>> >> >> >> (XEN) - Extended Page Tables (EPT) > >>>> >> >>>> >> >> >> (XEN) - Virtual-Processor Identifiers (VPID) > >>>> >> >>>> >> >> >> (XEN) - Virtual NMI > >>>> >> >>>> >> >> >> (XEN) - MSR direct-access bitmap > >>>> >> >>>> >> >> >> (XEN) HVM: ASIDs enabled. > >>>> >> >>>> >> >> >> (XEN) HVM: VMX enabled > >>>> >> >>>> >> >> >> (XEN) HVM: Hardware Assisted Paging detected. > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = fe711000 iommu->reg = ffff82c3fff57000 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c9008010e60262 ecap = f0207a > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = fe710000 iommu->reg = ffff82c3fff56000 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c90780106f0462 ecap = f020fa > >>>> >> >>>> >> >> >> (XEN) Intel VT-d Snoop Control not supported. > >>>> >> >>>> >> >> >> (XEN) Intel VT-d DMA Passthrough not supported. > >>>> >> >>>> >> >> >> (XEN) Intel VT-d Queued Invalidation supported. > >>>> >> >>>> >> >> >> (XEN) Intel VT-d Interrupt Remapping supported. > >>>> >> >>>> >> >> >> (XEN) I/O virtualisation enabled > >>>> >> >>>> >> >> >> (XEN) I/O virtualisation for PV guests disabled > >>>> >> >>>> >> >> >> (XEN) Total of 8 processors activated. > >>>> >> >>>> >> >> >> (XEN) ENABLING IO-APIC IRQs > >>>> >> >>>> >> >> >> (XEN) -> Using new ACK method > >>>> >> >>>> >> >> >> (XEN) TSC is reliable, synchronization unnecessary > >>>> >> >>>> >> >> >> (XEN) Platform timer is 14.318MHz HPET > >>>> >> >>>> >> >> >> (XEN) Allocated console ring of 16 KiB. > >>>> >> >>>> >> >> >> (XEN) Brought up 8 CPUs > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:0.0 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.0 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.1 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.0 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.1 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.2 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:14.3 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:19.0 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.0 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.1 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.2 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.7 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:1b.0 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.0 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.1 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.2 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.7 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.0 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.2 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.3 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.5 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.0 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.1 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.2 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.0 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.1 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.2 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 5:0.0 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.0 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.1 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.2 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.0 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.1 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.2 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = a:0.0 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.0 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.1 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.2 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.3 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.4 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.5 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.6 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.7 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.0 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.1 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.0 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.1 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.0 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.1 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.4 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.0 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.1 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.2 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.3 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.0 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.1 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.2 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.3 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.0 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.1 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.2 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.3 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = ffff82c3fff57000 > >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = ffff82c3fff56000 > >>>> >> >>>> >> >> >> (XEN) *** LOADING DOMAIN 0 *** > >>>> >> >>>> >> >> >> (XEN) Xen kernel: 64-bit, lsb, compat32 > >>>> >> >>>> >> >> >> (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x26ae000 > >>>> >> >>>> >> >> >> (XEN) PHYSICAL MEMORY ARRANGEMENT: > >>>> >> >>>> >> >> >> (XEN) Dom0 alloc.: 0000000210000000->0000000220000000 > >>>> >> >>>> >> >> >> (XEN) VIRTUAL MEMORY ARRANGEMENT: > >>>> >> >>>> >> >> >> (XEN) Loaded kernel: ffffffff81000000->ffffffff826ae000 > >>>> >> >>>> >> >> >> (XEN) Init. ramdisk: ffffffff826ae000->ffffffff8f4de600 > >>>> >> >>>> >> >> >> (XEN) Phys-Mach map: ffffffff8f4df000->ffffffff8f55f000 > >>>> >> >>>> >> >> >> (XEN) Start info: ffffffff8f55f000->ffffffff8f55f4b4 > >>>> >> >>>> >> >> >> (XEN) Page tables: ffffffff8f560000->ffffffff8f5df000 > >>>> >> >>>> >> >> >> (XEN) Boot stack: ffffffff8f5df000->ffffffff8f5e0000 > >>>> >> >>>> >> >> >> (XEN) TOTAL: ffffffff80000000->ffffffff8f800000 > >>>> >> >>>> >> >> >> (XEN) ENTRY ADDRESS: ffffffff81a10860 > >>>> >> >>>> >> >> >> (XEN) Dom0 has maximum 1 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 \047CTRL-a\047 three times to switch input to Xen) > >>>> >> >>>> >> >> >> (XEN) Freed 164kB init memory. > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 pirq=0 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=2, irq=0 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=000009f0 pirq=0 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 3 already mapped > >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 4 already mapped > >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 5 already mapped > >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 6 already mapped > >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 7 already mapped > >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 8 already mapped > >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 9 already mapped > >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 10 already mapped > >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 11 already mapped > >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 12 already mapped > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000009f0 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 pirq=0 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=23, irq=23 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a929 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a929 pirq=23 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 pirq=16 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 pirq=16 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 > >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > >>>> >> >>>> >> >> > > >>>> >> >>>> >> >> >> _______________________________________________ > >>>> >> >>>> >> >> >> Xen-users mailing list > >>>> >> >>>> >> >> >> Xen-users@lists.xensource.com > >>>> >> >>>> >> >> >> http://lists.xensource.com/xen-users > >>>> >> >>>> >> >> > > >>>> >> >>>> >> > > >>>> >> >>>> > > >>>> >> >>> > >>>> >> >> > >>>> >> > > >>>> > > >>> > > > > > > > > > > > > -- > > Best regards, > > Sander mailto:linux@eikelenboom.it > > > > ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: Re: [Xen-users] RE: Xen4 / Intel DX58SO Mobo / VT-d not working 2010-05-14 21:34 ` Pasi Kärkkäinen @ 2010-05-14 21:57 ` chris 2010-05-15 6:56 ` Sander Eikelenboom 0 siblings, 1 reply; 32+ messages in thread From: chris @ 2010-05-14 21:57 UTC (permalink / raw) To: Pasi Kärkkäinen Cc: Sander Eikelenboom, Xen-Devel List, Xen-Users List I tried 3.4.2 with the same 2 dom0's and it doesnt even boot fully. One hangs completely and the other goes really really slooow. The working machine is in production so i cant try 4.0 :( - chris On Fri, May 14, 2010 at 5:34 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > On Fri, May 14, 2010 at 05:26:22PM -0400, chris wrote: >> My guests are HVM so thats not really possible. Yes the machine with >> 3.4.2 has a hardware IOMMU. >> > > What if you install Xen 4.0 to the other machine? > Or Xen 3.4.2 to this machine? > > Does it work then? > > Trying to figure out if it's hardware/BIOS related, > or Xen version related. > > -- Pasi > >> - chris >> >> On Fri, May 14, 2010 at 5:25 PM, Sander Eikelenboom >> <linux@eikelenboom.it> wrote: >> > Hello chris, >> > >> > But does the other machine have an IOMMU on 3.4.2 ? >> > I passthrough a few USB controllers my self, but the machine doesn't have a hardware IOMMU, >> > so it uses the SWIOTLB changed by Konrad to work with Xen and let the DMA of the USB controllers work. >> > It's working on xen-4.0.1-testing, xen-next pvops kernel from a few weeks ago, various domU kernel. >> > One domU kernel is a 2.6.33 from Konrad's tree, with patched and backported xhci support from 2.6.34. >> > >> > So perhaps you could try with the IOMMU off, see if it makes a difference, and would point the problem to the IOMMU more specifically. >> > Oh yes, what pci backend mode have you choosen in your dom0 kernel config ? >> > You have 3 options, virtual, passthrough or slot. >> > I allways tend to use passthrough, don't know it it makes a big difference though, but at least all functions get registered under the same device id in the guest. >> > >> > >> > >> > -- >> > >> > Sander >> > >> > >> > >> > Friday, May 14, 2010, 9:46:01 PM, you wrote: >> > >> >> I added a pci sound card and interestingly that works. I'm digging >> >> around for another pci-e device to try to identify if its all pci-e or >> >> only this device. Strange this is that I have a few other machines >> >> with this same usb controller which is working on 3.4.2. >> > >> >> *scratches head* >> > >> >> - chris >> > >> >> On Fri, May 14, 2010 at 3:21 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >> >>> On Fri, May 14, 2010 at 03:18:02PM -0400, chris wrote: >> >>>> It is a multifunction device, a pci-e usb controller, so I assumed all >> >>>> them had to be passed through. I just changed it to only 02:00.0 and >> >>>> same thing >> >>>> >> >>>> test-box2:~# cat /etc/xen/vm-five.cfg | grep pci >> >>>> pci = ['02:00.0'] >> >>>> test-box2:~# xm create /etc/xen/vm-five.cfg >> >>>> Using config file "/etc/xen/vm-five.cfg". >> >>>> Error: Failed to assign device to IOMMU >> >>>> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >> >>>> >> >>> >> >>> Hmm.. weird. >> >>> >> >>> Two things to try: >> >>> >> >>> 1) Try passthru some other device (which is just a single pci id) >> >>> 2) Try passthru that pci-e usb controller to Linux PV guest and see if that works >> >>> >> >>> -- Pasi >> >>> >> >>>> >> >>>> On Fri, May 14, 2010 at 3:11 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >> >>>> > On Fri, May 14, 2010 at 03:05:49PM -0400, chris wrote: >> >>>> >> Pasi, >> >>>> >> >> >>>> >> Tried latest stable/2.6.32.x per your advice, no change. Anyone on >> >>>> >> xen-devel that can help me troubleshoot further? Everything looks >> >>>> >> right, can't figure out why vt-d is not working but it must be some >> >>>> >> kind of bug :( >> >>>> >> >> >>>> > >> >>>> > Did you try the suggestion said earlier.. try to just passthru the first pci device? >> >>>> > >> >>>> > -- Pasi >> >>>> > >> >>>> >> test-box2:~# uname -a >> >>>> >> Linux test-box2 2.6.32.12 #1 SMP Fri May 14 13:40:05 EDT 2010 x86_64 GNU/Linux >> >>>> >> >> >>>> >> test-box2:~# xm info | grep virt_caps >> >>>> >> virt_caps : hvm hvm_directio >> >>>> >> >> >>>> >> test-box2:~# xm pci-list-assignable-devices >> >>>> >> 0000:02:00.0 >> >>>> >> 0000:02:00.1 >> >>>> >> 0000:02:00.2 >> >>>> >> >> >>>> >> test-box2:~# xm create /etc/xen/vm-five.cfg >> >>>> >> Using config file "/etc/xen/vm-five.cfg". >> >>>> >> Error: Failed to assign device to IOMMU >> >>>> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >> >>>> >> >> >>>> >> test-box2:~# cat /etc/xen/vm-five.cfg | grep -v '#' >> >>>> >> kernel = '/usr/lib/xen/boot/hvmloader' >> >>>> >> builder = 'hvm' >> >>>> >> memory = '1792' >> >>>> >> device_model='/usr/lib/xen/bin/qemu-dm' >> >>>> >> disk = [ 'phy:/dev/storage/vm-five,ioemu:hda,w', >> >>>> >> 'phy:/dev/sr0,ioemu:hdc:cdrom,r' >> >>>> >> ] >> >>>> >> name = 'vm-five' >> >>>> >> vif = ['type=ioemu, bridge=eth0, mac=00:16:3D:37:A1:42'] >> >>>> >> boot='dc' >> >>>> >> cpus='0-1' >> >>>> >> vcpus=2 >> >>>> >> acpi=1 >> >>>> >> ahci=1 >> >>>> >> vnc=1 >> >>>> >> sdl=0 >> >>>> >> timer_mode=1 >> >>>> >> usb=1 >> >>>> >> usbdevice='tablet' >> >>>> >> localtime=1 >> >>>> >> pci = ['02:00.0','02:00.1','02:00.2'] >> >>>> >> >> >>>> >> On Thu, May 13, 2010 at 2:28 PM, chris <tknchris@gmail.com> wrote: >> >>>> >> > Forwarding to xen-devel. Can't seem to get VT-d working with xen4 from >> >>>> >> > tarball on xen.org 2.6.31.13 pv_ops dom0. On pasi's advice I tried >> >>>> >> > switching to stable/2.6.32.x branch for dom0 and that doesnt even >> >>>> >> > build. Did something change recently thats breaking compilation? >> >>>> >> > >> >>>> >> > Attached is xen dmesg with iommu=verbose loglvl=all guest_loglvl=all, >> >>>> >> > and dom0 dmesg from 2.6.31.x >> >>>> >> > >> >>>> >> > Any ideas on why VT-d is not working on this board? Initialization >> >>>> >> > looks good, xen reports hvm_directio capability, everything says VT-d >> >>>> >> > should work until domain is created. >> >>>> >> > >> >>>> >> > Any ideas why stable/2.6.32.x wont build? >> >>>> >> > >> >>>> >> > - chris >> >>>> >> > >> >>>> >> > On Thu, May 13, 2010 at 2:07 PM, chris <tknchris@gmail.com> wrote: >> >>>> >> >> I redid it with oldconfig which I didn't think would help and same >> >>>> >> >> thing. I guess this tree is broken? Can someone else try and see if >> >>>> >> >> they can build it? Ugh, whata day :) >> >>>> >> >> >> >>>> >> >> On Thu, May 13, 2010 at 1:58 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >> >>>> >> >>> On Thu, May 13, 2010 at 01:55:25PM -0400, chris wrote: >> >>>> >> >>>> I used the default config on the wiki which you created. Steps I took were: >> >>>> >> >>>> >> >>>> >> >>>> # make clean distclean >> >>>> >> >>>> # wget -O .config >> >>>> >> >>>> "http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.10-pvops-dom0-xen-stable-x86_64" >> >>>> >> >>> >> >>>> >> >>> You should do "make oldconfig" at this point. >> >>>> >> >>> >> >>>> >> >>>> # make -j8 bzImage >> >>>> >> >>>> (blah blah) >> >>>> >> >>>> LD vmlinux.o >> >>>> >> >>>> MODPOST vmlinux.o >> >>>> >> >>>> WARNING: modpost: Found 7 section mismatch(es). >> >>>> >> >>>> To see full details build your kernel with: >> >>>> >> >>>> 'make CONFIG_DEBUG_SECTION_MISMATCH=y' >> >>>> >> >>>> GEN .version >> >>>> >> >>>> CHK include/linux/compile.h >> >>>> >> >>>> UPD include/linux/compile.h >> >>>> >> >>>> CC init/version.o >> >>>> >> >>>> LD init/built-in.o >> >>>> >> >>>> LD .tmp_vmlinux1 >> >>>> >> >>>> drivers/built-in.o: In function `do_hvm_suspend': >> >>>> >> >>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: undefined reference >> >>>> >> >>>> to `xenbus_suspend' >> >>>> >> >>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: undefined reference >> >>>> >> >>>> to `xenbus_resume' >> >>>> >> >>>> make: *** [.tmp_vmlinux1] Error 1 >> >>>> >> >>>> >> >>>> >> >>> >> >>>> >> >>> Hmm.. weird. I wonder if something has changed recently or what's going on in here.. >> >>>> >> >>> >> >>>> >> >>> -- Pasi >> >>>> >> >>> >> >>>> >> >>>> >> >>>> >> >>>> On Thu, May 13, 2010 at 11:47 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >> >>>> >> >>>> > On Thu, May 13, 2010 at 11:33:57AM -0400, chris wrote: >> >>>> >> >>>> >> Successfully grabbed the sources and failed to build: >> >>>> >> >>>> >> >> >>>> >> >>>> >> LD .tmp_vmlinux1 >> >>>> >> >>>> >> drivers/built-in.o: In function `do_hvm_suspend': >> >>>> >> >>>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: undefined reference >> >>>> >> >>>> >> to `xenbus_suspend' >> >>>> >> >>>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: undefined reference >> >>>> >> >>>> >> to `xenbus_resume' >> >>>> >> >>>> >> make: *** [.tmp_vmlinux1] Error 1 >> >>>> >> >>>> >> >> >>>> >> >>>> >> :( >> >>>> >> >>>> >> >> >>>> >> >>>> > >> >>>> >> >>>> > Try the example .config files provided on the wiki page. >> >>>> >> >>>> > >> >>>> >> >>>> > -- Pasi >> >>>> >> >>>> > >> >>>> >> >>>> >> On Thu, May 13, 2010 at 10:14 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >> >>>> >> >>>> >> > On Thu, May 13, 2010 at 10:12:56AM -0400, chris wrote: >> >>>> >> >>>> >> >> Pasi, >> >>>> >> >>>> >> >> >> >>>> >> >>>> >> >> How do I pull those kernel sources you referenced? I see it mentioned >> >>>> >> >>>> >> >> on http://wiki.xensource.com/xenwiki/XenParavirtOps but no details on >> >>>> >> >>>> >> >> how to retrieve it. >> >>>> >> >>>> >> >> >> >>>> >> >>>> >> > >> >>>> >> >>>> >> > The instructions are there if you read it carefully.. >> >>>> >> >>>> >> > There's the topic of how to switch branches. >> >>>> >> >>>> >> > >> >>>> >> >>>> >> > -- Pasi >> >>>> >> >>>> >> > >> >>>> >> >>>> >> >> - chris >> >>>> >> >>>> >> >> >> >>>> >> >>>> >> >> On Thu, May 13, 2010 at 8:29 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >> >>>> >> >>>> >> >> > On Wed, May 12, 2010 at 08:41:34PM -0400, chris wrote: >> >>>> >> >>>> >> >> >> When reading the vtdhowto I noticed the ability to set iommu=verbose. >> >>>> >> >>>> >> >> >> Here is that output, I don't know if it helps at all to figure out >> >>>> >> >>>> >> >> >> what is wrong. >> >>>> >> >>>> >> >> >> >> >>>> >> >>>> >> >> > >> >>>> >> >>>> >> >> > That seems to be OK: >> >>>> >> >>>> >> >> > >> >>>> >> >>>> >> >> > (XEN) I/O virtualisation enabled >> >>>> >> >>>> >> >> > (XEN) I/O virtualisation for PV guests disabled >> >>>> >> >>>> >> >> > >> >>>> >> >>>> >> >> > So hmm.. I wonder if it's related to MSI stuff? >> >>>> >> >>>> >> >> > You could try xen.git xen/stable-2.6.32.x branch instead and see if that makes a difference.. >> >>>> >> >>>> >> >> > >> >>>> >> >>>> >> >> > -- Pasi >> >>>> >> >>>> >> >> > >> >>>> >> >>>> >> >> >> >> >>>> >> >>>> >> >> >> ---------- Forwarded message ---------- >> >>>> >> >>>> >> >> >> From: chris <tknchris@gmail.com> >> >>>> >> >>>> >> >> >> Date: Wed, May 12, 2010 at 5:28 PM >> >>>> >> >>>> >> >> >> Subject: Xen4 / Intel DX58SO Mobo / VT-d not working >> >>>> >> >>>> >> >> >> To: Xen-Users List <xen-users@lists.xensource.com> >> >>>> >> >>>> >> >> >> >> >>>> >> >>>> >> >> >> >> >>>> >> >>>> >> >> >> Hello, >> >>>> >> >>>> >> >> >> >> >>>> >> >>>> >> >> >> I've previously been successful with Xen4 and VT-d on other systems. I >> >>>> >> >>>> >> >> >> am having trouble getting VT-d passthrough working to a WinXP domain >> >>>> >> >>>> >> >> >> with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is enabled in bios, >> >>>> >> >>>> >> >> >> xm info shows hvm_directio capability, I have iommu=1 set, I have the >> >>>> >> >>>> >> >> >> devices bound to pciback on dom0 cmdline, xm >> >>>> >> >>>> >> >> >> pci-list-assignable-devices shows the devices as assignable. When I >> >>>> >> >>>> >> >> >> attempt to start the VM I get the error: >> >>>> >> >>>> >> >> >> >> >>>> >> >>>> >> >> >> Error: Failed to assign device to IOMMU >> >>>> >> >>>> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >> >>>> >> >>>> >> >> >> >> >>>> >> >>>> >> >> >> Below is all the information I can think of that would be useful to >> >>>> >> >>>> >> >> >> help debug it: >> >>>> >> >>>> >> >> >> >> >>>> >> >>>> >> >> >> BIOS VT-d Enabled: >> >>>> >> >>>> >> >> >> http://i43.tinypic.com/nl3a5e.jpg >> >>>> >> >>>> >> >> >> http://i42.tinypic.com/nqvlu1.jpg >> >>>> >> >>>> >> >> >> >> >>>> >> >>>> >> >> >> grub entry: >> >>>> >> >>>> >> >> >> >> >>>> >> >>>> >> >> >> title Xen 4.0.0 / Debian GNU/Linux, kernel 2.6.31.13 >> >>>> >> >>>> >> >> >> root (hd0,0) >> >>>> >> >>>> >> >> >> kernel /boot/xen-4.0.0.gz iommu=1 dom0_mem=256M >> >>>> >> >>>> >> >> >> dom0_max_vcpus=1 dom0_vcpus_pin=true >> >>>> >> >>>> >> >> >> module /boot/vmlinuz-2.6.31.13 root=/dev/md0 ro console=tty0 >> >>>> >> >>>> >> >> >> xen-pciback.permissive >> >>>> >> >>>> >> >> >> xen-pciback.hide=(02:00.0)(02:00.1)(02:00.2)(04:00.0)(04:00.1)(04:00.2)(07:00.0)(07:00.1)(07:00.2)(09:00.0)(09:00.1)(09:00.2) >> >>>> >> >>>> >> >> >> module /boot/initrd.img-2.6.31.13 >> >>>> >> >>>> >> >> >> >> >>>> >> >>>> >> >> >> # xm pci-list-assignable-devices >> >>>> >> >>>> >> >> >> 0000:09:00.0 >> >>>> >> >>>> >> >> >> 0000:09:00.1 >> >>>> >> >>>> >> >> >> 0000:09:00.2 >> >>>> >> >>>> >> >> >> 0000:07:00.0 >> >>>> >> >>>> >> >> >> 0000:07:00.1 >> >>>> >> >>>> >> >> >> 0000:07:00.2 >> >>>> >> >>>> >> >> >> 0000:04:00.0 >> >>>> >> >>>> >> >> >> 0000:04:00.1 >> >>>> >> >>>> >> >> >> 0000:04:00.2 >> >>>> >> >>>> >> >> >> 0000:02:00.0 >> >>>> >> >>>> >> >> >> 0000:02:00.1 >> >>>> >> >>>> >> >> >> 0000:02:00.2 >> >>>> >> >>>> >> >> >> >> >>>> >> >>>> >> >> >> # xm info >> >>>> >> >>>> >> >> >> host : test-box2 >> >>>> >> >>>> >> >> >> release : 2.6.31.13 >> >>>> >> >>>> >> >> >> version : #2 SMP Wed May 12 14:11:37 EDT 2010 >> >>>> >> >>>> >> >> >> machine : x86_64 >> >>>> >> >>>> >> >> >> nr_cpus : 8 >> >>>> >> >>>> >> >> >> nr_nodes : 1 >> >>>> >> >>>> >> >> >> cores_per_socket : 4 >> >>>> >> >>>> >> >> >> threads_per_core : 2 >> >>>> >> >>>> >> >> >> cpu_mhz : 2800 >> >>>> >> >>>> >> >> >> hw_caps : >> >>>> >> >>>> >> >> >> bfebfbff:28100800:00000000:00001b40:0098e3bd:00000000:00000001:00000000 >> >>>> >> >>>> >> >> >> virt_caps : hvm hvm_directio >> >>>> >> >>>> >> >> >> total_memory : 7950 >> >>>> >> >>>> >> >> >> free_memory : 7812 >> >>>> >> >>>> >> >> >> node_to_cpu : node0:0-7 >> >>>> >> >>>> >> >> >> node_to_memory : node0:7812 >> >>>> >> >>>> >> >> >> node_to_dma32_mem : node0:3249 >> >>>> >> >>>> >> >> >> max_node_id : 0 >> >>>> >> >>>> >> >> >> xen_major : 4 >> >>>> >> >>>> >> >> >> xen_minor : 0 >> >>>> >> >>>> >> >> >> xen_extra : .0 >> >>>> >> >>>> >> >> >> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 >> >>>> >> >>>> >> >> >> hvm-3.0-x86_32p hvm-3.0-x86_64 >> >>>> >> >>>> >> >> >> xen_scheduler : credit >> >>>> >> >>>> >> >> >> xen_pagesize : 4096 >> >>>> >> >>>> >> >> >> platform_params : virt_start=0xffff800000000000 >> >>>> >> >>>> >> >> >> xen_changeset : unavailable >> >>>> >> >>>> >> >> >> xen_commandline : iommu=1 dom0_mem=256M dom0_max_vcpus=1 >> >>>> >> >>>> >> >> >> dom0_vcpus_pin=true >> >>>> >> >>>> >> >> >> cc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1) >> >>>> >> >>>> >> >> >> cc_compile_by : root >> >>>> >> >>>> >> >> >> cc_compile_domain : >> >>>> >> >>>> >> >> >> cc_compile_date : Thu May 6 13:41:25 EDT 2010 >> >>>> >> >>>> >> >> >> xend_config_format : 4 >> >>>> >> >>>> >> >> >> >> >>>> >> >>>> >> >> >> # xm create vm-five.cfg >> >>>> >> >>>> >> >> >> Using config file "./vm-five.cfg". >> >>>> >> >>>> >> >> >> Error: Failed to assign device to IOMMU >> >>>> >> >>>> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >> >>>> >> >>>> >> >> >> >> >>>> >> >>>> >> >> >> I feel like I'm missing something really obvious but I've been at it >> >>>> >> >>>> >> >> >> for a while now and have run out of brain power. Anyone have any idea >> >>>> >> >>>> >> >> >> what might be wrong? >> >>>> >> >>>> >> >> >> >> >>>> >> >>>> >> >> >> - chris >> >>>> >> >>>> >> >> > >> >>>> >> >>>> >> >> >> __ __ _ _ ___ ___ >> >>>> >> >>>> >> >> >> \ \/ /___ _ __ | || | / _ \ / _ \ >> >>>> >> >>>> >> >> >> \ // _ \ \047_ \ | || |_| | | | | | | >> >>>> >> >>>> >> >> >> / \ __/ | | | |__ _| |_| | |_| | >> >>>> >> >>>> >> >> >> /_/\_\___|_| |_| |_|(_)___(_)___/ >> >>>> >> >>>> >> >> >> >> >>>> >> >>>> >> >> >> (XEN) Xen version 4.0.0 (root@) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) Thu May 6 13:41:25 EDT 2010 >> >>>> >> >>>> >> >> >> (XEN) Latest ChangeSet: unavailable >> >>>> >> >>>> >> >> >> (XEN) Command line: iommu=verbose dom0_mem=256M dom0_max_vcpus=1 dom0_vcpus_pin=true >> >>>> >> >>>> >> >> >> (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 - 000000000008f000 (usable) >> >>>> >> >>>> >> >> >> (XEN) 000000000008f000 - 0000000000090000 (reserved) >> >>>> >> >>>> >> >> >> (XEN) 0000000000090000 - 000000000009ec00 (usable) >> >>>> >> >>>> >> >> >> (XEN) 000000000009ec00 - 00000000000a0000 (reserved) >> >>>> >> >>>> >> >> >> (XEN) 00000000000e0000 - 0000000000100000 (reserved) >> >>>> >> >>>> >> >> >> (XEN) 0000000000100000 - 00000000cf4bd000 (usable) >> >>>> >> >>>> >> >> >> (XEN) 00000000cf4bd000 - 00000000cf4bf000 (reserved) >> >>>> >> >>>> >> >> >> (XEN) 00000000cf4bf000 - 00000000cf4c2000 (usable) >> >>>> >> >>>> >> >> >> (XEN) 00000000cf4c2000 - 00000000cf7bf000 (ACPI NVS) >> >>>> >> >>>> >> >> >> (XEN) 00000000cf7bf000 - 00000000cf7df000 (usable) >> >>>> >> >>>> >> >> >> (XEN) 00000000cf7df000 - 00000000cf7ff000 (ACPI data) >> >>>> >> >>>> >> >> >> (XEN) 00000000cf7ff000 - 00000000cf800000 (usable) >> >>>> >> >>>> >> >> >> (XEN) 00000000cf800000 - 00000000d0000000 (reserved) >> >>>> >> >>>> >> >> >> (XEN) 00000000f8000000 - 00000000fd000000 (reserved) >> >>>> >> >>>> >> >> >> (XEN) 00000000ffe00000 - 0000000100000000 (reserved) >> >>>> >> >>>> >> >> >> (XEN) 0000000100000000 - 0000000230000000 (usable) >> >>>> >> >>>> >> >> >> (XEN) ACPI: RSDP 000FE020, 0024 (r2 INTEL ) >> >>>> >> >>>> >> >> >> (XEN) ACPI: XSDT CF7FE120, 0074 (r1 INTEL DX58SO 11F6 1000013) >> >>>> >> >>>> >> >> >> (XEN) ACPI: FACP CF7FD000, 00F4 (r3 INTEL DX58SO 11F6 MSFT 100000D) >> >>>> >> >>>> >> >> >> (XEN) ACPI Warning (tbfadt-0444): Optional field "Pm2ControlBlock" has zero address or length: 0000000000000450/0 [20070126] >> >>>> >> >>>> >> >> >> (XEN) ACPI: DSDT CF7F8000, 4641 (r2 INTEL DX58SO 11F6 MSFT 100000D) >> >>>> >> >>>> >> >> >> (XEN) ACPI: FACS CF728000, 0040 >> >>>> >> >>>> >> >> >> (XEN) ACPI: APIC CF7F7000, 0138 (r2 INTEL DX58SO 11F6 MSFT 100000D) >> >>>> >> >>>> >> >> >> (XEN) ACPI: WDDT CF7F6000, 0040 (r1 INTEL DX58SO 11F6 MSFT 100000D) >> >>>> >> >>>> >> >> >> (XEN) ACPI: MCFG CF7F5000, 003C (r1 INTEL DX58SO 11F6 MSFT 100000D) >> >>>> >> >>>> >> >> >> (XEN) ACPI: ASF! CF7F4000, 00AC (r32 INTEL DX58SO 11F6 MSFT 100000D) >> >>>> >> >>>> >> >> >> (XEN) ACPI: HPET CF7F3000, 0038 (r1 INTEL DX58SO 11F6 MSFT 100000D) >> >>>> >> >>>> >> >> >> (XEN) ACPI: SSDT CF7E2000, E134 (r1 INTEL SSDT PM 11F6 MSFT 100000D) >> >>>> >> >>>> >> >> >> (XEN) ACPI: DMAR CF7DF000, 0140 (r1 INTEL DX58SO 11F6 MSFT 100000D) >> >>>> >> >>>> >> >> >> (XEN) ACPI: WDTT CF7F1000, 020C (r2 INTEL DX58SO 11F6 MSFT 100000D) >> >>>> >> >>>> >> >> >> (XEN) ACPI: ASPT CF7F2000, 0034 (r4 INTEL PerfTune 11F6 MSFT 100000D) >> >>>> >> >>>> >> >> >> (XEN) System RAM: 7950MB (8140820kB) >> >>>> >> >>>> >> >> >> (XEN) Domain heap initialised >> >>>> >> >>>> >> >> >> (XEN) Processor #0 7:10 APIC version 21 >> >>>> >> >>>> >> >> >> (XEN) Processor #2 7:10 APIC version 21 >> >>>> >> >>>> >> >> >> (XEN) Processor #4 7:10 APIC version 21 >> >>>> >> >>>> >> >> >> (XEN) Processor #6 7:10 APIC version 21 >> >>>> >> >>>> >> >> >> (XEN) Processor #1 7:10 APIC version 21 >> >>>> >> >>>> >> >> >> (XEN) Processor #3 7:10 APIC version 21 >> >>>> >> >>>> >> >> >> (XEN) Processor #5 7:10 APIC version 21 >> >>>> >> >>>> >> >> >> (XEN) Processor #7 7:10 APIC version 21 >> >>>> >> >>>> >> >> >> (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 >> >>>> >> >>>> >> >> >> (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs >> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:679: Host address width 39 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: >> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = fe711000 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1b.0 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: >> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = fe710000 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:340: IOAPIC: f0:1f.7 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:411: flags: INCLUDE_ALL >> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e9000 end_address e9fff >> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.1 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ea000 end_address eafff >> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.2 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr eb000 end_address ebfff >> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.0 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e6000 end_address e6fff >> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.1 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e7000 end_address e7fff >> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.2 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e8000 end_address e8fff >> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ec000 end_address eefff >> >>>> >> >>>> >> >> >> (XEN) Using scheduler: SMP Credit Scheduler (credit) >> >>>> >> >>>> >> >> >> (XEN) Detected 2800.125 MHz processor. >> >>>> >> >>>> >> >> >> (XEN) Initing memory sharing. >> >>>> >> >>>> >> >> >> (XEN) VMX: Supported advanced features: >> >>>> >> >>>> >> >> >> (XEN) - APIC MMIO access virtualisation >> >>>> >> >>>> >> >> >> (XEN) - APIC TPR shadow >> >>>> >> >>>> >> >> >> (XEN) - Extended Page Tables (EPT) >> >>>> >> >>>> >> >> >> (XEN) - Virtual-Processor Identifiers (VPID) >> >>>> >> >>>> >> >> >> (XEN) - Virtual NMI >> >>>> >> >>>> >> >> >> (XEN) - MSR direct-access bitmap >> >>>> >> >>>> >> >> >> (XEN) HVM: ASIDs enabled. >> >>>> >> >>>> >> >> >> (XEN) HVM: VMX enabled >> >>>> >> >>>> >> >> >> (XEN) HVM: Hardware Assisted Paging detected. >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = fe711000 iommu->reg = ffff82c3fff57000 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c9008010e60262 ecap = f0207a >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = fe710000 iommu->reg = ffff82c3fff56000 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c90780106f0462 ecap = f020fa >> >>>> >> >>>> >> >> >> (XEN) Intel VT-d Snoop Control not supported. >> >>>> >> >>>> >> >> >> (XEN) Intel VT-d DMA Passthrough not supported. >> >>>> >> >>>> >> >> >> (XEN) Intel VT-d Queued Invalidation supported. >> >>>> >> >>>> >> >> >> (XEN) Intel VT-d Interrupt Remapping supported. >> >>>> >> >>>> >> >> >> (XEN) I/O virtualisation enabled >> >>>> >> >>>> >> >> >> (XEN) I/O virtualisation for PV guests disabled >> >>>> >> >>>> >> >> >> (XEN) Total of 8 processors activated. >> >>>> >> >>>> >> >> >> (XEN) ENABLING IO-APIC IRQs >> >>>> >> >>>> >> >> >> (XEN) -> Using new ACK method >> >>>> >> >>>> >> >> >> (XEN) TSC is reliable, synchronization unnecessary >> >>>> >> >>>> >> >> >> (XEN) Platform timer is 14.318MHz HPET >> >>>> >> >>>> >> >> >> (XEN) Allocated console ring of 16 KiB. >> >>>> >> >>>> >> >> >> (XEN) Brought up 8 CPUs >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:0.0 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.0 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.1 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.0 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.1 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.2 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:14.3 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:19.0 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.0 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.1 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.2 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.7 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:1b.0 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.0 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.1 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.2 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.7 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.0 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.2 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.3 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.5 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.0 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.1 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.2 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.0 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.1 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.2 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 5:0.0 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.0 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.1 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.2 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.0 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.1 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.2 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = a:0.0 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.0 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.1 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.2 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.3 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.4 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.5 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.6 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.7 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.0 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.1 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.0 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.1 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.0 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.1 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.4 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.0 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.1 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.2 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.3 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.0 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.1 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.2 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.3 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.0 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.1 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.2 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.3 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = ffff82c3fff57000 >> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = ffff82c3fff56000 >> >>>> >> >>>> >> >> >> (XEN) *** LOADING DOMAIN 0 *** >> >>>> >> >>>> >> >> >> (XEN) Xen kernel: 64-bit, lsb, compat32 >> >>>> >> >>>> >> >> >> (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x26ae000 >> >>>> >> >>>> >> >> >> (XEN) PHYSICAL MEMORY ARRANGEMENT: >> >>>> >> >>>> >> >> >> (XEN) Dom0 alloc.: 0000000210000000->0000000220000000 >> >>>> >> >>>> >> >> >> (XEN) VIRTUAL MEMORY ARRANGEMENT: >> >>>> >> >>>> >> >> >> (XEN) Loaded kernel: ffffffff81000000->ffffffff826ae000 >> >>>> >> >>>> >> >> >> (XEN) Init. ramdisk: ffffffff826ae000->ffffffff8f4de600 >> >>>> >> >>>> >> >> >> (XEN) Phys-Mach map: ffffffff8f4df000->ffffffff8f55f000 >> >>>> >> >>>> >> >> >> (XEN) Start info: ffffffff8f55f000->ffffffff8f55f4b4 >> >>>> >> >>>> >> >> >> (XEN) Page tables: ffffffff8f560000->ffffffff8f5df000 >> >>>> >> >>>> >> >> >> (XEN) Boot stack: ffffffff8f5df000->ffffffff8f5e0000 >> >>>> >> >>>> >> >> >> (XEN) TOTAL: ffffffff80000000->ffffffff8f800000 >> >>>> >> >>>> >> >> >> (XEN) ENTRY ADDRESS: ffffffff81a10860 >> >>>> >> >>>> >> >> >> (XEN) Dom0 has maximum 1 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 \047CTRL-a\047 three times to switch input to Xen) >> >>>> >> >>>> >> >> >> (XEN) Freed 164kB init memory. >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 pirq=0 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=2, irq=0 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=000009f0 pirq=0 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 3 already mapped >> >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 4 already mapped >> >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 5 already mapped >> >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 6 already mapped >> >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 7 already mapped >> >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 8 already mapped >> >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 9 already mapped >> >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 10 already mapped >> >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 11 already mapped >> >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 12 already mapped >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000009f0 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 pirq=0 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=23, irq=23 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a929 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a929 pirq=23 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 pirq=16 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 pirq=16 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 >> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >>>> >> >>>> >> >> > >> >>>> >> >>>> >> >> >> _______________________________________________ >> >>>> >> >>>> >> >> >> Xen-users mailing list >> >>>> >> >>>> >> >> >> Xen-users@lists.xensource.com >> >>>> >> >>>> >> >> >> http://lists.xensource.com/xen-users >> >>>> >> >>>> >> >> > >> >>>> >> >>>> >> > >> >>>> >> >>>> > >> >>>> >> >>> >> >>>> >> >> >> >>>> >> > >> >>>> > >> >>> >> > >> > >> > >> > >> > >> > -- >> > Best regards, >> > Sander mailto:linux@eikelenboom.it >> > >> > > ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: Re: [Xen-users] RE: Xen4 / Intel DX58SO Mobo / VT-d not working 2010-05-14 21:57 ` chris @ 2010-05-15 6:56 ` Sander Eikelenboom 0 siblings, 0 replies; 32+ messages in thread From: Sander Eikelenboom @ 2010-05-15 6:56 UTC (permalink / raw) To: chris; +Cc: Xen-Devel List, Xen-Users List Hello chris, Newer pvops dom0's require xen 3.4.3 or newer as far as I know. -- Sander Friday, May 14, 2010, 11:57:53 PM, you wrote: > I tried 3.4.2 with the same 2 dom0's and it doesnt even boot fully. > One hangs completely and the other goes really really slooow. The > working machine is in production so i cant try 4.0 :( > - chris > On Fri, May 14, 2010 at 5:34 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >> On Fri, May 14, 2010 at 05:26:22PM -0400, chris wrote: >>> My guests are HVM so thats not really possible. Yes the machine with >>> 3.4.2 has a hardware IOMMU. >>> >> >> What if you install Xen 4.0 to the other machine? >> Or Xen 3.4.2 to this machine? >> >> Does it work then? >> >> Trying to figure out if it's hardware/BIOS related, >> or Xen version related. >> >> -- Pasi >> >>> - chris >>> >>> On Fri, May 14, 2010 at 5:25 PM, Sander Eikelenboom >>> <linux@eikelenboom.it> wrote: >>> > Hello chris, >>> > >>> > But does the other machine have an IOMMU on 3.4.2 ? >>> > I passthrough a few USB controllers my self, but the machine doesn't have a hardware IOMMU, >>> > so it uses the SWIOTLB changed by Konrad to work with Xen and let the DMA of the USB controllers work. >>> > It's working on xen-4.0.1-testing, xen-next pvops kernel from a few weeks ago, various domU kernel. >>> > One domU kernel is a 2.6.33 from Konrad's tree, with patched and backported xhci support from 2.6.34. >>> > >>> > So perhaps you could try with the IOMMU off, see if it makes a difference, and would point the problem to the IOMMU more specifically. >>> > Oh yes, what pci backend mode have you choosen in your dom0 kernel config ? >>> > You have 3 options, virtual, passthrough or slot. >>> > I allways tend to use passthrough, don't know it it makes a big difference though, but at least all functions get registered under the same device id in the guest. >>> > >>> > >>> > >>> > -- >>> > >>> > Sander >>> > >>> > >>> > >>> > Friday, May 14, 2010, 9:46:01 PM, you wrote: >>> > >>> >> I added a pci sound card and interestingly that works. I'm digging >>> >> around for another pci-e device to try to identify if its all pci-e or >>> >> only this device. Strange this is that I have a few other machines >>> >> with this same usb controller which is working on 3.4.2. >>> > >>> >> *scratches head* >>> > >>> >> - chris >>> > >>> >> On Fri, May 14, 2010 at 3:21 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>> >>> On Fri, May 14, 2010 at 03:18:02PM -0400, chris wrote: >>> >>>> It is a multifunction device, a pci-e usb controller, so I assumed all >>> >>>> them had to be passed through. I just changed it to only 02:00.0 and >>> >>>> same thing >>> >>>> >>> >>>> test-box2:~# cat /etc/xen/vm-five.cfg | grep pci >>> >>>> pci = ['02:00.0'] >>> >>>> test-box2:~# xm create /etc/xen/vm-five.cfg >>> >>>> Using config file "/etc/xen/vm-five.cfg". >>> >>>> Error: Failed to assign device to IOMMU >>> >>>> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>> >>>> >>> >>> >>> >>> Hmm.. weird. >>> >>> >>> >>> Two things to try: >>> >>> >>> >>> 1) Try passthru some other device (which is just a single pci id) >>> >>> 2) Try passthru that pci-e usb controller to Linux PV guest and see if that works >>> >>> >>> >>> -- Pasi >>> >>> >>> >>>> >>> >>>> On Fri, May 14, 2010 at 3:11 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>> >>>> > On Fri, May 14, 2010 at 03:05:49PM -0400, chris wrote: >>> >>>> >> Pasi, >>> >>>> >> >>> >>>> >> Tried latest stable/2.6.32.x per your advice, no change. Anyone on >>> >>>> >> xen-devel that can help me troubleshoot further? Everything looks >>> >>>> >> right, can't figure out why vt-d is not working but it must be some >>> >>>> >> kind of bug :( >>> >>>> >> >>> >>>> > >>> >>>> > Did you try the suggestion said earlier.. try to just passthru the first pci device? >>> >>>> > >>> >>>> > -- Pasi >>> >>>> > >>> >>>> >> test-box2:~# uname -a >>> >>>> >> Linux test-box2 2.6.32.12 #1 SMP Fri May 14 13:40:05 EDT 2010 x86_64 GNU/Linux >>> >>>> >> >>> >>>> >> test-box2:~# xm info | grep virt_caps >>> >>>> >> virt_caps : hvm hvm_directio >>> >>>> >> >>> >>>> >> test-box2:~# xm pci-list-assignable-devices >>> >>>> >> 0000:02:00.0 >>> >>>> >> 0000:02:00.1 >>> >>>> >> 0000:02:00.2 >>> >>>> >> >>> >>>> >> test-box2:~# xm create /etc/xen/vm-five.cfg >>> >>>> >> Using config file "/etc/xen/vm-five.cfg". >>> >>>> >> Error: Failed to assign device to IOMMU >>> >>>> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>> >>>> >> >>> >>>> >> test-box2:~# cat /etc/xen/vm-five.cfg | grep -v '#' >>> >>>> >> kernel = '/usr/lib/xen/boot/hvmloader' >>> >>>> >> builder = 'hvm' >>> >>>> >> memory = '1792' >>> >>>> >> device_model='/usr/lib/xen/bin/qemu-dm' >>> >>>> >> disk = [ 'phy:/dev/storage/vm-five,ioemu:hda,w', >>> >>>> >> 'phy:/dev/sr0,ioemu:hdc:cdrom,r' >>> >>>> >> ] >>> >>>> >> name = 'vm-five' >>> >>>> >> vif = ['type=ioemu, bridge=eth0, mac=00:16:3D:37:A1:42'] >>> >>>> >> boot='dc' >>> >>>> >> cpus='0-1' >>> >>>> >> vcpus=2 >>> >>>> >> acpi=1 >>> >>>> >> ahci=1 >>> >>>> >> vnc=1 >>> >>>> >> sdl=0 >>> >>>> >> timer_mode=1 >>> >>>> >> usb=1 >>> >>>> >> usbdevice='tablet' >>> >>>> >> localtime=1 >>> >>>> >> pci = ['02:00.0','02:00.1','02:00.2'] >>> >>>> >> >>> >>>> >> On Thu, May 13, 2010 at 2:28 PM, chris <tknchris@gmail.com> wrote: >>> >>>> >> > Forwarding to xen-devel. Can't seem to get VT-d working with xen4 from >>> >>>> >> > tarball on xen.org 2.6.31.13 pv_ops dom0. On pasi's advice I tried >>> >>>> >> > switching to stable/2.6.32.x branch for dom0 and that doesnt even >>> >>>> >> > build. Did something change recently thats breaking compilation? >>> >>>> >> > >>> >>>> >> > Attached is xen dmesg with iommu=verbose loglvl=all guest_loglvl=all, >>> >>>> >> > and dom0 dmesg from 2.6.31.x >>> >>>> >> > >>> >>>> >> > Any ideas on why VT-d is not working on this board? Initialization >>> >>>> >> > looks good, xen reports hvm_directio capability, everything says VT-d >>> >>>> >> > should work until domain is created. >>> >>>> >> > >>> >>>> >> > Any ideas why stable/2.6.32.x wont build? >>> >>>> >> > >>> >>>> >> > - chris >>> >>>> >> > >>> >>>> >> > On Thu, May 13, 2010 at 2:07 PM, chris <tknchris@gmail.com> wrote: >>> >>>> >> >> I redid it with oldconfig which I didn't think would help and same >>> >>>> >> >> thing. I guess this tree is broken? Can someone else try and see if >>> >>>> >> >> they can build it? Ugh, whata day :) >>> >>>> >> >> >>> >>>> >> >> On Thu, May 13, 2010 at 1:58 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>> >>>> >> >>> On Thu, May 13, 2010 at 01:55:25PM -0400, chris wrote: >>> >>>> >> >>>> I used the default config on the wiki which you created. Steps I took were: >>> >>>> >> >>>> >>> >>>> >> >>>> # make clean distclean >>> >>>> >> >>>> # wget -O .config >>> >>>> >> >>>> "http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.10-pvops-dom0-xen-stable-x86_64" >>> >>>> >> >>> >>> >>>> >> >>> You should do "make oldconfig" at this point. >>> >>>> >> >>> >>> >>>> >> >>>> # make -j8 bzImage >>> >>>> >> >>>> (blah blah) >>> >>>> >> >>>> LD vmlinux.o >>> >>>> >> >>>> MODPOST vmlinux.o >>> >>>> >> >>>> WARNING: modpost: Found 7 section mismatch(es). >>> >>>> >> >>>> To see full details build your kernel with: >>> >>>> >> >>>> 'make CONFIG_DEBUG_SECTION_MISMATCH=y' >>> >>>> >> >>>> GEN .version >>> >>>> >> >>>> CHK include/linux/compile.h >>> >>>> >> >>>> UPD include/linux/compile.h >>> >>>> >> >>>> CC init/version.o >>> >>>> >> >>>> LD init/built-in.o >>> >>>> >> >>>> LD .tmp_vmlinux1 >>> >>>> >> >>>> drivers/built-in.o: In function `do_hvm_suspend': >>> >>>> >> >>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: undefined reference >>> >>>> >> >>>> to `xenbus_suspend' >>> >>>> >> >>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: undefined reference >>> >>>> >> >>>> to `xenbus_resume' >>> >>>> >> >>>> make: *** [.tmp_vmlinux1] Error 1 >>> >>>> >> >>>> >>> >>>> >> >>> >>> >>>> >> >>> Hmm.. weird. I wonder if something has changed recently or what's going on in here.. >>> >>>> >> >>> >>> >>>> >> >>> -- Pasi >>> >>>> >> >>> >>> >>>> >> >>>> >>> >>>> >> >>>> On Thu, May 13, 2010 at 11:47 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>> >>>> >> >>>> > On Thu, May 13, 2010 at 11:33:57AM -0400, chris wrote: >>> >>>> >> >>>> >> Successfully grabbed the sources and failed to build: >>> >>>> >> >>>> >> >>> >>>> >> >>>> >> LD .tmp_vmlinux1 >>> >>>> >> >>>> >> drivers/built-in.o: In function `do_hvm_suspend': >>> >>>> >> >>>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: undefined reference >>> >>>> >> >>>> >> to `xenbus_suspend' >>> >>>> >> >>>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: undefined reference >>> >>>> >> >>>> >> to `xenbus_resume' >>> >>>> >> >>>> >> make: *** [.tmp_vmlinux1] Error 1 >>> >>>> >> >>>> >> >>> >>>> >> >>>> >> :( >>> >>>> >> >>>> >> >>> >>>> >> >>>> > >>> >>>> >> >>>> > Try the example .config files provided on the wiki page. >>> >>>> >> >>>> > >>> >>>> >> >>>> > -- Pasi >>> >>>> >> >>>> > >>> >>>> >> >>>> >> On Thu, May 13, 2010 at 10:14 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>> >>>> >> >>>> >> > On Thu, May 13, 2010 at 10:12:56AM -0400, chris wrote: >>> >>>> >> >>>> >> >> Pasi, >>> >>>> >> >>>> >> >> >>> >>>> >> >>>> >> >> How do I pull those kernel sources you referenced? I see it mentioned >>> >>>> >> >>>> >> >> on http://wiki.xensource.com/xenwiki/XenParavirtOps but no details on >>> >>>> >> >>>> >> >> how to retrieve it. >>> >>>> >> >>>> >> >> >>> >>>> >> >>>> >> > >>> >>>> >> >>>> >> > The instructions are there if you read it carefully.. >>> >>>> >> >>>> >> > There's the topic of how to switch branches. >>> >>>> >> >>>> >> > >>> >>>> >> >>>> >> > -- Pasi >>> >>>> >> >>>> >> > >>> >>>> >> >>>> >> >> - chris >>> >>>> >> >>>> >> >> >>> >>>> >> >>>> >> >> On Thu, May 13, 2010 at 8:29 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: >>> >>>> >> >>>> >> >> > On Wed, May 12, 2010 at 08:41:34PM -0400, chris wrote: >>> >>>> >> >>>> >> >> >> When reading the vtdhowto I noticed the ability to set iommu=verbose. >>> >>>> >> >>>> >> >> >> Here is that output, I don't know if it helps at all to figure out >>> >>>> >> >>>> >> >> >> what is wrong. >>> >>>> >> >>>> >> >> >> >>> >>>> >> >>>> >> >> > >>> >>>> >> >>>> >> >> > That seems to be OK: >>> >>>> >> >>>> >> >> > >>> >>>> >> >>>> >> >> > (XEN) I/O virtualisation enabled >>> >>>> >> >>>> >> >> > (XEN) I/O virtualisation for PV guests disabled >>> >>>> >> >>>> >> >> > >>> >>>> >> >>>> >> >> > So hmm.. I wonder if it's related to MSI stuff? >>> >>>> >> >>>> >> >> > You could try xen.git xen/stable-2.6.32.x branch instead and see if that makes a difference.. >>> >>>> >> >>>> >> >> > >>> >>>> >> >>>> >> >> > -- Pasi >>> >>>> >> >>>> >> >> > >>> >>>> >> >>>> >> >> >> >>> >>>> >> >>>> >> >> >> ---------- Forwarded message ---------- >>> >>>> >> >>>> >> >> >> From: chris <tknchris@gmail.com> >>> >>>> >> >>>> >> >> >> Date: Wed, May 12, 2010 at 5:28 PM >>> >>>> >> >>>> >> >> >> Subject: Xen4 / Intel DX58SO Mobo / VT-d not working >>> >>>> >> >>>> >> >> >> To: Xen-Users List <xen-users@lists.xensource.com> >>> >>>> >> >>>> >> >> >> >>> >>>> >> >>>> >> >> >> >>> >>>> >> >>>> >> >> >> Hello, >>> >>>> >> >>>> >> >> >> >>> >>>> >> >>>> >> >> >> I've previously been successful with Xen4 and VT-d on other systems. I >>> >>>> >> >>>> >> >> >> am having trouble getting VT-d passthrough working to a WinXP domain >>> >>>> >> >>>> >> >> >> with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is enabled in bios, >>> >>>> >> >>>> >> >> >> xm info shows hvm_directio capability, I have iommu=1 set, I have the >>> >>>> >> >>>> >> >> >> devices bound to pciback on dom0 cmdline, xm >>> >>>> >> >>>> >> >> >> pci-list-assignable-devices shows the devices as assignable. When I >>> >>>> >> >>>> >> >> >> attempt to start the VM I get the error: >>> >>>> >> >>>> >> >> >> >>> >>>> >> >>>> >> >> >> Error: Failed to assign device to IOMMU >>> >>>> >> >>>> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>> >>>> >> >>>> >> >> >> >>> >>>> >> >>>> >> >> >> Below is all the information I can think of that would be useful to >>> >>>> >> >>>> >> >> >> help debug it: >>> >>>> >> >>>> >> >> >> >>> >>>> >> >>>> >> >> >> BIOS VT-d Enabled: >>> >>>> >> >>>> >> >> >> http://i43.tinypic.com/nl3a5e.jpg >>> >>>> >> >>>> >> >> >> http://i42.tinypic.com/nqvlu1.jpg >>> >>>> >> >>>> >> >> >> >>> >>>> >> >>>> >> >> >> grub entry: >>> >>>> >> >>>> >> >> >> >>> >>>> >> >>>> >> >> >> title Xen 4.0.0 / Debian GNU/Linux, kernel 2.6.31.13 >>> >>>> >> >>>> >> >> >> root (hd0,0) >>> >>>> >> >>>> >> >> >> kernel /boot/xen-4.0.0.gz iommu=1 dom0_mem=256M >>> >>>> >> >>>> >> >> >> dom0_max_vcpus=1 dom0_vcpus_pin=true >>> >>>> >> >>>> >> >> >> module /boot/vmlinuz-2.6.31.13 root=/dev/md0 ro console=tty0 >>> >>>> >> >>>> >> >> >> xen-pciback.permissive >>> >>>> >> >>>> >> >> >> xen-pciback.hide=(02:00.0)(02:00.1)(02:00.2)(04:00.0)(04:00.1)(04:00.2)(07:00.0)(07:00.1)(07:00.2)(09:00.0)(09:00.1)(09:00.2) >>> >>>> >> >>>> >> >> >> module /boot/initrd.img-2.6.31.13 >>> >>>> >> >>>> >> >> >> >>> >>>> >> >>>> >> >> >> # xm pci-list-assignable-devices >>> >>>> >> >>>> >> >> >> 0000:09:00.0 >>> >>>> >> >>>> >> >> >> 0000:09:00.1 >>> >>>> >> >>>> >> >> >> 0000:09:00.2 >>> >>>> >> >>>> >> >> >> 0000:07:00.0 >>> >>>> >> >>>> >> >> >> 0000:07:00.1 >>> >>>> >> >>>> >> >> >> 0000:07:00.2 >>> >>>> >> >>>> >> >> >> 0000:04:00.0 >>> >>>> >> >>>> >> >> >> 0000:04:00.1 >>> >>>> >> >>>> >> >> >> 0000:04:00.2 >>> >>>> >> >>>> >> >> >> 0000:02:00.0 >>> >>>> >> >>>> >> >> >> 0000:02:00.1 >>> >>>> >> >>>> >> >> >> 0000:02:00.2 >>> >>>> >> >>>> >> >> >> >>> >>>> >> >>>> >> >> >> # xm info >>> >>>> >> >>>> >> >> >> host : test-box2 >>> >>>> >> >>>> >> >> >> release : 2.6.31.13 >>> >>>> >> >>>> >> >> >> version : #2 SMP Wed May 12 14:11:37 EDT 2010 >>> >>>> >> >>>> >> >> >> machine : x86_64 >>> >>>> >> >>>> >> >> >> nr_cpus : 8 >>> >>>> >> >>>> >> >> >> nr_nodes : 1 >>> >>>> >> >>>> >> >> >> cores_per_socket : 4 >>> >>>> >> >>>> >> >> >> threads_per_core : 2 >>> >>>> >> >>>> >> >> >> cpu_mhz : 2800 >>> >>>> >> >>>> >> >> >> hw_caps : >>> >>>> >> >>>> >> >> >> bfebfbff:28100800:00000000:00001b40:0098e3bd:00000000:00000001:00000000 >>> >>>> >> >>>> >> >> >> virt_caps : hvm hvm_directio >>> >>>> >> >>>> >> >> >> total_memory : 7950 >>> >>>> >> >>>> >> >> >> free_memory : 7812 >>> >>>> >> >>>> >> >> >> node_to_cpu : node0:0-7 >>> >>>> >> >>>> >> >> >> node_to_memory : node0:7812 >>> >>>> >> >>>> >> >> >> node_to_dma32_mem : node0:3249 >>> >>>> >> >>>> >> >> >> max_node_id : 0 >>> >>>> >> >>>> >> >> >> xen_major : 4 >>> >>>> >> >>>> >> >> >> xen_minor : 0 >>> >>>> >> >>>> >> >> >> xen_extra : .0 >>> >>>> >> >>>> >> >> >> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 >>> >>>> >> >>>> >> >> >> hvm-3.0-x86_32p hvm-3.0-x86_64 >>> >>>> >> >>>> >> >> >> xen_scheduler : credit >>> >>>> >> >>>> >> >> >> xen_pagesize : 4096 >>> >>>> >> >>>> >> >> >> platform_params : virt_start=0xffff800000000000 >>> >>>> >> >>>> >> >> >> xen_changeset : unavailable >>> >>>> >> >>>> >> >> >> xen_commandline : iommu=1 dom0_mem=256M dom0_max_vcpus=1 >>> >>>> >> >>>> >> >> >> dom0_vcpus_pin=true >>> >>>> >> >>>> >> >> >> cc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1) >>> >>>> >> >>>> >> >> >> cc_compile_by : root >>> >>>> >> >>>> >> >> >> cc_compile_domain : >>> >>>> >> >>>> >> >> >> cc_compile_date : Thu May 6 13:41:25 EDT 2010 >>> >>>> >> >>>> >> >> >> xend_config_format : 4 >>> >>>> >> >>>> >> >> >> >>> >>>> >> >>>> >> >> >> # xm create vm-five.cfg >>> >>>> >> >>>> >> >> >> Using config file "./vm-five.cfg". >>> >>>> >> >>>> >> >> >> Error: Failed to assign device to IOMMU >>> >>>> >> >>>> >> >> >> (0000:02:00.0@100,msitranslate=1,power_mgmt=0) >>> >>>> >> >>>> >> >> >> >>> >>>> >> >>>> >> >> >> I feel like I'm missing something really obvious but I've been at it >>> >>>> >> >>>> >> >> >> for a while now and have run out of brain power. Anyone have any idea >>> >>>> >> >>>> >> >> >> what might be wrong? >>> >>>> >> >>>> >> >> >> >>> >>>> >> >>>> >> >> >> - chris >>> >>>> >> >>>> >> >> > >>> >>>> >> >>>> >> >> >> __ __ _ _ ___ ___ >>> >>>> >> >>>> >> >> >> \ \/ /___ _ __ | || | / _ \ / _ \ >>> >>>> >> >>>> >> >> >> \ // _ \ \047_ \ | || |_| | | | | | | >>> >>>> >> >>>> >> >> >> / \ __/ | | | |__ _| |_| | |_| | >>> >>>> >> >>>> >> >> >> /_/\_\___|_| |_| |_|(_)___(_)___/ >>> >>>> >> >>>> >> >> >> >>> >>>> >> >>>> >> >> >> (XEN) Xen version 4.0.0 (root@) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) Thu May 6 13:41:25 EDT 2010 >>> >>>> >> >>>> >> >> >> (XEN) Latest ChangeSet: unavailable >>> >>>> >> >>>> >> >> >> (XEN) Command line: iommu=verbose dom0_mem=256M dom0_max_vcpus=1 dom0_vcpus_pin=true >>> >>>> >> >>>> >> >> >> (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 - 000000000008f000 (usable) >>> >>>> >> >>>> >> >> >> (XEN) 000000000008f000 - 0000000000090000 (reserved) >>> >>>> >> >>>> >> >> >> (XEN) 0000000000090000 - 000000000009ec00 (usable) >>> >>>> >> >>>> >> >> >> (XEN) 000000000009ec00 - 00000000000a0000 (reserved) >>> >>>> >> >>>> >> >> >> (XEN) 00000000000e0000 - 0000000000100000 (reserved) >>> >>>> >> >>>> >> >> >> (XEN) 0000000000100000 - 00000000cf4bd000 (usable) >>> >>>> >> >>>> >> >> >> (XEN) 00000000cf4bd000 - 00000000cf4bf000 (reserved) >>> >>>> >> >>>> >> >> >> (XEN) 00000000cf4bf000 - 00000000cf4c2000 (usable) >>> >>>> >> >>>> >> >> >> (XEN) 00000000cf4c2000 - 00000000cf7bf000 (ACPI NVS) >>> >>>> >> >>>> >> >> >> (XEN) 00000000cf7bf000 - 00000000cf7df000 (usable) >>> >>>> >> >>>> >> >> >> (XEN) 00000000cf7df000 - 00000000cf7ff000 (ACPI data) >>> >>>> >> >>>> >> >> >> (XEN) 00000000cf7ff000 - 00000000cf800000 (usable) >>> >>>> >> >>>> >> >> >> (XEN) 00000000cf800000 - 00000000d0000000 (reserved) >>> >>>> >> >>>> >> >> >> (XEN) 00000000f8000000 - 00000000fd000000 (reserved) >>> >>>> >> >>>> >> >> >> (XEN) 00000000ffe00000 - 0000000100000000 (reserved) >>> >>>> >> >>>> >> >> >> (XEN) 0000000100000000 - 0000000230000000 (usable) >>> >>>> >> >>>> >> >> >> (XEN) ACPI: RSDP 000FE020, 0024 (r2 INTEL ) >>> >>>> >> >>>> >> >> >> (XEN) ACPI: XSDT CF7FE120, 0074 (r1 INTEL DX58SO 11F6 1000013) >>> >>>> >> >>>> >> >> >> (XEN) ACPI: FACP CF7FD000, 00F4 (r3 INTEL DX58SO 11F6 MSFT 100000D) >>> >>>> >> >>>> >> >> >> (XEN) ACPI Warning (tbfadt-0444): Optional field "Pm2ControlBlock" has zero address or length: 0000000000000450/0 [20070126] >>> >>>> >> >>>> >> >> >> (XEN) ACPI: DSDT CF7F8000, 4641 (r2 INTEL DX58SO 11F6 MSFT 100000D) >>> >>>> >> >>>> >> >> >> (XEN) ACPI: FACS CF728000, 0040 >>> >>>> >> >>>> >> >> >> (XEN) ACPI: APIC CF7F7000, 0138 (r2 INTEL DX58SO 11F6 MSFT 100000D) >>> >>>> >> >>>> >> >> >> (XEN) ACPI: WDDT CF7F6000, 0040 (r1 INTEL DX58SO 11F6 MSFT 100000D) >>> >>>> >> >>>> >> >> >> (XEN) ACPI: MCFG CF7F5000, 003C (r1 INTEL DX58SO 11F6 MSFT 100000D) >>> >>>> >> >>>> >> >> >> (XEN) ACPI: ASF! CF7F4000, 00AC (r32 INTEL DX58SO 11F6 MSFT 100000D) >>> >>>> >> >>>> >> >> >> (XEN) ACPI: HPET CF7F3000, 0038 (r1 INTEL DX58SO 11F6 MSFT 100000D) >>> >>>> >> >>>> >> >> >> (XEN) ACPI: SSDT CF7E2000, E134 (r1 INTEL SSDT PM 11F6 MSFT 100000D) >>> >>>> >> >>>> >> >> >> (XEN) ACPI: DMAR CF7DF000, 0140 (r1 INTEL DX58SO 11F6 MSFT 100000D) >>> >>>> >> >>>> >> >> >> (XEN) ACPI: WDTT CF7F1000, 020C (r2 INTEL DX58SO 11F6 MSFT 100000D) >>> >>>> >> >>>> >> >> >> (XEN) ACPI: ASPT CF7F2000, 0034 (r4 INTEL PerfTune 11F6 MSFT 100000D) >>> >>>> >> >>>> >> >> >> (XEN) System RAM: 7950MB (8140820kB) >>> >>>> >> >>>> >> >> >> (XEN) Domain heap initialised >>> >>>> >> >>>> >> >> >> (XEN) Processor #0 7:10 APIC version 21 >>> >>>> >> >>>> >> >> >> (XEN) Processor #2 7:10 APIC version 21 >>> >>>> >> >>>> >> >> >> (XEN) Processor #4 7:10 APIC version 21 >>> >>>> >> >>>> >> >> >> (XEN) Processor #6 7:10 APIC version 21 >>> >>>> >> >>>> >> >> >> (XEN) Processor #1 7:10 APIC version 21 >>> >>>> >> >>>> >> >> >> (XEN) Processor #3 7:10 APIC version 21 >>> >>>> >> >>>> >> >> >> (XEN) Processor #5 7:10 APIC version 21 >>> >>>> >> >>>> >> >> >> (XEN) Processor #7 7:10 APIC version 21 >>> >>>> >> >>>> >> >> >> (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 >>> >>>> >> >>>> >> >> >> (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:679: Host address width 39 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = fe711000 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1b.0 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:398: dmaru->address = fe710000 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:340: IOAPIC: f0:1f.7 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:411: flags: INCLUDE_ALL >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e9000 end_address e9fff >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.1 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ea000 end_address eafff >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.2 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr eb000 end_address ebfff >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.0 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e6000 end_address e6fff >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.1 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e7000 end_address e7fff >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.2 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e8000 end_address e8fff >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]dmar.c:571: RMRR region: base_addr ec000 end_address eefff >>> >>>> >> >>>> >> >> >> (XEN) Using scheduler: SMP Credit Scheduler (credit) >>> >>>> >> >>>> >> >> >> (XEN) Detected 2800.125 MHz processor. >>> >>>> >> >>>> >> >> >> (XEN) Initing memory sharing. >>> >>>> >> >>>> >> >> >> (XEN) VMX: Supported advanced features: >>> >>>> >> >>>> >> >> >> (XEN) - APIC MMIO access virtualisation >>> >>>> >> >>>> >> >> >> (XEN) - APIC TPR shadow >>> >>>> >> >>>> >> >> >> (XEN) - Extended Page Tables (EPT) >>> >>>> >> >>>> >> >> >> (XEN) - Virtual-Processor Identifiers (VPID) >>> >>>> >> >>>> >> >> >> (XEN) - Virtual NMI >>> >>>> >> >>>> >> >> >> (XEN) - MSR direct-access bitmap >>> >>>> >> >>>> >> >> >> (XEN) HVM: ASIDs enabled. >>> >>>> >> >>>> >> >> >> (XEN) HVM: VMX enabled >>> >>>> >> >>>> >> >> >> (XEN) HVM: Hardware Assisted Paging detected. >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = fe711000 iommu->reg = ffff82c3fff57000 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c9008010e60262 ecap = f0207a >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address = fe710000 iommu->reg = ffff82c3fff56000 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap = c90780106f0462 ecap = f020fa >>> >>>> >> >>>> >> >> >> (XEN) Intel VT-d Snoop Control not supported. >>> >>>> >> >>>> >> >> >> (XEN) Intel VT-d DMA Passthrough not supported. >>> >>>> >> >>>> >> >> >> (XEN) Intel VT-d Queued Invalidation supported. >>> >>>> >> >>>> >> >> >> (XEN) Intel VT-d Interrupt Remapping supported. >>> >>>> >> >>>> >> >> >> (XEN) I/O virtualisation enabled >>> >>>> >> >>>> >> >> >> (XEN) I/O virtualisation for PV guests disabled >>> >>>> >> >>>> >> >> >> (XEN) Total of 8 processors activated. >>> >>>> >> >>>> >> >> >> (XEN) ENABLING IO-APIC IRQs >>> >>>> >> >>>> >> >> >> (XEN) -> Using new ACK method >>> >>>> >> >>>> >> >> >> (XEN) TSC is reliable, synchronization unnecessary >>> >>>> >> >>>> >> >> >> (XEN) Platform timer is 14.318MHz HPET >>> >>>> >> >>>> >> >> >> (XEN) Allocated console ring of 16 KiB. >>> >>>> >> >>>> >> >> >> (XEN) Brought up 8 CPUs >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:0.0 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.0 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:10.1 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.0 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.1 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:14.2 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:14.3 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:19.0 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.0 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.1 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.2 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.7 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:1b.0 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.0 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.1 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.2 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.7 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.0 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.2 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.3 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.5 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.0 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.1 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 2:0.2 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.0 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.1 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 4:0.2 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 5:0.0 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.0 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.1 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 7:0.2 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.0 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.1 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 9:0.2 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = a:0.0 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.0 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.1 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.2 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.3 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.4 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.5 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.6 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = b:3.7 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.0 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:0.1 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.0 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:2.1 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.0 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.1 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:3.4 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.0 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.1 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.2 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:4.3 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.0 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.1 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.2 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:5.3 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.0 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.1 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.2 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 3f:6.3 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = ffff82c3fff57000 >>> >>>> >> >>>> >> >> >> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = ffff82c3fff56000 >>> >>>> >> >>>> >> >> >> (XEN) *** LOADING DOMAIN 0 *** >>> >>>> >> >>>> >> >> >> (XEN) Xen kernel: 64-bit, lsb, compat32 >>> >>>> >> >>>> >> >> >> (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x26ae000 >>> >>>> >> >>>> >> >> >> (XEN) PHYSICAL MEMORY ARRANGEMENT: >>> >>>> >> >>>> >> >> >> (XEN) Dom0 alloc.: 0000000210000000->0000000220000000 >>> >>>> >> >>>> >> >> >> (XEN) VIRTUAL MEMORY ARRANGEMENT: >>> >>>> >> >>>> >> >> >> (XEN) Loaded kernel: ffffffff81000000->ffffffff826ae000 >>> >>>> >> >>>> >> >> >> (XEN) Init. ramdisk: ffffffff826ae000->ffffffff8f4de600 >>> >>>> >> >>>> >> >> >> (XEN) Phys-Mach map: ffffffff8f4df000->ffffffff8f55f000 >>> >>>> >> >>>> >> >> >> (XEN) Start info: ffffffff8f55f000->ffffffff8f55f4b4 >>> >>>> >> >>>> >> >> >> (XEN) Page tables: ffffffff8f560000->ffffffff8f5df000 >>> >>>> >> >>>> >> >> >> (XEN) Boot stack: ffffffff8f5df000->ffffffff8f5e0000 >>> >>>> >> >>>> >> >> >> (XEN) TOTAL: ffffffff80000000->ffffffff8f800000 >>> >>>> >> >>>> >> >> >> (XEN) ENTRY ADDRESS: ffffffff81a10860 >>> >>>> >> >>>> >> >> >> (XEN) Dom0 has maximum 1 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 \047CTRL-a\047 three times to switch input to Xen) >>> >>>> >> >>>> >> >> >> (XEN) Freed 164kB init memory. >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 pirq=0 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=2, irq=0 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000109f0 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=000009f0 pirq=0 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 3 already mapped >>> >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 4 already mapped >>> >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 5 already mapped >>> >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 6 already mapped >>> >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 7 already mapped >>> >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 8 already mapped >>> >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 9 already mapped >>> >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 10 already mapped >>> >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 11 already mapped >>> >>>> >> >>>> >> >> >> (XEN) irq.c:1445: dom0: pirq 0 or irq 12 already mapped >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=0, irq=0 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=000009f0 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=00010000 pirq=0 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=23, irq=23 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a929 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a929 pirq=23 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 pirq=16 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=16, irq=16 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9b0 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9b0 pirq=16 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=19, irq=19 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c8 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c8 pirq=19 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: apic=0, pin=18, irq=18 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=0001a9c0 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=0000a9c0 pirq=18 >>> >>>> >> >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> >>>> >> >>>> >> >> > >>> >>>> >> >>>> >> >> >> _______________________________________________ >>> >>>> >> >>>> >> >> >> Xen-users mailing list >>> >>>> >> >>>> >> >> >> Xen-users@lists.xensource.com >>> >>>> >> >>>> >> >> >> http://lists.xensource.com/xen-users >>> >>>> >> >>>> >> >> > >>> >>>> >> >>>> >> > >>> >>>> >> >>>> > >>> >>>> >> >>> >>> >>>> >> >> >>> >>>> >> > >>> >>>> > >>> >>> >>> > >>> > >>> > >>> > >>> > >>> > -- >>> > Best regards, >>> > Sander mailto:linux@eikelenboom.it >>> > >>> > >> -- Best regards, Sander mailto:linux@eikelenboom.it ^ permalink raw reply [flat|nested] 32+ messages in thread
![[-- Attachment #1.2: logo_signature.jpg --] [-- Type: image/jpeg, Size: 2634 bytes --]](../../AANLkTinK0dOHpcw9q91avrfn5kQFU42StrX2_OYsLNBS@mail.gmail.com/1.2-logo_signature.jpg){kind=link}
end of thread, other threads:[~2010-05-24 2:54 UTC | newest]
Thread overview: 32+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <AANLkTingpLEP-MzziwzAKBJfNCzIwPiExwJGsVvzy7Bb@mail.gmail.com>
[not found] ` <AANLkTimVFTsfWR62doUMZOIlMCVBAVJioscvRzUBbIPD@mail.gmail.com>
[not found] ` <20100513122939.GB17817@reaktio.net>
[not found] ` <AANLkTinCxjsORy7_LUAeZPQoGllg4TcVQeym9cf7rn5S@mail.gmail.com>
[not found] ` <20100513141417.GT17817@reaktio.net>
[not found] ` <AANLkTilIotxoc6GE22WGlInpcm1BJmj72QSumIPU4oR2@mail.gmail.com>
[not found] ` <20100513154728.GV17817@reaktio.net>
[not found] ` <AANLkTilQPnVdBEY8jSDWh-Y--vqugPDqGAE-k41IU_rB@mail.gmail.com>
[not found] ` <20100513175808.GD17817@reaktio.net>
[not found] ` <AANLkTimKlhHnJ70MSbtniRbj6EirU-0BnT259Smgv_rb@mail.gmail.com>
2010-05-13 18:10 ` [Xen-users] xen/stable-2.6.32.x compilation failure in do_hvm_suspend() Pasi Kärkkäinen
2010-05-13 18:22 ` Dan Magenheimer
2010-05-13 18:32 ` M A Young
2010-05-13 18:37 ` [Xen-devel] " chris
2010-05-13 18:44 ` Re: [Xen-users] " M A Young
2010-05-13 18:50 ` chris
2010-05-14 14:45 ` chris
[not found] ` <4BED8925.8010405@interface-tech.com>
2010-05-14 17:41 ` chris
2010-05-14 18:51 ` Pasi Kärkkäinen
2010-05-14 18:53 ` Pierre POMES
2010-05-14 19:15 ` Pasi Kärkkäinen
2010-05-14 19:43 ` [Xen-devel] " Pierre POMES
2010-05-13 18:28 ` [Xen-users] RE: Xen4 / Intel DX58SO Mobo / VT-d not working chris
2010-05-14 19:05 ` chris
2010-05-14 19:11 ` Pasi Kärkkäinen
2010-05-14 19:18 ` [Xen-users] " chris
2010-05-14 19:21 ` Pasi Kärkkäinen
2010-05-14 19:46 ` [Xen-users] " chris
2010-05-14 20:39 ` chris
2010-05-14 20:50 ` Pasi Kärkkäinen
2010-05-14 21:17 ` [Xen-users] " chris
2010-05-16 7:36 ` [Xen-devel] " Han, Weidong
2010-05-16 13:00 ` chris
2010-05-17 17:05 ` chris
2010-05-18 9:31 ` Re: [Xen-users] " Weidong Han
2010-05-21 19:41 ` chris
2010-05-24 2:54 ` [Xen-devel] " Weidong Han
2010-05-14 21:25 ` Re: [Xen-users] " Sander Eikelenboom
2010-05-14 21:26 ` chris
2010-05-14 21:34 ` Pasi Kärkkäinen
2010-05-14 21:57 ` chris
2010-05-15 6:56 ` Sander Eikelenboom
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).