For the record: I had to pass options kvm ignore_msrs=1
to the kvm module to solve the issue. On Sat, Aug 4, 2018 at 4:09 PM, Alexander Petrenz <[email protected]> wrote: > Hi, > > well as I said, the problem only occurs when I boot the partition with the > win 10 installation via the vm. I can boot it natively without any > problems. I lost the activation due to the hardware change, however. > > BR > > On Sat, 4 Aug 2018, 07:49 Alex John, <[email protected]> wrote: > >> On Fri, Aug 03, 2018 at 11:10:19AM +0200, Alexander Petrenz wrote: >> > Hi, >> > >> > I used to have an intel core i7 system and I have a Win10 guest with a >> pci >> > passthroughed graphics card. This UEFI based setup was running fine and >> > stable. >> > Recently I upgraded to an amd ryzen system. I adjusted device ID of the >> > graphics card and I'm no longer using the pci-stub driver, but vfio-pci >> > directly. According to the lspci output this is working fine (vfio >> driver >> > bound to the graphics card). >> >> iirc Windows does not like the processor (or any hardware) to be changed >> suddenly, so you're better off reinstalling the VM. >> >> Alex >> >> > However the VM doesn't boot anymore. It's just looping around a screen >> > telling me that automatic repair is prepared. >> > When booted natively the win10 works still flawlessly. Is there >> anything I >> > need to adjust at the config because of the change of the pc hardware? >> > I already booted into the windows setup and tried to fix the boot record >> > via bcdedit, but that didn't change anything. >> > Does anybody have an idea what else I could try? >> > >> > Thanks and regards >> > Alex >> >>
