public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: "Kanagarajan, Vijaikumar" <Vijaikumar_Kanagarajan@mentor.com>
To: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
	"P T, Sarath" <Sarath_PT@mentor.com>
Subject: RE: [cip-dev] [isar-cip-core] [PATCH] scripts/start-efishell.sh: Add -nographic option
Date: Mon, 27 Jun 2022 08:47:42 +0000	[thread overview]
Message-ID: <54228d21f64f448a9e2bc77f9d975497@mentor.com> (raw)
In-Reply-To: <665fa99b-7ab0-1b8c-3662-c1f1ad7a8d4c@siemens.com>



> -----Original Message-----
> From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On
> Behalf Of Jan Kiszka
> Sent: 27 June 2022 13:44
> To: P T, Sarath <Sarath_PT@mentor.com>; cip-dev@lists.cip-project.org
> Subject: Re: [cip-dev] [isar-cip-core] [PATCH] scripts/start-efishell.sh: Add -
> nographic option
> 
> On 27.06.22 09:12, Sarath P T wrote:
> > From: sarath P T <Sarath_PT@mentor.com>
> >
> > When we launch the start-efishell.sh script for adding the keys into
> > OVMF firmware we faced gtk initialization failed error. So it seems we
> > need to open the OVMF in nographic mode, hence we added the required
> > option to the script.
> >
> 
> Which QEMU-Version? Which OVMF version (buster/bullseye/something
> else)?
> I'm not seeing this, but I'm facing other issues with that firmware provided by
> bullseye (a crash).

Nope. Not related to OVMF crashes. This is just to make the script work on headless systems/over ssh.

Sarath, 
Can you send a V2 with a modified commit message. The latter half is a bit misleading. Probably you meant
"open QEMU" and not OVMF.

Thanks,
Vijai Kumar K


> 
> > Signed-off-by: sarath P T <Sarath_PT@mentor.com>
> > ---
> >  scripts/start-efishell.sh | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/scripts/start-efishell.sh b/scripts/start-efishell.sh
> > index d451f43..0831f83 100755
> > --- a/scripts/start-efishell.sh
> > +++ b/scripts/start-efishell.sh
> > @@ -2,7 +2,7 @@
> >  ovmf_code=${OVMF_CODE:-/usr/share/OVMF/OVMF_CODE.secboot.fd}
> >  ovmf_vars=${OVMF_VARS:-./OVMF_VARS.fd}
> >  DISK=$1
> > -qemu-system-x86_64 -enable-kvm -M q35 \
> > +qemu-system-x86_64 -enable-kvm -M q35 -nographic \
> >                     -cpu host,hv_relaxed,hv_vapic,hv-spinlocks=0xfff -smp 2 -m 2G -
> no-hpet \
> >                     -global ICH9-LPC.disable_s3=1 \
> >                     -global isa-fdc.driveA= \
> Jan
> 
> --
> Siemens AG, Technology
> Competence Center Embedded Linux

      parent reply	other threads:[~2022-06-27  8:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220627071206.21277-1-Sarath_PT@mentor.com>
2022-06-27  8:14 ` [cip-dev] [isar-cip-core] [PATCH] scripts/start-efishell.sh: Add -nographic option Jan Kiszka
2022-06-27  8:23   ` Gylstorff Quirin
2022-06-27 12:52     ` Jan Kiszka
2022-06-27 12:57       ` Kanagarajan, Vijaikumar
2022-06-27 13:04         ` Jan Kiszka
2022-06-27  8:47   ` Kanagarajan, Vijaikumar [this message]

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=54228d21f64f448a9e2bc77f9d975497@mentor.com \
    --to=vijaikumar_kanagarajan@mentor.com \
    --cc=Sarath_PT@mentor.com \
    --cc=cip-dev@lists.cip-project.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox