search for: d32767

...@ 2.40GHz stepping 06 (XEN) Total of 2 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 (XEN) checking TSC synchronization across 2 CPUs: passed. (XEN) Platform timer is 14.318MHz HPET (XEN) microcode.c:73:d32767 microcode: CPU1 resumed (XEN) Brought up 2 CPUs (XEN) [VT-D]iommu.c:1692: Queued Invalidation hardware not found (XEN) [VT-D]iommu.c:1692: Queued Invalidation hardware not found (XEN) [VT-D]iommu.c:1692: Queued Invalidation hardware not found (XEN) [VT-D]iommu.c:1700: Interrupt Remapping hardware n...

...d. (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) checking TSC synchronization across 8 CPUs: passed. (XEN) Platform timer is 3.579MHz ACPI PM Timer (XEN) Brought up 8 CPUs (XEN) I/O virtualisation enabled (XEN) I/O virtualisation for PV guests disabled (XEN) [VT-D]iommu.c:1269:d32767 domain_context_mapping:invalid (XEN) [VT-D]iommu.c:1269:d32767 domain_context_mapping:invalid (XEN) [VT-D]iommu.c:1269:d32767 domain_context_mapping:invalid (XEN) [VT-D]iommu.c:1269:d32767 domain_context_mapping:invalid (XEN) [VT-D]iommu.c:1269:d32767 domain_context_mapping:invalid (XEN) [VT-D]iomm...

...d. (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) checking TSC synchronization across 8 CPUs: passed. (XEN) Platform timer is 3.579MHz ACPI PM Timer (XEN) Brought up 8 CPUs (XEN) I/O virtualisation enabled (XEN) I/O virtualisation for PV guests disabled (XEN) [VT-D]iommu.c:1269:d32767 domain_context_mapping:invalid (XEN) [VT-D]iommu.c:1269:d32767 domain_context_mapping:invalid (XEN) [VT-D]iommu.c:1269:d32767 domain_context_mapping:invalid (XEN) [VT-D]iommu.c:1269:d32767 domain_context_mapping:invalid (XEN) [VT-D]iommu.c:1269:d32767 domain_context_mapping:invalid (XEN) [VT-D]iomm...

...2.27GHz stepping 05 (XEN) Total of 16 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 (XEN) checking TSC synchronization across 16 CPUs: passed. (XEN) Platform timer is 14.318MHz HPET (XEN) microcode.c:73:d32767 microcode: CPU1 resumed (XEN) microcode.c:73:d32767 microcode: CPU9 resumed (XEN) microcode.c:73:d32767 microcode: CPU14 resumed (XEN) microcode.c:73:d32767 microcode: CPU3 resumed (XEN) microcode.c:73:d32767 microcode: CPU6 resumed (XEN) microcode.c:73:d32767 microcode: CPU15 resumed (XEN) microco...

...2.27GHz stepping 05 (XEN) Total of 16 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 (XEN) checking TSC synchronization across 16 CPUs: passed. (XEN) Platform timer is 14.318MHz HPET (XEN) microcode.c:73:d32767 microcode: CPU1 resumed (XEN) microcode.c:73:d32767 microcode: CPU9 resumed (XEN) microcode.c:73:d32767 microcode: CPU14 resumed (XEN) microcode.c:73:d32767 microcode: CPU3 resumed (XEN) microcode.c:73:d32767 microcode: CPU6 resumed (XEN) microcode.c:73:d32767 microcode: CPU15 resumed (XEN) microco...

