Open ChristophSchmidpeter opened 5 years ago
I had the same issue on a Thinkpad T480s. It works fine on a Windows 10 guest with SeaBIOS.
See also: https://github.com/intel/gvt-linux/issues/20#issuecomment-365496162
@albionxy @daramos , For Linux VM, please follow https://github.com/intel/gvt-linux/wiki/GVTg_Setup_Guide#412-linux-intel-gfx-card-support that make sure guest xorg.conf file set well.
@daramos: I tried it with BIOS now and it works now. Thank you for that valuable information!
S for people who might encounter the same issue: Using BIOS is a good workaround for this issue if one does not have to use UEFI.
@TerrenceXu: It does not work with UEFI + Windows for me. Linux seems to work, however. Can you reproduce the issue with Windows 10 + UEFI on your system? And if yes, is it a regression, or has it never worked yet?
I have same bug but I use desktop with i5-6600 - hd530 and wayland running on rx480. Pretty much there no any display output under VFIO section and there are these errors (ignored rdmsr) in dmesg log.
(I use Arch Linux with newest packages).
@TitusLabienus @HoshiYamazaki, Looks it is Windows Graphic driver issue, it not support UEFI bios with dma-buf.
@TitusLabienus @HoshiYamazaki, Looks it is Windows Graphic driver issue, it not support UEFI bios with dma-buf.
If I remember correctly I had the same issue on legacy BIOS, but I will check it again maybe in this week or next.
@TerrenceXu Does dma-buf + Uefi + Windows work now?
I have build the staging branch, and now it runs on my Coffee Lake host with a Linux client pretty well. Thank you for the great work. 😊
However, I cannot get the Windows guest to work. The GPU was correctly recognized as UHD 630, after the Intel driver 25.20.10.6577, which was the only one listed on the Intel webpage as being compatible with the i7 8750H model, had been installed. Running the Windows 10 x64 UEFI client with the same host configuration as for the Linux guest does not give any display output when vga=none is set, however. The client does boot though, as I could verify via ssh/vnc. Dmesg on the host shows several error messages in the same format, which appear just after the client startup has been triggered (compare DmesgBeforeWin10Start.txt with DmesgAfterWin10Start.txt):
[ 105.806639] kvm [5630]: vcpu0, guest rIP: 0xfffff80123de62dc ignored rdmsr: 0x611
This behaviour is reproducible every time on my system. My startup script is an adapted UEFI version of the example for dma-buf with GTK (see StartWin10Guest.txt).
Did I install the right driver version, or is there another one I should try instead?
Host System:
System: Thinkpad P72 OS: Arch Linux CPU: Coffee Lake (i7-8750H) GPU: Optimus system with UHD Graphics 630 + Quadro P600 Driver: xf86-video-intel 1:2.99.917+860+g3a2dec17-1 nvidia-dkms 418.43-4 Branch: gvt-staging (built 03.03.19)