KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

Rommy · 2015-01-14 21:05:49

Thank you :-) It works!

nbhs · 2015-01-14 21:06:05

aw wrote:

I think if=none goes on the -drive option...

Yeah sorry, i edited it

Duelist · 2015-01-15 14:29:17

Mmmay be what we need is a new FAQ/OP-post made up. Any opinions/suggestions about that?

tully · 2015-01-16 05:49:08

I've followed the steps and attempted to read through a lot of the comments looking for anything relating to my problem but I haven't found anything to help.

First, my specs

CPU: i7 4790k
Mobo: g1.sniper h6
Main GPU: GTX 970
Passthrough GPU: GTX 260

I currently see no errors in dmesg or from qemu. I am using this to start the VM

qemu-system-x86_64 -enable-kvm -m 1024 -cpu host -smp 4,sockets=1,cores=4,threads=1 -vga none -device vfio-pci,host=06:00.0,x-vga=on

The QEMU 2.2.0 monitor console pops up and when I switch inputs on my monitor all I see is "entering powersave mode" and no signal seems to be passed to it.

The only dmesg info that shows up is this

[ 2283.841755] vfio-pci 0000:06:00.0: enabling device (0400 -> 0403)

I am using the kernel supplied in OP's post which was built using makepkg. The card is picked up by pci-stub in dmesg, the vfio-bind command works without error.

Last edited by tully (2015-01-16 06:09:22)

ceri · 2015-01-16 06:35:48

Duelist wrote:

Mmmay be what we need is a new FAQ/OP-post made up. Any opinions/suggestions about that?

It would be nice to have everything that's known all in one place, as opposed to scattered all around this thread with no decent way of searching (besides awkward google searches). I think putting it on the arch wiki would be best since it would be editable by all.

I actually considered starting one but I don't have time to maintain it. Here is a collection of useful links I found for my personal usage:
http://pastebin.com/sdkZPykz

(for some links, you have to scroll down to a *reply* with the useful info)

slis · 2015-01-16 07:21:25

@ tully
try using rom file for your gpu

sinny · 2015-01-16 08:43:37

tully wrote:

I've followed the steps and attempted to read through a lot of the comments looking for anything relating to my problem but I haven't found anything to help.
First, my specs
CPU: i7 4790k
Mobo: g1.sniper h6
Main GPU: GTX 970
Passthrough GPU: GTX 260
I currently see no errors in dmesg or from qemu. I am using this to start the VM
qemu-system-x86_64 -enable-kvm -m 1024 -cpu host -smp 4,sockets=1,cores=4,threads=1 -vga none -device vfio-pci,host=06:00.0,x-vga=on
The QEMU 2.2.0 monitor console pops up and when I switch inputs on my monitor all I see is "entering powersave mode" and no signal seems to be passed to it.
The only dmesg info that shows up is this
[ 2283.841755] vfio-pci 0000:06:00.0: enabling device (0400 -> 0403)
I am using the kernel supplied in OP's post which was built using makepkg. The card is picked up by pci-stub in dmesg, the vfio-bind command works without error.

there is a note in OP:

NOTE: There might be some problems using nvidia/fglrx/nouveau drivers on the host gpu, see the ISSUES section below on how to solve this.

i beleive there was a note in now-missing ISSUES section about the need to patch nvidia drivers if both host and guest are using nvidia gpus (or something like that - cant remember for sure)

Last edited by sinny (2015-01-16 08:43:49)

winie · 2015-01-16 11:42:53

tully wrote:

I've followed the steps and attempted to read through a lot of the comments looking for anything relating to my problem but I haven't found anything to help.
First, my specs
CPU: i7 4790k...

I suggest you to use the intel integrated gpu as main gpu and use OVMF uefi in guest instead of bios

zlice · 2015-01-16 13:18:11

don't see a way to search just this thread (156 pages)

i have 2 cards - problem is the card i'd like to passthrough is seen by my mobo(asus) as primary, guessing because it's in slot1, but i can't swap it because the thing's so big

is there any way to switch the pci bus? i've seen people talk about modding kernel code but i don't really know where i'd start to look if that's even the answer

