[vfio-users] cannot boot windows guest after update

[thibaut noah]

Manage to find a way to access my virtio drivers by selecting the "system
image recovery" option.
Not doing a thing and i installed all those needed. (they are installed on
detected windows drive right?)

At this point i think windows has an issue with recognizing an emulated
device, no idea which but this isn't related to the install itself.
It's more of a bug due to a switch between native and virtualized, it
usually takes about a minute for windows to detect all devices and switch
to appropriate config, obviously this time it is failing.
Since i can access the windows drive, even if windows does not fully launch
it means virtio drivers are there, otherwise i assume i wouldn't see
anything at all except the efi shell ? (please someone correct me if i am
wrong).

Still the fact that windows does not detect both cd-rom devices on the
repair menu but manage to see them while on the system recovery screen is
strange.

2016-05-05 16:52 GMT+02:00 thibaut noah <thibaut.noah at gmail.com>:

> 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.jansson at 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.
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/vfio-users/attachments/20160505/5fcf6451/attachment.htm>