From: "Shi, Steven" <steven.shi@intel.com>
To: Laszlo Ersek <lersek@redhat.com>, edk2-devel-01 <edk2-devel@ml01.01.org>
Cc: "Tian, Feng" <feng.tian@intel.com>,
"Justen, Jordan L" <jordan.l.justen@intel.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Fan, Jeff" <jeff.fan@intel.com>,
"Zeng, Star" <star.zeng@intel.com>
Subject: Re: Testing SMM with QEMU, KVM and libvirt
Date: Tue, 21 Feb 2017 09:22:22 +0000 [thread overview]
Message-ID: <06C8AB66E78EE34A949939824ABE2B313B495660@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <d0420e8f-3653-7c0c-717c-85104b5006f3@redhat.com>
Hi Laszlo,
I wonder if you could offer a Ubuntu version wiki for the Testing-SMM-with-QEMU,-KVM-and-libvirt? I'm trying to port your steps to my Ubuntu 16.04, but meet lots of troubles. The Ubuntu apt-get virsh version is too old to support smm feature in your ovmf.fedora.q35.template, and I have to build the new version libvirt by myself. I meet lots of failures when configure the new version virsh, and wonder if you could help.
Steven Shi
Intel\SSG\STO\UEFI Firmware
Tel: +86 021-61166522
iNet: 821-6522
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Laszlo Ersek
> Sent: Tuesday, February 7, 2017 9:07 PM
> To: edk2-devel-01 <edk2-devel@ml01.01.org>
> Cc: Tian, Feng <feng.tian@intel.com>; Justen, Jordan L
> <jordan.l.justen@intel.com>; Yao, Jiewen <jiewen.yao@intel.com>; Kinney,
> Michael D <michael.d.kinney@intel.com>; Fan, Jeff <jeff.fan@intel.com>; Zeng,
> Star <star.zeng@intel.com>
> Subject: [edk2] Testing SMM with QEMU, KVM and libvirt
>
> Hi,
>
> I've added the following article to the TianoCore wiki:
>
> https://github.com/tianocore/tianocore.github.io/wiki/Testing-SMM-with-
> QEMU,-KVM-and-libvirt
>
> It should help both Windows and Linux desktop users build a KVM test
> machine / environment that closely resembles mine. Such an environment
> is useful for testing and regression-testing new MP and SMM features and
> bugfixes.
>
> The initial setup is not short, but once you got it up and running, it's
> very simple to rebuild OVMF with the edk2 changes, install the firmware
> binary in the right place (see the article) and then click the Play
> button on the Fedora 25 and Windows 10 guests, to see the changes in action.
>
> If you have smaller updates or structural reorgs for the document,
> there's no need to ask me, just go ahead and do them.
>
> If some significant information is missing that you'd like me to add, I
> think I'd prefer new TianoCore BZs at this time (Product: Tianocore
> Feature Requests, Component: Web Content, Assignee: yours truly). I
> don't know when I'll have time again to dig into this.
>
> Sorry if I forgot someone off the CC list.
>
> Thanks!
> Laszlo
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2017-02-21 9:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 13:07 Testing SMM with QEMU, KVM and libvirt Laszlo Ersek
2017-02-21 9:22 ` Shi, Steven [this message]
2017-02-21 10:18 ` Laszlo Ersek
2017-02-23 5:11 ` Shi, Steven
2017-02-23 9:02 ` Laszlo Ersek
2017-02-23 9:07 ` Laszlo Ersek
2017-04-19 16:07 ` Blibbet
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=06C8AB66E78EE34A949939824ABE2B313B495660@shsmsx102.ccr.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