On Wed, Oct 10, Konrad Rzeszutek Wilk wrote: > The commit 254d1a3f02ebc10ccc6e4903394d8d3f484f715e, titled > "xen/pv-on-hvm kexec: shutdown watches from old kernel" assumes that the > XenBus backend can deal with reading of values from: > "control/platform-feature-xs_reset_watches": > > ... a patch for xenstored is required so that it > accepts the XS_RESET_WATCHES request from a client (see changeset > 23839:42a45baf037d in xen-unstable.hg). Without the patch for xenstored > the registration of watches will fail and some features of a PVonHVM > guest are not available. The guest is still able to boot, but repeated > kexec boots will fail." > > Sadly this is not true when using a Xen 3.4 hypervisor and booting a PVHVM > guest. We end up hanging at:
This is sad. So far I have not seen reports like that with a sles11sp1 or sles11sp2 guest. Thats either because noone uses Xen 3.4+sles11 (or recent openSuSE) HVM guests, or because it happens to work with that combination. If the patch solves the issue: Acked-by: Olaf Hering <[email protected]> Olaf -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