Hi, I installed Xen 4.0.1 from source on Debian 5.0.8 and when boot my computer hardware reboots at like "Scrubbing Free RAM". I tryed to find some information here but none was helpfull to me. Anyone? I have 4GB memory and a AMD Turion II X2 M500 (

...APIC timer ... (XEN) ..... CPU clock speed is 2659.9553 MHz. (XEN) ..... host bus clock speed is 132.9977 MHz. (XEN) ..... bus_scale = 0x00008834 (XEN) TSC is reliable, synchronization unnecessary (XEN) Platform timer is 14.318MHz HPET ?(XEN) Allocated console ring of 256 KiB. (XEN) microcode.c:73:d32767 microcode: CPU1 resumed (XEN) microcode.c:73:d32767 microcode: CPU13 resumed (XEN) microcode.c:73:d32767 microcode: CPU23 resumed (XEN) microcode.c:73:d32767 microcode: CPU21 resumed (XEN) microcode.c:73:d32767 microcode: CPU9 resumed (XEN) microcode.c:73:d32767 microcode: CPU22 resumed (XEN) micro...

...le = 0x0000CCD7 (XEN) TSC is reliable, synchronization unnecessary (XEN) Platform timer appears to have unexpectedly wrapped 10 or more times. (XEN) Platform timer is 14.318MHz HPET ÿ(XEN) Allocated console ring of 128 KiB. (XEN) do_IRQ: 1.231 No irq handler for vector (irq -1) (XEN) microcode.c:73:d32767 microcode: CPU1 resumed (XEN) do_IRQ: 2.231 No irq handler for vector (irq -1) (XEN) microcode.c:73:d32767 microcode: CPU2 resumed (XEN) do_IRQ: 3.231 No irq handler for vector (irq -1) (XEN) microcode.c:73:d32767 microcode: CPU3 resumed (XEN) do_IRQ: 4.231 No irq handler for vector (irq -1) (XEN)...

Hello, I have some diagnostic Info for you. Tried to get xen-4.0.1 working on another node of my cluster. Only difference: Newer revision of the Hardware. Exactly same Software Stack. Stack: Ubuntu Lucid 64bit, xen-4.0.1 from Source, selfbuilt linux-2.6.32.27 from xen/stable-2.6.32.x Nodes working: HP DL380G5 16GB (Intel X5460) Node not working: HP DL380G6 16GB (Intel X5550) Effect: Xen

Hi developers, I met some domU issues and the log suggests missing interrupt. Details from here: http://www.gossamer-threads.com/lists/xen/users/263938#263938 In summary, this is the suspicious log: (XEN) vmsi.c:122:d32767 Unsupported delivery mode 3 I''ve checked the code in question and found that mode 3 is an ''reserved_1'' mode. I want to trace down the source of this mode setting to root-cause the issue. But I''m not an xen developer, and am even a newbie as a xen user. Could any...

I''ve seen a recent report claiming that it works: http://linux-bsd-sharing.blogspot.pt/2012/10/howto-xen-413-windows-8-hvm-domu-with.html However, in my case, with a slightly different HW configuration the story is totally different. :-（ My config: HW: I7-3770 + AsRock H77M-ITX board Dom0: Debian Wheezy stock xen (v4.1.3) + Debian stock kernel (3.2.x / 3.6.x) 64 bit version. Note that

Hi Everyone I have sorted out the initial issues I''ve had and decided to give Xen another go. I''m trying to run Xen using kernel 2.6.37-rc3 (previous attempt with rc1 failed, and when I gave it a second go, rc3 was already out). As previously, 2.6.37-rc3 boots fine natively. 2.6.32 boots natively and under Xen as dom0, but I have reservations against running 2.6.32,

Hi Everyone I have sorted out the initial issues I''ve had and decided to give Xen another go. I''m trying to run Xen using kernel 2.6.37-rc3 (previous attempt with rc1 failed, and when I gave it a second go, rc3 was already out). As previously, 2.6.37-rc3 boots fine natively. 2.6.32 boots natively and under Xen as dom0, but I have reservations against running 2.6.32,

...p_one_2:bdf = 0:2:0 (XEN) intel-iommu.c:1186:d0 domain_context_mapping:PCI: bdf = 0:2:0 (XEN) domctl.c:552:d0 XEN_DOMCTL_assign_device: bdf = 0:2:0 (XEN) io.c:115:d0 XEN_DOMCTL_irq_mapping: m_irq = 14 device = 2 intx = 0 (XEN) io.c:157:d0 hvm_dpci_eoi:: device 2 intx 0 (XEN) io.c:157:d32767 hvm_dpci_eoi:: device 2 intx 0 (XEN) io.c:157:d32767 hvm_dpci_eoi:: device 2 intx 0 (XEN) HVM1: HVM Loader (XEN) HVM1: Detected Xen v3.2-unstable (XEN) HVM1: Writing SMBIOS tables ... (XEN) HVM1: Loading ROMBIOS ... (XEN) HVM1: 8972 bytes of ROMBIOS high-memory extensions: (XEN...

...=f7c40 nr=4 (XEN) irq.c:270: Dom14 PCI link 0 changed 5 -> 0 (XEN) irq.c:270: Dom14 PCI link 1 changed 10 -> 0 (XEN) irq.c:270: Dom14 PCI link 2 changed 11 -> 0 (XEN) irq.c:270: Dom14 PCI link 3 changed 5 -> 0 (XEN) irq.c:2234: dom14: pirq 51 or emuirq 23 already mapped (XEN) vmsi.c:108:d32767 Unsupported delivery mode 3 (XEN) emulate.c:88:d14 bad mmio size 16 (XEN) io.c:199:d14 MMIO emulation failed @ 0033:7fa98cc628b4: 66 0f 7f 0f 0f 28 56 10 0f 29 (XEN) stdvga.c:147:d14 entering stdvga and caching modes (XEN) stdvga.c:151:d14 leaving stdvga (XEN) emulate.c:88:d14 bad mmio size 16 (XEN...

...N) Enabled directed EOI with ioapic_ack_old on! (XEN) Total of 4 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) -> Using old ACK method (XEN) TSC is reliable, synchronization unnecessary (XEN) Platform timer is 14.318MHz HPET (XEN) Allocated console ring of 16 KiB. (XEN) microcode.c:73:d32767 microcode: CPU1 resumed (XEN) microcode.c:73:d32767 microcode: CPU3 resumed (XEN) Brought up 4 CPUs (XEN) microcode.c:73:d32767 microcode: CPU2 resumed (XEN) Created cpupool 0 with scheduler SMP Credit Scheduler (credit) (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:0.0 (XEN) [VT-D]iommu.c:1332: d0...

...st bus clock speed is 132.9995 MHz. (XEN) ..... bus_scale = 0x00008834 (XEN) TSC is reliable, synchronization unnecessary (XEN) Platform timer appears to have unexpectedly wrapped 10 or more times. (XEN) Platform timer is 14.318MHz HPET ?(XEN) Allocated console ring of 128 KiB. (XEN) microcode.c:73:d32767 microcode: CPU1 resumed (XEN) microcode.c:73:d32767 microcode: CPU11 resumed (XEN) microcode.c:73:d32767 microcode: CPU8 resumed (XEN) microcode.c:73:d32767 microcode: CPU9 resumed (XEN) microcode.c:73:d32767 microcode: CPU7 resumed (XEN) microcode.c:73:d32767 microcode: CPU5 resumed (XEN) microcod...

Hi- I am trying to pass an LSI SAS2008-based HBA (IBM M1015) through to an HVM Solaris VM, using Xen 4.2 unstable and the qemu-traditional device model. On boot I see the following error: MPT BIOS Fault 09h encountered at adapter PCI(00h,05h,00h) A list search yielded (http://comments.gmane.org/gmane.comp.emulators.xen.devel/128172), however there was no solution for an HVM VM. I''ve

...s maximum 4 VCPUs (XEN) Scrubbing Free RAM: ........................................................................................................................................................................................................................................done. (XEN) trace.c:89:d32767 calc_tinfo_first_offset: NR_CPUs 128, offset_in_bytes 258, t_info_first_offset 65 (XEN) Xen trace buffers: disabled (XEN) Std. Loglevel: All (XEN) Guest Loglevel: All (XEN) Xen is relinquishing VGA console. (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xe...

Xen 3.4 xen-unstable.hg from yesterday with debian etch on 64bit arch Intel/Lenovo Q35 Mainboard with VT-d enabled Bootoptions iommu=1 vtd=1 pci.backhide for a PCI-E nvidia graphiccard xm dmesg Error messages includes: [VT-D] iommu.c: 1694:d32767 iommu: mapping reserved region failed [VT-D] iommu.c: 1542:d0 intel_iommu_add_device: context mapping failed If i try to start my HVM by xm create win2k the system reboots any ideas? -- stefan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com...