Hi
I have a working configuration with ubuntu guest. I tried using 1G pages
and found that I need at least 4G for the linux driver to load. I am using
the standard XFX roms that I used to flash the BIOS which are signed and
not modded. I have tried taking the working native windows configuration
a
I have a working configuration with an RX480, Windows 10 guest and Linux
x64 host, but with a Sandy Bridge i5. Can you give more information? Host
kernel version, chipset, iommu groups, qemu/libvirt configuration... Have
you ever managed to get it working with a different graphics card or guest
OS?
I have 2 Xeon 5540s (4 physical and 4 logical per CPU) currently one entire
CPU is dedicated to the vm (basically what it says in numa 0 in lscpu) I
didn't quite get the guide, what would be the best setup to get the most
out of the vm for gaming? Or is that the best configuration I have atm
On Fe
Does the RX480 work with windows 10 guest on linux x64 host haswell vt-d?
I have working config for linux guest but windows 10 gives error -31
"Could not install drivers" and video driver using low res vga driver
(from windows) all booting UEFI.
Have tried 3 different windows version drivers 16.9
Hi Thomas,
awesome work! I've changed my (gaming-)setup (2x Xeon E5-2670 (8 real
cores per CPU)) to the following:
VM1 and VM2:
Each gets 4 real cores on CPU0; Emulator-Thread is pinned to the
respective Hyper-Threading cores.
VM3:
6 real cores on CPU1; Emulator-Thread is pinned to the resp
For windows 10 :
Test 1 : windows native drivers : intel HD620 error ("windows is stopping
this periphical ...code 43 )
Test 2 : windows + intel drivers from intel site : intel HD620 error,
it installs but , same error driver in device manager
In the two case, windows display a very basic scree
On Thu, 2 Feb 2017 13:18:55 +0700
harry tulus wrote:
> What's the different pci-stub of vfio exactly?
pci-stub is a dummy driver. AIUI it was originally developed because
the original KVM device assignment didn't actually bind to the assigned
device as a host driver, it simply grabbed the devic
On Thu, 2 Feb 2017 17:35:48 +0100
nicolas prochazka wrote:
> So for linux guest , it is a kernel i915 version problem, too old for
> kabylake .
> with fedora 25, 4.8.13 wayland start nicely and glxinfo is ok.
So Linux is OK with the QEMU patch? Clearly the guest drivers need to
support the ha
So for linux guest , it is a kernel i915 version problem, too old for
kabylake .
with fedora 25, 4.8.13 wayland start nicely and glxinfo is ok.
For windows, i'm trying with windows native, no success, then with last
kabylake igd driver from intel.
Is you want, i can prepare an acces to linux k
On Thu, 2 Feb 2017 15:50:54 +0100
nicolas prochazka wrote:
> So :
> - Host is now in 4.11 with patch , linux guest always in 4.4.
> -> nothing seems to be change
> screen is divide into 3.
>
> - Then after :
> https://lists.nongnu.org/archive/html/qemu-devel/2016-12/msg01600.html
>
> Screen i
So :
- Host is now in 4.11 with patch , linux guest always in 4.4.
-> nothing seems to be change
screen is divide into 3.
- Then after :
https://lists.nongnu.org/archive/html/qemu-devel/2016-12/msg01600.html
Screen is now as simple screen, so it's better but :
- IGD does not work,
under win10 =>
Oops. Forgot, that it was a qemu patch against non-released
qemu-2.9. Sometimes it is helpful to have a developer correcting the bad
memory segments of mailing list subscribers. ;) So that one might
actually also help. Is the Kabylake kernel fix irrelevant in this case?
Thanks,
Manuel
> On Thu, Feb
On Thu, Feb 2, 2017 at 5:54 AM, nicolas prochazka <
prochazka.nico...@gmail.com> wrote:
> Hello,
> We are using vfio igd passthrough :
> Win10 | Linux ubuntu : broadwell IGD / skylake IGD ( intel nuc
> plateforme )
> without problem, igd is working well .
>
>
> Now with the new intel nuc ( kaby
Ok, thanks for 2. I just found it funny, that I’ve seen this on
bare-metal too. 1: Yeah, I was unsure about that. I considered 2 guest
systems as a possibility, but the description was unclear. So yes, you
most likely need the patch for Kabylake, which will be in 4.11, so it is
not available in any
I think I made myself misunderstood,
1 - Host is Linux kernel 4.9.7 .
Linux ubuntu 4.4 is the guest.
The patch in 4.11 is relevant to guest machine or host machine ?
2 - yes.
Regards,
Nicolas
2017-02-02 14:41 GMT+01:00 Manuel Ullmann :
> Hi,
>
> in theory kernel 4.4 does not support vfio-
Hi,
in theory kernel 4.4 does not support vfio-igd yet, but since it works
for Broadwell/Skylake, Ubuntu seems to have backported the patches.
There was a fix released for Kabylake, that will be introduced in kernel
v4.11. Interesting by the way, that it works to some extent. I’ve seen
that scree
Hello,
We are using vfio igd passthrough :
Win10 | Linux ubuntu : broadwell IGD / skylake IGD ( intel nuc plateforme
)
without problem, igd is working well .
Now with the new intel nuc ( kabylake / nuc7i) ,
Neither windows nor linux recognize intel graphic card.
Under windows, drivers is on e
17 matches
Mail list logo
