similar to: about IOAPIC in Xen 3.0

Hi Konrad, I just tried to boot a 3.8.0-rc0 kernel (last commit: 7313264b899bbf3988841296265a6e0e8a7b6521) as dom0 on my machine with current xen-unstable. The boot stalls: [ 0.000000] ACPI: PM-Timer IO Port: 0x808 [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01]

All. I am running Xen on an ES7000 system with 4 procs and 4 GB memory. I am running Suse Sles-9 (32-bit) on the machine. I have compiled Xen (the tip on the unstable tree : 6552) with PAE enabled (XEN_TARGET_X86_PAE=y). The system boots fine. I started xend and when I tried to bring up a virtual machine, the system gave me the following error on the command line. On the serial port, I saw an

Package: xen-hypervisor-3.0.3-1-amd64 Version: 3.0.3-0-2 Severity: important about every 1 in 10 boots I am getting the following error: (XEN) ************************************ (XEN) CPU0 FATAL TRAP 6 (invalid opcode), ERROR_CODE 0000, IN INTERRUPT CONTEXT. (XEN) System shutting down -- need manual reset. (XEN) ************************************ This seems to happen in the CPU detection

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-6 Severity: normal Dear Maintainer, I'm trying to boot into xen/dom0 but so far all attempts have resulted in a crash followed by an automatic reboot. My hardware is Motherboard: Asus Sabertooth 990FX R2.0 CPU: AMD FX-8350 GPU: Sapphire Radeon R9 285 A trace of the kernel panic follows (full log captured over serial should

Hi, I did a git pull on pv_ops tree this morning and now get a crash when eth0 is started, here is the full boot log: Booting ''Xen 3.4 / Linux 2.6.29-rc6-tip'' root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /xen.gz com1=115200,8n1 console=com1,vga iommu=1 [Multiboot-elf, <0x100000:0x131748:0x8e8b8>, shtab=0x2c0078, entry=0x100000] module

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-1 Severity: normal My 32Bit Dom0-crashes with error "Out of SW-IOMMU space for 65536 bytes" after doing moderate I/O on the local storage, which is a software-raid1 over 3 harddrives, connected to the builtin Perc H200 controller with ext3-fs. The error is reproduceable with "dd if=/dev/zero of=bigfile bs=1024 count=1000000"

Hi, I have a system based on a Supermicro X8DTH-i motherboard and a Xeon E5506 CPU. It was previously running Debian lenny with xen-hypervisor-3.2-1-amd64 (3.2.1-2) / linux-image-2.6.26-2-xen-amd64 (2.6.26-29) without incident. I upgraded it to Debian squeeze, with xen-hypervisor-4.0-amd64 (4.0.1-4) / linux-image-2.6.32-5-xen-amd64 (2.6.32-45) and now it does not complete a boot of the dom0

hi: I had installed Xen-2.0.6 on my server DELL 2850 with 6G memory, dual Xeon CPU, it''s can''t use all 6G memory, i had upgrade to Xen-unstable, it''s still can use 3.3G memory. [root@CentOS4 ~]# xm dmesg __ __ _____ ___ _ _ \ \/ /___ _ __ |___ / / _ \ __| | _____ _____| | \ // _ \ ''_ \ |_ \| | | |__ / _`

hi: I had installed Xen-2.0.6 on my server DELL 2850 with 6G memory, dual Xeon CPU, it''s can''t use all 6G memory, i had upgrade to Xen-unstable, it''s still can use 3.3G memory. [root@CentOS4 ~]# xm dmesg __ __ _____ ___ _ _ \ \/ /___ _ __ |___ / / _ \ __| | _____ _____| | \ // _ \ ''_ \ |_ \| | | |__ / _`

During boot of dom0, I get the following. Box is remote, so I''m now waiting for proxy power button pusher ;-) tg3 init fails doing dma_alloc_coherent (I assume this is from tg3_init_one -> tg3_test_dma -> pci_alloc_consistent -> dma_alloc_coherent). Looks like an issue with the amount of memory in dom0. Is this known? thanks, -chris root (hd0,0) Filesystem type is ext2fs,

