Unable to boot Turnkey ISOs into several VM systems


#1

I’m probably doing something stupid but I’m not seeing so I apologize in advance.

I grabbed the mineos jessie ISO from the wiki and tried to install it clean both into a unRAID VM and a WIndows Hyper-V VM. In both instances neither system recognized the ISO as a bootable device and went no further than the initial power on screen.

Checking the jessie ISO (And the tkl ISO to confirm I’m not goofing up the download) I only see two directories “casper” and “isolinux” which looks like it should work, but I do not see any root files that would allow the ISO to actually bootable.

Am I just being dense and I need a base Linux distro (IIRC debian is the original base) for the turnkey install and the ISO is not a standalone install, or am I right in my understanding that Turnkey is a standalone install and doing something else incredibly stupid?


#2

In addition to casper and isolinux, you might also see [BOOT].

I don’t believe the directory is actually called [BOOT], but just that the ISO viewer I’m using designated it that way. In Windows 10 Mount, as an example, it is entirely absent.

Inside is (according to my viewer 7zip) Boot-NoEmul.img which would constitute the bootable portion of the CD filesystem.

The ISO is definitely a standalone install, but you’re probably not doing anything stupid; we’re just not sure why your unRAID VM or Hyper-V is not booting it.

Here’s what you should expect to see:

Anybody else here with experience with those two VM/hypervisor softwares have any clues for this non-boot?


#3

I have been attempting to use the turnkey iso to setup a VM on my FreeNAS server. It will not boot to it either.

I have also noticed the [BOOT] folder missing in windows, but visible in 7zip with the .img file in it.


#4

FreeNAS only seems to have decent support for UEFI VM’s… it looks like this iso needs to be updated to make it UEFI compatible, I would imagine that would fix most of the issues with a lot of these hypervisors.


#5

Just had this problem for Hyper-V
It was solved by using Gen-1 instead of Gen-2 in Hyper-V