similar to: Bug#606030: xen-hypervisor-4.0-amd64: Cannot start Xen guest with sda hdd-config

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,

Trying to debug a database server getting cpu softlocks causing SSHD to hang and not let anybody log in. Figured that a good first step would be to get some kernel dumps when the problem occurs. According to what I read at the following web site, I can get dumps for softlock problems too. Here's the site: http://blog.kreyolys.com/2011/03/17/no-panic-its-just-a-kernel-panic/ Using a

Ok im trying to play Counter Strike 1.6, but it crashes when i join a server. The Video is set to OpenGL and when i set it to "Software" it started working (but the quality was really shitty so i want OpenGL). I have this video card VGA compatible controller [0300]: ATI Technologies Inc RS480 [Radeon Xpress 200G Series] And when the game crashed i got this error: Code: Allocating

> Just making sure.. you''re running Xen 4.1 ? > The userspace qemu blkback implementation is *only* in Xen 4.1 .. > And it should get used automatically if dom0 kernel blkback is not available. Attempt of DomU install env above :- # xl create -c f14.install Parsing config file f14.install Daemon running with PID 3411                             [    0.000000] Initializing

Hi. While testing subvolumes in btrfs on 2.6.32.9, I hit a kernel BUG: [ 492.164012] kernel BUG at fs/btrfs/inode.c:4365! The commands to reproduce this bug are as follows: # mount -t btrfs /dev/sda5 /scratch # btrfsctl -S subvol /scratch # date > /scratch/date # ln /scratch/date /scratch/subvol/ ln segfaults, and the bug above is found in dmesg. Subsequent accesses to the subvolume

Hi Xen developers, We are hitting a DomU Linux kernel panic and we''d like to find a solution for it. We are porting our virtual appliance to Amazon''s AWS. Our kernel is 2.6.27.57. We know it is old but we have to stay with it for now. The problem is when the kernel (64-bit) boots up in EC2 ( a large instance with 7.5 GB memory), the kernel crashes when hitting the BUG in

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''m trying to boot a PV VM I just installed (following http://wiki.xen.org/wiki/Debian_Guest_Installation_Using_Debian_Installer) without success. My XEN installation is xen-unstable 54c8c9eaee92+ on a Debian unstable machine (x86_64), kernel 3.3.4+. The VM I installed is, again, a Debian unstable x86_64. The installation went smoothly; I used an 8GB file as a disk back-end. I went

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9 On a fresh installation of Debian Jessie, when I try to start a domU, it try to access to a dom0 LVM Volume Group : [...] (I put all the boot at the end) Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Begin: Assembling all MD

[Please keep replies on the list] > ************************************************************ > * IMPORTANT NOTICE > * > * When reporting bugs, include the COMPLETE, UNEDITED > * output below in your bug report. > * > ************************************************************ > libguestfs: trace: set_verbose true

I've tried the workaround you suggested but it doesn't seem to work. Also tried to add just "libsbz.so" to zz-workaround with no success. It throws the same error as before. PS: Sorry I've just hit reply without checking the "To:" address and I guess it sent directly to you. On Thu, Sep 3, 2020 at 1:59 PM Richard W.M. Jones <rjones@redhat.com> wrote: >

Source: xen Severity: normal Dear Maintainer, After an upgrade, my passthroughed NIC stopped working. I created a new jessie domU and tried to passthrough some PCI devices and found that both USB3 host controller and tg3 NIC generated these lines in domU dmesg: xen:events: Failed to obtain physical IRQ 31 xen:events: Failed to obtain physical IRQ 32 xen:events: Failed to obtain physical IRQ 33

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.1-2 Severity: normal After giving xen a shoot with the fresh lenny packages, an annoying bug comes up right after trying to boot into the new system. I'll provide further informations if needed. Please see serial debug output below and here http://plzk.de/xen-lenny (maxlines got extended for comfortable reading) XEN) Xen version 3.2-1

Xen developers, After an upgrade of my Debian Jessie dom0 and domUs, my passthroughed NIC stopped working. This bug was probably introduced in Debian Jessie sometime between 2015-12-30 and 2016-01-08 as 2015-12-30 as 2015-12-30 was the last time I upgraded without any problems according to my dpkg.log. This bug has also been reported to Debian Bug (https://bugs.debian.org/810379), where I got

On Wed, Jan 27, 2016 at 7:30 PM, Konrad Rzeszutek Wilk < konrad.wilk at oracle.com> wrote: > On Sat, Jan 23, 2016 at 05:12:04PM +0100, Tommi Airikka wrote: > > Xen developers, > > > > After an upgrade of my Debian Jessie dom0 and domUs, my passthroughed > > NIC stopped working. > > This bug was probably introduced in Debian Jessie sometime > > between

To get x86 to work, you need to compile /arch/x86/boot and /arch/x86/boot/compressed with gcc. The rest can be compiled with llvm-gcc. The only adjustment you need to make is to /arch/x86/kernel/signal_32.c to fix the stack offset in sys_sigreturn. Also you must compile with -O0. instcombine is causing the crashes you are seeing. I know mem2reg, sccp, simplifycfg, and dce result in a working

Hi, I have been trying to get NIC PCI Passthrough to work on Xen 4.3.0 and have hit a wall. On attaching the NIC the domU network driver (igb) crashes. I followed the Xen PCI Passthrough wiki http://wiki.xen.org/wiki/Xen_PCI_Passthrough and am using dynamic device assignment with xl. Trying to passthrough this device: root@dom0:~# lspci|grep 82575EB 05:00.1 Ethernet controller: Intel

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

For people who want to try hacking on the linux kernel with llvm, here is a head start: http://llvm.org/~alenhar2/k.tbz This is a 2.6.27.5 kernel with a .config file for qemu/kvm with virtio devices (I also think it will work with the default devices). The build process uses llvm-gcc -> opt -> llc so you can add your own (per-file) passes to the build process or debug specific passes.