All of lore.kernel.org
 help / color / mirror / Atom feed
From: joeyli <jlee@suse.com>
To: JBottomley@parallels.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fwd: UEFI Secure boot using qemu-kvm
Date: Thu, 28 Jun 2012 18:24:51 +0800	[thread overview]
Message-ID: <1340879091.6196.147.camel@linux-s257.site> (raw)
In-Reply-To: <CAGLnvc-hLpUZaaOkeWMRtYefwL5goxuWP_99FyAzem7s_mncPg@mail.gmail.com>

Hi James, 

於 四,2012-06-28 於 18:11 +0800,lee joey 提到:
> 
> 
> ---------- Forwarded message ----------
> From: joeyli <jlee@suse.com>
> Date: 2012/6/28
> Subject: Re: UEFI Secure boot using qemu-kvm
> To: JBottomley@parallels.com
> Cc: linux-kernel@vger.kernel.org
> 
> 
> Hi James,
> 
> On Wed, Jun 27, 2012 at 06:34:05PM +0100, James Bottomley wrote:
> 
> > The purpose of this email is to widen the pool of people who are
> playing
> > with UEFI Secure boot.  The Linux Foundation Technical Advisory
> Board
> > have been looking into this because it turns out to be rather
> difficult
> > to lay your hands on real UEFI Secure Boot enabled hardware.
> 
> 
> 
> I am following your approach to reproduce your UEFI environment with
> qemu-kvm. After run qemu-system-x86_64 the kvm launched and go to UEFI
> shell success. So far so good!
> 
> But, I got a problem is the keyboard layout is not US keyboard, So I
> need build a mapping table for reference when key-in any letter:
> 
> [               e
> /               x
> s               i
> enter           t
> down            enter
> page up         down
> ...
> 
> 
> Did you meet this issue on your side?
> 

I just found this issue only happen on when I used ssh connect to the
machine that setup environment then run qemu-kvm.

When direct launch qemu-kvm on the machine, there have no keyboard
layout problem. Not sure this problem is dependent to qemu or UEFI
image.


Thanks a lot!
Joey Lee



  parent reply	other threads:[~2012-06-28 10:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-28 10:01 UEFI Secure boot using qemu-kvm joeyli
2012-06-28 10:22 ` James Bottomley
2012-06-28 10:49   ` joeyli
     [not found] ` <CAGLnvc-hLpUZaaOkeWMRtYefwL5goxuWP_99FyAzem7s_mncPg@mail.gmail.com>
2012-06-28 10:24   ` joeyli [this message]
2012-06-30 16:21     ` Fwd: " joeyli
2012-07-12 22:17       ` Khalid Aziz
2012-07-19  9:41         ` James Bottomley
2012-07-19 15:55           ` Khalid Aziz

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=1340879091.6196.147.camel@linux-s257.site \
    --to=jlee@suse.com \
    --cc=JBottomley@parallels.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.