I got as far as running the install of the OS on VM but get an error about no device drivers found. I tried the virtio-win-0.1.190-1 driver but no luck after looking on the net. Please help
thanks
really hope somebody can guide me
thanks
What were you choices for the setup of the VM in TrueNAS?
Add the virtio ISO file as a CD ROM drive to your VM. Then the windows installer will see it during installation.
1 Like
yes i have done this and used various versions of the virtio ISO file the red hat drivers show but wont install and show my drives
thanks
for the drives VirtIO or AHCI
You can also run the VM first without virtio and switch it later to use virtio. Just install using ahci and as network intel.
so use AHCI disk ?
Yes. Then install the drivers and switch.
same result no drives show during windows setup
this is my LOG
2024-12-04 14:27:13.924+0000: starting up libvirt version: 9.0.0, package: 9.0.0-4 (Debian), qemu version: 7.2.11Debian 1:7.2+dfsg-7+deb12u6, kernel: 6.6.44-production+truenas, hostname: truenas.local
LC_ALL=C
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
HOME=/var/lib/libvirt/qemu/domain-1-4_shadyP
XDG_DATA_HOME=/var/lib/libvirt/qemu/domain-1-4_shadyP/.local/share
XDG_CACHE_HOME=/var/lib/libvirt/qemu/domain-1-4_shadyP/.cache
XDG_CONFIG_HOME=/var/lib/libvirt/qemu/domain-1-4_shadyP/.config
/usr/bin/qemu-system-x86_64
-name guest=4_shadyP,debug-threads=on
-S
-object ‘{“qom-type”:“secret”,“id”:“masterKey0”,“format”:“raw”,“file”:“/var/lib/libvirt/qemu/domain-1-4_shadyP/master-key.aes”}’
-machine pc-i440fx-7.2,usb=off,dump-guest-core=off,memory-backend=pc.ram
-accel kvm
-cpu qemu64,hv-time=on,hv-relaxed=on,hv-vapic=on,hv-spinlocks=0x1fff,hv-vpindex=on,hv-synic=on,hv-stimer=on,hv-reset=on,hv-frequencies=on,hv-tlbflush=on,hv-ipi=on
-m 8192
-object ‘{“qom-type”:“memory-backend-ram”,“id”:“pc.ram”,“size”:8589934592}’
-overcommit mem-lock=off
-smp 32,sockets=2,dies=1,cores=2,threads=8
-uuid 043a2a3f-88c6-46cf-b54b-bc8d39b96e4c
-no-user-config
-nodefaults
-chardev socket,id=charmonitor,fd=34,server=on,wait=off
-mon chardev=charmonitor,id=monitor,mode=control
-rtc base=localtime
-no-shutdown
-boot strict=on
-device ‘{“driver”:“nec-usb-xhci”,“id”:“usb”,“bus”:“pci.0”,“addr”:“0x4”}’
-device ‘{“driver”:“ahci”,“id”:“sata0”,“bus”:“pci.0”,“addr”:“0x5”}’
-device ‘{“driver”:“virtio-serial-pci”,“id”:“virtio-serial0”,“bus”:“pci.0”,“addr”:“0x6”}’
-blockdev ‘{“driver”:“file”,“filename”:“/mnt/d0/iso/109103-Win10.iso”,“node-name”:“libvirt-3-storage”,“auto-read-only”:true,“discard”:“unmap”}’
-blockdev ‘{“node-name”:“libvirt-3-format”,“read-only”:true,“driver”:“raw”,“file”:“libvirt-3-storage”}’
-device ‘{“driver”:“ide-cd”,“bus”:“sata0.0”,“drive”:“libvirt-3-format”,“id”:“sata0-0-0”,“bootindex”:1}’
-blockdev ‘{“driver”:“host_device”,“filename”:“/dev/zvol/d0/vm/shadyP-w3p43”,“aio”:“threads”,“node-name”:“libvirt-2-storage”,“cache”:{“direct”:true,“no-flush”:false},“auto-read-only”:true,“discard”:“unmap”}’
-blockdev ‘{“node-name”:“libvirt-2-format”,“read-only”:false,“discard”:“unmap”,“cache”:{“direct”:true,“no-flush”:false},“driver”:“raw”,“file”:“libvirt-2-storage”}’
-device ‘{“driver”:“ide-hd”,“bus”:“sata0.1”,“drive”:“libvirt-2-format”,“id”:“sata0-0-1”,“bootindex”:2,“write-cache”:“on”}’
-blockdev ‘{“driver”:“file”,“filename”:“/mnt/d0/iso/virtio-win-0.1.266.iso”,“node-name”:“libvirt-1-storage”,“auto-read-only”:true,“discard”:“unmap”}’
-blockdev ‘{“node-name”:“libvirt-1-format”,“read-only”:true,“driver”:“raw”,“file”:“libvirt-1-storage”}’
-device ‘{“driver”:“ide-cd”,“bus”:“sata0.2”,“drive”:“libvirt-1-format”,“id”:“sata0-0-2”,“bootindex”:3}’
-netdev ‘{“type”:“tap”,“fd”:“35”,“id”:“hostnet0”}’
-device ‘{“driver”:“e1000”,“netdev”:“hostnet0”,“id”:“net0”,“mac”:“00:a0:98:61:49:5e”,“bus”:“pci.0”,“addr”:“0x3”}’
-chardev pty,id=charserial0
-device ‘{“driver”:“isa-serial”,“chardev”:“charserial0”,“id”:“serial0”,“index”:0}’
-chardev spicevmc,id=charchannel0,name=vdagent
-device ‘{“driver”:“virtserialport”,“bus”:“virtio-serial0.0”,“nr”:1,“chardev”:“charchannel0”,“id”:“channel0”,“name”:“com.redhat.spice.0”}’
-chardev socket,id=charchannel1,fd=33,server=on,wait=off
-device ‘{“driver”:“virtserialport”,“bus”:“virtio-serial0.0”,“nr”:2,“chardev”:“charchannel1”,“id”:“channel1”,“name”:“org.qemu.guest_agent.0”}’
-device ‘{“driver”:“usb-tablet”,“id”:“input0”,“bus”:“usb.0”,“port”:“1”}’
-audiodev ‘{“id”:“audio1”,“driver”:“spice”}’
-spice port=5900,addr=0.0.0.0,seamless-migration=on
-device ‘{“driver”:“qxl-vga”,“id”:“video0”,“max_outputs”:1,“ram_size”:67108864,“vram_size”:67108864,“vram64_size_mb”:0,“vgamem_mb”:16,“xres”:1024,“yres”:768,“bus”:“pci.0”,“addr”:“0x2”}’
-device ‘{“driver”:“virtio-balloon-pci”,“id”:“balloon0”,“bus”:“pci.0”,“addr”:“0x7”}’
-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny
-msg timestamp=on
char device redirected to /dev/pts/0 (label charserial0)
2024-12-04T14:27:13.995195Z qemu-system-x86_64: -accel kvm: warning: Number of SMP cpus requested (32) exceeds the recommended cpus supported by KVM (16)
2024-12-04T14:27:13.995216Z qemu-system-x86_64: -accel kvm: warning: Number of hotpluggable cpus requested (32) exceeds the recommended cpus supported by KVM (16)
2024-12-04T14:27:28.982687Z qemu-system-x86_64: warning: Spice: …/server/reds.cpp:2107:reds_handle_ticket: Invalid password
i have a bridge interface br0 , would that be causing the issue
Can you post screenshots of your entire VM config ?
all of a sudeen i cant upload images to this site smh maybe i should just go proxmox and screw truenas
An error occurred: Sorry, you can’t embed media items in a post. what is this
Go browse some other topics and take the tutorial to raise your forum trust level. You will get more posting rights after becoming Basic user.
TrueNAS-Bot
Type this in a new reply and send to bring up the tutorial, if you haven’t done it already.
@TrueNAS-Bot start tutorial
ok thanks
@TrueNAS-Bot start tutorial
G_W, please upload the screenshots. You are listed as a Basic User so it should work now.
Did you browse for the drivers at the point in the screenshot that you had in your first post? Into the VirtIO ISO you mounted and into the amd64 folder?