From: "Gerd Hoffmann" <kraxel@redhat.com>
To: "Boeuf, Sebastien" <sebastien.boeuf@intel.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: EFI shell with microvm
Date: Thu, 6 Jan 2022 13:44:01 +0100 [thread overview]
Message-ID: <20220106124401.btcx5ykka2k37sae@sirius.home.kraxel.org> (raw)
In-Reply-To: <BY5PR11MB4401FFB398D23229FF3A6636EA4C9@BY5PR11MB4401.namprd11.prod.outlook.com>
On Thu, Jan 06, 2022 at 11:25:37AM +0000, Boeuf, Sebastien wrote:
> Hi Gerd,
>
> I was looking at a way to add support for EFI shell interaction with Cloud Hypervisor when
> I realized you added the support for microvm with commit 55f47d22998.
> I have been able to hack OvmfPkgX64 similarly to get it to work, but here are two follow up
> questions:
How do you want interact? Serial console? That should work just fine
with OvmfPkgX64.
qemu-system-x86_64 -nographic -bios Build/OvmfX64/DEBUG_GCC5/FV/OVMF.fd -net none
Possibly you have to add the cloud hypervisor pci id somewhere so isa
lpc and serial line driver are initialized properly. SioBusDxe looks
like a hot candidate.
microvm has no lpc bridge, so I had to do it in a different way ...
> 2. I can see the shell but I can't interact with it, do you have a similar behavior with microvm
> or is it because I'm missing the interrupt support?
Works fine for me.
qemu-system-x86_64 -nographic -machine microvm,rtc=on -bios Build/MicrovmX64/DEBUG_GCC5/FV/MICROVM.fd
HTH,
Gerd
next prev parent reply other threads:[~2022-01-06 12:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 11:25 EFI shell with microvm Boeuf, Sebastien
2022-01-06 12:44 ` Gerd Hoffmann [this message]
2022-01-06 13:08 ` Boeuf, Sebastien
2022-01-07 12:07 ` Gerd Hoffmann
2022-01-07 13:06 ` Boeuf, Sebastien
2022-01-07 13:37 ` Gerd Hoffmann
2022-01-10 0:16 ` Min Xu
2022-01-10 9:05 ` Boeuf, Sebastien
2022-01-07 14:12 ` Boeuf, Sebastien
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-list 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=20220106124401.btcx5ykka2k37sae@sirius.home.kraxel.org \
--to=devel@edk2.groups.io \
/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