On 01.07.11 at 13:52, Petr Tesarik
wrote: Dne Pá 1. července 2011 12:30:53 Jan Beulich napsal(a): On 01.07.11 at 11:49, Petr Tesarik
wrote: Since there's no 32-bit hypervisor, it doesn't make much sense to run a 32-bit dom0 on top of 64-bit Xen. That's really the main question here; the removal of the 32-bit hypervisor is more or less decided already.
However, since there will still be a kernel-xen (that can be used as domU), will you please make sure that it will refuse to boot rather than fail silently if somebody tries
How is "refuse to boot" different from "fail silently"? The kernel can't (rely on being able to) issue user visible messages this early, and there's currently no mechanism for Xen to tell whether a particular kernel is Dom0-capable (nor can I immediately see a strait forward and backward compatible way to add one).
My idea was that kernel-xen would keep just enough awareness of its environments that it can boot at least to a point to give a user-visible warning.
If this doesn't work, could we e.g. develop a mechanism to allow the dom0 kernel to fail on boot and return to the hypervisor, passing a fail message to be printed out by Xen?
Implying that everyone has a serial console installed. Xen doesn't by default print to the screen anymore once it passes control to Dom0. We can certainly come up with a mechanism to announce the Dom0 kernel's capabilities to Xen, but it'll require a little bit of thought so this doesn't turn out a hack and is backward compatible. Jan -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org