No disk found when installing windows 11 Pro
Expected behaviour
Windows 11 installs
Actual behaviour
i get into the windows setup, but there is no disk selectable in setup.
Steps to reproduce the behaviour
- create a config:
guest_os="windows"
disk_img="windows-11/disk.qcow2"
iso="Win11_23H2_German_x64v2.iso"
fixed_iso="virtio-win-0.1.240.iso"
tpm="on"
secureboot="off"
cpu_cores="6"
ram="16G"
disk_size="300G"
--> quickemu --vm windows-11.conf
Quickemu output
Quickemu 4.9.1 using /usr/bin/qemu-system-x86_64 v7.0.0
- Host: Pop!_OS 22.04 LTS running Linux 6.6 (hannes-lnx)
- CPU: 11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz
- CPU VM: 1 Socket(s), 3 Core(s), 2 Thread(s), 16G RAM
- BOOT: EFI (Windows), OVMF (/usr/share/OVMF/OVMF_CODE.fd), SecureBoot (off).
- Disk: windows-11/disk.qcow2 (300G)
Looks unused, booting from Win11_23H2_German_x64v2.iso
- Boot ISO: Win11_23H2_German_x64v2.iso
- CD-ROM: virtio-win-0.1.240.iso
- Display: SDL, virtio-vga-gl, GL (on), VirGL (on)
- Sound: intel-hda
- ssh: On host: ssh user@localhost -p 22220
- WebDAV: On guest: dav://localhost:9843/
- TPM: windows-11/windows-11.swtpm-sock (14684)
- Network: User (virtio-net)
- Monitor: On host: nc -U "windows-11/windows-11-monitor.socket"
or : socat -,echo=0,icanon=0 unix-connect:windows-11/windows-11-monitor.socket
- Serial: On host: nc -U "windows-11/windows-11-serial.socket"
or : socat -,echo=0,icanon=0 unix-connect:windows-11/windows-11-serial.socket
- Process: Starting windows-11.conf as windows-11 (14697)
- Sending: sendkey ret
Linux Distribution & Kernel
Run the following and paste the output.
lsb_release --all
uname -a
No LSB modules are available.
Distributor ID: Pop
Description: Pop!_OS 22.04 LTS
Release: 22.04
Codename: jammy
Linux user-lnx 6.6.10-76060610-generic #202401051437~1704728131~22.04~24d69e2 SMP PREEMPT_DYNAMIC Mon J x86_64 x86_64 x86_64 GNU/Linux
If anyone has an idea what to do i would be very happy!! THanks a lot for help!
Quick reply - when installing it with quickget it works. but i have to manually replace the iso path in the config
Why is this closed? The problem persists.
Hi,
I just run into the same problem, but I added a second CDRROM device with the virtio-win image, and upon clicking "Load controllers", I was given some options. For Windows 11, the obvious one was E:\amd64\viostor\w11\viostor.inf. The hard drive was then found. I took all this from Virt-manager from Manjaro
UPDATE: actually, I encountered this problem when setting up a VirtIO virtual disk. Win 11 does detect a SATA disk with no extra drivers required.
I confirm that I also experienced the issue and I had to manually select the driver E:\amd64\viostor\w11\viostor.inf to make the drive appear.
Why was this closed? It's a legitimate issue someone is having. At the very minimum, could you at least provide information as to why this problem is invalid?