edit:
Asus M5A99FX PRO R20
pci-stub is in dmesg but the card is still what displays bios and OS
even trying to run Xorg on the card i want, it grabs pci:1:0:0 even though it's not in my xorg.conf
both ati/amd cards (5870 and 290)

Last edited by zlice (2015-01-16 13:23:03)

tully · 2015-01-16 15:12:30

winie wrote:

tully wrote:
I've followed the steps and attempted to read through a lot of the comments looking for anything relating to my problem but I haven't found anything to help.
First, my specs
CPU: i7 4790k...
I suggest you to use the intel integrated gpu as main gpu and use OVMF uefi in guest instead of bios

I have three monitors. I can't extend to 3 monitors with IGP.

tully · 2015-01-16 16:18:17

slis wrote:

@ tully
try using rom file for your gpu

I pulled the ROM with gpu-z in windows and tried a few from techpowerup. Here is the output when I try to use it.

root@tully ~]# qemu-system-x86_64 -enable-kvm -M q35 -m 4G -cpu host -smp 3,sockets=1,cores=3,threads=1 -bios /usr/share/qemu/bios.bin -k en-us -no-reboot -vga none -device qxl -device ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1 -device vfio-pci,host=06:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on,rombar=0,romfile=/root/GT200.rom -boot menu=on
dma: command 84 not supported
dma: command 84 not supported
dma: command b4 not supported
dma: command b4 not supported
dma: command 84 not supported
dma: command 84 not supported
dma: command 78 not supported
dma: command c not supported
dma: command 48 not supported
dma: command 48 not supported
dma: command 4c not supported
dma: command c not supported

Myranti · 2015-01-16 16:37:43

zlice wrote:

i have 2 cards - problem is the card i'd like to passthrough is seen by my mobo(asus) as primary, guessing because it's in slot1, but i can't swap it because the thing's so big
is there any way to switch the pci bus? i've seen people talk about modding kernel code but i don't really know where i'd start to look if that's even the answer

Unless there's an option in your bios to actually choose which PCIe slot to boot primary graphics from, which from a look at the manual doesn't seem to be the case and not something I have on my own board (Asus P9D WS), so your only other option is to swap the cards around.

When you say you can't swap because it's too big, is it because it wouldn't fit in that spot in the case or because it's taking up another slot that you're using or due to the physical constraints of the case? It looks like, from the manual, that only two of the PCIe/PCI slots are PCIe 2 x16 slots on that board as well (1 and 4).

Last edited by Myranti (2015-01-16 16:38:06)

zlice · 2015-01-16 16:54:23

Myranti wrote:

zlice wrote:
i have 2 cards - problem is the card i'd like to passthrough is seen by my mobo(asus) as primary, guessing because it's in slot1, but i can't swap it because the thing's so big
is there any way to switch the pci bus? i've seen people talk about modding kernel code but i don't really know where i'd start to look if that's even the answer
Unless there's an option in your bios to actually choose which PCIe slot to boot primary graphics from, which from a look at the manual doesn't seem to be the case and not something I have on my own board (Asus P9D WS), so your only other option is to swap the cards around.
When you say you can't swap because it's too big, is it because it wouldn't fit in that spot in the case or because it's taking up another slot that you're using or due to the physical constraints of the case? It looks like, from the manual, that only two of the PCIe/PCI slots are PCIe 2 x16 slots on that board as well (1 and 4).

ya there's nothing in bios about video but switching PEG/PCI which does nothing.
and yes the card it too big, i'd have to cut up the HD holder.

i may try to unbind/bind and ssh to see if i can get anything to happen...then i'm going to take it out of the case to make sure slot1 is what's making it display (probably why)

if i can get it working out of the case...i'll probably burn another $70...

sinny · 2015-01-16 17:31:47

tully wrote:

winie wrote:
tully wrote:
I've followed the steps and attempted to read through a lot of the comments looking for anything relating to my problem but I haven't found anything to help.
First, my specs
CPU: i7 4790k...
I suggest you to use the intel integrated gpu as main gpu and use OVMF uefi in guest instead of bios

I have three monitors. I can't extend to 3 monitors with IGP.

