similar to: Bug#588310: Xen enabled kernel cannot find the / partition

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 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,

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:

Hi All, I am trying to get the pv_ops Xen dom0 kernel working with Xen 3.4 but with no success. I have been at this for 2 weeks now with different problems. Initially I could not get dom0 to boot when using LVM, so I reinstalled and didn''t use LVM. Now I am getting stack overran or currupted errors. Here is the boot log; From <IRQ 0> to the last line keeps on repeating until

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

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

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

Hi, we are currently working on getting windows working on your xen servers. but we are facing a severe problem where dom0 and all domus hang for 1-5 seconds from time to time. we think it is probably because of disk i/o, because top sometimes says 100% wa (waiting on io) during the hang. dom0 has cpu 0 for exclusive use and the windows vms use cpu 1 to 7. should we give dom0 more than once

Hellow all, i need help to fix this bug: ACPI BIOS Bug: Error: A valid RSDP was not found (20120711/tbxfroot-219) Because of this first errors i get this after, and it causes don''t work USB ports and some PCI cards on the system: can''t find IRQ for PCI INT A; please try using pci=biosirq Kernel: 3.6.1-xen self compiled (work perfect without xen multiboot) Xen Version: 4.2

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

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

Hi, I have been receiving messages on a new DomU''s kern.log. I''ve done a lot of googling, but haven''t came up with anything very useful, at least not in a Xen context. I was wondering if anyone had any suggestions about what could be wrong. From everything I have read, there should be a stack trace included, but I am not seeing one. Thanks in advance, Ian. on

I have a perc5i (and perc5e) raid controller in my poweredge 2970 running centos 5.5. The RAID controller config is set for write-back policy, which I can confirm by checking in OpenManage. I also called Dell and ran their reporting application and had them double check to make sure everything looks OK hardware wise and they confirm that it does Yet when CentOS boots is appears to use the

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:

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:

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9+deb8u1 Severity: important I already posted this on the xen-devel-mailinglist but no one seems to have an answer. I'm posting it here because perhaps someone using Debian and Virtualization might have an idea about this? Since Debian 8 I observe that live migrating a PVM on XEN 4.4.1 (also 4.5.1) and Linux Kernel 4.1.0 (also 3.18) requires

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

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

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

A gentle reminder on this issue Please can any one help on this problem? ________________________________ From: Manyam, Ramesh Sent: Wednesday, November 19, 2008 7:46 PM To: xen-devel@lists.xensource.com Subject: megaraid sas driver failing in Xen-3.4 unstable version On Xen-3.4 (unstable version), I have created CentOS HVM guest & WS2K8 HVM guest and dedicated MegaRAID SAS controller but