Missing driver during windows install

Errandil · March 17, 2022, 7:16pm

Hi,
I have issues with installing a Windows 11 VM.
I followed the YouTube tutorial, but always get a popup during the installation that there is a missing driver.

These are the commands I used.

distrobuilder repack-windows /<path>/<isoname>.iso /<path>/w11_lxd.iso

lxc init w11 --empty --vm
lxc config device override w11 root size=80GB
lxc config set w11 limits.cpu=4 limits.memory=8GB
lxc config device add w11 vtpm tpm`
lxc config device add w11 install disk source=/<path>/w11_lxd.iso boot.priority=10
lxc start w11 --console=vga

I am running Fedora 35.
LXD version: 4.24 (snap package)

Kind Regards,
Errandil

stgraber · March 17, 2022, 7:18pm

@monstermunchkin did something regress with Windows 11?

Errandil · March 17, 2022, 7:21pm

Forgot to mention, have the same thing with Windows 10 20H2 and 21H2
Distrobuilder version: 2.0 (snap)

monstermunchkin · March 18, 2022, 6:41am

I’ll check this.

monstermunchkin · March 18, 2022, 11:27am

I can confirm this. Even with older virtio-win ISOs, the Windows 11 installation won’t work. The vioscsi driver for some reason is not recognized or accepted.

Errandil · March 18, 2022, 12:30pm

I also tried it with version 0.1.196 of the drivers today, it had the same issue.
If there is something I can test, please let me know.

monstermunchkin · March 18, 2022, 12:57pm

This seems related

github.com/virtio-win/kvm-guest-drivers-windows

Virtio-win driver (virtio-blk and virtio-scsi) don't work when they are used on bhyve with Windows 11 as guest os.

opened 06:23PM - 17 Mar 22 UTC

Marietto2008

Bug

Hello. What I want to achieve is to pass thru two of my NTFS "formatted" disk…s to a Windows 11 VM,but without passing them thru using the USB controller in FreeBSD with a bhyve virtual machine (in the example below I tried to boot Windows 11 from the nvme disk nvd0. I'm using this FreeBSD version : ``` FreeBSD marietto 13.0-RELEASE FreeBSD 13.0-RELEASE #8 n244809-dff3dead3734: Wed Feb 23 13:16:32 CET 2022 marietto@marietto:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 ``` I've configured the bhyve VM like this : ``` bhyve -S -c sockets=1,cores=2,threads=2 -m 4G -w -H -A \ -s 0,hostbridge \ -s 1,ahci-hd,/dev/nvd0 \ -s 2,virtio-blk,/dev/da4p2 \ -s 3,virtio-blk,/dev/da2p1 \ -s 8,virtio-net,tap4 \ -s 10,hda,play=/dev/dsp,rec=/dev/dsp \ -s 29,fbuf,tcp=[0.0.0.0:5904](http://0.0.0.0:5904/),w=1440,h=900 \ -s 30,xhci,tablet \ -s 31,lpc \ -l bootrom,/usr/local/share/uefi-firmware/BHYVE_BHF_CODE.fd \ vm4 < /dev/null & sleep 2 && vncviewer 0:4 ``` These are the NTFS disks that I would like to see inside the Windows 11 guest os : ``` -s 2,virtio-blk,/dev/da4p2 \ -s 3,virtio-blk,/dev/da2p1 \ => 34 19532873661 da4 GPT (9.1T) 34 32734 1 ms-reserved (16M) 32768 19532838912 2 ms-basic-data (9.1T) 19532871680 2015 - free - (1.0M) => 34 23437705149 da2 GPT (11T) 34 2014 - free - (1.0M) 2048 23437701120 1 ms-basic-data (11T) 23437703168 2015 - free - (1.0M) ``` As you can see I've used the virtio-blk driver,so inside the Windows 11 VM I've installed the latest version of the virtio drivers. The disks attached are 0 byte large,so they aren't recognized by Windows 11. Is this a bug or what ? They are USB 3.0 disks. You can give a look at the images below if u want to have a better understanding : https://forums.freebsd.org/attachments/1-jpg.13311/ https://forums.freebsd.org/attachments/2-jpg.13312/ I've tried also like this : ``` bhyve -S -c sockets=1,cores=2,threads=2 -m 4G -w -H -A \ -s 0,hostbridge \ -s 1,ahci-hd,/dev/nvd0 \ -s 2,virtio-blk,/dev/da4 \ -s 3,virtio-blk,/dev/da2 \ -s 8,virtio-net,tap4 \ -s 10,hda,play=/dev/dsp,rec=/dev/dsp \ -s 29,fbuf,tcp=[0.0.0.0:5904](http://0.0.0.0:5904/),w=1440,h=900 \ -s 30,xhci,tablet \ -s 31,lpc \ -l bootrom,/usr/local/share/uefi-firmware/BHYVE_BHF_CODE.fd \ vm4 < /dev/null & sleep 2 && vncviewer 0:4 ``` and I get this error : **Assertion failed: (n >= 2 && n <= BLOCKIF_IOV_MAX + 2), function pci_vtblk_proc, file /usr/src/usr.sbin/bhyve/pci_virtio_block.c, line 324.** I have tried also with : ``` -s 2,virtio-scsi,/dev/da4p2 \ -s 3,virtio-scsi,/dev/da2p1 \ ``` and I have also installed the virtio-scsi driver on Windows 11,that has been accepted by windows,but the disks aren't recognized : https://forums.freebsd.org/attachments/screenshot_2022-03-13_11-23-54-jpg.13321/ https://forums.freebsd.org/attachments/screenshot_2022-03-13_11-10-16-jpg.13320/ Finally I tried by virtualizing ubuntu with bhyve using the virtio-scsi driver on ubuntu as guest os and it worked,so there is a bug only on the drivers for windows. You can see what happens with ubuntu going on the freebsd forum at this address : https://forums.FreeBSD.org/threads/usb-3-0-disks-not-recognized-by-windows-if-passed-through-as-slots.84402/post-559924