well, if you gonna ignore possible need to patch nvidia drivers, you could try twisting your setup a bit:
- [ host ] virtualization host, nothing more (minimal install)
- [ guest0 ] takes the role of your current triple-monitor host
- [ guest1 ] your currently desired guest (i assume windows)

Denso · 2015-01-16 18:47:54

Hi everyone , long time no see .

Does anyone experience soft lockups of VMs once every couple of minutes ?

I always experience such lockups that lasts for a second or less in every Windows 8.1 VM I have . This is on my X99 host by the way .

CMD line if anyone would have an idea what's causing them :

qemu-system-x86_64 -name main -nographic \
-enable-kvm -m 8192 -cpu host,kvm=off -smp 2,sockets=1,cores=2,threads=1 \
-vga none -nodefconfig \
-drive if=pflash,format=raw,readonly,file=/usr/share/ovmf/x64/ovmf_code_x64.bin \
-drive if=pflash,format=raw,file=/VMs/ovmf_main.bin \
-device vfio-pci,host=05:00.0,multifunction=on \
-device vfio-pci,host=05:00.1 \
-device vfio-pci,host=0f:00.0 \
-device vfio-pci,host=00:1b.0 \
-drive file=/VMs/Win_Main.img,cache=none,format=raw,if=none,id=drive0,aio=native \
-device virtio-blk-pci,drive=drive0,ioeventfd=on,bootindex=1 \
-device virtio-scsi-pci,id=scsi \
-drive file=/VMs/Win8.iso,id=iso_install,if=none \
-device scsi-cd,drive=iso_install \
-cdrom /VMs/virtio.iso \
-localtime \
-net nic,model=virtio,macaddr=33:29:21:5F:C4:7D -net bridge,br=br0 \
-monitor unix:/tmp/vm_main,server,nowait &

I believe that heavy HDD activity causes it more often . These VMs are sitting on a 4 disk RAID0 . Disks are 7200 ones .

tully · 2015-01-16 19:01:00

sinny wrote:

tully wrote:
winie wrote:
I suggest you to use the intel integrated gpu as main gpu and use OVMF uefi in guest instead of bios

I have three monitors. I can't extend to 3 monitors with IGP.
well, if you gonna ignore possible need to patch nvidia drivers, you could try twisting your setup a bit:
- [ host ] virtualization host, nothing more (minimal install)
- [ guest0 ] takes the role of your current triple-monitor host
- [ guest1 ] your currently desired guest (i assume windows)

Would you mind elaborating on that setup? I'm assuming you are suggesting that I passthrough my 970 to a linux VM and then the 260 to a windows VM. I would think that if the 260 doesn't currently work with this setup that OP provided that it wouldn't work under those circumstances either. I'm probably missing something though which is why I'm asking for clarification.

I wasn't attempting to ignore patching the nvidia drivers, I simply haven't found any up to date information on doing it. The last I saw was about two years ago and I'd prefer to be on a more recent driver.

If I can't get the 260 to work I think the next recourse is to just bit the bullet and run two monitors off the 260 and one off the IGP. From my understanding I can't have 3 monitors extended and able to pass applications back and forth with that setup. But, I should be able to use OVMF with the 970 I think. Do you know if the host gpu has to support OVMF as well or is it only the GPU that is getting passed through?

Thanks

Denso · 2015-01-16 19:23:36

Do you know if the host gpu has to support OVMF as well or is it only the GPU that is getting passed through?

Only the GPU you're passing-through . OVMF has nothing to do with your host GPUs .

walkindude · 2015-01-16 21:29:21

Tried to switch GPUs on my mobo:

so, now we have

HD 6850, x16, blue
R9 270, x4, black

