similar to: Possible bug, dom0 crash on ubuntu

Hey I wanted to try my hand at doing some GPU passthrough so on my ASUS M5A97 which in the pass worked with an older BIOS (but said BIOS had issues after S3 suspend) - but with a BIOS the PCI passthrough does not work. That is due to:: (XEN) IVHD Error: Invalid IO-APIC 0xff (XEN) AMD-Vi: Error initialization

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

Today is my day! This is with Xen 4.4 (pulled today) when I build a kernel in dom0 and have two guests launching at the same time. This is what I get: (XEN) Assertion ''l1e_get_pfn(MAPCACHE_L1ENT(hashent->idx)) == hashent->mfn'' failed at domain_page.c:203 and it blows up. Here is the full log: \ \/ /___ _ __ | || | | || | _ _ _ __ ___| |_ __ _| |__ | | ___

Hi, I''ve not tried pv_ops for a long time but just got a new system (Supermicro X9DRL-iF) so decided to try 3.5.0 with the latest Xen 4.2-unstable, unfortunately the system crashes immediately after loading dom0: traps.c:486:d0 Unhandled invalid opcode fault/trap [#6] on VCPU 0 [ec=0000] I''ve tried loading both bzImage and vmlinuz (gzip compressed vmlinuz) with the same

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

For some reason it seems to fail somewhere in either nouveau_display_create or nouveau_display_init. Kernel 3.16 is nearly 2 years old though, and countless changes and fixes have gone into the nouveau kernel driver since then. Does this still happen with a recent kernel? You can try a livecd from https://nouveau.pmoreau.org/ which has all the very latest nouveau-related software. On Wed, Jul 6,

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9+deb8u3 Severity: grave Hello, I am trying to install the XEN Hypervisor on a Debian Jessie Server. When I am booting without the Hypervisor, everything works fine, but when I am Booting WITH the XEN-Hypervisor, then System crashes / reboots after the "Scrubbing Free RAM" Message without any Error-message, just a blank screen.

https://bugs.freedesktop.org/show_bug.cgi?id=109681 Bug ID: 109681 Summary: Nvidia GT710 => nouveau + wayland + swayWM => crash when use acceleration (open Firefox) Product: Mesa Version: 18.3 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical

Is that an error that prevents anything from working? It's probably expected... On Thu, Jul 7, 2016 at 2:07 PM, abcd <abcdeluxe at web.de> wrote: > Thanks for the quick help! > > Indeed a kernel update resolved the issue, there one problem left > though: I get an error: > > Xorg.0.log: Couldn't load sub module "fb". > > I can't find out what

Hi, I am using libguestfs 1.12.0 and I am facing a problem with it . I am using guestfs python bindings to "launch" a vdi image file . It works fine except immediately after a VM is stopped(which uses the same vdi file) i.e in normal conditions launch command works but when a vm (which uses the same vdi file) is started - stopped , a call to "launch" command hangs the

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

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

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

Hi Konrad I encountered a bug when trying to bring offline a cpu then online it again in HVM. As I''m not very familiar with HVM stuffs I cannot come up with a quick fix. The HVM DomU is configured with 4 vcpus. After booting into command prompt, I do following operations. # echo 0 > /sys/devices/system/cpu/cpu3/online # echo 1 > /sys/devices/system/cpu/cpu3/online With

Trying to get Xen going on Fedora 9. Xen was installed from the distro RPMs. Xen version is 3.2.0 and the linux-xen version is 2.6.25.3. Xen seems to come up fine, but the system just hangs at the point where booting of Dom0 should start. There is absolutely no output from Dom0. I configured Xen to log to a serial port and captured the output below. Any suggestions on how to continue

Hi, I have a problematic CentOS XEN server and hope someone could point me in the right direction to optimize it a bit. The server runs on a Core2Quad 9300, with 8GB RAM (max motherboard can take, 1U chassis) on an Intel motherboard with a 1TB SATA HDD. dom0 is set to 512MB limit with a few small XEM VM's running: root at zaxen01:[~]$ xm list Name ID

Hi, I am having problems with the nouveau driver from Debian. Can I get help here? Cheers

[ 0.000000] microcode: CPU0 microcode updated early to revision 0x1b, date = 2014-05-29 [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 4.4.0-rc3+ (airlied at crackbookpro) (gcc version 5.1.1 20150618 (Red Hat 5.1.1-4) (GCC) ) #44 SMP Sat Dec 5 16:05:39 AEST 2015 [

Hi, I took this issue to the Fedora forum initially, but no-one there has been able to offer any guidance, so I have decided to come to the nouveau community directly. I was running a KDE desktop under Fedora 21 successfully, including the ability to use a direct text login on an older card (GXT 560 Ti) with an entirely stock Fedora, fully updated. I simply replaced the old card with an