The virtio-win drivers ISO drive also uses sata so that the Windows installer can read it.The installer CD/ISO drive uses the sata bus so that the Windows installer can boot.The installed boot disk uses scsi as its disk bus with discard='unmap' in the for TRIM support.Here's how I customised my libvirt domain XML for Windows: So spare yourself the headache of troubleshooting and reinstall Windows once more. (And in the case of changing the boot disk bus after installation, it does not appear to be possible for Windows 10, as I found out.) It's an annoying process with no guarantee of success. You would have to adapt the instructions from this Super User answer. The easiest way to resolve this is to configure the libvirt domain XML how you want it beforehand and then reinstall Windows for that hardware.Ī harder way would be to start up the Windows install ISO, add virtio-win drivers with DISM, and hope that one of them fixes the BSOD. For example, if I installed Windows on the scsi ( virtio-scsi) disk bus and then changed the disk bus to virtio ( virtio-blk), I'll get this far before the guest crashes with no details: It's especially hard to figure out what caused the blue screen if you do not remember what you changed. If you changed something in your libvirt domain XML after installation, the IRQL_NOT_LESS_OR_EQUAL blue screen of death could easily happen. Windows is fragile when it comes to hardware changes, virtualised or bare metal. It sounds like you were able to reinstall Windows, but the first boot blue-screened. Just to test, I tried stripping the VM configuration. var/lib/libvirt/qemu/nvram/win10_VARS.fd usr/share/edk2.git/ovmf-圆4/OVMF_CODE-pure-efi.fd Its lacking the vfio-drivers.iso and the Bootdrive, because the problem is that the Win10.iso won't boot. I already had the VM up and running (so it is possible to get around that error), except for the error 43 thing from nVidia, but then i realized that my base system was corrupted, so I decided to do a clean reinstallation, which worked perfectly until the first VM boot up. I see that the error is related to memory allocation, but I have no idea what to change to make it work. When i try to boot from a current and tested Win10.iso it gives me the BSOD with IRQL_NOT_LESS_OR_EQUAL. So the goal will be to get host-passthrough/ Copy host CPU configuration to work. Problem: I will have performance impacts if i emulate a CPU instead of just handing it over. So the IRQL error is caused by the CPU passtrough! Now the installer starts without any issues. One of the first things i tried was switching from host-passthrough/ Copy host CPU configuration in CPU to Hypervisor Default. Then I installed virt-manager and set up a new VM based on the recommendations from the answers.Īfter trying the prebuild arch OVMF images with the same results i started to change ALL the options. Then I set up libvirtd daemon with its dependencies, where I had to add virtlogd and dbus daemon by hand. Afterwards, I bound my nVidia GTX 970 to the vfio-pci kernel module. I installed a clean Void Linux and set up IOMMU and fixed my IVRS table. Since my gaming hardware supports IOMMU, I decided to migrate the machine to Linux.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |