Hi,

I tried it once with a custom ISO but didn't get any further than the
OpenBSD UEFI boot loader.  At this point, it couldn't find the disk so
I couldn't get to boot OpenBSD.  But this was in the early stages of
our UEFI support.

So we seem to miss some EFI drivers for Hyper-V Gen 2.  If you get to
the boot loader and it finds the disk, you still might not be able to
get display output if it doesn't use an efifb(4)-compatible display.

btw. Is there any reason or benefit to use Gen 2?  AFAIK, it is only
for Windows for secure boot etc.  I think Gen 1 is fine for OpenBSD,
you even have the hvn(4) and the hyperv(4) drivers now.  Even the
latest machines in Azure are Gen 1-based.

Reyk

On Mon, Mar 27, 2017 at 10:07:03AM +0200, Markus Rosjat wrote:
> Hi there,
> 
> like the topic says I look for some feedback here. I try to set up a Gen 2
> Hyper-V VM (Gen 1 is really not a problem) so I need to boot with a UEFI
> Medium. Since the normal iso doesnt provide that I took the following
> approch:
> 
>  1. I created a USB stick from installXX.fs
>  2. verified that I could boot from the stick
>  3. created a VHDX from the stick
>  4. Attached it to a Gen 2 VM
>  5. booted the VM and here Im stuck for now
>     It starts to bood but instead of showing me all the nice dmesg
>     stuff I would expect  it just went black.
> 
> but the rest of the way would look like this
> 
>  6. Install OpenBSD on another VHDX
>  7. dettach the first VHDX
> 
> So the question really is, do I miss a step or is it just not possible at
> the moment to get it working with Gen 2 VMs? The secure boot feature of the
> VM is disabled.
> 
> Regards
> 
> -- 
> Markus Rosjat    fon: +49 351 8107223    mail: [email protected]
> 
> G+H Webservice GbR Gorzolla, Herrmann
> K??nigsbr??cker Str. 70, 01099 Dresden
> 
> http://www.ghweb.de
> fon: +49 351 8107220   fax: +49 351 8107227
> 
> Bitte pr??fen Sie, ob diese Mail wirklich ausgedruckt werden muss! Before
> you print it, think about your responsibility and commitment to the
> ENVIRONMENT
> 

-- 

Reply via email to