virtio-win-pkg-scripts
virtio-win-pkg-scripts copied to clipboard
virtio-win
Windows 7 no more working
Build 195 (Dec 19, 2019) was the last published build that contains WinXP/WS2003 and Winn7 binaries. Since that point those targets were exuded from our regular builds. However, if your question is about the binaries themselves, then you can find them in any resent virtio-win RPM published at fedorapeople site ( https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/. )
Best, Vadim.
Is the installer msi working ? It gives me an error, and ask me to use windows 8
msi installers and package bundle are designed to work for Win8/WS2012(R2) and Win10/WS2016/2019 only. On previous versions you need to install the drivers manually.
Build 195 (Dec 19, 2019) was the last published build that contains WinXP/WS2003 and Winn7 binaries. Since that point those targets were exuded from our regular builds. However, if your question is about the binaries themselves, then you can find them in any resent virtio-win RPM published at fedorapeople site ( https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/. )
Best, Vadim.
Unless I'm misunderstanding which build numbers are being mentioned here, build 0.1.195 doesn't exist yet. The latest is 0.1.190-1, dated Jan 13, 2021.
As of Dec 19, 2019, it appears the latest build was 0.1.173-1.
From the win7-drivers branch, it appears like after build 0.1.173-5, the binaries were added to the old-drivers direcotry, to continue being distributed, but no longer be built.
The latest build that actually works for me during Windows 7 installation using vioscsi is 0.1.173-9, dated March 23, 2020.
Am I correct that even build 0.1.190-1 should work, although for the Windows 7 drivers, they would simply be copies of 0.1.173-something being carried forward?
They don't. All of the vioscsi drivers for build 0.1.185-1 and after give me the error: "No signed device drivers were found. Make sure that the installation media contains the correct drivers, and then click OK."
Below is the qemu command I'm using, and I attempt choosing "E:\vioscsi\w7\amd64".
I haven't figured out how to check the signatures on the files, but this all leads me to believe that commit 1360f4d may have accidentally committed at least some unsigned/improperly signed Win7 drivers, and that commit ddb36a8 may have done the same.
/usr/bin/qemu-system-x86_64 \
-name win7-iso,process=qemu:win7-iso \
-no-user-config \
-nodefaults \
-nographic \
-uuid 6875edfe-17ad-4958-b8e6-34740a43d6f9 \
-pidfile /tmp/vm_win7-iso.pid \
-machine q35,accel=kvm,vmport=off,dump-guest-core=off \
-cpu SandyBridge-IBRS \
-smp cpus=1,cores=1,threads=1,sockets=1 \
-m 512M \
-drive if=pflash,format=raw,readonly,file=/usr/share/ovmf/x64/OVMF_CODE.fd \
-drive if=pflash,format=raw,readonly,file=/var/qemu/efivars/vm_win7-iso.fd \
-monitor telnet:localhost:6001,server,nowait,nodelay \
-spice unix,addr=/tmp/spice.win7-iso.sock,disable-ticketing \
-device qxl-vga,bus=pcie.0,addr=1,max_outputs=1 \
-usbdevice tablet \
-netdev bridge,id=network0,br=br0 \
-device virtio-net-pci,netdev=network0,mac=3c:11:f0:89:af:ca,bus=pcie.0,addr=3 \
-blockdev raw,node-name=install_iso,read-only=on,file.driver=file,file.filename=/mnt/losable/ISOs/en_windows_7_professional_with_sp1_x64_dvd_u_676939.iso \
-device ide-cd,drive=install_iso,bus=ide.0,bootindex=0 \
-blockdev raw,node-name=virtio_iso,read-only=on,file.driver=file,file.filename=/mnt/losable/ISOs/virtio-win-0.1.190-1.iso \
-device ide-cd,drive=virtio_iso,bus=ide.1,bootindex=99 \
-device virtio-scsi-pci,id=scsi1 \
-drive driver=raw,node-name=hd0,file=/dev/lvm/vm_win7-iso,if=none,discard=unmap,cache=none,aio=threads \
-device scsi-hd,drive=hd0,bootindex=1
I haven't figured out how to check the signatures on the files
Use SignTool from Windows Studio 2019, example:
SignTool verify /v /c netkvm.cat /pa netkvm.sys netkvm.inf
After doing some test, I come to these conclusion.
[DIR] virtio-win-0.1.173-9/ 2020-03-23 20:23 -
balloon.inf 08/12/2019,61.80.104.17300
viostor.inf 08/12/2019,61.80.104.17300
vioscsi.inf 08/12/2019,61.80.104.17300
[DIR] virtio-win-0.1.185-1/ virtio-win-0.1.187-1/ 2020-06-03 19:20 -
balloon.inf 01/08/2020,61.81.104.17600
viostor.inf 01/08/2020,61.81.104.17600
vioscsi.inf 01/08/2020,61.81.104.17600
[DIR] virtio-win-0.1.189-1/ 2020-08-10 08:01 -
balloon.inf 12/12/2019,61.81.104.17400
viostor.inf 12/12/2019,61.81.104.17400
vioscsi.inf 12/12/2019,61.81.104.17400
[DIR] virtio-win-0.1.217-1/ virtio-win-0.1.229-1/ 2022-04-14 08:04 -
balloon.inf 03/10/2019,61.77.104.16900
viostor.inf 06/07/2019,61.77.104.17200
vioscsi.inf 08/03/2018,61.76.104.16000
on my test environment
173 everything works
185/187 vioscsi.sys Windows cannot verify the digital signature for this file
189 balloon.sys cause BSOD
229 vioscsi not working
So 0.1.173-9 is the best choise on my windows 7 environment
Plus, it includes newer drivers compare to latest version 0.1.229-1 which release on 2023-01-09
After doing some test, I come to these conclusion.
[DIR] virtio-win-0.1.173-9/ 2020-03-23 20:23 - balloon.inf 08/12/2019,61.80.104.17300 viostor.inf 08/12/2019,61.80.104.17300 vioscsi.inf 08/12/2019,61.80.104.17300 [DIR] virtio-win-0.1.185-1/ virtio-win-0.1.187-1/ 2020-06-03 19:20 - balloon.inf 01/08/2020,61.81.104.17600 viostor.inf 01/08/2020,61.81.104.17600 vioscsi.inf 01/08/2020,61.81.104.17600 [DIR] virtio-win-0.1.189-1/ 2020-08-10 08:01 - balloon.inf 12/12/2019,61.81.104.17400 viostor.inf 12/12/2019,61.81.104.17400 vioscsi.inf 12/12/2019,61.81.104.17400 [DIR] virtio-win-0.1.217-1/ virtio-win-0.1.229-1/ 2022-04-14 08:04 - balloon.inf 03/10/2019,61.77.104.16900 viostor.inf 06/07/2019,61.77.104.17200 vioscsi.inf 08/03/2018,61.76.104.16000on my test environment
173 everything works 185/187 vioscsi.sys Windows cannot verify the digital signature for this file 189 balloon.sys cause BSOD 229 vioscsi not workingSo
0.1.173-9is the best choise on my windows 7 environmentPlus, it includes newer drivers compare to latest version
0.1.229-1which release on2023-01-09
hey uh so pretty late here, but I tried this on my VM and through device manager nothing shows up, and the installers asks me to use Windows 8 and above. Any solution or am I just dumb?
hey uh so pretty late here, but I tried this on my VM and through device manager nothing shows up, and the installers asks me to use Windows 8 and above. Any solution or am I just dumb?
IIRC you manually need to select the .inf files for each device. In the device manager, go to each unknown device, go to properties, driver, and do a manual driver search, tell it one of the folders of the virtio driver package. You'll need to either find out which driver is for which device (check PCI ids) or you need to guess, which worked well for me.
Yeah but how do I get the Windows Aero theme working?
Get Outlook for Androidhttps://aka.ms/AAb9ysg
From: Axel Gembe @.> Sent: Monday, September 4, 2023 9:08:32 AM To: virtio-win/virtio-win-pkg-scripts @.> Cc: Aditya Khullar @.>; Comment @.> Subject: Re: [virtio-win/virtio-win-pkg-scripts] Windows 7 no more working (#40)
After doing some test, I come to these conclusion.
[DIR] virtio-win-0.1.173-9/ 2020-03-23 20:23 - balloon.inf 08/12/2019,61.80.104.17300 viostor.inf 08/12/2019,61.80.104.17300 vioscsi.inf 08/12/2019,61.80.104.17300
[DIR] virtio-win-0.1.185-1/ virtio-win-0.1.187-1/ 2020-06-03 19:20 - balloon.inf 01/08/2020,61.81.104.17600 viostor.inf 01/08/2020,61.81.104.17600 vioscsi.inf 01/08/2020,61.81.104.17600
[DIR] virtio-win-0.1.189-1/ 2020-08-10 08:01 - balloon.inf 12/12/2019,61.81.104.17400 viostor.inf 12/12/2019,61.81.104.17400 vioscsi.inf 12/12/2019,61.81.104.17400
[DIR] virtio-win-0.1.217-1/ virtio-win-0.1.229-1/ 2022-04-14 08:04 - balloon.inf 03/10/2019,61.77.104.16900 viostor.inf 06/07/2019,61.77.104.17200 vioscsi.inf 08/03/2018,61.76.104.16000
on my test environment
173 everything works 185/187 vioscsi.sys Windows cannot verify the digital signature for this file 189 balloon.sys cause BSOD 229 vioscsi not working
So 0.1.173-9 is the best choise on my windows 7 environment Plus, it includes newer drivers compare to latest version 0.1.229-1 which release on 2023-01-09
hey uh so pretty late here, but I tried this on my VM and through device manager nothing shows up, and the installers asks me to use Windows 8 and above. Any solution or am I just dumb?
IIRC you manually need to select the .inf files for each device. In the device manager, go to each unknown device, go to properties, driver, and do a manual driver search, tell it one of the folders of the virtio driver package. You'll need to either find out which driver is for which device (check PCI ids) or you need to guess, which worked well for me.
— Reply to this email directly, view it on GitHubhttps://github.com/virtio-win/virtio-win-pkg-scripts/issues/40#issuecomment-1704564278, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARLJ7VD4VD24LON47LEDKY3XYVELRANCNFSM4ZTY6QVQ. You are receiving this because you commented.Message ID: @.***>
I'm not sure if you can. I think there is no real acceleration for that in the drivers, or are you using GPU passthrough? Anyway, this issue is probably the wrong one and given that the drivers already don't support Windows 7, it is unlikely to be fixed.
I see. I'll try gpu pass through first, not sure if gpu pass through works on laptops although I do got 2 GPUs in mine, still I'll try. If not ig I'll be stuck to virtualbox :p Thanks for your help dude
Get Outlook for Androidhttps://aka.ms/AAb9ysg
From: Axel Gembe @.> Sent: Monday, September 4, 2023 9:24:46 AM To: virtio-win/virtio-win-pkg-scripts @.> Cc: Aditya Khullar @.>; Comment @.> Subject: Re: [virtio-win/virtio-win-pkg-scripts] Windows 7 no more working (#40)
I'm not sure if you can. I think there is no real acceleration for that in the drivers, or are you using GPU passthrough? Anyway, this issue is probably the wrong one and given that the drivers already don't support Windows 7, it is unlikely to be fixed.
— Reply to this email directly, view it on GitHubhttps://github.com/virtio-win/virtio-win-pkg-scripts/issues/40#issuecomment-1704573106, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARLJ7VF6ICT5UN2OXEC4OMLXYVGINANCNFSM4ZTY6QVQ. You are receiving this because you commented.Message ID: @.***>