On 16/02/18 17:25, Jan Beulich wrote:
On 16.02.18 at 16:52, wrote:
>> On Fri, Feb 16, 2018 at 08:10:48AM -0700, Jan Beulich wrote:
>>> I've just had to deal with an early boot crash of Linux which occurred
>>> so early that even "earlyprintk=xen" did not produce any useful output.
>>> Hence t
>>> On 16.02.18 at 16:52, wrote:
> On Fri, Feb 16, 2018 at 08:10:48AM -0700, Jan Beulich wrote:
>> I've just had to deal with an early boot crash of Linux which occurred
>> so early that even "earlyprintk=xen" did not produce any useful output.
>> Hence the domain appeared to hang, while in fact i
On Fri, Feb 16, 2018 at 03:59:45PM +, Wei Liu wrote:
> On Fri, Feb 16, 2018 at 03:52:48PM +, Roger Pau Monné wrote:
> > On Fri, Feb 16, 2018 at 08:10:48AM -0700, Jan Beulich wrote:
> > > I've just had to deal with an early boot crash of Linux which occurred
> > > so early that even "earlypr
On Fri, Feb 16, 2018 at 03:52:48PM +, Roger Pau Monné wrote:
> On Fri, Feb 16, 2018 at 08:10:48AM -0700, Jan Beulich wrote:
> > I've just had to deal with an early boot crash of Linux which occurred
> > so early that even "earlyprintk=xen" did not produce any useful output.
> > Hence the domain
On Fri, Feb 16, 2018 at 08:10:48AM -0700, Jan Beulich wrote:
> I've just had to deal with an early boot crash of Linux which occurred
> so early that even "earlyprintk=xen" did not produce any useful output.
> Hence the domain appeared to hang, while in fact it had brought down its
> only vCPU. By
On 16/02/18 15:10, Jan Beulich wrote:
> --- a/xen/common/domain.c
> +++ b/xen/common/domain.c
> @@ -1321,6 +1321,22 @@ long do_vcpu_op(int cmd, unsigned int vc
> break;
>
> case VCPUOP_down:
> +for_each_vcpu ( d, v )
> +if ( v->vcpu_id != vcpuid && !test_bit(_VPF
