Re: [vfio-users] Problem with vfio-pci device type and memory > 10G (or 8G)

Thanks Alex! Will try to reduce the memory used and check. Anjali From: Alex Williamson mailto:alex.l.william...@gmail.com>> Date: Tuesday, December 13, 2016 at 3:23 PM To: Anjali Kulkarni mailto:anj...@juniper.net>> Cc: "vfio-users@redhat.com" mailto:vfio-users@re

Re: [vfio-users] Problem with vfio-pci device type and memory > 10G (or 8G)

On Tue, Dec 13, 2016 at 4:15 PM, Anjali Kulkarni wrote: > Thanks Alex, I think you got it, there is a lot of memory (251G), but it > seems to be mostly all in use: > > vmstat -s > > 263843488 K total memory > > 254973760 K used memory > > > Everything looks used up? > The difference

Re: [vfio-users] Problem with vfio-pci device type and memory > 10G (or 8G)

Thanks Alex, I think you got it, there is a lot of memory (251G), but it seems to be mostly all in use: vmstat -s 263843488 K total memory 254973760 K used memory Everything looks used up? Anjali From: Alex Williamson mailto:alex.l.william...@gmail.com>> Date: Tuesday, Decem

Re: [vfio-users] Problem with vfio-pci device type and memory > 10G (or 8G)

Still missing the most critical piece of information, how much memory is installed in the host? ___ vfio-users mailing list vfio-users@redhat.com https://www.redhat.com/mailman/listinfo/vfio-users

Re: [vfio-users] Problem with vfio-pci device type and memory > 10G (or 8G)

To add, this works perfectly fine (only change from non-working command is memory is changed from 12288 to 4096): /usr/bin/qemu-system-x86_64 -drive if=ide,file=/home/me/myimage.img --enable-kvm -m 4096 -smp 2,sockets=1,cores=1,threads=2 -device vfio-pci,host=03:10.0,id=hostdev0,bus=pci.0,addr

[vfio-users] Problem with vfio-pci device type and memory > 10G (or 8G)

Hi, I am observing that with memory of 10G or 12G, with a vfio-pci device type, qemu hangs and system becomes slow and sluggish, and eventually you need to kill the hung qemu process which never returns. For eg.: /usr/bin/qemu-system-x86_64 -drive if=ide,file=/home/me/myimage.img --enable-kvm

Re: [vfio-users] IGD passthrough: No Seabios output; PTE read access not set

Hi, thanks for the explanation. bios-256k.bin is the only non-symlinked blob on Gentoo. All other blobs of vgabios, sgabios and seabios are symlinked. I switched to libvirt and kernel-4.8.13 in the meantime and have issues with getting hugepages and emulated sound devices to work (in a non-crackl

Re: [vfio-users] IGD passthrough: No Seabios output; PTE read access not set

Hi, > confusing though, that removing the -bios option fixed it. I thought > qemu depends on seabios and if I diff the bios.bin files in > /usr/share/seabios and /usr/share/qemu diff finds no binary differences. > So which bios is qemu now using? Is it built-in? An explanation would be > very mu