On Wed, 2011-09-14 at 10:14 +0300, Pekka Enberg wrote:
> On Wed, Sep 14, 2011 at 10:11 AM, Sasha Levin <levinsasha928@xxxxxxxxx> wrote:
> > We currently don't have sufficient support for mouse, this patch disables
> > it by default to prevent the delay when booting.
> >
> > It should be removed once sufficient mouse support is added.
> >
> > Signed-off-by: Sasha Levin <levinsasha928@xxxxxxxxx>
> > ---
> > tools/kvm/builtin-run.c | 3 ++-
> > 1 files changed, 2 insertions(+), 1 deletions(-)
> >
> > diff --git a/tools/kvm/builtin-run.c b/tools/kvm/builtin-run.c
> > index 465bbe7..2795115 100644
> > --- a/tools/kvm/builtin-run.c
> > +++ b/tools/kvm/builtin-run.c
> > @@ -736,7 +736,8 @@ int kvm_cmd_run(int argc, const char **argv, const char *prefix)
> > vidmode = 0;
> >
> > memset(real_cmdline, 0, sizeof(real_cmdline));
> > - strcpy(real_cmdline, "notsc noapic noacpi pci=conf1 reboot=k panic=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1");
> > + strcpy(real_cmdline, "notsc noapic noacpi pci=conf1 reboot=k panic=1 i8042.direct=1 "
> > + "i8042.dumbkbd=1 i8042.nopnp=1 i8042.noaux=1");
> > if (vnc || sdl) {
> > strcat(real_cmdline, " video=vesafb console=tty0");
> > } else
>
> What's the problem? IIRC mouse works just fine in VNC mode?
The problem is that it causes a pretty long delay (~5-6 sec) during
boot.
VNC mouse could use some more love before I'd say it's good, one example
that the host mouse and guest mouse aren't synced.
--
Sasha.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
