I don't understand, i have only one windows installation and like i said it boots perfectly if i don't run it with qemu-kvm.
Didn't find a way to install virtio drivers on native windows since they are not used by the system. So if i have to do a recovery i can only do it from the vm which i am unable to do at the moment. Going into efi sheel and running bootx64 in fso: /efi/boot gets me to the same repair screen as simply launching the vm. Also i tried to add windows iso and virtio iso in the hope that i would be able to do a "repair" by booting on the iso but it seems both disks are not detected by windows though i added them with virt-manager. (they were detected a while ago but not anymore). I'm suppose to seem them on windows repair in the "use a device" screen but i don't, only efi internal shell. 2016-05-05 16:36 GMT+02:00 Torbjorn Jansson < torbjorn.jans...@mbox200.swipnet.se>: > On 2016-05-05 15:19, thibaut noah wrote: > >> What do you mean by offline windows copy? This is a native windows 10 >> install. >> I boot it native all the time to do benchmarks and all, never had any >> issue >> before the update. >> >> I assume what you mean by boot drivers is virtio drivers? >> >> > "offline copy" as in the windows installation that you are not currently > running. > dism cant be used on the currently running windows instance. > booting to recovery is enough, this recovery can be from a usb stick or > install dvd or whatever you prefer. > > example: > dism /Image:C:\ /Add-Driver /Driver:X:\drivers\ /Recurse > > assuming C:\ is the drive where the broken offline version is. > check drive letter, it might not be what you expect. > > also, this is not really vfio specific things, so probably a bit offtopic. > > and as i said before, all this will do is to add drivers, like those > needed to find your boot device. > >
_______________________________________________ vfio-users mailing list vfio-users@redhat.com https://www.redhat.com/mailman/listinfo/vfio-users
