hyper-v FreeBSD 14.3 fails to boot under Hyper V

Z

zg123

During an attempt to create a new FreeBSD VM under Hyper V on Windows Server 2019, I am getting the following error:

The application encountered an error while attempting to change the state of 'VM name'.
'VM Name' failed to start.
Synthetic SCSI controller (Instance ID <guid>): Failed to Power on with Error 'The file or directory is corrupt and unreadable.'.
Attachment G:\temp\iso_name.iso' failed to open because of error 'The file or directory is corrupt and unreadable.'.

And then it goes on and on about the same as above.
Here's what I tried:
- Assign 'Read' permissions to 'Everyone', on the ISO and G:\temp\ where it was sitting (having previously gotten the same error on Desktop).
- Copy the ISO back to the old Windows Server 2016 (where it had been used to create an existing VM with the same OS) and try to create a new copy of the same VM successfully.
- Copy an ISO image of a different OS (Windows Server) to the same folder and successfully boot a brand-new VM from it. In all the 3 cases the VM type is 2.

IMO the above actions prove that there is no problem with either the ISO, or its copy, or the directory, or their permissions. I am left with blaming the combination of WS 2019 Hyper V and FreeBSD 14.3.
I can't believe that no one ever successfully booted FreeBSD 14.3 under WS 2019 Hyper V. This forum would have likely heard about any such problem. Am I missing something obvious in building this VM?
The specific flavor of FreeBSD is OpnSense soft router, which is hardened. Should that matter?
 
zg123 said:
OpnSense soft router
Click to expand...
OPNsense is not supported here.

DutchDaemon

Thread 'GhostBSD, pfSense, TrueNAS, and all other FreeBSD Derivatives'

Questions about 'derivative FreeBSDs', like
  • GhostBSD
  • TrueNAS
  • XigmaNAS
  • OPNsense
  • pfSense
  • BSD Router Project
  • NomadBSD
  • helloSystem
  • HardenedBSD
should be asked on the forums and/or mailing lists for these specific products. See below for links.

If you still think your questions should be asked here, beware of the following:

  • To show that you have indeed tried to get a solution from the forum or mailing list of the...
  • Thanks
  • Like
 
SirDice said:
OPNsense is not supported here.

DutchDaemon

Thread 'GhostBSD, pfSense, TrueNAS, and all other FreeBSD Derivatives'

Questions about 'derivative FreeBSDs', like
  • GhostBSD
  • TrueNAS
  • XigmaNAS
  • OPNsense
  • pfSense
  • BSD Router Project
  • NomadBSD
  • helloSystem
  • HardenedBSD
should be asked on the forums and/or mailing lists for these specific products. See below for links.

If you still think your questions should be asked here, beware of the following:

  • To show that you have indeed tried to get a solution from the forum or mailing list of the...
  • Thanks
  • Like
Click to expand...
It's not supported anywhere, TBH. The question is about booting the FreeBSD which it is under the hood.
 
Just for giggles, I built a VMWare machine from the same image, and once it passes the initial loading screen with ASCII art, it then goes into an endless loop, being unable to load getty.
Somehow WS 2016 is not having any problems with it, whereas WS 2019 and VMWare 6 do.
 
You must log in or register to reply here.
Back
Top