Processing control commands:
> reassign -1 xen-hypervisor-4.8-amd64
Bug #880554 [linux-image-4.9.0-4-amd64] xen domu freezes with kernel
linux-image-4.9.0-4-amd64
Bug reassigned from package 'linux-image-4.9.0-4-amd64' to
'xen-hypervisor-4.8-amd64'.
No longer marked as found in versions li
control: reassign -1 xen-hypervisor-4.8-amd64
On Sat, 2018-01-06 at 15:23 +0100, Valentin Vidic wrote:
> On Sat, Jan 06, 2018 at 03:08:26PM +0100, Yves-Alexis Perez wrote:
> > According to that link, the fix seems to be configuration rather than
> > code.
> > Does this mean this bug against the
On Sat, Jan 06, 2018 at 03:08:26PM +0100, Yves-Alexis Perez wrote:
> According to that link, the fix seems to be configuration rather than code.
> Does this mean this bug against the kernel should be closed?
Yes, the problem seems to be in the Xen hypervisor and not the Linux
kernel itself. The
On Fri, 2017-11-17 at 07:39 +0100, Valentin Vidic wrote:
> Hi,
>
> The problem seems to be caused by the new multi-queue xen blk driver
> and I was advised by the Xen devs to increase the gnttab_max_frames=256
> parameter for the hypervisor. This has solved the blocking issue
> for me and it has
Hi,
The problem seems to be caused by the new multi-queue xen blk driver
and I was advised by the Xen devs to increase the gnttab_max_frames=256
parameter for the hypervisor. This has solved the blocking issue
for me and it has been running without problems for a few months now.
I/O to LUNs
We're having the same problem here. For some reason, only 2 domUs are
affected (the dom0 has a total of 22 domUs, 14 of those are running
Debian stretch, and 13 of those are running Linux 4.9.51-1).
The `xl console` output of the first domU (according to our monitoring
it hangs since
Update:
First of all: Forget my observation about the 'system boot time'. I
mixed up something, the dom0 boot time was increased, but this happened
probably due to the not (well/propper) handled lvm thin activation
during system boot.
One last thing I pulled from domu with the original
Update:
Sadly the my productive system froze in the early afternoon today again
with the older kernel as well (4.9.30-2+deb9u5). so that wasn't a temp
workaround. Paradoxically nothing showed up on the xl console (within a
screen) at dom0. No errors, nothing, the vm just stopped responding.
Package: linux-image-4.9.0-4-amd64
Version: 4.9.51-1
Severity: critical
As I can tell right now, the domu system simply freezes. The logs simply
end at some point until the new reboot stuff comes up. Sometimes it's
still possible to log on to the system, but nothing really works. It is
like
9 matches
Mail list logo
