Post Reply 
 
Thread Rating:
  • 1 Vote(s) - 1 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Hyper-V Gen 2
2017-05-26, 10:59
Post: #2
RE: Hyper-V Gen 2
(2017-05-25 17:40)mastacontrola Wrote:  We've determined the cause was introduced in:
https://github.com/ipxe/ipxe/commit/a0f6...d9663f5269

And made more difficult to patch with:
https://github.com/ipxe/ipxe/commit/276d...d5a93b20d6

By reverting the changes in these two commits, Gen 2 Hyper-V systems are able to boot.

I don't know if it's a big problem to correct for, or if simply reverting will be the best bet.

Those patches cannot simply be reverted. hv_map_hypercall() and hv_map_synic() are now used on the hv_unquiesce() path, and we rely on hv_map_hypercall() accepting a situation in which the guest OS ID MSR is already non-zero in order to recover from having our network connection dropped in the middle of an iSCSI boot: http://git.ipxe.org/ipxe.git/commitdiff/b91cc98.

How are you starting iPXE within your Gen 2 VM?

Michael
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
Hyper-V Gen 2 - mastacontrola - 2017-05-25, 17:40
RE: Hyper-V Gen 2 - mcb30 - 2017-05-26 10:59
RE: Hyper-V Gen 2 - mastacontrola - 2017-05-26, 12:23
RE: Hyper-V Gen 2 - mcb30 - 2017-05-26, 13:38
RE: Hyper-V Gen 2 - mastacontrola - 2017-05-27, 01:35
RE: Hyper-V Gen 2 - mastacontrola - 2017-05-31, 18:00
RE: Hyper-V Gen 2 - mcb30 - 2017-05-31, 18:05
RE: Hyper-V Gen 2 - mastacontrola - 2017-05-31, 18:48
RE: Hyper-V Gen 2 - mhiroaki - 2017-06-08, 13:57
RE: Hyper-V Gen 2 - mastacontrola - 2017-06-13, 14:45
RE: Hyper-V Gen 2 - NiKiZe - 2017-07-25, 16:35
RE: Hyper-V Gen 2 - NiKiZe - 2017-07-27, 10:58
RE: Hyper-V Gen 2 - mcb30 - 2017-07-28, 21:32
RE: Hyper-V Gen 2 - mastacontrola - 2017-07-31, 00:25



User(s) browsing this thread: 1 Guest(s)