stgraber · March 18, 2022, 3:44pm

That’s odd because I have a working Windows 11 VM here, so if it can work properly once installed, we should be able to make the install work too, no?

Errandil · March 20, 2022, 2:02pm

Hi,
I did some extra testing.

The strange thing is that windows does recognize the disks, but still asks for drivers.

Tested under Windows 10, 11 and Windows server 2019.
Is there a way to rollback to LXD 4.23 just to test?

stgraber · March 20, 2022, 4:37pm

You can snap install lxd --channel=4.23 on a clean system to get LXD 4.23.

Errandil · March 20, 2022, 7:03pm

Works without any issue in 4.23

I think it’s a bug in 4.24

stgraber · March 21, 2022, 12:27am

Can you show:

uname -a
lxc storage list

Errandil · March 21, 2022, 6:03am

On the machine with 4.24 (Fedora 35 Desktop not working)

Linux <hostname> 5.16.15-201.fc35.x86_64 #1 SMP PREEMPT Thu Mar 17 05:45:13 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

+---------+--------+--------------------------------------+-------------+---------+---------+
|  NAME   | DRIVER |                SOURCE                | DESCRIPTION | USED BY |  STATE  |
+---------+--------+--------------------------------------+-------------+---------+---------+
| default | btrfs  | 201039aa-1f61-4f79-8736-534f766fc61a |             | 11      | CREATED |
+---------+--------+--------------------------------------+-------------+---------+---------+
| pool2   | dir    | /mnt/files/lxd/                      |             | 1       | CREATED |
+---------+--------+--------------------------------------+-------------+---------+---------+

The test machine with 4.23 (Fedora 35 Server working)

Linux <hostname> 5.16.15-201.fc35.x86_64 #1 SMP PREEMPT Thu Mar 17 05:45:13 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
+---------+--------+------------------------------------------------+-------------+---------+
|  NAME   | DRIVER |                     SOURCE                     | DESCRIPTION | USED BY |
+---------+--------+------------------------------------------------+-------------+---------+
| default | dir    | /var/snap/lxd/common/lxd/storage-pools/default |             | 2       |
+---------+--------+------------------------------------------------+-------------+---------+

monstermunchkin · March 21, 2022, 12:04pm

This is the commit which causes the issue

geoffbland · March 22, 2022, 8:18pm

Just came here after a google - I’m just following the same video to install Win11 and I get the same error as reported above on the Win11 install.

I am running Ubuntu 20.04 Desktop with LXD 4.24.

I’m doing this for a demo of LXD for work next week. I’ll keep an eye out on this thread. Cheers.

$ uname -a
Linux sm01 5.13.0-35-generic #40~20.04.1-Ubuntu SMP Mon Mar 7 09:18:32 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
$ lxc storage list
+------------+--------+-----------------------------------------------+-------------+---------+---------+
|    NAME    | DRIVER |                    SOURCE                     | DESCRIPTION | USED BY |  STATE  |
+------------+--------+-----------------------------------------------+-------------+---------+---------+
| lxd-pool01 | zfs    | /var/snap/lxd/common/lxd/disks/lxd-pool01.img |             | 9       | CREATED |
+------------+--------+-----------------------------------------------+-------------+---------+---------+
$ lxd --version
4.24

stgraber · March 23, 2022, 8:35pm

Reproduced the issue and confirmed that the disk is properly detected and functional. I can partition it, format it and use it from the command line in the installer.

But the installer still doesn’t want to install on it for some reason.

stgraber · March 23, 2022, 10:13pm

geoffbland · March 24, 2022, 6:33am

Thanks for the fix. Do we need to wait for the next LXD release - or is there a easy way to patch LXD 4.24 with this fix for now?

stgraber · March 24, 2022, 4:27pm

The fix was cherry-picked and is rolling out now, a snap refresh lxd will most likely pull it in already, if not, trying in a few hours should do it.

Errandil · March 24, 2022, 5:50pm

Thank you for the fast fix. Will try to test tomorrow or Saturday