xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Sven Köhler" <sven.koehler@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: xen + pvops dom0: keyboard not working
Date: Fri, 10 Jun 2011 15:33:46 -0400	[thread overview]
Message-ID: <20110610193346.GA25739@dumpdata.com> (raw)
In-Reply-To: <istp58$o04$1@dough.gmane.org>

On Fri, Jun 10, 2011 at 08:52:31PM +0200, Sven Köhler wrote:
> Hi,
> 
> when booting xen 4.1 with latest konrad/stable/2.6.39.x branch (both
> 64bit) under virtualbox, the keyboard is seriously broken. I haven't

What is "seriously broken"? And what about serial logs, /proc/interrupts
etc?
> tested on real hardware yes, but without xen, the kernel works fine.
> 
> I see the same issue when booting 3.0-rc1.

There was one patch added in past 3.0-rc2 to fix PS/2 keyboards
not working right. Not sure if I merged it in stable/2.6.39.x.
Anyhow, you can get the fix by polling the latest linus/master


> 
> Strange thing is:
> the old 2.6.18 kernel with xen 4.1 inside virtualbox is just fine.
> 
> Do you consider this a bug? If so, I will try to provide additional
> information. Or do you think this might be a bug in virtualbox?

No idea. without some idea of what is broken, or what the
proc/interrupts, or what the linux kernel says about the keyboard
I have no idea.

> 
> 
> Regards,
>   Sven
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

  reply	other threads:[~2011-06-10 19:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-10 18:52 xen + pvops dom0: keyboard not working Sven Köhler
2011-06-10 19:33 ` Konrad Rzeszutek Wilk [this message]
2011-06-10 20:20   ` Sven Köhler
2011-06-10 21:06     ` Sven Köhler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110610193346.GA25739@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=sven.koehler@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).