I''ve installed Xen kernel for dom0 on a CentOS 4.4 but when i reboot the kernel says: _/\_\___|_| |_| |____(_)___(_)____(_)___/ http://www.cl.cam.ac.uk/netos/xenmdev = 59.12 University of Cambridge Computer Laboratory6 Sep 26 01:52 qemu-dm.6463.log Xen version 3.0.3.0 (root@uk.xensource.com) (gcc version 3.4.6 20060404 (Red Hastart qemu- -rw-r--r-- 1 root root t 3.4.6-3)) Mon Oct

Just trying to understand if anything might be going on with this crash dump or just faulty hardware ? dmesg at the end ---Mike # gdb -k /kernel.debug vmcore.0 GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type

Hey, I have a nighly build/test system that boots various machines with upstream Linux and randomly selects Xen 4.1, Xen 4.2, Xen 4.3 and unstable. After a bit of digging I found out that Xen 4.2 ''xl'' (but not ''xm'') has some badness in it. When "migrating" (''xl'' save followed by ''xl'' restore'') the PVHVM

OK, here's the info Bastian asked for. Transcript: rob at thismachine:~$ dmesg Bootdata ok (command line is root=/dev/sda1 ro ) Linux version 2.6.18-5-amd64 (Debian 2.6.18.dfsg.1-13) (dannf at debian.org) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Thu May 31 23:51:05 UTC 2007 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009c800 (usable)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I followed the instructions here: http://nixcraft.com/file-servers/14803-how-centos-5-pxe-linux-installation-server.html, along with a few other sources that were less successful, and I finally got a pxe boot going. I'm using CentOS 5.3 x86_64 media as the source. The server boots, but keeps hanging. Here is my boot line:

Hi, I need a help with tracking down following issue: When trying to boot Xen on a system with Ivy Bridge stepping C0 CPU, it is stuck on CPU initialization. I''ve added some tracing to apic writes/reads and traced it so far to sending INIT IPI. (XEN) HVM: VMX enabled (XEN) HVM: Hardware Assisted Paging detected. (XEN) Setting warm reset code and vector. (XEN) apic_wrmsr (0x280,0x0)

Hello, I''m attempting to boot Xen 4.0.1 on a SuperMicro H8DGi-F motherboard and having not much luck. I can boot the 2.6.32.26 (or .27) kernels alone, but when I add Xen into the mix, I get consistent boot failure. I''ve tried Xen 4.0.1-release, 4.0.2-rc1-pre and 4.0.2-rc2-pre, all get the same failure. xen/next-2.6.37 works and boots great, but since netback isn''t

I wanted to boot gentoo on xen, but it doesn''t work. What can I do? Booting ''Xen 3.0.0 / Linux 2.6.12.5'' root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /xen.gz dom0_mem=131072 com1=115200,8n1 [Multiboot-elf, <0x100000:0x641cc:0x27e34>, shtab=0x18c078, entry=0x100000] module /vmlinuz-2.6.12.5-xen-0 root=/dev/md0

(copying xen-devel, full logs are at bugs.debian.org/748052, this is Debian Jessie, Xen 4.3.0 and Linux 3.13 Mike also reported that Debian Wheezy Xen 4.1.4 didn't work either, not clear which kernel that was with though, Wheezy's 3.2 or Jessie's 3.13) On Thu, 2014-05-15 at 10:11 -0700, Mike Egglestone wrote: > Here are some results with (now) the latest BIOS version 41. (was >

Hey, It looks like one of the patches that went in Xen 4.1 blows up. This used to work over the weekend, so I can only surmise it is one the three patches. This is with a debug=y build (which has been working nicely for the last month or more). It looks like one of the patches that went in Xen 4.1 blows up. This used to work a day ago - that is c/s 23551 worked nicely. ----- Forwarded message