similar to: Bug#755753: xen-hypervisor-4.1-amd64: xen crashes at random

Hello. It is update of my previous message. I''ve checked that I can passthrough discrete graphic card, but when I try use in IGP (without discrete card in the slot) linux come to desktop without usage in inteldmr driver indeed. Dmesg show that I have some problem with ioremap. Is someone tried do pci/vga passthrough of integrated graphic or know way to solve that problem? Best regards.

Hi, I have a problem booting the Xen hypervisor on my brand new Lenovo Thinkpad T400 2765D2G (Core2 Duo P8600 CPU, 2.40GHz. 4GB RAM). I''m running Debian 5.0 (Lenny) and I use the Debian-provided xen-hypervisor-3.2-1-amd64 package. The Dom0 kernel seems to be the Xen patches ported to a 2.6.26 kernel: linux-image-2.6.26-1-xen-amd64 I can boot the hypervisor only very unrealiably: Out of

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.1-2 Severity: important The Xen hypervisor very unreliably boots on my 4GB Lenovo Thinkpad T400 2765D2G. Right after installation it booted the DomO kernel from linux-image-2.6.26-1-xen-amd64 without any problems, but every subsequent restart failed completely. Once I had a XEN "early fatal page fault" error message, on every other of

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3+deb7u1 Severity: normal I tried GRUB_CMDLINE_XEN="dom0_mem=8192M": that delivers 6964868K total, then crashes when used=2837436K free=4127432K. By crash I mean the gnome screen was blown away, replaced by a black screen with white log lines. That seems to happen every time dom0 uses a large amount of memory. After setting

Hello. Minimal testcase for my problem: No X running, just a TTY. Use of the nouveau kernel module as of today (or any older) with an up to date vanilla kernel. Hardware: DELL Vostro 3500 with Geforce 310M. To suspend to ram I use this script, as suggested in Documentation/power/s2ram.txt: #!/bin/sh sync echo 1 > /sys/power/pm_trace echo mem > /sys/power/state When I try to suspend to

https://bugs.freedesktop.org/show_bug.cgi?id=54830 Bug #: 54830 Summary: Display is shifted to right (ASUS VS197) Classification: Unclassified Product: xorg Version: 7.7 (2011) Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: minor Priority: medium Component:

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

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

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

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

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

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 Everyone! I've been trying to get my Nvidia 9800m GT working with the latest nouveau drivers with no luck so far. First of all I'd like to mention that this is a weird card as it is an SLI in one piece of hardware (not 2 separated cards). It came with my Dell XPS M1730 laptop. I know SLI is not currently supported and _I don't want_ to use SLI, I just would like to use one of

My kernel crashed for some other reason, and now I can''t mount my btrfs filesystem. I don''t care about the data, it''s backed up. I''ll compile a 3.5 kernel, but is there any info you''d like off that filesystem to see why btrfs is crashing on mount? Marc [ 313.152857] device label btrfs_pool1 devid 1 transid 20769 /dev/mapper/disk1 [ 313.171318]

dmesg output after a resume from a suspend. the device in question was /dev/sdb mounted on /home. after a device failure to resume properly, the link is then reset by the kernel but comes back as /dev/sde. /dev/sdb disappeared entirely, and is now referred to as sde. attempted to remount rw of sde, seemed to succeed, mount/mtab said that it was rw now but i couldn''t write to the volume

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

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

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

Hi guys, Last week I've switched from my old & good 3.4.63 to 3.14-rc1 and noticed nasty display corruptions when using nouveau. It seems that changing parts of the screen are appearing for a fraction of second in random places. I've recorded this behavior: http://www.youtube.com/watch?v=IEq7JzGVzj0 My hardware is some old motherboard with 00:05.0 VGA compatible controller [0300]: