From 0cbaa0aacf83523a6887a1ebb2c6adb8ea04e620 Mon Sep 17 00:00:00 2001 From: David Scott Date: Mon, 14 Mar 2011 16:25:32 +0000 Subject: [PATCH] Add a conclusion --- posts/2011-03-14-pvfb.mdwn | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/posts/2011-03-14-pvfb.mdwn b/posts/2011-03-14-pvfb.mdwn index 011efb7..587387a 100644 --- a/posts/2011-03-14-pvfb.mdwn +++ b/posts/2011-03-14-pvfb.mdwn @@ -94,4 +94,18 @@ an error in the X log: and a non-working pointer. The workaround I described above tells the X server to ignore the relative axes and to really expect absolute co-ordinates. +Conclusion +---------- + + * The PVFB code is present and works at least as well as "vncterm" for + text-based stuff. + * The X configuration needs to be slightly tweaked -- it doesn't just work + out of the box. This is still better than "vncterm" where X will never + work (unless you like ascii-art) + * We should consider switching to PVFB by default, on a guest-per-guest + basis (after checking the kernels have new enough frontends) + * We should develop a plan to fix the niggles with X, particularly the + relative vs absolute mouse. If necessary perhaps we need to supply the + guest with two pointers: one relative-only and one absolute-only? + [[!tag tags/XCP]]