after reboot can't load to my kernel, it just stuck on
grub complaining about diskfilter writes (system's on lvm, just wait or press any key -> it goes away, and system boots as expected)

It doesn't matter if I removed pci-ids or not.

But I managed to boot in ARCH-kernel, and now I get in dmesg:

walkindude@Desktop> sudo dmesg | grep -i AMD-Vi ~
[sudo] password for walkindude:
[ 0.107871] AMD-Vi: device: 00:00.2 cap: 0040 seg: 0 flags: 3e info 1300
[ 0.107872] AMD-Vi: mmio-addr: 00000000feb20000
[ 0.107883] AMD-Vi: DEV_SELECT_RANGE_START    devid: 00:00.0 flags: 00
[ 0.107885] AMD-Vi: DEV_RANGE_END    devid: 00:00.2
[ 0.107886] AMD-Vi: DEV_SELECT    devid: 00:02.0 flags: 00
[ 0.107887] AMD-Vi: DEV_SELECT_RANGE_START    devid: 01:00.0 flags: 00
[ 0.107888] AMD-Vi: DEV_RANGE_END    devid: 01:00.1
[ 0.107889] AMD-Vi: DEV_SELECT    devid: 00:11.0 flags: 00
[ 0.107890] AMD-Vi: DEV_SELECT_RANGE_START    devid: 00:12.0 flags: 00
[ 0.107891] AMD-Vi: DEV_RANGE_END    devid: 00:12.2
[ 0.107892] AMD-Vi: DEV_SELECT_RANGE_START    devid: 00:13.0 flags: 00
[ 0.107893] AMD-Vi: DEV_RANGE_END    devid: 00:13.2
[ 0.107894] AMD-Vi: DEV_SELECT    devid: 00:14.0 flags: d7
[ 0.107895] AMD-Vi: DEV_SELECT    devid: 00:14.3 flags: 00
[ 0.107896] AMD-Vi: DEV_SELECT    devid: 00:14.4 flags: 00
[ 0.107898] AMD-Vi: DEV_ALIAS_RANGE    devid: 02:00.0 flags: 00 devid_to: 00:14.4
[ 0.107898] AMD-Vi: DEV_RANGE_END    devid: 02:1f.7
[ 0.107906] AMD-Vi: DEV_SELECT    devid: 00:14.5 flags: 00
[ 0.107907] AMD-Vi: DEV_SELECT    devid: 00:15.0 flags: 00
[ 0.107908] AMD-Vi: DEV_SELECT_RANGE_START    devid: 03:00.0 flags: 00
[ 0.107909] AMD-Vi: DEV_RANGE_END    devid: 03:00.1
[ 0.107910] AMD-Vi: DEV_SELECT_RANGE_START    devid: 00:16.0 flags: 00
[ 0.107911] AMD-Vi: DEV_RANGE_END    devid: 00:16.2
[ 0.107912] AMD-Vi: DEV_SPECIAL(IOAPIC[0]) devid: 00:14.0
[ 0.107914] AMD-Vi: DEV_SPECIAL(HPET[0]) devid: 00:14.0
[ 0.107915] AMD-Vi: DEV_SPECIAL(IOAPIC[255]) devid: 00:00.1
[ 2.908990] AMD-Vi: Found IOMMU at 0000:00:00.2 cap 0x40
[ 2.908992] AMD-Vi: Interrupt remapping enabled
[ 2.909114] AMD-Vi: Initialized for Passthrough Mode
[ 3.045906] AMD-Vi: Completion-Wait loop timed out
[ 3.156248] AMD-Vi: Completion-Wait loop timed out
[ 3.266509] AMD-Vi: Completion-Wait loop timed out
[ 3.376798] AMD-Vi: Completion-Wait loop timed out
[ 3.487084] AMD-Vi: Completion-Wait loop timed out
[ 3.597349] AMD-Vi: Completion-Wait loop timed out
[ 3.707628] AMD-Vi: Completion-Wait loop timed out
[ 3.817917] AMD-Vi: Completion-Wait loop timed out
[ 3.928191] AMD-Vi: Completion-Wait loop timed out
[ 4.017795] AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=03:00.0 address=0x00000002331e88e0]
[ 4.017805] AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=03:00.0 address=0x00000002331e8900]
[ 4.017810] AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=03:00.0 address=0x00000002331e8930]

If I switch GPUs back,my kernel boots, but during this process I'm seing something strange (can't find it later in logs, so I shot it by my phone camera)
http://rghost.net/private/60392304/15d7 … e5413.view
These two line were present on all my attempts (on this and previous pages of current topic)

In dmesg after

