public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"lersek@redhat.com" <lersek@redhat.com>,
	"ard.biesheuvel@linaro.org" <ard.biesheuvel@linaro.org>,
	Sean Brogan <sean.brogan@microsoft.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [PATCH] .azurepipelines: Enable CI for OvmfPkg and EmulatorPkg
Date: Mon, 30 Mar 2020 21:29:56 +0000	[thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F5B9EF161B@ORSMSX113.amr.corp.intel.com> (raw)
In-Reply-To: <39cb76cf-4c89-24dd-b03c-b2dcdf1d7af4@redhat.com>

Hi Laszlo,

I think using the QEMU feature to map a path from the host as 
a FAT formatted driver has value to provision QEMU with a set
of target tests to run.  I agree there is no persistent storage
of writes to this type of drive.  I believe writes are supported
if file state is needed during the single boot of QEMU.

In order to get test results out of QEMU back to the host,
I was considering the use of consoles mapped as named pipes
and send all test results out the console device and the
host can parse the logs.

I have not had good experiences trying to build virtual
disks, provision them, map them into QEMU, and remount
from host to collect test results.  Slow operations and
cumbersome to mount/unmount from the host (at least from
Windows environments).

Mike

> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On
> Behalf Of Laszlo Ersek
> Sent: Monday, March 30, 2020 2:11 PM
> To: devel@edk2.groups.io; ard.biesheuvel@linaro.org; Sean
> Brogan <sean.brogan@microsoft.com>
> Subject: Re: [edk2-devel] [PATCH] .azurepipelines: Enable
> CI for OvmfPkg and EmulatorPkg
> 
> On 03/30/20 08:07, Ard Biesheuvel wrote:
> > On Mon, 30 Mar 2020 at 01:16, Sean via Groups.Io
> > <sean.brogan=microsoft.com@groups.io> wrote:
> >>
> >> Ard/Laszlo or anyone familiar with QEMU.
> >>
> >> I read up on the ovmf readme and the qemu wiki but
> still have a few issues i am hoping for quick/easy
> answers.
> >>
> >> 1. How do i programmatically exit the emulator.
> Seems like uefi shell > reset just reboots.  Other ideas?
> >
> > 'reset' is supposed to do that. Use 'reset -s' to kill
> the VM
> >
> >> 2. Is there an easy way to map a local file system so
> that i can setup a startup.nsh?
> >>
> >
> > As Andrew points out, use '-hda fat:<path>' and it will
> be exposed to
> > the VM as a FAT formatted block device.
> 
> Note that it will not offer (functional, or any) write
> support.
> 
> I prefer "mtools" or "guestfish" for formatting and
> populating a virtual
> disk image.
> 
> None of those are easy ways, admittedly -- I'm not
> offering some
> examples right now exactly because I have to sit down and
> think about
> them every time I need them. :) If there's interest in
> such commands, I
> could hack up something, but then please give me some
> specs, and I'll
> have to work on these things in the morning (while my
> brain is still not
> mush).
> 
> Thanks
> Laszlo
> 
> 
> 


  reply	other threads:[~2020-03-30 21:29 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26  7:04 [PATCH] .azurepipelines: Enable CI for OvmfPkg and EmulatorPkg Zhang, Shenglei
2020-03-26  7:11 ` [edk2-devel] " Rebecca Cran
2020-03-26  7:50   ` [EXTERNAL] " Bret Barkelew
2020-03-26  8:43 ` Ard Biesheuvel
2020-03-26  8:45   ` Zhang, Shenglei
2020-03-27 14:36   ` Laszlo Ersek
2020-03-27 14:39     ` Laszlo Ersek
2020-03-26 23:26 ` [EXTERNAL] " Bret Barkelew
2020-03-27  0:00   ` Michael D Kinney
2020-03-27  0:14     ` Bret Barkelew
2020-03-27  1:59       ` Michael D Kinney
2020-03-27  2:04         ` Liming Gao
2020-03-27  2:50           ` Sean
2020-03-28  2:29 ` [edk2-devel] " Sean
2020-03-28  2:38   ` Rebecca Cran
2020-03-28  2:48     ` Sean
2020-03-28 19:29       ` Sean
2020-03-28 20:28         ` Ard Biesheuvel
2020-03-28 21:47           ` Sean
2020-03-29  8:51             ` Ard Biesheuvel
2020-03-29 23:16               ` Sean
2020-03-30  1:44                 ` Andrew Fish
2020-03-30  6:07                 ` Ard Biesheuvel
2020-03-30  9:31                   ` Sean
2020-03-30  9:35                     ` Ard Biesheuvel
2020-03-30 17:00                       ` Sean
2020-03-30 17:04                         ` Ard Biesheuvel
2020-03-30 17:11                           ` Sean
2020-03-30 17:44                             ` Ard Biesheuvel
2020-03-30 19:07                               ` Sean
2020-03-30 19:51                                 ` Ard Biesheuvel
2020-03-30 20:56                               ` Laszlo Ersek
2020-03-30 21:03                                 ` Sean
2020-03-30 21:13                                   ` Rebecca Cran
2020-04-05  6:39                                   ` Sean
2020-04-06 10:11                                     ` Ard Biesheuvel
2020-04-07 13:21                                       ` Laszlo Ersek
2020-03-30 21:22                                 ` Ard Biesheuvel
2020-03-31 12:13                                   ` Laszlo Ersek
2020-03-30 21:11                   ` Laszlo Ersek
2020-03-30 21:29                     ` Michael D Kinney [this message]
2020-03-30 21:42                       ` Sean
2020-03-30 21:46                         ` Ard Biesheuvel
2020-03-31  6:31                           ` Sean
2020-03-31  6:40                             ` Ard Biesheuvel
2020-03-31 16:26                               ` Sean
2020-03-31 16:32                                 ` Ard Biesheuvel
2020-03-30 22:45                         ` Rebecca Cran
2020-03-30 22:58                         ` Michael D Kinney
2020-03-31 12:27                       ` Laszlo Ersek

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=E92EE9817A31E24EB0585FDF735412F5B9EF161B@ORSMSX113.amr.corp.intel.com \
    --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