sorry for the accidental incomplete sending,
I cannot see anything in my knowledge, but people more experienced than
me could catch what's wrong. Furthermore, since the correct drivers
attach as shown by lspci, and your later update-initramfs, it doesn't
matter.
- Zycor
> Hi,
>
> I'm a newbie and I have tried many ways to passthrough the gpu to the
> guest. It works well but I found many guides is outdated. So I have
> some questions.
>
> 1. How many ways to achieve the gpu passthrough nowadays, legacy vga
> via seabios、non-vga(UEFI) via OVMF? What's the differe
> OK, I did the following:
>
> * Added the 'qemu' user to the 'input' group.
> * Edited /etc/libvirt/qemu.conf to add the evdev devices
> * Restarted libvirtd
>
> I still get the same error.
>
> poc
>
- Check the ownership of the /dev/input/ devices matches what I've seen
in my experience (root:i
https://www.reddit.com/r/VFIO/comments/4ued9a/passing_evdev_devices_for_keyboardmouse/
pressing the two control keys switches keyboard and mouse between host
and a single guest
___
vfio-users mailing list
vfio-users@redhat.com
https://www.redhat.com/mai
all known CPUs and AMD might not be a good choice. I'd expect more
to come out now that researchers' attention is on this subject.
- Zycorax Tokoroa
On 07/01/18 12:28, Ivan Volosyuk wrote:
> From what I heard virtualization setups suffer the most from the
> vulnerabilities. Af
> This is probably slightly OOT, I’m intrigued in setting up with pure
> libvirt without virt-manager (virsh?), is there any converter that you
> use to migrate from pure QEMU command line? I don’t really like the way
> virt-manager force me to use specific location for my image storage
> pool, wh
tching usually means you are using incompatible versions of the
patch and the kernel together, where the code has changed enough to
confuse patch. As it has been told, look for a patch that's appropriate
to your kernel version. Errors during the building of the kernel need
more detail to be understood
Zycorax Tokoroa
___
vfio-users mailing list
vfio-users@redhat.com
https://www.redhat.com/mailman/listinfo/vfio-users
file where applicable
On Mon, May 2, 2016 at 2:40 AM, Zycorax Tokoroa mailto:zyco...@phoxden.xyz>> wrote:
I seem to have troubles in getting vfio to work under ubuntu.
I have two discrete graphic cards, a GTX 970 (to be passed trough)
and a GTX 960 for the host. The GTX 960 is
It'd seem nvidia-361 doesn't do the trick and leaves the second card
bound to vfio-pci. I haven't tried other versions on 16.04, but I recall
that older drivers had the same issues on 15.10.
Thanks for the help.
Hi,
I forgot to add that I too blacklist nouveau module, but I use nvidia
module
efault setup.
FWIW I used to isolate 6 of the 12 logical cores of my processor and to
pin the vCPUs to them. I haven't seen the host choking, not tuning just
gets a slightly worse performance on the VM
Zycorax Tokoroa
___
vfio-users maili
Thanks, I guess that was just a nobbish question then..
I was also wondering about SLI/CF, as far as you know, as long the iommu
groups are properly isolated, can one get sli/cf working by porting two
identical GPUs on one guest, and occasionally reassign one of the GPUs
to a second guest and run
11 matches
Mail list logo