AMD-Vi: Initialized for Passthrough Mode

nothing, no lines about

Completion-Wait loop timed out or

Event logged [IOTLB_INV_TIMEOUT device=03:00.0 address=0x00000002331e8900]

UEFI bios on my mobo (M5A97 PRO) is the latest available: 1604. I'd flashed it a long time ago, during the installation of FX CPU.

What is wrong here? Should I buy the second revision or completely another AM3+ motherboard? or smth wrong in my settings?

tully · 2015-01-16 22:08:57

Denso wrote:

Do you know if the host gpu has to support OVMF as well or is it only the GPU that is getting passed through?
Only the GPU you're passing-through . OVMF has nothing to do with your host GPUs .

Thanks. I've reconfigured my rig now. My gtx 260 is in the primary pcie slot, gtx 970 in the second. I've got all the monitors working and extended with xrandr. Time to give OVMF a shot.

dwe11er · 2015-01-16 22:58:41

Denso wrote:

Hi everyone , long time no see .
Does anyone experience soft lockups of VMs once every couple of minutes ?
I always experience such lockups that lasts for a second or less in every Windows 8.1 VM I have . This is on my X99 host by the way .
CMD line if anyone would have an idea what's causing them :
qemu-system-x86_64 -name main -nographic \
-enable-kvm -m 8192 -cpu host,kvm=off -smp 2,sockets=1,cores=2,threads=1 \
-vga none -nodefconfig \
-drive if=pflash,format=raw,readonly,file=/usr/share/ovmf/x64/ovmf_code_x64.bin \
-drive if=pflash,format=raw,file=/VMs/ovmf_main.bin \
-device vfio-pci,host=05:00.0,multifunction=on \
-device vfio-pci,host=05:00.1 \
-device vfio-pci,host=0f:00.0 \
-device vfio-pci,host=00:1b.0 \
-drive file=/VMs/Win_Main.img,cache=none,format=raw,if=none,id=drive0,aio=native \
-device virtio-blk-pci,drive=drive0,ioeventfd=on,bootindex=1 \
-device virtio-scsi-pci,id=scsi \
-drive file=/VMs/Win8.iso,id=iso_install,if=none \
-device scsi-cd,drive=iso_install \
-cdrom /VMs/virtio.iso \
-localtime \
-net nic,model=virtio,macaddr=33:29:21:5F:C4:7D -net bridge,br=br0 \
-monitor unix:/tmp/vm_main,server,nowait &
I believe that heavy HDD activity causes it more often . These VMs are sitting on a 4 disk RAID0 . Disks are 7200 ones .

