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 translating this to a shutdown, the situation will be
better recognizable.
Signed-off-by: Jan Beulich <jbeul...@suse.com>
--- 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_down, &v->pause_flags)
)
+ {
+ rc = 1;
+ break;
+ }
+
+ if ( !rc )
+ {
+ domain_shutdown(d, SHUTDOWN_poweroff);
+ break;
+ }
+
+ rc = 0;
+ v = d->vcpu[vcpuid];
+
#ifdef CONFIG_X86
if ( pv_shim )
rc = continue_hypercall_on_cpu(0, pv_shim_cpu_down, v);
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
