From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Subject: Re: RE: Xen4 / Intel DX58SO Mobo / VT-d not working Date: Fri, 14 May 2010 22:11:07 +0300 Message-ID: <20100514191107.GD17817@reaktio.net> References: <20100513122939.GB17817@reaktio.net> <20100513141417.GT17817@reaktio.net> <20100513154728.GV17817@reaktio.net> <20100513175808.GD17817@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xensource.com Errors-To: xen-users-bounces@lists.xensource.com To: chris Cc: Xen-Devel List , Xen-Users List List-Id: xen-devel@lists.xenproject.org On Fri, May 14, 2010 at 03:05:49PM -0400, chris wrote: > Pasi, >=20 > 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 :( >=20 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 GN= U/Linux >=20 > test-box2:~# xm info | grep virt_caps > virt_caps : hvm hvm_directio >=20 > test-box2:~# xm pci-list-assignable-devices > 0000:02:00.0 > 0000:02:00.1 > 0000:02:00.2 >=20 > 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=3D1,power_mgmt=3D0) >=20 > test-box2:~# cat /etc/xen/vm-five.cfg | grep -v '#' > kernel =3D '/usr/lib/xen/boot/hvmloader' > builder =3D 'hvm' > memory =3D '1792' > device_model=3D'/usr/lib/xen/bin/qemu-dm' > disk =3D [ 'phy:/dev/storage/vm-five,ioemu:hda,w', > 'phy:/dev/sr0,ioemu:hdc:cdrom,r' > ] > name =3D 'vm-five' > vif =3D ['type=3Dioemu, bridge=3Deth0, mac=3D00:16:3D:37:A1:42'] > boot=3D'dc' > cpus=3D'0-1' > vcpus=3D2 > acpi=3D1 > ahci=3D1 > vnc=3D1 > sdl=3D0 > timer_mode=3D1 > usb=3D1 > usbdevice=3D'tablet' > localtime=3D1 > pci =3D ['02:00.0','02:00.1','02:00.2'] >=20 > On Thu, May 13, 2010 at 2:28 PM, chris wrote: > > Forwarding to xen-devel. Can't seem to get VT-d working with xen4 fro= m > > 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=3Dverbose loglvl=3Dall guest_loglvl=3D= 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 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=E4rkk=E4inen = 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 t= ook were: > >>>> > >>>> # make clean distclean > >>>> # wget -O .config > >>>> "http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.10-p= vops-dom0-xen-stable-x86_64" > >>> > >>> You should do "make oldconfig" at this point. > >>> > >>>> # make -j8 bzImage > >>>> (blah blah) > >>>> =A0 LD =A0 =A0 =A0vmlinux.o > >>>> =A0 MODPOST vmlinux.o > >>>> WARNING: modpost: Found 7 section mismatch(es). > >>>> To see full details build your kernel with: > >>>> 'make CONFIG_DEBUG_SECTION_MISMATCH=3Dy' > >>>> =A0 GEN =A0 =A0 .version > >>>> =A0 CHK =A0 =A0 include/linux/compile.h > >>>> =A0 UPD =A0 =A0 include/linux/compile.h > >>>> =A0 CC =A0 =A0 =A0init/version.o > >>>> =A0 LD =A0 =A0 =A0init/built-in.o > >>>> =A0 LD =A0 =A0 =A0.tmp_vmlinux1 > >>>> drivers/built-in.o: In function `do_hvm_suspend': > >>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: undefined referen= ce > >>>> to `xenbus_suspend' > >>>> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: undefined referen= ce > >>>> to `xenbus_resume' > >>>> make: *** [.tmp_vmlinux1] Error 1 > >>>> > >>> > >>> Hmm.. weird. I wonder if something has changed recently or what's g= oing on in here.. > >>> > >>> -- Pasi > >>> > >>>> > >>>> On Thu, May 13, 2010 at 11:47 AM, Pasi K=E4rkk=E4inen wrote: > >>>> > On Thu, May 13, 2010 at 11:33:57AM -0400, chris wrote: > >>>> >> Successfully grabbed the sources and failed to build: > >>>> >> > >>>> >> =A0 LD =A0 =A0 =A0.tmp_vmlinux1 > >>>> >> drivers/built-in.o: In function `do_hvm_suspend': > >>>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:124: undefined refe= rence > >>>> >> to `xenbus_suspend' > >>>> >> /mnt/tmp/linux-2.6-xen/drivers/xen/manage.c:138: undefined refe= rence > >>>> >> 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=E4rkk=E4inen 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 d= etails 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=E4rkk=E4inen wrote: > >>>> >> >> > On Wed, May 12, 2010 at 08:41:34PM -0400, chris wrote: > >>>> >> >> >> When reading the vtdhowto I noticed the ability to set io= mmu=3Dverbose. > >>>> >> >> >> Here is that output, I don't know if it helps at all to f= igure 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 a= nd see if that makes a difference.. > >>>> >> >> > > >>>> >> >> > -- Pasi > >>>> >> >> > > >>>> >> >> >> > >>>> >> >> >> ---------- Forwarded message ---------- > >>>> >> >> >> From: chris > >>>> >> >> >> Date: Wed, May 12, 2010 at 5:28 PM > >>>> >> >> >> Subject: Xen4 / Intel DX58SO Mobo / VT-d not working > >>>> >> >> >> To: Xen-Users List > >>>> >> >> >> > >>>> >> >> >> > >>>> >> >> >> Hello, > >>>> >> >> >> > >>>> >> >> >> I've previously been successful with Xen4 and VT-d on oth= er systems. I > >>>> >> >> >> am having trouble getting VT-d passthrough working to a W= inXP domain > >>>> >> >> >> with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is ena= bled in bios, > >>>> >> >> >> xm info shows hvm_directio capability, I have iommu=3D1 s= et, I have the > >>>> >> >> >> devices bound to pciback on dom0 cmdline, xm > >>>> >> >> >> pci-list-assignable-devices shows the devices as assignab= le. When I > >>>> >> >> >> attempt to start the VM I get the error: > >>>> >> >> >> > >>>> >> >> >> Error: Failed to assign device to IOMMU > >>>> >> >> >> (0000:02:00.0@100,msitranslate=3D1,power_mgmt=3D0) > >>>> >> >> >> > >>>> >> >> >> 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 =A0 =A0 =A0 =A0 =A0 Xen 4.0.0 / Debian GNU/Linux, k= ernel 2.6.31.13 > >>>> >> >> >> root =A0 =A0 =A0 =A0 =A0 =A0(hd0,0) > >>>> >> >> >> kernel =A0 =A0 =A0 =A0 =A0/boot/xen-4.0.0.gz iommu=3D1 do= m0_mem=3D256M > >>>> >> >> >> dom0_max_vcpus=3D1 dom0_vcpus_pin=3Dtrue > >>>> >> >> >> module =A0 =A0 =A0 =A0 =A0/boot/vmlinuz-2.6.31.13 root=3D= /dev/md0 ro console=3Dtty0 > >>>> >> >> >> xen-pciback.permissive > >>>> >> >> >> xen-pciback.hide=3D(02:00.0)(02:00.1)(02:00.2)(04:00.0)(0= 4:00.1)(04:00.2)(07:00.0)(07:00.1)(07:00.2)(09:00.0)(09:00.1)(09:00.2) > >>>> >> >> >> module =A0 =A0 =A0 =A0 =A0/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 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 : test-box2 > >>>> >> >> >> release =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0: 2.6.31.13 > >>>> >> >> >> version =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0: #2 SMP Wed May 1= 2 14:11:37 EDT 2010 > >>>> >> >> >> machine =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0: x86_64 > >>>> >> >> >> nr_cpus =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0: 8 > >>>> >> >> >> nr_nodes =A0 =A0 =A0 =A0 =A0 =A0 =A0 : 1 > >>>> >> >> >> cores_per_socket =A0 =A0 =A0 : 4 > >>>> >> >> >> threads_per_core =A0 =A0 =A0 : 2 > >>>> >> >> >> cpu_mhz =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0: 2800 > >>>> >> >> >> hw_caps =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0: > >>>> >> >> >> bfebfbff:28100800:00000000:00001b40:0098e3bd:00000000:000= 00001:00000000 > >>>> >> >> >> virt_caps =A0 =A0 =A0 =A0 =A0 =A0 =A0: hvm hvm_directio > >>>> >> >> >> total_memory =A0 =A0 =A0 =A0 =A0 : 7950 > >>>> >> >> >> free_memory =A0 =A0 =A0 =A0 =A0 =A0: 7812 > >>>> >> >> >> node_to_cpu =A0 =A0 =A0 =A0 =A0 =A0: node0:0-7 > >>>> >> >> >> node_to_memory =A0 =A0 =A0 =A0 : node0:7812 > >>>> >> >> >> node_to_dma32_mem =A0 =A0 =A0: node0:3249 > >>>> >> >> >> max_node_id =A0 =A0 =A0 =A0 =A0 =A0: 0 > >>>> >> >> >> xen_major =A0 =A0 =A0 =A0 =A0 =A0 =A0: 4 > >>>> >> >> >> xen_minor =A0 =A0 =A0 =A0 =A0 =A0 =A0: 0 > >>>> >> >> >> xen_extra =A0 =A0 =A0 =A0 =A0 =A0 =A0: .0 > >>>> >> >> >> xen_caps =A0 =A0 =A0 =A0 =A0 =A0 =A0 : 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 =A0 =A0 =A0 =A0 =A0: credit > >>>> >> >> >> xen_pagesize =A0 =A0 =A0 =A0 =A0 : 4096 > >>>> >> >> >> platform_params =A0 =A0 =A0 =A0: virt_start=3D0xffff80000= 0000000 > >>>> >> >> >> xen_changeset =A0 =A0 =A0 =A0 =A0: unavailable > >>>> >> >> >> xen_commandline =A0 =A0 =A0 =A0: iommu=3D1 dom0_mem=3D256= M dom0_max_vcpus=3D1 > >>>> >> >> >> dom0_vcpus_pin=3Dtrue > >>>> >> >> >> cc_compiler =A0 =A0 =A0 =A0 =A0 =A0: gcc version 4.3.2 (D= ebian 4.3.2-1.1) > >>>> >> >> >> cc_compile_by =A0 =A0 =A0 =A0 =A0: root > >>>> >> >> >> cc_compile_domain =A0 =A0 =A0: > >>>> >> >> >> cc_compile_date =A0 =A0 =A0 =A0: Thu May =A06 13:41:25 ED= T 2010 > >>>> >> >> >> xend_config_format =A0 =A0 : 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=3D1,power_mgmt=3D0) > >>>> >> >> >> > >>>> >> >> >> 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 h= ave any idea > >>>> >> >> >> what might be wrong? > >>>> >> >> >> > >>>> >> >> >> - chris > >>>> >> >> > > >>>> >> >> >> =A0__ =A0__ =A0 =A0 =A0 =A0 =A0 =A0_ =A0_ =A0 =A0___ =A0 = ___ > >>>> >> >> >> =A0\ \/ /___ _ __ =A0 | || | =A0/ _ \ / _ \ > >>>> >> >> >> =A0 \ =A0// _ \ \047_ \ =A0| || |_| | | | | | | > >>>> >> >> >> =A0 / =A0\ =A0__/ | | | |__ =A0 _| |_| | |_| | > >>>> >> >> >> =A0/_/\_\___|_| |_| =A0 =A0|_|(_)___(_)___/ > >>>> >> >> >> > >>>> >> >> >> (XEN) Xen version 4.0.0 (root@) (gcc version 4.3.2 (Debia= n 4.3.2-1.1) ) Thu May =A06 13:41:25 EDT 2010 > >>>> >> >> >> (XEN) Latest ChangeSet: unavailable > >>>> >> >> >> (XEN) Command line: iommu=3Dverbose dom0_mem=3D256M dom0_= max_vcpus=3D1 dom0_vcpus_pin=3Dtrue > >>>> >> >> >> (XEN) Video information: > >>>> >> >> >> (XEN) =A0VGA is text mode 80x25, font 8x16 > >>>> >> >> >> (XEN) =A0VBE/DDC methods: none; EDID transfer time: 0 sec= onds > >>>> >> >> >> (XEN) =A0EDID info not retrieved because no DDC retrieval= method detected > >>>> >> >> >> (XEN) Disc information: > >>>> >> >> >> (XEN) =A0Found 2 MBR signatures > >>>> >> >> >> (XEN) =A0Found 2 EDD information structures > >>>> >> >> >> (XEN) Xen-e820 RAM map: > >>>> >> >> >> (XEN) =A00000000000000000 - 000000000008f000 (usable) > >>>> >> >> >> (XEN) =A0000000000008f000 - 0000000000090000 (reserved) > >>>> >> >> >> (XEN) =A00000000000090000 - 000000000009ec00 (usable) > >>>> >> >> >> (XEN) =A0000000000009ec00 - 00000000000a0000 (reserved) > >>>> >> >> >> (XEN) =A000000000000e0000 - 0000000000100000 (reserved) > >>>> >> >> >> (XEN) =A00000000000100000 - 00000000cf4bd000 (usable) > >>>> >> >> >> (XEN) =A000000000cf4bd000 - 00000000cf4bf000 (reserved) > >>>> >> >> >> (XEN) =A000000000cf4bf000 - 00000000cf4c2000 (usable) > >>>> >> >> >> (XEN) =A000000000cf4c2000 - 00000000cf7bf000 (ACPI NVS) > >>>> >> >> >> (XEN) =A000000000cf7bf000 - 00000000cf7df000 (usable) > >>>> >> >> >> (XEN) =A000000000cf7df000 - 00000000cf7ff000 (ACPI data) > >>>> >> >> >> (XEN) =A000000000cf7ff000 - 00000000cf800000 (usable) > >>>> >> >> >> (XEN) =A000000000cf800000 - 00000000d0000000 (reserved) > >>>> >> >> >> (XEN) =A000000000f8000000 - 00000000fd000000 (reserved) > >>>> >> >> >> (XEN) =A000000000ffe00000 - 0000000100000000 (reserved) > >>>> >> >> >> (XEN) =A00000000100000000 - 0000000230000000 (usable) > >>>> >> >> >> (XEN) ACPI: RSDP 000FE020, 0024 (r2 INTEL ) > >>>> >> >> >> (XEN) ACPI: XSDT CF7FE120, 0074 (r1 INTEL =A0DX58SO =A0 =A0= =A0 11F6 =A0 =A0 =A0 1000013) > >>>> >> >> >> (XEN) ACPI: FACP CF7FD000, 00F4 (r3 INTEL =A0DX58SO =A0 =A0= =A0 11F6 MSFT =A0100000D) > >>>> >> >> >> (XEN) ACPI Warning (tbfadt-0444): Optional field "Pm2Cont= rolBlock" has zero address or length: 0000000000000450/0 [20070126] > >>>> >> >> >> (XEN) ACPI: DSDT CF7F8000, 4641 (r2 INTEL =A0DX58SO =A0 =A0= =A0 11F6 MSFT =A0100000D) > >>>> >> >> >> (XEN) ACPI: FACS CF728000, 0040 > >>>> >> >> >> (XEN) ACPI: APIC CF7F7000, 0138 (r2 INTEL =A0DX58SO =A0 =A0= =A0 11F6 MSFT =A0100000D) > >>>> >> >> >> (XEN) ACPI: WDDT CF7F6000, 0040 (r1 INTEL =A0DX58SO =A0 =A0= =A0 11F6 MSFT =A0100000D) > >>>> >> >> >> (XEN) ACPI: MCFG CF7F5000, 003C (r1 INTEL =A0DX58SO =A0 =A0= =A0 11F6 MSFT =A0100000D) > >>>> >> >> >> (XEN) ACPI: ASF! CF7F4000, 00AC (r32 INTEL =A0DX58SO =A0 = =A0 =A0 11F6 MSFT =A0100000D) > >>>> >> >> >> (XEN) ACPI: HPET CF7F3000, 0038 (r1 INTEL =A0DX58SO =A0 =A0= =A0 11F6 MSFT =A0100000D) > >>>> >> >> >> (XEN) ACPI: SSDT CF7E2000, E134 (r1 INTEL =A0SSDT =A0PM =A0= =A0 11F6 MSFT =A0100000D) > >>>> >> >> >> (XEN) ACPI: DMAR CF7DF000, 0140 (r1 INTEL =A0DX58SO =A0 =A0= =A0 11F6 MSFT =A0100000D) > >>>> >> >> >> (XEN) ACPI: WDTT CF7F1000, 020C (r2 INTEL =A0DX58SO =A0 =A0= =A0 11F6 MSFT =A0100000D) > >>>> >> >> >> (XEN) ACPI: ASPT CF7F2000, 0034 (r4 INTEL =A0PerfTune =A0= =A0 11F6 MSFT =A0100000D) > >>>> >> >> >> (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 0xfec0000= 0, GSI 0-23 > >>>> >> >> >> (XEN) Enabling APIC mode: =A0Flat. =A0Using 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: =A0 dmaru->address =3D fe711000 > >>>> >> >> >> (XEN) [VT-D]dmar.c:334: =A0 endpoint: 0:1b.0 > >>>> >> >> >> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: > >>>> >> >> >> (XEN) [VT-D]dmar.c:398: =A0 dmaru->address =3D fe710000 > >>>> >> >> >> (XEN) [VT-D]dmar.c:340: =A0 IOAPIC: f0:1f.7 > >>>> >> >> >> (XEN) [VT-D]dmar.c:411: =A0 flags: INCLUDE_ALL > >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >>>> >> >> >> (XEN) [VT-D]dmar.c:334: =A0 endpoint: 0:1d.0 > >>>> >> >> >> (XEN) [VT-D]dmar.c:571: =A0 RMRR region: base_addr e9000 = end_address e9fff > >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >>>> >> >> >> (XEN) [VT-D]dmar.c:334: =A0 endpoint: 0:1d.1 > >>>> >> >> >> (XEN) [VT-D]dmar.c:571: =A0 RMRR region: base_addr ea000 = end_address eafff > >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >>>> >> >> >> (XEN) [VT-D]dmar.c:334: =A0 endpoint: 0:1d.2 > >>>> >> >> >> (XEN) [VT-D]dmar.c:571: =A0 RMRR region: base_addr eb000 = end_address ebfff > >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >>>> >> >> >> (XEN) [VT-D]dmar.c:334: =A0 endpoint: 0:1a.0 > >>>> >> >> >> (XEN) [VT-D]dmar.c:571: =A0 RMRR region: base_addr e6000 = end_address e6fff > >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >>>> >> >> >> (XEN) [VT-D]dmar.c:334: =A0 endpoint: 0:1a.1 > >>>> >> >> >> (XEN) [VT-D]dmar.c:571: =A0 RMRR region: base_addr e7000 = end_address e7fff > >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >>>> >> >> >> (XEN) [VT-D]dmar.c:334: =A0 endpoint: 0:1a.2 > >>>> >> >> >> (XEN) [VT-D]dmar.c:571: =A0 RMRR region: base_addr e8000 = end_address e8fff > >>>> >> >> >> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: > >>>> >> >> >> (XEN) [VT-D]dmar.c:334: =A0 endpoint: 0:1d.0 > >>>> >> >> >> (XEN) [VT-D]dmar.c:571: =A0 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) =A0- APIC MMIO access virtualisation > >>>> >> >> >> (XEN) =A0- APIC TPR shadow > >>>> >> >> >> (XEN) =A0- Extended Page Tables (EPT) > >>>> >> >> >> (XEN) =A0- Virtual-Processor Identifiers (VPID) > >>>> >> >> >> (XEN) =A0- Virtual NMI > >>>> >> >> >> (XEN) =A0- 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 =3D fe711000 iomm= u->reg =3D ffff82c3fff57000 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap =3D c9008010e60262 ecap =3D= f0207a > >>>> >> >> >> (XEN) [VT-D]iommu.c:1078: drhd->address =3D fe710000 iomm= u->reg =3D ffff82c3fff56000 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1080: cap =3D c90780106f0462 ecap =3D= 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) =A0-> 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 =3D 0:0.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 0:10.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 0:10.1 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf =3D 0:14.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf =3D 0:14.1 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf =3D 0:14.2 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 0:14.3 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 0:19.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 0:1a.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 0:1a.1 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 0:1a.2 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 0:1a.7 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf =3D 0:1b.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 0:1d.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 0:1d.1 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 0:1d.2 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 0:1d.7 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 0:1f.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 0:1f.2 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 0:1f.3 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 0:1f.5 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 2:0.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 2:0.1 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 2:0.2 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 4:0.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 4:0.1 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 4:0.2 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf =3D 5:0.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 7:0.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 7:0.1 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 7:0.2 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 9:0.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 9:0.1 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 9:0.2 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf =3D a:0.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D b:3.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D b:3.1 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D b:3.2 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D b:3.3 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D b:3.4 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D b:3.5 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D b:3.6 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D b:3.7 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 3f:0.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 3f:0.1 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 3f:2.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 3f:2.1 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 3f:3.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 3f:3.1 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 3f:3.4 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 3f:4.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 3f:4.1 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 3f:4.2 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 3f:4.3 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 3f:5.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 3f:5.1 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 3f:5.2 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 3f:5.3 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 3f:6.0 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 3f:6.1 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 3f:6.2 > >>>> >> >> >> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf =3D 3f:6.3 > >>>> >> >> >> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu-= >reg =3D ffff82c3fff57000 > >>>> >> >> >> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu-= >reg =3D ffff82c3fff56000 > >>>> >> >> >> (XEN) *** LOADING DOMAIN 0 *** > >>>> >> >> >> (XEN) =A0Xen =A0kernel: 64-bit, lsb, compat32 > >>>> >> >> >> (XEN) =A0Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -= > 0x26ae000 > >>>> >> >> >> (XEN) PHYSICAL MEMORY ARRANGEMENT: > >>>> >> >> >> (XEN) =A0Dom0 alloc.: =A0 0000000210000000->0000000220000= 000 > >>>> >> >> >> (XEN) VIRTUAL MEMORY ARRANGEMENT: > >>>> >> >> >> (XEN) =A0Loaded kernel: ffffffff81000000->ffffffff826ae00= 0 > >>>> >> >> >> (XEN) =A0Init. ramdisk: ffffffff826ae000->ffffffff8f4de60= 0 > >>>> >> >> >> (XEN) =A0Phys-Mach map: ffffffff8f4df000->ffffffff8f55f00= 0 > >>>> >> >> >> (XEN) =A0Start info: =A0 =A0ffffffff8f55f000->ffffffff8f5= 5f4b4 > >>>> >> >> >> (XEN) =A0Page tables: =A0 ffffffff8f560000->ffffffff8f5df= 000 > >>>> >> >> >> (XEN) =A0Boot stack: =A0 =A0ffffffff8f5df000->ffffffff8f5= e0000 > >>>> >> >> >> (XEN) =A0TOTAL: =A0 =A0 =A0 =A0 ffffffff80000000->fffffff= f8f800000 > >>>> >> >> >> (XEN) =A0ENTRY 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 w= arnings) > >>>> >> >> >> (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=3D0, pin=3D0, irq=3D0 > >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=3D000109f0 > >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=3D00010000 pirq=3D0 > >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin f= or in-use IRQ! > >>>> >> >> >> (XEN) ioapic_guest_write: apic=3D0, pin=3D2, irq=3D0 > >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=3D000109f0 > >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=3D000009f0 pirq=3D0 > >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin f= or 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=3D0, pin=3D0, irq=3D0 > >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=3D000009f0 > >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=3D00010000 pirq=3D0 > >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin f= or in-use IRQ! > >>>> >> >> >> (XEN) ioapic_guest_write: apic=3D0, pin=3D18, irq=3D18 > >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=3D0001a9c0 > >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=3D0000a9c0 pirq=3D18 > >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin f= or in-use IRQ! > >>>> >> >> >> (XEN) ioapic_guest_write: apic=3D0, pin=3D19, irq=3D19 > >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=3D0001a9c8 > >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=3D0000a9c8 pirq=3D19 > >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin f= or in-use IRQ! > >>>> >> >> >> (XEN) ioapic_guest_write: apic=3D0, pin=3D23, irq=3D23 > >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=3D0001a929 > >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=3D0000a929 pirq=3D23 > >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin f= or in-use IRQ! > >>>> >> >> >> (XEN) ioapic_guest_write: apic=3D0, pin=3D19, irq=3D19 > >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=3D0001a9c8 > >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=3D0000a9c8 pirq=3D19 > >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin f= or in-use IRQ! > >>>> >> >> >> (XEN) ioapic_guest_write: apic=3D0, pin=3D18, irq=3D18 > >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=3D0001a9c0 > >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=3D0000a9c0 pirq=3D18 > >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin f= or in-use IRQ! > >>>> >> >> >> (XEN) ioapic_guest_write: apic=3D0, pin=3D16, irq=3D16 > >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=3D0001a9b0 > >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=3D0000a9b0 pirq=3D16 > >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin f= or in-use IRQ! > >>>> >> >> >> (XEN) ioapic_guest_write: apic=3D0, pin=3D16, irq=3D16 > >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=3D0001a9b0 > >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=3D0000a9b0 pirq=3D16 > >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin f= or in-use IRQ! > >>>> >> >> >> (XEN) ioapic_guest_write: apic=3D0, pin=3D19, irq=3D19 > >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=3D0001a9c8 > >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=3D0000a9c8 pirq=3D19 > >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin f= or in-use IRQ! > >>>> >> >> >> (XEN) ioapic_guest_write: apic=3D0, pin=3D18, irq=3D18 > >>>> >> >> >> (XEN) ioapic_guest_write: new_entry=3D0001a9c0 > >>>> >> >> >> (XEN) ioapic_guest_write: old_entry=3D0000a9c0 pirq=3D18 > >>>> >> >> >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin f= or in-use IRQ! > >>>> >> >> > > >>>> >> >> >> _______________________________________________ > >>>> >> >> >> Xen-users mailing list > >>>> >> >> >> Xen-users@lists.xensource.com > >>>> >> >> >> http://lists.xensource.com/xen-users > >>>> >> >> > > >>>> >> > > >>>> > > >>> > >> > >