bhyve Bhyve on FreeBSD 14.1 -> Cannot Boot Windows 10 Installation File... Now Boots, but "Missing Drivers"

D

Dave-D

Last time I attempted to install Window 10 on Bhyve was about a year ago, everything went well.

I'm now running FreeBSD 14.1, trying to install Windows 10 64-bit as a Bhyve guest, but running into problems.

No matter what I try in the .conf file, installer bails because it cannot find the boot loader file.

Searched the web and may have found my issue:

"Windows 10 needs edk2-bhyve version 202202_10 (or less.)"

Version I'm currently running:

pkg info edk2-bhyve
g202308_04

Mentions "cannot find boot loader" issues with versions latter than 2022_10.

I need to run Windows 10 Pro
and Windows 11 Pro on Bhyve.


Can someone please help me?
 
I set up a windows 10 VM in bhyve recently and i didn't face with any problem. I use vm-bhyve to manage VMs.

Code: 
% pkg info edk2-bhyve bhyve-firmware
edk2-bhyve-g202308_5
bhyve-firmware-1.0_2

% cat /vm/w10/w10.conf
loader="uefi"
graphics="yes"
xhci_mouse="yes"
cpu=4
memory=8G

# put up to 8 disks on a single ahci controller.
# without this, adding a disk pushes the following network devices onto higher slot numbers,
# which causes windows to see them as a new interface
ahci_device_limit="8"

# ideally this should be changed to virtio-net and drivers installed in the guest
# e1000 works out-of-the-box
network0_type="e1000"
network0_switch="public"

disk0_type="nvme"
disk0_name="disk0.img"

# windows expects the host to expose localtime by default, not UTC
utctime="no"
uuid="xxxxxxxxxxxxxxxxxxxxxxxxxx"
network0_mac="xx:xx:xx:xx:xx:xx"
 
nxjoseph said:
nxjoseph said:
I set up a windows 10 VM in bhyve recently and i didn't face with any problem. I use vm-bhyve to manage VMs.

Code: 
% pkg info edk2-bhyve bhyve-firmware
edk2-bhyve-g202308_5
bhyve-firmware-1.0_2

% cat /vm/w10/w10.conf
loader="uefi"
graphics="yes"
xhci_mouse="yes"
cpu=4
memory=8G

# put up to 8 disks on a single ahci controller.
# without this, adding a disk pushes the following network devices onto higher slot numbers,
# which causes windows to see them as a new interface
ahci_device_limit="8"

# ideally this should be changed to virtio-net and drivers installed in the guest
# e1000 works out-of-the-box
network0_type="e1000"
network0_switch="public"

disk0_type="nvme"
disk0_name="disk0.img"

# windows expects the host to expose localtime by default, not UTC
utctime="no"
uuid="xxxxxxxxxxxxxxxxxxxxxxxxxx"
network0_mac="xx:xx:xx:xx:xx:xx"
Click to expand...
Click to expand...

My bhyve_firmware version is same as yours,
My edk2-bhyve version is g202308_4.

Putting in all your same settings (except for last two lines, which are auto-generated),
this is what I get:

1722634434578.png
 
Is this what you get when you booted the installation iso? If so, iso may be to blame, maybe it's corrupt.
 
nxjoseph said:
Is this what you get when you booted the installation iso? If so, iso may be to blame, maybe it's corrupt.
Click to expand...

I was just thinking the same. Maybe there's something wrong with the .iso I downloaded from the microsoft site.

For what its worth, the windows 11 .iso I downloaded at the same time produced the same result.

Seems like last time (a year ago) I generated an .iso from a windows 10 install dvd. Had no problems with that.

Maybe that's the next step...
 
I found the downloadable ISOs for w10 and w11 broken even for a normal physical machine install. They were asking for additional drivers. I had to make a USB stick with their downloadable image maker, that worked.
 
nxjoseph said:
I set up a windows 10 VM in bhyve recently and i didn't face with any problem. I use vm-bhyve to manage VMs.
Click to expand...
Using your exact config settings in my template.

nxjoseph said:
Is this what you get when you booted the installation iso? If so, iso may be to blame, maybe it's corrupt.
Click to expand...
Yes, the windows10 .iso file downloaded from microsoft's site was the problem. Install would not load with that file.

cracauer@ said:
I found the downloadable ISOs for w10 and w11 broken even for a normal physical machine install. They were asking for additional drivers. I had to make a USB stick with their downloadable image maker, that worked.
Click to expand...
I made an .iso from a recently purchased windows 10 usb stick, using dd.
Windows installer now loads, install routine starts,
but then grumbles about missing drivers.

"Load Driver:
A media driver your computer needs is missing.
No device drivers were found. Make sure that the installation media contains the correct drivers, and then click OK."

I didn't see any posts about how to solve this missing driver issue.
 
Dave-D said:
Windows installer now loads, install routine starts,
but then grumbles about missing drivers.

"Load Driver:
A media driver your computer needs is missing.
No device drivers were found. Make sure that the installation media contains the correct drivers, and then click OK."

I didn't see any posts about how to solve this missing driver issue.
Click to expand...
I have a NVME disk, if you don't have NVME disk, change it to ahci-hd

Code: 
disk0_type="ahci-hd"
disk0_name="disk0.img"

You might want to increase disk space given to Windows 10.

truncate -s 100GB /path/to/vm/disk0.img
 
nxjoseph said:
I have a NVME disk, if you don't have NVME disk, change it to ahci-hd
Click to expand...
Config is set to:
disk0_type="ahci-hd"

No matter what I do, I keep getting the same error:

"Load Driver:
A media driver your computer needs is missing.
No device drivers were found. Make sure that the installation media contains the correct drivers, and then click OK."

It then says, "This could be a DVD, USB or hard disk driver."


I'm wondering...
I made this .iso from a usb stick of windows 10 pro.

But, since I'm now attempting to run it from a hard drive,
could the differences in the two file systems (whatever those
differences might be) be causing this problem, which makes
the system ask for a driver so it can "interpret" the file it see's?

Last time I made the .iso from a CD copy of windows 10 pro.
Also a different file system, but had no problem.
???
 
Dave-D said:
I made an .iso from a recently purchased windows 10 usb stick, using dd.
Windows installer now loads, install routine starts,
but then grumbles about missing drivers.

"Load Driver:
A media driver your computer needs is missing.
No device drivers were found. Make sure that the installation media contains the correct drivers, and then click OK."

I didn't see any posts about how to solve this missing driver issue.
Click to expand...

Again, I could not provide that idiot ISO with whatever it wanted there, and I put considerable effort in.

I had to use their image making tool to prepare a USB stick on an existing (and still working) Windows machine.
 
cracauer@ said:
Again, I could not provide that idiot ISO with whatever it wanted there, and I put considerable effort in.
Click to expand...

The real problem is, in fact, that windows is junk.
And, the more we work with something like FreeBSD,
the more painful it gets to work with junk.

I have personally banished windows from my own enterprise,
this one is for a friend, who has to run windows because of industry supplied software.

What I'm trying to do is to (eventually) run windows 11 on bhyve to get around the
future hardware insanity and whatever else, running the required windows applications
in a window on a linux desktop, using something like RemoteApp.

I'm thinking this would be a much more stable environment, and better overall, if I can pull it off.

But, on second thought, maybe all of this early trouble is a warning sign.
if something breaks, I'm the one that has to deal with this insanity, their enterprise is down,
and I lose my sanity trying to get it going again.

Maybe this isn't such a good idea.

I'm just about ready to tell this friend that they will have to run windows on the clients
and deal with the insanity at that level.

Windows is what forced me out of the computer business.
Got sick of dealing with the increasing insanity and losing money
every time I was forced to work on it. I don't miss it and don't want to go back.

There is great pleasure in "doing without" windows, in what is still a "windows world,"
and coming out better, by far, for the effort.

Windows gives me a serious headache.
 
I just made a windows 10 .iso using brasero on devuan linux,
selected "copy CD,"
selected "copy to iso."

Now windows 10 installs on Bhyve.

This proves that my real problem is
finding a windows 10 .iso that works.
 
Me neither, I downloaded mine from there maybe a couple of weeks ago and used it yesterday to install my W10 VM under bhyve. Worked first try...
 
FreeBSD 14.1, my daily driver. I'm sure of this because my only Windows machine is my company's laptop which has USB disabled by policy, therefore it's impossible that I downloaded the ISO from there and then transferred on my laptop via memstick. Not only that, that Windows laptop has VPN software installed and thus cannot see my FreeBSD machine, so...
 
You must log in or register to reply here.
Back
Top