Hello,
Not going into details. If you want to run windows on KVM virtIO drivers must be embedded in ISO. mkdir c:\wim mkdir c:\mount copy install.wim and boot.wim to c:\wim dism /get-wiminfo /wimfile:C:\wim\install.wim Remove not needed indexes: Remove-WindowsImage -ImagePath "C:\wim\install.wim" -Index 4 -CheckIntegrity Sample get-wiminfo remove: Index : 3 Name : Windows Server 2019 Datacenter Description : (Recommended) This option omits most of the Windows graphical environment. Manage with a command prompt and PowerShell, or remotely with Windows Admin Center or other tools. Size : 8 350 409 038 bytes Index : 4 Name : Windows Server 2019 Datacenter (Desktop Experience) Description : This option installs the full Windows graphical environment, consuming extra drive space. It can be useful if you want to use the Windows desktop or have an app that requires it. Size : 14 553 156 579 bytes Mount iso with latest drivers: https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/ Inject drivers: (this is for Windows server 2019): dism /Mount-Wim /WimFile:C:\Wim\boot.wim /Index:2 /MountDir:C:\mount dism /image:C:\mount /Add-Driver "/driver:d:\Balloon\2k19\amd64\balloon.inf" /forceunsigned dism /image:C:\mount /Add-Driver "/driver:d:\NetKVM\2k19\amd64\netkvm.inf" /forceunsigned dism /image:C:\mount /Add-Driver "/driver:d:\viorng\2k19\amd64\viorng.inf" /forceunsigned dism /image:C:\mount /Add-Driver "/driver:d:\vioscsi\2k19\amd64\vioscsi.inf" /forceunsigned dism /image:C:\mount /Add-Driver "/driver:d:\vioserial\2k19\amd64\vioser.inf" /forceunsigned dism /image:C:\mount /Add-Driver "/driver:d:\viostor\2k19\amd64\viostor.inf" /forceunsigned dism /unmount-wim /mountdir:c:\mount /commit dism /Mount-Wim /WimFile:C:\WIM\install.wim /Index:1 /MountDir:C:\mount dism /image:C:\mount /Add-Driver "/driver:d:\Balloon\2k19\amd64\balloon.inf" /forceunsigned dism /image:C:\mount /Add-Driver "/driver:d:\NetKVM\2k19\amd64\netkvm.inf" /forceunsigned dism /image:C:\mount /Add-Driver "/driver:d:\viorng\2k19\amd64\viorng.inf" /forceunsigned dism /image:C:\mount /Add-Driver "/driver:d:\vioscsi\2k19\amd64\vioscsi.inf" /forceunsigned dism /image:C:\mount /Add-Driver "/driver:d:\vioserial\2k19\amd64\vioser.inf" /forceunsigned dism /image:C:\mount /Add-Driver "/driver:d:\viostor\2k19\amd64\viostor.inf" /forceunsigned dism /unmount-wim /mountdir:c:\mount /commit dism /Mount-Wim /WimFile:C:\WIM\install.wim /Index:2 /MountDir:C:\mount dism /image:C:\mount /Add-Driver "/driver:d:\Balloon\2k19\amd64\balloon.inf" /forceunsigned dism /image:C:\mount /Add-Driver "/driver:d:\NetKVM\2k19\amd64\netkvm.inf" /forceunsigned dism /image:C:\mount /Add-Driver "/driver:d:\viorng\2k19\amd64\viorng.inf" /forceunsigned dism /image:C:\mount /Add-Driver "/driver:d:\vioscsi\2k19\amd64\vioscsi.inf" /forceunsigned dism /image:C:\mount /Add-Driver "/driver:d:\vioserial\2k19\amd64\vioser.inf" /forceunsigned dism /image:C:\mount /Add-Driver "/driver:d:\viostor\2k19\amd64\viostor.inf" /forceunsigned dism /unmount-wim /mountdir:c:\mount /commit Modify ISO: (oscdimg.exe is part of windows deployment tool) Oscdimg.exe -u2 -bC:\Users\user\Downloads\en_windows_server_2019_updated_june_2020_x64_dvd_KVM\boot\ etfsboot.com -h C:\Users\user\Downloads\en_windows_server_2019_updated_june_2020_x64_dvd_KVM C:\Users\user\Downloads\en_windows_server_2019_updated_june_2020_x64_dvd_KVM\123.iso Oscdimg.exe -u2 -bC:\<YOUR DIR> \expandedSetup\boot\etfsboot.com -h C:\<YOUR DIR> \expandedSetup C:\<YOUR DIR> \Win7.iso On Fri, 30 Jul 2021 at 14:08, technologyrss.mail < technologyrss.m...@gmail.com> wrote: > *yes some is ok.* > > but how can I check > > iso contain correct drivers for hypervisor. > > I am use KVM. > can you share any driver include iso link? > > *Thanks.* > *---* > *Alamin* > > On 7/30/2021 4:58 PM, Kristaps Cudars wrote: > > Hello, > > Confirm that iso is compatible with your hypervisor. > Confirm that iso is not corrupted. > Confirm that installation and consequent boot is happening in same mode bios > or uefi > Confirm that iso contain correct drivers for hypervisor. > Confirm that os type is selected correctly. > > > On 2021/07/30 10:50:41, "technologyrss.mail" <technologyrss.m...@gmail.com> > <technologyrss.m...@gmail.com> wrote: > > when windows installation done, > then I remove iso and reboot vm then I see this error. > > *--** > **Alamin* > > On 7/30/2021 4:46 PM, Kristaps Cudars wrote: > > Hello, > > Usually it indicates that installation media/iso is corrupted. > Its polite toon to ask such questions in users mailing list. > > On 2021/07/30 10:37:20, "technologyrss.mail" <technologyrss.m...@gmail.com> > <technologyrss.m...@gmail.com> wrote: > > *Hi,* > > I install windows 10 vm but can't access. I see some error. > > What is issue? Please help me. > > > -- > > *Thanks & Regards.* > > *Support Admin* > > Facebook <htps://facebook.com/technologyrss> | > Twitter<https://twitter.com/technologyrss1> > <https://twitter.com/technologyrss1> | > YouTube<http://www.youtube.com/channel/UCBq7qGqFEUe6ObVHMuxudTw> > <http://www.youtube.com/channel/UCBq7qGqFEUe6ObVHMuxudTw> | > LinkedIn<https://www.linkedin.com/company/technologyrss/> > <https://www.linkedin.com/company/technologyrss/> > > 116/1 West Malibagh, D. I. T Road > Dhaka-1217, Bangladesh > *Mob :* +88 01716915504* > Email :* support.ad...@technologyrss.com* > Web :* www.technologyrss.com > >
