search for: ioapic_ack_old

...wrote: > So it seems like dom0 is unable to (correctly) bind to some hardware > interrupts. I wonder if these messages from Xen's dmesg are relevant. > (XEN) Not enabling x2APIC: depends on iommu_supports_eim. > (XEN) I/O virtualisation disabled > (XEN) Enabled directed EOI with ioapic_ack_old on! The last one certainly isn't, and the first two shouldn't (albeit the non-Xen kernel is running in x2APIC mode). That difference is likely because the Xen and non-Xen boots are with differing BIOS configurations, or on different machines: The non-Xen boot shows a DMAR ACPI table, while...

...de clear that even you cant do a lot about it you still collect details. CPU Intel Core i7 X980 Mainboard Asus P6T WS Professional (X58/LGA1333)(bios 1207) rev. 1.01G I also have two other questions (last time I was testing Xen it was back in ''06). A) (XEN) Enabled directed EOI with ioapic_ack_old on! (XEN) ENABLING IO-APIC IRQs (XEN) -> Using old ACK method What does this mean? B) When the hypervisor tries to load my DOM0 it takes a long time until it continues the boot process (it hangs somewhere after freeing unused memory (loaded the initrd)) - what could that be? I append my dme...

...it seems like dom0 is unable to (correctly) bind to some hardware >> interrupts. I wonder if these messages from Xen's dmesg are relevant. >> (XEN) Not enabling x2APIC: depends on iommu_supports_eim. >> (XEN) I/O virtualisation disabled >> (XEN) Enabled directed EOI with ioapic_ack_old on! > > The last one certainly isn't, and the first two shouldn't (albeit the > non-Xen kernel is running in x2APIC mode). That difference is likely > because the Xen and non-Xen boots are with differing BIOS > configurations, or on different machines: The non-Xen boot shows...

Hello I have Debian Linux 2.6.32-5-xen-amd64 Xen 4.0.1, 2 SAS drives in RAID 1, 16GB ram. I have virtualized Windows 2003R2 32bit where you install the latest version 0.11.0.295 gplpv After reading and reading forums and post testing, I noticed that the hard disk performance drops significantly when I assign the windows domU 9GB ram. (below I leave the config files) If I run the

...it seems like dom0 is unable to (correctly) bind to some hardware >> interrupts. I wonder if these messages from Xen's dmesg are relevant. >> (XEN) Not enabling x2APIC: depends on iommu_supports_eim. >> (XEN) I/O virtualisation disabled >> (XEN) Enabled directed EOI with ioapic_ack_old on! > The last one certainly isn't, and the first two shouldn't (albeit the > non-Xen kernel is running in x2APIC mode). That difference is likely > because the Xen and non-Xen boots are with differing BIOS > configurations, or on different machines: The non-Xen boot shows >...

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3+deb7u1 Severity: important Dear Maintainer, Just upgraded a Supermicro server (X9SCM-F motherboard) from Squeeze to Wheezy. And now the IPMI serial console no longer work as it used to. It hangs like this: [...] (XEN) Enabled directed EOI with ioapic_ack_old on! (XEN) ENABLING IO-APIC IRQs (XEN) -> Using old ACK method (XEN) Platform timer is 14.318MHz HPET ( Xen cmdline: placeholder dom0_max_vcpus=2 dom0_vcpus_pin dom0_mem=2048M com1=115200,8n1,0x3e8,4 console=com1,vga Linux cmdline: placeholder root=/dev/mapper/vg01-root ro console=hvc0 earlypr...

...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) 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) Brought up 4 CPUs (XEN) [VT-D]iommu.c:818: iommu_fault_status: Faul Yes, they stop like that....

...-d Dom0 DMA Passthrough not enabled. > (XEN) Intel VT-d Queued Invalidation enabled. > (XEN) Intel VT-d Interrupt Remapping enabled. > (XEN) Intel VT-d Shared EPT tables not enabled. > (XEN) I/O virtualisation enabled > (XEN) - Dom0 mode: Relaxed > (XEN) Enabled directed EOI with ioapic_ack_old on! > (XEN) ENABLING IO-APIC IRQs > (XEN) -> Using old ACK method > (XEN) Platform timer is 14.318MHz HPET > (XEN) Allocated console ring of 16 KiB. > (XEN) VMX: Supported advanced features: > (XEN) - APIC MMIO access virtualisation > (XEN) - APIC TPR shadow > (XEN) -...

...ted Paging detected. (XEN) Intel VT-d Snoop Control 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) - Dom0 mode: Relaxed (XEN) Enabled directed EOI with ioapic_ack_old on! (XEN) Total of 16 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 32 KiB. (XEN) Brought up 16 CPUs (XEN) *** LOADING DOMAIN 0 *** (XEN)...

