[vfio-users] Intel Graphics assignment , legacy mode : vm freeze, after one reboot

[Manuel Ullmann]

Hi,

actually I reinstalled it twice since passthrough is working. The first
time, because I destroyed the VM too often, when Windows was already
booting and passthrough was not working yet.

The second time because I switched from the sata interface to
virtio for iothread performance reasons and Windows did not manage to
install a goddamn io controller driver from the recovery, although I could
install it for the recovery tools. The boot issues fixer did not get the
idea, that the io controller driver available for it could be worthwhile
to install into the main system. Windows sucks, but yeah, that’s the
reason, why you can only use it for gaming and not productivity.

Best regards,
Manuel
> Hi,
> I'd suggest trying with a "clean" windows image.
> I used to have similar issue and fixed by install a new windows from
> iso with local storage. However after that I use the "good" image
> through NFS and it still works.
>
> The "bad" image is a Win7 installed with qemu 0.12 and it do works
> with qemu 2.8-pr1 on another host. I use it throught NFS and the
> seabios just fail to boot the os when I enable IGD passthrough. No
> idear on the root cause.
>
> Regards,
> Daimon
>
> On Monday, December 26, 2016 8:22 AM, Manuel Ullmann
> <ullman.alias at posteo.de> wrote:
>
> Hello,
>
> I know this answer won’t help, but I also get this freeze occasionally
> (50% would be a good approximation). I also use vfio-igd assignment
> and had
> also kernel 4.8.x (now 4.9.0; still reproducible).
> My workaround is currently destroying of the VM on reboots and blindly
> rebooting it via virsh (after login).
> The bug could be limited to IGD assignment, since noone else replied
> and
> most people here seem to use discrete graphics assignment.
> To spare you the XML format documentation lookup, I use the line
> <on_reboot>destroy</on_reboot>
> in libvirt XML for VM destroying, but you most likely knew that.
>
> Sorry for not having a better workaround.
>
> Best regards,
> Manuel
>
> Nicolas Prochazka <nicolas.prochazka at gmail.com> writes:
>
>> Hello, 
>> Host : linux 4.8.x
>> Guest Vm : windows
>> Primary vga : intel IGD 
>> qemu : 2.7.0
>>
>> /usr/bin/qemu-system-x86_64 -name win10 -S -machine
>> pc-i440fx-2.7,accel=kvm,usb=off -cpu
>> host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff -bios
>> /usr/share/seabios/bios.bin -m 14079 -mem-prealloc -mem-path
>> /dev/hugepages/libvirt/qemu -realtime mlock=off -smp
>> 2,sockets=1,cores=2,threads=1 -uuid
>> 336f5637-f280-3d98-8491-7becd338aec9 -nographic -no-user-config -
>> nodefaults -chardev
>>
> socket,id=charmonitor,path=/var/lib/libvirt/qemu/win10.monitor,server,nowait
>> -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime
> -
>> no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global
>> PIIX4_PM.disable_s4=1 -boot strict=on -device
>> piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device
>> virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive
>> file=nbd:unix:/tmp/win10.ctl,if=none,id=drive-ide0-0-0,format=raw -
>> device
>> ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1
> -
>> drive
> file=nbd:unix:/tmp/swap.ctl,if=none,id=drive-ide0-0-1,format=raw
>> -device ide-hd,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1 -
>> netdev tap,fd=19,id=hostnet0 -device
>>
> e1000,netdev=hostnet0,id=net0,mac=ac:de:50:7d:88:85,bus=pci.0,addr=0x3
>> -chardev
>>
> socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/win10.org.qemu.guest_agent.0,server,nowait
>> -device
>>
> virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0
>> -device vfio-pci,host=00:02.0,id=hostdev0,bus=pci.0,addr=0x2 -device
>> vfio-pci,host=00:14.0,id=hostdev1,bus=pci.0,addr=0x5 -device
>> vfio-pci,host=00:1f.3,id=hostdev2,bus=pci.0,addr=0x6 -netdev
>> user,id=user.0,restrict=on,hostfwd=tcp:127.0.0.1:5901-:5900 -device
>> e1000,netdev=user.0 -msg timestamp=on
>>
>> VM is working very well, 3D benchmark is good, stability. 
>> Only one problem : If I reboot VM from windows , there's 50% that vm
>> freeze at seabios start : we only see black screen with seabios /
> pxe
>> boot , VM seems to be blocked. 
>>
>> Any suggestion ?
>>
>> Regards, 
>> Nicolas Prochazka
>>
>>
>> _______________________________________________
>> vfio-users mailing list
>> vfio-users at redhat.com
>> https://www.redhat.com/mailman/listinfo/vfio-users
>
> _______________________________________________
> vfio-users mailing list
> vfio-users at redhat.com
> https://www.redhat.com/mailman/listinfo/vfio-users