|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] RE: Xen4 / Intel DX58SO Mobo / VT-d not working
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@xxxxxxxxx> 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@xxxxxx> 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@xxxxxx> 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@xxxxxxxxx> 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@xxxxxxxxx> 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@xxxxxx> > >>> >> >> 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@xxxxxx> > >>> >> >>>> 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@xxxxxx> 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@xxxxxx> 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@xxxxxxxxx> > >>> >> >>>> >> >> >> Date: Wed, May 12, 2010 at 5:28 PM > >>> >> >>>> >> >> >> Subject: Xen4 / Intel DX58SO Mobo / VT-d not working > >>> >> >>>> >> >> >> To: Xen-Users List <xen-users@xxxxxxxxxxxxxxxxxxx> > >>> >> >>>> >> >> >> > >>> >> >>>> >> >> >> > >>> >> >>>> >> >> >> 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@xxxxxxxxxxxxxxxxxxx > >>> >> >>>> >> >> >> http://lists.xensource.com/xen-users > >>> >> >>>> >> >> > > >>> >> >>>> >> > > >>> >> >>>> > > >>> >> >>> > >>> >> >> > >>> >> > > >>> > > >> > > _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |
