26.10.2015 11:54, Gavin Pidgley wrote:
> Package: qemu-system-x86
> Version: 2.1+dfsg-12~bpo70+1
> Severity: important
>
> Dear Maintainer,
>
> We are seeing guests lockup/hang with qemu. The guests hang with 100% CPU
> usage. The problem seems to be storage/IO related, but there is not
>
Is it possible that these changes can be backported? I can see 2.4 is
available in "testing", but won't be released for the foreseeable future
and I presume 2.4 itself it unlikely to get backported to Wheezy anyhow.
It would be greatly appreciated if these specific fixes can be
backported at
> Not by me, and it is very unlikely the release team can be convinced the
> result is safe. These patches applies on top of event loop refactoring
> happened during 2.4 release cycle and requires relatively large number
> of other changes all over.
Okay, does that mean this is going to put
28.10.2015 17:41, Gavin Pidgley пишет:
> Is it possible that these changes can be backported?
Not by me, and it is very unlikely the release team can be convinced the
result is safe. These patches applies on top of event loop refactoring
happened during 2.4 release cycle and requires relatively
Package: qemu-system-x86
Version: 2.1+dfsg-12~bpo70+1
Severity: important
Dear Maintainer,
We are seeing guests lockup/hang with qemu. The guests hang with 100% CPU
usage. The problem seems to be storage/IO related, but there is not necessarily
high IO happening on the host at the time the guest
5 matches
Mail list logo
