On Fri, Feb 10, 2017 at 09:27:46AM +0100, Håkon Alstadheim wrote:
> I just tried to provoke the bug, after applying your patch and
> re-enabling tmem, but it seems there are more variables in the equation
> to make a crash happen. Before this week the VM in question would
> reliably crash/hang on
I just tried to provoke the bug, after applying your patch and
re-enabling tmem, but it seems there are more variables in the equation
to make a crash happen. Before this week the VM in question would
reliably crash/hang on boot during the past month and through several
re-boots of the dom0.
I
Den 2017-02-09 18:30, skrev Roger Pau Monné:
On Mon, Feb 06, 2017 at 12:31:20AM +0100, Håkon Alstadheim wrote:
I get the BUG below in dom0 when trying to start a windows 10 domu
(hvm,
with some pv-drivers installed ) . Below is "xl info", then comes
dmesg
output, and finally domu config
On Mon, Feb 06, 2017 at 12:31:20AM +0100, Håkon Alstadheim wrote:
> I get the BUG below in dom0 when trying to start a windows 10 domu (hvm,
> with some pv-drivers installed ) . Below is "xl info", then comes dmesg
> output, and finally domu config attached at end.
>
> This domain is started very
CC Roger and Konrad
On Mon, Feb 06, 2017 at 12:31:20AM +0100, Håkon Alstadheim wrote:
> I get the BUG below in dom0 when trying to start a windows 10 domu (hvm,
> with some pv-drivers installed ) . Below is "xl info", then comes dmesg
> output, and finally domu config attached at end.
>
> This
I get the BUG below in dom0 when trying to start a windows 10 domu (hvm,
with some pv-drivers installed ) . Below is "xl info", then comes dmesg
output, and finally domu config attached at end.
This domain is started very rarely, so may have been broken for some
time. All my other domains ar
