[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#813657: progress?



* Daniel Pocock <daniel@pocock.pro> [2016-03-02 13:01]:
> Have you heard about anybody starting on this package?

Michael Tokarev said he might package it.  I haven't heard from anyone
else.

Unfortunately, I cannot answer any of the questions.  I'd like to use
virgl and qemu but I have never done so yet.

> I cloned the upstream git and I was able to build the binary:
> 
> sudo apt-get install libepoxy-dev
> ./autogen.sh
> make -j13
> $ find . -name '*.so*'
> ./src/gallium/auxiliary/Makefile.sources
> ./src/.libs/libvirglrenderer.so.0.2.0
> ./src/.libs/libvirglrenderer.so.0
> ./src/.libs/libvirglrenderer.so
> 
> Is there any documentation or quickstart that explains the complete
> virgl solution?  For example,
> - which client application is used to access the VM? Does it rely on a
> network protocol or does it give the VM direct video window access when
> running locally?
> - which other Debian packages need updating?  I saw #813658
> - is an updated kernel only required in a guest or also in the host?
> - is there a driver for Windows guests?
> 
> I saw some comments that some features are in the 4.2 kernel but others
> are in 4.4:
> https://virgil3d.github.io/
> "Kernel Linux 4.2 contains the modesetting only drivers. Linux 4.4
> contains the 3D supported pieces."
> 4.4 appears to be in unstable, 4.3 in backports, so jessie users might
> have to build their own kernel for now.
> 
> Regards,
> 
> Daniel

-- 
Martin Michlmayr
http://www.cyrius.com/


Reply to: