Displaying 20 results from an estimated 40000 matches similar to: "Cannot boot Dom0: Thread overran stack, or stack corrupted"
2009 Mar 04
1
pv_ops kernel 2.6.29-rc6 boot failure
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
2009 Feb 27
8
Kernel build failure
Did a ''git pull'' a few minutes ago and tried to rebuild my kernel and
was given this error:
make
CHK include/linux/version.h
CHK include/linux/utsrelease.h
SYMLINK include/asm -> include/asm-x86
CALL scripts/checksyscalls.sh
CHK include/linux/compile.h
CC drivers/acpi/acpica/hwsleep.o
drivers/acpi/acpica/hwsleep.c: In function
2011 Apr 14
3
Debian Squeeze hangs with kernel 2.6.32-5-xen-686
Hi all!
After upgrading to Squeeze, I am watching a Xen VMHost that after a
while it hangs. This did not happen when I was using Xen with Debian
Lenny (in this case as with Squeeze, the Xen components are from Debian
repositories).
In each case I connected a keyboard and monitor to the computer and the
screen remained black without answering any key.
This problem seems to also affect domUs,
2010 Mar 15
1
Could not obtain handle on privileged command interface
Hello,
when I try to start xend I receive this error:
root@xenized:~# xend start
ERROR Internal error: Could not obtain handle on privileged command
interface (2 = No such file or directory)
Traceback (most recent call last):
File "/usr/sbin/xend", line 36, in <module>
from xen.xend.server import SrvDaemon
File
2010 Aug 21
24
Freeze with 2.6.32.19 and xen-4.0.1rc5
Hi,
i have big trouble with a Debian Lenny dom0 and latest kernel 2.6.32.19
with xen-4.0.1rc5. Due some reason the system freezes from time to time.
I used kernel 2.6.31.9 with xen-3.4.2 before. The machine doesn''t write
anything to serial console so there are no errors or something like that.
Perhaps there is something to see from the logs ...
Hardware
Board: Intel DQ45CB
CPU:
2008 Nov 29
24
pv_ops dom0 testing
I am trying to get a pv_ops dom0 working for testing,
but I am running into an elf_init error:
(XEN) *** LOADING DOMAIN 0 ***
(XEN) elf_init: not an ELF binary
Full output attached.
>From what I have read on the mailing lists, it seems
that it is usually a problem with either grub or a
corrupt dom0 kernel.
Attached is my kernel config (2.6.28-rc6-tip).
I followed the instructions on:
2010 May 28
3
Problems with PCI pass-through
Hello!
I'm having problems getting PCI pass-through to work.
This is on a AMD64 system, paravirtualized with xen-hypervisor-4.0-amd64
4.0.0-1~experimental.1, dom0: linux-image-2.6.32-5-xen-amd64 2.6.32-12.
From IRC, earlier today:
<tschwinge> waldi: Aren't the Debian xen domU-capable kernels supposed to
contain the PCI frontend (needed for PCI pass-through)? I'm getting:
2010 May 28
3
Problems with PCI pass-through
Hello!
I'm having problems getting PCI pass-through to work.
This is on a AMD64 system, paravirtualized with xen-hypervisor-4.0-amd64
4.0.0-1~experimental.1, dom0: linux-image-2.6.32-5-xen-amd64 2.6.32-12.
From IRC, earlier today:
<tschwinge> waldi: Aren't the Debian xen domU-capable kernels supposed to
contain the PCI frontend (needed for PCI pass-through)? I'm getting:
2010 Apr 07
15
XEN 4.0 boot error
Hey all,
Just downloaded the new Xen 4.0 and ran
Make xen
Make tools
Make stubdom
Copied the new files from dist/install
Im already running pv_ops 2.6.31.6 kernel.
When I boot i get
(XEN) Panic on CPU 0:
(XEN) IO-APIC + timer doesn''t work!
I have tried booting with noapic boot option but makes no difference.
The system worked fine on 3.4.2
CPU is AMD.
2010 Apr 13
1
Xen breaks aacraid
Hello,
I''m using Xen 4.0.0 compiled from source with the 2.6.31.13 kernel
that it pulls down on its own. I added support for the aacraid driver
to the kernel using ''make menuconfig'' from the
build-linux-2.6-pvops_x86_64 subdirectory, and then built and
installed the whole thing using ''make install'' from the xen-4.0.0
directory. I compiled this
2014 May 15
0
Bug#748052: Bug#748052: Bug#748052: Bug#748052: xen-hypervisor-4.3-a
Ian Campbell <ijc at hellion.org.uk> writes:
#Please boot with loglvl=all on the hypervisor command line for this too.
No problem Ian,
Here are some results with (now) the latest BIOS version 41. (was version 35)
This is a fresh new install of Debian "Testing" non production server.
Just wanted to run some test domU's.
Changing USB ports, no effect. I even tried a different
2012 Jul 27
6
Failure to boot, Debian squeeze with 4.0.1 hypervisor, timer problems?
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
2011 Aug 15
4
Kernel 3.1.0-rc2 hangs on boot, Xen 4.1.1
Hello,
I tried out kernel 3.1.0-rc2 on my i386 Laptop with Xen 4.1.1. Booting
hangs after these messages on the VGA console:
pci 0000:02:09.0: address space collision: [mem 0x000da000-0x000dafff] conflicts with reserved [mem 0x0009f800-0x000fffff]
reserve RAM buffer: 00000000 0009f000 - 00000000 0009ffff
reserve RAM buffer: 00000000 38400000 - 00000000 3bffffff
reserve RAM buffer: 00000001
2011 Aug 15
4
Kernel 3.1.0-rc2 hangs on boot, Xen 4.1.1
Hello,
I tried out kernel 3.1.0-rc2 on my i386 Laptop with Xen 4.1.1. Booting
hangs after these messages on the VGA console:
pci 0000:02:09.0: address space collision: [mem 0x000da000-0x000dafff] conflicts with reserved [mem 0x0009f800-0x000fffff]
reserve RAM buffer: 00000000 0009f000 - 00000000 0009ffff
reserve RAM buffer: 00000000 38400000 - 00000000 3bffffff
reserve RAM buffer: 00000001
2010 Jul 07
2
Bug#588310: Xen enabled kernel cannot find the / partition
Package: xen-hypervisor-3.4-amd64 and linux-image-2.6.32-5-xen-amd64
Version: 3.4.3-1 and 2.6.32-15
Hello all,
GRUB-PC does not automatically populate Xen related parameters in
/boot/grub/grub.cfg so I added them manually (see below). All the
packages involved on my Dell PowerEdge R710 running Debian GNU/Linux
Squeeze AMD64 are from the Squeeze repository. There are four (4) 1TB
SATA HDD
2010 Nov 16
0
Bug#603727: xen-hypervisor-4.0-amd64: i386 Dom0 crashes after doing some I/O on local storage (software Raid1 on SAS-drives with mpt2sas driver)
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"
2012 Feb 12
0
Bug#659642: xen-hypervisor-4.0-amd64: outl segfaults when restoring monitor from sleep with DPMS
Package: xen-hypervisor-4.0-amd64
Version: 4.0.1-4
Severity: normal
Tags: squeeze
When the monitor is being restored from power saving mode via DPMS, X will lock
up/restart. This only occurs when running Xen hypervisor. Running just 2.6.32-5
-xen-amd64 doesn't produce this effect. Note that both 2.6.32-5-xen-amd64 and
2.6.32-5-xen-amd64 with Xen 4.0.1 are running with nopat (to workaround
2013 Mar 05
8
eDP screen corruption using linux 3.8 & xen 4.2
Konrad, et al,
I am seeing visual corruption (almost like an interlacing problem) with
i915 under Xen on some platforms using linux-3.8.
See attached file for an example of the visual corruption.
This particular platform is an HP Elitebook 2540p
The same kernel and ramdisk, when booted as native linux does not show this
corruption.
dmesg is attached, as well (out.txt) - but I did not see
2012 Jan 12
9
linux 3.3-pre-rc1: Starting domU fails with Error: Failed to query current memory allocation of dom0.
Hi Konrad,
Today i tried linuses tree of today (last commit is 4c4d285ad5665bfbd983b95fde8d7a477d24a361).
It boots dom0 fine, but it fails to start any domU with: "Error: Failed to query current memory allocation of dom0."
With my previous 3.1.5 kernel everything is fine, nothing else changed in config in between.
dmesg and xm dmesg attached
--
Sander
Dom0 shows:
total
2011 Jan 09
11
(no subject)
OK, so after several weeks of trying to get various versions of Xen running of various distributions, I''m starting to wonder if I''ve got a hardware compatibility problem and as the system never really boots with the Xen kernel I''ve got no log files to tell me where the problem is. I was wondering if there''s a way to compile from source with debug turned on,