similar to: Bug#820862: xen-hypervisor-4.4-amd64: Xen VM on Jessie freezes often with INFO: task jbd2/xvda2-8:111 blocked for more than 120 seconds

Dear XEN-Team I've set up a complete new VM, tested copying and backuping with following error again: [ 1920.052129] INFO: task jbd2/xvda2-8:98 blocked for more than 120 seconds. [ 1920.052143] Not tainted 3.16.0-4-amd64 #1 [ 1920.052147] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1920.052153] jbd2/xvda2-8 D ffff880004986e78 0 98

Dear Debian-Bugteam Unfortunately this problem still exists. I want to use the server in production environment, but can't by reason of this error. Installed XEN-Versions: ii xen-hypervisor-4.4-amd64 4.4.1-9+deb8u5 amd64 Xen Hypervisor on AMD64 ii xen-linux-system-3.16.0-4-amd64 3.16.7-ckt25-2 amd64

Dear All, Can''t start system because kernel can''t load file systems to and get the next error: modprobe: can''t load module microcode (kernel/arch/x86/kernel/microcode.ko): No such device done. Begin: Running /scripts/init-premount ... Begin: Requesting microcode update using per-core interface ... done. done. Begin: Mounting root file system ... Begin: Running

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9 Severity: grave Justification: renders package unusable Hi, I was running Debian Wheezy (amd64) and xen-hypervisor 4.1 on a Dell PowerEdge R720. Xen was working fine. Xen was configured with LVM Now, I'm trying Debian Jessie (amd64) and I have a strange problem. After booting, Xen seems to be working : /etc/init.d/xen status ? xen.service

On Wed, 2016-02-03 at 15:28 -0500, Konrad Rzeszutek Wilk wrote: > > > And I wonder if the XEN_DOMCTL_irq_permission aka, > > > xc_domain_irq_permission > > > had been called. I remember that at some point we missed it for > > > Xend.. > > > > > False alarm. > > It was all in Linux. Attached are four patches (the first two > are for