|
On 24/09/2014 6:43 PM, Ian Campbell
wrote:
On Wed, 2014-09-24 at 11:23 +0100, Stefano Stabellini wrote:On ARM (and on PV on HVM x86) we want vfb to work by default if the xenstore keys are there. But I don't think that it means we need to wait 30 secs for it at boot. What is a reasonable amount of time to wait for on a slow and overcommitted system? Maybe 5 to 10 secs?NB there are already two classes of wait. Non-essential (xenbus_probe_frontend.c's wording) wait 30s essential wait for an additional 270s (so 300s total). Non-essential appears to be vfb and vkbd (but not mouse?). We could certainly consider reducing the 30 (and increasing the 270 to correspond). Hello Debian Kernel, Circling back after 11 months, there doesn't seem to be much progress on this issue (30 seconds hang during VM boot due to xenbus_probe_frontend in EC2; http://bugs.xenproject.org/xen/bug/43). Is it feasible to change the Debian linux-image-amd64 kernel to have: -CONFIG_XEN_FBDEV_FRONTEND=y +CONFIG_XEN_FBDEV_FRONTEND=m ... so that in the EC2 environment I can blacklist the module and not have the boot delay (ie, in Jessie, linux-image-3.16.0-4-amd64)? Looks like it was a loadable module previously in the 686-bigmem kernels circa 2.6.28 in 2009. Ta. (Original thread from Sept 2014: https://lists.debian.org/debian-kernel/2014/09/msg00229.html) --
Mobile: +61 422 166 708, Email: james_AT_rcpt.to |