...its: 24 GSI, 760 MSI/MSI-X (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Detected 3093.046 MHz processor. (XEN) Initing memory sharing. (XEN) mce_intel.c:1162: MCA Capability: BCAST 1 SER 0 CMCine check reporting enabled (XEN) I/O virtualisation disabled (XEN) Enabled directed EOI with ioapic_ack_old on! (XEN) ENABLING IO-APIC IRQs (XEN) -> Using old ACK method (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 (XEN) TSC deadline timer enabled (XEN) Platform timer is 14.318MHz HPET (XEN) Allocated console ring of 32 KiB. (XEN) VMX: Supported advanced features: (XEN) - Extended Page...

...eems like dom0 is unable to (correctly) bind to some hardware > > interrupts. I wonder if these messages from Xen's dmesg are relevant. > > (XEN) Not enabling x2APIC: depends on iommu_supports_eim. > > (XEN) I/O virtualisation disabled > > (XEN) Enabled directed EOI with ioapic_ack_old on! > > The last one certainly isn't, and the first two shouldn't (albeit the > non-Xen kernel is running in x2APIC mode). That difference is likely > because the Xen and non-Xen boots are with differing BIOS > configurations, or on different machines: The non-Xen boot shows...

Hello All! I have a new OpenSuse 12.2 (with 3.4.33-2.24-xen kernel) + Xen 4.1.3 install on an IBM x3550 server. The system is booted via EFI with Grub2 bootloader and it boots up normally, either with or without Xen. But i have one trouble with it: I can''t get console access working with Xen. The strange thing is, despite the "WARNING: no console will be available to

...tel VT-d Queued Invalidation enabled. > > > (XEN) Intel VT-d Interrupt Remapping enabled. > > > (XEN) Intel VT-d Shared EPT tables not enabled. > > > (XEN) I/O virtualisation enabled > > > (XEN) - Dom0 mode: Relaxed > > > (XEN) Enabled directed EOI with ioapic_ack_old on! > > > (XEN) ENABLING IO-APIC IRQs > > > (XEN) -> Using old ACK method > > > (XEN) Platform timer is 14.318MHz HPET > > > (XEN) Allocated console ring of 16 KiB. > > > (XEN) VMX: Supported advanced features: > > > (XEN) - APIC MMIO acces...

...op Control enabled. (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. (XEN) Intel VT-d Queued Invalidation enabled. (XEN) Intel VT-d Interrupt Remapping enabled. (XEN) Intel VT-d Shared EPT tables enabled. (XEN) I/O virtualisation enabled (XEN) - Dom0 mode: Relaxed (XEN) Enabled directed EOI with ioapic_ack_old on! (XEN) ENABLING IO-APIC IRQs (XEN) -> Using old ACK method (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 (XEN) TSC deadline timer enabled (XEN) Platform timer is 14.318MHz HPET (XEN) Defaulting to alternative key handling; send ''A'' to switch to normal mode. (XE...

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

...t: using cntxt_size: 0x340 and states: 00000000:00000007 (XEN) Intel machine check reporting enabled on CPU#0. (XEN) CPU0: Thermal monitoring enabled (TM1) (XEN) I/O virtualisation disabled (XEN) CPU0: Intel Genuine Intel(R) CPU 0 @ 1.60GHz stepping 01 (XEN) Enabled directed EOI with ioapic_ack_old on! (XEN) Booting processor 1/2 eip 8c000 (XEN) Initializing CPU#1 (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K (XEN) CPU: L2 cache: 256K (XEN) CPU: L3 cache: 20480K (XEN) CPU: Physical Processor ID: 0 (XEN) CPU: Processor Core ID: 1 (XEN) HVM: ASIDs enabled. (XEN) xsave_init: cpu1: cntxt_max_size:...

...tended MCE MSR 0 (XEN) Intel machine check reporting enabled (XEN) PCI: MCFG configuration 0: base f8000000 segment 0000 buses 00 - 3f (XEN) PCI: MCFG area at f8000000 reserved in E820 (XEN) PCI: Using MCFG for segment 0000 bus 00-3f (XEN) I/O virtualisation disabled (XEN) Enabled directed EOI with ioapic_ack_old on! (XEN) ENABLING IO-APIC IRQs (XEN) -> Using old ACK method (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 (XEN) TSC deadline timer enabled (XEN) Platform timer is 14.318MHz HPET (XEN) Allocated console ring of 64 KiB. (XEN) mwait-idle: MWAIT substates: 0x1120 (XEN) mwait-idle: v0...

...ol not enabled. (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. (XEN) Intel VT-d Queued Invalidation enabled. (XEN) Intel VT-d Interrupt Remapping enabled. (XEN) Intel VT-d Shared EPT tables not enabled. (XEN) I/O virtualisation enabled (XEN) - Dom0 mode: Relaxed (XEN) Enabled directed EOI with ioapic_ack_old on! (XEN) ENABLING IO-APIC IRQs (XEN) -> Using old ACK method (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 (XEN) TSC deadline timer enabled (XEN) [2012-06-17 00:22:20] Platform timer is 14.318MHz HPET (XEN) [2012-06-17 00:22:20] Allocated console ring of 32 KiB. (XEN) [2012-06-17...

...t enabled. (XEN) I/O virtualisation enabled (XEN) - Dom0 mode: Relaxed (XEN) apic_rdmsr(0x20) = 0x0 (XEN) apic_rdmsr(0x30) = 0x1060015 (XEN) Getting VERSION: 1060015 (XEN) apic_rdmsr(0x30) = 0x1060015 (XEN) Getting VERSION: 1060015 (XEN) apic_rdmsr(0x30) = 0x1060015 (XEN) Enabled directed EOI with ioapic_ack_old on! (XEN) apic_rdmsr(0x20) = 0x0 (XEN) Getting ID: 0 (XEN) apic_rdmsr(0x350) = 0x700 (XEN) Getting LVT0: 700 (XEN) apic_rdmsr(0x360) = 0x400 (XEN) Getting LVT1: 400 (XEN) apic_rdmsr(0x30) = 0x1060015 (XEN) apic_rdmsr(0x20) = 0x0 (XEN) apic_rdmsr(0xd0) = 0x1 (XEN) apic_wrmsr (0x80,0x10) (XEN) apic_r...

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3 Severity: grave Justification: causes non-serious data loss -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash