search for: cpu13

...160] xen-acpi-processor: (CX): Hypervisor error (-22) for ACPI CPU10 [ 32.728164] xen-acpi-processor: (CX): Hypervisor error (-22) for ACPI CPU11 [ 32.728168] xen-acpi-processor: (CX): Hypervisor error (-22) for ACPI CPU12 [ 32.728172] xen-acpi-processor: (CX): Hypervisor error (-22) for ACPI CPU13 [ 32.728176] xen-acpi-processor: (CX): Hypervisor error (-22) for ACPI CPU14 xl dmesg: (XEN) Monitor-Mwait will be used to enter C1 state (XEN) Monitor-Mwait will be used to enter C3 state (XEN) no cpu_id for acpi_id 8 (XEN) no cpu_id for acpi_id 9 (XEN) no cpu_id for acpi_id 10 (XEN) no cpu_...

...U0 -> NODE0 (XEN) CPU1 -> NODE1 (XEN) CPU2 -> NODE0 (XEN) CPU3 -> NODE1 (XEN) CPU4 -> NODE0 (XEN) CPU5 -> NODE1 (XEN) CPU6 -> NODE0 (XEN) CPU7 -> NODE1 (XEN) CPU8 -> NODE0 (XEN) CPU9 -> NODE1 (XEN) CPU10 -> NODE0 (XEN) CPU11 -> NODE1 (XEN) CPU12 -> NODE0 (XEN) CPU13 -> NODE1 (XEN) CPU14 -> NODE0 (XEN) CPU15 -> NODE1 CPU-to-node mapping for Xen 4.1-unstable (xen_changeset:Mon Oct 18 17:40:08 2010 +0100 22262:c0a39dbc624d): (XEN) *** Serial input -> Xen (type ''CTRL-a'' three times to switch input to DOM0) (XEN) ''u'...

...ping 05 (XEN) Booting processor 13/21 eip 8c000 (XEN) Initializing CPU#13 (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K (XEN) CPU: L2 cache: 256K (XEN) CPU: L3 cache: 8192K (XEN) CPU: Physical Processor ID: 1 (XEN) CPU: Processor Core ID: 2 (XEN) Intel machine check reporting enabled on CPU#13. (XEN) CPU13: Thermal monitoring enabled (TM1) (XEN) CMCI: find owner on CPU13 (XEN) CMCI: CPU13 owner_map[0], no_cmci_map[93] (XEN) CPU13: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz stepping 05 (XEN) Booting processor 14/7 eip 8c000 (XEN) Initializing CPU#14 (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K (XE...

...ping 05 (XEN) Booting processor 13/21 eip 8c000 (XEN) Initializing CPU#13 (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K (XEN) CPU: L2 cache: 256K (XEN) CPU: L3 cache: 8192K (XEN) CPU: Physical Processor ID: 1 (XEN) CPU: Processor Core ID: 2 (XEN) Intel machine check reporting enabled on CPU#13. (XEN) CPU13: Thermal monitoring enabled (TM1) (XEN) CMCI: find owner on CPU13 (XEN) CMCI: CPU13 owner_map[0], no_cmci_map[93] (XEN) CPU13: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz stepping 05 (XEN) Booting processor 14/7 eip 8c000 (XEN) Initializing CPU#14 (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K (XE...

...40GHz stepping 05 (XEN) Booting processor 11/3 eip 8c000 (XEN) CPU11: Intel(R) Xeon(R) CPU E5530 @ 2.40GHz stepping 05 (XEN) Booting processor 12/21 eip 8c000 (XEN) CPU12: Intel(R) Xeon(R) CPU E5530 @ 2.40GHz stepping 05 (XEN) Booting processor 13/5 eip 8c000 (XEN) CPU13: Intel(R) Xeon(R) CPU E5530 @ 2.40GHz stepping 05 (XEN) Booting processor 14/23 eip 8c000 (XEN) CPU14: Intel(R) Xeon(R) CPU E5530 @ 2.40GHz stepping 05 (XEN) Booting processor 15/7 eip 8c000 (XEN) CPU15: Intel(R) Xeon(R) CPU E5530 @ 2.40GHz stepping 05 (XE...

Hey Ian and Stefano, Please see this thread: http://lists.xen.org/archives/html/xen-devel/2013-05/msg01053.html for the debug patches and some of the discussion. These three patches fix an race that has been in QEMU traditional for a long time. The guts of the bug is that if you have a guest with these options: vcpus=1 maxvcpus=32 and do ''xl vcpu-set <guest> 32'' the

...E5520 @ 2.27GHz stepping 05 (XEN) Booting processor 11/7 eip 8c000 (XEN) CPU11: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz stepping 05 (XEN) Booting processor 12/17 eip 8c000 (XEN) CPU12: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz stepping 05 (XEN) Booting processor 13/19 eip 8c000 (XEN) CPU13: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz stepping 05 (XEN) Booting processor 14/21 eip 8c000 (XEN) CPU14: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz stepping 05 (XEN) Booting processor 15/23 eip 8c000 (XEN) CPU15: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz stepping 05 (XEN) Total...

...i31 0K 384K RUN 8 18.4H 30.96% idle{idle: cpu8} 7619 dovenull 81 0 59048K 32864K CPU20 20 2:01 30.96% imap-login 11 root 155 ki31 0K 384K CPU18 18 18.3H 30.76% idle{idle: cpu18} 11 root 155 ki31 0K 384K RUN 13 18.3H 30.57% idle{idle: cpu13} 11 root 155 ki31 0K 384K RUN 12 18.3H 30.47% idle{idle: cpu12} 11 root 155 ki31 0K 384K RUN 20 18.3H 30.08% idle{idle: cpu20} 11 root 155 ki31 0K 384K RUN 10 18.4H 29.88% idle{idle: cpu10} 11 root 155 ki31 0K 384K...

Hi, I have a Dell T710 with 4 X 10G ethernet interfaces (2 X Dual port Intel 82599 cards). It is running FreeBSD RELENG_8 last updated on July 13. What I see is packet loss (0 - 40%) on IPv6 packets in vlans, when the machine is not the originator of the packets. Let me try to describe a little more. If a neigbouring machine ping6 it, there will be packet loss. If it act as a router for ipv6,

Please see the three patches that fix the ACPI AML and QEMU race. They have been Ack-ed by both George (for inclusion in Xen 4.3) and by Stefano. They should be candidates for back-port in older hypervisors. Konrad Rzeszutek Wilk (3): piix4acpi, xen, vcpu hotplug: Split the notification from the changes. piix4acpi, xen: Clarify that the qemu_set_irq calls just do an IRQ pulse.

I would also like to help as well. As KMacy knows before i asked a lot of questions for T2 types of servers but unfortunately i have no more access to those kind of hardware as well. I;m willing to participate if a team will be formated.

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 (

...11.231 No irq handler for vector (irq -1) (XEN) microcode.c:73:d32767 microcode: CPU11 resumed (XEN) do_IRQ: 12.231 No irq handler for vector (irq -1) (XEN) microcode.c:73:d32767 microcode: CPU12 resumed (XEN) do_IRQ: 13.231 No irq handler for vector (irq -1) (XEN) microcode.c:73:d32767 microcode: CPU13 resumed (XEN) do_IRQ: 14.231 No irq handler for vector (irq -1) (XEN) microcode.c:73:d32767 microcode: CPU14 resumed (XEN) Brought up 16 CPUs (XEN) do_IRQ: 15.231 No irq handler for vector (irq -1) (XEN) microcode.c:73:d32767 microcode: CPU15 resumed (XEN) HPET: 4 timers in total, 3 timers will be...

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

...... 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) microcode.c:73:d32767 microcode: CPU10 resumed (XEN) microcode.c:73:d32767...

Hello, I''m trying to compile Xen unstable on NetBSD, I''ve aplied the patches from http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/sysutils/xentools41/patches/?only_with_tag=MAIN and copied the blk files from http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/sysutils/xentools41/files/?only_with_tag=MAIN (I don''t know which of these patches have been applied to xen unstable, so

...(rev 02) ff:13.5 Performance counters: Intel Corporation Device 3c44 (rev 02) ff:13.6 System peripheral: Intel Corporation Device 3c45 (rev 02) CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7 CPU8 CPU9 CPU10 CPU11 CPU12 CPU13 CPU14 CPU15 CPU16 CPU17 CPU18 CPU19 CPU20 CPU21 CPU22 CPU23 CPU24 CPU25 CPU26 CPU27 CPU28 CPU29 CPU30 CPU31 8: 1 0 0 0 0 0 0 0...