From: Jon Doron <arilou@gmail.com>
To: Roman Kagan <rvkagan@yandex-team.ru>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
kvm@vger.kernel.org, linux-hyperv@vger.kernel.org
Subject: Re: [PATCH v2 0/1] x86/kvm/hyper-v: Add support to SYNIC exit on EOM
Date: Thu, 7 May 2020 06:00:37 +0300 [thread overview]
Message-ID: <20200507030037.GE2862@jondnuc> (raw)
In-Reply-To: <20200506084615.GA32841@rvkaganb>
On 06/05/2020, Roman Kagan wrote:
>On Wed, May 06, 2020 at 07:49:29AM +0300, Jon Doron wrote:
>> Thanks Roman, I see your point, it's important for me to get the EDK2
>> working properly not sure why it's not working for me.
>
>As I wrote a good deal of that code I hope I should be able to help (and
>I'd be interested, too). How exactly does the "not working" look like?
>
Basically when I built the BIOS from the hv-scsi branch you pointed me
out to, the BIOS did not see the virtio-blk device to boot from, I
usually take the BIOS from (https://www.kraxel.org/repos/) but I will
try to build the latest EDK2 and see if it identifies the virtio-blk
device and boots from it, if that's the case perhaps i just need to
rebase your branch over the latest master of EDK2.
>Also I'm a bit confused as to why UEFI is critical for the work you're
>doing? Can't it be made to work with BIOS first?
>
The reason I want to have the UEFI option is because I need SecureBoot
to turn on VBS.
>> Do you know by any chance if the EDK2 hyperv patches were submitted and if
>> they were why they were not merged in?
>
>I do, as I'm probably the only one who could have submitted them :)
>
>No they were not submitted. Neither were the ones for SeaBIOS nor iPXE.
>The reason was that I had found no way to use alternative firmware with
>HyperV, so the only environment where that would be useful and testable
>was QEMU with VMBus. Therefore I thought it made no sense to submit
>them until VMBus landed in QEMU.
>
>Thanks,
>Roman.
Heh I see, well I'm really happy that you are here helping so we can try
and finally add VMBus to QEMU, I realize it's a big effort but I'm
willing to spend the time and do the required changes...
I'm working this only during my free time so things takes me longer than
usual (sorry for that..)
I will keep update on results once I get to test with latest EDK2 :)
Thanks,
-- Jon.
next prev parent reply other threads:[~2020-05-07 3:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 8:38 [PATCH v2 0/1] x86/kvm/hyper-v: Add support to SYNIC exit on EOM Jon Doron
2020-04-16 8:38 ` [PATCH v2 1/1] " Jon Doron
2020-04-16 12:00 ` [PATCH v2 0/1] " Roman Kagan
2020-04-16 12:54 ` Jon Doron
2020-04-17 10:42 ` Roman Kagan
2020-04-18 6:41 ` Jon Doron
2020-04-24 12:20 ` Jon Doron
2020-04-24 13:37 ` Roman Kagan
2020-04-25 6:16 ` Jon Doron
2020-05-02 14:47 ` Jon Doron
2020-05-03 19:19 ` Roman Kagan
2020-05-04 15:55 ` Vitaly Kuznetsov
2020-05-05 8:01 ` Roman Kagan
2020-05-05 10:38 ` Jon Doron
2020-05-05 20:00 ` Roman Kagan
2020-05-06 4:49 ` Jon Doron
2020-05-06 8:46 ` Roman Kagan
2020-05-07 3:00 ` Jon Doron [this message]
2020-05-08 14:29 ` Jon Doron
2020-05-08 16:56 ` Roman Kagan
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=20200507030037.GE2862@jondnuc \
--to=arilou@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=rvkagan@yandex-team.ru \
--cc=vkuznets@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).