It's probably because you're using images instead of block devices (and if your fs is btrfs then can be even worse. Also, how much RAM did you left for your host?

Denso · 2015-01-16 23:09:25

dwe11er wrote:

It's probably because you're using images instead of block devices (and if your fs is btrfs then can be even worse. Also, how much RAM did you left for your host?

I went the RAW images path because they're easy to manage , move around , duplicate and delete . Those soft lock-ups used to happen alot when I was using QCOW2 images , they are alot less now with RAW but not gone completely . The RAID0 which all of these images are is an MDRAID (RAID0) + EXT4 . About the ram , now the whole system is consuming 18GB out of 32GB total , so It's not about the RAM I guess .

tully · 2015-01-17 03:08:56

Update: We have video! Using the 970 as the passthrough and OVMF I was able to get output to the screen. However, I'm unable to get the VM to boot from the windows iso. When trying it I see "Boot failed. EFI DVD/CDROM 1", it tries to pxe boot, then it kicks over to the UEFI Interactive shell v2.1.

Here is my qemu launch script

qemu-system-x86_64 -enable-kvm -m 8192 -cpu host,kvm=off -smp 2,cores=2,threads=1 \
-vga none \
-drive if=pflash,format=raw,file=/usr/share/ovmf/ovmf_x64.bin \
-device virtio-scsi-pci,id=scsi \
-device vfio-pci,host=06:00.0,multifunction=on \
-device vfio-pci,host=06:00.1 \
-drive file=/VMs/win.img,id=disk,format=raw,if=none -device scsi-hd,drive=disk \
-drive file=/VMs/win8.iso,id=isocd,if=none -device scsi-cd,drive=isocd \
-drive file=/VMs/virt.iso,id=virtiocd,if=none -device ide-cd,bus=ide.1,drive=virtiocd \
-boot menu=on

Also, this is probably pretty stupid but I haven't found an answer anywhere else. How exactly are you guys using your keyboard and mouse in the guest? I saw a youtube video of someone using synergy so that seems like a good option, but other than plugging in a separate keyboard and passing it through as well I'm at a loss as to how I'm supposed to share the keyboard and mouse without them potentially getting stuck in the guest. Thanks for all of your help.

zlice · 2015-01-17 08:30:33

so after messing around for quite some time. i ended up with an old 8600gts and my r290...

maybe it's an issue someone came across on this thread, but can someone tell me how my video output is from my passthrough but device manager/amd doesn't know it's an amd card?
changed my qemu command a few times, maybe i have to redo the VM.

Denso · 2015-01-17 10:27:56

tully wrote:

Update: We have video! Using the 970 as the passthrough and OVMF I was able to get output to the screen. However, I'm unable to get the VM to boot from the windows iso. When trying it I see "Boot failed. EFI DVD/CDROM 1", it tries to pxe boot, then it kicks over to the UEFI Interactive shell v2.1.

Use this to assign the ISO to the VM :

-device virtio-scsi-pci,id=scsi \
-drive file=/VMs/win8.iso,id=iso_install,if=none \
-device scsi-cd,drive=iso_install \

Good luck !

Myranti · 2015-01-17 16:10:41

tully wrote:

How exactly are you guys using your keyboard and mouse in the guest? I saw a youtube video of someone using synergy so that seems like a good option, but other than plugging in a separate keyboard and passing it through as well I'm at a loss as to how I'm supposed to share the keyboard and mouse without them potentially getting stuck in the guest.

My setup is less common I assume, but I actually have essentially a dumb* USB switch setup (well, 2 of them actually), that I soldered together with some 4 Pole Double Throw (4PDT), On-Off-On switches and some short USB connectors and then have a separate PCIe USB 3 card passed through to the guest, giving me dedicated USB ports on the guest with separate USB connections going to the host and guest (via the USB 3 card) and then switch between them with the switches. You could also get some sort of basic USB switch if you were using something like a dedicated USB card, the kind of thing that's designed to share printers for instance (like an Aten US221A), though depending on the keyboard it might not pass through multimedia keys or other special keys (like the Roccat keyboard and mouse I used to use).

* When I say dumb, I mean that it's not like the Aten US221A that I mentioned which normally keeps the devices enumerated on each system whether connected to a particular system or not. In my setup it's dumb and actually results in disconnection of the electrical circuit, akin to unplugging and plugging the cable back in, also meaning that the keyboard and mouse have to re-enumerate each time you switch systems.

Arch Linux

#3876 2015-01-14 21:05:49

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

#3877 2015-01-14 21:06:05

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

#3878 2015-01-15 14:29:17

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

#3879 2015-01-16 05:49:08

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

#3880 2015-01-16 06:35:48

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

#3881 2015-01-16 07:21:25

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

#3882 2015-01-16 08:43:37

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

#3883 2015-01-16 11:42:53

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

#3884 2015-01-16 13:18:11

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

#3885 2015-01-16 15:12:30

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

#3886 2015-01-16 16:18:17

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

#3887 2015-01-16 16:37:43

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

#3888 2015-01-16 16:54:23

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

#3889 2015-01-16 17:31:47

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

#3890 2015-01-16 18:47:54

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

#3891 2015-01-16 19:01:00

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

#3892 2015-01-16 19:23:36

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

#3893 2015-01-16 21:29:21

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

#3894 2015-01-16 22:08:57

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

#3895 2015-01-16 22:58:41

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

#3896 2015-01-16 23:09:25

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

#3897 2015-01-17 03:08:56

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

#3898 2015-01-17 08:30:33

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

#3899 2015-01-17 10:27:56

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

#3900 2015-01-17 16:10:41

Re: KVM VGA-Passthrough using the new vfio-vga support in kernel =>3.9

Board footer