OPNsense Forum

Archive => 18.1 Legacy Series => Topic started by: RamGuy on April 12, 2018, 03:15:15 pm

Title: Windows Server 2016 - Not able to install OPNSense 18.1 or 17.7.5 in Hyper-V G.2
Post by: RamGuy on April 12, 2018, 03:15:15 pm
I'm having a lot of trouble with getting OPNsense installed in Hyper-V on a Windows Server 2016.

I noticed that the wiki claims OPNsense supports both Gen.1 and Gen.2 installations in Hyper-V but I can't get it to install at all.


Using "OPNsense-18.1-OpenSSL-dvd-amd64.iso" I will only get;

/boot/kernel/kernel text=0x161c868
elf64_loadimage: read failed
can't load file '/boot/kernel/kernel' : input/output error
can't load file '/boot/kernel/kernel' : input/output error
Error while including /boot/menu.rc in the line:
menu-display
/
Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel]...
/boot/kernel/kernel text=0x161c868
elf64_loadimage: read failed
can't load 'kernel'

Type '?' for a list of commands. 'help' for more detailed help.
OK


I've tried both regular boot and safe mode.



I have tried with 1GB, 2GB and 4GB RAM with and without dynamic memory enabled. I have tried with 80GB Dynamic VHDX, with 80GB FIXED VHDX and I have tried with VHDX on multiple drives on my server.


With and without Secure Boot enabled. With and without integration services enabled.




I decided to try 17.7.5 while at what as it and that gave me these results;

Using "OPNsense-17.7.5-OpenSSL-dvd-amd64.iso" I only get a endless list of;

vm_fault: pager read error, pid 1 (init)
vm_fault: pager read error, pid 1 (init)
vm_fault: pager read error, pid 1 (init)
vm_fault: pager read error, pid 1 (init)
vm_fault: pager read error, pid 1 (init)
vm_fault: pager read error, pid 1 (init)
vm_fault: pager read error, pid 1 (init)
vm_fault: pager read error, pid 1 (init)
vm_fault: pager read error, pid 1 (init)
vm_fault: pager read error, pid 1 (init)


I've tried both regular boot and safe mode.



I have tried with 1GB, 2GB and 4GB RAM with and without dynamic memory enabled. I have tried with 80GB Dynamic VHDX, with 80GB FIXED VHDX and I have tried with VHDX on multiple drives on my server.


With and without Secure Boot enabled. With and without integration services enabled.


Am I doing something wrong here?
Title: Re: Windows Server 2016 - Not able to install OPNSense 18.1 or 17.7.5 in Hyper-V G.2
Post by: Maurice on April 12, 2018, 04:38:10 pm
18.1 works fine with Hyper-V Gen2. 17.7 indeed had some known issues with Gen2. Tested with Windows Server 2012 R2 and Windows 10.

Does it fail immediately when booting the ISO or after installation (when booting from the VHDX)?

Did you verify the checksum of the ISO? Is it stored on a local drive?

(Settings I use for 18.1: Secure Boot disabled, 1024 MB RAM, Dynamic Memory disabled, dynamic VHDX.)
Title: Re: Windows Server 2016 - Not able to install OPNSense 18.1 or 17.7.5 in Hyper-V G.2
Post by: weust on April 12, 2018, 06:50:09 pm
Ramguy, we spoke on IRC. Did you try creating a new VM from scratch yet?
Title: Re: Windows Server 2016 - Not able to install OPNSense 18.1 or 17.7.5 in Hyper-V G.2
Post by: RamGuy on April 12, 2018, 11:05:07 pm
I have just concluded with something being fishy with the server or something. I did compare checksum on the ISO so its not corrupted. I even tried creating the VM using Hyper-V on my Windows 10 desktop and everything works just fine there, but upon exporting the VM and importing it on Hyper-V on the server I get the same;

/boot/kernel/kernel text=0x161c868
elf64_loadimage: read failed
can't load file '/boot/kernel/kernel' : input/output error
can't load file '/boot/kernel/kernel' : input/output error
Error while including /boot/menu.rc in the line:
menu-display
/
Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel]...
/boot/kernel/kernel text=0x161c868
elf64_loadimage: read failed
can't load 'kernel'

Type '?' for a list of commands. 'help' for more detailed help.
OK


During boot. It just seems incapable of doing a EFI boot of OPNsense, both from a already installed VHDX and from the ISO.

I had to settle with Gen.1 for now.